CN113330791A

CN113330791A - Apparatus and method for wireless communication

Info

Publication number: CN113330791A
Application number: CN202080009502.4A
Authority: CN
Inventors: 徐婧
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-11-17
Filing date: 2020-11-17
Publication date: 2021-08-31
Also published as: WO2021093892A1; EP3977795B1; EP3977795A4; CN113766618A; CN113766618B; EP3977795A1; US20220124791A1

Abstract

An apparatus and method of wireless communication are provided. A method performed by a User Equipment (UE) includes: configured with an Information Element (IE) from a base station, and perform a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources; indicating a Physical Uplink Shared Channel (PUSCH) priority; indicating a hybrid automatic repeat request-acknowledgement (HARQ-ACK) priority; indicating the validity of the PUSCH transmission scheme; indicating a number of repetitions of a PUSCH transmission scheme; or power control for CG PUSCH. This can solve the problems in the prior art, support HARQ-ACK codebooks in CGs, support PUSCH transmission scheme switching, support power control for CGs, provide good communication performance and/or provide high reliability.

Description

Apparatus and method for wireless communication

Technical Field

The present disclosure relates to the field of communication systems, and more particularly, to an apparatus and method for wireless communication capable of providing good communication performance and/or high reliability.

Background

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These wireless communication systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems, such as Long Term Evolution (LTE) systems, and fifth generation (5G) systems, which may be referred to as New Radio (NR) systems. A wireless multiple-access communication system may include several base stations or network access nodes, each supporting communication for multiple communication devices, which may otherwise be referred to as User Equipments (UEs), simultaneously. The wireless communication network may include base stations capable of supporting UE communications. A UE may communicate with a base station via the downlink and uplink. The downlink refers to the communication link from the base station to the UE, and the uplink refers to the communication link from the UE to the base station.

In wireless communications, a Physical Uplink Shared Channel (PUSCH) transmission may be: dynamically scheduled by an uplink grant in Downlink Control Information (DCI), which is called a dynamic grant; semi-statically configured and scheduled by higher layer parameters without detecting uplink grants in the DCI, which is referred to as type 1 Configured Grant (CG); or semi-statically configured by higher layer parameters and semi-persistently scheduled by an uplink grant in the DCI, which is referred to as type 2 CG. How to use a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook, power control for inter-UE multiplexing, and/or PUSCH repetition enhancement in configuring grant transmission remains an open question.

Therefore, there is a need for an apparatus (such as a User Equipment (UE) and/or a base station) and method for wireless communication that can solve the problems in the prior art, support HARQ-ACK codebook in CG, support PUSCH transmission scheme switching, support power control for CG, provide good communication performance and/or provide high reliability.

Disclosure of Invention

An object of the present disclosure is to propose an apparatus (such as a User Equipment (UE) and/or a base station) and a method of wireless communication, which can solve the problems in the prior art, support HARQ-ACK codebook in CG, support PUSCH transmission scheme switching, support power control for CG, provide good communication performance and/or provide high reliability.

In a first aspect of the disclosure, a method of wireless communication by a User Equipment (UE) includes being configured with an Information Element (IE) from a base station, and performing a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH.

In a second aspect of the disclosure, a method of wireless communication by a base station includes configuring an Information Element (IE) to a User Equipment (UE), and controlling the UE to perform a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH.

In a third aspect of the disclosure, a user equipment includes a memory, a transceiver, and a processor coupled with the memory and the transceiver. The processor is configured with an Information Element (IE) from a base station. The processor is configured to perform a Configuration Grant (CG) transmission using a first parameter from an IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH.

In a fourth aspect of the disclosure, a base station includes a memory, a transceiver, and a processor coupled with the memory and the transceiver. The processor is configured to configure an Information Element (IE) to a User Equipment (UE). The processor is configured to control the UE to perform a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH.

In a fifth aspect of the disclosure, a non-transitory machine-readable storage medium has instructions stored thereon, which when executed by a computer, cause the computer to perform the above-described method.

In a sixth aspect of the disclosure, a chip comprises a processor configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to perform the above method.

In a seventh aspect of the present disclosure, a computer-readable storage medium has stored therein a computer program for causing a computer to execute the above-described method.

In an eighth aspect of the disclosure, a computer program product comprising a computer program for causing a computer to perform the above method.

In a ninth aspect of the present disclosure, a computer program causes a computer to execute the above method.

Drawings

In order to more clearly explain embodiments of the present disclosure or related techniques, the following drawings will briefly be described in the embodiments. It is apparent that these drawings are merely some embodiments of the disclosure and that other drawings may be derived from those of ordinary skill in the art without undue experimentation.

Fig. 1 is a diagram illustrating an example of option 4 for Physical Uplink Shared Channel (PUSCH) enhancement.

Fig. 2 is a block diagram illustrating one or more User Equipments (UEs) and a base station in wireless communication in a communication network system according to an embodiment of the present disclosure.

Fig. 3 is a flow chart of a method of wireless communication performed by a User Equipment (UE) in accordance with an embodiment of the present disclosure.

Fig. 4 is a flow chart of a method of wireless communication performed by a base station in accordance with an embodiment of the present disclosure.

Fig. 5 is a block diagram of a system for wireless communication in accordance with an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in detail with reference to the following drawings by technical problems, structural features, attained objects, and effects. In particular, the terminology used in the embodiments of the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure.

In some embodiments, two hybrid automatic repeat request acknowledgement (HARQ-ACK) codebooks, power control for multiplexing between User Equipments (UEs), and Physical Uplink Shared Channel (PUSCH) repetition enhancements have been discussed for dynamic transmissions. Configuration Grant (CG) transmissions include type 1CG transmissions and type 2CG transmissions. For type 1CG transmissions, all parameters are configured by Radio Resource Control (RRC). For type 2CG transmission, a partial parameter is configured by RRC and indicated by Downlink Control Information (DCI), which is used for type 2CG activation. The RRC-related parameters are configured by ConfiguredGrantConfig information elements, as shown in table 1.

Table 1: ConfiguredGrantConfig information element

