User Equipment, Base Station, and Signaling for Authorization of Multiple Active Configurations

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a common configuration, the common configuration including parameters shared by grants of multiple configurations. The UE also includes a transmitting circuit configured to perform a transmission on a physical uplink shared channel (PUSCH) based on the parameters shared by the grants of the multiple configurations of the common configuration.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems and, more particularly, to user equipment (UE), base stations, and signaling for authorization of multiple active configurations. Background Art

[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable service, expanded coverage, and enhanced functionality. A wireless communication system can provide communication for multiple wireless communication devices, each of which can be served by a base station. A base station is a device that communicates with wireless communication devices.

[0003] With the development of wireless communication equipment, people have been seeking ways to improve communication capacity, speed, flexibility and / or efficiency. However, improving communication capacity, speed, flexibility and / or efficiency may bring certain problems.

[0004] For example, a wireless communication device may use a communication structure to communicate with one or more devices. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods that improve communication flexibility and / or efficiency may be advantageous. Summary of the Invention

[0005] In one example, a user equipment (UE) communicating with a base station includes: a receiving circuit configured to: receive a radio resource control (RRC) message including first information indicating a repetition type for a first configured grant (CG) physical uplink shared channel (PUSCH) transmission, receive an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, receive an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission; a transmitting circuit configured to: perform a first CG PUSCH transmission based on the first information and the third information, and perform a second CG PUSCH transmission based on the second information and the third information.

[0006] In one example, a base station device that communicates with a user equipment (UE) includes: a transmission circuit configured to: transmit a radio resource control (RRC) message including first information indicating a repetition type for a first configured grant (CG) physical uplink shared channel (PUSCH) transmission, transmit an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, and transmit an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission; and a receiving circuit configured to: receive a first CG PUSCH transmission based on the first information and the third information, and receive a second CG PUSCH transmission based on the second information and the third information.

[0007] In one example, a communication method of a user equipment includes: receiving a radio resource control (RRC) message including first information indicating a repetition type for a grant (CG) physical uplink shared channel (PUSCH) transmission of a first configuration, receiving an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, receiving an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission, performing a first CG PUSCH transmission based on the first information and the third information, and performing a second CG PUSCH transmission based on the second information and the third information.

[0008] In one example, a communication method of a base station device includes: transmitting a radio resource control (RRC) message including first information indicating a repetition type for a first configured grant (CG) physical uplink shared channel (PUSCH) transmission, transmitting an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, transmitting an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission, receiving a first CG PUSCH transmission based on the first information and the third information, and receiving a second CG PUSCH transmission based on the second information and the third information. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] ] Figure 1 is a block diagram illustrating one specific implementation of one or more base station devices (gNBs) and one or more user equipment (UEs) in which systems and methods for signaling may be implemented.

[0010] Figure 2 Examples of multiple parameters are shown.

[0011] Figure 3 is a diagram showing one example of a resource grid and resource blocks.

[0012] Figure 4 An example of a resource area is shown.

[0013] Figure 5 An example of UL transmission corresponding to a configured grant is shown.

[0014] Figure 6 Various components that may be utilized in a UE are shown.

[0015] Figure 7 Various components that may be utilized in a gNB are shown.

[0016] Figure 8 is a block diagram illustrating one specific implementation of a UE in which one or more of the systems and / or methods described herein may be implemented.

[0017] Figure 9 is a block diagram illustrating one specific implementation of a gNB in which one or more of the systems and / or methods described herein may be implemented.

[0018] Figure 10 is a block diagram illustrating a specific implementation of a gNB.

[0019] Figure 11 is a block diagram illustrating a specific implementation of a UE. DETAILED DESCRIPTION

[0020] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a common configuration, the common configuration including parameters shared by grants of multiple configurations. The UE also includes a transmitting circuit configured to perform a transmission on a physical uplink shared channel (PUSCH) based on the parameters shared by the grants of the multiple configurations of the common configuration.

[0021] In one approach, parameters in a configuration-specific authorization can override parameters in a public configuration. In another approach, parameters in a public configuration can override parameters in a configuration-specific authorization.

[0022] The shared parameters may be included in the configuration of the authorization of the primary configuration. The authorization of the secondary configuration may follow the shared parameters included in the configuration of the authorization of the primary configuration.

[0023] The present invention also describes a base station apparatus. The base station apparatus includes a transmission circuit configured to transmit a common configuration, the common configuration including parameters shared by grants of multiple configurations. The base station apparatus also includes a reception circuit configured to receive transmissions on a PUSCH based on the parameters shared by the grants of the multiple configurations of the common configuration.

[0024] The present invention also describes a communication method for a UE. The method includes receiving a common configuration, the common configuration including parameters shared by multiple configured grants. The method also includes performing a transmission on a PUSCH based on the parameters shared by the multiple configured grants in the common configuration.

[0025] The present invention also describes a communication method for a base station apparatus. The method includes transmitting a common configuration, the common configuration including parameters shared by grants of multiple configurations. The method also includes receiving a transmission on a PUSCH based on the parameters shared by the grants of the multiple configurations of the common configuration.

[0026] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that develops globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems, and devices.

[0027] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future needs. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0028] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, LTE-Advanced (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15). However, the scope of the present disclosure should not be limited in this respect. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0029] A wireless communication device may be an electronic device that transmits voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, wireless communication devices are generally referred to as UEs. However, since the scope of the present disclosure should not be limited to 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to represent the more general term "wireless communication device." A UE may also be more generally referred to as a terminal device.

[0030] In the 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a home-enhanced or evolved Node B (HeNB), or some other similar term. Since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station," "Node B," "eNB," "gNB," and "HeNB" may be used interchangeably herein to refer to the more general term "base station." In addition, the term "base station" may be used to refer to an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to refer to a wireless communication device and / or a base station. An eNB may also be more generally referred to as a base station device.

[0031] It should be noted that, as used herein, a "cell" can be any communication channel designated by a standardization or regulatory body for use with International Mobile Telecommunications-Advanced (IMT-Advanced), and all or a subset thereof, adopted by 3GPP as an authorized frequency band (e.g., a frequency band) for communication between an eNB and a UE. It should also be noted that, in the general description of E-UTRA and E-UTRAN, as used herein, a "cell" can be defined (e.g., specified) as "a combination of downlink resources and optional uplink resources." The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources can be indicated in system information transmitted on the downlink resources.

[0032] The fifth-generation communication system, referred to as NR (New Radio Technology) by 3GPP, envisions the use of time, frequency, and / or spatial resources to enable services such as eMBB (enhanced Mobile Broadband) transmission, URLLC (Ultra-Reliable and Low-Latency Communication) transmission, and eMTC (Massive Machine Type Communication) transmission. Furthermore, in NR, one or more bandwidth parts (BWPs) in a serving cell and / or for one or more serving cells may be designated (e.g., configured) for transmission of different services. A user equipment (UE) may receive downlink signals and / or transmit uplink signals in the BWPs of one or more serving cells.

[0033] In order for services to efficiently use time, frequency, and / or space resources, it would be useful to be able to effectively control downlink and / or uplink transmissions. Therefore, a process for effectively controlling downlink and / or uplink transmissions should be designed. Therefore, a detailed design of the process for downlink and / or uplink transmissions may be beneficial.

[0034] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods generally described and illustrated in the drawings herein can be arranged and designed in a variety of different implementations. Therefore, the following more detailed description of several implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0035] Figure 1 is a block diagram illustrating one implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for signaling may be implemented. The one or more UEs 102 communicate with the one or more gNBs 160 using one or more physical antennas 122a-n. For example, the UE 102 transmits electromagnetic signals to and receives electromagnetic signals from the gNB 160 using the one or more physical antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n. In some implementations, the terms "base station," "eNB," and / or "gNB" may refer to and / or be replaced by the term "transmission reception point (TRP)." For example, in some implementations, in conjunction with Figure 1 The gNB160 described may be a TRP.

[0036] The UE 102 and the gNB 160 may communicate with each other using one or more channels and / or one or more signals 119, 121. For example, the UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include physical shared channels (e.g., PUSCH (Physical Uplink Shared Channel)) and / or physical control channels (e.g., PUCCH (Physical Uplink Control Channel)). For example, the one or more gNBs 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119. Examples of downlink channels 119 include physical shared channels (e.g., PDSCH (Physical Downlink Shared Channel)) and / or physical control channels (PDCCH (Physical Downlink Control Channel)). Other types of channels and / or signals may also be used.

[0037] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operations module 124. For example, one or more receive paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0038] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.

[0039] The demodulator 114 may demodulate the one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signal. The decoder 108 may generate a decoded signal 110, which may include the UE-decoded signal 106 (also referred to as the first UE-decoded signal 106). For example, the first UE-decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal in the decoded signal 110 (also referred to as the second UE-decoded signal 110) may include overhead data and / or control data. For example, the second UE-decoded signal 110 may provide data that the UE operations module 124 may use to perform one or more operations.

[0040] Generally speaking, the UE operations module 124 can enable the UE 102 to communicate with the one or more gNBs 160. The UE operations module 124 can include one or more of the UE scheduling modules 126.

[0041] The UE scheduling module 126 may perform downlink reception and uplink transmission. The one or more downlink receptions may include reception of data, reception of downlink control information, and / or reception of downlink reference signals. In addition, uplink transmissions may include transmission of data, transmission of uplink control information, and / or transmission of uplink reference signals.

[0042] In a radio communication system, physical channels (uplink physical channels and / or downlink physical channels) may be defined. The physical channels (uplink physical channels and / or downlink physical channels) may be used to transmit information delivered from higher layers.

[0043] For example, in the uplink, a PRACH (physical random access channel) may be defined. In some methods, the PRACH (e.g., a random access procedure) may be used for an initial access connection establishment procedure, a handover procedure, a connection reestablishment, timing adjustment (e.g., for synchronization of uplink transmissions, for UL synchronization), and / or for requesting uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).

[0044] In another example, a physical uplink control channel (PUCCH) may be defined. The PUCCH may be used to transmit uplink control information (UCI). The UCI may include a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI), and / or a scheduling request (SR). The HARQ-ACK is used to indicate a positive acknowledgement (ACK) or negative acknowledgement (NACK) of downlink data (e.g., a transport block, a medium access control protocol data unit (MAC PDU), and / or a downlink shared channel (DL-SCH)). The CSI is used to indicate the state of a downlink channel (e.g., a downlink signal). In addition, the SR is used to request resources for uplink data (e.g., a transport block, a MAC PDU, and / or an uplink shared channel (UL-SCH)).

[0045] Here, DL-SCH and / or UL-SCH may be transport channels used in the MAC layer. Furthermore, a transport block (TB) and / or a MAC PDU may be defined as a unit of a transport channel used in the MAC layer. A transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver a transport block to the physical layer (e.g., the MAC layer delivers data as a transport block to the physical layer). In the physical layer, a transport block may be mapped to one or more codewords.

[0046] In the downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used to transmit downlink control information (DCI). Here, more than one DCI format may be defined for DCI transmission on the PDCCH. That is, fields may be defined in the DCI format and mapped to information bits (e.g., DCI bits).

[0047] For example, DCI format 1_0 for scheduling PDSCH in a cell may be defined as a DCI format for downlink. In addition, as described herein, one or more radio network temporary identifiers (e.g., cell RNTI (C-RNTI), configured scheduling RNTI (CS-RNTI), system information RNTI (SI-RNTI), and / or random access RNTI (RA-RNTI)) may be used to transmit DCI format 1_0. In addition, DCI format 1_0 may be monitored (e.g., transmitted, mapped) in a common search space (CSS) and / or a UE-specific search space (USS). Alternatively, DCI format 1_0 may be monitored (e.g., transmitted, mapped) only in the CSS.

[0048] For example, the DCI included in DCI format 1_0 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, or alternatively, the DCI included in DCI format 1_0 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_0 may be a TPC (e.g., transmit power control) command for a scheduled PUCCH.

[0049] Additionally or alternatively, DCI format 1_1 for scheduling the PDSCH in the cell may be defined as a DCI format for the downlink. Additionally or alternatively, a C-RNTI or CS-RNTI may be used to transmit DCI format 1_1. Additionally or alternatively, DCI format 1_1 may be monitored (e.g., transmitted and / or mapped) in the CSS and / or USS.

[0050] For example, the DCI included in DCI format 1_1 may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_1 may be a TPC command for a scheduled PUCCH. Additionally or alternatively, the DCI included in DCI format 1_1 may be a CSI request for requesting (e.g., triggering) transmission of CSI (e.g., a CSI report (e.g., an aperiodic CSI report)).

[0051] Additionally or alternatively, DCI format 0_0 for scheduling the PUSCH in the cell may be defined as the DCI format for the uplink. Additionally or alternatively, a C-RNTI, a CS-RNTI, and / or a temporary C-RNTI may be used to transmit DCI format 0_0. Additionally or alternatively, DCI format 0_0 may be monitored (e.g., transmitted, mapped) in the CSS and / or USS. Alternatively, DCI format 0_0 may be monitored (e.g., transmitted, mapped) only in the CSS.

[0052] For example, the DCI included in DCI format 0_0 may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_0 may be a redundancy version. Additionally or alternatively, the DCI included in DCI format 0_0 may be a TPC command for a scheduled PUSCH.

[0053] Additionally or alternatively, DCI format 0_1 for scheduling the PUSCH in the cell may be defined as the DCI format for the uplink. Additionally or alternatively, C-RNTI and CS-RNTI may be used to transmit DCI format 0_1. Additionally or alternatively, DCI format 0_1 may be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0054] For example, the DCI included in DCI format 0_1 may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_1 may be a TPC command for a scheduled PUSCH. Additionally or alternatively, the DCI included in DCI format 0_1 may be a CSI request for requesting a CSI report. Additionally or alternatively, as described below, the DCI included in DCI format 0_1 may be information indicating a configured index of a configured grant.

