Pusch-related method and apparatus for node in wireless communication

Abstract

Disclosed in the present application are a PUSCH-related method and apparatus for a node in wireless communication. A method for a terminal comprises: sending a first PUSCH and a second PUSCH, wherein a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, and the first orthogonal sequence is an orthogonal sequence of the PUSCHs; whether the second PUSCH can overlap with a first-type PUCCH depends on whether the first PUSCH overlaps with the first-type PUCCH; and the first-type PUCCH is a PUCCH for at least HARQ-ACK information.

Description

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

[0001] This application claims priority to the Chinese patent application No. 202411093114.5, filed on August 08, 2024, with the State Intellectual Property Office, and entitled “Method and apparatus related to PUSCH in a node for wireless communication”, the entire content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to a transmission method and apparatus in a wireless communication system, in particular, a transmission method and apparatus of a wireless signal in a wireless communication system supporting a cellular network. BACKGROUND

[0003] The existing NR (New Radio) system supports applying an orthogonal sequence to PUCCH (Physical Uplink Control CHannel) to realize multiplexing between users.

[0004] Applying an orthogonal sequence to PUSCH (Physical Uplink Shared CHannel) can further improve the multiplexing capability of the system, thereby significantly increasing the uplink capacity. SUMMARY

[0005] After introducing PUSCH transmission applying an orthogonal sequence, how to optimize the corresponding system design is an important problem to be considered; the present application discloses a solution to the above problem. It should be noted that the present application can be applied to various wireless communication scenarios, such as non-terrestrial networks (NTN) and terrestrial networks (TN), and achieve similar technical effects. In addition, adopting a unified solution in different scenarios (including but not limited to non-terrestrial networks and terrestrial networks) helps to reduce hardware complexity and cost, or improve performance. In the case of no conflict, any node in the embodiments of the present application and the features in the embodiments can be applied to any other node. In the case of no conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other.

[0006] In the case of need, the explanation of the terms in the present application can refer to the description of the specification protocols TS37 series and TS38 series of 3GPP.

[0007] The present application discloses a method in a first node for wireless communication, comprising:

[0008] transmitting the first PUSCH and the second PUSCH, the first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCHs;

[0009] wherein whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH being a PUCCH for at least HARQ-ACK information.

[0010] As an embodiment, the first node is a terminal.

[0011] As an embodiment, the problem to be solved by the present application comprises: how to constrain the overlap between a PUSCH to which an orthogonal sequence is applied and a PUCCH for at least HARQ-ACK information.

[0012] As an embodiment, the problem to be solved by the present application comprises: how to improve the uplink transmission performance in a scenario where the function of applying an orthogonal sequence to PUSCH transmission is enabled.

[0013] As an embodiment, the above method is beneficial to improving the uplink transmission performance by constraining the overlap between a PUSCH to which an orthogonal sequence is applied and a PUCCH for at least HARQ-ACK (Hybrid Automatic Repeat reQuest Acknowledgement) information.

[0014] As an embodiment, the above method has the benefits of: being beneficial to reducing the requirement for terminal capability and saving terminal cost.

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

[0016] When the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

[0017] As an embodiment, to ensure the orthogonality between PUSCH transmissions of different users to which the orthogonal sequence is applied, an effective UCI (Uplink Control Information) multiplexing scheme is to multiplex the UCI onto all PUSCHs to which the same orthogonal sequence is applied; for scenarios using this scheme, the benefits of the above method include: avoiding the situation that the HARQ-ACK information corresponding to different PUCCHs of the first type is multiplexed onto the same PUSCH due to the overlap between multiple PUSCHs to which the orthogonal sequence is applied and different PUCCHs of the first type, reducing the impact of the inconsistency between the two parties in some HARQ-ACK feedback on the performance of other uplink transmissions, and also reducing the complexity of system design.

[0018] As an embodiment, the benefits of the above method include: small amount of standardization work.

[0019] As an embodiment, in the above method, when the first PUSCH overlaps with a PUCCH of the first type, the second PUSCH cannot overlap with any PUCCH of the first type.

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

[0021] When a first set of conditions is met, the second PUSCH can overlap with the PUCCH of the first type; the first set of conditions includes that the first PUSCH does not overlap with the PUCCH of the first type.

[0022] As an embodiment, the benefits of the above method include: allowing one of the PUSCHs to which the orthogonal sequence is applied to overlap with the PUCCH of the first type, ensuring scheduling flexibility, and good compatibility with existing 3GPP protocols.

[0023] According to an aspect of the present application, the above method is characterized in that,

[0024] When the first PUSCH overlaps with the PUCCH of the first type, whether the second PUSCH can overlap with the PUCCH of the first type depends on the number of UCI bits corresponding to the PUCCH of the first type that overlaps with the first PUSCH.

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

[0026] The first PUSCH and the second PUSCH are 2 repetitions of the same PUSCH.

[0027] As an embodiment, in combination with the above features, the scheme disclosed in the present application can be applied to repeated transmission of PUSCH, and has good compatibility.

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

[0029] receiving a first DCI (Downlink Control Information), the first DCI scheduling the same PUSCH;

[0030] The first DCI includes indication information of the first orthogonal sequence.

[0031] As an embodiment, the above method has the advantages including: the first orthogonal sequence can be flexibly indicated.

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

[0033] The first PUSCH and the second PUSCH are in different slots respectively.

[0034] As an embodiment, the scheme disclosed in the present application is applicable to the scenario that the orthogonal sequence is applied to multiple PUSCHs (multiple repetitions of the same PUSCH) across slots, and has advantages in such a scenario.

[0035] The present application discloses a method in a second node for wireless communication, comprising:

[0036] receiving a first PUSCH and a second PUSCH, a first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCH;

[0037] The second PUSCH can or can not overlap with a first type of PUCCH depending on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information.

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

[0039] When the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

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

[0041] When the first PUSCH overlaps with the PUCCH of the first type, whether the second PUSCH can overlap with the PUCCH of the first type depends on a number of UCI bits corresponding to the PUCCH of the first type overlapping with the first PUSCH.

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

[0043] When a first set of conditions is met, the second PUSCH can overlap with the PUCCH of the first type; the first set of conditions includes that the first PUSCH does not overlap with the PUCCH of the first type.

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

[0045] The first PUSCH and the second PUSCH are 2 repetitions of a same PUSCH.

[0046] According to an aspect of the present application, the above method is characterized in that, comprising:

[0047] transmitting a first DCI, the first DCI scheduling the same PUSCH;

[0048] The first DCI includes indication information of the first orthogonal sequence.

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

[0050] The first PUSCH and the second PUSCH are in different slots respectively.

[0051] The present application discloses a first node for wireless communication, comprising:

[0052] a first transmitter, transmitting a first PUSCH and a second PUSCH, a first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCH;

[0053] Wherein, whether the second PUSCH can overlap with the PUCCH of the first type depends on whether the first PUSCH overlaps with the PUCCH of the first type; the PUCCH of the first type is a PUCCH for at least HARQ-ACK information.

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

