Method and apparatus relating to pusch in node for wireless communication

Abstract

The invention discloses a method and an apparatus related to a PUSCH in a node for wireless communication. A method for a terminal is 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 the PUSCH; wherein whether the second PUSCH can be overlapped with the PUCCH of the first type or not depends on whether the first PUSCH is overlapped with the PUCCH of the first type or not; the PUCCH of the first type is a PUCCH for at least HARQ-ACK information.

Description

Technical Field

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

[0002] The existing NR (New Radio) system supports the use of orthogonal sequences for PUCCH (Physical Uplink Control Channel) to achieve multiplexing between users.

[0003] Applying orthogonal sequences to PUSCH (Physical Uplink Shared Channel) can further improve the multiplexing ability of the system, thereby significantly increasing the uplink capacity. Summary of the Invention

[0004] After introducing PUSCH transmission with orthogonal sequences, how to optimize the corresponding system design is an important issue 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 Network (NTN) and Terrestrial Network (TN), and achieve similar technical effects. In addition, adopting a unified solution for different scenarios (including but not limited to non-terrestrial network and terrestrial network) helps to reduce hardware complexity and cost, or improve performance. Without conflict, the embodiments and features in any node of the present application can be applied to any other node. Without conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily.

[0005] If necessary, the interpretation of the terms in the present application can refer to the descriptions in the 3GPP specification protocols TS37 series and TS38 series.

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

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

[0008] Among them, 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.

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

[0010] As an embodiment, the problems to be solved by this application include: how to restrict the overlap between the PUSCH applying orthogonal sequences and the PUCCH for at least HARQ-ACK information.

[0011] As an embodiment, the problems to be solved by this application include: in a scenario where the function of applying orthogonal sequences to PUSCH transmission is enabled, how to improve the uplink transmission performance.

[0012] As an embodiment, the above method is beneficial to improving the uplink transmission performance by restricting the overlap between the PUSCH applying orthogonal sequences and the PUCCH for at least HARQ-ACK (Hybrid Automatic Repeat reQuest Acknowledgement) information.

[0013] As an embodiment, the benefits of the above method include: being beneficial to reducing the requirements for terminal capabilities and saving terminal costs.

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

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

[0016] As an embodiment, to ensure the orthogonality between the PUSCH transmissions of different users applying orthogonal sequences, an effective UCI (Uplink Control Information) multiplexing scheme is to multiplex UCI onto all PUSCHs to which the same orthogonal sequence is applied; for a scenario adopting this scheme, the benefits of the above method include: avoiding the HARQ-ACK information corresponding to different PUCCHs of the first type being multiplexed onto the same PUSCH due to multiple PUSCHs applying orthogonal sequences overlapping with different PUCCHs of the first type respectively, reducing the impact of inconsistent understanding of some HARQ-ACK feedback between the communication parties on other uplink transmission performances, and at the same time reducing the complexity of system design.

[0017] As an example, the advantages of the above method include: small standardized workload.

[0018] As an example, in the above method, when the first PUSCH overlaps with one of the first type of PUCCH, the second PUSCH cannot overlap with any of the first type of PUCCH.

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

[0020] When the first condition set is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first condition set includes that the first PUSCH does not overlap with the first type of PUCCH.

[0021] As an example, the advantages of the above method include: allowing one of the PUSCHs applying orthogonal sequences to overlap with the first type of PUCCH, ensuring scheduling flexibility and good compatibility with existing 3GPP protocols.

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

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

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

[0025] The first PUSCH and the second PUSCH are two repetitions of the same PUSCH.

[0026] As an example, combining the above features, the solution disclosed in the present application can be applied to the repeated transmission of PUSCH and has good compatibility.

[0027] According to one aspect of the present application, the above method is characterized by including:

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

[0029] Wherein, the first DCI includes indication information of the first orthogonal sequence.

[0030] As an example, the advantages of the above method include: being able to flexibly indicate the first orthogonal sequence.

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

[0032] the first PUSCH and the second PUSCH are in different time slots respectively.

[0033] As an embodiment, the solution disclosed in the present application is applicable to the scenario where orthogonal sequences are applied to multiple PUSCHs (multiple repetitions of the same PUSCH) across time slots, and has advantages in such a scenario.

