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

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive first downlink control information (DCI) for indicating deactivation of a configured grant corresponding to a configured grant configuration with a first index. The UE further includes a transmitting circuit configured to transmit a configured grant acknowledgement medium access control (MAC) control element (CE) based on receiving the first DCI. The configured grant acknowledgement MAC CE includes a value indicating a deactivation state of the configured grant configuration with the first index.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to new signaling, procedures, user equipment (UE), and base stations 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 services, extended coverage areas, 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 can be a device that communicates with wireless communication devices.

[0003] With the development of wireless communication devices, there has been a continuous search for ways to improve communication capacity, speed, flexibility, and / or efficiency. However, improving communication capacity, speed, flexibility, and / or efficiency may pose certain problems.

[0004] For example, a wireless communication device can communicate with one or more devices using a communication structure. However, the communication structure used may provide only limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving 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 apparatus, the UE comprising: a receiving circuit configured to receive a first radio resource control (RRC) message including first information for configuring more than one configured grant (CG) physical uplink shared channel (PUSCH) configuration, each CG PUSCH configuration including a configuration index, the receiving circuit being configured to receive a second RRC message including second information for configuring a table for CG PUSCH configuration release, each entry in the table including a set of configuration indices, the receiving circuit being configured to detect a physical downlink control channel (PDCCH) in a downlink control information (DCI) format having a cyclic redundancy check (CRC) scrambled by a first radio network temporary identifier (RNTI), the DCI format being for activation and deactivation / release of the CG PUSCH configuration; a transmitting circuit configured to perform uplink data transmission on a PUSCH based on the first information based on detection of a DCI format including third information for indicating activation of uplink data transmission on the CG PUSCH; and a processing circuit configured to deactivate and / or release a corresponding CG PUSCH configuration according to the DCI format and the second information based on detection of a DCI format including fourth information for indicating deactivation / release of the CG PUSCH configuration, the index of the deactivated / released CG PUSCH configuration being given by the second information and / or the DCI format.

[0006] In one example, a base station device communicating with a user equipment (UE), the base station device comprising: a transmission circuit configured to transmit a first radio resource control (RRC) message including first information for configuring more than one configured grant (CG) physical uplink shared channel (PUSCH) configuration, each CG PUSCH configuration including a configuration index, the transmission circuit being configured to transmit a second RRC message including second information for configuring a table for CG PUSCH configuration release, each entry in the table including a set of configuration indexes, the transmission circuit being configured to transmit a physical downlink control channel (PDCCH) in a downlink control information (DCI) format having a cyclic redundancy check (CRC) scrambled by a first radio network temporary identifier (RNTI), the DCI format being for activation and deactivation / release of the CG PUSCH configuration; a receiving circuit configured to receive an uplink data transmission on the PUSCH based on the first information based on a transmission of a DCI format including third information for indicating activation of the uplink data transmission on the CG PUSCH; a processing circuit configured to deactivate and / or release a corresponding CG PUSCH configuration according to the DCI format and the second information based on a transmission of a DCI format including fourth information for indicating deactivation / release of the CG PUSCH configuration, the index of the deactivated / released CG PUSCH configuration being given by the second information and / or the DCI format.

[0007] In one example, a communication method of a user equipment (UE) communicating with a base station device, the method comprising: receiving a first radio resource control (RRC) message including first information for configuring more than one configured grant (CG) physical uplink shared channel (PUSCH) configuration, each CG PUSCH configuration including a configuration index; receiving a second RRC message including second information for configuring a table for CG PUSCH configuration release, each entry in the table including a set of configuration indexes; detecting a physical downlink control channel (PDCCH) in a downlink control information (DCI) format having a cyclic redundancy check (CRC) scrambled by a first radio network temporary identifier (RNTI), the DCI format being for activation and deactivation / release of the CG PUSCH configuration; transmitting an uplink data transmission on the PUSCH based on the first information based on a detection of a DCI format including third information for indicating activation of the uplink data transmission on the CG PUSCH; deactivating and / or releasing a corresponding CG PUSCH configuration according to the DCI format and the second information based on a detection of a DCI format including fourth information for indicating deactivation / release of the CG PUSCH configuration, the index of the deactivated / released CG PUSCH configuration being given by the second information and / or the DCI format.

[0008] In one example, a communication method for a base station device communicating with a user equipment (UE), the method comprising: transmitting a first radio resource control (RRC) message including first information for configuring more than one configured grant (CG) physical uplink shared channel (PUSCH) configuration, each CG PUSCH configuration including a configuration index; transmitting a second RRC message including second information for configuring a table for CG PUSCH configuration release, each entry in the table including a set of configuration indices; transmitting a physical downlink control channel (PDCCH) in a downlink control information (DCI) format having a cyclic redundancy check (CRC) scrambled by a first radio network temporary identifier (RNTI), the DCI format being for activation and deactivation / release of the CG PUSCH configuration; receiving an uplink data transmission on a PUSCH based on the first information based on transmission of a DCI format including third information for indicating activation of the uplink data transmission on the CG PUSCH; deactivating and / or releasing a corresponding CG PUSCH configuration according to the DCI format and the second information based on transmission of a DCI format including fourth information for indicating deactivation / release of the CG PUSCH configuration, the index of the deactivated / released CG PUSCH configuration being given by the second information and / or the DCI format. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a block diagram showing a particular implementation of one or more base station devices (gNBs) and one or more user equipments (UEs) in which a system and method for signaling can be implemented.

[0010] Figure 2 shows examples of a plurality of parameters.

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

[0012] Figure 4 shows examples of resource regions.

[0013] Figure 5 shows an example of a UL transmission corresponding to a configured grant.

[0014] Figure 6 shows an example of a configured grant acknowledgment medium access control (MAC) control element (CE).

[0015] Figure 7 shows various components that can be utilized in a UE.

[0016] Figure 8 shows various components that can be utilized in a gNB.

[0017] Figure 9 is a block diagram illustrating a specific implementation of a UE 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 in which one or more of the systems and / or methods described herein may be implemented.

[0019] Figure 11 is a block diagram illustrating a specific implementation of a gNB.

[0020] Figure 12 is a block diagram illustrating a specific implementation of a UE. Detailed Description

[0021] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a first downlink control information (DCI) for indicating deactivation of a configured grant corresponding to a configured grant configuration having a first index. The UE further includes a transmitting circuit configured to transmit a configured grant acknowledgment medium access control (MAC) control element (CE) based on receiving the first DCI. The configured grant acknowledgment MAC CE includes a value indicating a deactivation state of the configured grant configuration having the first index.

[0022] The receiving circuit may also be configured to receive a second DCI for indicating activation of a configured grant corresponding to a configured grant configuration having a second index. The transmitting circuit may also be configured to perform transmission on a physical uplink shared channel (PUSCH) based on receiving the second DCI. The configured grant acknowledgment MAC CE may include a value indicating an activation state of the configured grant configuration having the second index.

[0023] The size of a field for indicating an activation state and / or a deactivation state may be determined based on the number of configured grant configurations. The fields set to indicate values of an activation state and / or a deactivation state may be specified in ascending order based on the index of the configured grant configurations.

[0024] The present invention also describes a base station device. The base station device includes a transmitting circuit configured to transmit a first DCI for indicating deactivation of a configured grant corresponding to a configured grant configuration having a first index. The base station device further includes a receiving circuit configured to receive a configured grant acknowledgment MAC CE based on transmission of the first DCI. The configured grant acknowledgment MAC CE includes a value indicating a deactivation state of the configured grant configuration having the first index.

[0025] The present invention also describes a communication method for a UE. The method includes receiving a first DCI for indicating deactivation of a configured grant corresponding to a configured grant with a first index. The method also includes transmitting a configured grant acknowledgment MAC CE based on receiving the first DCI. The configured grant acknowledgment MAC CE includes a value indicating a deactivation state of the configured grant with the first index.

[0026] The present invention also describes a communication method for a base station device. The method includes transmitting a first DCI for indicating deactivation of a configured grant corresponding to a configured grant with a first index. The method also includes receiving a configured grant acknowledgment MAC CE based on the transmission of the first DCI. The configured grant acknowledgment MAC CE includes a value indicating a deactivation state of the configured grant with the first index.

[0027] The 3rd Generation Partnership Project (also known as "3GPP") is a cooperation agreement aimed at formulating globally applicable technical specifications and technical reports for third-generation and fourth-generation wireless communication systems. 3GPP can formulate specifications for next-generation mobile networks, systems, and devices.

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

[0029] 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 regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0030] A wireless communication device can be an electronic device that is used to transmit voice and / or data to a base station, which in turn can communicate with the device's network (e.g., the public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, the 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), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, the wireless communication device is typically referred to as a UE. However, since the scope of this 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 more generally be referred to as a terminal device.

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

[0032] It should be noted that, as used herein, a "cell" can be any such communication channel: which is designated by a standardization or regulatory body for use in International Mobile Telecommunications - Advanced (IMT - Advanced) and all or a subset thereof, such that it is 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 overall description of E - UTRA and E - UTRAN, as used herein, a "cell" can be defined (e.g., designated) as "a combination of downlink resources and optionally uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources can be indicated in the system information that can be transmitted on the downlink resources.

[0033] The fifth-generation communication system, which is referred to as NR (New Radio) by 3GPP, is envisioned to use time, frequency, and / or spatial resources to permit services such as eMBB (Enhanced Mobile Broadband) transmission, URLLC (Ultra-Reliable and Low-Latency Communication) transmission, and eMTC (Massive Machine-Type Communication) transmission. Also, in NR, transmissions for different services can be specified (e.g., configured) for one or more bandwidth parts (BWPs) in a serving cell and / or for one or more serving cells. A user equipment (UE) can receive downlink signals and / or transmit uplink signals in the BWP(s) of one and / or more serving cells.

[0034] To enable services to effectively use time, frequency, and / or spatial resources, it would be useful to be able to effectively control downlink and / or uplink transmissions. Accordingly, a process for effectively controlling downlink and / or uplink transmissions should be designed. Thus, a detailed design of the process for downlink and / or uplink transmissions may be beneficial.

[0035] Various examples of the systems and methods disclosed herein will now be described with reference to the drawings, where 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 specific implementations. Thus, the more detailed description of several specific implementations presented below is not intended to limit the scope of the claimed subject matter but merely represents the described systems and methods.

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

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

[0038] Each of the one or more UEs 102 can 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 operation module 124. For example, one or more receive paths and / or transmit paths can 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) can be implemented.

[0039] The transceiver 118 can include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 can receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 can receive and down-convert the signals to generate one or more received signals 116. The one or more received signals 116 can be provided to the demodulator 114. One or more transmitters 158 can transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, one or more transmitters 158 can up-convert and transmit one or more modulated signals 156.

[0040] The demodulator 114 may demodulate 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 signals. 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 operation module 124 can use to perform one or more operations.

[0041] Generally, the UE operation module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include one or more of the UE scheduling modules 126.

[0042] The UE scheduling module 126 may perform downlink reception and uplink transmission. The one or more downlink receptions include the reception of data, the reception of downlink control information, and / or the reception of downlink reference signals. Additionally, the uplink transmission includes the transmission of data, the transmission of uplink control information, and / or the transmission of uplink reference signals.

[0043] 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 a higher layer.

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

[0045] In another example, a Physical Uplink Control Channel (PUCCH) can be defined. The PUCCH can be used to transmit uplink control information (UCI). The UCI can include Hybrid Automatic Repeat reQuest - ACK (HARQ - ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The HARQ - ACK is used to indicate an 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). Additionally, 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)).

[0046] Here, the DL - SCH and / or UL - SCH can be transport channels used in the MAC layer. Additionally, a transport block (TB) and / or a MAC PDU can be defined as units of a transport channel used in the MAC layer. The transport block can be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer can deliver the 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, the transport block can be mapped to one or more codewords.

[0047] In the downlink, a Physical Downlink Control Channel (PDCCH) can be defined. The PDCCH can be used to transmit downlink control information (DCI). Here, more than one DCI format can be defined for DCI transmission on the PDCCH. That is, a DCI format can be defined with fields, and the fields can be mapped to information bits (e.g., DCI bits).

[0048] For example, DCI format 1_0 for scheduling the Physical Downlink Shared Channel (PDSCH) in a cell can be defined as a DCI format for the downlink. Additionally, as described herein, one or more Radio Network Temporary Identifiers (e.g., Cell Radio Network Temporary Identifier (C - RNTI), Configured Scheduling RNTI (CS - RNTI), System Information RNTI (SI - RNTI), and / or Random Access RNTI (RA - RNTI)) can be used to transmit DCI format 1_0. Additionally, DCI format 1_0 can 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 can be monitored (e.g., transmitted, mapped) only in the CSS.

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

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

