Wireless communication method, and device and storage medium

Abstract

Provided in the embodiments of the present application are a wireless communication method, and a device and a storage medium. The method comprises: a terminal device sending first information, wherein the first information comprises information of first data, and the first data is data having remaining time meeting a latency requirement.

Description

Wireless communication method, device, and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technologies, and in particular to a wireless communication method and device, and a storage medium. Background Art

[0002] In communication systems, some services require low latency, high throughput, and high reliability, such as the extended reality (XR) service in the fifth-generation (5G) wireless communication system. In XR services, data usually consists of multiple quality of service (QoS) flows, and its service volume is very large. XR service flows need to meet certain latency requirements during transmission, especially since some data streams need to arrive at the server for decoding at the same time. The delay of any one data stream will cause the joint decoding of multiple data streams to fail.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a wireless communication method and device, and a storage medium.

[0005] The wireless communication method provided in the embodiment of the present application includes:

[0006] The terminal device sends a first message, where the first message includes information about first data, and the first data is data for which the remaining time meets the delay requirement.

[0007] The wireless communication method provided in the embodiment of the present application includes:

[0008] The terminal device sends third data, and the third data includes first data and second data, the first data is data that the remaining time meets the delay requirement, and the second data is data that the remaining time does not meet the delay requirement.

[0009] The wireless communication method provided in the embodiment of the present application includes:

[0010] The terminal device sends third information, which includes information about the data volume of the first data and information about the data volume of the second data. The first data is data that meets the delay requirement in the remaining time, and the second data is data that does not meet the delay requirement in the remaining time.

[0011] The wireless communication method provided in the embodiment of the present application includes:

[0012] The network device receives first information, where the first information includes information about first data, and the first data is data for which remaining time meets a delay requirement.

[0013] The wireless communication method provided in the embodiment of the present application includes:

[0014] The network device receives third data, where the third data includes first data and second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0015] The wireless communication method provided in the embodiment of the present application includes:

[0016] The network device receives third information, which includes information about the data volume of first data and information about the data volume of second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0017] The terminal device provided in the embodiment of the present application includes:

[0018] The first communication unit is configured to send first information, where the first information includes information about first data, and the first data is data whose remaining time meets the delay requirement.

[0019] The terminal device provided in the embodiment of the present application includes:

[0020] The second communication unit is configured to send third data, where the third data includes first data and second data, the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0021] The terminal device provided in the embodiment of the present application includes:

[0022] The third communication unit is configured to send third information, where the third information includes information about the data volume of the first data and information about the data volume of the second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0023] The network device provided in the embodiment of the present application includes:

[0024] The fourth communication unit is configured to receive first information, where the first information includes information about first data, and the first data is data whose remaining time meets the delay requirement.

[0025] The network device provided in the embodiment of the present application includes:

[0026] The fifth communication unit is configured to receive third data, where the third data includes first data and second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0027] The network device provided in the embodiment of the present application includes:

[0028] The sixth communication unit is configured to receive third information, wherein the third information includes information about the data volume of the first data and information about the data volume of the second data, the first data is data that meets the delay requirement in the remaining time, and the second data is data that does not meet the delay requirement in the remaining time.

[0029] The communication device provided in an embodiment of the present application may be a terminal device or a network device in the above-mentioned solution, and the communication device includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory to perform the above-mentioned wireless communication method.

[0030] The chip provided in the embodiment of the present application is used to implement the above-mentioned wireless communication method.

[0031] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned wireless communication method.

[0032] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned wireless communication method.

[0033] The computer program product provided in the embodiments of the present application includes computer program instructions, which enable a computer to execute the above-mentioned wireless communication method.

[0034] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned wireless communication method.

[0035] Through the above technical solution, the terminal device sends the first information to the network device, and the first information is used to indicate the information of non-delay sensitive data, so that the network device can obtain the situation of non-delay sensitive data in the data to be sent by the terminal device, transmit delay sensitive data in time, and ensure the transmission requirements of delay sensitive data. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0037] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0038] FIG2 is a schematic diagram of an optional structure of a delay status report (DSR) media access control control element (MAC CE) according to an embodiment of the present application;

[0039] FIG3 is an optional schematic flow chart of a wireless communication method according to an embodiment of the present application;

[0040] FIG4 is a schematic diagram of an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0041] FIG5 is an optional schematic flow chart of a wireless communication method according to an embodiment of the present application;

[0042] FIG6 is a schematic diagram of an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0043] FIG7 is an optional schematic flow chart of a wireless communication method according to an embodiment of the present application;

[0044] FIG8 is a schematic diagram of an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0045] FIG9 is an optional schematic flow chart of a wireless communication method according to an embodiment of the present application;

[0046] FIG10 is an optional schematic flow chart of a wireless communication method according to an embodiment of the present application;

[0047] FIG11 is an optional schematic flow chart of a wireless communication method according to an embodiment of the present application;

[0048] FIG12 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0049] FIG13 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0050] FIG14 is a schematic diagram of an optional structure of a MAC CE defined in an embodiment of the present application;

[0051] FIG15 is a schematic diagram of an optional structure of a MAC CE defined in an embodiment of the present application;

[0052] FIG16 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0053] FIG17 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0054] FIG18 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0055] FIG19 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0056] FIG20 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0057] FIG21 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0058] FIG22 is a schematic diagram of an optional structure of an enhanced DSR MAC CE provided in an embodiment of the present application;

[0059] FIG23 is a schematic diagram of an optional structure of a MAC CE defined in an embodiment of the present application;

[0060] FIG24 is a schematic diagram of an optional structure of a MAC CE defined in an embodiment of the present application;

[0061] FIG25 is an optional schematic structural diagram of a terminal device provided in an embodiment of the present application;

[0062] FIG26 is an optional schematic structural diagram of a terminal device provided in an embodiment of the present application;

[0063] FIG27 is an optional schematic structural diagram of a terminal device provided in an embodiment of the present application;

[0064] FIG28 is an optional schematic structural diagram of a network device provided in an embodiment of the present application;

[0065] FIG29 is an optional schematic structural diagram of a network device provided in an embodiment of the present application;

[0066] FIG30 is an optional schematic structural diagram of a network device provided in an embodiment of the present application;

[0067] FIG31 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0068] FIG32 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0069] Figure 33 is a schematic block diagram of a communication system provided by an embodiment of the present application. DETAILED DESCRIPTION

[0070] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0071] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0072] As shown in Figure 1, a communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0073] It should be understood that the embodiments of the present application are only illustrative of the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, fifth generation (5G) communication system (also known as New Radio (NR) communication system), or future communication systems.

[0074] In the communication system 100 shown in Figure 1, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area and may communicate with the terminal device 110 (eg, UE) located within the coverage area.

[0075] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0076] The terminal device 110 can be used for device-to-device (D2D) communication.

[0077] The wireless communication system 100 may further include a core network device 130 for communicating with the base station. The core network device 130 may be a 5G core network (5G Core, 5GC) device. During network evolution, the core network device may also be called another name, or a new network entity may be formed by dividing the core network's functions. This embodiment of the present application does not limit this.

[0078] The functional units in the communication system 100 may also establish connections and implement communication via next generation (NG) network interfaces.

[0079] Figure 1 exemplarily shows a base station, a core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base stations and each base station may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0080] Optionally, different terminal devices 110 may perform side-by-side communication.

[0081] It should be noted that Figure 1 is merely an example of a system applicable to this application. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the associated objects are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; or it can mean that A and B have an association relationship. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between two objects, or that there is an association relationship between the two objects, or a relationship between an indicator and the indicated, a configuration and the configured, and so on. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit its specific implementation method. For example, predefined can refer to a definition in a protocol. It should also be understood that in the embodiments of the present application, the “protocol” can refer to a standard protocol in the field of communications, such as an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0082] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0083] A key service in augmented reality (AR), virtual reality (VR), and cloud gaming (CG), or XR / CG, is video streaming. Its arrival rate (measured in frames per second) can be 30fps, 60fps, 90fps, or 120fps. The corresponding video stream periods are {33.33ms, 16.67ms, 11.11ms, and 8.33ms}. XR also has transmission latency requirements.

[0084] For XR, one research direction is scheduling enhancement for latency.

[0085] For UL, enhancements are specified using latency / deadline information to support UL scheduling to achieve high XR capacity while meeting latency requirements / avoiding late PDUs.

[0086] In 5G NR, the network device can configure DSR for the terminal device. When the DSR reporting conditions are met, the terminal device reports the delay information and the corresponding data volume information to the network device. The reporting of the DSR information can help the network device understand the remaining time of the data, and / or assist the network in scheduling. Whether the DSR is triggered is determined by whether the remaining delay of the Packet Data Convergence Protocol (PDCP) discard timer is less than the threshold. The amount of data reported is the amount of delay-critical data. Delay-critical data is data whose remaining delay of the PDCP discard timer is less than the threshold.

[0087] When the network device activates Packet Data Unit (PDU) set important (PSI)-based discard, the PDU set with lower importance will maintain the discardTimerForLowImportance timer. Accordingly, such packets will not be counted in the DSR triggering and the DSR reported data volume even if the remaining delay is small.

[0088] DSR MAC CE

[0089] The DSR MAC CE is identified by the eLCID carried in the MAC subheader.

[0090] The DSR process is used to provide the LCG latency status to the serving base station. The latency status of a Logical Channel Group (LCG) includes the remaining time, which is the minimum remaining value of the PDCP deletion timer in the Service Data Unit (SDU) buffered by the LCG, and the total amount of delay-sensitive uplink data in the LCG calculated based on the data volume calculation process.

[0091] Radio Resource Control (RRC) controls DSR by configuring the following parameters: Remaining Time Threshold, which acts on the remaining time and is used to trigger DSR of the LCG.

[0092] If an LCG is configured for DSR, if the smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in a DSR MAC CE becomes below remainingTimeThreshold of the LCG, and if there is no DSR pending for the LCG since the last transmission of a DSR MAC CE, then the MAC CE shall trigger a DSR for that LCG.

[0093] If there is at least one pending DSR, then:

[0094] If resources are available for new transmission and the resources can carry the DSR MAC CE and its subheader based on the result of logical channel prioritization (LCP), a DSR MAC CE is generated.

[0095] If there is no pending SR that has been triggered with the same logical channel (LCH) as this DSR, then the SR is triggered.

[0096] The fields in the DSR MAC CE, as shown in Figure 2, include:

[0097] LCG i : This field indicates the presence of a i The delay information (i.e., the remaining time and buffer size fields) of the LCG is set to 1. i Field indicating that the report is for LCG i The delay information of LCG is set to 0. i Field indicating no LCG reported i Delay information; where 1 LCG occupies 1 bit.

[0098] Remaining Time: This field indicates the shortest remaining value of the PDCP discardTimer among all PDCP SDUs buffered by the LCG at the time of the first symbol of the first PUSCH transmission including this DSR-MAC CE. This field is 6 bits long. The value r in this field indicates the remaining time in the range of (r, r+1] milliseconds. The remaining time occupies 6 bits.

[0099] Buffer Status Report (BSR) Table (BT): This field is present only if the corresponding LCG is configured with an additional BSR TableAllowed; otherwise, this field is reserved. If present, a BT field set to 1 indicates that the buffer size specified by one table is used to set the value of the Buffer Size field, while a BT field set to 0 indicates that the buffer size specified by another table is used.

[0100] Buffer Size: The Buffer Size field indicates the total amount of delay-critical UL data for the LCG after the MAC PDU has been established, based on the data volume calculation process specified for the associated RLC and PDCP entities respectively. If the corresponding LCG is configured with an additional BSR Table Allowed and the amount of delay-critical UL data for an LCG is within the specified buffer size, the MAC entity shall use the specified buffer size to set the value of this field; otherwise, the MAC entity shall use another table. This field is expressed in bytes. The length of this field is 8 bits (Oct), or 1 byte.

[0101] The Remaining Time, BT, and Buffer Size fields of an LCG shall be reported in two consecutive octets. These three fields for different LCGs shall be included in the DSR MAC CE in ascending order according to LCGi.

[0102] Delay-critical PDCP SDUs, if the parameter pdu-SetDiscard is not configured, indicate the PDCP SDUs for which the remaining time until the expiry of the discardTimer is less than the remaining TimeThreshold. If the parameter pdu-SetDiscard is configured, indicate the PDCP SDUs belonging to a PDU set for which at least one PDCP SDU of the PDU set has a remaining time until the expiry of the discardTimer less than the remaining TimeThreshold.

[0103] For the purpose of MAC DSR, the transmitted PDCP entity shall consider the following as the amount of delay-sensitive PDCP data:

[0104] Delay-sensitive PDCP SDUs that do not form PDCP data PDUs;

[0105] PDCP data PDUs that include delay-sensitive PDCP SDUs and are not delivered to lower layers;

[0106] PDCP control PDU;

[0107] Transmitted PDCP SDU.

[0108] If a PDCP SDU becomes a delay-critical PDCP SDU, and if the corresponding PDCP Data PDU has already been submitted to lower layers, the delay-critical indication for the PDCP Data PDU is provided to lower layers.

[0109] In the related art, the requirement of prioritizing the transmission of delay-sensitive data is not considered between a logical channel (LCH) or multiple LCHs. Specifically, the DSR is reported for the delay-sensitive data of the LCG.

[0110] In some cases, the LCG may contain data from both LCH1 and LCH2, with LCH1 having a higher priority than LCH2. However, the data in LCH1 is not latency-sensitive. Therefore, the network device prioritizes LCH1 data over DSR-scheduled UL resources, preventing the timely transmission of latency-sensitive data on LCH2.

[0111] In other cases, when using PSI-based discard, low importance (low importance), i.e., unimportant PDUs (or PDU sets), i.e., non-delay-sensitive data, and non-low importance PDUs (or PDU sets) may coexist in one LCH, and the low importance PDUs (or PDU sets) may be the data that arrives first. When a non-low importance PDU (or PDU set) triggers a DSR report and the reported DSR does not report the amount of data corresponding to the low importance PDU (or PDU set), but only the amount of data of the non-low importance PDU (or PDU set). In this way, the network device will give priority to transmitting the low importance PDU (or PDU set) data based on the UL resources scheduled by the DSR and the relevant technology, which will result in the non-low importance PDU (or PDU set) data not being transmitted in a timely manner.

[0112] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0113] FIG3 is a wireless communication method provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG3 , the method includes:

[0114] S301. The terminal device sends first information, where the first information includes information about first data, and the first data is data whose remaining time meets the delay requirement.

[0115] FIG4 is a wireless communication method provided in an embodiment of the present application, which is applied to a network device, as shown in FIG4 , including:

[0116] S401. A network device receives first information, where the first information includes information about first data, and the first data is data whose remaining time meets a delay requirement.

[0117] FIG5 is a wireless communication method provided in an embodiment of the present application, which is applied to a wireless communication system including a terminal device and a network device. As shown in FIG5 , the method includes:

[0118] S501. A terminal device sends first information to a network device, where the first information includes information about first data.

[0119] Next, the wireless communication method shown in FIG. 3 , FIG. 4 or FIG. 5 is described.

[0120] When the data to be transmitted of the terminal device includes first data and second data, first information is generated, and the first information includes information about the first data in the data to be transmitted.

[0121] In the embodiment of the present application, the first data is data whose remaining time meets the delay requirement, and the description of the first data can be replaced by non-delay-sensitive data or non-delay-critical data.

[0122] The second data is data whose remaining time does not meet the delay requirement, and the description of the second data can be replaced by delay-sensitive data or delay-critical data.

[0123] In this embodiment of the present application, the latency requirement may be determined based on a threshold. If the remaining time of the data is greater than or equal to the threshold, the data is considered to meet the latency requirement and is classified as first data. If the remaining time of the data is less than the threshold, the data is considered to not meet the latency requirement and is classified as second data.

[0124] When the network device receives the first information from the terminal device, it can determine the first data to be transmitted based on the first information, thereby avoiding the situation where the terminal device prioritizes the transmission of the first data based on the order of arrival of the data or LCP, resulting in the transmission resources being unable to carry the second data, thereby causing the second data to not be transmitted to the network device side in a timely manner.

[0125] In an embodiment of the present application, the network device schedules resources based on the first information indicating information of non-delay-sensitive data, so that delay-sensitive data can be transmitted to the network device in a timely manner, thereby ensuring the transmission requirements of delay-sensitive data.

[0126] In some embodiments, the terminal device sends the first information, including:

[0127] When the DSR is triggered, the terminal device sends the first information.

[0128] The terminal device can be configured with a DSR mechanism by the network device. The terminal device triggers DSR when the DSR reporting conditions are met. The DSR information reported by the DSR can be transmitted together with the first information or separately.

[0129] In some embodiments, the first information includes information of a first logical channel LCH or a logical channel group LCG.

[0130] The first LCH or LCG can be understood as one LCH or LCG among the one or more LCHs or LCGs corresponding to the first data indicated by the first information.

[0131] It can be understood that the data of the first LCH or LCG includes the second data.

[0132] Optionally, the data of the first LCH or LCG includes the second data and the first data.

[0133] In some embodiments, the first information includes first indication information, and the first indication information is used to indicate the existence of first data.

[0134] The first indication information is used to indicate to the network device that the first data exists.

[0135] In some embodiments, the first indication information is based on LCH, LCG, or terminal device indication.

[0136] The first indication information is based on the LCH indication, which can be understood as the first indication information being per LCH, ie, indicating that each LCH in one or more LCHs has the first data.

[0137] The first indication information is based on the LCG indication, which can be understood as the first indication information being per LCG, ie, indicating that the first data exists in each LCG in one or more LCGs.

[0138] The first indication information is based on the terminal device indication, which can be understood as the first indication information being per terminal device, ie, indicating that the first data exists in the terminal device.

