Method and apparatus used in communication node for wireless communication

By optimizing the uplink granting time schedule and control information sending strategy in wireless communication nodes, the problem of low control information sending efficiency is solved, and higher signaling overhead and resource utilization is achieved. It is suitable for a variety of wireless communication scenarios .

WO2024235092A1PCT designated stage expired Publication Date: 2024-11-21SHANGHAI LANGBO COMM TECH CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/091910
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-16
Filing Date
2024-05-09
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In future wireless communication systems, the transmission of control information has problems such as low efficiency and high latency, especially in many application scenarios, it is difficult to meet the performance requirements of high speed and low latency.

Method used

By adopting a unified design scheme in the wireless communication node, we ensure that the time of uplink grant does not overlap, and decide whether to send control information after receiving the uplink grant, avoid unnecessary information transmission, and optimize signaling overhead and resource utilization.

Benefits of technology

It effectively reduces signaling overhead, improves the utilization rate of wireless resources and flexible scheduling capabilities, and is suitable for a variety of wireless communication scenarios, including NR, LTE, V2X and IAB systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024091910_21112024_PF_FP_ABST
    Figure CN2024091910_21112024_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, which configures uplink grants, wherein any two uplink grants configured by the first message do not overlap in time; whether to send first control information at a first uplink grant depends on an uplink grant after the first uplink grant; and the first uplink grant and the uplink grant after the first uplink grant are configured by the first message; and the first control information is used for indicating whether the uplink grant is not used. The solution provided in the present application reduces unnecessary sending of first control information, reduces the signaling overheads, and improves the resource utilization rate.
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 control information. 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 controlling the sending of information is a key issue.

[0005] To address the above-mentioned issues, the present application provides a solution for the transmission of control information. In the description of the above-mentioned issues, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) systems, achieving technical effects similar to those of the NR system. Furthermore, although the present application provides a specific implementation for the uplink, the present application can also be used in scenarios such as the downlink, achieving technical effects similar to those of the uplink. Furthermore, adopting a unified design solution for different scenarios can also help reduce hardware complexity and cost. Furthermore, although the present application provides a specific implementation for the XR scenario, the present application can also be used in uplink enhancement scenarios, achieving technical effects similar to those of the XR system. Furthermore, although the present application provides a specific implementation for the PUSCH (Physical Uplink Shared CHannel), the present application can also be used in scenarios such as PRACH, PUCCH, or PUSCH repetition, achieving technical effects similar to those of the PUSCH. Furthermore, although the original intention of this application is for the Uu air interface, this application can also be used for the PC5 port to achieve technical effects similar to 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) scenario, the communication scenario between the terminal and the relay, and the relay and the base station, to achieve technical effects similar to those 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) communication scenario, to achieve technical effects similar to those 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 technical effects similar to those in the TN scenario. In addition, adopting a unified solution for different scenarios also helps 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] As an embodiment, the interpretation of terms in this application refers to the definition of the standard protocol of IEEE (Institute of Electrical and Electronics Engineers).

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

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

[0012] 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;

[0013] Among them, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

[0014] As an embodiment, the problem to be solved by the present application includes: how to determine whether to grant sending of the first control information in the first uplink.

[0015] As an embodiment, the problem to be solved by the present application includes: how to avoid sending the first control information in the first uplink grant.

[0016] As an embodiment, the characteristics of the above method include: determining whether to send the first control information in the first uplink grant based on an uplink grant after at least the first uplink grant.

[0017] As an embodiment, the benefits of the above method include: avoiding sending the first control information in the first uplink grant.

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

[0019] As an embodiment, the benefits of the above method include: improving the utilization rate of wireless resources.

[0020] As an embodiment, the benefits of the above method include: achieving flexible scheduling of wireless resources.

[0021] According to one aspect of the present application, it is characterized in that whether the first control information is sent in the first uplink grant depends on whether there is at least one unused uplink grant in the uplink grant after the first uplink grant; when there is at least one unused uplink grant in the uplink grant after the first uplink grant, the first control information is sent in the first uplink grant; when there is no unused uplink grant in the uplink grant after the first uplink grant, the first control information is not sent in the first uplink grant.

[0022] As an embodiment, the above method further reduces unnecessary information transmission.

[0023] As an embodiment, the above method reduces signaling overhead.

[0024] As an embodiment, the above method improves the utilization rate of wireless resources.

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

[0026] receiving a second message, the second message indicating a first set of symbols;

[0027] Whether to send the first control information in the first uplink grant depends on the time domain position of the uplink grant after the first uplink grant and the position of the first symbol set.

[0028] As an embodiment, the above method avoids indicating redundant information through the first control information.

[0029] As an embodiment, the above method further reduces unnecessary information transmission.

[0030] As an embodiment, the above method reduces signaling overhead.

[0031] As an embodiment, the above method improves the utilization rate of wireless resources.

[0032] According to one aspect of the present application, it is characterized in that the first uplink grant satisfies a first set of conditions, one of the conditions in the first set of conditions being that the MAC (Medium Access Control) PDU (Protocol Data Unit) corresponding to the first uplink grant does not have a MAC SDU (Service Data Unit).

[0033] As an embodiment, the characteristics of the above method include: when at least the first condition set is satisfied, whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant.

[0034] As an embodiment, the characteristics of the above method include: whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant only when the first condition set is met.

[0035] As an embodiment, the above method further reduces unnecessary information transmission.

[0036] As an embodiment, the above method reduces signaling overhead.

[0037] As an embodiment, the above method improves the utilization rate of wireless resources.

[0038] According to one aspect of the present application, it is characterized in that whether to send the first control information in the first uplink grant depends on the size and effective data amount of the first uplink grant.

[0039] As an embodiment, the characteristics of the above method include: whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant only when the first uplink grant cannot accommodate the valid data and the first control information at the same time.

[0040] As an embodiment, the characteristics of the above method include: when at least the first uplink grant cannot accommodate the valid data and the first control information at the same time, whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant.

[0041] As an embodiment, the above method further reduces unnecessary information transmission.

[0042] As an embodiment, the above method reduces signaling overhead.

[0043] As an embodiment, the above method improves the utilization rate of wireless resources.

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

[0045] sending second control information;

[0046] The second control information indicates whether to send the first control information in the first uplink grant.

[0047] As an embodiment, the above method reduces unnecessary information transmission while avoiding misunderstanding between the second node and the first node regarding whether to send the first control information.

[0048] As an embodiment, the above method improves the flexibility of sending the first control information.

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

[0050] Receive a first parameter;

[0051] The first parameter is used to determine whether sending the first control information in the first uplink grant depends on the uplink grant after the first uplink grant; the first parameter is not either enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured.

[0052] As an embodiment, the characteristics of the above method include: only when the first parameter is configured, whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant.

[0053] As an embodiment, the above method reduces unnecessary information transmission while avoiding misunderstanding between the second node and the first node regarding whether to send the first control information.

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

[0055] 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;

[0056] Whether the recipient of the first message sends the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

[0057] According to one aspect of the present application, it is characterized in that whether the receiver of the first message sends the first control information in the first uplink grant depends on whether there is at least one unused uplink grant in the uplink grant after the first uplink grant; when there is at least one unused uplink grant in the uplink grant after the first uplink grant, the first control information is sent in the first uplink grant; when there is no unused uplink grant in the uplink grant after the first uplink grant, the first control information is not sent in the first uplink grant.

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

[0059] sending a second message, wherein the second message indicates the first set of symbols;

[0060] Whether the receiver of the first message sends the first control information in the first uplink grant depends on the time domain position of the uplink grant and the position of the first symbol set after the first uplink grant.

[0061] According to one aspect of the present application, it is characterized in that the first uplink grant satisfies a first set of conditions, and one of the conditions in the first set of conditions is that the MAC PDU corresponding to the first uplink grant has no MAC SDU.

[0062] According to one aspect of the present application, it is characterized in that whether the recipient of the first message sends the first control information in the first uplink grant depends on the size and effective data amount of the first uplink grant.

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

[0064] receiving second control information;

[0065] The second control information is sent only to the recipient of the first message; the second control information indicates whether to send the first control information when the first uplink is granted.

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

[0067] Send the first parameter;

[0068] The first parameter is used to determine whether sending the first control information in the first uplink grant depends on the uplink grant after the first uplink grant; the first parameter is not either enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured.

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

