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 is used for receiving the uplink and downlink TDD configuration signaling; the first transmitter is used for transmitting a first PUSCH (Physical Uplink Shared Channel) in an effective PUSCH opportunity; wherein for any PUSCH opportunity, whether the PUSCH opportunity is valid or not is related to whether conditions in a first condition set are met or not, and when all conditions in the first condition set are met, the PUSCH opportunity is valid; the first condition set comprises a first condition, whether the first condition is satisfied depends on a first type of symbols, and the first type of symbols comprises symbols which are indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a transmission method and device for wireless signals in a wireless communication system supporting a cellular network. Background Art

[0002] In the existing NR (New Radio) system, spectrum resources are statically divided into FDD (Frequency Division Duplex) spectrum and TDD (Time Division Duplex) spectrum. For TDD spectrum, both base stations and UE (User Equipment) work in half-duplex mode. This half-duplex mode avoids self-interference and can alleviate the impact of cross-link interference (CLI), but it also brings problems such as reduced resource utilization and increased latency. In response to these problems, supporting flexible duplex mode or variable link direction (uplink or downlink or flexible) on TDD spectrum or FDD spectrum has become a possible solution. At the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) 1#103e meeting, research on duplex technology was agreed, especially the sub-band non-overlapping full duplex (SBFD) mode at the gNB (NR Node B) end was proposed. In this mode, the same symbol will be used for uplink in part of the frequency resources and for downlink in another part of the frequency resources, thereby improving resource utilization and reducing latency.

[0003] 3GPP introduced the two-step random access procedure (2-stepRAtypeprocedure) in NR Release-16. The MsgA (MessageA) of the two-step random access procedure includes a random access preamble and a physical uplink shared channel (PUSCH) payload, where the random access preamble is sent on a PRACH opportunity and the physical uplink shared channel payload is sent on a PUSCH opportunity. The time-frequency resources used for the transmission of the physical uplink shared channel payload in MsgA are preconfigured, and some PUSCH opportunities may be invalid due to some resource conflicts. Summary of the invention

[0004] After introducing symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission, how to enhance PUSCH opportunities is an important issue to be considered in order to improve random access performance; the present application discloses solutions to the above problems. It should be noted that the present application can be applied to a variety of wireless communication scenarios, such as scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, scenarios supporting only half-duplex modes, etc., and achieve similar technical effects. In addition, the use of a unified solution for different scenarios (including but not limited to scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, and scenarios supporting only half-duplex modes) can also help reduce hardware complexity and cost, or improve performance. In the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily.

[0005] If necessary, the interpretation of the terms in this application may refer to the description of the 3GPP specification protocols TS37 series and TS38 series.

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

[0007] Receiving uplink and downlink TDD configuration signaling;

[0008] Send the first PUSCH in a valid PUSCH opportunity;

[0009] Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0010] As an embodiment, the problem to be solved by the present application includes: how to determine a valid PUSCH opportunity in a scenario that supports allowing MsgAPUSCH transmission on the first type of symbols.

[0011] As an embodiment, the problem to be solved by the present application includes: how to improve the performance of random access.

[0012] As an embodiment, the benefits of the above method include: being conducive to improving resource utilization.

[0013] As an embodiment, the benefits of the above method include: being conducive to improving uplink coverage.

[0014] As an embodiment, the benefits of the above method include: it is helpful to reduce transmission delay.

[0015] As an embodiment, the benefits of the above method include: being helpful in improving the success rate of random access.

[0016] As an embodiment, the benefits of the above method include: facilitating support of full-duplex operation (operation(s)) (non-overlapping sub-bands or other types) at least on the base station side.

[0017] As an embodiment, the benefits of the above method include: it is conducive to flexibly configuring whether a PUSCH opportunity is used for random access according to the current interference environment and resource configuration.

[0018] According to one aspect of the present application, the above method is characterized in that:

[0019] The first condition is that any one of the PUSCH opportunities is in the first type of symbols.

[0020] As an embodiment, the benefits of the above method include: it is facilitating the use of PUSCH resources to send MsgA on symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission, thereby improving the capacity of random access.

[0021] According to one aspect of the present application, the above method is characterized in that:

[0022] The first condition is that the start of any PUSCH opportunity is at least N later than the nearest symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap Related to the subcarrier spacing.

[0023] As an embodiment, the benefits of the above method include: it is facilitating the use of PUSCH resources to send MsgA on symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission, thereby improving the capacity of random access.

[0024] As an embodiment, the benefits of the above method include: sufficient uplink and downlink switching preparation time is reserved.

[0025] As an embodiment, the benefits of the above method include: improving the configuration flexibility of the uplink and downlink switching preparation time.

[0026] According to one aspect of the present application, the above method is characterized in that it includes:

[0027] Sending a first PRACH;

[0028] The first PUSCH is sent after the first PRACH.

[0029] As an embodiment, the benefits of the above method include: improving transmission reliability.

[0030] As an embodiment, the benefits of the above method include: improving the probability of successful random access.

[0031] According to one aspect of the present application, the above method is characterized in that:

[0032] The uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon.

[0033] As an embodiment, the benefits of the above method include: it is facilitating redefinition of cell specific downlink symbols.

[0034] As an embodiment, the benefits of the above method include: being able to effectively utilize symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationCommon and belonging to the first category of symbols to send the first PUSCH, thereby increasing random access capacity or reducing transmission delay of the first PUSCH.

[0035] According to one aspect of the present application, the above method is characterized in that:

[0036] Whether one of the conditions in the first set of conditions is satisfied depends on the SS / PBCH block.

[0037] As an embodiment, the benefits of the above method include: reducing the interference of PUSCH transmission on SS / PBCH blocks.

[0038] According to one aspect of the present application, the above method is characterized in that:

[0039] Any PUSCH opportunity occupies time-frequency resources and is associated with one DMRS resource.

[0040] As an embodiment, the benefits of the above method include: reducing interference between PUSCHs and improving the success rate of random access.

[0041] As an embodiment, the benefits of the above method include: improving the demodulation performance of PUSCH.

[0042] As an embodiment, the benefits of the above method include: being conducive to improving resource utilization.

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

[0044] Send uplink and downlink TDD configuration signaling;

[0045] Receiving a first PUSCH in a valid PUSCH opportunity;

[0046] Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0047] According to one aspect of the present application, the above method is characterized in that:

[0048] The first condition is that any one of the PUSCH opportunities is in the first type of symbols.

[0049] According to one aspect of the present application, the above method is characterized in that:

[0050] The first condition is that the start of any PUSCH opportunity is at least N later than the nearest symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap Related to the subcarrier spacing.

[0051] According to one aspect of the present application, the above method is characterized in that it includes:

[0052] receiving a first PRACH;

[0053] The first PUSCH is received after the first PRACH.

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

[0055] The uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon.

[0056] According to one aspect of the present application, the above method is characterized in that:

[0057] Whether one of the conditions in the first set of conditions is satisfied depends on the SS / PBCH block.

[0058] According to one aspect of the present application, the above method is characterized in that:

[0059] Any PUSCH opportunity occupies time-frequency resources and is associated with one DMRS resource.

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

[0061] A first receiver receives uplink and downlink TDD configuration signaling;

[0062] A first transmitter sends a first PUSCH in a valid PUSCH opportunity;

[0063] Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0065] A second transmitter sends uplink and downlink TDD configuration signaling;

[0066] A second receiver receives a first PUSCH in a valid PUSCH opportunity;

[0067] Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0069] Figure 1 A processing flow chart of a first node according to an embodiment of the present application is shown;

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

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

[0072] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0073] Figure 5 A signal transmission flow chart according to an embodiment of the present application is shown;

[0074] Figure 6 A schematic diagram illustrating a first condition according to an embodiment of the present application is shown;

[0075] Figure 7 A schematic diagram illustrating a first condition according to an embodiment of the present application is shown;

[0076] Figure 8 A schematic diagram illustrating sending a first PRACH according to an embodiment of the present application is shown;

[0077] Fig. 9 A schematic diagram illustrating a first type of symbol according to an embodiment of the present application is shown;

