Method and apparatus used in communication node for wireless communication

By optimizing the BSR transmission process in the wireless communication system and configuring uplink granting and timer management through control information, the problem of low BSR transmission efficiency was solved, achieving efficient resource utilization and reduced scheduling latency.

WO2024245000A1PCT designated stage expired Publication Date: 2024-12-05SHANGHAI LANGBO COMM TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/093806
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-26
Filing Date
2024-05-17
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

In future wireless communication systems, BSR transmission suffers from inefficiency and resource waste, especially in scenarios with multiple uplink grants. Existing technologies struggle to optimize the BSR transmission process, leading to improper resource scheduling and increased latency.

Method used

By receiving and sending control information to configure uplink grants, any two uplink grants do not overlap in time, and the control information determines whether to restart the timer or trigger a BSR, optimizing the indication of the buffer size field in the BSR MAC CE and reducing unnecessary BSR transmissions.

Benefits of technology

It reduces the probability of timer restart, increases the probability of BSR triggering, shortens scheduling latency, optimizes resource utilization, and reduces signaling overhead and resource waste.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024093806_05122024_PF_FP_ABST
    Figure CN2024093806_05122024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed in the present application are a method and apparatus used in a communication node for wireless communication. The method comprises: a communication node receiving a first message, wherein the first message configures uplink grants, and any two uplink grants configured by the first message do not overlap with each other in terms of time; triggering at least one BSR; and after the action of triggering the at least one BSR, sending a first MAC PDU on a first uplink grant, wherein whether the first MAC PDU comprises a BSR MAC CE (Control Element) depends on whether a first condition set is satisfied; when the first condition set is satisfied, the first MAC PDU does not comprise the BSR MAC CE; when the first condition set is not satisfied, the first MAC PDU comprises the BSR MAC CE; the first condition set is related to an uplink grant following the first uplink grant; and the first uplink grant and the uplink grant following the first uplink grant are configured by the first message. By means of the solution provided in the present application, the reporting of a BSR is optimized, and unnecessary sending of the BSR is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

A method and apparatus for use in a communication node for wireless communication Technical Field

[0001] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to a method and apparatus for sending a BSR (Buffer Status Report). Background Art

[0002] The application scenarios of future wireless communication systems are becoming increasingly diverse, and each scenario places high-speed and low-latency performance requirements on the system. For example, to meet the diverse performance requirements of various application scenarios, such as capacity demands, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #98 plenary meeting approved the "XR (Extended Reality) Enhancements for NR (New Radio)" WI (Work Item).

[0003] Summary of the Invention

[0004] The inventors have discovered through research that the sending of BSRs is a key issue, especially but not limited to the sending of BSRs for multiple uplink grants.

[0005] To address the above-mentioned issues, this application provides a solution for sending control information. While the NR system is used as an example in the description of the above-mentioned issues, this application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced), achieving similar technical effects as the NR system. Furthermore, while this application provides specific implementations for the uplink, it can also be applied to scenarios such as the downlink, achieving similar technical effects as the uplink. Furthermore, adopting a unified design for different scenarios can also help reduce hardware complexity and cost. Furthermore, while this application provides specific implementations for XR scenarios, it can also be applied to scenarios for uplink enhancement, achieving similar technical effects as the XR system. Furthermore, while this application provides specific implementations for BSR, it can also be applied to scenarios such as delay reporting or BSR-equivalent reporting, achieving similar technical effects as the BSR. Furthermore, while this application is initially intended for the Uu air interface, it can also be applied to the PC5 interface, achieving similar technical effects as the Uu air interface. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the V2X (Vehicle-to-Everything, Internet of Vehicles) scenario, the communication scenario between the terminal and the relay, and the relay and the base station, to achieve similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the IAB (Integrated Access and Backhaul, integrated access and backhaul) communication scenario, to achieve similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of this application is for the terrestrial network (TN) scenario, this application is also applicable to the non-terrestrial network (NTN) communication scenario, to achieve similar technical effects in the TN scenario. In addition, the use of a unified solution for different scenarios can also help reduce hardware complexity and cost.

[0006] As an embodiment, the interpretation of terminology in this application refers to the definition of 3GPP specification protocol TS36 series.

[0007] As an embodiment, the interpretation of the terms in this application refers to the definition of the 3GPP specification protocol TS38 series.

[0008] As an embodiment, the interpretation of the terms in this application refers to the definitions of the 3GPP specification protocol TS37 series.

[0009] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

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

[0011] receiving a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0012] sending first control information on the first uplink grant, the first control information indicating whether at least one uplink grant subsequent to the first uplink grant is not used;

[0013] For one uplink grant among the at least one uplink grant after the first uplink grant, determining whether to restart a first timer according to an indication of the one uplink grant by the first control information;

[0014] Among them, the behavior determines whether to restart the first timer based on the indication of the first control information for the one uplink grant, including: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; the expiration of the first timer is used to trigger the BSR; the first uplink grant and the at least one uplink grant after the first uplink grant are configured by the first message.

[0015] According to one aspect of the present application, it is characterized in that the behavior determines whether to restart the first timer based on the indication of the first control information for the uplink grant, including: when the first control information indicates that the uplink grant is not used, the first timer is not restarted.

[0016] As an embodiment, the problem to be solved by this application includes: how to optimize BSR.

[0017] As an embodiment, the problem to be solved by the present application includes: how to process the first timer for an uplink grant in at least one uplink grant after the first uplink grant indicated by the first control information whether to be used.

[0018] As an embodiment, the characteristics of the above method include: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used.

[0019] As an embodiment, the benefits of the above method include: reducing the probability of the first timer being restarted.

[0020] As an embodiment, the benefits of the above method include: increasing the probability of BSR being triggered.

[0021] As an embodiment, the benefits of the above method include: shortening the scheduling delay.

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

[0023] Sending a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0024] receiving first control information on the first uplink grant, the first control information indicating whether at least one uplink grant subsequent to the first uplink grant is not used;

[0025] Among them, for one uplink grant among the at least one uplink grant after the first uplink grant, the recipient of the first message determines whether to restart the first timer based on the indication of the one uplink grant by the first control information; the behavior determines whether to restart the first timer based on the indication of the one uplink grant by the first control information, including: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; expiration of the first timer is used to trigger BSR; the first uplink grant and the at least one uplink grant after the first uplink grant are configured by the first message.

[0026] According to one aspect of the present application, it is characterized in that the behavior determines whether to restart the first timer based on the indication of the first control information for the uplink grant, including: when the first control information indicates that the uplink grant is not used, the first timer is not restarted.

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

[0028] A first receiver receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0029] a first transmitter, sending first control information on the first uplink grant, the first control information indicating whether at least one uplink grant subsequent to the first uplink grant is not used;

[0030] The first transmitter determines, for one uplink grant among the at least one uplink grant subsequent to the first uplink grant, according to an indication of the one uplink grant by the first control information, whether to restart a first timer;

[0031] Among them, the behavior determines whether to restart the first timer based on the indication of the first control information for the one uplink grant, including: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; the expiration of the first timer is used to trigger the BSR; the first uplink grant and the at least one uplink grant after the first uplink grant are configured by the first message.

[0032] According to one aspect of the present application, it is characterized in that the behavior determines whether to restart the first timer based on the indication of the first control information for the uplink grant, including: when the first control information indicates that the uplink grant is not used, the first timer is not restarted.

[0033] The present application discloses a second node used for wireless communication, characterized by comprising:

[0034] A second transmitter sends a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0035] a second receiver receiving first control information on the first uplink grant, the first control information indicating whether at least one uplink grant subsequent to the first uplink grant is not used;

[0036] Among them, for one uplink grant among the at least one uplink grant after the first uplink grant, the recipient of the first message determines whether to restart the first timer based on the indication of the one uplink grant by the first control information; the behavior determines whether to restart the first timer based on the indication of the one uplink grant by the first control information, including: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; expiration of the first timer is used to trigger BSR; the first uplink grant and the at least one uplink grant after the first uplink grant are configured by the first message.

[0037] According to one aspect of the present application, it is characterized in that the behavior determines whether to restart the first timer based on the indication of the first control information for the uplink grant, including: when the first control information indicates that the uplink grant is not used, the first timer is not restarted.

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

[0039] receiving a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0040] triggering at least one BSR; after the action triggers at least one BSR, sending a first MAC PDU on a first uplink grant, the first MAC PDU including a BSR MAC CE;

[0041] The indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0042] As an embodiment, the problem to be solved by the present application includes: how to set the value of the buffer size field in the BSR MAC CE.

[0043] As an embodiment, the characteristics of the above method include: the indication of the buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

[0044] As an embodiment, the benefits of the above method include: avoiding resource waste caused by requesting too many resources.

[0045] As an embodiment, the benefits of the above method include: being beneficial for resource scheduling.

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

[0047] Sending a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0048] receiving a first MAC PDU on a first uplink grant, the first MAC PDU including a BSR MAC CE;

[0049] In which, after at least one BSR is triggered, the first MAC PDU is sent; the indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

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

[0051] A first receiver receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0052] A first transmitter triggers at least one BSR; after the behavior triggers the at least one BSR, sends a first MAC PDU on a first uplink grant, the first MAC PDU including a BSR MAC CE;

[0053] The indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0054] The present application discloses a second node used for wireless communication, characterized by comprising:

[0055] A second transmitter sends a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0056] a second receiver receiving a first MAC PDU on a first uplink grant, wherein the first MAC PDU includes a BSR MAC CE;

[0057] In which, after at least one BSR is triggered, the first MAC PDU is sent; the indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

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

[0059] receiving a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0060] triggering at least one BSR; after the action triggers at least one BSR, sending a first MAC PDU on a first uplink grant, the first MAC PDU including a BSR MAC CE;

[0061] In which, the first cache size field in the BSR MAC CE included in the first MAC PDU is set to the first cache size index; the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1; the first cache size index indicates the first cache size value in the first table.

[0062] As an embodiment, the problem to be solved by the present application includes: how to determine the buffer size value indicated by the buffer size field in the BSR MAC CE.

[0063] As an embodiment, the characteristics of the above method include: the buffer size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU is related to the first buffer size value and M1.

[0064] As an embodiment, the benefits of the above method include: avoiding the introduction of a BSR table.

[0065] As an embodiment, the benefits of the above method include: achieving flexible reporting of cache size.

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

[0067] Sending a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0068] receiving a first MAC PDU on a first uplink grant, the first MAC PDU including a BSR MAC CE;

[0069] In which, the first cache size field in the BSR MAC CE included in the first MAC PDU is set to the first cache size index; the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1; the first cache size index indicates the first cache size value in the first table.

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

[0071] A first receiver receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0072] A first transmitter triggers at least one BSR; after the behavior triggers the at least one BSR, sends a first MAC PDU on a first uplink grant, the first MAC PDU including a BSR MAC CE;

[0073] In which, the first cache size field in the BSR MAC CE included in the first MAC PDU is set to the first cache size index; the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1; the first cache size index indicates the first cache size value in the first table.

[0074] The present application discloses a second node used for wireless communication, characterized by comprising:

[0075] A second transmitter sends a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0076] a second receiver receiving a first MAC PDU on a first uplink grant, wherein the first MAC PDU includes a BSR MAC CE;

[0077] In which, after at least one BSR is triggered, the first MAC PDU is sent; the first cache size field in the BSR MAC CE included in the first MAC PDU is set to the first cache size index; the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1; the first cache size index indicates the first cache size value in the first table.

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

[0079] receiving a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0080] Triggering at least one BSR; after the behavior triggers the at least one BSR, sending a first MAC (Medium Access Control) PDU (Protocol Data Unit) on a first uplink grant;

[0081] Whether the first MAC PDU includes a BSR MAC CE (Control Element) depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include a BSR MAC CE; when the first condition set is not met, the first MAC PDU includes a BSR MAC CE; the first condition set is related to an uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0082] As an embodiment, the problem to be solved by this application includes: how to optimize BSR.

[0083] As an embodiment, the problem to be solved by the present application includes: how to determine whether the first MAC PDU sent on the first uplink grant configured by the first message includes a BSR MAC CE.

[0084] As an embodiment, the characteristics of the above method include: whether the first MAC PDU includes the BSR MAC CE depends on the uplink grant after the first uplink grant.

[0085] As an embodiment, the characteristics of the above method include: determining whether the first MAC PDU includes a BSR MAC CE based on an uplink grant subsequent to the first uplink grant.

[0086] As an embodiment, the characteristics of the above method include: whether the first MAC PDU includes the BSR MAC CE is related to the uplink grant after the first uplink grant.

[0087] As an embodiment, the benefits of the above method include: optimizing BSR reporting.

[0088] As an embodiment, the benefits of the above method include: reducing unnecessary BSR transmission.

[0089] As an embodiment, the benefits of the above method include: saving uplink granted resources.