[0055] Additionally or alternatively, upon receiving DCI format 1_0 and / or DCI format 1_1 (e.g., based on detecting DCI format 1_0 and / or DCI format 1_1), UE 102 may perform PDSCH reception. Additionally or alternatively, upon receiving DCI format 0_0 and / or DCI format 0_1 (e.g., based on detecting DCI format 0_0 and / or DCI format 0_1), UE 102 may perform PUSCH transmission.

[0056] Here, as described above, the RNTI (e.g., Radio Network Temporary Identifier) allocated to UE 102 may be used for transmission of DCI (e.g., DCI format, DL control channel (e.g., PDCCH)). That is, gNB 160 may transmit information for configuring (e.g., allocating) the RNTI to UE 102 (e.g., by using an RRC message).

[0057] For example, a CRC (cyclic redundancy check) parity bit (also referred to as CRC) generated based on the DCI is appended to the DCI, and after appending, the CRC parity bit is scrambled by the RNTI. The UE 102 may attempt to decode (e.g., blindly decode, monitor, or detect) the DCI to which the CRC parity bit scrambled by the RNTI is appended. For example, the UE 102 may detect a downlink control channel (e.g., PDCCH, DCI, or DCI format) based on blind decoding. That is, the UE 102 may decode the downlink control channel using the CRC scrambled by the RNTI. In other words, the UE 102 may monitor the downlink control channel using the RNTI. For example, the UE 102 may detect the DCI format using the RNTI.

[0058] Here, the RNTI may include C-RNTI (Cell-RNTI), CS-RNTI (Configured Scheduling C-RNTI), SI-RNTI (System Information RNTI), RA-RNTI (Random Access RNTI) and / or Temporary C-RNTI.

[0059] For example, the C-RNTI can be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, the CS-RNTI can be a unique identifier for scheduling transmissions based on configuration-based authorization. Additionally or alternatively, the SI-RNTI can be used to identify a system message (SI) (e.g., an SI message) mapped on the BCCH and dynamically carried on the DL-SCH. Additionally or alternatively, the SI-RNTI can be used for broadcasting of the SI. Additionally or alternatively, the RA-RNTI can be an identifier for a random access procedure (e.g., Msg.2 transmission). Additionally or alternatively, a temporary C-RNTI can be used for a random access procedure (e.g., scheduling of a Msg.3 (re)transmission (e.g., Msg.3 PUSCH (re)transmission)).

[0060] Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, when a PDSCH (e.g., PDSCH resources) is scheduled using a DCI format, the UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resources). Additionally or alternatively, when a PUSCH (e.g., PUSCH resources) is scheduled using a DCI format, the UE 102 may transmit uplink data on the scheduled PUSCH (e.g., PUSCH resources). For example, the PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport blocks). Additionally or alternatively, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport blocks).

[0061] Furthermore, the PDSCH and / or PUSCH may be used to transmit information from higher layers (e.g., the radio resource control (RRC) layer and / or the MAC layer). For example, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit RRC messages (RRC signals). Additionally or alternatively, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit MAC control elements (MAC CEs). Herein, the RRC messages and / or MAC CEs are also referred to as higher layer signals.

[0062] In some methods, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used to broadcast a Master Information Block (MIB). Here, system information may be divided into a MIB and multiple System Information Blocks (SIBs). For example, the MIB may be used to carry minimum system information. Additionally or alternatively, the SIB may be used to carry system information messages.

[0063] In some methods, in the downlink, a synchronization signal (SS) may be defined. The SS may be used to acquire time and / or frequency synchronization with a cell. Additionally or alternatively, the SS may be used to detect the physical layer cell ID of a cell.

[0064] In uplink radio communication, the UL RS may be used as an uplink physical signal. Additionally or alternatively, in downlink radio communication, the DL RS may be used as a downlink physical signal. The uplink physical signal and / or the downlink physical signal may not be used to transmit information provided by a higher layer, but may be used by the physical layer.

[0065] Here, for simplicity of description, in some implementations, it may be assumed that the downlink physical channels and / or downlink physical signals described herein are included in downlink signals (e.g., DL signals). Additionally or alternatively, for simplicity of description, in some implementations, it may be assumed that the uplink physical channels and / or uplink physical signals described herein are included in uplink signals (i.e., UL signals).

[0066] The UE operations module 124 may provide information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform a receiver 120 when to receive a retransmission.

[0067] UE operations module 124 may provide information 138 to demodulator 114. For example, UE operations module 124 may inform demodulator 114 of the modulation pattern expected for transmissions from gNB 160.

[0068] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of the encoding to expect for the transmission from the gNB 160.

[0069] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0070] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

[0071] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of the modulation type (e.g., constellation mapping) to be used for transmission to gNB 160. Modulator 154 may modulate coded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.

[0072] The UE operations module 124 may provide information 140 to the one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit signals to the gNB 160. For example, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may upconvert the modulated signal 156 and transmit the modulated signal to the one or more gNBs 160.

[0073] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operations module 182. For example, one or more receive paths and / or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

[0074] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and downconvert a signal to generate one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0075] Demodulator 172 may demodulate the one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to decoder 166. gNB 160 may use decoder 166 to decode the signals. Decoder 166 may generate one or more decoded signals 164, 168. For example, first eNB-decoded signal 164 may include received payload data, which may be stored in data buffer 162. Second eNB-decoded signal 168 may include overhead data and / or control data. For example, second eNB-decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that gNB operations module 182 may use to perform one or more operations.

[0076] Generally, the gNB operations module 182 may enable the gNB 160 to communicate with the one or more UEs 102. The gNB operations module 182 may include one or more of the gNB scheduling modules 194. The gNB scheduling module 194 may perform scheduling of downlink and / or uplink transmissions as described herein.

[0077] The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of the modulation pattern expected for transmissions from the UE 102.

[0078] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of the encoding to expect for transmissions from the UE 102.

[0079] gNB operations module 182 may provide information 101 to encoder 109. Information 101 may include data to be encoded and / or instructions for encoding. For example, gNB operations module 182 may instruct encoder 109 to encode information 101, including transmission data 105.

[0080] Encoder 109 may encode transmission data 105 and / or other information included in information 101 provided by gNB operations module 182. For example, encoding transmission data 105 and / or other information included in information 101 may involve error detection and / or correction coding, mapping data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. Encoder 109 may provide encoded data 111 to modulator 113. Transmission data 105 may include network data to be relayed to UE 102.

[0081] The gNB operations module 182 may provide information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of the modulation type (e.g., constellation mapping) to be used for transmission to the UE 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.

[0082] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when (or when not) to transmit signals to the UE 102. The one or more transmitters 117 may upconvert the modulated signal 115 and transmit the modulated signal to the one or more UEs 102.

[0083] It should be noted that DL subframes may be transmitted from the gNB 160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and the one or more UEs 102 may transmit data in standard special subframes.

[0084] It should also be noted that one or more of the elements or components thereof included in the eNB 160 and the UE 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

[0085] Figure 2 An example of multiple parameters 201 is shown. Figure 2 As shown, multiple parameters 201 (e.g., multiple subcarrier spacings) may be supported. For example, μ (e.g., subcarrier space configuration) and cyclic prefix (e.g., μ and cyclic prefix of a carrier bandwidth portion) may be configured by higher layer parameters (e.g., RRC messages) for downlink and / or uplink. Here, 15 kHz may be a reference parameter 201. For example, the RE of the reference parameter 201 may be defined as having a subcarrier spacing of 15 kHz in the frequency domain and a 2048Ts+CP length (e.g., 160Ts or 144Ts) in the time domain, where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds.

[0086] Additionally or alternatively, the number of OFDM symbols 203 per slot may be determined based on μ (eg, subcarrier spatial configuration). Here, for example, slot configuration 0 (eg, the number of OFDM symbols 203 per slot may be 14) and / or slot configuration (eg, the number of OFDM symbols 203 per slot may be 7) may be defined.

[0087] Figure 3 is a diagram illustrating one example of a resource grid 301 and resource blocks 391 (eg, for downlink and / or uplink). Figure 3 The illustrated resource grid 301 and resource blocks 391 may be used in some implementations of the systems and methods disclosed herein.

[0088] exist Figure 3 In the example, a subframe 369 may include Symbol 387. Additionally or alternatively, a resource block 391 may include multiple resource elements (REs) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) may be adopted, which may also be referred to as CP-OFDM. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. A downlink RB pair may include two downlink RBs 391 that are consecutive in the time domain. Additionally or alternatively, a downlink RB 391 may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k, l), where k and l are indices in the frequency domain and time domain, respectively.

[0089] Additionally or alternatively, in the uplink, in addition to CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) access scheme, also known as discrete Fourier transform spread OFDM (DFT-S-OFDM), may be employed. An uplink radio frame may include multiple pairs of uplink resource blocks 391. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. An uplink RB pair may include two uplink RBs 391 that are consecutive in the time domain. An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM / DFT-S-OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k, l) in the time slot, where k and l are indices in the frequency and time domains, respectively.

[0090] Each element and subcarrier configuration in the resource grid 301 (eg, antenna port p) is referred to as a resource element 389 and is uniquely identified by an index pair (k, l), where is an index in the frequency domain, and l refers to the symbol position in the time domain. The resource element (k, l) 389 on antenna port p and the subcarrier spacing configuration μ are denoted as (k, l) p, μ. A physical resource block 391 is defined as a continuous subcarrier in the frequency domain. Physical resource blocks 391 are spaced from 0 to Number. Physical resource block number in the frequency domain nThe relationship between PRB and resource element (k, l) is given by

[0091] Figure 4 An example of a resource region (e.g., a downlink resource region) is shown. A set 401 of one or more PRBs 491 (e.g., a control resource set (i.e., CORESET)) can be configured for DL control channel monitoring (e.g., PDCCH monitoring). For example, a CORESET is a set 401 of PRBs 491 in the frequency domain and / or time domain, within which the UE 102 attempts to decode DCI (e.g., DCI format, PDCCH). In the case where the PRBs 491 may or may not be frequency-contiguous and / or time-contiguous, the UE 102 may be configured with one or more control resource sets (e.g., CORESETs), and one DCI message may be mapped within the one control resource set. In the frequency domain, the PRB 491 is the resource unit size of the DL control channel (which may or may not include a DM-RS).

[0092] Based on the corresponding search space set, UE 102 may monitor a set of PDCCH candidates in one or more control resource sets (e.g., CORESETs) on the active DL bandwidth part (BWP) on each activated serving cell. Here, the term "monitoring" may imply that UE 102 attempts to decode each PDCCH (e.g., a set of PDCCH candidates) based on the monitored DCI format. Furthermore, a PDCCH candidate may be a candidate for possible mapping, allocation, and / or transmission of a DL control channel.

[0093] The set of PDCCH candidates to be monitored by UE 102 may be defined according to a search space set (e.g., also referred to as a search space). UE 102 may monitor the set of PDCCH candidates in the search space. The search space set may include a common search space (CSS, UE-common search space) and / or a user equipment-specific search space (USS, UE-specific search space).

[0094] That is, a CSS and / or USS may be defined (e.g., configured) in the region of a DL control channel. For example, the CSS may be used to transmit DCI to multiple UEs 102. For example, a Type 0-PDCCH common search space may be defined for a DCI format having a CRC scrambled by an SI-RNTI. Additionally or alternatively, a Type 1-PDCCH common search space may be defined for a DCI format having a CRC scrambled by an RA-RNTI, a temporary C-RNTI, and / or a C-RNTI. Additionally or alternatively, a Type 3-PDCCH common search space may be defined for a DCI format having a CRC scrambled by a C-RNTI and / or a CS-RNTI.

[0095] The USS may be used to transmit DCI to a specific UE 102. For example, the USS may be determined based on a radio network temporary identifier (RNTI) (e.g., C-RNTI). For example, the USS may be defined for a DCI format having a CRC scrambled by the C-RNTI and / or CS-RNTI.

[0096] Here, the gNB 160 may transmit first information for configuring (e.g., determining) one or more CORESETs using an RRC message. For example, for each DL BWP in a DL BWP (e.g., each DL BWP in a serving cell), the gNB 106 may transmit first information for configuring the one or more CORESETs using an RRC message. For example, the first information may include information for configuring an index of the CORESET. In addition, the first information may include information for configuring a plurality of consecutive symbols for the CORESET. In addition, the first information may include information for configuring a resource block set for the CORESET.

[0097] Additionally or alternatively, gNB 160 may transmit second information for configuring the search space set using an RRC message. For example, the second information may be configured for each search space set. For example, the second information may include information for configuring the index of the search space set. Additionally or alternatively, the second information may include information for configuring the index of the CORESET associated with the search space set. Additionally or alternatively, the second information may include information for indicating a PDCCH monitoring periodicity and / or a PDCCH monitoring offset at which UE 102 monitors the PDCCH in the search space set. Additionally or alternatively, the second information may include information for indicating a PDCCH monitoring pattern within a timeslot. For example, the information for indicating the PDCCH monitoring pattern may indicate the first symbol within the timeslot for PDCCH monitoring. For example, UE 102 may determine a PDCCH monitoring timing based on the PDCCH monitoring periodicity, the PDCCH monitoring offset, and / or the PDCCH monitoring pattern within the timeslot.

[0098] Additionally or alternatively, the second information may include information indicating the type of the search space set (e.g., information indicating whether the search space set is a CSS or a USS). Additionally or alternatively, the second information may include information of one or more DCI formats for instructing UE 102 to monitor the PDCCH in the search space set accordingly. For example, if the search space set is a CSS (e.g., if the search space set is configured as a CSS), DCI format 0_0 and / or DCI format 1_0 may be configured to monitor the PDCCH (e.g., a candidate for the PDCCH). Here, the DCI format for monitoring the PDCCH in the CSS may be scrambled by a C-RNTI, a CS-RNTI, a RA-RNTI, a temporary C-RNTI, a P-RNTI, and / or an SI-RNTI.