[0055] a second receiver configured to receive the first PUSCH and the second PUSCH, the first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCHs;

[0056] wherein whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH being a PUCCH for at least HARQ-ACK information.

[0057] As one embodiment, the present application has the following advantages:

[0058] • the impact of the inconsistency between the two parties in the communication on the understanding of some HARQ-ACK feedback on the performance of other uplink transmissions is reduced;

[0059] • it is conducive to improving the performance of uplink transmission;

[0060] • it is conducive to saving terminal cost;

[0061] • good compatibility;

[0062] • taking into account the complexity of system design and scheduling flexibility. BRIEF DESCRIPTION OF DRAWINGS

[0063] Other characteristics, objects and advantages of the present application will become more apparent from the following detailed description of non-restrictive embodiments, made with reference to the attached drawings:

[0064] Fig. 1 shows a processing flowchart of a first node according to one embodiment of the present application;

[0065] Fig. 2 shows a schematic diagram of a network architecture according to one embodiment of the present application;

[0066] Fig. 3 shows a schematic diagram of a radio protocol architecture for the user plane and control plane according to one embodiment of the present application;

[0067] Fig. 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the present application;

[0068] Fig. 5 shows a signal transmission flowchart according to one embodiment of the present application;

[0069] Fig. 6 shows an explanatory diagram of whether the second PUSCH can overlap with the first type of PUCCH depending on whether the first PUSCH overlaps with the first type of PUCCH according to one embodiment of the present application;

[0070] Figure 7 shows an explanatory diagram of whether a second PUSCH can overlap with a first type of PUCCH depending on whether a first PUSCH overlaps with the first type of PUCCH according to an embodiment of the present application;

[0071] Figure 8 shows an explanatory diagram of a first PUSCH and a second PUSCH according to an embodiment of the present application;

[0072] Figure 9 shows an explanatory diagram of a first PUSCH and a second PUSCH according to an embodiment of the present application;

[0073] Figure 10 shows an explanatory diagram of a first orthogonal sequence applied to at least a first PUSCH and a second PUSCH according to an embodiment of the present application;

[0074] Figure 11 shows a structural block diagram of a processing device for use in a first node according to an embodiment of the present application;

[0075] Figure 12 shows a structural block diagram of a processing device for use in a second node according to an embodiment of the present application. DETAILED DESCRIPTION

[0076] The technical solutions of the present application will be described in further detail below with reference to the accompanying drawings. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily without conflict.

[0077] Embodiment 1

[0078] Embodiment 1 shows a processing flowchart of a first node according to an embodiment of the present application, as shown in Figure 1.

[0079] In Embodiment 1, the first node in the present application transmits a first PUSCH and a second PUSCH in step 101.

[0080] In Embodiment 1, a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCH; whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information.

[0081] As an embodiment, the first PUSCH and the second PUSCH are 2 repetitions of the same PUSCH.

[0082] As an embodiment, the multiple repetitions of the same PUSCH are sequentially ordered in the time domain.

[0083] As an embodiment, the multiple repetitions of the same PUSCH are in different slots respectively.

[0084] As an embodiment, the first node transmits a same transport block (TB) in the first PUSCH and the second PUSCH.

[0085] As an embodiment, the first PUSCH and the second PUSCH are 2 repetitions of the same PUSCH, and the first PUSCH and the second PUSCH are in different slots respectively.

[0086] As an embodiment, in combination with the above features, the scheme disclosed in the present application can be applied to PUSCH repetition Type A defined in 3GPP protocol, and has good compatibility.

[0087] As an embodiment, the first PUSCH and the second PUSCH are scheduled by the same DCI.

[0088] As an embodiment, the first orthogonal sequence is applied to the transmission of the same PUSCH.

[0089] As an embodiment, the first orthogonal sequence is applied to the multiple repetitions of the same PUSCH.

[0090] As an embodiment, the time-frequency resources for the first PUSCH and the second PUSCH are configurable.

[0091] As an embodiment, the first orthogonal sequence is configurable.

[0092] As an embodiment, the orthogonal sequence in the present application includes an orthogonal cover code.

[0093] As an embodiment, the orthogonal sequence of the PUSCH is an orthogonal sequence defined for PUSCH transmission.

[0094] As an embodiment, the orthogonal sequence of the PUSCH is an orthogonal sequence configured to be applied to PUSCH transmission.

[0095] As an embodiment, the orthogonal sequence of the PUSCH is an orthogonal sequence configured to be applied to multiple repetitions of PUSCH transmission.

[0096] As an embodiment, the first orthogonal sequence depends on a first configuration.

[0097] As an embodiment, the first configuration includes the configuration of the first orthogonal sequence.

[0098] As an embodiment, the first configuration indicates the first orthogonal sequence.

[0099] As an embodiment, the first configuration indicates a length of the first orthogonal sequence.

[0100] As an embodiment, the first configuration comprises an index of the first orthogonal sequence.

[0101] As an embodiment, the first configuration is a configuration of a physical layer.

[0102] As an embodiment, the benefit of the above method comprises: a delay of configuration taking effect is small.

[0103] As an embodiment, the first configuration is a configuration of higher layer parameter(s).

[0104] As an embodiment, the first configuration is a configuration of a Medium Access Control (MAC) layer.

[0105] As an embodiment, the first configuration is a configuration of a Radio Resource Control (RRC) layer.

[0106] As an embodiment, the benefit of the above method comprises: a reliability of configuration parameter transmission is high.

[0107] As an embodiment, the first configuration comprises a configuration of an orthogonal cover code for PUSCH.

[0108] As an embodiment, the first configuration comprises a configuration of a length of an orthogonal cover code for PUSCH.

[0109] As an embodiment, the first configuration comprises an indication of an index of an orthogonal cover code for PUSCH.

[0110] As an embodiment, whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH, which is equivalent to whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH.

[0111] As an embodiment, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH does not overlap with the first type of PUCCH.

[0112] As one embodiment, whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH, including:

[0113] As one embodiment, whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH, including:

[0114] whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

[0115] As one embodiment, whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH, including:

[0116] when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH; when a first set of conditions is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions includes that the first PUSCH does not overlap with the first type of PUCCH.

[0117] As one embodiment, whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH, including:

[0118] when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH does not overlap with the first type of PUCCH; when a first set of conditions is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions includes that the first PUSCH does not overlap with the first type of PUCCH.

[0119] As one embodiment, all the overlaps mentioned in this application refer to overlaps in time domain.

[0120] As one embodiment, in this application, the overlap between a PUSCH and a PUCCH means that the PUSCH and the PUCCH have overlap in time domain.

[0121] As an embodiment, in the present application, a PUSCH overlaps with a PUCCH means that the PUSCH and the PUCCH at least partially overlap in time domain.

