Method and apparatus related to PUSCH in node used for wireless communication

Abstract

The invention discloses a method and an apparatus related to a PUSCH in a node used for wireless communication. The first receiver is used for receiving first signaling, and the first signaling is used for indicating time domain resources allocated to the first PUSCH; the first transmitter is used for transmitting the first PUSCH; wherein whether transform precoding is enabled for the first PUSCH is a configuration following a first parameter or a configuration following a second parameter depending on a symbol type of at least one symbol allocated to the first PUSCH; the symbol type at least comprises full duplex and non-full duplex, and the first parameter and the second parameter are respectively two configuration parameters of transform precoding for Msg3 transmission.

Description

Technical Field

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

[0002] In existing NR (New Radio) systems, spectrum resources are statically divided into FDD (Frequency Division Duplex) and TDD (Time Division Duplex) spectrum. For TDD spectrum, both base stations and user equipment (UE) operate in half-duplex mode. This half-duplex mode avoids self-interference and mitigates the impact of cross-link interference (CLI), but it also leads to reduced resource utilization and increased latency. To address these issues, supporting flexible duplex modes or variable link directions (uplink, downlink, or flexible) in TDD or FDD spectrum is a possible solution. The 3rd Generation Partnership Project (3GPP) has agreed to conduct research on duplex technologies, specifically sub-band non-overlapping full-duplex (SBFD) mode for gNBs (NR Node Bs). Optimizing system design accordingly is a key component of this research.

[0003] PUSCH (Physical Uplink Shared CHannel) transmission is an important aspect in wireless communications. Summary of the Invention

[0004] How to optimize the transmission performance of PUSCH is a key issue that needs to be considered in system design; this application discloses a solution to the above problem. It should be noted that this application can be applicable 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, 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, and scenarios using more flexible 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 this application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.

[0005] Where 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 first signaling, where the first signaling indicates time domain resources allocated to a first PUSCH;

[0008] sending the first PUSCH;

[0009] Among them, whether the first PUSCH enables transform precoding according to the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission.

[0010] As an embodiment, the problem to be solved by the present application includes: how to enhance the configuration of the PUSCH transmission waveform (with or without transform precoding enabled OFDM) in a system configured with full-duplex symbols.

[0011] As an embodiment, the problem to be solved by the present application includes: how to determine whether to enable transform precoding for the first PUSCH.

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

[0013] As an embodiment, the benefits of the above method include: improving configuration flexibility.

[0014] As an embodiment, the advantages of the above method include: good compatibility with existing 3GPP protocols and small workload for standardization.

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

[0016] When at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0017] As an embodiment, the advantages of the above method include: high configuration flexibility.

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

[0019] When at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when all symbols allocated to the first PUSCH are non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

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

[0021] The first information element is an information element used to configure UE-specific PUSCH parameters corresponding to the first PUSCH. The name of the first information element includes PUSCH-Config; the parameter transformPrecoder is not configured in the first information element.

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

[0023] The first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH.

[0024] As an embodiment, in combination with the above features, when the UE-specific (UE specific) configuration transform precoding PUSCH parameters are not configured (thereby saving configuration signaling overhead): according to the scheme disclosed in the present application, the UE can determine which transform precoding configuration parameters for Msg3 transmission to apply to the PUSCH other than the DCI-scheduled PUSCH for random access based on the symbol type of the allocated symbol; such a feature can make the transmission of the PUSCH other than the DCI-scheduled PUSCH for random access more adapted to the system configuration on the corresponding type of symbol, thereby improving the transmission performance of the PUSCH other than the DCI-scheduled PUSCH for random access.

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

[0026] The first PUSCH is a PUSCH with configured grant (aPUSCH with configured grant).

[0027] As an embodiment, in combination with the above features, when the configuration transformation precoding parameters for uplink transmission without dynamic grant are not configured (thereby saving configuration signaling overhead): according to the scheme disclosed in the present application, the UE can determine which configuration parameters for the transformation precoding of Msg3 transmission to apply to the configuration-granted PUSCH based on the symbol type of the allocated symbol; such a feature can make the transmission of the configuration-granted PUSCH more adaptable to the system configuration on the corresponding type of symbol, thereby improving the transmission performance of the configuration-granted PUSCH.

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

[0029] The first PUSCH is a configured granted PUSCH, and the second information element is an information element used to configure parameters corresponding to the first PUSCH; the second information element is used to configure uplink transmission without dynamic grant (uplink transmission without dynamic grant), and the name of the second information element includes ConfiguredGrantConfig; in the second information element, the parameter transformPrecoder is not configured.

[0030] As an embodiment, in combination with the above features, when the configuration transformation precoding parameters for uplink transmission without dynamic grant are not configured (thereby saving configuration signaling overhead): according to the scheme disclosed in the present application, the UE can determine which configuration parameters for the transformation precoding of Msg3 transmission to apply to the configuration-granted PUSCH based on the symbol type of the allocated symbol; such a feature can make the transmission of the configuration-granted PUSCH more adaptable to the system configuration on the corresponding type of symbol, thereby improving the transmission performance of the configuration-granted PUSCH.

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

[0032] The symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

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

[0034] The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

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

[0036] Sending first signaling, where the first signaling indicates time domain resources allocated to a first PUSCH;

[0037] receiving the first PUSCH;

[0038] Among them, whether the first PUSCH enables transform precoding according to the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission.

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

[0040] When at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

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

[0042] When at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when all symbols allocated to the first PUSCH are non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

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

