Method and apparatus in node used for wireless communication

Abstract

The invention discloses a method and an apparatus in a node used for wireless communication. The first receiver receives a first signaling, and the first signaling is used for determining a target air interface resource pool; a first transmitter for transmitting first information; wherein the first information is used for indicating whether to send the PUSCH in the target air interface resource pool; the first transmitter is related to at least one of whether the PUSCH and the first information are sent in the target air interface resource pool or not and whether the target air interface resource pool is overlapped with a feature resource or not, and the feature resource is a resource for at least one UCI; when either a first condition or a second condition is satisfied, the first transmitter transmits a PUSCH in the target air interface resource pool, and first MCS information is used for the transmission of the PUSCH; the first condition comprises that the target air interface resource pool is overlapped with a feature resource, and the second condition comprises that the first information indicates that the PUSCH is sent in the target air interface resource pool.

Description

Technical Field

[0001] This application relates to transmission methods and apparatus in wireless communication systems, and more particularly to methods and apparatus for transmitting wireless signals in wireless communication systems supporting cellular networks. Background Technology

[0002] XR (Extended Reality) is considered a highly promising technology, and the optimal form and development trend for promoting large-scale XR applications will become one of the typical applications of future communications. Supporting XR services in 5G NR (New Radio) is an important aspect of system design. Based on the service characteristics of XR, enhancing the uplink transmission of ConfiguredGrant (CG) is an effective means to achieve XR support; how to determine whether to send the PUSCH corresponding to the enhanced CG is a crucial issue that must be considered. Summary of the Invention

[0003] To address the aforementioned problems, this application discloses a solution. It should be noted that the above description uses XR as an example; this application is also applicable to other scenarios, such as eMBB (Enhancement Mobile Broadband), URLLC (Ultra-Reliable and Low-Latency Communication), MBS (Multicast Broadcast Services), IoT (Internet of Things), vehicle-to-everything (V2X), NTN (non-terrestrial networks), and shared spectrum, achieving similar technical effects. Furthermore, adopting a unified solution across different scenarios (including but not limited to XR, eMBB, URLLC, MBS, IoT, V2X, NTN, and shared spectrum) can help reduce hardware complexity and cost, or improve performance. Unless otherwise specified, embodiments and features in any node of this application can be applied to any other node. Unless otherwise specified, embodiments and features in any node of this application can be arbitrarily combined with each other.

[0004] As an example, the interpretation of the terminology in this application is based on the definition in the 3GPP specification protocol TS36 series.

[0005] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS38 series.

[0006] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS37 series.

[0007] As an example, the interpretation of terms in this application is based on the definitions in the IEEE (Institute of Electrical and Electronics Engineers) specification protocols.

[0008] This application discloses a method used in a first node of wireless communication, characterized by comprising:

[0009] Receive the first signaling, which is used to determine the target air interface resource pool;

[0010] Send the first message;

[0011] Wherein, the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether to send a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, a PUSCH is sent in the target air interface resource pool, and the first MCS information is used for the sending of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that a PUSCH is sent in the target air interface resource pool.

[0012] As an example, the advantages of the above method include: improved performance of UCI feedback.

[0013] As an example, the advantages of the above method include: improved performance of user data transmission.

[0014] As an example, the advantages of the above method include: simplifying system design and reducing the detection complexity on the base station side.

[0015] As an example, the advantages of the above method include avoiding inconsistencies in the understanding between the communicating parties regarding whether or not PUSCH has been sent.

[0016] As an example, the advantages of the above method include: it helps to meet the latency requirements of business operations.

[0017] As an example, the advantages of the above method include: improved resource utilization.

[0018] As an example, the advantages of the above method include good compatibility.

[0019] As an example, the advantages of the above method include minimal changes to existing 3GPP standards.

[0020] According to one aspect of this application, the above method is characterized in that,

[0021] The first set of conditions includes at least the first condition and the second condition; when any condition in the first set of conditions is met, PUSCH is sent in the target air interface resource pool; when none of the conditions in the first set of conditions are met, PUSCH transmission is abandoned in the target air interface resource pool.

[0022] According to one aspect of this application, the above method is characterized in that,

[0023] When the first condition is met and the first information indicates that PUSCH is not sent in the target air interface resource pool, PUSCH is sent in the target air interface resource pool.

[0024] According to one aspect of this application, the above method is characterized in that,

[0025] When the first condition is not met and the first information indicates that PUSCH should not be sent in the target air interface resource pool, the sending of PUSCH is abandoned in the target air interface resource pool.

[0026] According to one aspect of this application, the above method is characterized in that,

[0027] The first signaling is used to identify multiple air interface resource pools, the target air interface resource pool being one of the multiple air interface resource pools, and an air interface resource pool other than the target air interface resource pool being used to send the first information.

[0028] According to one aspect of this application, the above method is characterized in that,

[0029] The first information includes a bitmap, in which any bit is used to indicate whether a PUSCH is sent in one of the plurality of air interface resource pools.

[0030] According to one aspect of this application, the above method is characterized in that,

[0031] The multiple air interface resource pools are multiple PUSCH opportunities. The multiple air interface resource pools are in the same CG period. The first information is sent in the first PUSCH opportunity among the multiple PUSCH opportunities. The multiple air interface resource pools do not overlap with each other in the time domain.

[0032] According to one aspect of this application, the above method is characterized in that,

[0033] The target air interface resource pool is a PUSCH opportunity.

[0034] According to one aspect of this application, the above method is characterized in that,

[0035] The target air interface resource pool is a CG PUSCH opportunity.

[0036] This application discloses a method used in a second node for wireless communication, characterized by comprising:

[0037] Send a first signaling message, which is used to determine the target air interface resource pool;

[0038] Receive the first message;

[0039] Wherein, the first information is used to indicate whether to send PUSCH in the target air interface resource pool; whether to receive PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, PUSCH is received in the target air interface resource pool, and the first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that PUSCH is sent in the target air interface resource pool.

[0040] According to one aspect of this application, the above method is characterized in that,

[0041] The first set of conditions includes at least the first condition and the second condition; when any condition in the first set of conditions is met, PUSCH is received in the target air interface resource pool; when none of the conditions in the first set of conditions are met, PUSCH reception is abandoned in the target air interface resource pool.

[0042] According to one aspect of this application, the above method is characterized in that,

[0043] When the first condition is met and the first information indicates that no PUSCH is sent in the target air interface resource pool, PUSCH is received in the target air interface resource pool.

[0044] According to one aspect of this application, the above method is characterized in that,

[0045] When the first condition is not met and the first information indicates that PUSCH should not be sent in the target air interface resource pool, the reception of PUSCH in the target air interface resource pool is abandoned.

[0046] According to one aspect of this application, the above method is characterized in that,

[0047] The first signaling is used to identify multiple air interface resource pools, the target air interface resource pool being one of the multiple air interface resource pools, and the first information is received in an air interface resource pool other than the target air interface resource pool among the multiple air interface resource pools.

[0048] According to one aspect of this application, the above method is characterized in that,

[0049] The first information includes a bitmap, in which any bit is used to indicate whether a PUSCH is sent in one of the plurality of air interface resource pools.

[0050] According to one aspect of this application, the above method is characterized in that,

[0051] The multiple air interface resource pools are multiple PUSCH opportunities. The multiple air interface resource pools are in the same CG cycle. The first information is received in the first PUSCH opportunity among the multiple PUSCH opportunities. The multiple air interface resource pools do not overlap with each other in the time domain.

[0052] According to one aspect of this application, the above method is characterized in that,

[0053] The target air interface resource pool is a PUSCH opportunity.

[0054] According to one aspect of this application, the above method is characterized in that,

[0055] The target air interface resource pool is a CG PUSCH opportunity.

[0056] This application discloses a first node used for wireless communication, characterized in that it comprises:

[0057] The first receiver receives the first signaling, which is used to determine the target air interface resource pool.

[0058] The first transmitter sends the first message;

[0059] Wherein, the first information is used to indicate whether to transmit PUSCH in the target air interface resource pool; whether the first transmitter transmits PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, the first transmitter transmits PUSCH in the target air interface resource pool, and the first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that PUSCH is transmitted in the target air interface resource pool.

[0060] This application discloses a second node used for wireless communication, characterized in that it comprises:

[0061] The second transmitter sends a first signaling message, which is used to determine the target air interface resource pool.

[0062] The second receiver receives the first information;

[0063] Wherein, the first information is used to indicate whether to transmit PUSCH in the target air interface resource pool; whether the second receiver receives PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, the second receiver receives PUSCH in the target air interface resource pool, and the first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that PUSCH is transmitted in the target air interface resource pool. Attached Figure Description

[0064] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0065] Figure 1 A flowchart illustrating the processing of a first node according to an embodiment of this application is shown;