[0078] Fig.10 A schematic diagram illustrating any PUSCH opportunity according to an embodiment of the present application is shown;

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

[0080] Fig.12 A structural block diagram of a processing device in a second node device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

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

[0082] Example 1

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

[0084] In Embodiment 1, the first node in the present application receives uplink and downlink TDD configuration signaling in step 101; and sends a first PUSCH in a valid PUSCH opportunity in step 102.

[0085] In embodiment 1, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met, and when all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0086] As an embodiment, the uplink and downlink TDD configuration signaling includes higher layer signaling.

[0087] As an embodiment, the uplink and downlink TDD configuration signaling includes semi-static signaling.

[0088] As an embodiment, the uplink and downlink TDD configuration signaling includes cell common signaling.

[0089] As an embodiment, the uplink and downlink TDD configuration signaling includes UE group common signaling.

[0090] As an embodiment, the uplink and downlink TDD configuration signaling includes UE-specific signaling.

[0091] As an embodiment, the link direction configuration configured by the uplink and downlink TDD configuration signaling is applicable to the entire frequency band occupied by the service cell to which it belongs.

[0092] As an embodiment, the link direction configuration configured by the uplink and downlink TDD configuration signaling is applicable to the entire carrier to which it belongs.

[0093] As an embodiment, the uplink and downlink TDD configuration signaling includes RRC signaling.

[0094] As an embodiment, the uplink and downlink TDD configuration signaling includes one or more RRC IEs.

[0095] As an embodiment, the uplink and downlink TDD configuration signaling includes multiple RRC IEs.

[0096] As an embodiment, the uplink and downlink TDD configuration signaling includes one or more fields of each RRC IE in multiple RRC IEs.

[0097] As an embodiment, the uplink and downlink TDD configuration signaling is an RRC IE.

[0098] As an embodiment, the uplink and downlink TDD configuration signaling includes one or more fields in an RRC IE.

[0099] As an embodiment, the uplink and downlink TDD configuration signaling is a signaling indicating the link direction of the symbol.

[0100] As an embodiment, the uplink and downlink TDD configuration signaling includes time domain configuration information.

[0101] As an embodiment, the uplink and downlink TDD configuration signaling includes UL / DL (Uplink / Downlink) TDD (Time Division Duplexing) configuration information.

[0102] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon.

[0103] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationDedicated.

[0104] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0105] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationCommon.

[0106] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationDedicated.

[0107] As an embodiment, the name of the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon.

[0108] As an embodiment, the name of the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationDedicated.

[0109] As an embodiment, the first PUSCH is a PUSCH used for a second type of random access procedure (Type-2 random access procedure).

[0110] As a sub-embodiment of this embodiment, the second type of random access process is a CBRA (Contention Based Random Access) process.

[0111] As a sub-embodiment of this embodiment, the second type of random access process is a CFRA (Contention Free Random Access, contention-free random access) process.

[0112] As a sub-embodiment of this embodiment, the second type of random access procedure is used to obtain synchronous reconfiguration (reconfiguration with sync).

[0113] As a sub-embodiment of this embodiment, the second type of random access procedure is used to obtain uplink synchronization.

[0114] As a sub-embodiment of this embodiment, the second type of random access procedure is used for BFR (Beam Failure Recovery).

[0115] As a sub-embodiment of this embodiment, the second type of random access process is used for handover (HO).

[0116] As a sub-embodiment of this embodiment, the second type of random access process is used for cell switching.

[0117] As an embodiment, the first PUSCH is a PUSCH in a 2-step RACH (Random Access CHannel).

[0118] As an embodiment, the first PUSCH is a MsgAPUSCH.

[0119] As an embodiment, the first PUSCH carries a part of MsgA.

[0120] As an embodiment, MsgA described in this application refers to: Massage A, message A.

[0121] As an embodiment, MsgA described in this application refers to: Msg A, message A.

[0122] As an embodiment, MsgA described in this application refers to: MSGA, message A.

[0123] As an embodiment, the first node is configured with multiple PUSCH opportunities.

[0124] As an embodiment, the first PUSCH occupies a valid PUSCH opportunity.

[0125] As an embodiment, PUSCH may be sent in a valid PUSCH opportunity.

[0126] As an embodiment, if a PUSCH opportunity is not valid, PUSCH is not sent in this PUSCH opportunity.

[0127] As an embodiment, a PUSCH opportunity is defined by time-frequency resources.

[0128] As an embodiment, the expression "sending a first PUSCH" includes the following meaning: sending a signal in the first PUSCH.

[0129] As an embodiment, the statement "sending a first PUSCH" includes the following meaning: sending a bit block on the first PUSCH.

[0130] As an embodiment, the expression "sending a first PUSCH" includes the following meaning: sending at least one of a transport block (transportblock(s)) or a CSI report (report(s)) on the first PUSCH.

[0131] As an embodiment, the expression "sending a first PUSCH" includes the following meaning: performing a first PUSCH transmission (PUSCH transmission).

[0132] As an embodiment, the statement "sending a first PUSCH" includes: at least one of the transport block or the CSI report (report(s)) undergoes CRC attachment, code block segmentation, code block CRC (Cyclic redundancy check) attachment, channel coding, rate matching, code block concatenation, scrambling, modulation, layer mapping, transform precoding, precoding, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and modulation up-conversion and then is sent on the first PUSCH.

[0133] As an embodiment, the statement "sending PUSCH" includes: at least one of the coded bits in the transport block or the CSI report (report(s)) is subjected to scrambling, modulation, layer mapping, antenna port mapping, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and modulation up-conversion and then sent on the first PUSCH.

[0134] As an embodiment, the statement "sending PUSCH" includes: at least one of the transport block or CSI report (report(s)) undergoes CRC attachment, code block segmentation, code block CRC attachment, channel coding, rate matching, code block concatenation, scrambling, modulation, layer mapping, precoding, antenna port mapping, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and modulation up-conversion, and then is sent on the first PUSCH.

[0135] As an embodiment, any one of the PUSCH opportunities is defined by frequency domain resources and time domain resources.

[0136] As an embodiment, any one of the PUSCH opportunities occupies time-frequency resources.

[0137] As an embodiment, any one of the PUSCH opportunities is configurable.

[0138] As an embodiment, any one of the PUSCH opportunities is associated with a DMRS (DeModulation Reference Signal) resource.

[0139] As an embodiment, DMRS resources may be carried on any of the PUSCH opportunities.

[0140] As an embodiment, if a PUSCH opportunity is not valid, the PUSCH opportunity is not used to send PUSCH.

[0141] As an embodiment, whether any PUSCH opportunity is valid or not is related to whether the conditions in the first condition set are met.

[0142] As an embodiment, when all conditions in the first condition set are met, any PUSCH opportunity is valid.

[0143] As an embodiment, if any of the PUSCH opportunities is not valid, then at least one condition in the first condition set is not satisfied.

[0144] As an embodiment, when the first condition is met, whether any one of the PUSCH opportunities is valid also depends on whether other conditions in the first condition set except the first condition are met. If any one of the PUSCH opportunities is not valid, then there is at least one condition in the first condition set that is not met.

[0145] As an embodiment, if any PUSCH opportunity is not valid, the first condition is not satisfied or there is at least one condition in the first condition set other than the first condition that is not satisfied.

[0146] As an embodiment, when the first condition is not met, any PUSCH opportunity is not valid.

[0147] As an embodiment, when all conditions in the first condition set are met, any one of the PUSCH opportunities is valid, and the first PUSCH is sent in any one of the PUSCH opportunities.

[0148] As an embodiment, when at least one condition in the first condition set is not satisfied, any one of the PUSCH opportunities is not valid, and the first PUSCH is not sent in any one of the PUSCH opportunities.

[0149] As an embodiment, the first condition set includes conditions for determining whether any of the PUSCH opportunities is a valid PUSCH opportunity.

[0150] As an embodiment, the first condition set only includes the first condition.

[0151] As an embodiment, the first condition set also includes at least one condition other than the first condition.

[0152] As an embodiment, the first condition set also includes: any PUSCH opportunity does not overlap with any valid PRACH opportunity (valid PRACH occassion) in the time domain and the frequency domain.