[0044] The first information element is an information element used to configure UE-specific PUSCH parameters corresponding to the first PUSCH. The name of the first information element includes PUSCH-Config; the parameter transformPrecoder is not configured in the first information element.

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

[0046] The first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH.

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

[0048] The first PUSCH is a PUSCH with configured grant (aPUSCH with configured grant).

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

[0050] The first PUSCH is a configured granted PUSCH, and the second information element is an information element used to configure parameters corresponding to the first PUSCH; the second information element is used to configure uplink transmission without dynamic grant (uplink transmission without dynamic grant), and the name of the second information element includes ConfiguredGrantConfig; in the second information element, the parameter transformPrecoder is not configured.

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

[0052] The symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

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

[0054] The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

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

[0056] A first receiver receives first signaling, where the first signaling indicates time domain resources allocated to a first PUSCH;

[0057] A first transmitter transmits the first PUSCH;

[0058] Among them, whether the first PUSCH enables transform precoding according to the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission.

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

[0060] A second transmitter sends a first signaling, where the first signaling indicates a time domain resource allocated to a first PUSCH;

[0061] a second receiver, receiving the first PUSCH;

[0062] Among them, whether the first PUSCH enables transform precoding according to the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0068] Figure 5 shows a signal transmission flow chart according to an embodiment of the present application;

[0069] Figure 6 A schematic diagram illustrating whether transform precoding is enabled for a first PUSCH and whether the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH according to one embodiment of the present application;

[0070] Figure 7 A schematic diagram illustrating a full-duplex symbol and a non-full-duplex symbol according to an embodiment of the present application is shown;

[0071] Figure 8 A structural block diagram of a processing device in a first node device according to an embodiment of the present application is shown;

[0072] Figure 9 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

[0073] The technical solution of the present application will be further described in detail below with reference to 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.

[0074] Example 1

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

[0076] In embodiment 1, the first node in the present application receives a first signaling in step 101; and sends a first PUSCH in step 102.

[0077] In embodiment 1, the first signaling indicates the time domain resources allocated to the first PUSCH; whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission, respectively.

[0078] As an embodiment, the first signaling includes downlink control information.

[0079] As an embodiment, the first signaling is physical layer signaling.

[0080] As an embodiment, the first signaling is in DCI (Downlink control information) format.

[0081] As an embodiment, the benefits of the above method include: scheduling using the DCI format has a small delay.

[0082] As an embodiment, the first signaling is a DCI format other than DCI format 0_0 (DCI format 0_0).

[0083] As an embodiment, the first signaling has a DCI format other than DCI format 0_0.

[0084] As an embodiment, the first signaling is a DCI format for scheduling the first PUSCH.

[0085] As an embodiment, the first signaling includes an uplink grant (UL grant).

[0086] As an embodiment, the first signaling dynamically schedules the first PUSCH.

[0087] As an embodiment, the first signaling semi-persistently schedules the first PUSCH.

[0088] As an embodiment, the first signaling is RRC signaling.

[0089] As an embodiment, the first signaling is the information element configuredGrantConfig.

[0090] As an embodiment, the benefits of the above method include: high reliability of signaling transmission.

[0091] As an embodiment, the first signaling indicates the time domain resources allocated to the first PUSCH, including: a field in the first signaling indicates the time domain resources allocated to the first PUSCH.

[0092] As an embodiment, the time domain resources allocated to the first PUSCH include multiple symbols.

[0093] As an embodiment, the sending of the first PUSCH (Physical Uplink Shared CHannel) includes: sending a signal on the first PUSCH.

[0094] As an embodiment, the sending of the first PUSCH includes: sending at least one of a transport block (Transport Block(s)) or a CSI (Channel State Information) report (CSIreport(s)) on the first PUSCH.

[0095] As an embodiment, the transform precoding may be used to generate an uplink transmission waveform.

[0096] As an embodiment, the transform precoding includes DFT (Discrete Fourier Transform) precoding (DFT-precoding).

[0097] As an embodiment, the transform precoding is a precoding that performs DFT spreading.

[0098] As an embodiment, enabling transform precoding for the first PUSCH includes: the transmission waveform of the first PUSCH is CP-OFDM that performs DFT expansion; not enabling transform precoding for the first PUSCH includes: the transmission waveform of the first PUSCH is CP-OFDM that does not perform DFT expansion.

[0099] As an embodiment, transform precoding is enabled for the first PUSCH, including: the transmission of the first PUSCH adopts a DFT-s-OFDM (DFT-spread OFDM) waveform; transform precoding is not enabled for the first PUSCH, including: the transmission of the first PUSCH adopts a CP-OFDM (Cyclic Prefix OFDM) waveform.

[0100] As an embodiment, enabling transform precoding for the first PUSCH includes: in the process of generating the transmission of the first PUSCH, transform precoding is performed; not enabling transform precoding for the first PUSCH includes: in the process of generating the transmission of the first PUSCH, transform precoding is not performed or the execution of transform precoding is skipped.

[0101] As an embodiment, the behavior of enabling / disabling transform precoding for the first PUSCH is a behavior of the first node.

[0102] As an embodiment, the first parameter is a higher layer parameter.

[0103] As an embodiment, the first parameter is an RRC layer parameter.

[0104] As an embodiment, the first parameter is in an information element (IE) for configuring random access parameters.

[0105] As an embodiment, the name of the first parameter includes msg3-transformPrecoder.