[0034] The present application discloses a method in a second node for wireless communication, characterized by including:

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

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

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

[0038] when the first PUSCH overlaps with the first type of PUCCH, the second PUSCH cannot overlap with the first type of PUCCH.

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

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

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

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

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

[0044] The first PUSCH and the second PUSCH are two repetitions of the same PUSCH.

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

[0046] Sending a first DCI, where the first DCI schedules the same PUSCH;

[0047] Wherein, the first DCI includes indication information of the first orthogonal sequence.

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

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

[0050] The present application discloses a first node for wireless communication, which is characterized in that it includes:

[0051] A first transmitter, which sends a first PUSCH and a second PUSCH, and a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, and the first orthogonal sequence is the orthogonal sequence of the PUSCH;

[0052] 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 the PUCCH for at least HARQ-ACK information.

[0053] The present application discloses a second node for wireless communication, which is characterized in that it includes:

[0054] A second receiver, which receives a first PUSCH and a second PUSCH, and a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, and the first orthogonal sequence is the orthogonal sequence of the PUSCH;

[0055] 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 the PUCCH for at least HARQ-ACK information.

[0056] As an embodiment, the present application has the following advantages:

[0057] · Alleviates the impact of inconsistent understanding of some HARQ-ACK feedback between the communication parties on other uplink transmission performances;

[0058] · Facilitates improving the uplink transmission performance;

[0059] · Facilitate terminal cost savings;

[0060] · Good compatibility;

[0061] · Take into account both the complexity of system design and scheduling flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0063] Figure 1 Shows a processing flow chart of a first node according to an embodiment of the present application;

[0064] Figure 2 Shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0065] Figure 3 Shows a schematic diagram of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0066] Figure 4 Shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

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

[0068] Figure 6 Shows an explanatory schematic diagram of whether a second PUSCH can overlap with a first - type PUCCH depending on whether a first PUSCH overlaps with the first - type PUCCH;

[0069] Figure 7 Shows an explanatory schematic diagram of whether a second PUSCH can overlap with a first - type PUCCH depending on whether a first PUSCH overlaps with the first - type PUCCH;

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

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

[0072] Figure 10 Shows an explanatory schematic diagram of a first orthogonal sequence applied to at least a first PUSCH and a second PUSCH;

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

[0074] Figure 12 shows a structural block diagram of a processing device in a second node according to an embodiment of the present application. Detailed implementation manners

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

[0076] Example 1

[0077] Embodiment 1 exemplifies a processing flow chart of a first node according to an embodiment of the present application, as shown in the accompanying Figure 1 drawing.

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

[0079] In Embodiment 1, 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 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.

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

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

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

[0083] As an embodiment, the first node repeatedly sends the same transport block (TB) in the first PUSCH and the second PUSCH.

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

[0085] As an embodiment, combining the above features, the solution disclosed in the present application can be applied to PUSCH repetition Type A defined in the 3GPP protocol, with good compatibility.

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

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

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

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

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

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

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

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

[0094] As an embodiment, the orthogonal sequence of PUSCH is the orthogonal sequence configured for application to multiple repeated transmissions of PUSCH.

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

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

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

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

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

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

[0101] As an embodiment, the advantages of the above method include: small delay for configuration to take effect.

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

[0103] As an embodiment, the first configuration is a configuration of the MAC layer.

[0104] As an embodiment, the first configuration is a configuration of the RRC layer.

[0105] As an embodiment, the advantages of the above method include: high reliability of configuration parameter transmission.

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

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

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

[0109] As an 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, which is equivalent to that whether the second PUSCH overlaps with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH.

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

[0111] As an embodiment, whether the second PUSCH can overlap with the first type of PUCCH is related to whether the first PUSCH overlaps with the first type of PUCCH.

[0112] As an 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] Whether the second PUSCH can overlap with the first type of PUCCH is related to 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.

[0114] As an 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:

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

[0116] As an embodiment, whether the second PUSCH overlaps with the first type of PUCCH depends on whether the first PUSCH overlaps with the first type of PUCCH, including:

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

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

[0119] As an embodiment, in this application, a PUSCH overlapping with a PUCCH means that this PUSCH and this PUCCH overlap in the time domain.

