Method and apparatus related to UCI multiplexing used in wireless communication node

Abstract

The application discloses a method and apparatus related to UCI multiplexing used in a wireless communication node. A communication node receives a first signaling, the first PUCCH being a PUCCH for a first UCI, the first PUCCH depending on the first signaling; wherein the first PUCCH is overlapped with one air interface resource sub-pool in a first air interface resource pool, the first air interface resource pool comprises a plurality of air interface resource sub-pools, and the plurality of air interface resource sub-pools in the first air interface resource pool are respectively in a plurality of time slots. Each air interface resource sub-pool in the first air interface resource pool comprises at least part of a first PUSCH, the first air interface resource pool depends on a first configuration, and the first configuration is a configuration of an orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured and granted PUSCH.

Description

Technical Field

[0001] The present application relates to a transmission method and apparatus in a wireless communication system, particularly to a method and apparatus for transmitting wireless signals in a non-terrestrial network communication system. Background Art

[0002] In the existing NR (New Radio) system, the DMRS (Demodulation Reference Signal) of PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel) support multiplexing of multiple antenna ports / multiple users through orthogonal sequences.

[0003] In December 2023, the 3GPP (the 3rd Generation Partnership Project) RAN (Radio Access Network) #102 meeting decided to study the multiplexing of multiple users using orthogonal sequences on PUSCH in the "Non-Terrestrial Network (NTN) for NR (New Radio)" research project (Work Item, WI), that is, multiple users need to transmit PUSCH with orthogonal code domains within the same time-frequency resources. This multiplexing technology can significantly improve the uplink capacity and throughput. Summary of the Invention

[0004] After introducing the configuration of the orthogonal sequence of PUSCH, the multiplexing relationship between UCI (Uplink Control Information) and PUSCH 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 communication scenarios of non-terrestrial networks (NTN) and terrestrial networks (TN), and similar technical effects can be achieved. In addition, adopting a unified solution in different scenarios (including but not limited to communication scenarios of non-terrestrial networks and terrestrial networks) helps to reduce the hardware complexity and cost, or improve the 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] When necessary, the interpretation of the terms in this application may refer to the descriptions in the 3GPP specification protocols TS37 series and TS38 series.

[0006] This application discloses a method used in a terminal, which is characterized by including:

[0007] Receiving a first signaling, where the first PUCCH is a PUCCH for a first UCI, and the first PUCCH depends on the first signaling;

[0008] Wherein, the first PUCCH overlaps with an air interface resource sub-pool in a first air interface resource pool, the first air interface resource pool includes multiple air interface resource sub-pools, the multiple air interface resource sub-pools in the first air interface resource pool are respectively in multiple time slots, each air interface resource sub-pool in the first air interface resource pool includes at least part of a first PUSCH, the first air interface resource pool depends on a first configuration, and the first configuration is a configuration of orthogonal sequences of the PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0009] As an embodiment, the problems to be solved by this application include: in a communication scenario where orthogonal sequences of the PUSCH are configured, how to solve the overlap between the PUCCH and the PUSCH.

[0010] As an embodiment, the problems to be solved by this application include: in a communication scenario where orthogonal sequences of the PUSCH are configured, how to determine the multiplexing relationship between the first UCI and the first air interface resource pool.

[0011] As an embodiment, the characteristics of the above method include: compared with the configured grant PUSCH, the transmission of the dynamically scheduled PUSCH is more timely and flexible, and the base station can better eliminate the interference between multiple users caused by the destruction of the orthogonality of the PUSCH.

[0012] As an embodiment, the characteristics of the above method include: for the configured grant PUSCH, the transmission of the UL-SCH and the UCI multiplexing are based on the configuration of the orthogonal sequences of the PUSCH, that is, both the transmission of the UL-SCH and the UCI multiplexing apply the orthogonal sequences of the PUSCH, and the UCI is multiplexed into each air interface resource sub-pool that applies the orthogonal sequences of the PUSCH. Such characteristics are beneficial to maintaining the orthogonality obtained by multiple terminals including the terminal through the orthogonal sequences of the PUSCH.

[0013] As an embodiment, the advantages of the above method include: it is beneficial to support multiple users in occupying the same time-frequency resources, improving the uplink capacity and throughput.

[0014] As an embodiment, the advantages of the above method include: it is beneficial to ensure the transmission performance of PUSCH and reduce the interference between multiple users.

[0015] As an embodiment, the advantages of the above method include: improving the flexibility of base station configuration and scheduling.

[0016] As an embodiment, the advantages of the above method include: small changes to the existing 3GPP protocol, with good backward compatibility.

[0017] As an embodiment, the advantages of the above method include: improving the adaptability between UCI multiplexing and the type of PUSCH.

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

[0019] The multiplexing relationship between the first UCI and the first radio interface resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

[0020] As an embodiment, the characteristics of the above method include: the multiplexing relationship between the first UCI and the first radio interface resource pool depends on the type of the first PUSCH and the type of the first PUCCH.

[0021] As an embodiment, the characteristics of the above method include: compared with a non-dynamically triggered PUCCH, the transmission of a dynamically triggered PUCCH is more timely and flexible, and the base station can better eliminate the interference between multiple users caused by the destruction of the orthogonality of PUSCH.

[0022] As an embodiment, the advantages of the above method include: improving the adaptability between UCI multiplexing and the types of PUSCH and PUCCH.

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

[0024] When the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each radio interface resource sub-pool in the first radio interface resource pool.

[0025] As an embodiment, the characteristics of the above method include: under the configuration of the orthogonal sequence of PUSCH, when the configured granted PUSCH overlaps with the non-dynamically triggered PUCCH, an effective UCI multiplexing method is that UCI is multiplexed into each radio resource sub-pool of the radio resource to which PUSCH is applied.

[0026] As an embodiment, the advantages of the above method include: it is beneficial to maintain the orthogonality obtained by multiple terminals including the terminal through the orthogonal sequence of PUSCH.

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

[0028] Whether the first UCI is multiplexed into each radio resource sub-pool in the first radio resource pool depends on the length of the orthogonal sequence of PUSCH determined by the first configuration and the number of bits of the first UCI.

[0029] As an embodiment, the characteristics of the above method include: by restricting the length of the orthogonal sequence of PUSCH, the situation of too long orthogonal sequence of PUSCH is avoided, and sufficient UCI processing time is reserved for the terminal.

[0030] As an embodiment, the characteristics of the above method include: by restricting the number of UCI bits, the situation that too many UCI bits occupy too much transmission resources is avoided, and the transmission performance of the UL-SCH transport block is improved.

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

[0032] Sending a first signal in the first radio resource pool;

[0033] Wherein, a first bit block and a second bit block are used to generate the first signal, the first bit block includes at least one TB, and the second bit block includes the first UCI.

[0034] As an embodiment, the characteristics of the above method include: when PUSCH overlaps with PUCCH for UCI, perform the operation of multiplexing UCI onto PUSCH and send PUSCH.

[0035] As an embodiment, the advantages of the above method include: small changes to the existing 3GPP protocol, and good backward compatibility.

[0036] As an embodiment, the advantages of the above method include: improving the transmission efficiency of the uplink.

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

[0038] Whether the first signal transmitted in the first radio resource pool uses the orthogonal sequence of PUSCH depends on at least the former of the types of the first PUSCH and the types of the first PUCCH.

[0039] As an embodiment, the characteristics of the above method include: under the configuration of the orthogonal sequence of PUSCH, according to at least the former of the types of the first PUSCH and the types of the first PUCCH, it is determined that the first UCI is multiplexed into the radio resource sub-pool in the first radio resource pool that overlaps with the first PUCCH. Then, the transmission of the UL-SCH transport block falls back to not using the orthogonal sequence of PUSCH, that is, neither the UCI nor the transmission of the UL-SCH transport block uses the orthogonal sequence of PUSCH.

[0040] As an embodiment, the characteristics of the above method include: under the configuration of the orthogonal sequence of PUSCH, according to at least the former of the types of the first PUSCH and the types of the first PUCCH, it is determined that the first UCI is multiplexed into the radio resource sub-pool in the first radio resource pool that overlaps with the first PUCCH. Then, the transmission of the UL-SCH transport block uses the orthogonal sequence of PUSCH, that is, the UCI does not use the orthogonal sequence of PUSCH, while the transmission of the UL-SCH transport block uses the orthogonal sequence of PUSCH; in addition, in order to reduce the interference between the PUSCHs of code division multiplexing of different terminals, other terminals that perform code division multiplexing with the terminal should abandon the transmission of the PUSCH of code division multiplexing.

[0041] As an embodiment, the characteristics of the above method include: under the configuration of the orthogonal sequence of PUSCH, according to at least the former of the types of the first PUSCH and the types of the first PUCCH, it is determined that the first UCI is multiplexed into each radio resource sub-pool in the first radio resource pool. Then, the transmission of the UL-SCH transport block uses the orthogonal sequence of PUSCH, that is, both the UCI and the transmission of the UL-SCH transport block use the orthogonal sequence of PUSCH.

[0042] As an embodiment, the advantages of the above method include: it is beneficial to avoid the interference between the PUSCHs of code division multiplexing of different users caused by improper UCI multiplexing operations.

[0043] As an embodiment, the advantages of the above method include: determining whether the transmission of the UL-SCH transport block uses the orthogonal sequence of PUSCH according to at least the former of the types of PUSCH and the types of PUCCH improves the flexibility of base station configuration and scheduling.

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

[0045] Abandon sending a second signal in the first radio resource pool;

[0046] Wherein, a first bit block is used to generate the second signal, and the first bit block includes at least one TB; when the first PUSCH is a configured-grant PUSCH and the first PUCCH is a non-dynamically-triggered PUCCH: the second signal is not sent, and the first UCI is not multiplexed into any radio resource sub-pool in the first radio resource pool.

[0047] As an embodiment, the characteristics of the above method include: when the configured-grant PUSCH overlaps with the non-dynamically-triggered PUCCH, instead of performing the UCI multiplexing operation, the PUSCH is dropped to ensure the transmission performance of the PUCCH.

