Wireless communication method and device

Abstract

The invention discloses a wireless communication method and device. The first node sends a first MAC PDU, wherein the first MAC PDU comprises a first delay state report; cancelling at least one cache status report as a response to the first MAC PDU being sent; wherein the first delay status report comprises a first uplink data volume, the first uplink data volume is not less than the uplink data volume when a first cache status report is triggered, and the first cache status report is one of the at least one cache status report. According to the invention, by canceling the cache state report, signaling can be saved, and UE reporting can be optimized.

Description

Technical Field

[0001] The present application relates to methods and devices in wireless communication systems, and more particularly to methods and devices supporting delay-sensitive service transmission in wireless communication. Background Art

[0002] In response to the rapid development of real-time services such as XR (eXtended Reality), 3GPP (3rd Generation Partner Project) RAN1 (Radio Access Network 1) launched SI (Study Item) in Release 17 for "Study on XR Evaluations for NR". The study believes that XR is an important use case and service for Release 18 and subsequent versions. XR refers to various types of augmented, virtual and mixed environments, which perform human-machine communication with the help of handheld and wearable end-user equipment (UE). Since many XR use cases have strict packet delay budgets (PDB), they bring a series of challenges to NR (New Radio). Summary of the invention

[0003] The inventors have found through research that in the prior art, the UE informs the network of the amount of data waiting to be uploaded by reporting buffer status information. Since the network does not have the maximum delay information for uplink data to wait, if the network does not schedule the uplink data for transmission in time, the uplink data will reach the maximum delay and be discarded, thereby affecting the service quality. For delay-sensitive services, how to report the delay information of uplink data waiting to be transmitted and how to coordinate the uplink data delay information with the uplink data buffer information to improve the uplink transmission efficiency is a problem that needs to be solved.

[0004] In response to the above problems, the present application discloses a solution. Although the present application is for delay-sensitive business scenarios, including but not limited to typical XR, URLLC (Ultra Reliable and Low Latency Communication), Internet of Vehicles, MBS (Multicast and Broadcast Services), etc., the present application can also be used for other types of business scenarios, such as eMBB (Enhance Mobile Broadband), IoT (Internet of Things), NTN (non-terrestrial networks), shared spectrum (shared spectrum) and other scenarios, and similar technical effects can be achieved. In addition, the use of a unified solution for different scenarios (including but not limited to XR, URLLC, Internet of Vehicles, MBS, eMBB, IoT, NTN, shared spectrum) can also help reduce hardware complexity and cost, or improve network performance. In the absence of conflict, the embodiments and features in the first node of the present application can be applied to any other node, and vice versa. In the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily. In particular, the interpretation of the terminology, nouns, functions, and variables in this application (unless otherwise specified) can refer to the definitions in the 3GPP specification protocols TS38 series and TS37 series.

[0005] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0006] Sending a first MAC PDU, wherein the first MAC PDU includes a first delay status report;

[0007] canceling at least one buffer status report in response to the first MAC PDU being sent;

[0008] The first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first buffer status report is triggered, and the first buffer status report is a buffer status report among the at least one buffer status report.

[0009] As an embodiment, the problem to be solved by the present application includes: how to collaboratively process delay status reports and cache status reports.

[0010] As an embodiment, the above method cancels at least one cache status report by sending a first delay status report.

[0011] As an embodiment, the above method cancels the buffer status report when the uplink data amount is less than the first uplink data amount when triggered.

[0012] As an embodiment, the above method can reduce the sending of buffer status reports MAC (Medium Access Control) CE (Control Element) by canceling some buffer status reports, thereby saving air interface signaling.

[0013] As an embodiment, the above method processes the delay status report and the buffer status report in a coordinated manner, which can optimize UE reporting.

[0014] As an embodiment, the above method can save UE power consumption.

[0015] As an embodiment, the at least one cache status report is triggered and not cancelled.

[0016] As an embodiment, the at least one cache status report is triggered before the first MAC PDU (Protocol Data Unit) is assembled.

[0017] As an embodiment, the first delay status report is a MAC CE.

[0018] For ease of understanding, the following explanations are given: the first delay status report in the present application is a MAC CE, which can be replaced by the first delay status report MAC CE; unless otherwise specified, the delay status report in the present application is a signal or indication.

[0019] As an embodiment, each cache status report of the at least one cache status report is a signal or an indication.

[0020] As an embodiment, when a buffer status report is triggered and not cancelled, if there are UL-SCH (Uplink-Shared Channel) resources available for a new transmission, a buffer status report MAC CE is generated.

[0021] For ease of understanding, the following explanations are given: the cache status report in this application is a signal or indication, and the cache status report MACCE is a MAC CE.

[0022] According to one aspect of the present application, it includes:

[0023] The first delay status report indicates a first remaining time value, the first remaining time value being dependent on a value of a PDCP discard timer associated with the uplink data at the first time;

[0024] The first time corresponds to the time of the first symbol sent by the first PUSCH, and the first PUSCH carries the first delay status report.

[0025] According to one aspect of the present application, it includes:

[0026] The first uplink data amount indicates the amount of uplink data whose remaining time value is not greater than the first remaining time value.

[0027] According to one aspect of the present application, it includes:

[0028] receiving a first message, wherein the first message configures a first remaining time threshold for a first logical channel group;

[0029] When the remaining time value of the first PDU is not greater than the first remaining time threshold, triggering a delay status report;

[0030] Among them, the first uplink PDU belongs to the first logical channel group; the delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to generate the first delay status report.

[0031] As an embodiment, the at least one delay status report includes all delay status reports that are triggered and not canceled before the first MAC PDU is assembled.

[0032] As an embodiment, after the first MAC PDU is sent, the at least one delay status report is cancelled.

[0033] As a sub-embodiment of the above embodiment, the above method can reduce the delay in sending the status report MAC CE and save air interface signaling.

[0034] As an embodiment, after the first MAC PDU is sent, some delay status reports in the at least one delay status report are not cancelled.

[0035] According to one aspect of the present application, it includes:

[0036] The at least one buffer status report includes a buffer status report that is triggered and not canceled before the first buffer status report.

[0037] As an embodiment, a buffer status report that is triggered and not canceled before the first buffer status report has an uplink data volume that is greater than the first uplink data volume when it is triggered.

[0038] As an embodiment, the uplink data volume of a buffer status report that is triggered and not canceled before the first buffer status report when it is triggered is not used to determine whether to cancel the buffer status report.

[0039] As an embodiment, the above method can further cancel invalid buffer status reports, reduce buffer status report MAC CE sending, and save air interface signaling.

[0040] According to one aspect of the present application, it includes:

[0041] At least part of the at least one buffer status report is triggered after the one delay status report triggered by the first PDU.

[0042] As an embodiment, the delay status report triggered by the first PDU is the last delayed status report triggered among the at least one delay status report.

[0043] As an embodiment, the event that triggers a delay status report is different from the event that triggers a buffer status report.

[0044] As an embodiment, the time when the at least one delay status report is triggered is unrelated to the time when the at least one cache status report is triggered.

[0045] As an embodiment, part of the cache status reports in the at least one cache status report is triggered before the delay status report triggered by the first PDU, and the other remaining part of the cache status report in the at least one cache status report is triggered after the delay status report triggered by the first PDU.

[0046] According to one aspect of the present application, it includes:

[0047] After the first MAC PDU is sent, a delayed status report triggered by the second PDU is not cancelled;