[0099] Additionally or alternatively, if the search space set is a USS (e.g., if the search space set is configured as a USS), DCI format 0_0 and / or DCI format 1_0 may be configured to monitor the PDCCH (e.g., a candidate for the PDCCH). Additionally or alternatively, if the search space set is a USS, DCI format 0_1 and / or DCI format 1_1 may be configured to monitor the PDCCH (e.g., a candidate for the PDCCH). For example, if the search space set is a USS, either the first set of DCI formats (DCI format 0_0 and / or DCI format 1_0) or the second set of DCI formats (DCI format 0_1 and / or DCI format 1_1) may be configured to monitor the PDCCH (e.g., a candidate for the PDCCH). Here, the DCI format for monitoring the PDCCH in the USS may be scrambled by the C-RNTI or the CS-RNTI. For example, the second information may be configured according to the search space set. That is, the second information may be configured for each search space set in the search space set.

[0100] Here, for example, for a serving cell, gNB 160 may configure four DL BWP sets (e.g., up to four DL BWPs, one DL BWP set) using RRC messaging (e.g., for reception by UE 102). Additionally or alternatively, gNB 160 may indicate active DL BWPs using a DCI format for the downlink. For example, for each DL BWP in a DL BWP set, gNB 160 may configure the subcarrier spacing, cyclic prefix, number of consecutive PRBs 491 (e.g., bandwidth of the PRBs), and / or index (e.g., index of the DL BWP) in the DL BWP set using RRC messaging.

[0101] Additionally or alternatively, for the serving cell, gNB 160 may configure four UL BWP sets (e.g., up to four UL BWPs, one UL BWP set) using RRC messaging (e.g., for transmission by UE 102). Additionally or alternatively, gNB 160 may indicate the active UL BWP using a DCI format for the uplink. Additionally or alternatively, for each UL BWP in the UL BWP set, gNB 160 may configure the subcarrier spacing, cyclic prefix, number of consecutive PRBs 491 (e.g., bandwidth of the PRBs), index (e.g., index of the UL BWP) in the UL BWP set using RRC messaging.

[0102] Additionally or alternatively, the UE 102 may perform reception on the PDCCH in the DL BWP and / or reception on the PDSCH in the DL BWP based on the configuration for the DL BWP. Additionally or alternatively, the UE 102 may perform based on the configuration for the UL BWP.

[0103] Figure 5 An example of UL transmission corresponding to the configured grant is shown. Figure 5 As described above, UE 102 may perform UL transmission (e.g., (re)transmission on the UL-SCH and / or (re)transmission on the PUSCH 503a-d). For example, UE 102 may perform UL transmission on the PUSCH 503a-d on the UL BWP in the serving cell. Here, the DL BWP and the UL BWP are linked together when the DL BWP index and the UL BWP index are the same. Furthermore, upon detecting a downlink signal (e.g., PDCCH 501a-d) on the DL BWP (e.g., the active DL BWP), UE 102 performs UL transmission corresponding to the configured grant on the UL BWP (e.g., the active UL BWP) that is linked to the DL BWP that detected the downlink signal.

[0104] For example, UL transmissions may be dynamically scheduled by an uplink grant in DCI (e.g., a DCI format for uplink with a CRC scrambled by the C-RNTI). Additionally or alternatively, UL transmissions may correspond to a configured grant type 1 and / or a configured grant type 2. Transmissions corresponding to the configured grant type 1 may be semi-statically configured to operate upon receiving the parameters of the configured ConfiguredGrantConfig including rrc-ConfiguredUplinkGrant, without detecting an uplink grant in DCI (e.g., a DCI format for uplink). Transmissions corresponding to the configured grant type 2 may be scheduled by an uplink grant in a valid activation DCI (e.g., an activation DCI format for uplink with a CRC scrambled by the CS-RNTI) after receiving the parameters of the ConfiguredGrantConfig not including rrc-ConfiguredUplinkGrant.

[0105] That is, UL transmission corresponding to the configured grant can be scheduled (e.g., activated) using a DCI format having a CRC scrambled by the CS-RNTI. Furthermore, two types of UL transmissions correspond to the configured grant. For example, one of the two types of UL transmissions may be referred to as transmission corresponding to the configured grant type 1 (e.g., configured grant type 1 transmission for UL transmission of the configured grant type 1). Furthermore, one of the two types of UL transmissions may be referred to as transmission corresponding to the configured grant type 2 (e.g., configured grant type 2 transmission for UL transmission of the configured grant type 2).

[0106] Here, for a configured grant type 1 transmission, the uplink grant may be provided by RRC (e.g., an RRC layer). For example, upon receiving an RRC message including an uplink grant (e.g., a configuration for a configured grant type 1 transmission), UE 102 may store the uplink grant as the configured grant.