[0153] As a sub-embodiment of this embodiment, the valid PRACH opportunity includes a PRACH opportunity associated with a first type of random access procedure.

[0154] As a sub-embodiment of this embodiment, the valid PRACH opportunities also include PRACH opportunities associated with the second type of random access process.

[0155] As a sub-embodiment of this embodiment, a valid PRACH opportunity may be used to send a preamble.

[0156] As a sub-embodiment of this embodiment, if a PRACH opportunity is not a valid PRACH opportunity, then this PRACH opportunity is not used to send a preamble.

[0157] As a sub-embodiment of this embodiment, a valid PRACH opportunity may be used for PRACH transmission.

[0158] As a sub-embodiment of this embodiment, if a PRACH opportunity is not a valid PRACH opportunity, then this PRACH opportunity is not used for PRACH transmission.

[0159] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the effective PRACH opportunity are configured by higher layer signaling.

[0160] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured by RRC signaling.

[0161] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured in part or all of the fields of the RACH-ConfigCommon IE.

[0162] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured in part or all of the fields of the MagA-ConfigCommon IE.

[0163] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured in part or all of the fields of RACH-ConfigCommonTwoStepRAIE.

[0164] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured in part or all of the fields of the RACH-ConfigGeneric IE.

[0165] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured in part or all of the fields of RACH-ConfigGenericTwoStepRAIE.

[0166] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured in part or all of the fields of the RACH-ConfigDedicated IE.

[0167] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured in part or all of the fields of the CFRA-TwoStep IE.

[0168] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured by a SIB (System Information Block) message.

[0169] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the valid PRACH opportunity are configured by SIB1.

[0170] As a sub-embodiment of this embodiment, the time-frequency resources occupied by the effective PRACH opportunity are pre-defined.

[0171] As a sub-embodiment of this embodiment, the name of the RRC signaling for configuring the valid PRACH includes "RACH".

[0172] As a sub-embodiment of this embodiment, the name of the RRC signaling for configuring the valid PRACH includes "Config".

[0173] As a sub-embodiment of this embodiment, the name of the RRC signaling for configuring the valid PRACH includes "TwoStep".

[0174] As a sub-embodiment of this embodiment, the name of the RRC signaling for configuring the valid PRACH includes "RA".

[0175] As a sub-embodiment of this embodiment, the step of determining the valid PRACH opportunity refers to Section 8.1 of 3GPP TS38.213.

[0176] As an embodiment, when any PUSCH opportunity overlaps with any valid PRACH opportunity (valid PRACH occassion) in the time domain, any PUSCH opportunity is not valid.

[0177] As a sub-embodiment of this embodiment, the valid PRACH opportunity includes a PRACH opportunity associated with a first type of random access procedure.

[0178] As a sub-embodiment of this embodiment, the valid PRACH opportunities also include PRACH opportunities associated with the second type of random access process.

[0179] As a sub-embodiment of this embodiment, the step of determining the valid PRACH opportunity refers to Section 8.1 of 3GPP TS38.213.

[0180] As an embodiment, when any PUSCH opportunity overlaps with any valid PRACH opportunity (validPRACH occassion) in the frequency domain, any PUSCH opportunity is not valid.

[0181] As a sub-embodiment of this embodiment, the valid PRACH opportunity includes a PRACH opportunity associated with a first type of random access procedure.

[0182] As a sub-embodiment of this embodiment, the valid PRACH opportunities also include PRACH opportunities associated with the second type of random access process.

[0183] As a sub-embodiment of this embodiment, the step of determining the valid PRACH opportunity refers to Section 8.1 of 3GPP TS38.213.

[0184] As an embodiment, when any PUSCH opportunity overlaps with any valid PRACH opportunity (valid PRACH occassion) in the time domain or the frequency domain, any PUSCH opportunity is not valid.

[0185] As a sub-embodiment of this embodiment, the valid PRACH opportunity includes a PRACH opportunity associated with a first type of random access procedure.

[0186] As a sub-embodiment of this embodiment, the valid PRACH opportunities also include PRACH opportunities associated with the second type of random access process.

[0187] As a sub-embodiment of this embodiment, the step of determining the valid PRACH opportunity refers to Section 8.1 of 3GPP TS38.213.

[0188] As an embodiment, the first type of symbols includes symbols indicated as uplink symbols (UL symbols) by the uplink and downlink TDD configuration signaling.

[0189] As an embodiment, the first category of symbols does not include symbols indicated as uplink symbols by the uplink and downlink TDD configuration signaling.

[0190] As an embodiment, the first type of symbols is configurable.

[0191] As an embodiment, the benefits of the above method include: facilitating support of full-duplex operation (sub-band non-overlapping or other types) at least on the base station side.

[0192] As an embodiment, the benefits of the above method include: improving the configuration or scheduling flexibility of the PUSCH used to carry MsgA.

[0193] As an embodiment, the first information block includes configuration information of the first category of symbols.

[0194] As a sub-embodiment of this embodiment, the first information block is carried by higher layer signaling.

[0195] As a sub-embodiment of this embodiment, the first information block is carried by RRC (Radio Resource Control) signaling.

[0196] As a sub-embodiment of this embodiment, the first information block includes information in at least one RRC IE (Information Element).

[0197] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in an RRC IE.

[0198] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in each RRC IE in multiple RRC IEs.

[0199] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in a SIB (System Information Block).

[0200] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in the MIB (Master Information Block).

[0201] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in SIB1 (System Information Block 1).

[0202] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in RMSI (Remaining Minimum System Information).

[0203] As a sub-embodiment of this embodiment, the first information block is cell-common.

[0204] As a sub-embodiment of this embodiment, the first information block is cell-specific.

[0205] As a sub-embodiment of this embodiment, the first information block is group-common.

[0206] As a sub-embodiment of this embodiment, the first information block is user equipment (UE-dedicated).

[0207] As a sub-embodiment of this embodiment, the first information block is configured per subband.

[0208] As a sub-embodiment of this embodiment, the first information block is configured per (per) BWP (BandWidth Part, partial bandwidth).

[0209] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "tdd".

[0210] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "DL".

[0211] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "UL".

[0212] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "Config".

[0213] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "SBFD".

[0214] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "subband".

[0215] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "duplex".

[0216] As a sub-embodiment of this embodiment, the first information block is carried by a MAC CE (Medium Access Control layer Control Element).

[0217] As a sub-embodiment of this embodiment, the first information block includes information in at least one MAC CE.

[0218] As a sub-embodiment of this embodiment, the first information block is carried by dynamic signaling.

[0219] As a sub-embodiment of this embodiment, the first information block is carried by physical layer signaling.

[0220] As a sub-embodiment of this embodiment, the first information block is carried by DCI (Downlink Control Information, downlink control information).

[0221] As a sub-embodiment of this embodiment, the first information block includes information in at least one RRC IE and information in at least one DCI.

[0222] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields in a DCI format.

[0223] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields in DCI format 2_X, where X is a non-negative integer.

[0224] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields in DCI format2_8.

[0225] As a sub-embodiment of this embodiment, the first information block is used to configure SBFD (SubBand non-overlapping Full Duplex) time slots or symbols.

[0226] As a sub-embodiment of this embodiment, the first information block is used to configure a time slot or symbol supporting full-duplex.

[0227] As a sub-embodiment of this embodiment, whether the symbol used for SS / PBCH block (SS / PBCH block, synchronization signal and physical broadcast channel block) reception is the first type of symbol is configured by the first information block.

[0228] As a sub-embodiment of this embodiment, the benefits of the above method include: it is helpful to ensure the reception performance of the SS / PBCH block through reasonable configuration.

[0229] As a sub-embodiment of this embodiment, the symbols used for SS / PBCH block (SS / PBCH block, synchronization signal and physical broadcast channel block) reception are not the first type of symbols.

[0230] As a sub-embodiment of this embodiment, the first information block is received before the uplink and downlink TDD configuration signaling.

[0231] As a sub-embodiment of this embodiment, the first information block is received after the uplink and downlink TDD configuration signaling.