In some embodiments, the PUSCH repetition scheme includes two options: release 16(Rel-16) PUSCH transmission scheme and release 15(Rel-15) PUSCH transmission scheme. For the Rel-16 PUSCH transmission scheme: option 4. For the Rel-15 PUSCH transmission scheme: the transmission is made according to the Rel-15 behavior, with or without slot aggregation. With slot aggregation, the number of repetitions may be configured semi-statically (as in Rel-15) or indicated dynamically (as agreed by Rel-16).

Here is a description of option 4 from TR 38.824: one or more actual PUSCH repetitions in one slot, or two or more actual PUSCH repetitions across slot boundaries in consecutive available slots, are supported using one Uplink (UL) grant for dynamic PUSCH and one configuration grant configuration for configuration grant PUSCH. Further comprising:

the number of repetitions signaled by the gNB represents the "nominal" number of repetitions. The actual number of repetitions may be greater than the nominal number. FFS: for dynamic PUSCH and type 2 configuration granted PUSCH, signaled dynamically or semi-statically.

A Time Domain Resource Allocation (TDRA) field in DCI or a TDRA parameter in a type 1 configuration grant indicates resources for a first "nominal" repetition.

3. Time domain resources for the remaining repetitions are derived based at least on the resources used for the first repetition and the UL/Downlink (DL) direction of the symbol. To be further studied (FFS), there is a detailed interaction of the UL/DL direction determination process.

4. If a "nominal" repetition crosses a slot boundary or DL/UL switch point, the "nominal" repetition is divided into multiple PUSCH repetitions, one PUSCH repetition in each UL period in a slot. Repeated processing under certain conditions (e.g., too small in duration due to the split) will be further studied at the Work Item (WI) stage.

5. No demodulation reference signal (DMRS) is shared that is repeated across multiple PUSCHs.

6. There is no increase in the maximum Transport Block Size (TBS) compared to Rel-15.

7.FFS：L>14。

S + L may be greater than 14.

FFS: TDRA is up to 4 bits wide.

10. Note that: different repetitions may have the same or different Redundancy Versions (RVs).

Fig. 1 shows an example of option 4 for Physical Uplink Shared Channel (PUSCH) enhancement. These examples include 4 symbol and 2 repetition examples, 4 symbol and 4 repetition examples, and 14 symbol and 1 repetition examples. In the example of 14 symbols and 1 repetition, S plus L is greater than 14. S may refer to the number of symbols, L may refer to the total number of resources used for one repetition, and the value of S may be equal to the value of L.

Fig. 2 illustrates that in some embodiments one or more User Equipments (UEs) 10 and base stations (e.g., gnbs or enbs) 20 for wireless communication in a communication network system 30 are provided in accordance with embodiments of the present disclosure. The communication network system 30 includes one or more UEs 10 and base stations 20. One or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The

processor

11 or 21 may be configured to implement the proposed functions, processes and/or methods described in this specification. The layers of the radio interface protocol may be implemented in the

processor

11 or 21. The

memory

12 or 22 is operatively coupled with the

processor

11 or 21 and stores various information to operate the

processor

11 or 21. The

transceiver

13 or 23 is operatively coupled with the

processor

11 or 21, and the

transceiver

13 or 23 transmits and/or receives radio signals.

The

processor

11 or 21 may comprise an application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device. The

memory

12 or 22 may include read-only memory (ROM), Random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. The

transceiver

13 or 23 may include a baseband circuit to process radio frequency signals. When an embodiment is implemented in software, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules may be stored in the

memory

12 or 22 and executed by the

processor

11 or 21. The

memory

12 or 22 may be implemented within the

processor

11 or 21 or external to the

processor

11 or 21, in which case the

memory

12 or 22 may be communicatively coupled to the

processor

11 or 21 via various means as is known in the art.

In some embodiments, the processor 11 is configured with an Information Element (IE) from the base station 20. Processor 11 is configured to perform a Configuration Grant (CG) transmission using a first parameter from the IE for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH. This may solve the problems in the prior art, support HARQ-ACK codebooks in CGs, support PUSCH transmission scheme switching, support power control for CGs, provide good communication performance and/or provide high reliability.

In some embodiments, the processor 21 is configured to configure an Information Element (IE) to the UE 10. The processor 21 is configured to control the UE 10 to perform a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH. This may solve the problems in the prior art, support HARQ-ACK codebooks in CGs, support PUSCH transmission scheme switching, support power control for CGs, provide good communication performance and/or provide high reliability.

Fig. 3 illustrates a method 200 of wireless communication by a User Equipment (UE) in accordance with an embodiment of the disclosure. In some embodiments, method 200 includes: block 202 configured with an Information Element (IE) from a base station, and block 204 performing a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH. This may solve the problems in the prior art, support HARQ-ACK codebooks in CGs, support PUSCH transmission scheme switching, support power control for CGs, provide good communication performance and/or provide high reliability.

Fig. 4 illustrates a method 300 of wireless communication by a base station in accordance with an embodiment of the disclosure. In some embodiments, the method 300 includes: block 302, configuring an Information Element (IE) to a User Equipment (UE), and block 304, controlling the UE to perform a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of: uplink Control Information (UCI) multiplexing in CG resources, indicating Physical Uplink Shared Channel (PUSCH) priority, indicating hybrid automatic repeat request acknowledgement (HARQ-ACK) priority, indicating validity of PUSCH transmission scheme, indicating number of repetitions of PUSCH transmission scheme, or power control for CG PUSCH. This may solve the problems in the prior art, support HARQ-ACK codebooks in CGs, support PUSCH transmission scheme switching, support power control for CGs, provide good communication performance and/or provide high reliability.

In some embodiments, the IE comprises a ConfiguredGrantConfig IE. In some embodiments, the PUSCH transmission scheme includes a release 15PUSCH transmission scheme and/or a release 16PUSCH transmission scheme. In some embodiments, the first parameter comprises a UCI-OnPUSCH parameter configured in an IE, the UCI-OnPUSCH parameter being used for UCI multiplexing in CG resources.