[0048] As an embodiment, the advantages of the above method include: avoiding introducing overly complex UCI multiplexing operations, being able to reduce the capability requirements of the terminal, and reducing the power consumption and cost of the terminal.

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

[0050] Send first capability information, where the first capability information indicates the maximum length supported by the terminal;

[0051] Wherein, the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

[0052] As an embodiment, the advantages of the above method include: being beneficial to supporting different terminals to report different code division multiplexing capabilities, and being beneficial to the base station for more flexible resource scheduling.

[0053] As an embodiment, the advantages of the above method include: being beneficial to the base station to better perform user pairing according to the reported capability information and improving the pairing success rate.

[0054] As an embodiment, the advantages of the above method include: being beneficial to supporting the coexistence of orthogonal sequences of PUSCH under multiple lengths and having good forward compatibility.

[0055] The present application discloses a method used in a base station, which is characterized in that it includes:

[0056] Send a first signaling, where the first PUCCH is a PUCCH for a first UCI, and the first PUCCH depends on the first signaling;

[0057] Among them, the first PUCCH overlaps with one air interface resource sub-pool in the first air interface resource pool. The first air interface resource pool includes multiple air interface resource sub-pools. The multiple air interface resource sub-pools in the first air interface resource pool are respectively in multiple time slots. Each air interface resource sub-pool in the first air interface resource pool includes at least part of the first PUSCH. The first air interface resource pool depends on the first configuration, and the first configuration is the configuration of the orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

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

[0059] The multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

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

[0061] When the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool.

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

[0063] Whether the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

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

[0065] Receiving a first signal in the first air interface resource pool;

[0066] Among them, a first bit block and a second bit block are used to generate the first signal. The first bit block includes at least one TB, and the second bit block includes the first UCI.

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

[0068] Whether the orthogonal sequence of the PUSCH is applied to the first signal transmitted in the first radio resource pool depends on at least the former of both the type of the first PUSCH and the type of the first PUCCH.

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

[0070] Abandon receiving a second signal in the first radio resource pool;

[0071] Wherein, a first bit block is used to generate the second signal, and the first bit block includes at least one TB; when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not transmitted, and the first UCI is not multiplexed into any radio resource sub-pool in the first radio resource pool.

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

[0073] Receive first capability information, where the first capability information indicates the maximum length supported by the terminal;

[0074] Wherein, the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

[0075] The present application discloses a terminal, characterized in that the terminal includes: one or more processors and a memory;

[0076] The memory is coupled to the one or more processors, and the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to cause the terminal to execute the method used in the terminal.

[0077] The present application discloses a base station, characterized in that the base station includes: one or more processors and a memory;

[0078] The memory is coupled to the one or more processors, and the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to cause the base station to execute the method used in the base station. Description of the Drawings

[0079] 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:

[0080] Figure 1 Shows a processing flow chart of a terminal according to an embodiment of the present application;

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

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

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

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

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

[0086] Figure 7 Shows an illustrative schematic diagram of a first PUCCH overlapping with an air interface resource sub-pool in a first air interface resource pool;

[0087] Figure 8 Shows an illustrative schematic diagram of a first PUCCH overlapping with an air interface resource sub-pool in a first air interface resource pool;

[0088] Figure 9 Shows an illustrative schematic diagram of a multiplexing relationship between a first UCI and a first air interface resource pool;

[0089] Figure 10 Shows an illustrative schematic diagram of the type of a first PUCCH;

[0090] Figure 11 Shows an illustrative schematic diagram that whether a first signal transmitted in a first air interface resource pool applies an orthogonal sequence of a PUSCH depends on at least the former of both the type of the first PUSCH and the type of the first PUCCH;

[0091] Figure 12 Shows a structural block diagram of a processing device in a terminal according to an embodiment of the present application;

[0092] Figure 13 FIG. 1 shows a structural block diagram of a processing apparatus in a base station according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0094] Example 1

[0095] Embodiment 1 exemplifies a processing flow chart of a terminal according to an embodiment of the present application, as shown in the accompanying Figure 1 drawings.

[0096] In Embodiment 1, the terminal in the present application receives a first signaling in step 101.

[0097] In Embodiment 1, the first PUCCH is a PUCCH for the first UCI, and the first PUCCH depends on the first signaling; the first PUCCH overlaps with an air interface resource sub-pool in a first air interface resource pool, the first air interface resource pool includes a plurality of air interface resource sub-pools, the plurality of air interface resource sub-pools in the first air interface resource pool are respectively in a plurality of time slots, each air interface resource sub-pool in the first air interface resource pool includes at least a part of the first PUSCH, the first air interface resource pool depends on a first configuration, and the first configuration is a configuration of an orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0098] As an embodiment, the first signaling includes control information bits.

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

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

[0101] As an embodiment, the first signaling is a DCI format for dynamically scheduling a PDSCH (Physical Downlink Shared Channel).

[0102] As an embodiment, the first signaling is a DCI format for semi-persistently scheduling a PDSCH.

[0103] As an example, the benefits of the above method include: small latency in indication using the DCI format.

[0104] As an example, the first signaling is transmitted on the downlink.

[0105] As an example, the first signaling is transmitted on the PDCCH (Physical Downlink Control CHannel).

[0106] As an example, the first signaling is higher layer signaling.

[0107] As an example, the first signaling is a MAC CE (Medium Access Control layer Control Element).

[0108] As an example, the first signaling is RRC (Radio Resource Control) signaling.

[0109] As an example, the first signaling is a PUCCH-Config IE (Information Element).

[0110] As an example, the first signaling is a PUCCH-ConfigCommon IE (Information Element).

[0111] As an example, the first signaling is an SPS-Config IE (Information Element).

[0112] As an example, the first signaling is an SPS-PUCCH-AN IE (Information Element).

[0113] As an example, the first signaling is a CSI-ReportConfig IE (Information Element).

[0114] As an example, the first UCI at least includes HARQ-ACK (Hybrid Automatic Repeat Request ACKnowledgement) information.

[0115] As an example, the first UCI includes CSI (Channel State Information).

[0116] As an example, the first UCI does not include CSI.

[0117] As an example, the first UCI does not include SR (Scheduling Request).

[0118] As an example, the first UCI is the UCI included in the first PUCCH.

[0119] As an example, the first UCI is the UCI (Uplink Control Information) that the terminal would transmit in the first PUCCH.

[0120] As an example, the first UCI is the UCI configured to be multiplexed into the first PUCCH.

[0121] As an example, the first UCI is the UCI determined to be transmitted on the first PUCCH before processing the overlap between the PUCCH and the PUSCH.

[0122] As an example, the first PUCCH is a PUCCH (Physical Uplink Control CHannel) for transmitting the first UCI.

[0123] As an example, the first PUCCH is a PUCCH triggered for transmitting at least the first UCI.

[0124] As an example, the terminal would transmit the first PUCCH with the first UCI.

[0125] As an example, the first PUCCH carries the first UCI.

[0126] As an example, the first PUCCH is within a slot.

[0127] As an example, the first PUCCH is a PUCCH without repetitions in a single slot.

[0128] As an embodiment, the repetition transmission times of the first PUCCH is equal to 1.

[0129] As an embodiment, when a PUCCH is a PUCCH with times of repetitions, this PUCCH is repeatedly transmitted; when a PUCCH is a

[0130] PUCCH with times of repetitions, this PUCCH is not repeatedly transmitted.

[0131] As a sub - embodiment of the above - mentioned embodiment, the is provided by pucch - RepetitionNrofSlots.

[0132] As an embodiment, the first PUCCH depends on the first signaling, including: the first PUCCH is triggered by the first signaling.

[0133] As an embodiment, the first PUCCH depends on the first signaling, including: the first signaling indicates the PUCCH resource for the first PUCCH.

[0134] As an embodiment, the first PUCCH depends on the first signaling, including: the index of the first control channel element (CCE) of the PDCCH for receiving the first signaling and the PUCCH resource indicator field in the first signaling are used to determine the transmission resource of the first PUCCH.

[0135] As an embodiment, the first PUCCH depends on the first signaling, including: the first PUCCH responds to (in response to) the detected (detecting) first signaling.

[0136] As an embodiment, an air interface resource sub - pool in the first air interface resource pool includes time - frequency resources.

[0137] As an embodiment, an air interface resource sub - pool in the first air interface resource pool is allocated for PUSCH transmission.

[0138] As an embodiment, an air interface resource sub - pool in the first air interface resource pool includes at least a part of a PUSCH.

[0139] As an example, one radio resource sub - pool in the first radio resource pool includes one repetition of a PUSCH.

[0140] As an example, the first radio resource pool includes a plurality of radio resource sub - pools.

[0141] As an example, the number of radio resource sub - pools in the first radio resource pool can be configured as one of 2, 4, and 8.

[0142] As an example, the number of radio resource sub - pools in the first radio resource pool can be configured as one of 2 and 4.

[0143] As an example, each radio resource sub - pool in the first radio resource pool includes all symbols in one time slot in the time domain.

[0144] As an example, each radio resource sub - pool in the first radio resource pool only includes some symbols in one time slot in the time domain.

[0145] As an example, for each radio resource sub - pool in the first radio resource pool, at least part of the first PUSCH included therein includes one repetition of the first PUSCH.

[0146] As an example, each radio resource sub - pool in the first radio resource pool is a part of the first radio resource pool.

[0147] As an example, each radio resource sub - pool in the first radio resource pool includes a part of the first PUSCH.

[0148] As an example, each radio resource sub - pool in the first radio resource pool includes a part of the first PUSCH after being divided in the time domain.

[0149] As an example, each radio resource sub - pool in the first radio resource pool includes a part of the first PUSCH in the corresponding time slot.

[0150] As an example, each radio resource sub - pool in the first radio resource pool is at least part of the first PUSCH.

[0151] As an example, each radio resource sub - pool in the first radio resource pool is a part of the first PUSCH.

[0152] As an example, each radio resource sub - pool in the first radio resource pool is one repetition of the first PUSCH.

[0153] As an example, in terms of time domain, the multiple air interface resource sub-pools in the first air interface resource pool are respectively in multiple time slots.

[0154] As an example, the first PUSCH is a PUSCH of PUSCH repetition Type A.