[0066] Figure 2 A schematic diagram of a network architecture according to an embodiment of this application is shown;

[0067] Figure 3A schematic diagram of a wireless protocol architecture for the user plane and control plane according to an embodiment of this application is shown;

[0068] Figure 4 A schematic diagram of a first communication device and a second communication device according to an embodiment of this application is shown;

[0069] Figure 5 A signal transmission flowchart according to an embodiment of this application is shown;

[0070] Figure 6 A schematic diagram illustrating the relationship between a first set of conditions according to an embodiment of this application and whether a PUSCH is sent in a target air interface resource pool is shown.

[0071] Figure 7 A schematic diagram illustrating the relationship between a first signaling, multiple air interface resource pools, a target air interface resource pool, and first information according to an embodiment of this application is shown.

[0072] Figure 8 A schematic diagram illustrating first information according to an embodiment of this application is shown;

[0073] Figure 9 A schematic diagram illustrating the relationship between multiple air interface resource pools, multiple PUSCH opportunities, a target air interface resource pool, and first information according to an embodiment of this application is shown.

[0074] Figure 10 A schematic diagram illustrating the relationship between a first signaling according to an embodiment of this application, multiple air interface resource pools, multiple PUSCH opportunities, a target air interface resource pool, and the relationship between the first information is shown.

[0075] Figure 11 A structural block diagram of a processing apparatus in a first node device according to an embodiment of this application is shown;

[0076] Figure 12 A structural block diagram of a processing apparatus in a second node device according to an embodiment of this application is shown. Detailed Implementation

[0077] The technical solution of this application will be further described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.

[0078] Example 1

[0079] Example 1 illustrates a processing flowchart of the first node according to an embodiment of this application, as shown in the attached diagram. Figure 1 As shown.

[0080] In Embodiment 1, the first node in this application receives the first signaling in step 101 and sends the first information in step 102.

[0081] In Embodiment 1, the first signaling is used to determine a target air interface resource pool; the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether to send a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either a first condition or a second condition is met, a PUSCH is sent in the target air interface resource pool, and first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that a PUSCH is sent in the target air interface resource pool.

[0082] As one example, the first signaling includes the higher-level parameter configuredGrantConfig.

[0083] As an example, the first signaling is the higher-level parameter configuredGrantConfig.

[0084] As an example, the first signaling is DCI (Downlink control information).

[0085] As an example, the first signaling is a DCI that includes a UL grant.

[0086] As one embodiment, the first signaling includes RRC signaling.

[0087] As one embodiment, the first signaling includes a higher layer parameter.

[0088] As an example, the first signaling is used to configure the target air interface resource pool.

[0089] As an example, the first signaling is used to instruct the target air interface resource pool.

[0090] As an example, the first signaling explicitly indicates the target air interface resource pool.

[0091] As an example, the first signaling implicitly indicates the target air interface resource pool.

[0092] As an example, the first signaling is used to indicate the frequency domain resources occupied by the target air interface resource pool.

[0093] As an example, the first signaling is used to indicate the time-domain resources occupied by the target air interface resource pool.

[0094] As an example, the first signaling is used to indicate the slot in which the target air interface resource pool is located.

[0095] As an example, the first signaling is used to configure multiple air interface resource pools, and the target air interface resource pool is one of the multiple air interface resource pools.

[0096] As an example, at least one parameter value included in the first signaling is used to infer the target air interface resource pool.

[0097] As an example, the target air interface resource pool is a PUSCH occasion.

[0098] As an example, the target air interface resource pool is a CG PUSCH opportunity (CGPUSCHoccasion).

[0099] As an example, the target air interface resource pool is the air interface resources occupied by a PUSCH occasion.

[0100] As an example, the target air interface resource pool is the air interface resources occupied by a CGPUSCH occasion (PUSCH occasion).

[0101] As an example, the target air interface resource pool is an opportunity for PUSCH transmission.

[0102] As an example, the target air interface resource pool is an opportunity for CG PUSCH transmission.

[0103] As an example, the target air interface resource pool is reserved for PUSCH transmission.

[0104] As an example, the target air interface resource pool is reserved for the transmission of CG PUSCH.

[0105] As an example, from the perspective of frequency and time domains, the target air interface resource pool includes multiple REs (Resource elements).

[0106] As one embodiment, the first information includes physical layer signaling.

[0107] As one example, the first information includes RRC signaling.

[0108] As an example, the first information is UCI (Uplink control information).

[0109] As an example, the first information is a CG-UCI.

[0110] As an example, the first information is a bit or a field in a CG-UCI.

[0111] As an example, the first information is carried by at least one UCI bit multiplexed onto the PUSCH.

[0112] As an example, the first information is a UCI bit.

[0113] As an example, the first information is represented by one bit.

[0114] As an example, the first information is a bit, where a value of 0 indicates that PUSCH is sent in the target air interface resource pool, and a value of 1 indicates that PUSCH is not sent in the target air interface resource pool.

[0115] As an example, the first information is a bit, and "the first information indicates that PUSCH is sent in the target air interface resource pool" and "the first information is a bit, and the value of the bit is 0" are equivalent or interchangeable. Similarly, "the first information indicates that PUSCH is not sent in the target air interface resource pool" and "the first information is a bit, and the value of the bit is 1" are equivalent or interchangeable.

[0116] As an example, the first information is a bit, where a value of 1 indicates that PUSCH is sent in the target air interface resource pool, and a value of 0 indicates that PUSCH is not sent in the target air interface resource pool.

[0117] As an example, "the first information indicates that PUSCH is sent in the target air interface resource pool" and "the first information is a bit, and the value of the bit is 1" are equivalent or interchangeable. Similarly, "the first information indicates that PUSCH is not sent in the target air interface resource pool" and "the value of the bit is 0" are equivalent or interchangeable.

[0118] As one embodiment, the first information is a field, and the field includes multiple bits.

[0119] As an example, the first information is a field, the field comprising multiple bits, at least one value in the range of values ​​of the field indicating that PUSCH is sent in the target air interface resource pool, and at least another value in the range of values ​​of the field indicating that PUSCH is not sent in the target air interface resource pool.

[0120] As an example, the first information explicitly indicates whether a PUSCH is sent in the target air interface resource pool.

[0121] As an example, the first information implicitly indicates whether a PUSCH is sent in the target air interface resource pool.

[0122] As an example, sending PUSCH in the target air interface resource pool means that the target air interface resource pool is used to send PUSCH.

[0123] As an example, the first node sending a PUSCH in the target air interface resource pool has the following meaning: the first node sends at least one transport block in a PUSCH, and the target air interface resource pool includes the air interface resources occupied by this PUSCH.

[0124] As an example, the first node sending a PUSCH in the target air interface resource pool has the following meaning: the first node sends at least one bit in a PUSCH, and the target air interface resource pool includes the air interface resources occupied by this PUSCH.

[0125] As an example, the first node sending a PUSCH in the target air interface resource pool has the following meaning: the first node sends a radio signal in a PUSCH, and the target air interface resource pool includes the air interface resources occupied by this PUSCH.

[0126] As an example, the first node sending a PUSCH in the target air interface resource pool has the following meaning: the first node sends at least one bit through a PUSCH, and the target air interface resource pool includes the air interface resources occupied by this PUSCH.

[0127] As an example, the first node sending a PUSCH in the target air interface resource pool has the following meaning: the target air interface resource pool includes the air interface resources occupied by the signal sent through a PUSCH.

[0128] As an example, whether the first node sends PUSCH and the first information in the target air interface resource pool, and whether the target air interface resource pool overlaps with the feature resources, are both related.

[0129] As an example, the first node sends PUSCH and the first information in the target air interface resource pool, and the target air interface resource pool overlaps with the feature resource, which are at least the latter two.

[0130] As an example, whether the first node sends a PUSCH in the target air interface resource pool depends on at least one of the following: the first information and whether the target air interface resource pool overlaps with the feature resource.

[0131] As one embodiment, whether the first node sends a PUSCH in the target air interface resource pool depends on at least the latter of the first information and whether the target air interface resource pool overlaps with the feature resource.

[0132] As an example, whether the first node sends a PUSCH in the target air interface resource pool depends on the first information and whether the target air interface resource pool overlaps with the feature resources.

[0133] As an example, the PUSCH transmitted in the target air interface resource pool is a CG PUSCH (Physical uplink shared channel).

[0134] As an example, the statement "whether to send PUSCH in the target air interface resource pool" means whether to send CG PUSCH in the target air interface resource pool.

[0135] As an example, the statement "the first information is used to indicate whether PUSCH is sent in the target air interface resource pool" means that the first information is used to indicate whether CGPUSCH is sent in the target air interface resource pool.