[0070] 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;

[0071] Among them, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

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

[0073] 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;

[0074] Whether the recipient of the first message sends the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

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

[0076] - Avoid sending the first control information in the first uplink grant;

[0077] -. Reduce signaling overhead;

[0078] -.Improve the utilization of wireless resources;

[0079] -. Realize flexible scheduling of wireless resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] 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:

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

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

[0083] 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;

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

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

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

[0087] FIG7 shows a wireless signal transmission flow chart according to yet another embodiment of the present application;

[0088] FIG8 is a schematic diagram showing whether there is at least one unused uplink grant in an uplink grant after the first control information for sending the first uplink grant depends on the first uplink grant according to an embodiment of the present application;

[0089] FIG9 is a schematic diagram showing whether to send the first control information in the first uplink grant according to an embodiment of the present application depending on the size of the first uplink grant and the amount of valid data;

[0090] FIG10 is a schematic diagram showing a first uplink grant satisfying a first set of conditions according to an embodiment of the present application;

[0091] FIG11 is a schematic diagram showing a case where a MAC PDU is not generated for a HARQ entity corresponding to a first uplink grant according to an embodiment of the present application;

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

[0093] FIG13 shows a structural block diagram of a processing device used in a second node according to an embodiment of the present application. DETAILED DESCRIPTION

[0094] 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 in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0095] Example 1

[0096] Example 1 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 Figure 1. In Figure 1, 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 between the steps represented.

[0097] In Example 1, the first node in the present application receives a first message in step 101, and the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; wherein, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

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

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

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

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

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

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

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

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

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

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

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

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

[0110] 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).

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

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

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

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

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

[0116] As an embodiment, the first message is a CellGroupConfig IE.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0144] As an embodiment, the uplink grant configured by the first message occupies PUSCH resources.

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

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

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

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

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

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

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

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

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

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

[0155] As an embodiment, each uplink grant configured by the first message is a PUSCH (Physical uplink shared channel) resource.

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

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

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

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

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

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

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

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

[0164] As an embodiment, the uplink grants configured in the first message belong to the same configuration period.

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

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

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

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

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

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

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

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

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

[0174] As an embodiment, uplink grants in a configuration period have the same MCS or at least one of frequency domain resources or PUSCH duration.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0197] As an embodiment, the uplink grants subsequent to the first uplink grant belong to multiple configuration periods.

[0198] As an embodiment, the uplink grants after the first uplink grant belong to a continuous configuration period.

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

[0200] As an embodiment, the K2 uplink grants belong to a maximum of M1 configuration periods; M1 is a positive integer.

[0201] As an embodiment, the K2 uplink grants belong to M1 configuration periods; M1 is a positive integer.

[0202] As an embodiment, the M1 is predefined.

[0203] As an embodiment, the M1 is configurable.

[0204] As an embodiment, M1 is fixed.

[0205] As an embodiment, M1 is 2.

[0206] As an embodiment, M1 is 1.

[0207] As an embodiment, the M1 configuration periods are adjacent.

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

[0209] As an embodiment, the uplink grant after the first uplink grant is an uplink grant within a given time interval.

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

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

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

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

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

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

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

[0217] As an embodiment, the uplink grant following the first uplink grant is at least one valid uplink grant following the first uplink grant.

[0218] As a sub-embodiment of this embodiment, the valid uplink grant is an uplink grant that can be indicated by the first control information as to whether it is not to be used.

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

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

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

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

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

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

[0225] As an embodiment, the uplink grant following the first uplink grant is an adjacent uplink grant.

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

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

[0228] As an embodiment, the uplink grants after the first uplink grant are not adjacent.

[0229] As an embodiment, there are two uplink grants that are adjacent in the time domain in the uplink grant after the first uplink grant, and there is at least one uplink grant configured by the first message between the two uplink grants.

[0230] As an embodiment, at least the uplink grant subsequent to the first uplink grant is used to determine whether to send the first control information in the first uplink grant.

[0231] As an embodiment, whether to send the first control information in the first uplink grant is related to the uplink grant after at least the first uplink grant.

[0232] As an embodiment, whether to send the first control information in the first uplink grant depends on the configuration of the uplink grant after the first uplink grant.

[0233] As an embodiment, whether to send the first control information in the first uplink grant depends on the number of the uplink grants after the first uplink grant.

[0234] As a sub-embodiment of this embodiment, when the number of uplink grants after the first uplink grant is not 0, the first control information is sent in the first uplink grant; when the number of uplink grants after the first uplink grant is 0, the first control information is not sent in the first uplink grant.

[0235] As a sub-embodiment of this embodiment, the first uplink grant and the uplink grant subsequent to the first uplink grant belong to the same configuration period.

[0236] As an embodiment, whether to send the first control information in the first uplink grant depends on the number of unused uplink grants in the uplink grant after the first uplink grant; when the number of unused uplink grants in the uplink grant after the first uplink grant reaches a threshold, the first control information is sent in the first uplink grant; when the number of unused uplink grants in the uplink grant after the first uplink grant does not reach a threshold, the first control information is not sent in the first uplink grant.

[0237] As a sub-embodiment of this embodiment, the threshold is not less than 1.

[0238] As a sub-embodiment of this embodiment, the threshold is greater than 1.

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

[0240] As a sub-embodiment of this embodiment, the threshold is a positive integer.

[0241] As a sub-embodiment of this embodiment, reaching / not reaching the threshold value refers to being equal to or being greater than / less than the threshold value.

[0242] As a sub-embodiment of this embodiment, reaching / not reaching the threshold value refers to being greater than / less than or equal to the threshold value.

[0243] As an embodiment, whether to send the first control information in the first uplink grant depends on the time domain position of the uplink grant after the first uplink grant.

[0244] As a sub-embodiment of this embodiment, when at least one of the uplink grants after the first uplink grant does not overlap with the first symbol set, the first control information is sent in the first uplink grant; when all the uplink grants after the first uplink grant overlap with the first symbol set, the first control information is not sent in the first uplink grant.

[0245] As an embodiment, the first control information is transmitted on a physical layer channel.

[0246] As an embodiment, the first control information is multiplexed on a physical layer channel.

[0247] As an embodiment, the first control information is uplink control information (UCI).

[0248] As an embodiment, the first control information is a CG-UCI.

[0249] As an embodiment, the first control information is a UTO (Unused Transmission Occasion) - UCI.

[0250] As an embodiment, the first control information is a portion of bits in a PUSCH transmission.

[0251] As an embodiment, the first control information is transmitted on PUSCH.

[0252] As an embodiment, the first control information occupies PUSCH resources.

[0253] As an embodiment, the first control information occupies the PUSCH resources granted by the first uplink.

[0254] As an embodiment, the position of the first control information on the PUSCH resource corresponding to the first uplink grant is predefined.

[0255] As an embodiment, the position of the first control information on the PUSCH resource corresponding to the first uplink grant is RRC configured.

[0256] As an embodiment, the position of the first control information on the PUSCH resource corresponding to the first uplink grant is calculated.

[0257] As an embodiment, the number of bits occupied by the first control information is fixed.

[0258] As an embodiment, the number of bits occupied by the first control information is configurable.

[0259] As an embodiment, the number of bits occupied by the first control information is predefined.

[0260] As an embodiment, the number of bits occupied by the first control information is a default number.

[0261] As an embodiment, the first control information includes a bitmap.

[0262] As an embodiment, the first control information is a bit map.

[0263] As an embodiment, the first control information includes a bit map, and the bit map corresponds to the uplink grant after the first uplink grant.

[0264] As a sub-embodiment of this embodiment, any bit in the bitmap corresponds to an uplink grant in the uplink grants after the first uplink grant.

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

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

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

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

[0269] As a sub-embodiment of this embodiment, the bit map is a continuous positive integer number of bits.

[0270] As a sub-embodiment of this embodiment, the bit map is a non-continuous positive integer number of bits.

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

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

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

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

[0275] As a sub-embodiment of this embodiment, the size of the bitmap is the number of bits occupied by the bitmap.

[0276] As a sub-embodiment of this embodiment, the size of the bitmap depends on the number of the uplink grants after the first uplink grant.

[0277] As a sub-embodiment of this embodiment, the size of the bitmap is equal to the number of the uplink grants after the first uplink grant.