[0090] As an embodiment, the benefits of the above method include: reducing signaling overhead.

[0091] As an embodiment, the benefits of the above method include: balancing resource scheduling and resource utilization.

[0092] According to one aspect of the present application, it is characterized by comprising:

[0093] First control information is sent on the first uplink grant, where the first control information indicates whether at least one uplink grant subsequent to the first uplink grant is not used.

[0094] According to one aspect of the present application, it is characterized by comprising:

[0095] For one uplink grant among the at least one uplink grant following the first uplink grant, determining whether to restart a first timer according to an indication of the one uplink grant by the first control information;

[0096] The behavior of determining whether to restart the first timer based on the indication of the first control information for the uplink grant includes: restarting the first timer only when the first control information does not indicate that the uplink grant is not used; and the expiration of the first timer is used to trigger the BSR.

[0097] As an embodiment, the benefits of the above method include: reducing the probability of the first timer being restarted.

[0098] As an embodiment, the benefits of the above method include: increasing the probability of BSR being triggered.

[0099] As an embodiment, the benefits of the above method include: shortening the scheduling delay.

[0100] According to one aspect of the present application, it is characterized in that the first control information does not indicate that any uplink grant in the uplink grant after the first uplink grant is not used.

[0101] According to one aspect of the present application, it is characterized in that the first condition set is related to the delay budget of at least one data packet set, and each data packet set in the at least one data packet set includes at least one data packet.

[0102] According to one aspect of the present application, it is characterized by comprising:

[0103] When the first set of conditions is met, canceling the triggered BSR;

[0104] The BSR triggered by the behavior cancellation is used to determine that the first MAC PDU does not include a BSR.

[0105] According to one aspect of the present application, it is characterized in that, if the first MAC PDU includes a BSR MAC CE, the indication of the buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

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

[0107] Sending a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0108] receiving a first MAC PDU on a first uplink grant;

[0109] In which, after at least one BSR is triggered, the first MAC PDU is sent; whether the first MAC PDU includes BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include BSR MAC CE; when the first condition set is not met, the first MAC PDU includes BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0110] According to one aspect of the present application, it is characterized by comprising:

[0111] First control information is received on the first uplink grant, where the first control information indicates whether at least one uplink grant subsequent to the first uplink grant is not used.

[0112] According to one aspect of the present application, it is characterized in that, for one uplink grant among the at least one uplink grant after the first uplink grant, the receiver of the first message determines whether to restart the first timer based on the indication of the one uplink grant by the first control information; the behavior determines whether to restart the first timer based on the indication of the one uplink grant by the first control information, including: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; and the expiration of the first timer is used to trigger a BSR.

[0113] According to one aspect of the present application, it is characterized in that the first control information does not indicate that any uplink grant in the uplink grant after the first uplink grant is not used.

[0114] According to one aspect of the present application, it is characterized in that the first condition set is related to the delay budget of at least one data packet set, and each data packet set in the at least one data packet set includes at least one data packet.

[0115] According to one aspect of the present application, it is characterized in that when the first condition set is met, the receiver of the first message cancels the triggered BSR; the behavior of canceling the triggered BSR is used to determine that the first MAC PDU does not include a BSR.

[0116] According to one aspect of the present application, it is characterized in that, if the first MAC PDU includes a BSR MAC CE, the indication of the buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

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

[0118] A first receiver receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0119] a first transmitter, triggering at least one BSR; and sending a first MAC PDU on a first uplink grant after the action triggers the at least one BSR;

[0120] Whether the first MAC PDU includes the BSR MAC CE depends on whether the first condition set is met; when the first condition set is met, the first MAC PDU does not include the BSR MAC CE; when the first condition set is not met, the first MAC PDU includes the BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0121] The present application discloses a second node used for wireless communication, characterized by comprising:

[0122] A second transmitter sends a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0123] a second receiver, receiving a first MAC PDU on a first uplink grant;

[0124] In which, after at least one BSR is triggered, the first MAC PDU is sent; whether the first MAC PDU includes BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include BSR MAC CE; when the first condition set is not met, the first MAC PDU includes BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0125] As an example, compared with traditional solutions, this application has the following advantages:

[0126] -.Optimized BSR reporting;

[0127] -.Reduce the sending of unnecessary BSRs;

[0128] -. Saves resources granted by upstream;

[0129] -. Reduced signaling overhead;

[0130] -.Balanced resource scheduling and resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0132] FIG1A shows a flow chart of transmission of a first message and a first MAC PDU according to one embodiment of the present application;

[0133] FIG1B shows a flow chart of transmission of a first message and first control information according to an embodiment of the present application;

[0134] FIG1C shows a flow chart of transmission of a first message and a first MAC PDU according to one embodiment of the present application;

[0135] FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0136] FIG3 is a schematic diagram showing an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0137] FIG4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0138] FIG5 shows a wireless signal transmission flow chart according to an embodiment of the present application;

[0139] FIG6 shows a wireless signal transmission flow chart according to another embodiment of the present application;

[0140] FIG7 is a schematic diagram showing that the first control information does not indicate that any uplink grant after the first uplink grant is not used according to an embodiment of the present application;

[0141] FIG8 is a schematic diagram showing a relationship between a first condition set and a delay budget of at least one data packet set according to an embodiment of the present application;

[0142] FIG9 shows a structural block diagram of a processing device used in a first node according to an embodiment of the present application;

[0143] FIG10 shows a structural block diagram of a processing device used in a second node according to an embodiment of the present application;

[0144] FIG11 shows a schematic diagram of determining whether to restart a first timer based on an indication of an uplink grant by first control information according to an embodiment of the present application. DETAILED DESCRIPTION

[0145] 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, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other in any way.

[0146] Example 1A

[0147] Example 1A illustrates a flowchart of the transmission of a first message and a first MAC PDU according to an embodiment of the present application, as shown in Figure 1A. In Figure 1A, each box represents a step. It is particularly important to emphasize that the order of the boxes in the figure does not represent the temporal sequence of the steps represented.

[0148] In Example 1A, the first node in the present application receives a first message in step 101A, and the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; in step 102A, at least one BSR is triggered; in step 103A, after the behavior triggers at least one BSR, a first MAC PDU is sent on the first uplink grant; wherein, whether the first MAC PDU includes the BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include the BSR MAC CE; when the first condition set is not met, the first MAC PDU includes the BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0149] As an embodiment, the first node is configured with only a first MAC entity.

[0150] As an embodiment, the first node is configured with at least two MAC entities, and the first MAC entity is one of the at least two MAC entities.

[0151] As an embodiment, the at least two MAC entities are two MAC entities, and the two MAC entities are respectively a MAC entity of an MCG and a MAC entity of an SCG.

[0152] As an embodiment, the first message is UE-specific signaling.

[0153] As an embodiment, the first message is cell common signaling.

[0154] As an embodiment, the first message is used to configure CG (Configured Grant).

[0155] As an embodiment, the first message is used for semi-persistently configuration.

[0156] As an embodiment, the first message is layer 1 signaling (L1 signalling).

[0157] As an embodiment, the first message is transmitted via PDCCH (Physical downlink control channel).

[0158] As an embodiment, the first message is a DCI (Downlink control information).

[0159] As an embodiment, the DCI format of the first message is DCI format 0_0.

[0160] As an embodiment, the DCI format of the first message is DCI format 0_1.

[0161] As an embodiment, the DCI format of the first message is DCI format 0_2.

[0162] As an embodiment, the DCI format of the first message is a new DCI format.

[0163] As an embodiment, the first message includes at least one field in a DCI format.

[0164] As an embodiment, the first message is a DCI whose CRC (Cyclic redundancy check) is scrambled by CS (Configured Scheduling)-RNTI (Radio Network Temporary Identity).

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

[0166] As an embodiment, the first message includes an RRC message and a DCI.

[0167] As an embodiment, the first message includes an RRC message and a MAC CE (Control Element).

[0168] As an embodiment, the first message is an RRC message.

[0169] As an embodiment, the first message is an RRCReconfiguration message.

[0170] As an embodiment, the first message is a CellGroupConfig IE (Information Element).

[0171] As an embodiment, the first message includes an IE whose name includes ConfiguredGrantConfig.

[0172] As an embodiment, the first message is a ConfiguredGrantConfig IE.

[0173] As an embodiment, the first message includes a field, and the field indicates a first index.

[0174] As a sub-embodiment of this embodiment, the name of the domain includes configuredGrantConfigIndex.

[0175] As a sub-embodiment of this embodiment, the one field is a configuredGrantConfigIndex field.

[0176] As a sub-embodiment of this embodiment, the name of the domain includes configuredGrantConfigIndexMAC.

[0177] As a sub-embodiment of this embodiment, the one field is a configuredGrantConfigIndex field.

[0178] As a sub-embodiment of this embodiment, the first index is used to indicate a CG configuration.

[0179] As a sub-embodiment of this embodiment, the first index is used to indicate the CG configuration to which the uplink grant of the first message configuration belongs.

[0180] As a sub-embodiment of this embodiment, the first index is associated with the CG configuration to which the uplink grant of the first message configuration belongs.

[0181] As an embodiment, the first message includes a field indicating an offset.

[0182] As a sub-embodiment of this embodiment, the offset is used to determine the time interval in the time domain between any two adjacent uplink grants configured by the first message.

[0183] As a sub-embodiment of this embodiment, the offset is the time interval between an end time of an uplink grant configured by the first message and a start time of another uplink grant configured by the first message immediately following the uplink grant.

[0184] As a sub-embodiment of this embodiment, the offset is used to determine the time interval between the time slots occupied by any two adjacent uplink grants configured by the first message.

[0185] As a sub-embodiment of this embodiment, the offset is the time interval between the last time slot occupied by an uplink grant configured by the first message and the first time slot occupied by another uplink grant configured by the first message immediately following the uplink grant.

[0186] As a sub-embodiment of this embodiment, the offset is a non-negative number.

[0187] As a sub-embodiment of this embodiment, the offset is a positive number.

[0188] As a sub-embodiment of this embodiment, the offset is a non-negative integer.

[0189] As a sub-embodiment of this embodiment, the offset is a positive integer.

[0190] As a sub-embodiment of this embodiment, the unit of the offset is a time slot.

[0191] As a sub-embodiment of this embodiment, the unit of the offset is millisecond (ms).

[0192] As a sub-embodiment of this embodiment, the unit of the offset is 0.5 time slots.

[0193] As a sub-embodiment of this embodiment, the unit of the offset is 0.5 milliseconds.

[0194] As an embodiment, the uplink grant configured in the first message is related.

[0195] As an embodiment, at least two uplink grants in the uplink grants configured by the first message are unrelated.

[0196] As an embodiment, the uplink grant configured in the first message is for the same MAC (Medium Access Control) entity.

[0197] As an embodiment, the uplink grant configured in the first message is for the same UL BWP (Bandwidth Part).

[0198] As an embodiment, the uplink grant configured by the first message occupies PUSCH (Physical uplink shared channel) resources.

[0199] As an embodiment, the type of uplink grant configured in the first message is configured grant Type 1.

[0200] As an embodiment, the type of uplink grant configured in the first message is configured grant Type 2.

[0201] As an embodiment, the uplink grant configured by the first message is used for UL-SCH (Uplink Shared Channel) data transmission.

[0202] As an embodiment, the uplink grant configured in the first message belongs to the same CG configuration.

[0203] As an embodiment, there are at least two uplink grants in the uplink grant configured by the first message that belong to the same configuration period.

[0204] As an embodiment, each uplink grant configured by the first message is an uplink grant (UL grant).

[0205] As an embodiment, each uplink grant configured by the first message is part of a UL grant.

[0206] As an embodiment, each uplink grant configured by the first message is a transmission opportunity (Transmission Occasion, TO).

[0207] As an embodiment, each uplink grant configured by the first message is a sending opportunity in a configuration period.

[0208] As an embodiment, each uplink grant configured by the first message is an uplink resource block.

[0209] As an embodiment, each uplink grant configured by the first message is a PUSCH resource.

[0210] As an embodiment, each uplink grant configured by the first message occupies one PUSCH resource.

[0211] As an embodiment, each uplink grant configured by the first message occupies a PUSCH opportunity.

[0212] As an embodiment, each uplink grant configured by the first message corresponds to a PUSCH duration.

[0213] As an embodiment, each uplink grant configured by the first message corresponds to a PUSCH transmission.

[0214] As an embodiment, each uplink grant configured by the first message is configured with an index.

[0215] As a sub-embodiment of this embodiment, the index is unique within a configuration cycle.

[0216] As a sub-embodiment of this embodiment, the index is used to identify an uplink grant within a configuration period.

[0217] As an embodiment, the first message is used to determine a CG configuration, the CG configuration includes at least one configuration cycle, and each configuration cycle in the at least one configuration cycle includes at least one uplink grant.