[0122] As an embodiment, in the present application, a PUSCH does not overlap with a PUCCH means that the PUSCH and the PUCCH do not overlap in time domain.

[0123] As an embodiment, the first type of PUCCH is a PUCCH determined to be used for transmitting at least HARQ-ACK information before handling the overlap of PUCCH and PUSCH.

[0124] As an embodiment, the first type of PUCCH is a PUCCH determined to be used for transmitting at least the first of HARQ-ACK information and CSI report(s) before handling the overlap of PUCCH and PUSCH.

[0125] As an embodiment, the first type of PUCCH is used to carry at least HARQ-ACK information.

[0126] As an embodiment, the first type of PUCCH is a PUCCH including HARQ-ACK information.

[0127] As an embodiment, the first type of PUCCH is a PUCCH for at least HARQ-ACK information, including that when HARQ-ACK information would be transmitted in a PUCCH, the PUCCH is the first type of PUCCH.

[0128] As an embodiment, when the first PUSCH overlaps with the first type of PUCCH, the HARQ-ACK information corresponding to the PUCCH of the first type is multiplexed onto the second PUSCH is also multiplexed onto the first PUSCH.

[0129] As an embodiment, when the second PUSCH overlaps with the first type of PUCCH, the HARQ-ACK information corresponding to the PUCCH of the first type is multiplexed onto the second PUSCH is also multiplexed onto the first PUSCH.

[0130] As an embodiment, the above method has the advantage of facilitating maintaining the orthogonality obtained by the orthogonal sequences of PUSCH among multiple users including the first node.

[0131] As one embodiment, the number of the first type of PUCCHs overlapping with one PUSCH is no more than 1.

[0132] As one embodiment, different first type of PUCCHs can exist in different slots.

[0133] As one embodiment, in this application, the first type of PUCCH refers to a type of PUCCH, rather than a specific PUCCH.

[0134] Embodiment 2

[0135] Embodiment 2 illustrates a diagram of a network architecture according to one embodiment of the application, as shown in FIG. 2. FIG. 2 illustrates a network architecture 200 for a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system. The 5G NR / LTE / LTE-A network architecture 200 can be referred to as a 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5GC (5G Core Network, 5G Core Network) / EPC (Evolved Packet Core) 210, a HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and at least one of an Internet service 230. The 5GS / EPS can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the 5GS / EPS provides packet-switched services, however, one of skill 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 a node 203 and other nodes 204. The node 203 provides user and control plane protocol terminations toward the UE 201. The node 203 can be connected to the other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. The node 203 can also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (Transmitter Receiver Point), or some other suitable terminology. The node 203 provides an access point to the 5GC / EPC 210 for a UE 201.Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, Personal Digital Assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aerial vehicles, narrowband internet of things devices, machine type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional device. Those skilled in the art will also recognize that UE 201 can be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. Node 203 is connected to 5GC / EPC 210 over an S1 / NG interface. 5GC / EPC 210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. MME / AMF / SMF 211 is the control node that processes the signaling between UE 201 and 5GC / EPC 210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocal) packets are transferred through S-GW / UPF 212, which itself connects to P-GW / UPF 213. The P-GW provides UE IP address allocation as well as other functions. P-GW / UPF 213 connects to Internet services 230. Internet services 230 include operator corresponding Internet protocol services, which can include the Internet, an intranet, IMS (IP Multimedia Subsystem), and packet switching services, among others.

[0136] As one embodiment, the UE 201 corresponds to the first node in the present application.

[0137] As one embodiment, the gNB 203 corresponds to the second node in the present application.

[0138] As one embodiment, the UE 201 corresponds to the first node in the present application, and the gNB 203 corresponds to the second node in the present application.

[0139] As one embodiment, the gNB 203 is a Macro Cellular base station.

[0140] As one embodiment, the gNB 203 is a Micro Cell base station.

[0141] As one embodiment, the gNB 203 is a Pico Cell base station.

[0142] As one embodiment, the gNB 203 is a Femto Cell base station.

[0143] As one embodiment, the gNB 203 is a base station device supporting large latency difference.

[0144] As one embodiment, the gNB 203 is a flying platform device.

[0145] As one embodiment, the gNB 203 is a satellite device.

[0146] Embodiment 3

[0147] 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 3 shows the radio protocol architecture for the control plane 300 between a first communication node device (UE, gNB or RSU (Road Side Unit) in V2X (Vehicle to Everything), a vehicle mounted device or a vehicle mounted communication module) and a second communication node device (gNB, UE or RSU in V2X, a vehicle mounted device or a vehicle mounted communication module), or between two UEs, in three layers: Layer 1 (L1), Layer 2 (L2) and 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 the present document. Layer 2 (L2 layer) 305 is above the PHY 301 and is responsible for the link between the first communication node device and the second communication node device, as well as between two UEs, through the PHY 301. The L2 305 includes a MAC sublayer 302, a RLC (Radio Link Control) sublayer 303 and a PDCP (Packet Data Convergence Protocol) sublayer 304, which are terminated 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 ciphering the data packets, as well as providing header compression and decompression. 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. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 302 is also responsible for HARQ operations. The RRC sublayer 306 in L3 in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second communication node device and the first communication node device.The radio protocol architecture for the user plane 350 comprises Layer 1 (LI) and Layer 2 (L2) and is substantially the same as the corresponding layers and sub-layers in the control plane 300 for the first communication node device and the second communication node device for the physical layer 351, the PDCP sub-layer 354 in the L2 layer 355, the RLC sub-layer 353 in the L2 layer 355, and the MAC sub-layer 352 in the L2 layer 355, but the PDCP sub-layer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is the SDAP (Service Data Adaptation Protocol) sub-layer 356, which is responsible for mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support diverse traffic types. Although not illustrated, the first communication node device can have several upper layers above the L2 layer 355, including a network layer (e.g., IP (Internet Protocol) layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., a remote UE, a server, etc.).

[0148] As one embodiment, the wireless protocol architecture in FIG. 3 is applicable to the first node in the present application.

[0149] As one embodiment, the wireless protocol architecture in FIG. 3 is applicable to the second node in the present application.

[0150] As one embodiment, the first DCI in the present application is generated at the PHY 301.

[0151] As one embodiment, the first PUSCH in the present application is generated at the PHY 351.

[0152] As one embodiment, the second PUSCH in the present application is generated at the PHY 351.

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

[0154] Embodiment 4

[0155] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in FIG. 4. FIG. 4 is a block diagram of a first communication device 410 and a second communication device 450 that communicate with each other in an access network.

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

[0157] 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 multiple antenna transmit processor 457, a multiple antenna receive processor 458, a transmitter / receiver 454, and antennas 452.