[0048] The first uplink data volume does not include the data volume of the second PDU.

[0049] As an embodiment, the above method is different from the buffer status report process: after the buffer status report MAC CE is sent, all triggered buffer status reports are cancelled; and after the delay status report MAC CE is sent, some delay status reports can be retained and not cancelled.

[0050] As an embodiment, the above method can generate a new delay status report MAC CE to report the data volume information that has not been reported by retaining the delay status report when there are UL-SCH resources.

[0051] As an embodiment, the above method can effectively support the reporting of data volume of delay-sensitive services.

[0052] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0053] receiving a first MAC PDU, the first MAC PDU comprising a first delay status report;

[0054] Among them, the first MAC PDU is sent to cancel at least one cache status report; the first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report in the at least one cache status report.

[0055] According to one aspect of the present application, it includes:

[0056] The first delay status report indicates a first remaining time value, the first remaining time value being dependent on a value of a PDCP discard timer associated with the uplink data at the first time;

[0057] The first time corresponds to the time of the first symbol sent by the first PUSCH, and the first PUSCH carries the first delay status report.

[0058] According to one aspect of the present application, it includes:

[0059] The first uplink data amount indicates the amount of uplink data whose remaining time value is not greater than the first remaining time value.

[0060] According to one aspect of the present application, it includes:

[0061] Sending a first message, wherein the first message configures a first remaining time threshold for a first logical channel group;

[0062] Wherein, when the remaining time value of the first PDU is not greater than the first remaining time threshold, a delay status report is triggered; the first uplink PDU belongs to the first logical channel group; the one delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to generate the first delay status report

[0063] According to one aspect of the present application, it includes:

[0064] The at least one buffer status report includes a buffer status report that is triggered and not canceled before the first buffer status report.

[0065] According to one aspect of the present application, it includes:

[0066] At least part of the at least one buffer status report is triggered after the one delay status report triggered by the first PDU.

[0067] According to one aspect of the present application, it includes:

[0068] After the first MAC PDU is sent, a delayed status report triggered by the second PDU is not cancelled;

[0069] The first uplink data volume does not include the data volume of the second PDU.

[0070] The present application discloses a first node used for wireless communication, characterized in that it includes:

[0071] A first transceiver sends a first MAC PDU, wherein the first MAC PDU includes a first delay status report;

[0072] a first processor, in response to the first MAC PDU being sent, canceling at least one buffer status report;

[0073] The first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first buffer status report is triggered, and the first buffer status report is a buffer status report among the at least one buffer status report.

[0074] The present application discloses a second node used for wireless communication, characterized in that it includes:

[0075] A second transceiver receives a first MAC PDU, wherein the first MAC PDU includes a first delay status report;

[0076] Among them, the first MAC PDU is sent to cancel at least one cache status report; the first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report in the at least one cache status report. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0078] Figure 1 An example of a transmission flow chart of a first node according to an embodiment of the present application is provided;

[0079] Figure 2 A schematic diagram illustrating a network architecture according to an embodiment of the present application is illustrated;

[0080] Figure 3 A schematic diagram illustrating a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0081] Figure 4 A hardware module schematic diagram of a communication device according to an embodiment of the present application is illustrated;

[0082] Figure 5 An example of a wireless signal transmission flow chart according to an embodiment of the present application is provided;

[0083] Figure 6 An example of a first delay status report, a first uplink data volume and a first remaining time according to an embodiment of the present application is provided;

[0084] Figure 7 An example of at least one delay status report according to an embodiment of the present application, a schematic diagram of the time relationship between a first time and a first PUSCH;

[0085] Figure 8 A schematic diagram illustrating a first cache status report and at least one cache status report according to an embodiment of the present application is illustrated;

[0086] Fig. 9 A schematic diagram illustrating a delay status report and at least one buffer status report triggered by a first PDU according to an embodiment of the present application is illustrated;

[0087] Fig.10 An example of a relationship between a delay status report triggered by a first PDU, a delay status report triggered by a second PDU and a first PUSCH according to an embodiment of the present application is provided;

[0088] Fig.11 An example structural diagram of a processing device in a first node according to an embodiment of the present application is shown;

[0089] Fig.12 The structural diagram of the processing device in the second node according to one embodiment of the present application is illustrated. DETAILED DESCRIPTION

[0090] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, in the absence of conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other.

[0091] Example 1

[0092] Embodiment 1 illustrates a transmission flow chart of a first node according to an embodiment of the present application, as shown in the attached Figure 1 shown.

[0093] In Example 1, the first node 100 sends a first MAC PDU in step 101, and the first MAC PDU includes a first delay status report; in step 102, as a response to the first MAC PDU being sent, at least one cache status report is canceled; wherein the first delay status report indicates a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report among the at least one cache status report.

[0094] As an embodiment, a first MAC PDU is sent, wherein the first MAC PDU includes a first delay status report.

[0095] As an embodiment, the first delay status report is a MAC sublayer control information unit.

[0096] As an embodiment, the first delay status report is a MAC CE.

[0097] As an embodiment, the first delay status report is a delay status report MAC CE.

[0098] As an embodiment, the first delay status report is a DSR (Dealy Status Report) MAC CE.

[0099] As an embodiment, the first delay status report is an eBSR (enhanced Buffer Status Report) MAC CE.

[0100] As an embodiment, the first MAC PDU includes a MAC subPDU (sub-PDU), and the one MACsubPDU includes the first delay status report and a subheader of the first delay status report.

[0101] As an embodiment, the first MAC PDU does not include a delay status report MAC CE other than the first delay status report.

[0102] As an embodiment, the first MAC PDU includes a cache status report MAC CE.

[0103] As an embodiment, the first MAC PDU includes a second uplink data volume.

[0104] As a sub-embodiment of the above embodiment, the second uplink data amount is greater than the first uplink data amount.

[0105] As a sub-embodiment of the above embodiment, the second uplink data volume is the uplink data volume when the last buffer status report is triggered before the first MAC PDU is assembled.

[0106] As a sub-embodiment of the above embodiment, the second uplink data amount is the difference between the uplink data amount when the last buffer status report is triggered before the first MAC PDU is assembled and the first uplink data amount.

[0107] As an embodiment, the first MAC PDU does not include a cache status report MAC CE.

[0108] As a sub-embodiment of the above embodiment, the amount of uplink data when the last buffer status report is triggered before the first MAC PDU assembly is not greater than the first uplink data amount.

[0109] As a sub-embodiment of the above embodiment, the uplink transmission resources indicated by the uplink grant are insufficient to include a buffer status report MAC CE.

[0110] As an embodiment, the priority of the delay status report MAC CE is higher than the priority of the buffer status report MAC CE.

[0111] As an embodiment, the buffer status report is one of Long BSR (long buffer status report), Extended Long BSR (extended long buffer status report), Short BSR (short buffer status report) or Extended Short BSR (extended short buffer status report).

[0112] As an embodiment, the cache status report is one of Long BSR, Long Truncated BSR, Extended Long BSR, Extended Long Truncated BSR, Short BSR, Short Truncated BSR, Extended Short BSR or Extended Short Truncated BSR.

[0113] As an embodiment, in response to the first MAC PDU being sent, at least one cache status report is canceled.

[0114] As an embodiment, a cache status report is a signal.

[0115] As an embodiment, a cache status report is an indication.

[0116] As an embodiment, a cache status report is indicated by 1 bit.

[0117] As an embodiment, before the first MAC PDU is sent, the at least one buffer status report is triggered and not cancelled.