[0278] As a sub-embodiment of this embodiment, the size of the bitmap is not greater than the number of the uplink grants after the first uplink grant.

[0279] As a sub-embodiment of this embodiment, the size of the bitmap is not less than the number of the uplink grants after the first uplink grant.

[0280] As an embodiment, the first uplink grant is an uplink grant configured by the first message, and each uplink grant in the uplink grants after the first uplink grant is an uplink grant configured by the first message.

[0281] As an embodiment, the first uplink grant and the uplink grant after the first uplink grant belong to the same CG configuration configured by the first message.

[0282] As an embodiment, the first uplink grant and the uplink grant after the first uplink grant belong to the same configuration period of the same CG configuration configured by the first message.

[0283] As an embodiment, the first uplink grant and the uplink grant after the first uplink grant belong to at least one configuration period of the same CG configuration configured by the first message.

[0284] As an embodiment, the first uplink grant and the uplink grant after the first uplink grant belong to multiple configuration cycles of the same CG configuration configured by the first message.

[0285] As an embodiment, the first control information is used to indicate whether the uplink grant configured by the first message is not used.

[0286] As an embodiment, the first control information is used to indicate whether the uplink grant after the first uplink grant configured by the first message is not used.

[0287] As an embodiment, the first control information is used to indicate whether the uplink grant after the first uplink grant configured by the first message is not used.

[0288] As an embodiment, the first control information is used to indicate whether the uplink grant after the first uplink grant is not used.

[0289] As an embodiment, the first control information is used to indicate whether the uplink grant is unused or not unused.

[0290] As an embodiment, the first control information is used to indicate whether at least one uplink grant is unused or non-unused.

[0291] As an embodiment, the first control information is used to indicate whether each uplink grant in at least one uplink grant is unused or non-unused.

[0292] As an embodiment, the bit map in the first control information is used to indicate whether the uplink grant is unused or not unused.

[0293] As an embodiment, any bit in the bitmap in the first control information is used to indicate whether the uplink grant corresponding to the any bit is unused or not unused.

[0294] As an embodiment, on the premise that the first control information is sent, the first control information is used to indicate whether the uplink grant is not used.

[0295] As an embodiment, on the premise that the first control information is sent, the first control information indicates whether each uplink grant in the uplink grant after the first uplink grant is not used.

[0296] As an embodiment, on the premise that the first control information is sent, each bit in the bitmap in the first control information indicates whether an uplink grant in the uplink grant after the first uplink grant is not used.

[0297] As an embodiment, non-use / non-non-use refers to: non-use / use.

[0298] As an embodiment, not using / not not using means: will not use / will use.

[0299] As an embodiment, not used / not unused means: not needing to be retained / needing to be retained.

[0300] As an example, not used / not not used refers to: not needed / needed.

[0301] As an embodiment, unused / not unused refers to: unused / not unused.

[0302] As an embodiment, unused / non-unused refers to: unused / used.

[0303] As an embodiment, if the first control information is sent in the first uplink grant, the first uplink grant includes the first control information.

[0304] As a sub-embodiment of this embodiment, a MAC PDU is generated for the HARQ entity corresponding to the first uplink grant.

[0305] As a sub-embodiment of this embodiment, a transport block is generated for the HARQ entity corresponding to the first uplink grant.

[0306] As a sub-embodiment of this embodiment, sending is performed on the first uplink grant.

[0307] As an embodiment, if the first control information is not sent in the first uplink grant, the first uplink grant does not include the first control information.

[0308] As a sub-embodiment of this embodiment, not sending the first control information in the first uplink grant means that the first uplink grant does not include the first control information.

[0309] As a sub-embodiment of this embodiment, not sending the first control information in the first uplink grant may be replaced by: not including the first control information in the first uplink grant.

[0310] As a sub-embodiment of this embodiment, the fact that the first control information is not included in the first uplink grant is used to determine not to send the first control information in the first uplink grant.

[0311] As a sub-embodiment of this embodiment, the PUSCH resources corresponding to the first control information are reserved.

[0312] As a sub-embodiment of this embodiment, the PUSCH resources corresponding to the first control information are used to send a transmission block (TB).

[0313] As a sub-embodiment of this embodiment, no transmission is performed on the PUSCH resources corresponding to the first control information.

[0314] As an embodiment, if the first control information is not sent in the first uplink grant, a MAC PDU is not generated for a HARQ (Hybrid Automatic Repeat Request) entity corresponding to the first uplink grant.

[0315] As a sub-embodiment of this embodiment, not sending the first control information in the first uplink grant means: not generating a MAC PDU for the HARQ entity corresponding to the first uplink grant.

[0316] As a sub-embodiment of this embodiment, not sending the first control information in the first uplink grant may be replaced by not generating a MAC PDU for the HARQ entity corresponding to the first uplink grant.

[0317] As a sub-embodiment of this embodiment, not generating a MAC PDU for the HARQ entity corresponding to the first uplink grant is used to determine not to send the first control information in the first uplink grant.

[0318] As a sub-embodiment of this embodiment, not generating a MAC PDU for the HARQ entity corresponding to the first uplink grant is used to determine not to perform any transmission on the first uplink grant.

[0319] As a sub-embodiment of this embodiment, not generating a MAC PDU for the HARQ entity corresponding to the first uplink grant is used to determine not generating a transport block for the HARQ entity corresponding to the first uplink grant.

[0320] As an embodiment, if the first control information is not sent in the first uplink grant, no sending is performed on the first uplink grant.

[0321] As a sub-embodiment of this embodiment, not sending the first control information in the first uplink grant means: not performing any sending on the first uplink grant.

[0322] As a sub-embodiment of this embodiment, not sending the first control information in the first uplink grant may be replaced by: not performing any sending on the first uplink grant.

[0323] As a sub-embodiment of this embodiment, no transmission is performed on the PUSCH resources corresponding to the first uplink grant.

[0324] As a sub-embodiment of this embodiment, not performing any transmission on the first uplink grant is used to determine not to send the first control information on the first uplink grant.

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

[0326] As an embodiment, the first node is configured with multiple MAC entities, the first MAC entity is one of the multiple MAC entities, and the operations in this application only involve the first MAC entity.

[0327] Example 2

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

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

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

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

[0332] As an embodiment, the node 203 is a base station (BS).

[0333] As an embodiment, the node 203 is a base transceiver station (BTS).

[0334] As an embodiment, the node 203 is a Node B (NB).

[0335] As an embodiment, the node 203 is a gNB.

[0336] As an embodiment, the node 203 is an eNB.

[0337] As an embodiment, the node 203 is an ng-eNB.

[0338] As an embodiment, the node 203 is an en-gNB.

[0339] As an embodiment, the node 203 is a CU (Centralized Unit).

[0340] As an embodiment, the node 203 is a DU (Distributed Unit).

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

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

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

[0344] As an embodiment, the user equipment supports transmission of a terrestrial network (Non-Terrestrial Network, NTN).

[0345] As an embodiment, the user equipment supports transmission on a non-terrestrial network (Terrestrial Network).

[0346] As an embodiment, the user equipment supports transmission in a network with a large delay difference.

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

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

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

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

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

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

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

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

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

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

[0357] As an embodiment, the base station device supports transmission in a network with large delay difference.

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

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

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

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

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

[0363] As an embodiment, the base station device includes a base station device that supports a large delay difference.

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

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

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

[0367] As an embodiment, the base station device includes a CU.

[0368] As an embodiment, the base station device includes a DU.

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

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

[0371] As an embodiment, the base station equipment includes an IAB (Integrated Access and Backhaul)-node.

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

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

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

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

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

[0377] As an embodiment, the relay includes a relay.

[0378] As an embodiment, the relay includes an L3 relay.

[0379] As an embodiment, the relay includes an L2 relay.

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

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

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

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

[0384] Example 3

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

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

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

[0388] As an embodiment, the first signal in the present application is generated by the PHY301 or PHY351.

[0389] As an embodiment, the second signal in the present application is generated by the PHY301 or PHY351.

[0390] As an embodiment, the third signal in the present application is generated by the RRC306.

[0391] As an embodiment, the third signal in the present application is generated by the MAC302 or MAC352.

[0392] As an embodiment, the third signal in the present application is generated by the PHY301 or PHY351.

[0393] As an embodiment, the fourth signal in the present application is generated by the RRC306.