[0051] For example, the DCI included in DCI format 1_1 can be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a frequency-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a time-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_1 can be a TPC command for the PUCCH used for scheduling. Additionally or alternatively, the DCI included in DCI format 1_1 can be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., CSI report (e.g., aperiodic CSI report)). Additionally or alternatively, as described below, the DCI included in DCI format 1_1 can be information for indicating an index of the configuration of DL semi-persistent scheduling (SPS) (e.g., SPS configuration index).

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

[0053] For example, the DCI included in DCI format 1_2 can be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a frequency-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a time-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_2 can be a TPC command for scheduling PUCCH. Additionally or alternatively, the DCI included in DCI format 1_2 can be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., CSI report (e.g., aperiodic CSI report)). Additionally or alternatively, the DCI included in DCI format 1_2 can be a configurable field, e.g., antenna port [0 - 2 bits], transmission configuration indicator [0 - 3 bits], rate matching indicator [0 - 2 bits], SRS request [0 - 3 bits], PRB bundling size indicator [0 - 1 bit], carrier indicator [0 - 3 bits], CSI request [0 - 3 bits], ZP CSI-RS trigger [0 - 2 bits], β offset indicator [0 - 2 bits], SRS resource indicator [0 - 4 bits], repetition factor [0 - 2 bits] and / or priority indicator [0 - 3 bits]. Additionally or alternatively, as described below, the DCI included in DCI format 1_2 can be information (e.g., SPS configuration index) for indicating an index of the configuration of DL semi-persistent scheduling (SPS).

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

[0055] 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 scheduling PUSCH.

[0056] Additionally or alternatively, DCI format 0_1 for scheduling PUSCH in a cell may be defined as a DCI format for the uplink. Additionally or alternatively, C-RNTI, 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.

[0057] 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 scheduling 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 the configuration index of a configured grant (e.g., CG configuration index).

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

[0059] For example, the DCI included in DCI format 0_2 may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a frequency-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a time-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_2 may be a TPC command for scheduling PUSCH. Additionally or alternatively, the DCI included in DCI format 0_2 may be a CSI request for requesting a CSI report. Additionally or alternatively, the DCI included in DCI format 0_2 may be a configurable field, e.g., antenna port [0 - 2 bits], transmission configuration indicator [0 - 3 bits], rate matching indicator [0 - 2 bits], SRS request [0 - 3 bits], PRB bundling size indicator [0 - 1 bit], carrier indicator [0 - 3 bits], CSI request [0 - 3 bits], ZP CSI-RS trigger [0 - 2 bits], β offset indicator [0 - 2 bits], SRS resource indicator [0 - 4 bits], repetition factor [0 - 2 bits] and / or priority indicator [0 - 3 bits]. Additionally or alternatively, as described below, the DCI included in DCI format 0_2 may be information for indicating the index of a configured grant (e.g., CG configuration index).

[0060] Additionally or alternatively, in the case of receiving DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 (e.g., based on detecting DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2), UE 102 may perform PDSCH reception. Additionally or alternatively, in the case of receiving DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 (e.g., based on detecting DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2), UE 102 may perform PUSCH transmission.

[0061] Here, as described above, the RNTI (e.g., radio network temporary identifier) assigned to UE 102 may be used for the transmission of DCI (e.g., one or more DCI formats, one or more DL control channels (e.g., one or more PDCCHs)). That is, gNB 160 may transmit (e.g., by using an RRC message) information for configuring (e.g., allocating) the RNTI to UE 102.

[0062] For example, CRC (Cyclic Redundancy Check) parity bits generated based on DCI (also simply referred to as CRC) are appended to the DCI, and after the appending, the CRC parity bits are scrambled by an RNTI. The UE 102 may attempt to decode (e.g., blind decode, monitor, detect) the DCI to which the CRC parity bits scrambled by the RNTI are appended. For example, the UE 102 detects a DL control channel (e.g., PDCCH, DCI, DCI format) based on blind decoding. That is, the UE 102 may use the CRC scrambled by the RNTI to decode the DL control channel. In other words, the UE 102 may use the RNTI to monitor the DL control channel. For example, the UE 102 may use the RNTI to detect the DCI format.

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

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

[0065] Additionally or alternatively, a Physical Downlink Shared Channel (PDSCH) and a Physical Uplink Shared Channel (PUSCH) may be defined. For example, in the case of scheduling the PDSCH (e.g., PDSCH resource) by using a DCI format, the UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resource). Additionally or alternatively, in the case of scheduling the PUSCH (e.g., PUSCH resource) by using a DCI format, the UE 102 transmits uplink data on the scheduled PUSCH (e.g., PUSCH resource). For example, the PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport block). Additionally or alternatively, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport block).

[0066] In addition, the PDSCH and / or PUSCH can be used to transmit information of 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) can 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) can be used to transmit MAC control elements (MAC CE). Here, the RRC messages and / or the MAC CE are also referred to as higher layer signals.

[0067] In some methods, a physical broadcast channel (PBCH) can be defined. For example, the PBCH can be used to broadcast the MIB (master information block). Here, the system information can be divided into the MIB and multiple SIBs (system information blocks). For example, the MIB can be used to carry the minimum system information. Additionally or alternatively, the SIB can be used to carry system information messages.

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

[0069] In radio communication for the uplink, the UL RS can be used as an uplink physical signal. Additionally or alternatively, in radio communication for the downlink, the DL RS can 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 the higher layer, but are used by the physical layer.

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

[0071] The UE operation module 124 can provide the information 148 to one or more receivers 120. For example, the UE operation module 124 can notify one or more receivers 120 when to receive a retransmission.

[0072] The UE operation module 124 can provide the information 138 to the demodulator 114. For example, the UE operation module 124 can notify the demodulator 114 of the modulation pattern expected for the transmission from the gNB 160.

[0073] The UE operation module 124 may provide information 136 to the decoder 108. For example, the UE operation module 124 may notify the decoder 108 of the encoding expected for transmissions from the gNB 160.

[0074] 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 transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0075] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operation 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, temporal, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to the modulator 154.

[0076] The UE operation module 124 may provide information 144 to the modulator 154. For example, the UE operation module 124 may notify the modulator 154 of the modulation type (e.g., constellation mapping) for transmission to the gNB 160. The modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0077] The UE operation module 124 may provide information 140 to one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operation 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 the UL subframe. The one or more transmitters 158 may up-convert the modulated signal 156 and transmit the modulated signal to one or more gNBs 160.

[0078] 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 operation module 182. For example, one or more receive paths and / or transmission 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.

[0079] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. 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 down-convert the signals to generate one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. One or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, one or more transmitters 117 may up-convert and transmit one or more modulated signals 115.

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

[0081] Generally, the gNB operation module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operation 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.

[0082] The gNB operation module 182 may provide information 188 to the demodulator 172. For example, the gNB operation module 182 may notify the demodulator 172 of the modulation pattern expected for transmissions from one or more UEs 102.

[0083] The gNB operation module 182 may provide information 186 to the decoder 166. For example, the gNB operation module 182 may notify the decoder 166 of the coding expected for transmissions from one or more UEs 102.

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

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

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

[0087] The gNB operation module 182 may provide the information 192 to one or more transmitters 117. The information 192 may include instructions for one or more transmitters 117. For example, the gNB operation module 182 may indicate to one or more transmitters 117 when (when not) to transmit signals to one or more UEs 102. One or more transmitters 117 may up-convert one or more modulated signals 115 and transmit the one or more modulated signals to one or more UEs 102.

[0088] 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 one or more UEs 102 may transmit data in standard special subframes.

[0089] It should also be noted that one or more of the elements or their components included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or their components may be implemented as chips, circuits, or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or executed using hardware. For example, one or more of the methods described herein may be implemented in a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc., and / or implemented using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

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

[0091] Additionally or alternatively, the number of OFDM symbols per time slot can be determined based on μ (e.g., subcarrier spacing configuration). Here, for example, time slot configuration 0 (e.g., the number of OFDM symbols per time slot can be 14) and / or time slot configuration (e.g., the number of OFDM symbols per time slot can be 7) can be defined.

[0092] Figure 3 is a diagram showing an example of a resource grid 301 and a resource block 391 (e.g., for downlink and / or uplink). Figure 3 The resource grid 301 and resource block 391 shown can be used in some specific implementations of the systems and methods disclosed herein.

[0093] In Figure 3 a subframe 369 can include symbols 387.

[0094] Additionally or alternatively, the resource block 391 can include multiple resource elements (REs) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) can be adopted, which can also be referred to as CP - OFDM. The downlink radio frame can include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to as physical resource blocks (PRBs). The downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slot. The downlink RB pair can include two consecutive downlink RBs 391 in the time domain. Additionally or alternatively, the downlink RB 391 can include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. The region 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 the indices in the frequency domain and time domain respectively.

[0095] Additionally or alternatively, in the uplink, in addition to CP-OFDM, a single-carrier frequency-division multiple access (SC-FDMA) access scheme may also be employed, which is also referred to as discrete Fourier transform spread OFDM (DFT-S-OFDM). The 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 area defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is referred to as a resource element (RE) 389 and is uniquely identified by an index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and the time domain, respectively.

[0096] Each element and subcarrier configuration μ in the resource grid 301 (e.g., antenna port p) is referred to as a resource element 389 and is uniquely identified by an index pair (k, l), where k = 0, …, is the index in the frequency domain, and 1 refers to the symbol position in the time domain.

[0097] The resource element (k, l) 389 and subcarrier spacing configuration μ on antenna port p are denoted as (k, l)p,μ. A physical resource block 391 is defined as a continuous set of subcarriers in the frequency domain The physical resource block 391 ranges from 0 to numbered in the frequency domain. The physical resource block number in the frequency domain n The relationship between the PRB and the resource element (k, l) is given by:

[0098] Figure 4 FIG. shows an example of a resource region (e.g., the resource region for the downlink). One or more sets 401 of PRBs 491 (e.g., control resource sets (i.e., CORESETs)) may 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 the 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-continuous and / or time-continuous, the UE 102 may be configured with one or more control resource sets (e.g., CORESETs), and one DCI message may be mapped within one control resource set. In the frequency domain, a PRB 491 is the resource unit size of the DL control channel (which may or may not include DM-RS).

[0099] UE 102 may monitor a candidate set of PDCCHs in one or more control resource sets (e.g., CORESET) on an active DL bandwidth part (BWP) on each active serving cell according to a corresponding search space set. Here, the term "monitor" may imply that UE 102 attempts to decode each DL control channel (e.g., the candidate set of PDCCHs) according to the monitored DCI format. Additionally, a candidate of PDCCH may be a candidate where the DL control channel may be mapped, allocated, and / or transmitted.

[0100] A candidate set of PDCCHs to be monitored by UE 102 may be defined according to a search space set (e.g., also simply referred to as a search space). UE 102 may monitor the candidate set of PDCCHs 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).

[0101] That is, CSS and / or USS may be defined (e.g., configured) in the region of the DL control channel. For example, CSS may be used to transmit DCI to multiple UEs 102. For example, a Type0-PDCCH common search space may be defined for one or more DCI formats having a CRC scrambled by SI-RNTI. Additionally or alternatively, a Type1-PDCCH common search space may be defined for DCI formats having a CRC scrambled by RA-RNTI, temporary C-RNTI, and / or C-RNTI. Additionally or alternatively, a Type3-PDCCH common search space may be defined for DCI formats having a CRC scrambled by C-RNTI and / or CS-RNTI.

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

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

[0104] Additionally or alternatively, gNB 160 may transmit second information for configuring a search space set by 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 the PDCCH monitoring periodicity and / or PDCCH monitoring offset in which UE 102 monitors the PDCCH in the search space set. Additionally or alternatively, the second information may include information for indicating the PDCCH monitoring mode within a time slot. For example, the information for indicating the PDCCH monitoring mode may be used to indicate the first symbol within the time slot for PDCCH monitoring. For example, UE 102 may determine the PDCCH monitoring occasion based on the PDCCH monitoring periodicity, PDCCH monitoring offset, and / or PDCCH monitoring mode within the time slot.

[0105] Additionally or alternatively, the second information may include information for indicating the type of the search space set (e.g., information for indicating whether the search space set is a CSS or a USS). Additionally or alternatively, the second information may include information for indicating one or more DCI formats in which UE 102 monitors 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., PDCCH candidates). Here, the DCI format for monitoring the PDCCH in the CSS may be scrambled by C-RNTI, CS-RNTI, RA-RNTI, temporary C-RNTI, P-RNTI, and / or SI-RNTI.

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