[0118] As an embodiment, when the uplink data of a logical channel belonging to an LCG (Logical Channel Group) is available to a MAC entity, and the priority of the logical channel to which the uplink data belongs is higher than the priority of any other logical channel, a cache status report is triggered; wherein any other logical channel belongs to any other LCG and contains available uplink data.

[0119] As an embodiment, when uplink data of a logical channel belonging to an LCG is available to a MAC entity and any logical channel included in the LCG has no available uplink data, a buffer status report is triggered.

[0120] As a sub-embodiment of the above two embodiments, the buffer status report is a regular buffer status report (regular BSR).

[0121] As an embodiment, when UL (Uplink) resources are allocated and the number of padding bits is equal to or greater than the size of the buffer status report MAC CE plus its subheader, a buffer status report is triggered.

[0122] As a sub-embodiment of the above embodiment, the buffer status report is a padding buffer status report (padding BSR).

[0123] As an embodiment, when a retxBSR-Timer (BSR retransmission timer) expires and at least one logical channel belonging to an LCG contains uplink data, a buffer status report is triggered.

[0124] As a sub-embodiment of the above embodiment, the buffer status report is a regular buffer status report (regular BSR).

[0125] As an embodiment, when the periodicBSR-Timer (BSR periodic timer) expires, a buffer status report is triggered.

[0126] As a sub-embodiment of the above embodiment, the buffer status report is a periodic buffer status report (periodic BSR).

[0127] As an embodiment, the sending of the first MAC PDU includes: the first MAC PDU is delivered to a protocol layer below MAC of the first node.

[0128] As an embodiment, the sending of the first MAC PDU includes: a first PUSCH (Physical Uplink Shared Channel) is sent, and the first PUSCH carries the first MAC PDU.

[0129] As an embodiment, the first delay status report indicates a first uplink data volume.

[0130] As an embodiment, the first delay status report implicitly indicates the first uplink data amount.

[0131] As an embodiment, the first uplink data amount means: a first buffer size (buffer size).

[0132] As an embodiment, the first delay status report includes a cache size index (index), and the first uplink data amount is indicated by the value of the cache size index.

[0133] As a sub-embodiment of the above embodiment, the first uplink data amount is obtained by looking up a table according to the value of the cache size index.

[0134] As an embodiment, the first uplink data volume indicates a data volume value.

[0135] As an embodiment, the first uplink data volume indicates a data volume interval.

[0136] As a sub-embodiment of the above embodiment, the first uplink data amount is not greater than a maximum data amount value indicated by the value of the cache size index included in the first delay status report.

[0137] As a sub-embodiment of the above embodiment, the first uplink data amount is greater than the minimum data amount value indicated by the value of the buffer size index included in the first delay status report.

[0138] As a sub-embodiment of the above embodiment, the first uplink data amount is not less than the data amount value indicated by the value of the cache size index included in the first delay status report.

[0139] As an embodiment, the first uplink data amount is determined by a MAC entity of the first node.

[0140] As an embodiment, the first uplink data volume is determined according to a data volume calculation process at a PDCP (Packet Data Convergence Protocol) sublayer and an RLC (Radio Link Control) sublayer of the first node.

[0141] As an embodiment, the first uplink data volume includes at least a portion of the available uplink data volume.

[0142] As an embodiment, the first uplink data amount is not less than the uplink data amount when the first cache status report is triggered.

[0143] As an embodiment, the first uplink data volume is greater than the uplink data volume when the first cache status report is triggered.

[0144] As an embodiment, the first uplink data amount is equal to the uplink data amount when the first buffer status report is triggered.

[0145] As an embodiment, the first cache status report is a cache status report among the at least one cache status report.

[0146] As an embodiment, the first cache status report is a cache status report that is triggered earliest among the at least one cache status report.

[0147] As a sub-embodiment of the above embodiment, the data volume of the buffer status reports triggered and not canceled after the first buffer status report included in the at least one buffer status report is smaller than the first uplink data volume when being triggered.

[0148] As an embodiment, the first cache status report is a cache status report that is triggered latest among the at least one cache status report.

[0149] As an embodiment, the amount of uplink data when the first cache status report is triggered includes the amount of available uplink data cached in the PDCP sublayer and / or RLC sublayer of the first node.

[0150] As an embodiment, when the first buffer status report is triggered, the uplink data cached in the PDCP sublayer includes a PDCP SDU (Service Data Unit) that has not yet been composed into a PDCP PDU.

[0151] As an embodiment, when the first buffer status report is triggered, the uplink data buffered in the PDCP sublayer includes a PDCP PDU that has not yet been delivered to the protocol layers below the PDCP.

[0152] As an embodiment, when the first buffer status report is triggered, the uplink data cached in the PDCP sublayer includes a PDCP control PDU.

[0153] As an embodiment, the uplink data cached in the PDCP sublayer when the first buffer status report is triggered includes the PDCP SDU belonging to AM (Acknowledged Mode) DRB (Data Radio Bearer) to be retransmitted.

[0154] As an embodiment, when the first buffer status report is triggered, the uplink data buffered in the PDCP sublayer includes the PDCP data PDU belonging to the AM DRB to be retransmitted.

[0155] As an embodiment, the uplink data cached in the RLC sublayer when the first buffer status report is triggered includes RLC SDU and RLC SDU segments that have not yet included RLC data-only PDU.

[0156] As an embodiment, the uplink data cached in the RLC sublayer when the first cache status report is triggered includes RLC data PDU waiting for initial transmission.

[0157] As an embodiment, when the first buffer status report is triggered, the uplink data cached in the RLC sublayer includes RLC data PDU waiting for retransmission.

[0158] As an embodiment, the calculation of the amount of available uplink data may refer to 3GPP specifications TS38.322 and TS38.323; the data amount is expressed in bytes.

[0159] Example 2

[0160] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2A diagram illustrating a network architecture 200 for NR 5G, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) systems. The NR 5G, LTE or LTE-A network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet switching services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit switching services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., a backhaul link). The XnAP protocol of the Xn interface is used to transmit control plane messages of the wireless network, and the user plane protocol of the Xn interface is used to transmit user plane data. gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (Transmission Reception Point, a sending and receiving node) or some other suitable term. In a NTN (Non Terrestrial Network, a non-terrestrial / satellite network) network, gNB 203 may be a satellite, an aircraft, or a ground base station relayed by a satellite. gNB203 provides an access point to 5GC / EPC210 for UE201.Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, vehicle-mounted devices, vehicle-mounted communication units, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and PS (Packet Switching) streaming services.

[0161] As an embodiment, the UE201 corresponds to the first node in this application.

[0162] As an embodiment, the gNB203 corresponds to the second node in this application.

[0163] As an embodiment, the UE201 is a user equipment.

[0164] As an embodiment, the UE 201 is a layer 2U2N remote UE.

[0165] As an embodiment, the UE201 is a V2X terminal.

[0166] As an embodiment, the UE 201 is a relay node.

[0167] As an embodiment, the gNB203 is a macro cell base station.

[0168] As an embodiment, the gNB203 is a micro cell base station.

[0169] As an embodiment, the gNB203 is a pico cell base station.

[0170] As an embodiment, the gNB203 is a home base station (Femtocell).

[0171] As an embodiment, the gNB203 is a base station device that supports large delay difference.

[0172] As an embodiment, the gNB203 is a flying platform device.