[0120] As an embodiment, in this application, a PUSCH overlapping with a PUCCH means that this PUSCH and this PUCCH at least partially overlap in the time domain.

[0121] As an embodiment, in this application, a PUSCH not overlapping with a PUCCH means that this PUSCH and this PUCCH do not overlap in the time domain.

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

[0123] As an example, the first type of PUCCH is determined to be the PUCCH to be used for transmitting at least the former of HARQ-ACK information and CSI (Channel State Information) report(s) before processing the overlap between PUCCH and PUSCH.

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

[0125] As an example, the first type of PUCCH is the PUCCH including HARQ-ACK information.

[0126] As an example, the first type of PUCCH is the PUCCH for at least HARQ-ACK information, including: when HARQ-ACK information would be transmitted in a PUCCH, this PUCCH is the first type of PUCCH.

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

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

[0129] As an example, the advantages of the above method include: being conducive to maintaining the orthogonality obtained by the orthogonal sequences of PUSCH among multiple users including the first node.

[0130] As an example, the number of the first type of PUCCH overlapping with a PUSCH is not greater than 1.

[0131] As an example, different first types of PUCCH may exist in different time slots.

[0132] As an example, in this application, the first type of PUCCH refers to a class of PUCCH, rather than a specific PUCCH.

[0133] Example 2

[0134] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the appended Figure 2 figure. The appended Figure 2Describes the network architecture 200 of the 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 5GS (5G System) / EPS (Evolved Packet System) or some other suitable term. The 5GS / EPS 200 includes at least one of UE (User Equipment) 201, RAN (Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet service 230. The 5GS / EPS can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the 5GS / EPS provides packet-switched services. However, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks that provide 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 the Xn interface (e.g., backhaul) / X2 interface. Node 203 can 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 suitable term. Node 203 provides an access point for UE 201 to the 5GC / EPC 210. Examples of UE 201 include cellular phones, smartphones, 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, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional devices.A person skilled in the art may also refer to the UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. The node 203 is connected to the 5GC / EPC 210 via the S1 / NG interface. The 5GC / EPC 210 includes an MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMFs 214, an S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Date Network Gateway) / UPF 213. The MME / AMF / SMF 211 is a control node that processes the signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through the S-GW / UPF 212, which is itself connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet service 230. The Internet service 230 includes carrier-corresponding Internet protocol services, which may specifically include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet switching services.

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

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

[0137] As an 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.

[0138] As an embodiment, the gNB 203 is a macrocellular base station.

[0139] As an example, the gNB 203 is a Micro Cell base station.

[0140] As an example, the gNB 203 is a Pico Cell base station.

[0141] As an example, the gNB 203 is a Femtocell.

[0142] As an example, the gNB 203 is a base station device that supports large delay differences.

[0143] As an example, the gNB 203 is an airborne platform device.

[0144] As an example, the gNB 203 is a satellite device.

[0145] Example 3

[0146] Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in the appendix Figure 3 as follows. Figure 3 It is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. Figure 3Show the radio protocol architecture of the control plane 300 for the first communication node device (UE, gNB or RSU (Road Side Unit), in-vehicle device or in-vehicle communication module in V2X (Vehicle to Everything)) and the second communication node device (gNB, UE or RSU in V2X, in-vehicle device or in-vehicle communication module), or between two UEs, using 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 PHY301 in this document. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first communication node device and the second communication node device and between two UEs through PHY301. L2 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303 and a PDCP (Packet Data Convergence Protocol) sublayer 304, and these sublayers 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 handover support for 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 disordered reception due to HARQ (Hybrid Automatic Repeat Qequest). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in L3 in the control plane 300 is responsible for obtaining radio resources (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 of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). For the radio protocol architecture in the user plane 350 for the first communication node device and the second communication node device, 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 are substantially the same as the corresponding layers and sub-layers in the control plane 300. However, the PDCP sub-layer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sub-layer 356. The SDAP sub-layer 356 is responsible for the mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support service diversity. Although not shown, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., an 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.).

[0147] As an example, the Figure 3 radio protocol architecture in

[0148] As an example, the Figure 3 radio protocol architecture in

[0149] As an example, the first DCI in this application is generated at the PHY301.