[0107] 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) (e.g., for reception by UE 102) by using an RRC message. Additionally or alternatively, gNB 160 may indicate the active DL BWP by using a DCI format for the downlink. For example, for each DL BWP in the DL BWP set, gNB 160 may configure the subcarrier spacing, cyclic prefix, number of consecutive PRBs 491 (e.g., bandwidth of the PRB), and / or index (e.g., index of the DL BWP, DL BWP ID) of the DL BWP set by using an RRC message.

[0108] Additionally or alternatively, for a serving cell, gNB 160 may configure four UL BWP sets (e.g., up to four UL BWPs, one UL BWP set) (e.g., for transmission by UE 102) by using an RRC message. Additionally or alternatively, gNB 160 may indicate the active UL BWP by 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 PRB), index (e.g., index of the UL BWP) of the UL BWP set by using an RRC message.

[0109] 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 the same based on the configuration for the UL BWP.

[0110] Figure 5 An example of a UL transmission corresponding to a configured grant is shown. As Figure 5 described, the UE 102 may perform UL transmissions (e.g., (re)transmissions on the UL-SCH and / or (re)transmissions on the PUSCH 503a-d). For example, the UE 102 may perform UL transmissions 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 index of the DL BWP is the same as the index of the UL BWP. And, based on detecting a downlink signal (e.g., PDCCH 501a-d) on the DL BWP (e.g., the active DL BWP), the UE 102 performs a UL transmission corresponding to the configured grant on the UL BWP (e.g., the active UL BWP) linked to the DL BWP where the downlink signal is detected.

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

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

[0113] Here, for configured grant type 1 transmission, uplink grant can be provided by RRC (e.g., RRC layer). For example, in the case where UE 102 receives an RRC message including uplink grant (e.g., configuration for configured grant type 1 transmission), UE 102 can store the uplink grant as a configured grant.

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

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

[0116] Here, a DCI format with a CRC scrambled by a CS-RNTI can be used to indicate a 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, the retransmission can be indicated by using an NDI set to "1" (i.e., the NDI field is set to "1", NDI = "1"). Here, as described above, the NDI (i.e., the NDI field) can be included in a DCI format with a CRC scrambled by a CS-RNTI. That is, a PUSCH retransmission can be scheduled by using a PDCCH 501 with an NDI set to "1" and a CRC scrambled by a CS-RNTI (e.g., a DCI format for the uplink).

[0117] 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 can store the uplink grant as a configured grant (e.g., for the serving cell). Additionally, the UE 102 can initialize (if not active) or re-initialize (if already active) the configured grant to start in a symbol according to a parameter (e.g., timeDomainoffset), and re-occur with a parameter (e.g., periodicity). And, after the uplink grant is configured for the configured grant type 1, the UE 102 can sequentially consider the Nth uplink grant occurring associated with a symbol, for which symbol:

[0118] [(SFN * numberOflSlotsPerFrame * numberOfSymbolsPerSlot)+(number of slots in the frame * numberOfSymbolsPerSlot)+number of symbols in the slot]=(timeDomainOffset + N * periodicity) modulo 1024. (1)

[0120] Additionally, for example, for a configured grant type 2 transmission, after the uplink grant is configured for the configured grant type 2, the UE 102 can sequentially consider the Nth uplink grant occurring associated with a symbol, for which symbol:

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

[0123] Here, SFN 开始时间 , time slot 开始时间 and symbol 开始时间 are respectively the SFN (i.e., system frame number), time slot, and symbol when (re)initializing the configured uplink grant. Additionally, for example, the gNB 160 can configure parameters (such as periodicity) by using RRC messages.

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

[0125] For example, the gNB 160 can transmit parameters for the configured grant type 1 transmission by using RRC messages (such as dedicated RRC messages, UE-specific RRC messages). And the UE 102 can perform the configured grant type 1 transmission based on the parameters included in the RRC message. Additionally, the gNB 160 can transmit parameters for the configured grant type 2 transmission by using RRC messages (such as dedicated RRC messages, UE-specific RRC messages). And the UE 102 can perform the configured grant type 2 transmission based on the parameters included in the RRC message.

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

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

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

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

[0130] -powerControlLoopToUse: The closed control loop to be applied. A parameter used to determine the transmission power of PUSCH transmission (e.g., transmission corresponding to the configured grant)

[0131] -p0-PUSCH-Alpha: The index of the P0-PUSCPl-AlphaSet used for this configuration. A parameter used to determine the transmission power of PUSCH transmission (e.g., transmission corresponding to the configured grant)

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

[0133] -nrofPLARQ-Processes: The number of HARQ processes configured for configured grant type 1 transmission and / or configured grant type 2 transmission

[0134] -repK: The number of repetitions to be applied to configured grant type 1 transmission and / or configured grant type 2 transmission

[0135] -repK-RV: The redundancy version sequence to be applied to configured grant type 1 transmission and / or configured grant type 2 transmission

[0136] Additionally or alternatively, for configured grant type 1 transmission, the following parameters can be configured. For example, the mobility parameters can be included in rrc-ConfiguredUplinkGrant in the ConfiguredGrantConfig IE.

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

[0138] -timeDomainAllocation: Indicates the combination of the start symbol and length and the PUSCH mapping type

[0139] -frequencyDomainAllocation: Indicates frequency domain resource allocation

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

[0141] -mcsAndTBS: Indicates the modulation order, target code rate, and / or TB size

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

[0143] -pathlossReferencelndex: A parameter for power control for type 1 transmission of the configured grant (i.e., for this configuration)

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

[0145] For example, gNB 160 can transmit the third information through an RRC message, and this third information is used to configure that the multiple configurations of the configured grant are enabled (e.g., permitted). That is, gNB 160 can transmit the third information through an RRC message, and this third information is used to indicate whether the single configuration of the configured grant or the multiple configurations of the configured grant are used for the transmission corresponding to the configured grant.

[0146] That is, when the single configuration of the configured grant is configured, the single configuration of the configured grant can be used for the transmission corresponding to the configured grant. Additionally, when the multiple configurations of the configured grant are configured, the multiple configurations of the configured grant can be used for the transmission corresponding to the configured grant. Additionally, when the multiple configurations of the configured grant are not configured, the single configuration of the configured grant can be used for the transmission corresponding to the configured grant.

[0147] Here, the third information can be configured according to each serving cell. For example, the third information can be configured for each of the serving cells (e.g., the primary cell and / or the one or more secondary cells). Additionally or alternatively, the third information can be configured according to the UL bandwidth part (UL BWP). For example, the third information can be configured for each UL BWP in the UL BWP (each UL BWP in the UL BWP of the serving cell). Additionally or alternatively, the third information can be configured for configured grant type 1 transmission and / or configured grant type 2 transmission. For example, the third information can generally be configured for configured grant type 1 transmission and configured grant type 2 transmission. Additionally or alternatively, the third information can be separately configured for configured grant type 1 transmission and configured grant type 2 transmission.

[0148] For example, as described below, in the case where the third information is generally configured for configured grant type 1 transmission and configured grant type 2 transmission, the configured index can be configured for ConfiguredGrantConfig. Additionally or alternatively, in the case where the third information is separately configured for configured grant type 1 transmission and configured grant type 2 transmission, the index of the configured index can be configured for ConfiguredGrantConfig and / or the configured index can be configured for rrc-ConfiguredUplinkGrant.

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

[0150] That is, the single configuration of the configured grant can 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 can be configured (and / or activated) for a given BWP (e.g., UL BWP) of a single serving cell.

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

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

[0153] -dataScramblingldentityPUSCH: An identifier for data scrambling (e.g., PUSCH transmission) used to initiate a PUSCH

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

[0155] -PUSCH-PowerControl: A parameter used to determine the transmission power of PUSCH transmission

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

[0157] -pusch-TimeDomainAllocationList: A list of time-domain resource allocations for the timing of DCI formats for uplink and UL transmissions

[0158] -pusch-AggregationFactor: The number of repetitions of UL transmission (e.g., PUSCH transmission)

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

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

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

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

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

[0164] -tpc-Accumulation: If enabled, UE 102 applies the transmission power (TPC) command via accumulation. If not enabled, UE 102 applies the TPC command without accumulation. The parameter indicates the configuration of the TPC command (e.g., whether the TPC command accumulates or not (i.e., the absolute value is used as the TPC command))

[0165] -p0-NominalWithoutGrant: A parameter used to determine the transmission power of a transmission corresponding to a configured grant

[0166] -p0-Alpha: A parameter used to determine the transmission power of PUSCH transmission

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

[0168] For example, in the case where the multiple configurations of the configured grant are configured, the multiple configurations of PUSCH503 can be configured. That is, when gNB 160 configures the multiple configurations of the configured grant, gNB 160 can always configure the multiple configurations of PUSCH503. For example, in the case where the single configuration of the configured grant is configured, the single configuration of PUSCH 503 can be configured. That is, when gNB 160 configures the single configuration of the configured grant, gNB 160 can always configure the single configuration of PUSCH 503.

[0169] Here, when the multiple configured authorizations are configured, the configured index can be configured. For example, the configured index can be included in ConfiguredGrantConfig (e.g., or ConfiguredGrantConfig IE). Additionally or alternatively, the configured index can be included in rrc-ConfiguredUplinkGrant (e.g., in ConfiguredGrantConfig IE). Additionally or alternatively, the configured index can be included in PUSCH-config.

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

[0171] That is, each configuration among the multiple configured authorizations can be identified by using the configured index (e.g., the index of the configured grant configuration). Additionally, each configuration among the multiple configurations of PUSCH 503 can be identified by using the configured index (e.g., the index of the PUSCH configuration). Additionally, the link between each configuration among the multiple configured authorizations and each configuration among the multiple configurations of PUSCH 503 (e.g., the correspondence between each configuration among the multiple configured authorizations and each configuration among the multiple configurations of PUSCH 503) can be identified by using the configured index.

[0172] For example, when the multiple configured authorizations (e.g., four configured authorizations) are configured for configured grant transmission, the 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") can be configured as the configured index for each configuration among the multiple configured authorizations.

[0173] For example, the index "0" can be configured for the first configuration among the multiple configured authorizations (e.g., as configuration index #0). Additionally, the index "1" can be configured for the second configuration among the multiple configured authorizations (e.g., as configuration index #1). Additionally, the index "2" can be configured for the third configuration among the multiple configured authorizations (e.g., as configuration index #2). Additionally, the index "1" can be configured for the fourth configuration among the multiple configured authorizations (e.g., as configuration index #3).

[0174] For example, when the multiple configurations of PUSCH (e.g., four configurations of PUSCH) are configured, the index "0", the index "1", the index "2", and / or the index "3" can be configured as the configuration index for each of the multiple configurations of PUSCH 503. That is, when the multiple configurations of PUSCH 503 (e.g., four configurations of PUSCH 503) are configured, the index "0", the index "1", the index "2", and / or the index "3" can be configured as the configuration index for each of the multiple configurations of PUSCH 503.

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

[0176] And, when the configuration index of the configured grant is the same as the configuration index of PUSCH 503, the configuration of the configured grant can be linked with the configuration of PUSCH 503. That is, when the configuration index of the configured grant is the same as the configuration index of PUSCH 503, the configuration of the configured grant and the configuration of PUSCH 503 can be linked together.

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

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

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

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

[0181] Here, the authorized configuration of the configuration other than the configuration with index "X" may include a part of the parameters included in PUSCH-config. And, the configuration with index "X" may not include a part of the parameters included in PUSCH-config.

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

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

[0184] That is, when the plurality of configurations of the authorized configuration are configured, a part of the parameters (e.g., the parameters described as included in PUSCH-config) may be configured in the ConfiguredGrantConfig IE (e.g., ConfiguredGrantConfig and / or rrc-ConfiguredUplinkGrant).

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

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

[0187] For example, the configuration of PUSCH 503 linked to the authorized configuration of a configuration other than the configuration with index "X" may include the scaling of dataScramblingIdentityPUSCH, txConfig, tpc-Accumulation, and / or UCI-OnPUSCH. Also, the configuration of PUSCH 503 linked to the authorized configuration 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.

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

[0189] Here, when the single configuration of configured grant is configured (i.e., when the multiple configurations of configured grant are not configured), the UE 102 can perform the transmission corresponding to the configured grant based on the single configuration of configured grant.

[0190] For example, for the configured grant type 1 transmission, when the configuration of the configured grant with index "1" is configured, the UE 102 can perform the 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 the configured grant type 1 transmission, when the single configuration of configured grant is configured, the UE 102 can perform the transmission corresponding to the configured grant based on the configuration with index "X". That is, when the single configuration of configured grant is configured, the configuration with index "X" can always be applied to the transmission corresponding to the configured grant.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0204] Here, the plurality of configurations of PUSCH 503 may be activated simultaneously (e.g., at the same time) by using the single DCI format with NDI set to "1". That is, the single DCI format may include information for indicating one or more indexes of the configuration of PUSCH 503 to be applied to the retransmission. For example, in the case where the plurality of configurations are configured and the configuration of PUSCH 503 with index "1" and the configuration of PUSCH 503 with index "3" are indicated, UE102 may perform the retransmission based on the configuration of PUSCH 503 with index "1" and the configuration of PUSCH 503 with index "3".

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

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

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

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