[0218] As an embodiment, the first message is used to determine at least one CG configuration, each CG configuration in the at least one CG configuration includes at least one configuration cycle, and each configuration cycle in the at least one configuration cycle includes at least one uplink grant.

[0219] As an embodiment, the first message configuration belongs to the uplink grant of the same configuration period.

[0220] As an embodiment, the first message configures at least one configuration period, and each configuration period in the at least one configuration period includes at least one uplink grant.

[0221] As an embodiment, the first message configures the starting time of each configuration cycle.

[0222] As an embodiment, the first message configures the duration of each configuration period.

[0223] As an embodiment, the first message configures the number of transmission opportunities in each configuration period.

[0224] As an embodiment, the first message configures the time interval between adjacent transmission opportunities in each configuration period.

[0225] As an embodiment, each configuration period of the first message configuration includes at least two uplink grants.

[0226] As an embodiment, at least one configuration period configured by the first message includes at least two uplink grants.

[0227] As an embodiment, a configuration cycle is a configuration cycle of a CG.

[0228] As an embodiment, a configuration cycle is a configuration cycle in a CG configuration.

[0229] As an embodiment, uplink grants in a configuration period have the same MCS (Modulation Coding Mode) or at least one of frequency domain resources or PUSCH duration.

[0230] As an embodiment, a configuration period includes at least one uplink grant.

[0231] As an embodiment, the number of uplink grants included in a configuration period is configurable.

[0232] As an embodiment, the number of uplink grants included in a configuration period is predefined.

[0233] As an embodiment, the number of uplink grants included in one configuration period is fixed.

[0234] As an embodiment, the number of uplink grants included in a configuration period is explicitly indicated by an RRC message.

[0235] As an embodiment, the number of uplink grants included in a configuration period is implicitly indicated by an RRC message.

[0236] As an embodiment, two adjacent uplink grants in a configuration period include at least one symbol.

[0237] As an embodiment, no symbol is included between two adjacent uplink grants in a configuration period.

[0238] As an embodiment, at least one symbol is included between any two adjacent configuration periods.

[0239] As an embodiment, any two adjacent configuration periods do not include any symbol.

[0240] As an embodiment, any two uplink grants configured by the first message do not overlap in time, which means that the time domain resources allocated by the first message for the any two uplink grants do not overlap.

[0241] As an embodiment, any two uplink grants configured by the first message do not overlap in time, which means that the PUSCH durations corresponding to the any two uplink grants configured by the first message do not overlap in time.

[0242] As an embodiment, any two uplink grants configured by the first message do not overlap in time, which means that PUSCH resources corresponding to the any two uplink grants configured by the first message do not overlap in time.

[0243] As an embodiment, any two uplink grants configured by the first message do not overlap in time, which means that the time domain resources occupied by the any two uplink grants configured by the first message do not overlap.

[0244] As an embodiment, one of the at least one BSR is a Regular BSR.

[0245] As an embodiment, one of the at least one BSR is a Periodic BSR.

[0246] As an embodiment, one of the at least one BSR is a Padding BSR.

[0247] As an embodiment, one of the at least one BSR is any one of a Regular BSR, a Periodic BSR, or a Padding BSR.

[0248] As an embodiment, one of the at least one BSR is any one of a Regular BSR and a Periodic BSR.

[0249] As an embodiment, the first MAC PDU is a MAC PDU sent after the behavior triggers at least one BSR.

[0250] As an embodiment, the first MAC PDU is the first MAC PDU sent after the behavior triggers at least one BSR.

[0251] As an embodiment, the first MAC PDU is sent on the first uplink grant after a last BSR in the at least one BSR is triggered.

[0252] As an embodiment, the first MAC PDU is sent on the first uplink grant after at least one of the at least one BSR is triggered.

[0253] As an embodiment, when the first MAC PDU is sent on the first uplink grant, the at least one BSR has been triggered and has not been cancelled.

[0254] As an embodiment, when the first MAC PDU is sent on the first uplink grant, the at least one BSR has been triggered and has been cancelled.

[0255] As an embodiment, the behavior of sending the first MAC PDU on the first uplink grant includes: a HARQ entity corresponding to the first uplink grant requests a new transmission for a TB including the first MAC PDU.

[0256] As an embodiment, the act of sending a first MAC PDU on a first uplink grant includes: storing the first uplink grant received from a HARQ entity.

[0257] As an embodiment, the behavior of sending a first MAC PDU on a first uplink grant includes: instructing a physical layer to generate a transmission based on the stored first uplink grant.

[0258] As an embodiment, the first uplink grant is the last uplink grant in a configuration cycle.

[0259] As an embodiment, the first uplink grant is the first uplink grant in a configuration period.

[0260] As an embodiment, the first uplink grant is the first uplink grant for performing uplink transmission in a configuration period.

[0261] As an embodiment, the first uplink grant is any uplink grant in a configuration period.

[0262] As an embodiment, if the first MAC PDU includes a BSR MAC CE, the indication of the buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

[0263] As an embodiment, if the first MAC PDU includes a BSR MAC CE, the indication of the buffer size field in the BSR MAC CE included in the first MAC PDU does not depend on the uplink grant after the first uplink grant.

[0264] As an embodiment, the BSR MAC CE is any one of Long MAC CE, Extended Long MAC CE, Short MAC CE, or Extended Short BSR MAC CE.

[0265] As an embodiment, the BSR MAC CE is any one of Long BSR MAC CE, Extended Long BSR MAC CE, Short BSR MAC CE, Extended Short BSR MAC CE, or the first BSR MAC CE.

[0266] As an embodiment, the BSR MAC CE is any one of at least one of Long BSR MAC CE, Extended Long BSR MAC CE, Short BSR MAC CE, Extended Short BSR MAC CE, and the first BSR MAC CE.

[0267] As an embodiment, the BSR MAC CE is the first BSR MAC CE.

[0268] As an embodiment, the first BSR MAC CE is indicated by a first LCID (Logical Channel ID).

[0269] As an embodiment, the first LCID is the value of the LCID field in the MAC subheader corresponding to the BSR MAC CE.

[0270] As an embodiment, the first LCID is an integer not less than 37 and not greater than 42.

[0271] As an embodiment, the MAC subheader corresponding to the BSR MAC CE includes an LCID field, and the LCID field indicates the first LCID.

[0272] As an embodiment, the first BSR MAC CE is indicated by a first eLCID (extended LCID).

[0273] As an embodiment, the first eLCID is the value of the eLCID field in the MAC subheader corresponding to the BSR MAC CE.

[0274] As an embodiment, the MAC subheader corresponding to the BSR MAC CE includes an LCID field and an eLCID field, the LCID field is set to 34, and the eLCID field indicates the first eLCID.

[0275] As an embodiment, the first eLCID is an integer not less than 0 and not greater than 228.

[0276] As an embodiment, the first eLCID is an integer not less than 200 and not greater than 228.

[0277] As an embodiment, the first eLCID is an integer not less than 210 and not greater than 228.

[0278] As an embodiment, the format of the first BSR MAC CE includes at least one field for indicating a delay budget.

[0279] As an embodiment, the format of the first BSR MAC CE does not include any field for indicating a delay budget.

[0280] As an embodiment, the first BSR MAC CE includes a field indicating a logical channel.

[0281] As an embodiment, the first BSR MAC CE does not include a field indicating a logical channel.

[0282] As an embodiment, the first BSR MAC CE includes a field indicating a logical channel group.

[0283] As an embodiment, the first BSR MAC CE does not include a field indicating a logical channel group.

[0284] As an embodiment, the format of the first BSR MAC CE is the same as the format of Figure 6.1.3.1-2 in 3GPP TS38.321.

[0285] As an embodiment, the format of the first BSR MAC CE is different from the format of Figure 6.1.3.1-2 in 3GPP TS38.321.

[0286] As an embodiment, the first BSR MAC CE includes a buffer size (Buffer Size) field.

[0287] As an embodiment, the second largest buffer size value (BS value) indicated by the buffer size field in the first BSR MAC CE is greater than 81338368 bytes.

[0288] As an embodiment, if the value of the buffer size field in the first BSR MAC CE is 253, the buffer size indicated by the buffer size field in the first BSR MAC CE is greater than 81338368 bytes.

[0289] As an embodiment, the cache size field in the first BSR MAC CE occupies 8 bytes.

[0290] As an embodiment, the cache size field in the first BSR MAC CE occupies 7 bytes.

[0291] As an embodiment, the cache size field in the first BSR MAC CE occupies 6 bytes.

[0292] As an embodiment, the first cache size field in the BSR MAC CE included in the first MAC PDU is set to a first cache size index; the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is not less than the first cache size value; and the first cache size index indicates the first cache size value in the first table.

[0293] As an embodiment, the first cache size field in the BSR MAC CE included in the first MAC PDU is set to a first cache size index; the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1; the first cache size index indicates the first cache size value in the first table.

[0294] As a sub-embodiment of this embodiment, the buffer size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU is not greater than the product of the first buffer size value and M1.

[0295] As a sub-embodiment of this embodiment, if the first table is Table 6.1.3.1-2 in 3GPP TS38.321, the first cache size index is 180, the first cache size value is 824928, and the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is not greater than 824928×M1.

[0296] As a sub-embodiment of this embodiment, the buffer size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU is not greater than the product of the first buffer size value and log2(M1).

[0297] As a sub-embodiment of this embodiment, the buffer size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU is not greater than the first buffer size value plus 2M1 The product of .

[0298] As a sub-embodiment of this embodiment, the first buffer size field is any buffer size field in the first BSR MAC CE.

[0299] As a sub-embodiment of this embodiment, the first cache size field is the cache size field corresponding to the first LCG in the first BSR MAC CE; the first LCG is configured with the M1.

[0300] As a sub-embodiment of this embodiment, the first buffer size field is the buffer size field corresponding to the first logical channel in the first BSR MAC CE; the first logical channel is configured with the M1.

[0301] As a sub-embodiment of this embodiment, the M1 is configurable.

[0302] As a sub-embodiment of this embodiment, the M1 is predefined.

[0303] As a sub-embodiment of this embodiment, the M1 is variable.

[0304] As a sub-embodiment of this embodiment, M1 is fixed.

[0305] As a sub-embodiment of this embodiment, M1 is a positive number.

[0306] As a sub-embodiment of this embodiment, M1 is a positive integer.

[0307] As a sub-embodiment of this embodiment, M1 is greater than 1.

[0308] As a sub-embodiment of this embodiment, M1 is less than 1.

[0309] As a sub-embodiment of this embodiment, the RRC message configures the M1. As an embodiment, the above method avoids adding a new field in the BSR MAC CE, reducing the impact on the existing protocol.

[0310] As a sub-embodiment of this embodiment, the M1 is configured to the first MAC entity.

[0311] As a sub-embodiment of this embodiment, a field in a MAC-CellGroupConfig IE indicates the M1.

[0312] As a sub-embodiment of this embodiment, the M1 is configured to the first logical channel.

[0313] As a sub-embodiment of this embodiment, a field in a LogicalChannelConfig IE indicates the M1.

[0314] As a sub-embodiment of this embodiment, the M1 is configured to the first LCG.

[0315] As a sub-embodiment of this embodiment, a MAC-CellGroupConfig IE indicates the first LCG and the M1.

[0316] As a sub-embodiment of this embodiment, the RRC message indicates K1 values, M1 is one of the K1 values; and K1 is a positive integer.

[0317] As a sub-embodiment of this embodiment, one MAC-CellGroupConfig IE indicates the K1 values.

[0318] As a sub-embodiment of this embodiment, the K1 values ​​are respectively configured to K1 LCGs, and the first LCG is one of the K1 LCGs.

[0319] As a sub-embodiment of this embodiment, K1 is variable.

[0320] As a sub-embodiment of this embodiment, the above method configures a scaling value for LCG, which is more flexible.

[0321] As a sub-embodiment of this embodiment, the maximum value of K1 is maxLCG-ID+1.

[0322] As a sub-embodiment of this embodiment, the maximum value of K1 is 7.

[0323] As a sub-embodiment of this embodiment, K1 is fixed.

[0324] As a sub-embodiment of this embodiment, the above method avoids indication errors caused by signaling interaction.

[0325] As a sub-embodiment of this embodiment, a field in the BSR MAC CE included in the first MAC PDU indicates the M1; the BSR MAC CE included in the first MAC PDU is the first BSR MAC CE.

[0326] As a sub-embodiment of this embodiment, the above method makes BSR reporting more flexible.

[0327] As an embodiment, the first cache size index is a cache size index in the first table.

[0328] As an embodiment, the first cache size index is an index in the first table.

[0329] As an embodiment, the first buffer size index is a buffer size level.

[0330] As an embodiment, the first cache size index is an index corresponding to the first cache size value in the first table.

[0331] As an embodiment, the first table includes 256 indexes.

[0332] As an embodiment, the first table includes 32 indexes.

[0333] As an embodiment, at least one index in the first table is reserved.