[0106] As an embodiment, the second parameter is a higher layer parameter.

[0107] As an embodiment, the second parameter is an RRC layer parameter.

[0108] As an embodiment, the second parameter is in the information element for configuring random access parameters.

[0109] As an embodiment, the name of the second parameter includes msg3-transformPrecoder.

[0110] As an embodiment, the Msg3 is a message including a C-RNTI MAC CE or CCCH SDU transmitted on an UL-SCH (Uplink Shared Channel).

[0111] As an embodiment, the Msg3 is a message used for contention resolution (Contention Resolution) in the random access process.

[0112] As an embodiment, the first parameter is not the second parameter.

[0113] As an embodiment, the first parameter and the second parameter are configured separately.

[0114] As an embodiment, the first parameter and the second parameter are in different information elements.

[0115] As an embodiment, the first parameter and the second parameter are respectively in different RACH-ConfigCommons.

[0116] As an embodiment, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH, including:

[0117] When at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0118] As an embodiment, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH, including:

[0119] When at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when all symbols allocated to the first PUSCH are non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0120] As a sub-embodiment of the above embodiment, when the first parameter is configured, the two candidate values ​​of the first parameter respectively indicate enabling transform precoding and not enabling transform precoding; and whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0121] The configuration of the second parameter is represented by a second field; when the second field exists, transform precoding is enabled for the first PUSCH; when the second field does not exist, transform precoding is not enabled for the first PUSCH.

[0122] As a sub-embodiment of the above embodiment, when the first parameter is configured, two candidate values ​​of the first parameter respectively indicate enabling transform precoding and disabling transform precoding; and whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including: for the first PUSCH, the first node shall (shall) consider (consider) whether to enable transform precoding based on the configured first parameter;

[0123] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0124] The configuration of the second parameter is represented by a second domain; when the second domain exists, the first node should consider enabling (enabling) transform precoding for the first PUSCH; when the second domain does not exist, the first node should consider not enabling (disabling) transform precoding for the first PUSCH.

[0125] As an embodiment, the second parameter is configured.

[0126] As an embodiment, in the present application: the symbols allocated to the first PUSCH are all symbols allocated to the first PUSCH in the time domain.

[0127] As an embodiment, the at least one symbol allocated to the first PUSCH is in the time domain.

[0128] As an embodiment, the time domain resource allocation field in the first signaling in the present application indicates the symbols allocated to the first PUSCH.

[0129] As an embodiment, a symbol is a symbol in the time domain.

[0130] As an embodiment, a symbol is an OFDM (Orthogonal Frequency Division Multiplex) symbol.

[0131] As an embodiment, a symbol is a symbol in a slot.

[0132] As an embodiment, all symbols allocated to the first PUSCH are full-duplex symbols, or all symbols allocated to the first PUSCH are non-full-duplex symbols.

[0133] As an embodiment, when the symbols allocated to the first PUSCH are full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0134] As an embodiment, when the symbols allocated to the first PUSCH are full-duplex symbols and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are full-duplex symbols and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when the symbols allocated to the first PUSCH are non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0135] As an embodiment, the symbol type of a full-duplex symbol is full-duplex, and the symbol type of a non-full-duplex symbol is non-full-duplex.

[0136] As an embodiment, there is no symbol that is both a full-duplex symbol and a non-full-duplex symbol.

[0137] As an embodiment, the symbol types only include full-duplex and non-full-duplex; when a symbol is not a full-duplex symbol, the symbol is a non-full-duplex symbol.

[0138] As an embodiment, the symbol type also includes symbol types other than full-duplex and non-full-duplex.

[0139] As an embodiment, when a symbol is indicated by uplink and downlink TDD configuration signaling as downlink and can be used for uplink transmission, the symbol is a full-duplex symbol.

[0140] As an embodiment, the benefits of the above method include: improving uplink performance.

[0141] As an embodiment, when a symbol is indicated as uplink by uplink / downlink TDD configuration signaling, the symbol is a non-full-duplex symbol.

[0142] As an embodiment, when a symbol is configured to be usable for full-duplex operation, the symbol is a full-duplex symbol; when a symbol is configured not to be used for full-duplex operation, the symbol is a non-full-duplex symbol.

[0143] As an embodiment, when a symbol is configured to be usable for full-duplex operation, the symbol is a full-duplex symbol; when a symbol is not configured to be usable for full-duplex operation, the symbol is a non-full-duplex symbol.

[0144] As an embodiment, the symbols used for the SBFD operation are symbols of a full-duplex symbol type, and are not symbols of a non-full-duplex symbol type.

[0145] As an embodiment, the symbols not used for the SBFD operation are symbols of a non-full-duplex symbol type, and are not symbols of a full-duplex symbol type.

[0146] As an embodiment, SBFD symbols are full-duplex symbols, and non-SBFD symbols are non-full-duplex symbols.

[0147] As an embodiment, when the first PUSCH is in a full-duplex time slot, the symbols allocated to the first PUSCH are all full-duplex symbols.

[0148] As a sub-embodiment of the above embodiment, all symbols in a full-duplex time slot are full-duplex symbols.

[0149] As an embodiment, when the first PUSCH is in a non-full-duplex time slot, the symbols allocated to the first PUSCH are all non-full-duplex symbols.

[0150] As a sub-embodiment of the above embodiment, all symbols in a non-full-duplex time slot are non-full-duplex symbols.

[0151] Example 2