[0139] In an embodiment of the present application, the first indication information can indicate whether non-delay sensitive data exists in each LCH or LCG in one or more LCHs or LCGs, or indicate whether non-delay sensitive data exists in the terminal device in the form of bits.

[0140] In some embodiments, the first information includes second indication information, and the second indication information is used to indicate the data volume of the first data.

[0141] The second indication information is used to indicate the data volume of the first data to the network device.

[0142] In some embodiments, the second indication information is based on LCH, LCG or terminal device indication.

[0143] The second indication information is based on the LCH indication, which can be understood as the second indication information being per LCH, ie indicating the data amount of the first data of each LCH in one or more LCHs.

[0144] The second indication information is based on the LCG indication, which can be understood as the second indication information being per LCG, ie, indicating the data volume of the first data of each LCG in one or more LCGs.

[0145] The second indication information is based on the terminal device indication, which can be understood as the second indication information being per terminal device, that is, indicating the data volume of the first data of the terminal device.

[0146] In the embodiment of the present application, the transmission of the second indication information provides the network device with more accurate information about the first data compared to the transmission of the first indication information, which can help the network device perform more accurate scheduling.

[0147] In the embodiment of the present application, the first information may include first indication information and / or second information.

[0148] It is understandable that if the first information includes first indication information and second indication information, the indication unit based on the first indication information is the same as or different from the indication unit based on the second indication information, wherein the indication unit includes: LCH, LCG or terminal equipment.

[0149] In one example, the first indication information is based on the LCH indication, and the second indication information is based on the LCG indication.

[0150] In one example, the first indication information is based on the LCG indication, and the second indication information is based on the LCG indication.

[0151] In one example, the first indication information is based on the LCG indication, and the second indication information is based on the terminal device indication.

[0152] In some embodiments, the first information is carried in one or more of the following:

[0153] MAC PDU;

[0154] MAC sub-PDU header;

[0155] MAC sub-PDU payload (padding);

[0156] MAC CE;

[0157] MAC CE subheader.

[0158] In one example, the first information is based on an indication from the terminal device, and the first information is located in a header or a payload of a MAC sub-PDU.

[0159] In one example, the first information is indicated based on the LCH or LCG, and the first information is located in the MAC CE or a subheader of the MAC CE.

[0160] In some embodiments, the payload of the MAC CE or MAC sub-PDU includes one of the following:

[0161] an enhanced DSR MAC CE, where the enhanced DSR MAC CE is a DSR MAC CE including the first information;

[0162] BSR MAC CE;

[0163] Defined MAC CE.

[0164] The enhanced DSR MAC CE may be understood as a DSR MAC CE that carries the first information through reserved bits or newly added bits in the DSR MAC CE.

[0165] The BSR MAC CE can be understood as a MAC CE triggered based on the BSR, wherein, when the DSR reporting condition is met, the BSR reporting is also triggered, so that the first information is reported through the BSR MAC CE.

[0166] In the case where the BSR MAC CE carries the first information, the BSR is triggered simultaneously when the DSR is triggered, thereby reducing the design work of the new MAC CE.

[0167] The defined MAC CE can be understood as a new MAC CE specifically carrying the first information.

[0168] In some embodiments, factors determining whether to generate the enhanced DSR MAC CE or whether to generate the defined MAC CE include one or more of the following:

[0169] Factor 1: Whether it is necessary to generate an enhanced DSR MAC CE or a defined MAC CE;

[0170] Factor 2: whether the first data exists;

[0171] Factor 3: whether the first data arrives first;

[0172] Factor 4: whether the first data arrives before the second data, and the second data is data whose remaining time does not meet the delay requirement;

[0173] Factor 5: whether the second data is the first number of data in the LCH buffer;

[0174] Factor 6: whether the second data is not the second number of data before;

[0175] Factor 7: Whether the uplink grant can carry the enhanced DSR MAC CE or the defined MAC CE.

[0176] Factors 1 to 6 are used to indicate whether the first information needs to be reported. The following situations indicate that the first information needs to be reported:

[0177] An enhanced DSR MAC CE or a defined MAC CE needs to be generated;

[0178] The first data exists;

[0179] The first data is the data that arrives first;

[0180] The first data arrives before the second data;

[0181] The second data is not the first number of data in the LCH buffer;

[0182] The second data is not the first second number of data.

[0183] For factor 4, it can be determined whether the first data arrives at the terminal device, the PDCP layer of the terminal device, or the MAC layer of the terminal device before the second data.

[0184] The terminal device determines whether to generate a DSC MAC CE, an enhanced DSR MAC CE, or a defined MAC CE based on one or more factors from Factor 1 to Factor 7.

[0185] The terminal device determines whether it is necessary or possible to generate an enhanced DSC MAC CE or a defined MAC CE based on one or more factors from factor 1 to factor 7. If necessary and possible, the terminal device generates an enhanced DSC MAC CE or a defined MAC CE; if not necessary or not possible, the terminal device generates a DSR MAC CE.

[0186] In one example, if the uplink resources used for the new transmission can carry the enhanced DSC MAC CE or the defined MAC CE, the enhanced DSC MAC CE or the defined MAC CE is generated.

[0187] In one example, if the uplink resources used for new transmission cannot carry the enhanced DSC MAC CE or the defined MAC CE, a DSC MAC CE is generated.

[0188] In one example, if the enhanced DSR MAC CE is higher than the DSR MAC CE, an enhanced DSC MAC CE is generated.

[0189] In one example, non-delay-sensitive data is the data that arrives first, and the uplink grant can only carry one DSR MAC CE, or one enhanced DSR MAC CE or defined MAC CE, then an enhanced DSC MAC CE or a defined MAC CE is generated.

[0190] In the embodiment of the present application, if an enhanced DSR MAC CE or a defined MAC CE is generated, the first information is carried by the enhanced DSR MAC CE or the defined MAC CE; if a DSR MAC CE is generated, the first information is not transmitted.

[0191] In some embodiments, the priority of the defined MAC CE is lower than or equal to the priority of the DSR MAC CE; or,

[0192] The priority of the enhanced DSR MAC CE is higher than or equal to the priority of the DSR MAC CE.

[0193] In some embodiments, one uplink grant can carry the defined MAC CE and DSR MAC CE simultaneously.

[0194] It is understandable that the defined MAC CE and DSR MAC CE may be reported to the network device together, or may be reported to the network device in one uplink grant.

[0195] In some embodiments, the first condition for triggering the BSR corresponding to the BSR MAC CE includes one or more of the following:

[0196] Condition 1A: There is a data packet in the first LCH or LCG whose remaining time is less than or equal to the threshold;

[0197] Condition 1B: Data packets in the first LCH or LCG with a remaining time less than or equal to the threshold have not been transmitted or reported;

[0198] Condition 1C: The data packets whose minimum remaining time in the first LCH or LCG is less than or equal to the threshold have not been transmitted or reported;

[0199] Condition 1D: There is no pending DSR in the first LCG;

[0200] Condition 1E: When DSR is triggered, the BSR of the corresponding LCG is also triggered.

[0201] Condition 1F: The first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists.

[0202] One or more of conditions 1A to 1C indicates that there is delay-sensitive data that needs to be reported.

[0203] Condition 1D indicates that there is no DSR capable of reporting delay-sensitive data.

[0204] Condition 1E indicates that the triggering of DSR can trigger BSR. In this case, the BSR can be considered as the BSR associated with DSR, or the triggering condition of the BSR can be considered to be the same as that of DSR.

[0205] In condition 1F, there is a first mechanism: the triggering of the DSR report can trigger the BSR or the presence of the first information triggers the BSR. If the first mechanism is configured or enabled, the first mechanism can be executed.

[0206] In some embodiments, the second condition for canceling the BSR includes one or more of the following:

[0207] Condition 2A: The DSR is cancelled;

[0208] Condition 2B: The BSR is triggered based on the DSR and the DSR is canceled;

[0209] Condition 2C: The first mechanism is configured or enabled, wherein the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when the first information exists;

[0210] Condition 2D: The second mechanism is configured or enabled, which cancels the BSR when the DSR cancellation condition is met;

[0211] Condition 2E: The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR;

[0212] Condition 2F: The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR;

[0213] Condition 2G: The transmitted uplink grant carries the data volume of the BSR;

[0214] Condition 2H: All service data units SDU of the DSR are deleted.

[0215] For condition 2A, when DSR is canceled, all BSRs can be canceled.

[0216] For condition 2B, when the DSR is canceled, the BSR triggered based on the canceled DSR may be canceled.

[0217] For condition 2C, the triggering condition of the BSR can include the triggering of the DSR or the existence of the first information.

[0218] For condition 2D, the cancellation of DSR can trigger the cancellation of BSR.

[0219] For conditions 2E to 2F, it indicates that the transmission of the DSR data and the BSR data has been performed through the uplink bearer, and therefore, there is no need to report the first information.

[0220] For condition 2G, it indicates that the delay-sensitive data and the non-delay-sensitive data have been reported, and therefore there is no need to report the first information.

[0221] For condition 2H, the SDU representing the data to be transmitted has been deleted and the data does not need to be transmitted, so there is no need to report the first information.

[0222] In some embodiments, the BSR cannot trigger a scheduling request SR and / or cannot trigger a random access RA procedure; or,

[0223] In the absence of an available uplink grant, the BSR is not allowed to trigger an SR, and / or the BSR is not allowed to trigger an RA process.

[0224] The BSR cannot trigger a scheduling request SR and / or cannot trigger a random access RA process, so the BSR triggered based on the reporting of the first information is only used for the transmission of the first information, and is not used for triggering SR and RA.

[0225] In the absence of available uplink authorization, the BSR is not allowed to trigger the SR, and / or, the BSR is not allowed to trigger the RA process, then the uplink authorization for reporting the first information is only used for the transmission of the BSR MAC CE. In the absence of available uplink authorization, the SR and RA processes based on the BSR are not triggered, so as to avoid the BSR triggering the SR and RA processes from preempting the reporting resources of the first information.

[0226] In some embodiments,

[0227] If the SR triggered by the DSR is cancelled, the SR triggered by the BSR is cancelled; and / or,

[0228] If the first RA process triggered by the SR triggered by the DSR is stopped, the second RA process corresponding to the SR triggered by the BSR is stopped.

[0229] In the case that the triggered DSR triggers the SR and the SR is canceled, it can be considered that the SR process is not needed currently, and the SR triggered by the triggered BSR is canceled synchronously.

[0230] In the case where the DSR-SR triggers the first RA process and the first RA process is canceled, it can be considered that the RA process is not needed currently, and the RA process triggered by the BSR-SR is canceled synchronously.

[0231] In some embodiments, the third condition in which the SR triggered by the BSR is canceled or the second RA process corresponding to the SR triggered by the BSR is stopped includes one or more of the following:

[0232] Condition 3A: The BSR is triggered based on the DSR and the DSR is canceled, and the first RA process triggered by the DSR is canceled;

[0233] Condition 3B: The SR is triggered by a BSR, which is triggered based on the DSR, or is triggered when the first information exists;

[0234] Condition 3C: The RA process is triggered by an SR, and the SR is triggered by a BSR, and the BSR is triggered based on the DSR, or is triggered when the first information exists;

[0235] Condition 3D: the DSR is canceled, or the SR triggered by the DSR is canceled, or the RA process triggered by the SR triggered by the BSR is terminated;

[0236] Condition 3E: A third mechanism is configured or enabled, wherein the third mechanism cancels the second RA process if a cancellation condition of the first random access process is met;

[0237] Condition 3F: The first mechanism is configured or enabled, and the first mechanism triggers BSR when the DSR reporting condition is met;

[0238] Condition 3G: The second mechanism is configured or enabled, and the second mechanism cancels the BSR when the DSR cancellation condition is met;

[0239] Condition 3H: The fourth mechanism is configured or enabled, wherein if the SR triggered by the DSR is cancelled, the corresponding SR triggered by the BSR is invalidated;

[0240] Condition 3I: The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR;

[0241] Condition 3J: The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR;

[0242] Condition 3K: The transmitted uplink grant carries the data volume of the BSR;

[0243] Condition 3L: The transmitted uplink grant carries the DSR MAC CE;

[0244] Condition 3M: All service data units SDU of the DSR are deleted.

[0245] In conditions 3A to 3D, the triggering conditions of the SR or second RA process triggered by the BSR have been canceled, and the same process triggered by the DSR associated with the BSR has been canceled. At this time, there is no need to execute the SR or second RA process triggered by the BSR, and the SR or second RA process triggered by the BSR can be canceled.

[0246] Conditions 3E to 3H configure or enable the triggering relationship or cancellation relationship between the BSR and the associated DSR.

[0247] Conditions 3I to 3M represent the transmission or deletion of data. In this case, there is no need for BSR, and the SR and second RA process triggered by the BSR may not be executed.

[0248] FIG6 is a wireless communication method provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG6 , the method includes:

[0249] S601. The terminal device sends third data, where the third data includes first data and second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0250] FIG7 is a wireless communication method provided in an embodiment of the present application, which is applied to a network device. As shown in FIG7 , the method includes:

[0251] S / 701. The network device receives third data, which includes first data and second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0252] FIG8 is a wireless communication method provided in an embodiment of the present application, which is applied to a wireless communication system including a terminal device and a network device. As shown in FIG8 , the method includes:

[0253] S801. The terminal device sends third data to the network device. The third data includes first data and second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0254] Next, the wireless communication method shown in FIG. 6 , FIG. 7 or FIG. 8 will be described.

[0255] When the data to be transmitted of the terminal device includes non-delay sensitive data and delay sensitive data, the non-delay data and delay sensitive data in the data to be transmitted are sent together to the network device, so that the network device can receive the delay sensitive data in time.

[0256] In an embodiment of the present application, delay-sensitive data and non-delay-sensitive data are transmitted to the network device together, avoiding the situation where the terminal device prioritizes the transmission of non-delay-sensitive data based on the order of data arrival or LCP, resulting in the delay-sensitive data not being able to be transmitted to the network device in a timely manner, thereby ensuring the transmission requirements of delay-sensitive data.

[0257] In some embodiments, the third data is data corresponding to the first LCH or LCG; or,

[0258] The third data is data corresponding to the first LCH or LCG and the second LCH or LCG;

[0259] The data in the first LCH or LCG includes the second data; the data in the second LCH or LCG includes the first data.

[0260] The third data is data corresponding to the first LCH or LCG, which can be understood as the third data being data of one LCH or LCG.

[0261] The third data is data corresponding to the first LCH or LCG and the second LCH or LCG. It can be understood that the third data is data of multiple LCHs or LCGs.

[0262] It can be understood that when the third data corresponds to the data of the first LCH or LCG and the second LCH or LCG, the third data corresponds to multiple LCHs or LCGs, the first LCH or LCG and the second LCH or LCG are two different LCHs or LCGs among the corresponding multiple LCHs or LCGs, and the data of the first LCH or LCG includes delay-sensitive data, and the data of the second LCH or LCG includes non-delay-sensitive data.

[0263] When the third data corresponds to an LCH or LCG, the terminal device packages and transmits the data of the LCH or LCG.

[0264] When the third data corresponds to multiple LCHs or LCGs, the terminal device packages and transmits the data of different LCHs or LCGs, and the package packaging or transmission order between different LCHs or LCGs needs to consider the priority between the LCHs or LCGs.

[0265] In some embodiments, the second data is packaged or transmitted before the first data.

[0266] In an embodiment of the present application, the delay-sensitive data is packaged or transmitted before the non-delay-sensitive data, so that the terminal device preferentially sends the delay-sensitive data to the network device, ensuring timely transmission of the delay-sensitive data.

[0267] Optionally, the network device may enable the delay-sensitive data to be packaged or transmitted before the delay-insensitive data when the network device side performs data transmission.

[0268] In some embodiments, the transmission of the second data prior to the packetization or transmission of the first data comprises one or more of the following:

[0269] Case 1: the PDCP, RLC, or MAC preferentially transmits the second data;

[0270] Case 2: The PDCP, RLC, or MAC preferentially delivers the second data to a lower layer;

[0271] Case 3: The PDCP, RLC, or MAC preferentially packages the SDU of the second data into a PDU;

[0272] Case 4: The MAC preferentially multiplexes the second data during the LCP process;

[0273] Case 5: The second data is preferentially multiplexed or carried by adjusting the parameters of the logical channel priority LCP;

[0274] Case 6: using the first LCP process to preferentially multiplex or carry the second data;

[0275] Case 7: Prioritizing multiplexing or carrying the second data on the uplink grant;

[0276] Case 8: Modify the LCP mapping restriction so that the first uplink authorization can multiplex or carry the second data, or so that the first uplink authorization can multiplex or carry the second data if there are remaining uplink resources according to the LCP process.

[0277] In the embodiment of the present application, the second data can be controlled to be transmitted before the first data through the order of data packaging, submission, multiplexing, and transmission, and the second data can also be controlled to be transmitted before the first data through the LCP process.

[0278] In some embodiments, the first uplink grant is an uplink grant configured to be unable to carry first LCH or LCG data, and second data exists in the first LCH or LCG.

[0279] For the first uplink authorization that cannot carry the data of the first LCH or LCG, that is, the second data, the LCP mapping restriction is modified so that the first uplink authorization can carry the data of the first LCH or LCG, that is, the second data, thereby ensuring the transmission of the second data.

[0280] In some embodiments, the adjusting the parameters of the LCP includes one or more of the following:

[0281] Adjust the token bucket size of the first LCH or LCG;

[0282] Adjusting the priority bit rate of the first LCH or LCG;

[0283] Adjust the logical channel priority of the first LCH or LCG.