[0173] As an embodiment, the gNB203 is a satellite device.

[0174] As an embodiment, the gNB203 is a testing device (e.g., a transceiver that simulates some functions of a base station, a signaling tester).

[0175] As an embodiment, the wireless link from the UE201 to the gNB203 is an uplink, and the uplink is used to perform uplink transmission.

[0176] As an embodiment, the wireless link from the gNB203 to the UE201 is a downlink, and the downlink is used to perform downlink transmission.

[0177] As an embodiment, the UE201 and the gNB203 are connected via a Uu air interface.

[0178] Example 3

[0179] Embodiment 3 illustrates a schematic diagram of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application, as shown in the attached figure. Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 of the UE and gNB is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY 301 in this article. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the UE and the gNB through PHY 301. The L2 layer 305 includes the MAC (Medium Access Control) sublayer 302, the RLC (Radio Link Control) sublayer 303, and the PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the gNB on the network side. The PDCP sublayer 304 provides data encryption and integrity protection. The PDCP sublayer 304 also provides support for inter-zone mobility of UEs between gNBs. The RLC sublayer 303 provides segmentation and reassembly of data packets, and retransmits lost data packets through ARQ (Automatic Repeat Request). The RLC sublayer 303 also provides duplicate data packet detection and protocol error detection. The MAC sublayer 302 provides mapping between logical channels and transport channels and multiplexing of logical channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between UEs. The MAC sublayer 302 is also responsible for HARQ (Hybrid Automatic Repeat Request) operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the gNB and the UE. The wireless protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The wireless protocol architecture in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce wireless transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services.The wireless protocol architecture of the UE in the user plane 350 may include, at the L2 layer, a SDAP sublayer 356, a PDCP sublayer 354, a portion of or all of the protocol sublayers of the RLC sublayer 353 and the MAC sublayer 352. Although not shown, the UE may also have several upper layers above the L2 layer 355, including a network layer (e.g., an IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

[0180] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0181] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0182] As an embodiment, the first MAC PDU in the present application is generated by the MAC302 or the MAC352.

[0183] As an embodiment, the first delay status report in the present application is generated by the MAC302 or the MAC352.

[0184] As an embodiment, the at least one cache status report in the present application is generated by the MAC302 or the MAC352.

[0185] As an embodiment, the at least one delay status report in the present application is generated by the MAC302 or the MAC352.

[0186] As an embodiment, the first message in the present application is generated in the RRC306.

[0187] As an embodiment, the L2 layer 305 belongs to a higher layer.

[0188] As an embodiment, the RRC sublayer 306 in the L3 layer belongs to a higher layer.

[0189] As an example, Figure 3 The entities of multiple sublayers of the control plane in the vertical direction form a signaling radio bearer (SRB).

[0190] As an example, Figure 3 The entities of multiple sublayers of the user plane in the vertical direction form a data radio bearer (DRB).

[0191] As an example, Figure 3 The entities of multiple sublayers of the user plane in the vertical direction form an MRB.

[0192] As an embodiment, the lower layer part of the radio bearer constitutes an RLC bearer; wherein the lower layer of the radio bearer includes entities and logical channels of the RLC sublayer.

[0193] As an embodiment, the RLC channel is a SAP (Service Access Point) between the RLC303 and the PDCP304.

[0194] As an embodiment, the RLC channel is a SAP between the RLC353 and the PDCP354.

[0195] As an embodiment, the logical channel is the SAP between the RLC303 and the MAC302.

[0196] As an embodiment, the logical channel is the SAP between the RLC353 and the MAC352.

[0197] As an embodiment, the transport channel is the SAP between the MAC 302 and the PHY 301 .

[0198] As an embodiment, the transmission channel is SAP between the MAC352 and the PHY351.

[0199] As an embodiment, data units of layer 3 and above protocol layers are mapped to data radio bearers in the user plane.

[0200] Example 4

[0201] Embodiment 4 illustrates a hardware module schematic diagram of a communication device according to an embodiment of the present application, as shown in the attached Figure 4 shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0202] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0203] The second communication device 410 includes a controller / processor 475, a memory 476, a data source 477, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter / receiver 418 and an antenna 420.

[0204] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the upper layer data packets from the core network or the upper layer data packets from the data source 477 are provided to the controller / processor 475. The core network and the data source 477 represent all the protocol layers above the L2 layer. The controller / processor 475 implements the functionality of the L2 layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for the retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0205] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover higher layer data packets from the second communication device 410. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing.

[0206] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, the upper layer data packets are provided to the controller / processor 459 using the data source 467. The data source 467 represents all the protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0207] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the reception functions at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the first communication device 450. The upper layer data packets from the controller / processor 475 may be provided to the core network or all protocol layers above the L2 layer, and various control signals may also be provided to the core network or L3 for L3 processing.

[0208] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least: sends a first MAC PDU, the first MAC PDU includes a first delay status report; as a response to the first MAC PDU being sent, cancels at least one cache status report; wherein the first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report among the at least one cache status report.

[0209] As an embodiment, the first communication device 450 apparatus includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: sending a first MAC PDU, wherein the first MAC PDU includes a first delay status report; as a response to the first MAC PDU being sent, canceling at least one cache status report; wherein the first delay status report includes a first uplink data volume, wherein the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is one cache status report among the at least one cache status report.

[0210] As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the second communication device 410 apparatus at least: receives a first MAC PDU, the first MAC PDU includes a first delay status report; wherein the first MAC PDU is sent to cancel at least one cache status report; the first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report among the at least one cache status report.

[0211] As an embodiment, the second communication device 410 apparatus includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: receiving a first MAC PDU, wherein the first MAC PDU includes a first delay status report; wherein the first MAC PDU is sent to cancel at least one cache status report; the first delay status report includes a first uplink data volume, wherein the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is one of the at least one cache status reports.

[0212] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0213] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0214] As an embodiment, the first communication device 450 is a UE.

[0215] As an embodiment, the first communication device 450 is a layer 2U2N remote UE.

[0216] As an embodiment, the first communication device 450 is a layer 3 relay node.

[0217] As an embodiment, the second communication device 410 is a base station.

[0218] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468 or the controller / processor 459 is used to send the first MAC PDU in the present application.

[0219] As an embodiment, at least one of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470 or the controller / processor 475 is used to receive the first MAC PDU in the present application.

[0220] As an embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller / processor 475 is used to send the first message I in the present application.

[0221] As an embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna reception processor 458, the reception processor 456 or the controller / processor 459 is used to receive the first message in the present application.

[0222] Example 5

[0223] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 As shown in the attached Figure 5 In the example, the first node N51 and the second node N52 communicate via an air interface. It should be noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0224] for First node N51 , receiving a first message in step S511; triggering a delay status report in step S512 by a first PDU; sending a first MAC PDU in step S513; and canceling at least one cache status report in step S514.

[0225] for Second node N52 , sending a first message in step S521, and receiving a first MAC PDU in step S522.

[0226] In Example 5, a first message is received, and the first message configures a first remaining time threshold for a first logical channel group; when the remaining time value of a first PDU is not greater than the first remaining time threshold, a delay status report is triggered; wherein the first uplink PDU belongs to the first logical channel group; the one delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to generate the first delay status report; a first MAC PDU is sent, and the first MAC PDU includes a first delay status report; as a response to the first MAC PDU being sent, at least one cache status report is canceled; wherein the first delay status report indicates a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report among the at least one cache status report.