[0150] As an example, the first PUSCH in this application is generated at the PHY351.

[0151] As an example, the second PUSCH in this application is generated at the PHY351.

[0152] As an example, the upper layer in this application refers to the layer above the physical layer.

[0153] Example 4

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

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

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

[0157] In the transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the 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, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, and mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then uses the inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. Subsequently, the multi-antenna transmit processor 471 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 and then provides it to different antennas 420.

[0158] 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 signals through its respective antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 perform various signal processing functions of the L1 layer. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receivers 454. The receive processor 456 uses the Fast Fourier Transform (FFT) to convert the baseband multi-carrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 456, where the reference signal will be used for channel estimation, and the data signal recovers any spatial stream destined for the second communication device 450 after multi-antenna detection in the multi-antenna receive processor 458. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. Subsequently, the receive processor 456 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 channel. Subsequently, the upper layer data and control signals are provided to the controller / processor 459. The controller / processor 459 performs 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. 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, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. Subsequently, the upper layer data packets are provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing.

[0159] 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 at the first communication device 410 described in the transmission from the first communication device 410 to the second communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements L2 layer functions for the user plane and the control plane. The controller / processor 459 is also responsible for retransmitting lost packets and signaling to the first communication device 410. A transmit processor 468 performs modulation mapping and channel coding processing, and a multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Subsequently, the transmit processor 468 modulates the generated spatial streams into multi-carrier / single-carrier symbol streams, and after an analog precoding / beamforming operation in the multi-antenna transmit processor 457, provides them to different antennas 452 via a transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and then provides it to the antenna 452.

[0160] 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 at the second communication device 450 described in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 jointly implement the L1 layer functions. A controller / processor 475 implements the L2 layer functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as 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, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. The upper layer data packets from the controller / processor 475 may be provided to the core network.

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

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

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

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

[0165] 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 is at least configured to: send 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 the orthogonal sequence of the 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.

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

[0167] As an embodiment, the second communication device 450 includes: a memory storing a computer - readable instruction program, the computer - readable instruction program generating actions when executed by at least one processor, the actions including: sending 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 the orthogonal sequence of the 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.

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

[0169] As an example, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The first communication device 410 is at least configured to: receive 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 the 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.

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

[0171] As an example, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: 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 the 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.

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

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

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

[0175] As an example, 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 this application.

[0176] 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 used to transmit the first DCI in the present application.

[0177] 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 used to transmit the first PUSCH in the present application.

[0178] 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 used to receive the first PUSCH in the present application.

[0179] 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 used to transmit the second PUSCH in the present application.

[0180] 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 used to receive the second PUSCH in the present application.

[0181] Example 5

[0182] Embodiment 5 exemplifies a signal transmission flowchart according to an embodiment of the present application, as shown in the appendix Figure 5 as shown. In the appendix Figure 5 the first node U1 and the second node U2 communicate through an air interface. In particular, in the appendix Figure 5 the steps in the dashed box F1 are optional.

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

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

[0185] In Embodiment 5, the first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, and the first orthogonal sequence is the orthogonal sequence of the PUSCH; 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 the PUCCH for at least HARQ-ACK information; the first PUSCH and the second PUSCH are two repetitions of the same PUSCH, and the first DCI schedules the same PUSCH; the first PUSCH and the second PUSCH are in different time slots respectively.

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