[0158] In the transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements functionality of the L2 layer. In the transmission from the first communication device 410 to the second communication device 450, the controller / processor 475 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations for 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 multiple antenna transmit processor 471 implement various signal processing functions for the LI layer (i.e., physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, and mapping of coded and interleaved data onto various signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multiple antenna transmit processor 471 performs digital spatial pre-coding of the coded and modulated symbols, including codebook-based and non-codebook-based pre-coding, and beamforming processing, to generate one or more spatial streams. The transmit processor 416 then maps to each spatial stream to the subcarriers, multiplexes with reference signals (e.g., pilot) in the time and / or frequency domain, and then performs an inverse fast Fourier transform (IFFT) to generate a time-domain multicarrier symbol stream for the physical channel. The multiple antenna transmit processor 471 then performs transmit analog pre-coding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multiple antenna transmit processor 471 into a radio frequency stream, and then provides the radio frequency stream to the corresponding antenna 420.

[0159] In the transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives a signal through its respective antenna 452. Each receiver 454 recovers information modulated onto an RF carrier and converts the RF stream into a baseband multicarrier symbol stream, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various signal processing functions of the Ll layer. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receivers 454. The receive processor 456 converts the baseband multicarrier symbol stream from 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 signals and the reference signals are demultiplexed by the receive processor 456, where the reference signals will be used for channel estimation, and the data signals are recovered after multi-antenna detection in the multi-antenna receive processor 458 for any spatial streams destined for the second communication device 450. The symbols on each spatial stream are demodulated and recovered by the receive processor 456 and generate soft decisions. The receive processor 456 then decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communication device 410 on the physical channels. 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 can be associated with a memory 460 that stores program codes and data. The memory 460 can be referred to as a computer-readable medium. In the transmission from the first communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, 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 can also be provided to the L3 for L3 processing.

[0160] In the transmission from the second communication device 450 to the first communication device 410, at the second communication device 450, a data source 467 is used to provide upper layer data packets to a controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmit function described at the first communication device 410 in the transmission from the first communication device 410 to the second communication device 450, the controller / processor 459 implements header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations 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, channel coding processing, multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, and then the transmit processor 468 modulates the generated spatial streams into multi-carrier / single-carrier symbol streams, which are then provided to different antennas 452 via the transmitters 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency signal, and then provides the radio frequency signal to the antenna 452.

[0161] In the transmission from the second communication device 450 to the first communication device 410, the functions at the first communication device 410 are similar to the receive functions described at the second communication device 450 in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives a radio frequency signal through its respective antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna receive processor 472 and the receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 together implement the functions of the L1 layer. The controller / processor 475 implements the functions of the L2 layer. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer readable medium. In the transmission from the second communication device 450 to the first communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer data packets from the UE 450. Upper layer data packets from the controller / processor 475 can be provided to a core network.

[0162] As one embodiment, the first node in the present application comprises the second communication device 450, and the second node in the present application comprises the first communication device 410.

[0163] As one subembodiment of the above embodiment, the first node is a user equipment, and the second node is a relay node.

[0164] As one subembodiment of the above embodiment, the first node is a user equipment, and the second node is a base station equipment.

[0165] As one subembodiment of the above embodiment, the first node is a relay node, and the second node is a base station equipment.

[0166] As one embodiment, the second communication device 450 comprises at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the second communication device 450 to perform. The second communication device 450 is caused to perform: transmitting a first PUSCH and a second PUSCH, a first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCH; wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH being a PUCCH for at least HARQ-ACK information.

[0167] As one subembodiment of the above embodiment, the second communication device 450 corresponds to the first node in the present application.

[0168] As one embodiment, the second communication device 450 comprises a memory storing a program of computer readable instructions to produce actions when executed by at least one processor, the actions comprising: transmitting a first PUSCH and a second PUSCH, a first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCH; wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH being a PUCCH for at least HARQ-ACK information.

[0169] As one subembodiment of the above embodiment, the second communication device 450 corresponds to the first node in the present application.

[0170] As one embodiment, the first communication device 410 comprises: at least one processor and at least one memory including a computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the first communication device 410 to perform: receiving a first PUSCH and a second PUSCH, a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence is an orthogonal sequence of PUSCH; wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information.

[0171] As one sub-embodiment of the above-mentioned embodiment, the first communication device 410 corresponds to the second node in the present application.

[0172] As one embodiment, the first communication device 410 comprises: a memory storing a computer readable program of instructions which, when executed by at least one processor, causes actions comprising: receiving a first PUSCH and a second PUSCH, a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence is an orthogonal sequence of PUSCH; wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information.

[0173] As one sub-embodiment of the above-mentioned embodiment, the first communication device 410 corresponds to the second node in the present application.

[0174] As one embodiment, the first node in the present application comprises the second communication device 450.

[0175] As one embodiment, the second node in the present application comprises the first communication device 410.

[0176] As one embodiment, at least one of {the antenna 452, the receiver 454, the multi-antenna reception processor 458, the reception processor 456, the controller / processor 459, the memory 460, the data source 467} is used to receive the first DCI in the present application.

[0177] As an embodiment, at least one of {the antenna 420, the transmitter 418, the multi-antenna transmission processor 471, the transmission processor 416, the controller / processor 475, the memory 476} is configured to transmit the first DCI in the present application.

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

[0179] 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, the memory 476} is configured to receive the first PUSCH in the present application.

[0180] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468, the controller / processor 459, the memory 460, the data source 467} is configured to transmit the second PUSCH in the present application.

[0181] 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, the memory 476} is configured to receive the second PUSCH in the present application.

[0182] Embodiment 5

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

[0184] The first node U1 receives the first DCI in step S511; transmits the first PUSCH and the second PUSCH in step S512.

[0185] The second node U2 transmits the first DCI in step S521; receives the first PUSCH and the second PUSCH in step S522.

[0186] In Embodiment 5, a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence is an orthogonal sequence of PUSCH; whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information; the first PUSCH and the second PUSCH are 2 repetitions of a same PUSCH, the first DCI schedules the same PUSCH; the first PUSCH and the second PUSCH are in different slots respectively.

[0187] As a sub-embodiment of Embodiment 5, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

[0188] As a sub-embodiment of Embodiment 5, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH; when a first set of conditions is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions comprises that the first PUSCH does not overlap with the first type of PUCCH.

[0189] As a sub-embodiment of Embodiment 5, when the first PUSCH overlaps with the first type of PUCCH, whether the second PUSCH can overlap with the first type of PUCCH depends on a number of UCI bits corresponding to the first type of PUCCH that overlaps with the first PUSCH; when a first set of conditions is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions comprises that the first PUSCH does not overlap with the first type of PUCCH.

[0190] As an embodiment, the first node U1 is the first node in the present application.

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

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

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

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

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

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

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

[0198] As one embodiment, the air interface between the second node U2 and the first node U1 comprises a wireless interface between a relay device and a user equipment.

[0199] As one embodiment, the steps in the dashed box F1 are present.

[0200] As one embodiment, the first DCI is carried by a PDCCH (Physical Downlink Control Channel).

[0201] As one embodiment, the first DCI is one DCI format.