In some embodiments, the UCI-OnPUSCH parameter is configured to match CG priorities if the CG PUSCH level 2 physical priority is determined by an indication in each CG configuration from the base station. In some embodiments, the indication in each CG configuration includes a Radio Resource Control (RRC) parameter.

In some embodiments, the first parameter comprises one of two UCI-OnPUSCH or BetaOffsets parameters, and the two UCI-OnPUSCH or BetaOffsets parameters are configured in the IE. In some embodiments, performing the CG transmission using the first parameter from the IE further comprises: receiving an indication in a type 2CG PUSCH activation from a base station; and selecting one of the two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the type 2CG PUSCH activation. In some embodiments, the indication in type 2CG PUSCH activation is used to indicate PUSCH priority and/or a Radio Network Temporary Identifier (RNTI) to which DCI for type 2CG PUSCH activation applies, a control resource set (CORESET), a search space, a Downlink Control Information (DCI) format, a field in DCI. In some embodiments, the first parameter is configured to match CG priority if the 2-level physical priority of CG PUSCH is overridden by type 2CG PUSCH activation.

In some embodiments, performing the CG transmission using the first parameter from the IE further comprises: receiving an indication in DCI for a Physical Downlink Shared Channel (PDSCH) from a base station, wherein HARQ-CK for PDSCH is multiplexed in a type 2CG PUSCH; and selecting one of the two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the DCI for the PDSCH. In some embodiments, the indication in the DCI for PDSCH is used to indicate HARQ-ACK priority and/or to apply the RNTI, CORESET, search space, DCI format, fields in the DCI for type 2CG PUSCH activation. In some embodiments, the first parameter is configured to match CG priorities and HARQ-ACK priorities if the CG PUSCH level 2 physical priority is determined by an indication in each CG configuration from the base station. In some embodiments, the indication in each CG configuration includes an RRC parameter.

In some embodiments, performing the CG transmission using the first parameter from the IE further comprises: receiving a first indication in type 2CG PUSCH activation and a second indication in DCI for a PDSCH from a base station, wherein HARQ-CK for the PDSCH is multiplexed in a type 2CG PUSCH; and selecting one of the two UCI-OnPUSCH or BetaOffsets parameters based on the first indication in the type 2CG PUSCH activation and the second indication in the DCI for the PDSCH. In some embodiments, the first indication in type 2CG PUSCH activation is used to indicate PUSCH priority and/or to apply a RNTI, CORESET, search space, DCI format, field in DCI for type 2CG PUSCH activation; and/or a second indication in the DCI for PDSCH to indicate HARQ-ACK priority and/or to apply a RNTI, CORESET, search space, DCI format, fields in the DCI for type 2CG PUSCH activation. In some embodiments, the first parameter is configured to match CG priority and HARQ-ACK priority if the CG PUSCH level 2 physical priority is covered by a type 2CG PUSCH activation.

In some embodiments, the first parameter is used to indicate whether a release 15PUSCH transmission scheme is valid or a release 16PUSCH transmission scheme is valid. In some embodiments, the time domain resource allocation is determined by type 2CG activation and/or a first parameter.

In some embodiments, the first parameter comprises a repK parameter configured in the IE, the repK parameter indicating a number of repetitions of the PUSCH transmission scheme. In some embodiments, if the repK parameter is greater than 1, a release 15PUSCH transmission scheme is applied; otherwise, if the repK parameter is not greater than 1, the PUSCH transmission scheme depends on the DCI format. In some embodiments, the PUSCH transmission scheme depends on the DCI format if the repK parameter is equal to 1. In some embodiments, the PUSCH transmission scheme is associated with a DCI format. In some embodiments, the association between the PUSCH transmission scheme and the DCI format is configured by higher layer parameters. In some embodiments, the PUSCH transmission scheme configuration is semi-static for configuring the grant.

In some embodiments, the first parameters include power control parameters configured in the IE for power control for CG PUSCHs other than the first CG PUSCH, and open-loop parameters in DCI for type 2 configuration grant activation for power control for the first CG PUSCH.

Some embodiments of the present disclosure provide solutions to support PUSCH transmission scheme switching between two HARQ-ACK codebooks in a configuration grant, Rel-15 and Rel-16 and/or power control for a configuration grant. Some embodiments of the present disclosure provide techniques to enable a UE to determine whether a Remaining Minimum System Information (RMSI) control resource set (CORESET) configuration table is based on those for a 5MHz minimum channel bandwidth or those for a 10MHz minimum channel bandwidth to address the problems in the prior art, i.e., how to use HARQ-ACK codebooks in configuring grant transmissions, power control for inter-UE multiplexing, and/or PUSCH repetition enhancements remain a pending problem.

Example (c):

one UCI-OnPUSCH parameter is directly configured in the ConfiguredGrantConfig Information Element (IE). The UCI-OnPUSCH parameter is used for configuring UCI multiplexing in authorized resources. Benefits of this example include that the UCI-OnPUSCH parameters may be configured to match the configuration grant priority if the level 2 Physical (PHY) priority of the CG PUSCH is determined by an explicit indication (as a new RRC parameter) in each CG configuration.

Example (c):

at least two UCI-OnPUSCH or BetaOffsets parameters are configured in the ConfigardGrantConfig IE. One of the two UCI-OnPUSCH or BetaOffsets parameters is selected based on the indication in the type 2CG PUSCH activation. The indication in type 2CG PUSCH activation is used to indicate PUSCH priority. Optionally, the indication in type 2CG PUSCH activation may apply RNTI, CORESET, search space, DCI format, fields in DCI for DCI of type 2CG PUSCH activation. The beneficial effects of this example include: if the 2-level PHY priority of the CG PUSCH can be covered by type 2CG PUSCH activation, the UCI-OnPUSCH parameter matching the PUSCH priority cannot be defined because the PUSCH priority is not defined before the type 2CG PUSCH activation. The present example matches the UCI-OnPUSCH parameters for configuration authorization to the configuration authorization priority.

Example (c):