[0394] As an embodiment, the fourth signal in the present application is generated by the MAC302 or MAC352.

[0395] As an embodiment, the fourth signal in the present application is generated by the PHY301 or PHY351.

[0396] As an embodiment, the fifth signal in the present application is generated by the RRC306.

[0397] As an embodiment, the fifth signal in the present application is generated by the MAC302 or MAC352.

[0398] As an embodiment, the fifth signal in the present application is generated by the PHY301 or PHY351.

[0399] As an embodiment, the first signaling in this application is generated in the RRC306.

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

[0401] As an embodiment, the first signaling in this application is generated in the PHY301 or PHY351.

[0402] Example 4

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

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

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

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

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

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

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

[0410] 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; wherein, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

[0411] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating an action when executed by at least one processor, the action 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; wherein, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

[0412] 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 together with the at least one processor. The second communication device 410 at least: 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; wherein whether the recipient of the first message sends first control information in the first uplink grant 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; and the first control information is used to indicate whether the uplink grant is not used. As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating an action when executed by at least one processor, the action 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; wherein, whether the recipient of the first message sends the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

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

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

[0415] 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 second message.

[0416] 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 the second message.

[0417] As an embodiment, at least one of the antenna 452 , the receiver 454 , the receive processor 456 , and the controller / processor 459 is configured to receive a first parameter.

[0418] 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 transmit the first parameter.

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

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

[0421] 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 second control information.

[0422] 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 second control information.

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

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

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

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

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

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

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

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

[0431] Example 5

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

[0433] For the first node U01, in step S5101, a first parameter is received; in step S5102, 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 S5103, first control information is sent in the first uplink grant.

[0434] For the second node N02, in step S5201, the first parameter is sent; in step S5202, the first message is sent; in step S5203, the first control information is received.

[0435] In embodiment 5, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

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

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

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

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

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

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

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

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

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

[0445] As an embodiment, the dotted box F5.1 is optional.

[0446] As an embodiment, the dotted box F5.1 exists.

[0447] As a sub-embodiment of this embodiment, the first parameter is received.

[0448] As a sub-embodiment of this embodiment, the first MAC entity of the first node U01 is configured with the first parameter to determine that the first MAC entity of the first node U01 is configured with the first parameter.

[0449] As a sub-embodiment of this embodiment, only when the first MAC entity of the first node U01 is configured with the first parameter, whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant.

[0450] As a sub-embodiment of this embodiment, under the assumption that the first MAC entity of the first node U01 is not configured with the first parameter, the first control information is always sent in the first uplink grant.

[0451] As a sub-embodiment of this embodiment, the first parameter is received and the value of the first parameter is true.

[0452] As a sub-embodiment of this embodiment, the first MAC entity of the first node U01 is configured with the first parameter and the value of the first parameter is true, which is used to determine that the first MAC entity of the first node U01 is configured with the first parameter.

[0453] As a sub-embodiment of this embodiment, whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant only when the first MAC entity of the first node U01 is configured with the first parameter and the value of the first parameter is true.

[0454] As a sub-embodiment of this embodiment, under the assumption that the first MAC entity of the first node U01 is not configured with the first parameter or the first MAC entity of the first node U01 is configured with the first parameter and the value of the first parameter is false, the first control information is always sent in the first uplink grant.

[0455] As a sub-embodiment of this embodiment, the first parameter is only applicable when one configuration period includes multiple uplink grants.

[0456] As a sub-embodiment of this embodiment, for an uplink grant configured by an RRC message before 3GPP Release 18, the first parameter is not effective.

[0457] As a sub-embodiment of this embodiment, the first parameter is effective only for an uplink grant configured by an RRC message of 3GPP Release 18 and belonging to a configuration period including multiple uplink grants.

[0458] As a sub-embodiment of this embodiment, the first parameter is not indicated by an enhancedSkipUplinkTxConfigured-r16 field, and the first parameter is not indicated by a skipUplinkTxDynamic field.

[0459] As a sub-embodiment of this embodiment, the name of the first parameter includes at least one of Skip or Uplink or Tx or Configured or Multiple or XR or enhanced or 2 or CTO.

[0460] As a sub-embodiment of this embodiment, the name of the first parameter includes enhancedSkipUplinkTxConfigured.

[0461] As a sub-embodiment of this embodiment, the first parameter is used to determine whether to abandon sending the first control information in the first uplink grant in dependence on an uplink grant subsequent to the first uplink grant.

[0462] As an embodiment, the dotted box F5.1 does not exist.

[0463] As a sub-embodiment of this embodiment, the first MAC entity of the first node U01 is configured with enhancedSkipUplinkTxConfigured and the value of enhancedSkipUplinkTxConfigured is true.

[0464] As a sub-embodiment of this embodiment, the MAC-CellGroupConfig to which the first message belongs includes an enhancedSkipUplinkTxConfigured field.

[0465] As a sub-embodiment of this embodiment, the first MAC entity of the first node U01 is configured with skipUplinkTxDynamic and the value of skipUplinkTxDynamic is true.

[0466] As a sub-embodiment of this embodiment, the MAC-CellGroupConfig to which the first message belongs includes a skipUplinkTxDynamic field.

[0467] As a sub-embodiment of this embodiment, the first MAC entity of the first node U01 is not configured with either enhancedSkipUplinkTxConfigured or skipUplinkTxDynamic whose values ​​are true.

[0468] As a sub-embodiment of this embodiment, the MAC-CellGroupConfig to which the first message belongs does not include either a skipUplinkTxDynamic field or an enhancedSkipUplinkTxConfigured field.

[0469] As a sub-embodiment of this embodiment, whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant only when the first MAC entity of the first node U01 is configured with enhancedSkipUplinkTxConfigured and the value of enhancedSkipUplinkTxConfigured is true.

[0470] As a sub-embodiment of this embodiment, the above method reuses existing configuration parameters to reduce the impact on the protocol.

[0471] As a sub-embodiment of this embodiment, whether to send the first control information in the first uplink grant depends on the uplink grant after the first uplink grant only when the first MAC entity of the first node U01 is configured with skipUplinkTxDynamic and the value of skipUplinkTxDynamic is true.

[0472] As a sub-embodiment of this embodiment, the above method reuses existing configuration parameters to reduce the impact on the protocol.

[0473] As a sub-embodiment of this embodiment, regardless of whether the first MAC entity of the first node U01 is configured with either enhancedSkipUplinkTxConfigured or skipUplinkTxDynamic, whether the first control information is sent in the first uplink grant depends on the uplink grant after the first uplink grant.

[0474] As a sub-embodiment of this embodiment, the above method does not rely on RRC configuration, thereby improving the flexibility of UE implementation.

[0475] As an embodiment, the dotted box F5.2 is optional.

[0476] As an embodiment, the first control information is sent in the first uplink grant; the dotted box F5.2 exists.

[0477] As an embodiment, the first control information is not sent in the first uplink grant; the dotted box F5.2 does not exist.

[0478] As an embodiment, whether the sending of the first control information in the first uplink grant depends on at least one uplink grant that is not used in the uplink grant after the first uplink grant, or the time domain position of the uplink grant and the position of the first symbol set after the first uplink grant, or whether the sending of the first control information in the first uplink grant depends on at least one of the size and effective data amount of the first uplink grant.

[0479] Example 6

[0480] Example 6 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in FIG6 .

[0481] For the first node U01, in step S6101, a second message is received, where the second message indicates a first symbol set.

[0482] For the second node N02, in step S6201, the second message is sent.

[0483] In embodiment 6, whether to send the first control information in the first uplink grant depends on the time domain position of the uplink grant after the first uplink grant and the position of the first symbol set.

[0484] As an embodiment, the second message is received before the first message is received.

[0485] As an embodiment, the second message is received after the first message is received.

[0486] As an embodiment, it is particularly noted that the order in this example does not limit the order of receiving the first message and the second message in this application.

[0487] As an embodiment, the first symbol set includes at least one time slot.

[0488] As an embodiment, the first symbol set is at least one symbol.

[0489] As an embodiment, the first symbol set includes at least 1 millisecond.

[0490] As an embodiment, the first symbol set includes at least 1 second.

[0491] As an embodiment, the first symbol set is not continuous in the time domain.

