CN118301768A

CN118301768A - Parameter configuration method, device and storage medium

Info

Publication number: CN118301768A
Application number: CN202410395426.5A
Authority: CN
Inventors: 苟伟; 韩祥辉; 石靖; 寇帅华; 刘星
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2024-04-02
Filing date: 2024-04-02
Publication date: 2024-07-05

Abstract

The embodiment of the application discloses a parameter configuration method, equipment and a storage medium. Comprising the following steps: receiving the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value; determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type of symbols include a first type of symbol and a second type of symbol; multiplexing the UCI in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in a PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH. And the transmission of uplink control information is facilitated.

Description

Parameter configuration method, device and storage medium

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a parameter configuration method, equipment and a storage medium.

Background

In the prior art, uplink control information (Uplink Control Information, UCI) may be transmitted in a Physical Uplink shared channel (Physical Uplink SHARED CHANNEL, PDSCH), and in order to ensure the reliability of UCI transmission, one parameter is used as a resource for determining the use of UCI in the resources of PUSCH. However, when PUSCH transmission is performed in SBFD symbols and non-SBFD symbols (or CCFD symbols and non-CCFD symbols) after sub-band Full Duplex (subband Full Duplex, SBFD) sub-band and Co-frequency simultaneous Full Duplex (CCFD) are introduced, the same parameters may need to be configured, and in general, interference is higher than interference in UL fractional Bandwidth (BWP), since adjacent frequency domain is used to transmit DL and adjacent frequency domain resources are not used to transmit DL.

Disclosure of Invention

The embodiment of the application provides a parameter configuration method, equipment and a storage medium. And the transmission of uplink control information is facilitated.

To achieve the above object, an embodiment of the present application provides a parameter configuration method, which is executed by a user equipment and includes:

receiving the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value;

Determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type of symbols include a first type of symbol and a second type of symbol;

Multiplexing the UCI in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in a PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH.

To achieve the above object, an embodiment of the present application provides a parameter configuration method, which is executed by a base station, including:

transmitting the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value;

receiving the UCI multiplexed in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in a PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH.

In order to achieve the above object, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor executes the program to implement a parameter configuration method according to the embodiment of the present application.

In order to achieve the above object, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements a parameter configuration method according to an embodiment of the present application.

The embodiment of the application discloses a parameter configuration method, equipment and a storage medium. Comprising the following steps: receiving the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value; determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type symbols include a first type symbol and a second type symbol; multiplexing UCI in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in the PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH. And the transmission of uplink control information is facilitated.

Drawings

FIG. 1 is a flowchart of a method for configuring parameters according to an embodiment of the present application;

fig. 2 is a schematic diagram of a UCI provided in an embodiment of the present application in which a part of UCI is also punctured/canceled for transmission;

Fig. 3 is a schematic diagram of multiplexing UCI in the remaining resources in the PUSCH according to an embodiment of the present application;

FIG. 4 is a flowchart of a method for configuring parameters according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a parameter configuration device according to an embodiment of the present application;

Fig. 6 is a schematic structural diagram of a parameter configuration device according to an embodiment of the present application;

Fig. 7 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

To improve UL coverage, reduce latency and increase capacity of UL transmissions for TDD systems, sub-band full duplex techniques (subband full duplex, SBFD) are proposed for RRC connected UEs.

In some or all DL symbols/slots, one UL subband and at most 2 DL subbands are configured. For example, the UL subband and the DL subband are required to be configured based on DL BWP and UL BWP pairs that are required to have the same center frequency. In the frequency domain, the frequency domain resources of the UL subband and the frequency domain resources of the DL subband are generally considered to be configured within the frequency domain of DL BWP. DL BWP is valid in DL symbols or slots. But in the frequency domain, the frequency domain resources of the UL subband and the frequency domain resources of the DL subband may also be configured outside the DL BWP, e.g., part or all of the frequency domain resources of the UL subband and the frequency domain resources of the DL subband are outside the frequency domain range of the DL BWP.

The UL subband and the DL subband are also referred to as SBFD subbands, i.e. one SBFD subband is configured in DL BWP in DL symbols/slots, the SBFD subband typically comprising at least one DL subband and one UL subband.

For example, in a 100MHz TDD carrier, 20 consecutive RBs are configured as the UL subband in DL BWP in DL symbols/slots, and the remaining frequency domain resources of the DL BWP are DL subbands (gap may not be configured), or one DL subband is also configured in DL BWP in DL symbols/slots. Thus, in DL symbols/slots, the UL sub-band can be used for UL transmission and DL sub-band can be used for DL transmission. At the current stage, the sub-band full duplex technique includes the following features: the base station has the ability to perform both reception (in the UL sub-band) and transmission (in the DL sub-band) in the same time domain. The UE does not have the capability to perform reception (in DL subbands) and transmission (in UL subbands) simultaneously in the same time domain. Here, UL and DL subbands are configured in the same OFDM symbol/slot and are frequency-divided.

For convenience of description, some technical terms are as follows: the symbol configured with SBFD subbands is referred to as SBFD symbol. A slot containing SBFD symbols is called SBFD slot. The symbol for which the SBFD subbands are not configured is referred to as a non-SBFD symbol (i.e., a normal symbol). A slot that does not contain the SBFD symbols is called non-SBFD slot.

In order to further improve the system efficiency and the spectrum efficiency, the application provides a Co-frequency Co-time Full Duplex (CCFD) operation. First, CCFD subband resources are proposed, i.e., one CCFD subband is configured in the frequency domain for one carrier (the configuration of the CCFD subband may reuse the configuration of the following SBFD subbands). In one carrier, the base station configures one RB set as a CCFD subband on a continuous RB basis in the frequency domain and for CCFD operation, and configures some slots or symbols as CCFD subbands on a symbol basis or slots in the time domain and for CCFD operation. In this way, some time-frequency resources (denoted as resource a) are available for CCFD operation. Resource a, also referred to as the CCFD sub-band, includes resources that can be used for DL transmission and UL reception. At least from the base station side, resource a can be used for co-frequency simultaneous full duplex transmission. That is, the base station can simultaneously transmit DL signals and receive UL signals in resource a using the same time, the same frequency. The UE side may support only DL transmission and UL transmission of time division. In the present application, the symbol/slot configured with the resource a is referred to as a CCFD symbol/slot, and the symbol/slot not configured with the resource a is referred to as a non-CCFD symbol/slot (e.g., a conventional DL, UL or F symbol/slot).

The following related methods are provided based on SBFD subbands, but these methods can also be used based on CCFD subbands, e.g., only SBFD symbols/slots in these methods need to be replaced with CCFD symbols/slots, and non-SBFD symbols/slots with non-CCFD symbols/slots. Further, if the following related methods are provided based on UL subbands or DL subbands, the DL subbands and UL subbands can be replaced by CCFD subbands because the CCFD subbands can support DL reception and UL transmission simultaneously. Correspondingly, UCI multiplexed on PUSCH in SBFD subband/UL subband in SBFD symbols and UCI multiplexed on PUSCH in ULBWP in non-SBFD symbols can also be replaced by UCI multiplexed on PUSCH in CCFD subband in CCFD symbols and UCI multiplexed on PUSCH in UL BWP in non-CCFD symbols.

Fig. 1 is a flowchart of a method for configuring parameters, where the method is performed by a User Equipment (UE) side, and as shown in fig. 1, the method includes:

s110, receiving the first information and/or the second information.

Wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value. The first information may be information in physical layer signaling and the second information may be information in radio resource control (Radio Resource Control, RRC) signaling. The DCI triggering PUSCH may be understood as DCI scheduling or activating PUSCH, i.e., PUSCH scheduled by DCI and semi-static PUSCH activated by DCI. In this embodiment, the UE receives the physical layer signaling and RRC signaling issued by the base station.

S120, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information.

Wherein the type symbols include a first type symbol and a second type symbol. The first type of symbols are SBFD symbols and the second type of symbols are non-SBFD symbols; or the first type of symbol is a CCFD symbol and the second type of symbol is a non-CCFD symbol.

S130, UCI is multiplexed in PUSCH transmission based on the target beta offset value.

The target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in the PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH. I.e., UCI includes HARQ-ACK information, first partial CSI information, second partial CSI information, etc.

In one embodiment, if the first information includes: the DCI triggering PUSCH does not contain a beta offset value indication field, and the second information includes a beta offset value for configuring semi-static, a target beta offset value (hereinafter referred to as betaoffset) for PUSCH transmission of UCI in a type symbol is determined based on the first information and/or the second information, including at least one of: determining a semi-static beta offset value as a target beta offset value for PUSCH transmission of UL subbands in a first type of symbol for UCI transmission; or determining a semi-static beta offset value as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or determining the semi-static beta offset value as a target beta offset value for a first priority PUSCH transmission of UL subbands in a first type of symbol for UCI transmission; or determining a semi-static beta offset value as a target beta offset value for a first priority PUSCH transmission of UL BWP in a second type symbol for UCI transmission; or determining the semi-static beta offset value as a target beta offset value for a second priority PUSCH transmission of UL subbands in the first type of symbols for UCI transmission; or a semi-static beta offset value is determined as a target beta offset value for a second priority PUSCH transmission transmitting UL BWP in a second type symbol.

For example, taking SBFD techniques as an example, if a DCI format does not contain betaoffset indication field and the DCI format triggers a PUSCH transmission from UE and the UE is configured by higher layer signaling to be semi-static with betaoffsets value, the UE determines betaoffset that the PUSCH transmission in SBFD symbols and in non-SBFD symbols takes into account the following mechanism: the base station configures a semi-static betaoffset value for the UE to be transmitted in the UL subband in SBFD symbols for the PUSCH transmission, and the UE performs UCI multiplexing in the PUSCH transmission based on the betaoffset value. Or the base station configures the UE with a semi-static betaoffset value to be transmitted in UL BWP of non-SBFD symbols for the PUSCH transmission, and the UE performs UCI multiplexing in the PUSCH transmission based on the betaoffset value.