[0227] As an embodiment, the second node N52 is a base station maintaining a service cell of the first node N51.

[0228] As an embodiment, the second node N52 is a Transmit / Receive Point (TRP) of a service cell of the first node N51.

[0229] As an embodiment, the second node N52 is a maintaining base station of a master cell group (MCG) of the first node N51.

[0230] As an embodiment, the second node N52 is a base station maintaining a secondary cell group (SCG) of the first node N51.

[0231] As an embodiment, a first message is received, wherein the first message configures a first remaining time threshold for a first logical channel group.

[0232] As an embodiment, the first message is a high-level message.

[0233] As an embodiment, the first message is an RRC (Radio Resource Control) message.

[0234] As an embodiment, the first message is all or part of an IE (Information Element) in an RRC signaling.

[0235] As an embodiment, the first message is all or part of a field in an IE in an RRC signaling.

[0236] As an embodiment, the first logical channel group includes at least one logical channel.

[0237] As an embodiment, the first remaining time threshold is applied to the PDU of any logical channel included in the first logical channel group.

[0238] As an embodiment, the first remaining time threshold is a remaining time threshold of uplink data configured to trigger a delay status report of the first logical channel group.

[0239] As an embodiment, the first remaining time threshold is the value of the parameter remainingTimeThreshold (remaining time threshold).

[0240] As an embodiment, when the remaining time value of the first PDU is not greater than the first remaining time threshold, a delay status report is triggered.

[0241] As an embodiment, when the remaining time value of the first PDU is less than the first remaining time threshold, a delay status report is triggered.

[0242] As an embodiment, when the remaining time value of the first PDU is equal to the first remaining time threshold, a delay status report is triggered.

[0243] As an embodiment, a delay status report is a signal.

[0244] As an embodiment, a delay status report is an indication.

[0245] As an embodiment, a delay status report is indicated by 1 bit.

[0246] As an embodiment, the first uplink PDU is a data unit generated at layer 3 or a protocol layer above layer 3.

[0247] As a sub-embodiment of the above embodiment, the first uplink PDU is an IP (Internet Protocol) data packet.

[0248] As a sub-embodiment of the above embodiment, the first uplink PDU is an application layer data packet.

[0249] As an embodiment, the first uplink PDU belongs to a radio bearer, and the radio bearer is associated with a logical channel in the first logical channel group.

[0250] As an embodiment, the first uplink PDU belongs to the first logical channel group.

[0251] As an embodiment, the first uplink PDU is cached in the PDCP sublayer of the first node.

[0252] As an embodiment, the first uplink PDU is cached in the RLC sublayer of the first node.

[0253] As an embodiment, the remaining time of the first uplink PDU depends on the value of a PDCP discard timer (discardTimer) associated with the first uplink PDU.

[0254] As an embodiment, the remaining time value of the first uplink PDU is determined according to the value of the PDCP discard timer associated with the first uplink PDU.

[0255] As an embodiment, the remaining time value of the first uplink PDU is the current value of the PDCP discard timer associated with the first uplink PDU.

[0256] As an embodiment, the remaining time value of the first uplink PDU is the difference between the expiration value of the PDCP discard timer associated with the first uplink PDU and the current value of the PDCP discard timer associated with the first uplink PDU.

[0257] As an embodiment, the expiration value of the PDCP discard timer associated with the first uplink PDU is configurable.

[0258] As an embodiment, as a response to receiving the first uplink PDU at the PDCP sublayer of the first node, a PDCP discard timer associated with the first uplink PDU is started.

[0259] As an embodiment, the PDCP discard timer associated with the first uplink PDU is maintained at the PDCP sublayer of the first node.

[0260] As an embodiment, a timer is in a running state after it is started; when the timer is in the running state, the timer is updated in a next time interval, and then it is determined whether the timer has expired.

[0261] As an embodiment, the one time interval includes 1 millisecond.

[0262] As an embodiment, the time interval includes a time length of 1 time slot.

[0263] As an embodiment, the time interval includes a time length of 1 subframe.

[0264] As an embodiment, when a timer is started, the value of the timer is set to 0, and the phrase updating the timer includes: adding 1 to the value of the timer; and determining that the timer is expired when the value of the timer is the expiration value of the timer.

[0265] As an embodiment, when a timer is started, the value of the timer is set to the expiration value of the timer, and the phrase for updating the timer includes: reducing the value of the timer by 1; and when the value of the timer is 0, determining that the timer has expired.

[0266] As an embodiment, the description of the timer operation in the present application is applicable to the PDCP discard timer associated with the uplink data.

[0267] As an embodiment, the delay status report triggered by the first PDU is one of at least one delay status report.

[0268] As an embodiment, the delay status report triggered by the first PDU is the earliest triggered delay status report among the at least one delay status report.

[0269] As an embodiment, the delay status report triggered by the first PDU is the delay status report that is triggered latest among the at least one delay status report.

[0270] As an embodiment, the delay status report triggered by the first PDU is any delay status report among the at least one delay status report.

[0271] As an embodiment, all buffer status reports in the at least one buffer status report are triggered before the delay status report triggered by the first PDU is triggered.

[0272] As an embodiment, the at least one delay status report is triggered and not cancelled.

[0273] As an embodiment, the at least one delay status report is triggered and not cancelled before the first MAC PDU is assembled.

[0274] As an embodiment, the at least one delay status report is cancelled after the first MAC PDU is sent.

[0275] As an embodiment, some of the delay status reports in the at least one delay status report are cancelled after the first MAC PDU is sent.

[0276] As an embodiment, some of the delay status reports in the at least one delay status report are not cancelled after the first MAC PDU is sent.

[0277] As an embodiment, the buffer status report and the delay status report are triggered by different events and are independent of each other.

[0278] As an embodiment, the buffer status report and the delay status report may be triggered at the same time.

[0279] As an embodiment, the at least one delay status report is used to generate the first delay status report.

[0280] It should be particularly noted that any delay status report in the at least one delay status report is a signal or an indication, and the first delay status report is a MAC CE.

[0281] As an embodiment, the delay status report triggered by the first PDU is used to generate the first delay status report.

[0282] As a sub-embodiment of the above embodiment, the first delay status report includes an identifier of the first logical channel group.

[0283] As an embodiment, when the at least one delay status report is triggered and not cancelled, if there are UL-SCH resources available for a new transmission, a multiplexing and assembly procedure is indicated to generate the first delay status report.

[0284] Example 6

[0285] Embodiment 6 illustrates a schematic diagram of a first delay status report, a first uplink data volume and a first remaining time according to an embodiment of the present application, as shown in the attached figure. Figure 6 shown.

[0286] As an embodiment, the first delay status report indicates a first remaining time value.

[0287] As an embodiment, the first delay status report includes a remaining time index, and the first remaining time value is indicated by the value of the remaining time index.

[0288] As a sub-embodiment of the above embodiment, the first remaining time value is obtained by looking up a table according to the value of the remaining time index.

[0289] As an embodiment, the first remaining time value indicates a time value.

[0290] As an embodiment, the first remaining time value indicates a time interval.

[0291] As a sub-embodiment of the above embodiment, the first remaining time value is not greater than the maximum remaining time value indicated by the value of the remaining time index included in the first delay status report.

[0292] As a sub-embodiment of the above embodiment, the first remaining time value is greater than the minimum remaining time value indicated by the value of the remaining time index included in the first delay status report.