[0155] As an example, the first PUSCH is a PUSCH of PUSCH repetition Type A scheduled by DCI format or a PUSCH of PUSCH repetition Type A with a configured grant.

[0156] As an example, the multiple air interface resource sub-pools in the first air interface resource pool are in consecutive time slots.

[0157] As an example, the multiple air interface resource sub-pools in the first air interface resource pool are in non-consecutive time slots.

[0158] As an example, adjacent air interface resource sub-pools in the first air interface resource pool are consecutive in time domain.

[0159] As an example, there is a time domain interval between adjacent air interface resource sub-pools in the first air interface resource pool.

[0160] As an example, the symbols included in an air interface resource sub-pool in the first air interface resource pool in a corresponding time slot are configurable.

[0161] As an example, the symbols included in an air interface resource sub-pool in the first air interface resource pool in a corresponding time slot are indicated by the time domain resource assignment field in the DCI scheduling the first PUSCH.

[0162] As an example, the symbols included in an air interface resource sub-pool in the first air interface resource pool in a corresponding time slot are indicated by the time domain resource assignment field in the DCI activating the first PUSCH.

[0163] As an example, the symbols included in an air interface resource sub-pool in the first air interface resource pool in a corresponding time slot are indicated by the higher layer parameter timeDomainAllocation in rrc-ConfiguredUplinkGrant.

[0164] As an embodiment, the symbols included in an air interface resource sub - pool in the first air interface resource pool are symbols defined in the time domain.

[0165] As an embodiment, the symbols included in an air interface resource sub - pool in the first air interface resource pool are OFDM symbols.

[0166] As an embodiment, the symbols included in an air interface resource sub - pool in the first air interface resource pool are symbols in a time slot.

[0167] As an embodiment, the overlap in this application refers to the overlap in the time domain.

[0168] As an embodiment, the first PUCCH overlaps with an air interface resource sub - pool in the first air interface resource pool, which means that the first PUCCH and this air interface resource sub - pool in the first air interface resource pool overlap at least partially in the time domain.

[0169] As an embodiment, the first configuration includes the configuration of higher layer parameters.

[0170] As an embodiment, the first configuration includes the configuration of the MAC (Medium Access Control) layer.

[0171] As an embodiment, the first configuration includes the configuration of the RRC (Radio Resource Control) layer.

[0172] As an embodiment, the benefits of the above - mentioned method include: high reliability of configuration parameter transmission.

[0173] As an embodiment, the first configuration includes the configuration of the length of the orthogonal sequence(s) of the PUSCH.

[0174] As an embodiment, the first configuration includes the indication of the index of the orthogonal sequence of the PUSCH.

[0175] As an embodiment, the orthogonal sequence in this application includes an orthogonal cover code.

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

[0177] As an embodiment, the orthogonal sequence of the PUSCH is an orthogonal sequence configured for use in PUSCH transmission.

[0178] As an example, the orthogonal sequence of the PUSCH is the orthogonal sequence configured for multiple repeated transmissions of the PUSCH.

[0179] As an example, the first configuration includes the configuration of the orthogonal cover code for the PUSCH.

[0180] As an example, the first configuration includes the configuration of the length of the orthogonal cover code for the PUSCH.

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

[0182] As an example, the first configuration indicates the multiple radio resource sub-pools in the first radio resource pool.

[0183] As an example, the number of radio resource sub-pools in the first radio resource pool is determined according to the first configuration.

[0184] As an example, the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration.

[0185] As an example, the length of the orthogonal sequence of the PUSCH determined by the first configuration is equal to one of 2, 4, and 8.

[0186] As an example, the length of the orthogonal sequence of the PUSCH determined by the first configuration is equal to one of 2 and 4.

[0187] As an example, the candidates of the type of the first PUSCH include dynamic scheduling and configured grant.

[0188] As an example, when the first PUSCH is dynamically scheduled by an uplink grant in DCI, the first PUSCH is a dynamically scheduled PUSCH.

[0189] As an example, when the first PUSCH is a PUSCH based on a dynamic grant, the first PUSCH is a dynamically scheduled PUSCH.

[0190] As an example, when the first PUSCH corresponds to configured grant Type 1 or configured grant Type 2, the first PUSCH is a configured grant PUSCH.

[0191] As an example, when the first PUSCH corresponds to configured grant Type 2 activated by DCI, the first PUSCH is a configured grant PUSCH.

[0192] As an example, when the first PUSCH is a configured-grant based PUSCH, the first PUSCH is a configured grant PUSCH.

[0193] As an example, when the first PUSCH is semi-persistently scheduled by a valid activation DCI in the uplink grant, the first PUSCH is a configured grant PUSCH.

[0194] As an example, when the first PUSCH is semi-statically configured, the first PUSCH is a configured grant PUSCH.

[0195] As an example, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, including: whether the first UCI is multiplexed into the first radio resource pool depends on the type of the first PUSCH.

[0196] As an example, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, including: which radio resource sub-pool or sub-pools in the first radio resource pool the first UCI is multiplexed into depends on the type of the first PUSCH.

[0197] As an example, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, including: when the first PUSCH is a configured grant PUSCH, the first UCI is multiplexed into each radio resource sub-pool in the first radio resource pool; when the first PUSCH is a dynamically scheduled PUSCH, the first UCI is multiplexed into the radio resource sub-pool that overlaps with the first PUCCH in the first radio resource pool.

[0198] As a sub - embodiment of the above - mentioned embodiment, when the first PUSCH is a dynamically scheduled PUSCH, the first UCI is not multiplexed into the radio resource sub - pool in the first radio resource pool that does not overlap with the first PUCCH.

[0199] As an embodiment, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, including: when the first PUSCH is a configured - grant PUSCH, the first UCI is not multiplexed into the first radio resource pool; when the first PUSCH is a dynamically scheduled PUSCH, the first UCI is multiplexed into the first radio resource pool.

[0200] As an embodiment, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, including: when the first PUSCH is a configured - grant PUSCH, the first UCI is not multiplexed into any radio resource sub - pool in the first radio resource pool; when the first PUSCH is a dynamically scheduled PUSCH, the first UCI is multiplexed into the radio resource sub - pool in the first radio resource pool that overlaps with the first PUCCH.

[0201] As a sub - embodiment of the above - mentioned embodiment, when the first PUSCH is a dynamically scheduled PUSCH, the first UCI is not multiplexed into the radio resource sub - pool in the first radio resource pool that does not overlap with the first PUCCH.

[0202] As an embodiment, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, including: the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH and the type of the first PUCCH.

[0203] As an embodiment, the first PUCCH is a dynamically triggered PUCCH or a non - dynamically triggered PUCCH.

[0204] As an embodiment, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH and the type of the first PUCCH, including: when the first PUSCH is a configured - grant PUSCH and the first PUCCH is a dynamically triggered PUCCH, the first UCI is multiplexed into the radio resource sub - pool in the first radio resource pool that overlaps with the first PUCCH.

[0205] As a sub - embodiment of the above - mentioned embodiment, when the first PUSCH is a configured - grant PUSCH and the first PUCCH is a dynamically - triggered PUCCH, the first UCI is not multiplexed into the radio - access - network resource sub - pool in the first radio - access - network resource pool that does not overlap with the first PUCCH.

[0206] As an embodiment, the multiplexing relationship between the first UCI and the first radio - access - network resource pool depends on the type of the first PUSCH and the type of the first PUCCH, including: when the first PUSCH is a configured - grant PUSCH and the first PUCCH is a non - dynamically - triggered PUCCH, the first UCI is not multiplexed into the first radio - access - network resource pool.

[0207] As an embodiment, the multiplexing relationship between the first UCI and the first radio - access - network resource pool depends on the type of the first PUSCH and the type of the first PUCCH, including: when the first PUSCH is a dynamically - scheduled PUSCH or the first PUCCH is a dynamically - triggered PUCCH, the first UCI is multiplexed into the first radio - access - network resource pool.

[0208] As an embodiment, the multiplexing relationship between the first UCI and the first radio - access - network resource pool depends on the type of the first PUSCH and the type of the first PUCCH, including: when the first PUSCH is a dynamically - scheduled PUSCH or the first PUCCH is a dynamically - triggered PUCCH, the first UCI is multiplexed into the radio - access - network resource sub - pool in the first radio - access - network resource pool that overlaps with the first PUCCH.

[0209] As a sub - embodiment of the above - mentioned embodiment, when the first PUSCH is a dynamically - scheduled PUSCH or the first PUCCH is a dynamically - triggered PUCCH, the first UCI is not multiplexed into the radio - access - network resource sub - pool in the first radio - access - network resource pool that does not overlap with the first PUCCH.

[0210] As an embodiment, the multiplexing relationship between the first UCI and the first radio - access - network resource pool depends on the type of the first PUSCH and the type of the first PUCCH, including: when the first PUSCH is a configured - grant PUSCH and the first PUCCH is a non - dynamically - triggered PUCCH, the first UCI is not multiplexed into any radio - access - network resource sub - pool in the first radio - access - network resource pool.

[0211] As an example, the multiplexing relationship between the first UCI and the first radio access network (RAN) resource pool depends on the type of the first physical uplink shared channel (PUSCH) and the type of the first physical uplink control channel (PUCCH), including: when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH, the first UCI is multiplexed into each RAN resource sub-pool in the first RAN resource pool.

[0212] As an example, whether the first UCI is multiplexed into each RAN resource sub-pool in the first RAN resource pool depends on the length of the orthogonal sequence of the first configured PUSCH and the number of bits of the first UCI.

[0213] As an example, for the first UCI to be multiplexed into each RAN resource sub-pool in the first RAN resource pool, the following conditions need to be met: the length of the orthogonal sequence of the first configured PUSCH is not greater than a first threshold, and the number of bits of the first UCI is not greater than a second threshold.

[0214] As an example, the advantages of the above method include: improving the timeliness of the first UCI transmission.

[0215] As an example, the advantages of the above method include: facilitating the avoidance of deterioration of the transmission performance of the UL-SCH transport block caused by excessive UCI bits being multiplexed onto the PUSCH.

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

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

[0218] As an example, the first threshold is predefined.