[0209] That is, for (re)transmission, when applying the authorized configuration with index "0" (i.e., when applying a part of the parameters of the authorized configuration with index "0"), the configuration of PUSCH 503 with index "0" (i.e., a part of the parameters of the configuration of PUSCH 503 with index "0") can be applied. Additionally, for (re)transmission, when applying the authorized configuration with index "1" (i.e., when applying a part of the parameters of the authorized configuration with index "1"), the configuration of PUSCH 503 with index "1" (i.e., a part of the parameters of the configuration of PUSCH 503 with index "1") can be applied. Additionally, for (re)transmission, when applying the authorized configuration with index "2" (i.e., when applying a part of the parameters of the authorized configuration with index "2"), the configuration of PUSCH 503 with index "2" (i.e., a part of the parameters of the configuration of PUSCH 503 with index "2") can be applied. Additionally, for (re)transmission, when applying the authorized configuration with index "3" (i.e., when applying a part of the parameters of the authorized configuration with index "3"), the configuration of PUSCH 503 with index "3" (i.e., a part of the parameters of the configuration of PUSCH 503 with index "3") can be applied.

[0210] Additionally, for (re)transmission, when applying the authorized configuration with index "X" (i.e., when applying a part of the parameters of the authorized configuration with index "X"), the configuration of PUSCH 503 linked to the authorization of the configuration with index "X" (i.e., a part of the parameters of the configuration of PUSCH 503 linked to the configuration with index "X") can be applied.

[0211] Additionally or alternatively, for (re)transmission, in the case of applying the configuration of PUSCH 503 with index "0" (i.e., in the case of applying a part of the parameters of the configuration of PUSCH 503 with index "0"), the configuration of the grant with index "0" (i.e., a part of the parameters of the grant with index "0") can be applied. Additionally, for (re)transmission, in the case of applying the configuration of PUSCH 503 with index "1" (i.e., in the case of applying a part of the parameters of the configuration of PUSCH 503 with index "1"), the configuration of the grant with index "1" (i.e., a part of the parameters of the grant with index "1") can be applied. Additionally, for (re)transmission, in the case of applying the configuration of PUSCH 503 with index "2" (i.e., in the case of applying a part of the parameters of the configuration of PUSCH 503 with index "2"), the configuration of the grant with index "2" (i.e., a part of the parameters of the grant with index "2") can be applied. Additionally, for (re)transmission, in the case of applying the configuration of PUSCH 503 with index "3" (i.e., in the case of applying a part of the parameters of the configuration of PUSCH 503 with index "3"), the configuration of the grant with index "3" (i.e., a part of the parameters of the grant with index "3") can be applied.

[0212] Additionally, for (re)transmission, in the case of applying the configuration of PUSCH 503 linked to the configuration with index "X" (i.e., in the case of applying a part of the parameters of the configuration of PUSCH 503 linked to the configuration with index "X"), the configuration with index "X" (i.e., a part of the parameters of the configuration with index "X") can be applied.

[0213] Additionally or alternatively, for simplicity of description, in some specific embodiments, it can be assumed that this single configuration of the grant of the configuration described herein and / or this single configuration of PUSCH 503 is included in a single configuration "A". Additionally, for simplicity of description, in some specific embodiments, it can be assumed that these multiple configurations of the grant of the configuration described herein and / or these multiple configurations of PUSCH 503 are included in multiple configurations "B".

[0214] As described above, the information indicating the index of the configuration of the grant can 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 the information indicating the index of the configuration of the grant.

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

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

[0217] Additionally or alternatively, in the case where DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to "0") is detected, UE 102 performs a transmission corresponding to the configured authorization based on the single configuration "A" (e.g., as described above). That is, even if the plurality of configured authorizations are configured, in the case where DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to "0") is detected, UE 102 may perform a transmission corresponding to the configured authorization based on the single configuration "A".

[0218] For example, in the case where DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to "0") is detected, UE 102 may perform a transmission corresponding to the configured authorization based on the configuration with index "X" and / or the configuration of PUSCH503 linked to the configuration with index "X".

[0219] Additionally or alternatively, in the case where DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to "1") is detected, UE 102 performs a retransmission (e.g., retransmission of the TB) based on the single configuration "A" (e.g., as described above). That is, even if the plurality of configured authorizations are configured, in the case where DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to "1") is detected, UE 102 may perform a retransmission based on the single configuration "A".

[0220] For example, in the case where DCI format 0_0 with a CRC scrambled by CS-RNTI (e.g., NDI set to "1") is detected, UE 102 may perform a retransmission based on the configuration with index "X" and / or the configuration of PUSCH503 linked to the configuration with index "X".

[0221] Additionally or alternatively, in the 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 the CSS (i.e., CSS set), the UE 102 performs a transmission corresponding to the configured grant based on this 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 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 (i.e., CSS set), the UE 102 can perform a transmission corresponding to the configured grant based on this single configuration "A". That is, in the 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 the USS (i.e., USS set), the UE 102 performs a transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).

[0222] For example, in the 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 the CSS (i.e., CSS set), the UE 102 can perform a transmission corresponding to the configured grant based on the configuration with index "X" and / or the configuration of the PUSCH 503 linked to the configuration with index "X".

[0223] Additionally or alternatively, in the 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 the CSS (i.e., CSS set), the UE 102 performs a retransmission (e.g., retransmission of the TB) based on this 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 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 (i.e., CSS set), the UE 102 can perform a retransmission based on this single configuration "A".

[0224] For example, 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 a CS-RNTI is detected in CSS (i.e., the CSS set), the UE 102 may perform a retransmission based on the configuration with index "X" and / or the configuration of the PUSCH 503 linked to the configuration with index "X".

[0225] Additionally or alternatively, 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 a CS-RNTI is detected in CORESET#0, the UE 102 performs a transmission corresponding to the configured grant based on this 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") (e.g., DCI format 0_0 and / or DCI format 0_1 of the DCI format) with a CRC scrambled by a CS-RNTI is detected in CORESET#0, the UE 102 may perform a transmission corresponding to the configured grant based on this single configuration "A". 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 a CS-RNTI is detected in a CORESET other than CORESET#0, the UE 102 performs a transmission corresponding to the configured grant based on the multiple configurations "B" (e.g., as described above).

[0226] For example, 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 a CS-RNTI is detected in CORESET#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 to the configuration with index "X".

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

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

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

[0230] For example, in the 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 search space set #0, UE 102 may perform a transmission corresponding to the configured grant based on the configuration having index "X" and / or the configuration of PUSCH 503 linked to the configuration having index "X".

[0231] Additionally or alternatively, in the 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 search space set #0, UE 102 performs a retransmission (e.g., retransmission of a TB) based on this 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 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 search space set #0, UE 102 may perform a retransmission based on this single configuration "A".

[0232] For example, in the 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 search space set #0, UE 102 may perform a retransmission based on the configuration having index "X" and / or the configuration of PUSCH 503 linked to the configuration having index "X".

[0233] In addition, grouping of the configurations of the configured grant may be supported. For example, gNB 160 may transmit, by using an RRC message, information for configuring the correspondence between the configured grant configuration group (e.g., the configured grant configuration group having an index) and the configuration of the configured grant (e.g., the configuration of the configured grant having an index). For example, the configuration of the configured grant having index "0" may correspond to the configured grant configuration group having index "0". In addition, the configuration of the configured grant having index "1" may correspond to the configured grant configuration group having index "1". In addition, the configuration of the configured grant having index "2" may correspond to the configured grant configuration group having index "0". That is, the configuration of the configured grant having index "0" and the configuration of the configured grant having index "2" may belong to the same group (i.e., the configured grant configuration group "0"). In addition, the configuration of the configured grant having index "4" may correspond to the configured grant configuration group having index "1". That is, the configuration of the configured grant having index "1" and the configuration of the configured grant having index "4" may belong to the same group (i.e., the configured grant configuration group "1").

[0234] In addition, a group for configuring PUSCH can be supported. For example, gNB 160 can transmit information for 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) by using an RRC message. For example, the configuration of PUSCH with index "0" can correspond to the PUSCH configuration group with index "1". In addition, the configuration of PUSCH with index "1" can correspond to the PUSCH configuration group with index "0". In addition, the configuration of PUSCH with index "2" can correspond to the PUSCH configuration group with index "0". That is, the configuration of PUSCH with index "1" and the configuration of PUSCH with index "2" can belong to the same group (i.e., PUSCH configuration group "0"). In addition, the configuration of PUSCH with index "3" can correspond to the PUSCH configuration group with index "1". That is, the configuration of PUSCH with index "0" and the configuration of PUSCH with index "3" can belong to the same group (i.e., PUSCH configuration group "1").

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

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

[0237] Figure 6An example of a configured grant confirmation medium access control (MAC) control element (CE) 601 is shown. As described above, for configured grant type 2, the gNB 160 may transmit a DCI format (e.g., a second DCI and / or PDCCH) for indicating the activation of a configured grant (e.g., a configured grant corresponding to the configuration of the configured grant with an index). For example, based on receiving a DCI format (e.g., a second DCI and / or PDCCH) for indicating the activation of a configured grant (e.g., a configured grant corresponding to the configuration of the configured grant with index "2"), the UE 102 may perform a transmission on the PUSCH (e.g., perform a transmission on the PUSCH based on the parameters configured by the configuration of the configured grant with index "2"). Additionally, based on receiving a DCI format for indicating the activation of a configured grant (e.g., a configured grant corresponding to the configuration of the configured grant with index "2" and a configured grant corresponding to the configuration of the configured grant with index "3"), the UE 102 may perform a transmission on the PUSCH (e.g., perform a transmission on the PUSCH based on the parameters configured by the configuration of the configured grant with index "2" and / or the parameters configured by the configuration of the configured grant with index "3").

[0238] Additionally or alternatively, for configured grant type 2, the gNB 160 may transmit a DCI format (e.g., a first DCI and / or PDCCH) for indicating the deactivation of a configured grant (e.g., a configured grant corresponding to the configuration of the configured grant with an index). For example, based on receiving a DCI format (e.g., a first DCI and / or PDCCH) for indicating the deactivation of a configured grant (e.g., a configured grant corresponding to the configuration of the configured grant with index "2"), the UE 102 may clear the configured grant (e.g., clear the configured grant corresponding to the configuration of the configured grant with index "2"). Additionally, based on receiving a DCI format for indicating the deactivation of a configured grant (e.g., a configured grant corresponding to the configuration of the configured grant with index "2" and a configured grant corresponding to the configuration of the configured grant with index "3"), the UE 102 may clear the configured grant (e.g., clear the configured grant corresponding to the configuration of the configured grant with index "2" and the configured grant corresponding to the configuration of the configured grant with index "3"). That is, based on receiving a DCI format for the deactivation of a configured grant corresponding to the configuration of the configured grant with an index, the UE 102 may clear the corresponding configured grant (e.g., only clear the corresponding configured grant), and maintain the storage of the configured grant that does not correspond to the configuration of the configured grant with an index.

[0239] That is, for the configured grant type 2, the UE 102 may clear the configured grant (e.g., the configured grant corresponding to the deactivated configured grant). Here, the UE 102 may clear the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. That is, based on receiving the DCI format for deactivating the configured grant, the configured grant confirmation MAC CE 601 may be triggered. For example, the UE 102 may trigger the configured grant confirmation MAC CE 601 and clear the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. Here, when triggering the configured grant confirmation MAC CE 601, the UE 102 may transmit the configured grant confirmation MAC CE 601. For example, when the configured grant confirmation MAC CE 601 is triggered and not cancelled, and when UL resources are allocated for a new transmission, the configured grant confirmation MAC CE 601 may be transmitted.

[0240] In addition, as described above, the configuration of the configured grant may be linked to the configuration of the PUSCH. And the UE 102 may clear the configuration of the PUSCH linked to the configuration of the deactivated configured grant. Here, the UE 102 may clear the configuration of the PUSCH linked to the configuration of the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. That is, based on receiving the DCI format for deactivating the configured grant, the configured grant confirmation MAC CE 601 may be triggered and / or the configuration of the PUSCH linked to the configuration of the configured grant may be cleared. For example, the UE 102 may trigger the configured grant confirmation MAC CE 601 and clear the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601. Additionally, the UE 102 may trigger the configured grant confirmation MAC CE 601 and clear the configuration of the PUSCH linked to the configuration of the configured grant immediately after the first transmission of the configured grant confirmation MAC CE 601.