Wherein the base station and the UE agree that if the PUSCH transmission is performed in the UL subband in SBFD symbols, HARQ-ACK, CSI-1 (first partial CSI) and CSI-2 (second partial CSI) are transmitted in the PUSCH based on betaoffset, betaoffset2 and betaoffset, respectively. If the PUSCH transmission is performed in UL BWP in non-SBFD symbols, HARQ-ACK, CSI-1 (first partial CSI) and CSI-2 (second partial CSI) transmission in the PUSCH is based on betaoffset-1, betaoffset2-1 and betaoffset-1, respectively.

For example, if a DCI format does not contain betaoffset indication field and the DCI format triggers a PUSCH transmission with priority 1 or priority 0 from the UE and the UE is configured by higher layer signaling to be semi-static with betaoffsets values, the UE determines betaoffset values as PUSCH transmissions in SBFD symbols and in non-SBFD symbols, taking into account the following mechanism: the base station configures a semi-static betaoffset value for the UE to be transmitted in the UL subband in SBFD symbols for the PUSCH transmission with priority 1, and the UE performs UCI multiplexing in the PUSCH transmission based on the betaoffset value.

Wherein the betaoffset value is h_ betaoffset1 for HARQ-ACK information having priority 1 to be transmitted in the PUSCH.

Optionally, the base station configures the UE with a semi-static betaoffset value to be transmitted in the UL subband in SBFD symbols for the PUSCH transmission with priority 0, and the UE performs UCI multiplexing in the PUSCH transmission based on the betaoffset value.

Wherein the betaoffset value is l_ betaoffset1 for HARQ-ACK information having priority 0 to be transmitted in the PUSCH.

Optionally, the base station configures a semi-static betaoffset value for the UE to be transmitted in UL BWP in non-SBFD symbols for the PUSCH transmission with priority 1, and the UE performs UCI multiplexing in the PUSCH transmission based on the betaoffset value.

Wherein the betaoffset value is h_ betaoffset1-1 for HARQ-ACK information having priority 1 to be transmitted in the PUSCH.

The base station configures a semi-static betaoffset value for the UE to be transmitted in UL BWP in non-SBFD symbols for the PUSCH transmission with priority 0, and the UE performs UCI multiplexing in the PUSCH transmission based on the betaoffset value.

Here, the betaoffset value is l_ betaoffset1-1 for transmission of HARQ-ACK information having priority 0 in the PUSCH.

Wherein priority 1 is higher than priority 0.

In this embodiment, the base station and the UE agree that if the PUSCH transmission with priority 1 is performed in the UL subband in SBFD symbols, the HARQ-ACK transmission with priority 1 is based on h_ betaoffset1 in the PUSCH. If the PUSCH transmission with priority 1 is performed in UL BWP in non-SBFD symbols, HARQ-ACK with priority 1 is transmitted in the PUSCH based on h_ betaoffset1-1. If the PUSCH transmission with priority 0 is performed in the UL subband in SBFD symbols, the HARQ-ACK transmission with priority 0 is based on l_ betaoffset1 in the PUSCH. If the PUSCH transmission with priority 0 is performed in UL BWP in non-SBFD symbols, HARQ-ACK with priority 0 is transmitted in the PUSCH based on l_ betaoffset1-1.

Optionally, if the first information includes: the DCI triggering PUSCH does not contain a beta offset value indication field, and the second information includes a beta offset value for configuring semi-static. Determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, further comprising at least one of: if the beta offset value associated with the first type symbol is not configured, determining the beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; or if the beta offset value associated with the second type symbol is not configured, determining the beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; Or if the beta offset value with the first priority associated with the first type symbol is not configured, determining the beta offset value with the first priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the first priority for UL sub-bands in the first type symbol for UCI transmission; or if the beta offset value with the first priority associated with the first type symbol is not configured, determining the beta offset value with the second priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the first priority for UL sub-bands in the first type symbol for UCI transmission; Or if the beta offset value with the second priority associated with the first type symbol is not configured, determining the beta offset value with the first priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the second priority for UL sub-bands in the first type symbol for UCI transmission; or if the beta offset value with the second priority associated with the first type symbol is not configured, determining the beta offset value with the second priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the second priority for UL sub-bands in the first type symbol for UCI transmission; Or if the beta offset value with the first priority associated with the second type symbol is not configured, determining the beta offset value with the first priority associated with the first type symbol as a target beta offset value for PUSCH transmission with the first priority for UCI transmission of UL BWP in the second type symbol; or if the beta offset value with the first priority associated with the second type symbol is not configured, determining the beta offset value with the second priority associated with the first type symbol as a target beta offset value for PUSCH transmission with the first priority for UCI transmission of UL BWP in the second type symbol; Or if the beta offset value with the second priority associated with the second type symbol is not configured, determining the beta offset value with the first priority associated with the first type symbol as a target beta offset value for PUSCH transmission with the second priority for UCI transmission of UL BWP in the second type symbol; or if the beta offset value with the second priority associated with the second type symbol is not configured, determining the beta offset value with the second priority associated with the first type symbol as a target beta offset value for PUSCH transmission with the second priority for UCI transmission of UL BWP in the second type symbol.

Specifically, if UCI is transmitted in PUSCH as described above, if betaoffset value associated with SBFD symbols is not configured, then base station and UE agree that betaoffset value associated with non-SBFD symbols can be used for UCI transmission in PUSCH in SBFD symbols. If the betaoffset value associated with the non-SBFD symbol is not configured, then the base station and UE agree that the betaoffset value associated with the SBFD symbol can be used for UCI transmission in the PUSCH in the non-SBFD symbol.

Wherein UCI and PUSCH may be assumed to have the same priority index.

If the UCI is transmitted in PUSCH with priority 0 (or priority 1) as described above, if betaoffset value with priority 0 (or priority 1) associated with SBFD symbols (or non-SBFD symbols) is not configured, the base station and the UE agree that betaoffset value with priority 1 (or priority 0) associated with non-SBFD symbols (or SBFD symbols) can be used for UCI transmission in SBFD symbols (or non-SBFD symbols) in the PUSCH with priority 0 (or priority 1).

Specifically, if the betaoffset value with priority 0 associated with SBFD symbols is not configured, the base station and UE agree that the betaoffset value with priority 1 associated with non-SBFD symbols can be used for UCI transmission in SBFD symbols in the PUSCH with priority 0. If the betaoffset value with priority 0 associated with SBFD symbols is not configured, the base station and the UE agree that the betaoffset value with priority 0 associated with non-SBFD symbols can be used for UCI transmission in SBFD symbols in the PUSCH with priority 0. If the betaoffset value with priority 1 associated with SBFD symbols is not configured, the base station and UE agree that the betaoffset value with priority 1 associated with non-SBFD symbols can be used for UCI transmission in SBFD symbols in the PUSCH with priority 1. If the betaoffset value with priority 1 associated with SBFD symbols is not configured, the base station and UE agree that the betaoffset value with priority 0 associated with non-SBFD symbols can be used for UCI transmission in SBFD symbols in the PUSCH with priority 1.

Specifically, if the betaoffset value with priority 0 associated with the non-SBFD symbol is not configured, the base station and UE agree that the betaoffset value with priority 1 associated with the SBFD symbol can be used for UCI transmission in the non-SBFD symbol in the PUSCH with priority 0. If the betaoffset value with priority 0 associated with the non-SBFD symbol is not configured, the base station and the UE agree that the betaoffset value with priority 0 associated with the SBFD symbol can be used for UCI transmission in the non-SBFD symbol in the PUSCH with priority 0. If the betaoffset value with priority 1 associated with the non-SBFD symbol is not configured, the base station and the UE agree that the betaoffset value with priority 1 associated with the SBFD symbol can be used for UCI transmission in the non-SBFD symbol in the PUSCH with priority 1. If the betaoffset value with priority 1 associated with the non-SBFD symbol is not configured, the base station and UE agree that the betaoffset value with priority 0 associated with the SBFD symbol can be used for UCI transmission in the non-SBFD symbol in the PUSCH with priority 1.

In one embodiment, if the first information includes PUSCH being semi-static and the second information includes a beta offset value for configuring semi-static, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information includes at least one of: determining a beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; or determining a beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or determining a first priority beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of a first priority of UL subbands in the first type symbol for UCI transmission; or determining a second priority beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of a second priority for UL sub-bands in the first type symbol for UCI transmission; or determining a first priority beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of the first priority of UL BWP in the second type symbol for UCI transmission; or determining a second priority beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of a second priority for UL BWP in the second type symbol for UCI transmission.

For example, if a PUSCH transmission is semi-statically configured and a UE is configured with a semi-static betaoffset value, then for UCI transmission in the PUSCH in SBFD symbols, the base station and UE agree that the betaoffset value associated with SBFD symbols is used; or for the PUSCH transmission of UCI in the non-SBFD symbol, the base station and UE agree that the betaoffset value associated with the non-SBFD symbol is used.

For example, if the PUSCH transmission has priority 1 and UCI has priority 1, then the base station and UE agree that the betaoffset value of priority 1 associated with SBFD symbols is used for the UCI in the PUSCH transmission in SBFD symbols. If the PUSCH transmission has priority 0 and UCI has priority 0, then the base station and UE agree that a betaoffset value of priority 0 associated with SBFD symbols is used for the PUSCH transmission in SBFD symbols for the UCI. If the PUSCH transmission has priority 1 and UCI has priority 1, then the base station and UE agree that the betaoffset value of priority 1 associated with the non-SBFD symbol is used for the UCI transmission in the PUSCH in the non-SBFD symbol. If the PUSCH transmission has priority 0 and UCI has priority 0, then the base station and UE agree that a betaoffset value of priority 0 associated with the non-SBFD symbol is used for the UCI transmission in the PUSCH in the non-SBFD symbol.