[0136] As an example, the non-overlapping nature of the target air interface resource pool and the feature resources means that the target air interface resource pool and the feature resources do not overlap in the time domain.

[0137] As an example, the overlap between the target air interface resource pool and the feature resources means that the target air interface resource pool and the feature resources overlap in the time domain.

[0138] As an example, the target air interface resource pool is configured for uplink transmissions that are not dynamically granted.

[0139] As an example, the feature resource is a PUCCH resource.

[0140] As an example, a feature resource includes a PUCCH resource.

[0141] As an example, the statement "the feature resource is a resource for at least one UCI" means that the feature resource is a PUCCH resource.

[0142] As an example, the statement "the feature resource is a resource for at least one UCI" means that the feature resource is a PUCCH resource for at least HARQ-ACK.

[0143] As an example, the statement "the feature resource is a resource for at least one UCI" means that the feature resource is a PUCCH resource used for at least one of HARQ-ACK, SR, and CSI (Channel State Information) reporting.

[0144] As an example, the statement "the characteristic resource is a resource for at least one UCI" means that the characteristic resource is a PUCCH (Physical uplink control channel) resource used for at least HARQ-ACK (Hybrid automatic repeat request acknowledgment) and SR (Scheduling request).

[0145] As an example, the statement "the first condition includes the overlap between the target air interface resource pool and the feature resource" includes: the first condition includes: if the target air interface resource pool is used to send PUSCH, the UCI bits will be multiplexed into this PUSCH.

[0146] As an example, the statement "the first condition includes the overlap between the target air interface resource pool and the feature resource" includes: the first condition includes: if the target air interface resource pool is used to send PUSCH, at least the HARQ-ACK bits will be multiplexed into this PUSCH.

[0147] As an example, the first condition is that the target air interface resource pool overlaps with the feature resources.

[0148] As an example, the first condition is that the target air interface resource pool overlaps with a characteristic resource.

[0149] As an example, the first condition is that the target air interface resource pool overlaps with multiple feature resources.

[0150] As an example, the first condition is that the target air interface resource pool overlaps with at least one characteristic resource.

[0151] As an example, the first condition is that the target air interface resource pool overlaps with any characteristic resource.

[0152] As an example, the first condition only includes: the target air interface resource pool overlaps with the feature resources.

[0153] As an example, the first condition includes multiple sub-conditions, and the first condition being satisfied means that all the sub-conditions included in the first condition are satisfied; one of the multiple sub-conditions is that the target air interface resource pool overlaps with the feature resource.

[0154] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: if the target air interface resource pool is used to send PUSCH, then at least the HARQ-ACK bits will be multiplexed into this PUSCH.

[0155] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: if the target air interface resource pool is used to send PUSCH, then the UCI bits will be multiplexed into this PUSCH.

[0156] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: the timeline conditions for UCI multiplexing to PUSCH are met.

[0157] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: UCI will be reused in the target air interface resource pool.

[0158] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: at least HARQ-ACK information will be reused in the target air interface resource pool.

[0159] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: UCI will be multiplexed and transmitted in the target air interface resource pool.

[0160] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: at least HARQ-ACK information will be reused and sent in the target air interface resource pool.

[0161] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: the frequency domain resources occupied by the target air interface resource pool are in the active uplink (UL) BWP (Bandwidth part) on the primary cell (PCell).

[0162] As an example, the first condition being met means that the target air interface resource pool overlaps with the feature resources.

[0163] As an example, the first condition being met means that the timeline condition of the target air interface resource pool overlapping with the feature resources and UCI being multiplexed into PUSCH is met.

[0164] As an example, the statement "the target air interface resource pool overlaps with the feature resources" means that UCI will be reused in the target air interface resource pool.

[0165] As an example, the statement "the target air interface resource pool overlaps with the feature resources" means that at least HARQ-ACK information will be reused in the target air interface resource pool.

[0166] As an example, the statement "the target air interface resource pool overlaps with the feature resources" means that the UCI will be reused and transmitted in the target air interface resource pool.

[0167] As an example, the statement "the target air interface resource pool overlaps with the feature resources" means that at least HARQ-ACK information will be reused and sent in the target air interface resource pool.

[0168] As an example, the second condition is: the first information indicates that PUSCH is sent in the target air interface resource pool.

[0169] As one embodiment, the second condition only includes: the first information indicates that PUSCH is sent in the target air interface resource pool.

[0170] As an example, the second condition includes multiple sub-conditions, and the second condition being satisfied means that all the sub-conditions included in the second condition are satisfied; one of the multiple sub-conditions is that the first information indicates that PUSCH is sent in the target air interface resource pool.

[0171] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: there are no other PUSCHs that overlap with the target air interface resource pool in the time domain.

[0172] As a sub-implementation of the above embodiment, another sub-condition among the plurality of sub-conditions is: the target air interface resource pool does not overlap with the downlink (DL) symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or the symbols of SS / PBCH blocks with the index provided by ssb-PositionsInBurst.

[0173] As an example, the second condition being met means that the first information indicates that a PUSCH is sent in the target air interface resource pool.

[0174] As an example, the first information depends at least on whether the target air interface resource pool overlaps with the feature resources.

[0175] As an example, if the target air interface resource pool overlaps with the feature resource, the first information indicates that a PUSCH should be sent in the first air interface resource pool group.

[0176] As an example, if the target air interface resource pool overlaps with the feature resource, the first information is set to indicate that PUSCH is sent in the first air interface resource pool group.

[0177] As an example, if the target air interface resource pool overlaps with the feature resource, the first information is expected to instruct the PUSCH to be sent in the first air interface resource pool group.

[0178] As an example, if the first condition is met, the first information indicates that a PUSCH is sent in the first air interface resource pool group.

[0179] As an example, if the first condition is met, the first information is set to indicate that a PUSCH is sent in the first air interface resource pool group.

[0180] As an example, if the first condition is met, the first information is expected to instruct the transmission of PUSCH in the first air interface resource pool group.

[0181] As an example, when the first condition is met and the first information indicates that no PUSCH is sent in the target air interface resource pool, the first node sends PUSCH in the target air interface resource pool.

[0182] As an example, when the first condition is not met and the first information indicates that PUSCH is not to be sent in the target air interface resource pool, the first node abandons sending PUSCH in the target air interface resource pool.

[0183] As an example, when the second condition is met, the first condition may or may not be met.

[0184] As an example, when the second condition is not met, the first condition may or may not be met.

[0185] As an example, if the first condition is met, then the second condition is also met.

[0186] As an example, if the second condition is not met, then the first condition is also not met.

[0187] As an example, when the first condition is met, the second condition may or may not be met.

[0188] As an example, when the first condition is not met, the second condition may or may not be met.

[0189] As an example, the statement "the first information is used to indicate whether to send PUSCH in the target air interface resource pool" means that the first information is at least used to indicate whether to send PUSCH in the target air interface resource pool.

[0190] As an example, when the first condition is met and the first information indicates that PUSCH is not sent in the target air interface resource pool, the first node sends PUSCH in the target air interface resource pool; when the first condition is not met and the first information indicates that PUSCH is not sent in the target air interface resource pool, the first node abandons sending PUSCH in the target air interface resource pool.

[0191] As an example, the first MCS information is a parameter indicating the MCS (modulation and coding scheme) table used for PUSCH.

[0192] As an example, the first MCS information is the MCS used by the PUSCH that is sent in the target air interface resource pool.

[0193] As an example, the first MCS information is used to determine the modulation order and target code rate of the PUSCH to be transmitted in the target air interface resource pool.

[0194] As a sub-example of the above embodiments, the modulation order and the target code rate are determined based on a lookup table method.

[0195] As a sub-example of the above embodiments, the modulation order and the target code rate are determined based on a predefined mapping relationship.

[0196] As an example, the statement "the first MCS information is used for the transmission of the PUSCH" means that the PUSCH transmitted in the target air interface resource pool adopts the modulation order and target code rate corresponding to the first MCS information.

[0197] As an example, the first MCS information is configured by RRC signaling.

[0198] As an example, the first MCS information is configured by the first signaling.

[0199] As an example, the first MCS information is configured in ConfiguredGrantConfig.

[0200] As an example, the first MCS information is configured in PUSCH-Config.

[0201] As an example, the statement "the first MCS information is configurable" means that the first information includes the first MCS information.

[0202] As an example, the first MCS information is an MCS index.

[0203] As an example, based on the configuration of higher-layer parameters, transform precoding is disabled for the PUSCH transmitted in the target air interface resource pool.

[0204] Example 2

[0205] Example 2 illustrates a schematic diagram of a network architecture according to this application, as shown in the attached diagram. Figure 2 As shown.