[0219] As an example, the first threshold depends on the UE capability.

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

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

[0222] As an example, the first threshold is not greater than 8.

[0223] As an example, the second threshold is configurable.

[0224] As an example, the second threshold is configured by RRC signaling.

[0225] As an embodiment, the second threshold is configured by maxPayloadSize.

[0226] As an embodiment, the second threshold is predefined.

[0227] As an embodiment, the second threshold is a positive integer.

[0228] As an embodiment, the second threshold is greater than 1.

[0229] As an embodiment, the second threshold is not greater than 1706.

[0230] As an embodiment, when the first PUSCH is a configured-grant PUSCH, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the first threshold, and the number of bits of the first UCI is not greater than the second threshold: the first UCI is multiplexed into each radio resource sub-pool in the first radio resource pool.

[0231] As an embodiment, when the first PUSCH is a configured-grant PUSCH, and the first PUCCH is a non-dynamically-triggered PUCCH, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the first threshold, and the number of bits of the first UCI is not greater than the second threshold: the first UCI is multiplexed into each radio resource sub-pool in the first radio resource pool.

[0232] As an embodiment, when the length of the orthogonal sequence of the PUSCH determined by the first configuration is greater than the first threshold, or when the number of bits of the first UCI is greater than the second threshold: the first UCI is not multiplexed into each radio resource sub-pool in the first radio resource pool.

[0233] As an embodiment, multiple radio resource pools are allocated for the transmission of the first PUSCH.

[0234] As an embodiment, the first radio resource pool is a radio resource pool among the multiple radio resource pools that overlaps with the first PUCCH.

[0235] As an embodiment, the number of radio resource sub-pools in each radio resource pool among the multiple radio resource pools is equal.

[0236] Example 2

[0237] Embodiment 2 exemplifies a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the appendix Figure 2 as shown. AppendixFigure 2Describes the network architecture 200 of 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 may 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 a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, an HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and an Internet service 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 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 a node 203 and other nodes 204. The node 203 provides user and control plane protocol termination towards the UE 201. The node 203 may be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. The node 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (Transmitter Receiver Point), or some other suitable term. The node 203 provides an access point to the 5GC / EPC 210 for the UE 201. Examples of the 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, 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 through 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, and the S-GW / UPF 212 itself is 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 operator-corresponding Internet protocol services, specifically including the Internet, intranet, IMS (IP Multimedia Subsystem), and packet switching services.

[0238] As an embodiment, the UE 201 corresponds to the terminal in the present application.

[0239] As an embodiment, the gNB 203 corresponds to the base station in the present application.

[0240] As an embodiment, the UE 201 corresponds to the terminal in the present application, and the gNB 203 corresponds to the base station in the present application.

[0241] As an embodiment, the gNB 203 is a macro cellular base station.

[0242] As an example, the gNB 203 is a Microcell base station.

[0243] As an example, the gNB 203 is a Picocell base station.

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

[0245] As an example, the gNB 203 is a base station device supporting large delay differences.

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

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

[0248] Example 3

[0249] 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 the user plane 350 and the control plane 300. Figure 3The radio protocol architecture for controlling plane 300 is shown with 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 herein. 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 as well as 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. 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. 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 Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in L3 of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling. The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). In the user plane 350, the radio protocol architecture is generally the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355. However, the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for the mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support service diversity.

[0250] As an example, attachFigure 3 The wireless protocol architecture in

[0251] As an example, the Figure 3 wireless protocol architecture in

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

[0253] As an example, the first PUCCH in this application is generated by the PHY301.

[0254] As an example, the first PUSCH in this application is generated by the PHY301.

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

[0256] As an example, the first signal in this application is generated by the PHY301.

[0257] As an example, the first signal in this application is generated by the PHY351.

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

[0259] As an example, the higher layer in this application refers to the layers above the physical layer.

[0260] As an example, the higher layer in this application includes the MAC layer.

[0261] As an example, the higher layer in this application includes the RRC layer.

[0262] Example 4

[0263] Example 4 shows a schematic diagram of a first communication device and a second communication device according to this application, as shown in the appendix Figure 4 as shown. Figure 4 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.

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

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

[0266] 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 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 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 time-domain multi-carrier symbol streams. Subsequently, the multi-antenna transmit processor 471 performs transmit analog precoding / beamforming operations on the time-domain multi-carrier symbol streams. Each transmitter 418 converts the baseband multi-carrier symbol streams provided by the multi-antenna transmit processor 471 into radio frequency streams, and then provides them to different antennas 420.

[0267] 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 via 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 that is 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 is recovered in the multi-antenna receive processor 458 for any spatial stream destined for the second communication device 450 after multi-antenna detection. 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 deinterleaves 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.

[0268] 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 an upper layer data packet 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, 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 retransmission of 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 passing through analog precoding / beamforming operations 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.

[0269] 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 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 L1 layer functions. A controller / processor 475 implements 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 the upper layer data packet from the second communication device 450. The upper layer data packet from the controller / processor 475 may be provided to the core network.

[0270] As an example, the terminal in the present application includes the second communication device 450, and the base station in the present application includes the first communication device 410.

[0271] As a sub - embodiment of the above - mentioned embodiment, the second communication device 450 is a user equipment, and the first communication device 410 is a relay node.

[0272] As a sub - embodiment of the above - mentioned embodiment, the second communication device 450 is a user equipment, and the first communication device 410 is a base station device.

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

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

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

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

[0277] 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 with the at least one processor. The second communication device 450 is at least configured to: receive first signaling, where a first PUCCH is a PUCCH for a first UCI, and the first PUCCH depends on the first signaling; the first PUCCH overlaps with an air - interface resource sub - pool in a first air - interface resource pool, the first air - interface resource pool including a plurality of air - interface resource sub - pools, the plurality of air - interface resource sub - pools in the first air - interface resource pool are respectively in a plurality of time slots, each air - interface resource sub - pool in the first air - interface resource pool includes at least a part of a first PUSCH, the first air - interface resource pool depends on a first configuration, the first configuration being a configuration of an orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first air - interface resource pool depends on the type of the first PUSCH, the first PUSCH being a dynamically scheduled PUSCH or a configured - grant PUSCH.

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

[0279] 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: receiving a first signaling, the first PUCCH being a PUCCH for a first UCI, the first PUCCH depending on the first signaling; the first PUCCH overlapping with an air - interface resource sub - pool in a first air - interface resource pool, the first air - interface resource pool including a plurality of air - interface resource sub - pools, the plurality of air - interface resource sub - pools in the first air - interface resource pool being in a plurality of time slots respectively, each air - interface resource sub - pool in the first air - interface resource pool including at least a part of a first PUSCH, the first air - interface resource pool depending on a first configuration, the first configuration being a configuration of orthogonal sequences of PUSCH; the multiplexing relationship between the first UCI and the first air - interface resource pool depending on the type of the first PUSCH, the first PUSCH being a dynamically scheduled PUSCH or a configured - grant PUSCH.

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

[0281] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code being configured to be used together with the at least one processor. The first communication device 410 is at least configured to: send a first signaling, the first PUCCH being a PUCCH for a first UCI, the first PUCCH depending on the first signaling; the first PUCCH overlapping with an air - interface resource sub - pool in a first air - interface resource pool, the first air - interface resource pool including a plurality of air - interface resource sub - pools, the plurality of air - interface resource sub - pools in the first air - interface resource pool being in a plurality of time slots respectively, each air - interface resource sub - pool in the first air - interface resource pool including at least a part of a first PUSCH, the first air - interface resource pool depending on a first configuration, the first configuration being a configuration of orthogonal sequences of PUSCH; the multiplexing relationship between the first UCI and the first air - interface resource pool depending on the type of the first PUSCH, the first PUSCH being a dynamically scheduled PUSCH or a configured - grant PUSCH.

[0282] As a sub - embodiment of the above - mentioned embodiment, the first communication device 410 corresponds to the base station in the present application.

[0283] As an embodiment, 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: sending a first signaling, where a first PUCCH is a PUCCH for a first UCI, and the first PUCCH depends on the first signaling; the first PUCCH overlaps with an air interface resource sub-pool in a first air interface resource pool, the first air interface resource pool includes a plurality of air interface resource sub-pools, the plurality of air interface resource sub-pools in the first air interface resource pool are respectively in a plurality of time slots, each air interface resource sub-pool in the first air interface resource pool includes at least a part of a first PUSCH, the first air interface resource pool depends on a first configuration, and the first configuration is a configuration of an orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0284] As a sub-embodiment of the above embodiment, the first communication device 410 corresponds to the base station in the present application.

[0285] As an 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 signaling in the present application.

[0286] 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 send the first signaling in the present application.

[0287] 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 PUCCH in the present application.

[0288] 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 send the first PUCCH in the present application.

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

[0290] As an example, 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, the data source 467} is used to transmit the first PUSCH in the present application.

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

[0292] As an example, 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, the data source 467} is used to transmit the first signal in the present application.

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

[0294] As an example, at least one of {the antenna 420, the transmitter 418, the multi-antenna transmitting processor 471, the transmitting processor 416, the controller / processor 475, the memory 476} is used to transmit the first capability information in the present application.

[0295] Example 5

[0296] Embodiment 5 exemplifies a signal transmission flowchart according to an embodiment of the present application, as shown in the appendix Figure 5 shown. In the appendix Figure 5 the communication between the terminal U1 and the base station U2 is through the air interface. In the appendix Figure 5 the dashed boxes F1 and F2 are optional. It should be specifically noted that the order in this embodiment does not limit the signal transmission order and the implementation order in the present application.

[0297] The terminal U1 sends the first capability information in step S51A, receives the first signaling in step S511, and sends the first signal in the first radio access network (RAN) resource pool in step S51B.

[0298] The base station U2 receives the first capability information in step S52A, sends the first signaling in step S521, and receives the first signal in the first RAN resource pool in step S52B.