In one embodiment, if the first information includes: the DCI format triggering PUSCH is 0_0, and the second information includes a beta offset value for configuring dynamic, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, including at least one of: determining a first value of a set of beta offset values associated with the first type of symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type of symbol for UCI transmission; or determining a first value of a set of beta offset values associated with the second type of symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; or determining a first value of a set of beta offset values of a first priority associated with the first type of symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type of symbol for UCI transmission; or determining a first value of a set of beta offset values of a second priority associated with the first type of symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type of symbol for UCI transmission; or determining a first value of a set of first priority beta offset values associated with the second type of symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; or determining a first value of a set of second priority beta offset values associated with the second type of symbol as a target beta offset value for PUSCH transmission for UL BWP in the second type of symbol for UCI transmission.

Wherein DCI format 0_0 does not contain betaoffset indication fields.

For example, if a PUSCH transmission is triggered by dci0_0 and the UE is configured betaoffset to be dynamic, then for the UCI transmission in the PUSCH in SBFD symbols, the base station and UE agree that the first value in the betaoffset value set associated with SBFD symbols is used. For the transmission of UCI in this PUSCH in the non-SBFD symbol, the base station and UE agree that the first value in the set of betaoffset values associated with the non-SBFD symbol is used.

For example, if a PUSCH transmission is triggered by dci0_0 and the UE is configured betaoffset to take on value dynamically, then the base station and UE agree that the first value in the set of betaoffset values of priority 1 associated with SBFD symbols is used for the UCI transmission of priority 1 in the PUSCH in SBFD symbols. For the transmission of UCI of priority 0 in this PUSCH in SBFD symbols, the base station and UE agree that the first value in the set of betaoffset values of priority 0 associated with SBFD symbols is used. For the transmission of UCI of priority 1 in this PUSCH in non-SBFD symbols, the base station and UE agree that the first value in the set of betaoffset values of priority 1 associated with non-SBFD symbols is used. For the transmission of UCI of priority 0 in this PUSCH in the non-SBFD symbol, the base station and UE agree that the first value in the set of betaoffset values of priority 0 associated with the non-SBFD symbol is used.

Wherein betaoffset values are a dynamic representation betaoffset set of values is configured. It is assumed here that sets of 2 betaoffset values are respectively configured and associated with SBFD symbols and non-SBFD symbols, respectively.

In one embodiment, if the second information includes: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value associated with a first type symbol and a beta offset value associated with a second type symbol; or configuring one set of two beta offset values, one associated with a first type of symbol and the other associated with a second type of symbol; the manner of determining the target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and the second information may be: determining a beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; the beta offset value associated with the second type symbol is determined as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission.

For example, if UCI is transmitted in PUSCH and in SBFD symbols or non-SBFD symbols, the base station configures a set of betaoffset values, each set containing a betaoffset value. Or the base station configures a betaoffset-valued set, and the set contains 2 betaoffset values, and the 2 betaoffset values are respectively associated with non-SBFD symbols and SBFD symbols, thereby reducing the set configuration.

In one embodiment, if the second information includes: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value and an adjustment parameter which are associated with a first type symbol; the manner of determining the target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information may be: determining a beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; another beta offset is determined from the beta offset value and the adjustment parameter associated with the first type of symbol and is determined as a target beta offset value for PUSCH transmission for UL BWP in the second type of symbol for UCI transmission. Or alternatively

In one embodiment, if the second information includes: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value and an adjustment parameter which are associated with a second type symbol; the manner of determining the target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information may be: determining a beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; and determining another beta offset according to the beta offset value and the adjustment parameter associated with the second type of symbol, and determining the other beta offset as a target beta offset value for PUSCH transmission of the UL sub-band in the first type of symbol for UCI transmission.

Wherein the adjustment parameter comprises an offset or scaling factor and the offset or scaling factor has a stable interference difference setting based on transmissions in UL subbands and UL BWP, which may be an average of historical interference.

Illustratively, the base station configures a set of betaoffset values and associates with non-SBFD symbols, and configures an offset/scaling factor, and obtains another betaoffset value based on the betaoffset values in the set and the offset/scaling factor and associates with SBFD symbols. Or the base station configures a betaoffset value set and associates with SBFD symbols, and configures an offset/scaling factor, and obtains another betaoffset value based on the betaoffset value in the set and the offset/scaling factor and associates with non-SBFD symbols.

In one embodiment, if the first information includes: the DCI triggering PUSCH includes a beta offset value indication field, and the second information includes: for configuring a dynamic beta offset value and configuring a beta offset value set associated with a first type symbol and a beta offset value set associated with a second type symbol, determining a target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information, comprising at least one of: determining a beta offset value determined from a beta offset value set associated with the first type symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; or determining a beta offset value determined from a beta offset value set associated with the second type symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission for UCI transmission of UL BWP in the second type symbol.

Wherein if the number of elements in the beta offset value set associated with the first type symbol is different from the number of elements in the beta offset value set associated with the second type symbol, the number of bits in the beta offset value indication field is determined according to the maximum number of elements.

For example, if a DCI format contains betaoffset indication fields and the DCI format triggers a PUSCH transmission and the UE is configured by higher layer signaling to be betaoffset values are dynamic, the UE determines betaoffset values as PUSCH transmissions in SBFD symbols and in non-SBFD symbols, taking into account the following mechanism: the base station configures a set 1 of betaoffset values for the UE, and the set 1 is associated with SBFD symbols, e.g., UCI is used when transmitted in PUSCH in UL subband in SBFD symbols, and the UE performs UCI multiplexing in the PUSCH transmission based on the determined one betaoffset value. The base station configures a set 2 of betaoffset values for the UE, and the set 2 is associated with non-SBFD symbols, e.g., UCI is used when transmitted in PUSCH in UL BWP in non-SBFD symbols, and the UE performs UCI multiplexing in the PUSCH transmission based on the determined one betaoffset value.

Wherein betaoffset set 1 is actually a corresponding set for each UCI type. For example, betaoffset values for HARQ-ACK information transmitted in PUSCH in SBFD symbols correspond to one set, betaoffset values for CSI-1 (first partial CSI) information transmitted in PUSCH in SBFD symbols correspond to one set, and betaoffset values for CSI-2 (second partial CSI) information transmitted in PUSCH in SBFD symbols correspond to one set. CSI-2 is decoded requiring inner information based on CSI-1. Accordingly, for non-SBFD symbols, betaoffset set 2 is actually a corresponding set for each UCI type. For example: the betaoffset value for HARQ-ACK information transmitted in PUSCH in non-SBFD symbols corresponds to one set, the betaoffset value for CSI-1 (first partial CSI) information transmitted in PUSCH in non-SBFD symbols corresponds to one set, and the betaoffset value for CSI-2 (second partial CSI) information transmitted in PUSCH in non-SBFD symbols corresponds to one set.

Wherein the betaoffset value is determined based on the betaoffset indication field corresponding set in the DCI format.

Wherein if the DCI includes only one betaoffset indication field, the UE determines that the PUSCH is transmitted in SBFD symbols, the UE uses the betaoffset indication field to determine betaoffset from betaoffset sets associated with SBFD symbols to perform UCI transmission in the PUSCH. If the DCI includes only one betaoffset indication field, the UE determines that the PUSCH is transmitted in a non-SBFD symbol, the UE uses the betaoffset indication field to determine betaoffset from a betaoffset set associated with a non-SBFD symbol to perform UCI transmission in the PUSCH.

If the number of elements in the set associated with SBFD symbols is not equal to the number of elements in the set associated with non-SBFD symbols and this results in betaoffset indicating that the field requires a different number of bits, e.g., one set contains 2 elements, betaoffset indicates that the field only needs 1bit and another set contains 4 elements, betaoffset indicates that the field needs 2bits, betaoffset indicates that the field is determined by the maximum number of bits and 0 is inserted to occupy the bit before the smaller number of bits. For example, in the above example, betaoffset indicates that the field is 2bits, and the UE determines that the high 1bit of the 2bits is 0 when determining a betaoffset value from the set of 2 elements.

In one embodiment, the second information further comprises: configuring a control resource set associated with the first type symbol and a control resource set associated with the second type symbol, determining a target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information, including at least one of: if the DCI corresponding to the beta offset value indication field is received from the control resource set associated with the first type symbol, the beta offset value determined by the beta offset value indication field from the beta offset value set associated with the first type symbol is determined as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; if the DCI corresponding to the beta offset value indication field is received from the control resource set associated with the second type symbol, the beta offset value determined by the beta offset value indication field from the beta offset value set associated with the second type symbol is determined as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission.

For example, if the DCI includes only one betaoffset indication field, it may be that the base station and the UE agree on corresponding CORESET for DL or UL transmission in SBFD symbols and DL or UL transmission configuration/association in non-SBFD symbols, respectively. That is, for example, if the PUSCH is triggered by a DCI for transmission in SBFD symbols, the DCI should be transmitted in CORESET associated with SBFD symbols. If the PUSCH is triggered by the DCI to be transmitted in a non-SBFD symbol, the DCI should be transmitted in CORESET associated with a non-SBFD symbol.

Thus, if the UE receives a DCI triggering PUSCH from CORESET associated with SBFD symbols, then since the DCI is received from CORESET associated with SBFD symbols, the UE determines: betaoffset in the DCI indicates that the field should determine betaoffset value from the betaoffset set associated with the SBFD symbol. Or if the UE receives a DCI triggering PUSCH from CORESET associated with a non-SBFD symbol, then since the DCI is received from CORESET associated with a non-SBFD symbol, the UE determines: betaoffset in the DCI indicates that the field should determine betaoffset value from the betaoffset set associated with the non-SBFD symbol.

In one embodiment, the first information further comprises: the DCI includes another beta offset value indication field, where one beta offset value indication field is associated with a first type symbol, and the other beta offset value indication field is associated with a second type symbol as a first beta offset value indication field, and as a second beta offset value indication field, a manner of determining a target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information may be: determining a beta offset value determined from a set of beta offset values associated with the first type symbol based on the first beta offset value indication field as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; the beta offset value determined from the set of beta offset values associated with the second type of symbol based on the second beta offset value indication field is determined as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission.