at least two UCI-OnPUSCH or BetaOffsets parameters are configured for type 2CG in the ConfiguredGrantConfig IE. One of the two UCI-OnPUSCH or BetaOffsets parameters is selected based on an indication in the DCI for the PDSCH. HARQ-CK for PDSCH is multiplexed in type 2CG PUSCH. The indication in the DCI for the PDSCH is used to indicate the HARQ-ACK priority. Optionally, the indication may apply the RNTI, CORESET, search space, DCI format, fields in DCI for type 2CG PUSCH activated DCI. The benefits of this example include if the level 2 PHY priority of CG PUSCH is determined by an explicit indication (as a new RRC parameter) in each CG configuration, however UCI multiplexed in type 2CG PUSCH is undefined before HARQ-ACK transmission occurs. The present example matches the UCI-OnPUSCH parameters for configuration grant with the configuration grant priority and HARQ-ACK priority.

Example (c):

at least two UCI-OnPUSCH or BetaOffsets parameters are configured in the ConfigardGrantConfig IE. One of the two UCI-OnPUSCH or BetaOffsets parameters is selected based on a first indication in a type 2CG PUSCH activation and a second indication in DCI for PDSCH. HARQ-CK for PDSCH is multiplexed in type 2CG PUSCH. The first indication in the type 2CG PUSCH activation is used to indicate the PUSCH priority. The second indication in the DCI for the PDSCH is used to indicate HARQ-ACK priority. Optionally, the first indication and/or the second indication may apply RNTI, CORESET, search space, DCI format, fields in DCI for type 2CG PUSCH activation. The beneficial effects of this example include: if the 2-level PHY priority of the CG PUSCH can be covered by type 2CG PUSCH activation, since the PUSCH priority is undefined before the type 2CG PUSCH activation, the UCI-OnPUSCH parameter matching the PUSCH priority cannot be defined, and the UCI multiplexed in the type 2CG PUSCH is undefined before the HARQ-ACK transmission occurs. The present example matches the UCI-OnPUSCH parameters for configuration grant with the configuration grant priority and HARQ-ACK priority.

Example (c):

the parameters in the ConfiguredGrantConfig IE indicate which PUSCH transmission scheme (Rel-15 or Rel-16) is valid. The time domain resource allocation is determined by the type 2CG activation and the parameter.

Example (c):

the repK in the ConfiguredGrantConfig IE is used to indicate the number of repetitions of the Rel-15 PUSCH transmission scheme and/or PUSCH transmission scheme such as the Rel-16 PUSCH transmission scheme. If the repK is greater than 1, a Rel-15 PUSCH transmission scheme is applied, otherwise (e.g. repK ═ 1 in ConfiguredGrantConfig), a PUSCH transmission scheme such as a Rel-16 PUSCH transmission scheme depends on the DCI format. Optionally, a PUSCH transmission scheme, such as the Rel-16 PUSCH transmission scheme, is associated with the DCI format. The association of a PUSCH transmission scheme, such as the Rel-16 PUSCH transmission scheme, with a DCI format is configured by higher layer parameters. Optionally, the repetition scheme includes a Rel-15 PUSCH transmission scheme and a Rel-16 PUSCH transmission scheme. Benefits of this example include that PUSCH transmission scheme configurations are semi-static for configuration grants, and/or reuse of rep-K does not affect flexibility and reduces overhead.

Example (c):

open loop parameters in DCI for type 2 configuration grant activation are used for power control for the first CG PUSCH. The power control for CG PUSCHs other than the first CG PUSCH is based on the power control parameters in the configredgrantconfig IE.

In summary, the methods disclosed in some embodiments of the present application may be used to implement at least the following: two HARQ-ACK codebooks are provided in the configuration grant to make UCI multiplexing more efficient since it matches the PUSCH priority and the HARQ-ACK priority. The PUSCH transmission scheme switching is between Rel-15 and Rel-16, where reusing the repK does not affect the transmission efficiency and reduces the signaling overhead. Power control for the configuration grant makes the first CG PUSCH power control efficient, which may match the system scheduling conditions in time.

The commercial interest of some embodiments is as follows. 1. The problems in the prior art are solved. 2. Supporting the HARQ-ACK codebook in CG. 3. PUSCH transmission scheme switching is supported. 4. Power control for the CG is supported. 5. Providing good communication performance. 6. Providing high reliability. 7. Some embodiments of the present disclosure are developed by 5G-NR chipset vendors, V2X communication system development vendors, car manufacturers including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc., drones (unmanned aerial vehicles), smart phone manufacturers, communication devices for public safety, AR/VR device manufacturers for uses such as gaming, meetings/seminars, education. Some embodiments of the present disclosure are a combination of "techniques/processes" that may be employed in the 3GPP specifications to create an end product. Some embodiments of the present disclosure propose a technical mechanism.

Fig. 5 is a block diagram of an example system 700 for wireless communication in accordance with an embodiment of the present disclosure. The embodiments described herein may be implemented in a system using any suitably configured hardware and/or software. Fig. 5 shows a system 700 that includes at least a Radio Frequency (RF) circuit 710, a baseband circuit 720, an application circuit 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled to each other as shown. The application circuitry 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors, such as a graphics processor and an application processor. A processor may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to be run on the system.

Baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise a baseband processor. The baseband circuitry may handle various wireless control functions that are capable of communicating with one or more radio networks through the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may support communication with Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), Wireless Personal Area Networks (WPAN). Embodiments in which baseband circuitry is used for radio communications supporting more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In various embodiments, baseband circuitry 720 may include circuitry to operate using signals that are not strictly considered at baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry to operate using signals having an intermediate frequency between the baseband frequency and the radio frequency. The RF circuitry 710 is capable of communicating with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include converters, filters, amplifiers, and the like to facilitate communication with the wireless network. In various embodiments, RF circuitry 710 may include circuitry to operate using signals that are not strictly considered to be at radio frequencies. For example, in some embodiments, the RF circuitry may include circuitry that operates using signals having an intermediate frequency between a baseband frequency and a radio frequency.

In various embodiments, the transmit circuitry, control circuitry, or receive circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, baseband circuitry, and/or application circuitry. As used herein, "circuitry" may refer to, or include, portions of: an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with, one or more software or hardware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and/or memory/storage may be implemented together on a system on a chip (SOC). Memory/storage 740 may be used to load and store data and/or instructions (e.g., for a system). The memory/storage of one embodiment may include any combination of suitable volatile memory (such as Dynamic Random Access Memory (DRAM)) and/or non-volatile memory (such as flash memory).