[0334] As an embodiment, any index in the first table is not reserved.

[0335] As an embodiment, the first cache size value is a cache size value in the first table.

[0336] As an embodiment, the BSR MAC CE included in the first MAC PDU is the first BSR MAC CE.

[0337] As an embodiment, the BSR MAC CE included in the first MAC PDU is a Long BSR MAC CE.

[0338] As an embodiment, the BSR MAC CE included in the first MAC PDU is an Extended Long BSR MAC CE.

[0339] As an embodiment, the BSR MAC CE included in the first MAC PDU is a Short BSR MAC CE.

[0340] As an embodiment, the BSR MAC CE included in the first MAC PDU is an Extended Short BSR MAC CE.

[0341] As an embodiment, the value of the first buffer size field in the BSR MAC CE included in the first MAC PDU is an index, and the index indicates a buffer size value.

[0342] As an embodiment, the buffer size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU is determined by looking up a table.

[0343] As an embodiment, the first table is a newly introduced table in 3GPP TS38.321.

[0344] As an embodiment, the above method avoids other problems caused by dynamic configuration of tables.

[0345] As an embodiment, the above method reduces protocol impact.

[0346] As an embodiment, the first table is Table 6.1.3.1-1 in 3GPP TS38.321.

[0347] As an embodiment, the first table is Table 6.1.3.1-2 in 3GPP TS38.321.

[0348] As an embodiment, the above method avoids introducing a new table.

[0349] As an embodiment, the above method makes the table configurable and more flexible.

[0350] As an embodiment, the phrase “the first condition set is related to an uplink grant subsequent to the first uplink grant” means that the first condition set is related to a size of the uplink grant subsequent to the first uplink grant.

[0351] As an embodiment, the phrase “the first condition set is related to uplink grants subsequent to the first uplink grant” means that the first condition set is related to the number of uplink grants subsequent to the first uplink grant.

[0352] As an embodiment, the phrase “the first condition set is related to an uplink grant subsequent to the first uplink grant” means that the first condition set is related to a position of the uplink grant in a configuration period to which the first uplink grant belongs.

[0353] As an embodiment, the phrase “the first condition set is related to an uplink grant subsequent to the first uplink grant” means that the first condition set is related to the first uplink grant and the uplink grant subsequent to the first uplink grant.

[0354] As an embodiment, the phrase “the first condition set is related to an uplink grant subsequent to the first uplink grant” means that the first condition set is related to the sum of the sizes of the first uplink grant and the uplink grant subsequent to the first uplink grant.

[0355] As an embodiment, the phrase "the first condition set is related to the uplink grant after the first uplink grant" means: the first condition set is related to the position of the uplink grant in the configuration period to which the first uplink grant belongs; and the uplink grant after the first uplink grant belongs to the configuration period to which the first uplink grant belongs.

[0356] As a sub-embodiment of this embodiment, when the first uplink grant is the first uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is satisfied; when the first uplink grant is not the first uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is not satisfied.

[0357] As a sub-embodiment of this embodiment, when the first uplink grant is the last uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is satisfied; when the first uplink grant is not the last uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is not satisfied.

[0358] As an embodiment, the phrase “the first condition set is related to an uplink grant subsequent to the first uplink grant” means that the first condition set is related to the number of the uplink grants subsequent to the first uplink grant and a first integer.

[0359] As a sub-embodiment of this embodiment, when the number of uplink grants after at least the first uplink grant is greater than a first integer, the first condition set is satisfied; when the number of uplink grants after at least the first uplink grant is less than the first integer, the first condition set is not satisfied.

[0360] As a sub-embodiment of this embodiment, the first condition set is satisfied when the number of the uplink grants after at least the first uplink grant is equal to a first integer.

[0361] As a sub-embodiment of this embodiment, when the number of the uplink grants after at least the first uplink grant is equal to a first integer, the first condition set is not satisfied.

[0362] As a sub-embodiment of this embodiment, the first integer is configurable.

[0363] As a sub-embodiment of this embodiment, the first integer is predefined.

[0364] As an embodiment, the phrase "the first condition set is related to the uplink grant after the first uplink grant" means: the first condition set is related to the position of the first uplink grant in the configuration period to which the first uplink grant belongs; and the uplink grant after the first uplink grant belongs to the configuration period to which the first uplink grant belongs.

[0365] As a sub-embodiment of this embodiment, when the first uplink grant is the first uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is satisfied; when the first uplink grant is not the first uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is not satisfied.

[0366] As a sub-embodiment of this embodiment, when the first uplink grant is not the first uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is satisfied; when the first uplink grant is the first uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is not satisfied.

[0367] As a sub-embodiment of this embodiment, when the first uplink grant is the last uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is satisfied; when the first uplink grant is not the last uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is not satisfied.

[0368] As a sub-embodiment of this embodiment, when the first uplink grant is not the last uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is satisfied; when the first uplink grant is the last uplink grant in the configuration period to which the first uplink grant belongs, the first condition set is not satisfied.

[0369] As an embodiment, the phrase "the first condition set is related to the uplink grant after the first uplink grant" means that the first condition set is related to whether the first uplink grant and the uplink grant after the first uplink grant can accommodate all pending data available for transmission.

[0370] As a sub-embodiment of this embodiment, the first condition set is satisfied when at least the first uplink grant and the uplink grant after the first uplink grant can accommodate all pending data available for transmission; the first condition set is not satisfied when the first uplink grant and the uplink grant after the first uplink grant cannot accommodate all pending data available for transmission.

[0371] As an embodiment, the phrase that the first condition set is related to the uplink grant after the first uplink grant means that the first condition set is related to whether the uplink grant after the first uplink grant can accommodate the remaining pending data available for transmission.

[0372] As a sub-embodiment of this embodiment, the first condition set is satisfied when at least the uplink grant after the first uplink grant can accommodate the remaining pending data available for transmission; when the uplink grant after the first uplink grant cannot accommodate the remaining pending data available for transmission, the first condition set is not satisfied.

[0373] As an embodiment, the phrase "the first condition set is related to the uplink grant after the first uplink grant" means that: the first condition set is related to whether the first uplink grant and the uplink grant after the first uplink grant can accommodate all pending data available for transmission and cannot accommodate the BSR MAC CE plus its sub-header.

[0374] As a sub-embodiment of this embodiment, the first condition set is satisfied when at least the first uplink grant and the uplink grant after the first uplink grant can accommodate all pending data available for transmission and cannot accommodate the BSR MAC CE plus its sub-header; the first condition set is not satisfied when the first uplink grant and the uplink grant after the first uplink grant cannot accommodate all pending data available for transmission or the first uplink grant and the uplink grant after the first uplink grant can accommodate all pending data available for transmission and can accommodate the BSR MAC CE plus its sub-header.

[0375] As an embodiment, the uplink grant after the first uplink grant belongs to the same CG configuration of the first message configuration.

[0376] As an embodiment, the uplink grant after the first uplink grant belongs to at least one CG configuration of the first message configuration.

[0377] As an embodiment, the uplink grant following the first uplink grant is an adjacent uplink grant configured by the first message.

[0378] As an embodiment, there is no uplink grant configured by the first message between two uplink grants that are adjacent in the time domain in the uplink grant after the first uplink grant.

[0379] As an embodiment, the configured indexes of the uplink grants after the first uplink grant are continuous.

[0380] As an embodiment, the uplink grant following the first uplink grant is not an adjacent uplink grant configured by the first message.

[0381] As an embodiment, there is at least one uplink grant configured by the first message between two consecutive uplink grants in the uplink grant after the first uplink grant.

[0382] As an embodiment, the indexes configured for the uplink grants after the first uplink grant are not continuous.

[0383] As an embodiment, the uplink grants after the first uplink grant belong to the same configuration period.

[0384] As a sub-embodiment of this embodiment, the same configuration period is configured by the first message.

[0385] As a sub-embodiment of this embodiment, the same configuration period includes the first uplink grant.

[0386] As an embodiment, the uplink grant after the first uplink grant belongs to at least one configuration period.

[0387] As a sub-embodiment of this embodiment, the at least one configuration period is configured by the first message.

[0388] As a sub-embodiment of this embodiment, one configuration cycle in the at least one configuration cycle includes the first uplink grant.

[0389] As a sub-embodiment of this embodiment, the at least one configuration cycle is one configuration cycle.

[0390] As a sub-embodiment of this embodiment, the at least one configuration cycle is multiple configuration cycles, and the multiple configuration cycles are continuous.

[0391] As a sub-embodiment of this embodiment, the at least one configuration cycle is a plurality of configuration cycles, and the plurality of configuration cycles are not continuous.

[0392] As an embodiment, the uplink grant after the first uplink grant belongs to a maximum of Q1 configuration periods; Q1 is a positive integer.

[0393] As a sub-embodiment of this embodiment, Q1 is predefined.

[0394] As a sub-embodiment of this embodiment, Q1 is configurable.

[0395] As a sub-embodiment of this embodiment, Q1 is fixed.

[0396] As a sub-embodiment of this embodiment, Q1 is 2.

[0397] As a sub-embodiment of this embodiment, Q1 is 1.

[0398] As a sub-embodiment of this embodiment, the Q1 configuration periods are adjacent.

[0399] As an embodiment, the number of uplink grants after the first uplink grant is indicated by an RRC message.

[0400] As an embodiment, the number of uplink grants after the first uplink grant is explicitly indicated by an RRC message.

[0401] As an embodiment, the number of uplink grants after the first uplink grant is implicitly indicated by an RRC message.

[0402] As an embodiment, the number of uplink grants after the first uplink grant is fixed.

[0403] As an embodiment, the number of uplink grants after the first uplink grant is a default number.

[0404] As an embodiment, the number of the uplink grants after the first uplink grant is predefined.

[0405] As an embodiment, the number of uplink grants after the first uplink grant depends on the number of bits occupied by the first bitmap in the first control information.

[0406] As an embodiment, the number of the uplink grants after the first uplink grant depends on the uplink grant that is later than the first uplink grant in the time domain in the configuration period to which the first uplink grant belongs.

[0407] As an embodiment, any uplink grant among the uplink grants subsequent to the first uplink grant is later in time than the first uplink grant.

[0408] As an embodiment, any uplink grant among the uplink grants after the first uplink grant belongs to a given time interval in the time domain.

[0409] As a sub-embodiment of this embodiment, the length of the given time interval is semi-statically configured.

[0410] As a sub-embodiment of this embodiment, the length of the given time interval changes dynamically.

[0411] As a sub-embodiment of this embodiment, the given time interval is configured by RRC.

[0412] As a sub-embodiment of this embodiment, the given time interval is predefined.

[0413] As a sub-embodiment of this embodiment, the given time interval is a positive integer number of milliseconds.

[0414] As a sub-embodiment of this embodiment, the given time interval is a positive integer number of sending cycles.

[0415] As a sub-embodiment of this embodiment, the sending period is the time interval between two adjacent uplink grants in a configuration period.

[0416] As a sub-embodiment of this embodiment, the given time interval is a positive integer number of configuration cycles.

[0417] As a sub-embodiment of this embodiment, the starting moment of the given time interval is related to the time domain position of the first uplink grant.

[0418] As a sub-embodiment of this embodiment, the starting moment of the given time interval is the starting moment of the time domain position of the first uplink grant.

[0419] As a sub-embodiment of this embodiment, the starting time of the given time interval is the ending time of the time domain position of the first uplink grant.

[0420] As a sub-embodiment of this embodiment, the starting moment of the given time interval is a moment X1 symbols after the end moment of the time domain position of the first uplink grant; the X1 is predefined, or the X1 is preconfigured.

[0421] As a sub-embodiment of this embodiment, the given time interval is the time interval between the first uplink grant and the last uplink grant in the configuration period to which the first uplink grant belongs.

[0422] As an embodiment, any uplink grant among the uplink grants after the first uplink grant is a valid uplink grant.

[0423] As a sub-embodiment of this embodiment, the valid uplink grant is an uplink grant that at least does not overlap with the first symbol set.

[0424] As a sub-embodiment of this embodiment, the valid uplink grant is an uplink grant that at least belongs to the given time interval.

[0425] As a sub-embodiment of this embodiment, the valid uplink grant is an uplink grant that is later than the first uplink grant at least in the time domain.

[0426] As a sub-embodiment of this embodiment, the valid uplink grant is an uplink grant that at least belongs to the given time interval and does not overlap with the first symbol set.

[0427] As a sub-embodiment of this embodiment, the valid uplink grant is an uplink grant that is later than the first uplink grant at least in the time domain and does not overlap with the first set of symbols.

[0428] As a sub-embodiment of this embodiment, the valid uplink grant is an uplink grant that is later than the first uplink grant at least in the time domain, belongs to the given time interval, and does not overlap with the first set of symbols.

[0429] As an embodiment, all the data to be processed and available for transmission are the data available for transmission when the first uplink is granted to be transmitted.