[0206] Appendix Figure 2A diagram illustrating the network architecture 200 of 5G NR, LTE (Long-Term Evolution), and LTE-A (Long-Term Evolution Advanced) systems is provided. The 5G NR or LTE network architecture 200 may be referred to as EPS (Evolved Packet System) 200 or some other suitable term. EPS 200 may include one or more UE (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, EPC (Evolved Packet Core) / 5G-CN (5G-Core Network) 210, HSS (Home Subscriber Server) 220, and Internet service 230. EPS may interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown in the diagram, EPS provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol termination to UE 201. gNB 203 can connect to other gNBs 204 via the Xn interface (e.g., backhaul). gNB 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 suitable term. gNB 203 provides UE 201 with access to EPC / 5G-CN 210. Examples of UE201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband IoT devices, machine-type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE201 as a mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term. gNB203 connects to EPC / 5G-CN 210 via the S1 / NG interface.The EPC / 5G-CN 210 includes the MME (Mobility Management Entity), AMF (Authentication Management Field), and UPF (User Plane Function) 211, other MMEs, AMFs, and UPFs 214, the S-GW (Service Gateway) 212, and the P-GW (Packet Data Network Gateway) 213. The MME / AMF / UPF 211 is the control node that handles signaling between the UE 201 and the EPC / 5G-CN 210. Generally, the MME / AMF / UPF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through the S-GW 212, which is itself connected to the P-GW 213. The P-GW 213 provides UE IP address allocation and other functions. The P-GW 213 is connected to the Internet service 230. Internet services 230 include operator-compliant Internet protocol services, which may specifically include the Internet, intranets, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0207] As an example, the UE201 corresponds to the first node in this application.

[0208] As an example, the UE201 corresponds to the second node in this application.

[0209] As an example, the UE201 is a UE.

[0210] As an example, the UE201 is a UE that supports multicast transmission.

[0211] As an example, the UE201 is a conventional UE.

[0212] As an example, gNB203 corresponds to the first node in this application.

[0213] As an example, gNB203 corresponds to the second node in this application.

[0214] As an example, UE201 corresponds to the first node in this application, and gNB203 corresponds to the second node in this application.

[0215] As an example, the gNB203 is a macrocell base station.

[0216] As an example, the gNB203 is a microcell base station.

[0217] As an example, the gNB203 is a PicoCell base station.

[0218] As an example, the gNB203 is a femtocell.

[0219] As an example, the gNB203 is a base station device that supports large latency differences.

[0220] As one example, the gNB203 is a flight platform device.

[0221] As an example, the gNB203 is a satellite device.

[0222] As an example, the gNB203 is a base station that enables network power saving enhancement.

[0223] As an example, the first node and the second node in this application both correspond to the UE201, for example, V2X communication is performed between the first node and the second node.

[0224] Example 3

[0225] Example 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for a user plane and a control plane according to this application, as shown in the attached diagram. Figure 3 As shown. Figure 3 This is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300. Figure 3The radio protocol architecture for the control plane 300 between the first communication node device (UE, gNB, or RSU in V2X) and the second communication node device (gNB, UE, or RSU in V2X), or between two UEs, is illustrated 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. L1 layer will be referred to herein as PHY301. Layer 2 (L2 layer) 305 sits above PHY301 and is responsible for the link between the first and second communication node devices and between the two UEs via PHY301. L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second communication node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. PDCP sublayer 304 also provides security through encrypted data packets and supports cross-cell mobility between second communication node devices and the first communication node device. RLC sublayer 303 provides upper layer data packet segmentation and reassembly, retransmission of lost data packets, and data packet reordering to compensate for out-of-order reception due to HARQ. MAC sublayer 302 provides multiplexing between the logical and transport channels. MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell between the first communication node devices. 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 acquiring radio resources (i.e., radio bearers) and configuring the lower layer using RRC signaling between the second and first communication node devices. The radio protocol architecture of user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The radio protocol architecture for the first and second communication node devices in user plane 350 is largely the same as the corresponding layers and sublayers in control plane 300 for physical layer 351, PDCP sublayer 354 in L2 layer 355, RLC sublayer 353 in L2 layer 355 and MAC sublayer 352 in L2 layer 355. However, PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS streams and data radio bearers (DRBs) to support service diversity. Although not illustrated, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., IP layer) terminating at the P-GW on the network side and an application layer terminating at the other end of the connection (e.g., a remote UE, server, etc.).

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

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

[0228] As an example, the first signaling in this application is generated in the RRC sublayer 306.

[0229] As an example, the first signaling in this application is generated in the MAC sublayer 302.

[0230] As an example, the first signaling in this application is generated in the PHY301.

[0231] As an example, the first information in this application is generated in the RRC sublayer 306.

[0232] As an example, the first information in this application is generated in the MAC sublayer 302.

[0233] As an example, the first information in this application is generated in the PHY301.

[0234] As an example, a PUSCH in this application is generated in the PHY301.

[0235] Example 4

[0236] Example 4 shows schematic diagrams of a first communication device and a second communication device according to this application, as shown in the appendix. Figure 4 As shown. Figure 4 This is a block diagram of a first communication device 410 and a second communication device 450 communicating with each other in an access network.

[0237] The first communication device 410 includes a controller / processor 475, a memory 476, a receiver processor 470, a transmitter processor 416, a multi-antenna receiver processor 472, a multi-antenna transmitter processor 471, a transmitter / receiver 418, and an antenna 420.

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

[0239] In the transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper-layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 layer functionality. In the transmission from the first communication device 410 to the second 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 second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmitting lost packets and signaling to the second 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). Transmit processor 416 performs encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, and mapping of signal clusters based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-Phase Shift Keying (M-PSK), M-QAM). Multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. 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 multicarrier symbol stream provided by the multi-antenna transmitter processor 471 into an radio frequency stream, which is then provided to different antennas 420.

[0240] In the transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 456. The receiver processor 456 and the multi-antenna receiver processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 454. The receiver processor 456 uses a Fast Fourier Transform (FFT) to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiver processor 456, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 458 after multi-antenna detection to recover any spatial stream destined for the second communication device 450. Symbols on each spatial stream are demodulated and recovered in the receive processor 456, generating soft decisions. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper-layer data and control signals transmitted by the first communication device 410 over 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 Layer 2. The controller / processor 459 may be associated with a memory 460 storing program code and data. The memory 460 may be referred to as computer-readable media. In the transmission from the first communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover upper-layer data packets from the core network. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 for Layer 3 processing.

[0241] In the transmission from the second communication device 450 to the first communication device 410, at the second communication device 450, a data source 467 is used 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 functions at the first communication device 410 described in the transmission from the first communication device 410 to the second 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 retransmitting lost packets and signaling to the first communication device 410. Transmit processor 468 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 457, the stream is provided to different antennas 452 via transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by multi-antenna transmit processor 457 into a radio frequency symbol stream before providing it to antenna 452.

[0242] In the transmission from the second communication device 450 to the first communication device 410, the function at the first communication device 410 is similar to the receiving function at the second communication device 450 described in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 472 and the receiving processor 470. The receiving processor 470 and the multi-antenna receiving processor 472 jointly implement the L1 layer functions. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as computer-readable media. In the transmission from the second communication device 450 to the first communication device 410, the controller / processor 475 provides multiplexing between the transmission 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 the controller / processor 475 can be provided to the core network.

[0243] As an example, the first node in this application includes the second communication device 450, and the second node in this application includes the first communication device 410.

[0244] As a sub-implementation of the above embodiments, the first node is a user equipment, and the second node is a user equipment.

[0245] As a sub-implementation of the above embodiments, the first node is a user equipment and the second node is a relay node.

[0246] As a sub-implementation of the above embodiments, the first node is a relay node and the second node is a user equipment.

[0247] As a sub-implementation of the above embodiments, the first node is a user equipment and the second node is a base station equipment.

[0248] As a sub-implementation of the above embodiments, the first node is a relay node and the second node is a base station device.

[0249] As a sub-implementation of the above embodiments, the second node is a user equipment and the first node is a base station equipment.

[0250] As a sub-implementation of the above embodiments, the second node is a relay node, and the first node is a base station device.

[0251] As a sub-implementation of the above embodiments, the second communication device 450 includes: at least one controller / processor; the at least one controller / processor is responsible for HARQ operation.

[0252] As a sub-implementation of the above embodiments, the first communication device 410 includes: at least one controller / processor; the at least one controller / processor is responsible for HARQ operation.

[0253] As a sub-implementation of the above embodiments, the first communication device 410 includes: at least one controller / processor; the at least one controller / processor is responsible for error detection using positive acknowledgment (ACK) and / or negative acknowledgment (NACK) protocols to support HARQ operation.