[0152] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached diagram. Figure 2 As shown. Figure 2The network architecture 200 of a 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 a 5G System (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5G Core Network (5G Core Network) / EPC (Evolved Packet Core) 210, a Home Subscriber Server (HSS) / Unified Data Management (UDM) 220, and an Internet service 230. The 5GS / EPS may interconnect with other access networks, but for simplicity, these entities / interfaces are not shown. As shown, the 5GS / EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP (Transmitter Receiver Point), or some other appropriate terminology. Node 203 provides an access point to the 5GC / EPC 210 for UE 201. Examples of UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a Personal Digital Assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device.Those skilled in the art may also refer to UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other 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 MMEs / AMFs / SMFs 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 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 services 230. Internet services 230 include operator-specific Internet protocol services, which may specifically include Internet, intranet, IMS (IP Multimedia Subsystem) and packet switching services.

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

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

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

[0156] As an embodiment, the gNB203 is a macrocellular base station.

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

[0158] As an embodiment, the gNB203 is a picocell (PicoCell) base station.

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

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

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

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

[0163] Example 3

[0164] Example 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. 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 for the control plane 300 between a first communication node device (a UE, an RSU (Road Side Unit) in a gNB or V2X (Vehicle to Everything), a vehicle-mounted device or a vehicle-mounted communication module) and a second communication node device (a gNB, an RSU in a UE or V2X, a vehicle-mounted device or a vehicle-mounted communication module), or two UEs, is shown using 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 PHY 301 in this article. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the first and second communication node devices and the two UEs through PHY 301. 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 support for inter-zone mobility of the first communication node device between the second communication node devices. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) 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 and second communication node devices in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300, including the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355. However, the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping QoS (Quality of Service) flows and data radio bearers (DRBs) to support service diversity. 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) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

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

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

[0167] As an embodiment, the first signaling in the present application is generated in the RRC sublayer 306.

[0168] As an embodiment, the first signaling in this application is generated by the PHY301.

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

[0170] Example 4

[0171] Example 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.

[0172] The first communications 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 .

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

[0174] During transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 layer functionality. During 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 allocation of radio resources 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 performs coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, as well as mapping signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations 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, which is then provided to a different antenna 420.

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

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

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

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

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

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

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

[0182] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 450 device at least: receives first signaling, the first signaling indicating the time domain resources allocated to the first PUSCH; sends the first PUSCH; wherein whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission.

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

[0184] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates an action when executed by at least one processor, the action including: receiving a first signaling, the first signaling indicating the time domain resources allocated to the first PUSCH; sending the first PUSCH; wherein, whether the transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for the transform precoding for Msg3 transmission respectively.

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

[0186] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends first signaling, the first signaling indicating the time domain resources allocated to the first PUSCH; receives the first PUSCH; wherein whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission.

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

[0188] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates an action when executed by at least one processor, the action including: sending a first signaling, wherein the first signaling indicates the time domain resources allocated to the first PUSCH; receiving the first PUSCH; wherein, whether the transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for the transform precoding for Msg3 transmission respectively.

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

[0190] 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, the data source 467} is used to receive the first signaling in this application.

[0191] 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, the memory 476} is used to send the first signaling in this application.

[0192] 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, the data source 467} is used to receive the uplink and downlink TDD configuration signaling in this application.

[0193] 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, the memory 476} is used to send the uplink and downlink TDD configuration signaling in this application.

[0194] 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 this application.

[0195] 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 this application.

[0196] Example 5

[0197] Example 5 illustrates a signal transmission flow chart according to an embodiment of the present application, as shown in the attached figure. 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 via an air interface.

[0198] The first node U1 receives the first signaling in step S511 and sends the first PUSCH in step S512.

[0199] The second node U2 sends a first signaling in step S521; and receives a first PUSCH in step S522.

[0200] In embodiment 5, the first signaling indicates the time domain resources allocated to the first PUSCH; whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission respectively; when a symbol is indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by the uplink and downlink TDD configuration signaling, this symbol is a non-full-duplex symbol.

[0201] As a sub-embodiment of Example 5, when at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0202] As a sub-embodiment of Example 5, when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0203] As a sub-embodiment of Example 5, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated; when at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0204] As a sub-embodiment of Example 5, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0205] As an embodiment, the first signaling is a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH; the above features can be combined with embodiment 5 and its sub-embodiments.

[0206] As an embodiment, the first PUSCH is a configuration-granted PUSCH; the above features can be combined with embodiment 5 and its sub-embodiments.

[0207] As an embodiment, the first information element is an information element used to configure the UE-specific PUSCH parameters corresponding to the first PUSCH, the name of the first information element includes PUSCH-Config, and the parameter transformPrecoder is not configured in the first information element; the above features can be combined with embodiment 5 and its sub-embodiments.

[0208] As an embodiment, the first signaling is a DCI format other than DCI format 0_0, the first signaling schedules the first PUSCH, the first information element is an information element for configuring the UE-specific PUSCH parameters corresponding to the first PUSCH, the name of the first information element includes PUSCH-Config, and the parameter transformPrecoder is not configured in the first information element; the above features can be combined with embodiment 5 and its sub-embodiments.

[0209] As an embodiment, the second information element is an information element for configuring uplink transmission without dynamic grant (uplinktransmission without dynamic grant), the name of the second information element includes ConfiguredGrantConfig, the first PUSCH is a configured granted PUSCH (a PUSCH withconfigured grant), and the parameter transformPrecoder is not configured in the second information element; the above features can be combined with embodiment 5 and its sub-embodiments.