[0430] As an embodiment, all the data to be processed and available for transmission are the data available for transmission when processing the first uplink grant.

[0431] As an embodiment, the remaining data to be processed and available for transmission is the data remaining after removing the data sent on the first uplink grant from all the data to be processed and available for transmission.

[0432] As an embodiment, the remaining data to be processed and available for transmission is the data remaining after removing the data sent on the first uplink grant from all the data to be processed and available for transmission when processing the first uplink grant.

[0433] As an embodiment, the processing of the first uplink grant includes: performing a HARQ operation on the first uplink grant.

[0434] As an embodiment, the processing of the first uplink grant includes: performing a multiplexing and assembly process for the first uplink grant.

[0435] As an embodiment, the processing of the first uplink grant includes: performing an LCP (Logical Channel Prioritization) process for the first uplink grant.

[0436] As an embodiment, this embodiment does not limit the specific time of processing the first uplink grant.

[0437] As an embodiment, all the data to be processed and available for transmission include a set of data packets.

[0438] As an embodiment, all the data to be processed and available for transmission include data packet sets and data packets.

[0439] As an embodiment, the remaining data to be processed and available for transmission includes a set of data packets.

[0440] As an embodiment, the remaining data to be processed and available for transmission includes a data packet set and a data packet.

[0441] As an embodiment, one of the at least one BSR is triggered by at least a set of data packets.

[0442] As an embodiment, one of the at least one BSR is triggered by at least a set of data packets.

[0443] As an embodiment, one of the at least one BSR is triggered by uplink data for a logical channel that becomes available to the MAC entity.

[0444] As an embodiment, one of the at least one BSR is triggered by expiration of retxBSR-Timer.

[0445] As an embodiment, one of the at least one BSR is triggered by expiration of a periodicBSR-Timer.

[0446] As an embodiment, at least two data packets in a data packet set have a dependency relationship.

[0447] As an embodiment, any two data packets in a data packet set have a dependency relationship.

[0448] As an embodiment, a data packet set includes at least one data packet.

[0449] As an embodiment, a data packet set includes multiple data packets.

[0450] As an embodiment, a data packet set includes a finite number of data packets.

[0451] As an embodiment, a data packet set is a PDU set.

[0452] As an embodiment, a data packet set is associated with a PDCP (Packet Data Convergence Protocol) entity.

[0453] As an embodiment, a data packet set is associated with multiple PDCP entities.

[0454] As an embodiment, a data packet set is not associated with multiple PDCP entities.

[0455] As an embodiment, a data packet set is associated with only one DRB (Data Radio Bearer).

[0456] As an embodiment, a set of data packets is associated with multiple DRBs.

[0457] As an embodiment, a set of data packets is associated with one or more DRBs.

[0458] As an embodiment, all data packets in a data packet set belong to the same LCG.

[0459] As an embodiment, any two data packets in a data packet set belong to different LCGs.

[0460] As an embodiment, there are two data packets in a data packet set that belong to different LCGs.

[0461] As an embodiment, any two data packets in a data packet set belong to the same LCG.

[0462] As an embodiment, any two data packets in a data packet set belong to the same logical channel of the same LCG.

[0463] As an embodiment, any two data packets in a data packet set belong to different logical channels of the same LCG.

[0464] In one embodiment, at least one data packet in a data packet set is a buffered data packet.

[0465] In one embodiment, each data packet in a data packet set is a buffered data packet.

[0466] In one embodiment, at least one data packet in a data packet set is an expected data packet.

[0467] In one embodiment, each data packet in a data packet set is an expected data packet.

[0468] As an embodiment, a data packet in a data packet set is a PDU.

[0469] As an embodiment, a data packet in a data packet set is a payload of a PDU.

[0470] As an embodiment, a data packet in a data packet set is a data packet of the PDCP sublayer.

[0471] As an embodiment, a data packet in a data packet set is a PDCP PDU.

[0472] As an embodiment, a data packet in a data packet set is a PDCP SDU.

[0473] As an embodiment, a data packet in a data packet set is a data packet of the RLC sublayer.

[0474] As an embodiment, a data packet in a data packet set is an RLC PDU.

[0475] As an embodiment, a data packet in a data packet set is an RLC SDU.

[0476] As an embodiment, a data packet in a data packet set is an RLC SDU segment.

[0477] As an embodiment, each data packet in a data packet set corresponds to a given identifier.

[0478] As an embodiment, each data packet in a data packet set is configured with a given identifier.

[0479] As an embodiment, each data packet in a data packet set is indicated with a given identifier.

[0480] As an embodiment, each data packet in a data packet set is marked with a given identifier.

[0481] Example 1B

[0482] Example 1B illustrates a flowchart of the transmission of a first message and first control information according to an embodiment of the present application, as shown in FIG1B . In FIG1B , each box represents a step, and it is particularly important to emphasize that the order of the boxes in the figure does not represent the temporal sequence of the steps represented.

[0483] In embodiment 1B, the first node in the present application receives a first message in step 101B, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; in step 102B, first control information is sent on the first uplink grant, wherein the first control information indicates whether at least one uplink grant after the first uplink grant is not used; in step 103B, for one uplink grant among the at least one uplink grant after the first uplink grant, whether to restart the first timer is determined according to the indication of the one uplink grant by the first control information; wherein the behavior of determining whether to restart the first timer according to the indication of the one uplink grant by the first control information includes: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; expiration of the first timer is used to trigger a BSR; the first uplink grant and the at least one uplink grant after the first uplink grant are configured by the first message.

[0484] As an embodiment, the behavior of determining whether to restart the first timer based on the indication of the first control information for the uplink grant includes: when the first control information indicates that the uplink grant is not used, the first timer is not restarted.

[0485] As an embodiment, a first MAC PDU is sent on the first uplink grant.

[0486] As an embodiment, the first MAC PDU includes at least one of a MAC SDU (Service Data Unit), a MAC CE, a MAC subheader, or padding.

[0487] As an embodiment, whether the first MAC PDU includes BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include BSR MAC CE; when the first condition set is not met, the first MAC PDU includes BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message; before the first MAC PDU is sent, at least one BSR is triggered.

[0488] As an embodiment, whether the first MAC PDU includes the BSR MAC CE does not depend on whether the first condition set is met.

[0489] Example 1C

[0490] Example 1C illustrates a flowchart of the transmission of a first message and a first MAC PDU according to an embodiment of the present application, as shown in Figure 1C. In Figure 1C, each box represents a step. It is particularly important to emphasize that the order of the boxes in the figure does not represent the temporal sequence of the steps represented.

[0491] In Example 1C, the first node in the present application receives a first message in step 101B, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; in step 102B, at least one BSR is triggered; in step 103B, after the behavior triggers at least one BSR, a first MAC PDU is sent on the first uplink grant, where the first MAC PDU includes a BSR MAC CE.

[0492] As an embodiment, the indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0493] As an embodiment, the phrase "the indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant" means that the size of the uplink grant after removing at least the first uplink grant from the total amount of available data obtained according to the data amount calculation process in 3GPP TS 38.322 and 3GPP TS 38.323 is used to determine the cache size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU.

[0494] As an embodiment, the phrase "the indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant" means that after the first MAC PDU has been constructed, the size of the uplink grant after removing at least the first uplink grant from the total amount of available data of all logical channels of an LCG obtained according to the data volume calculation process in 3GPP TS 38.322 and 3GPP TS 38.323 is used to determine the buffer size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU.

[0495] As an embodiment, the phrase "the indication of the first buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant" means that after the first MAC PDU has been constructed, the size of the uplink grant after removing at least the first uplink grant from the total amount of available data of at least one logical channel obtained according to the data amount calculation process in 3GPP TS 38.322 and 3GPP TS 38.323 is used to determine the buffer size value indicated by the first buffer size field in the BSR MAC CE included in the first MAC PDU.

[0496] As an embodiment, the first cache size field in the BSR MAC CE included in the first MAC PDU is set to a first cache size index; the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1; the first cache size index indicates the first cache size value in the first table.

[0497] As an embodiment, the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1, or the indication of the first cache size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

[0498] As an embodiment, the cache size value indicated by the first cache size field in the BSR MAC CE included in the first MAC PDU is related to the first cache size value and M1, and the indication of the first cache size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

[0499] Example 2

[0500] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in FIG2 . FIG2 illustrates a network architecture 200 of a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system. The 5G NR / LTE / LTE-A network architecture 200 may be referred to as a 5G System (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5G Core Network (5G Core Network) / EPC (Evolved Packet Core) 210, a Home Subscriber Server (HSS) / UDM (Unified Data Management) 220, and an Internet service 230. 5GS / EPS can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmitter / receiver node), or some other appropriate terminology. Node 203 provides an access point to the 5GC / EPC 210 for UE 201. Examples of UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device.Those skilled in the art may also refer to UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term. Node 203 is connected to 5GC / EPC 210 via an S1 / NG interface. 5GC / EPC 210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. MME / AMF / SMF 211 is a control node that handles signaling between UE 201 and 5GC / EPC 210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF 212, which is itself connected to P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. P-GW / UPF 213 is connected to Internet Services 230. Internet Services 230 includes operator-specific Internet Protocol services, specifically the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

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

[0502] As an embodiment, the UE 201 is a user equipment (UE).

[0503] As an embodiment, the UE 201 is a base station (BS).

[0504] As an embodiment, the UE 201 is a relay device.

[0505] As an embodiment, the UE 201 is a gateway device.

[0506] As an embodiment, the node 203 corresponds to the second node in this application.

[0507] As an embodiment, the node 203 is a base station device.

[0508] As an embodiment, the node 203 is a user equipment.

[0509] As an embodiment, the node 203 is a relay device.

[0510] As an embodiment, the node 203 is a gateway device.

[0511] Typically, the UE 201 is a user equipment, and the node 203 is a base station device.

[0512] Typically, the UE 201 is a user equipment, and the node 203 is a user equipment.

[0513] Typically, the UE 201 is a base station device, and the node 203 is a base station device.

[0514] As an embodiment, the user equipment supports transmission of a non-terrestrial network (NTN).

[0515] As an embodiment, the user equipment supports transmission via a terrestrial network (Terrestrial Network).

[0516] As an embodiment, the user equipment supports dual connection (DC) transmission.

[0517] As an embodiment, the user equipment includes an aircraft.

[0518] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0519] As an embodiment, the user equipment includes a vessel.

[0520] As an embodiment, the user equipment includes an Internet of Things terminal.

[0521] As an embodiment, the user equipment includes a terminal of the Industrial Internet of Things.

[0522] As an embodiment, the user equipment includes a device that supports low-latency and high-reliability transmission.

[0523] As an embodiment, the user equipment includes a test device.

[0524] As an embodiment, the user equipment includes a signaling tester.

[0525] As an embodiment, the user equipment includes an IAB (Integrated Access and Backhaul)-MT (Mobile Termination).

[0526] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0527] As an embodiment, the base station device supports transmission of a terrestrial network.

[0528] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0529] As an embodiment, the base station device includes a Node B (NB).

[0530] As an embodiment, the base station device includes a gNB.

[0531] As an embodiment, the base station device includes an eNB.

[0532] As an embodiment, the base station device includes ng-eNB.

[0533] As an embodiment, the base station device includes an en-gNB.

[0534] As an embodiment, the base station device includes a CU (Centralized Unit).

[0535] As an embodiment, the base station device includes a DU (Distributed Unit).

[0536] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

[0537] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.

[0538] As an embodiment, the base station device includes a micro cell base station.

[0539] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0540] As an embodiment, the base station device includes a home base station (Femtocell).

[0541] As an embodiment, the base station device includes a flying platform device.

[0542] As an embodiment, the base station device includes a satellite device.

[0543] As an embodiment, the base station device includes a testing device.

[0544] As an embodiment, the base station equipment includes a signaling tester.

[0545] As an embodiment, the base station device includes a gateway device.

[0546] As an embodiment, the base station device includes an IAB-node.

[0547] As an embodiment, the base station device includes an IAB-donor.

[0548] As an embodiment, the base station device includes an IAB-donor-CU.

[0549] As an embodiment, the base station device includes an IAB-donor-DU.

[0550] As an embodiment, the base station device includes an IAB-DU.

[0551] As an embodiment, the base station device includes an IAB-MT.

[0552] As an embodiment, the relay device includes a relay.

[0553] As an embodiment, the relay device includes an L3 relay.

[0554] As an embodiment, the relay device includes an L2 relay.

[0555] As an embodiment, the relay device includes a router.

[0556] As an embodiment, the relay device includes a switch.

[0557] As an embodiment, the relay device includes a gateway device.

[0558] As an embodiment, the relay device includes user equipment.

[0559] As an embodiment, the relay device includes a base station device.

[0560] Example 3