[0284] Here, the LCP process is adjusted by adjusting LCP parameters to ensure priority multiplexing or carrying of data of the first LCH or LCG. The adjusted LCP parameters may include one or more of the following parameters of the first LCH or LCG: token bucket size, priority bit rate (PBR), and logical channel priority.

[0285] In some embodiments, using the first LCP process includes one or more of the following:

[0286] Usage mode 1: prioritize multiplexing the data of the first LCH or LCG;

[0287] Usage mode 2: prioritize multiplexing the second data in the first LCH or LCG;

[0288] Usage mode 3: when allocating resources to the first LCH or LCG based on the LCP process, allocating resources according to the data volume of the second data of the first LCH or LCG;

[0289] Usage mode 4: when allocating resources to an LCH or LCG based on the LCP process, first allocate resources to the first LCH or LCG or first allocate resources to the second data of the first LCH or LCG;

[0290] Usage mode 5: When allocating resources to LCH or LCG based on the LCP process, if there are remaining uplink transmission resources, perform at least one of the following: not carrying padding bits, transmitting data of the first LCH or LCG, or allocating resources to the first LCH or LCG.

[0291] In usage mode 3, resources are allocated according to the data amount of the second data of the first LCH or LCG, ensuring that the allocated resources can transmit the second data of the first LCH or LCG.

[0292] In usage mode 4, resources are allocated preferentially to the first LCH or LCG or the second data of the first LCH or LCG.

[0293] In usage mode 5, the remaining uplink transmission resources are uplink grants configured to be unable to carry the first LCH or LCG data. At this time, the uplink resources can be used to carry the first LCH or LCG data by not carrying padding bits, transmitting one or both of the first LCH or LCG data, or resources can be allocated to the first LCH or LCG so that the first LCH or LCG data can be transmitted.

[0294] In some embodiments, the fourth condition that the second data is packaged or transmitted before the first data includes:

[0295] Condition 4A: The second data reaches the PDCP layer, the RLC layer, or the MAC layer after the first data;

[0296] Condition 4B: the second data is not the first amount of data to be transmitted;

[0297] Condition 4C: the total amount of the second data and the first data is greater than the total amount of the first LCH that can be carried by the uplink grant;

[0298] Condition 4D: The total amount of the second data and the non-sensitive data preceding the second data is greater than the total amount of data of the first LCH that can be carried by the uplink grant;

[0299] Condition 4E: The total amount of the second data and the first data is greater than the token bucket size corresponding to the first LCH that can be carried by the uplink grant;

[0300] Condition 4F: The total amount of the second data and the non-sensitive data before the second data is greater than the token bucket size corresponding to the first LCH that can be carried by the uplink authorization.

[0301] In an embodiment of the present application, in the first LCH or LCG, when the second data meets one or more conditions 4A to 4E, the transmission of the first data will precede the second data. In this case, the terminal device controls the packaging, delivery, serving or transmission process of the second data so that the second data is transmitted before the first data, thereby ensuring the timely transmission of the second data.

[0302] In some embodiments, the method on the terminal device side further includes one or more of the following:

[0303] Adjustment 1. The terminal device adjusts the multiplexing or packetization order of the data of the first LCH or LCG and the second LCH or LCG;

[0304] Adjustment 2: The terminal device adjusts transmission of data of the first LCH or LCG and the second LCH or LCG;

[0305] The data of the first LCH or LCG is multiplexed, packaged, or transmitted before the data of the second LCH or LCG.

[0306] The terminal device adjusts the multiplexing or packetizing order or transmission of the first LCH or LCG and the second LCH or LCG so that the data of the first LCH or LCG is multiplexed, packetized, or transmitted before the data of the second LCH or LCG, thereby allowing the data of the first LCH or LCG with delay-sensitive data to be transmitted to the network device before the second LCH or LCG.

[0307] Here, in the case where the third data corresponds to multiple LCHs or LCGs, the terminal device may adjust one or more of 1 and 2 to control the transmission of delay-sensitive data.

[0308] In some embodiments,

[0309] Among the priorities of LCHs or LCGs, the priority of the first LCH or LCG is higher than the priority of the second LCH or LCG; and / or,

[0310] In the multiplexing or packetizing order of MAC SDU, the multiplexing or packetizing of the MAC SDU of the first LCH or LCG precedes the multiplexing or packetizing of the MAC SDU of the second LCH or LCG.

[0311] In an embodiment of the present application, the priority of the LCH or LCG is adjusted so that the priority of the first LCH or LCG is higher than the priority of the second LCH or LCG. The adjustment is an adjustment of the configuration parameters of the LCH or LCG.

[0312] In an embodiment of the present application, the multiplexing or packetizing order of MAC SDU is adjusted so that the multiplexing or packetizing of the MAC SDU of the first LCH or LCG precedes the multiplexing or packetizing of the MAC SDU of the second LCH or LCG. This adjustment is to adjust the multiplexing or packetizing order of MAC SDU, breaking the principle of first-arrival, first-packaging, and then multiplexing of MAC SDU.

[0313] In some embodiments, the priority of the first LCH or LCG is higher than the priority of the second LCH or LCG, including:

[0314] Priority adjustment mode 1: The priority of the first LCH or LCG is adjusted to the highest priority;

[0315] Priority adjustment mode 2: the priority of the first LCH or LCG is adjusted to the highest sub-priority among LCHs or LCGs of the same priority;

[0316] Priority adjustment mode 3: The priority of the first LCH or LCG is adjusted to a higher priority among LCHs or LCGs of the same priority;

[0317] Priority adjustment mode 4: The priorities of all first LCHs or LCGs are adjusted to be higher than the priorities of other LCHs or LCGs of the same priority, and all first LCHs or LCGs are sorted according to their delays;

[0318] Priority adjustment method 5: The priorities of all first LCHs or LCGs are adjusted to be the same and higher than the priorities of other LCHs or LCGs, and all first LCHs or LCGs are sorted according to their delays.

[0319] In an embodiment of the present application, one or more priority adjustment methods 1 to 5 are used to ensure that the priority of the first LCH or LCG is higher than the priority of the second LCH or LCG.

[0320] In the embodiment of the present application, the priority adjustment methods 1 to 5 that do not conflict with each other can be used in combination or individually.

[0321] In some embodiments, the fifth condition for adjusting the multiplexing or packetization order of data of the first LCH or LCG and the second LCH or LCG, or adjusting the transmission of data of the first LCG and the second LCG includes one or more of the following:

[0322] Condition 5A: The priority of the first LCH or LCG is lower than the priorities of other LCHs or LCGs;

[0323] Condition 5B: The priority of the first LCH or LCG is lower than the priority of the second LCH or LCG;

[0324] Condition 5C: The total amount of data on the first LCH or LCG and the second LCH or LCG is greater than the total amount of data that can be carried by the uplink grant;

[0325] Condition 5D: The second data or the data of the first LCH or LCG cannot all be multiplexed on the uplink grant;

[0326] Condition 5E: The token bucket size or priority bit rate of the first LCH or LCG is smaller than the size of the second data of the first LCH or LCG.

[0327] If one or more of conditions 5A to 5E are met, the data of the first LCH or LCG may not be transmitted in time. At this time, the transmission of the data of the first LCH or LCG is guaranteed by adjusting the multiplexing or packetization order of the data of the first LCH or LCG and the second LCH or LCG, or adjusting the transmission of the data of the first LCG and the second LCG.

[0328] For conditions 5A to 5B, the transmission of the first LCH or LCG will be later than that of other LCHs or LCGs or the second LCH or LCG, so there is a possibility that the data of the first LCH or LCG will not be transmitted or will be transmitted late.

[0329] For conditions 5C to 5D, the uplink authorization cannot carry the data of the first LCH or LCG and the second LCH or LCG at the same time, and the data of the first LCH or LCG may not be transmitted or may be transmitted late.

[0330] For condition 5E, the uplink grant cannot carry the data of the first LCH or LCG, so the data of the first LCH or LCG may not be transmitted or may be transmitted late.

[0331] In some embodiments, the second data includes one or more of the following:

[0332] Data whose delay is less than or equal to the first threshold;

[0333] Data indicating that the remaining duration of the first timer is less than or equal to the second threshold;

[0334] Data in which the packet delay budget PDB or the delay budget PSDB of a data packet set is less than or equal to the third threshold;

[0335] Data corresponding to a QoS flow whose delay requirement is less than or equal to a fourth threshold based on the Quality of Service (QoS) requirement.

[0336] In some embodiments, the second data includes one or more of the following:

[0337] Service Data Adaptation Protocol (SDAP) SDU or SDAP PDU;

[0338] PDCP SDU or PDCP PDU;

[0339] RLC SDU or RLC PDU;

[0340] MAC SDU;

[0341] PDU collection or data burst.

[0342] In some embodiments, for the wireless communication method shown in FIG6 , the method further includes:

[0343] The terminal device sends second information, where the second information is used to indicate the delay and / or data volume of the sent data.

[0344] In some embodiments, for the wireless communication method shown in FIG7 , the method further includes:

[0345] The network device receives second information, where the second information is used to indicate a delay and / or a data volume of sent data.

[0346] The terminal device reports the second information to the network device, so that the network device schedules or configures uplink authorization to the terminal device based on the second information, and the terminal device sends delay-sensitive data and non-delay-sensitive data based on the uplink authorization.

[0347] FIG9 is a wireless communication method provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG9 , the method includes:

[0348] S901. The terminal device sends third information, which includes information about the data volume of first data and information about the data volume of second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0349] FIG10 is a wireless communication method provided in an embodiment of the present application, which is applied to a network device. As shown in FIG10 , the method includes:

[0350] S1001. The network device receives third information, where the third information includes information about the data volume of first data and information about the data volume of second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0351] FIG11 is a wireless communication method provided in an embodiment of the present application, which is applied to a wireless communication system including a terminal device and a network device. As shown in FIG11 , the method includes:

[0352] S1101. The terminal device sends third information to the network device, where the third information includes information about the data volume of the first data and information about the data volume of the second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0353] When the data to be transmitted by the terminal device includes non-delay sensitive data and delay sensitive data, third information is generated, and the third information includes information on the data volume of the delay sensitive data and information on the data volume of the non-delay sensitive data.

[0354] When the network device receives the third information sent by the terminal device, it can determine the data volume of non-delay-sensitive data and the data volume of delay-sensitive data to be transmitted based on the third information, thereby avoiding the terminal device prioritizing the transmission of non-delay-sensitive data based on the order of data arrival or LCP, resulting in the transmission resources being unable to carry delay-sensitive data, thereby causing the delay-sensitive data to not be transmitted to the network device side in a timely manner.

[0355] Optionally, the third information is used by the network device to schedule uplink resources, where the uplink resources are used to transmit delay-sensitive data and non-delay-sensitive data, so that delay-sensitive data can be transmitted in a timely manner, thereby ensuring the transmission requirements of delay-sensitive data.

[0356] In an embodiment of the present application, the network device schedules resources based on third information indicating the data volume of non-delay-sensitive data and the data volume of delay-sensitive data, so that the delay-sensitive data can be transmitted to the network device in a timely manner, thereby ensuring the transmission requirements of the delay-sensitive data.

[0357] In some embodiments, the third information is statistics collected by the PDCP layer and / or the RLC layer, and / or is informed by the PDCP layer and / or the RLC layer to the MAC layer.

[0358] In the embodiment of the present application, the amount of data counted and / or delivered to the MAC layer by the PDCP layer and / or the RLC layer is the amount of delay-sensitive data and the amount of non-delay-sensitive data. Compared with the related art, only the amount of delay-sensitive data is counted, which can avoid the inconsistency between the data to be sent (delay-sensitive data and non-delay-sensitive data) and the actual counted data amount, and avoid the situation where part of the data to be sent is not sent.

[0359] Optionally, the network device may enable the PDCP layer and / or RLC layer of the terminal device to count the third information and / or the PDCP layer and / or RLC layer to inform the MAC layer of the statistical third information.

[0360] In some embodiments, the sixth condition that the third information includes information about the amount of the second data and information about the amount of the first data includes one or more of the following:

[0361] Condition 6A: the data of the one or more LCHs or LCGs to be transmitted includes the second data and the first data;

[0362] Condition 6B: In a third LCH or LCG of the plurality of LCHs or LCGs, an SDU of the second data arrives after an SDU of the first data, and data of the third LCH or LCG includes the second data and the first data;

[0363] Condition 6C: A priority of a first LCH or LCG among the plurality of LCHs or LCGs is lower than a priority of other LCHs or LCGs among the plurality of LCHs or LCGs, and the first LCH is an LCH having second data;

[0364] Condition 6D: The priority of the first LCH is lower than the priority of a second LCH or LCG among the multiple LCHs or LCGs, and the second LCH or LCG is an LCH or LCG having the first data;

[0365] Condition 6E: The token bucket size or the priority bit rate of the first LCH or LCG is smaller than the size of the second data in the first LCH or LCG;

[0366] Condition 6F: The token bucket size or the priority bit rate of the first LCH is smaller than the amount of data to be transmitted in the first LCH;

[0367] Condition 6G: the second data of the first LCH or LCG is not the first fourth number of data in the first LCH or LCG;

[0368] Condition 6H: The SDU of the second data of the first LCH or LCG is not the first fifth number of SDUs in the first LCH or LCG.

[0369] If one or more of conditions 6A to 6H are met, there is a possibility that the second data cannot be transmitted in a timely manner. Condition 6A indicates that the data to be transmitted includes the second data and the first data; Conditions 6B to 6D indicate that if there are multiple LCHs or LCGs and the LCH or LCG containing the second data has a low priority, there is a possibility that the second data cannot be transmitted or is transmitted late; Conditions 6E to 6F indicate that there is a possibility that the second data in the LCH or LCG containing the second data cannot be transmitted in a timely manner.

[0370] In some embodiments,

[0371] The first data is all first data to be transmitted in the corresponding LCH or LCG, or,

[0372] The first data is all first data to be transmitted in the corresponding LCH or LCG and arrives before the second data.

[0373] If the first data corresponds to all first data to be transmitted in the LCH or LCG, the network device can allocate resources for all first data and second data based on the third indication information to achieve transmission of all first data and second data and ensure timely transmission of the second data.

[0374] If the first data corresponds to all the first data to be transmitted in the corresponding LCH or LCG and arrives before the second data, the network device can allocate resources for the second data and the first data before the second data based on the third indication information, realize the transmission of the second data and the first data before the second data, and ensure the timely transmission of the second data.

[0375] In some embodiments, the third information is included in a DSR MAC CE or an enhanced DSR MAC CE or a defined MAC CE.

[0376] Here, for the description of DSR MAC CE or enhanced DSR MAC CE or defined MAC CE, please refer to the description of DSR MAC CE or enhanced DSR MAC CE or defined MAC CE in the wireless communication method shown in Figures 3 to 5, which will not be repeated here.

[0377] Among them, the way in which DSR MAC CE or enhanced DSR MAC CE or defined MAC CE carries the third information can refer to the way in which DSR MAC CE or enhanced DSR MAC CE or defined MAC CE carries the first information.

[0378] In an embodiment of the present application, the meaning of the information on the amount of data carried by the DSR MAC CE or enhanced DSR MAC CE or defined MAC CE has changed relative to the meaning or definition of the DSR MAC CE in the related art, and is the data amount of the first data and the information on the data amount of the first data.

[0379] In some embodiments, the third information includes one or more of the following:

[0380] Information on the amount of data for an LCH or LCG or UE;

[0381] Information on the data volume corresponding to all SDUs or PDUs to be transmitted;

[0382] Data volume information of the second data and data volume information of the first data that arrived before the second data arrived;

[0383] data volume information of the second data and data volume information of the first data;

[0384] The data amount information of the second data and the data amount information of the other data.

[0385] In some embodiments, the third information carries data amount information corresponding to the fourth LCH or LCG, and the data amount information includes one or more of the following:

[0386] Information on the data volume corresponding to all SDUs or PDUs to be transmitted in the fourth LCH or LCG;

[0387] Data amount information of the second data in the fourth LCH or LCG and data amount information of the first data arriving before the second data arrives;

[0388] Data amount information of the second data and data amount information of the first data in the fourth LCH or LCG;

[0389] The data amount information of the second data and the data amount information of other data in the fourth LCH or LCG.

[0390] It can be understood that in the embodiments of the present application, the wireless communication methods shown in Figures 3 to 5, the wireless communication methods described in Figures 6 to 8, and the wireless communication methods shown in Figures 9 to 11 are methods for ensuring that delay-sensitive data can be transmitted in a timely manner. In the wireless communication methods shown in Figures 3 to 5, the terminal device reports information about non-delay-sensitive data to the network device, so that the network device schedules resources for the terminal device based on the received information about non-delay-sensitive data. In the wireless communication methods shown in Figures 6 to 8, the terminal device reports non-delay-sensitive data and delay-sensitive data to the network device, so that the network device can receive non-delay-sensitive data and delay-sensitive data. In the wireless communication methods shown in Figures 9 to 10, the terminal device reports information about the amount of non-delay-sensitive data and information about the amount of delay-sensitive data to the network device, so that the network device can perform accurate resource scheduling based on the received information about the amount of non-delay-sensitive data and information about the amount of delay-sensitive data.

[0391] It can be understood that the wireless communication methods shown in Figures 3 to 5, the wireless communication methods described in Figures 6 to 8, and the wireless communication methods shown in Figures 9 to 11 can be implemented independently, and when the schemes do not conflict, one or more of the wireless communication methods shown in Figures 3 to 5, the wireless communication methods described in Figures 6 to 8, and the wireless communication methods shown in Figures 9 to 11 can be implemented in combination.

[0392] In one example, the terminal device reports first information to the network device.

[0393] In one example, the terminal device reports the first information and the third information to the network device, so that the network device schedules resources based on the received first information and the third information.