Illustratively, the base station and the UE agree that another betaoffset indication field is added to the DCI, so that the DCI includes 2 betaoffset indication fields and is associated with a betaoffset set corresponding to SBFD symbols and a betaoffset set corresponding to non-SBFD symbols, respectively. Thus, the UE receives a DCI triggering a PUSCH, determines a symbol type (SBFD symbols or non-SBFD symbols) of the PUSCH to be transmitted, and then determines betaoffset value from a set corresponding to the determined symbol type based on betaoffset indication field corresponding to the determined symbol type, thereby performing UCI transmission in the PUSCH.

This approach can solve the problem that UCI when the PUSCH is transmitted only in one SBFD slot or non-SBFD slot is multiplexed on the PUSCH, and also that UCI when the PUSCH is transmitted across different types of slots (e.g., across SBFD slot and non-SBFD slot, i.e., the PUSCH transmission is with repetition, or periodicity). For example, one PUSCH transmission is transmitted across 2 slots. The first slot is SBFD slot and the PUSCH transmission is in SBFD symbols. The second slot is non-SBFD slot and the PUSCH transmission is in the non-SBFD symbol. Further assuming that UCI is transmitted in the PUSCH in the 2 slots, respectively, the base station and the UE agree that the UE determines betaoffset values based on the set associated with the symbol type and betaoffset indication field, respectively, and completes UCI transmission in the PUSCH in the first slot and the second slot, respectively, using the determined betaoffset values.

In one embodiment, if one PUSCH transmission is transmitted across slots of different types of symbols, the first information further includes: configuring an adjustment parameter, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, including at least one of: determining a beta offset value determined from a beta offset value set associated with the first type symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; determining a beta offset value determined according to the target beta offset value and the adjustment parameter as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or alternatively

Determining a beta offset value determined from a beta offset value set associated with the second type of symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; and determining the beta offset value determined according to the target beta offset value and the adjustment parameter as the target beta offset value of PUSCH transmission of the UL sub-band in the first type symbol for UCI transmission.

Illustratively, if the DCI contains one betaoffset indication field and if one PUSCH transmission is transmitted across different types of slots, then different betaoffset values are determined to perform UCI transmission in PUSCH in different symbol types in one of the following ways: the base station configures or agrees with the UE an offset or scaling factor. If the UE determines that one betaoffset value is UCI for transmission in PUSCH in SBFD symbols, the UE derives another betaoffset value as UCI for transmission in PUSCH in non-SBFD symbols based on the offset or scaling factor. If the UE determines that one betaoffset value is UCI for transmission in PUSCH in non-SBFD symbols, the UE derives another betaoffset value for UCI for transmission in PUSCH in SBFD symbols based on the offset or scaling factor.

In one embodiment, if one PUSCH transmission is transmitted across slots of different types of symbols, the first information includes: configuring the beta offset value indication field to be associated with the beta offset value set associated with the first type symbol and the beta offset value set associated with the second type symbol at the same time, the method for determining the target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information may be: determining a beta offset value determined from a beta offset value set associated with the first type symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; the beta offset value determined from the beta offset value set associated with the second type of symbol based on the beta offset value indication field is determined as a target beta offset value for PUSCH transmission for UCI transmission of UL BWP in the second type of symbol.

Illustratively, if the DCI contains one betaoffset indication field and if one PUSCH transmission is transmitted across different types of slots, then different betaoffset values are determined to perform UCI transmission in PUSCH in different symbol types in one of the following ways: betaoffset in the DCI indicates that a field associates two sets of betaoffset values simultaneously. For example, the set associated with SBFD symbols and the set associated with non-SBFD symbols are associated with the betaoffset indication field simultaneously, and the UE uses the betaoffset indication field to determine betaoffset values from the two sets, respectively, and for the corresponding symbol types, respectively. For example, betaoffset indicates that the field has a value of 0, the UE determines the first one betaoffsets from the two sets, respectively, which are used for UCI transmission in PUSCH in SBFD symbols and non-SBFD symbols, respectively.

Alternatively, if the PUSCH transmission has priority 1 (or priority 0) and UCI has priority 1 (or priority 0), then for the UCI transmission in the PUSCH in SBFD symbols (or non-SBFD symbols), the base station and UE agree to determine a betaoffset value from the set of betaoffset values of priority 1 (or priority 0) associated with SBFD symbols (or non-SBFD symbols) according to the betaoffset indication field in the DCI.

In one embodiment, the first information further comprises at least one of: associating the same time slot interval k, the same time slot interval k set or the same time domain resource allocation table for the first type of symbols and the second type of symbols; the method also comprises the following steps: the slot position where the PUSCH triggered by the DCI is transmitted is determined based on at least one of the same slot interval, the same set of slot intervals, or the same time domain resource allocation table.

Wherein, the time slot interval k satisfies: if the DCI triggering the PUSCH is received in the time slot n, the time slot in which the PUSCH triggered by the DCI is positioned is the time slot n+k; the time domain resource allocation table refers to a PUSCH time domain resource allocation table, where the table includes at least one column that is a slot interval and at least two columns that are symbol positions of the PUSCH.

For example, for a PUSCH triggered by DCI, the UE can determine the slot position and symbol position of the triggered PUSCH based on the time domain resource allocation in the DCI. The time domain resource allocation contains a slot interval k, for example, the DCI is transmitted at slot n, and the PUSCH scheduled by the DCI is transmitted at slot n+k. However, after SBFD symbols are introduced, considering that SBFD symbols and non-SBFD symbols are configured with k independently, after the UE receives the DCI, it is unclear for the UE whether k in the time domain resource allocation in the DCI should be parsed according to a k value corresponding to SBFD symbols or according to a k value corresponding to non-SBFD symbols, and since the k value cannot be determined, the UE cannot determine a slot position of a PUSCH based on the time domain resource allocation in the DCI, so that the UE cannot determine a symbol position where the PUSCH is transmitted, and thus cannot determine a symbol type of a symbol where the PUSCH is located. To solve the above problem, the base station and the UE agree that the same k value or k set is configured as SBFD symbols and non-SBFD symbols, or that the same time domain resource allocation table is configured as SBFD symbols and non-SBFD symbols, or that one time domain resource allocation table is shared by SBFD symbols and non-SBFD symbols, where the time domain resource allocation table includes a plurality of columns, one of which is a k value, so that at least one column corresponding to the k value is the same between SBFD symbols and non-SBFD symbols.

In one embodiment, the method further comprises the steps of: if part of the time domain or frequency domain resources of the PUSCH are punctured/canceled, UCI is transmitted only in the remaining resources of the PUSCH; wherein the resources used by the UCI are determined based on the determined target beta offset value, the number of bits of the UCI, and the PUSCH remaining resources, and the UCI is mapped in the PUSCH remaining resources for transmission.

Optionally, if part of the time domain or frequency domain resources of the PUSCH are punctured/cancelled and the PUSCH is triggered to be transmitted in the first type symbol, UCI is multiplexed in the remaining resources of the PUSCH.

Wherein, the remaining resources of the PUSCH are resources of which the PUSCH is located in the time domain and/or the frequency domain of the UL sub-band.

Specifically, for the case where one PUSCH is partially punctured/cancelled, especially for the case where a part of frequency domain resources of the PUSCH is punctured/cancelled, it may also cause UCI (especially HARQ-ACK) transmitted in the resources of the punctured/cancelled PUSCH to be punctured/cancelled, which may eventually result in reduced reliability of UCI, especially when UCI is HARQ-ACK information, which has a great influence. Thus, improvements are given below.

The base station and the UE agree that if a part of the time domain or frequency domain resources of the PUSCH is punctured/cancelled, i.e., the PUSCH cannot be transmitted in the part of the time domain or frequency domain resources, UCI is transmitted in the PUSCH only in the remaining resources of the PUSCH for UCI transmission in the PUSCH. One PUSCH is scheduled for transmission in the UL subband in SBFD symbols, but due to PUSCH resource allocation limitations, some of the PUSCH resources are beyond the frequency domain of the UL subband, e.g., as shown in fig. 2, a portion of UCI is punctured/cancelled for transmission. For the above case, the base station and the UE determine the remaining resources of the PUSCH, i.e., resources in the UL subband frequency domain, and multiplex UCI in the remaining resources in the PUSCH. Such as shown in fig. 3.

Specifically, when the UE determines the resources occupied by the UCI, the UE is only based on the remaining resources of the PUSCH, i.e., the resources of the UL subband. For example, in a calculation formula for calculating resources used for UCI in an existing protocol (TS 38.212), a part of parameter meanings are re-interpreted. For example, one of the existing formulas is represented as follows:

Wherein O is the number of bits of HARQ-ACK, the first partial CSI or the second partial CSI;

If O is greater than or equal to 360, L=11, then L is the number of CRC bits for the HARQ-ACK, the first partial CSI, or the second partial CSI;

the beta offset value corresponding to the HARQ-ACK, the first partial CSI or the second partial CSI;

c _UL-SCH is the number of code blocks of the UL-SCH in the PUSCH transmission;

is the scheduled bandwidth of PUSCH transmission, expressed in number of subcarriers; The number of subcarriers carrying PTRS in OFDM symbols in PUSCH transmission; Is the number of resource elements available for transmitting UCI in OFDM symbol/in PUSCH transmission The total number of OFDM symbols for PUSCH, including all OFDM symbols for DMRS; for any OFDM symbol carrying DMRS of PUSCH,For any OFDM symbol that does not carry a DMRS for PUSCH,

Alpha is a scaling parameter configured by an upper layer;

l ₀ is the symbol index of the first OFDM symbol carrying no PUSCH DMRS after the first DMRS symbol in PUSCH transmission.

There are a number of formulas for calculating UCI resources in the existing protocol (TS 38.212), which are applicable to different situations. All of these formulas haveAnd the following is providedThe calculation method is as described above, so the method herein is applicable to all formulas for calculating UCI resources. For example, to be used therein for calculationParameters in the formula of (2)And the meaning of (c) is modified, for example,Represents PUSCH resources in UL subbands in the scheduled bandwidth of one PUSCH transmission, and is represented by the number of subcarriers. That is to say that the first and second,Originally representing the scheduled bandwidth, but now only the resources remaining in the scheduled bandwidth after the resources outside the UL sub-band are removed, i.e. the resources located in the UL sub-band.