[0232] As a sub-embodiment of this embodiment, the first information block and the uplink and downlink TDD configuration signaling are received simultaneously.

[0233] Typically, PBCH (Physical Broadcast CHannel), PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal) form a SS / PBCH block in consecutive symbols.

[0234] As an embodiment, which symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling belong to the first category of symbols is configurable.

[0235] As an embodiment, the benefits of the above method include: improving the configuration or scheduling flexibility of the PUSCH used to carry MsgA.

[0236] As an embodiment, the benefits of the above method include: reducing the delay of random access.

[0237] As an embodiment, the benefits of the above method include: being helpful in improving the coverage of MsgA.

[0238] As an embodiment, which symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling do not belong to the first category of symbols are configurable.

[0239] As an embodiment, the benefits of the above method include: improving the configuration or scheduling flexibility of the PUSCH used to carry MsgA.

[0240] As an embodiment, the benefits of the above method include: being conducive to reducing cross-link interference (Cross-Link Interference, CLI).

[0241] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least PUSCH (Physical Uplink Shared CHannel) transmission.

[0242] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least PUCCH (Physical Uplink Control CHannel) transmission.

[0243] As an embodiment, the expression "can be used for uplink transmission" means: can be used at least for SRS (Sounding Reference Signal) transmission.

[0244] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least one of PUSCH transmission, PUCCH transmission, PRACH (Physical Random Access CHannel) transmission and SRS transmission.

[0245] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least two of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0246] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least three of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0247] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0248] As an embodiment, the expression "can be used for uplink transmission" means: can be used for transmission of UL-SCH (Uplink Shared Channel(s)).

[0249] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission carrying MsgA.

[0250] As an embodiment, the statement "whether the first condition is satisfied depends on the first category of symbols" means: whether the first condition is satisfied depends on which symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling belong to the first category of symbols.

[0251] As an embodiment, the statement "whether the first condition is satisfied depends on the first category of symbols" means: whether the first condition is satisfied depends on which symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling do not belong to the first category of symbols.

[0252] As an embodiment, a symbol in the present application is a time domain symbol.

[0253] As an embodiment, a symbol in the present application is a symbol in a slot.

[0254] As an embodiment, a symbol in the present application includes a time duration in the time domain.

[0255] As an embodiment, a symbol in the present application is a single carrier symbol.

[0256] As an embodiment, a symbol in the present application is a multi-carrier symbol.

[0257] As an embodiment, a symbol in the present application is a SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol.

[0258] As an embodiment, a symbol in the present application is a FBMC (Filter Bank Multi Carrier) symbol.

[0259] As an embodiment, a symbol in the present application is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0260] As an embodiment, a symbol in the present application is obtained by performing OFDM symbol generation on the output of a transform precoding.

[0261] As an embodiment, a symbol in the present application is a DFT-s-OFDM (Discrete Fourier Transform spread OFDM) symbol.

[0262] As an embodiment, a symbol in the present application includes a CP-OFDM (Cyclic Prefix-OFDM) symbol.

[0263] Example 2

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

[0265] As an embodiment, the UE201 corresponds to the first node in the present application.

[0266] As an embodiment, the UE201 is a user equipment (User Equipment, UE).

[0267] As an embodiment, the UE201 is a base station (BS).

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

[0269] As an embodiment, the UE201 is a gateway device.

[0270] As an embodiment, the node 203 corresponds to the second node in the present application.

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

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

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

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

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

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

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

[0278] As an embodiment, the user equipment supports a more flexible duplex mode or a full-duplex mode (non-overlapping sub-bands or other types).

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

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

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

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

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

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

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

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

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

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

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

[0290] As an embodiment, the base station device supports a more flexible duplex mode or a (non-overlapping sub-band or other type) full-duplex mode.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0317] Example 3

[0318] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 for a first communication node device (RSU (Road Side Unit) in a UE, gNB or V2X (Vehicle to Everything), a vehicle-mounted device or a vehicle-mounted communication module) and a second communication node device (RSU in a gNB, UE or V2X, a vehicle-mounted device or a vehicle-mounted communication module), or two UEs is shown with three layers: Layer 1 (Layer 1, L1), Layer 2 (Layer 2, L2) and Layer 3 (Layer 3, L3). L1 is the lowest layer and implements various PHY (physical layer) signal processing functions. L1 will be referred to as PHY301 in this article. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first communication node device and the second communication node device and the two UEs through PHY301. L2305 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. The PDCP sublayer 304 also provides security by encrypting data packets, and provides inter-zone mobility support for the first communication node device between the second communication node device. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception caused by HARQ (Hybrid Automatic Repeat Qequest). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in L3 in the control plane 300 is responsible for obtaining radio resources (ie, radio bearers) and configuring lower layers using RRC signaling between the second communication node device and the first communication node device.The radio protocol architecture of the user plane 350 includes layer 1 (L1) and layer 2 (L2). The radio protocol architecture for the first communication node device and the second communication node device in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support the diversity of services. Although not shown in the figure, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., IP (Internet Protocol) 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, a server, etc.).

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

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

[0321] As an embodiment, the uplink and downlink TDD configuration signaling in the present application is generated in the RRC sublayer 306.

[0322] As an embodiment, the first information block in the present application is generated in the RRC sublayer 306.

[0323] As an embodiment, the first information block in the present application is generated in the MAC sublayer 302 or the MAC sublayer 352.

[0324] As an embodiment, the first information block in the present application is generated in the PHY301 or PHY351.

[0325] As an embodiment, the first PUSCH in the present application is generated by the PHY351.

[0326] As an embodiment, the first PRACH in the present application is generated in the PHY301 or PHY351.

[0327] As an embodiment, the higher layer in the present application refers to a layer above the physical layer.

[0328] As an embodiment, the higher layer in the present application includes a MAC layer.

[0329] As an embodiment, the higher layer in the present application includes an RRC layer.

[0330] Example 4

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

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

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

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

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

[0336] 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 function 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, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the first communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0337] 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 reception 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 a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the second communication device 450 to the first communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0338] As an embodiment, the first node in the present application includes the second communication device 450 , and the second node in the present application includes the first communication device 410 .

[0339] As a sub-embodiment of the above embodiment, the first node is a user equipment, and the second node is a relay node.

[0340] As a sub-embodiment of the above embodiment, the first node is a user equipment, and the second node is a base station device.

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

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

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

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

[0345] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 450 device at least: receives uplink and downlink TDD configuration signaling; sends a first PUSCH in a valid PUSCH opportunity; wherein, for any PUSCH opportunity, the validity is related to whether the conditions in the first condition set are met, and when all conditions in the first condition set are met, the any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0347] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving uplink and downlink TDD configuration signaling; sending a first PUSCH in a valid PUSCH opportunity; wherein, for any PUSCH opportunity, the validity is related to whether the conditions in a first condition set are met, and when all conditions in the first condition set are met, the any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0349] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends uplink and downlink TDD configuration signaling; receives a first PUSCH in a valid PUSCH opportunity; wherein, for any PUSCH opportunity, the validity is related to whether the conditions in the first condition set are met, and when all conditions in the first condition set are met, the any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0351] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending uplink and downlink TDD configuration signaling; receiving a first PUSCH in a valid PUSCH opportunity; wherein, for any PUSCH opportunity, the validity or not is related to whether the conditions in a first condition set are met, and when all conditions in the first condition set are met, the any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0353] As an embodiment, 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 uplink and downlink TDD configuration signaling in the present application.

[0354] As an embodiment, at least one of {the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475, and the memory 476} is used to send the first RRC signaling uplink and downlink TDD configuration signaling in the present application.

[0355] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to send the first PUSCH in the one valid PUSCH opportunity in the present application.

[0356] As an embodiment, at least one of {the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470, the controller / processor 475, and the memory 476} is used to receive the first PUSCH in the one valid PUSCH opportunity in the present application.

[0357] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to send the first PRACH in the present application.

[0358] As an embodiment, at least one of {the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470, the controller / processor 475, and the memory 476} is used to receive the first PRACH in the present application.

[0359] Example 5