[0241] Here, the configured grant confirmation MAC CE 601 may be identified by using a MAC sub-header having an LCID (e.g., logical channel identifier) (e.g., the value (e.g., index) of the LCID of the UL-SCH) (e.g., 55). Additionally, the size (e.g., length) of the configured grant confirmation MAC CE 601 may be defined (e.g., specified) as fixed. For example, the size (e.g., length) of the configured grant confirmation MAC CE 601 may be defined as 16 bits. Additionally or alternatively, the size (e.g., length) of the configured grant confirmation MAC CE 601 may be defined (e.g., specified) as 24 bits.

[0242] For example, for the configured grant confirmation MAC CE 601, a field of the serving cell identifier (e.g., serving cell ID) 603 may be defined. For example, the field of the serving cell ID 603 may be used to indicate the index of the serving cell to which the configured grant confirmation MAC CE 601 is applied (e.g., the index of the primary cell (e.g., "000" (i.e., zero)) and / or the index of the secondary cell (e.g., a value other than "000")). For example, the size (e.g., length) of the field of the serving cell ID 603 may be defined as 5 bits.

[0243] Additionally or alternatively, for the configured grant confirmation MAC CE 601, a field of the bandwidth part identifier (e.g., BWP ID) 605 may be defined. For example, the field of the BWP ID 605 may be used to indicate the index of the UL BWP to which the configured grant confirmation MAC CE 601 is applied. For example, the field of the BWP ID 605 may be used to indicate the index of the UL BWP to which the configured grant confirmation MAC CE 601 is applied, as the code point of the BWP indicator field included in the DCI format. For example, the size (e.g., length) of the field of the BWP ID 605 may be defined (e.g., specified) as 2 bits.

[0244] Additionally or alternatively, for the configured grant confirmation MAC CE 601, a field (e.g., S i (e.g., the maximum number of i = 7 (e.g., 0 to 7) or 15 (e.g., 0 to 15)). That is, this field (e.g., S i ) may be used to indicate the activation status and / or deactivation status of the configured grant configuration within the plurality of active configurations (e.g., the plurality of active configurations configured by the gNB 160 by using the RRC message). For example, the field (e.g., S i ) set to the value "1" may be used to indicate that the status of the corresponding configuration of the configured grant is active (e.g., activated). Additionally, the field (e.g., S i ) set to the value "0" may be used to indicate that the status of the corresponding configuration of the configured grant is deactivated (e.g., deactivated).

[0245] Additionally or alternatively, the size of the field (e.g., S i ) may be determined based on the number of configured grants. That is, the size of the field (e.g., S i) size. For example, when the configured number of configured authorizations is configured to "4" (e.g., as the number of multiple active configurations), the field (e.g., S i) size can be "4" (e.g., S0, S1, S2, and S3 can be used to indicate the active state and / or deactivation state). Additionally, when the configured number of configured authorizations is configured to "10" (e.g., as the number of authorized configurations of multiple configurations), the field (e.g., S i ) size can be "10" (e.g., S0, S1, S2, S3, S4, S5, S6, S7, S8, and S9 can be used to indicate the active state and / or deactivation state).

[0246] Additionally or alternatively, a field (e.g., S i ) set to a value (e.g., "0" or "1") used to indicate the active state and / or deactivation state can be defined (e.g., specified) in ascending order (e.g., or in descending order) based on the index of the configured authorization configuration. For example, S0 can refer to the authorized configuration of the configuration with the lowest index (e.g., the authorized configuration of the configuration with the lowest index within the multiple active configurations (e.g., configured by using the RRC message). Additionally, S1 can refer to the authorized configuration of the configuration with the second lowest index (e.g., the authorized configuration of the configuration with the second lowest index within the multiple active configurations (e.g., configured by using the RRC message). Additionally, S2 can refer to the authorized configuration of the configuration with the third lowest index (e.g., the authorized configuration of the configuration with the third lowest index within the multiple active configurations (e.g., configured by using the RRC message).

[0247] For example, when the authorized configuration of the configuration with index "1", the authorized configuration of the configuration with index "8", and the authorized configuration of the configuration with index "3" are configured (e.g., as the multiple active configurations), S0 can refer to the active state and / or deactivation state of the authorized configuration of the configuration with index "1", S1 can refer to the active state and / or deactivation state of the authorized configuration of the configuration with index "3", and S2 can refer to the active state and / or deactivation state of the authorized configuration of the configuration with index "8".

[0248] That is, UE 102 can determine the field (e.g., S i ) and the configured authorization configuration (e.g., the field corresponding to the configured authorization configuration (e.g., S i )) based on the index of the configured authorization configuration. And, based on the index of the configured authorization configuration, UE 102 can set (e.g., map) the value used to indicate the active state or deactivation state to the field (e.g., the determined field "S i ").

[0249] As described above, in the systems and methods disclosed herein, the configured authorization configuration can be replaced by a configured authorization configuration group. Here, the configured authorization configuration group can include the one or more configured authorization configurations. As described above, gNB 160 can transmit information for configuring the correspondence between the configured authorization configuration group and the one or more configured authorization configurations by using an RRC message.

[0250] That is, for the configured grant confirmation MAC CE 601, a field (e.g., S i (e.g., the maximum number of i = 7 (e.g., 0 to 7) or 15 (e.g., 0 to 15)). That is, this field (e.g., S i ) can be used to indicate the activation state and / or deactivation state of the configured authorization configuration group within the plurality of active configurations (e.g., the plurality of active configurations configured by gNB 160 by using an RRC message). For example, a field (e.g., S i ) set to the value "1" can be used to indicate that the state of the corresponding configured authorization configuration group is active (e.g., activated). Additionally, a field (e.g., S i ) set to the value "0" can be used to indicate that the state of the corresponding configured authorization configuration group is deactivated (e.g., deactivated).

[0251] Additionally or alternatively, the size of a field (e.g., S i ) can be determined based on the number of configured authorization configuration groups. That is, the size of a field (e.g., S i ) can be determined based on the number of configured authorization configuration groups within the plurality of active configurations (e.g., configured by using an RRC message). For example, when the number of configured authorization configuration groups is configured to be "4" (e.g., as the number of the plurality of active configurations), the size of the field (e.g., S i) can be "4" (e.g., S0, S1, S2, and S3 can be used to indicate the activation state and / or deactivation state). Additionally, when the number of configured authorization configuration groups is configured to be "10" (e.g., as the number of the plurality of configured authorizations), the size of the field (e.g., S i ) can be "10" (e.g., S0, S1, S2, S3, S4, S5, S6, S7, S8, and S9 can be used to indicate the activation state and / or deactivation state).

[0252] Additionally or alternatively, a field (e.g., S i) It can be defined (e.g., specified) in ascending order (or in descending order, for example) based on the index of the configured authorization configuration group. For example, S0 can refer to the configured authorization configuration group with the lowest index (e.g., the configured authorization configuration group with the lowest index among the multiple active configurations (e.g., configured by using an RRC message)). Additionally, S1 can refer to the configured authorization configuration group with the second lowest index (e.g., the configured authorization configuration group with the second lowest index among the multiple active configurations (e.g., configured by using an RRC message)). Additionally, S2 can refer to the configured authorization configuration group with the third lowest index (e.g., the configured authorization configuration group with the third lowest index among the multiple active configurations (e.g., configured by using an RRC message)).

[0253] For example, in the case where the configured authorization configuration group with index "1", the configured authorization configuration group with index "8", and the configured authorization configuration group with index "3" are configured, S0 can refer to the activation state and / or deactivation state of the configured authorization configuration group with index "1", S1 can refer to the activation state and / or deactivation state of the configured authorization configuration group with index "3", and S2 can refer to the activation state and / or deactivation state of the configured authorization configuration group with index "8". Here, for example, the configured authorization configuration group with index "1" can include the configured authorization of the configuration with index "1" and the configured authorization of the configuration with index "8". Additionally, the configured authorization configuration group with index "8" can include the configured authorization of the configuration with index "6", the configured authorization of the configuration with index "10", and the configured authorization of the configuration with index "14". Additionally, the configured authorization configuration group with index "3" can include the configured authorization of the configuration with index "5".

[0254] That is, UE 102 can determine a field (e.g., S i ) and the corresponding relationship between the configured authorization configuration group (e.g., the field corresponding to the configured authorization configuration group (e.g., S i )) based on the index of the configured authorization configuration group. And based on the index of the configured authorization configuration group, UE 102 can set (e.g., map) the value used to indicate the activation state or deactivation state to the field (e.g., the determined field S “i”).

[0255] Additionally or alternatively, for the configured authorization confirmation MAC CE 601, a field for reserved bits (e.g., “R”) can be defined. For example, the field of the reserved bits can be set to "0" (i.e., zero).

[0256] To support multiple configurations of configured authorization, some RRC parameters can be introduced.

[0257] An RRC parameter (e.g., UL-Configuredgrantconfig-index) may be introduced to indicate the index of the UL-configured grant configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-index) may be included in each RRC configuration of the configured grant (e.g., ConfiguredGrantConfig IE). The value of the RRC parameter (e.g., UL-Configuredgrantconfig-index) may be 0, 1, 2, …, maxNrofConfiguredgrantconfig-2 or maxNrofConfiguredgrantconfig-1. maxNrofConfiguredgrantconfig is the maximum number of CG configurations, which may be 12.

[0258] RRC parameters (e.g., UL-Configuredgrantconfig-ToAddModList) can be introduced to configure more than one UL-configured grant configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-ToAddModList) can be a list or sequence of elements. The elements here can be configured grant configurations (e.g., ConfiguredGrantConfig) or equivalent mappings. The elements of the list or sequence can contain an identity (INTEGER) (e.g., ElementId) that explicitly identifies the element when adding, modifying, and removing. Here, ElementId can be the index of the UL-configured grant configuration (e.g., UL-Configuredgrantconfig-index). For each element (e.g., ConfiguredGrantConfig) in the RRC parameter (e.g., UL-ConfiguredGrantConfig-ToAddModList), if the current UE configuration includes an element (e.g., ConfiguredGrantConfig) with a given ElementId (e.g., UL-Configuredgrantconfig-index), the UE modifies the configured element (e.g., ConfiguredGrantConfig) according to the received element, otherwise the UE adds the received element (e.g., ConfiguredGrantConfig) to the UE configuration. That is, if the UE receives a CG configuration corresponding to the index and the list in the UE configuration has a CG configuration corresponding to the index, the UE updates the CG configuration according to the received CG configuration. If the UE receives a CG configuration corresponding to the index and the list in the UE configuration does not have a CG configuration corresponding to the index, the UE adds the CG configuration to the list and / or its configuration according to the received CG configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-ToAddModList) can be from 1 to maxNrofConfiguredgrantconfig of ConfiguredGrantConfig (e.g., 12).

[0259] RRC parameters (e.g., UL-Configuredgrantconfig-ToReleaseList) can be introduced to release more than one UL-configured grant configuration. The RRC parameter (e.g., UL-Configuredgrantconfig-ToReleaseList) can be a list or sequence of ElementIds (e.g., UL-Configuredgrantconfig-index). For each ElementId (e.g., UL-ConfiguredGrantConfig-index) in the RRC parameter (e.g., UL-ConfiguredGrantConfig-ToReleaseList), if the current UE configuration includes an element (UL-configured grant configuration, e.g., ConfiguredGrantConfig) with the given ElementId (e.g., UL-Configuredgrantconfig-index), the UE releases the element (UL-configured grant configuration, e.g., ConfiguredGrantConfig) from the current UE configuration. That is, if the list includes a configured grant configuration index and the current UE configuration includes the configured grant configuration corresponding to that index, the UE releases the configured grant configuration corresponding to that index.

[0260] To support the joint release and / or individual release of multiple configured grant configurations, the DCI field (e.g., DCI format 0_0, DCI format 0_1, and / or DCI format 0_2) in the release DCI and / or the higher layer configurable table (e.g., CG configuration release table) and / or the fixed / default table can be used to indicate which CG configuration to release. That is, M (e.g., M <= 4) bits in the release DCI are used to indicate which CG configuration to release, where the association between each state indicated by this indication and the CG configuration depends on the fact that 2^M states are higher layer configurable, and each of these states can be mapped to a single or multiple CG configurations to be released. In the case of a state without a higher layer configuration, individual release is used, where the release corresponds to the CG configuration index indicated by this indication.

[0261] For example, the value m of the DCI field (e.g., CG configuration index) in the DCI can provide the row index m + 1 to the allocation table. The determination of the table used can be defined as follows. The index row defines which CG configuration to release.

[0262] The table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList) can be configured at a higher layer. The table is UE-specific (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config) and / or commonly configured (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon). The table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList) can be a list / sequence of CG configuration index sets (e.g., UL-Type2Configuredgrantconfig-ReleaseState). Each CG configuration index set can include one or more CG configuration indexes that can be released. The CG configuration index set can be empty, which means that no CG configuration will be released. An example of the RRC-configured table is shown in List 1. The maximum number of entries in the table / sequence / list (e.g., maxNrofUL-CG-ReleaseState) can be 16 or depend on the number of bits in the DCI field (e.g., CG configuration index).