[0394] In one example, the terminal device reports third information to the network device, and reports first data based on the uplink resources configured by the network device based on the third information.

[0395] In one example, the terminal device reports first information to the network device, and reports first data based on the uplink resources configured by the network device based on the first information.

[0396] The following further describes the wireless communication method provided in the embodiments of the present application.

[0397] The wireless communication method provided by the embodiments of the present application includes but is not limited to one or more of the following embodiments 1 to 4.

[0398] Example 1

[0399] A new reporting method or a new reporting trigger condition. The reporting is used to report the presence of non-delay-sensitive data, i.e., delay-sensitive data, or to report information about non-delay-sensitive data. Optionally, the reporting uses an existing MAC CE or introduces a new MAC CE. Optionally, the existing MAC CE may be a BSR MAC CE or a DSR MAC CE. If non-delay-sensitive data is added to a DSR MAC CE, or if information about non-delay-sensitive data is reported, the DSR MAC CE may be referred to as an enhanced MAC CE.

[0400] Implementation Plan 1

[0401] Enhanced DSR, indicating data presence information.

[0402] In the case of triggering DSR, first information is carried in the enhanced DSR MAC CE, where the first information is used to indicate to the base station the existence of non-delay critical data, that is, non-delay critical data.

[0403] Optionally, the first information may be indicated per LCG or per UE.

[0404] If the indication is per LCG, a bitmap can be used to indicate whether the LCG corresponding to the bitmap position has non-delay critical data. The bitmap is located in the MAC CE.

[0405] If it is indicated per UE, a reserved bit in the payload can be used, or a new bit can be added to indicate whether the UE has non-delay critical data.

[0406] Optionally, the first information is written in the MAC CE, and may also be carried in the header of the MAC subPDU.

[0407] If it is carried in the packet header, a reserved bit in the packet header can be used to indicate whether there is non-delay critical data. Furthermore, the indication is per UE.

[0408] If carried in a packet header, or carried in a MAC CE, a new logical channel identify (LCID) may be introduced to identify the MAC CE as a new MAC CE, ie, a MAC CE carrying information of the non-delay critical data.

[0409] Optionally, when a DSR is triggered, whether to indicate the generation of a DSR MAC CE or an enhanced DSR MAC CE depends on at least one of the following factors:

[0410] Factor 1: Whether to generate an enhanced DSR MAC CE;

[0411] Factor 2: Is there any non-delay critical data?

[0412] Factor 3: Whether non-delay critical data arrives before delay-critical data;

[0413] Factor 4: Is the delay-critical data not the first N data?

[0414] Factor 5: Whether the uplink grant can carry the enhanced DSR MAC CE.

[0415] Example 1: Uplink shared channel resources are available for new transmission and the uplink shared channel can carry enhanced DSR MAC CE (UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the enhanced DSR MAC CE plus its subheader), then an enhanced DSR MAC CE is generated.

[0416] Example 2: Uplink shared channel resources can be used for new transmission and the uplink shared channel can carry DSR MAC CE, but cannot carry enhanced DSR MAC CE and its subheader, then a DSR MAC CE is generated.

[0417] Example 3: Enhanced DSR MAC CE takes precedence over DSR MAC CE

[0418] Example 4: An uplink grant can only carry one DSR MAC CE or one enhanced DSR MAC CE.

[0419] Example 5: If non-delay critical data exists, or non-delay critical data arrives before delay-critical data, or delay-critical data is not the first N data (eg, N=1), an enhanced DSR MAC CE is generated.

[0420] Example 6: There is non-delay critical data, or the non-delay critical data arrives before the delay-critical data, or the delay-critical data is not the first N data (such as N=1), and the UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the enhanced DSR MAC CE plus its subheader, then an enhanced DSR MAC CE is generated.

[0421] In an embodiment of the present application, the structure of the enhanced DSR MAC CE may be shown in Figure 12 or Figure 13. In Figure 12, the R bit of the DSR MAC CE is used to indicate the presence of non-critical data, represented by U. The R bit used can be one or more. Optionally, in the case of multiple R bits, each LCG can indicate a U. In Figure 13, a row of information for different LCGs is added to the DSR MAC CE. For example, each LCG in oct2 indicates whether the corresponding LCG has non-critical data.

[0422] An extension of Solution 1 is to introduce a new MAC CE whose triggering conditions are the same as the DSR triggering conditions. The new MAC CE includes per-UE or per-LCG reporting of first information. The priority of the new MAC CE can be the same as or lower than the priority of the DSR MAC CE. The new MAC CE is reported to the base station together with the DSR MAC CE, or can be reported to the base station in an uplink grant.

[0423] The new MAC CE is used to indicate the presence of non-critical data, which can be indicated per UE or per LCG as shown in Figure 14 or Figure 15.

[0424] Implementation Plan 2

[0425] Enhanced DSR indicates data volume information. Compared with implementation method 1, implementation method 2 provides more accurate information, which can help the base station perform more precise scheduling.

[0426] In the case of triggering DSR, first information is carried in the enhanced DSR MAC CE, where the first information is used to indicate the data volume of non-delay critical data to the base station.

[0427] Optionally, the first information may be indicated per LCG or per UE.

[0428] If it is indicated per LCG, a bitmap can be used to indicate whether the LCG corresponding to the bitmap position has non-delay critical data. The bitmap is located in the MAC CE. Optionally, data volume information is indicated for the LCG with non-delay critical data. Alternatively, if it is indicated per LCG, regardless of whether the LCG has non-delay critical data, all relevant LCGs indicate the data volume information (the LCG without non-delay critical data volume can be indicated as NULL, 0, or a specific value).

[0429] If per-UE indication is used, a reserved bit in the payload can be used, or a new bit can be added, to indicate whether the UE has non-delay critical data. And / or, the amount of non-delay critical data per UE as a whole, or across all LCGs reported, can be indicated.

[0430] Optionally, the first information is written in the MAC CE, and may also be carried in the header of the MAC subPDU.

[0431] Optionally, the information is carried in the packet header and the MAC CE. Specifically, a reserved bit in the packet header can be used to indicate whether non-delay critical data exists. Furthermore, the first information indication is per UE. Furthermore, the amount of non-delay critical data is indicated in the MAC CE.

[0432] Optionally, it is carried in the MAC CE. Specifically, a reserved bit indication or a specific bit can be used to indicate whether non-delay critical data exists, and / or the amount of non-delay critical data can be indicated in a specific bit or position.

[0433] If carried in the packet header and / or carried in the MAC CE, a new LCID may be introduced to identify the MAC CE as an enhanced DSR MAC CE, that is, a MAC CE carrying information of the non-delay critical data.

[0434] Optionally, when a DSR is triggered, whether to indicate the generation of a DSR MAC CE or an enhanced DSR MAC CE depends on at least one of the following factors:

[0435] Factor 1: Whether to generate an enhanced DSR MAC CE;

[0436] Factor 2: Is there any non-delay critical data?

[0437] Factor 3: Whether non-delay critical data arrives before delay-critical data;

[0438] Factor 4: Is the delay-critical data not the first N data?

[0439] Factor 5: Whether the uplink grant can carry the enhanced DSR MAC CE.

[0440] Example 1: Uplink shared channel resources are available for new transmission and the uplink shared channel can carry enhanced DSR MAC CE (UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the enhanced DSR MAC CE plus its subheader), then an enhanced DSR MAC CE is generated.

[0441] Example 2: Uplink shared channel resources can be used for new transmission and the uplink shared channel can carry DSR MAC CE, but cannot carry enhanced DSR MAC CE and its subheader, then a DSR MAC CE is generated.

[0442] Example 3: Enhanced DSR MAC CE takes precedence over DSR MAC CE

[0443] Example 4: An uplink grant can only carry one DSR MAC CE or one enhanced DSR MAC CE.

[0444] Example 5: If non-delay critical data exists, or non-delay critical data arrives before delay-critical data, or delay-critical data is not the first N data (eg, N=1), an enhanced DSR MAC CE is generated.

[0445] Example 6: There is non-delay critical data, or the non-delay critical data arrives before the delay-critical data, or the delay-critical data is not the first N data (such as N=1), and the UL-SCH resources can be used for new transmission and can carry the enhanced DSR MAC CE plus its subheader, then an enhanced DSR MAC CE is generated.

[0446] In the embodiment of the present application, the structure of the enhanced DSR MAC CE may be as shown in Figures 16 to 22.

[0447] In Figure 16, the R bit of the DSR MAC CE is used to indicate the presence of non-critical data, represented by U. Each LCG's corresponding U indicates whether the LCG has non-critical data to transmit. The buffer size in the second row of each LCG indicates the amount of non-critical data.

[0448] In Figure 17, the buffer size in the second row of each LCG of the DSR MAC CE represents the amount of non-critical data.

[0449] In Figure 18, the R bit of the DSR MAC CE is used to indicate the presence of non-critical data, represented by U. Each LCG's corresponding U indicates whether the LCG has non-critical data to transmit. The buffer size of each LCG represents the amount of critical and non-critical data.

[0450] In Figure 19, a line is added to the DSR MAC CE, such as oct2, to indicate whether non-critical data exists. The buffer size of each LCG represents the amount of delay-critical data, or the buffer size of each LCG represents the amount of both non-delay critical and delay-critical data.

[0451] In Figure 20, a line is added to the DSR MAC CE, such as oct2, to indicate whether non-critical data exists. The first line of each LCG, buffer size, represents the amount of delay-critical data, and the second line of each LCG, buffer size, represents the amount of non-delay-critical data.

[0452] In Figure 21, a last row is added to the DSR MAC CE. The buffer size in the last row represents the total amount of non-critical data. The total amount of data is the total amount of data of the UE or the reported LCGs. If there is no non-critical data, it can be reported as 0 or indicated by the R bit position in one or more of the MAC CEs (for example, if the R bit position is used, the last row may not appear when the data amount is 0).

[0453] In FIG22 , the buffer size of each LCG of the DSR MAC CE represents the amount of critical and non-critical data.

[0454] How to implement the extension of solution 2

[0455] A new MAC CE is introduced, whose triggering conditions are the same as the DSR triggering conditions. The first information is reported per UE or per LCG in the new MAC CE. The priority of the new MAC CE can be the same as or lower than the priority of the DSR MAC CE. The new MAC CE is reported to the base station together with the DSR MAC CE, or can be reported to the base station in an uplink grant.

[0456] The new MAC CE is used to indicate the amount of non-critical data. As shown in Figure 23, each row of BS represents the amount of non-delay critical data of each corresponding LCG. The LCG bitmap represents whether the LCG has non-delay critical data. When the LCG position indicates no, the corresponding BS row may optionally not appear. As shown in Figure 24, each row of BS represents the total amount of non-delay critical data of each corresponding LCG. The total data amount can be that of the UE or the total data amount of these LCGs reported. The LCG bitmap represents whether the LCG has non-delay critical data.

[0457] Implementation Plan 3

[0458] Enhanced BSR: When the DSR reporting conditions are met, BSR reporting is also triggered. Compared with implementation methods 1 or 2, implementation method 3 uses simultaneous BSR triggering, which reduces the work of new MAC CE design, but requires consideration of how to cancel this BSR.

[0459] When DSR is triggered, DSR reporting is triggered and BSR reporting is triggered at the same time. Alternatively, when DSR reporting is met, BSR reporting is triggered.

[0460] The DSR triggering condition includes at least one of the following: whether a data packet with a minimum remaining time has not been reported or transmitted, the LCG has no pending DSR, and a mechanism for reporting a BSR that meets the DSR reporting condition is configured or enabled.

[0461] For example: if the smallest remaining value of the PDCP discardTimers among all the data buffered for the LCG that has not been transmitted in any MAC PDU or reported as data volume in a DSR MAC CE becomes below remainingTimeThreshold of the LCG; and

[0462] If there is no DSR pending for the LCG since the last transmission of a DSR MAC CE,

[0463] Optionally, if the DSR is cancelled according to the DSR cancellation condition, the BSR may be cancelled.

[0464] Optionally, the BSR is canceled if at least one of the following conditions is met:

[0465] BSR is triggered by DSR, and the corresponding DSR is canceled. l The mechanism of reporting BSR when DSR reporting conditions are met is configured or enabled; the mechanism of canceling BSR when DSR cancellation conditions are met is configured or enabled; UL grant can carry DSR MAC CE and corresponding BSR MAC CE; UL grant can carry DSR and the data volume corresponding to DSR; UL grant can carry the data volume corresponding to the triggered BSR; UL grant can carry the corresponding DSR MAC CE; all SDUs corresponding to the suspended DSR are deleted.

[0466] It can be described as:

[0467] The MAC entity shall cancel a pending BSR if the associated pending DSR is cancelled;

[0468] The MAC entity shall cancel a pending BSR, either when all the SDUs associated with the DSR have been discarded, or when a MAC PDU is transmitted and this MAC PDU includes either all the SDUs associated with the DSR.

[0469] The MAC entity shall cancel a pending BSR when a MAC PDU is transmitted and this MAC PDU includes a BSR MAC CE and / or a DSR MAC CE that contains the delay information of all the SDUs associated with the DSR.

[0470] Optionally, if a BSR is triggered as described above, the pending BSR cannot trigger a corresponding RACH process, or cannot trigger an SR.

[0471] Optionally, if the corresponding RACH process is canceled according to the condition that the RACH triggered by the DSR-SR is canceled, the corresponding RACH process triggered by the BSR-SR may be canceled.

[0472] Optionally, the RACH triggered by the BSR-SR is canceled when at least one of the following conditions is met:

[0473] BSR is triggered by DSR, the corresponding DSR is canceled, and the corresponding RACH triggered by DSR-SR is canceled;

[0474] The mechanism of canceling the corresponding BSR-SR RACH when the DSR-SR RACH cancellation conditions are met is configured or enabled; the mechanism of reporting the BSR when the DSR reporting conditions are met is configured or enabled; the mechanism of canceling the BSR when the DSR cancellation conditions are met is configured or enabled; the UL grant can carry the DSR MAC CE and the corresponding BSR MAC CE; the UL grant can carry the DSR and the corresponding data volume of the DSR; the UL grant can carry the data volume of the corresponding triggered BSR; the UL grant can carry the corresponding DSR MAC CE; all SDUs corresponding to the suspended DSR are deleted.

[0475] In the first embodiment provided by the embodiments of the present application, when there are delay-sensitive data and non-delay-sensitive data in one LCH or in part of the LCHs of multiple LCHs, the delay-sensitive data is transmitted first to ensure the transmission requirements of the delay-sensitive data.

[0476] Example 2

[0477] Prioritize latency-sensitive data.

[0478] Specifically, for an LCH, one of the following methods can be used: 1. Prioritize sending delay-sensitive data; 2. Prioritize delay-sensitive SDU grouping; 3. Prioritize multiplexing delay-sensitive MAC SDU in MAC PDU; 4. Modify the token bucket size (Bj), or PBR.

[0479] For multiple LCHs, one of the following methods can be used: 1. Adjust the priority of LCH; 2. Prioritize the multiplexing of delay-sensitive MAC SDUs into MAC PDUs.

[0480] For an uplink grant, the UE generates a MAC PDU and / or performs an LCP process and / or invokes a multiplexing and assembly function. If latency-sensitive data exists, the UE prioritizes transmission of the data, or prioritizes or ensures multiplexing of the data during the LCP process, or prioritizes or ensures multiplexing and grouping of the data during the multiplexing and assembly process. Specifically, this includes at least one of the following:

[0481] The data described in the first item, delay-sensitive data, includes at least: PDCP SDU / PDU, RLC SDU / PDU, and MAC SDU.

[0482] The second item, the delay sensitivity, means that the delay of the data is less than or equal to the first threshold, or the remaining duration of the first timer of the data is less than or equal to the second threshold (the first timer is the PDCP discard timer, or discardTimerForLowImportance), or the packet delay budget (PDB) of the data / the delay budget of the data packet set (PSDB) is less than or equal to the third threshold.

[0483] Item 3: For an LCH, the UE prioritizes packetization, delivery, multiplexing, or transmission of the delay-sensitive data. Specifically, one of the following methods may be used:

[0484] Method 1: Break the first-in-first-out principle. In some cases, if there are delay-sensitive data and non-delay-sensitive data in an LCH, when packaging or sending data to the lower layer, priority will be given to packaging or sending the delay-sensitive data. In other cases, if there are delay-sensitive data and non-delay-sensitive data in an LCH, and the delay-sensitive data arrives later, or the delay-sensitive data is not the first or the first N data to be transmitted, or the total data size of the delay-sensitive data and the non-delay-sensitive data is greater than the total data size of the LCH that the uplink grant can carry, or the total data size of the delay-sensitive data and the non-delay-sensitive data before the delay-sensitive data is greater than the total data size of the LCH that the uplink grant can carry, when packaging or sending data to the lower layer, priority will be given to packaging or sending the delay-sensitive data.

[0485] Method 2: Prioritize the delivery of delay-sensitive data.

[0486] Method 3: Prioritize delay-sensitive SDU grouping.

[0487] Method 4: Prioritize the multiplexing of delay-sensitive MAC SDUs into MAC PDUs.

[0488] Method 5: Modify Bj or PBR.

[0489] In some cases, if there are delay-sensitive data and non-delay-sensitive data in an LCH, Bj or PBR is adjusted when assembling packets or LCP.

[0490] In other cases, if an LCH contains both delay-sensitive data and non-delay-sensitive data, and the delay-sensitive data arrives later, or the delay-sensitive data is not the first or the first N data to be transmitted, or the total amount of delay-sensitive data and non-delay-sensitive data is greater than the total amount of data that the uplink grant can carry on the LCH, or the total amount of delay-sensitive data and non-delay-sensitive data preceding the delay-sensitive data is greater than the total amount of data that the uplink grant can carry on the LCH, Bj or PBR is adjusted when assembling packets or LCPs. The purpose is to ensure that delay-critical data can be transmitted.