[0202] As one embodiment, the first DCI schedules multiple repetitions of the same PUSCH.

[0203] As one embodiment, the first DCI comprises indication information of the first orthogonal sequence.

[0204] As one embodiment, the first DCI comprises indication information of a length of the first orthogonal sequence.

[0205] As one embodiment, the steps in the dashed box F1 are not present.

[0206] Embodiment 6

[0207] Embodiment 6 illustrates an explanatory diagram of whether a second PUSCH can overlap with a first type of PUCCH depending on whether a first PUSCH overlaps with the first type of PUCCH according to one embodiment of the present application, as shown in FIG. 6.

[0208] In embodiment 6, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH; when a first set of conditions is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions comprises that the first PUSCH does not overlap with the first type of PUCCH.

[0209] As one embodiment, the second PUSCH cannot overlap with the first type of PUCCH includes that the first node does not expect the second PUSCH to overlap with the first type of PUCCH.

[0210] As one embodiment, the second PUSCH cannot overlap with the first type of PUCCH includes that the case of the second PUSCH overlapping with the first type of PUCCH is not allowed to occur.

[0211] As one embodiment, the second PUSCH does not overlap with the first type of PUCCH when the first PUSCH overlaps with the first type of PUCCH; the second PUSCH can overlap with the first type of PUCCH when a first set of conditions is satisfied; the first set of conditions includes that the first PUSCH does not overlap with the first type of PUCCH.

[0212] As one embodiment, the second PUSCH can overlap with the first type of PUCCH includes that the case of the second PUSCH overlapping with the first type of PUCCH is allowed to occur.

[0213] As one embodiment, the second PUSCH can overlap with the first type of PUCCH includes that the second PUSCH is configured or scheduled to overlap with or not overlap with the first type of PUCCH.

[0214] As one embodiment, the first set of conditions being satisfied means that all conditions in the first set of conditions are satisfied.

[0215] As one embodiment, the first set of conditions includes more than one condition.

[0216] As one embodiment, the first set of conditions includes only one condition.

[0217] As one embodiment, the first set of conditions includes only that the first PUSCH does not overlap with the first type of PUCCH.

[0218] As one embodiment, the first set of conditions includes more than that the first PUSCH does not overlap with the first type of PUCCH.

[0219] As one embodiment, one condition in the first set of conditions is that the first PUSCH does not overlap with the first type of PUCCH.

[0220] As one embodiment, one condition in the first set of conditions comprises: the first PUSCH does not overlap with the first type of PUCCH.

[0221] As one embodiment, the first orthogonal sequence is applied to K PUSCHs, the first PUSCH and the second PUSCH both belong to the K PUSCHs, and K is greater than 2; one condition in the first set of conditions is that none of the PUSCHs other than the second PUSCH among the K PUSCHs overlaps with the first type of PUCCH.

[0222] As one embodiment, when any of the PUSCHs other than the second PUSCH among the K PUSCHs overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

[0223] As one embodiment, when any of the PUSCHs other than the second PUSCH among the K PUSCHs overlaps with the first type of PUCCH, the second PUSCH does not overlap with the first type of PUCCH.

[0224] As one embodiment, one condition in the first set of conditions is that the second PUSCH does not carry an aperiodic CSI report.

[0225] Embodiment 7

[0226] Embodiment 7 illustrates a diagram illustrating whether the second PUSCH can overlap with the first type of PUCCH depending on whether the first PUSCH overlaps with the first type of PUCCH according to one embodiment of the present application, as shown in FIG. 7.

[0227] In embodiment 7, when the first PUSCH overlaps with the first type of PUCCH, whether the second PUSCH can overlap with the first type of PUCCH depends on the number of UCI bits corresponding to the first type of PUCCH that overlaps with the first PUSCH; when a first set of conditions is met, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions comprises that the first PUSCH does not overlap with the first type of PUCCH.

[0228] As one embodiment, the first PUSCH overlaps with one PUCCH of the first type; the second PUSCH cannot overlap with PUCCH of the first type when a number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is greater than a first threshold; the second PUSCH can overlap with PUCCH of the first type when the number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is not greater than the first threshold.

[0229] As one embodiment, the above method has the benefit of facilitating avoiding deterioration of transmission performance of UL-SCH (Uplink Shared Channel) transport block caused by multiplexing too many UCI bits into PUSCH.

[0230] As one embodiment, the first PUSCH overlaps with one PUCCH of the first type; the second PUSCH cannot overlap with PUCCH of the first type when a number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is not greater than a first threshold; the second PUSCH can overlap with PUCCH of the first type when the number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is greater than the first threshold.

[0231] As one embodiment, the second PUSCH cannot overlap with PUCCH of the first type comprises that the first node does not expect the second PUSCH to overlap with PUCCH of the first type.

[0232] As one embodiment, the second PUSCH cannot overlap with PUCCH of the first type comprises that the case of the second PUSCH overlapping with PUCCH of the first type is not allowed to occur.

[0233] As one embodiment, whether the second PUSCH can overlap with PUCCH of the first type depends on a number of UCI bits corresponding to the PUCCH of the first type overlapping with the first PUSCH is equivalent to whether the second PUSCH overlaps with PUCCH of the first type depends on a number of UCI bits corresponding to the PUCCH of the first type overlapping with the first PUSCH.

[0234] As one embodiment, the first PUSCH overlaps with one PUCCH of the first type; when the number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is greater than a first threshold, the second PUSCH does not overlap with PUCCH of the first type; when the number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is not greater than the first threshold, the second PUSCH can overlap with PUCCH of the first type.

[0235] As one embodiment, the benefit of the above method includes facilitating avoiding the deterioration of the transmission performance of UL-SCH transport blocks due to too many UCI bits being multiplexed to PUSCH.

[0236] As one embodiment, the first PUSCH overlaps with one PUCCH of the first type; when the number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is not greater than a first threshold, the second PUSCH does not overlap with PUCCH of the first type; when the number of UCI bits corresponding to the one PUCCH of the first type overlapping with the first PUSCH is greater than the first threshold, the second PUSCH can overlap with PUCCH of the first type.

[0237] As one embodiment, the second PUSCH can overlap with PUCCH of the first type includes that the case of the second PUSCH overlapping with PUCCH of the first type is allowed to occur.

[0238] As one embodiment, the second PUSCH can overlap with PUCCH of the first type includes that based on configuration or scheduling, the second PUSCH overlaps with or does not overlap with PUCCH of the first type.

[0239] As one embodiment, the number of UCI bits corresponding to one PUCCH is determined before handling the overlap of PUCCH and PUSCH.

[0240] As one embodiment, the number of UCI bits corresponding to one PUCCH is the number of bits of UCI carried by this PUCCH.

[0241] As one embodiment, the number of UCI bits corresponding to one PUCCH is the number of bits of UCI included in this PUCCH.

[0242] As an embodiment, when UCI would be transmitted in a PUCCH, the bits of the UCI are the UCI bits corresponding to the PUCCH.