[0210] As an embodiment, the information elements mentioned in this application are all information elements of the RRC layer.

[0211] As an embodiment, the first signaling is RRC signaling, and the first signaling is the second information element.

[0212] As an embodiment, the first signaling is RRC signaling, and the second information element includes the first signaling.

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

[0214] As an embodiment, the second node U2 is the second node in this application.

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

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

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

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

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

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

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

[0222] As an embodiment, the second node U1 receives the uplink and downlink TDD configuration signaling.

[0223] As an embodiment, the second node U2 sends the uplink and downlink TDD configuration signaling.

[0224] As an embodiment, the uplink / downlink TDD configuration signaling is sent / received before the first signaling.

[0225] As an embodiment, when the first node obtains information corresponding to the configuration of the first parameter, the first parameter is configured.

[0226] As an embodiment, when the first node obtains information corresponding to the configuration of the second parameter, the second parameter is configured.

[0227] As an embodiment, the first parameter is configured, including: the configuration of the first parameter is provided by the second node to the first node.

[0228] As an embodiment, the first parameter is not configured, including: the second node does not provide the configuration of the first parameter to the first node.

[0229] As an embodiment, the second parameter is configured, including: the configuration of the second parameter is provided by the second node to the first node.

[0230] As an embodiment, the configuration of the first parameter is before the sending / receiving of the first signaling.

[0231] As an embodiment, the configuration of the second parameter occurs before the sending / receiving of the first signaling.

[0232] As an embodiment, the first parameter, the second parameter, and the uplink / downlink TDD configuration signaling may be sent / received in any order.

[0233] As an embodiment, for the second node: whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, or whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, is an assumption necessary for performing reception of the first PUSCH.

[0234] Example 6

[0235] Embodiment 6 illustrates a schematic diagram of whether the first PUSCH enables transform precoding according to an embodiment of the present application and whether the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH, as shown in the attached figure. Figure 6 shown.

[0236] In embodiment 6, the first node: first, determines the symbol type of the symbols allocated to the first PUSCH in step S601; if at least one symbol allocated to the first PUSCH is a full-duplex symbol, then considers whether to enable transform precoding for the first PUSCH according to the configuration of the first parameter in step S602; if the symbols allocated to the first PUSCH are all non-full-duplex symbols, then considers whether to enable transform precoding for the first PUSCH according to the configuration of the second parameter in step S603.

[0237] As an embodiment, the first node may adopt other methods different from the steps in Embodiment 6 to obtain the following effects:

[0238] When at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0239] As an embodiment, the first parameter is a configuration parameter for full-duplex symbols.

[0240] As an embodiment, the configuration of the first parameter is applicable to Msg3 transmission on full-duplex symbols.

[0241] As an embodiment, the configuration of the first parameter is applicable to the transmission of PUSCH on full-duplex symbols.

[0242] As an embodiment, the second parameter is a parameter for at least a non-full-duplex symbol.

[0243] As an embodiment, the configuration of the second parameter is at least applicable to Msg3 transmission on non-full-duplex symbols.

[0244] As an embodiment, the configuration of the second parameter is at least applicable to the transmission of PUSCH on non-full-duplex symbols.

[0245] As an embodiment, the first parameter indicates whether transform precoding is enabled, and the second parameter indicates whether transform precoding is enabled.

[0246] As an embodiment, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including: for the first PUSCH, the first node shall consider (consider) whether to enable transform precoding according to the configured first parameter;

[0247] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including: for the first PUSCH, the first node shall consider whether transform precoding is enabled according to the configured second parameter.

[0248] As an embodiment, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including:

[0249] The configuration of the first parameter is represented by a first field; when the first field exists, transform precoding is enabled for the first PUSCH; when the first field does not exist, transform precoding is not enabled for the first PUSCH;

[0250] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0251] The configuration of the second parameter is represented by a second field; when the second field exists, transform precoding is enabled for the first PUSCH; when the second field does not exist, transform precoding is not enabled for the first PUSCH.

[0252] As an embodiment, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including:

[0253] The configuration of the first parameter is represented by a first field; when the first field is present, the first node should consider enabling transform precoding for the first PUSCH; when the first field is not present, the first node should consider disabling transform precoding for the first PUSCH;

[0254] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0255] The configuration of the second parameter is represented by a second domain; when the second domain exists, the first node should consider enabling (enabling) transform precoding for the first PUSCH; when the second domain does not exist, the first node should consider not enabling (disabling) transform precoding for the first PUSCH.

[0256] As an embodiment, the benefits of the above method include: being conducive to reducing the signaling overhead for the first parameter.

[0257] As an embodiment, the first parameter is configured, and the two candidate values ​​of the first parameter respectively indicate enabling transform precoding and not enabling transform precoding; and whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0258] The configuration of the second parameter is represented by a second field; when the second field exists, transform precoding is enabled for the first PUSCH; when the second field does not exist, transform precoding is not enabled for the first PUSCH.

[0259] As an embodiment, the first parameter is configured, and the two candidate values ​​of the first parameter respectively indicate enabling transform precoding and not enabling transform precoding; whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including: for the first PUSCH, the first node shall (shall) consider (consider) whether to enable transform precoding according to the configured first parameter;

[0260] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0261] The configuration of the second parameter is represented by a second domain; when the second domain exists, the first node should consider enabling (enabling) transform precoding for the first PUSCH; when the second domain does not exist, the first node should consider not enabling (disabling) transform precoding for the first PUSCH.