[0491] Method 6: Modify the LCH mapping restriction. If there is delay-sensitive data, or the remaining delay of the data is less than a threshold, then even if the LCH is configured not to use the uplink grant, the LCH data or delay-sensitive data can be multiplexed in the uplink grant.

[0492] Item 4: For multiple LCHs, the UE prioritizes grouping, sending, multiplexing, or transmitting the delay-sensitive data. Specifically, one of the following methods may be used:

[0493] Method 1: Adjust the priority of LCH.

[0494] Under the first condition, the UE adjusts the priority of the LCH. The LCH is an LCH with delay-sensitive data (priority), or the LCH is an LCH without delay-sensitive data (low priority).

[0495] The first condition includes at least one of the following: there are delay-sensitive data and non-delay-sensitive data among the multiple LCHs; the priority of the LCH for delay-sensitive data is lower than the priority of other LCHs; the priority of the LCH for delay-sensitive data is lower than the priority of the LCH for non-delay-sensitive data; the total data size of the LCH for delay-sensitive data and the LCH for non-delay-sensitive data is greater than the total data size of the LCH that can be carried by the uplink grant, and according to the LCP process, the data of the delay-sensitive data or the LCH corresponding to the data cannot be multiplexed on the uplink grant; the total data size of the LCH for delay-sensitive data and the LCH for non-delay-sensitive data (and to be multiplexed in the uplink grant before the delay-sensitive data is multiplexed) is greater than the total data size of the LCH that can be carried by the uplink grant, the Bj or PBR of the LCH for delay-sensitive data is less than the size of the critical data, and the data of the LCH for delay-sensitive data cannot be carried on the uplink grant.

[0496] In some embodiments, the priority of the LCH with latency-sensitive data is adjusted to the highest priority (e.g., LCH1 has a lower LCH priority than LCH2, and if LCH1 has latency-sensitive data, LCH1 is considered to have a higher priority than LCH2);

[0497] In some embodiments, the priority of an LCH containing latency-sensitive data is adjusted to a relatively highest priority, where the relatively highest priority is the highest priority among all LCHs with the same LCH priority. (For example, if LCH1 and LCH2 have the same LCH priority, and LCH1 contains latency-sensitive data, then LCH1 is considered to have a higher priority than LCH2, or the sub-priority of LCH1 is considered to have a higher sub-priority than LCH2.)

[0498] In some embodiments, after being sorted according to the priority order of the LCP, the LCPs are reordered according to latency. Optionally, all LCHs with latency-sensitive data may be considered to have the same priority, or the priority order may be further limited based on the remaining time of the data in the LCHs with latency-sensitive data (for example, if LCH1 has 1 second of data remaining and LCH2 has 2 seconds of data remaining, LCH1 has a higher priority. LCH3 has no latency-sensitive data and has the lowest priority).

[0499] Method 2: Prioritize the multiplexing of delay-sensitive MAC SDUs into MAC PDUs.

[0500] Under the first condition, the UE preferentially multiplexes the delay-sensitive MAC SDU into the MAC PDU. The LCH is an LCH with delay-sensitive data (priority), or the LCH is an LCH without delay-sensitive data (low priority). The first condition includes at least one of the following: there are delay-sensitive data and non-delay-sensitive data among the multiple LCHs, the priority of the LCH for delay-sensitive data is lower than the priority of other LCHs, the priority of the LCH for delay-sensitive data is lower than the priority of the non-delay-sensitive LCH, the total data size of the LCH for delay-sensitive data and the LCH for non-delay-sensitive data is greater than the total data size of the LCH that can be carried by the uplink grant, according to the LCP process, the data of the delay-sensitive data or the LCH corresponding to the data cannot be multiplexed on the uplink grant, the total data size of the LCH for delay-sensitive data and the LCH for non-delay-sensitive data (and to be multiplexed in the uplink grant before the delay-sensitive data is multiplexed) is greater than the total data size of the LCH that can be carried by the uplink grant, the Bj or PBR of the LCH for delay-sensitive data is less than the size of the delay-critical data, and the data of the LCH for delay-sensitive data cannot be carried on the uplink grant.

[0501] Compared with method 2, the UE behavior in method 1 is to adjust the LCH priority, that is, the configuration parameters;

[0502] Compared with method 1, method 2 adjusts the data packaging process and does not change the configuration parameters.

[0503] Among them, the third and fourth items can be used together or separately.

[0504] On the basis of the above steps, the UE reports the delay and / or data volume information to the base station, and the reporting may be in the form of DSR and / or BSR.

[0505] Optionally, the base station schedules or configures an uplink grant based on the report.

[0506] Example 3

[0507] Modify the definition of data volume reporting in DSR MAC CE, or modify the definition of data volume statistics of PDCP / RLC

[0508] When the UE statistically reports the DSR MAC CE, the data volume information reported in the DSR MAC CE. The data volume information is statistically reported by the PDCP and / or RLC, and / or notified to the MAC layer. Specifically, it includes at least one of the following:

[0509] A. The data volume information includes the data volume information of delay-critical data and the data volume information of non-delay critical data.

[0510] B. Optionally, when the second condition is met, the data volume information includes the data volume information of delay-critical data and also includes the data volume information of non-delay critical data. The second condition includes at least one of the following: there are delay-sensitive data and non-delay-sensitive data in the multiple LCHs; the priority of the LCH for delay-sensitive data is lower than the priority of other LCHs; the priority of the LCH for delay-sensitive data is lower than the priority of the non-delay-sensitive LCH; the Bj or PBR of the LCH for delay-sensitive data is smaller than the size of the duration-critical data; the delay-sensitive SDU / PDU is not the first N SDU / PDU in the LCH (optionally, N is an integer, such as 1, 2, 3, etc.), the delay-sensitive SDU / PDU arrives later in the LCH than the non-delay critical SDU / PDU, and the delay-sensitive SDU / PDU arrives first in the LCH.

[0511] C. When the DSR triggering condition is met and the DSR MAC CE is reported, the data volume information is reported, where the data volume information is the data volume information in A or B.

[0512] D, explanation for described data amount information, just concrete mode is, modify the definition of the data amount content of data amount reporting among the DSR MAC CE (as, think or define, the data amount reported, be included in the data amount of all SDU / PDUs in this LCH, perhaps, be included in the data amount of the delay-critical SDU / PDU in this LCH and the data amount information of the non-delay critical SDU / PDU before delay-critical, perhaps, comprise the information of the data amount of other (as non-delay critical SDU / PDU) data while the data amount of delay-critical SDU / PDU, perhaps, be included in the data amount information of the non-delay critical SDU / PDU before delay-critical while the data amount of delay-critical SDU / PDU), perhaps, for modifying the definition of the data amount of PDCP / RLC statistics (as, when statistics, be included in the data amount of all SDU / PDUs in this LCH, perhaps, be included in the data amount of the delay-critical SDU / PDU in this LCH and the data amount information of the non-delay critical SDU / PDU before delay-critical).

[0513] Based on the report, the base station schedules or configures uplink transmission resources.

[0514] In Example 3 of the present application, when delay-sensitive data and non-delay-sensitive data exist in an LCH, or in some LCHs of multiple LCHs, the information reported by the UE reflects the information of the non-delay-critical data, ensuring the transmission requirements of the delay-sensitive data. Compared with Examples 1 and 2, this solution redefines the physical meaning of the reported content, but may have less impact on the protocol.

[0515] Example 4

[0516] For a network energy saving (NES) cell, the cell is an on-demand system information block 1 (SIB1) cell, or a SIB1-less cell, that is, SIB1 is not provided directly but is provided upon request by an NES UE.

[0517] The wireless communication method provided in the embodiments of the present application includes one or more of the following:

[0518] A first UE cannot access the NES cell. The first UE is a non-NES UE, i.e., a legacy UE, or a UE that does not support sending an on-demand SIB1 request, or a UE that supports the on-demand SIB request function. The access includes cell selection or reselection to the NES cell, or a Rel-18 NES UE (e.g., a UE that supports cell DTX / DRX, or another example, a UE that supports NES-specific CHO).

[0519] The first UE is controlled in one or more of the following ways so that the first UE cannot access the NES cell:

[0520] Using the cell bar indication in the Master Information Block (MIB), in one example, the cell bar is set to be barred, and the first UE cannot access the NES cell; or, the ssb-SubcarrierOffset is indicated as a reserved value, or, it is indicated in the MIB that SIB1 is not transmitted, and the first UE cannot access the NES cell.

[0521] The first UE accesses the NES cell (such as the NES cell sends SIB1 at the request of the second UE), but the first UE cannot receive SIB1 or has no valid SIB1 (such as the NES cell does not send SIB1 again), then the first UE reselects to other cells with the same frequency point, or considers that the NES cell is banned for 300s (or other duration).

[0522] If the first UE learns that a cell is the NES cell, the first UE does not select or reselect the NES cell and / or does not perform a final check. For example, if the first UE is a UE that does not support NES or is a Rel18 NES UE, in the SIB2 / 3 / 4 configuration, the frequency of the NES cell is configured to be a frequency with a low or lowest reselection priority, or the NES cell is set as an excluded cell.

[0523] The second UE may access the NES cell. The second UE is not the first UE, or the second UE is a UE that supports sending an on-demand SIB1 request, or the second UE is a UE that has sent an on-demand SIB1 request.

[0524] The second UE considers the cell bar indication in the MIB of the NES cell to be not barred (even if the cell barred indication in the MIB is set to barred), or the second UE ignores the bar indication in the MIB of the NES cell. Specifically, if the second UE obtains the first control indication and / or on-demand SIB1 request-related configuration information of the NES cell, the UE considers the cell bar indication in the MIB of the NES cell to be not barred (even if the cell barred indication in the MIB is set to barred), or the second UE ignores the bar indication in the MIB of the NES cell. For example, if the first control indication of the NES cell can access the NES cell (or the first control information appears, or the first control information has a specific value), and / or the UE has on-demand SIB1 request-related configuration information (which can be for the NES cell or a common configuration), the UE considers the cell bar indication in the MIB of the NES cell to be not barred (even if the cell barred indication in the MIB is set to barred), or the second UE ignores the bar indication in the MIB of the NES cell.

[0525] The second UE can access the NES cell. Specifically, whether to access the NES cell can be determined in one of the following ways. For example, a UE that receives the first control indication and / or on-demand SIB1 request related configuration information of the NES cell can determine whether it can access the NES cell and / or send an on-demand SIB1 request, or camp in the NES cell based on the received information. For example, if the first control indication of the NES cell can access the NES cell (or the first control information appears, or the first control information is a specific value), and / or the UE has on-demand SIB1 request related configuration information (which can be the NES cell or a public configuration), then the UE can send an on-demand SIB1 request, and / or can select or reselect the NES cell, and / or perform a final check on the NES cell, and / or camp in the NES cell. For example, the first control indication of the NES cell and / or the on-demand SIB1 request related configuration information is received by the second UE on a cell capable of sending SIB1 (such as the anchor cell of the NES cell or the neighboring cell of the NES cell, or the NES cell).

[0526] The second UE accesses the NES cell (e.g., the NES cell sends SIB1 at the request of the second UE), but the second UE cannot receive SIB1 or has no valid SIB1 (e.g., the NES cell does not send SIB1 again), then the second UE resends the on-demand SIB1 request, or reselects to another cell with the same frequency, or considers that the NES cell is banned for 300s (or other duration).

[0527] Among them, UE3 of the second UE accesses the NES cell (such as the NES cell sends SIB1 at the request of UE2 of the second UE), but UE3 of the second UE cannot receive SIB1 or has no valid SIB1 (such as the NES cell does not send SIB1 again), then UE3 of the second UE sends an on-demand SIB1 request, or reselects to other cells with the same frequency point, or considers that the NES cell is barred for 300s (or other duration). UE2 of the second UE accesses the NES cell (such as the NES cell sends SIB1 at the request of UE2 of the second UE), but UE2 of the second UE cannot receive SIB1 or has no valid SIB1 (such as the NES cell does not send SIB1 again), then UE2 of the second UE resends the on-demand SIB1 request, or reselects to other cells with the same frequency point, or considers that the NES cell is barred for 300s (or other duration).

[0528] The UE3 of the second UE determines whether it can select or reselect the NES cell or whether it can camp or access the NES cell. The UE3 of the second UE determines based on one or more of the following information: whether there is a first control indication of the NES cell or whether the first control information indicates that access is possible or whether the first control information is a specific value (for example, if the first control information appears, or the first control indication indicates that access is possible, or the first control information is a specific value, then the UE3 can select, reselect, camp on, or access the NES cell), whether the UE has on-demand SIB1 request related configuration information (which can be for the NES cell or a public configuration. If there is a configuration, or if there is a configuration specific to the NES cell, then the UE3 can select, reselect, camp on, or access the NES cell), whether second control information appears in the SIB of the NES cell, or whether the second control information indicates that access is possible, or whether the second control information is a specific value (if it appears, or indicates access, or is a specific value, then the UE3 can select, reselect, camp on, or access the NES cell).

[0529] The second UE may consider the cell reselection frequency of the NES cell to have a high priority, or may preferentially select the NES cell. Alternatively, a dedicated cell reselection priority and / or a dedicated cell reselection allowed / excluded list may be configured for the second UE, thereby giving the second UE a higher priority in selecting the NES cell or its frequency, or giving the second UE a lower priority in selecting the NES cell or its frequency.

[0530] In some implementations, the on-demand (OD) configuration (configuration information related to the on-demand SIB1 request) may be used to indicate at least one of the following: an NES cell identifier or list, resource configuration information for sending the on-demand SIB1 request (or UL Wake Up Signal (WUS) configuration), a relationship between the UL-WUS configuration and the NES cell identifier / list, a NES cell frequency or frequency list, etc.

[0531] Optionally, the OD configuration may include one or more of the following: a configuration for sending an on-demand request (per NES cell or common for this function), an NES cell identifier or list, and an NES cell frequency or frequency list. Furthermore, the information provided by the network device to the UE may also simultaneously indicate the NES cell or which NES cells are R18 NES cells (i.e., cells that support cell DTX / DRX). Furthermore, the information provided by the network device to the UE may also include cell selection parameters and / or cell reselection parameters (the parameters are used by the UE to select or reselect the NES cell, and / or to send an on-demand SIB1 request).

[0532] For example, based on the cell selection parameter, or based on satisfying the S criterion, the UE selects the NES cell or sends an on-demand SIB1 request. For example, based on the cell selection parameter and / or reselection parameter, or based on satisfying the S criterion and / or R, or based on the cell selection parameter and / or reselection parameter satisfying the cell reselection criterion, the UE reselects the NES cell or sends an on-demand SIB1 request. For example, the cell selection parameter and / or reselection parameter is at least one of SIB1 / 2 / 3 / 4 for cell selection parameters and / or reselection parameters. Optionally, the configuration of sending on-demand requests may be sent to all NES cells, may be sent to only some NES cells, or may not be sent to all NES cells.

[0533] For an NES UE, if it knows that a cell is an on-demand SIB1 cell, and if the UE is not configured to send an on-demand request (or is not configured to send an OD request for the cell), option 1: the NES UE does not read SIB1, option 2: the NES UE performs cell selection or reselection, or selects or reselects to another cell, or selects or reselects a cell of another frequency, or excludes the NES cell from the selected or reselected cell.

[0534] For the case where the NES cell MIB indicates that the device is prohibited, the UE behavior may include but is not limited to the following (for example):

[0535] Behavior A: If it is a legacy UE, the legacy UE does not search SIB1. The legacy UE is a UE that does not support on-demand SIB1 and does not support cell DTX / DRX.

[0536] Action B, otherwise, other circumstances: including at least one of the following:

[0537] Case 1: The UE does not receive the OD configuration (configuration related to on-demand SIB1 requests). This NES cell could be an R18 UE (a UE supporting cell DTX / DRX) or an R19 UE (a UE supporting on-demand SIB1 requests). The R18 UE should search because it may be an R18 base station (this may waste SIB1 searches because it may ultimately be an R19 base station). If the R19 UE is also an R18 UE, a search is required. If the R19 UE is not an R18 UE, no search is required.

[0538] Case 2: The UE obtains the OD configuration, which is specific to the NES cell. This UE must be an R19 UE. This NES cell must be R19. This UE needs to search.

[0539] Case 3: The UE receives the OD configuration, which is common and not cell-specific. This UE must be an R19 UE. The NES cell can be either R18 or R19. The UE must search, but the search may be in vain, resulting in invalid results, as it may end up with an R18 NES cell.

[0540] For UEs in NES cells, the behavior can be as follows:

[0541] Behavior A, such as OD configuration is provided per cell.

[0542] Based on reselection, if Cell A provides OD config for NES cell, the R19 UE tries to camp on NES cell. If Cell A does not provide OD config for NES cell but UE has it via RRC release, the UE tries to camp on NES cell. Otherwise, no try. (For reselection, if Cell A provides OD config for NES cell, the R19 UE tries to camp on NES cell. If Cell A does not provide OD config for NES cell but UE has it via RRC release, the UE tries to camp on NES cell. Otherwise, no try.) Wherein, Cell A is the cell that sends at least its own SIB1 and / or OD configuration.

[0543] Based on the selection, if the UE has OD configuration via RRC release, the UE tries to camp on the NES cell. Otherwise, no try.

[0544] Action B: If the OD configuration is provided based on the (per)NES function, but the network device also provides a list or identifier of NES cells, then:

[0545] Based on reselection, if Cell A provides OD config and NES cell list, the R19 UE tries to camp on NES cell. If Cell A does not provide OD config but UE has OD config and NES cell list (or identification) via RRC release, the UE tries to camp on NES cell. Otherwise, no try.