[0263]

[0264] List 1

[0265] The table can be fixed in this specification. That is, one or more default tables can be applied to the combined and / or individual release of multiple CG configurations. Some examples shown are Table 1, Table 2, and Table 3.

[0266] Row index CG configuration index set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 9 8 10 9 11 10 12 11

[0267] Table 1

[0268] Row index CG configuration index set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 9 8 10 9 11 10 12 11 13 0、1、2 14 3、4、5 15 6、7、8 16 9、10、11

[0269] Table 2

[0270] Row index CG configuration index set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 9 8 10 9 11 10 12 11 13 0、1、2、3 14 4、5、6、7 15 8、9、10、11 16 0、1、2、3、4、5、6、7、8、9、10、11

[0271] Table 3

[0272] Here, more than one table for CG configuration release can be defined and / or configured. In the case of more than one table (e.g., a CG configuration release table, a table including RRC configurations, and / or a default table), the determination of the table to be used for CG configuration release can depend on the DCI format for releasing DCI, the RRC configuration (e.g., whether a UE-specific table and / or a commonly configured table is configured), the PDCCH search space where the UE detects the release DCI, and / or the CORESET where the UE detects the release DCI.

[0273] For example, if there is no RRC-configured table (e.g., if the parameter for indicating the table (e.g., no value of the parameter) is not configured to indicate the table), the default table (e.g., Table 1, Table 2, Table 3, or any table specified in this specification) can be applied to joint / individual CG configuration release. In another example, if there is no RRC-configured table, joint release of multiple CG configurations may not be supported. That is, only individual release is supported (e.g., by using a single DCI format for releasing DCI at a certain timing to release only one CG configuration). Each value in the DCI field (e.g., CG configuration index) can have a one-to-one mapping with the CG configuration that can be released. For example, the DCI field (e.g., CG configuration index) value m of the DCI can indicate that the CG configuration with index m can be released.

[0274] For example, if a UE-specific RRC table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config) is configured for the UE and the UE detects the release DCI (e.g., DCI format 0_2, DCI format 0_1, and / or DCI format 0_0) in the UE-specific search space, the UE-specific RRC table (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config) can be applied to (e.g., always applied to) joint / individual CG configuration release (e.g., regardless of whether other tables (e.g., UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon and / or any default table) can be configured and / or provided).

[0275] For example, if a common RRC table is configured (e.g., the UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon) (e.g., there is no UE-specific RRC table for the UE (e.g., the UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-Config)), the common RRC table (e.g., the UL-Type2Configuredgrantconfig-ReleaseStateList in pusch-ConfigCommon) can be applied to joint / individual CG configuration release. For example, if both a common RRC table and a UE-specific RRC table are configured, the UE can apply the UE-specific RRC table to be used for CG configuration release. For example, if both a common RRC table and a UE-specific RRC table are configured for the UE, the UE-specific RRC table (e.g., the configuration of the UE-specific RRC table) can overwrite the common RRC table (e.g., the configuration of the common RRC table).

[0276] For example, if the UE detects a release DCI (e.g., DCI format 0_2, DCI format 0_1, and / or DCI format 0_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), the default table (e.g., Table 1, Table 2, Table 3, or any table specified in the specification (e.g., defined by this specification)) can be applied to joint / individual CG configuration release. In another example, if the UE detects a release DCI (e.g., DCI format 0_2, DCI format 0_1, and / or DCI format 0_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), the joint release of multiple CG configurations may not be supported. That is, only individual release is supported. Each value in the DCI field (e.g., the CG configuration index) can have a one-to-one mapping with the CG configuration that can be released. For example, the DCI field (e.g., the CG configuration index) value m of the DCI can indicate that the CG configuration with index m can be released.

[0277] Another example is shown in Table 4. As shown in Table 4, the UE can determine the table to be applied to the CG configuration release (e.g., in the default table, the common RRC table, and / or the UE-specific RRC table). That is, as described above, the UE can determine the table (e.g., in the default table, the common RRC table, and / or the UE-specific RRC table) based on the DCI format for the DCI release, the RRC configuration (e.g., whether the UE-specific RRC table is configured and / or whether the common RRC table is the configured table), the PDCCH search space in which the UE detects the DCI format for the DCI release, and / or the CORESET in which the UE monitors the DCI format for the DCI release (e.g., the index of the CORESET).

[0278]

[0279] Table 4

[0280] If the DCI for release is a fallback DCI (e.g., DCI format 0_0), there may be no DCI field (e.g., CG configuration index) to indicate which CG configuration to release, and some fallback behaviors can be described here. For example, if the UE detects DCI format 0_0 for CG configuration release, the UE may release all CG configurations (e.g., all type 2 CG configurations). In another example, if the UE detects DCI format 0_0 for CG configuration release, the UE may release a specific configuration (e.g., a specific type 2 CG configuration) and / or the default configuration (e.g., the default type 2 CG configuration). For example, if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with a predetermined index (e.g., the CG configuration with index "0" (e.g., as a specific type 2 CG configuration and / or the default type 2 CG configuration)). Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with the lowest index (e.g., the minimum index). For example, in the case where a CG configuration with index "1", a CG configuration with index "3", and a CG configuration with index "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with "1". Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with the highest index (e.g., the maximum index). For example, in the case where a CG configuration with index "1", a CG configuration with index "3", and a CG configuration with index "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release, the UE may release the CG configuration with "5". Here, the specific configuration and / or the default configuration can be defined by this specification and the known information between the gNB and the UE. That is, for the detection of DCI format 0_0 for CG configuration release, the UE can determine which CG configuration to release based on the index for the CG configuration (e.g., configured by the gNB). In another example, if multiple CG configurations are configured, it may not be desirable for the UE to receive DCI format 0_0 for CG configuration release.

[0281] Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release all CG configurations (e.g., all type 2 CG configurations). In another example, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release a specific configuration (e.g., a specific type 2 CG configuration) and / or a default configuration (e.g., a default type 2 CG configuration). For example, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release a CG configuration with a predetermined index (e.g., a CG configuration with index "0" (e.g., as a specific type 2 CG configuration and / or a default type 2 CG configuration)). Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with the lowest index (e.g., the minimum index). For example, in the case where a CG configuration with index "1", a CG configuration with index "3", and a CG configuration with index "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with "1". Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with the highest index (e.g., the maximum index). For example, in the case where a CG configuration with index "1", a CG configuration with index "3", and a CG configuration with index "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS, the UE may release the CG configuration with "5". That is, for the detection of DCI format 0_0 for CG configuration release in the CSS, the UE may determine which CG configuration to release based on the index for the CG configuration (e.g., configured by the gNB).

[0282] Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release all CG configurations (e.g., all type 2 CG configurations). In another example, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release a specific configuration (e.g., a specific type 2 CG configuration) and / or a default configuration (e.g., a default type 2 CG configuration). For example, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release a CG configuration with a predetermined index (e.g., a CG configuration with index "0" (e.g., as a specific type 2 CG configuration and / or a default type 2 CG configuration)). Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with the lowest index (e.g., the minimum index). For example, in the case where a CG configuration with index "1", a CG configuration with index "3", and a CG configuration with index "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with "1". Additionally or alternatively, if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with the highest index (e.g., the maximum index). For example, in the case where a CG configuration with index "1", a CG configuration with index "3", and a CG configuration with index "5" are configured, and if the UE detects DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the CG configuration with "5". That is, for the detection of DCI format 0_0 for CG configuration release in the CSS associated with CORESET#0, the UE may determine which CG configuration to release based on the index for the CG configuration (e.g., configured by the gNB).

[0283] Semi-persistent scheduling (SPS) is configured by RRC for each serving cell and each BWP. Activation and deactivation of DL SPS can be independent between serving cells. For DL SPS, DL allocations are provided by the PDCCH (e.g., DCI format 1_0, DCI format 1_1, and / or DCI format 1_2), and are stored or cleared based on L1 signaling indicating SPS activation or deactivation / release.

[0284] When SPS is configured, the RRC configures the following parameters (e.g., SPS-Config IE):

[0285] -cs-RNTI: The CS-RNTI is used for activation, deactivation, and retransmission;

[0286] -nrofHARQ-Processes: The number of HARQ processes configured for SPS;

[0287] -periodicity: The periodicity of the downlink allocation configured for SPS.

[0288] When SPS is released by the upper layer, all corresponding configurations shall be released. After configuring the downlink allocation for SPS, the MAC entity shall sequentially consider that the Nth downlink allocation occurs in the following time slot, for which: (numberOfSlotsPerFrame x SFN + number of time slots in the frame) = [(numberOfSlotsPerFrame x SFN_start_time + time slot start time) + N x periodicity x numberOfSlotsPerFrame / 10] modulo (1024 x numberOfSlotsPerFrame)

[0289] where SFN 开始时间 and time slot 开始时间 are respectively the SFN and time slot of the first transmission of the PDSCH, where the configured downlink allocation is (re-)initialized.

[0290] To support multiple configurations of SPS, some RRC parameters may be introduced.

[0291] RRC parameters (e.g., DL-SPSconfig-index) may be introduced to indicate the index of the SPS configuration. The RRC parameter (e.g., DL-SPSconfig-index) may be included in each RRC configuration of SPS (e.g., SPS-Config IE). The value of the RRC parameter (e.g., DL-SPSconfig-index) may be 0, 1, 2, …, maxNrofSPSconfig - 2 or maxNrofSPSconfig - 1. maxNrofSPSconfig is the maximum number of SPS configurations, which may be 8 (12 or 16).

[0292] RRC parameters (e.g., DL-SPSconfig-ToAddModList) can be introduced to configure more than one DL SPS configuration. The RRC parameter (e.g., DL-SPSconfig-ToAddModList) can be a list or sequence of elements. The elements here can be SPS configurations (e.g., SPS-Config) or equivalent mappings. The elements of the list or sequence can include an identity (INTEGER) (e.g., ElementId) that explicitly identifies the element when adding, modifying, and removing. Here, ElementId can be the index of the DL SPS configuration (e.g., DL-SPSconfig-index). For each element (e.g., SPS-Config) in the RRC parameter (e.g., DL-SPSconfig-ToAddModList), if the current UE configuration includes an element (e.g., SPS-Config) with a given ElementId (e.g., DL-SPSconfig-index), the UE modifies the configured element (e.g., SPS-Config) according to the received element, otherwise the UE adds the received element (e.g., SPS-Config) to the UE configuration. That is, if the UE receives an SPS configuration corresponding to an index and the list in the UE configuration has an SPS configuration corresponding to that index, the UE updates the SPS configuration according to the received SPS configuration. If the UE receives an SPS configuration corresponding to an index and the list in the UE configuration does not have an SPS configuration corresponding to that index, the UE adds the SPS configuration to the list and / or its configuration according to the received SPS configuration. The RRC parameter (e.g., DL-SPSconfig-ToAddModList) can be from 1 to the maxNrofSPSconfig of SPS-Config (e.g., 8, 12, 16).

[0293] RRC parameters (e.g., DL-SPSconfig-ToReleaseList) can be introduced to release more than one DL SPS configuration. The RRC parameter (e.g., DL-SPSconfig-ToReleaseList) can be a list or sequence of ElementIds (e.g., DL-SPSconfig-index). For each ElementId (e.g., DL-SPSconfig-index) in the RRC parameter (e.g., DL-SPSconfig-ToReleaseList), if the current UE configuration includes an element (DL SPS configuration, e.g., SPS-Config) with the given ElementId (e.g., DL-SPSconfig-index), the UE releases the element (DL SPS configuration, e.g., SPS-Config) from the current UE configuration. That is, if the list includes an SPS configuration index and the current UE configuration includes the SPS configuration corresponding to that index, the UE releases the SPS configuration corresponding to that index.