[0561] Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in FIG3 . FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 illustrates the radio protocol architecture for the control plane 300 using 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 herein as PHY 301. Layer 2 (L2 layer) 305 is above PHY 301 and includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets and supports inter-zone mobility. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling. The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture in the user plane 350 is generally identical to the corresponding layers and sublayers in the control plane 300, including 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. However, the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping QoS flows to data radio bearers (DRBs) to support service diversity.

[0562] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the first node in this application.

[0563] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the second node in this application.

[0564] As an embodiment, the first message in this application is generated in the RRC306.

[0565] As an embodiment, the first message in the present application is generated by the MAC302 or MAC352.

[0566] As an embodiment, the first message in this application is generated by the PHY301 or PHY351.

[0567] As an embodiment, the first MAC PDU in the present application is generated in the RRC306.

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

[0569] As an embodiment, the first control information in this application is generated in the RRC306.

[0570] As an embodiment, the first control information in this application is generated by the MAC302 or MAC352.

[0571] Example 4

[0572] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in Figure 4. 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.

[0573] 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 .

[0574] The second communication device 410 includes a controller / processor 475 , a memory 476 , 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 .

[0575] During transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to the controller / processor 475 at the second communication device 410. The controller / processor 475 implements L2 layer functionality. During 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 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), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming 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 and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier 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.

[0576] During 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 via 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, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a fast Fourier transform (FFT). In the frequency domain, the receive processor 456 demultiplexes the physical layer data signal and reference signal, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive 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 code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the core network. 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 layer for L3 processing.

[0577] During transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission functionality 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 based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 457, the stream is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a RF symbol stream before providing it to the antenna 452.

[0578] During transmission from the first communications device 450 to the second communications device 410, the functionality at the second communications device 410 is similar to the reception functionality at the first communications device 450 described for transmission from the second communications device 410 to the first communications device 450. Each receiver 418 receives RF signals via its corresponding antenna 420, converts the received RF signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement L1 layer functionality. A controller / processor 475 implements L2 layer functionality. The controller / processor 475 may be associated with a memory 476 storing program codes and data. The memory 476 may be referred to as a computer-readable medium. During transmission from the first communications device 450 to the second communications device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0579] As an embodiment, the first communication device 450 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 at least: receives a first message, the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; triggers at least one BSR; after the behavior triggers at least one BSR, sends a first MAC PDU on the first uplink grant; wherein, whether the first MAC PDU includes a BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include a BSR MAC CE; when the first condition set is not met, the first MAC PDU includes a BSR MAC CE; the first condition set is related to an uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0580] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receiving a first message, the first message configuring an uplink grant, any two uplink grants configured by the first message not overlapping in time; triggering at least one BSR; after the behavior triggers at least one BSR, sending a first MAC PDU on the first uplink grant; wherein, whether the first MAC PDU includes a BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include a BSR MAC CE; when the first condition set is not met, the first MAC PDU includes a BSR MAC CE; the first condition set is related to an uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0581] As an embodiment, the second communication device 410 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 with the at least one processor. The second communication device 410 at least: sends a first message, the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; receives a first MAC PDU on the first uplink grant; wherein the first MAC PDU is sent after at least one BSR is triggered; whether the first MAC PDU includes a BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include a BSR MAC CE; when the first condition set is not met, the first MAC PDU includes a BSR MAC CE; the first condition set is related to an uplink grant subsequent to the first uplink grant; the first uplink grant and the uplink grant subsequent to the first uplink grant are configured by the first message.

[0582] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: sending a first message, the first message configuring an uplink grant, any two uplink grants configured by the first message not overlapping in time; receiving a first MAC PDU on the first uplink grant; wherein, the first MAC PDU is sent after at least one BSR is triggered; whether the first MAC PDU includes a BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include a BSR MAC CE; when the first condition set is not met, the first MAC PDU includes a BSR MAC CE; the first condition set is related to an uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0583] As an embodiment, at least one of the antenna 452 , the receiver 454 , the reception processor 456 , and the controller / processor 459 is used to receive a first message.

[0584] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first message.

[0585] As an embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, and the controller / processor 459 is used to trigger at least one BSR.

[0586] As an embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, and the controller / processor 459 is used to cancel the triggered BSR.

[0587] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to transmit a first MAC PDU.

[0588] As an embodiment, at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller / processor 475 is used to receive a first MAC PDU.

[0589] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to send first control information.

[0590] As an embodiment, at least one of the antenna 420, the receiver 418, the reception processor 470, and the controller / processor 475 is configured to receive first control information.

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

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

[0593] As an embodiment, the first communication device 450 is a user equipment.

[0594] As an embodiment, the first communication device 450 is a base station device.

[0595] As an embodiment, the first communication device 450 is a relay device.

[0596] As an embodiment, the second communication device 410 is a user equipment.

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

[0598] As an embodiment, the second communication device 410 is a relay device.

[0599] Example 5

[0600] Example 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in FIG5. It should be noted that the order in this example does not limit the signal transmission order and implementation order in the present application.

[0601] For the first node U01, in step S5101, a first message is received, the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; in step S5102, at least one BSR is triggered; in step S5103, whether a first condition set is satisfied is determined; when the first condition set is satisfied, step S5105(a) is executed; when the first condition set is not satisfied, step S5105(b) is executed; in step S5105(a), after the behavior triggers at least one BSR, a first MAC PDU is sent on the first uplink grant, the first MAC PDU does not include a BSR MAC CE; in step S5105(b), after the behavior triggers at least one BSR, a first MAC PDU is sent on the first uplink grant, the first MAC PDU includes a BSR MAC CE CE; in step S5104, when the first condition set is met, cancel the triggered BSR; in step S5106, send first control information on the first uplink grant, the first control information indicating whether at least one uplink grant after the first uplink grant is not used.

[0602] For the second node N02, in step S5201, the first message is sent; in step S5202(a), the first MAC PDU is received, and the first MAC PDU does not include BSR MAC CE; in step S5202(b), the first MAC PDU is received, and the first MAC PDU includes BSR MAC CE; in step S5203, the first control information is received.

[0603] In embodiment 5, whether the first MAC PDU includes BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include BSR MAC CE; when the first condition set is not met, the first MAC PDU includes BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0604] As an embodiment, the first node U01 is a user equipment.

[0605] As an embodiment, the first node U01 is a base station device.

[0606] As an embodiment, the first node U01 is a relay device.

[0607] As an embodiment, the second node N02 is a base station device.

[0608] As an embodiment, the second node N02 is a user equipment.

[0609] As an embodiment, the second node N02 is a relay device.

[0610] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a base station device.

[0611] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0612] As an embodiment, the first node U01 is a base station device, and the second node N02 is a base station device.

[0613] As an embodiment, the first node U01 and the second node N02 are connected wirelessly.

[0614] As an embodiment, the first node U01 and the second node N02 are connected via a wired connection.

[0615] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0616] As an embodiment, the first node U01 and the second node N02 are connected via an IAB port.

[0617] As an embodiment, the first node U01 and the second node N02 are connected via a PC5 interface.

[0618] As an embodiment, only one of the dashed box F5.1 and the dashed box F5.2 exists.

[0619] As an embodiment, the dotted box F5.1 exists, and the dotted box F5.2 does not exist.

[0620] As a sub-embodiment of this embodiment, step S5104(a) exists.

[0621] As a subsidiary embodiment of this sub-embodiment, the above method reduces the sending of BSR MAC CE and saves resources.

[0622] As a subsidiary embodiment of this sub-embodiment, the behavior of canceling the triggered BSR refers to: canceling all triggered BSRs.

[0623] As a subsidiary embodiment of this sub-embodiment, the behavior of canceling the triggered BSR refers to: canceling the at least one triggered BSR.

[0624] As a subsidiary embodiment of this sub-embodiment, if step S5104(a) is executed, step S5105(a) is executed.

[0625] As a sub-embodiment of this embodiment, step S5104(a) does not exist.

[0626] As a subsidiary embodiment of this sub-embodiment, the above method can send the BSR MAC CE in time after the first uplink grant.

[0627] As an embodiment, the dotted box F5.1 does not exist, and the dotted box F5.2 exists.

[0628] As a sub-embodiment of this embodiment, after step S5105(b), if the BSR MAC CE in the first MAC PDU includes a cache status up to (including) the last event that triggered the BSR before the first MAC PDU was assembled, all BSRs triggered before the first MAC PDU was assembled are canceled.

[0629] As a sub-embodiment of this embodiment, after step S5105(b), even if the BSR MAC CE in the first MAC PDU includes a cache status up to (including) the last event that triggered the BSR before the first MAC PDU was assembled, the triggered BSR is not canceled.

[0630] As a sub-embodiment of this embodiment, the above method can update the cache status in time after the first uplink grant.

[0631] As an embodiment, the dotted box F5.3 exists.

[0632] As a sub-embodiment of this embodiment, first control information is sent on the first uplink grant, where the first control information indicates whether at least one uplink grant after the first uplink grant is not used.

[0633] As a sub-embodiment of this embodiment, the first control information is transmitted on a physical layer channel corresponding to the first uplink grant.

[0634] As a sub-embodiment of this embodiment, the first control information is multiplexed on the physical layer channel corresponding to the first uplink grant.

[0635] As a sub-embodiment of this embodiment, the first control information occupies physical layer resources corresponding to the first uplink grant.

[0636] As a sub-embodiment of this embodiment, the first control information occupies PUSCH resources corresponding to the first uplink grant.

[0637] As a sub-embodiment of this embodiment, the position of the first control information on the PUSCH resource corresponding to the first uplink grant is predefined.

[0638] As a sub-embodiment of this embodiment, the position of the first control information on the PUSCH resource corresponding to the first uplink grant is configured by RRC.

[0639] As a sub-embodiment of this embodiment, the position of the first control information on the PUSCH resource corresponding to the first uplink grant is calculated.

[0640] As a sub-embodiment of this embodiment, the first control information is uplink control information (UCI).

[0641] As a sub-embodiment of this embodiment, the first control information is a CG-UCI.

[0642] As a sub-embodiment of this embodiment, the first control information is a UTO (Unused Transmission Occasion)-UCI.

[0643] As a sub-embodiment of this embodiment, the number of bits occupied by the first control information is fixed.

[0644] As a sub-embodiment of this embodiment, the number of bits occupied by the first control information is configurable.

[0645] As a sub-embodiment of this embodiment, the number of bits occupied by the first control information is predefined.

[0646] As a sub-embodiment of this embodiment, the number of bits occupied by the first control information is a default number.

[0647] As a sub-embodiment of this embodiment, the first control information includes a first bitmap.

[0648] As a sub-embodiment of this embodiment, the first control information is a first bit map.

[0649] As a sub-embodiment of this embodiment, the first control information includes a first bit map, and the first bit map corresponds to the at least one uplink grant after the first uplink grant.

[0650] As a sub-embodiment of this embodiment, any bit in the first bitmap corresponds to an uplink grant in the at least one uplink grant after the first uplink grant.

[0651] As a sub-embodiment of this embodiment, the state of a bit in the first bitmap is used to indicate whether the uplink grant corresponding to the bit is not used.

[0652] As a sub-embodiment of this embodiment, if a bit in the first bit map is set to 1, it indicates that the uplink grant corresponding to the bit is not used; if a bit in the first bit map is set to 0, it indicates that the uplink grant corresponding to the bit is not unused.

[0653] As a sub-embodiment of this embodiment, if a bit in the first bit map is set to 0, it indicates that the uplink grant corresponding to the bit is not used; if a bit in the first bit map is set to 1, it indicates that the uplink grant corresponding to the bit is not unused.

[0654] As a sub-embodiment of this embodiment, the first bit map is a bit string.

[0655] As a sub-embodiment of this embodiment, the first bitmap is a continuous positive integer number of bits.

[0656] As a sub-embodiment of this embodiment, the first bitmap is a non-continuous positive integer number of bits.

[0657] As a sub-embodiment of this embodiment, the size of the first bitmap is fixed.

[0658] As a sub-embodiment of this embodiment, the size of the first bitmap is configured by RRC.

[0659] As a sub-embodiment of this embodiment, the size of the first bitmap is predefined.

[0660] As a sub-embodiment of this embodiment, the size of the first bitmap is variable.

[0661] As a sub-embodiment of this embodiment, the size of the first bit map is the number of bits occupied by the first bit map.

[0662] As a sub-embodiment of this embodiment, the size of the first bitmap depends on the number of the at least one uplink grant after the first uplink grant.

[0663] As a sub-embodiment of this embodiment, the size of the first bitmap is equal to the number of the at least one uplink grant after the first uplink grant.

[0664] As a sub-embodiment of this embodiment, the size of the first bitmap is not greater than the number of the at least one uplink grant after the first uplink grant.

[0665] As a sub-embodiment of this embodiment, the size of the first bitmap is not less than the number of the at least one uplink grant after the first uplink grant.