Can also be described as: to the prior artShould be interpreted as the number of valid sub-carriers in the bandwidth of the scheduled PUSCH. I.e., subcarriers beyond the frequency domain resources of the UL subband are considered invalid and subcarriers within the frequency domain resources in the UL subband are valid. Alternatively, if the UE is configured with a UL subband and the PUSCH of the UE is transmitted in the UL subband, the UE always determines an effective resource (at least a frequency-domain effective resource) among the resources allocated for the PUSCH as a resource for the PUSCH, and uses the PUSCH resource (here, the effective resource, not the allocated resource) to determine the UCI resource from among the PUSCH resources based on the above formula. Further, when UCI is transmitted in the PUSCH-valid resource, the existing UCI mapping rule is reused. According to the technical scheme of the embodiment, the first information and/or the second information are received; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value; determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type symbols include a first type symbol and a second type symbol; multiplexing UCI in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in the PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH. And the transmission of uplink control information is facilitated.

In one embodiment, the manner of multiplexing the UCI in PUSCH transmission based on the target beta offset value may be: for a connected state user equipment or an idle state device, if an intersection resource of an UL subband and an activated UL BWP in a frequency domain is greater than 0, multiplexing the UCI in PUSCH transmission based on at least one of the following factors: physical resources performing the transmission; wherein the physical resources include UL subbands or available PRBs. Or performing resource allocation corresponding to transmission; wherein the resource configuration comprises: TDRA of UL subband, TDRA of UL BWP is activated, TDRA of available PRB associations. Or parameters used for performing the transmission. Wherein the parameters include: SCS of UL subband, SCS of available PRB, SCS of activated UL BWP.

If the intersection resource of the UL subband and the activated UL BWP in the frequency domain is equal to 0, multiplexing the UCI in PUSCH transmission based on at least one of the following factors: physical resources performing the transmission; wherein the physical resources include UL subbands. Or performs resource allocation corresponding to the transmission. Wherein the resource configuration comprises: TDRA of UL subband, TDRA of UL BWP is activated, TDRA of available PRB associations. Or performing parameters used for transmission; wherein the parameters include: SCS of UL subband, SCS of available PRB, SCS of activated UL BWP. Or no transmission is performed.

Some methods for transmission in SBFD subbands (including UL and DL subbands) are provided below.

In the related art, the UE can be configured with one initial DL/UL BWP and can configure 4 DL/UL BWPs but activate only one DL/UL BWP for DL reception and UL transmission.

Further, since the configuration of DL/UL BWP is optional, if active DL/UL BWP is not configured, the UE uses the initial DL/UL BWP for DL reception and UL transmission, and also uses parameters (e.g., SCS) and resource configuration (e.g., DL TDRA table, UL TDRA table, common PUCCH resource) etc. of the initial DL/UL BWP configured.

Further, in some cases, the UE has the active DL/UP BWP configured but not configured with the corresponding time domain resource configuration, e.g., after the active DL BWP is configured but without the corresponding TDRA table configured, in which case the UE uses the TDRA table corresponding to the initial DL BWP; or for example, after the activated UL BWP is configured, but the corresponding PUCCH-config or PUSCH TDRA table is not provided, the UE may use the cell common PUCCH resource or the TDRA table corresponding to the initial UL BWP. The only time domain resource configuration described above uses another BWP (or is said to fall back to another BWP associated time domain resource configuration), and the actual transmission is still in the active DL/UL BWP.

Therefore, based on the above analysis, after the SBFD sub-band configuration, but the "available PRB" is 0 as described above may also occur, and the corresponding transmission mechanism, or UE behavior (or backoff mechanism) needs to be considered as well.

For the possible reasons that result in an available PRB of 0:

1) The activated DL/UL BWP is not configured. The existing protocols can support, and also have corresponding base station and UE behaviors.

2) The DL subbands are not configured and only the UL subbands are configured. This is currently only possible, depending on the progress of the discussion that follows.

The active DL/UL BWP is configured, the DL sub-band and UL sub-band are also configured, but there is still no frequency domain intersection. The probability of occurrence of this situation is not large. There is a need for a base station that does not want to schedule one SBFD UE DL or UL sub-band based to achieve this in a way that there is no intersection, otherwise as in the current case the SBFD UE can only transmit in terms of DL and UL sub-bands in SBFD symbols. Of course, the introduction of a signaling is also conceivable to achieve this object.

For downstream reception

Definition of available PRBs in both cases.

(1) The "available PRB" is defined based on the frequency domain intersection resources of the initial DL BWP and DL subband and is used for downlink reception (including SIBs (broadcast) and UE-level DL reception (including msg2/msgB/msg4 in random access procedure, and SIBs in non-broadcast form)).

(2) The "available PRBs" are defined as: if the UE is not configured with an activated DL BWP, the UE considers the intersection of the initial DL BWP and the DL sub-band as an "available PRB" for downlink reception (including SIBs (broadcast) and DL reception at the UE level (including msg2/msgB/msg4, and SIBs in non-broadcast form)).

Case 1: for RRC connected UEs.

In SBFD symbols, if the intersection resource of DL subbands and activated DL BWP in the frequency domain (DL "available PRB") is greater than 0, msg2/msgB/msg 4/PDSCH containing SIB (UE triggered, non-broadcast mechanism) is transmitted from the base station or received by the UE based on the following factors:

① Physical resources to perform transmission (e.g., in DL subbands, in active DL BWP, or in available PRBs);

② Performing a transmission corresponding resource configuration (e.g., the transmission corresponding resource is determined to be DL subband based TDRA, activate DL BWP TDRA, available PRB association TDRA (less likely));

③ Parameters used for performing the transmission, e.g., SCS of DL subband, SCS of available PRBs, SCS of activated DL BWP.

In SBFD symbols, if the intersection resource of DL subbands and activated DL BWP in the frequency domain (DL "available PRB") is equal to 0, msg2/msgB/msg 4/PDSCH containing SIB (UE triggered, non-broadcast mechanism) is transmitted from the base station or received by the UE based on the following factors:

① Physical resources to perform transmission (e.g., in DL subbands, or in active DL BWP);

Case 2: idle state UE (connection state UE may also be)

In SBFD symbols, if the intersection resource of DL subband and cell initial DL BWP in frequency domain (DL "available PRB") is greater than 0, msg2/msgB/msg 4/PDSCH (broadcast) containing SIB is transmitted from the base station or received by the UE based on the following factors:

① Physical resources (e.g., in DL subbands, or in initial DL BWP, or in available PRBs) to perform the transmission;

② Performing a transmission corresponding resource configuration (e.g., the transmission corresponding resource is determined to be based on TDRA of DL subbands, TDRA of initial DL BWP, TDRA (less likely) of available PRB associations);

③ Parameters used for performing the transmission, e.g., SCS of DL subband, SCS of available PRBs, SCS of initial DL BWP.

In SBFD symbols, if the intersection resource of DL subband and cell initial DL BWP in frequency domain (DL "available PRB") is equal to 0, msg2/msgB/msg 4/PDSCH (broadcast mechanism) containing SIB is transmitted from the base station or received by the UE based on the following factors:

① Physical resources to perform transmission (e.g., in DL subbands, or in initial DL BWP);

Note that: in the above case 1 and case 2 rules, if msg 2/4/PDSCH containing SIB is transmitted in a DL subband, the base station and UE consider that no more than m RBs in the DL subband are used, where m is equal to the number of RBs of the initial DL BWP. The method is suitable for connected-state UE and idle UE.

For upstream transmission

PRB definition available in both cases

(1) The "available PRBs" are defined based on the frequency domain intersection resources of the initial UL BWP and UL sub-bands and are used for uplink transmission (UL transmission including msg1/msgA in random access procedure and UE level (PUCCH including msg3 and msg4/msgB in random access procedure)).

(2) The "available PRBs" are defined as: if the UE is not configured with activated UL BWP, the UE considers the intersection of the initial UL BWP and UL sub-bands as "available PRBs" for uplink reception (msg 1/msgA and UL transmissions at the UE level (PUCCH including msg3 and msg 4/msgB)).

Case 1: for connected UEs

In SBFD symbols, if the intersection resource of UL subband and activated UL BWP in frequency domain (UL "available PRB") is greater than 0, the UL transmission at msg1/msgA and UE level (PUCCH including msg3 and msg 4/msgB) is received by the base station or transmitted from the UE based on the following factors:

① Physical resources (e.g., in UL subbands, or in available PRBs) to perform the transmission;

② Performing a transmission corresponding resource configuration (e.g., the transmission corresponding resource is determined to be based on TDRA of UL subband, TDRA of UL BWP is activated, TDRA (less likely) of available PRB associations);

③ Parameters used for performing the transmission, e.g., SCS of UL subband, SCS of available PRBs, SCS of activated UL BWP.

Note that: all cases limit the number of PRBs that can be used not to exceed the number of PRBs of the initial UL BWP.

In SBFD symbols, if the intersection resource of UL subband and activated UL BWP in frequency domain (UL "available PRB") is equal to 0, msg1/msgA and UL transmission at UE level (PUCCH including msg3 and msg 4/msgB) are received by the base station or transmitted from the UE based on the following factors:

① Physical resources (e.g., in UL subbands) that perform transmission;

④ The above transmission is not performed in SBFD symbols.

Case 2: for idle UE (connectivity may also be)

In SBFD symbols, if the intersection resource of the UL sub-band and the initial UL BWP in the frequency domain (UL "available PRB") is greater than 0, the UL transmissions at msg1/msgA and UE level (PUCCH including msg3 and msg 4/msgB) are received by the base station or transmitted from the UE based on the following factors:

In SBFD symbols, if the intersection resource of the UL sub-band and the initial UL BWP in the frequency domain (UL "available PRB") is equal to 0, the UL transmissions at msg1/msgA and UE level (PUCCH including msg3 and msg 4/msgB) are received by the base station or transmitted from the UE based on the following factors:

① Physical resources (e.g., in UL subbands) that perform transmission;

④ The above transmission is not performed in SBFD symbols.