[0546] Based on the selection, if the UE has OD configuration and NES cell list (or identification) via RRC release, the UE tries to camp on the NES cell. Otherwise, no try.

[0547] For system information updates or paging

[0548] Solution 1 (Alt1): Whenever there is a system information update or paging, the NES cell sends a notification to the UE. Optionally, the NES cell has previously sent SIB1 (this can be continuous, but there may be periods of lag). Optionally, the UE residing on the NES cell receives the notification.

[0549] Solution 2 (Alt12): NES cells that are not transmitting SIB1 do not send system information updates or paging. Optionally, UEs residing in the NES cell or having previously obtained SIB1 information from the NES cell will behave as follows: Alt1: Upon re-routing to another cell, the UE will send a UL WUS requesting the NES cell to send SIB1. Alt2: Upon selecting or reselecting another cell, to determine if the stored SIB1 is valid, the UE must re-acquire the entire SIB1 message in the selected or reselected cell, rather than simply comparing the area or value tag for consistency.

[0550] The UE behavior for NES cells can be as follows (for example): cell selection, cell reselection, or pause. For example, if the network provides information to the UE, the information may include on-demand SIB1 request-related configuration information + NES cell, or which NES cells or cells are R18 NES cells (i.e., cells supporting cell DTX / DRX). Optionally, the NES cell MIB indicates "cellbarred". Optionally, the contents of one or more boxes shown in Table 1 are used as the UE behavior.

[0551] Table 1. UE behavior examples

[0552] The UE behavior for NES cells can be, for example, cell selection, cell reselection, or cell reselection. For example, if the network provides information to the UE, the information may include on-demand SIB1 request-related configuration information that is not provided to the NES cell, or which NES cells or cells are R18 NES cells (i.e., cells that support cell DTX / DRX). Optionally, the NES cell MIB indicates "cellbarred." Optionally, the contents of one or more boxes shown in Table 2 are used as the UE behavior.

[0553] Table 2. UE behavior examples

[0554] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0555] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in 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 the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0556] FIG25 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. As shown in FIG25 , the terminal device 2500 includes:

[0557] The first communication unit 2501 is configured to send first information, where the first information includes information about first data, and the first data is data whose remaining time meets the delay requirement.

[0558] In some embodiments, the first communication unit 2501 is further configured to send the first information when a delay status report DSR is triggered.

[0559] In some embodiments, the first information includes information of a first logical channel LCH or a logical channel group LCG.

[0560] In some embodiments, the first information includes first indication information, and the first indication information is used to indicate the existence of first data.

[0561] In some embodiments, the first indication information is based on LCH, LCG, or terminal device indication.

[0562] In some embodiments, the first information includes second indication information, and the second indication information is used to indicate the data volume of the first data.

[0563] In some embodiments, the second indication information is based on LCH, LCG or terminal device indication.

[0564] In some embodiments, the first information is carried in one or more of the following:

[0565] MAC PDU;

[0566] MAC sub-PDU header;

[0567] MAC sub-PDU payload;

[0568] MAC CE;

[0569] MAC CE subheader.

[0570] In some embodiments, the payload of the MAC CE or MAC sub-PDU includes one of the following:

[0571] an enhanced DSR MAC CE, where the enhanced DSR MAC CE is a DSR MAC CE including the first information;

[0572] BSR MAC CE;

[0573] Defined MAC CE.

[0574] In some embodiments, factors determining whether to generate the enhanced DSR MAC CE or whether to generate the defined MAC CE include one or more of the following:

[0575] Whether to generate enhanced DSR MAC CE or defined MAC CE;

[0576] whether the first data exists;

[0577] Whether the first data is the data that arrives first;

[0578] Whether the first data arrives before the second data, the second data being data whose remaining time does not meet the latency requirement;

[0579] Whether the second data is the first number of data in the LCH buffer;

[0580] whether the second data is not the first second number of data;

[0581] Whether the uplink grant can carry the enhanced DSR MAC CE or the defined MAC CE.

[0582] In some embodiments,

[0583] The priority of the defined MAC CE is lower than or equal to the priority of the DSR MAC CE; or,

[0584] The priority of the enhanced DSR MAC CE is higher than or equal to the priority of the DSR MAC CE.

[0585] In some embodiments, one uplink grant can carry the defined MAC CE and DSR MAC CE simultaneously.

[0586] In some embodiments, the first condition for triggering the BSR corresponding to the BSR MAC CE includes one or more of the following:

[0587] There is a data packet in the first LCH or LCG whose remaining time is less than or equal to the threshold;

[0588] Data packets in the first LCH or LCG with a remaining time less than or equal to the threshold have not been transmitted or reported;

[0589] The data packets whose minimum remaining time in the first LCH or LCG is less than or equal to the threshold have not been transmitted or reported;

[0590] There is no pending DSR in the first LCG;

[0591] When DSR is triggered, the BSR of the corresponding LCG is also triggered;

[0592] A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists.

[0593] In some embodiments, the second condition for canceling the BSR includes one or more of the following:

[0594] The DSR is cancelled;

[0595] The BSR is triggered based on the DSR and the DSR is canceled;

[0596] A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists;

[0597] A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met;

[0598] The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR;

[0599] The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR;

[0600] The transmitted uplink grant carries the data volume of the BSR;

[0601] All service data units SDU of the DSR are deleted.

[0602] In some embodiments, the BSR cannot trigger a scheduling request SR and / or cannot trigger a random access RA procedure; or,

[0603] In the absence of an available uplink grant, the BSR is not allowed to trigger an SR, and / or the BSR is not allowed to trigger an RA process.

[0604] In some embodiments,

[0605] If the SR triggered by the DSR is cancelled, the SR triggered by the BSR is cancelled; and / or,

[0606] If the first RA process triggered by the SR triggered by the DSR is stopped, the second RA process corresponding to the SR triggered by the BSR is stopped.

[0607] In some embodiments, the third condition in which the SR triggered by the BSR is canceled or the second RA process corresponding to the SR triggered by the BSR is stopped includes one or more of the following:

[0608] The BSR is triggered based on the DSR and the DSR is canceled, and the first RA process triggered by the DSR is canceled;

[0609] The SR is triggered by a BSR, which is triggered based on the DSR, or is triggered when the first information exists;

[0610] The RA process is triggered by an SR, and the SR is triggered by a BSR, and the BSR is triggered based on the DSR, or is triggered when the first information exists;

[0611] The DSR is canceled, or the SR triggered by the DSR is canceled, or the RA process triggered by the SR triggered by the BSR is terminated;

[0612] A third mechanism is configured or enabled, wherein the third mechanism cancels the second RA process when a cancellation condition of the first random access process is met;

[0613] A first mechanism is configured or enabled, wherein the first mechanism triggers a BSR when a DSR reporting condition is met;

[0614] A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met;

[0615] A fourth mechanism is configured or enabled, wherein if a DSR-triggered SR is canceled, the corresponding BSR-triggered SR is invalidated.

[0616] The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR;

[0617] The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR;

[0618] The transmitted uplink grant carries the data volume of the BSR;

[0619] The transmitted uplink grant carries the DSR MAC CE;

[0620] All service data units SDU of the DSR are deleted.

[0621] FIG26 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. As shown in FIG26 , the terminal device 2600 includes:

[0622] The second communication unit 2601 is configured to send third data, where the third data includes first data and second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0623] In some embodiments,

[0624] The third data is data corresponding to the first LCH or LCG; or,

[0625] The third data is data corresponding to the first LCH or LCG and the second LCH or LCG;

[0626] The data in the first LCH or LCG includes the second data; the data in the second LCH or LCG includes the first data.

[0627] In some embodiments, the second data is packaged or transmitted before the first data.

[0628] In some embodiments, the transmission of the second data prior to the packetization or transmission of the first data comprises one or more of the following:

[0629] The PDCP, RLC or MAC preferentially transmits the second data;

[0630] The PDCP, RLC or MAC preferentially delivers the second data to a lower layer;

[0631] The PDCP, RLC or MAC preferentially packages the SDU of the second data into a PDU;

[0632] The MAC preferentially multiplexes the second data during the LCP process;

[0633] Prioritizing multiplexing or carrying the second data by adjusting parameters of the logical channel priority LCP;

[0634] Using the first LCP process, preferentially multiplexing or carrying the second data;

[0635] Prioritizing multiplexing or carrying the second data on an uplink grant;

[0636] Modify the LCP mapping restriction so that the first uplink grant can multiplex or carry the second data, or so that the first uplink grant can multiplex or carry the second data if there are remaining uplink resources according to the LCP process.

[0637] In some embodiments, the first uplink grant is an uplink grant configured to be unable to carry first LCH or LCG data, and second data exists in the first LCH or LCG.

[0638] In some embodiments, the adjusting the parameters of the LCP includes one or more of the following:

[0639] Adjust the token bucket size of the first LCH or LCG;

[0640] Adjusting the priority bit rate of the first LCH or LCG;

[0641] Adjust the logical channel priority of the first LCH or LCG.

[0642] In some embodiments, using the first LCP process includes one or more of the following:

[0643] Prioritize multiplexing of data from the first LCH or LCG;

[0644] Prioritize multiplexing of the second data in the first LCH or LCG;

[0645] Allocating resources according to the data amount of the second data of the first LCH or LCG when allocating resources to the first LCH or LCG based on the LCP process;

[0646] When allocating resources to the LCH or LCG based on the LCP process, first allocate resources to the first LCH or LCG or first allocate resources to the second data of the first LCH or LCG;

[0647] When allocating resources to an LCH or LCG based on the LCP process, if there are remaining uplink transmission resources, perform at least one of the following: not carrying padding bits, transmitting data of the first LCH or LCG, or allocating resources to the first LCH or LCG.

[0648] In some embodiments, the fourth condition that the second data is packaged or transmitted before the first data includes:

[0649] The second data reaches the PDCP layer, the RLC layer, or the MAC layer after the first data;

[0650] The second data is not the first third amount of data to be transmitted;

[0651] The total amount of the second data and the first data is greater than the total amount of data of the first LCH that can be carried by the uplink grant;

[0652] The total amount of the second data and the non-sensitive data before the second data is greater than the total amount of data of the first LCH that can be carried by the uplink grant;

[0653] The total amount of the second data and the first data is greater than the token bucket size corresponding to the first LCH that can be carried by the uplink grant;

[0654] The total data volume of the second data and the non-sensitive data before the second data is greater than the token bucket size corresponding to the first LCH that can be carried by the uplink authorization.

[0655] In some embodiments, the method further comprises one or more of the following:

[0656] The terminal device adjusts the multiplexing or packetizing order of data of the first LCH or LCG and the second LCH or LCG;

[0657] The terminal device adjusts the transmission of data of the first LCH or LCG and the second LCH or LCG;

[0658] The data of the first LCH or LCG is multiplexed, packaged, or transmitted before the data of the second LCH or LCG.

[0659] In some embodiments,

[0660] Among the priorities of LCHs or LCGs, the priority of the first LCH or LCG is higher than the priority of the second LCH or LCG; and / or,

[0661] In the multiplexing or packetizing order of MAC SDU, the multiplexing or packetizing of the MAC SDU of the first LCH or LCG precedes the multiplexing or packetizing of the MAC SDU of the second LCH or LCG.

[0662] In some embodiments, the priority of the first LCH or LCG is higher than the priority of the second LCH or LCG, including:

[0663] The priority of the first LCH or LCG is adjusted to the highest priority;

[0664] The priority of the first LCH or LCG is adjusted to the highest sub-priority among LCHs or LCGs of the same priority;

[0665] The priority of the first LCH or LCG is adjusted to a higher priority among LCHs or LCGs of the same priority;

[0666] The priorities of all first LCHs or LCGs are adjusted to be higher than the priorities of other LCHs or LCGs of the same priority, and all first LCHs or LCGs are sorted according to their delays;

[0667] The priorities of all first LCHs or LCGs are adjusted to be the same and higher than the priorities of other LCHs or LCGs, and all first LCHs or LCGs are sorted according to their delays.

[0668] In some embodiments, the fifth condition for adjusting the multiplexing or packetization order of data of the first LCH or LCG and the second LCH or LCG, or adjusting the transmission of data of the first LCG and the second LCG includes one or more of the following:

[0669] The priority of the first LCH or LCG is lower than the priority of other LCHs or LCGs;

[0670] The priority of the first LCH or LCG is lower than the priority of the second LCH or LCG;

[0671] The total amount of data of the first LCH or LCG and the second LCH or LCG is greater than the total amount of data that can be carried by the uplink grant;

[0672] The second data or the data of the first LCH or LCG cannot all be multiplexed on the uplink grant;

[0673] The token bucket size or the priority bit rate of the first LCH or LCG is smaller than the size of the second data of the first LCH or LCG.

[0674] In some embodiments, the second data includes one or more of the following:

[0675] Data whose delay is less than or equal to the first threshold;

[0676] Data indicating that the remaining duration of the first timer is less than or equal to the second threshold;

[0677] Data in which the packet delay budget PDB or the delay budget PSDB of a data packet set is less than or equal to the third threshold;

[0678] Data corresponding to the QoS flow whose delay requirement is less than or equal to the fourth threshold based on the quality of service (QoS) requirement.

[0679] In some embodiments, the second data includes one or more of the following:

[0680] SDAP SDU or SDAP PDU;

[0681] PDCP SDU or PDCP PDU;

[0682] RLC SDU or RLC PDU;

[0683] MAC SDU;

[0684] A collection of PDUs or a data burst.

[0685] In some embodiments, the second communication unit 2601 is further configured to send second information, where the second information is used to indicate the delay and / or data volume of the sent data.

[0686] FIG27 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. As shown in FIG27 , the terminal device 2700 includes:

[0687] The third communication unit 2701 is configured to send third information, where the third information includes information about the data volume of the first data and information about the data volume of the second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0688] In some embodiments, the third information is statistics collected by the PDCP layer and / or the RLC layer, and / or is informed by the PDCP layer and / or the RLC layer to the MAC layer.

[0689] In some embodiments, the sixth condition that the third information includes information about the amount of the second data and information about the amount of the first data includes one or more of the following:

[0690] The data of the one or more LCHs or LCGs to be transmitted includes the second data and the first data;

[0691] In a third LCH or LCG of the plurality of LCHs, an SDU of the second data arrives after an SDU of the first data, and data of the third LCH or LCG includes the second data and the first data;

[0692] A priority of a first LCH or LCG among the plurality of LCHs or LCGs is lower than a priority of other LCHs or LCGs among the plurality of LCHs or LCGs, the first LCH or LCG being an LCH or LCG having second data;

[0693] The priority of the first LCH or LCG is lower than the priority of a second LCH or LCG among the plurality of LCHs or LCGs, and the second LCH or LCG is a LCH or LCG having the first data;

[0694] The token bucket size or the priority bit rate of the first LCH or LCG is smaller than the size of the second data in the first LCH or LCG;

[0695] The token bucket size or priority bit rate of the first LCH or LCG is smaller than the amount of data to be transmitted in the first LCH or LCG;

[0696] The second data of the first LCH or LCG is not the first fourth amount of data in the first LCH or LCG;

[0697] The SDU of the second data of the first LCH or LCG is not the first fifth number of SDUs in the first LCH or LCG.

[0698] In some embodiments,

[0699] The first data is all first data to be transmitted in the corresponding LCH or LCG, or,

[0700] The first data is all first data to be transmitted in the corresponding LCH or LCG and arriving before the second data.

[0701] In some embodiments, the third information is included in a DSR MAC CE or an enhanced DSR MAC CE or a defined MAC CE.

[0702] In some embodiments, the third information includes one or more of the following:

[0703] Information on the amount of data for the LCH or LCG or terminal equipment;

[0704] Information on the data volume corresponding to all SDUs or PDUs to be transmitted;

[0705] Data volume information of the second data and data volume information of the first data that arrived before the second data arrived;

[0706] data volume information of the second data and data volume information of the first data;

[0707] The data amount information of the second data and the data amount information of the other data.

[0708] In some embodiments, the third information carries data amount information corresponding to the fourth LCH or LCG, and the data amount information includes one or more of the following:

[0709] Information on the data volume corresponding to all SDUs or PDUs to be transmitted in the fourth LCH or LCG;

[0710] Data amount information of the second data in the fourth LCH or LCG and data amount information of the first data arriving before the second data arrives;

[0711] Data amount information of the second data and data amount information of the first data in the fourth LCH or LCG;

[0712] The data amount information of the second data and the data amount information of other data in the fourth LCH or LCG.

[0713] The first, second, and third communication units in the terminal device can be implemented by a transceiver in the network device. The terminal device may also include a generation unit for generating data to be transmitted, wherein the generation unit can be implemented by a processor in the terminal device. In practical applications, the first, second, and third communication units can be the same communication unit.

[0714] FIG28 is a schematic diagram of the structure of a network device provided in an embodiment of the present application. As shown in FIG28 , the network device 2800 includes:

[0715] The fourth communication unit 2801 is configured to receive first information, where the first information includes information about first data, and the first data is data whose remaining time meets the delay requirement.

[0716] In some embodiments, the first information includes information of a first logical channel LCH or a logical channel group LCG.

[0717] In some embodiments, the first information includes first indication information, and the first indication information is used to indicate the existence of first data.

[0718] In some embodiments, the first indication information is based on LCH, LCG, or terminal device indication.

[0719] In some embodiments, the first information includes second indication information, and the second indication information is used to indicate the data volume of the first data.

[0720] In some embodiments, the second indication information is based on LCH, LCG or terminal device indication.

[0721] In some embodiments, the first information is carried in one or more of the following:

[0722] MAC PDU;

[0723] MAC sub-PDU header;