[0299] In Embodiment 5, the first physical uplink control channel (PUCCH) is for the PUCCH of the first uplink control information (UCI), and the first PUCCH depends on the first signaling; the first PUCCH overlaps with one RAN resource sub-pool in the first RAN resource pool. The first RAN resource pool includes multiple RAN resource sub-pools. The multiple RAN resource sub-pools in the first RAN resource pool are respectively in multiple time slots. Each RAN resource sub-pool in the first RAN resource pool includes at least a part of the first physical uplink shared channel (PUSCH). The first RAN resource pool depends on the first configuration, and the first configuration is the configuration of the orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first RAN resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0300] As a sub-embodiment of Embodiment 5, the multiplexing relationship between the first UCI and the first RAN resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

[0301] As an ancillary embodiment of the above sub-embodiment, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each RAN resource sub-pool in the first RAN resource pool.

[0302] As a sub-embodiment of Embodiment 5, whether the first UCI is multiplexed into each RAN resource sub-pool in the first RAN resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

[0303] As an ancillary embodiment of the above sub-embodiment, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: whether the first UCI is multiplexed into each RAN resource sub-pool in the first RAN resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

[0304] As a sub - embodiment of Embodiment 5, the first bit block and the second bit block are used to generate the first signal. The first bit block includes at least one TB, and the second bit block includes the first UCI.

[0305] As a sub - embodiment of Embodiment 5, whether the orthogonal sequence of PUSCH is applied to the first signal transmitted in the first radio access resource pool depends on at least the former of both the type of the first PUSCH and the type of the first PUCCH.

[0306] As a sub - embodiment of Embodiment 5, the first capability information indicates the maximum length supported by the terminal; the number of radio access resource sub - pools in the first radio access resource pool is equal to the length of the orthogonal sequence of PUSCH determined by the first configuration, and the length of the orthogonal sequence of PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

[0307] As an embodiment, the terminal U1 is the terminal in this application.

[0308] As an embodiment, the base station U2 is the base station in this application.

[0309] As an embodiment, the terminal U1 is a UE.

[0310] As an embodiment, the base station U2 is a base station.

[0311] As an embodiment, the air interface between the base station U2 and the terminal U1 is the Uu interface.

[0312] As an embodiment, the air interface between the base station U2 and the terminal U1 includes a cellular link.

[0313] As an embodiment, the air interface between the base station U2 and the terminal U1 includes a wireless interface between the base station device and the user equipment.

[0314] As an embodiment, the air interface between the base station U2 and the terminal U1 includes a wireless interface between the satellite device and the user equipment.

[0315] As an embodiment, the air interface between the base station U2 and the terminal U1 includes a wireless interface between the relay device and the user equipment.

[0316] As an embodiment, the dotted - line box F1 exists.

[0317] As an embodiment, the first capability information indicates the maximum length supported by the terminal, and the length of the orthogonal sequence of PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

[0318] As an example, the maximum length supported by the terminal is the maximum length of the orthogonal sequence of the PUSCH supported by the terminal.

[0319] As an example, the maximum length of the orthogonal sequence of the PUSCH supported by the terminal depends on the UE capability of the terminal.

[0320] As an example, the first capability information indicates that the maximum length supported by the terminal is 2, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is 2.

[0321] As an example, the first capability information indicates that the maximum length supported by the terminal is 4, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is 2 or 4.

[0322] As an example, the transmission of the first capability information is before the reception of the first signaling.

[0323] As an example, the reception of the first capability information is before the transmission of the first signaling.

[0324] As an example, the dashed box F1 does not exist.

[0325] As an example, the dashed box F2 exists.

[0326] As an example, the first signal includes a wireless signal.

[0327] As an example, the first signal includes a radio frequency signal.

[0328] As an example, the first signal includes a baseband signal.

[0329] As an example, the first signal includes a transmission signal on the uplink.

[0330] As an example, the first signal occupies a positive integer number of resource elements in the time-frequency domain.

[0331] As an example, the first signal corresponds to an uplink grant.

[0332] As an example, the sending of the first signal includes: sending at least one of a transport block(s) or CSI (Channel State Information) report(s) via the first signal.

[0333] As an example, the first bit block includes one TB (Transport Block) or two TBs, and the second bit block includes the first UCI.

[0334] As an example, the first bit block carries UL-SCH (Uplink Shared Channel) data.

[0335] As an example, the first bit block is a UL-SCH transport block.

[0336] As an example, the sending of the first signal includes: sending the first bit block and the second bit block via the first signal.

[0337] As an example, the sending of the first signal includes: the output after at least part of the terminal sending the first bit block and the second bit block through transport block CRC attachment, code block segmentation, code block CRC attachment, channel coding, rate matching, code block concatenation, scrambling, modulation, layer mapping, transform precoding, precoding, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and modulation up-conversion.

[0338] As an example, the sending of the first signal in the first radio access network resource pool includes: the terminal multiplexing the first bit block and the second bit block together into the first radio access network resource pool.

[0339] As an example, the reception of the first signaling is before the transmission of the first signal.

[0340] As an example, the transmission of the first signaling is before the reception of the first signal.

[0341] As an example, the transmission / reception of the first capability information is before the transmission / reception of the first signal.

[0342] As an example, regardless of whether the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH, the first signal is transmitted.

[0343] As an example, regardless of whether the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH, and regardless of whether the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH, the first signal is transmitted.

[0344] As an example, the dashed box F2 does not exist.

[0345] Example 6

[0346] Example 6 exemplifies a signal transmission flowchart according to an embodiment of the present application, as shown in the appendix Figure 6 as shown. In the appendix Figure 6 the communication between the terminal U1 and the base station U2 is through the air interface. In the appendix Figure 6 the dashed box F1 and the dashed box F2 are optional. It should be specifically noted that the order in this embodiment does not limit the signal transmission order and the implementation order in the present application.

[0347] The terminal U1 transmits the first capability information in step S51A; receives the first signaling in step S511; and abandons transmitting the second signal in the first air interface resource pool in step S51B.

[0348] The base station U2 receives the first capability information in step S52A; transmits the first signaling in step S521; and abandons receiving the second signal in the first air interface resource pool in step S52B.

[0349] In Embodiment 6, the first PUCCH is the PUCCH for the first UCI, and the first PUCCH depends on the first signaling; the first PUCCH overlaps with one radio resource sub-pool in the first radio resource pool. The first radio resource pool includes multiple radio resource sub-pools. The multiple radio resource sub-pools in the first radio resource pool are respectively in multiple time slots. Each radio resource sub-pool in the first radio resource pool includes at least part of the first PUSCH. The first radio resource pool depends on the first configuration, and the first configuration is the configuration of the orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0350] As a sub-embodiment of Embodiment 6, the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

[0351] As a sub-embodiment of Embodiment 6, the first bit block is used to generate the second signal, and the first bit block includes at least one TB; when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not sent, and the first UCI is not multiplexed into any radio resource sub-pool in the first radio resource pool.

[0352] As a sub-embodiment of Embodiment 6, the first capability information indicates the maximum length supported by the terminal; the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

[0353] As an embodiment, the terminal U1 is the terminal in the present application.

[0354] As an embodiment, the base station U2 is the base station in the present application.

[0355] As an embodiment, the terminal U1 is a UE.

[0356] As an embodiment, the base station U2 is a base station.

[0357] As an embodiment, the air interface between the base station U2 and the terminal U1 is the Uu interface.

[0358] As an example, the air interface between the base station U2 and the terminal U1 includes a cellular link.

[0359] As an example, the air interface between the base station U2 and the terminal U1 includes a wireless interface between the base station device and the user equipment.

[0360] As an example, the air interface between the base station U2 and the terminal U1 includes a wireless interface between the satellite device and the user equipment.

[0361] As an example, the air interface between the base station U2 and the terminal U1 includes a wireless interface between the relay device and the user equipment.

[0362] As an example, the dashed box F1 exists.

[0363] As an example, the first capability information indicates the maximum length supported by the terminal, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

[0364] As an example, the maximum length supported by the terminal is the maximum length of the orthogonal sequence of the PUSCH supported by the terminal.

[0365] As an example, the maximum length of the orthogonal sequence of the PUSCH supported by the terminal depends on the UE capability of the terminal.

[0366] As an example, the first capability information indicates that the maximum length supported by the terminal is 2, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is 2.

[0367] As an example, if the first capability information indicates that the maximum length supported by the terminal is 2, the terminal does not expect the length of the orthogonal sequence of the PUSCH determined by the first configuration to be 4.

[0368] As an example, the first capability information indicates that the maximum length supported by the terminal is 4, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is 2 or 4.

[0369] As an example, the transmission of the first capability information is before the reception of the first signaling.

[0370] As an example, the reception of the first capability information is before the transmission of the first signaling.

[0371] As an example, the dashed box F1 does not exist.

[0372] As an example, the dashed box F2 exists.

[0373] As an example, the second signal includes a wireless signal.

[0374] As an example, the second signal includes a radio frequency signal.

[0375] As an example, the second signal includes a baseband signal.

[0376] As an example, the second signal includes a transmission signal on the uplink.

[0377] As an example, the second signal occupies a positive integer number of resource elements in the time-frequency domain.

[0378] As an example, the second signal corresponds to an uplink grant.

[0379] As an example, the abandonment of transmitting the second signal includes: the second signal is skipped.

[0380] As an example, the first bit block includes one TB (Transport Block) or two TBs.

[0381] As an example, the first bit block carries UL-SCH (Uplink Shared Channel) data.

[0382] As an example, the first bit block is a UL-SCH transport block.

[0383] As an example, when the first PUSCH is a configured grant PUSCH: the second signal is not transmitted, and the first UCI is not multiplexed into any of the radio access network resource sub-pools in the first radio access network resource pool.

[0384] As an example, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not transmitted, and the first UCI is not multiplexed into any of the radio access network resource sub-pools in the first radio access network resource pool.

[0385] As an example, the dashed box F2 does not exist.

[0386] As an example, the terminal transmits the first signal in the first radio access network (RAN) resource pool, or the terminal abandons transmitting the second signal in the first RAN resource pool.

[0387] As an example, the base station receives the first signal in the first RAN resource pool, or the terminal abandons receiving the second signal in the first RAN resource pool.

[0388] As an example, whether the first signal is transmitted or the second signal is not transmitted depends on the type of the first physical uplink shared channel (PUSCH).