[0262] As an embodiment, the configuration of the first parameter is represented by a first domain, including: the configuration of the first parameter is represented by whether the first domain exists or not.

[0263] As an embodiment, the configuration of the second parameter is represented by a second field, including: the configuration of the second parameter is represented by whether the second field exists or not.

[0264] As an embodiment, the first domain is a domain of the RRC layer.

[0265] As an embodiment, the first field is a field defined in an information element.

[0266] As an embodiment, the name of the first domain includes msg3-transformPrecoder.

[0267] As an embodiment, the first field is a field indicating that transform precoding is enabled for Msg3 transmission.

[0268] As an embodiment, the second domain is a domain of the RRC layer.

[0269] As an embodiment, the second field is a field defined in an information element.

[0270] As an embodiment, the name of the second domain includes msg3-transformPrecoder.

[0271] As an embodiment, the second field is a field indicating that transform precoding is enabled for Msg3 transmission.

[0272] As an embodiment, the configuration of the first parameter is represented by the first domain, and the configuration of the second parameter is represented by the second domain, and the first domain and the second domain are two different domains.

[0273] As an embodiment, the first parameter is configured and the second parameter is configured.

[0274] As an embodiment, for the second node: whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, or whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, is an assumption necessary for performing reception of the first PUSCH.

[0275] Example 7

[0276] Example 7 illustrates a schematic diagram of a full-duplex symbol and a non-full-duplex symbol according to an embodiment of the present application, as shown in the attached figure. Figure 7 shown.

[0277] In embodiment 7, when a symbol is indicated as downlink by uplink / downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink / downlink TDD configuration signaling, this symbol is a non-full-duplex symbol.

[0278] As an embodiment, the symbols indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission are full-duplex symbols.

[0279] As an embodiment, in combination with the above features, the method disclosed in the present application is conducive to improving the transmission performance of the PUSCH on the symbols indicated as downlink by the uplink and downlink TDD configuration signaling and available for uplink transmission.

[0280] As an embodiment, any full-duplex symbol is a symbol indicated as a downlink symbol by the uplink / downlink TDD configuration signaling and can be used for uplink transmission.

[0281] As an embodiment, there is a full-duplex symbol that is not indicated as a downlink symbol by the uplink / downlink TDD configuration signaling and can be used for uplink transmission.

[0282] As an embodiment, whether a flexible symbol is a full-duplex symbol is configurable.

[0283] As an embodiment, whether a flexible symbol is a full-duplex symbol is configured by RRC signaling.

[0284] As an embodiment, there is one flexible symbol configured as a full-duplex symbol.

[0285] As an embodiment, a symbol indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission is indicated as downlink by the uplink / downlink TDD configuration signaling, and this symbol can be used for uplink transmission.

[0286] As an embodiment, there is at least one symbol indicated as a downlink symbol by the uplink / downlink TDD configuration signaling that is not a full-duplex symbol.

[0287] As an embodiment, whether a symbol indicated as a downlink symbol by the uplink / downlink TDD configuration signaling is a full-duplex symbol is configurable.

[0288] As an embodiment, whether a downlink symbol indicated by the uplink and downlink TDD configuration signaling is a full-duplex symbol is configured by RRC signaling.

[0289] As an embodiment, the symbols indicated by the uplink / downlink TDD configuration signaling as downlink symbols and unavailable for uplink transmission are not full-duplex symbols.

[0290] As an embodiment, symbols indicated as uplink by the uplink / downlink TDD configuration signaling are not available for downlink transmission.

[0291] As an embodiment, the signal that can be used for uplink transmission includes: at least being used for PUSCH (Physical Uplink Shared CHannel, physical uplink shared channel) transmission (transmission(s)).

[0292] As an embodiment, combined with the above features, the method disclosed in this application is conducive to significantly improving the uplink capacity of the system.

[0293] As an embodiment, the signal that can be used for uplink transmission includes: at least signal that can be used for PUSCH and PUCCH (Physical Uplink Control CHannel, physical uplink control channel) transmission (transmission(s)).

[0294] As an embodiment, the signal that can be used for uplink transmission includes: at least one of PUSCH transmission, PUCCH transmission, PRACH (Physical Random Access CHannel) transmission (transmission(s)) and SRS (Sounding Reference Signal) transmission (transmission(s)).

[0295] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for at least two of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0296] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for at least three of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0297] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0298] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for UL-SCH (Uplink Shared Channel(s)) transmission.

[0299] As an embodiment, the uplink / downlink TDD (Time Division Duplex) configuration signaling is signaling indicating the link direction of the symbol.

[0300] As an embodiment, the uplink and downlink TDD configuration signaling indicates at least one symbol as downlink.

[0301] As an embodiment, the uplink and downlink TDD configuration signaling indicates at least one symbol as uplink.

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

[0303] As an embodiment, the benefits of the above method include: high reliability of signaling transmission.

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

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

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

[0307] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

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

[0309] As an embodiment, when a symbol is indicated as uplink / downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, this symbol is a symbol indicated as uplink / downlink by the uplink / downlink TDD configuration signaling.

[0310] Example 8

[0311] Example 8 illustrates a structural block diagram of a processing device in a first node device, as shown in the attached figure. Figure 8 As shown in the attached Figure 8 In the embodiment, the first node device processing apparatus A00 includes a first receiver A01 and a first transmitter A02.

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

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

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

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

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

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

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

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