[0666] As a sub-embodiment of this embodiment, the first control information does not indicate that any uplink grant in the uplink grants after the first uplink grant is not used.

[0667] As an embodiment, any uplink grant among the uplink grants after the first uplink grant is indicated by the first control information.

[0668] As an embodiment, at least one of the uplink grants subsequent to the first uplink grant is not indicated by the first control information.

[0669] As a sub-embodiment of this embodiment, the at least one uplink grant in the uplink grant after the first uplink grant that is not indicated by the first control information is not used by default.

[0670] As a sub-embodiment of this embodiment, the at least one uplink grant in the uplink grant after the first uplink grant that is not indicated by the first control information is not unused by default.

[0671] As an embodiment, the phrase that the first control information does not indicate that any uplink grant in the uplink grant after the first uplink grant is not used means that the first control information indicates that any uplink grant in the uplink grant after the first uplink grant is not unused.

[0672] As an embodiment, the phrase that the first control information does not indicate that any uplink grant in the uplink grant after the first uplink grant is not used means that: any uplink grant in the uplink grant after the first uplink grant is indicated by the first control information as not being unused or is not indicated by the first control information.

[0673] As an embodiment, the phrase that the first control information does not indicate that any uplink grant in the uplink grant after the first uplink grant is not used means that any uplink grant in the uplink grant after the first uplink grant is a valid uplink grant.

[0674] As an embodiment, the valid uplink grant is an uplink grant that can at least be indicated by the first control information as to whether it is not to be used.

[0675] As an embodiment, the valid uplink grant is an uplink grant that at least does not overlap with the first set of symbols and can be indicated by the first control information as to whether it is not to be used.

[0676] As an embodiment, the valid uplink grant is an uplink grant that at least belongs to the given time interval and does not overlap with the first set of symbols and can be indicated by the first control information as being not used.

[0677] As an embodiment, if the first control information indicates that an uplink grant is not used, the uplink grant is not a valid uplink grant.

[0678] As an embodiment, the dotted box F5.3 does not exist.

[0679] As an embodiment, both the dotted box F5.1 and the dotted box F5.3 exist.

[0680] As a sub-embodiment of this embodiment, this embodiment does not limit the order of step S5105 (a) and step S5106.

[0681] As a sub-embodiment of this embodiment, step S5105(a) and step S5106 are executed simultaneously.

[0682] As an embodiment, both the dotted box F5.2 and the dotted box F5.3 exist.

[0683] As a sub-embodiment of this embodiment, this embodiment does not limit the order of step S5105 (b) and step S5106.

[0684] As a sub-embodiment of this embodiment, step S5105(b) and step S5106 are executed simultaneously.

[0685] As an embodiment, the first timer is restarted for each uplink grant configured in the first message.

[0686] As an embodiment, the first timer is restarted for each uplink grant in the uplink grant after the first uplink grant.

[0687] As an embodiment, for each uplink grant of the at least one uplink grant after the first uplink grant indicated by the first control information as not to be used, the first timer is restarted.

[0688] As an embodiment, for at least one uplink grant among the at least one uplink grant after the first uplink grant indicated by the first control information as not to be used, the first timer is not restarted.

[0689] As an embodiment, in each uplink grant configured in the first message, if the first timer is running, the first timer is restarted.

[0690] As an embodiment, for each uplink grant in the uplink grant after the first uplink grant, if the first timer is running, the first timer is restarted.

[0691] As an embodiment, for each uplink grant of the at least one uplink grant after the first uplink grant indicated by the first control information as not to be used, if the first timer is running, the first timer is restarted.

[0692] As an embodiment, for at least one uplink grant among the at least one uplink grant after the first uplink grant indicated by the first control information as not to be used, if the first timer is running, the first timer is not restarted.

[0693] Example 6

[0694] Example 6 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in Figure 6. It should be noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0695] For the first node U01, in step S6101, for one uplink grant among the at least one uplink grant after the first uplink grant, determine whether the first control information indicates that the one uplink grant is not unused; when the first control information does not indicate that the one uplink grant is unused, go to step S6102; otherwise, skip step S6102; in step S6102, restart the first timer.

[0696] In embodiment 6, for one uplink grant among the at least one uplink grant after the first uplink grant, whether to restart the first timer is determined according to the indication of the one uplink grant by the first control information; the behavior of determining whether to restart the first timer according to the indication of the one uplink grant by the first control information includes: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; expiration of the first timer is used to trigger a BSR.

[0697] As an embodiment, the one uplink grant is any uplink grant among the at least one uplink grant after the first uplink grant.

[0698] As an embodiment, the one uplink grant is the first uplink grant among the at least one uplink grant after the first uplink grant.

[0699] As an embodiment, the one uplink grant is an uplink grant adjacent to the first uplink grant among the at least one uplink grant following the first uplink grant.

[0700] As an embodiment, the uplink grant is an uplink grant corresponding to the first bit in the first bit map in the first control information.

[0701] As an embodiment, at the first moment, the first timer is restarted only when the first control information does not indicate that the one uplink grant is not used.

[0702] As an embodiment, the first moment is related to the time domain resource granted by the uplink.

[0703] As an embodiment, the first moment is related to the moment when the uplink grant is determined.

[0704] As an embodiment, the first moment is related to the moment when the uplink grant is obtained.

[0705] As an embodiment, the first moment is earlier than the starting moment of the uplink grant in the time domain.

[0706] As an embodiment, the first moment is the starting moment of the uplink grant in the time domain.

[0707] As an embodiment, the first moment is the moment when the uplink grant is determined.

[0708] As an embodiment, the first moment is the moment when the uplink grant is obtained.

[0709] As an embodiment, the first moment is later than the cut-off moment of the first uplink grant in the time domain.

[0710] As an embodiment, the first moment is when the MAC entity has the uplink grant sent on the UL-SCH.

[0711] As an embodiment, the first moment is when the MAC entity receives the uplink grant.

[0712] As an embodiment, the one uplink grant is used for new data transmission.

[0713] As an embodiment, the one uplink grant is for new data transmission on the UL-SCH.

[0714] As an embodiment, any uplink grant configured by the first message is used for new data transmission.

[0715] As an embodiment, any uplink grant configured by the first message is for new data transmission on the UL-SCH.

[0716] As an embodiment, when the first control information indicates that the uplink grant is not used, the first uplink grant is considered to be a de-prioritized uplink grant.

[0717] As an embodiment, when the first control information indicates that the one uplink grant is not used, the first timer is not restarted.

[0718] As an embodiment, the phrase means only when the first control information does not indicate that the one uplink grant is not used: the first control information indicates that the one uplink grant is not unused.

[0719] As an embodiment, the phrase means only when the first control information does not indicate that the one uplink grant is not used: the first control information does not indicate that the one uplink grant is not used.

[0720] As an embodiment, the sentence "restarting the first timer only when the first control information does not indicate that the one uplink grant is not used" includes: restarting the first timer if the first timer is running only when the first control information does not indicate that the one uplink grant is not used.

[0721] As an embodiment, when the first control information does not indicate that the one uplink grant is not used, if the first timer is not running, the first timer is not started.

[0722] As an embodiment, the first timer is retxBSR-Timer.

[0723] As an embodiment, when the first timer is reached, a BSR is triggered.

[0724] As an embodiment, when the first timer is reached, a Regular BSR is triggered.

[0725] As an embodiment, when the first timer is reached and at least one logical channel belonging to an LCG includes uplink data (UL data), a BSR is triggered.

[0726] As an embodiment, when the first timer is reached and at least one logical channel belonging to an LCG includes uplink data (UL data), a Regular BSR is triggered.

[0727] Example 7

[0728] Embodiment 7 illustrates a schematic diagram in which the first control information according to an embodiment of the present application does not indicate that any uplink grant after the first uplink grant is not used, as shown in Figure 7. In Embodiment 7, the first control information does not indicate that any uplink grant after the first uplink grant is not used.

[0729] As an embodiment, any uplink grant among the uplink grants after the first uplink grant is not indicated as not to be used by the first control information.

[0730] As an embodiment, any uplink grant among the uplink grants after the first uplink grant is indicated for use by the first control information.

[0731] As an embodiment, any uplink grant among the uplink grants after the first uplink grant is indicated by the first control information as non-unused.

[0732] As an embodiment, any uplink grant among the uplink grants subsequent to the first uplink grant is indicated by the first control information as not unused or is not indicated by the first control information.

[0733] As an embodiment, any uplink grant among the uplink grants subsequent to the first uplink grant is not determined to be unused.

[0734] As an embodiment, when an uplink grant is determined to be unused, the first control information indicates that the uplink grant is not used; when an uplink grant is not determined to be unused, the first control information does not indicate that the uplink grant is not used.

[0735] As an embodiment, when an uplink grant is determined to be not used, the first control information indicates that the uplink grant is not used or the first control information does not indicate that the uplink grant is not used; when an uplink grant is not determined to be not used, the first control information does not indicate that the uplink grant is not used.

[0736] As an embodiment, when an uplink grant is determined to be not used, the first control information indicates that the uplink grant is not used; when an uplink grant is not determined to be not used, the first control information does not indicate that the uplink grant is not used or the first control information does not indicate the uplink grant.

[0737] As an embodiment, the fact that the first control information does not indicate that the uplink grant is not used means that the first control information indicates that the uplink grant is not unused.

[0738] As an embodiment, the fact that the first control information does not indicate that the one uplink grant is not used means that the first control information indicates that the one uplink grant is used.

[0739] Example 8

[0740] Example 8 illustrates a schematic diagram of a first condition set related to a delay budget of at least one data packet set according to an embodiment of the present application, as shown in FIG8 .

[0741] In the eighth embodiment, the first set of conditions is related to a delay budget of at least one data packet set, each of the at least one data packet set including at least one data packet.

[0742] As an embodiment, any uplink grant among the uplink grants subsequent to the first uplink grant is no later than the expiration time of the delay budget of the at least one data packet set.

[0743] As an embodiment, all the data to be processed and available for transmission include the at least one data packet set.

[0744] As an embodiment, the remaining data to be processed and available for transmission includes the at least one data packet set.

[0745] As an embodiment, all the data to be processed and available for transmission are the at least one data packet set.

[0746] As an embodiment, the remaining data to be processed and available for transmission is the at least one data packet set.

[0747] As an embodiment, the first set of conditions is met when the delay budget of at least the at least one set of data packets is greater than a first threshold; the first threshold is configurable.

[0748] As a sub-embodiment of this embodiment, if the delay budget of the at least one data packet set is less than the first threshold, the first MAC PDU includes a BSR MAC CE.

[0749] As a sub-embodiment of this embodiment, if the delay budget of the at least one data packet set is less than the first threshold, the first MAC PDU includes a BSR MAC CE; the BSR MAC CE indicates the delay budget.

[0750] As a sub-embodiment of this embodiment, the first threshold is configurable.

[0751] As a sub-embodiment of this embodiment, the first threshold is predefined.

[0752] As an embodiment, the first condition set is satisfied when the expiration time of the delay budget of at least the at least one data packet set is later than the expiration time of the latest uplink grant in the time domain among the uplink grants after the first uplink grant.

[0753] As a sub-embodiment of this embodiment, the deadline of the delay budget of the at least one data packet set is earlier than the deadline of the latest uplink grant in the time domain among the uplink grants after the first uplink grant, and the first MAC PDU includes BSR MAC CE.

[0754] As a sub-embodiment of this embodiment, the deadline of the delay budget of the at least one data packet set is earlier than the deadline of the latest uplink grant in the time domain among the uplink grants after the first uplink grant, and the first MAC PDU includes a BSR MAC CE; the BSR MAC CE indicates the delay budget.

[0755] As a sub-embodiment of this embodiment, the expiration time of the delay budget of the at least one data packet set is later than the expiration time of the latest uplink grant in the time domain among the uplink grants after the first uplink grant, which means: the expiration time of the delay budget of the at least one data packet set is later than the N1th symbol after the expiration time of the latest uplink grant in the time domain among the uplink grants after the first uplink grant.

[0756] As a sub-embodiment of this embodiment, N1 is configurable.

[0757] As a sub-embodiment of this embodiment, N1 is predefined.

[0758] As an embodiment, the at least one data packet set belongs to the same logical channel.

[0759] As an embodiment, the at least one data packet set belongs to the same logical channel group (Logical Channel Group, LCG).

[0760] As an embodiment, the at least one data packet set belongs to the same MAC entity.

[0761] As an embodiment, the at least one data packet set belongs to the same DRB (Data Radio Bearer).

[0762] As an embodiment, each data packet set in the at least one data packet set is a PDU set.

[0763] As an embodiment, the delay budget of the at least one data packet set is a minimum value among multiple delay budgets.

[0764] As an embodiment, the delay budget of the at least one data packet set is a minimum value of the delay budget of each data packet set in the at least one data packet set.

[0765] As an embodiment, the delay budgets of the at least one data packet set share a common delay budget.