[0389] As an example, whether the first signal is transmitted or the second signal is not transmitted depends on the type of the first PUSCH and the type of the first physical uplink control channel (PUCCH).

[0390] As an example, when the first PUSCH is a configured grant PUSCH: the second signal is not transmitted.

[0391] As an example, when the first PUSCH is a dynamically scheduled PUSCH: the first signal is transmitted.

[0392] As an example, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not transmitted.

[0393] As an example, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a dynamically triggered PUCCH: the first signal is transmitted.

[0394] As an example, when the first PUSCH is a dynamically scheduled PUSCH, or the first PUCCH is a dynamically triggered PUCCH: the first signal is transmitted.

[0395] As an example, when the first PUSCH is a configured grant PUSCH: in each RAN resource pool in the first RAN resource pool, a sub-signal of the second signal is abandoned from being transmitted.

[0396] As an example, when the first PUSCH is a dynamically scheduled PUSCH: in each RAN resource pool in the first RAN resource pool, a sub-signal of the first signal is transmitted.

[0397] As an example, when the first PUSCH is a configured-grant PUSCH and the first PUCCH is a non-dynamically-triggered PUCCH: Abandon transmitting a sub-signal of the second signal in each radio resource pool in the first radio resource pool.

[0398] As an example, when the first PUSCH is a configured-grant PUSCH and the first PUCCH is a dynamically-triggered PUCCH: Transmit a sub-signal of the first signal in each radio resource pool in the first radio resource pool.

[0399] As an example, when the first PUSCH is a dynamically-scheduled PUSCH or the first PUCCH is a dynamically-triggered PUCCH: Transmit a sub-signal of the first signal in each radio resource pool in the first radio resource pool.

[0400] Example 7

[0401] Embodiment 7 shows an illustrative schematic diagram of the first PUCCH overlapping with a radio resource sub-pool in the first radio resource pool according to an embodiment of the present application, as shown in the appendix Figure 7 shown. In the appendix Figure 7 A rectangle filled with diagonal lines represents a radio resource sub-pool in the first radio resource pool, a rectangle filled with diamond lines represents the first PUCCH, and the rectangle filled with diagonal lines circled by a dashed square represents the first radio resource pool.

[0402] In Embodiment 7, the first radio resource pool includes two radio resource sub-pools, which are respectively in two time slots. Each radio resource sub-pool in these two radio resource sub-pools is a repetition of the first PUSCH, and the first PUCCH has an overlap in time with one of the two radio resource sub-pools.

[0403] As an example, the first PUCCH only has an overlap in time with one of the two radio resource sub-pools.

[0404] As an example, in the appendix Figure 7 the first radio resource pool includes radio resource sub-pool #0 and radio resource sub-pool #1. Radio resource sub-pool #0 and radio resource sub-pool #1 are respectively in two time slots. Radio resource sub-pool #0 and radio resource sub-pool #1 are both a repetition of the first PUSCH, and the first PUCCH has an overlap in time with radio resource sub-pool #1.

[0405] As an example, the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is 2.

[0406] As an example, radio resource sub-pool #0 and radio resource sub-pool #1 are in consecutive time slots.

[0407] As an example, radio resource sub-pool #0 and radio resource sub-pool #1 are in non-consecutive time slots.

[0408] As an example, radio resource sub-pool #0 and radio resource sub-pool #1 are continuous in the time domain.

[0409] As an example, there is a time domain interval between radio resource sub-pool #0 and radio resource sub-pool #1.

[0410] As an example, the first PUCCH overlapping with a radio resource sub-pool in the first radio resource pool means that the radio resource sub-pool in the first radio resource pool overlapping with the first PUCCH is one of radio resource sub-pool #0 and radio resource sub-pool #1.

[0411] Example 8

[0412] Embodiment 8 shows an illustrative diagram of the first PUCCH overlapping with a radio resource sub-pool in the first radio resource pool according to an embodiment of the present application, as shown in the appendix Figure 8 shown. In the appendix Figure 8 A rectangle filled with diagonal lines represents a radio resource sub-pool in the first radio resource pool, a rectangle filled with diamond lines represents the first PUCCH, and the rectangle filled with diagonal lines circled by a dotted square represents the first radio resource pool.

[0413] In Embodiment 8, the first radio resource pool includes four radio resource sub-pools, and these four radio resource sub-pools are respectively in four time slots. Each radio resource sub-pool among these four radio resource sub-pools is a repetition of the first PUSCH, and the first PUCCH has an overlap in time with one of these four radio resource sub-pools.

[0414] As an example, the first PUCCH only has an overlap in time with one of these four radio resource sub-pools.

[0415] As an example, in the appendix Figure 8Among them, the first radio resource pool includes radio resource sub-pool #0, radio resource sub-pool #1, radio resource sub-pool #2, and radio resource sub-pool #3. The radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3 are respectively in four time slots. The radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3 are all one repetition of the first PUSCH. The first PUCCH overlaps with the radio resource sub-pool #1 in the time domain.

[0416] As an embodiment, the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is 4.

[0417] As an embodiment, the radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3 are in consecutive time slots.

[0418] As an embodiment, the radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3 are in non-consecutive time slots.

[0419] As an embodiment, radio resource sub-pool #i and radio resource sub-pool #i + 1 are two adjacent radio resource sub-pools in the first radio resource pool. The radio resource sub-pool #i and the radio resource sub-pool #i + 1 are continuous in the time domain, and i is one of 0, 1, 2, 3.

[0420] As an embodiment, radio resource sub-pool #i and radio resource sub-pool #i + 1 are two adjacent radio resource sub-pools in the first radio resource pool. There is a time domain interval between the radio resource sub-pool #i and the radio resource sub-pool #i + 1, and i is one of 0, 1, 2, 3.

[0421] As an embodiment, the first PUCCH overlapping with a radio resource sub-pool in the first radio resource pool means that the radio resource sub-pool in the first radio resource pool overlapping with the first PUCCH is one of the radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3.

[0422] Example 9

[0423] Embodiment 9 shows an explanatory schematic diagram of the multiplexing relationship between the first UCI and the first radio resource pool according to an embodiment of the present application, as shown in the appendix Figure 9 shown. In the appendix Figure 9Among them, a slant-filled rectangle represents an air interface resource sub-pool in the first air interface resource pool. The slant-filled rectangles circled by the dashed-line square represent the first air interface resource pool. The unfilled solid rectangle pointed to by the solid arrow represents that the first UCI is multiplexed into an air interface resource sub-pool in the first air interface resource pool. The unfilled dashed rectangle pointed to by the dashed arrow represents that the first UCI is not multiplexed into an air interface resource sub-pool in the first air interface resource pool.

[0424] In Embodiment 9, the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool, or the first UCI is multiplexed into the air interface resource sub-pools in the first air interface resource pool that overlap with the first PUCCH, or the first UCI is not multiplexed into any air interface resource sub-pool in the first air interface resource pool.

[0425] As an embodiment, in Figure 9 Case (a) of the appendix, the first air interface resource pool includes four air interface resource sub-pools, and the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool.

[0426] As an embodiment, in Figure 9 Case (a) of the appendix, the first air interface resource pool includes air interface resource sub-pool #0, air interface resource sub-pool #1, air interface resource sub-pool #2, and air interface resource sub-pool #3. As long as any one of the air interface resource sub-pool #0, the air interface resource sub-pool #1, the air interface resource sub-pool #2, and the air interface resource sub-pool #3 overlaps with the first PUCCH in the time domain, the first UCI is multiplexed into any one of the air interface resource sub-pool #0, the air interface resource sub-pool #1, the air interface resource sub-pool #2, and the air interface resource sub-pool #3.

[0427] As an embodiment, in Figure 9 Case (b) of the appendix, the first air interface resource pool includes four air interface resource sub-pools, and the first UCI is multiplexed into the air interface resource sub-pools in the first air interface resource pool that overlap with the first PUCCH.

[0428] As an embodiment, in Figure 9 Case (b) of the appendix, the first air interface resource pool includes air interface resource sub-pool #0, air interface resource sub-pool #1, air interface resource sub-pool #2, and air interface resource sub-pool #3. Only the air interface resource sub-pool #1 overlaps with the first PUCCH in the time domain. The first UCI is multiplexed into the air interface resource sub-pool #1, and the first UCI is not multiplexed into any one of the air interface resource sub-pool #0, the air interface resource sub-pool #2, and the air interface resource sub-pool #3.

[0429] As an example, in the case (c) shown in the appendix Figure 9 the first radio resource pool includes four radio resource sub-pools, and the first UCI is not multiplexed into any of the radio resource sub-pools in the first radio resource pool.

[0430] As an example, in the case (c) shown in the appendix Figure 9 the first radio resource pool includes radio resource sub-pool #0, radio resource sub-pool #1, radio resource sub-pool #2, and radio resource sub-pool #3, and the first UCI is not multiplexed into any of the radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3.

[0431] As an example, in the case (c) shown in the appendix Figure 9 the first radio resource pool includes radio resource sub-pool #0, radio resource sub-pool #1, radio resource sub-pool #2, and radio resource sub-pool #3. As long as any of the radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3 overlaps with the first PUCCH in the time domain, the first UCI is not multiplexed into any of the radio resource sub-pool #0, the radio resource sub-pool #1, the radio resource sub-pool #2, and the radio resource sub-pool #3.

[0432] As an example, the length of the orthogonal sequence of the first configured PUSCH is 4, and the description of the multiplexing relationship between the first UCI and the first radio resource pool shown in Example 9 also applies to the orthogonal sequences of PUSCHs with other lengths.

[0433] Example 10

[0434] Example 10 shows a schematic diagram of the description of the type of the first PUCCH according to an embodiment of the present application, as shown in the appendix Figure 10 shown.

[0435] In Example 10, the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

[0436] As an example, the candidates for the type of the first PUCCH include dynamic triggering and non-dynamic triggering.

[0437] As an example, when the first PUCCH is in response to the terminal's detection of the DCI format, the first PUCCH is a dynamically triggered PUCCH.

[0438] As an example, when the first PUCCH is not in response to the terminal's detection of DCI format, the first PUCCH is a non-dynamically triggered PUCCH.