[0724] MAC sub-PDU payload;

[0725] MAC CE;

[0726] MAC CE subheader.

[0727] In some embodiments, the payload of the MAC CE or MAC sub-PDU includes one of the following:

[0728] an enhanced DSR MAC CE, where the enhanced DSR MAC CE is a DSR MAC CE including the first information;

[0729] BSR MAC CE;

[0730] Defined MAC CE.

[0731] In some embodiments, factors determining whether to generate the enhanced DSR MAC CE or whether to generate the defined MAC CE include one or more of the following:

[0732] Whether to generate enhanced DSR MAC CE or defined MAC CE;

[0733] whether the first data exists;

[0734] Whether the first data is the data that arrives first;

[0735] Whether the first data arrives before the second data, the second data being data whose remaining time does not meet the latency requirement;

[0736] Whether the second data is the first number of data in the LCH buffer;

[0737] whether the second data is not the first second number of data;

[0738] Whether the uplink grant can carry the enhanced DSR MAC CE or the defined MAC CE.

[0739] In some embodiments,

[0740] The priority of the defined MAC CE is lower than or equal to the priority of the DSR MAC CE; or,

[0741] The priority of the enhanced DSR MAC CE is higher than or equal to the priority of the DSR MAC CE.

[0742] In some embodiments, one uplink grant can carry the defined MAC CE and DSR MAC CE simultaneously.

[0743] In some embodiments, the first condition for triggering the BSR corresponding to the BSR MAC CE includes one or more of the following:

[0744] There is a data packet in the first LCH or LCG whose remaining time is less than or equal to the threshold;

[0745] Data packets in the first LCH or LCG with a remaining time less than or equal to the threshold have not been transmitted or reported;

[0746] The data packets whose minimum remaining time in the first LCH or LCG is less than or equal to the threshold have not been transmitted or reported;

[0747] There is no pending DSR in the first LCG;

[0748] When DSR is triggered, the BSR of the corresponding LCG is also triggered;

[0749] A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists.

[0750] In some embodiments, the second condition for canceling the BSR includes one or more of the following:

[0751] The DSR is cancelled;

[0752] The BSR is triggered based on the DSR and the DSR is canceled;

[0753] A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists;

[0754] A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met;

[0755] The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR;

[0756] The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR;

[0757] The transmitted uplink grant carries the data volume of the BSR;

[0758] All service data units SDU of the DSR are deleted.

[0759] In some embodiments, the BSR cannot trigger a scheduling request SR and / or cannot trigger a random access RA procedure; or,

[0760] In the absence of an available uplink grant, the BSR is not allowed to trigger an SR, and / or the BSR is not allowed to trigger an RA process.

[0761] In some embodiments,

[0762] If the SR triggered by the DSR is cancelled, the SR triggered by the BSR is cancelled; and / or,

[0763] If the first RA process triggered by the SR triggered by the DSR is stopped, the second RA process corresponding to the SR triggered by the BSR is stopped.

[0764] In some embodiments, the third condition in which the SR triggered by the BSR is canceled or the second RA process corresponding to the SR triggered by the BSR is stopped includes one or more of the following:

[0765] The BSR is triggered based on the DSR and the DSR is canceled, and the first RA process triggered by the DSR is canceled;

[0766] The SR is triggered by a BSR, which is triggered based on the DSR, or is triggered when the first information exists;

[0767] The RA process is triggered by an SR, and the SR is triggered by a BSR, and the BSR is triggered based on the DSR, or is triggered when the first information exists;

[0768] The DSR is canceled, or the SR triggered by the DSR is canceled, or the RA process triggered by the SR triggered by the BSR is terminated;

[0769] A third mechanism is configured or enabled, wherein the third mechanism cancels the second RA process when a cancellation condition of the first random access process is met;

[0770] A first mechanism is configured or enabled, wherein the first mechanism triggers a BSR when a DSR reporting condition is met;

[0771] A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met;

[0772] A fourth mechanism is configured or enabled, wherein if a DSR-triggered SR is canceled, the corresponding BSR-triggered SR is invalidated.

[0773] The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR;

[0774] The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR;

[0775] The transmitted uplink grant carries the data volume of the BSR;

[0776] The transmitted uplink grant carries the DSR MAC CE;

[0777] All service data units SDU of the DSR are deleted.

[0778] FIG29 is a schematic diagram of the structure of a network device provided in an embodiment of the present application. As shown in FIG29 , the network device 2900 includes:

[0779] The fifth communication unit 2901 is configured to receive third data, where the third data includes first data and second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

[0780] In some embodiments, the third data is data corresponding to the first LCH or LCG; or,

[0781] The third data is data corresponding to the first LCH or LCG and the second LCH or LCG;

[0782] The data in the first LCH or LCG includes the second data; the data in the second LCH or LCG includes the first data.

[0783] In some embodiments, the second data is transmitted before the first data.

[0784] In some embodiments, the second data includes one or more of the following:

[0785] Data whose delay is less than or equal to the first threshold;

[0786] Data indicating that the remaining duration of the first timer is less than or equal to the second threshold;

[0787] Data in which the packet delay budget PDB or the delay budget PSDB of a data packet set is less than or equal to the third threshold;

[0788] Data corresponding to the QoS flow whose delay requirement is less than or equal to the fourth threshold based on the quality of service (QoS) requirement.

[0789] In some embodiments, the second data includes one or more of the following:

[0790] SDAP SDU or SDAP PDU;

[0791] PDCP SDU or PDCP PDU;

[0792] RLC SDU or RLC PDU;

[0793] MAC SDU;

[0794] A collection of PDUs or a data burst.

[0795] FIG30 is a schematic diagram of the structure of a network device provided in an embodiment of the present application. As shown in FIG30 , the network device 3000 includes:

[0796] The sixth communication unit 3001 is configured to receive third information, wherein the third information includes information about the data volume of the first data and information about the data volume of the second data, the first data is data that meets the delay requirement in the remaining time, and the second data is data that does not meet the delay requirement in the remaining time.

[0797] In some embodiments, the sixth condition that the third information includes information about the amount of the second data and information about the amount of the first data includes one or more of the following:

[0798] The data of the one or more logical channels LCH or logical channel group LCG to be transmitted includes the second data and the first data;

[0799] In a third LCH or LCG of the plurality of LCHs, an SDU of the second data arrives after an SDU of the first data, and data of the third LCH or LCG includes the second data and the first data;

[0800] A priority of a first LCH or LCG among the plurality of LCHs or LCGs is lower than a priority of other LCHs or LCGs among the plurality of LCHs or LCGs, the first LCH or LCG being an LCH or LCG having second data;

[0801] The priority of the first LCH or LCG is lower than the priority of a second LCH or LCG among the plurality of LCHs or LCGs, and the second LCH or LCG is a LCH or LCG having the first data;

[0802] The token bucket size or the priority bit rate of the first LCH or LCG is smaller than the size of the second data in the first LCH or LCG;

[0803] The token bucket size or priority bit rate of the first LCH or LCG is smaller than the amount of data to be transmitted in the first LCH or LCG;

[0804] The second data of the first LCH or LCG is not the first fourth amount of data in the first LCH or LCG;

[0805] The SDU of the second data of the first LCH or LCG is not the first fifth number of SDUs in the first LCH or LCG.

[0806] In some embodiments,

[0807] The first data is all first data to be transmitted in the corresponding LCH or LCG, or,

[0808] The first data is all first data to be transmitted in the corresponding LCH or LCG and arriving before the second data.

[0809] In some embodiments, the third information is included in a DSR MAC CE or an enhanced DSR MAC CE or a defined MAC CE.

[0810] In some embodiments, the third information includes one or more of the following:

[0811] Information on the amount of data for the LCH or LCG or terminal equipment;

[0812] Information on the data volume corresponding to all SDUs or PDUs to be transmitted;

[0813] Data volume information of the second data and data volume information of the first data that arrived before the second data arrived;

[0814] data volume information of the second data and data volume information of the first data;

[0815] The data amount information of the second data and the data amount information of the other data.

[0816] In some embodiments, the third information carries data amount information corresponding to the fourth LCH or LCG, and the data amount information includes one or more of the following:

[0817] Information on the data volume corresponding to all SDUs or PDUs to be transmitted in the fourth LCH or LCG;

[0818] Data amount information of the second data in the fourth LCH or LCG and data amount information of the first data arriving before the second data arrives;

[0819] Data amount information of the second data and data amount information of the first data in the fourth LCH or LCG;

[0820] The data amount information of the second data and the data amount information of other data in the fourth LCH or LCG.

[0821] The fourth, fifth, and sixth communication units in the network device may be implemented by a transceiver in the network device. The network device may also include a determination unit for parsing received data, wherein the determination unit may be implemented by a processor in the network device. In practical applications, the fourth, fifth, and sixth communication units may be the same communication unit.

[0822] Those skilled in the art should understand that the relevant description of the above-mentioned wireless communication device in the embodiment of the present application can be understood with reference to the relevant description of the wireless communication method in the embodiment of the present application.

[0823] Figure 31 is a schematic diagram of a communication device 3100 provided in an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 3100 shown in Figure 31 includes a processor 3110, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0824] Optionally, as shown in FIG31 , the communication device 3100 may further include a memory 3120. The processor 3110 may call and execute a computer program from the memory 3120 to implement the method in the embodiment of the present application.

[0825] The memory 3120 may be a separate device independent of the processor 3110 , or may be integrated into the processor 3110 .

[0826] Optionally, as shown in FIG31 , the communication device 3100 may further include a transceiver 3130 , and the processor 3110 may control the transceiver 3130 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0827] The transceiver 3130 may include a transmitter and a receiver. The transceiver 3130 may further include an antenna, and the number of antennas may be one or more.

[0828] Optionally, the communication device 3100 may specifically be a terminal device of an embodiment of the present application, and the communication device 3100 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0829] Optionally, the communication device 3100 may specifically be a network device in an embodiment of the present application, and the communication device 3100 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0830] Figure 32 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 3200 shown in Figure 32 includes a processor 3210, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0831] Optionally, as shown in FIG32 , the chip 3200 may further include a memory 3220. The processor 3210 may call and execute a computer program from the memory 3220 to implement the method in the embodiment of the present application.

[0832] The memory 3220 may be a separate device independent of the processor 3210 , or may be integrated into the processor 3210 .

[0833] Optionally, the chip 3200 may further include an input interface 3230. The processor 3210 may control the input interface 3230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0834] Optionally, the chip 3200 may further include an output interface 3240. The processor 3210 may control the output interface 3240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0835] Optionally, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0836] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0837] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0838] FIG33 is a schematic block diagram of a communication system 3300 provided in an embodiment of the present application. As shown in FIG33 , the communication system 3300 includes a terminal device 3310 and a network device 3320 .

[0839] Among them, the terminal device 3310 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 3320 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they will not be repeated here.

[0840] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0841] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0842] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0843] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0844] Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0845] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0846] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0847] Optionally, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0848] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0849] The embodiment of the present application also provides a computer program.

[0850] Optionally, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0851] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0852] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0853] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0854] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0855] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0856] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0857] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0858] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, the method comprising: The terminal device sends a first message, where the first message includes information about first data, and the first data is data whose remaining time meets the delay requirement.

2. The method according to claim 1, wherein The terminal device sends first information, including: The terminal device sends the first information when the delay status report DSR is triggered.

3. The method according to claim 1 or 2, wherein: The first information includes information of a first logical channel LCH or a logical channel group LCG.

4. The method according to any one of claims 1 to 3, wherein: The first information includes first indication information, where the first indication information is used to indicate the existence of first data.

5. The method according to claim 4, wherein The first indication information is based on LCH, LCG, or terminal device indication.

6. The method according to any one of claims 1 to 5, wherein: The first information includes second indication information, and the second indication information is used to indicate the data volume of the first data.

7. The method according to claim 6, wherein: The second indication information is based on LCH, LCG or terminal equipment indication.

8. The method according to any one of claims 1 to 7, wherein: The first information is carried in one or more of the following: Media Access Control MAC Packet Data Unit PDU; MAC sub-PDU header; MAC sub-PDU payload; Media Access Control Element MAC CE; MAC CE subheader.

9. The method according to claim 8, wherein The payload of the MAC CE or MAC sub-PDU includes one of the following: an enhanced DSR MAC CE, where the enhanced DSR MAC CE is a DSR MAC CE including the first information; Buffer status reporting BSR MAC CE; Defined MAC CE.

10. The method according to claim 9, wherein: Factors determining whether to generate the enhanced DSR MAC CE or whether to generate the defined MAC CE include one or more of the following: Whether to generate enhanced DSR MAC CE or defined MAC CE; whether the first data exists; Whether the first data is the data that arrives first; Whether the first data arrives before the second data, the second data being data whose remaining time does not meet the latency requirement; Whether the second data is the first number of data in the LCH buffer; whether the second data is not the first second number of data; Whether the uplink grant can carry the enhanced DSR MAC CE or the defined MAC CE.

11. The method according to claim 9 or 10, wherein: The priority of the defined MAC CE is lower than or equal to the priority of the DSR MAC CE; or, The priority of the enhanced DSR MAC CE is higher than or equal to the priority of the DSR MAC CE.

12. The method according to any one of claims 9 to 11, wherein: One uplink grant can carry the defined MAC CE and DSR MAC CE at the same time.

13. The method according to claim 9, wherein The first condition for triggering the BSR corresponding to the BSR MAC CE includes one or more of the following: There is a data packet in the first LCH or LCG whose remaining time is less than or equal to the threshold; Data packets in the first LCH or LCG with a remaining time less than or equal to the threshold have not been transmitted or reported; The data packets whose minimum remaining time in the first LCH or LCG is less than or equal to the threshold have not been transmitted or reported; There is no pending DSR in the first LCG; When DSR is triggered, the BSR of the corresponding LCG is also triggered; A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists.

14. The method according to claim 9 or 13, wherein: The second condition for canceling the BSR includes one or more of the following: The DSR is cancelled; The BSR is triggered based on the DSR and the DSR is canceled; A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists; A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met; The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR; The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR; The transmitted uplink grant carries the data volume of the BSR; All service data units SDU of the DSR are deleted.

15. The method according to claim 9, 13 or 14, wherein The BSR cannot trigger a scheduling request SR and / or cannot trigger a random access RA process; or, In the absence of an available uplink grant, the BSR is not allowed to trigger an SR, and / or the BSR is not allowed to trigger an RA process.

16. The method according to any one of claims 13 to 14, wherein: If the SR triggered by the DSR is cancelled, the SR triggered by the BSR is cancelled; and / or, If the first RA process triggered by the SR triggered by the DSR is stopped, the second RA process corresponding to the SR triggered by the BSR is stopped.

17. The method according to claim 16, wherein The third condition that the SR triggered by the BSR is canceled, or the second RA process corresponding to the SR triggered by the BSR is stopped includes one or more of the following: The BSR is triggered based on the DSR and the DSR is canceled, and the first RA process triggered by the DSR is canceled; The SR is triggered by a BSR, which is triggered based on the DSR, or is triggered when the first information exists; The RA process is triggered by an SR, and the SR is triggered by a BSR, and the BSR is triggered based on the DSR, or is triggered when the first information exists; The DSR is canceled, or the SR triggered by the DSR is canceled, or the RA process triggered by the SR triggered by the BSR is terminated; A third mechanism is configured or enabled, wherein the third mechanism cancels the second RA process when a cancellation condition of the first random access process is met; A first mechanism is configured or enabled, wherein the first mechanism triggers a BSR when a DSR reporting condition is met; A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met; A fourth mechanism is configured or enabled, wherein if a DSR-triggered SR is canceled, the corresponding BSR-triggered SR is invalidated. The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR; The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR; The transmitted uplink grant carries the data volume of the BSR; The transmitted uplink grant carries the DSR MAC CE; All service data units SDU of the DSR are deleted.

18. A wireless communication method, the method comprising: The terminal device sends third data, and the third data includes first data and second data, the first data is data that the remaining time meets the delay requirement, and the second data is data that the remaining time does not meet the delay requirement.

19. The method according to claim 18, wherein The third data is data corresponding to the first logical channel LCH or logical channel group LCG; or, The third data is data corresponding to the first LCH or LCG and the second LCH or LCG; The data in the first LCH or LCG includes the second data; the data in the second LCH or LCG includes the first data.

20. The method according to claim 18 or 19, wherein The second data is packaged or transmitted before the first data.

21. The method according to claim 20, wherein The transmission of the second data prior to the packaging or transmission of the first data includes one or more of the following: Packet Data Convergence Protocol PDCP or Radio Link Control RLC or MAC preferentially transmits the second data; PDCP, RLC, or MAC preferentially delivers the second data to a lower layer; PDCP, RLC or MAC preferentially packages the SDU of the second data into a PDU; MAC preferentially multiplexes the second data during the LCP process; Prioritizing multiplexing or carrying the second data by adjusting parameters of the logical channel priority LCP; Using the first LCP process, preferentially multiplexing or carrying the second data; Prioritizing multiplexing or carrying the second data on an uplink grant; Modify the LCP mapping restriction so that the first uplink grant can multiplex or carry the second data, or so that the first uplink grant can multiplex or carry the second data if there are remaining uplink resources according to the LCP process.

22. The method according to claim 21, wherein The first uplink authorization is an uplink authorization configured to be unable to carry first LCH or LCG data, and second data exists in the first LCH or LCG.

23. The method according to claim 21, wherein The parameters for adjusting the LCP include one or more of the following: Adjust the token bucket size of the first LCH or LCG; Adjusting the priority bit rate of the first LCH or LCG; Adjust the logical channel priority of the first LCH or LCG.