[0766] As an embodiment, at the expiration time of the delay budget of the at least one data packet set, at least one data packet of the at least one data packet set is discarded.

[0767] As an embodiment, at the expiration time of the delay budget of the at least one data packet set, each data packet of the at least one data packet set is discarded.

[0768] As an embodiment, the expiration time of the delay budget of the at least one data packet set is the time when a PDCP discard timer expires.

[0769] As an embodiment, the PDCP discard timer is discardTimer.

[0770] As an embodiment, the name of the PDCP discard timer includes discard and Timer.

[0771] As an embodiment, the name of the PDCP discard timer includes discardTimer.

[0772] As an embodiment, the delay budget is remaining time.

[0773] As an embodiment, the delay budget is PDB (PDB Delay Budget).

[0774] As an embodiment, the delay budget is PSDB (PDU-Set Delay Budget, PDU set delay budget).

[0775] As an embodiment, the delay budget is calculated based on PSDB.

[0776] As an embodiment, the delay budget is calculated based on PSDB and PDCP discard timers.

[0777] As an embodiment, the delay budget is calculated based on the PDCP discard timer.

[0778] As an embodiment, the delay budget is a remaining time of a PDCP discard timer.

[0779] Example 9

[0780] Embodiment 9 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in FIG9 . In FIG9 , the processing device 900 in the first node includes a first receiver 901 and a first transmitter 902 .

[0781] A first receiver 901 receives a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0782] A first transmitter 902 triggers at least one BSR; after the action triggers at least one BSR, sends a first MAC PDU on a first uplink grant;

[0783] In Example 9, whether the first MAC PDU includes the BSR MAC CE depends on whether the first condition set is met; when the first condition set is met, the first MAC PDU does not include the BSR MAC CE; when the first condition set is not met, the first MAC PDU includes the BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0784] As an embodiment, the first transmitter 902 sends first control information on the first uplink grant, where the first control information indicates whether at least one uplink grant after the first uplink grant is not used.

[0785] As an embodiment, the first transmitter 902 determines whether to restart the first timer for one uplink grant among the at least one uplink grant after the first uplink grant based on the indication of the one uplink grant by the first control information; wherein the behavior of determining whether to restart the first timer based on the indication of the one uplink grant by the first control information includes: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; and expiration of the first timer is used to trigger a BSR.

[0786] As an embodiment, the first control information does not indicate that any uplink grant in the uplink grant after the first uplink grant is not used.

[0787] As an embodiment, the first condition set is related to a delay budget of at least one data packet set, and each data packet set in the at least one data packet set includes at least one data packet.

[0788] As an embodiment, the first transmitter 902 cancels the triggered BSR when the first condition set is met; wherein the behavior of canceling the triggered BSR is used to determine that the first MAC PDU does not include a BSR.

[0789] As an embodiment, if the first MAC PDU includes a BSR MAC CE, the indication of the buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

[0790] As an embodiment, the first receiver 901 includes the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in FIG. 4 of the present application.

[0791] As an embodiment, the first receiver 901 includes the antenna 452, receiver 454, multi-antenna receiving processor 458, and receiving processor 456 in FIG. 4 of the present application.

[0792] As an embodiment, the first receiver 901 includes the antenna 452, the receiver 454, and the receiving processor 456 in FIG. 4 of the present application.

[0793] As an embodiment, the first transmitter 902 includes the antenna 452, transmitter 454, multi-antenna transmission processor 457, transmission processor 468, controller / processor 459, memory 460 and data source 467 in FIG. 4 of the present application.

[0794] As an embodiment, the first transmitter 902 includes the antenna 452, transmitter 454, multi-antenna transmission processor 457, and transmission processor 468 in FIG. 4 of the present application.

[0795] As an embodiment, the first transmitter 902 includes the antenna 452, transmitter 454, and transmission processor 468 in FIG. 4 of the present application.

[0796] Example 10

[0797] Embodiment 10 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in FIG10. In FIG10, the processing device 1000 in the second node includes a second transmitter 1001 and a second receiver 1002.

[0798] The second transmitter 1001 sends a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time;

[0799] The second receiver 1002 receives a first MAC PDU in a first uplink grant;

[0800] In Example 10, after at least one BSR is triggered, the first MAC PDU is sent; whether the first MAC PDU includes the BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include the BSR MAC CE; when the first condition set is not met, the first MAC PDU includes the BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

[0801] As an embodiment, the second receiver 1002 receives first control information on the first uplink grant, where the first control information indicates whether at least one uplink grant after the first uplink grant is not used.

[0802] As an embodiment, for one uplink grant among the at least one uplink grant after the first uplink grant, the receiver of the first message determines whether to restart the first timer based on the indication of the one uplink grant by the first control information; the behavior of determining whether to restart the first timer based on the indication of the one uplink grant by the first control information includes: restarting the first timer only when the first control information does not indicate that the one uplink grant is not used; the expiration of the first timer is used to trigger a BSR.

[0803] As an embodiment, the first control information does not indicate that any uplink grant in the uplink grant after the first uplink grant is not used.

[0804] As an embodiment, the first condition set is related to a delay budget of at least one data packet set, and each data packet set in the at least one data packet set includes at least one data packet.

[0805] As an embodiment, when the first condition set is met, the receiver of the first message cancels the triggered BSR; the behavior of canceling the triggered BSR is used to determine that the first MAC PDU does not include a BSR.

[0806] As an embodiment, if the first MAC PDU includes a BSR MAC CE, the indication of the buffer size field in the BSR MAC CE included in the first MAC PDU depends on the uplink grant after the first uplink grant.

[0807] As an embodiment, the second transmitter 1001 includes the antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476 in FIG. 4 of the present application.

[0808] As an embodiment, the second transmitter 1001 includes the antenna 420, transmitter 418, multi-antenna transmission processor 471, and transmission processor 416 in FIG. 4 of the present application.

[0809] As an embodiment, the second transmitter 1001 includes the antenna 420, transmitter 418, and transmission processor 416 in FIG. 4 of the present application.

[0810] As an embodiment, the second receiver 1002 includes the antenna 420, the receiver 418, the multi-antenna receiving processor 472, the receiving processor 470, the controller / processor 475, and the memory 476 in FIG. 4 of the present application.

[0811] As an embodiment, the second receiver 1002 includes the antenna 420, the receiver 418, the multi-antenna receiving processor 472, and the receiving processor 470 in FIG. 4 of the present application.

[0812] As an embodiment, the second receiver 1002 includes the antenna 420, the receiver 418, and the receiving processor 470 in FIG. 4 of the present application.

[0813] Example 11

[0814] Embodiment 11 illustrates a schematic diagram of determining whether to restart the first timer based on an indication of an uplink grant by the first control information according to an embodiment of the present application, as shown in FIG11. In FIG11, the horizontal axis represents time; each box filled with horizontal lines belongs to an uplink grant configured by the first message, box i filled with horizontal lines represents the first uplink grant, boxes i+1, i+2, i+3, etc. filled with horizontal lines represent uplink grants indicated by the first bitmap after the first uplink grant; and dotted boxes i+1, i+2, i+3, etc. represent the first bitmap in the first control information.

[0815] In embodiment 11, the first control information includes a first bitmap; the one uplink grant among the at least one uplink grant after the first uplink grant indicated by the first control information is the uplink grant corresponding to the box i+1 filled with a horizontal line box.

[0816] As an embodiment, the first bitmap i+1, i+2, i+3... in the first control information respectively indicates whether the uplink grant corresponding to the boxes i+1, i+2, i+3... filled with horizontal lines is not used.

[0817] As an embodiment, for the uplink grant corresponding to the box i+1 filled with the horizontal line box, the bit i+1 in the first bit map in the first control information does not indicate that the uplink grant is not used, and at the first moment, the first timer is restarted.

[0818] As an embodiment, for the uplink grant corresponding to the box i+1 filled with the horizontal line box, the bit i+1 in the first bit map in the first control information indicates that the uplink grant is not used, and at the first moment, the first timer is not restarted.

[0819] As an embodiment, the first moment is earlier than the starting moment of the uplink grant corresponding to the box i+1 filled with horizontal lines in the time domain.

[0820] As an embodiment, the first moment is the starting moment of the uplink grant corresponding to the box i+1 filled with horizontal lines in the time domain.

[0821] As an embodiment, the first moment is the moment when the uplink grant corresponding to the box i+1 filled with horizontal lines is determined.

[0822] As an embodiment, the first moment is later than the cut-off moment of the first uplink grant in the time domain.

[0823] As an embodiment, the first moment is related to the time domain resources granted in the uplink corresponding to the box i+1 filled with horizontal lines.

[0824] As an embodiment, the first moment is related to the determined moment of uplink grant corresponding to the box i+1 filled with horizontal lines.

[0825] As an embodiment, this embodiment does not limit whether there is other uplink grant configured by the first message between the two adjacent uplink grants in FIG. 11 .

[0826] As an embodiment, this embodiment does not limit the sizes of the first bitmaps i+1, i+2, i+3, ... in FIG11 .

[0827] As an embodiment, this embodiment does not limit whether the uplink grants in the first bitmap i+1, i+2, i+3, etc. in FIG. 11 belong to the same configuration period.

[0828] As an embodiment, in this embodiment, for the convenience of description, the first control information includes a first bit map; in a specific implementation, there is no restriction on how the first control information indicates whether at least one uplink grant after the first uplink grant is not used.

[0829] As an embodiment, in this embodiment, for the convenience of description, the uplink grant corresponding to the box i+1 filled with a horizontal line box is used as the one uplink grant among the at least one uplink grant after the first uplink grant indicated by the first control information; in a specific implementation, there is no restriction on whether the one uplink grant among the at least one uplink grant after the first uplink grant indicated by the first control information is the uplink grant corresponding to the box i+1 filled with a horizontal line box.

[0830] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing 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 functional module. This application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in this application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR node B) NR node B, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0831] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; A first transmitter triggers at least one BSR; After the action triggers at least one BSR, sending a first MAC PDU on a first uplink grant; Whether the first MAC PDU includes BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include BSR MAC CE; when the first condition set is not met, the first MAC PDU includes BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

2. The first node according to claim 1, characterized in that: include: The first transmitter sends first control information on the first uplink grant, wherein the first control information indicates whether at least one uplink grant after the first uplink grant is not used.

3. The first node according to claim 2, characterized in that: include: The first transmitter determines, for an uplink grant among the at least one uplink grant after the first uplink grant, whether to restart a first timer according to an indication of the one uplink grant by the first control information; The behavior of determining whether to restart the first timer according to the indication of the first control information for the uplink grant includes: restarting the first timer only when the first control information does not indicate that the uplink grant is not used; and expiration of the first timer is used to trigger a BSR.

4. The first node according to claim 2 or 3, characterized in that: The first control information does not indicate that any uplink grant in the uplink grants after the first uplink grant is not used.

5. The first node according to any one of claims 1 to 4, characterized in that: The first set of conditions is related to a delay budget of at least one data packet set, each of the at least one data packet set including at least one data packet.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The first transmitter cancels the triggered BSR when the first condition set is met; The BSR triggered by the behavior cancellation is used to determine that the first MAC PDU does not include a BSR.

7. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; a second receiver, receiving a first MAC PDU on a first uplink grant; Among them, after at least one BSR is triggered, the first MAC PDU is sent; whether the first MAC PDU includes BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include BSR MAC CE; when the first condition set is not met, the first MAC PDU includes BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

8. A method in a first node for wireless communication, characterized in that: include: receiving a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; Trigger at least one BSR; After the action triggers at least one BSR, sending a first MAC PDU on a first uplink grant; Whether the first MAC PDU includes BSR MAC CE depends on whether a first condition set is met; when the first condition set is met, the first MAC PDU does not include BSR MAC CE; when the first condition set is not met, the first MAC PDU includes BSR MAC CE; the first condition set is related to the uplink grant after the first uplink grant; the first uplink grant and the uplink grant after the first uplink grant are configured by the first message.

9. A method in a second node for wireless communication, characterized in that: include: Sending a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; receiving a first MAC PDU on a first uplink grant; wherein, after at least one BSR is triggered, the first MAC PDU is sent; whether the first MAC PDU includes the BSR MAC CE depends on whether a first condition set is satisfied; when the first condition set is satisfied, the first MAC PDU does not include the BSR MAC CE; when the first condition set is not satisfied, the first MAC PDU includes the BSR MAC CE; the first condition set is related to the first uplink authorization relevant to the subsequent upward grant; The first uplink grant and the uplink grant subsequent to the first uplink grant are configured by the first message.

Citation Information

Patent Citations

  • Data scheduling method and device

    CN113228732A

  • Method and apparatus for delivering buffer status report of relay in wireless communication system

    CN113259987A

  • Method and apparatus in communication node used for wireless communication

    CN114828268A

  • Logical Channel Prioritization for Pre-Emption

    US20220174683A1