Note that: in the above case 1 and case 2 rules, if msg3 is transmitted in the UL subband, the base station and UE consider that no more than n RBs in the UL subband are used, where n is equal to the number of RBs of the initial UL BWP. The method is suitable for connected-state UE and idle UE.

In the presence of SBFD subbands and non-SBFD symbols, multiple occasions of a DL reception or UL transmission are located in different types of symbols/slots, respectively, or one occasin is located in different types of symbols/slots at the same time, then how the DL reception or UL transmission should be performed.

After supporting SBFD subbands (including UL subbands or DL subbands), the OFDM symbols/slots can be separated into two types, denoted as first type symbol/slot and second type symbol/slot (the second type is SBFD symbols if the first type is non-SBFD symbols, or vice versa), as is clear from the related concepts described above. The SBFD symbol contains DL subbands and UL subbands, which are typically composed of consecutive RBs, up to 2 DL subbands, each DL subband also being composed of consecutive RBs. non-SBFD symbols are symbols that are not configured for SBFD subbands. It is apparent that DL reception or UL transmission in SBFD symbols are interfered with each other, whereas DL reception or UL transmission is performed only in non-SBFD symbols, so there is no interference between UL transmission and DL reception.

For one DL reception or UL transmission, if they are periodic and/or with repeated transmission, the one DL reception or UL transmission has multiple transmissions occasions, some of these occasions are located only in SBFD symbols, some are located only in non-SBFD symbols, and some are located simultaneously in SBFD symbols and non-SBFD symbols (e.g., the Occasion contains 10 symbols, with the first 5 symbols located in SBFD symbols, the last 5 symbols located in non-SBFD symbols, or vice versa). In this case, a solution mechanism is provided below to complete the corresponding DL reception or UL transmission.

One DL reception or UL transmission described above may include:

1) With repeated transmissions: PDSCH/PUSCH/PUCCH repetitions. For example, one PDSCH/PUSCH/PUCCH transmission is configured to repeat 4 times, i.e., the transmission needs to be performed in 4 occasions times, then, since the configuration of SBFD symbols does not exactly match the periodicity and resources of the SPS PDSCH/CG PUSCH, some occasions are located only at SBFD symbols, some occasions are located only at non-SBFD symbols, or some occasions are located at both SBFD symbols and non-SBFD symbols.

2) Periodic transmission: SPS PDSCH/configuration authorized PUSCH, periodic/semi-PERSISTENT SRS/CSI-RS/PUCCH/PDCCH. For example, since the configuration of SBFD symbols does not exactly match the periodicity and resources of SPS PDSCH/CG PUSCH/SRS/CSI-RS/PUCCH/PDCCH, some SPS PDSCH/CG PUSCHSRS/CSI-RS/PUCCH/PDCCH occasions are located only at SBFD symbols, some SPS PDSCH/CG PUSCHSRS/CSI-RS/PUCCH/PDCCH occasions are located only at non-SBFD symbols, or some SPS PDSCH/CG PUSCHSRS/CSI-RS/PUCCH/PDCCH occasions are located at both SBFD symbols and non-SBFD symbols.

3) The transport block corresponding to a transmission spans multiple slots, TBoMS. For example, one larger TB is configured to perform transmission in 4 slots, so that the transmission has 4 occasions slots in 4 slots, respectively. Then, some occasions are located only at SBFD symbols, some occasions are located only at non-SBFD symbols, or some occasions are located at both SBFD symbols and non-SBFD symbols, since the SBFD symbols' configuration does not exactly match the periodicity and resources of the SPS PDSCH/CG PUSCH.

4) Multiple PUSCH/PDSCH scheduled by one DCI are in different slots, for example, one DCI schedules 4 PDSCH/PUSCH and one PUSCH/PUSCH corresponds to one TB, so that the 4 PDSCH/PUSCH scheduled has 4 occasions but one TB corresponding to each occasions. Since the SBFD symbols are configured to not exactly match the periodicity and resources of the SPS PDSCH/CG PUSCH, some occasions are located only at SBFD symbols, some occasions are located only at non-SBFD symbols, or some occasions are located at both SBFD symbols and non-SBFD symbols.

In general, DL reception/UL transmission of different types of symbols/slots is performed based on respective configured corresponding parameters, for example, power control related parameters, beam related parameters, precoding related parameters, MCS, aggregation level of PDCCH, TCI status configuration parameters, QCL relation configuration parameters, etc. There are also some cases where DL reception/UL transmission with one of the types of symbols/slots is not configured, for example.

For one DL reception/UL transmission, if it is configured to be associated with a first type of symbol/slot, and if one of its occalations is configured/determined to be located only in a second type of symbol/slot, then at least one of the following is supported:

1) The UE does not expect the corresponding DL reception/UL transmission to be performed in the occalation, and the base station does not perform the corresponding DL reception/UL transmission in the occalation.

2) The base station and the UE agree that the corresponding DL reception/UL transmission is performed in the occalation, but that the transmission parameters used are those that were configured when the DL reception/UL transmission was transmitted in the second type of symbol/slot (it is assumed here that the DL reception/UL transmission was configured in association with the first type of symbol/slot, but that the base station still configures or agrees with the transmission parameters used for transmission in the second type of symbol/slot).

3) The base station and the UE agree that the corresponding DL reception/UL transmission is performed in the occalation, but that the transmission parameters used are at least one of the following:

a. If the DL reception/UL transmission is repetition-bearing, the same transmission parameters as the first repetition transmission are used, or the transmission parameters configured when the DL reception/UL transmission is transmitted in the first type of symbol/slot are used, or the transmission parameters configured when the DL reception/UL transmission is transmitted in the second type of symbol/slot are used (if any). The transmission parameters here include at least one of: power control related parameters, beam related parameters (e.g., TCI (Transmission Configuration Indicator) relation, quasi Co-sited QCL (Quasi Co-Location) relation), precoding related parameters, MCS table, UCI multiplexed betaoffset parameters, maximum RANK number, DMRS mapping type.

B. If the DL reception/UL transmission is PDCCH, or CORESET/SEARCHSPACE of PDCCH, the transmission parameters configured at the time of transmission of the first type of symbol/slot are used, or the transmission parameters configured at the time of transmission of the second type of symbol/slot (if any) are used. The transmission parameters here include at least one of: aggregation level (aggregation level) related parameters, and the number of PDCCH CANDIDATES per aggregation level.

C. If the DL reception/UL transmission is PUSCH repetition Type B (defined at TS 38.214), the occipital is split into two UL transmissions because the symbols corresponding to the occipital include a first type of symbol and a second type of symbol. Wherein the two UL transmissions are each in a different type of symbol, i.e., the occalasion is originally one nominal repetition, but since the symbol types corresponding to the occalasion corresponding repetition are different, the one nominal repetition is divided into two actual repetition transmissions and is performed in two symbol types in the symbol corresponding to the occalasion, respectively. Wherein the actual retransmission is performed in the second type of symbol, and the transmission parameters used for the retransmission include at least one of: if the DL reception/UL transmission is configured with transmission parameters associated with a second symbol type, using the transmission parameters associated with the second symbol type; if the DL reception/UL transmission is not configured with transmission parameters associated with the second symbol type, using transmission parameters associated with the first symbol type such that the transmission parameters used for the two actual transmissions are the same; using the same transmission parameters in the first repeated transmission as the DL reception/UL transmission; using transmission parameters configured for the DL reception/UL transmission and corresponding to SBFD symbols/slots types; the transmission parameters here include at least one of: power control related parameters, beam related parameters (e.g., TCI (Transmission Configuration Indicator) relation, quasi Co-sited QCL (Quasi Co-Location) relation), precoding related parameters, MCS table, UCI multiplexed betaoffset parameters, maximum RANK number, DMRS mapping type.

Fig. 4 is a flowchart of a method for configuring parameters, where the method is performed by a base station side, and as shown in fig. 4, the method includes:

s410, the first information and/or the second information are sent.

Wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value;

s420, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information.

The manner of determining the target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information may be referred to the above embodiments, and will not be described herein.

S430, UCI multiplexed in PUSCH transmission based on the target beta offset value is received.

The target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in the PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH.

Fig. 5 is a schematic structural diagram of a parameter configuration apparatus provided in an embodiment of the present application, where the apparatus is disposed in a user equipment, and includes:

An information receiving module 510, configured to receive the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value;

A target beta offset value determining module 520, configured to determine a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type symbols include a first type symbol and a second type symbol;

A UCI transmission module 530, configured to multiplex UCI in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in the PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH.

Optionally, if the first information includes: the DCI triggering PUSCH does not contain a beta offset value indication field, and the second information includes a beta offset value for configuring semi-static, the target beta offset value determining module 520 is further configured to:

determining a semi-static beta offset value as a target beta offset value for PUSCH transmission of UL subbands in a first type of symbol for UCI transmission; or alternatively

Determining a semi-static beta offset value as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; or alternatively

Determining a semi-static beta offset value as a target beta offset value for a first priority PUSCH transmission of UL subbands in a first type of symbol for UCI transmission; or alternatively

Determining a semi-static beta offset value as a target beta offset value for a first priority PUSCH transmission of UL BWP in a second type symbol for UCI transmission; or alternatively

Determining a semi-static beta offset value as a target beta offset value for a second priority PUSCH transmission of UL subbands in the first type of symbols for UCI transmission; or alternatively

The semi-static beta offset value is determined as the target beta offset value for the second priority PUSCH transmission transmitting UL BWP in the second type symbol.

Optionally, the target beta offset value determining module 520 is further configured to:

if the beta offset value associated with the first type symbol is not configured, determining the beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; or alternatively

If the beta offset value associated with the second type symbol is not configured, determining the beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or alternatively

If the beta offset value with the first priority associated with the first type symbol is not configured, determining the beta offset value with the first priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the first priority for UL sub-bands in the first type symbol for UCI transmission; or alternatively

If the beta offset value with the first priority associated with the first type symbol is not configured, determining the beta offset value with the second priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the first priority for UL sub-bands in the first type symbol for UCI transmission; or alternatively