[0360] Embodiment 5 illustrates a signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 As shown in the attached Figure 5 In the embodiment, the first node U1 and the second node U2 communicate with each other through the air interface. Figure 5 , the steps in the dashed box F1 are optional.

[0361] The first node U1 receives uplink and downlink TDD configuration signaling in step S511; sends a first PRACH in step S51A; and sends a first PUSCH in a valid PUSCH opportunity in step S512.

[0362] The second node U2 sends uplink and downlink TDD configuration signaling in step S521; receives a first PRACH in step S52A; and receives a first PUSCH in a valid PUSCH opportunity in step S522.

[0363] In embodiment 5, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met, and when all conditions in the first condition set are met, the any PUSCH opportunity is valid; the any PUSCH opportunity occupies time-frequency resources and is associated with a DMRS resource; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission; the first condition is: the any PUSCH opportunity is in the first type of symbol; or the first condition is: the start of any PUSCH opportunity is at least N later than the most recent symbol that does not belong to the first type of symbol and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap Related to the subcarrier spacing.

[0364] As a sub-embodiment of Embodiment 5, the first PUSCH is sent after the first PRACH.

[0365] As a sub-embodiment of Embodiment 5, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon.

[0366] As a sub-embodiment of Embodiment 5, whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block.

[0367] As an embodiment, the first node U1 is the first node in this application.

[0368] As an embodiment, the second node U2 is the second node in the present application.

[0369] As an embodiment, the first node U1 is a UE.

[0370] As an embodiment, the second node U2 is a base station.

[0371] As an embodiment, the air interface between the second node U2 and the first node U1 is a Uu interface.

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

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

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

[0375] As an embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between a relay device and a user equipment.

[0376] As an example, Figure 5 The steps in the dashed box F1 exist.

[0377] As an embodiment, the sending / receiving of the first PUSCH is after the first PRACH.

[0378] As an embodiment, the transmission / reception of the first PUSCH and the first PRACH are not in the same time slot.

[0379] As an example, Figure 5 The steps in the dashed box F1 do not exist.

[0380] Example 6

[0381] Embodiment 6 illustrates a schematic diagram of the first condition according to an embodiment of the present application, as shown in the attached Figure 6 shown.

[0382] In Embodiment 6, the first condition is that any one of the PUSCH opportunities is in the first category of symbols.

[0383] As an embodiment, when every symbol occupied by a PUSCH opportunity in the time domain is a symbol of the first category, the PUSCH opportunity is in the first category of symbols; when at least one symbol occupied by a PUSCH opportunity in the time domain is not a symbol of the first category, the PUSCH opportunity is not in the first category of symbols.

[0384] As an embodiment, when each symbol occupied by a PUSCH opportunity in the time domain overlaps with the first category of symbols, this PUSCH opportunity is in the first category of symbols; when at least one symbol occupied by a PUSCH opportunity in the time domain does not overlap with the first category of symbols, this PUSCH opportunity is not in the first category of symbols.

[0385] As an embodiment, when any symbol overlapping with a PUSCH opportunity in the time domain is the first type of symbol, this PUSCH opportunity is in the first type of symbols; when at least one symbol overlapping with a PUSCH opportunity in the time domain is not the first type of symbol, this PUSCH opportunity is not in the first type of symbols.

[0386] As an embodiment, the first condition set includes the first condition.

[0387] As an embodiment, the first condition set also includes: any PUSCH opportunity does not overlap with any valid PRACH occasion (valid PRACH occasion) in the time domain and the frequency domain.

[0388] As an embodiment, the first condition set further includes: the start of any PUSCH opportunity is at least N times later than the last downlink symbol that does not belong to the first category of symbols. gap symbols, the N gap Related to the subcarrier spacing.

[0389] As an embodiment, the most recent downlink symbol that does not belong to the first category of symbols is: the last symbol that does not belong to the first category of symbols before the start of any PUSCH opportunity and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling.

[0390] As an embodiment, the most recent downlink symbol that does not belong to the first category of symbols is: the last symbol that does not belong to the first category of symbols before the end of any PUSCH opportunity and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling.

[0391] As an embodiment, the first condition set further includes: the start of any PUSCH opportunity is at least N later than the last symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap与 The subcarrier spacing is related.

[0392] As an embodiment, the most recent symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling is: the last symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling before the start of any PUSCH opportunity.

[0393] As an embodiment, the most recent symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling is: the last symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling before the end of any PUSCH opportunity.

[0394] As an embodiment, when the first condition is met and any PUSCH opportunity does not overlap with any valid PRACH opportunity in the time domain and the frequency domain, any PUSCH opportunity is valid.

[0395] Example 7

[0396] Embodiment 7 illustrates a schematic diagram of the first condition according to an embodiment of the present application, as shown in the attached Figure 7 shown.

[0397] In embodiment 7, the first condition is that the start of any PUSCH opportunity is at least N times later than the nearest symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap Related to the subcarrier spacing.

[0398] As an embodiment, the most recent symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling is: the last symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling before the start of any PUSCH opportunity.

[0399] As an embodiment, the most recent symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling is: the last symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling before the end of any PUSCH opportunity.

[0400] As an embodiment, when the start of any PUSCH opportunity is not at least N later than the most recent symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling gap When 1 symbol, any PUSCH opportunity is not valid.

[0401] As an embodiment, the first condition set includes the first condition.

[0402] As an embodiment, the first condition set further includes: the start of any PUSCH opportunity is at least N times later than the symbol of the last downlink symbol that does not belong to the first category of symbols. gap symbols, the N gap Related to the subcarrier spacing.

[0403] As an embodiment, the benefits of the above method include: sufficient uplink and downlink switching preparation time is reserved.

[0404] As an embodiment, the benefits of the above method include: improving the configuration flexibility of the uplink and downlink switching preparation time.

[0405] As an embodiment, the most recent downlink symbol that does not belong to the first category of symbols is: the last symbol that does not belong to the first category of symbols before the start of any PUSCH opportunity and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling.

[0406] As an embodiment, the most recent downlink symbol that does not belong to the first category of symbols is: the last symbol that does not belong to the first category of symbols before the end of any PUSCH opportunity and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling.

[0407] As an embodiment, when the start of any PUSCH opportunity is not at least N later than the symbol of the nearest downlink symbol that does not belong to the first category of symbols gap When 1 symbol, any PUSCH opportunity is not valid.

[0408] As an embodiment, the benefits of the above method include: reducing the interference of PUSCH transmission on SS / PBCH blocks.

[0409] As an embodiment, the first condition set further includes: the start of any PUSCH opportunity is at least N later than the most recent SS / PBCH block symbol. gap symbols, the N gap Related to the subcarrier spacing.

[0410] As an embodiment, the most recent SS / PBCH block symbol is the last symbol of the last SS / PBCH block before the start of any PUSCH opportunity.

[0411] As an embodiment, the most recent SS / PBCH block symbol is the last symbol of the last SS / PBCH block before the end of any PUSCH opportunity.

[0412] As an example, the N gap is configurable.

[0413] As an example, the N in this application gap Depends on the subcarrier spacing.

[0414] As an example, the N in this application gap The mapping relationship between the candidates and multiple preamble subcarrier spacings (Preamble SubCarrier Spacing, Preamble SCS) is predefined.

[0415] As an example, the N in this application gap The candidate is a non-negative integer.

[0416] As an example, the N in this application gap The candidates include 0, 2, 8 and 16.

[0417] As an embodiment, the first condition set also includes: any PUSCH opportunity in the PUSCH time slot is not before the SS / PBCH.

[0418] As a sub-embodiment of this embodiment, the PUSCH time slot is a time slot to which any PUSCH opportunity belongs in the time domain.

[0419] As an embodiment, when any PUSCH opportunity is before the SS / PBCH block in the PUSCH time slot, any PUSCH opportunity is not valid.

[0420] As an embodiment, the benefits of the above method include: reducing the interference of PUSCH transmission on SS / PBCH blocks.

[0421] As an embodiment, the first condition set further includes: if channelAccessMode is configured as semiStatic, any PUSCH opportunity has no overlap with consecutive time domain symbols that are not used for transmission before the start of the next channel occupancy time;