In various embodiments, I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system, and/or one or more peripheral component interfaces designed to enable peripheral components to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc., and the peripheral component interface may include, but is not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, and a power supply interface. In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or positioning information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyroscopic sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or may interact with baseband circuitry and/or RF circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

In various embodiments, display 750 may include displays, such as liquid crystal displays and touch screen displays. In various embodiments, system 700 may be a mobile computing device, such as but not limited to a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, AR/VR glasses, and the like. In various embodiments, the system may have more or fewer components, and/or different structures. The methods described herein may be implemented by a computer program where appropriate. The computer program may be stored in a storage medium (such as a non-transitory storage medium).

One of ordinary skill in the art understands that each of the units, algorithms, and steps described and disclosed in the embodiments of the present disclosure is implemented using electronic hardware or a combination of software and electronic hardware for a computer. Whether functions are run in hardware or in software depends on the application conditions and design requirements of the solution. Skilled artisans may implement the functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. As understood by a person skilled in the art, since the working processes of the above-described systems, devices and units are substantially the same, he/she may refer to the working processes of the systems, devices and units in the above-described embodiments. For ease of description and simplicity, these operations will not be described in detail.

It will be appreciated that the systems, devices and methods in the embodiments of the present disclosure may be implemented in other ways. The above embodiments are only examples. The division of the cells is based only on logical functions, while other divisions exist in the implementation. Multiple units or components may be combined or integrated in another system. Some features may be omitted or skipped. On the other hand, the mutual coupling, direct coupling or communicative coupling shown or discussed may be operated electronically, mechanically or otherwise through some port, device or unit, indirectly or communicatively.

Elements described as separate parts are used for illustration and are not physically separate. The elements shown are physical elements or not, i.e. located in one location or distributed over a plurality of network elements. Some or all of the elements are used for purposes of the embodiments. Furthermore, each functional unit in each embodiment may be integrated into one processing unit, physically separated from each other, or integrated with two or more units into one processing unit.

If the software functional unit is implemented and used and sold as a product, it may be stored in a readable storage medium in a computer. Based on this understanding, the technical solutions proposed by the present disclosure can be implemented in the form of a software product, in essence, or in part. Alternatively, some of the technical solutions advantageous to the conventional art may be implemented in the form of software products. A software product in a computer is stored in a storage medium and includes a plurality of commands for a computing device, such as a personal computer, server, or network device, to execute all or some of the steps disclosed by embodiments of the present disclosure. The storage medium includes a USB disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a floppy disk, or other medium capable of storing program code.

While the disclosure has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the disclosure is not to be limited to the disclosed embodiment, but is intended to cover various arrangements without departing from the broadest interpretation of the appended claims.

Claims

1. A method of wireless communication by a User Equipment (UE), comprising:

configured with Information Elements (IE) from a base station; and

performing a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of:

uplink Control Information (UCI) multiplexing in CG resources;

indicating a Physical Uplink Shared Channel (PUSCH) priority;

indicating a hybrid automatic repeat request-acknowledgement (HARQ-ACK) priority;

indicating the validity of the PUSCH transmission scheme;

indicating a number of repetitions of a PUSCH transmission scheme; or

Power control for CG PUSCH.

2. The method of claim 1, wherein the IE comprises a configuredggrantconfig IE.

3. The method according to claim 1 or 2, wherein the PUSCH transmission scheme comprises a release 15PUSCH transmission scheme and/or a release 16PUSCH transmission scheme.

4. The method of any of claims 1-3, wherein the first parameter comprises a UCI-OnPUSCH parameter configured in the IE, and the UCI-OnPUSCH parameter is used for UCI multiplexing in the CG resources.

5. The method of claim 4, wherein the UCI-OnPUSCH parameter is configured to match CG priority if CG PUSCH level 2 physical priority is determined by an indication in each CG configuration from the base station.

6. The method of claim 5, wherein the indication in each CG configuration comprises a Radio Resource Control (RRC) parameter.

7. The method of any of claims 1-3, wherein the first parameter comprises one of two UCI-OnPUSCH or BetaOffsets parameters configured in the IE.

8. The method of claim 7, wherein performing the CG transmission using the first parameter from the IE further comprises:

receiving an indication in a type 2CG PUSCH activation from the base station; and

selecting one of the two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the type 2CG PUSCH activation.

9. The method of claim 8, wherein the indication in the type 2CG PUSCH activation is to indicate the PUSCH priority and/or a Radio Network Temporary Identifier (RNTI) to which DCI for the type 2CG PUSCH activation applies, a control resource set (CORESET), a search space, a Downlink Control Information (DCI) format, a field in the DCI.

10. The method of claim 8 or 9, wherein the first parameter is configured to match CG priority if the type 2CG PUSCH physical priority is covered by the type 2CG PUSCH activation.

11. The method of claim 7, wherein performing the CG transmission using the first parameter from the IE further comprises:

receiving an indication in DCI for a Physical Downlink Shared Channel (PDSCH) from the base station, wherein HARQ-CK for PDSCH is multiplexed in a type 2CG PUSCH; and

selecting one of two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the DCI for the PDSCH.

12. The method of claim 11, wherein the indication in the DCI for PDSCH indicates the HARQ-CK priority and/or an RNTI, CORESET, search space, DCI format, field in the DCI to which DCI for type 2CG PUSCH activation is applied.

13. The method of claim 11 or 12, wherein the first parameter is configured to match CG priority and the HARQ-ACK priority if the CG PUSCH level 2 physical priority is determined by an indication in each CG configuration from the base station.

14. The method of claim 13, wherein the indication in each CG configuration comprises an RRC parameter.

15. The method of claim 7, wherein performing the CG transmission using the first parameter from the IE further comprises:

receiving a first indication in type 2CG PUSCH activation and a second indication in DCI of a PDSCH from the base station, wherein HARQ-CK for the PDSCH is multiplexed in a type 2CG PUSCH; and