If the beta offset value with the second priority associated with the first type symbol is not configured, determining the beta offset value with the first priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the second priority for UL sub-bands in the first type symbol for UCI transmission; or alternatively

If the beta offset value with the second priority associated with the first type symbol is not configured, determining the beta offset value with the second priority associated with the second type symbol as a target beta offset value for PUSCH transmission with the second priority for UL sub-bands in the first type symbol for UCI transmission; or alternatively

If the beta offset value with the first priority associated with the second type symbol is not configured, determining the beta offset value with the first priority associated with the first type symbol as a target beta offset value for PUSCH transmission with the first priority for UCI transmission in UL BWP in the second type symbol; or alternatively

If the beta offset value with the first priority associated with the second type symbol is not configured, determining the beta offset value with the second priority associated with the first type symbol as a target beta offset value for PUSCH transmission with the first priority for UCI transmission of UL BWP in the second type symbol; or alternatively

If the beta offset value with the second priority associated with the second type symbol is not configured, determining the beta offset value with the first priority associated with the first type symbol as a target beta offset value for PUSCH transmission with the second priority for UL BWP in the second type symbol for UCI transmission; or alternatively

If the beta offset value associated with the second type symbol having the second priority is not configured, the beta offset value associated with the first type symbol having the second priority is determined as a target beta offset value for PUSCH transmission having the second priority for UCI transmission of UL BWP in the second type symbol.

Optionally, if the first information includes that the PUSCH is semi-static, and the second information includes a beta offset value for configuring the semi-static, the target beta offset value determining module 520 is further configured to:

determining a beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; or alternatively

Determining a beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or alternatively

Determining a first priority beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of a first priority of UL subbands in the first type symbol for UCI transmission; or alternatively

Determining a second priority beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of a second priority for UL sub-bands in the first type symbol for UCI transmission; or alternatively

Determining a first priority beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of the first priority of UL BWP in the second type symbol for UCI transmission; or alternatively

The second priority beta offset value associated with the second type symbol is determined as a target beta offset value for the second priority PUSCH transmission of UL BWP in the second type symbol for UCI transmission.

Optionally, if the first information includes: the DCI format triggering PUSCH is 0_0, and the second information includes a beta offset value used for configuring dynamic, the target beta offset value determining module 520 is further configured to:

Determining a first value of a set of beta offset values associated with the first type of symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type of symbol for UCI transmission; or alternatively

Determining a first value of a set of beta offset values associated with the second type of symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; or alternatively

Determining a first value of a set of beta offset values of a first priority associated with the first type of symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type of symbol for UCI transmission; or alternatively

Determining a first value of a set of beta offset values of a second priority associated with the first type of symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type of symbol for UCI transmission; or alternatively

Determining a first value of a set of first priority beta offset values associated with the second type of symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; or alternatively

A first value of a set of second priority beta offset values associated with the second type of symbol is determined as a target beta offset value for PUSCH transmission for UL BWP in the second type of symbol for UCI transmission.

Optionally, if the second information includes: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value associated with a first type symbol and a beta offset value associated with a second type symbol; or configuring one set of two beta offset values, one associated with a first type of symbol and the other associated with a second type of symbol;

the target beta offset value determination module 520 is further configured to:

determining a beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; the beta offset value associated with the second type symbol is determined as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission.

Optionally, if the second information includes: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value and an adjustment parameter which are associated with a first type symbol; the target beta offset value determination module 520 is further configured to:

determining a beta offset value associated with the first type symbol as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission;

determining another beta offset according to the beta offset value and the adjustment parameter associated with the first type symbol, and determining the other beta offset as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or alternatively

If the second information includes: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value and an adjustment parameter which are associated with a second type symbol; determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, comprising:

Determining a beta offset value associated with the second type symbol as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission;

And determining another beta offset according to the beta offset value and the adjustment parameter associated with the second type of symbol, and determining the other beta offset as a target beta offset value for PUSCH transmission of the UL sub-band in the first type of symbol for UCI transmission.

Optionally, if the first information includes: the DCI triggering PUSCH includes a beta offset value indication field, and the second information includes: for configuring a dynamic beta offset value, and configuring a beta offset value set associated with a first type of symbol and a beta offset value set associated with a second type of symbol, the target beta offset value determining module 520 is further configured to:

Determining a beta offset value determined from a beta offset value set associated with the first type symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission; or alternatively

Determining a beta offset value determined from a beta offset value set associated with the second type of symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; wherein if the number of elements in the beta offset value set associated with the first type symbol is different from the number of elements in the beta offset value set associated with the second type symbol, the number of bits in the beta offset value indication field is determined according to the maximum number of elements.

Optionally, the second information further includes: configuring the set of control resources associated with the first type of symbol and the set of control resources associated with the second type of symbol, the target beta offset value determination module 520 is further configured to:

If the DCI corresponding to the beta offset value indication field is received from the control resource set associated with the first type symbol, the beta offset value determined by the beta offset value indication field from the beta offset value set associated with the first type symbol is determined as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission;

If the DCI corresponding to the beta offset value indication field is received from the control resource set associated with the second type symbol, the beta offset value determined by the beta offset value indication field from the beta offset value set associated with the second type symbol is determined as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission.

Optionally, the first information further includes: the DCI includes another beta offset value indication field, where one beta offset value indication field is associated with a first type symbol, as a first beta offset value indication field, and another beta offset value indication field is associated with a second type symbol, as a second beta offset value indication field, then the target beta offset value determining module 520 is further configured to:

determining a beta offset value determined from a set of beta offset values associated with the first type symbol based on the first beta offset value indication field as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission;

The beta offset value determined from the set of beta offset values associated with the second type of symbol based on the second beta offset value indication field is determined as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission.

Optionally, if one PUSCH transmission is transmitted across slots of different types of symbols, the first information further includes: configuring an adjustment parameter, the target beta offset value determining module 520 is further configured to:

Determining a beta offset value determined from a beta offset value set associated with the first type symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission;

Determining a beta offset value determined according to the target beta offset value and the adjustment parameter as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or alternatively

Determining a beta offset value determined from a beta offset value set associated with the second type of symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission;

And determining the beta offset value determined according to the target beta offset value and the adjustment parameter as the target beta offset value of PUSCH transmission of the UL sub-band in the first type symbol for UCI transmission.

Optionally, if one PUSCH transmission is transmitted across slots of different types of symbols, the first information includes: the target beta offset value determining module 520 is further configured to configure the beta offset value indicating field to be associated with the beta offset value set associated with the first type symbol and the beta offset value set associated with the second type symbol at the same time:

The beta offset value determined from the beta offset value set associated with the second type of symbol based on the beta offset value indication field is determined as a target beta offset value for PUSCH transmission for UCI transmission of UL BWP in the second type of symbol.

Optionally, the first information further includes at least one of: associating the same time slot interval k, the same time slot interval k set or the same time domain resource allocation table for the first type of symbols and the second type of symbols; further comprises: a time slot position determining module, configured to:

Determining a slot position where a PUSCH triggered by DCI is transmitted based on at least one of the same slot interval, the same set of slot intervals, or the same time domain resource allocation table;

Optionally, the method further comprises: a transmission resource determining module, configured to:

If part of the time domain or frequency domain resources of the PUSCH are punctured/canceled, UCI is transmitted only in the remaining resources of the PUSCH; wherein the resources used by the UCI are determined based on the determined target beta offset value, the number of bits of the UCI, and the PUSCH remaining resources, and the UCI is mapped in the PUSCH remaining resources for transmission.

Optionally, the transmission resource determining module is further configured to: if part of time domain or frequency domain resources of the PUSCH are punctured/canceled and the PUSCH is triggered to be transmitted in the first type symbol, UCI is multiplexed in the remaining resources of the PUSCH; wherein, the remaining resources of the PUSCH are resources of which the PUSCH is located in the time domain and/or the frequency domain of the UL sub-band.

Optionally, UCI transmission module 530 is further configured to:

For a connected state user equipment or an idle state device, if an intersection resource of an UL subband and an activated UL BWP in a frequency domain is greater than 0, UCI is multiplexed in PUSCH transmission based on at least one of the following factors:

physical resources performing the transmission; wherein the physical resources include UL subbands or available PRBs; or alternatively

Performing resource allocation corresponding to transmission; wherein the resource configuration comprises: TDRA of UL subband, TDRA of UL BWP is activated, TDRA of available PRB associations; or alternatively

Performing parameters used for transmission; wherein the parameters include: SCS of UL subband, SCS of available PRB, SCS of activated UL BWP;

if the intersection resource of UL subband and activated UL BWP in frequency domain is equal to 0, UCI is multiplexed in PUSCH transmission based on at least one of the following factors:

physical resources performing the transmission; wherein the physical resources comprise UL subbands; or alternatively

Performing parameters used for transmission; wherein the parameters include: SCS of UL subband, SCS of available PRB, SCS of activated UL BWP; or alternatively

No transmission is performed.

Fig. 6 is a schematic structural diagram of a parameter configuration apparatus according to an embodiment of the present application, where the apparatus is disposed in a base station, and includes:

An information sending module 610, configured to send the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value;

A target beta offset value determining module 620, configured to determine a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type symbols include a first type symbol and a second type symbol;

The UCI receiving module is used for receiving UCI multiplexed in the PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in the PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH.

In one embodiment, fig. 7 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 7, the apparatus provided by the present application includes: processor 510 and memory 520. The number of processors 510 in the device may be one or more, one processor 510 being illustrated in fig. 7. The amount of memory 520 in the device may be one or more, one memory 520 being illustrated in fig. 7. The processor 510 and memory 520 of the device may be connected by a bus or otherwise, for example in fig. 7. In an embodiment, the device is a computer device.

The memory 520 serves as a computer-readable storage medium, and may be configured to store a software program, a computer-executable program, and modules, such as program instructions/modules (e.g., an encoding module and a first transmitting module in a data transmission apparatus) corresponding to the apparatus according to any embodiment of the present application. Memory 520 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created according to the use of the device, etc. In addition, memory 520 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, memory 520 may further include memory located remotely from processor 510, which may be connected to the device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The device provided by the above embodiment may be configured to execute the parameter configuration method provided by any of the above embodiments, and have corresponding functions and effects.