[0294] To support the joint release and / or individual release of multiple SPS configurations, DCI fields (e.g., DCI format 1_0, DCI format 1_1, and / or DCI format 1_2) in the release DCI and / or a higher layer configurable table (e.g., CG configuration release table) and / or a fixed / default table can be used to indicate which SPS configuration to release. That is, M (e.g., M <= 4) bits in the release DCI are used to indicate which SPS configuration to release, where the association between each state indicated by the indication and the SPS configuration depends on 2^M states being higher layer configurable, and each of these states can be mapped to a single or multiple SPS configurations to be released. In the case of a state without a higher layer configuration, individual release is used, where the release corresponds to the SPS configuration index indicated by the indication.

[0295] For example, the value m of the DCI field (e.g., SPS configuration index) in the DCI can provide the row index m + 1 to the allocation table. The determination of the table used can be defined as follows. The index row defines which SPS configuration to release.

[0296] This table (e.g., DL-SPSconfig-ReleaseStateList) can be configured at a higher layer. This table is UE-specific (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config) and / or commonly configured (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon). This table (e.g., DL-SPSconfig-ReleaseStateList) can be a list / sequence of SPS configuration index sets (e.g., DL-SPSconfig-ReleaseState). Each SPS configuration index set may include one or more than one SPS configuration index that can be released. The SPS configuration index set can be empty, which means that no SPS configuration will be released. An example of the RRC-configured table is shown in List 2. The maximum number of entries in this table / sequence / list (e.g., maxNrofDL-SPS-ReleaseState) can be 16 or depend on the number of bits in the DCI field (e.g., SPS configuration index).

[0297]

[0298] List 2

[0299] This table can be fixed in this specification. That is, one or more default tables can be applied to the combined and / or individual release of multiple SPS configurations. Some examples shown are Table 5, Table 6, and Table 7.

[0300] Row index SPS configuration index set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7

[0301] Table 5

[0302] Row index SPS configuration index set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 9 8 10 9 11 10 12 11 13 12 14 13 15 14 16 15

[0303] Table 6

[0304] Row index SPS configuration index set 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 9 0、1 10 2、3 11 4、5 12 6、7 13 0、1、2、3 14 4、5、6、7 15 Not applicable 16 0、1、2、3、4、5、6、7、8、9、10、11

[0305] Table 7

[0306] Here, more than one table for SPS configuration release can be defined and / or configured. In the case of more than one table (e.g., SPS configuration release tables, including RRC-configured tables and / or default tables), the determination of the table to be used for SPS configuration release can depend on the DCI format for the release DCI, the RRC configuration (e.g., whether a UE-specific table and / or a commonly configured table is configured), the PDCCH search space where the UE detects the release DCI, and / or the CORESET where the UE detects the release DCI.

[0307] For example, if there is no RRC-configured table (e.g., if the parameter for indicating the table (e.g., no value of the parameter) for indicating the table is not configured), the default table (e.g., Table 5, Table 6, Table 7, or any table specified in this specification) can be applied to joint / individual SPS configuration release. In another example, if there is no RRC-configured table, the joint release of multiple SPS configurations may not be supported. That is, only individual release is supported (e.g., by using a single DCI format for releasing DCI at a certain timing, only one SPS configuration is released). Each value in the DCI field (e.g., SPS configuration index) can have a one-to-one mapping with the SPS configuration that can be released. For example, the DCI field (e.g., SPS configuration index) value m of the DCI can indicate that the SPS configuration with index m can be released.

[0308] For example, if a UE-specific RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config) is configured for the UE and the UE detects a release DCI (e.g., DCI format 1_2, DCI format 1_1, and / or DCI format 1_0) in the UE-specific search space, the UE-specific RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config) can be applied to (e.g., always applied to) joint / individual SPS configuration release (e.g., regardless of whether other tables (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon and / or any default table) can be configured and / or provided).

[0309] For example, if a common RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon) is configured (e.g., there is no UE-specific RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-Config) for the UE), the common RRC table (e.g., DL-SPSconfig-ReleaseStateList in pdsch-ConfigCommon) can be applied to joint / individual SPS configuration release. For example, if a common RRC table and a UE-specific RRC table are configured, the UE can apply the UE-specific RRC table to be used for CG configuration release. For example, if a common RRC table and a UE-specific RRC table are configured for the UE, the UE-specific RRC table (e.g., the configuration of the UE-specific RRC table) can overwrite the common RRC table (e.g., the configuration of the common RRC table).

[0310] For example, if the UE detects a release DCI (e.g., DCI format 1_2, DCI format 1_1, and / or DCI format 1_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), then the default table (e.g., Table 5, Table 6, Table 7, or any table specified in the specification (e.g., defined by this specification)) can be applied to the joint / individual SPS configuration release. In another example, if the UE detects a release DCI (e.g., DCI format 1_2, DCI format 1_1, and / or DCI format 1_0) in a common search space associated with CORESET 0 (e.g., and / or a common search space not associated with CORESET 0), then the joint release of multiple SPS configurations may not be supported. That is, only individual release is supported. Each value in the DCI field (e.g., SPS configuration index) can have a one-to-one mapping with the SPS configuration that can be released. For example, the DCI field (e.g., SPS configuration index) value m of the DCI can indicate that the SPS configuration with index m can be released.

[0311] Another example is shown in Table 8. As shown in Table 8, the UE can determine the table to be applied to the SPS configuration release (e.g., in the default table, the common RRC table, and / or the UE-specific RRC table). That is, as described above, the UE can determine the table (e.g., in the default table, the common RRC table, and / or the UE-specific RRC table) based on the DCI format for the release DCI, the RRC configuration (e.g., whether the UE-specific RRC table is configured and / or whether the common RRC table is the configured table), the PDCCH search space in which the UE detects the DCI format for the release DCI, and / or the CORESET in which the UE monitors the DCI format for the release DCI (e.g., the index of the CORESET).

[0312]

[0313] Table 8

[0314] If the DCI for release is a fallback DCI (e.g., DCI format 1_0), there may be no DCI field (e.g., SPS configuration index) to indicate which SPS configuration to release, and some fallback behaviors can be described here. For example, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release all SPS configurations (e.g., all SPS configurations). In another example, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release a specific configuration (e.g., a specific SPS configuration) and / or the default configuration (e.g., the default SPS configuration). For example, if the UE detects DCI format 1_0 for CG configuration release, the UE may release the SPS configuration with a predetermined index (e.g., the SPS configuration with index "0" (e.g., as a specific SPS configuration and / or the default SPS configuration)). Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release the SPS configuration with the lowest index (e.g., the minimum index). For example, in the case where an SPS configuration with index "1", an SPS configuration with index "3", and an SPS configuration with index "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release, the UE may release the SPS configuration with "1". Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release, the UE may release the SPS configuration with the highest index (e.g., the maximum index). For example, in the case where an SPS configuration with index "1", an SPS configuration with index "3", and an SPS configuration with index "5" are configured, and if the UE detects DCI format 0_0 for SPS configuration release, the UE may release the SPS configuration with "5". Here, the specific configuration and / or the default configuration can be defined by this specification and the known information between the gNB and the UE. That is, for the detection of DCI format 0_0 for SPS configuration release, the UE can determine which SPS configuration to release based on the index for the SPS configuration (e.g., configured by the gNB). In another example, if multiple SPS configurations are configured, it may not be desirable for the UE to receive DCI format 1_0 for SPS configuration release.

[0315] Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release all SPS configurations (e.g., all SPS configurations). In another example, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release a specific configuration (e.g., a specific SPS configuration) and / or the default configuration (e.g., the default SPS configuration). For example, if the UE detects DCI format 1_0 for CG configuration release in the CSS, the UE may release the SPS configuration with a predetermined index (e.g., the SPS configuration with index "0" (e.g., as a specific SPS configuration and / or the default SPS configuration)). Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release the SPS configuration with the lowest index (e.g., the minimum index). For example, in the case where SPS configurations with index "1", SPS configurations with index "3", and SPS configurations with index "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release the SPS configuration with "1". Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release the SPS configuration with the highest index (e.g., the maximum index). For example, in the case where SPS configurations with index "1", SPS configurations with index "3", and SPS configurations with index "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS, the UE may release the SPS configuration with "5". That is, for the detection of DCI format 1_0 for SPS configuration release in the CSS, the UE may determine which SPS configuration to release based on the index for the SPS configuration (e.g., configured by the gNB).

[0316] Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release all SPS configurations (e.g., all SPS configurations). In another example, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release a specific configuration (e.g., a specific SPS configuration) and / or the default configuration (e.g., the default SPS configuration). For example, if the UE detects DCI format 1_0 for CG configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with a predetermined index (e.g., the SPS configuration with index "0" (e.g., as a specific SPS configuration and / or the default SPS configuration)). Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with the lowest index (e.g., the minimum index). For example, in the case where SPS configurations with index "1", SPS configurations with index "3", and SPS configurations with index "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with "1". Additionally or alternatively, if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with the highest index (e.g., the maximum index). For example, in the case where SPS configurations with index "1", SPS configurations with index "3", and SPS configurations with index "5" are configured, and if the UE detects DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may release the SPS configuration with "5". That is, for the detection of DCI format 1_0 for SPS configuration release in the CSS associated with CORESET#0, the UE may determine which SPS configuration to release based on the index for the SPS configuration (e.g., configured by the gNB).

[0317] This document describes the PDCCH verification for grant type 2 for DL SPS and UL configuration. If the CRC of the corresponding DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, and / or DCI format 0_2) is scrambled by the CS-RNTI provided by the cs-RNTI, and the new data indication field of the enabled transport block is set to "0", the UE can verify the DL SPS allocation PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or scheduling release. If all fields of the DCI format are set according to predefined rules (e.g., special fields in the DCI format can be set to specific values for DLSPS and UL grant type 2 scheduling activation PDCCH verification and / or scheduling release PDCCH verification), the verification of the DCI format (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, and / or DCI format 0_2) is implemented. If the verification is implemented, the UE regards the information of the DCI format as a valid activation or valid release of DL SPS or the configured UL grant type 2. If the verification is not implemented, the UE discards all information of the DCI format. For example, if the HARQ process number field in the DCI format is set to all "0" and / or the redundancy version field in the DCI format is set to "00", the UE can regard the information of the DCI format as a valid activation of DL SPS or the configured UL grant type 2. In the case of supporting multiple configurations (multiple SPS configurations and / or CG configurations), the configuration index field in the DCI format can be used to indicate which SPS configuration and / or CG configuration is activated. For example, if the HARQ process number field in the DCI format is set to all "0" and / or the redundancy version field in the DCI format is set to "00" and / or the modulation and coding scheme field in the DCI format is set to all "1" and / or the frequency domain resource allocation is set to all "1", the UE can regard the information of the DCI format as a valid release of DL SPS or the configured UL grant type 2. In the case of supporting multiple configurations (multiple SPS configurations and / or CG configurations), the configuration index field in the DCI format can be used to indicate which SPS configuration and / or CG configuration is released / deactivated.

[0318] Figure 7 illustrates various components that can be used for UE 702. In conjunction with Figure 7 the UE 702 described can be based on in conjunction with Figure 1Implemented by the described UE 102. UE 702 includes a processor 703 that controls the operation of UE 702. The processor 703 may also be referred to as a central processing unit (CPU). A memory 705 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device that can store 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.

[0319] UE 702 may also include a housing that houses one or more transmitters 758 and one or more receivers 720 to allow for the transmission and reception of data. The transmitter 758 and the receiver 720 may be combined into one or more transceivers 718. One or more antennas 722a-n are attached to the housing and electrically coupled to the transceiver 718.

[0320] The various components of UE 702 are coupled together by a bus system 711 (which may include a power bus, a control signal bus, and a status signal bus in addition to the data bus). However, for clarity, the various buses are shown as the bus system 711 in Figure 7 UE 702 may also include a digital signal processor (DSP) 713 for processing signals. UE 702 may also include a communication interface 715 that provides user access to the functions of UE 702. Figure 7 The UE 702 shown is a functional block diagram rather than a list of specific components.

[0321] Figure 8 Various components that can be used for the gNB 860 are shown. The gNB 860 described in conjunction with Figure 8 may be based on the combination described in Figure 1Implemented by the described gNB 160. gNB 860 includes a processor 803 that controls the operation of gNB 860. The processor 803 may also be referred to as a central processing unit (CPU). A memory 805 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device that can store information) provides instructions 807a and data 809a to the processor 803. A portion of the memory 805 may also include non-volatile random access memory (NVRAM). Instructions 807b and data 809b may also reside in the processor 803. The instructions 807b and / or data 809b loaded into the processor 803 may also include instructions 807a and / or data 809a from the memory 805 that are loaded for execution or processing by the processor 803. The instructions 807b may be executed by the processor 803 to implement the methods described herein.

[0322] gNB 860 may also include a housing that houses one or more transmitters 817 and one or more receivers 878 to allow for the transmission and reception of data. The transmitters 817 and receivers 878 may be combined into one or more transceivers 876. One or more antennas 880a-n are attached to the housing and electrically coupled to the transceivers 876.