[0422] As an embodiment, if channelAccessMode is configured as semiStatic, when any PUSCH opportunity overlaps with a continuous time domain symbol that is not used to perform transmission before the start of the next channel occupancy time, any PUSCH opportunity is not valid.

[0423] As an embodiment, if channelAccessMode is configured as dynamic, the validity of any PUSCH opportunity is related to whether other conditions in the first condition set are met; when the other conditions in the first condition set are met, any PUSCH opportunity is valid; otherwise, any PUSCH opportunity is not valid.

[0424] As an embodiment, the first condition set also includes: any PUSCH opportunity does not overlap with any valid PRACH occasion (valid PRACH occasion) in the time domain and the frequency domain.

[0425] As an embodiment, when any PUSCH opportunity overlaps with any valid PRACH occasion in the time domain or the frequency domain, any PUSCH occasion is not valid.

[0426] As an embodiment, the benefits of the above method include: reducing the possibility of conflict between PUSCH and PRACH.

[0427] As an embodiment, the benefits of the above method include: reducing the interference of PUSCH transmission on PRACH.

[0428] As an embodiment, the statement "whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block" means: whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block that is not in the PUSCH time slot, and the PUSCH time slot is the time slot to which any PUSCH opportunity belongs in the time domain.

[0429] As an embodiment, the statement "whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block" means: whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block before any PUSCH opportunity in the PUSCH time slot, and the PUSCH time slot is the time slot to which any PUSCH opportunity belongs in the time domain.

[0430] As an embodiment, the statement "whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block" means: whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block in the PUSCH time slot that is not before any PUSCH opportunity, and the PUSCH time slot is the time slot to which any PUSCH opportunity belongs in the time domain.

[0431] As an embodiment, the statement "whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block" means: whether one of the conditions in the first condition set is satisfied depends on the most recent SS / PBCH block before any PUSCH opportunity.

[0432] As an embodiment, the statement "whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block" means: whether one of the conditions in the first condition set is satisfied depends on the most recent SS / PBCH block before the start of any PUSCH opportunity.

[0433] As an embodiment, the statement "whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block" means: whether one of the conditions in the first condition set is satisfied depends on the most recent SS / PBCH block before the end of any PUSCH opportunity.

[0434] Example 8

[0435] Embodiment 8 illustrates a schematic diagram of sending the first PRACH according to an embodiment of the present application, as shown in the attached figure. Figure 8 shown.

[0436] In Embodiment 8, the first node sends a first PRACH, and the first PUSCH is sent after the first PRACH.

[0437] As an embodiment, the first PRACH is a PRACH in a 2-step RACH (Random Access CHannel).

[0438] As an embodiment, the RA-TYPE corresponding to the PRACH is 2-stepRA.

[0439] As an embodiment, the first PRACH is a MsgAPRACH.

[0440] As an embodiment, the first PRACH carries a part of MsgA.

[0441] As an embodiment, the mapping method between the valid PRACH opportunities and the valid PUSCH opportunities is predefined, and the valid PRACH opportunity for sending the first PRACH is mapped to the valid PUSCH opportunity for sending the first PUSCH.

[0442] As an embodiment, a valid PRACH opportunity for sending the first PRACH is configured to be mapped to a valid PUSCH opportunity for sending the first PUSCH.

[0443] As an embodiment, the first node is configured with multiple PRACH opportunities, and the transmission of the first PRACH occupies one of the PRACH opportunities.

[0444] As an embodiment, the definition of valid PRACH opportunities refers to Section 8.1 of 3GPP TS 38.213.

[0445] As an embodiment, a valid PRACH opportunity is a PRACH opportunity that can be used to send a PRACH.

[0446] As an embodiment, the first PRACH carries a random access preamble.

[0447] As an embodiment, the random access preamble carried by the first PRACH is selected by a MAC (Medium Access Control) entity of the first node from among the preambles used for CFRA.

[0448] As an embodiment, the random access preamble carried by the first PRACH is selected by a MAC entity of the first node from among preambles used for CBRA.

[0449] As an embodiment, the random access preamble carried by the first PRACH is a random access preamble used for a 2-step random access process.

[0450] As a sub-embodiment, a ZC (Zadoff-Chu) sequence is used to generate the random access preamble carried by the first PRACH.

[0451] As a sub-embodiment, a pseudo-random sequence is used to generate the random access preamble carried by the first PRACH.

[0452] As an embodiment, the transmission of the first PUSCH is at least N symbols later than the transmission of the first PRACH, where N is related to the subcarrier spacing.

[0453] As an embodiment, the benefits of the above method include: improving configuration flexibility and reducing the probability of resource overlap / conflict.

[0454] As an embodiment, the N in the present application depends on the subcarrier spacing.

[0455] As an embodiment, the mapping relationship between the candidates of N in the present application and the subcarrier spacing (SCS) of the activated uplink partial bandwidth (BandWidth Part, BWP) is predefined.

[0456] As an embodiment, the candidate for N in the present application is a non-negative integer.

[0457] As an embodiment, the candidate for N in the present application is a positive integer.

[0458] As an embodiment, the candidates for N in the present application include 2, 4, 16 and 32.

[0459] As an embodiment, the first PRACH and the first PUSCH carry MsgA together.

[0460] As an embodiment, the first PRACH and the first PUSCH are not in the same time slot.

[0461] Example 9

[0462] Embodiment 9 illustrates a schematic diagram of the first type of symbols according to an embodiment of the present application, as shown in the attached figure. Fig. 9 shown.

[0463] In Embodiment 9, the first type of symbols includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0464] As an embodiment, the benefits of the above method include: being conducive to improving the transmission performance of the uplink.

[0465] As an embodiment, the benefits of the above method include: it is helpful to reduce transmission delay.

[0466] As an embodiment, the benefits of the above method include: facilitating support of full-duplex operation (non-overlapping sub-bands or other types) at least on the base station side.

[0467] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon, and the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission belong to the first category of symbols.

[0468] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationCommon and available for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0469] As an embodiment, the first symbol is a symbol indicated as a downlink symbol by the uplink and downlink TDD configuration signaling, and whether the first symbol belongs to the first category of symbols is configurable; if the first symbol can be used for uplink transmission, the first symbol belongs to the first category of symbols; otherwise, the first symbol does not belong to the first category of symbols.

[0470] As an embodiment, the symbol indicated as an uplink symbol by the uplink and downlink TDD configuration signaling belongs to the first category of symbols.

[0471] As an embodiment, the above method has the following advantages: it has good compatibility with existing 3GPP technical specifications.

[0472] As an embodiment, the symbols indicated as flexible symbols by the uplink and downlink TDD configuration signaling belong to the first category of symbols.

[0473] As an embodiment, the above method has the following advantages: it has good compatibility with existing 3GPP technical specifications.

[0474] As an embodiment, whether the symbol indicated as a flexible symbol by the uplink and downlink TDD configuration signaling belongs to the first category of symbols is configured by the first information block.

[0475] As an embodiment, whether the symbol received for the SS / PBCH block (SS / PBCH block, synchronization signal and physical broadcast channel block) is the first type of symbol is configured by the first information block.

[0476] As an embodiment, the benefits of the above method include: it is helpful to ensure the reception performance of the SS / PBCH block through reasonable configuration.

[0477] As an embodiment, the symbols used for SS / PBCH block reception do not belong to the first category of symbols.

[0478] Example 10

[0479] Embodiment 10 illustrates a schematic diagram of any PUSCH opportunity according to an embodiment of the present application, as shown in the attached figure. Fig.10 shown.

[0480] In embodiment 10, any one of the PUSCH opportunities occupies time-frequency resources and is associated with one DMRS resource.

[0481] As an embodiment, any one of the PUSCH opportunities is predefined for PUSCH transmission.

[0482] As an embodiment, any one of the PUSCH opportunities is predefined for MsgAPUSCH transmission.

[0483] As an embodiment, the time-frequency resources occupied by any PUSCH opportunity depend on the associated mapping between one or more preambles (Preamble) and PUSCH.