[0243] As an embodiment, the first threshold is configurable.

[0244] As an embodiment, the first threshold is configured by RRC signaling.

[0245] As an embodiment, the first threshold is a positive integer.

[0246] As an embodiment, the first threshold is greater than 1.

[0247] As an embodiment, the first threshold is not greater than 1706.

[0248] As an embodiment, the first set of conditions is satisfied if all the conditions in the first set of conditions are satisfied.

[0249] As an embodiment, the first set of conditions includes more than one condition.

[0250] As an embodiment, the first set of conditions includes only one condition.

[0251] As an embodiment, the first set of conditions includes only that the first PUSCH does not overlap with the PUCCH of the first type.

[0252] As an embodiment, the first set of conditions includes more than that the first PUSCH does not overlap with the PUCCH of the first type.

[0253] As an embodiment, one of the conditions in the first set of conditions is that the first PUSCH does not overlap with the PUCCH of the first type.

[0254] As an embodiment, one of the conditions in the first set of conditions includes that the first PUSCH does not overlap with the PUCCH of the first type.

[0255] As an embodiment, the first orthogonal sequence is applied to K PUSCHs, the first PUSCH and the second PUSCH both belong to the K PUSCHs, and K is greater than 2; one of the conditions in the first set of conditions is that none of the PUSCHs other than the second PUSCH among the K PUSCHs overlaps with the PUCCH of the first type.

[0256] As an embodiment, one of the conditions in the first set of conditions is that the second PUSCH does not carry an aperiodic CSI report.

[0257] Embodiment 8

[0258] Embodiment 8 illustrates an illustrative diagram of a first PUSCH and a second PUSCH according to an embodiment of the present application, as shown in FIG. 8. In FIG. 8, a black filled square represents a PUSCH.

[0259] In embodiment 8, a same transport block is repeated in 4 PUSCHs, the 4 PUSCHs including the first PUSCH and the second PUSCH; the first orthogonal sequence is applied to the 4 PUSCHs.

[0260] As an embodiment, information bits carried by the 4 PUSCHs are the same.

[0261] As an embodiment, coded bits carried by the 4 PUSCHs are the same.

[0262] As an embodiment, the 4 PUSCHs are 4 repetitions of a same PUSCH.

[0263] As an embodiment, the 4 PUSCHs are sequentially ordered in time domain.

[0264] As an embodiment, the 4 PUSCHs are in different slots respectively.

[0265] As an embodiment, the first PUSCH and the second PUSCH are any 2 PUSCHs of the 4 PUSCHs.

[0266] As an embodiment, one DCI schedules the 4 PUSCHs.

[0267] Embodiment 9

[0268] Embodiment 9 illustrates an illustrative diagram of a first PUSCH and a second PUSCH according to an embodiment of the present application, as shown in FIG. 9. In FIG. 9, a black filled square represents a PUSCH.

[0269] In embodiment 9, a same transport block is repeated in 6 PUSCHs; the 6 PUSCHs are divided into 3 PUSCH groups, each PUSCH group including 2 PUSCHs, the first orthogonal sequence is applied to each PUSCH group; the first PUSCH and the second PUSCH belong to a same PUSCH group of the 3 PUSCH groups.

[0270] As an embodiment, the 6 PUSCHs carry the same information bits.

[0271] As an embodiment, the 6 PUSCHs carry the same coded bits.

[0272] As an embodiment, the 6 PUSCHs are 6 repetitions of one same PUSCH.

[0273] As an embodiment, the 6 PUSCHs are sequentially ordered in time domain.

[0274] As an embodiment, the 6 PUSCHs are in different slots respectively.

[0275] As an embodiment, one DCI schedules the 6 PUSCHs.

[0276] As an embodiment, the first PUSCH and the second PUSCH are two PUSCHs in any one of the 3 PUSCH groups.

[0277] Embodiment 10

[0278] Embodiment 10 illustrates a diagram showing application of a first orthogonal sequence to at least a first PUSCH and a second PUSCH according to an embodiment of the present application, as shown in FIG. 10. In FIG. 10, a black filled square represents a PUSCH.

[0279] In Embodiment 10, a1, a2,..., aKare K elements in the first orthogonal sequence; the a1, the a2,..., the aKare used for generating transmissions in PUSCH#1, PUSCH#2,..., PUSCH#K respectively; the first PUSCH and the second PUSCH are two of the K PUSCHs (i.e., the PUSCH#1, the PUSCH#2,..., the PUSCH#K). K K

[0280] In Embodiment 10, the first orthogonal sequence is applied to the K PUSCHs.

[0281] As an embodiment, the K PUSCHs are K repetitions of one same PUSCH.

[0282] As an embodiment, the target set of complex-valued symbols comprises complex-valued symbols generated after at least transform precoding of a plurality of modulation symbols, a i ​​The result of multiplying the complex-valued symbol in the target complex-valued symbol set is mapped to the time-frequency resources allocated to PUSCH#i and then transmitted; where i is any value in 1, 2, …, K.

[0283] As an embodiment, the target complex-valued symbol set includes complex-valued symbols generated after at least layer mapping and precoding of a plurality of modulation symbols, a i The result of multiplying the complex-valued symbol in the target complex-valued symbol set is mapped to the time-frequency resources allocated to PUSCH#i and then transmitted; where i is any value in 1, 2, …, K.

[0284] As an embodiment, the target complex-valued symbol set includes complex-valued symbols generated after at least layer mapping and precoding of a plurality of modulation symbols, a

[0285] As an embodiment, the target complex-valued symbol set includes complex-valued symbols generated after at least layer mapping and precoding of a plurality of modulation symbols, a

[0286] As an embodiment, the target complex-valued symbol set includes complex-valued symbols generated after at least layer mapping and precoding of a plurality of modulation symbols, a

[0287] As an embodiment, the target complex-valued symbol set includes complex-valued symbols generated after at least layer mapping and precoding of a plurality of modulation symbols, a i The result of multiplying the modulation symbol in the target modulation symbol set is mapped to the time-frequency resources allocated to PUSCH#i and then transmitted after at least transform precoding of the complex-valued symbol generated; where i is any value in 1, 2, …, K.

[0288] As an embodiment, the target modulation symbol set includes modulation symbols, a i The result of multiplying the modulation symbol in the target modulation symbol set is mapped to the time-frequency resources allocated to PUSCH#i and then transmitted after at least layer mapping and precoding of the complex-valued symbol generated; where i is any value in 1, 2, …, K.

[0289] As an embodiment, the target modulation symbol set includes modulation symbols, a

[0290] As an embodiment, the target modulation symbol set includes modulation symbols, a

[0291] As an embodiment, the target set of modulation symbols comprises modulation symbols generated by scrambling encoded bits of UL-SCH data.

[0292] As an embodiment, the K is equal to a length of the first orthogonal sequence.

[0293] As an embodiment, the first configuration indicates the K.