[0254] As one embodiment, the second 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 with the at least one processor. The second communication device 450 means at least: receiving first signaling, the first signaling being used to determine a target air interface resource pool; transmitting first information; wherein the first information is used to indicate whether to transmit a PUSCH in the target air interface resource pool; whether to transmit a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a characteristic resource, the characteristic resource being a resource for at least one UCI; transmitting a PUSCH in the target air interface resource pool when either a first condition or a second condition is met, the first MCS information being used for the transmission of the PUSCH, the first MCS information being configurable; the first condition including the target air interface resource pool overlapping with a characteristic resource, and the second condition including the first information indicating that a PUSCH is transmitted in the target air interface resource pool.

[0255] As a sub-implementation of the above embodiments, the second communication device 450 corresponds to the first node in this application.

[0256] As one embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program that, when executed by at least one processor, produces actions including: receiving first signaling used to determine a target air interface resource pool; sending first information; wherein the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether to send a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, the feature resource being a resource for at least one UCI; sending a PUSCH in the target air interface resource pool when either a first condition or a second condition is met, the first MCS information being used for the transmission of the PUSCH, the first MCS information being configurable; the first condition including the target air interface resource pool overlapping with a feature resource, and the second condition including the first information indicating that a PUSCH should be sent in the target air interface resource pool.

[0257] As a sub-implementation of the above embodiments, the second communication device 450 corresponds to the first node in this application.

[0258] As one embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The first communication device 410 includes at least: transmitting first signaling, the first signaling being used to determine a target air interface resource pool; receiving first information; wherein the first information is used to indicate whether to transmit a PUSCH in the target air interface resource pool; whether to receive a PUSCH in the target air interface resource pool is related to at least one of the following: the first information, and whether the target air interface resource pool overlaps with a characteristic resource, the characteristic resource being a resource for at least one UCI; receiving a PUSCH in the target air interface resource pool when either a first condition or a second condition is met, the first MCS information being used for the transmission of the PUSCH, the first MCS information being configurable; the first condition including the target air interface resource pool overlapping with a characteristic resource, and the second condition including the first information indicating that a PUSCH is transmitted in the target air interface resource pool.

[0259] As a sub-implementation of the above embodiments, the first communication device 410 corresponds to the second node in this application.

[0260] As one embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program that, when executed by at least one processor, produces actions including: sending first signaling used to determine a target air interface resource pool; receiving first information; wherein the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether to receive a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, the feature resource being a resource for at least one UCI; receiving a PUSCH in the target air interface resource pool when either a first condition or a second condition is met, the first MCS information being used for the transmission of the PUSCH, the first MCS information being configurable; the first condition including the target air interface resource pool overlapping with a feature resource, and the second condition including the first information indicating that a PUSCH is sent in the target air interface resource pool.

[0261] As a sub-implementation of the above embodiments, the first communication device 410 corresponds to the second node in this application.

[0262] As an example, at least one of {the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467} is used to receive the first signaling in this application.

[0263] As an example, at least one of {the antenna 420, the transmitter 418, the multi-antenna transmitter processor 471, the transmitter processor 416, the controller / processor 475, and the memory 476} is used to transmit the first signaling in this application.

[0264] As an example, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmitter processor 458, the transmitter processor 468, the controller / processor 459, the memory 460, and the data source 467} is used to transmit the first information in this application.

[0265] As an example, at least one of {the antenna 420, the receiver 418, the multi-antenna receiving processor 472, the receiving processor 470, the controller / processor 475, and the memory 476} is used to receive the first information in this application.

[0266] As an example, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmitter processor 458, the transmitter processor 468, the controller / processor 459, the memory 460, and the data source 467} is used to transmit a PUSCH in this application.

[0267] As an example, at least one of {the antenna 420, the receiver 418, the multi-antenna receiver processor 472, the receiver processor 470, the controller / processor 475, and the memory 476} is used to receive a PUSCH in this application.

[0268] Example 5

[0269] Example 5 illustrates a signal transmission flowchart according to an embodiment of this application, as shown in the attached diagram. Figure 5 As shown. In the appendix Figure 5 In this system, the first node U1 and the second node U2 communicate via an air interface. Specifically, in the attached... Figure 5 In the dashed box F1, the steps are optional.

[0270] The first node U1 receives the first signaling in step S511; sends the first information in step S512; and sends PUSCH in the target air interface resource pool in step S513.

[0271] The second node U2 sends the first signaling in step S521; receives the first information in step S522; and receives PUSCH in the target air interface resource pool in step S523.

[0272] In Embodiment 5, the first signaling is used to determine the target air interface resource pool; the first information is used to indicate whether to send PUSCH in the target air interface resource pool; whether the first node U1 sends PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, the first node U1 sends PUSCH in the target air interface resource pool, and the second node U2 receives PUSCH in the target air interface resource pool; when the first condition is not met and the first information indicates that PUSCH is not sent in the target air interface resource pool, the first node U1 abandons sending PUSCH in the target air interface resource pool, and the first MCS information is used for the sending of PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that PUSCH is sent in the target air interface resource pool.

[0273] As a sub-implementation of Embodiment 5, the first signaling is used to determine multiple air interface resource pools, the target air interface resource pool is one of the multiple air interface resource pools, and an air interface resource pool other than the target air interface resource pool is used to send the first information; the multiple air interface resource pools are multiple PUSCH opportunities, and the multiple air interface resource pools are in the same CG cycle.

[0274] As an example, the first node U1 is the first node in this application.

[0275] As an example, the second node U2 is the second node in this application.

[0276] As an example, the first node U1 is a UE.

[0277] As an example, the first node U1 is a base station.

[0278] As one example, the second node U2 is a base station.

[0279] As an example, the second node U2 is a UE.

[0280] As one embodiment, the air interface between the second node U2 and the first node U1 is the Uu interface.

[0281] As one embodiment, the air interface between the second node U2 and the first node U1 includes a cellular link.

[0282] As an example, the air interface between the second node U2 and the first node U1 is a PC5 interface.

[0283] As one embodiment, the air interface between the second node U2 and the first node U1 includes a side link.

[0284] As one embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between the base station equipment and the user equipment.

[0285] As one embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between satellite equipment and user equipment.

[0286] As one embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between user equipment and user equipment.

[0287] As an example, the problem this application aims to solve includes: how to determine whether to send a PUSCH in the target air interface resource pool.

[0288] As an example, the problem this application aims to solve includes: how to avoid inconsistencies in the understanding between the two communicating parties regarding whether or not a PUSCH has been sent.

[0289] As an example, the problem to be solved by this application includes: the base station cannot know whether the UCI is multiplexed on the CG PUSCH because the first information is not decoded correctly.

[0290] As an example, the problem this application aims to solve includes: how to improve the performance of UCI feedback.

[0291] As an example, the problem this application aims to solve includes: how to handle the overlap between PUSCH opportunities and PUCCH resources.

[0292] As an example, the problem this application aims to solve includes: how to reduce the detection complexity on the base station side.

[0293] As an example, the problem this application aims to solve includes: how to make the uplink transmission of enhanced CG compatible with UCI multiplexing.

[0294] As an example, the steps in the dashed box F1 are present.

[0295] As an example, the step in the dashed box F1 does not exist.

[0296] As an example, the step in dashed box F1 exists when either the first condition or the second condition is met.

[0297] As an example, the step in dashed box F1 exists when the first condition is met and the first information indicates that no PUSCH is sent in the target air interface resource pool.

[0298] As an example, the step in dashed box F1 is not present when the first condition is not met and the first information indicates that no PUSCH is sent in the target air interface resource pool.

[0299] As an example, the first set of conditions includes at least the first condition and the second condition; when any condition in the first set of conditions is satisfied, the step in the dashed box F1 exists; when none of the conditions in the first set of conditions are satisfied, the step in the dashed box F1 does not exist.

[0300] Example 6

[0301] Example 6 illustrates a schematic diagram of the relationship between a first set of conditions according to an embodiment of this application and whether a PUSCH is sent in the target air interface resource pool, as shown in the attached diagram. Figure 6 As shown.

[0302] In Embodiment 6, when any condition in the first condition set is met, the first node sends a PUSCH in the target air interface resource pool; when none of the conditions in the first condition set are met, the first node abandons sending a PUSCH in the target air interface resource pool; the first condition set includes at least the first condition and the second condition.

[0303] As an example, the first set of conditions includes only the first condition and the second condition.

[0304] As an example, the first set of conditions also includes at least one condition in addition to the first condition and the second condition.

[0305] As an example, the first set of conditions also includes conditions that are unrelated to both the first information and whether the target air interface resource pool overlaps with the feature resources.

[0306] As an example, the first set of conditions further includes a third condition, which includes that the target air interface resource pool is the first PUSCH opportunity in the CG cycle.