[0492] As an embodiment, whether the first set of symbols is continuous in the time domain is configurable.

[0493] As an embodiment, the first symbol set is configurable.

[0494] As an embodiment, the first symbol set is the time domain resource configured by the second message.

[0495] As an embodiment, the first symbol set is a time domain resource determined by the second message.

[0496] As an embodiment, the first symbol set is a time domain resource activated by the second message.

[0497] As an embodiment, the first symbol set is a time domain resource configured and activated by the second message.

[0498] As an embodiment, the first symbol set is a time domain resource corresponding to a time-frequency resource allocated to the secondary link.

[0499] As an embodiment, the above method reduces the impact on secondary link communication.

[0500] As an embodiment, the first symbol set is the time when a service cell of the first node U01 is in a network energy-saving state.

[0501] As a sub-embodiment of this embodiment, the first symbol set is the inactive time of DRX (Discontinuous Reception) / DTX (Discontinuous Transmission) of a serving cell of the first node U01.

[0502] As an embodiment, the first symbol set is the time at which a timer is running.

[0503] As a sub-embodiment of this embodiment, the timer is a timer of the MAC sublayer.

[0504] As a sub-embodiment of this embodiment, the maintenance of the timer is irrelevant to the random access procedure.

[0505] As a sub-embodiment of this embodiment, the timer is used for a random access procedure.

[0506] As a sub-embodiment of this embodiment, the timer is used to monitor downlink signaling during the random access process.

[0507] As a sub-embodiment of this embodiment, the one timer is a ra-ResponseWindow.

[0508] As a sub-embodiment of this embodiment, the timer is a msgB-ResponseWindow.

[0509] As a sub-embodiment of this embodiment, the timer is a ra-ContentionResolutionTimer.

[0510] As an embodiment, the second message is an RRC message.

[0511] As an embodiment, the second message includes at least one RRC message.

[0512] As an embodiment, the second message includes at least one RRC IE.

[0513] As an embodiment, the second message includes at least one RRC domain.

[0514] As an embodiment, the second message includes signaling of at least one protocol layer below the RRC protocol layer.

[0515] As an embodiment, the second message is signaling of at least one protocol layer below the RRC protocol layer.

[0516] As an embodiment, the second message configures the first set of symbols.

[0517] As an embodiment, the second message is used to determine the first set of symbols.

[0518] As an embodiment, the second message configures and activates the first set of symbols.

[0519] As an embodiment, the second message includes at least one RRC message, and the at least one RRC message is used to configure the first symbol set; the second message includes signaling of at least one protocol layer below the RRC protocol layer, and the signaling of the at least one protocol layer below the RRC protocol layer is used to activate the first symbol set.

[0520] As an embodiment, the second message indicates the first set of symbols in time domain resources for downlink transmission.

[0521] As a sub-embodiment of this embodiment, the time domain resource for downlink transmission is a downlink time slot.

[0522] As a sub-embodiment of this embodiment, the time domain resource for downlink transmission is a flexible time slot.

[0523] As a sub-embodiment of this embodiment, the time domain resource for downlink transmission is a downlink time slot or a flexible time slot.

[0524] As a sub-embodiment of this embodiment, each symbol in the first symbol set is configured for subband non-overlapping full duplex (SBFD).

[0525] As a sub-embodiment of this embodiment, a SIB1 (System Information Block 1) is used to configure the time domain resources for downlink transmission.

[0526] As a sub-embodiment of this embodiment, a ServingCellConfigCommon IE is used to configure the time domain resources for downlink transmission.

[0527] As a sub-embodiment of this embodiment, a ServingCellConfigCommonSIB IE is used to configure the time domain resources for downlink transmission.

[0528] As a sub-embodiment of this embodiment, a BWP-Uplink IE is used to configure the time domain resources for downlink transmission.

[0529] As a sub-embodiment of this embodiment, a BWP-UplinkCommon IE is used to configure the time domain resources for downlink transmission.

[0530] As a sub-embodiment of this embodiment, a tdd-UL-DL-ConfigurationCommon field is used to configure the time domain resources for downlink transmission.

[0531] As a sub-embodiment of this embodiment, an RRC domain whose name includes tdd-UL-DL-ConfigurationCommon is used to configure the time domain resources for downlink transmission.

[0532] As a sub-embodiment of this embodiment, a TDD-UL-DL-ConfigCommon IE is used to configure the time domain resources for downlink transmission.

[0533] As a sub-embodiment of this embodiment, a TDD-UL-DL-Pattern IE is used to configure the time domain resources for downlink transmission.

[0534] As a sub-embodiment of this embodiment, a TDD-UL-DL-ConfigDedicated IE is used to configure the time domain resources for downlink transmission.

[0535] As an embodiment, the first symbol set is an activated measurement gap.

[0536] As a sub-embodiment of this embodiment, the above method reduces the impact on the activated measurement interval.

[0537] As a sub-embodiment of this embodiment, the first symbol set is the duration of an activated measurement interval.

[0538] As a sub-embodiment of this embodiment, the first symbol set is a time domain resource occupied by an activated measurement interval.

[0539] As a sub-embodiment of this embodiment, the first symbol set is configured for the time of an activated measurement interval.

[0540] As a sub-embodiment of this embodiment, the one activated measurement interval is used to perform measurement.

[0541] As a sub-embodiment of this embodiment, the activated measurement interval is an FR1 (Frequency range 1) measurement interval.

[0542] As a sub-embodiment of this embodiment, the activated measurement interval is an FR2 (Frequency range 2) measurement interval.

[0543] As a sub-embodiment of this embodiment, the frequency domain resources corresponding to the activated measurement interval overlap with the frequency domain resources granted in the uplink configured by the first message.

[0544] As a sub-embodiment of this embodiment, the frequency domain resources corresponding to the activated measurement interval belong to the frequency domain resources granted in the uplink configured by the first message.

[0545] As a sub-embodiment of this embodiment, the frequency domain resources granted in the uplink configured by the first message belong to the frequency domain resources corresponding to the one activated measurement interval.

[0546] As a sub-embodiment of this embodiment, the frequency domain resources corresponding to the activated measurement interval and the frequency domain resources granted in the uplink configured by the first message do not overlap.

[0547] As an embodiment, the first symbol set is a time domain resource allocated to a candidate uplink grant.

[0548] As a sub-embodiment of this embodiment, the first symbol set is a PUSCH duration allocated to a candidate uplink grant.

[0549] As a sub-embodiment of this embodiment, the candidate uplink grant is addressed to a Temporary C-RNTI.

[0550] As a sub-embodiment of this embodiment, the above method reduces the impact on random access.

[0551] As a sub-embodiment of this embodiment, the candidate uplink grant is dynamically received on the PDCCH.

[0552] As a sub-embodiment of this embodiment, the candidate uplink grant is received in a random access response (Random Access Response, RAR).

[0553] As a sub-embodiment of this embodiment, the above method reduces the impact on random access.

[0554] As a sub-embodiment of this embodiment, the candidate uplink grant is configured semi-persistently by RRC.

[0555] As a sub-embodiment of this embodiment, the candidate uplink grant is determined according to the PUSCH resource associated with MSGA (Message A).

[0556] As a sub-embodiment of this embodiment, the above method reduces the impact on random access.

[0557] As a sub-embodiment of this embodiment, the candidate uplink grant is a DG (Dynamic Grant).

[0558] As a sub-embodiment of this embodiment, the above method reduces the impact on uplink granting of dynamic scheduling.

[0559] As a sub-embodiment of this embodiment, the candidate uplink grant is a CG; the one CG is not an uplink grant in the uplink grant configured by the first message.

[0560] As a sub-embodiment of this embodiment, the candidate uplink grant has a higher priority than the target uplink grant.

[0561] As a sub-embodiment of this embodiment, the above method reduces the impact on uplink grants with higher priorities.

[0562] As a sub-embodiment of this embodiment, the MAC entity is configured with lch-based Prioritization.

[0563] As a sub-embodiment of this embodiment, the MAC entity is not configured with lch-based Prioritization.

[0564] As a sub-embodiment of this embodiment, the MAC entity is configured with lch-based Prioritization; the candidate uplink grant is addressed to the Temporary C-RNTI, or the candidate uplink grant is received in a random access response, or the candidate uplink grant is associated with an MSGA payload.