[0293] As a sub-embodiment of the above embodiment, the first remaining time value is not less than the remaining time value indicated by the value of the remaining time index included in the first delay status report.

[0294] Example 6 provides a table that indicates the remaining time value through a one-to-one correspondence between the remaining time index and the remaining time. When the value of the remaining time index is 0, the corresponding remaining time value is not greater than t0; when the value of the remaining time index is 1, the corresponding remaining time value is greater than t0 and not greater than t1; when the value of the remaining time index is 2, the corresponding remaining time value is greater than t1 and not greater than t2, and so on, which will not be repeated here.

[0295] As an embodiment, the first remaining time value includes N bits, and N is a positive integer not less than 1 and not greater than 8.

[0296] As an embodiment, the first remaining time value depends on the value of the PDCP discard timer associated with the uplink data at the first time.

[0297] As an embodiment, the first remaining time value is determined according to the value of the PDCP discard timer associated with the uplink data at the first time.

[0298] As an embodiment, the first remaining time value is the value of the PDCP discard timer associated with the uplink data at the first time.

[0299] As an embodiment, the first remaining time value is the difference between the expiration value of the PDCP discard timer associated with the uplink data at the first time and the current value of the corresponding PDCP discard timer.

[0300] As an embodiment, the expiration value of the PDCP discard timer associated with the uplink data is configurable.

[0301] As an embodiment, the expiration value of the PDCP discard timer associated with the uplink data is preconfigured.

[0302] As an embodiment, the first remaining time value is the minimum value of the PDCP discard timer associated with the uplink data at the first time.

[0303] As a sub-embodiment of the above embodiment, three PDUs are cached in the first node, and the three PDUs are respectively associated with three PDCP discard timers in the PDCP sublayer, and the three PDUs are respectively cached in the PDCP sublayer and / or RLC sublayer of the first node; at the first time, the values ​​of the three PDCP discard timers corresponding to the three PDUs are 5, 8 and 16 respectively, and the first remaining time value is 5.

[0304] As an embodiment, the first remaining time value is the minimum value of the difference between the expiration value of the PDCP discard timer associated with the uplink data at the first time and the current value of the corresponding PDCP discard timer.

[0305] As a sub-embodiment of the above embodiment, three PDUs are cached at the first node, and the three PDUs are respectively associated with three PDCP discard timers in the PDCP sublayer, and the three PDUs are respectively cached in the PDCP sublayer and / or RLC sublayer of the first node; at the first time, the values ​​of the three PDCP discard timers corresponding to the three PDUs are 5, 8 and 16 respectively, and the expiration values ​​of the three PDCP discard timers are all 30; at the first time, the absolute value of the difference between the value of the PDCP discard timer associated with the uplink data and the expiration value of the corresponding PDCP discard timer is 25, 22 and 14 respectively; the first remaining time value is 14.

[0306] As an embodiment, the first uplink data volume corresponds to the first remaining time value.

[0307] As an embodiment, the first uplink data amount depends on the first remaining time value.

[0308] As an embodiment, the first uplink data amount indicates the amount of uplink data whose remaining time value is not greater than the first remaining time value.

[0309] As an embodiment, one uplink data is associated with one PDCP discard timer, and the remaining time of the uplink data depends on the value of the associated PDCP discard timer.

[0310] As an embodiment, the remaining time of an uplink data is the current value of the PDCP discard timer associated with the uplink data.

[0311] As an embodiment, the remaining time of an uplink data is the difference between the expiration value of the PDCP discard timer associated with the uplink data and the current value of the corresponding PDCP discard timer.

[0312] As an embodiment, the first uplink data amount indicates the amount of uplink data within a time interval indicated by the first remaining time value.

[0313] As an embodiment, the first uplink data amount indicates the amount of uplink data whose remaining time value is not greater than the first remaining time value and is greater than 0.

[0314] As an embodiment, when the value of a PDCP discard timer associated with an uplink data is 0, the uplink data is discarded and is not used to count the first uplink data amount.

[0315] Attachment of Example 6 Figure 6In the embodiment, the first delay status report includes the first remaining time value, the first uplink data volume and others; the others may include a logical channel group identifier, the logical channel group identifier indicates the logical channel group to which the uplink data belongs, and the volume of the uplink data is used to determine the first uplink data volume; the others may also include a second remaining time value and a corresponding second uplink data volume; wherein the second remaining time value is not equal to the first remaining time value.

[0316] Example 7

[0317] Embodiment 7 illustrates a schematic diagram of the time relationship between at least one delay status report, a first time, and a first PUSCH according to an embodiment of the present application, as shown in the attached figure. Figure 7 Attached Figure 7 In the figure, each rectangular box filled with slashes represents a triggered delay status report, the bold box represents the time domain resources occupied by the first PUSCH, and each rectangular box in the bold box represents an OFDM symbol.

[0318] As an embodiment, the first PUSCH carries the first delay status report.

[0319] As an embodiment, the first PUSCH carries the first MAC PDU.

[0320] As an embodiment, the first MAC PDU generates the first PUSCH after undergoing at least part of CRC attachment, code block segmentation, code block CRC attachment, channel coding, rate matching, code block concatenation, scrambling, modulation, layer mapping, transform precoding, precoding, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and modulation up-conversion.

[0321] As an embodiment, the first PUSCH is a configured UL (uplink) transmission.

[0322] As an embodiment, the first PUSCH corresponds to a configured uplink grant (configured uplink grant).

[0323] As an embodiment, the first PUSCH occupies at least one symbol.

[0324] As an embodiment, the first time corresponds to the time of the first symbol sent by the first PUSCH.

[0325] As a sub-embodiment of the above two embodiments, the one symbol is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0326] As a sub-embodiment of the above two embodiments, the one symbol is a multi-carrier symbol.

[0327] As a sub-embodiment of the above two embodiments, the one symbol is a single carrier symbol.

[0328] As an embodiment, the first PUSCH sending includes: sending a signal in the first PUSCH.

[0329] As an embodiment, the first PUSCH sending includes: sending at least one bit block in the first PUSCH.

[0330] As an embodiment, the first PUSCH is used for new transmission.

[0331] As an embodiment, the first transmission of a transport block (TB) is a new transmission.

[0332] As an embodiment, there is no previous NDI for a transport block for a new transport.

[0333] As an embodiment, any transmission in a repetition of a transmission block is a new transmission.

[0334] As an embodiment, the first transmission in repeated transmission of a transmission block is a new transmission.

[0335] As an embodiment, the at least one delay status report is triggered before the first PUSCH is sent and is cancelled after the first PUSCH is sent.

[0336] Example 8

[0337] Embodiment 8 illustrates a schematic diagram of a first cache status report and at least one cache status report according to an embodiment of the present application, as shown in the attached figure. Figure 8 Attached Figure 8 In the figure, a rectangular box represents a cache status report, and a rectangular box filled with slashes represents the first cache status report.

[0338] As an embodiment, the at least one cache status report includes a cache status report that is triggered and not canceled before the first cache status report.

[0339] As an embodiment, the above method can cancel invalid buffer status reports, avoid unnecessary buffer status report MAC CE sending, and cause waste of uplink resources.

[0340] As an embodiment, the first buffer status report is a buffer status report that is most recently triggered before the first MAC PDU is assembled and when the amount of uplink data is less than the first uplink data amount.

[0341] As a sub-embodiment of the above embodiment, the at least one cache status report does not include a cache status report triggered after the first cache status report.