[0307] As an example, sending PUSCH in the target air interface resource pool means that the target air interface resource pool is used to send PUSCH.

[0308] As an example, sending PUSCH in the target air interface resource pool means that the target air interface resource pool is used to send CG PUSCH.

[0309] As an example, sending PUSCH in the target air interface resource pool means sending CG PUSCH in the target air interface resource pool.

[0310] As an example, abandoning the transmission of PUSCH in the target air interface resource pool means that the target air interface resource pool is not used for transmitting PUSCH.

[0311] As an example, abandoning the transmission of PUSCH in the target air interface resource pool means that the target air interface resource pool is not used to transmit CG PUSCH.

[0312] As an example, abandoning the transmission of PUSCH in the target air interface resource pool means that PUSCH is not transmitted in the target air interface resource pool.

[0313] As an example, abandoning the transmission of PUSCH in the target air interface resource pool means: not transmitting CG PUSCH in the target air interface resource pool.

[0314] Example 7

[0315] Example 7 illustrates a schematic diagram of the relationship between first signaling, multiple air interface resource pools, a target air interface resource pool, and first information according to an embodiment of this application, as shown in the attached diagram. Figure 7 As shown.

[0316] In Embodiment 7, the first signaling is used to determine multiple air interface resource pools, the target air interface resource pool is one of the multiple air interface resource pools, and an air interface resource pool other than the target air interface resource pool is used to send the first information.

[0317] As an example, the first signaling is used to instruct the plurality of air interface resource pools.

[0318] As an example, the first signaling explicitly indicates the plurality of air interface resource pools.

[0319] As an example, the first signaling implicitly indicates the plurality of air interface resource pools.

[0320] As an example, the first signaling is used to indicate the frequency domain resources occupied by each of the plurality of air interface resource pools.

[0321] As an example, the first signaling is used to indicate the time-domain resources occupied by each of the plurality of air interface resource pools.

[0322] As an example, the first signaling is used to indicate the slot in which each of the plurality of air interface resource pools is located.

[0323] As an example, the first signaling is used to configure the plurality of air interface resource pools.

[0324] As an example, at least one parameter value included in the first signaling is used to infer the plurality of air interface resource pools.

[0325] As an example, the first information is used to indicate whether PUSCH is sent in each of at least one of the plurality of air interface resource pools.

[0326] As one embodiment, the first air interface resource pool among the plurality of air interface resource pools is used to send the first information.

[0327] As an example, the first information is sent in an air interface resource pool other than the target air interface resource pool among the plurality of air interface resource pools.

[0328] As an example, the first air interface resource pool among the plurality of air interface resource pools is used to send a PUSCH, and the first information is multiplexed onto this PUSCH.

[0329] As an example, the first air interface resource pool among the plurality of air interface resource pools is used to send a PUSCH, which carries the first information.

[0330] As an example, one of the multiple air interface resource pools preceding the target air interface resource pool is used to send the first information.

[0331] As an example, the statement "an air interface resource pool other than the target air interface resource pool among the plurality of air interface resource pools is used to send the first information" includes: an air interface resource pool preceding the target air interface resource pool among the plurality of air interface resource pools is used to send a PUSCH, and the first information is multiplexed onto this PUSCH.

[0332] As an example, the target air interface resource pool is the last air interface resource pool among the plurality of air interface resource pools.

[0333] As an example, the target air interface resource pool is an air interface resource pool other than the first air interface resource pool among the plurality of air interface resource pools.

[0334] As an example, the target air interface resource pool is the first air interface resource pool among the plurality of air interface resource pools.

[0335] As an example, from a time domain perspective, the first air interface resource pool among the plurality of air interface resource pools is the earliest air interface resource pool among the plurality of air interface resource pools.

[0336] As an example, from a time domain perspective, the last air interface resource pool among the plurality of air interface resource pools is the latest air interface resource pool among the plurality of air interface resource pools.

[0337] As an example, each of the plurality of air interface resource pools is a PUSCH occasion.

[0338] As an example, each of the plurality of air interface resource pools is an opportunity for PUSCH.

[0339] As an example, each of the plurality of air interface resource pools is an opportunity for CG PUSCH.

[0340] As an example, each of the plurality of air interface resource pools is reserved for the transmission of PUSCH.

[0341] As an example, each of the plurality of air interface resource pools is reserved for the transmission of CG PUSCH.

[0342] As an example, from the perspective of frequency and time domains, each of the multiple air interface resource pools includes multiple REs.

[0343] As an example, one of the multiple air interface resource pools is a PUSCH occasion.

[0344] As an example, one of the multiple air interface resource pools is an opportunity for PUSCH.

[0345] As an example, one of the multiple air interface resource pools is an opportunity for CG PUSCH.

[0346] As an example, one of the multiple air interface resource pools is reserved for PUSCH transmission.

[0347] As an example, one of the multiple air interface resource pools is reserved for the transmission of CG PUSCH.

[0348] As an example, from the perspective of frequency and time domains, one of the multiple air interface resource pools includes multiple REs.

[0349] As an example, the multiple air interface resource pools are in the same CG cycle.

[0350] As an example, the CG cycle is a cycle configured for uplink transmission without dynamic grant.

[0351] As an example, a CG cycle is a CG (configured grant) cycle.

[0352] As an example, the CG cycle is configurable.

[0353] As an example, a CG cycle includes multiple symbols.

[0354] As an example, a CG cycle includes multiple time slots.

[0355] Example 8

[0356] Example 8 illustrates a schematic diagram of first information according to an embodiment of this application, as shown in the attached diagram. Figure 8 As shown.

[0357] In embodiment 8, the first information includes a bitmap, in which any bit is used to indicate whether a PUSCH is sent in one of the plurality of air interface resource pools.

[0358] As one embodiment, the first information includes multiple bits, which together indicate whether a PUSCH is sent in each of the multiple air interface resource pools.

[0359] Example 9

[0360] Example 9 illustrates a schematic diagram illustrating the relationship between multiple air interface resource pools, multiple PUSCH opportunities, a target air interface resource pool, and first information according to an embodiment of this application, as shown in the attached diagram. Figure 9 As shown.

[0361] In Example 9, the multiple air interface resource pools are multiple PUSCH opportunities, and the target air interface resource pool is a PUSCH opportunity other than the first PUSCH opportunity among the multiple PUSCH opportunities; the multiple air interface resource pools are in the same CG cycle, and the first information is sent in the first PUSCH opportunity among the multiple PUSCH opportunities.

[0362] As an example, the multiple air interface resource pools do not overlap with each other in the time domain.

[0363] As one example, the plurality of air interface resource pools are arranged sequentially in the time domain.

[0364] As an example, from a time domain perspective, the first PUSCH opportunity among the plurality of PUSCH opportunities is the earliest PUSCH opportunity among the plurality of PUSCH opportunities.

[0365] As an example, from a time domain perspective, the last PUSCH opportunity among the plurality of PUSCH opportunities is the latest PUSCH opportunity among the plurality of PUSCH opportunities.

[0366] As an example, the first information is multiplexed onto the PUSCH and then sent.

[0367] As one example, the multiple air interface resource pools are located in multiple different time slots.

[0368] As one example, the multiple air interface resource pools each occupy different time domain resources.

[0369] As one embodiment, the plurality of air interface resource pools are each a plurality of PUSCH opportunities. In the same CG cycle, the first information is sent in the first PUSCH opportunity among the plurality of PUSCH opportunities.

[0370] As an example, each of the plurality of PUSCH opportunities is a CG PUSCH opportunity.

[0371] As an example, each of the plurality of PUSCH opportunities is an opportunity for PUSCH transmission.

[0372] As an example, each of the plurality of PUSCH opportunities is an opportunity for CG PUSCH transmission.

[0373] As an example, each of the plurality of PUSCH opportunities is an opportunity reserved for PUSCH transmission.

[0374] As an example, each of the plurality of PUSCH opportunities is a reserved opportunity for CG PUSCH transmission.

[0375] As an example, the multiple air interface resource pools are in the same CG cycle.

[0376] Example 10

[0377] Example 10 illustrates a schematic diagram of the relationships between first signaling, multiple air interface resource pools, multiple PUSCH opportunities, a target air interface resource pool, and first information according to an embodiment of this application, as shown in the attached diagram. Figure 10 As shown.

[0378] In Embodiment 10, the first signaling is used to determine multiple air interface resource pools, the target air interface resource pool being one of the multiple air interface resource pools, the multiple air interface resource pools being multiple PUSCH opportunities, the multiple air interface resource pools being in the same CG cycle, and the first information being sent before the multiple PUSCH opportunities.

[0379] As an example, the multiple air interface resource pools do not overlap with each other in the time domain.