[0320] As an embodiment, the first receiver A01 includes the attached Figure 4 At 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.

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

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

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

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

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

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

[0327] As an embodiment, the first receiver A01 receives a first signaling, and the first signaling indicates the time domain resources allocated to the first PUSCH; the first transmitter A02 sends the first PUSCH; wherein, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission respectively.

[0328] As an embodiment, when at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0329] As an embodiment, when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0330] As an embodiment, the first information element is an information element for configuring UE-specific PUSCH parameters corresponding to the first PUSCH, and the name of the first information element includes PUSCH-Config; the parameter transformPrecoder is not configured in the first information element.

[0331] As an embodiment, the first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH.

[0332] As an embodiment, the first PUSCH is a PUSCH with configured grant (aPUSCH with configured grant).

[0333] As an embodiment, the first PUSCH is a configured granted PUSCH, and the second information element is an information element used to configure parameters corresponding to the first PUSCH; the second information element is used to configure uplink transmission without dynamic grant (uplink transmission without dynamic grant), and the name of the second information element includes ConfiguredGrantConfig; in the second information element, the parameter transformPrecoder is not configured.

[0334] As an embodiment, the symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

[0335] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0336] As an embodiment, the first receiver A01 receives a first signaling, wherein the first signaling indicates a time domain resource allocated to the first PUSCH; the first transmitter A02 sends the first PUSCH; wherein, whether the first PUSCH enables transform precoding is in accordance with the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding transmitted for Msg3 respectively; when at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether the first PUSCH enables transform precoding is in accordance with the configuration of the first parameter. The configuration of the number, the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether to enable transform precoding for the first PUSCH follows the configuration of the second parameter; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is a non-full-duplex symbol; the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0337] As a sub-embodiment of the above embodiment, the first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH.

[0338] As a sub-embodiment of the above embodiment, the first PUSCH is a configuration-granted PUSCH.

[0339] As a sub-embodiment of the above embodiment, the determining whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including: for the first PUSCH, the first node shall consider (consider) whether transform precoding is enabled according to the configured first parameter;

[0340] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including: for the first PUSCH, the first node shall consider whether transform precoding is enabled according to the configured second parameter.

[0341] As a sub-embodiment of the foregoing embodiment, the enabling of transform precoding for the first PUSCH in accordance with the configuration of the first parameter includes:

[0342] The configuration of the first parameter is represented by a first field; when the first field exists, transform precoding is enabled for the first PUSCH; when the first field does not exist, transform precoding is not enabled for the first PUSCH;

[0343] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0344] The configuration of the second parameter is represented by a second field; when the second field exists, transform precoding is enabled for the first PUSCH; when the second field does not exist, transform precoding is not enabled for the first PUSCH.

[0345] As a sub-embodiment of the foregoing embodiment, the enabling of transform precoding for the first PUSCH in accordance with the configuration of the first parameter includes:

[0346] The configuration of the first parameter is represented by a first field; when the first field is present, the first node should consider enabling transform precoding for the first PUSCH; when the first field is not present, the first node should consider disabling transform precoding for the first PUSCH;

[0347] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0348] The configuration of the second parameter is represented by a second domain; when the second domain exists, the first node should consider enabling (enabling) transform precoding for the first PUSCH; when the second domain does not exist, the first node should consider not enabling (disabling) transform precoding for the first PUSCH.

[0349] As a sub-embodiment of the above embodiment, the first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH; and whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including: for the first PUSCH, the first node shall (shall) consider (consider) whether to enable transform precoding according to the configured first parameter;

[0350] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including: for the first PUSCH, the first node shall consider whether transform precoding is enabled according to the configured second parameter.

[0351] As a sub-embodiment of the above embodiment, the first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH; and whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including:

[0352] The configuration of the first parameter is represented by a first field; when the first field exists, transform precoding is enabled for the first PUSCH; when the first field does not exist, transform precoding is not enabled for the first PUSCH;

[0353] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0354] The configuration of the second parameter is represented by a second field; when the second field exists, transform precoding is enabled for the first PUSCH; when the second field does not exist, transform precoding is not enabled for the first PUSCH.

[0355] As a sub-embodiment of the above embodiment, the first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH; and whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including:

[0356] The configuration of the first parameter is represented by a first field; when the first field is present, the first node should consider enabling transform precoding for the first PUSCH; when the first field is not present, the first node should consider disabling transform precoding for the first PUSCH;

[0357] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0358] The configuration of the second parameter is represented by a second domain; when the second domain exists, the first node should consider enabling (enabling) transform precoding for the first PUSCH; when the second domain does not exist, the first node should consider not enabling (disabling) transform precoding for the first PUSCH.

[0359] As a sub-embodiment of the above embodiment, the first PUSCH is a configured granted PUSCH; and whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including: for the first PUSCH, the first node shall (shall) consider (consider) whether to enable transform precoding according to the configured first parameter;

[0360] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including: for the first PUSCH, the first node shall consider whether transform precoding is enabled according to the configured second parameter.

[0361] As a sub-embodiment of the above embodiment, the first PUSCH is a PUSCH for which grant is configured; and whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including:

[0362] The configuration of the first parameter is represented by a first field; when the first field exists, transform precoding is enabled for the first PUSCH; when the first field does not exist, transform precoding is not enabled for the first PUSCH;

[0363] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0364] The configuration of the second parameter is represented by a second field; when the second field exists, transform precoding is enabled for the first PUSCH; when the second field does not exist, transform precoding is not enabled for the first PUSCH.