[0323] The various components of gNB 860 are coupled together by a bus system 811 (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 shown as the bus system 811 in Figure 8 . gNB 860 may also include a digital signal processor (DSP) 813 for processing signals. gNB 860 may also include a communication interface 815 that provides user access to the functions of gNB 860. Figure 8 The gNB 860 shown is a functional block diagram rather than a list of specific components.

[0324] Figure 9 is a block diagram showing a specific implementation of a UE 902 in which one or more of the systems and / or methods described herein may be implemented. UE 902 includes a transmitting device 958, a receiving device 920, and a control device 924. The transmitting device 958, the receiving device 920, and the control device 924 may be configured to perform one or more of the functions described above Figure 1 above. The above Figure 7 shows Figure 9 an example of the specific device structure of Figure 1 . Various other structures may be implemented to achieve one or more of the functions of

[0325] Figure 10FIG. is a block diagram illustrating a specific implementation of gNB 1060 in which one or more of the systems and / or methods described herein may be implemented. gNB 1060 includes a transmitting device 1017, a receiving device 1078, and a control device 1082. The transmitting device 1017, the receiving device 1078, and the control device 1082 may be configured to perform one or more of the functions described above Figure 1 above Figure 8 shows Figure 10 an example of the specific device structure. Various other structures may be implemented to achieve Figure 1 one or more of the functions. For example, the DSP may be implemented by software.

[0326] Figure 11 FIG. is a block diagram illustrating a specific implementation of gNB 1160. gNB 1160 may be an example of gNB160 described in conjunction with Figure 1 gNB 1160 may include a high-layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

[0327] The high-layer processor 1123 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-layer parameters to the physical layer. The high-layer processor 1123 may obtain transport blocks from the physical layer. The high-layer processor 1123 may send to / obtain from the high layer of the UE high-layer messages such as RRC messages and MAC messages. The high-layer processor 1123 may provide a transport block to the PDSCH transmitter and provide transmission parameters related to the transport block to the PDCCH transmitter.

[0328] The DL transmitter 1125 may multiplex downlink physical channels and downlink physical signals (including reservation signals) and transmit them via the transmit antenna 1131. The UL receiver 1133 may receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1131. The PUCCH receiver 1135 may provide UCI to the high-layer processor 1123. The PUSCH receiver 1137 may provide the received transport block to the high-layer processor 1123.

[0329] Figure 12 FIG. is a block diagram illustrating a specific implementation of UE 1202. UE 1202 may be in conjunction with Figure 1Example of the described UE102. The UE 1202 may include a high-layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. The UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[0330] The high-layer processor 1223 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-layer parameters to the physical layer. The high-layer processor 1223 may obtain transport blocks from the physical layer. The high-layer processor 1223 may send to / obtain from the high layer of the UE high-layer messages, such as RRC messages and MAC messages. The high-layer processor 1223 may provide a transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

[0331] The DL receiver 1243 may receive multiplexed downlink physical channels and downlink physical signals via the receiving antenna 1231 and demultiplex them. The PDCCH receiver 1245 may provide DCI to the high-layer processor 1223. The PDSCH receiver 1247 may provide the received transport block to the high-layer processor 1223.

[0332] 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 some of the methods described herein may be applied to DL and / or UL transmission. A combination of one or more of some of the methods described herein may not be excluded in the system and method.

[0333] It should be noted that the names of the physical channels described herein are examples. Other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH", "New Generation (G) PDCCH, GPDSCH, GPUCCH, and GPUSCH", etc.

[0334] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or a processor. As used herein, the term "computer-readable medium" may represent a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example and not limitation, a computer-readable medium or a processor-readable medium 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 the required program code in the form of instructions or data structures and can be accessed by a computer or a processor.

[0335] As used herein, disk and optical disk include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu- ray disc, where the disk typically duplicates data magnetically and the optical disk duplicates data optically using a laser.

[0336] It should be noted that one or more of the methods described herein can be implemented in hardware and / or executed using hardware. For example, one or more of the methods described herein can be implemented in a chipset, application specific integrated circuit (ASIC), large scale integration (LSI), or integrated circuit, etc., and / or implemented using a chipset, application specific integrated circuit (ASIC), large scale integration (LSI), or integrated circuit, etc.

[0337] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. Without departing from the scope of the claims, these method steps and / or actions can be interchanged with each other and / or combined into a single step. In other words, unless the correct operation of the method requires steps or actions in a specific order, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.

[0338] It should be understood that the claims are not limited to the exact configurations and components shown above. Without departing from the scope of the claims, various modifications, changes, and alterations can be made to the arrangements, operations, and details of the systems, methods, and apparatuses described herein.

[0339] The program running on the gNB 160 or UE 102 according to the system and method is a program that controls a CPU, etc. in a manner to implement the functions according to the system and method (a program for computer operation). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, this information is stored in various ROMs or HDDs and read by the CPU whenever needed for modification or writing. As a recording medium on which the program is stored, any one of a semiconductor (e.g., ROM, non-volatile memory card, etc.), optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), magnetic storage medium (e.g., magnetic tape, floppy disk, etc.), etc. is possible. In addition, in some cases, the functions according to the system and method described herein are implemented by running the loaded program, and further, the functions according to the system and method are implemented based on instructions from the program in combination with an operating system or other application programs.

[0340] In addition, in the case where the program is commercially available, the program stored on a portable recording medium may be distributed, or the program may be transmitted to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. Further, some or all of the gNB 160 and the UE 102 according to the systems and methods described herein may be implemented as LSIs as typical integrated circuits. Each functional block of the gNB 160 and the UE 102 may be individually built into a chip, and some or all of the functional blocks may be integrated into a chip. Further, the technology of the integrated circuit is not limited to LSIs, and the integrated circuit for the functional block may be implemented using an application-specific circuit or a general-purpose processor. Further, if an integrated circuit technology alternative to LSIs emerges with the continuous progress of semiconductor technology, the integrated circuit applying such technology may also be used.

[0341] In addition, each functional block or various features of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit (usually one integrated circuit or a plurality of integrated circuits). The circuit designed to execute the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific or general-purpose integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each circuit described herein may be configured by a digital circuit or may be configured by an analog circuit. Further, when an integrated circuit technology for fabricating an integrated circuit to replace the current integrated circuit emerges due to the progress of semiconductor technology, the integrated circuit produced by such technology can also be used.

[0342] As used herein, the term “and / or” shall be interpreted to mean one or more items. For example, the phrase “A, B, and / or C” shall 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. As used herein, the phrase “at least one” should be interpreted to mean 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” shall 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. As used herein, the phrase “one or more” shall 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” shall 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.

[0343] <Cross-reference>

[0344] This non-provisional patent application claims priority under 35 U.S.C. § 119 to Provisional Patent Application No. 62 / 909,984, filed on October 3, 2019, the entire content of which is hereby incorporated by reference.

Claims

1. A user equipment (UE) communicating with a base station, the UE comprising: A receiving unit, the receiving unit being configured to: Receive a radio resource control (RRC) message for configuring more than one configured grant (CG) physical uplink shared channel (PUSCH) configuration; Receive an RRC configuration including first information comprising a list for configuring the release of a CG PUSCH configuration, wherein the list indicates multiple states, each state being associated with a corresponding CG PUSCH configuration; Detect a physical downlink control channel (PDCCH) of a first downlink control information (DCI) format having a cyclic redundancy check (CRC) scrambled by a first radio network temporary identifier (RNTI), the first DCI format being for the activation of the CG PUSCH configuration; and Detect a PDCCH of a second DCI format having a CRC scrambled by the first RNTI, the second DCI format being for the deactivation of the CG PUSCH configuration; A transmission unit, the transmission unit being configured to perform uplink data transmission on a PUSCH corresponding to the activated CG PUSCH configuration based on the detection of the first DCI format including second information for indicating the activation of the CG PUSCH configuration; and A processing unit, the processing unit being configured to release the CG PUSCH configuration based on the detection of the second DCI format and according to the second DCI format and the first information for configuring the list, the second DCI format including third information indicating: a) the release of the CG PUSCH configuration and b) one of the multiple states associated with one or more indexes of the released CG PUSCH configuration, wherein The third information includes a modulation and coding scheme field set to all '1's and a redundancy version field set to all '0's, which causes the UE to consider the third information as a valid release of the CG PUSCH configuration according to a predefined rule; and The predefined rule for the valid release is predefined as follows: the modulation and coding scheme field is to be set to all '1's and the redundancy version field is to be set to all '0's, but it is not predefined that the hybrid automatic repeat request (HARQ) process number field in the second DCI format is to be set to all '0's and the frequency domain resource allocation field in the second DCI format is to be set to all '1's.

2. The UE according to claim 1, wherein The first DCI format is one of DCI format 0_0, DCI format 0_1, and DCI format 0_2; and The second DCI format is the one of DCI format 0_0, DCI format 0_1, and DCI format 0_2.

3. The UE according to claim 1, wherein The first DCI format is one of DCI format 0_0, DCI format 0_1, and DCI format 0_2; and The second DCI format is another one of DCI format 0_0, DCI format 0_1, and DCI format 0_2.

4. A method performed by a User Equipment (UE) communicating with a base station, the method comprising: Receiving a Radio Resource Control (RRC) message for configuring more than one Configured Grant (CG) Physical Uplink Shared Channel (PUSCH) configuration; Receiving an RRC configuration including first information for configuring a list for CG PUSCH configuration release, wherein the list indicates multiple states, each state being associated with a corresponding CG PUSCH configuration; Detecting a Physical Downlink Control Channel (PDCCH) of a first Downlink Control Information (DCI) format having a Cyclic Redundancy Check (CRC) scrambled by a first Radio Network Temporary Identifier (RNTI), the first DCI format being for activation of the CG PUSCH configuration; Detecting a PDCCH of a second DCI format having a CRC scrambled by the first RNTI, the second DCI format being for deactivation of the CG PUSCH configuration; Performing uplink data transmission on a PUSCH corresponding to the activated CG PUSCH configuration based on detection of the first DCI format including second information for indicating activation of the CG PUSCH configuration; Releasing the CG PUSCH configuration based on detection of the second DCI format and according to the second DCI format and the first information for configuring the list, the second DCI format including third information indicating: a) releasing the CG PUSCH configuration and b) one of the multiple states associated with one or more indices of the released CG PUSCH configuration, wherein The third information includes a Modulation and Coding Scheme (MCS) field set to all '1's and a Redundancy Version (RV) field set to all '0's, which causes the UE to consider the third information as a valid release of the CG PUSCH configuration according to predefined rules, and The predefined rules for valid release are predefined as follows: the MCS field is to be set to all '1's and the RV field is to be set to all '0's, but not predefined as follows: the Hybrid Automatic Repeat reQuest (HARQ) process number field in the second DCI format is to be set to all '0's and the frequency domain resource allocation field in the second DCI format is to be set to all '1's.

5. A base station communicating with a User Equipment (UE), the base station comprising: A transmission unit configured to: Transmit a Radio Resource Control (RRC) message for configuring more than one Configured Grant (CG) Physical Uplink Shared Channel (PUSCH) configuration, Transmit an RRC configuration including first information for configuring a list for CG PUSCH configuration release, wherein the list indicates multiple states, each state being associated with a corresponding CG PUSCH configuration, Transmit a Physical Downlink Control Channel (PDCCH) of a first Downlink Control Information (DCI) format having a Cyclic Redundancy Check (CRC) scrambled by a first Radio Network Temporary Identifier (RNTI), the first DCI format being for activation of the CG PUSCH configuration, and Transmit a PDCCH with a second DCI format having a CRC scrambled by a first RNTI, the second DCI format being for deactivation of a CG PUSCH configuration; A receiving unit configured to receive an uplink data transmission on a PUSCH corresponding to an activated CG PUSCH configuration based on a transmission of a first DCI format including second information for indicating activation of the CG PUSCH configuration, where the second DCI format includes third information indicating: a) release of the CG PUSCH configuration and b) one of the plurality of states associated with one or more indices of the released CG PUSCH configuration, the second DCI format causing the UE to release the CG PUSCH configuration according to the second DCI format and first information for configuring the list, where the third information includes a modulation and coding scheme field set to all '1's and a redundancy version field set to all '0's, which causes the UE to consider the third information as a valid release of the CG PUSCH configuration according to a predefined rule, and the predefined rule for the valid release is predefined as follows: the modulation and coding scheme field is to be set to all '1's and the redundancy version field is to be set to all '0's, but not predefined as follows: the HARQ process number field in the second DCI format is to be set to all '0's and the frequency domain resource allocation field in the second DCI format is to be set to all '1's.

Images