[0380] As an example, the meaning of the first information being sent before the plurality of PUSCH opportunities includes: the first information being sent after being multiplexed onto a PUSCH, which, from a time domain perspective, is before the plurality of PUSCH opportunities.

[0381] As an example, the meaning of the first information being sent before the plurality of PUSCH opportunities includes: the first information being sent after being multiplexed onto a PUSCH, and from a time domain perspective, the end of this PUSCH before the earliest symbol occupied by any of the plurality of PUSCH opportunities.

[0382] As an example, the meaning of the first information being sent before the plurality of PUSCH opportunities includes: the first information being sent after being multiplexed onto a PUSCH, and from a time domain perspective, the time slot of this PUSCH is located before the time slot of any of the plurality of PUSCH opportunities.

[0383] As an example, the first information is multiplexed onto a PUSCH and then sent, and this PUSCH and the plurality of PUSCHs may be in the same CG cycle.

[0384] Example 11

[0385] Example 11 illustrates a structural block diagram of a processing device in a first node device, as shown in the attached diagram. Figure 11 As shown. In the appendix Figure 11 In the first node device processing unit 1100, there are a first receiver 1101 and a first transmitter 1102.

[0386] As an example, the first node device 1100 is a base station.

[0387] As an example, the first node device 1100 is a user equipment.

[0388] As an example, the first node device 1100 is a relay node.

[0389] As an example, the first node device 1100 is a vehicle-mounted communication device.

[0390] As an example, the first node device 1100 is a user equipment that supports V2X communication.

[0391] As an example, the first node device 1100 is a relay node that supports V2X communication.

[0392] As an example, the first node device 1100 is a user equipment that supports operation on the high-frequency spectrum.

[0393] As an example, the first node device 1100 is a user equipment that supports operation on a shared spectrum.

[0394] As an example, the first node device 1100 is a user device that supports XR services.

[0395] As an example, the first node device 1100 is a user equipment that supports multicast transmission.

[0396] As one embodiment, the first receiver 1101 includes the appendix to this application. Figure 4The antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, and data source 467 are at least one of them.

[0397] As one embodiment, the first receiver 1101 includes the appendix to this application. Figure 4 The antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, and data source 467 are at least the first five of the following:

[0398] As one embodiment, the first receiver 1101 includes the appendix to this application. Figure 4 At least four of the following: antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, and data source 467.

[0399] As one embodiment, the first receiver 1101 includes the appendix to this application. Figure 4 At least three of the following: antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, and data source 467.

[0400] As one embodiment, the first receiver 1101 includes the appendix to this application. Figure 4 At least two of the following: antenna 452, receiver 454, multi-antenna receiver processor 458, receiver processor 456, controller / processor 459, memory 460, and data source 467.

[0401] As one embodiment, the first transmitter 1102 includes the appendix to this application. Figure 4 The antenna 452, transmitter 454, multi-antenna transmitter processor 457, transmitter processor 468, controller / processor 459, memory 460 and data source 467 are at least one of them.

[0402] As one embodiment, the first transmitter 1102 includes the appendix to this application. Figure 4 The antenna 452, transmitter 454, multi-antenna transmitter processor 457, transmitter processor 468, controller / processor 459, memory 460, and data source 467 are at least the first five of the following:

[0403] As one embodiment, the first transmitter 1102 includes the appendix to this application. Figure 4 At least four of the following: antenna 452, transmitter 454, multi-antenna transmitter processor 457, transmitter processor 468, controller / processor 459, memory 460, and data source 467.

[0404] As one embodiment, the first transmitter 1102 includes the appendix to this application. Figure 4 At least three of the following: antenna 452, transmitter 454, multi-antenna transmitter processor 457, transmitter processor 468, controller / processor 459, memory 460, and data source 467.

[0405] As one embodiment, the first transmitter 1102 includes the appendix to this application. Figure 4 At least two of the following: antenna 452, transmitter 454, multi-antenna transmitter processor 457, transmitter processor 468, controller / processor 459, memory 460, and data source 467.

[0406] As one embodiment, the first receiver 1101 receives a first signaling, which is used to determine a target air interface resource pool; the first transmitter 1102 sends first information; wherein, the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether the first transmitter 1102 sends a PUSCH in the target air interface resource pool is related to at least one of the following: the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either a first condition or a second condition is met, the first transmitter 1102 sends a PUSCH in the target air interface resource pool, and first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that a PUSCH is sent in the target air interface resource pool.

[0407] As an example, the first set of conditions includes at least the first condition and the second condition; when any condition in the first set of conditions is met, the first transmitter 1102 transmits PUSCH in the target air interface resource pool; when none of the conditions in the first set of conditions are met, the first transmitter 1102 abandons transmitting PUSCH in the target air interface resource pool.

[0408] As an example, when the first condition is met and the first information indicates that no PUSCH is transmitted in the target air interface resource pool, the first transmitter 1102 transmits PUSCH in the target air interface resource pool.

[0409] As an example, when the first condition is not met and the first information indicates that PUSCH is not to be transmitted in the target air interface resource pool, the first transmitter 1102 abandons the transmission of PUSCH in the target air interface resource pool.

[0410] As an example, the first signaling is used to determine multiple air interface resource pools, the target air interface resource pool being one of the multiple air interface resource pools, and an air interface resource pool other than the target air interface resource pool being used to send the first information.

[0411] As an example, the first information includes a bitmap, in which any bit is used to indicate whether a PUSCH is sent in one of the plurality of air interface resource pools.

[0412] As an example, the multiple air interface resource pools are multiple PUSCH opportunities. In the same CG cycle, the first information is sent in the first PUSCH opportunity among the multiple PUSCH opportunities, and the multiple air interface resource pools do not overlap with each other in the time domain.

[0413] As an example, the target air interface resource pool is a PUSCH opportunity.

[0414] As an example, the target air interface resource pool is a CG PUSCH opportunity.

[0415] As one embodiment, the first receiver 1101 receives a first signaling, which is used to determine a target air interface resource pool; the first transmitter 1102 sends first information; wherein, the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether the first transmitter 1102 sends a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when the target air interface resource pool overlaps with a feature resource, the first transmitter 1102 sends a PUSCH in the target air interface resource pool, and first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; when the first information indicates that a PUSCH should be sent in the target air interface resource pool, the first transmitter 1102 sends a PUSCH in the target air interface resource pool.

[0416] As a sub-implementation of the above embodiments, the first signaling is either a DCI that includes a UL grant or a higher-level parameter configuredGrantConfig, the first information is a UCI, and the target air interface resource pool is a PUSCH opportunity.

[0417] As a sub-example of the above embodiment, when the target air interface resource pool does not overlap with the feature resource and the first information indicates that PUSCH is not transmitted in the target air interface resource pool, the first transmitter 1102 abandons the transmission of PUSCH in the target air interface resource pool.

[0418] As one embodiment, the first receiver 1101 receives a first signaling, which is used to determine a target air interface resource pool; the first transmitter 1102 sends first information; wherein, the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether the first transmitter 1102 sends a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, the feature resource being a resource for at least one UCI; when the target air interface resource pool overlaps with a feature resource and the timeline condition for UCI multiplexing to the PUSCH is met, the first transmitter 1102 sends a PUSCH in the target air interface resource pool, and first MCS information is used for the transmission of the PUSCH, the first MCS information being configurable; when the first information indicates that a PUSCH should be sent in the target air interface resource pool, the first transmitter 1102 sends a PUSCH in the target air interface resource pool.

[0419] As a sub-implementation of the above embodiments, the first signaling is either a DCI that includes a UL grant or a higher-level parameter configuredGrantConfig, the first information is a UCI, and the target air interface resource pool is a PUSCH opportunity.

[0420] As a sub-example of the above embodiment, when the target air interface resource pool does not overlap with the feature resource and the first information indicates that PUSCH is not transmitted in the target air interface resource pool, the first transmitter 1102 abandons the transmission of PUSCH in the target air interface resource pool.

[0421] As a sub-implementation of the above embodiments, when the target air interface resource pool overlaps with the feature resource and the timeline condition for UCI multiplexing to PUSCH is not met, and the first information indicates that PUSCH is not transmitted in the target air interface resource pool, the first transmitter 1102 abandons the transmission of PUSCH in the target air interface resource pool.

[0422] Example 12

[0423] Example 12 illustrates a structural block diagram of a processing device in a second node device, as shown in the attached diagram. Figure 12 As shown. In the appendix Figure 12 In the process, the second node device processing unit 1200 includes a second transmitter 1201 and a second receiver 1202.

[0424] As one embodiment, the second node device 1200 is a user equipment.

[0425] As one embodiment, the second node device 1200 is a base station.