[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; 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.

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

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

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

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

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

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

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

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

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

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

[0198] As an embodiment, the steps in the dashed box F1 exist.

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

[0200] As an embodiment, the first DCI is a DCI format.

[0201] As an embodiment, the first DCI schedules multiple repetitions of the same PUSCH.

[0202] As an embodiment, the first DCI includes indication information of the first orthogonal sequence.

[0203] As an embodiment, the first DCI includes indication information of the length of the first orthogonal sequence.

[0204] As an embodiment, the steps in the dashed box F1 do not exist.

[0205] Example 6

[0206] Embodiment 6 exemplifies a schematic diagram showing 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, as shown in the attached Figure 6 figure.

[0207] 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 the first condition set is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first condition set includes that the first PUSCH does not overlap with the first type of PUCCH.

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

[0209] As an embodiment, that the second PUSCH cannot overlap with the first type of PUCCH includes: the situation where the second PUSCH overlaps with the first type of PUCCH is not allowed to occur.

[0210] 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; when the first condition set is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first condition set includes that the first PUSCH does not overlap with the first type of PUCCH.

[0211] As an embodiment, that the second PUSCH can overlap with the first type of PUCCH includes: the situation where the second PUSCH overlaps with the first type of PUCCH is allowed to occur.

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

[0213] As an embodiment, that the first condition set is satisfied means that all conditions in the first condition set are satisfied.

[0214] As an embodiment, the first condition set includes more than one condition.

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

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

[0217] As an example, the first set of conditions includes more than just the first PUSCH not overlapping with the first type of PUCCH.

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

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

[0220] As an example, the first orthogonal sequence is applied to K PUSCHs, the first PUSCH and the second PUSCH both belong to the K PUSCHs, where K is greater than 2; one condition in the first set of conditions is that the PUSCHs among the K PUSCHs other than the second PUSCH do not overlap with the first type of PUCCH.

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

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

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

[0224] Example 7

[0225] Example 7 illustrates a schematic diagram showing whether the second PUSCH according to an embodiment of the present application can overlap with the first type of PUCCH depending on whether the first PUSCH overlaps with the first type of PUCCH, as shown in the appendix Figure 7 as shown.

[0226] 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 condition set is satisfied, the second PUSCH can overlap with the first type of PUCCH; the first condition set includes that the first PUSCH does not overlap with the first type of PUCCH.

[0227] As an 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 that overlaps with the first PUSCH is greater than a first threshold, the second PUSCH cannot overlap with the first type of PUCCH; when the number of UCI bits corresponding to the one PUCCH of the first type that overlaps with the first PUSCH is not greater than the first threshold, the second PUSCH can overlap with the first type of PUCCH.

[0228] As an embodiment, the advantages of the above method include: it is beneficial to avoid the deterioration of the transmission performance of the UL-SCH (Uplink Shared Channel) transport block caused by too many UCI bits being multiplexed onto the PUSCH.

[0229] As an 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 that overlaps with the first PUSCH is not greater than a first threshold, the second PUSCH cannot overlap with the first type of PUCCH; when the number of UCI bits corresponding to the one PUCCH of the first type that overlaps with the first PUSCH is greater than the first threshold, the second PUSCH can overlap with the first type of PUCCH.

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

[0231] As an embodiment, that the second PUSCH cannot overlap with the first type of PUCCH includes: the situation where the second PUSCH overlaps with the first type of PUCCH is not allowed to occur.

[0232] As an example, 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. That is to say, whether the second PUSCH overlaps 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.

[0233] As an example, 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 that overlaps with the first PUSCH is greater than a first threshold, the second PUSCH does not overlap with the first type of PUCCH; when the number of UCI bits corresponding to the one PUCCH of the first type that overlaps with the first PUSCH is not greater than the first threshold, the second PUSCH can overlap with the first type of PUCCH.

[0234] As an example, the advantages of the above method include: it is beneficial to avoid the deterioration of the transmission performance of the UL-SCH transport block caused by too many UCI bits being multiplexed onto the PUSCH.

[0235] As an example, 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 that overlaps with the first PUSCH is not greater than a first threshold, the second PUSCH does not overlap with the first type of PUCCH; when the number of UCI bits corresponding to the one PUCCH of the first type that overlaps with the first PUSCH is greater than the first threshold, the second PUSCH can overlap with the first type of PUCCH.

[0236] As an example, the second PUSCH can overlap with the first type of PUCCH, including: the situation where the second PUSCH overlaps with the first type of PUCCH is allowed to occur.

[0237] As an example, the second PUSCH can overlap with the first type of PUCCH, including: based on configuration or scheduling, the second PUSCH overlaps with or does not overlap with the first type of PUCCH.

[0238] As an example, the UCI bits corresponding to a PUCCH are the bits determined to send UCI on this PUCCH before processing the overlap between the PUCCH and the PUSCH.

[0239] As an example, the UCI bits corresponding to a PUCCH are the bits of the UCI carried by this PUCCH.

[0240] As an example, the UCI bits corresponding to a PUCCH are the bits of the UCI included in this PUCCH.

[0241] As an example, when UCI is to be sent in a PUCCH, the bits of the UCI are the UCI bits corresponding to this PUCCH.

[0242] As an example, the first threshold is configurable.

[0243] As an example, the first threshold is configured by RRC signaling.

[0244] As an example, the first threshold is a positive integer.

[0245] As an example, the first threshold is greater than 1.

[0246] As an example, the first threshold is not greater than 1706.

[0247] As an example, the satisfaction of the first set of conditions means that all conditions in the first set of conditions are satisfied.

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

[0249] As an example, the first set of conditions includes only one condition.

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

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

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

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

[0254] As an example, the first orthogonal sequence is applied to K PUSCHs, where 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 the PUSCHs among the K PUSCHs other than the second PUSCH do not overlap with the PUCCH of the first type.

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

[0256] Example 8

[0257] Embodiment 8 illustrates an explanatory schematic diagram of a first PUSCH and a second PUSCH according to an embodiment of the present application, as shown in the appendix Figure 8 as shown. In the appendix Figure 8 a gray-filled square represents a PUSCH.

[0258] In Embodiment 8, the same transport block is repeatedly transmitted in 4 PUSCHs, and the 4 PUSCHs include the first PUSCH and the second PUSCH; the first orthogonal sequence is applied to the 4 PUSCHs.

[0259] As an example, the information bits carried by the 4 PUSCHs are the same.

[0260] As an example, the coded bits carried by the 4 PUSCHs are the same.

[0261] As an example, the 4 PUSCHs are 4 repetitions of the same PUSCH.

[0262] As an example, the 4 PUSCHs are sorted in sequence in the time domain.

[0263] As an example, the 4 PUSCHs are in different time slots respectively.

[0264] As an example, the first PUSCH and the second PUSCH are any 2 PUSCHs among the 4 PUSCHs.

[0265] As an example, a DCI schedules the 4 PUSCHs.

[0266] Example 9

[0267] Embodiment 9 illustrates an explanatory schematic diagram of a first PUSCH and a second PUSCH according to an embodiment of the present application, as shown in the appendixFigure 9 As shown. In the appendix Figure 9 a gray-filled square represents a PUSCH.

[0268] In Embodiment 9, the same transport block is repeatedly transmitted in 6 PUSCHs; the 6 PUSCHs are divided into 3 PUSCH groups, each PUSCH group includes 2 PUSCHs, and the first orthogonal sequence is applied to each PUSCH group; the first PUSCH and the second PUSCH belong to the same PUSCH group among the 3 PUSCH groups.

[0269] As an embodiment, the information bits carried by the 6 PUSCHs are the same.

[0270] As an embodiment, the coded bits carried by the 6 PUSCHs are the same.

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

[0272] As an embodiment, the 6 PUSCHs are sorted in sequence in the time domain.

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

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

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

[0276] Example 10

[0277] Embodiment 10 exemplifies an illustrative schematic diagram of the application of the first orthogonal sequence according to an embodiment of the present application to at least the first PUSCH and the second PUSCH, as shown in the appendix Figure 10 As shown. In the appendix Figure 10 a gray-filled square represents a PUSCH.

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

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

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

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

[0282] As an embodiment, the target complex-valued symbol set includes complex-valued symbols generated by at least Layer mapping and Precoding of a plurality of modulation symbols, a i The result of multiplying with the complex-valued symbols in the target complex-valued symbol set is mapped into 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 plurality of modulation symbols are all modulation symbols generated for the same PUSCH.

[0284] As an embodiment, the plurality of modulation symbols include modulation symbols generated by scrambling the coded bits of a transport block.

[0285] As an embodiment, the plurality of modulation symbols include modulation symbols generated by scrambling the coded bits of UL-SCH data.

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

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

[0288] As an embodiment, the modulation symbols in the target modulation symbol set are all the modulation symbols generated for the same PUSCH.

[0289] As an embodiment, the target modulation symbol set includes the modulation symbols generated after scrambling the coded bits of a transport block.

[0290] As an embodiment, the target modulation symbol set includes the modulation symbols generated after scrambling the coded bits of UL-SCH data.

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

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

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

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

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

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

[0297] As an embodiment, the advantages of the above method include: reducing the system design complexity.

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

[0299] As an embodiment, a1, a2,..., a K The sorting positions in the first orthogonal sequence are from front to back.

[0300] As an embodiment, a1, a2,..., a K The sorting positions in the first orthogonal sequence are from back to front.

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

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

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

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

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

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

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

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

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

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

[0311] As an embodiment, the first PUSCH and the second PUSCH are any two PUSCHs among the K PUSCHs.

[0312] As an embodiment, a DCI schedules the K PUSCHs.

[0313] As an embodiment, the K PUSCHs are sorted in sequence in the time domain.

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

[0315] As an embodiment, the same transport block is repeatedly transmitted 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 among the more than one PUSCH groups.

[0316] Example 11

[0317] Embodiment 11 exemplifies a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in the appendix Figure 11 as shown. In the appendix Figure 11 , the processing device A00 in the first node includes a first receiver A01 and a first transmitter A02.

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

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

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

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

[0322] As an embodiment, the first node is a UE in NTN.

[0323] As an embodiment, the first node is a UE in TN.

[0324] As an embodiment, the first receiver A01 includes at least one of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 in the appendix of the present application Figure 4 .

[0325] As an embodiment, the first receiver A01 includes at least the first five of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 in the appendix of the present application Figure 4 .

[0326] As an embodiment, the first receiver A01 includes at least the first four of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 in the appendix of the present application Figure 4 .

[0327] As an embodiment, the first receiver A01 includes at least the first three of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 in the appendix of the present application Figure 4 .

[0328] As an embodiment, the first receiver A01 includes at least the first three of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 in the appendix of the present application Figure 4at least the first two of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 therein.

[0329] As an example, the first transmitter A02 includes the attachment of this application Figure 4 at least one of the antenna 452, the transmitter 454, the multi-antenna transmitting processor 457, the transmitting processor 468, the controller / processor 459, the memory 460, and the data source 467 therein.

[0330] As an example, the first transmitter A02 includes the attachment of this application Figure 4 at least the first five of the antenna 452, the transmitter 454, the multi-antenna transmitting processor 457, the transmitting processor 468, the controller / processor 459, the memory 460, and the data source 467 therein.

[0331] As an example, the first transmitter A02 includes the attachment of this application Figure 4 at least the first four of the antenna 452, the transmitter 454, the multi-antenna transmitting processor 457, the transmitting processor 468, the controller / processor 459, the memory 460, and the data source 467 therein.

[0332] As an example, the first transmitter A02 includes the attachment of this application Figure 4 at least the first three of the antenna 452, the transmitter 454, the multi-antenna transmitting processor 457, the transmitting processor 468, the controller / processor 459, the memory 460, and the data source 467 therein.

[0333] As an example, the first transmitter A02 includes the attachment of this application Figure 4 at least the first two of the antenna 452, the transmitter 454, the multi-antenna transmitting processor 457, the transmitting processor 468, the controller / processor 459, the memory 460, and the data source 467 therein.

[0334] As an example, the first transmitter A02 transmits a first PUSCH and a second PUSCH, and a first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, and the first orthogonal sequence is the orthogonal sequence of the PUSCH;

[0335] 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 the PUCCH for at least HARQ-ACK information.

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

[0337] As an example, 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.

[0338] As an example, 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.

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

[0340] As an example, the first PUSCH and the second PUSCH are two repetitions of the same PUSCH.

[0341] As an example, the first receiver A01 receives a first DCI, and the first DCI schedules the same PUSCH.

[0342] As an example, the first DCI includes indication information of the first orthogonal sequence.

[0343] As an example, the first PUSCH and the second PUSCH are in different time slots respectively.

[0344] As an example, the first transmitter A02 transmits a first PUSCH and a second PUSCH, and the first orthogonal sequence is applied to at least the first PUSCH and the second PUSCH, and the first orthogonal sequence is the orthogonal sequence of the PUSCH;

[0345] 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; 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 time slots respectively.

[0346] As a sub - embodiment of the above - mentioned embodiment, the first PUSCH and the second PUSCH are two repetitions of the same PUSCH.

[0347] As a sub - embodiment of the above - mentioned embodiment, when a first set of conditions is satisfied, 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.

[0348] As a sub - embodiment of the above - mentioned embodiment, the first PUSCH and the second PUSCH are two repetitions of the same PUSCH; when a first set of conditions is satisfied, 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.

[0349] Example 12

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

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

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

[0353] As an embodiment, the second node is a relay node.

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

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

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

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

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

[0359] As an example, the second transmitter B01 includes the attachment of this application Figure 4 at least the first four of the antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476 therein.

[0360] As an example, the second transmitter B01 includes the attachment of this application Figure 4 at least the first three of the antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476 therein.

[0361] As an example, the second transmitter B01 includes the attachment of this application Figure 4 at least the first two of the antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475, and memory 476 therein.

[0362] As an example, the second receiver B02 includes the attachment of this application Figure 4 at least one of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475, and memory 476 therein.

[0363] As an example, the second receiver B02 includes the attachment of this application Figure 4 at least the first five of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475, and memory 476 therein.

[0364] As an example, the second receiver B02 includes the attachment of this application Figure 4 at least the first four of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475, and memory 476 therein.

[0365] As an example, the second receiver B02 includes the attachment of this application Figure 4 at least the first three of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475, and memory 476 therein.

[0366] As an example, the second receiver B02 includes the attachment of this application Figure 4at least the first two of the antenna 420, the receiver 418, the multi-antenna receiving processor 472, the receiving processor 470, the controller / processor 475, and the memory 476.

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

[0368] 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 the PUCCH for at least HARQ-ACK information.

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

[0370] 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 that overlaps with the first PUSCH.

[0371] As an embodiment, 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.

[0372] As an embodiment, the second transmitter B01 transmits a first DCI, and the first DCI schedules at least the first PUSCH and the second PUSCH.

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

[0374] As an embodiment, the second transmitter B01 transmits a first DCI, and the first DCI schedules the same PUSCH.

[0375] As an embodiment, the first DCI includes indication information of the first orthogonal sequence.

[0376] As an embodiment, the first PUSCH and the second PUSCH are in different time slots respectively.

[0377] Those of ordinary skill in the art can understand that all or part of the steps in the above methods can be completed by a program instructing relevant hardware, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disc, etc. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiments can be implemented in hardware form or in the form of software function modules. This application is not limited to any specific form of the combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote control planes, aircraft, small airplanes, mobile phones, tablets, laptops, vehicle-mounted communication devices, transportation means, vehicles, RSU, 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 tablets, and other wireless communication devices. The base stations or system devices in this application include, but are not limited to, macrocell base stations, microcell base stations, small cell base stations, home base stations, relay base stations, eNB (evolved Node B), gNB, TRP, GNSS (Global Navigation Satellite System), relay satellites, satellite base stations, aerial base stations, RSU, drones, test equipment, such as transceiver devices or signaling testers that simulate some functions of base stations, and other wireless communication devices.

[0378] Those skilled in the art should understand that the present invention can be implemented in other specific forms without departing from its core or basic characteristics. Therefore, the currently disclosed embodiments should be regarded as descriptive rather than restrictive in any case. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within the equivalent meaning and scope thereof are considered to be included therein.

Claims

1. A method for a terminal, characterized in that: include: Sending a first PUSCH and a second PUSCH, 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 PUSCH; 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.

2. The method according to claim 1, characterized in that: 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 according to claim 1, characterized in that: 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.

4. The method according to any one of claims 1 to 3, characterized in that 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.

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

6. The method according to claim 5, characterized in that include: receiving a first DCI, where the first DCI schedules the same PUSCH; The first DCI includes 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 time slots respectively.

8. A terminal, characterized in that: The terminal includes: one or more processors and a memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions. The one or more processors call the computer instructions to enable the terminal to execute the method according to any one of claims 1 to 7.

9. A method for a base station, characterized in that: include: receiving 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 PUSCH; 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.

10. The method according to claim 9, characterized in that 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 according to claim 9, characterized in that 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.

12. The method according to any one of claims 9 to 11, characterized in that 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.

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

14. The method according to claim 13, characterized in that include: Sending a first DCI, where the first DCI schedules the same PUSCH; 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 time slots respectively.

16. A base station, characterized in that: The base station includes: one or more processors and a memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the base station to perform the method according to any one of claims 9 to 15.

Images