[0439] As an example, when the first PUCCH is a PUCCH triggered by detecting a DCI format, the first PUCCH is a dynamically triggered PUCCH.

[0440] As an example, when the first PUCCH is not a PUCCH triggered by detecting a DCI format, the first PUCCH is a non-dynamically triggered PUCCH.

[0441] As an example, when the first PUCCH is only for the HARQ-ACK information corresponding to the SPS PDSCH, the first PUCCH is a non-dynamically triggered PUCCH.

[0442] As an example, when the first PUCCH is only for CSI reporting, the first PUCCH is a non-dynamically triggered PUCCH.

[0443] Example 11

[0444] Embodiment 11 shows an illustrative diagram of whether the first signal transmitted in the first radio access network resource pool according to an embodiment of the present application applies the orthogonal sequence of the PUSCH depending on at least the former of both the type of the first PUSCH and the type of the first PUCCH, as shown in the appendix Figure 11 as shown.

[0445] As an example, whether the first signal transmitted in the first radio access network resource pool applies the orthogonal sequence of the PUSCH depends on the type of the first PUSCH and the type of the first PUCCH; when the first PUSCH is a configured-grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: a sub-signal of the first signal is transmitted in each radio access network resource sub-pool in the first radio access network resource pool, and the first signal applies a first orthogonal sequence; the first orthogonal sequence depends on the first configuration.

[0446] As an example, the first configuration includes the configuration of a first orthogonal sequence, the first orthogonal sequence is the orthogonal sequence of the PUSCH, and the number of radio access network resource sub-pools in the first radio access network resource pool is equal to the length of the first orthogonal sequence.

[0447] As an example, the first orthogonal sequence is an orthogonal sequence for PUSCH transmission.

[0448] As an example, the first orthogonal sequence includes a plurality of elements, and the plurality of elements are respectively used to generate transmissions in the plurality of air interface resource sub-pools in the first air interface resource pool.

[0449] As an example, the first configuration indicates the length of the first orthogonal sequence.

[0450] As an example, the first orthogonal sequence is one of a plurality of orthogonal sequences, orthogonality is maintained among the plurality of orthogonal sequences, and each orthogonal sequence in the plurality of orthogonal sequences corresponds to an index.

[0451] As an example, the first configuration indicates the index corresponding to the first orthogonal sequence among the plurality of orthogonal sequences.

[0452] As an example, the first orthogonal sequence is [a1, a2,..., a K , and K is equal to the length of the first orthogonal sequence.

[0453] As an example, the a1, the a2,..., the a K are respectively elements at different sorting positions in the first orthogonal sequence.

[0454] As an example, the sorting positions of the a1, the a2,..., the a K in the first orthogonal sequence are from front to back.

[0455] As an example, the sorting positions of the a1, the a2,..., the a K in the first orthogonal sequence are from back to front.

[0456] As an example, the first orthogonal sequence is a Walsh sequence.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0471] As an embodiment, whether the first signal transmitted in the first radio resource pool applies the orthogonal sequence of PUSCH depends on the type of the first PUSCH; when the first PUSCH is a dynamically scheduled PUSCH: a sub - signal of the first signal is transmitted in each radio resource sub - pool in the first radio resource pool, and the first signal applies the first orthogonal sequence.

[0472] As an example, whether the first signal transmitted in the first radio access resource pool uses the orthogonal sequence of PUSCH depends on the type of the first PUSCH; when the first PUSCH is a dynamically scheduled PUSCH: a sub-signal of the first signal is transmitted in each radio access resource sub-pool in the first radio access resource pool, and the first signal does not use the orthogonal sequence of PUSCH.

[0473] As an example, whether the first signal transmitted in the first radio access resource pool uses the orthogonal sequence of PUSCH depends on the type of the first PUSCH and the type of the first PUCCH; when the first PUSCH is a configured grant PUSCH and the first PUCCH is a dynamically triggered PUCCH: a sub-signal of the first signal is transmitted in each radio access resource sub-pool in the first radio access resource pool, and the first signal uses the first orthogonal sequence.

[0474] As an example, whether the first signal transmitted in the first radio access resource pool uses the orthogonal sequence of PUSCH depends on the type of the first PUSCH and the type of the first PUCCH; when the first PUSCH is a configured grant PUSCH and the first PUCCH is a dynamically triggered PUCCH: a sub-signal of the first signal is transmitted in each radio access resource sub-pool in the first radio access resource pool, and the first signal does not use the orthogonal sequence of PUSCH.

[0475] As an example, whether the first signal transmitted in the first radio access resource pool uses the orthogonal sequence of PUSCH depends on the type of the first PUSCH and the type of the first PUCCH; when the first PUSCH is a dynamically scheduled PUSCH or the first PUCCH is a dynamically triggered PUCCH: a sub-signal of the first signal is transmitted in each radio access resource sub-pool in the first radio access resource pool, and the first signal uses the first orthogonal sequence.

[0476] As an example, whether the first signal transmitted in the first radio access resource pool uses the orthogonal sequence of PUSCH depends on the type of the first PUSCH and the type of the first PUCCH; when the first PUSCH is a dynamically scheduled PUSCH or the first PUCCH is a dynamically triggered PUCCH: a sub-signal of the first signal is transmitted in each radio access resource sub-pool in the first radio access resource pool, and the first signal does not use the orthogonal sequence of PUSCH.

[0477] As an example, the first signal applies the first orthogonal sequence, including: the transmission of the first bit block applies the first orthogonal sequence.

[0478] As an example, the characteristics of the above method include: the first configuration indicates the first orthogonal sequence, and the transmission of the UL-SCH transport block applies the first orthogonal sequence.

[0479] As an example, the first signal does not apply the orthogonal sequence of the PUSCH, including: the transmission of the first bit block does not apply the orthogonal sequence of the PUSCH.

[0480] As an example, the characteristics of the above method include: the transmission of the UL-SCH transport block does not apply the orthogonal sequence of the PUSCH.

[0481] Example 12

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

[0483] As an example, the processing device A00 in the terminal is a processing device in a user equipment.

[0484] As an example, the processing device A00 in the terminal is a processing device in a relay node.

[0485] As an example, the processing device A00 in the terminal is a processing device in a vehicular communication device.

[0486] As an example, the processing device A00 in the terminal is a processing device in a conventional user equipment.

[0487] As an example, the processing device A00 in the terminal is a processing device in a user equipment supporting configurations related to communication of a non-terrestrial network.

[0488] As an example, the first receiver A01 includes 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, and the data source 467 in the appendix of the present application Figure 4 in the present application.

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

[0490] As an example, the first receiver A01 includes the attachment of this application Figure 4 at least the first four of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460, and data source 467 therein.

[0491] As an example, the first receiver A01 includes the attachment of this application Figure 4 at least the first three of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460, and data source 467 therein.

[0492] As an example, the first receiver A01 includes the attachment of this application Figure 4 at least the first two of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460, and data source 467 therein.

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

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

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

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

[0497] As an embodiment, the first transmitter A02 includes at least the first two of the antenna 452, transmitter 454, multi-antenna transmission processor 457, transmission processor 468, controller / processor 459, memory 460, and data source 467 attached to this application. Figure 4

[0498] As an embodiment, the first receiver A01 receives first signaling, and the first PUCCH is a PUCCH for the first UCI, and the first PUCCH depends on the first signaling;

[0499] Wherein, the first PUCCH overlaps with one air interface resource sub-pool in the first air interface resource pool, the first air interface resource pool includes a plurality of air interface resource sub-pools, the plurality of air interface resource sub-pools in the first air interface resource pool are respectively in a plurality of time slots, each air interface resource sub-pool in the first air interface resource pool includes at least part of the first PUSCH, the first air interface resource pool depends on the first configuration, and the first configuration is a configuration of the orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0500] As an embodiment, the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

[0501] As an embodiment, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool.

[0502] As an embodiment, whether the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

[0503] As an embodiment, the first transmitter A02 transmits a first signal in the first air interface resource pool.

[0504] As an embodiment, a first bit block and a second bit block are used to generate the first signal, the first bit block includes at least one TB, and the second bit block includes the first UCI.

[0505] As an example, whether the orthogonal sequence of PUSCH is applied to the first signal transmitted in the first radio resource pool depends on at least the former of both the type of the first PUSCH and the type of the first PUCCH.

[0506] As an example, the first transmitter A02 abandons transmitting the second signal in the first radio resource pool.

[0507] As an example, a first bit block is used to generate the second signal, and the first bit block includes at least one TB; when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not transmitted, and the first UCI is not multiplexed into any radio resource sub-pool in the first radio resource pool.

[0508] As an example, the first transmitter A02 transmits first capability information, and the first capability information indicates the maximum length supported by the terminal.

[0509] As an example, the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the first configured PUSCH, and the length of the orthogonal sequence of the first configured PUSCH is not greater than the maximum length supported by the terminal.

[0510] As an example, the first receiver A01 receives first signaling, the first PUCCH is a PUCCH for the first UCI, and the first PUCCH depends on the first signaling; the first transmitter A02 transmits first capability information, and the first capability information indicates the maximum length supported by the terminal; the first transmitter A02 transmits a first signal in the first radio resource pool;

[0511] Among them, the first PUCCH overlaps with one radio resource sub-pool in the first radio resource pool. The first radio resource pool includes multiple radio resource sub-pools. The multiple radio resource sub-pools in the first radio resource pool are respectively in multiple time slots. Each radio resource sub-pool in the first radio resource pool includes at least part of the first PUSCH. The first radio resource pool depends on the first configuration, and the first configuration is the configuration of the orthogonal sequence of the PUSCH; the number of radio resource sub-pools in the first radio resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal; the first bit block and the second bit block are used to generate the first signal. The first bit block includes at least one TB, and the second bit block includes the first UCI; the multiplexing relationship between the first UCI and the first radio resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0512] As a sub-embodiment of the above embodiment, the multiplexing relationship between the first UCI and the first radio resource pool also depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH; when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each radio resource sub-pool in the first radio resource pool.