[0426] As one embodiment, the second node device 1200 is a satellite device.

[0427] As one embodiment, the second node device 1200 is a relay node.

[0428] As one embodiment, the second node device 1200 is a vehicle-mounted communication device.

[0429] As one embodiment, the second node device 1200 is a user equipment that supports V2X communication.

[0430] As an example, the second node device 1200 is a device that supports operation on the high-frequency spectrum.

[0431] As an example, the second node device 1200 is a device that supports operation on a shared spectrum.

[0432] As one embodiment, the second node device 1200 is a device that supports XR services.

[0433] As one embodiment, the second node device 1200 is one of the testing devices, testing equipment, and testing instruments.

[0434] As one embodiment, the second transmitter 1201 includes the appendix to this application. Figure 4 The antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476 are at least one of them.

[0435] As one embodiment, the second transmitter 1201 includes the appendix to this application. Figure 4 The antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476 are at least the first five of the following:

[0436] As one embodiment, the second transmitter 1201 includes the appendix to this application. Figure 4 At least four of the following: antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476.

[0437] As one embodiment, the second transmitter 1201 includes the appendix to this application. Figure 4 At least three of the following: antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476.

[0438] As one embodiment, the second transmitter 1201 includes the appendix to this application. Figure 4 At least two of the following: antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476.

[0439] As one embodiment, the second receiver 1202 includes the appendix to this application. Figure 4 The antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, and memory 476 are at least one of them.

[0440] As one embodiment, the second receiver 1202 includes the appendix to this application. Figure 4 The antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, and memory 476 are at least the first five of the following:

[0441] As one embodiment, the second receiver 1202 includes the appendix to this application. Figure 4 At least four of the following: antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, and memory 476.

[0442] As one embodiment, the second receiver 1202 includes the appendix to this application. Figure 4 At least three of the following: antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, and memory 476.

[0443] As one embodiment, the second receiver 1202 includes the appendix to this application. Figure 4 At least two of the following: antenna 420, receiver 418, multi-antenna receiver processor 472, receiver processor 470, controller / processor 475, and memory 476.

[0444] As one embodiment, the second transmitter 1201 sends a first signaling message, which is used to determine a target air interface resource pool; the second receiver 1202 receives first information; wherein, the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether the second receiver 1202 receives a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, the feature resource being a resource for at least one UCI; when either a first condition or a second condition is met, the second receiver 1202 receives a PUSCH in the target air interface resource pool, and first MCS information is used for the transmission of the PUSCH, the first MCS information being configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that a PUSCH is sent in the target air interface resource pool.

[0445] As an example, the first set of conditions includes at least the first condition and the second condition; when any condition in the first set of conditions is met, the second receiver 1202 receives PUSCH in the target air interface resource pool; when all conditions in the first set of conditions are not met, the second receiver 1202 abandons receiving PUSCH in the target air interface resource pool.

[0446] As an example, when the first condition is met and the first information indicates that no PUSCH is sent in the target air interface resource pool, the second receiver 1202 receives PUSCH in the target air interface resource pool.

[0447] As an example, when the first condition is not met and the first information indicates that PUSCH is not sent in the target air interface resource pool, the second receiver 1202 abandons receiving PUSCH in the target air interface resource pool.

[0448] As an example, the first signaling is used to determine a plurality of air interface resource pools, the target air interface resource pool being one of the plurality of air interface resource pools, and the first information is received in an air interface resource pool other than the target air interface resource pool among the plurality of air interface resource pools.

[0449] As an example, the first information includes a bitmap, in which any bit is used to indicate whether a PUSCH is sent in one of the plurality of air interface resource pools.

[0450] As an example, the multiple air interface resource pools are multiple PUSCH opportunities. In the same CG cycle, the first information is received in the first PUSCH opportunity among the multiple PUSCH opportunities, and the multiple air interface resource pools do not overlap with each other in the time domain.

[0451] As an example, the target air interface resource pool is a PUSCH opportunity.

[0452] As an example, the target air interface resource pool is a CG PUSCH opportunity.

[0453] Those skilled in the art will understand that all or part of the steps in the above methods can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium, such as a read-only memory, hard disk, or optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiments can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The first node device in this application includes, but is not limited to, wireless communication devices such as mobile phones, tablets, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle communication devices, aircraft, airplanes, drones, and remote-controlled airplanes. The second node device in this application includes, but is not limited to, wireless communication devices such as mobile phones, tablets, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle communication devices, aircraft, airplanes, drones, and remote-controlled airplanes. The user equipment or UE or terminal in this application includes, but is not limited to, wireless communication devices such as mobile phones, tablets, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle communication devices, aircraft, airplanes, drones, and remote-controlled airplanes. The base station equipment or base station or network-side equipment in this application includes, but is not limited to, macrocell base stations, microcell base stations, home base stations, relay base stations, eNB, gNB, Transmitter Receiver Node (TRP), GNSS, relay satellite, satellite base station, airborne base station, testing device, testing equipment, testing instruments, and other equipment.

[0454] Those skilled in the art will understand that the present invention can be practiced in other specified forms without departing from its core or essential characteristics. Therefore, the embodiments disclosed herein should in any way be considered descriptive rather than restrictive. The scope of the invention is defined by the appended claims rather than the foregoing description, and all modifications within their equivalent meaning and scope are considered to be included therein.

Claims

1. A first node for wireless communication, characterized in that, include: The first receiver receives the first signaling, which is used to determine the target air interface resource pool. The first transmitter sends the first message; Wherein, the first information is used to indicate whether to transmit PUSCH in the target air interface resource pool; whether the first transmitter transmits PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, the first transmitter transmits PUSCH in the target air interface resource pool, and the first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that PUSCH is transmitted in the target air interface resource pool.

2. The first node according to claim 1, characterized in that, The first set of conditions includes at least the first condition and the second condition; when any condition in the first set of conditions is met, the first transmitter transmits PUSCH in the target air interface resource pool, and transform precoding is disabled; when none of the conditions in the first set of conditions are met, the first transmitter abandons transmitting PUSCH in the target air interface resource pool.

3. The first node according to claim 1 or 2, characterized in that, When the first condition is met and the first information indicates that no PUSCH is transmitted in the target air interface resource pool, the first transmitter transmits PUSCH in the target air interface resource pool.

4. The first node according to any one of claims 1 to 3, characterized in that, When the first condition is not met and the first information indicates that PUSCH is not to be transmitted in the target air interface resource pool, the first transmitter abandons the transmission of PUSCH in the target air interface resource pool.

5. The first node according to any one of claims 1 to 4, characterized in that, The first signaling is used to identify multiple air interface resource pools, the target air interface resource pool being one of the multiple air interface resource pools, and an air interface resource pool other than the target air interface resource pool being used to send the first information.

6. The first node according to claim 5, characterized in that, The first information includes a bitmap, in which any bit is used to indicate whether a PUSCH is sent in one of the plurality of air interface resource pools.

7. The first node according to claim 5 or 6, characterized in that, The multiple air interface resource pools are multiple PUSCH opportunities. The multiple air interface resource pools are in the same CG period. The first information is sent in the first PUSCH opportunity among the multiple PUSCH opportunities. The multiple air interface resource pools do not overlap with each other in the time domain.

8. A second node for use in wireless communication, characterized in that, include: The second transmitter sends a first signaling message, which is used to determine the target air interface resource pool. The second receiver receives the first information; Wherein, the first information is used to indicate whether to transmit PUSCH in the target air interface resource pool; whether the second receiver receives PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, the second receiver receives PUSCH in the target air interface resource pool, and the first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that PUSCH is transmitted in the target air interface resource pool.

9. A method for use in a first node in wireless communication, characterized in that, include: Receive the first signaling, which is used to determine the target air interface resource pool; Send the first message; Wherein, the first information is used to indicate whether to send a PUSCH in the target air interface resource pool; whether to send a PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, a PUSCH is sent in the target air interface resource pool, and the first MCS information is used for the sending of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that a PUSCH is sent in the target air interface resource pool.

10. A method for a second node in wireless communication, characterized in that, include: Send a first signaling message, which is used to determine the target air interface resource pool; Receive the first message; Wherein, the first information is used to indicate whether to send PUSCH in the target air interface resource pool; whether to receive PUSCH in the target air interface resource pool is related to at least one of the first information and whether the target air interface resource pool overlaps with a feature resource, wherein the feature resource is a resource for at least one UCI; when either the first condition or the second condition is met, PUSCH is received in the target air interface resource pool, and the first MCS information is used for the transmission of the PUSCH, wherein the first MCS information is configurable; the first condition includes the target air interface resource pool overlapping with a feature resource, and the second condition includes the first information indicating that PUSCH is sent in the target air interface resource pool.

Images