[0565] As a sub-embodiment of this embodiment, the MAC entity is not configured with lch-based Prioritization; the candidate uplink grant is dynamically received on the PDCCH, or the candidate uplink grant is received in a random access response, or the candidate uplink grant is associated with the MSGA payload.

[0566] As an embodiment, whether to send the first control information in the first uplink grant depends on the time domain position of at least one uplink grant and the position of the first symbol set in the uplink grant after the first uplink grant.

[0567] As an embodiment, whether to send the first control information in the first uplink grant depends on the time domain position of each uplink grant and the position of the first symbol set in the uplink grant after the first uplink grant.

[0568] As an embodiment, whether the first control information is sent in the first uplink grant depends on whether the uplink grant after the first uplink grant and the first symbol set overlap.

[0569] As an embodiment, whether the first control information is sent in the first uplink grant depends on whether the uplink grant after the first uplink grant belongs to the first symbol set.

[0570] As an embodiment, if each uplink grant in the uplink grant after the first uplink grant overlaps with the first symbol set, the first control information is not sent in the first uplink grant; if at least one uplink grant in the uplink grant after the first uplink grant does not overlap with the first symbol set, the first control information is sent in the first uplink grant.

[0571] As an embodiment, if each uplink grant in the uplink grant after the first uplink grant belongs to the first symbol set, the first control information is not sent in the first uplink grant; if at least one uplink grant in the uplink grant after the first uplink grant does not belong to the first symbol set, the first control information is sent in the first uplink grant.

[0572] As an embodiment, if each uplink grant in the uplink grant after the first uplink grant belongs to the first symbol set, not sending the first control information in the first uplink grant is used to implicitly indicate that each uplink grant in the uplink grant after the first uplink grant is not used.

[0573] As an embodiment, the uplink grant that overlaps with the first symbol set indicated by the second message is indicated as not being used by the first control information.

[0574] As an embodiment, the uplink grant that overlaps with the first symbol set indicated by the second message is considered to be an uplink grant with reduced priority.

[0575] As an embodiment, when one of the uplink grants following the first uplink grant overlaps with the first set of symbols, whether the uplink grant is not used is predefined.

[0576] As an embodiment, the second node N02 determines whether the uplink grant is not used according to whether an uplink grant in the uplink grants after the first uplink grant overlaps with the first symbol set.

[0577] As an embodiment, the above method avoids indicating redundant information through the first control information.

[0578] As an embodiment, the above method reduces signaling overhead.

[0579] Example 7

[0580] Example 7 illustrates a wireless signal transmission flow chart according to yet another embodiment of the present application, as shown in FIG7 .

[0581] For the first node U01, in step S7101, second control information is sent.

[0582] For the second node N02, in step S7201, the second control information is received.

[0583] In embodiment 7, the second control information indicates whether to send the first control information in the first uplink grant.

[0584] As an embodiment, step S5103 is executed.

[0585] As an embodiment, step S5103 is not executed.

[0586] As an embodiment, the second control information occupies at least one bit.

[0587] As an embodiment, the second control information occupies multiple bits.

[0588] As an embodiment, the second control information occupies one bit.

[0589] As an embodiment, the second control information is sent on an uplink grant other than the first uplink grant.

[0590] As an embodiment, the second control information is sent on a PUCCH (Physical Uplink Control CHannel).

[0591] As a sub-embodiment of this embodiment, the second control information occupies PUCCH resources.

[0592] As a sub-embodiment of this embodiment, the second control information is sent before the start time of the first uplink grant in the time domain.

[0593] As a sub-embodiment of this embodiment, the PUCCH resources occupied by the second control information are configured by an RRC message.

[0594] As an embodiment, the second control information is sent on the first uplink grant.

[0595] As a sub-embodiment of this embodiment, the first uplink grant carries the second control information.

[0596] As a sub-embodiment of this embodiment, the second control information is part of the bits of the PUSCH transmission corresponding to the first uplink grant.

[0597] As a sub-embodiment of this embodiment, the second control information is transmitted on a PUSCH corresponding to the first uplink grant.

[0598] As a sub-embodiment of this embodiment, in the PUSCH resources corresponding to the first uplink grant, the bits allocated to the second control information are higher than the bits allocated to the first control information.

[0599] As a sub-embodiment of this embodiment, in the PUSCH resources corresponding to the first uplink grant, the time domain resources allocated to the second control information are earlier than the time domain resources allocated to the first control information.

[0600] As an embodiment, the value of the second control information indicates whether the first control information is sent in the first uplink grant.

[0601] As a sub-embodiment of this embodiment, if the second control information is set to 1, the second control information indicates that the first control information is sent on the first uplink grant; if the second control information is set to 0, the second control information indicates that the first control information is not sent on the first uplink grant.

[0602] As a sub-embodiment of this embodiment, if the second control information is set to 0, the second control information indicates that the first control information is sent on the first uplink grant; if the second control information is set to 1, the second control information indicates that the first control information is not sent on the first uplink grant.

[0603] As an embodiment, whether the second control information is sent indicates whether the first control information is sent in the first uplink grant.

[0604] As a sub-embodiment of this embodiment, if the second control information is sent, it indicates that the first control information is sent on the first uplink grant; if the second control information is not sent, it indicates that the first control information is not sent on the first uplink grant.

[0605] As a sub-embodiment of this embodiment, the second control information is sent only when the first control information is sent on the first uplink grant.

[0606] As a sub-embodiment of this embodiment, if the second control information is not sent, it indicates that the first control information is sent on the first uplink grant; if the second control information is sent, it indicates that the first control information is not sent on the first uplink grant.

[0607] As a sub-embodiment of this embodiment, the second control information is sent only when the first control information is not sent in the first uplink grant.

[0608] As a sub-embodiment of this embodiment, the above method reduces the sending of the second control information and saves signaling overhead.

[0609] As a sub-embodiment of this embodiment, the above method improves resource utilization.

[0610] As an embodiment, when the first control information is not sent on the first uplink grant, the PUSCH resources corresponding to the first control information are used for transmission blocks.

[0611] As an embodiment, when the first control information is not sent on the first uplink grant, the PUSCH resources corresponding to the first control information are used for MAC PDU.

[0612] Example 8

[0613] Embodiment 8 illustrates a schematic diagram of whether there is at least one unused uplink grant in the uplink grant after the first control information is sent in the first uplink grant depending on the first uplink grant according to an embodiment of the present application, as shown in FIG8 .

[0614] In Example 8, whether the first control information is sent in the first uplink grant depends on whether there is at least one unused uplink grant in the uplink grant after the first uplink grant; when there is at least one unused uplink grant in the uplink grant after the first uplink grant, the first control information is sent in the first uplink grant; when there is no unused uplink grant in the uplink grant after the first uplink grant, the first control information is not sent in the first uplink grant.

[0615] As an embodiment, whether to send the first control information in the first uplink grant is determined based on whether there is at least one uplink grant that is not used in the uplink grant after the first uplink grant.

[0616] As an embodiment, whether there is at least one uplink grant in the uplink grant after the first uplink grant that is not used is used to determine whether to send the first control information in the first uplink grant.

[0617] As an embodiment, the fact that at least one uplink grant is not used in the uplink grants after the first uplink grant means that one or more uplink grants are not used in the uplink grants after the first uplink grant.

[0618] As an embodiment, the fact that there is at least one unused uplink grant in the uplink grants after the first uplink grant means: as long as there is an unused uplink grant in the uplink grants after the first uplink grant.

[0619] As an embodiment, the fact that at least one uplink grant in the uplink grants after the first uplink grant is not used means that all uplink grants other than those after the first uplink grant are not unused.

[0620] As an embodiment, the fact that there is no unused uplink grant in the uplink grants after the first uplink grant means that each uplink grant in the uplink grants after the first uplink grant is not unused.

[0621] As an embodiment, the fact that none of the uplink grants after the first uplink grant is unused means that none of the uplink grants after the first uplink grant is unused.

[0622] As an embodiment, the fact that there does not exist any uplink grant that is not used in the uplink grants after the first uplink grant means that all uplink grants in the uplink grants after the first uplink grant are not unused.

[0623] Example 9

[0624] Embodiment 9 illustrates a schematic diagram showing whether to send the first control information in the first uplink grant depends on the size of the first uplink grant and the amount of valid data according to an embodiment of the present application, as shown in FIG9 .