The program stored in the corresponding memory 520 may be program instructions/modules corresponding to the parameter configuration method provided in the embodiment of the present application, and the processor 510 executes one or more functions of the computer device and processes data by running the software program, instructions and modules stored in the memory 520, that is, implements the associated query method applied to data in the above method embodiment. It can be understood that when the device is a receiving end, the parameter configuration method provided by any embodiment of the present application can be executed, and the corresponding functions and effects are provided.

Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are for performing a parameter configuration method, the method comprising: receiving the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value; determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type of symbols include a first type of symbol and a second type of symbol; multiplexing the UCI in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in a PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH. Or transmitting the first information and/or the second information; wherein the first information includes DCI triggering PUSCH, and the second information includes: for configuring a semi-static beta offset value or a dynamic beta offset value; determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information; wherein the type of symbols include a first type of symbol and a second type of symbol; receiving the UCI multiplexed in PUSCH transmission based on the target beta offset value; the target beta offset value comprises a first beta offset value used for transmitting HARQ-ACK information in a PUSCH, a second beta offset value used for transmitting first partial CSI information in the PUSCH and a third beta offset value used for transmitting second partial CSI information in the PUSCH.

It will be appreciated by those skilled in the art that the term user equipment encompasses any suitable type of wireless user equipment, such as mobile telephones, portable data processing devices, portable web browsers, or car-mounted mobile stations.

In general, the various embodiments of the application may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.

Embodiments of the application may be implemented by a data processor of a mobile device executing computer program instructions, e.g. in a processor entity, either in hardware, or in a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages.

The block diagrams of any of the logic flows in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on a memory. The Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), optical storage devices and systems (digital versatile Disk (Digital Video Disc, DVD) or Compact Disk (CD)), and the like. The computer readable medium may include a non-transitory storage medium. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general purpose computers, special purpose computers, microprocessors, digital signal processors (DIGITAL SIGNAL Processing, DSP), application SPECIFIC INTEGRATED Circuits (ASIC), programmable logic devices (Field-Programmable GATE ARRAY, FGPA), and processors based on a multi-core processor architecture.

The foregoing description is only exemplary embodiments of the application and is not intended to limit the scope of the application.

Embodiments of the application may be implemented by a data processor of a mobile device executing computer program instructions, e.g. in a processor entity, either in hardware, or in a combination of software and hardware. The computer program instructions may be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or destination code written in any combination of one or more programming languages.

The foregoing detailed description of exemplary embodiments of the application has been provided by way of exemplary and non-limiting examples. Various modifications and adaptations to the above embodiments may become apparent to those skilled in the art without departing from the scope of the application, which is defined in the accompanying drawings and claims. Accordingly, the proper scope of the application is to be determined according to the claims.

Claims

1. A method of parameter configuration, the method performed by a user equipment, comprising:

2. The method of claim 1, wherein if the first information comprises: the DCI triggering PUSCH does not contain a beta offset value indication field, and the second information includes a beta offset value for configuring semi-static, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, including at least one of:

determining the semi-static beta offset value as a target beta offset value for PUSCH transmission of the UL sub-band in the first type symbol for UCI transmission; or alternatively

Determining the semi-static beta offset value as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or alternatively

Determining the semi-static beta offset value as a target beta offset value for first priority PUSCH transmission of UL subbands in a first type of symbol for UCI transmission; or alternatively

Determining the semi-static beta offset value as a target beta offset value for a first priority PUSCH transmission of UL BWP in a second type symbol for UCI transmission; or alternatively

Determining the semi-static beta offset value as a target beta offset value for a second priority PUSCH transmission of UL subbands in a first type symbol for UCI transmission; or alternatively

The semi-static beta offset value is determined as a target beta offset value for a second priority PUSCH transmission transmitting UL BWP in a second type symbol.

3. The method as recited in claim 2, further comprising:

4. The method of claim 1, wherein if the first information includes that the PUSCH is semi-static and the second information includes a beta offset value for configuring semi-static, determining a target beta offset value for PUSCH transmission for UCI in a type symbol based on the first information and/or the second information includes at least one of:

5. The method of claim 1, wherein if the first information comprises: and the DCI format triggering the PUSCH is 0_0, and the second information comprises a beta offset value used for configuring dynamics, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, wherein the target beta offset value comprises at least one of the following steps:

6. The method of claim 1, wherein if the second information comprises: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value associated with a first type symbol and a beta offset value associated with a second type symbol; or configuring one set of two beta offset values, one associated with a first type of symbol and the other associated with a second type of symbol;

Determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and the second information, comprising:

7. The method of claim 1, wherein if the second information comprises: the method comprises the steps of configuring a semi-static beta offset value, and configuring a beta offset value and an adjustment parameter which are associated with a first type symbol; determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, comprising:

Determining another beta offset according to the beta offset value associated with the first type symbol and the adjustment parameter, and determining the other beta offset as a target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission; or alternatively

And determining another beta offset according to the beta offset value associated with the second type symbol and the adjustment parameter, and determining the other beta offset as a target beta offset value for PUSCH transmission of the UL sub-band in the first type symbol for UCI transmission.

8. The method of claim 1, wherein if the first information comprises: the DCI triggering PUSCH includes a beta offset value indication field, and the second information includes: for configuring a dynamic beta offset value, and configuring a beta offset value set associated with a first type symbol and a beta offset value set associated with a second type symbol, determining a target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information, comprising at least one of:

Determining a beta offset value determined from a beta offset value set associated with the second type of symbol based on the beta offset value indication field as a target beta offset value for PUSCH transmission of UL BWP in the second type of symbol for UCI transmission; and if the number of the elements in the beta offset value set associated with the first type symbol is different from the number of the elements in the beta offset value set associated with the second type symbol, determining the bit number of the beta offset value indication field according to the maximum number of the elements.

9. The method of claim 1, wherein the second information further comprises: configuring a control resource set associated with a first type symbol and a control resource set associated with a second type symbol, determining a target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information, including at least one of:

If a DCI corresponding to a beta offset value indication field is received from a control resource set associated with a first type symbol, the beta offset value determined by the beta offset value indication field from the beta offset value set associated with the first type symbol is determined as a target beta offset value for PUSCH transmission of UL subbands in the first type symbol for UCI transmission;

If a beta offset value indicating that the DCI corresponding to the field is received from the control resource set associated with the second type symbol, the beta offset value indicating that the field is determined from the beta offset value set associated with the second type symbol is determined as the target beta offset value for PUSCH transmission of UL BWP in the second type symbol for UCI transmission.

10. The method of claim 1, wherein the first information further comprises: the DCI includes another beta offset value indication field, and one of the beta offset value indication fields is associated with a first type symbol, as a first beta offset value indication field, and the other beta offset value indication field is associated with a second type symbol, as a second beta offset value indication field, then determining a target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information, including:

11. The method of claim 1, wherein if one PUSCH transmission is transmitted across slots of different types of symbols, the first information further comprises: configuring an adjustment parameter, determining a target beta offset value for PUSCH transmission of UCI in a type symbol based on the first information and/or the second information, including at least one of:

Determining the beta offset value determined according to the target beta offset value and the adjustment parameter as a target beta offset value for PUSCH transmission of UL BWP in a second type symbol for UCI transmission; or alternatively

and determining the beta offset value determined according to the target beta offset value and the adjustment parameter as a target beta offset value for PUSCH transmission of the UL sub-band in the first type symbol for UCI transmission.

12. The method of claim 1, wherein the first information comprises, if one PUSCH transmission is transmitted across slots of different types of symbols: configuring the beta offset value indication field to be simultaneously associated with a beta offset value set associated with a first type symbol and a beta offset value set associated with a second type symbol, determining a target beta offset value for PUSCH transmission of UCI in the type symbol based on the first information and/or the second information, including:

13. The method of claim 1, wherein the first information further comprises at least one of: associating the same time slot interval k, the same time slot interval k set or the same time domain resource allocation table for the first type of symbols and the second type of symbols; further comprises:

Determining a time slot position where a PUSCH triggered by DCI is transmitted based on at least one of the same time slot interval, the same set of time slot intervals, or the same time domain resource allocation table;

Wherein, the time slot interval k satisfies: if the DCI triggering the PUSCH is received in a time slot n, the time slot of the PUSCH triggered by the DCI is a time slot n+k; the time domain resource allocation table refers to a time domain resource allocation table of the PUSCH, where at least one column is a slot interval, and at least two columns are symbol positions of the PUSCH.

14. The method as recited in claim 1, further comprising:

If part of the time domain or frequency domain resources of the PUSCH are punctured/canceled, the UCI is transmitted only in the remaining resources of the PUSCH; wherein the resources used by the UCI are determined based on the determined target beta offset value, the number of bits of the UCI, and the PUSCH remaining resources, and the UCI is mapped in the PUSCH remaining resources for transmission.

15. The method of claim 14 wherein the UCI is multiplexed in the PUSCH remaining resources if part of the PUSCH time or frequency domain resources are punctured/cancelled and PUSCH is triggered for transmission in a first type symbol; wherein, the remaining resources of the PUSCH are resources of the PUSCH in the time domain and/or the frequency domain of the UL sub-band.

16. The method of claim 1, wherein multiplexing the UCI in PUSCH transmission based on the target beta offset value comprises:

For a connected state user equipment or an idle state device, if an intersection resource of an UL subband and an activated UL BWP in a frequency domain is greater than 0, multiplexing the UCI in PUSCH transmission based on at least one of the following factors:

if the intersection resource of the UL subband and the activated UL BWP in the frequency domain is equal to 0, multiplexing the UCI in PUSCH transmission based on at least one of the following factors:

physical resources performing the transmission; wherein the physical resources include UL subbands; or alternatively

No transmission is performed.

17. A method for configuring parameters, the method being performed by a base station and comprising:

18. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the parameter configuration method of any one of claims 1-17 when the program is executed by the processor.

19. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements a parameter configuration method as claimed in any one of claims 1-17.