[0484] As an embodiment, the benefits of the above method include: facilitating the first node to find associated PUSCH resources after selecting a preamble code.

[0485] As an embodiment, the advantages of the above method include: taking into account both the flexibility and complexity of configuration.

[0486] As an embodiment, the time-frequency resources occupied by any PUSCH opportunity include time domain resources and frequency domain resources.

[0487] As an embodiment, any one of the PUSCH opportunities is a PUSCH opportunity in a PUSCH opportunity group (PUSCH occasions), and the time-frequency resource configuration of the PUSCH opportunity group includes a PUSCH time domain offset, a PUSCH frequency domain starting position and the number of PUSCH time slots.

[0488] As a sub-embodiment of this embodiment, the PUSCH opportunity group occupies several consecutive PUSCH time slots in the time domain, where the several refers to one or more, and each of the several consecutive PUSCH time slots has the same time domain resource allocation.

[0489] As a sub-embodiment of this embodiment, the PUSCH time domain offset is about the starting position of the time slot where each PRACH is located, and each PRACH includes one or more preambles.

[0490] As a sub-embodiment of this embodiment, the PUSCH time domain offset is used to determine the position of the earliest time slot where the first PUSCH opportunity in the time domain is located. The first PUSCH opportunity in the time domain is the first PUSCH opportunity that appears in the time domain in the PUSCH opportunity group.

[0491] As a sub-embodiment of this embodiment, the PUSCH time domain offset is configured through the msgA-PUSCH-TimeDomainOffset field.

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

[0493] As a sub-embodiment of this embodiment, the PUSCH time domain offset is a positive integer.

[0494] As a sub-embodiment of this embodiment, the PUSCH frequency domain starting position is used to determine the lowest PRB position where the first PUSCH opportunity in the frequency domain is located or to determine the IRB index where the first PUSCH opportunity in the frequency domain is located.

[0495] As a sub-embodiment of this embodiment, the PUSCH frequency domain starting position is configured through one of the frequencyStartMsgA-PUSCH field and the interlaceIndexFirstPO-MsgA-PUSCH field.

[0496] As a sub-embodiment of this embodiment, the number of PUSCH time slots is used to determine the number of consecutive time slots in which the PUSCH opportunity group is located.

[0497] As a sub-embodiment of this embodiment, the number of PUSCH time slots is configured through the nrofSlotsMsgA-PUSCH field.

[0498] As a sub-embodiment of this embodiment, the number of PUSCH time slots is a positive integer.

[0499] As an embodiment, any one of the PUSCH opportunities is a PUSCH opportunity in a PUSCH opportunity group (PUSCH occasions), and the time-frequency resource configuration of the PUSCH opportunity group in each time slot includes the number of frequency-division multiplexed PUSCH opportunities, the number of PUSCH opportunities in each time slot, the protection bandwidth between PUSCH opportunities, and the protection interval between PUSCH opportunities.

[0500] As a sub-embodiment of this embodiment, the number of frequency division multiplexed PUSCH opportunities is configured through the nrofMsgA-PO-FDM domain.

[0501] As a sub-embodiment of this embodiment, the number of frequency-division multiplexed PUSCH opportunities is a positive integer.

[0502] As a sub-embodiment of this embodiment, the number of frequency-division multiplexed PUSCH opportunities includes 1, 2, 4 and 8.

[0503] As a sub-embodiment of this embodiment, the number of PUSCH opportunities in each time slot is configured through the nrofMsgA-PO-PerSlot field.

[0504] As a sub-embodiment of this embodiment, the number of PUSCH opportunities in each time slot is a positive integer.

[0505] As a sub-embodiment of this embodiment, the number of PUSCH opportunities in each time slot includes 1, 2, 3 and 6.

[0506] As a sub-embodiment of this embodiment, the guard bandwidth between the PUSCH opportunities is configured through the guardBandMsgA-PUSCH field.

[0507] As a sub-embodiment of this embodiment, the unit of the protection bandwidth between the PUSCH opportunities is RB (Resource Block).

[0508] As a sub-embodiment of this embodiment, the unit of the protection bandwidth between the PUSCH opportunities is PRB (Physical RB, physical resource block).

[0509] As a sub-embodiment of this embodiment, the protection bandwidth between the PUSCH opportunities is a non-negative integer.

[0510] As a sub-embodiment of this embodiment, the guard interval between the PUSCH opportunities is configured via the guardPeriodMsgA-PUSCH field.

[0511] As a sub-embodiment of this embodiment, the unit of the protection interval between the PUSCH opportunities is symbol.

[0512] As a sub-embodiment of this embodiment, the guard interval between the PUSCH opportunities is a non-negative integer.

[0513] As an embodiment, any one of the PUSCH opportunities is a PUSCH opportunity in a PUSCH opportunity group (PUSCH occasions), and the time-frequency resource configuration of the PUSCH opportunity group in each time slot also includes a start symbol and a symbol length of the first PUSCH opportunity in the time domain, and the start symbol and the symbol length of the first PUSCH opportunity in the time domain are configured through one of the startSymbolAndLengthMsgA-PO domain and the msgA-PUSCH-TimeDomainAllocation domain.

[0514] As a sub-embodiment of this embodiment, only one of the startSymbolAndLengthMsgA-PO field and the msgA-PUSCH-TimeDomainAllocation field exists.

[0515] As an embodiment, any PUSCH opportunity includes several IRBs (Interlaced RBs) or PRBs, where the several refers to one or more, and the number of IRBs or PRBs included in any PUSCH opportunity is configured respectively through the nrofInterlacesPerMsgA-PO domain or the nrofPRBs-perMsgA-PO domain.

[0516] As an embodiment, any one of the PUSCH opportunities is configured to be mapped to a DMRS resource.

[0517] As an embodiment, the one DMRS resource associated with any PUSCH opportunity is configured through one or more RRC signalings.

[0518] As an embodiment, the one DMRS resource associated with any PUSCH opportunity is configured through one or more RRC messages.

[0519] As an embodiment, the one DMRS resource associated with any PUSCH opportunity is configured through one or more RRC IE (Information Element).

[0520] As an embodiment, the DMRS resource associated with any PUSCH opportunity is configured through one or more fields in an RRCIE.

[0521] As an embodiment, the one DMRS resource associated with any PUSCH opportunity is configured through a SIB1 (System Information Block 1) message.

[0522] As an embodiment, the one DMRS resource associated with any PUSCH opportunity is configured through at least one field in the MsgA-PUSCH-Config IE.

[0523] As an embodiment, the one DMRS resource associated with any PUSCH opportunity is configured through the MsgA-PUSCH-ResourceGroupA field or the MsgA-PUSCH-ResourceGroupB field in the MsgA-PUSCH-Config IE.

[0524] As a sub-embodiment of this embodiment, the DMRS resource associated with any PUSCH opportunity is related to the selected leading group type through which field configuration in the MsgA-PUSCH-Config IE (Information Element), and the leading group type includes the leading group Group A and the leading group Group B. For the steps of selecting the leading group type, refer to Section 5.1.2a of 3GPP TS 38.321.

[0525] As a sub-embodiment of this embodiment, when the leading group GroupA is selected to transmit MSGA, the one DMRS resource associated with any PUSCH opportunity is configured through the MsgA-PUSCH-ResourceGroupA field in the MsgA-PUSCH-Config IE; when the leading group GroupB is used to transmit MsgA, the DMRS resource is configured through the MsgA-PUSCH-ResourceGroupB field in the MsgA-PUSCH-Config IE.

[0526] As an embodiment, the one DMRS resource associated with any PUSCH opportunity is configured through at least one field in msgA-DMRS-Config.

[0527] Embodiment 11

[0528] Embodiment 11 illustrates a structural block diagram of a processing device in a first node device, as shown in the attached figure. Fig.11 As shown in the attached Fig.11 In the embodiment, the first node device processing apparatus A00 includes a first receiver A01 and a first transmitter A02.

[0529] As an embodiment, the first node device A00 is a user equipment.

[0530] As an embodiment, the first node device A00 is a relay node.

[0531] As an embodiment, the first node device A00 is a vehicle-mounted communication device.