[0625] In embodiment 9, whether to send the first control information in the first uplink grant depends on the size and valid data amount of the first uplink grant.

[0626] As an embodiment, when the first uplink grant can accommodate the valid data, and the first uplink grant cannot accommodate the valid data and the first control information at the same time, the first control information is not sent in the first uplink grant; when the first uplink grant cannot accommodate the valid data, or the first uplink grant can accommodate the valid data and the first control information at the same time, the first control information is sent in the first uplink grant.

[0627] As an embodiment, whether the first control information is sent in the first uplink grant depends on the size and effective data amount of the first uplink grant, and whether there is at least one uplink grant that is not unused in the uplink grant after the first control information is sent in the first uplink grant depends on the first uplink grant.

[0628] As a sub-embodiment of this embodiment, when the first uplink grant can accommodate the valid data, and the first uplink grant cannot accommodate the valid data and the first control information at the same time, and each uplink grant in the uplink grant after the first uplink grant is not used, the first control information is not sent in the first uplink grant.

[0629] As a sub-embodiment of this embodiment, when the first uplink grant cannot accommodate the valid data, or the first uplink grant can accommodate the valid data and the first control information at the same time, or there is at least one uplink grant that is not unused in the uplink grant after the first uplink grant, the first control information is sent in the first uplink grant.

[0630] As a sub-embodiment of this embodiment, not sending the first control information in the first uplink grant is used to implicitly indicate that each uplink grant in the uplink grants after the first uplink grant is not used.

[0631] As an embodiment, whether to send the first control information in the first uplink grant depends on the size and valid data amount of the first uplink grant and the uplink grant after the first uplink grant.

[0632] As an embodiment, when the first uplink grant and the uplink grant after the first uplink grant can accommodate the valid data, and the first uplink grant and the uplink grant after the first uplink grant cannot accommodate the valid data and the first control information at the same time, the first control information is not sent in the first uplink grant; when the first uplink grant and the uplink grant after the first uplink grant cannot accommodate the valid data, or the first uplink grant and the uplink grant after the first uplink grant can accommodate the valid data and the first control information at the same time, the first control information is sent in the first uplink grant.

[0633] As an embodiment, the first uplink grant being able to accommodate the valid data means that the size of the first uplink grant is not less than the amount of valid data.

[0634] As an embodiment, the first uplink grant being able to accommodate the valid data means that the number of bits in the first uplink grant that can be used to carry the valid data and the first control information is not less than the amount of valid data.

[0635] As an embodiment, the valid data refers to: all pending data available for transmission.

[0636] As an embodiment, the valid data includes uplink valid data of at least one LCG (Logical Channel Group) associated with the first MAC entity.

[0637] As an embodiment, the valid data includes uplink valid data of at least one logical channel (Logical Channel) associated with the first MAC entity.

[0638] As an embodiment, the valid data includes uplink valid data of any logical channel associated with the first MAC entity.

[0639] As an embodiment, the effective data volume refers to: the total amount of effective data.

[0640] As an embodiment, the valid data includes: available data.

[0641] As an embodiment, the valid data includes: data packets of the PDCP sublayer.

[0642] As an embodiment, the valid data includes: data packets of the RLC sublayer.

[0643] As an embodiment, the valid data includes: data packets of the PDCP sublayer and data packets of the RLC sublayer.

[0644] As an embodiment, the valid data includes: a MAC subheader.

[0645] As an embodiment, the valid data includes: the size of the MAC PDU corresponding to the valid data packet.

[0646] As an embodiment, the valid data includes: cached data packets.

[0647] As an embodiment, the valid data includes: data packets that have not yet arrived.

[0648] As an embodiment, the valid data includes: data packets before a given moment.

[0649] As an embodiment, the given moment is related to the latest uplink grant in the time domain among the uplink grants after the first uplink grant.

[0650] As an embodiment, the given time is related to PDB (PDU Delay Budget).

[0651] As an embodiment, the given time is related to PSDB (PDU Set Delay Budget).

[0652] As an embodiment, a PDU set includes at least one related PDU.

[0653] As an embodiment, a PDU set includes multiple related PDUs.

[0654] Example 10

[0655] Embodiment 10 illustrates a schematic diagram of a first uplink grant satisfying a first condition set according to an embodiment of the present application, as shown in FIG10 .

[0656] In embodiment 10, the first uplink grant satisfies a first set of conditions, one of which is that the MAC PDU corresponding to the first uplink grant does not have a MAC SDU.

[0657] As an embodiment, one of the conditions in the first condition set is that no UCI other than the first control information is multiplexed in the PUSCH transmission corresponding to the first uplink grant.

[0658] As an embodiment, the first condition set does not include UCI other than the first control information being multiplexed in the PUSCH transmission corresponding to the first uplink grant.

[0659] As a sub-embodiment of this embodiment, UCI other than the first control information is not allowed to be multiplexed in the PUSCH transmission corresponding to the first uplink grant.

[0660] As a sub-embodiment of this embodiment, UCI other than the control information used to indicate whether an uplink grant is not used is not allowed to be multiplexed in PUSCH transmission corresponding to any uplink grant configured by the first message.

[0661] As an embodiment, one of the conditions in the first condition set is that there is no aperiodic CSI (Channel Status Information) request for the corresponding PUSCH transmission for the first uplink grant.

[0662] As an embodiment, the first condition set does not include non-periodic CSI requests for which no corresponding PUSCH transmission is granted for the first uplink.

[0663] As a sub-embodiment of this embodiment, non-periodic CSI request for PUSCH transmission corresponding to the first uplink grant is not allowed.

[0664] As a sub-embodiment of this embodiment, non-periodic CSI requests for PUSCH transmission corresponding to any uplink grant configured by the first message are not allowed.

[0665] As an embodiment, one of the conditions in the first condition set is that the MAC PDU corresponding to the first uplink grant only includes a periodic BSR (Buffer Status Report) and any LCG has no available data, or that the MAC PDU corresponding to the first uplink grant only includes a padding BSR.

[0666] As an embodiment, the first condition set does not include that the MAC PDU corresponding to the first uplink grant only includes a periodic BSR and any LCG has no available data, or that the MAC PDU corresponding to the first uplink grant only includes a padding BSR.

[0667] As an embodiment, if any condition in the first condition set is not met, the first control information is sent in the first uplink grant.

[0668] As an embodiment, the first condition set is that the MAC PDU corresponding to the first uplink grant has no MAC SDU, or there is no UCI other than the first control information multiplexed in the PUSCH transmission corresponding to the first uplink grant, or there is no non-periodic CSI request for the PUSCH transmission corresponding to the first uplink grant, or the MAC PDU corresponding to the first uplink grant only includes a periodic BSR and any LCG has no available data or the MAC PDU corresponding to the first uplink grant only includes at least the former of the padding BSR.

[0669] As an embodiment, the first condition set is:

[0670] -. No UCI other than the first control information is multiplexed in the first uplink grant corresponding to the PUSCH transmission, and,

[0671] -. There is no aperiodic CSI request for the first uplink grant corresponding to the PUSCH transmission, and,

[0672] -. The MAC PDU corresponding to the first uplink grant has no MAC SDU, and,

[0673] -. The MAC PDU corresponding to the first uplink grant includes only a periodic BSR and no data is available in any LCG, or the MAC PDU corresponding to the first uplink grant includes only a padding BSR.

[0674] As an embodiment, the first condition set is:

[0675] -. There is no aperiodic CSI request for the first uplink grant corresponding to the PUSCH transmission, and,

[0676] -. The MAC PDU corresponding to the first uplink grant has no MAC SDU, and,

[0677] -. The MAC PDU corresponding to the first uplink grant includes only a periodic BSR and no data is available in any LCG, or the MAC PDU corresponding to the first uplink grant includes only a padding BSR.

[0678] As an embodiment, the first condition set is:

[0679] -. The MAC PDU corresponding to the first uplink grant has no MAC SDU, and,

[0680] -. The MAC PDU corresponding to the first uplink grant includes only a periodic BSR and no data is available in any LCG, or the MAC PDU corresponding to the first uplink grant includes only a padding BSR.

[0681] As an embodiment, the first condition set is:

[0682] -.The MAC PDU corresponding to the first uplink grant does not have a MAC SDU.

[0683] As an embodiment, the first condition set is:

[0684] -. There is no aperiodic CSI request for the first uplink grant corresponding to the PUSCH transmission, and,

[0685] -.The MAC PDU corresponding to the first uplink grant does not have a MAC SDU.

[0686] As an embodiment, the first condition set is:

[0687] -. No UCI other than the first control information is multiplexed in the first uplink grant corresponding to the PUSCH transmission, and,

[0688] -. There is no aperiodic CSI request for the first uplink grant corresponding to the PUSCH transmission, and,

[0689] -.The MAC PDU corresponding to the first uplink grant does not have a MAC SDU.

[0690] Example 11

[0691] Embodiment 11 illustrates a schematic diagram of not generating a MAC PDU for a HARQ entity corresponding to a first uplink grant according to an embodiment of the present application, as shown in FIG11. In FIG11, in block 1101, the first uplink grant satisfies the first set of conditions, and no uplink grant after the first uplink grant is unused; in block 1102, a MAC PDU is not generated for the HARQ entity corresponding to the first uplink grant.

[0692] In embodiment 11, when the first uplink grant satisfies the first condition set and there is no unused uplink grant in the uplink grants after the first uplink grant, a MAC PDU is not generated for the HARQ entity corresponding to the first uplink grant.

[0693] As an embodiment, the first uplink grant satisfies the first condition set and there is no uplink grant in the uplink grant after the first uplink grant that is not used to trigger not generating a MAC PDU for the HARQ entity corresponding to the first uplink grant.

[0694] As an embodiment, whether sending the first control information in the first uplink grant depends on the uplink grant after the first uplink grant refers to: whether there is at least one uplink grant that is not used in the uplink grant after sending the first control information in the first uplink grant depends on the first uplink grant.

[0695] As an embodiment, not sending the first control information in the first uplink grant means: not generating a MAC PDU for the HARQ entity corresponding to the first uplink grant.

[0696] As an embodiment, the first parameter is not received, and the first MAC entity of the first node is not configured with enhancedSkipUplinkTxConfigured.

[0697] As an embodiment, when the first parameter is received, and the first uplink grant satisfies the first condition set, and there is no uplink grant that is not used in the uplink grant after the first uplink grant, the first control information is not sent in the first uplink grant.

[0698] As an embodiment, when the first MAC entity of the first node is configured with enhancedSkipUplinkTxConfigured, and the first uplink grant satisfies the first condition set, and there is no uplink grant that is not used in the uplink grant after the first uplink grant, the first control information is not sent in the first uplink grant.

[0699] Example 12

[0700] Embodiment 12 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in FIG12. In FIG12, the processing device 1200 in the first node includes a first receiver 1201 and a first transmitter 1202.

[0701] A first receiver 1201 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;

[0702] In Example 12, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

[0703] As an embodiment, whether the first control information is sent in the first uplink grant depends on whether there is at least one unused uplink grant in the uplink grant after the first uplink grant; when there is at least one unused uplink grant in the uplink grant after the first uplink grant, the first control information is sent in the first uplink grant; when there is no unused uplink grant in the uplink grant after the first uplink grant, the first control information is not sent in the first uplink grant.

[0704] As an embodiment, the first receiver 1201 receives a second message, and the second message indicates a first symbol set; wherein, whether the first control information is sent in the first uplink grant depends on the time domain position of the uplink grant after the first uplink grant and the position of the first symbol set.

[0705] As an embodiment, the first uplink grant satisfies a first set of conditions, one of the conditions in the first set of conditions being that the MAC PDU corresponding to the first uplink grant does not have a MAC SDU.

[0706] As an embodiment, whether to send the first control information in the first uplink grant depends on the size and effective data amount of the first uplink grant.

[0707] As an embodiment, the first transmitter 1202 sends second control information; wherein, the second control information indicates whether to send the first control information when the first uplink is granted.

[0708] As an embodiment, the first receiver 1201 receives a first parameter; wherein the first parameter is used to determine whether sending the first control information in the first uplink grant depends on the uplink grant after the first uplink grant; the first parameter is not either enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured.

[0709] As an embodiment, the first receiver 1201 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.

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

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

[0712] As an embodiment, the first transmitter 1202 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.

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

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

[0715] Example 13

[0716] Embodiment 13 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in FIG13. In FIG13, the processing device 1300 in the second node includes a second transmitter 1301 and a second receiver 1302.

[0717] The second transmitter 1301 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;

[0718] In Example 13, whether the recipient of the first message sends the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

[0719] As an embodiment, whether the receiver of the first message sends the first control information in the first uplink grant depends on whether there is at least one unused uplink grant in the uplink grant after the first uplink grant; when there is at least one unused uplink grant in the uplink grant after the first uplink grant, the first control information is sent in the first uplink grant; when there is no unused uplink grant in the uplink grant after the first uplink grant, the first control information is not sent in the first uplink grant.

[0720] As an embodiment, the second transmitter 1301 sends a second message, and the second message indicates a first symbol set; wherein, whether the receiver of the first message sends the first control information in the first uplink grant depends on the time domain position of the uplink grant after the first uplink grant and the position of the first symbol set.

[0721] As an embodiment, the first uplink grant satisfies a first set of conditions, one of the conditions in the first set of conditions being that the MAC PDU corresponding to the first uplink grant does not have a MAC SDU.

[0722] As an embodiment, whether the receiver of the first message sends the first control information in the first uplink grant depends on the size and effective data amount of the first uplink grant.

[0723] As an embodiment, the second receiver 1302 receives second control information; wherein, the second control information indicates whether to send the first control information in the first uplink grant.

[0724] As an embodiment, the second transmitter 1301 sends a first parameter; wherein the first parameter is used to determine whether sending the first control information in the first uplink grant depends on the uplink grant after the first uplink grant; the first parameter is not either enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured.

[0725] As an embodiment, the second transmitter 1301 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.

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

[0727] As an embodiment, the second transmitter 1301 includes the antenna 420, transmitter 418, and transmission processor 416 in FIG. 4 of the present application.

[0728] As an embodiment, the second receiver 1302 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.

[0729] As an embodiment, the second receiver 1302 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.

[0730] As an embodiment, the second receiver 1302 includes the antenna 420, the receiver 418, and the receiving processor 470 in FIG. 4 of the present application.

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

[0732] 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; Among them, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

2. The first node according to claim 1, characterized in that: whether sending the first control information in the first uplink grant depends on whether there is at least one unused uplink grant in the uplink grant after the first uplink grant; when there is at least one unused uplink grant in the uplink grant after the first uplink grant, sending the first control information in the first uplink grant; When there is no unused uplink grant in the uplink grants after the first uplink grant, the first control information is not sent in the first uplink grant.

3. The first node according to claim 2, characterized in that: include: The first receiver receives a second message, wherein the second message indicates a first set of symbols; Whether to send the first control information in the first uplink grant depends on the time domain position of the uplink grant after the first uplink grant and the position of the first symbol set.

4. The first node according to any one of claims 1 to 3, characterized in that: The first uplink grant satisfies a first set of conditions, one of the conditions in the first set of conditions being that a MAC PDU corresponding to the first uplink grant has no MAC SDU.

5. The first node according to any one of claims 1 to 3, characterized in that: Whether to send the first control information in the first uplink grant depends on the size and effective data amount of the first uplink grant.

6. The first node according to any one of claims 1 to 5, characterized in that: include: A first transmitter sends second control information; The second control information indicates whether to send the first control information in the first uplink grant.

7. The first node according to any one of claims 1 to 6, characterized in that: include: The first receiver receives a first parameter; The first parameter is used to determine whether sending the first control information in the first uplink grant depends on the uplink grant after the first uplink grant; the first parameter is not any one of enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured.

8. 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; Whether the receiver of the first message sends the first control information in the first uplink grant 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; and the first control information is used to indicate whether the uplink grant is not used.

9. 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; Among them, whether to send the first control information in the first uplink grant 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; the first control information is used to indicate whether the uplink grant is not used.

10. 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; Whether the receiver of the first message sends the first control information in the first uplink grant 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; and the first control information is used to indicate whether the uplink grant is not used.

Citation Information

Patent Citations

  • Terminal device, base station device, and communication method

    CN113196849A

  • Method and apparatus in node used for wireless communication

    CN115915175A

  • Power control techniques for uplink control information transmissions in wireless communications

    US20190297580A1