selecting one of two UCI-OnPUSCH or BetaOffsets parameters based on the first indication in the type 2CG PUSCH activation and the second indication in the DCI for PDSCH.

16. The method of claim 15, wherein the first indication in the type 2CG PUSCH activation is for indicating the PUSCH priority and/or applying RNTI, CORESET, search space, DCI format, a field in the DCI for the type 2CG PUSCH activation; and/or

The second indication in the DCI for PDSCH is to indicate the HARQ-ACK priority and/or to apply the RNTI, the CORESET, the search space, the DCI format, the field in the DCI for the type 2CG PUSCH activation.

17. The method of claim 15 or 16, wherein the first parameter is configured to match CG priority and the HARQ-ACK priority if a level 2 physical priority of the CG PUSCH is covered by the type 2CG PUSCH activation.

18. The method of claim 17, wherein the first parameter is used to indicate whether the release 15PUSCH transmission scheme is valid or the release 16PUSCH transmission scheme is valid.

19. The method of claim 17 or 18, wherein a time domain resource allocation is determined by a type 2CG activation and/or the first parameter.

20. The method of any of claims 1-3, wherein the first parameter comprises a repK parameter configured in the IE, the repK parameter indicating a number of repetitions of the PUSCH transmission scheme.

21. The method of claim 20, wherein, if the repK parameter is greater than 1, applying the release 15PUSCH transmission scheme; otherwise, if the repK parameter is not greater than 1, the PUSCH transmission scheme depends on the DCI format.

22. The method of claim 21, wherein the PUSCH transmission scheme depends on the DCI format if the repK parameter is equal to 1.

23. The method of claim 22, wherein the PUSCH transmission scheme is associated with the DCI format.

24. The method of claim 23, wherein an association between the PUSCH transmission scheme and the DCI format is configured by higher layer parameters.

25. The method according to any of claims 20-24, wherein PUSCH transmission scheme configuration is semi-static for configuration grants.

26. The method of any of claims 1-3, wherein the first parameters include power control parameters configured in the IE for power control for the CG PUSCHs other than a first CG PUSCH, and open loop parameters in DCI for type 2 configuration grant activation for power control for the first CG PUSCH.

27. A method of wireless communication by a base station, comprising:

configuring an Information Element (IE) to a User Equipment (UE); and

control the UE to perform a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of:

uplink Control Information (UCI) multiplexing in CG resources;

indicating a Physical Uplink Shared Channel (PUSCH) priority;

indicating the validity of the PUSCH transmission scheme;

indicating a number of repetitions of a PUSCH transmission scheme; or

Power control for CG PUSCH.

28. The method of claim 27, wherein the IE comprises a configuredggrantconfig IE.

29. The method of claim 27 or 28, wherein the PUSCH transmission scheme comprises a release 15PUSCH transmission scheme and/or a release 16PUSCH transmission scheme.

30. The method of any of claims 27-29, wherein the first parameter comprises a UCI-OnPUSCH parameter configured in the IE, and the UCI-OnPUSCH parameter is used for UCI multiplexing in the CG resources.

31. The method of claim 30, wherein the UCI-OnPUSCH parameter is configured to match CG priority if a level 2 physical priority of the CG PUSCH is determined by an indication in each CG configuration from the base station.

32. The method of claim 31, wherein the indication in each CG configuration comprises a Radio Resource Control (RRC) parameter.

33. The method of any of claims 27-29, wherein the first parameter comprises one of two UCI-OnPUSCH or BetaOffsets parameters configured in the IE.

34. The method of claim 33, wherein controlling the UE to perform the CG transmission using the first parameter from the IE further comprises:

the UE receiving an indication in a type 2CG PUSCH activation from the base station; and

the UE selects one of two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the type 2CG PUSCH activation.

35. The method of claim 34, wherein the indication in the type 2CG PUSCH activation is used to indicate the PUSCH priority and/or a Radio Network Temporary Identifier (RNTI) to which DCI for the type 2CG PUSCH activation applies, a control resource set (CORESET), a search space, a Downlink Control Information (DCI) format, a field in the DCI.

36. The method of claim 34 or 35, wherein the first parameter is configured to match CG priority if a level 2 physical priority of the CG PUSCH is covered by the type 2CG PUSCH activation.

37. The method of claim 33, wherein controlling the UE to perform the CG transmission using the first parameter from the IE further comprises:

the UE receiving an indication in DCI for a Physical Downlink Shared Channel (PDSCH) from the base station, wherein HARQ-CK for PDSCH is multiplexed in a type 2CG PUSCH; and

the UE selects one of the two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the DCI for the PDSCH.

38. The method of claim 37, wherein the indication in the DCI for PDSCH indicates the HARQ-CK priority and/or applies RNTI, CORESET, search space, DCI format, fields in the DCI for the type 2CG PUSCH activation.

39. The method of claim 37 or 38, wherein the first parameter is configured to match CG priority and the HARQ-ACK priority if a level 2 physical priority of the CG PUSCH is determined by an indication in each CG configuration from the base station.

40. The method of claim 39, wherein the indication in each CG configuration comprises an RRC parameter.

41. The method of claim 33, wherein controlling the UE to perform the CG transmission using the first parameter from the IE further comprises:

the UE receiving a first indication in type 2CG PUSCH activation and a second indication in DCI for a PDSCH from the base station, wherein HARQ-CK for PDSCH is multiplexed in type 2CG PUSCH; and

the UE selects one of two UCI-OnPUSCH or BetaOffsets parameters based on the first indication in the type 2CG PUSCH activation and the second indication in the DCI for the PDSCH.

42. The method of claim 41, wherein the first indication in the type 2CG PUSCH activation is to indicate the PUSCH priority and/or an RNTI, a CORESET, a search space, a DCI format, a field in the DCI to apply DCI for the type 2CG PUSCH activation; and/or

43. The method of claim 41 or 42, wherein the first parameter is configured to match CG priority and the HARQ-ACK priority if a level 2 physical priority of the CG PUSCH is covered by the type 2CG PUSCH activation.

44. The method of claim 43, wherein the first parameter is used to indicate whether the release 15PUSCH transmission scheme is valid or the release 16PUSCH transmission scheme is valid.