[0294] As an embodiment, the K is greater than 1.

[0295] As an embodiment, the K is equal to 2.

[0296] As an embodiment, the K is equal to 4.

[0297] As an embodiment, the K is not greater than 8.

[0298] As an embodiment, the benefit of the above method includes reducing system design complexity.

[0299] As an embodiment, the K is not greater than 1024.

[0300] As an embodiment, the a1, the a2,..., the a K The ordering position in the first orthogonal sequence is from front to back.

[0301] As an embodiment, the a1, the a2,..., the a K The ordering position in the first orthogonal sequence is from back to front.

[0302] As an embodiment, the K is equal to 2, and the first orthogonal sequence is [a1 a2].

[0303] As a sub-embodiment of the above embodiment, the a1 is +1, and the a2 is +1.

[0304] As a sub-embodiment of the above embodiment, the a1 is +1, and the a2 is -1.

[0305] As an embodiment, the K is equal to 4, and the first orthogonal sequence is [a1 a2 a3 a4].

[0306] As a sub-embodiment of the above embodiment, the a1 is +1, the a2 is +1, the a3 is +1, and the a4 is +1.

[0307] As a sub-embodiment of the above embodiment, the a1 is +1, the a2 is -1, the a3 is +1, and the a4 is -1.

[0308] As a sub-embodiment of the above-mentioned embodiment, the a1 is +1, the a2 is +1, the a3 is -1, and the a4 is -1.

[0309] As a sub-embodiment of the above-mentioned embodiment, the a1 is +1, the a2 is -1, the a3 is -1, and the a4 is +1.

[0310] As an embodiment, the first orthogonal sequence is a Walsh sequence.

[0311] As an embodiment, the first orthogonal sequence is an orthogonal DFT (Discrete Fourier Transform) code.

[0312] As an embodiment, the first PUSCH and the second PUSCH are any 2 PUSCHs of the K PUSCHs.

[0313] As an embodiment, one DCI schedules the K PUSCHs.

[0314] As an embodiment, the K PUSCHs are sequentially ordered in time domain.

[0315] As an embodiment, the K PUSCHs are in different slots respectively.

[0316] As an embodiment, the same transport block is repeatedly sent in multiple PUSCHs; the multiple PUSCHs are divided into more than one PUSCH group, the number of PUSCHs included in each PUSCH group is equal to K, the first orthogonal sequence is applied to each PUSCH group; the K PUSCHs are in the same PUSCH group of the more than one PUSCH group.

[0317] Embodiment 11

[0318] Embodiment 11 shows a structure block diagram of a processing apparatus in a first node according to an embodiment of the present application, as shown in FIG. 11. In FIG. 11, the processing apparatus A00 in the first node includes a first receiver A01 and a first transmitter A02.

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

[0320] As an embodiment, the first node is a relay node.

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

[0322] As an embodiment, the first node is a conventional user equipment.

[0323] As one embodiment, the first node is a UE in a NTN.

[0324] As one embodiment, the first node is a UE in a TN.

[0325] As one embodiment, the first receiver A01 includes at least one of the following: antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460, and data source 467 in FIG. 4 of this application.

[0326] As one embodiment, the first receiver A01 includes at least the first five of the following: antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460, and data source 467 in FIG. 4 of this application.

[0327] As one embodiment, the first receiver A01 includes at least the first four of the following: antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460, and data source 467 in FIG. 4 of this application.

[0328] As one embodiment, the first receiver A01 includes at least the first three of the following: antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460, and data source 467 in FIG. 4 of this application.

[0329] As one embodiment, the first receiver A01 includes at least the first two of the following: antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460, and data source 467 in FIG. 4 of this application.

[0330] As one embodiment, the first transmitter A02 includes at least one of the following: antenna 452, transmitter 454, multi-antenna transmission processor 457, transmission processor 468, controller / processor 459, memory 460, and data source 467 in FIG. 4 of this application.

[0331] As one embodiment, the first transmitter A02 includes at least the first five of the following: antenna 452, transmitter 454, multi-antenna transmission processor 457, transmission processor 468, controller / processor 459, memory 460, and data source 467 in FIG. 4 of this application.

[0332] As an embodiment, the first transmitter A02 comprises at least the first three of the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468, the controller / processor 459, the memory 460 and the data source 467 in Figure 4 of the present application.

[0333] As an embodiment, the first transmitter A02 comprises at least the first three of the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468, the controller / processor 459, the memory 460 and the data source 467 in Figure 4 of the present application.

[0334] As an embodiment, the first transmitter A02 comprises at least the first three of the antenna 452, the transmitter 454, the multi-antenna transmission processor 457, the transmission processor 468, the controller / processor 459, the memory 460 and the data source 467 in Figure 4 of the present application.

[0335] As an embodiment, the first transmitter A02, transmits the first PUSCH and the second PUSCH, a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence is an orthogonal sequence of PUSCH.

[0336] Wherein, whether the second PUSCH can overlap with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information.

[0337] As an embodiment, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

[0338] As an embodiment, when the first PUSCH overlaps with the first type of PUCCH, whether the second PUSCH can overlap with the first type of PUCCH depends on the number of UCI bits corresponding to the first type of PUCCH overlapping with the first PUSCH.

[0339] As an embodiment, when a first set of conditions is met, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions includes that the first PUSCH does not overlap with the first type of PUCCH.

[0340] As an embodiment, the first receiver A01 receives a first DCI, the first DCI at least schedules the first PUSCH and the second PUSCH.

[0341] As one embodiment, the first PUSCH and the second PUSCH are 2 repetitions of a same PUSCH.

[0342] As one embodiment, the first receiver A01 receives a first DCI, the first DCI scheduling the same PUSCH.

[0343] As one embodiment, the first DCI comprises indication information of the first orthogonal sequence.

[0344] As one embodiment, the first PUSCH and the second PUSCH are in different slots respectively.

[0345] As one embodiment, the first transmitter A02 transmits a first PUSCH and a second PUSCH, a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence is an orthogonal sequence of PUSCH.

[0346] wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information; when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH; the first PUSCH and the second PUSCH are in different slots respectively.

[0347] As one sub-embodiment of the above embodiment, the first PUSCH and the second PUSCH are 2 repetitions of a same PUSCH.

[0348] As one sub-embodiment of the above embodiment, when a first condition set is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first condition set comprises that the first PUSCH does not overlap with the first type of PUCCH.

[0349] As one sub-embodiment of the above embodiment, the first PUSCH and the second PUSCH are 2 repetitions of a same PUSCH; when a first condition set is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first condition set comprises that the first PUSCH does not overlap with the first type of PUCCH.

[0350] Embodiment 12

[0351] Embodiment 12 illustrates a structural block diagram of a processing apparatus in a second node according to an embodiment of the application, as shown in Figure 12. In Figure 12, the processing apparatus B00 in the second node includes a second transmitter B01 and a second receiver B02.