[0513] As a sub-embodiment of the above embodiment, whether the first signal transmitted in the first radio resource pool applies the orthogonal sequence of the PUSCH depends on at least the former of the type of the first PUSCH and the type of the first PUCCH.

[0514] As a sub-embodiment of the above embodiment, whether the first UCI is multiplexed into each radio resource sub-pool in the first radio resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

[0515] As an embodiment, the first receiver A01 receives the first signaling. The first PUCCH is the PUCCH for the first UCI, and the first PUCCH depends on the first signaling; the first transmitter A02 sends the first capability information, and the first capability information indicates the maximum length supported by the terminal; the first transmitter A02 sends the first signal in the first radio resource pool.

[0516] Among them, the first PUCCH overlaps with an air interface resource sub-pool in the first air interface resource pool. The first air interface resource pool includes multiple air interface resource sub-pools. The multiple air interface resource sub-pools in the first air interface resource pool are respectively in multiple time slots. Each air interface resource sub-pool in the first air interface resource pool includes at least part of the first PUSCH. The first air interface resource pool depends on the first configuration, and the first configuration is the configuration of the orthogonal sequence of the PUSCH; the number of air interface resource sub-pools in the first air interface resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal; the first bit block and the second bit block are used to generate the first signal. The first bit block includes at least one TB, and the second bit block includes the first UCI; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH and the type of the first PUCCH. The first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

[0517] As a sub-embodiment of the above embodiment, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool.

[0518] As a sub-embodiment of the above embodiment, whether the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

[0519] As a sub-embodiment of the above embodiment, whether the first signal transmitted in the first air interface resource pool applies the orthogonal sequence of the PUSCH depends on at least the former of the type of the first PUSCH and the type of the first PUCCH.

[0520] As an embodiment, the first receiver A01 receives the first signaling. The first PUCCH is the PUCCH for the first UCI, and the first PUCCH depends on the first signaling; the first transmitter A02 transmits the first capability information, and the first capability information indicates the maximum length supported by the terminal; the first transmitter A02 abandons transmitting the second signal in the first air interface resource pool;

[0521] Among them, the first PUCCH overlaps with one air interface resource sub-pool in the first air interface resource pool. The first air interface resource pool includes multiple air interface resource sub-pools. The multiple air interface resource sub-pools in the first air interface resource pool are respectively in multiple time slots. Each air interface resource sub-pool in the first air interface resource pool includes at least part of the first PUSCH. The first air interface resource pool depends on the first configuration, and the first configuration is the configuration of the orthogonal sequence of the PUSCH; the number of air interface resource sub-pools in the first air interface resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal; the first bit block is used to generate the second signal, and the first bit block includes at least one TB; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH and the type of the first PUCCH. The first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH; the second signal is not sent, and the first UCI is not multiplexed into any air interface resource sub-pool in the first air interface resource pool.

[0522] As a sub-embodiment of the above embodiment, the first PUSCH is a configured grant PUSCH, and the first PUCCH is a non-dynamically triggered PUCCH.

[0523] Example 13

[0524] Embodiment 13 exemplifies a structural block diagram of a processing device in a base station according to an embodiment of the present application, as shown in the appendix Figure 13 shown. In the appendix Figure 13 the processing device B00 in the base station includes a second transmitter B01 and a second receiver B02.

[0525] As an embodiment, the processing device B00 in the base station is a processing device in a satellite device.

[0526] As an embodiment, the processing device B00 in the base station is a processing device in a relay node.

[0527] As an embodiment, the processing device B00 in the base station is a processing device in a base station supporting non-terrestrial network communication.

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

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

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

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

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

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

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

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

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

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

[0538] As an example, the second transmitter B01 transmits a first signaling, and the first PUCCH is a PUCCH for the first UCI, and the first PUCCH depends on the first signaling;

[0539] Wherein, the first PUCCH overlaps with an air interface resource sub-pool in a first air interface resource pool, the first air interface resource pool includes a plurality of air interface resource sub-pools, the plurality of air interface resource sub-pools in the first air interface resource pool are respectively in a plurality of time slots, each air interface resource sub-pool in the first air interface resource pool includes at least a part of the first PUSCH, the first air interface resource pool depends on a first configuration, and the first configuration is a configuration of an orthogonal sequence of the PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configured grant PUSCH.

[0540] As an example, the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

[0541] As an example, when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool.

[0542] As an example, whether the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

[0543] As an example, the second receiver B02 receives a first signal in the first air interface resource pool.

[0544] As an example, a first bit block and a second bit block are used to generate the first signal, the first bit block includes at least one TB, and the second bit block includes the first UCI.

[0545] As an example, whether the orthogonal sequence of PUSCH is applied to the first signal transmitted in the first radio access network resource pool depends on at least the former of the type of the first PUSCH and the type of the first PUCCH.

[0546] As an example, the second receiver B02 abandons receiving the second signal in the first radio access network resource pool.

[0547] As an example, a first bit block is used to generate the second signal, and the first bit block includes at least one TB; when the first PUSCH is a configured grant PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not transmitted, and the first UCI is not multiplexed into any radio access network resource sub-pool in the first radio access network resource pool.

[0548] As an example, the second receiver B02 receives first capability information, and the first capability information indicates the maximum length supported by the terminal.

[0549] As an example, the number of radio access network resource sub-pools in the first radio access network resource pool is equal to the length of the orthogonal sequence of the first configured PUSCH, and the length of the orthogonal sequence of the first configured PUSCH is not greater than the maximum length supported by the terminal.

[0550] Those of ordinary skill in the art can understand that all or part of the steps in the above methods can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disc, etc. Optionally, all or part of the steps of 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 the form of hardware or in the form of a software functional module. 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, tablet computers, notebooks, 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 tablet computers, and other wireless communication devices. The base station or system equipment in this application includes, but is 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 the base station, and other wireless communication devices.

[0551] Those skilled in the art should understand that the present invention can be implemented in other specified 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 are considered to be included therein.

Claims

1. A method used in a terminal, characterized in that: include: receiving a first signaling, where a first PUCCH is a PUCCH for a first UCI, and the first PUCCH depends on the first signaling; Among them, the first PUCCH overlaps with an air interface resource subpool in the first air interface resource pool, the first air interface resource pool includes multiple air interface resource subpools, the multiple air interface resource subpools in the first air interface resource pool are respectively in multiple time slots, each air interface resource subpool in the first air interface resource pool includes at least part of the first PUSCH, and the first air interface resource pool depends on a first configuration, and the first configuration is a configuration of an orthogonal sequence of PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configuration-granted PUSCH.

2. The method according to claim 1, characterized in that The multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

3. The method according to claim 2, characterized in that When the first PUSCH is a configured granted PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool.

4. The method according to claim 1, whether the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

5. The method according to any one of claims 1 to 4, characterized in that: include: Sending a first signal in the first air interface resource pool; A first bit block and a second bit block are used to generate the first signal, the first bit block includes at least one TB, and the second bit block includes the first UCI.

6. The method according to any one of claims 1 to 5, characterized in that: Whether the first signal transmitted in the first air interface resource pool applies an orthogonal sequence of a PUSCH depends on at least the former of the type of the first PUSCH and the type of the first PUCCH.

7. The method according to claim 2, characterized in that include: Abandon sending a second signal in the first air interface resource pool; In which, the first bit block is used to generate the second signal, and the first bit block includes at least one TB; when the first PUSCH is a configured granted PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not sent, and the first UCI is not multiplexed into any air interface resource sub-pool in the first air interface resource pool.

8. The method according to any one of claims 1 to 7, characterized in that: include: Sending first capability information, where the first capability information indicates a maximum length supported by the terminal; The number of air interface resource sub-pools in the first air interface resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

9. 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 8.

10. A method used in a base station, characterized in that: include: Sending a first signaling, where a first PUCCH is for a PUCCH of a first UCI, and the first PUCCH depends on the first signaling; Among them, the first PUCCH overlaps with an air interface resource subpool in the first air interface resource pool, the first air interface resource pool includes multiple air interface resource subpools, the multiple air interface resource subpools in the first air interface resource pool are respectively in multiple time slots, each air interface resource subpool in the first air interface resource pool includes at least part of the first PUSCH, and the first air interface resource pool depends on a first configuration, and the first configuration is a configuration of an orthogonal sequence of PUSCH; the multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUSCH, and the first PUSCH is a dynamically scheduled PUSCH or a configuration-granted PUSCH.

11. The method according to claim 10, characterized in that The multiplexing relationship between the first UCI and the first air interface resource pool depends on the type of the first PUCCH, and the first PUCCH is a dynamically triggered PUCCH or a non-dynamically triggered PUCCH.

12. The method according to claim 11, characterized in that When the first PUSCH is a configured granted PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool.

13. The method according to claim 10, whether the first UCI is multiplexed into each air interface resource sub-pool in the first air interface resource pool depends on the length of the orthogonal sequence of the PUSCH determined by the first configuration and the number of bits of the first UCI.

14. The method according to any one of claims 10 to 13, characterized in that include: Receiving a first signal in the first air interface resource pool; A first bit block and a second bit block are used to generate the first signal, the first bit block includes at least one TB, and the second bit block includes the first UCI.

15. The method according to any one of claims 10 to 14, characterized in that Whether the first signal transmitted in the first air interface resource pool applies an orthogonal sequence of a PUSCH depends on at least the former of the type of the first PUSCH and the type of the first PUCCH.

16. The method according to claim 11, characterized in that include: Abandon receiving a second signal in the first air interface resource pool; In which, the first bit block is used to generate the second signal, and the first bit block includes at least one TB; when the first PUSCH is a configured granted PUSCH and the first PUCCH is a non-dynamically triggered PUCCH: the second signal is not sent, and the first UCI is not multiplexed into any air interface resource sub-pool in the first air interface resource pool.

17. The method according to any one of claims 10 to 16, characterized in that include: receiving first capability information, where the first capability information indicates a maximum length supported by the terminal; The number of air interface resource sub-pools in the first air interface resource pool is equal to the length of the orthogonal sequence of the PUSCH determined by the first configuration, and the length of the orthogonal sequence of the PUSCH determined by the first configuration is not greater than the maximum length supported by the terminal.

18. 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 10 to 17.

Images