45. The method of claim 43 or 44, wherein a time domain resource allocation is determined by a type 2CG activation and/or the first parameter.

46. The method of any of claims 27-29, wherein the first parameter comprises a repK parameter configured in the IE, the repK parameter indicating a number of repetitions of the PUSCH transmission scheme.

47. The method of claim 46, wherein, if the repK parameter is greater than 1, applying the release 15PUSCH transmission scheme; otherwise, if the repK parameter is not greater than 1, the PUSCH transmission scheme depends on the DCI format.

48. The method of claim 47, wherein the PUSCH transmission scheme depends on the DCI format if the repK parameter is equal to 1.

49. The method of claim 48, wherein the PUSCH transmission scheme is associated with the DCI format.

50. The method of claim 49, wherein an association between the PUSCH transmission scheme and the DCI format is configured by higher layer parameters.

51. The method of any of claims 46-50, wherein the PUSCH transmission scheme configuration is semi-static for configuration grants.

52. The method of any of claims 27-29, wherein the first parameters comprise power control parameters configured in the IE for power control for the CG PUSCHs other than a first CG PUSCH, and open loop parameters in DCI for type 2 configuration grant activation for power control for the first CG PUSCH.

53. A User Equipment (UE), comprising:

a memory;

a transceiver; and

a processor coupled with the memory and the transceiver;

wherein the processor is configured with an Information Element (IE) from a base station; and

wherein the processor is configured to perform a Configuration Grant (CG) transmission using a first parameter from the IE, the first parameter for performing at least one of:

uplink Control Information (UCI) multiplexing in CG resources;

indicating a Physical Uplink Shared Channel (PUSCH) priority;

indicating the validity of the PUSCH transmission scheme;

indicating a number of repetitions of a PUSCH transmission scheme; or

Power control for CG PUSCH.

54. The UE of claim 53, wherein the IE comprises a ConfiguredGrantConfig IE.

55. The UE of claim 53 or 54, wherein the PUSCH transmission scheme comprises a release 15PUSCH transmission scheme and/or a release 16PUSCH transmission scheme.

56. The UE of any of claims 53-55, wherein the first parameters include UCI-OnPUSCH parameters configured in the IE, and the UCI-OnPUSCH parameters are used for UCI multiplexing in the CG resources.

57. The UE of claim 56, wherein the UCI-OnPUSCH parameter is configured to match CG priority if the CG PUSCH level 2 physical priority is determined by an indication in each CG configuration from the base station.

58. The UE of claim 57, wherein the indication in each CG configuration comprises a Radio Resource Control (RRC) parameter.

59. The UE of any of claims 53-55, wherein the first parameter comprises one of two UCI-OnPUSCH or BetaOffsets parameters configured in the IE.

60. The UE of claim 59, wherein the processor performing the CG transmission using the first parameter from the IE further comprises:

control the transceiver to receive an indication in a type 2CG PUSCH activation from the base station; and

the processor selects one of the two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the type 2CG PUSCH activation.

61. The UE of claim 60, wherein the indication in the type 2CG PUSCH activation is to indicate the PUSCH priority and/or a Radio Network Temporary Identifier (RNTI) to which a DCI for the type 2CG PUSCH activation applies, a control resource set (CORESET), a search space, a Downlink Control Information (DCI) format, a field in the DCI.

62. The UE of claim 60 or 61, wherein the first parameter is configured to match CG priority if a level 2 physical priority of the CG PUSCH is covered by the type 2CG PUSCH activation.

63. The UE of claim 59, wherein the processor performing the CG transmission using the first parameter from the IE further comprises:

control the transceiver to receive an indication in DCI for a Physical Downlink Shared Channel (PDSCH) from the base station, wherein HARQ-CK for PDSCH is multiplexed in a type 2CG PUSCH; and

the processor selects one of two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the DCI for the PDSCH.

64. The UE of claim 63, wherein the indication in the DCI for PDSCH is to indicate the HARQ-CK priority and/or an RNTI, a CORESET, a search space, a DCI format, a field in the DCI to which DCI for type 2CG PUSCH activation applies.

65. The UE of claim 63 or 64, wherein the first parameter is configured to match a CG priority and the HARQ-ACK priority if a level 2 physical priority of the CG PUSCH is determined by an indication in each CG configuration from the base station.

66. The UE of claim 65, wherein the indication in each CG configuration comprises an RRC parameter.

67. The UE of claim 59, wherein the processor performing the CG transmission using the first parameter from the IE further comprises:

control the transceiver to receive a first indication in a type 2CG PUSCH activation and a second indication in DCI for a PDSCH from the base station, wherein HARQ-CK for PDSCH is multiplexed in a type 2CG PUSCH; and

the processor selects one of the two UCI-OnPUSCH or BetaOffsets parameters based on the first indication in the type 2CG PUSCH activation and the second indication in the DCI for PDSCH.

68. The UE of claim 67, wherein the first indication in the type 2CG PUSCH activation is to indicate the PUSCH priority and/or an RNTI, a CORESET, a search space, a DCI format, a field in the DCI to apply DCI for the type 2CG PUSCH activation; and/or

The second indication in the DCI for PDSCH is used to indicate the HARQ-ACK priority and/or to apply the RNTI, the CORESET, the search space, the DCI format, the field in the DCI for the DCI of the type 2CG PUSCH activation.

69. The UE of claim 67 or 68, wherein the first parameter is configured to match CG priority and the HARQ-ACK priority if a level 2 physical priority of the CG PUSCH is covered by the type 2CG PUSCH activation.

70. The UE of claim 69, wherein the first parameter is to indicate whether the release 15PUSCH transmission scheme is valid or the release 16PUSCH transmission scheme is valid.

71. The UE of claim 69 or 70, wherein a time domain resource allocation is determined by a type 2CG activation and/or the first parameter.

72. The UE of any of claims 53 to 55, wherein the first parameter comprises a repK parameter configured in the IE, the repK parameter to indicate a number of repetitions of the PUSCH transmission scheme.