[0342] As an embodiment, the cache status report included in the at least one cache status report that is triggered and not canceled before the first cache status report has an uplink data volume that is greater than the first uplink data volume, or is equal to the first uplink data volume, or is less than the first uplink data volume when it is triggered.

[0343] Attachment of Example 8 Figure 8 In the embodiment, the first cache status report is the cache status report that was most recently triggered before the first MAC PDU was assembled and the amount of uplink data when triggered was less than the first uplink data amount, and the at least one cache status report includes the first cache status report and all cache status reports that were triggered and not canceled before the first cache status report.

[0344] Example 9

[0345] Embodiment 9 illustrates a schematic diagram of a delay status report and at least one buffer status report triggered by a first PDU according to an embodiment of the present application, as shown in the attached Fig. 9 Attached Fig. 9 In the figure, a rectangular box represents a cache status report, and a rectangular box filled with slashes represents a delay status report triggered by the first PDU.

[0346] As an embodiment, at least part of the at least one buffer status report is triggered after a delay status report triggered by the first PDU.

[0347] As an embodiment, at least part of the at least one buffer status report is triggered before the delay status report triggered by the first PDU.

[0348] As an embodiment, part of the cache status reports in the at least one cache status report are triggered before the delay status report triggered by the first PDU; and the remaining part of the cache status reports in the at least one cache status report are triggered after the delay status report triggered by the first PDU.

[0349] As an embodiment, the first uplink data volume is related to the volume of uplink data corresponding to the first remaining time value, and has no direct relationship with the volume of uplink data when a delay status report is triggered.

[0350] Attachment of Example 9 Fig. 9 In the embodiment, part of the cache status reports in at least one cache status report are triggered before the delay status report triggered by the first PDU; the remaining part of the cache status reports in the at least one cache status report are triggered after the delay status report triggered by the first PDU; at least the delay status report triggered by the first PDU is used to generate the first delay status report.

[0351] Example 10

[0352] Embodiment 10 illustrates a schematic diagram of the relationship between a delay status report triggered by a first PDU, a delay status report triggered by a second PDU and a first PUSCH according to an embodiment of the present application, as shown in the attached figure. Fig.10 shown.

[0353] As an embodiment, after the first MAC PDU is sent, a delay status report triggered by the second PDU is not canceled; wherein the first uplink data volume does not include the data volume of the second PDU.

[0354] As an embodiment, after the first MAC PDU is sent, the at least one delay status report is canceled, and the at least one delay status report includes the delay status report triggered by the first PDU; the at least one delay status report does not include the delay status report triggered by the second PDU.

[0355] As an embodiment, the PDCP discard timer associated with the second PDU has not expired.

[0356] As an embodiment, the second PDU is available uplink data.

[0357] As an embodiment, the delay status report triggered by the second PDU is triggered and not cancelled before the first MAC PDU is assembled.

[0358] As an embodiment, the delay status report triggered by the second PDU is triggered after the delay status report triggered by the first PDU.

[0359] As an embodiment, the delay status report triggered by the second PDU is triggered before the delay status report triggered by the first PDU.

[0360] As an embodiment, the delay status report triggered by the second PDU and the delay status report triggered by the first PDU are triggered at the same time.

[0361] As an embodiment, the time when the second PDU triggers a delay status report is later than the time when the first PDU triggers a delay status report.

[0362] As a sub-embodiment of the above embodiment, the logical channel to which the first PDU belongs and the logical channel to which the second PDU belongs belong to the same LCG.

[0363] As a sub-embodiment of the above embodiment, the first PDU and the second PDU belong to the same logical channel.

[0364] As an embodiment, the priority of the logical channel to which the second PDU belongs is lower than the priority of the logical channel to which the first PDU belongs.

[0365] As an embodiment, when sending the first PUSCH, the first remaining time value is less than the remaining time value of the second PDU.

[0366] As a sub-embodiment of the above embodiment, the first delay status report does not include the remaining time value of the second PDU.

[0367] Example 10 describes the difference between the processing of the delay status report and the processing of the cache status report: the cache status report MAC CE includes the amount of uplink data when the cache status report was most recently triggered before the MAC PDU assembly. After the cache status report MAC CE is sent, all triggered cache status reports are canceled; while the delay status report MAC CE may only include the first remaining time value and the first uplink data amount. At this time, the uplink data amount that triggers the delay status report but the corresponding remaining time value is greater than the first remaining time value is not included in the first delay status report. Therefore, the delay status report triggered by these uplink data cannot be canceled.

[0368] Specifically, the first PDU and the second PDU belong to the first logical channel group, and the first remaining time threshold configured for the first logical channel group is 15ms; the first PDU arrives at the PDCP sublayer 8ms earlier than the second PDU, so the delay status report triggered by the first PDU is 8ms earlier than the delay status report triggered by the second PDU; if the first delay status report is generated 10ms after the delay status report triggered by the first PDU, the first remaining time value is 5ms, and the corresponding first uplink data volume includes the data volume of the first PDU; and since the remaining time of the second PDU is 13ms, the data volume of the second PDU is not counted in the first uplink data volume, so the delay status report triggered by the second PDU cannot be canceled.

[0369] As an embodiment, the above method can timely trigger the generation of a new delay status report MAC CE to report the amount of data that has not been reported by retaining the delay status report, so as to facilitate the base station to schedule the upload in time.

[0370] As an embodiment, the above method can effectively support the reporting of data volume of delay-sensitive services.

[0371] Embodiment 11

[0372] Embodiment 11 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in the attached figure. Fig.11 As shown in the attached Fig.11 In the embodiment, the first node processing device 1100 includes a first transceiver 1101 and a first processor 1102. The first node 1100 is a UE.

[0373] In Example 11, a first transceiver 1101 sends a first MAC PDU, which includes a first delay status report; a first processor 1102, in response to the first MAC PDU being sent, cancels at least one cache status report; wherein the first delay status report includes a first uplink data volume, which is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report among the at least one cache status report.

[0374] As an embodiment, the first delay status report indicates a first remaining time value, and the first remaining time value depends on the value of the PDCP discard timer associated with the uplink data at the first time; wherein, the first time corresponds to the time of the first symbol sent by the first PUSCH, and the first PUSCH carries the first delay status report.

[0375] As an embodiment, the first delay status report indicates a first remaining time value, and the first remaining time value depends on the value of the PDCP discard timer associated with the uplink data at the first time; wherein, the first time corresponds to the time of the first symbol sent by the first PUSCH, and the first PUSCH carries the first delay status report; the first uplink data volume indicates the amount of uplink data whose remaining time value is not greater than the first remaining time value.

[0376] As an embodiment, the first transceiver 1101 receives a first message, and the first message configures a first remaining time threshold for a first logical channel group; the first processor 1102 triggers a delay status report when the remaining time value of the first PDU is not greater than the first remaining time threshold; wherein the first uplink PDU belongs to the first logical channel group; the delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to trigger the generation of the first delay status report.

[0377] As an embodiment, the at least one cache status report includes a cache status report that is triggered and not canceled before the first cache status report.

[0378] As an embodiment, the first transceiver 1101 receives a first message, and the first message configures a first remaining time threshold for a first logical channel group; the first processor 1102 triggers a delay status report when the remaining time value of the first PDU is not greater than the first remaining time threshold; wherein the first uplink PDU belongs to the first logical channel group; the delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to trigger the generation of the first delay status report; at least part of the at least one cache status report is triggered after the delay status report triggered by the first PDU.