24. The method according to claim 21, wherein The process of using the first LCP includes one or more of the following: Prioritize multiplexing of data from the first LCH or LCG; Prioritize multiplexing of the second data in the first LCH or LCG; Allocating resources according to the data amount of the second data of the first LCH or LCG when allocating resources to the first LCH or LCG based on the LCP process; When allocating resources to the LCH or LCG based on the LCP process, first allocate resources to the first LCH or LCG or first allocate resources to the second data of the first LCH or LCG; When allocating resources to an LCH or LCG based on the LCP process, if there are remaining uplink transmission resources, perform at least one of the following: not carrying padding bits, transmitting data of the first LCH or LCG, or allocating resources to the first LCH or LCG.

25. The method according to any one of claims 20 to 24, wherein The fourth condition that the second data is packaged or transmitted before the first data includes: The second data reaches the PDCP layer, the RLC layer, or the MAC layer after the first data; The second data is not the first third amount of data to be transmitted; The total amount of the second data and the first data is greater than the total amount of data of the first LCH that can be carried by the uplink grant; The total amount of the second data and the non-sensitive data before the second data is greater than the total amount of data of the first LCH that can be carried by the uplink grant; The total amount of the second data and the first data is greater than the token bucket size corresponding to the first LCH that can be carried by the uplink grant; The total data volume of the second data and the non-sensitive data before the second data is greater than the token bucket size corresponding to the first LCH that can be carried by the uplink authorization.

26. The method according to any one of claims 18 to 25, wherein The method may further comprise one or more of the following: The terminal device adjusts the multiplexing or packetizing order of data of the first LCH or LCG and the second LCH or LCG; The terminal device adjusts the transmission of data of the first LCH or LCG and the second LCH or LCG; The data of the first LCH or LCG is multiplexed, packaged, or transmitted before the data of the second LCH or LCG.

27. The method according to claim 26, wherein Among the priorities of the LCHs or LCGs, the priority of the first LCH or LCG is higher than the priority of the second LCH or LCG; and / or, In the multiplexing or packetizing order of MAC SDU, the multiplexing or packetizing of the MAC SDU of the first LCH or LCG precedes the multiplexing or packetizing of the MAC SDU of the second LCH or LCG.

28. The method according to claim 27, wherein The priority of the first LCH or LCG is higher than the priority of the second LCH or LCG, including: The priority of the first LCH or LCG is adjusted to the highest priority; The priority of the first LCH or LCG is adjusted to the highest sub-priority among LCHs or LCGs of the same priority; The priority of the first LCH or LCG is adjusted to a higher priority among LCHs or LCGs of the same priority; The priorities of all first LCHs or LCGs are adjusted to be higher than the priorities of other LCHs or LCGs of the same priority, and all first LCHs or LCGs are sorted according to their delays; The priorities of all first LCHs or LCGs are adjusted to be the same and higher than the priorities of other LCHs or LCGs, and all first LCHs or LCGs are sorted according to their delays.

29. The method according to any one of claims 26 to 28, wherein The fifth condition for adjusting the multiplexing or packetization order of data of the first LCH or LCG and the second LCH or LCG, or adjusting the transmission of data of the first LCG and the second LCG includes one or more of the following: The priority of the first LCH or LCG is lower than the priority of other LCHs or LCGs; The priority of the first LCH or LCG is lower than the priority of the second LCH or LCG; The total amount of data of the first LCH or LCG and the second LCH or LCG is greater than the total amount of data that can be carried by the uplink grant; The second data or the data of the first LCH or LCG cannot all be multiplexed on the uplink grant; The token bucket size or the priority bit rate of the first LCH or LCG is smaller than the size of the second data of the first LCH or LCG.

30. The method according to any one of claims 18 to 29, wherein The second data includes one or more of the following: Data whose delay is less than or equal to the first threshold; Data indicating that the remaining duration of the first timer is less than or equal to the second threshold; Data in which the packet delay budget PDB or the delay budget PSDB of a data packet set is less than or equal to the third threshold; Data corresponding to the QoS flow whose delay requirement is less than or equal to the fourth threshold based on the quality of service (QoS) requirement.

31. The method according to any one of claims 18 to 30, wherein The second data includes one or more of the following: Service Data Adaptation Protocol SDAP service data unit SDU or SDAP packet data unit PDU; Packet Data Convergence Protocol PDCP SDU or PDCP PDU; Radio Link Control RLC SDU or RLC PDU; Media Access Control MAC SDU; A collection of PDUs or a data burst.

32. The method according to any one of claims 18 to 31, wherein The method further comprises: The terminal device sends second information, where the second information is used to indicate the delay and / or data volume of the sent data.

33. A wireless communication method, the method comprising: The terminal device sends third information, which includes information about the data volume of the first data and information about the data volume of the second data. The first data is data that meets the delay requirement in the remaining time, and the second data is data that does not meet the delay requirement in the remaining time.

34. The method according to claim 33, wherein The third information is statistics collected by the Packet Data Convergence Protocol (PDCP) layer and / or the Radio Link Control (RLC) layer, and / or is informed by the PDCP layer and / or the RLC layer to the Medium Access Control (MAC) layer.

35. The method according to claim 33 or 34, wherein The sixth condition that the third information includes information about the data volume of the second data and information about the data volume of the first data includes one or more of the following: The data of the one or more logical channels LCH or logical channel group LCG to be transmitted includes the second data and the first data; In a third LCH or LCG of the plurality of LCHs, an SDU of the second data arrives after an SDU of the first data, and data of the third LCH or LCG includes the second data and the first data; A priority of a first LCH or LCG among the plurality of LCHs or LCGs is lower than a priority of other LCHs or LCGs among the plurality of LCHs or LCGs, the first LCH or LCG being an LCH or LCG having second data; The priority of the first LCH or LCG is lower than the priority of a second LCH or LCG among the plurality of LCHs or LCGs, and the second LCH or LCG is a LCH or LCG having the first data; The token bucket size or the priority bit rate of the first LCH or LCG is smaller than the size of the second data in the first LCH or LCG; The token bucket size or priority bit rate of the first LCH or LCG is smaller than the amount of data to be transmitted in the first LCH or LCG; The second data of the first LCH or LCG is not the first fourth amount of data in the first LCH or LCG; The SDU of the second data of the first LCH or LCG is not the first fifth number of SDUs in the first LCH or LCG.

36. The method according to any one of claims 33 to 35, wherein The first data is all first data to be transmitted in the corresponding LCH or LCG, or, The first data is all first data to be transmitted in the corresponding LCH or LCG and arriving before the second data.

37. The method according to any one of claims 33 to 36, wherein: The third information is included in the delay status reporting DSR MAC CE or the enhanced DSR MAC CE or the defined MAC CE.

38. The method according to any one of claims 33 to 37, wherein The third information includes one or more of the following: Information on the amount of data for the LCH or LCG or terminal equipment; Information on the data volume corresponding to all SDUs or PDUs to be transmitted; Data volume information of the second data and data volume information of the first data that arrived before the second data arrived; data volume information of the second data and data volume information of the first data; The data amount information of the second data and the data amount information of the other data.

39. The method according to any one of claims 33 to 38, wherein The third information carries data amount information corresponding to the fourth LCH or LCG, and the data amount information includes one or more of the following: Information on the data volume corresponding to all SDUs or PDUs to be transmitted in the fourth LCH or LCG; Data amount information of the second data in the fourth LCH or LCG and data amount information of the first data arriving before the second data arrives; Data amount information of the second data and data amount information of the first data in the fourth LCH or LCG; The data amount information of the second data and the data amount information of other data in the fourth LCH or LCG.

40. A wireless communication method, the method comprising: The network device receives first information, where the first information includes information about first data, and the first data is data for which remaining time meets a delay requirement.

41. The method according to claim 40, wherein The first information includes information of a first logical channel LCH or a logical channel group LCG.

42. The method according to any one of claims 40 to 41, wherein The first information includes first indication information, where the first indication information is used to indicate the existence of first data.

43. The method according to claim 42, wherein The first indication information is based on LCH, LCG, or terminal device indication.

44. The method according to any one of claims 40 to 43, wherein The first information includes second indication information, and the second indication information is used to indicate the data volume of the first data.

45. The method of claim 44, wherein: The second indication information is based on LCH, LCG or terminal equipment indication.

46. ​​The method according to any one of claims 40 to 45, wherein The first information is carried in one or more of the following: Media Access Control MAC Packet Data Unit PDU; MAC sub-PDU header; MAC sub-PDU payload; Media Access Control Element MAC CE; MAC CE subheader.

47. The method of claim 46, wherein The payload of the MAC CE or MAC sub-PDU includes one of the following: an enhanced DSR MAC CE, where the enhanced DSR MAC CE is a DSR MAC CE including the first information; Buffer status reporting BSR MAC CE; Defined MAC CE.

48. The method of claim 47, wherein Factors determining whether to generate the enhanced DSR MAC CE or whether to generate the defined MAC CE include one or more of the following: Whether to generate enhanced DSR MAC CE or defined MAC CE; whether the first data exists; Whether the first data is the data that arrives first; Whether the first data arrives before the second data, the second data being data whose remaining time does not meet the latency requirement; Whether the second data is the first number of data in the LCH buffer; whether the second data is not the first second number of data; Whether the uplink grant can carry the enhanced DSR MAC CE or the defined MAC CE.

49. The method according to claim 47 or 48, wherein The priority of the defined MAC CE is lower than or equal to the priority of the DSR MAC CE; or, The priority of the enhanced DSR MAC CE is higher than or equal to the priority of the DSR MAC CE.

50. The method according to any one of claims 47 to 49, wherein One uplink grant can carry the defined MAC CE and DSR MAC CE at the same time.

51. The method of claim 47, wherein: The first condition for triggering the BSR corresponding to the BSR MAC CE includes one or more of the following: There is a data packet in the first LCH or LCG whose remaining time is less than or equal to the threshold; Data packets in the first LCH or LCG with a remaining time less than or equal to the threshold have not been transmitted or reported; The data packets whose minimum remaining time in the first LCH or LCG is less than or equal to the threshold have not been transmitted or reported; There is no pending DSR in the first LCG; When DSR is triggered, the BSR of the corresponding LCG is also triggered; A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists.

52. The method according to claim 47 or 51, wherein The second condition for canceling the BSR includes one or more of the following: The DSR is cancelled; The BSR is triggered based on the DSR and the DSR is canceled; A first mechanism is configured or enabled, where the first mechanism triggers a BSR when a DSR reporting condition is met, or triggers a BSR when first information exists; A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met; The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR; The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR; The transmitted uplink grant carries the data volume of the BSR; All service data units SDU of the DSR are deleted.

53. The method of claim 47, 51 or 52, wherein: The BSR cannot trigger a scheduling request SR and / or cannot trigger a random access RA process; or, In the absence of an available uplink grant, the BSR is not allowed to trigger an SR, and / or the BSR is not allowed to trigger an RA process.

54. The method according to any one of claims 51 to 52, wherein: If the SR triggered by the DSR is cancelled, the SR triggered by the BSR is cancelled; and / or, If the first RA process triggered by the SR triggered by the DSR is stopped, the second RA process corresponding to the SR triggered by the BSR is stopped.

55. The method of claim 54, wherein The third condition that the SR triggered by the BSR is canceled, or the second RA process corresponding to the SR triggered by the BSR is stopped includes one or more of the following: The BSR is triggered based on the DSR and the DSR is canceled, and the first RA process triggered by the DSR is canceled; The SR is triggered by a BSR, which is triggered based on the DSR, or is triggered when the first information exists; The RA process is triggered by an SR, and the SR is triggered by a BSR, and the BSR is triggered based on the DSR, or is triggered when the first information exists; The DSR is canceled, or the SR triggered by the DSR is canceled, or the RA process triggered by the SR triggered by the BSR is terminated; A third mechanism is configured or enabled, wherein the third mechanism cancels the second RA process when a cancellation condition of the first random access process is met; A first mechanism is configured or enabled, wherein the first mechanism triggers a BSR when a DSR reporting condition is met; A second mechanism is configured or enabled, wherein the second mechanism cancels the BSR when the DSR cancellation condition is met; A fourth mechanism is configured or enabled, wherein if a DSR-triggered SR is canceled, the corresponding BSR-triggered SR is invalidated. The transmitted uplink grant carries the DSR MAC CE of the DSR and the BSR MAC CE of the BSR; The transmitted uplink grant carries the data volume of the DSR and the data volume of the BSR; The transmitted uplink grant carries the data volume of the BSR; The transmitted uplink grant carries the DSR MAC CE; All service data units SDU of the DSR are deleted.

56. A wireless communication method, the method comprising: The network device receives third data, where the third data includes first data and second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

57. The method of claim 56, wherein: The third data is data corresponding to the first logical channel LCH or logical channel group LCG; or, The third data is data corresponding to the first LCH or LCG and the second LCH or LCG; The data in the first LCH or LCG includes the second data; the data in the second LCH or LCG includes the first data.

58. The method according to claim 56 or 57, wherein The second data is transmitted before the first data.

59. The method according to any one of claims 56 to 58, wherein The second data includes one or more of the following: Data whose delay is less than or equal to the first threshold; Data indicating that the remaining duration of the first timer is less than or equal to the second threshold; Data in which the packet delay budget PDB or the delay budget PSDB of a data packet set is less than or equal to the third threshold; Data corresponding to the QoS flow whose delay requirement is less than or equal to the fourth threshold based on the quality of service (QoS) requirement.

60. The method according to any one of claims 56 to 59, wherein The second data includes one or more of the following: Service Data Adaptation Protocol SDAP service data unit SDU or SDAP packet data unit PDU; Packet Data Convergence Protocol PDCP SDU or PDCP PDU; Radio Link Control RLC SDU or RLC PDU; Media Access Control MAC SDU; A collection of PDUs or a data burst.

61. The method according to any one of claims 56 to 60, wherein The method further comprises: The network device receives second information, where the second information is used to indicate a delay and / or a data volume of sent data.

62. A wireless communication method, the method comprising: The network device receives third information, which includes information about the data volume of first data and information about the data volume of second data. The first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

63. The method of claim 62, wherein: The sixth condition that the third information includes information about the data volume of the second data and information about the data volume of the first data includes one or more of the following: The data of the one or more logical channels LCH or logical channel group LCG to be transmitted includes the second data and the first data; In a third LCH or LCG of the plurality of LCHs, an SDU of the second data arrives after an SDU of the first data, and data of the third LCH or LCG includes the second data and the first data; A priority of a first LCH or LCG among the plurality of LCHs or LCGs is lower than a priority of other LCHs or LCGs among the plurality of LCHs or LCGs, the first LCH or LCG being an LCH or LCG having second data; The priority of the first LCH or LCG is lower than the priority of a second LCH or LCG among the plurality of LCHs or LCGs, and the second LCH or LCG is a LCH or LCG having the first data; The token bucket size or the priority bit rate of the first LCH or LCG is smaller than the size of the second data in the first LCH or LCG; The token bucket size or priority bit rate of the first LCH or LCG is smaller than the amount of data to be transmitted in the first LCH or LCG; The second data of the first LCH or LCG is not the first fourth amount of data in the first LCH or LCG; The SDU of the second data of the first LCH or LCG is not the first fifth number of SDUs in the first LCH or LCG.

64. The method according to any one of claims 62 to 63, wherein The first data is all first data to be transmitted in the corresponding LCH or LCG, or, The first data is all first data to be transmitted in the corresponding LCH or LCG and arriving before the second data.

65. The method according to any one of claims 62 to 64, wherein The third information is included in the DSR MAC CE or the enhanced DSR MAC CE or the defined MAC CE.

66. The method according to any one of claims 62 to 65, wherein The third information includes one or more of the following: Information on the amount of data for the LCH or LCG or terminal equipment; Information on the data volume corresponding to all SDUs or PDUs to be transmitted; Data volume information of the second data and data volume information of the first data that arrived before the second data arrived; data volume information of the second data and data volume information of the first data; The data amount information of the second data and the data amount information of the other data.

67. The method according to any one of claims 62 to 66, wherein The third information carries data amount information corresponding to the fourth LCH or LCG, and the data amount information includes one or more of the following: Information on the data volume corresponding to all SDUs or PDUs to be transmitted in the fourth LCH or LCG; Data amount information of the second data in the fourth LCH or LCG and data amount information of the first data arriving before the second data arrives; Data amount information of the second data and data amount information of the first data in the fourth LCH or LCG; The data amount information of the second data and the data amount information of other data in the fourth LCH or LCG.

68. A terminal device comprising: The first communication unit is configured to send first information, where the first information includes information about first data, and the first data is data whose remaining time meets the delay requirement.

69. A terminal device comprising: The second communication unit is configured to send third data, where the third data includes first data and second data, the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

70. A terminal device comprising: The third communication unit is configured to send third information, where the third information includes information about the data volume of the first data and information about the data volume of the second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

71. A network device comprising: The fourth communication unit is configured to receive first information, where the first information includes information about first data, and the first data is data whose remaining time meets the delay requirement.

72. A network device comprising: The fifth communication unit is configured to receive third data, where the third data includes first data and second data, where the first data is data whose remaining time meets the delay requirement, and the second data is data whose remaining time does not meet the delay requirement.

73. A network device comprising: The sixth communication unit is configured to receive third information, wherein the third information includes information about the data volume of the first data and information about the data volume of the second data, the first data is data that meets the delay requirement in the remaining time, and the second data is data that does not meet the delay requirement in the remaining time.

74. A communication device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and to execute the method according to any one of claims 1 to 39, or to execute the method according to any one of claims 40 to 67.

75. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 39, or executes the method according to any one of claims 40 to 67.

76. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 39, or the method according to any one of claims 40 to 67.

77. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method according to any one of claims 1 to 39, or the method according to any one of claims 40 to 67.

78. A computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 39, or the method according to any one of claims 40 to 67.

Images