[0107] In addition, for the configured grant type 2, the uplink grant may be provided by the PDCCH 501 (e.g., an activation DCI format to be used to indicate activation, a configured grant activation, and / or activation of a configured grant (e.g., a configured grant corresponding to the configured grant configuration). For example, in the case where the UE 102 receives an uplink grant (e.g., an activation DCI format), the UE 102 may store the uplink grant as the configured grant. In addition, in the case where the UE 102 receives an uplink grant (e.g., a deactivation DCI format to be used to indicate deactivation, a configured grant deactivation, and / or deactivation of a configured grant (e.g., a configured grant corresponding to the configured grant configuration)), the UE 102 clears the configured uplink grant (e.g., a configured grant corresponding to the deactivation-configured grant configuration with an index). That is, the uplink grant may be provided by the PDCCH 501. The uplink grant provided by 501 may be stored as a configured grant based on a DCI format (e.g., L1 signaling) indicating activation of the configured grant (e.g., a DCI format for indicating activation of the configured grant). Additionally or alternatively, the uplink grant provided by PDCCH 501 may be cleared based on a DCI format (e.g., L1 signaling) indicating deactivation of the configured grant (e.g., a DCI format for indicating deactivation of the configured grant).

[0108] That is, for a configured grant type 2 transmission, a DCI format with a CRC scrambled by the CS-RNTI may be used to indicate activation (e.g., a configured grant activation). Additionally, for a configured grant type 2 transmission, a DCI format with a CRC scrambled by the CS-RNTI may be used to indicate deactivation (e.g., a configured grant deactivation).

[0109] Here, a DCI format with a CRC scrambled by a CS-RNTI may be used to indicate retransmission (e.g., retransmission of a TB (e.g., retransmission of a TB transmitted by a configured grant type 1 transmission and / or a configured grant type 2 transmission). For example, retransmission may be indicated by using an NDI set to "1" (i.e., an NDI field set to "1," NDI="1"). Here, as described above, the NDI (i.e., an NDI field) may be included in a DCI format with a CRC scrambled by a CS-RNTI. That is, PUSCH retransmission may be scheduled using a PDCCH 501 (e.g., a DCI format for uplink) with an NDI set to "1" and a CRC scrambled by a CS-RNTI.

[0110] Here, for example, for a configured grant type 1 transmission, based on the configuration of the configured grant type 1 (e.g., for the serving cell), the UE 102 may store the uplink grant as the configured grant (e.g., for the serving cell). Additionally, the UE 102 may initialize (if not active) or reinitialize (if already active) the configured grant to start in symbol 1 according to a parameter (e.g., timeDomainOffset) and reoccur using a parameter (e.g., periodicity). Furthermore, after the uplink grant is configured for the configured grant type 1, the UE 102 may sequentially consider the Nth uplink grant to occur in association with a symbol for which:

[0111] [(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot)+(number of slots in a frame*numberOfSymbolsPerSlot)+number of symbols in a slot]=(timeDomainOffset+N*periodicity) modulo 1024. (1)

[0113] Additionally, for example, for a configured grant type 2 transmission, after an uplink grant is configured for the configured grant type 2, UE 102 may sequentially consider that the Nth uplink grant occurs in association with a symbol for which:

[0114] [(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot)+(number of slots in a frame*numberOfSymbolsPerSlot)+number of symbols in a slot]=[(SFN 开始时间 *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+slot 开始 time*numberOfSymbolsPerSlot+symbol 开始时间 )+N*periodicity] modulo 1024. (2)

[0116] Here, SFN 开始时间 , time slot 开始时间 and symbol 开始时间 The SFN (i.e., system frame number), time slot, and symbol, respectively, when (re)initializing the configured uplink grant. Additionally, parameters (e.g., periodicity) may be configured by gNB 160, for example, using RRC messaging.

[0117] That is, for a configured grant type 1 transmission, UE 102 may initiate an uplink transmission based on receipt of the parameters included in the RRC message. Additionally, for a configured grant type 2 transmission, UE 102 may initiate an uplink transmission based on receipt of a DCI format for uplink with a CRC scrambled by the C-RNTI. Additionally, UE 102 may perform a retransmission of a TB (e.g., a retransmission on the UL-SCH, a retransmission on the PUSCH 503) based on receipt of a DCI format for uplink with a CRC scrambled by the C-RNTI, wherein the NDI included in the DCI format for uplink is set to "1."

[0118] For example, gNB 160 may transmit parameters for the configured Grant Type 1 transmission using an RRC message (e.g., a dedicated RRC message, a UE-specific RRC message). UE 102 may perform the configured Grant Type 1 transmission based on the parameters included in the RRC message. Additionally, gNB 160 may transmit parameters for the configured Grant Type 2 transmission using an RRC message (e.g., a dedicated RRC message, a UE-specific RRC message). UE 102 may perform the configured Grant Type 2 transmission based on the parameters included in the RRC message.

[0119] Here, for transmissions corresponding to the configured grants (i.e., configured grant type 1 transmissions and / or configured grant type 2 transmissions), the following parameters may be configured. For example, the following parameters may be included in the ConfiguredGrantConfig in the ConfiguredGrantConfig information element (IE). That is, the RRC message may include the ConfiguredGrantConfig IE.

[0120] -frequencyhopping: The value "intraSlot" enables "intra-slot frequency hopping", and the value "interSlot" enables "inter-slot frequency hopping"

[0121] -mcs-Table: Indicates the MCS table that the UE 102 should use for PUSCH (e.g., PUSCH transmission) (e.g., without transform precoding)

[0122] -mcs-TableTransformPrecoder: Indicates the MCS table that the UE 102 should use for PUSCH (e.g., PUSCH transmission) (e.g., with transform precoding)

[0123] -powerControlLoopToUse: The closed control loop to be applied. Parameters used to determine the transmit power for PUSCH transmissions (e.g., transmissions corresponding to configured grants)

[0124] -p0-PUSCH-Alpha: Index to the PO-PUSCH-AlphaSet used for this configuration. Parameter used to determine the transmit power of PUSCH transmissions (e.g., transmissions corresponding to the configured grants)

[0125] -transformPrecoder: Enables or disables transform precoding for transmissions corresponding to configured grants (i.e., configured grant type 1 transmissions and / or configured grant type 2 transmissions)

[0126] -nrofHARQ-Processes: Number of HARQ processes configured for configured grant type 1 transmission and / or configured grant type 2 transmission

[0127] -repK : Number of repetitions to apply to configured Grant Type 1 transfers and / or configured Grant Type 2 transfers

[0128] -repK-RV: Redundancy version sequence to be applied to configured grant type 1 transmissions and / or configured grant type 2 transmissions

[0129] Additionally or alternatively, for configured Grant Type 1 transmission, the following parameters may be configured: For example, flow parameters may be included in the rrc-ConfiguredUplinkGrant in the ConfiguredGrantConfig IE.

[0130] - timeDomainOffset: an offset value associated with the system frame number (SFN) = 0. That is, an offset value used to indicate the timing of the configured grant type 1 transmission.

[0131] -timeDomainAllocation: indicates the combination of the start symbol and length and the PUSCH mapping type

[0132] -frequencyDomainAllocation: indicates frequency domain resource allocation

[0133] -antennaport: Indicates the antenna port to be used for this configuration

[0134] -mcsAndTBS: indicates modulation order, target code rate and / or TB size

[0135] -frequencyHoppingOffset: The frequency hopping offset used when frequency hopping is enabled

[0136] -pathlossReferenceIndex: Parameters for power control of configured grant type 1 transmissions (i.e., for this configuration)

[0137] Here, multiple configurations of ConfiguredGrantConfig can be supported. That is, one or more configurations in ConfiguredGrantConfig can be configured. Furthermore, multiple configurations of rrc-ConfiguredUplinkGrant can be supported. That is, one or more configurations in rrc-ConfiguredUplinkGrant can be configured. Here, the configurations of ConfiguredGrantConfig and / or rrc-ConfiguredUplinkGrant may be referred to as configurations of configured grants. That is, a single configuration of configured grants can be supported. Furthermore, multiple configurations of configured grants can be supported.

[0138] For example, the gNB 160 may transmit, using an RRC message, third information indicating that the plurality of configurations of the configured grant are enabled (e.g., allowed). That is, the gNB 160 may transmit, using an RRC message, third information indicating whether the single configuration of the configured grant or the plurality of configurations of the configured grant is used for transmission corresponding to the configured grant.

[0139] That is, if the single configuration of the configured authorization is configured, the single configuration of the configured authorization can be used for transmission corresponding to the configured authorization. Alternatively, if the multiple configurations of the configured authorization are configured, the multiple configurations of the configured authorization can be used for transmission corresponding to the configured authorization. Alternatively, if the multiple configurations of the configured authorization are not configured, the single configuration of the configured authorization can be used for transmission corresponding to the configured authorization.

[0140] Here, the third information may be configured per serving cell. For example, the third information may be configured for each serving cell (e.g., a primary cell and / or one or more secondary cells). Additionally or alternatively, the third information may be configured per UL bandwidth part (UL BWP). For example, the third information may be configured for each UL BWP (each UL BWP in the serving cell). Additionally or alternatively, the third information may be configured for configured Grant Type 1 transmission and / or configured Grant Type 2 transmission. For example, the third information may be generally configured for configured Grant Type 1 transmission and configured Grant Type 2 transmission. Additionally or alternatively, the third information may be configured separately for configured Grant Type 1 transmission and configured Grant Type 2 transmission.

[0141] For example, as described below, when the third information is commonly configured for configured grant type 1 transmission and configured grant type 2 transmission, the configured index may be configured for ConfiguredGrantConfig. Additionally or alternatively, when the third information is separately configured for configured grant type 1 transmission and configured grant type 2 transmission, the index of the configured index may be configured for ConfiguredGrantConfig and / or the configured index may be configured for rrc-ConfiguredUplinkGrant.

[0142] Additionally or alternatively, a single configuration of the configured grant may be activated. That is, a single active configuration of the configured grant may be supported. Additionally or alternatively, multiple configurations of the configured grant may be activated. That is, multiple active configurations of the configured grant may be supported. For example, multiple active configurations of the configured grant for a given BWP (e.g., UL BWP) of a serving cell may be supported at least for different service / traffic types and / or to enhance reliability and reduce latency.

[0143] That is, the single configuration of the configured grant may be configured (and / or activated) for a given BWP (e.g., UL BWP) of a single serving cell. Additionally or alternatively, the multiple configurations of the configured grant may be configured (and / or activated) for a given BWP (e.g., UL BWP) of a single serving cell.

[0144] The UE 102 may perform configured grant type 1 transmission based on the single configuration of configured grants (if the single configuration of configured grants is used) and / or the multiple configurations of configured grants (if the multiple configurations of configured grants are used).

[0145] Additionally or alternatively, the following parameters may be configured for transmissions on PUSCH 503. For example, flow parameters may be included in the PUSCH-Config IE (e.g., included in the BWP-UplinkDedicated IE). The PUSCH-Config IE may be used to configure UE-specific parameters applicable to a specific BWP (e.g., a UL BWP). Furthermore, the BWP-Uplink Dedicated IE may be used to configure dedicated parameters for the UL BWP (i.e., UE-specific parameters). That is, the gNB 160 may transmit parameters for transmissions on PUSCH 503 using an RRC message (e.g., a dedicated RRC message, a UE-specific RRC message). For example, the following parameters may be used for transmissions on PUSCH 503 scheduled using a DCI format with a CRC scrambled by the C-RNTI.

[0146] -dataScramblingIdentityPUSCH: Identifier used to initiate data scrambling of PUSCH (e.g., PUSCH transmission)

[0147] -txConfig: Indicates whether the UE uses codebook-based transmission or non-codebook-based transmission

[0148] -PUSCH-PowerControl: Parameter used to determine the transmission power of PUSCH transmission

[0149] -frequencyHopping: The value "intraSlot" enables "intra-slot frequency hopping", and the value "interSlot" enables "inter-slot frequency hopping"

[0150] -pusch-TimeDomainAllocationList: List of time-domain resource allocations for DCI formats used for uplink and UL transmissions

[0151] -pusch-AggregationFactor: Number of repetitions of UL transmission (e.g., PUSCH transmission)

[0152] -mcs-Table: Indicates which MCS table the UE should use for PUSCH transmission (e.g. no transform precoding)

[0153] -mcs-TableTransformPrecoder: Indicates which MCS table the UE should use for PUSCH transmission (e.g. with transform precoding)

[0154] -transformPrecoder: UE-specific selection of transformer precoder for PUSCH transmission

[0155] - Scaling of UCI-OnPUSCH: Indicates the scaling factor to limit the number of resource elements allocated to UCI transmitted on PUSCH

[0156] Here, the parameter PUSCH-PowerControl may include the following parameters.

[0157] -PUSCH-PowerControl: If enabled, the UE 102 applies the transmit power (TPC) command via accumulation. If not enabled, the UE 102 applies the TPC command without accumulation. The parameter indicates the configuration of the TPC command (e.g., whether the TPC command is accumulated or not (i.e., the absolute value is used as the TPC command)).

[0158] -p0-NominalWithoutGrant: Parameter used to determine the transmit power for transmissions corresponding to the configured grant

[0159] -p0-Alpha: Parameter used to determine the transmit power of PUSCH transmission

[0160] Here, multiple configurations of PUSCH-Config can be supported. That is, one or more configurations in PUSCH-Config can be configured. Here, the configuration of PUSCH-Config can be referred to as the configuration of PUSCH 503. That is, a single configuration of PUSCH 503 can be supported. In addition, multiple configurations of PUSCH 503 can be supported.

[0161] For example, if the multiple configurations of the configured grant are configured, the multiple configurations of PUSCH 503 may be configured. That is, if the gNB 160 configures the multiple configurations of the configured grant, the gNB 160 may always configure the multiple configurations of PUSCH 503. For example, if the single configuration of the configured grant is configured, the single configuration of PUSCH 503 may be configured. That is, if the gNB 160 configures the single configuration of the configured grant, the gNB 160 may always configure the single configuration of PUSCH 503.

[0162] Here, when multiple configurations of the configured grant are configured, the configured index may be configured. For example, the configured index may be included in ConfiguredGrantConfig (e.g., or ConfiguredGrantConfig IE). Additionally or alternatively, the configured index may be included in rrc-ConfiguredUplinkGrant (e.g., in ConfiguredGrantConfig IE). Additionally or alternatively, the configured index may be included in PUSCH-config.

[0163] Here, the configured index may be an index of the configuration of ConfiguredGrantConfig. Additionally or alternatively, the configured index may be an index of the configuration of rrc-ConfiguredUplinkGrant. Additionally or alternatively, the configured index may be an index of the configuration of PUSCH-Config.

[0164] That is, each of the multiple configurations of the configured grant can be identified by using a configured index (e.g., an index of the configured grant configuration). In addition, each of the multiple configurations of the PUSCH 503 can be identified by using a configured index (e.g., an index of the PUSCH configuration). In addition, a link between each of the multiple configurations of the configured grant and each of the multiple configurations of the PUSCH 503 (e.g., a correspondence between each of the multiple configurations of the configured grant and each of the multiple configurations of the PUSCH 503) can be identified by using a configured index.

[0165] For example, in a case where the multiple configurations of the configured authorization (e.g., four configurations of the configured authorization) are configured for the configured authorization transmission, index "0" (e.g., value "0"), index "1" (e.g., value "1"), index "2" (e.g., value "2") and / or index "3" (e.g., value "3") may be configured as the index of the configuration for each of the multiple configurations of the configured authorization.

[0166] For example, index "0" may be configured for the first configuration of the plurality of configurations of the configuration authorization (e.g., as configuration index #0). Additionally, index "1" may be configured for the second configuration of the plurality of configurations of the configuration authorization (e.g., as configuration index #1). Additionally, index "2" may be configured for the third configuration of the plurality of configurations of the configuration authorization (e.g., as configuration index #2). Additionally, index "1" may be configured for the fourth configuration of the plurality of configurations of the configuration authorization (e.g., as configuration index #3).

[0167] For example, in the case where the multiple configurations of the PUSCH (e.g., four configurations of the PUSCH) are configured, index "0", index "1", index "2", and / or index "3" may be configured as the index of the configuration of each configuration in the multiple configurations of the PUSCH 503. That is, in the case where the multiple configurations of the PUSCH 503 (e.g., four configurations of the PUSCH 503) are configured, index "0", index "1", index "2", and / or index "3" may be configured as the index of the configuration of each configuration in the multiple configurations of the PUSCH 503.

[0168] For example, index "0" may be configured for the first configuration among the multiple configurations of the PUSCH (e.g., as configuration index #0). Additionally, index "1" may be configured for the second configuration among the multiple configurations of the PUSCH (e.g., as configuration index #1). Additionally, index "2" may be configured for the third configuration among the multiple configurations of the PUSCH (e.g., as configuration index #2). Additionally, index "1" may be configured for the fourth configuration among the multiple configurations of the PUSCH (e.g., as configuration index #3).

[0169] Furthermore, if the configured index of the configured grant is the same as the configured index of the PUSCH 503, the configured grant configuration may be linked to the configuration of the PUSCH 503. That is, if the configured index of the configured grant is the same as the configured index of the PUSCH 503, the configured grant configuration and the PUSCH 503 configuration may be linked.

[0170] Here, one of the multiple configurations of the configured grant (e.g., a configuration of the configured grant having an index "X (X=0, 1, 2, or 3)" (e.g., an index corresponding to one of the multiple configurations of the configured grant)) may be predefined by a specification and may be known information between the gNB 160 and the UE 102. Additionally or alternatively, the one of the multiple configurations of the configured grant may be configured by the gNB 160. For example, the gNB 160 may transmit information for configuring the one of the multiple configurations of the configured grant (e.g., an index corresponding to the one or more configurations of the configured grant) using an RRC message. The UE 102 may identify the one of the multiple configurations of the configured grant (e.g., an index corresponding to one of the multiple configurations of the configured grant based on the information). Here, the one of the multiple configurations of the configured grant may be referred to as the configuration having an index "X." That is, the index corresponding to the one of the multiple configurations of the configured grant may be referred to as the index "X."

[0171] As described above, the configuration with index "X" may be the configuration with index "0." Additionally or alternatively, the configuration with index "X" may be the configuration with index "1." Additionally or alternatively, the configuration with index "X" may be the configuration with index "2." Additionally or alternatively, the configuration with index "X" may be the configuration with index "3." That is, the configuration with index "X" may be the configuration with index "predetermined value."

[0172] Additionally or alternatively, the index of the configuration of the authorization of the configuration may not be configured for (e.g., applied to) the configuration with index "X". For example, the index of the configuration of the authorization of the configuration may be configured only for (e.g., applied only to) the configuration of the authorization of the configuration other than the configuration with index "X".

[0173] Additionally or alternatively, in the case of using the single configuration of the configured grant, the single configuration of the configured grant may correspond to the configuration with index "X". Additionally or alternatively, in the case of using the single configuration of the configured grant, the single configuration of the PUSCH 503 may be linked with the configuration with index "X". Additionally or alternatively, in the case of using the single configuration of the PUSCH 503, the single configuration of the PUSCH 503 may be linked with the configuration with index "X".

[0174] Here, the configuration of the grant of configurations other than the configuration with index 'X' may include a portion of the parameters included in the PUSCH-config. Also, the configuration with index 'X' may not include a portion of the parameters included in the PUSCH-config.

[0175] That is, the authorized configurations of the configurations other than the configuration with index 'X' may include scaling of dataScramblingIdentityPUSCH, txConfig, PUSCH-PowerControl, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, mcs-TableTransformPrecoder and / or UCI-OnPUSCH.

[0176] For example, the configurations granted for configurations other than the configuration with index "X" may include scaling of dataScramblingIdentityPUSCH, txConfig, and / or UCI-OnPUSCH. Also, the configurations granted for configurations other than the configuration with index "X" may not include PUSCH-PowerControl, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, and / or mcs-TableTransformPrecoder.

[0177] That is, in the case where the multiple configurations of the configured grant are configured, part of the parameters (for example, the parameters described as included in the PUSCH-config) may be configured in the ConfiguredGrantConfig IE (for example, ConfiguredGrantConfig and / or rrc-ConfiguredUplinkGrant).

[0178] Additionally or alternatively, the configuration of the PUSCH 503 linked to the configuration of the grant other than the configuration with index "X" may include a portion of the parameters (e.g., a portion of the parameters included in the PUSCH-config). Also, the configuration of the PUSCH 503 linked to the configuration with index "X" may include parameters (e.g., all parameters included in the above-mentioned PUSCH-config).

[0179] That is, the configuration of PUSCH 503 linked with the configuration of the grant of a configuration other than the configuration with index "X" may not include scaling of dataScramblingIdentityPUSCH, txConfig, PUSCH-PowerControl, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, mcs-TableTransformPrecoder and / or UCI-OnPUSCH.

[0180] For example, the configuration of the PUSCH 503 linked with the configuration of the grant of a configuration other than the configuration with index "X" may include scaling of dataScramblingIdentityPUSCH, txConfig, tpc-Accumulation, and / or UCI-OnPUSCH. Also, the configuration of the PUSCH 503 linked with the configuration of the grant of a configuration other than the configuration with index "X" may not include p0-NominalWithoutGrant, p0-Alpha, frequencyHopping, pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table, and / or mcs-TableTransformPrecoder.

[0181] That is, only a portion of the parameters (e.g., the parameters included in the PUSCH-config) may be configured as the multiple configurations (e.g., the multiple configurations of the PUSCH 503). That is, based on the multiple configurations of the configured grant, a portion of the parameters (e.g., the portion of the parameters included in the PUSCH-config) may be configured as the multiple configurations.

[0182] Here, in a case where the single configuration of the configured grant is configured (ie, in a case where the multiple configurations of the configured grant are not configured), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration of the configured grant.

[0183] For example, for a configured grant type 1 transmission, in a case where the configuration of the configured grant with index “1” is configured, the UE 102 may perform transmission corresponding to the configured grant based on the configuration of the configured grant with index “1” (i.e., the parameters included in the configuration of the configured grant with index “1”). Additionally or alternatively, as described above, for a configured grant type 1 transmission, in a case where the single configuration of the configured grant is configured, the UE 102 may perform transmission corresponding to the configured grant based on the configuration with index “X”. That is, in a case where the single configuration of the configured grant is configured, the configuration with index “X” may always be applied to transmission corresponding to the configured grant.

[0184] Additionally or alternatively, for a configured grant type 2 transmission, when a single configuration of the configured grant is configured, the UE 102 may identify the configured index of the configured grant (i.e., the index of the configured grant to be applied for transmission) based on information included in a DCI format (e.g., a DCI format for indicating activation of the configured grant) having a CRC scrambled by the CS-RNTI. That is, the DCI format may include information indicating the index of the configured grant configuration.

[0185] For example, for a configured grant type 2 transmission, if the single configuration of the configured grant is configured and the configuration of the configured grant with index "1" is indicated by using a DCI format with a CRC scrambled by the CS-RNTI, the UE 102 may perform transmission corresponding to the configured grant based on the configuration of the configured grant with index "1" (i.e., parameters included in the configuration of the configured grant with index "1"). That is, the configuration of the configured grant with index "1" may be activated by using a DCI format with a CRC scrambled by the CS-RNTI. Additionally or alternatively, as described above, for a configured grant type 2 transmission, if the single configuration of the configured grant is configured, the UE 102 may perform transmission corresponding to the configured grant based on the configuration with index "X". That is, if the single configuration of the configured grant is configured, the configuration with index "X" may always be applied to transmission corresponding to the configured grant.

[0186] Additionally or alternatively, for retransmissions scheduled using a DCI format with an NDI set to "1" for a CRC scrambled by the CS-RNTI, the UE 102 may identify the index of the configuration of the PUSCH 503 (i.e., the index of the configuration of the PUSCH 503 to be applied for transmission) based on information included in the DCI format with an NDI set to "1" for a CRC scrambled by the CS-RNTI. That is, the DCI format for the uplink may include information indicating the index of the configuration of the PUSCH 503.

[0187] For example, if the single configuration of the configured grant is configured and the configuration of the PUSCH 503 with index "1" is indicated by using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI, the UE 102 may perform retransmission based on the configuration of the PUSCH 503 with index "1" (i.e., the parameters included in the configuration of the PUSCH 503 with index "1"). That is, the configuration of the PUSCH 503 with index "1" may be activated by using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI. Additionally or alternatively, as described above, if the single configuration of the configured grant is configured, the UE 102 may perform retransmission based on the configuration of the PUSCH 503 linked with the configuration with index "X". That is, if the single configuration of the configured grant is configured, the configuration of the PUSCH 503 linked with the configuration with index "X" may always be applied to retransmission.

[0188] Additionally or alternatively, information indicating the index of the configured grant configurations may be included in the DCI format only when multiple configurations of the configured grant are configured. That is, when a single configuration of the configured grant is configured, information indicating the index of the configured grant configurations may not be included in the DCI format used for the uplink grant. Here, as described below, information indicating the index of the configured grant configurations may be included only in DCI format 0_1.

[0189] Additionally or alternatively, information indicating an index of the configuration of the PUSCH 503 may be included in the DCI format only when the multiple configurations of the configured grant are configured. That is, when the single configuration of the configured grant is configured, information indicating an index of the configuration of the PUSCH 503 may not be included in the DCI format. Here, as described below, information indicating an index of the configuration of the PUSCH 503 may be included only in DCI format 0_1.

[0190] Additionally or alternatively, in a case where the multiple configurations of the configured grant are configured, the UE 102 may perform transmission corresponding to the configured grant based on the multiple configurations of the configured grant.

[0191] For example, for a configured authorization type 1 transmission, in a case where a configuration with an index “1” and a configuration with an index “3” are configured, the UE 102 may perform transmission corresponding to the configured authorization based on the configuration of the authorization with an index “1” and the configuration of the authorization with an index “3” (i.e., parameters included in the configuration of the authorization with an index “1” and parameters included in the configuration of the authorization with an index “3”).

[0192] Additionally or alternatively, for a configured grant type 2 transmission, where the multiple configurations of the configured grant are configured, the UE 102 may identify an index of a configuration of the configured grant (i.e., an index of a configuration of the configured grant to be applied for the transmission) based on information included in a DCI format (e.g., a DCI format for indicating activation of the configured grant) having a CRC scrambled by the CS-RNTI.

[0193] For example, for a configured grant type 2 transmission, if multiple configurations of the configured grants are configured and the configuration of the configured grant with index "1" is indicated by using a DCI format with a CRC scrambled by the CS-RNTI, the UE 102 may perform transmission corresponding to the configured grant based on the configuration with index "1" (i.e., the parameters included in the configuration of the configured grant with index "1"). That is, the configuration of the configured grant with index "1" may be activated by using a DCI format with a CRC scrambled by the CS-RNTI. Additionally, if multiple configurations of the configured grants are configured and the configuration of the configured grant with index "3" is indicated by using a DCI format with a CRC scrambled by the CS-RNTI, the UE 102 may perform transmission corresponding to the configured grant based on the configuration with index "3" (i.e., the parameters included in the configuration of the configured grant with index "3"). That is, the configuration of the configured grant with index "3" may be activated by using a DCI format with a CRC scrambled by the CS-RNTI.

[0194] Here, the multiple configurations of the configured grants can be activated simultaneously (e.g., at the same time) by using the single DCI format with the CRC scrambled by the CS-RNTI. That is, the single DCI format may include information indicating one or more indexes of the configurations of the configured grants to be applied to the transmission corresponding to the configured grants. For example, if the multiple configurations are configured and the configuration of the configured grant with index "1" and the configuration of the configured grant with index "3" are indicated, the UE 102 may perform the transmission corresponding to the configured grant based on the configuration of the configured grant with index "1" and the configuration of the configured grant with index "3".

[0195] Additionally or alternatively, for retransmissions scheduled using a DCI format with an NDI set to "1" for a CRC scrambled by the CS-RNTI, if multiple configurations of the configured grant are configured, the UE 102 may identify the index of the configuration of the PUSCH 503 (i.e., the index of the configuration of the PUSCH 503 to be applied for transmission) based on information included in the DCI format with an NDI set to "1" for a CRC scrambled by the CS-RNTI. That is, the DCI format for the uplink may include information indicating the index of the configuration of the PUSCH 503.

[0196] For example, when the multiple configurations of the configured grant are configured and the configuration of the PUSCH 503 with an index of "1" is indicated by using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI, the UE 102 may perform retransmission based on the configuration of the PUSCH 503 with an index of "1" (i.e., the parameters included in the configuration of the PUSCH 503 with an index of "1"). That is, the configuration of the PUSCH 503 with an index of "1" may be activated by using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI. In addition, when the multiple configurations of the configured grant are configured and the configuration of the PUSCH 503 with an index of "3" is indicated by using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI, the UE 102 may perform retransmission based on the configuration of the PUSCH 503 with an index of "3" (i.e., the parameters included in the configuration of the PUSCH 503 with an index of "3"). That is, the configuration of the PUSCH 503 with an index of "3" may be activated by using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI.

[0197] Here, the multiple configurations of PUSCH 503 can be activated simultaneously (e.g., at the same time) by using the single DCI format with the NDI set to "1" in the CRC scrambled by the CS-RNTI. That is, the single DCI format may include information indicating one or more indexes of the configurations of PUSCH 503 to be applied to retransmission. For example, if the multiple configurations are configured and the configuration of PUSCH 503 with index "1" and the configuration of PUSCH 503 with index "3" are indicated, UE 102 may perform retransmission based on the configuration of PUSCH 503 with index "1" and the configuration of PUSCH 503 with index "3".

[0198] Additionally or alternatively, for transmissions corresponding to a configured grant (i.e., configured grant type 1 and / or configured grant type 2), the UE 102 may apply the parameters provided by ConfiguredGrantConfig to anticipate the scaling of dataScramblingIdentityPUSCH, txConfig, and / or UCI-OnPUSCH provided by PUSCH-config. That is, for transmissions corresponding to a configured grant, the UE 102 may apply a portion of the parameters included in ConfiguredGrantConfig. Additionally, for transmissions corresponding to a configured grant, the UE 102 may apply a portion of the parameters included in PUSCH-config (e.g., scaling of dataScramblingIdentityPUSCH, txConfig, and / or UCI-OnPUSCH).

[0199] Additionally or alternatively, for retransmissions scheduled using a DCI format with NDI set to "1" with a CRC scrambled by the CS-RNTI, the UE 102 may apply the parameters of the provided PUSCH-config to expect p0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPreder and / or transformPrecoder.

[0200] For example, for retransmissions scheduled using a DCI format with a CRC scrambled by the CS-RNTI and NDI set to "1," the UE 102 may apply the parameters provided in the PUSCH-config to expect p0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder, and / or transformPrecoder. Furthermore, instead of the p0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder, and / or transformPrecoder included in the PUSCH-config, the p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder, and / or transformPrecoder included in the ConfiguredGrantConfig may be used for the retransmissions. That is, for retransmissions scheduled using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI, the UE 102 may apply a portion of the parameters included in ConfiguredGrantConfig (e.g., p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder, and / or transformPrecoder). Additionally, for retransmissions scheduled using a DCI format with an NDI set to "1" and a CRC scrambled by the CS-RNTI, the UE 102 may apply a portion of the parameters included in PUSCH-config.

[0201] Here, in case the UE 102 applies a portion of the parameters included in ConfiguredGrantConfig and a portion of the parameters included in PUSCH-config, the configuration of the linked configured grant and the configuration of the PUSCH 503 may be used for (re)transmission.

[0202] That is, for (re)transmission, when the configuration of the grant with the configuration index “0” is applied (i.e., when a portion of the configured parameters of the grant with the configuration index “0” is applied), the configuration of the PUSCH 503 with the index “0” (i.e., a portion of the configured parameters of the PUSCH 503 with the index “0”) may be applied. Furthermore, for (re)transmission, when the configuration of the grant with the configuration index “1” is applied (i.e., when a portion of the configured parameters of the grant with the configuration index “1” is applied), the configuration of the PUSCH 503 with the index “1” (i.e., a portion of the configured parameters of the PUSCH 503 with the index “1”) may be applied. In addition, for (re)transmission, when the configuration of the grant with the configuration index "2" is applied (i.e., when a portion of the configured parameters of the grant with the configuration index "2" is applied), the configuration of the PUSCH 503 with the index "2" (i.e., a portion of the configured parameters of the PUSCH 503 with the index "2") may be applied. In addition, for (re)transmission, when the configuration of the grant with the configuration index "3" is applied (i.e., when a portion of the configured parameters of the grant with the configuration index "3" is applied), the configuration of the PUSCH 503 with the index "3" (i.e., a portion of the configured parameters of the PUSCH 503 with the index "3") may be applied.

[0203] In addition, for (re)transmission, in case of applying the configuration of the authorization of the configuration with index "X" (i.e., in case of applying a part of the parameters of the configuration of the authorization of the configuration with index "X"), the configuration of PUSCH 503 linked with the authorization of the configuration with index "X" (i.e., a part of the parameters of the configuration of PUSCH 503 linked with the configuration with index "X") may be applied.

[0204] Additionally or alternatively, for (re)transmission, when the configuration of the PUSCH 503 with an index of "0" is applied (i.e., when a portion of the parameters of the configuration of the PUSCH 503 with an index of "0" is applied), the configuration of the grant with an index of "0" may be applied (i.e., a portion of the parameters of the grant with an index of "0"). Furthermore, for (re)transmission, when the configuration of the PUSCH 503 with an index of "1" is applied (i.e., when a portion of the parameters of the configuration of the PUSCH 503 with an index of "1" is applied), the configuration of the grant with an index of "1" may be applied (i.e., a portion of the parameters of the grant with an index of "1"). In addition, for (re)transmission, when the configuration of the PUSCH 503 with the index "2" is applied (i.e., when a portion of the parameters of the configuration of the PUSCH 503 with the index "2" is applied), the configuration of the grant with the configuration index "2" (i.e., a portion of the parameters of the grant with the configuration index "2") may be applied. In addition, for (re)transmission, when the configuration of the PUSCH 503 with the index "3" is applied (i.e., when a portion of the parameters of the configuration of the PUSCH 503 with the index "3" is applied), the configuration of the grant with the configuration index "3" (i.e., a portion of the parameters of the grant with the configuration index "3") may be applied.

[0205] In addition, for (re)transmission, in the case of applying the configuration of PUSCH 503 linked with the configuration with index “X” (i.e., in the case of applying a part of the parameters of the configuration of PUSCH 503 linked with the configuration with index “X”), the configuration with index “X” (i.e., a part of the parameters of the configuration with index “X”) may be applied.

[0206] Additionally or alternatively, for simplicity of description, in some implementations, it may be assumed that the single configuration of the grant of the configurations described herein and / or the single configuration of the PUSCH 503 are included in a single configuration “A.” Furthermore, for simplicity of description, in some implementations, it may be assumed that the multiple configurations of the grant of the configurations described herein and / or the multiple configurations of the PUSCH 503 are included in multiple configurations “B.”

[0207] As described above, information indicating the configured index of the configured grant may be included only in DCI format 0_1 (i.e., DCI format 0_1 with CRC scrambled by CS-RNTI). That is, DCI format 0_0 may not include information indicating the configured index of the configured grant.

[0208] For example, in the case where the multiple configurations of the configured grant are configured, based on detecting (e.g., detecting, decoding) DCI format 0_1 with a CRC scrambled by CS-RNTI (e.g., NDI is set to "0"), UE 102 may perform transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).

[0209] Additionally or alternatively, in the case of the multiple configurations of the configured authorization, based on detecting DCI format 0_1 with a CRC scrambled by the CS-RNTI (e.g., NDI set to "1"), UE 102 may perform a retransmission (e.g., retransmission of a TB) based on the multiple configurations "B" (e.g., as described above).

[0210] Additionally or alternatively, upon detecting DCI format 0_0 with a CRC scrambled by the CS-RNTI (e.g., with NDI set to "0"), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A" (e.g., as described above). That is, even if multiple configurations of the configured grant are configured, upon detecting DCI format 0_0 with a CRC scrambled by the CS-RNTI (e.g., with NDI set to "0"), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A."

[0211] For example, in the event that a DCI format 0_0 with a CRC scrambled by a CS-RNTI is detected (e.g., NDI is set to “0”), the UE 102 may perform a transmission corresponding to the configured grant based on the configuration with index “X” and / or the configuration of the PUSCH 503 linked with the configuration with index “X”.

[0212] Additionally or alternatively, upon detecting DCI format 0_0 with a CRC scrambled by the CS-RNTI (e.g., NDI set to "1"), the UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). That is, even if multiple configurations of the configured grant are configured, upon detecting DCI format 0_0 with a CRC scrambled by the CS-RNTI (e.g., NDI set to "1"), the UE 102 may perform retransmission based on the single configuration "A."

[0213] For example, in the event of detecting DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to “1”), UE 102 may perform retransmission based on the configuration with index “X” and / or the configuration of PUSCH 503 linked with the configuration with index “X”.

[0214] Additionally or alternatively, when a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in the CSS (i.e., CSS set), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A" (e.g., as described above). That is, even if multiple configurations of the configured grant are configured, when a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in the CSS, the UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A." That is, in the event that a DCI format (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by CS-RNTI is detected in the USS (i.e., USS set), the UE 102 may perform transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).

[0215] For example, in the event that a DCI format (e.g., NDI is set to "0") having a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set) (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform a transmission corresponding to the configured grant based on the configuration with index "X" and / or the configuration of the PUSCH 503 linked with the configuration with index "X".

[0216] Additionally or alternatively, if a DCI format (e.g., NDI set to "0") with a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set) (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). That is, even if multiple configurations of the configured grant are configured, if a DCI format (e.g., NDI set to "0") with a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set) (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission based on the single configuration "A."

[0217] For example, in the event that a DCI format (e.g., NDI set to "0") having a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set) (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform retransmission based on a configuration having an index "X" and / or a configuration of the PUSCH 503 linked to the configuration having an index "X".

[0218] Additionally or alternatively, in a case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A” (e.g., as described above). That is, even if the multiple configurations of the configured grant are configured, in a case where a DCI format having a CRC scrambled by a CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, UE 102 may perform transmission corresponding to the configured grant based on the single configuration “A”. That is, in the event that a DCI format having a CRC scrambled by CS-RNTI (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a CORESET other than CORESET#0, UE 102 may perform transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).

[0219] For example, in the event that a DCI format with a CRC scrambled by the CS-RNTI (e.g., NDI is set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET#0, the UE 102 may perform transmission corresponding to the configured grant based on the configuration with index “X” and / or the configuration of the PUSCH 503 linked with the configuration with index “X”.

[0220] Additionally or alternatively, in the case where a DCI format (e.g., NDI is set to "0") with a CRC scrambled by a CS-RNTI is detected in CORESET #0 (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). That is, even if the multiple configurations of the configured grant are configured, in the case where a DCI format (e.g., NDI is set to "0") with a CRC scrambled by a CS-RNTI is detected in CORESET #0 (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform retransmission based on the single configuration "A".

[0221] For example, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET#0, the UE 102 may perform retransmission based on the configuration with index “X” and / or the configuration of the PUSCH 503 linked with the configuration with index “X”.

[0222] Additionally or alternatively, in a case where a DCI format (e.g., NDI set to "0") having a CRC scrambled by a CS-RNTI is detected in a search space set with an index of "0" (i.e., search space set #0) (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A" (e.g., as described above). That is, even if multiple configurations of the configured grant are configured, in a case where a DCI format (e.g., NDI set to "0") having a CRC scrambled by a CS-RNTI is detected in search space set #0 (e.g., DCI formats of DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform transmission corresponding to the configured grant based on the single configuration "A." That is, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a search space other than search space set #0, UE 102 may perform transmission corresponding to the configured authorization based on the multiple configurations "B" (e.g., as described above).

[0223] For example, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in search space set #0, UE 102 may perform a transmission corresponding to the configured grant based on the configuration with index “X” and / or the configuration of PUSCH 503 linked with the configuration with index “X”.

[0224] Additionally or alternatively, if a DCI format (e.g., NDI set to "0") with a CRC scrambled by a CS-RNTI is detected in search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission (e.g., retransmission of a TB) based on the single configuration "A" (e.g., as described above). That is, even if multiple configurations of the configured grant are configured, if a DCI format (e.g., NDI set to "0") with a CRC scrambled by a CS-RNTI is detected in search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission based on the single configuration "A."

[0225] For example, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI set to “0”) is detected in search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), the UE 102 may perform retransmission based on the configuration with index “X” and / or the configuration of the PUSCH 503 linked with the configuration with index “X”.

[0226] Additionally, grouping of configured grant configurations may be supported. For example, gNB 160 may transmit information regarding the correspondence between a configured grant configuration group (e.g., a configured grant configuration group with an index "") and a configured grant configuration (e.g., a configured grant configuration with an index "") using an RRC message. For example, a configured grant configuration with an index of "0" may correspond to a configured grant configuration group with an index of "0." Furthermore, a configured grant configuration with an index of "1" may correspond to a configured grant configuration group with an index of "1." Furthermore, a configured grant configuration with an index of "2" may correspond to a configured grant configuration group with an index of "0." That is, the configured grant configuration with an index of "0" and the configured grant configuration with an index of "2" may belong to the same group (i.e., configured grant configuration group "0"). Furthermore, a configured grant configuration with an index of "4" may correspond to a configured grant configuration group with an index of "1." That is, the authorized configuration of the configuration with index "1" and the authorized configuration of the configuration with index "4" may belong to the same group (ie, the authorized configuration group "1" of configurations).

[0227] In addition, grouping of PUSCH configurations may be supported. For example, gNB 160 may transmit information configuring the correspondence between a PUSCH configuration group (e.g., a PUSCH configuration group with an index) and a PUSCH configuration (e.g., a PUSCH configuration with an index) using an RRC message. For example, a PUSCH configuration with an index of "0" may correspond to a PUSCH configuration group with an index of "1." Furthermore, a PUSCH configuration with an index of "1" may correspond to a PUSCH configuration group with an index of "0." Furthermore, a PUSCH configuration with an index of "2" may correspond to a PUSCH configuration group with an index of "0." That is, a PUSCH configuration with an index of "1" and a PUSCH configuration with an index of "2" may belong to the same group (i.e., PUSCH configuration group "0"). Furthermore, a PUSCH configuration with an index of "3" may correspond to a PUSCH configuration group with an index of "1." That is, the configuration of a PUSCH with an index of '0' and the configuration of a PUSCH with an index of '3' may belong to the same group (ie, PUSCH configuration group '1').

[0228] That is, in the systems and methods disclosed herein, a configured authorized configuration (e.g., an authorized configuration with an index) can be replaced by a configured authorized configuration group (e.g., a group of authorized configurations with an index). Here, a configured authorized configuration group can include one or more configured authorized configurations (e.g., one or more configurations of authorized configurations with an index). For example, a configured authorized configuration with an index "X" can be replaced by a configured authorized configuration group with an index "X."

[0229] In addition, in the systems and methods disclosed herein, a PUSCH configuration (e.g., a PUSCH configuration with an index) may be replaced by a PUSCH configuration group (e.g., a PUSCH configuration group with an index). Here, the PUSCH configuration group may include one or more PUSCH configurations (e.g., one or more PUSCH configurations with an index).

[0230] Some parameters may be common across grant configurations of different configurations. That is, some parameters may be shared by grants of multiple configurations. Common or shared parameters may include frequencyHopping, cg-DMRS-Configuration, mcs-Table, mcs-TableTransformPrecoder, uci-OnPUSCH, resourceAllocation, rbg-Size, powerControlLoopToUse, p0-PUSCH-Alpha, transformPrecoder, nrofHARQ-Processes, repK, repK-RV, periodicity, timeDomainOffset, timeDomainAllocation, frequencyDomainAllocation, antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, srs-ResourceIndicator, mcsAndTBS, frequencyHoppingOffset, pathlossReferenceIndex, CG-UCI-OnPUSCH, pusch-TimeDomainAllocationList, repetition set, dynamic repetition enabler, or any combination of the above.

[0231] For example, the RRC message may include a common configuration (e.g., ConfiguredGrantConfig-common IE). The ConfiguredGrantConfig-common IE may include the above-mentioned common parameters or shared parameters. When one or more configured grants are configured, the parameters in the ConfiguredGrantConfig-common IE may or may not be applied to the corresponding configured grant. If the corresponding one or more parameters are not included in the grant configuration of a specific configuration (e.g., ConfiguredGrantConfig IE), the grant of the specific configuration may follow and / or apply the one or more parameters included in the common configuration (e.g., ConfiguredGrantConfig-common IE).

[0232] Some parameters can be configured in both the public configuration (e.g., ConfiguredGrantConfig - Public IE) and the configuration-specific grant configuration (e.g., ConfiguredGrantConfig). By design, parameters in the configuration-specific grant configuration can override parameters in the ConfiguredGrantConfig - Public IE. That is, even if the same parameter may have been configured in the public configuration (e.g., ConfiguredGrantConfig - Public IE), the configuration value of the parameter in the configuration-specific grant configuration can also be applied to the corresponding configuration grant.

[0233] In yet another design, parameters in the ConfiguredGrantConfig-Common IE may override parameters in the grant configuration of a specific configuration. That is, regardless of whether the same parameters have been configured in the grant configuration of a specific configuration (e.g., ConfiguredGrantConfig IE), the configuration values of the parameters in the common configuration (e.g., ConfiguredGrantConfig-Common IE) may be applied to the grant of the corresponding configuration.

[0234] In yet another design, for a configured grant type 2, if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set), UE 102 may perform transmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, even if some parameters of the one or more configurations of the configured grant are configured by a specific configuration (e.g., the ConfiguredGrantConfig IE), if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in the CSS, UE 102 may perform transmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, in the event that a DCI format (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by CS-RNTI is detected in the USS (e.g., USS set), UE 102 may perform transmission corresponding to the configured grant based on parameters in a specific configuration (e.g., ConfiguredGrantConfig IE).

[0235] In yet another design, if a DCI format (e.g., with NDI set to “1”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set), UE 102 may perform retransmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, even if some parameters of the one or more configurations of the configured grant are configured by a specific configuration (e.g., the ConfiguredGrantConfig IE), if a DCI format (e.g., with NDI set to “1”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in the CSS, UE 102 may perform retransmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, in the event that a DCI format (e.g., NDI is set to "1") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by CS-RNTI is detected in a USS (e.g., USS set), UE 102 may perform retransmission corresponding to the configured grant based on parameters in a specific configuration (e.g., ConfiguredGrantConfig IE).

[0236] In yet another design, for a configured grant type 2, if a DCI format with a CRC scrambled by a CS-RNTI (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, UE 102 may perform transmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, even if some parameters of the one or more configurations of the configured grant are configured by a specific configuration (e.g., ConfiguredGrantConfig IE), if a DCI format with a CRC scrambled by a CS-RNTI (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, UE 102 may perform transmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, in the event that a DCI format (e.g., NDI is set to "0") having a CRC scrambled by CS-RNTI is detected in a CORESET other than CORESET#0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform transmission corresponding to the configured grant based on parameters in a specific configuration (e.g., ConfiguredGrantConfig IE).

[0237] In yet another design, if a DCI format with a CRC scrambled by a CS-RNTI (e.g., with NDI set to “1”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, UE 102 may perform retransmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, even if some parameters of the one or more configurations of the configured grant are configured by a specific configuration (e.g., ConfiguredGrantConfig IE), if a DCI format with a CRC scrambled by a CS-RNTI (e.g., with NDI set to “1”) (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET #0, UE 102 may perform retransmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI is set to "1") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a CORESET other than CORESET#0, UE102 may perform retransmission corresponding to the configured grant based on parameters in a specific configuration (e.g., ConfiguredGrantConfig IE).

[0238] In yet another design, for a configured grant type 2, if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a search space set with an index of “0” (i.e., search space set #0), UE 102 may perform transmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, even if some parameters of the one or more configurations of the configured grant are configured by a specific configuration (e.g., ConfiguredGrantConfig IE), if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a search space set with an index of “0” (i.e., search space set #0), UE 102 may perform transmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI is set to "0") is detected in a search space set other than search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform transmission corresponding to the configured grant based on parameters in a specific configuration (e.g., ConfiguredGrantConfig IE).

[0239] In yet another design, if a DCI format (e.g., with NDI set to “1”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a search space set with an index of “0” (i.e., search space set #0), UE 102 may perform retransmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, even if some parameters of the one or more configurations of the configured grant are configured by a specific configuration (e.g., ConfiguredGrantConfig IE), if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format of DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a search space set with an index of “1” (i.e., search space set #0), UE 102 may perform retransmission corresponding to the configured grant based on parameters in the ConfiguredGrantConfig-Common IE. That is, in the event that a DCI format with a CRC scrambled by CS-RNTI (e.g., NDI is set to "1") is detected in a search space set other than search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission corresponding to the configured grant based on parameters in a specific configuration (e.g., ConfiguredGrantConfig IE).

[0240] In yet another example, the above-mentioned common parameters or shared parameters may be included in the configuration of a grant of a specific configuration referred to as a grant of a primary configuration (e.g., a grant of a configuration with an index “predetermined value (e.g., 0)”, a ConfiguredGrantConfig IE with a configuration index of 0). Grants of other configurations referred to as grants of a secondary configuration (e.g., grants of configurations with indexes other than “predetermined value (e.g., 0)”) may follow and / or apply the common parameters or shared parameters included in the configuration of the grant for the primary configuration. If the corresponding one or more parameters are not included in the grant configuration of a configuration other than the grant configuration of the primary configuration (e.g., the grant configuration of a configuration with an index “X” other than the index “predetermined value”), the grant configuration of the configuration other than the primary configuration may apply and / or follow the one or more parameters included in the configuration of the grant of the primary configuration (e.g., the grant configuration of the configuration with an index “predetermined value (e.g., 0)”).

[0241] Some parameters can be configured in both the grant configuration of the primary configuration (e.g., a configured grant with the index "predetermined value (e.g., 0)", the ConfiguredGrantConfig IE with the configuration index 0) and the grant configuration of the secondary configuration (e.g., a configured grant with an index other than "predetermined value (e.g., 0)"). By design, parameters in the grant configuration of the primary configuration can override parameters in the grant configuration of the secondary configuration. That is, even if the same parameter may have already been configured in the grant configuration of the secondary configuration, the configuration value of the parameter in the grant configuration of the primary configuration can also be applied to the grant of the secondary configuration.

[0242] In yet another design, parameters in the grant configuration of a secondary configuration may override parameters in the grant configuration of a primary configuration. That is, regardless of whether the same parameter may have been configured in the grant configuration of the primary configuration (e.g., ConfiguredGrantConfigIE), the configuration value of the parameter in the grant configuration of the secondary configuration may be applied to the grant of the secondary configuration.

[0243] In yet another design, for a configured grant type 2, if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set), UE 102 may perform transmission corresponding to a secondary configured grant (e.g., a configured grant with an index other than “predetermined value (e.g., 0)”) based on parameters in a primary configured grant configuration (e.g., a configured grant with an index “predetermined value (e.g., 0)”, a ConfiguredGrantConfig IE with a configuration index of 0). That is, even if some parameters for the secondary configured grant are configured by the secondary configured grant configuration, if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in the CSS, UE 102 may perform transmission corresponding to the secondary configured grant based on parameters in the primary configured grant configuration. That is, in the case where a DCI format (e.g., NDI is set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by the CS-RNTI is detected in the USS (i.e., USS set), the UE 102 may perform transmission corresponding to the secondary configured grant based on the parameters in the secondary configured grant configuration.

[0244] In yet another design, if a DCI format (e.g., with NDI set to “1”) having a CRC scrambled by a CS-RNTI is detected in a CSS (i.e., a CSS set) (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission corresponding to a secondary configured grant (e.g., a configured grant having an index other than “predetermined value (e.g., 0)”) based on parameters in a primary configured grant configuration (e.g., a configured grant having an index “predetermined value (e.g., 0)”, a ConfiguredGrantConfig IE having a configuration index of 0). That is, even if some parameters for the secondary configured grant are configured by the secondary configured grant configuration, if a DCI format (e.g., with NDI set to “1”) having a CRC scrambled by a CS-RNTI is detected in the CSS (e.g., DCI format of DCI format 0_0 and / or DCI format 0_1), UE 102 may perform transmission corresponding to the secondary configured grant based on parameters in the primary configured grant configuration. That is, in the event that a DCI format (e.g., NDI is set to "1") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by the CS-RNTI is detected in the USS (i.e., USS set), the UE 102 may perform retransmission corresponding to the secondary configured grant based on the parameters in the secondary configured grant configuration.

[0245] In yet another design, for configured grant type 2, if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in CORESET #0, UE 102 may perform transmission corresponding to a secondary configured grant (e.g., a configured grant with an index other than “predetermined value (e.g., 0)”) based on parameters in the primary configured grant configuration (e.g., a configured grant with an index “predetermined value (e.g., 0)”, a ConfiguredGrantConfig IE with a configuration index of 0). That is, even if some parameters for the secondary configured grant are configured by the secondary configured grant configuration, if a DCI format (e.g., with NDI set to “0”) (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in CORESET #0, UE 102 may perform transmission corresponding to the secondary configured grant based on parameters in the primary configured grant configuration. That is, in the case where a DCI format (e.g., NDI is set to "0") having a CRC scrambled by CS-RNTI is detected in a CORESET other than CORESET#0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform transmission corresponding to the secondary configured grant based on the parameters in the secondary configured grant configuration.

[0246] In yet another design, if a DCI format (e.g., with NDI set to “1”) having a CRC scrambled by a CS-RNTI is detected in CORESET #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission corresponding to a secondary configured grant (e.g., a configured grant with an index other than “predetermined value (e.g., 0)”) based on parameters in the grant configuration of the primary configuration (e.g., a configured grant with an index “predetermined value (e.g., 0)”, a ConfiguredGrantConfig IE with a configuration index of 0). That is, even if some parameters for the secondary configured grant are configured by the grant configuration of the secondary configuration, if a DCI format (e.g., with NDI set to “1”) having a CRC scrambled by a CS-RNTI is detected in CORESET #0 (e.g., DCI format of DCI format 0_0 and / or DCI format 0_1), UE 102 may perform transmission corresponding to the secondary configured grant based on parameters in the grant configuration of the primary configuration. That is, in the event that a DCI format having a CRC scrambled by CS-RNTI (e.g., NDI is set to "1") (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a CORESET other than CORESET#0, UE 102 may perform retransmission corresponding to the grant of the secondary configuration based on the parameters in the grant configuration of the secondary configuration.

[0247] In yet another design, for configured grant type 2, in a case where a DCI format (e.g., NDI set to "0") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a search space set with index "0" (i.e., search space set #0), UE 102 may perform transmission corresponding to a secondary configured grant (e.g., a configured grant with an index other than "predetermined value (e.g., 0)") based on parameters in the primary configured grant configuration (e.g., a configured grant with an index "predetermined value (e.g., 0)", a ConfiguredGrantConfig IE with a configuration index 0). That is, even if some parameters for the grant of the secondary configuration are configured by the grant configuration of the secondary configuration, if a DCI format (e.g., NDI is set to "0") with a CRC scrambled by the CS-RNTI is detected in the search space set with index "0" (i.e., search space set #0) (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform transmission corresponding to the grant of the secondary configuration based on the parameters in the grant configuration of the primary configuration. That is, if a DCI format (e.g., NDI is set to "0") with a CRC scrambled by the CS-RNTI is detected in a search space set other than search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform transmission corresponding to the grant of the secondary configuration based on the parameters in the grant configuration of the secondary configuration.

[0248] In yet another design, in a case where a DCI format (e.g., NDI set to "1") (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by a CS-RNTI is detected in a search space set with an index of "0" (i.e., search space set #0), UE 102 may perform retransmission corresponding to a secondary configured grant (e.g., a configured grant with an index other than "predetermined value (e.g., 0)") based on parameters in the primary configured grant configuration (e.g., a configured grant with an index "predetermined value (e.g., 0)", ConfiguredGrantConfig IE with a configuration index of 0). That is, even if some parameters for the grant of the secondary configuration are configured by the grant configuration of the secondary configuration, if a DCI format (e.g., NDI is set to "1") with a CRC scrambled by the CS-RNTI is detected in the search space set with index "0" (i.e., search space set #0) (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission corresponding to the grant of the secondary configuration based on the parameters in the grant configuration of the primary configuration. That is, if a DCI format (e.g., NDI is set to "1") with a CRC scrambled by the CS-RNTI is detected in a search space set other than search space set #0 (e.g., DCI format 0_0 and / or DCI format 0_1), UE 102 may perform retransmission corresponding to the grant of the secondary configuration based on the parameters in the grant configuration of the secondary configuration.

[0249] Minislot repetition and / or multi-segment transmission may also be supported for configured grants and / or grant-based PUSCH transmissions. Minislot repetition and / or multi-segment transmission may be enabled and / or configured jointly or individually for each configured grant and / or each PUSCH configuration.

[0250] For example, a grant configuration using one UL grant for dynamic PUSCH and one configuration for granted PUSCH configured via Option A can be used to support one or more actual PUSCH repetitions in a slot, or two or more actual PUSCH repetitions across slot boundaries in consecutive available slots. The number of repetitions signaled by gNB 160 (dynamically, e.g., via DCI indication, or semi-statically, e.g., via RRC configuration, or a combination thereof) can represent a "nominal" number of repetitions. The actual number of repetitions can be greater than the nominal number. The Time Domain Resource Allocation (TDRA) field in the DCI or the TDRA parameter in a Type 1 configured grant indicates the resources for the first "nominal" repetition. The time domain resources for the remaining repetitions are derived based on at least the resources used for the first repetition and the UL / DL direction of the symbol. If the "nominal" repetition (transmission opportunity) crosses a slot boundary or a DL / UL switch point, the "nominal" repetition (transmission opportunity) is split into multiple PUSCH repetitions (transmission opportunities), with one PUSCH repetition (transmission opportunity) per UL cycle in the slot. When multiple configurations of configured grants and / or multiple configurations of PUSCH transmissions are supported, Option A may be configured and / or enabled individually or collectively for each configured grant configuration and / or each PUSCH transmission configuration. One or more new tables for TDRA may be introduced for use with Option A. The new table for TDRA may be fixed by a specification (e.g., a default table). The new table for TDRA may be RRC configured. The new table for TDRA may generally be configured for multiple configurations of configured grants and / or multiple configurations of PUSCH transmissions. The new table for TDRA may be configured and / or enabled individually for each configured grant configuration and / or each PUSCH transmission configuration. How to determine the table for TDRA may follow the same process as the other parameter determinations described above.

[0251] In another example, one or more PUSCH repetitions in a time slot, or two or more PUSCH repetitions across time slot boundaries in consecutive available time slots, are supported using one UL grant for dynamic PUSCH and one configured grant configuration for authorized PUSCH configured via Option B. The Time Domain Resource Allocation (TDRA) field in the DCI or the TDRA parameter in the grant configured for Type 1 indicates an entry in a table configured by a higher layer. The number of repetitions, the starting symbol for each repetition, the length of each repetition, and the mapping of repetitions to time slots can be obtained from each entry in the table. More than one repetition can be mapped to a time slot. The resource allocation for each repetition is contained within a time slot. The repetitions for each transmission are contained within one UL cycle in a time slot. Where multiple configurations of configured grants and / or multiple configurations of PUSCH transmissions are supported, Option B can be configured and / or enabled individually or collectively for each configured grant configuration and / or each PUSCH transmission configuration. One or more new tables for TDRA can be introduced for use with Option B. The new table for TDRA can be fixed by a specification (e.g., a default table). The new table for TDRA can be RRC configured. A new TDRA table can generally be configured for multiple configurations of configured grants and / or multiple configurations of PUSCH transmissions. A new TDRA table can be configured and / or enabled separately for each configured grant configuration and / or each PUSCH transmission configuration. Determining the TDRA table can follow the same process as for determining other parameters described above.

[0252] Option A and Option B may be supported simultaneously. For example, Option A may be enabled and / or configured for one of the plurality of configurations, while Option B may be enabled and / or configured for another of the plurality of configurations. In yet another example, Option A (or Option B) may be enabled and / or configured for a configured grant, while Option B (or Option A) may be enabled and / or configured for grant-based PUSCH. In yet another example, Option A (or Option B) may be enabled and / or configured for a configured Grant Type 1, while Option B (or Option A) may be enabled and / or configured for a configured Grant Type 2.

[0253] Figure 6 1 shows various components that may be utilized in UE 602. Figure 6 The UE 602 described may be configured in accordance with Figure 1102. The UE 602 includes a processor 603 that controls the operation of the UE 602. The processor 603 may also be referred to as a central processing unit (CPU). A memory 605 (which may include read-only memory (ROM), random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 607a and data 609a to the processor 603. A portion of the memory 605 may also include non-volatile random access memory (NVRAM). Instructions 607b and data 609b may also reside in the processor 603. The instructions 607b and / or data 609b loaded into the processor 603 may also include instructions 607a and / or data 609a from the memory 605 and loaded for execution or processing by the processor 603. The instructions 607b may be executed by the processor 603 to implement the methods described herein.

[0254] The UE 602 may also include a housing that houses one or more transmitters 658 and one or more receivers 620 to allow for transmission and reception of data. The transmitters 658 and receivers 620 may be combined into one or more transceivers 618. One or more antennas 622a-n are attached to the housing and electrically coupled to the transceiver 618.

[0255] The various components of the UE 602 are coupled together via a bus system 611 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are not shown in FIG. Figure 6 6 as a bus system 611. The UE 602 may also include a digital signal processor (DSP) 613 for processing signals. The UE 602 may also include a communication interface 615 that provides user access to the functions of the UE 602. Figure 6 The UE 602 is shown as a functional block diagram rather than a listing of specific components.

[0256] Figure 7 Various components that may be utilized in gNB 760 are shown. Figure 7 The gNB760 described can be combined with Figure 1The gNB 760 may be implemented using the gNB 160 described herein. The gNB 760 includes a processor 703 that controls the operation of the gNB 760. The processor 703 may also be referred to as a central processing unit (CPU). Memory 705 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device capable of storing information) provides instructions 707a and data 709a to the processor 703. A portion of the memory 705 may also include non-volatile random access memory (NVRAM). Instructions 707b and data 709b may also reside in the processor 703. The instructions 707b and / or data 709b loaded into the processor 703 may also include instructions 707a and / or data 709a from the memory 705 that are loaded for execution or processing by the processor 703. The instructions 707b may be executed by the processor 703 to implement the methods described herein.

[0257] The gNB 760 may also include a housing that houses one or more transmitters 717 and one or more receivers 778 to allow for transmission and reception of data. The transmitters 717 and receivers 778 may be combined into one or more transceivers 776. One or more antennas 780a-n are attached to the housing and electrically coupled to the transceivers 776.

[0258] The various components of the gNB 760 are coupled together via a bus system 711 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for clarity, the various buses are not referred to in the following sections. Figure 7 760 is shown as bus system 711. gNB 760 may also include a digital signal processor (DSP) 713 for processing signals. gNB 760 may also include a communication interface 715 that provides users with access to the functions of gNB 760. Figure 7 The gNB 760 shown is a functional block diagram rather than a listing of specific components.

[0259] Figure 8 8 is a block diagram illustrating one specific implementation of a UE 802 in which one or more of the systems and / or methods described herein may be implemented. The UE 802 includes a transmitting device 858, a receiving device 820, and a control device 824. The transmitting device 858, the receiving device 820, and the control device 824 may be configured to perform a combination of the above. Figure 1 One or more of the functions described above. Figure 6 Shown Figure 8 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0260] Figure 9is a block diagram illustrating one specific implementation of a gNB 960 in which one or more of the systems and / or methods described herein may be implemented. The gNB 960 includes a transmitting device 917, a receiving device 978, and a control device 982. The transmitting device 917, the receiving device 978, and the control device 982 may be configured to perform a combination of the above. Figure 1 One or more of the functions described above. Figure 7 Shown Figure 9 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0261] Figure 10 is a block diagram illustrating a specific implementation of gNB 1060. gNB 1060 may be combined with Figure 1 10. The gNB 1060 may include a higher layer processor 1023, a DL transmitter 1025, a UL receiver 1033, and one or more antennas 1031. The DL transmitter 1025 may include a PDCCH transmitter 1027 and a PDSCH transmitter 1029. The UL receiver 1033 may include a PUCCH receiver 1035 and a PUSCH receiver 1037.

[0262] The higher-layer processor 1023 manages the behavior of the physical layer (DL transmitter and UL receiver) and provides higher-layer parameters to the physical layer. The higher-layer processor 1023 can obtain transport blocks from the physical layer. The higher-layer processor 1023 can send and receive higher-layer messages, such as RRC messages and MAC messages, to and from the higher layers of the UE. The higher-layer processor 1023 can provide transport blocks to the PDSCH transmitter and provide transmission parameters related to the transport blocks to the PDCCH transmitter.

[0263] The DL transmitter 1025 may multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via the transmission antenna 1031. The UL receiver 1033 may receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via the reception antenna 1031. The PUCCH receiver 1035 may provide UCI to the higher layer processor 1023. The PUSCH receiver 1037 may provide the received transport block to the higher layer processor 1023.

[0264] Figure 11 1 is a block diagram illustrating a specific implementation of UE 1102. UE 1102 may be a combination of Figure 1UE 1102 may include a higher layer processor 1123, a UL transmitter 1151, a DL receiver 1143, and one or more antennas 1131. The UL transmitter 1151 may include a PUCCH transmitter 1153 and a PUSCH transmitter 1155. The DL receiver 1143 may include a PDCCH receiver 1145 and a PDSCH receiver 1147.

[0265] The higher layer processor 1123 manages the behavior of the physical layer (DL transmitter and UL receiver) and provides higher layer parameters to the physical layer. The higher layer processor 1123 can obtain transport blocks from the physical layer. The higher layer processor 1123 can send and receive higher layer messages, such as RRC messages and MAC messages, to and from the higher layers of the UE. The higher layer processor 1123 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1153.

[0266] The DL receiver 1143 may receive and demultiplex the multiplexed downlink physical channel and the downlink physical signal via the reception antenna 1131. The PDCCH receiver 1145 may provide DCI to the higher layer processor 1123. The PDSCH receiver 1147 may provide the higher layer processor 1123 with the received transport block.

[0267] As described above, some methods for DL and / or UL transmission may be applied (e.g., specified). Here, a combination of one or more of the methods described herein may be applied to DL and / or UL transmission. The systems and methods may not exclude a combination of one or more of the methods described herein.

[0268] It should be noted that the names of the physical channels described herein are examples, and other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH," "new generation (G)PDCCH, GPDSCH, GPUCCH, and GPUSCH," and the like.

[0269] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or processor-readable medium. By way of example, and not limitation, computer-readable or processor-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disks and optical disks, as used herein, include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Optical disks, where magnetic disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. It should be noted that one or more of the methods described herein may be implemented in and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or performed using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit.

[0270] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with one another and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0271] It is to be understood that the claims are not limited to the precise configuration and components shown above, and that various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

[0272] The program running on the gNB 160 or UE 102 according to the systems and methods described herein controls the CPU, etc., to implement the functions according to the systems and methods (a program that causes the computer to operate). Information processed by these devices is then temporarily stored in RAM while being processed. This information is then stored in various ROMs or HDDs and read by the CPU for modification or writing whenever necessary. Possible recording media on which the program is stored include semiconductors (e.g., ROMs, nonvolatile memory cards, etc.), optical storage media (e.g., DVDs, MOs, MDs, CDs, BDs, etc.), and magnetic storage media (e.g., magnetic tapes, floppy disks, etc.). In some cases, the functions according to the systems and methods described herein are implemented by executing the loaded program. Alternatively, the functions according to the systems and methods are implemented based on instructions from the program in conjunction with an operating system or other application programs.

[0273] Furthermore, if the program is commercially available, it can be distributed stored on a portable recording medium, or it can be transferred to a server computer connected via a network such as the Internet. In this case, the storage device in the server computer is also included. Furthermore, some or all of the gNB 160 and UE 102 according to the systems and methods described herein can be implemented as LSIs, which are typical integrated circuits. Each functional block of the gNB 160 and UE 102 can be individually built into a chip, and some or all functional blocks can be integrated into a chip. Furthermore, integrated circuit technology is not limited to LSIs, and integrated circuits for functional blocks can be implemented using dedicated circuits or general-purpose processors. Furthermore, if integrated circuit technology that replaces LSIs emerges as semiconductor technology continues to advance, integrated circuits using such technology can also be used.

[0274] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned embodiments can be realized or executed by circuit (typically an integrated circuit or multiple integrated circuits). The circuit designed to perform the function described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices or discrete hardware components or a combination thereof. The general-purpose processor can be a microprocessor, or alternatively, the processor can be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or every kind of circuit described herein can be configured by a digital circuit, or can be configured by an analog circuit. In addition, when the technology of the integrated circuit replacing current integrated circuit occurs due to the progress of semiconductor technology, it is also possible to use the integrated circuit produced by this technology.

[0275] As used herein, the term "and / or" should be interpreted as meaning one or more items. For example, the phrase "A, B, and / or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "at least one" should be interpreted as meaning one or more items. For example, the phrase "at least one of A, B, and C" or the phrase "at least one of A, B, or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "one or more" should be understood to refer to one or more items. For example, the phrase "one or more of A, B, and C" or the phrase "one or more of A, B, or C" should be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.

[0276] <Summary>

[0277] In one example, a user equipment (UE) includes: a receiving circuit configured to receive a common configuration, the common configuration including parameters shared by grants of multiple configurations; and a transmitting circuit configured to perform a transmission on a physical uplink shared channel (PUSCH) based on the parameters shared by the grants of the multiple configurations of the common configuration.

[0278] In one example, in the UE, parameters in the authorization of the specific configuration override parameters of the public configuration.

[0279] In one example, in the UE, the parameters of the public configuration override the parameters in the authorization of the specific configuration.

[0280] In one example, in the UE, the shared parameters are included in the configuration for authorization of the main configuration.

[0281] In one example, in the UE, the authorization of the secondary configuration follows the shared parameters included in the configuration for the authorization of the primary configuration.

[0282] In one example, a base station apparatus includes: a transmission circuit configured to transmit a common configuration comprising parameters shared by authorizations of multiple configurations; and a reception circuit configured to receive transmissions on a physical uplink shared channel (PUSCH) based on the parameters shared by the authorizations of the multiple configurations of the common configuration.

[0283] In one example, in the base station apparatus, parameters in the authorization of the specific configuration override parameters of the public configuration.

[0284] In one example, in the base station apparatus, the parameters of the public configuration override the parameters in the authorization of the specific configuration.

[0285] In one example, in the base station apparatus, the shared parameters are included in a configuration for authorization of the main configuration.

[0286] In one example, in the base station apparatus, the authorization of the secondary configuration follows the shared parameters included in the configuration for the authorization of the primary configuration.

[0287] In one example, a communication method of a user equipment (UE) includes: receiving a common configuration, the common configuration including parameters shared by multiple configurations; and performing transmission on a physical uplink shared channel (PUSCH) based on the parameters shared by the multiple configurations of the common configuration.

[0288] In one example, in the method, parameters in the authorization of a specific configuration override parameters of the common configuration.

[0289] In one example, in the method, parameters of the public configuration override parameters in the authorization of the specific configuration.

[0290] In one example, in the method, the shared parameters are included in the configuration for authorization of the master configuration.

[0291] In one example, in the method, wherein authorization of the secondary configuration follows shared parameters included in the configuration for authorization of the primary configuration.

[0292] In one example, a communication method of a base station device includes: transmitting a common configuration, which includes parameters shared by multiple configurations of authorization; and receiving transmissions on a physical uplink shared channel (PUSCH) based on the parameters shared by the multiple configurations of authorization by the common configuration.

[0293] In one example, in the method, parameters in the authorization of a specific configuration override parameters of the common configuration.

[0294] In one example, in the method, parameters of the public configuration override parameters in the authorization of the specific configuration.

[0295] In one example, in the method, the shared parameters are included in the configuration for authorization of the master configuration.

[0296] In one example, in the method, wherein authorization of the secondary configuration follows shared parameters included in the configuration for authorization of the primary configuration.

[0297] In one example, a user equipment (UE) communicating with a base station includes: a receiving circuit configured to: receive a radio resource control (RRC) message including first information indicating a repetition type for a first configured grant (CG) physical uplink shared channel (PUSCH) transmission, receive an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, receive an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission; a transmitting circuit configured to: perform a first CG PUSCH transmission based on the first information and the third information, and perform a second CG PUSCH transmission based on the second information and the third information.

[0298] In one example, a base station device that communicates with a user equipment (UE) includes: a transmission circuit configured to: transmit a radio resource control (RRC) message including first information indicating a repetition type for a first configured grant (CG) physical uplink shared channel (PUSCH) transmission, transmit an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, and transmit an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission; and a receiving circuit configured to: receive a first CG PUSCH transmission based on the first information and the third information, and receive a second CG PUSCH transmission based on the second information and the third information.

[0299] In one example, a communication method of a user equipment includes: receiving a radio resource control (RRC) message including first information indicating a repetition type for a grant (CG) physical uplink shared channel (PUSCH) transmission of a first configuration, receiving an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, receiving an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission, performing a first CG PUSCH transmission based on the first information and the third information, and performing a second CG PUSCH transmission based on the second information and the third information.

[0300] In one example, a communication method of a base station device includes: transmitting a radio resource control (RRC) message including first information indicating a repetition type for a first configured grant (CG) physical uplink shared channel (PUSCH) transmission, transmitting an RRC message including second information indicating a repetition type for a second CG PUSCH transmission, transmitting an RRC message including third information indicating whether codebook-based transmission or non-codebook-based transmission is used for the first CG PUSCH transmission and the second CG PUSCH transmission, receiving a first CG PUSCH transmission based on the first information and the third information, and receiving a second CG PUSCH transmission based on the second information and the third information.

[0301] <Cross Reference>

[0302] This nonprovisional application claims priority under 35 U.S.C. §119 to provisional application 62 / 842,129, filed on May 2, 2019, the entire contents of which are hereby incorporated by reference.

Claims

1. A user equipment (UE) for communicating with a base station, the UE comprising: A receiving circuit, wherein the receiving circuit is configured to: Receive a radio resource control (RRC) message, where the RRC message includes: first information indicating that more than one configuration of granting CG physical uplink shared channel (PUSCH) transmission is configured for the UE; second information indicating a first configuration of a first CG PUSCH transmission; third information indicating a second configuration of a second CG PUSCH transmission; and Parameter PUSCH-Config, and A transmission circuit, the transmission circuit being configured to: performing the first CG PUSCH transmission based on the second information and the parameter PUSCH-Config, and The second CG PUSCH transmission is performed based on the third information and the parameter PUSCH-Config, wherein: In CG type 1, the second information includes information indicating a repetition type for the first CG PUSCH transmission, and the third information includes information indicating a repetition type for the second CG PUSCH transmission, and In CG type 2, information indicating a repetition type is commonly configured for the first CG PUSCH transmission and the second CG PUSCH transmission.

2. A base station apparatus for communicating with a user equipment (UE), the base station apparatus comprising: A transmission circuit, the transmission circuit being configured to: Transmitting a radio resource control (RRC) message, the RRC message including: first information indicating that more than one configuration of granting CG physical uplink shared channel (PUSCH) transmission is configured for the UE; second information indicating a first configuration of a first CG PUSCH transmission; third information indicating a second configuration of a second CG PUSCH transmission; and Parameter PUSCH-Config, and A receiving circuit, wherein the receiving circuit is configured to: receiving the first CG PUSCH transmission based on the second information and the parameter PUSCH-Config, and The second CG PUSCH transmission is received based on the third information and the parameter PUSCH-Config, wherein: In CG type 1, the second information includes information indicating a repetition type for the first CG PUSCH transmission, and the third information includes information indicating a repetition type for the second CG PUSCH transmission, and In CG type 2, information indicating a repetition type is commonly configured for the first CG PUSCH transmission and the second CG PUSCH transmission.

3. A communication method for user equipment (UE), the communication method comprising: Receive a radio resource control (RRC) message, where the RRC message includes: first information indicating that more than one configuration of granting CG physical uplink shared channel (PUSCH) transmission is configured for the UE; second information indicating a first configuration of a first CG PUSCH transmission; third information indicating a second configuration of a second CG PUSCH transmission; and Parameter PUSCH-Config, performing the first CG PUSCH transmission based on the second information and the parameter PUSCH-Config, and The second CG PUSCH transmission is performed based on the third information and the parameter PUSCH-Config, wherein: In CG type 1, the second information includes information indicating a repetition type for the first CG PUSCH transmission, and the third information includes information indicating a repetition type for the second CG PUSCH transmission, and In CG type 2, information indicating a repetition type is commonly configured for the first CG PUSCH transmission and the second CG PUSCH transmission.

Images