[0365] As a sub-embodiment of the above embodiment, the first PUSCH is a PUSCH for which grant is configured; and whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, including:

[0366] The configuration of the first parameter is represented by a first field; when the first field is present, the first node should consider enabling transform precoding for the first PUSCH; when the first field is not present, the first node should consider disabling transform precoding for the first PUSCH;

[0367] Whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter, including:

[0368] The configuration of the second parameter is represented by a second domain; when the second domain exists, the first node should consider enabling (enabling) transform precoding for the first PUSCH; when the second domain does not exist, the first node should consider not enabling (disabling) transform precoding for the first PUSCH.

[0369] Example 9

[0370] Example 9 illustrates a structural block diagram of a processing device in a second node device, as shown in the attached figure. Figure 9 As shown in the attached Figure 9 In the embodiment, the second node device processing apparatus B00 includes a second transmitter B01 and a second receiver B02.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0386] As an embodiment, the second transmitter B01 sends a first signaling, wherein the first signaling indicates the time domain resources allocated to the first PUSCH; the second receiver B02 receives the first PUSCH; wherein, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission, respectively.

[0387] As an embodiment, when at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0388] As an embodiment, when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether transform precoding is enabled for the first PUSCH follows the configuration of the second parameter.

[0389] As an embodiment, the first information element is an information element for configuring UE-specific PUSCH parameters corresponding to the first PUSCH, and the name of the first information element includes PUSCH-Config; the parameter transformPrecoder is not configured in the first information element.

[0390] As an embodiment, the first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH.

[0391] As an embodiment, the first PUSCH is a PUSCH with configured grant (aPUSCH with configured grant).

[0392] As an embodiment, the first PUSCH is a configured granted PUSCH, and the second information element is an information element used to configure parameters corresponding to the first PUSCH; the second information element is used to configure uplink transmission without dynamic grant (uplink transmission without dynamic grant), and the name of the second information element includes ConfiguredGrantConfig; in the second information element, the parameter transformPrecoder is not configured.

[0393] As an embodiment, the symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

[0394] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0395] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software functional module. The present application is not limited to any specific form of combination of software and hardware. 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 vehicles, vehicles, RSUs, wireless sensors, internet cards, Internet of Things terminals, RFID (Radio Frequency Identification) terminals, NB-IoT (Narrow Band Internet of Things) terminals, MTC (Machine Type Communication) terminals, eMTC (enhancedMTC) 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, RSUs, drones, test equipment, such as transceivers or signaling testers that simulate some functions of base stations, and other wireless communication equipment.

[0396] Those skilled in the art will appreciate that the present invention may be implemented in other specific forms without departing from its core or essential characteristics. Therefore, the presently disclosed embodiments should be considered in all respects as illustrative and not restrictive. The scope of the invention is determined by the appended claims, not the foregoing description, and all modifications that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first signaling, where the first signaling indicates a time domain resource allocated to a first PUSCH; A first transmitter, sending the first PUSCH; Among them, whether to enable transform precoding for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission respectively.

2. The first node according to claim 1, characterized in that: When at least one symbol allocated to the first PUSCH is a full-duplex symbol, whether to enable transform precoding for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether to enable transform precoding for the first PUSCH follows the configuration of the second parameter.

3. The first node according to claim 1, characterized in that: When at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is configured, whether to enable transform precoding for the first PUSCH follows the configuration of the first parameter, and the first parameter is a configuration parameter for full-duplex symbols; when at least one symbol allocated to the first PUSCH is a full-duplex symbol and the first parameter is not configured, whether to enable transform precoding for the first PUSCH follows the configuration of the second parameter; when the symbols allocated to the first PUSCH are all non-full-duplex symbols, whether to enable transform precoding for the first PUSCH follows the configuration of the second parameter.

4. The first node according to any one of claims 1 to 3, characterized in that: The first information element is an information element used to configure UE-specific PUSCH parameters corresponding to the first PUSCH, and the name of the first information element includes PUSCH-Config; the parameter transformPrecoder is not configured in the first information element.

5. The first node according to any one of claims 1 to 4, characterized in that: The first signaling has a DCI format other than DCI format 0_0, and the first signaling schedules the first PUSCH.

6. The first node according to any one of claims 1 to 4, characterized in that: The first PUSCH is a PUSCH for which grant is configured.

7. The first node according to any one of claims 1 to 6, characterized in that: The symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, the symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, the symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, the symbol is a non-full-duplex symbol.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first signaling, where the first signaling indicates a time domain resource allocated to a first PUSCH; A second receiver, receiving the first PUSCH; Among them, whether to enable transform precoding for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission respectively.

9. A method in a first node for wireless communication, characterized in that: include: receiving first signaling, where the first signaling indicates time domain resources allocated to a first PUSCH; Sending the first PUSCH; Among them, whether to enable transform precoding for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission respectively.

10. A method in a second node for wireless communication, characterized in that: include: Sending first signaling, where the first signaling indicates time domain resources allocated to a first PUSCH; receiving the first PUSCH; Among them, whether to enable transform precoding for the first PUSCH follows the configuration of the first parameter or the configuration of the second parameter depends on the symbol type of at least one symbol allocated to the first PUSCH; the symbol type includes at least full-duplex and non-full-duplex, and the first parameter and the second parameter are two configuration parameters for transform precoding for Msg3 transmission respectively.

Images