[0379] As an embodiment, after the first MAC PDU is sent, a delay status report triggered by the second PDU is not canceled; wherein the first uplink data volume does not include the data volume of the second PDU.

[0380] As an embodiment, the first transceiver 1101 includes Figure 4 The receiver 454 (including antenna 452), receive processor 456, multi-antenna receive processor 458 and controller / processor 459.

[0381] As an embodiment, the first transceiver 1101 includes Figure 4 At least one of the receiver 454 (including antenna 452), receive processor 456, multi-antenna receive processor 458 or controller / processor 459.

[0382] As an embodiment, the first transceiver 1101 includes Figure 4 The transmitter 454 (including antenna 452), transmit processor 468, multi-antenna transmit processor 457 and controller / processor 459.

[0383] As an embodiment, the first transceiver 1101 includes Figure 4 At least one of the transmitter 454 (including antenna 452), the transmit processor 468, the multi-antenna transmit processor 457 or the controller / processor 459.

[0384] As an embodiment, the first processor 1102 includes the Figure 4 Controller / processor 459 in.

[0385] Example 12

[0386] Embodiment 12 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in the attached figure. Fig.12 As shown in the attached Fig.12 In the embodiment, the second node processing device 1200 includes a second transceiver 1201. The second node 1200 is a base station.

[0387] In Example 12, the second transceiver 1201 receives a first MAC PDU, which includes a first delay status report; wherein the first MAC PDU is sent to cancel at least one cache status report; the first delay status report includes a first uplink data volume, which is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report among the at least one cache status report.

[0388] As an embodiment, the first delay status report indicates a first remaining time value, and the first remaining time value depends on the value of the PDCP discard timer associated with the uplink data at the first time; wherein, the first time corresponds to the time of the first symbol sent by the first PUSCH, and the first PUSCH carries the first delay status report.

[0389] As an embodiment, the first delay status report indicates a first remaining time value, and the first remaining time value depends on the value of the PDCP discard timer associated with the uplink data at the first time; wherein, the first time corresponds to the time of the first symbol sent by the first PUSCH, and the first PUSCH carries the first delay status report; the first uplink data volume indicates the amount of uplink data whose remaining time value is not greater than the first remaining time value.

[0390] As an embodiment, the second transceiver 1201 sends a first message, and the first message configures a first remaining time threshold for the first logical channel group; wherein, when the remaining time value of the first PDU is not greater than the first remaining time threshold, a delay status report is triggered; the first uplink PDU belongs to the first logical channel group; the one delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to trigger the generation of the first delay status report.

[0391] As an embodiment, the at least one cache status report includes a cache status report that is triggered and not canceled before the first cache status report.

[0392] As an embodiment, the second transceiver 1201 sends a first message, and the first message configures a first remaining time threshold for the first logical channel group; wherein, when the remaining time value of the first PDU is not greater than the first remaining time threshold, a delay status report is triggered; the first uplink PDU belongs to the first logical channel group; the one delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to trigger the generation of the first delay status report; at least part of the at least one cache status report is triggered after the one delay status report triggered by the first PDU.

[0393] As an embodiment, after the first MAC PDU is sent, a delay status report triggered by the second PDU is not canceled; wherein the first uplink data volume does not include the data volume of the second PDU.

[0394] As an embodiment, the second transceiver 1201 includes the attached Figure 4 The receiver 418 (including antenna 420), receive processor 470, multi-antenna receive processor 472 and controller / processor 475.

[0395] As an embodiment, the second transceiver 1201 includes the attached Figure 4 At least one of the receiver 418 (including the antenna 420), the receive processor 470, the multi-antenna receive processor 472 or the controller / processor 475.

[0396] As an embodiment, the second transceiver 1201 includes the attached Figure 4 The transmitter 418 (including antenna 420), transmit processor 416, multi-antenna transmit processor 471 and controller / processor 475.

[0397] As an embodiment, the second transceiver 1201 includes the attached Figure 4 At least one of the transmitter 418 (including antenna 420), the transmit processor 416, the multi-antenna transmit processor 471 or the controller / processor 475.

[0398] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The first type of communication node or UE or terminal in the present application includes but is not limited to mobile phones, tablet computers, notebooks, Internet cards, low-power devices, eMTC (enhanced Machine Type Communication, enhanced machine type communication) equipment, NB-IoT equipment, vehicle-mounted communication equipment, aircraft, airplanes, drones, remote-controlled aircraft and other wireless communication equipment. The second type of communication node or base station or network side equipment in the present application includes but is not limited to macrocellular base stations, microcellular base stations, home base stations, relay base stations, eNB, gNB, transmission and reception nodes TRP (Transmission and Reception Point, transmission and reception point), relay satellites, satellite base stations, aerial base stations and other wireless communication equipment.

[0399] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first transceiver sends a first MAC PDU, wherein the first MAC PDU includes a first delay status report; a first processor, in response to the first MAC PDU being sent, canceling at least one buffer status report; The first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first buffer status report is triggered, and the first buffer status report is a buffer status report among the at least one buffer status report.

2. The first node according to claim 1, characterized in that: The first delay status report indicates a first remaining time value, the first remaining time value being dependent on a value of a PDCP discard timer associated with the uplink data at the first time; The first time corresponds to the time of the first symbol sent by the first PUSCH, and the first PUSCH carries the first delay status report.

3. The first node according to claim 2, characterized in that: The first uplink data amount indicates the amount of uplink data whose remaining time value is not greater than the first remaining time value.

4. The first node according to any one of claims 1 to 3, comprising: The first transceiver receives a first message, wherein the first message configures a first remaining time threshold for a first logical channel group; The first processor triggers a delay status report when the remaining time value of the first PDU is not greater than the first remaining time threshold; Among them, the first uplink PDU belongs to the first logical channel group; the delay status report triggered by the first PDU is one of at least one delay status report, the at least one delay status report is triggered and not canceled, and the at least one delay status report is used to generate the first delay status report.

5. The first node according to any one of claims 1 to 4, characterized in that: The at least one buffer status report includes a buffer status report that is triggered and not canceled before the first buffer status report.

6. The first node according to any one of claims 4 or 5, characterized in that: At least part of the at least one buffer status report is triggered after the one delay status report triggered by the first PDU.

7. The first node according to any one of claims 1 to 6, characterized in that: After the first MAC PDU is sent, a delayed status report triggered by the second PDU is not cancelled; The first uplink data volume does not include the data volume of the second PDU.

8. A second node used for wireless communication, characterized in that: include: A second transceiver receives a first MAC PDU, wherein the first MAC PDU includes a first delay status report; Among them, the first MAC PDU is sent to cancel at least one cache status report; the first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first cache status report is triggered, and the first cache status report is a cache status report in the at least one cache status report.

9. A method in a first node for wireless communication, characterized in that: include: Sending a first MAC PDU, wherein the first MAC PDU includes a first delay status report; canceling at least one buffer status report in response to the first MAC PDU being sent; The first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first buffer status report is triggered, and the first buffer status report is a buffer status report among the at least one buffer status report.

10. A method in a second node for wireless communication, characterized in that: include: receiving a first MAC PDU, the first MAC PDU comprising a first delay status report; wherein the first MAC PDU is sent to cancel at least one buffer status report; The first delay status report includes a first uplink data volume, the first uplink data volume is not less than the uplink data volume when the first buffer status report is triggered, and the first buffer status report is a buffer status report among the at least one buffer status report.

Images