73. The UE of claim 72, wherein, if the repK parameter is greater than 1, the release 15PUSCH transmission scheme is applied; otherwise, if the repK parameter is not greater than 1, the PUSCH transmission scheme depends on the DCI format.

74. The UE of claim 73, wherein the PUSCH transmission scheme depends on the DCI format if the repK parameter is equal to 1.

75. The UE of claim 74, wherein the PUSCH transmission scheme is associated with the DCI format.

76. The UE of claim 75, wherein an association between the PUSCH transmission scheme and the DCI format is configured by higher layer parameters.

77. The UE of any of claims 72-76, wherein a PUSCH transmission scheme configuration is semi-static for configuration grants.

78. The UE of any of claims 53-55, wherein the first parameters include power control parameters configured in the IE for power control for the CG PUSCHs other than a first CG PUSCH, and open loop parameters in DCI for type 2 configuration grant activation for power control for the first CG PUSCH.

79. A base station, comprising:

a memory;

a transceiver; and

a processor coupled with the memory and the transceiver;

wherein the processor is configured to configure an Information Element (IE) to a User Equipment (UE); and

wherein the processor is configured to control the UE to perform a Configuration Grant (CG) transmission using a first parameter from the IE, wherein the first parameter is for performing at least one of:

uplink Control Information (UCI) multiplexing in CG resources;

indicating a Physical Uplink Shared Channel (PUSCH) priority;

indicating the validity of the PUSCH transmission scheme;

indicating a number of repetitions of a PUSCH transmission scheme; or

Power control for CG PUSCH.

80. The base station of claim 79, wherein the IE comprises a ConfiguredGrantConfig IE.

81. The base station according to claim 79 or 78, wherein the PUSCH transmission scheme comprises a release 15PUSCH transmission scheme and/or a release 16PUSCH transmission scheme.

82. The base station of any of claims 79 to 81, wherein the first parameters comprise UCI-OnPUSCH parameters configured in the IE, and the UCI-OnPUSCH parameters are used for UCI multiplexing in the CG resources.

83. The base station of claim 82, wherein the UCI-OnPUSCH parameter is configured to match CG priority if the CG PUSCH level 2 physical priority is determined by an indication in each CG configuration from the base station.

84. The base station of claim 83, wherein the indication in each CG configuration comprises a Radio Resource Control (RRC) parameter.

85. The base station of any of claims 79 to 81, wherein the first parameter comprises one of two UCI-OnPUSCH or BetaOffsets parameters configured in the IE.

86. The base station of claim 85, wherein the processor controlling the UE to perform the CG transmission using the first parameter from the IE further comprises:

87. The base station of claim 86, wherein the indication in the type 2CG PUSCH activation is to indicate the PUSCH priority and/or a Radio Network Temporary Identifier (RNTI) to which a DCI for the type 2CG PUSCH activation applies, a control resource set (CORESET), a search space, a Downlink Control Information (DCI) format, a field in the DCI.

88. The base station of claim 86 or 87, wherein the first parameter is configured to match CG priority if a level 2 physical priority of the CG PUSCH is covered by the type 2CG PUSCH activation.

89. The base station of claim 85, wherein the processor controlling the UE to perform the CG transmission using the first parameter from the IE further comprises:

the UE selects one of two UCI-OnPUSCH or BetaOffsets parameters based on the indication in the DCI for the PDSCH.

90. The base station of claim 89, wherein the indication in the DCI for PDSCH indicates the HARQ-CK priority and/or an RNTI, CORESET, search space, DCI format, field in the DCI to which DCI for type 2CG PUSCH activation is applied.

91. The base station of claim 89 or 90, wherein the first parameter is configured to match CG priority and the HARQ-ACK priority if a level 2 physical priority of the CG PUSCH is determined by an indication in each CG configuration from the base station.

92. The base station of claim 91, wherein the indication in each CG configuration comprises an RRC parameter.

93. The base station of claim 85, wherein the processor controlling the UE to perform the CG transmission using the first parameter from the IE further comprises:

94. The base station of claim 93, wherein the first indication in the type 2CG PUSCH activation is to indicate the PUSCH priority and/or to apply RNTI, CORESET, search space, DCI format, field in the DCI for the type 2CG PUSCH activation; and/or

95. The base station of claim 93 or 94, wherein the first parameter is configured to match CG priority and the HARQ-ACK priority if a level 2 physical priority of the CG PUSCH is covered by the type 2CG PUSCH activation.

96. The base station of claim 95, wherein the first parameter indicates whether the release 15PUSCH transmission scheme is valid or the release 16PUSCH transmission scheme is valid.

97. The base station of claim 95 or 96, wherein a time domain resource allocation is determined by type 2CG activation and/or the first parameter.

98. The base station of any one of claims 79 to 81, wherein the first parameter comprises a repK parameter configured in the IE, the repK parameter indicating a number of repetitions of the PUSCH transmission scheme.

99. The base station of claim 98, wherein, if the repK parameter is greater than 1, the release 15PUSCH transmission scheme is applied; otherwise, if the repK parameter is not greater than 1, the PUSCH transmission scheme depends on the DCI format.

100. The base station of claim 99, wherein the PUSCH transmission scheme depends on the DCI format if the repK parameter is equal to 1.

101. The base station of claim 100, wherein the PUSCH transmission scheme is associated with the DCI format.

102. The base station of claim 101, wherein an association between the PUSCH transmission scheme and the DCI format is configured by higher layer parameters.

103. The base station of any of claims 98 to 102, wherein the PUSCH transmission scheme configuration is semi-static for configuration grants.

104. The base station of any of claims 79 to 81, wherein the first parameters comprise power control parameters configured in the IE for power control for the CG PUSCHs other than a first CG PUSCH, and open loop parameters in DCI for type 2 configuration grant activation for power control for the first CG PUSCH.

105. A non-transitory machine-readable storage medium having instructions stored thereon, which when executed by a computer, cause the computer to perform the method of any of claims 1-52.

106. A chip, comprising:

a processor configured to invoke and execute a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any of claims 1 to 52.

107. A computer-readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to perform the method of any one of claims 1 to 52.

108. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 52.

109. A computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 52.