[0532] As an embodiment, the first node device A00 is a conventional user equipment.

[0533] As an embodiment, the first node device A00 is a UE with relevant configuration supporting (non-overlapping sub-bands or other types) full-duplex operation.

[0534] As an embodiment, the first receiver A01 includes the attached Figure 4 At least one of the antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460 and data source 467.

[0535] As an embodiment, the first receiver A01 includes the attached Figure 4 At least the first five of the antenna 452, receiver 454, multi-antenna receive processor 458, receive processor 456, controller / processor 459, memory 460 and data source 467.

[0536] As an embodiment, the first receiver A01 includes the attached Figure 4 At least the first four of the antenna 452, receiver 454, multi-antenna receive processor 458, receive processor 456, controller / processor 459, memory 460 and data source 467.

[0537] As an embodiment, the first receiver A01 includes the attached Figure 4At least the first three of the antenna 452, receiver 454, multi-antenna receive processor 458, receive processor 456, controller / processor 459, memory 460 and data source 467.

[0538] As an embodiment, the first receiver A01 includes the attached Figure 4 At least the first two of the antenna 452, receiver 454, multi-antenna receive processor 458, receive processor 456, controller / processor 459, memory 460 and data source 467.

[0539] As an embodiment, the first transmitter A02 includes the attached Figure 4 At least one of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.

[0540] As an embodiment, the first transmitter A02 includes the attached Figure 4 At least the first five of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.

[0541] As an embodiment, the first transmitter A02 includes the attached Figure 4 At least the first four of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.

[0542] As an embodiment, the first transmitter A02 includes the attached Figure 4 At least the first three of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.

[0543] As an embodiment, the first transmitter A02 includes the attached Figure 4 At least the first two of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.

[0544] As an embodiment, the first receiver A01 receives uplink and downlink TDD configuration signaling; the first transmitter A02 sends a first PUSCH in a valid PUSCH opportunity; wherein, for any PUSCH opportunity, the validity or not is related to whether the conditions in the first condition set are met, and when all conditions in the first condition set are met, the any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0545] As an embodiment, the first condition is that any one of the PUSCH opportunities is in the first category of symbols.

[0546] As an embodiment, the first condition is that the start of any PUSCH opportunity is at least N later than the nearest symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap Related to the subcarrier spacing.

[0547] As an embodiment, the first transmitter A02 sends a first PRACH; wherein the first PUSCH is sent after the first PRACH.

[0548] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommond.

[0549] As an embodiment, whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block.

[0550] As an embodiment, any one of the PUSCH opportunities occupies time-frequency resources and is associated with a DMRS resource.

[0551] Example 12

[0552] Embodiment 12 illustrates a structural block diagram of a processing device in a second node device, as shown in the attached figure. Fig.12 As shown in the attached Fig.12 In the embodiment, the second node device processing apparatus B00 includes a second transmitter B01 and a second receiver B02.

[0553] As an embodiment, the second node device B00 is a base station.

[0554] As an embodiment, the second node device B00 is a satellite device.

[0555] As an embodiment, the second node device B00 is a relay node.

[0556] As an embodiment, the second node device B00 is a base station supporting full-duplex operation (non-overlapping sub-bands or other types).

[0557] As an embodiment, the second node device B00 is a base station that only supports half-duplex operation.

[0558] As an embodiment, the second node device B00 is one of a test device, a test equipment, and a test instrument.

[0559] As an embodiment, the second transmitter B01 includes the attached Figure 4 At least one of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476.

[0560] As an embodiment, the second transmitter B01 includes the attached Figure 4 At least the first five of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476.

[0561] As an embodiment, the second transmitter B01 includes the attached Figure 4 At least the first four of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476.

[0562] As an embodiment, the second transmitter B01 includes the attached Figure 4 At least the first three of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476.

[0563] As an embodiment, the second transmitter B01 includes the attached Figure 4 At least the first two of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476.

[0564] As an embodiment, the second receiver B02 includes the attached Figure 4 At least one of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470, the controller / processor 475 and the memory 476.

[0565] As an embodiment, the second receiver B02 includes the attached Figure 4 At least the first five of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller / processor 475 and the memory 476.

[0566] As an embodiment, the second receiver B02 includes the attached Figure 4 At least the first four of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller / processor 475 and the memory 476.

[0567] As an embodiment, the second receiver B02 includes the attached Figure 4 At least the first three of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller / processor 475 and the memory 476.

[0568] As an embodiment, the second receiver B02 includes the attached Figure 4 At least the first two of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470, the controller / processor 475 and the memory 476.

[0569] As an embodiment, the second transmitter B01 sends uplink and downlink TDD configuration signaling; the second receiver B02 receives a first PUSCH in a valid PUSCH opportunity; wherein, for any PUSCH opportunity, the validity or not is related to whether the conditions in a first condition set are met, and when all conditions in the first condition set are met, the any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0570] As an embodiment, the first condition is that any one of the PUSCH opportunities is in the first category of symbols.

[0571] As an embodiment, the first condition is that the start of any PUSCH opportunity is at least N later than the nearest symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap Related to the subcarrier spacing.

[0572] As an embodiment, the second receiver B02 receives a first PRACH; wherein the first PUSCH is received after the first PRACH.

[0573] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon.

[0574] As an embodiment, whether one of the conditions in the first condition set is satisfied depends on the SS / PBCH block.

[0575] As an embodiment, any one of the PUSCH opportunities occupies time-frequency resources and is associated with a DMRS resource.

[0576] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, transportation tools, vehicles, RSUs, wireless sensors, Internet cards, Internet of Things terminals, RFID (Radio Frequency Identification, Radio Frequency Identification Technology) terminals, NB-IoT (Narrow Band Internet of Things, Narrow Band Internet of Things) terminals, MTC (Machine Type Communication, Machine Type Communication) terminals, eMTC (enhancedMTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, small cell base stations, home base stations, relay base stations, eNB (evolved Node B), gNB, TRP, GNSS (Global Navigation Satellite System), relay satellites, satellite base stations, aerial base stations, RSU, drones, test equipment, such as wireless communication equipment such as transceivers or signaling testers that simulate some functions of base stations.

[0577] It should be understood by those skilled in the art that the present invention may be implemented in other specified forms without departing from its core or essential features. Therefore, the embodiments disclosed herein should be considered illustrative rather than restrictive in any way. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within their equivalent meanings and regions are considered to be included therein.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives uplink and downlink TDD configuration signaling; A first transmitter sends a first PUSCH in a valid PUSCH opportunity; Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

2. The first node according to claim 1, characterized in that: The first condition is that any one of the PUSCH opportunities is in the first type of symbols.

3. The first node according to claim 1, characterized in that: The first condition is that the start of any PUSCH opportunity is at least N later than the nearest symbol that does not belong to the first category of symbols and is indicated as a downlink symbol by the uplink and downlink TDD configuration signaling. gap symbols, the N gap Related to the subcarrier spacing.

4. The first node according to any one of claims 1 to 3, characterized in that: include: The first transmitter sends a first PRACH; The first PUSCH is sent after the first PRACH.

5. The first node according to any one of claims 1 to 4, characterized in that: The uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon.

6. The first node according to any one of claims 1 to 5, characterized in that: Whether one of the conditions in the first set of conditions is satisfied depends on the SS / PBCH block.

7. The first node according to any one of claims 1 to 6, characterized in that: Any PUSCH opportunity occupies time-frequency resources and is associated with one DMRS resource.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends uplink and downlink TDD configuration signaling; A second receiver receives a first PUSCH in a valid PUSCH opportunity; Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

9. A method in a first node for wireless communication, characterized in that: include: Receiving uplink and downlink TDD configuration signaling; Send the first PUSCH in a valid PUSCH opportunity; Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

10. A method in a second node for wireless communication, characterized in that: include: Send uplink and downlink TDD configuration signaling; Receiving a first PUSCH in a valid PUSCH opportunity; Among them, for any PUSCH opportunity, its validity is related to whether the conditions in the first condition set are met. When all conditions in the first condition set are met, any PUSCH opportunity is valid; the first condition set includes a first condition, and whether the first condition is met depends on a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

Images