[0352] As one embodiment, the second node is a base station.

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

[0354] As one embodiment, the second node is a relay node.

[0355] As one embodiment, the second node is a base station of an NTN.

[0356] As one embodiment, the second node is a base station of a TN.

[0357] As one embodiment, the second node is one of a test apparatus, a test device, a test meter.

[0358] As one embodiment, the second transmitter B01 includes at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475 and the memory 476 in Figure 4 of the present application.

[0359] As one embodiment, the second transmitter B01 includes at least the first five of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475 and the memory 476 in Figure 4 of the present application.

[0360] As one embodiment, the second transmitter B01 includes at least the first four of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475 and the memory 476 in Figure 4 of the present application.

[0361] As one embodiment, the second transmitter B01 includes at least the first three of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475 and the memory 476 in Figure 4 of the present application.

[0362] As one embodiment, the second transmitter B01 includes at least the first two of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475 and the memory 476 in Figure 4 of the present application.

[0363] As an embodiment, the second receiver B02 comprises at least one of the following: antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in Figure 4 of the present application.

[0364] As an embodiment, the second receiver B02 comprises at least the first five of the following: antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in Figure 4 of the present application.

[0365] As an embodiment, the second receiver B02 comprises at least the first four of the following: antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in Figure 4 of the present application.

[0366] As an embodiment, the second receiver B02 comprises at least the first three of the following: antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in Figure 4 of the present application.

[0367] As an embodiment, the second receiver B02 comprises at least the first two of the following: antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in Figure 4 of the present application.

[0368] As an embodiment, the second receiver B02 receives a first PUSCH and a second PUSCH, a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence is an orthogonal sequence of PUSCH;

[0369] wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH is a PUCCH for at least HARQ-ACK information.

[0370] As an embodiment, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

[0371] As an embodiment, when the first PUSCH overlaps with the first type of PUCCH, whether the second PUSCH can overlap with the first type of PUCCH depends on a number of UCI bits corresponding to the first type of PUCCH that overlaps with the first PUSCH.

[0372] As one embodiment, the second PUSCH can overlap with the first type of PUCCH when a first set of conditions is satisfied; the first set of conditions includes that the first PUSCH does not overlap with the first type of PUCCH.

[0373] As one embodiment, the second transmitter B01 transmits a first DCI, the first DCI scheduling at least the first PUSCH and the second PUSCH.

[0374] As one embodiment, the first PUSCH and the second PUSCH are 2 repetitions of a same PUSCH.

[0375] As one embodiment, the second transmitter B01 transmits a first DCI, the first DCI scheduling the same PUSCH.

[0376] As one embodiment, the first DCI includes indication information of the first orthogonal sequence.

[0377] As one embodiment, the first PUSCH and the second PUSCH are in different slots respectively.

[0378] Those skilled in the art can understand that all or part of the steps in the foregoing method can be instructed by programs to related hardware, and the programs can be stored in a computer readable storage medium, such as a read-only memory, a hard disk, an optical disk or the like. Alternatively, all or part of the steps of the foregoing embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the foregoing embodiments can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in the present application include but are not limited to unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebook computers, vehicle-mounted communication devices, vehicles, vehicles, RSUs, wireless sensors, network cards, Internet of Things terminals, RFID (Radio Frequency Identification) terminals, NB-IoT (Narrow Band Internet of Things) terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base station or system device in the present application includes but is not limited to macro cellular base stations, micro cellular base stations, small cellular base stations, home base stations, relay base stations, eNB (evolved Node B), gNB, TRP, GNSS (Global Navigation Satellite System), relay satellites, satellite base stations, air base stations, RSUs, unmanned aerial vehicles, test equipment such as wireless communication devices that simulate part of the functions of base stations or signaling testers, and the like.

[0379] Those skilled in the art will understand that the application can be implemented by other specified forms without departing from the core or essential characteristics thereof. Therefore, the presently disclosed embodiments should in no way be considered as descriptive rather than limiting. The scope of the application is determined by the appended claims rather than the preceding description, and all modifications within the equivalent meaning and range of the claims are considered to be included therein.

Claims

1. A method for a terminal, characterized by, comprising: transmitting a first PUSCH and a second PUSCH, a first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCHs; wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH being a PUCCH for at least HARQ-ACK information.

2. The method of claim 1, wherein, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

3. The method of claim 1, wherein, when the first PUSCH overlaps with the first type of PUCCH, whether the second PUSCH can overlap with the first type of PUCCH depends on a number of UCI bits corresponding to the first type of the PUCCH that overlaps with the first PUSCH.

4. The method according to any one of claims 1 to 3, characterized in that, when a first set of conditions is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first set of conditions comprising that the first PUSCH does not overlap with the first type of PUCCH.

5. The method according to any one of claims 1 to 4, characterized in that, the first PUSCH and the second PUSCH are 2 repetitions of a same PUSCH.

6. The method of claim 5, wherein, comprising: receiving a first DCI, the first DCI scheduling the same PUSCH; wherein the first DCI comprises indication information of the first orthogonal sequence.

7. The method according to any one of claims 1 to 6, characterized in that, the first PUSCH and the second PUSCH are in different slots, respectively. 8.A terminal, comprising: one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is configured to store computer program codes, the computer program codes comprising computer instructions, and the one or more processors are configured to invoke the computer instructions to cause the terminal to perform the method according to any one of claims 1 to 7.

9. A method for a base station, characterized by, comprising: receiving a first PUSCH and a second PUSCH, a first orthogonal sequence being applied to at least the first PUSCH and the second PUSCH, the first orthogonal sequence being an orthogonal sequence of PUSCHs; wherein whether the second PUSCH can overlap with a first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH; the first type of PUCCH being a PUCCH for at least HARQ-ACK information.

10. The method of claim 9, wherein, when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

11. The method of claim 9, wherein, when the first PUSCH overlaps with the first type of PUCCH, whether the second PUSCH can overlap with the first type of PUCCH depends on a number of UCI bits corresponding to the first type of the PUCCH that overlaps with the first PUSCH.

12. The method according to any one of claims 9 to 11, characterized in that, The second PUSCH can overlap with the first type of PUCCH when a first set of conditions is met; the first set of conditions includes that the first PUSCH does not overlap with the first type of PUCCH.

13. The method according to any one of claims 9 to 12, characterized in that, The first PUSCH and the second PUSCH are 2-time repetitions of a same PUSCH.

14. The method of claim 13, wherein, Comprising: transmitting a first DCI, the first DCI scheduling the same PUSCH; wherein the first DCI includes indication information of the first orthogonal sequence.

15. The method according to any one of claims 9 to 14, characterized in that, The first PUSCH and the second PUSCH are in different slots respectively. 16.A base station, comprising: the base station comprises one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is configured to store computer program codes, the computer program codes comprising computer instructions, and the one or more processors are configured to invoke the computer instructions to enable the base station to perform the method according to any one of claims 9 to 15.

Images