US11638282B2 - Method, user equipment, apparatus, and computer-readable storage medium for PUSCH transmission, and method and base station for PUSCH reception - Google Patents

Method, user equipment, apparatus, and computer-readable storage medium for PUSCH transmission, and method and base station for PUSCH reception Download PDF

Info

Publication number
US11638282B2
US11638282B2 US17/735,930 US202217735930A US11638282B2 US 11638282 B2 US11638282 B2 US 11638282B2 US 202217735930 A US202217735930 A US 202217735930A US 11638282 B2 US11638282 B2 US 11638282B2
Authority
US
United States
Prior art keywords
configuration
dci format
configured grant
dci
configuration information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US17/735,930
Other languages
English (en)
Other versions
US20220264608A1 (en
Inventor
Duckhyun BAE
Hyunho Lee
Seonwook Kim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to US17/735,930 priority Critical patent/US11638282B2/en
Assigned to LG ELECTRONICS INC. reassignment LG ELECTRONICS INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BAE, Duckhyun, LEE, HYUNHO, KIM, SEONWOOK
Publication of US20220264608A1 publication Critical patent/US20220264608A1/en
Application granted granted Critical
Publication of US11638282B2 publication Critical patent/US11638282B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H04L1/0018—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement based on latency requirement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0072—Error control for data other than payload data, e.g. control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0075—Transmission of coding parameters to receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H04W72/1289—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • the present disclosure relates to a wireless communication system.
  • M2M machine-to-machine
  • MTC machine type communication
  • PCs personal computers
  • MIMO multiple input multiple output
  • BS multi-base station
  • eMBB enhanced mobile broadband
  • RAT legacy radio access technology
  • massive machine type communication for providing various services at anytime and anywhere by connecting a plurality of devices and objects to each other is one main issue to be considered in next-generation communication.
  • the number of UEs to which a BS should provide services in a prescribed resource region is increasing and the volume of data and control information that the BS transmits/receives to/from the UEs to which the BS provides services is also increasing. Since the amount of resources available to the BS for communication with the UE(s) is limited, a new method for the BS to efficiently receive/transmit uplink/downlink data and/or uplink/downlink control information from/to the UE(s) using the limited radio resources is needed. In other words, due to increase in the density of nodes and/or the density of UEs, a method for efficiently using high-density nodes or high-density UEs for communication is needed.
  • a method to efficiently support various services with different requirements in a wireless communication system is also needed.
  • An aspect of the present disclosure provides a method of transmitting a physical uplink shared channel (PUSCH) by a user equipment (UE) in a wireless communication system.
  • the method comprises: receiving a radio resource control (RRC) configuration including first configuration information for a first downlink control information (DCI) format and second configuration information for a second DCI format, receiving a configured grant configuration including a repetition scheme and resource allocation information, determining resource allocation of a configured grant based on i) configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration among the first configuration information and the second configuration information, and ii) the resource allocation information, and performing PUSCH transmission based on the resource allocation.
  • RRC radio resource control
  • Each of the first configuration information and the second configuration information may include a time domain resource allocation (TDRA) table.
  • TDRA time domain resource allocation
  • the UE includes at least one transceiver, at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations.
  • PUSCH physical uplink shared channel
  • the operations comprise: receiving a radio resource control (RRC) configuration including first configuration information for a first downlink control information (DCI) format and second configuration information for a second DCI format, receiving a configured grant configuration including a repetition scheme and resource allocation information, determining resource allocation of a configured grant based on i) configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration among the first configuration information and the second configuration information, and ii) the resource allocation information, and performing PUSCH transmission based on the resource allocation.
  • RRC radio resource control
  • DCI downlink control information
  • DCI downlink control information
  • second configuration information for a second DCI format
  • TDRA time domain resource allocation
  • the device includes at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations.
  • the operations comprise: receiving a radio resource control (RRC) configuration including first configuration information for a first downlink control information (DCI) format and second configuration information for a second DCI format, receiving a configured grant configuration including a repetition scheme and resource allocation information, determining resource allocation of a configured grant based on i) configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration among the first configuration information and the second configuration information, and ii) the resource allocation information, and performing physical uplink shared channel (PUSCH) transmission based on the resource allocation.
  • RRC radio resource control
  • DCI downlink control information
  • DCI downlink control information
  • second configuration information for a second DCI format
  • a configured grant configuration including a repetition scheme and resource allocation information
  • PUSCH physical uplink shared channel
  • Each of the first configuration information and the second configuration information may include
  • the computer-readable storage medium stores at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a user equipment (UE).
  • the operations comprise: receiving a radio resource control (RRC) configuration including first configuration information for a first downlink control information (DCI) format and second configuration information for a second DCI format, receiving a configured grant configuration including a repetition scheme and resource allocation information, determining resource allocation of a configured grant based on i) configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration among the first configuration information and the second configuration information, and ii) the resource allocation information, and performing physical uplink shared channel (PUSCH) transmission based on the resource allocation.
  • RRC radio resource control
  • DCI downlink control information
  • second configuration information for a second DCI format
  • a configured grant configuration including a repetition scheme and resource allocation information
  • PUSCH physical uplink shared channel
  • Each of the first configuration information and the second configuration information may include a time domain resource allocation (TDRA) table.
  • Another aspect of the present disclosure provides a method of receiving a physical uplink shared channel (PUSCH) by a base station from a user equipment (UE) in a wireless communication device.
  • the method comprises: transmitting a radio resource control (RRC) configuration including first configuration information for a first downlink control information (DCI) format and second configuration information for a second DCI format, generating resource allocation information for resource allocation of a configured grant, transmitting a configured grant configuration including a repetition scheme for the configured grant and the resource allocation information, and performing PUSCH reception based on the resource allocation.
  • RRC radio resource control
  • the BS comprises: at least one transceiver, at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations.
  • the operations comprise: transmitting a radio resource control (RRC) configuration including first configuration information for a first downlink control information (DCI) format and second configuration information for a second DCI format, generating resource allocation information for resource allocation of a configured grant, transmitting a configured grant configuration including a repetition scheme for the configured grant and the resource allocation information, and performing PUSCH reception based on the resource allocation.
  • RRC radio resource control
  • Generating the resource allocation information may include generating the resource allocation information based on i) configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration among the first configuration information and the second configuration information, and ii) the resource allocation information.
  • Each of the first configuration information and the second configuration information may include a time domain resource allocation (TDRA) table.
  • TDRA time domain resource allocation
  • determining the resource allocation of the configured grant may include determining resource allocation of the configured grant based on the first configuration information, based on both the first configuration information and the second configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration.
  • generating the resource allocation information may include generating the resource allocation information based on the first configuration information based on both the first configuration information and the second configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration.
  • the first DCI format may be a DCI format 0_1.
  • the second DCI format may be a DCI format 0_2.
  • a wireless communication signal may be efficiently transmitted/received. Accordingly, the total throughput of a wireless communication system may be raised.
  • various services with different requirements may be efficiently supported in a wireless communication system.
  • FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present disclosure
  • FIG. 4 illustrates an example of a frame structure used in a 3rd generation partnership project (3GPP)-based wireless communication system
  • FIG. 5 illustrates a resource grid of a slot
  • FIG. 6 illustrates slot structures used in a 3GPP-based system
  • FIG. 9 illustrates an example of types of repeated transmissions
  • FIG. 10 is a diagram showing an example of an UE operation according to some implementation(s) of the present disclosure.
  • FIG. 11 is a diagram showing an example of a UE operation according to some implementations of the present disclosure.
  • FIG. 12 is a diagram showing an example of a BS operation according to some implementation(s) of the present disclosure.
  • FIG. 13 illustrates a flow of signal transmission/reception between a UE and a BS according to some implementations of the present disclosure.
  • the multiple access systems may include, for example, a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single-carrier frequency division multiple access (SC-FDMA) system, a multi-carrier frequency division multiple access (MC-FDMA) system, etc.
  • CDMA may be implemented by radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be implemented by radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), enhanced data rates for GSM evolution (EDGE) (i.e., GERAN), etc.
  • OFDMA may be implemented by radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved-UTRA (E-UTRA), etc.
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • E-UTRA evolved-UTRA
  • UTRA is part of universal mobile telecommunications system (UMTS) and 3rd generation partnership project (3GPP) long-term evolution (LTE) is part of E-UMTS using E-UTRA.
  • 3GPP LTE adopts OFDMA on downlink (DL) and adopts SC-FDMA on uplink (UL).
  • LTE-advanced (LTE-A) is an evolved version of 3GPP LTE.
  • 3GPP based standard specifications for example, 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300, 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.331, etc.
  • a device “assumes” something, this may mean that a channel transmission entity transmits a channel in compliance with the corresponding “assumption”. This also may mean that a channel reception entity receives or decodes the channel in the form of conforming to the “assumption” on the premise that the channel has been transmitted in compliance with the “assumption”.
  • a user equipment may be fixed or mobile.
  • Each of various devices that transmit and/or receive user data and/or control information by communicating with a base station (BS) may be the UE.
  • the term UE may be referred to as terminal equipment, mobile station (MS), mobile terminal (MT), user terminal (UT), subscriber station (SS), wireless device, personal digital assistant (PDA), wireless modem, handheld device, etc.
  • a BS refers to a fixed station that communicates with a UE and/or another BS and exchanges data and control information with a UE and another BS.
  • the term BS may be referred to as advanced base station (ABS), Node-B (NB), evolved Node-B (eNB), base transceiver system (BTS), access point (AP), processing server (PS), etc.
  • ABS advanced base station
  • NB Node-B
  • eNB evolved Node-B
  • BTS base transceiver system
  • AP access point
  • PS processing server
  • a BS of a universal terrestrial radio access (UTRAN) is referred to as an NB
  • a BS of an evolved-UTRAN (E-UTRAN) is referred to as an eNB
  • a BS of new radio access technology network is referred to as a gNB.
  • the NB, eNB, or gNB will be referred to as a BS regardless of the type or version of communication technology.
  • a node refers to a fixed point capable of transmitting/receiving a radio signal to/from a UE by communication with the UE.
  • Various types of BSs may be used as nodes regardless of the names thereof.
  • a BS, NB, eNB, pico-cell eNB (PeNB), home eNB (HeNB), relay, repeater, etc. may be a node.
  • a node may not be a BS.
  • a radio remote head (RRH) or a radio remote unit (RRU) may be a node.
  • the RRH and RRU have power levels lower than that of the BS.
  • RRH/RRU Since the RRH or RRU (hereinafter, RRH/RRU) is connected to the BS through a dedicated line such as an optical cable in general, cooperative communication according to the RRH/RRU and the BS may be smoothly performed relative to cooperative communication according to BSs connected through a wireless link.
  • At least one antenna is installed per node.
  • An antenna may refer to a physical antenna port or refer to a virtual antenna or an antenna group.
  • the node may also be called a point.
  • a cell refers to a specific geographical area in which one or more nodes provide communication services. Accordingly, in the present disclosure, communication with a specific cell may mean communication with a BS or a node providing communication services to the specific cell.
  • a DL/UL signal of the specific cell refers to a DL/UL signal from/to the BS or the node providing communication services to the specific cell.
  • a cell providing UL/DL communication services to a UE is especially called a serving cell.
  • channel status/quality of the specific cell refers to channel status/quality of a channel or a communication link generated between the BS or the node providing communication services to the specific cell and the UE.
  • the UE may measure a DL channel state from a specific node using cell-specific reference signal(s) (CRS(s)) transmitted on a CRS resource and/or channel state information reference signal(s) (CSI-RS(s)) transmitted on a CSI-RS resource, allocated to the specific node by antenna port(s) of the specific node.
  • CRS cell-specific reference signal
  • CSI-RS channel state information reference signal
  • a 3GPP-based communication system uses the concept of a cell in order to manage radio resources, and a cell related with the radio resources is distinguished from a cell of a geographic area.
  • the “cell” of the geographic area may be understood as coverage within which a node may provide services using a carrier, and the “cell” of the radio resources is associated with bandwidth (BW), which is a frequency range configured by the carrier. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depend upon a carrier carrying the signal, coverage of the node may also be associated with coverage of the “cell” of radio resources used by the node. Accordingly, the term “cell” may be used to indicate service coverage by the node sometimes, radio resources at other times, or a range that a signal using the radio resources may reach with valid strength at other times.
  • BW bandwidth
  • the “cell” associated with the radio resources is defined by a combination of DL resources and UL resources, that is, a combination of a DL component carrier (CC) and a UL CC.
  • the cell may be configured by the DL resources only or by the combination of the DL resources and the UL resources.
  • linkage between a carrier frequency of the DL resources (or DL CC) and a carrier frequency of the UL resources (or UL CC) may be indicated by system information.
  • SIB2 system information block type 2
  • the carrier frequency may be equal to or different from a center frequency of each cell or CC.
  • CA carrier aggregation
  • the UE has only one radio resource control (RRC) connection with a network.
  • RRC radio resource control
  • one serving cell provides non-access stratum (NAS) mobility information.
  • NAS non-access stratum
  • RRC connection re-establishment/handover one serving cell provides security input.
  • This cell is referred to as a primary cell (Pcell).
  • the Pcell refers to a cell operating on a primary frequency on which the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.
  • secondary cells may be configured to form a set of serving cells together with the Pcell.
  • the Scell may be configured after completion of RRC connection establishment and used to provide additional radio resources in addition to resources of a specific cell (SpCell).
  • a carrier corresponding to the Pcell on DL is referred to as a downlink primary CC (DL PCC)
  • DL PCC downlink primary CC
  • UL PCC uplink primary CC
  • a carrier corresponding to the Scell on DL is referred to as a downlink secondary CC (DL SCC)
  • a carrier corresponding to the Scell on UL is referred to as an uplink secondary CC (UL SCC).
  • the term SpCell refers to the Pcell of a master cell group (MCG) or the Pcell of a secondary cell group (SCG).
  • MCG master cell group
  • SCG secondary cell group
  • the SpCell supports PUCCH transmission and contention-based random access and is always activated.
  • the MCG is a group of service cells associated with a master node (e.g., BS) and includes the SpCell (Pcell) and optionally one or more Scells.
  • the SCG is a subset of serving cells associated with a secondary node and includes a PSCell and 0 or more Scells.
  • RRC_CONNECTED state not configured with CA or DC, only one serving cell including only the Pcell is present.
  • serving cells refers to a set of cells including SpCell(s) and all Scell(s).
  • DC two medium access control (MAC) entities, i.e., one MAC entity for the MCG and one MAC entity for the SCG, are configured for the UE.
  • MAC medium access control
  • a UE with which CA is configured and DC is not configured may be configured with a Pcell PUCCH group, which includes the Pcell and 0 or more Scells, and an Scell PUCCH group, which includes only Scell(s).
  • PUCCH cell an Scell on which a PUCCH associated with the corresponding cell is transmitted (hereinafter, PUCCH cell) may be configured.
  • An Scell indicated as the PUCCH Scell belongs to the Scell PUCCH group and PUCCH transmission of related UCI is performed on the PUCCH Scell.
  • An Scell, which is not indicated as the PUCCH Scell or in which a cell indicated for PUCCH transmission is a Pcell belongs to the Pcell PUCCH group and PUCCH transmission of related UCI is performed on the Pcell.
  • the UE receives information on DL from the BS and the UE transmits information on UL to the BS.
  • the information that the BS and UE transmit and/or receive includes data and a variety of control information and there are various physical channels according to types/usage of the information that the UE and the BS transmit and/or receive.
  • a demodulation reference signal (DMRS), a channel state information RS (CSI-RS), etc. are defined as DL RSs.
  • the 3GPP-based communication standards define UL physical channels corresponding to resource elements carrying information originating from the higher layer and UL physical signals corresponding to resource elements which are used by the physical layer but do not carry the information originating from the higher layer.
  • a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as the UL physical channels
  • a DMRS for a UL control/data signal, a sounding reference signal (SRS) used for UL channel measurement, etc. are defined.
  • the PDCCH refers to a set of time-frequency resource elements (REs) that carry downlink control information (DCI)
  • the PDSCH refers to a set of REs that carry DL data.
  • the PUCCH, PUSCH, and PRACH refer to a set of time-frequency REs that carry uplink control information (UCI), UL data, and random access signals, respectively.
  • UCI uplink control information
  • UL data uplink control information
  • random access signals random access signals.
  • the meaning of “The UE transmits/receives the PUCCH/PUSCH/PRACH” is that the UE transmits/receives the UCI/UL data/random access signals on or through the PUCCH/PUSCH/PRACH, respectively.
  • the meaning of “the BS transmits/receives the PBCH/PDCCH/PDSCH” is that the BS transmits the broadcast information/DCI/DL data on or through a PBCH/PDCCH/PDSCH, respectively.
  • a radio resource (e.g., a time-frequency resource) scheduled or configured to the UE by the BS for transmission or reception of the PUCCH/PUSCH/PDSCH may be referred to as a PUCCH/PUSCH/PDSCH resource.
  • next-generation RAT is being discussed in consideration of eMBB communication, massive MTC, ultra-reliable and low-latency communication (URLLC), and the like.
  • URLLC ultra-reliable and low-latency communication
  • 3GPP a study on the next-generation mobile communication systems after EPC is being conducted.
  • the corresponding technology is referred to a new RAT (NR) or fifth-generation (5G) RAT, and a system using NR or supporting NR is referred to as an NR system.
  • NR new RAT
  • 5G fifth-generation
  • FIG. 1 illustrates an example of a communication system 1 to which implementations of the present disclosure are applied.
  • the communication system 1 applied to the present disclosure includes wireless devices, BSs, and a network.
  • the wireless devices represent devices performing communication using RAT (e.g., 5G NR or LTE (e.g., E-UTRA)) and may be referred to as communication/radio/5G devices.
  • RAT e.g., 5G NR or LTE (e.g., E-UTRA)
  • the wireless devices may include, without being limited to, a robot 100 a , vehicles 100 b - 1 and 100 b - 2 , an extended reality (XR) device 100 c , a hand-held device 100 d , a home appliance 100 e , an Internet of Things (IoT) device 100 f , and an artificial intelligence (AI) device/server 400 .
  • the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing vehicle-to-vehicle communication.
  • the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone).
  • UAV unmanned aerial vehicle
  • the XR device may include an augmented reality (AR)/virtual reality (VR)/mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc.
  • the hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smartglasses), and a computer (e.g., a notebook).
  • the home appliance may include a TV, a refrigerator, and a washing machine.
  • the IoT device may include a sensor and a smartmeter.
  • the BSs and the network may also be implemented as wireless devices and a specific wireless may operate as a BS/network node with respect to another wireless device.
  • the wireless devices 100 a to 100 f may be connected to a network 300 via BSs 200 .
  • AI technology may be applied to the wireless devices 100 a to 100 f and the wireless devices 100 a to 100 f may be connected to the AI server 400 via the network 300 .
  • the network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network.
  • the wireless devices 100 a to 100 f may communicate with each other through the BSs 200 /network 300
  • the wireless devices 100 a to 100 f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network.
  • the vehicles 100 b - 1 and 100 b - 2 may perform direct communication (e.g. vehicle-to-vehicle (V2V)/Vehicle-to-everything (V2X) communication).
  • the IoT device e.g., a sensor
  • the IoT device may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100 a to 100 f.
  • Wireless communication/connections 150 a and 150 b may be established between the wireless devices 100 a to 100 f and the BSs 200 and between the wireless devices 100 a to 100 f ).
  • the wireless communication/connections such as UL/DL communication 150 a and sidelink communication 150 b (or, device-to-device (D2D) communication) may be established by various RATs (e.g., 5G NR).
  • the wireless devices and the BSs/wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150 a and 150 b .
  • various configuration information configuring processes various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.
  • various signal processing processes e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping
  • resource allocating processes for transmitting/receiving radio signals
  • the first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108 .
  • the processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the below-described/proposed functions, procedures, and/or methods.
  • the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106 .
  • the processor(s) 102 may receive radio signals including second information/signals through the transceiver(s) 106 and then store information obtained by processing the second information/signals in the memory(s) 104 .
  • the memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102 .
  • the memory(s) 104 may perform a part or all of processes controlled by the processor(s) 102 or store software code including instructions for performing the below-described/proposed procedures and/or methods.
  • the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
  • RAT e.g., LTE or NR
  • the processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204 .
  • the memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202 .
  • the memory(s) 204 may perform a part or all of processes controlled by the processor(s) 202 or store software code including instructions for performing the below-described/proposed procedures and/or methods.
  • the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
  • RAT e.g., LTE or NR
  • the transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208 .
  • Each of the transceiver(s) 206 may include a transmitter and/or a receiver.
  • the transceiver(s) 206 is used interchangeably with RF unit(s).
  • the wireless device may represent the communication modem/circuit/chip.
  • the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include narrowband Internet of things for low-power communication as well as LTE, NR, and 6G.
  • the NB-IoT technology may be an example of low-power wide-area network (LPWAN) technologies and implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2.
  • LPWAN low-power wide-area network
  • the wireless communication technology implemented in the wireless devices XXX and YYY of the present disclosure may perform communication based on the LTE-M technology.
  • the LTE-M technology may be an example of LPWAN technologies and called by various names including enhanced machine type communication (eMTC).
  • eMTC enhanced machine type communication
  • One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202 .
  • the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer).
  • layers e.g., functional layers such as a physical (PHY) layer, medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer).
  • PHY physical
  • MAC medium access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • the one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data units (SDUs) according to the functions, procedures, proposals, and/or methods disclosed in the present disclosure.
  • the one or more processors 102 and 202 may generate messages, control information, data, or information according to the functions, procedures, proposals, and/or methods disclosed in the present disclosure.
  • the one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and/or methods disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206 .
  • the one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and/or methods disclosed in the present disclosure.
  • signals e.g., baseband signals
  • the one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers.
  • the one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • the functions, procedures, proposals, and/or methods disclosed in the present disclosure may be implemented using firmware or software, and the firmware or software may be configured to include the modules, procedures, or functions.
  • Firmware or software configured to perform the functions, procedures, proposals, and/or methods disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202 .
  • the functions, procedures, proposals, and/or methods disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.
  • the one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of the present disclosure, to one or more other devices.
  • the one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure, from one or more other devices.
  • the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals.
  • the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices.
  • the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.
  • the one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 .
  • the one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.
  • FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present disclosure.
  • wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules.
  • each of the wireless devices 100 and 200 may include a communication unit 110 , a control unit 120 , a memory unit 130 , and additional components 140 .
  • the communication unit may include a communication circuit 112 and transceiver(s) 114 .
  • the communication circuit 112 may include the one or more processors 102 and 202 and/or the one or more memories 104 and 204 of FIG. 2 .
  • the transceiver(s) 114 may include the one or more transceivers 106 and 206 and/or the one or more antennas 108 and 208 of FIG. 2 .
  • the control unit 120 is electrically connected to the communication unit 110 , the memory 130 , and the additional components 140 and controls overall operation of the wireless devices.
  • the control unit 120 may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit 130 .
  • the control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130 , information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110
  • the additional components 140 may be variously configured according to types of wireless devices.
  • the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit.
  • the wireless device may be implemented in the form of, without being limited to, the robot ( 100 a of FIG. 1 ), the vehicles ( 100 b - 1 and 100 b - 2 of FIG. 1 ), the XR device ( 100 c of FIG. 1 ), the hand-held device ( 100 d of FIG. 1 ), the home appliance ( 100 e of FIG. 1 ), the IoT device ( 100 f of FIG.
  • the wireless device may be used in a mobile or fixed place according to a use-case/service.
  • the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110 .
  • the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140 ) may be wirelessly connected through the communication unit 110 .
  • Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements.
  • the control unit 120 may be configured by a set of one or more processors.
  • control unit 120 may be configured by a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphical processing unit, and a memory control processor.
  • memory 130 may be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.
  • the at least one memory may store instructions or programs, and the instructions or programs may cause, when executed, at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present disclosure.
  • a computer readable storage medium may store at least one instruction or program, and the at least one instruction or program may cause, when executed by at least one processor, the at least one processor to perform operations according to some embodiments or implementations of the present disclosure.
  • a processing device or apparatus may include at least one processor, and at least one computer memory operably connected to the at least one processor.
  • the at least one computer memory may store instructions or programs, and the instructions or programs may cause, when executed, the at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present disclosure.
  • a communication device of the present disclosure includes at least one processor; and at least one computer memory operably connected to the at least one processor and configured to store instructions for causing, when executed, the at least one processor to perform operations according to example(s) of the present disclosure described later.
  • FIG. 4 illustrates an example of a frame structure used in a 3GPP-based wireless communication system.
  • the frame structure of FIG. 4 is purely exemplary and the number of subframes, the number of slots, and the number of symbols, in a frame, may be variously changed.
  • different OFDM numerologies e.g., subcarrier spacings (SCSs)
  • SCSs subcarrier spacings
  • the (absolute time) duration of a time resource including the same number of symbols e.g., a subframe, a slot, or a transmission time interval (TTI)
  • TTI transmission time interval
  • the symbol, the OFDM-based symbol, the OFDM symbol, the CP-OFDM symbol, and the DFT-s-OFDM symbol are used interchangeably.
  • Each half-frame includes 5 subframes and a duration T s (of a single subframe is 1 ms.
  • Subframes are further divided into slots and the number of slots in a subframe depends on a subcarrier spacing.
  • Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix. In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols.
  • the table below shows the number of OFDM symbols (N slot symb ) per slot, the number of slots (N frame,u slot ) per frame, and the number of slots (N subframe,u slot ) per subframe.
  • slots may be indexed within a subframe in ascending order as follows: n u s ⁇ 0, . . . , n subframe,u slot ⁇ 1 ⁇ and indexed within a frame in ascending order as follows: n u s,f ⁇ 0, . . . , n frame,u slot ⁇ 1 ⁇ .
  • FIG. 5 illustrates a resource grid of a slot.
  • the slot includes multiple (e.g., 14 or 12) symbols in the time domain.
  • a resource grid of N size,u grid,x *N RB sc subcarriers and N subframe,u symb OFDM symbols is defined, starting at a common resource block (CRB) N start,u grid indicated by higher layer signaling (e.g. RRC signaling), where N size,u grid,x is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink.
  • N RB sc is the number of subcarriers per RB.
  • N RB sc is typically 12.
  • the carrier bandwidth N size,u grid for the subcarrier spacing configuration u is given to the UE by a higher layer parameter (e.g. RRC parameter).
  • Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a resource element (RE) and one complex symbol may be mapped to each RE.
  • Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index 1 representing a symbol location relative to a reference point in the time domain.
  • an RB is defined by 12 consecutive subcarriers in the frequency domain.
  • RBs are classified into CRBs and physical resource blocks (PRBs).
  • the CRBs are numbered from 0 upwards in the frequency domain for the subcarrier spacing configuration u.
  • the center of subcarrier 0 of CRB 0 for the subcarrier spacing configuration u is equal to ‘Point A’ which serves as a common reference point for RB grids.
  • the PRBs for subcarrier spacing configuration u are defined within a bandwidth part (BWP) and numbered from 0 to N size,u BWP,i ⁇ 1, where i is a number of the BWP.
  • BWP bandwidth part
  • n u PRB n u CRB +N size,u BWP,i , where N size BWP,i is a CRB in which the BWP starts relative to CRB 0.
  • the BWP includes a plurality of consecutive RBs in the frequency domain.
  • the BWP may be a subset of contiguous CRBs defined for a given numerology u i in the BWP i on a given carrier.
  • a carrier may include a maximum of N (e.g., 5) BWPs.
  • the UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through an activated BWP and only a predetermined number of BWPs (e.g., one BWP) among BWPs configured for the UE may be active on the component carrier.
  • the network may configure at least an initial DL BWP and one (if the serving cell is configured with uplink) or two (if supplementary uplink is used) initial UL BWPs.
  • the network may configure additional UL and DL BWPs.
  • VRBs Virtual resource blocks
  • the VRBs may be mapped to PRBs according to non-interleaved mapping.
  • VRB n may be mapped to PRB n for non-interleaved VRB-to-PRB mapping.
  • FIG. 6 illustrates slot structures used in a 3GPP-based system.
  • each slot may have a self-contained structure including i) a DL control channel, ii) DL or UL data, and/or iii) a UL control channel.
  • the first N symbols in a slot may be used to transmit the DL control channel (hereinafter, DL control region) and the last M symbols in a slot may be used to transmit the UL control channel (hereinafter, UL control region), where N and M are integers other than negative numbers.
  • a resource region (hereinafter, data region) between the DL control region and the UL control region may be used to transmit DL data or UL data.
  • Symbols in a single slot may be divided into group(s) of consecutive symbols that may be used as DL symbols, UL symbols, or flexible symbols.
  • information indicating how each symbol in slot(s) is used will be referred to as a slot format.
  • which symbols in slot(s) are used for UL and which symbols in slot(s) are used for DL may be defined by a slot format.
  • the remaining symbols that are not configured as either DL symbols or UL symbols among symbols in the DL-UL pattern are flexible symbols.
  • the UE If the UE is provided with a configuration for the TDD DL-UL pattern, i.e., a TDD UL-DL configuration (e.g., tdd-UL-DL-ConfigurationCommon, or tdd-UL-DLConfigurationDedicated), through higher layer signaling, the UE sets a slot format per slot over a number of slots based on the configuration.
  • a TDD UL-DL configuration e.g., tdd-UL-DL-ConfigurationCommon, or tdd-UL-DLConfigurationDedicated
  • a predetermined number of combinations may be predefined as slot formats and the predefined slot formats may be respectively identified by slot format indexes.
  • the following table shows a part of the predefined slot formats. In the table below, D denotes a DL symbol, U denotes a UL symbol, and F denotes a flexible symbol.
  • the BS may configure a set of slot format combinations applicable to a corresponding serving cell per cell with respect to a set of serving cells through higher layer (e.g., RRC) signaling and cause the UE to monitor a group-common PDCCH for slot format indicator(s) (SFI(s)) through higher layer (e.g., RRC) signaling.
  • SFI DCI DCI carried by the group-common PDCCH for the SFI(s)
  • DCI format 2_0 is used as the SFI DCI.
  • N slot format indexes among slot format indexes for the predefined slot formats may be indicated for the slot format combination.
  • the BS informs the UE of an SFI-RNTI corresponding to an RNTI used for an SFI and the total length of a DCI payload scrambled with the SFI-RNTI.
  • the UE may determine slot format(s) for the corresponding serving cell from an SFI-index for the serving cell among SFI-indexes in the DCI payload in the PDCCH.
  • Symbols indicated as flexible symbols by the TDD DL-UL pattern configuration may be indicated as UL symbols, DL symbols, or flexible symbols by the SFI DCI. Symbols indicated as the DL/UL symbols by the TDD DL-UL pattern configuration are not overridden as the UL/DL symbols or the flexible symbols by the SFI DCI.
  • the UE determines whether each slot is used for UL or DL and determines symbol allocation in each slot based on the SFI DCI and/or on DCI for scheduling or triggering DL or UL signal transmission (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 0_0, DCI format 0_1, DCI format 0_2, or DCI format 2_3).
  • DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 0_0, DCI format 0_1, DCI format 0_2, or DCI format 2_3 e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 0_0, DCI format 0_1, DCI format 0_2, or DCI format 2_3
  • the UE for which carrier aggregation is configured may be configured to use one or more cells. If the UE is configured with a plurality of serving cells, the UE may be configured with one or multiple cell groups. The UE may also be configured with a plurality of cell groups associated with different BSs. Alternatively, the UE may be configured with a plurality of cell groups associated with a single BS. Each cell group of the UE includes one or more serving cells and includes a single PUCCH cell for which PUCCH resources are configured. The PUCCH cell may be a Pcell or an Scell configured as the PUCCH cell among Scells of a corresponding cell group. Each serving cell of the UE belongs to one of cell groups of the UE and does not belong to a plurality of cells.
  • NR frequency bands are defined as two types of frequency ranges, i.e., FR1 and FR2.
  • FR2 is also referred to as millimeter wave (mmW).
  • mmW millimeter wave
  • a PDCCH carries DCI.
  • the PDCCH i.e., DCI
  • DL-SCH downlink shared channel
  • UL-SCH uplink shared channel
  • PCH paging information about a paging channel
  • system information about the DL-SCH information about resource allocation for a control message, such as a random access response (RAR) transmitted on a PDSCH, of a layer (hereinafter, higher layer) positioned higher than a physical layer among protocol stacks of the UE/BS, a transmit power control command, information about activation/deactivation of configured scheduling (CS), etc.
  • RAR random access response
  • DCI including resource allocation information on the DL-SCH is called PDSCH scheduling DCI
  • DCI including resource allocation information on the UL-SCH is called PUSCH scheduling DCI.
  • the DCI includes a cyclic redundancy check (CRC).
  • the CRC is masked/scrambled with various identifiers (e.g., radio network temporary identifier (RNTI)) according to an owner or usage of the PDCCH. For example, if the PDCCH is for a specific UE, the CRS is masked with a UE identifier (e.g., cell-RNTI (C-RNTI)).
  • C-RNTI cell-RNTI
  • the CRC is masked with a paging RNTI (P-RNTI). If the PDCCH is for system information (e.g., system information block (SIB)), the CRC is masked with a system information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with a random access-RNTI (RA-RNTI).
  • SIB system information block
  • RA-RNTI random access-RNTI
  • Cross-carrier scheduling with a carrier indicator field may allow a PDCCH on a serving cell to schedule resources on another serving cell.
  • a PDSCH on a serving cell schedules a PDSCH or a PUSCH on the serving cell, it is referred to as self-carrier scheduling.
  • the BS may provide information about a cell scheduling the cell to the UE. For example, the BS may inform the UE whether a serving cell is scheduled by a PDCCH on another (scheduling) cell or scheduled by the serving cell.
  • the BS may inform the UE which cell signals DL assignments and UL grants for the serving cell.
  • a cell carrying a PDCCH is referred to as a scheduling cell
  • a cell where transmission of a PUSCH or a PDSCH is scheduled by DCI included in the PDCCH, that is, a cell carrying the PUSCH or PDSCH scheduled by the PDCCH is referred to as a scheduled cell.
  • a PDSCH is a physical layer UL channel for UL data transport.
  • the PDSCH carries DL data (e.g., DL-SCH transport block) and is subjected to modulation such as quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64 QAM, 256 QAM, etc.
  • a codeword is generated by encoding a transport block (TB).
  • the PDSCH may carry a maximum of two codewords. Scrambling and modulation mapping per codeword may be performed and modulation symbols generated from each codeword may be mapped to one or more layers. Each layer is mapped to a radio resource together with a DMRS and generated as an OFDM symbol signal. Then, the OFDM symbol signal is transmitted through a corresponding antenna port.
  • a PUCCH means a physical layer UL channel for UCI transmission.
  • the PUCCH carries UCI.
  • the UCI includes the following information.
  • PUCCH resources configured/indicated for/to the UE by the BS for HARQ-ACK, SR, and CSI transmission are referred to as a HARQ-ACK PUCCH resource, an SR PUCCH resource, and a CSI PUCCH resource, respectively.
  • PUCCH formats may be defined as follows according to UCI payload sizes and/or transmission lengths (e.g., the number of symbols included in PUCCH resources). In regard to the PUCCH formats, reference may also be made to Table 5.
  • PUCCH format 1 (PF1 or F1)
  • Configuration for PUCCH format 3 includes the following parameters for a corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, and/or the first symbol for PUCCH transmission.
  • the table below shows the PUCCH formats.
  • the PUCCH formats may be divided into short PUCCH formats (formats 0 and 2) and long PUCCH formats (formats 1, 3, and 4) according to PUCCH transmission length.
  • a PUCCH resource may be determined according to a UCI type (e.g., A/N, SR, or CSI).
  • a PUCCH resource used for UCI transmission may be determined based on a UCI (payload) size.
  • the BS may configure a plurality of PUCCH resource sets for the UE, and the UE may select a specific PUCCH resource set corresponding to a specific range according to the range of the UCI (payload) size (e.g., numbers of UCI bits).
  • K represents the number of PUCCH resource sets (K>1) and N i represents a maximum number of UCI bits supported by PUCCH resource set #i.
  • PUCCH resource set #1 may include resources of PUCCH formats 0 to 1
  • the other PUCCH resource sets may include resources of PUCCH formats 2 to 4 (see Table 6).
  • Configuration for each PUCCH resource includes a PUCCH resource index, a start PRB index, and configuration for one of PUCCH format 0 to PUCCH format 4.
  • the UE is configured with a code rate for multiplexing HARQ-ACK, SR, and CSI report(s) within PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4, by the BS through a higher layer parameter maxCodeRate.
  • the higher layer parameter maxCodeRate is used to determine how to feed back the UCI on PUCCH resources for PUCCH format 2, 3, or 4.
  • a PUCCH resource to be used for UCI transmission in a PUCCH resource set may be configured for the UE through higher layer signaling (e.g., RRC signaling).
  • the UCI type is HARQ-ACK for a semi-persistent scheduling (SPS) PDSCH
  • the PUCCH resource to be used for UCI transmission in the PUCCH resource set may be configured for the UE through higher layer signaling (e.g., RRC signaling).
  • the UCI type is HARQ-ACK for a PDSCH scheduled by DCI
  • the PUCCH resource to be used for UCI transmission in the PUCCH resource set may be scheduled by the DCI.
  • the BS may transmit the DCI to the UE on a PDCCH and indicate a PUCCH resource to be used for UCI transmission in a specific PUCCH resource set by an ACK/NACK resource indicator (ARI) in the DCI.
  • the ARI may be used to indicate a PUCCH resource for ACK/NACK transmission and also be referred to as a PUCCH resource indicator (PRI).
  • the DCI may be used for PDSCH scheduling and the UCI may include HARQ-ACK for a PDSCH.
  • the BS may configure a PUCCH resource set including a larger number of PUCCH resources than states representable by the ARI by (UE-specific) higher layer (e.g., RRC) signaling for the UE.
  • the ARI may indicate a PUCCH resource subset of the PUCCH resource set and which PUCCH resource in the indicated PUCCH resource subset is to be used may be determined according to an implicit rule based on transmission resource information about the PDCCH (e.g., the starting CCE index of the PDCCH).
  • the UE For UL-SCH data transmission, the UE should include UL resources available for the UE and, for DL-SCH data reception, the UE should include DL resources available for the UE.
  • the UL resources and the DL resources are assigned to the UE by the BS through resource allocation.
  • Resource allocation may include time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA).
  • TDRA time domain resource allocation
  • FDRA frequency domain resource allocation
  • UL resource allocation is also referred to as a UL grant and DL resource allocation is referred to as DL assignment.
  • the UL grant is dynamically received by the UE on the PDCCH or in RAR or semi-persistently configured for the UE by the BS through RRC signaling.
  • DL assignment is dynamically received by the UE on the PDCCH or semi-persistently configured for the UE by the BS through RRC signaling.
  • the BS may dynamically allocate UL resources to the UE through PDCCH(s) addressed to a cell radio network temporary Identifier (C-RNTI).
  • C-RNTI cell radio network temporary Identifier
  • the UE monitors the PDCCH(s) in order to discover possible UL grant(s) for UL transmission.
  • the BS may allocate the UL resources using a configured grant to the UE.
  • Two types of configured grants, Type 1 and Type 2 may be used.
  • the BS directly provides the configured UL grant (including periodicity) through RRC signaling.
  • the BS may configure a periodicity of an RRC-configured UL grant through RRC signaling and signal, activate, or deactivate the configured UL grant through the PDCCH addressed to a configured scheduling RNTI (CS-RNTI).
  • CS-RNTI configured scheduling RNTI
  • the PDCCH addressed to the CS-RNTI indicates that the corresponding UL grant may be implicitly reused according to the configured periodicity through RRC signaling until
  • the BS may dynamically allocate DL resources to the UE through PDCCH(s) addressed to the C-RNTI.
  • the UE monitors the PDCCH(s) in order to discover possible DL grant(s).
  • the BS may allocate the DL resources to the UE using SPS.
  • the BS may configure a periodicity of configured DL assignment through RRC signaling and signal, activate, or deactivate the configured DL assignment through the PDCCH addressed to the CS-RNTI.
  • the PDCCH addressed to the CS-RNTI indicates that the corresponding DL assignment may be implicitly reused according to the configured periodicity through RRC signaling until deactivation.
  • the PDCCH may be used to schedule DL transmission on the PDSCH and UL transmission on the PUSCH.
  • DCI on the PDCCH for scheduling DL transmission may include DL resource assignment that at least includes a modulation and coding format (e.g., modulation and coding scheme (MCS)) index I MCS ), resource allocation, and HARQ information, associated with a DL-SCH.
  • DCI on the PDCCH for scheduling UL transmission may include a UL scheduling grant that at least includes a modulation and coding format, resource allocation, and HARQ information, associated with a UL-SCH.
  • MCS modulation and coding scheme
  • DCI format 0_0, DCI format 0_1, or DCI format 0_2 may be used to schedule the PUSCH
  • DCI format 1_0, DCI format 1_1, or DCI format 1_2 may be used to schedule the PDSCH.
  • DCI format 0_2 and DCI format 1_2 may be used to schedule transmission having higher transmission reliability and lower latency requirements than transmission reliability and latency requirement guaranteed by DCI format 0_0, DCI format 0_1, DCI format 1_0, or DCI format 1_1.
  • Some implementations of the present disclosure may be applied to UL data transmission based on DCL format 0_2.
  • Some implementations of the present disclosure may be applied to DL data reception based on DCI format 1_2.
  • FIG. 7 illustrates an example of PDSCH TDRA caused by a PDCCH and an example of PUSCH TDRA caused by the PDCCH.
  • DCI carried by the PDCCH in order to schedule a PDSCH or a PUSCH includes a TDRA field.
  • the TDRA field provides a value m for a row index m+1 to an allocation table for the PDSCH or the PUSCH.
  • Predefined default PDSCH time domain allocation is applied as the allocation table for the PDSCH or a PDSCH TDRA table that the BS configures through RRC signaled pdsch-TimeDomainAllocationList is applied as the allocation table for the PDSCH.
  • Predefined default PUSCH time domain allocation is applied as the allocation table for the PUSCH or a PUSCH TDRA table that the BS configures through RRC signaled pusch-TimeDomainAllocationList is applied as the allocation table for the PUSCH.
  • the PDSCH TDRA table to be applied and/or the PUSCH TDRA table to be applied may be determined according a fixed/predefined rule (e.g., refer to 3GPP TS 38.214).
  • each indexed row defines a DL assignment-to-PDSCH slot offset K 0 , a start and length indicator SLIV (or directly, a start position (e.g., start symbol index S) and an allocation length (e.g., the number of symbols, L) of the PDSCH in a slot), and a PDSCH mapping type.
  • each indexed row defines a UL grant-to-PUSCH slot offset K 2 , a start position (e.g., start symbol index S) and an allocation length (e.g., the number of symbols, L) of the PUSCH in a slot, and a PUSCH mapping type.
  • K 0 for the PDSCH and K 2 for the PUSCH indicate the difference between the slot with the PDCCH and the slot with the PDSCH or PUSCH corresponding to the PDCCH.
  • SLIV denotes a joint indicator of the start symbol S relative to the start of the slot with the PDSCH or PUSCH and the number of consecutive symbols, L, counting from the symbol S.
  • One or two of the symbols of the PDSCH/PUSCH resource may be used as DMRS symbol(s) according to other DMRS parameters.
  • the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot according to RRC signaling.
  • PDSCH/PUSCH mapping type B a DMRS is mapped with respect to the first OFDM symbol of a PDSCH/PUSCH resource.
  • One or two symbols from the first symbol of the PDSCH/PUSCH resource may be used as DMRS symbol(s) according to other DMRS parameters.
  • the DMRS is located at the first symbol allocated for the PDSCH/PUSCH.
  • the PDSCH/PUSCH mapping type may be referred to as a mapping type or a DMRS mapping type.
  • PUSCH mapping type A may be referred to as mapping type A or DMRS mapping type A
  • PUSCH mapping type B may be referred to as mapping type B or DMRS mapping type B.
  • the scheduling DCI includes an FDRA field that provides assignment information about RBs used for the PDSCH or the PUSCH.
  • the FDRA field provides information about a cell for PDSCH or PUSCH transmission to the UE, information about a BWP for PDSCH or PUSCH transmission, and/or information about RBs for PDSCH or PUSCH transmission.
  • configured grant Type 1 there are two types of transmission without dynamic grant: configured grant Type 1 and configured grant Type 2.
  • configured grant Type 1 a UL grant is provided by RRC and stored as a configured UL grant.
  • configured grant Type 2 the UL grant is provided by the PDCCH and stored or cleared as the configured UL grant based on L1 signaling indicating configured UL grant activation or deactivation.
  • Type 1 and Type 2 may be configured by RRC per serving cell and per BWP. Multiple configurations may be active simultaneously on different serving cells.
  • the UE When configured grant Type 1 is configured, the UE may be provided with the following parameters through RRC signaling:
  • the UE Upon configuration of configured grant Type 1 for a serving cell by RRC, the UE stores the UL grant provided by RRC as a configured UL grant for an indicated serving cell and initializes or re-initializes the configured UL grant to start in a symbol according to timeDomainOffset and S (derived from SLIV) and to recur with periodicity.
  • An actual UL grant is provided to the UE by the PDCCH (addressed to the CS-RNTI).
  • the UE may be configured with semi-persistent scheduling (SPS) per serving cell and per BWP by RRC signaling from the BS.
  • SPS semi-persistent scheduling
  • For DL SPS DL assignment is provided to the UE by the PDCCH and stored or cleared based on L1 signaling indicating SPS activation or deactivation.
  • the UE When SPS is configured, the UE may be provided with the following parameters by the BS through RRC signaling:
  • the UE validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or a configured UL grant Type 2 PDCCH.
  • Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 7 and Table 8.
  • Table 7 shows an example of special fields for DL SPS and UL grant Type 2 scheduling activation PDCCH validation
  • Table 8 shows an example of special fields for DL SPS and UL grant Type 2 scheduling release PDCCH validation.
  • FIG. 8 illustrates a HARQ-ACK transmission/reception procedure.
  • the UE may detect a PDCCH in a slot n. Next, the UE may receive a PDSCH in a slot n+K0 according to scheduling information received through the PDCCH in the slot n and then transmit UCI through a PUCCH in a slot n+K1. In this case, the UCI includes a HARQ-ACK response for the PDSCH.
  • the DCI (e.g., DCI format 1_0 or DCI format 1_1) carried by the PDCCH for scheduling the PDSCH may include the following information.
  • a HARQ-ACK response may consist of one bit. If the PDSCH is configured to transmit a maximum of 2 TBs, the HARQ-ACK response may consist of 2 bits when spatial bundling is not configured and one bit when spatial bundling is configured.
  • a HARQ-ACK transmission timing for a plurality of PDSCHs is designated as slot n+K1
  • UCI transmitted in slot n+K1 includes a HARQ-ACK response for the plural PDSCHs.
  • parameters related to a HARQ-ACK payload size that the UE is to report are semi-statically determined by a (UE-specific) higher layer (e.g., RRC) signal.
  • the HARQ-ACK payload size of the semi-static HARQ-ACK codebook e.g., the (maximum) HARQ-ACK payload (size) transmitted through one PUCCH in one slot, may be determined based on the number of HARQ-ACK bits corresponding to a combination (hereinafter, bundling window) of all DL carriers (i.e., DL serving cells) configured for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) for which the HARQ-ACK transmission timing may be indicated.
  • bundling window a combination of all DL carriers (i.e., DL serving cells) configured for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) for which the HARQ-ACK transmission timing may be indicated.
  • the HARQ-ACK information may include possible maximum HARQ-ACK based on the bundling window. That is, HARQ-ACK information of slot #n may include HARQ-ACK corresponding to slot #(n ⁇ k). For example, when k ⁇ 1, 2, 3, 4, 5, 6, 7, 8 ⁇ , the HARQ-ACK information of slot #n may include HARQ-ACK corresponding to slot #(n ⁇ 8) to slot #(n ⁇ 1) regardless of actual DL data reception (i.e., HARQ-ACK of a maximum number).
  • the HARQ-ACK information may be replaced with a HARQ-ACK codebook or a HARQ-ACK payload.
  • a slot may be understood/replaced as/with a candidate occasion for DL data reception.
  • the bundling window may be determined based on the PDSCH-to-HARQ-ACK timing based on a HARQ-ACK slot, and a PDSCH-to-HARQ-ACK timing set may have predefined values (e.g., ⁇ 1, 2, 3, 4, 5, 6, 7, 8 ⁇ ) or may be configured by higher layer (RRC) signaling.
  • RRC higher layer
  • the HARQ-ACK payload size that the UE is to report may be dynamically changed by the DCI etc.
  • DL scheduling DCI may include a counter-DAI (i.e., c-DAI) and/or a total-DAI (i.e., t-DAI).
  • the DAI indicates a downlink assignment index and is used for the BS to inform the UE of transmitted or scheduled PDSCH(s) for which HARQ-ACK(s) are to be included in one HARQ-ACK transmission.
  • the c-DAI is an index indicating order between PDCCHs carrying DL scheduling DCI (hereinafter, DL scheduling PDCCHs), and t-DAI is an index indicating the total number of DL scheduling PDCCHs up to a current slot in which a PDCCH with the t-DAI is present.
  • a method of implementing a plurality of logical networks in a single physical network is considered.
  • the logical networks need to support services with various requirements (e.g., eMBB, mMTC, URLLC, etc.).
  • a physical layer of NR is designed to support a flexible transmission structure in consideration of the various service requirements.
  • the physical layer of NR may change, if necessary, an OFDM symbol length (OFDM symbol duration) and a subcarrier spacing (SCS) (hereinafter, OFDM numerology).
  • Transmission resources of physical channels may also be changed in a predetermined range (in units of symbols).
  • a PUCCH (resource) and a PUSCH (resource) may be configured to flexibly have a transmission length/transmission start timing within a predetermined range.
  • a master information block (MIB) on a PBCH provides parameters (e.g., CORESET #0 configuration) for monitoring a PDCCH for scheduling a PDSCH carrying system information block 1 (SIB1) to the UE.
  • the PBCH may also indicate that there is no associated SIB1.
  • the UE may be provided with not only a frequency range in which the UE may assume that there is no SSB associated with SSB1 but also other frequencies to search for an SSB associated with SIB1.
  • CORESET #0 which is a CORESET for scheduling SIB1 at least, may be configured by the MIB or dedicated RRC signaling.
  • a set of PDCCH candidates monitored by the UE is defined in terms of PDCCH search space sets.
  • the search space set may be a common search space (CS S) set or a UE-specific search space (USS) set.
  • CS S common search space
  • USS UE-specific search space
  • Each CORESET configuration is associated with one or more search space sets, and each search space set is associated with one CORESET configuration.
  • the search space set is determined based on the following parameters provided by the BS to the UE.
  • the parameter monitoringSymbolsWithinSlot may indicate the first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring (e.g., see monitoringSlotPeriodicityAndOffset and duration). For example, if monitoringSymbolsWithinSlot is configured with 14 bits, the most significant (left) bit represents the first OFDM symbol of a slot, and the second most significant (left) bit represents the second OFDM symbol of the slot. In this way, the bits of monitoringSymbolsWithinSlot may represent 14 OFDM symbols of the slot, respectively. For example, among the bits of monitoringSymbolsWithinSlot, bit(s) set to 1 may identify the first symbol(s) of a CORESET in a slot.
  • a UE monitors PDCCH candidates in PDCCH monitoring occasions only.
  • the UE determines a monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot.
  • the UE monitors PDCCH candidates for search space set s for T s consecutive slots, starting from slot n u s,f , and does not monitor PDCCH candidates for search space set s for the next k s ⁇ T s .
  • the following table shows search space sets, related RNTIs, and use cases thereof.
  • the following table shows DCI formats carried by a PDCCH.
  • DCI format 0_0 may be used to schedule a TB-based (or TB-level) PUSCH
  • DCI format 0_1 may be used to schedule a TB-based (or TB-level) PUSCH or a code block group (CBG)-based (or CBG-level) PUSCH
  • DCI format 1_0 may be used to schedule a TB-based (or TB-level) PDSCH
  • DCI format 1_1 may be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH.
  • DCI format 0_0 and DCI format 1_0 have fixed sizes after the BWP size is initially given by RRC.
  • DCI format 0_0 and DCI format 1_0 are fixed in size in fields other than a frequency domain resource assignment (FDRA) field, and the FDRA field may vary in size by configuration of a related parameter by the BS.
  • the size of the DCI field may be changed by various RRC reconfigurations by the BS.
  • DCI format 2_0 may be used to provide dynamic slot format information (e.g., SFI DCI) to the UE
  • DCI format 2_1 may be used to provide DL pre-emption information to the UE
  • DCI format 2_4 may be used to indicate a UL resource on which the UE needs to cancel UL transmission.
  • each of DCI format 0_0 and DCI format 0_1 may include an FDRA field for scheduling a PUSCH
  • each of DCI format 1_0 and DCI format 1_1 may include an FDRA field for scheduling a PDSCH.
  • the number of bits in the FDRA field of each of DCI format 0_0 and DCI format 0_1 may be determined based on N RB UL,BWP , which is the size of an active or initial UL BWP.
  • the number of bits in the FDRA field of each of DCI format 1_0 and DCI format 1_1 may be determined based on N RB DL,BWP , which is the size of an active or initial DL BWP.
  • URLLC has the low-latency and high-reliability requirements of a user-plane delay of 0.5 ms and transmission of X bytes of data within 1 ms at or below an error rate of 10 ⁇ 5 .
  • eMBB is characterized by a large traffic capacity, a file size equal to or less than tens to hundreds of bytes, and sporadic occurrence. Therefore, eMBB requires transmission at a maximum transmission rate with minimum overhead of control information, whereas URLLC requires a relatively short transmission duration (e.g., 2 symbols) and a reliable transmission method.
  • a reference time may be a basic unit for scheduling a specific physical channel, and a reference time unit may be changed according to the number of symbols and/or a subcarrier spacing (SCS) in the scheduling time unit.
  • SCS subcarrier spacing
  • Some embodiments/implementations of the present disclosure are described in the context of a slot or mini-slot as a reference time unit, for convenience of description.
  • a slot may be, for example, a basic scheduling unit used for general data traffic (e.g., eMBB).
  • a mini-slot may have a shorter duration than a slot in the time domain, and may be a scheduling basic unit used for a special purpose or for a special communication scheme (e.g., URLLC, an unlicensed band, or millimeter wave).
  • a special communication scheme e.g., URLLC, an unlicensed band, or millimeter wave.
  • the embodiment(s)/implementation(s) of the present disclosure may also be applied to physical channel transmission/reception in mini slots for eMBB or physical channel transmission/reception in slots for URLLC or other communication schemes.
  • the reliability of PUSCH/PDSCH transmission needs to be higher than that of existing PUSCH/PDSCH transmission. Repeated transmission of the PUSCH/PDSCH may be considered to improve the reliability of PUSCH/PDSCH transmission.
  • FIG. 9 illustrates an example of types of repeated transmissions. Two types of repeated transmissions may be scheduled.
  • repetition of the PUSCH/PDSCH may be applied to PUSCH/PDSCH transmission based on dynamic grants/DL assignments through a PDCCH.
  • Repetition of the PUSCH/PDSCH may also be applied to PUSCH/PDSCH transmission based on a configured grant.
  • Repetitions to be applied to PUSCH/PDSCH transmission may be indicated or configured to a UE by a BS.
  • a repetition factor K may be indicated to the UE through L1 signaling by the BS or may be configured to the UE through higher layer signaling by the BS.
  • the UE may repeat transmission/reception of a transport block across K transmission/reception opportunities.
  • the repetition factor may also be referred to as a repeated transmission factor.
  • the UE may be configured to perform multi-slot PUSCH transmission or multi-slot PDSCH reception.
  • the UE may be configured by the BS to apply allocation of the same symbol(s) across K consecutive slots where K is an integer greater than 1.
  • the UE may apply allocation of the same slot(s) in each of the K consecutive slots and may repeat transmission/reception of the transport block (TB) across the K consecutive slots.
  • a time in which one TB is to be transmitted/received may be referred to as a transmission occasion/reception occasion.
  • the UE may perform PDSCH reception/PUSCH transmission in K consecutive DL slot(s)/subslot(s) starting from a slot/subslot n. In this, the UE may assume that all K PDSCH receptions/transmissions are performed in the same resource block(s).
  • transmission/reception on the slot may be omitted from multi-slot PUSCH/PDSCH transmission/reception.
  • PUSCH/PDSCH repetition performed by applying the same resource allocation to a plurality of consecutive slots may be referred to as a PUSCH/PDSCH repetition type A.
  • the PUSCH/PDSCH repetition type A when the UE receives resource allocation for wireless transmission from the BS, it may be possible to repeatedly use a time-frequency resource defined in one slot in units of slots.
  • the time duration for K repeated transmissions for one TB may not exceed a time duration induced by a period P of the configured grant.
  • the UE may transmit/receive the PUSCH/PDSCH according to a redundancy version (RV) sequence only at a predetermined position among a plurality of PUSCH/PDSCH resources for PUSCH/PDSCH repetition.
  • RV redundancy version
  • the UE may start initial transmission of the TB at the first transmission opportunity among K transmission opportunities of K repetitions.
  • resource allocation information may be provided through an RRC configuration rather than the PDCCH.
  • DCI e.g., a timeDomainAllocation value m (i.e., a TDRA value), frequencyDomainAllocation (i.e., an FDRA value), or mcsAndTBS in a type 1 CG configuration
  • an interpretation result may vary depending on which DCI format is assumed for interpretation of the corresponding DCI.
  • different TDRA may be determined depending on which DCI format is used for a TDRA table to interpret the TDRA value, and even for the same mcsAndTBS value, a different MCS value may be determined depending on which MCS table is used.
  • a configured grant or semi-static scheduling e.g., configured grant or semi-persistent scheduling (SPS)
  • SPS semi-persistent scheduling
  • a plurality of DCI formats may be configured for UL or DL scheduling and may be used in activation/release or retransmission for the configured scheduling.
  • the UE may use a related RRC parameter and/or a predetermined value or table in order to interpret each DCI format.
  • the BS may configure a separate RRC parameter for each DCI format, and the UE and the BS may apply different RRC parameters when the respective DCI formats are interpreted.
  • the BS may configure a separate RRC parameter for the configured scheduling in addition to an RRC parameter for the dynamic scheduling to the UE.
  • the BS and the UE may also transmit and receive information included in one DCI format through RRC signaling, and thus DCI included in the RRC signaling needs to be interpreted in the end.
  • the BS may transfer information, to be transferred by one DCI format, to the UE through a higher layer parameter rrc-ConfiguredUplinkGrant that provides a configuration for “configured grant” transmission with a fully RRC-configured UL grant.
  • the UE and the BS may use a predetermined DCI format and, in this case, needs to determine which RRC parameter is to be used.
  • a method of determining a DCI format to be used to interpret the configured scheduling and methods of selecting an RRC parameter for interpreting the configured scheduling when the BS and the UE transmit and receive DCI through L1 signaling (e.g., a PDCCH) and/or higher layer signaling for the configured scheduling will be described.
  • a method of determining a bit length of each field included in a DCI format received through L1 signaling e.g., a PDCCH
  • selecting an RRC parameter for interpreting the bit length e.g., a timeDomainAllocation value m (i.e., a TDRA value), frequencyDomainAllocation (i.e., a FDRA value), or mcsAndTBS in a type 1 CG configuration
  • DCI e.g., a timeDomainAllocation value m (i.e., a TDRA value), frequencyDomainAllocation (i.e., a FDRA value), or mcsAndTBS in a type 1 CG configuration
  • Some implementations of the present disclosure may be performed in different ways depending on a used DCI format.
  • the operation of receiving parameter(s) to be applied to each DCI format through RRC signaling from the BS by the UE may be implemented by, for example, the device of FIG. 2 or 3 .
  • the one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive a parameter to be applied to each DCI format through RRC signaling, and the one or more transceivers 106 may receive parameter(s) to be applied to each of the DCI formats through the RRC signaling from the BS.
  • the higher layer parameters may be received in an RRC Connection Setup procedure of an initial access procedure.
  • the operation of receiving the CG configuration from the BS through RRC signaling by the UE may be implemented by, for example, the device of FIG. 2 or 3 .
  • the one or more processor 102 may control the one or more transceivers 106 and/or the one or more memories 104 to receive RRC signal including the CG configuration and the one or more transceivers 106 may receive the RRC signaling from the BS.
  • rrc-ConfiguredUplinkGrant may include, for example, the following parameters:
  • the UE may interpret parameter(s) or DCI (in the CG configuration) transmitted through RRC depending on the CG type of the CG of the CG configuration.
  • the UE may interpret DCI included in a PDCCH according to an implementation of the present disclosure after receiving the PDCCH for activating the CG (S 1004 b ).
  • the operation of determining a type of the CG according to whether the rrc-ConfiguredUplinkGrant parameter is included in the CG configuration and interpreting DCI according to each type by the UE may be implemented by the device of FIG. 2 or 3 .
  • the one or more processors 102 may determine the type of the CG according to whether the rrc-ConfiguredUplinkGrant parameter is present in the CG configuration and may interpret DCI included in the rrc-ConfiguredUplinkGrant or the PDCCH according to each type.
  • the UE may perform PUSCH transmission using the activated CG through a series of processes (S 1005 a and S 1005 b ). For example, the UE may interpret DCI according to a type of the CG recognized by the UE based on whether the rrc-ConfiguredUplinkGrant is included in the CG configuration, and may transmit, to the BS based on the interpreted DCI, the PUSCH on a UL resource that is based on the activated CG.
  • the operation of transmitting the PUSCH on a resource based on the activated CG by the UE may be implemented by the device of FIG. 2 or 3 .
  • the one or more processors 102 may control the one or more transceivers 106 and/or the one or more memories 104 to transmit the PUSCH on a resource based on the activated configured grant, and the one or more transceivers 106 may transmit the PUSCH on the resource based on the activated CG.
  • the UE may not expect other DCI formats except for a specific DCI format among a plurality of DCI formats configured for activation, release and/or retransmission to be used for activation and/or release. Alternatively, the UE may expect only a specific DCI format to be used for activation and/or release.
  • the specific DCI format may be configured commonly to a plurality of configured grants through higher layer signaling of the BS or separately for each configured grant.
  • the BS may configure a parameter for selecting one value among ⁇ formats0-0-And-0-1, formats0-0-And-0-2, and formats0-0-And-0-1-And-0-2 ⁇ to the UE and may limit a DCI format to be used in the configured grant.
  • the BS informs the UE to use formats0-0-And-0-1 among ⁇ formats0-0-And-0-1, formats0-0-And-0-2, and formats0-0-And-0-1-And-0-2 ⁇
  • only a DCI format 0_0 and a DCI format 0_1 may be limited to be used to activate/release a type 2 CG.
  • an applied DCI format may be limited to be included in a set of specific DCI formats.
  • the BS may transmit the set of the DCI formats to be applied separately for each of the configured grants or commonly to the configured grants to the UE, and the UE may select one of the DCI formats included in the received set and may apply the selected DCI format to transmission of the configured grant.
  • the BS may transmit a parameter value indicating each of the DCI formats to be applied to transmission of the configured grant to the UE, and the UE may select a specific DCI format to be applied to transmission of the configured grant by selecting a specific parameter value among the received parameter values.
  • the DCI formats may be DCI formats included in the DCI format set including the DCI formats to be applied to the configured grant.
  • the specific DCI format may be a DCI format that satisfies the following conditions.
  • the UE When the UE is semi-statically allocated a type 2 CG PUSCH transmission through valid activation DCI, the UE may expect DCI having certain characteristics to be used for activation and release.
  • the UE may consider a CORESET and/or a search space of a PDCCH, on which corresponding DCI is received, for validating a PDCCH reception for activation or release. For example, when a priority of transmission through the corresponding configured grant is configured in a certain CG configuration and a priority of dynamic scheduling is determined according to the CORESET and/or the search space on which the DCI of the dynamic scheduling is received, the UE may expect DCI for a certain CG configuration to be received only in a CORESET and/or a search space having the same priority of dynamic scheduling as the priority configured in the CG configuration.
  • receiving DCI in the CORESET and/or search space having the same priority as the priority in the CG configuration may be a necessary condition for determining valid activation or release DCI.
  • receiving DCI in the CORESET and/or search space having the same priority as the priority in the CG configuration may be used as one of conditions for determining the validity of the activation DCI or the release DCI.
  • the UE may use RRC parameter(s) included in the CG configuration in DCI interpretation.
  • the specific DCI format may be a DCI format having each field with higher configurability than an existing DCI format, for example, a DCI format 0_2.
  • implementation A2-1 and/or implementation A2-2 may be considered.
  • the corresponding parameter may be applied to DCI interpretation for the CG configuration.
  • the DCI field may be interpreted using the same method as a method of interpreting a corresponding field when a corresponding DCI format is used in dynamic scheduling (e.g., a DCI format 0_2 having a CRC scrambled by a C-RNTI).
  • the UE may use an RA type used in the corresponding DCI format, not the RA type of the CG configuration. That is, when the RA type based on the CG configuration and the RA type based on the DCI format are different from each other, the UE may use the RA type based on the DCI format.
  • a resource assignment field of the time or frequency domain may be interpreted using the same method as a method when the corresponding DCI format is used in dynamic scheduling.
  • the UE may assume that the corresponding DCI field is omitted even if the corresponding DCI format is used in the CG configuration.
  • the omitted DCI field value is assumed to be ‘0’ or ‘1’ and is not interpreted and the corresponding DCI format is used in dynamic scheduling (e.g., a DCI format 0_2 with CRC scrambled by a C-RNTI)
  • the same value or operation as a value or operation assumed when the corresponding DCI field is omitted may be used for the corresponding field.
  • an RRC parameter or a determination method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format 0_2 with CRC scrambled by a C-RNTI) may be used.
  • the UE may use a predefined/configured MCS table or a mcs-table parameter configured to determine the same may be used for a DCI format 0_2 with CRC scrambled by a C-RNTI, with respect to the DCI format 0_2 with CRC scrambled by the C-RNTI.
  • the UE when receiving parameter(s) that is different from or is not included in the CG configuration through RRC signaling, the UE may perform PUSCH transmission using the parameter(s) received through RRC signaling.
  • the DCI field may be partially omitted through RRC signaling.
  • the UE may use an RRC parameter or interpretation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format 0_2 with CRC scrambled by a C-RNTI) rather than using the RRC parameter included in the CG configuration in DCI interpretation.
  • the specific DCI format may be a DCI format (e.g., a DCI format 0_2) having each field with higher configurability than an existing DCI format. More specifically, the following may be considered.
  • the UE may exceptionally use the RRC parameter included in the CG configuration with respect to the specific RRC parameter related to a certain field.
  • the specific RRC parameter may be at least one of the followings:
  • an RRC parameter for dynamic scheduling may be freely configured while multiplexing different configured grants with each other or using a configured grant in which different UEs share a resource by using the same RRC parameter as dynamic scheduling for ease of DCI interpretation and also maintaining some flexibility and configurability of the configured grant.
  • the UE When the UE is semi-statically allocated a type 1 CG PUSCH transmission by receiving a CG configuration including specific RRC parameter(s) (e.g., rrc-ConfiguredUplinkGrant) for resource allocation, the UE may assume a specific DCI format in order to interpret the specific RRC parameter(s).
  • the specific DCI format may be configured commonly to a plurality of configured grants or separately for each configured grant, through higher layer signaling of the BS.
  • the BS may configure a parameter for selecting one value among ⁇ formats0-0, formats0-1, and formats0-2 ⁇ to the UE and may assume the corresponding configured DCI format for interpretation of rrc-ConfiguredUplinkGrant of the configured grant.
  • the UE may assume a specific DCI format (e.g., a DCI format 0_1) for this as a default. That is, when the UE does not receive the parameter for selecting the specific DCI format from the BS, the UE may assume a specific DCI format (e.g., a DCI format 0_1) in order to interpret rrc-ConfiguredUplinkGrant of the configured grant.
  • a specific DCI format (e.g., a DCI format 0_1) may be assumed for interpretation of rrc-ConfiguredUplinkGrant of the configured grant.
  • the specific DCI format may be a DCI format that satisfies the following condition.
  • the specific DCI format when a plurality of DCI formats satisfy the corresponding condition, may be assumed to be a DCI format having a larger size or a DCI format 0_1.
  • the specific RRC parameter may be a set of a plurality of parameters that refer to respective fields of a certain DCI format.
  • the specific RRC parameter is a set of certain RRC parameters, different sets may be used according to the selected specific DCI format.
  • the RRC configuration e.g., a TDRA table or an MCS table
  • the RRC configuration used to interpret the parameter(s) of rrc-ConfiguredUplinkGrant may not need to be separately provided to the UE, and thus signaling overhead may be reduced.
  • the UE may be capable of interpreting a TDRA value and MCS value in the type 1 CG based on the TDRA table and the MCS table configured for the specific DCI format, and thus signaling overhead may be reduced.
  • the BS may not need to explicitly signal the DCI format to the UE, and thus signaling overhead may be reduced.
  • the BS may set a repetition type B for transmission that is based on the DCI format 0_1, may set a repetition type A for the DCI format 0_2, may set a repetition scheme B for transmission based on the type 1 CG configuration, and may perform transmission to the UE, and accordingly, may inform the UE that the parameter(s) of rrc-ConfiguredUplinkGrant needs to be interpreted based on the RRC configuration for the DCI format 0_1.
  • the BS may not need to explicitly signal a DCI format related to the type 1 CG configuration to the UE, and thus signaling overhead may be reduced.
  • the DCI format assumed to interpret rrc-ConfiguredUplinkGrant included in the CG configuration is determined to be fixed, if the repetition scheme for transmission based on the DCI format is different from the repetition scheme based on the CG configuration, there may be a limit in performing scheduling by the BS.
  • the BS may need to perform resource allocation for the type 1 CG only in resource allocation (e.g., TDRA entries) to be applied to both the repetition type A and the repetition type B.
  • resource allocation e.g., time domain resource allocation
  • the BS needs to configure the repetition scheme of the type 1 CG to be always the same as the repetition scheme for the DCI format fixed to be used to interpret the type 1 CG.
  • the UE interprets parameter(s) of rrc-ConfiguredUplinkGrant in the type 1 CG configuration based on the RRC configuration for the DCI format that satisfies the specific condition, scheduling flexibility may be ensured compared with the case in which the DCI format related to the type 1 CG configuration is fixed to the specific DCI format.
  • implementation of the UE and the BS may be simplified while reducing unnecessary signaling overhead between the UE and the BS.
  • FIG. 11 is a diagram showing an example of a UE operation according to some implementations of the present disclosure.
  • the UE may receive an RRC configuration for a DCI format A and an RRC configuration for a DCI format B (S 1101 ) and may receive a CG configuration for CG-based PUSCH transmission (through RRC signaling) (S 1102 ).
  • Each of the RRC configuration for the DCI format A and the RRC configuration for the DCI format B may include a parameter indicating a repetition scheme for PUSCH transmission that is dynamically scheduled by the corresponding DCI format.
  • the CG configuration may include a parameter indicating a repetition scheme for the CG-based PUSCH transmission.
  • DCI for the PUSCH transmission may not be determined based on a DCI format of an activation PDCCH, and a specific DCI format needs to be assumed in order to interpret some or all (e.g., resource allocation information) of the parameters of rrc-ConfiguredUplinkGrant in the CG configuration.
  • some or all (e.g., resource allocation information) of the parameters of rrc-ConfiguredUplinkGrant in the CG configuration may be interpreted based on a DCI format having an RRC configuration in which the same repetition scheme as the repetition scheme set for the CG configuration is set.
  • the UE may interpret the resource allocation information based on the RRC configuration for the DCI format having an RRC configuration in which a repetition scheme is set to the repetition type B. For example, when the repetition scheme for the DCI format A (e.g., a DCI format 0_1) is set to the repetition type B, the UE may interpret the resource allocation information based on the RRC configuration for the DCI format A to determine a resource for the CG-based PUSCH transmission (S 1104 a ).
  • the repetition scheme for the DCI format A e.g., a DCI format 0_1
  • the UE may apply a TDRA value in the CG configuration to the TDRA table for the DCI format A to determine a resource for CG PUSCH transmission.
  • the UE may interpret the resource allocation information based on the RRC configuration for the DCI format B (e.g., a DCI format 0_2) to determine a resource for the CG-based PUSCH transmission (S 1104 b ).
  • the RRC configuration for the DCI format B e.g., a DCI format 0_2
  • the UE may apply a TDRA value in the CG configuration to a TDRA table for the DCI format B to determine a resource for CG PUSCH transmission.
  • the UE may perform PUSCH transmission based on the determined resource.
  • implementations A4-1 and/or A4-2 may also be additionally considered.
  • the UE may use an RRC parameter or interpretation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format with CRC scrambled by a C-RNTI) rather than using an RRC parameter included in the CG configuration to interpret a parameter based on the specific DCI format.
  • a specific parameter e.g., rrc-ConfiguredUplinkGrant
  • RRC parameter or interpretation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format with CRC scrambled by a C-RNTI) rather than using an RRC parameter included in the CG configuration to interpret a parameter based on the specific DCI format.
  • the UE may interpret the specific parameter based on an RRC parameter referenced when the DCI format A is used in dynamic scheduling in the case in which the specific RRC parameter needs to be interpreted based on the DCI format A and the UE may interpret the specific parameter with reference to an RRC parameter included in the corresponding CG configuration when the specific parameter needs to be interpreted based on the DCI format B.
  • the UE may interpret the specific parameter based on a parameter in an RRC configuration for the DCI format 0_1, and when the BS informs the UE that some parameters (e.g., a resource allocation type in the frequency domain) are not configured by RRC and the DCI format 0_0 using a predefined value (e.g., a resource allocation type 0) is a DCI format related to a CG configuration, the UE may interpret the specific parameter with reference to the RRC parameter (e.g., a resource allocation type included in a CG configuration) included in the CG configuration.
  • the RRC parameter e.g., a resource allocation type included in a CG configuration
  • an RRC parameter applied when the DCI format 0_1 is used for dynamic scheduling i.e., when the DCI format 0_1 is transmitted through a PDCCH
  • an RRC parameter applied when the DCI format 0_1 is used for dynamic scheduling may be applied to interpret the specific parameter.
  • the specific DCI format may be a DCI format (e.g., a DCI format 0_2) having each field with higher configurability than an existing DCI format.
  • an RRC parameter related to the specific DCI format may not be included in the specific RRC parameter.
  • the certain parameter may be an optional parameter.
  • the UE may perform the same operation as the case in which a DCI field related to the omitted parameter is omitted.
  • the UE may also perform the same operation when an RRC parameter indicating the corresponding field is omitted.
  • the specific field when a specific field of a specific DCI format is omitted by an RRC parameter, the specific field may be recognized by the UE as being a default. Similarly, even if the RRC parameter for omitting the specific field is not transmitted or is not included in the CG configuration, the UE may interpret the specific field in the same way as in the case in which the specific field is omitted by the RRC parameter.
  • a joint activation/release operation of one of a plurality of configured grants may be considered.
  • a configured grant that has the same configured grant index as a value indicated by an HARQ process number field included in DCI may be activated/released.
  • a UE having a plurality of configured grant configurations may use the following RRC parameter or RRC parameter set.
  • RRC parameter or RRC parameter set When a value of each field included in the DCI is generated, interpreted, and assumed, different options may be used.
  • a joint activation/release operation for simultaneously activating/releasing a plurality of configured grants may be considered.
  • the UE may release, through one received DCI, resource allocation of one or more configured grant configurations that is previously activated.
  • a plurality of configured grant configurations may be related to one DCI.
  • a RRC parameter e.g., entry of Type2Configuredgrantconfig-ReleaseStateList
  • a value indicated by a HARQ process number field included in the DCI may include one or more configured grant indexes.
  • the UE may use the following RRC parameter or RRC parameter set in order to interpret DCI.
  • RRC parameter or RRC parameter set When a value of each field included in the DCI is generated, interpreted, and assumed, different options may be used.
  • the UE may also determine the length of a DCI field using the same RRC parameter/parameter set. For example, when the same ConfiguredGrantConfig as an HARQ ID included in DCI is assumed for DCI interpretation, the length of the FDRA field may be determined through the resourceAllocation, rbg-Size included in ConfiguredGrantConfig and the length of an RB of a UL bandwidth part. In this case, when a DCI format 0_2 is used, an additional parameter (e.g., resourceAllocation-ForDCIFormat0_2, resourceAllocationType1GranularityForDCI-Format0-2-r16) included in the pusch-config may be exceptionally used. According to this, the RRC parameter used is included in only in 0_2, and thus the UE may assume a more accurate DCI length, and the BS may not introduce an unnecessary parameter in order to adjust a DCI size.
  • the RRC parameter used is included in only in 0_2, and thus the UE may assume a more accurate
  • the UE may not expect that the size of a corresponding field of DCI for a configured grant configuration is larger than the size of a corresponding field of dynamic scheduling, and may expect that a field is padded to ‘0’ to have the same value of the corresponding field of dynamic scheduling when the size of each field of DCI for the configured grant configuration and DCI for dynamic scheduling is small.
  • the length of a DCI field determined for activation/release DCI of SPS/CG may also be different from the length of a corresponding DCI field that is based on dynamic scheduling.
  • the UE may determine a method of making the field lengths to be the same using the following method.
  • the UE performs padding of ‘0’ when performing bit padding in the corresponding field in activation/release DCI of a configured grant.
  • the UE performs padding of ‘1’ when performing bit padding in the corresponding field in activation/release DCI of a configured grant.
  • the UE performs padding of ‘1’ when performing bit padding in a corresponding field in activation/release DCI of a configured grant.
  • the UE and the BS may perform activation/release DCI interpretation and validation without need to determine the accurate length of a DCI field during generation, interpretation, and validation of activation/release DCI.
  • FIG. 12 is a diagram showing an example of a BS operation according to some implementation(s) of the present disclosure.
  • the BS may determine a DCI format and RRC parameter to be used to transmit a configured grant.
  • an example of the BS operation according to some implementations of the present disclosure will be described.
  • the BS operation according to implementations of the present disclosure is not limited to the following example.
  • the BS may configure RRC parameter(s) for each of a plurality of DCI formats to the UE and may transmit the configured RRC parameter(s) to the UE (S 1201 ).
  • the BS may configure higher layer parameters indicating a frequency domain allocation type, an RBG size, whether to apply transform precoding, a TDRA table, a frequency hopping method, a repetition scheme, a number of repetitions, a DM-RS configuration, an MCS table, an RV field bit length, an HARQ process number field bit length, and/or beta-offset, for transmission based on the corresponding DCI format for each of the plurality of DCI formats and may transmit the configured RRC parameter(s) to the UE through RRC signaling.
  • the operation of configuring a parameter to be applied to each of the DCI formats and transmitting the configured parameter to the UE through RRC signaling to the UE by the BS may be implemented by, for example, the device of FIG. 2 or 3 .
  • the one or more processors 102 may configure a parameter to be applied to each of the DCI formats and may control the one or more transceivers 106 and/or the one or more memories 104 to transmit the configured parameter to the UE through RRC signaling, and the one or more transceivers 106 may transmit the configured parameter to the UE through RRC signaling.
  • the higher layer parameters may be transmitted in an RRC Connection Setup procedure in an initial access procedure.
  • the BS may configure a plurality of parameters to be included in a CG configuration to the UE and may transmit the CG configuration including the plurality of configured parameters to the UE through RRC signaling (S 1202 ).
  • the BS may transmit an RRC configuration for each DCI format and a CG configuration to the UE separately or together or may transmit the CG configuration before the RRC configuration for each DCI format.
  • the operation of configuring the plurality of parameters to be included in the CG configuration and transmitting the CG configuration including the plurality of configured parameter to the UE through RRC signaling may be implemented by, for example, the device of FIG. 2 or 3 .
  • the one or more processors 102 may configure the plurality of parameters included in the CG configuration and may control the one or more transceivers 106 and/or the one or more memories 104 to transmit the CG configuration including the plurality of configured parameters to the UE, and the one or more transceivers 106 may transmit the CG configuration including the plurality of configured parameters to the UE through RRC signaling.
  • the BS may transmit DCI for activation of the CG through the PDCCH (S 1204 ).
  • the operation of transmitting the DCI through the PDCCH by the BS when a parameter rrc-ConfiguredUplinkGrant is not present in the CG configuration may be implemented by, for example, the device of FIG. 2 or 3 .
  • the one or more processors 102 may control the one or more transceivers 106 and/or the one or more memories 104 to transmit the DCI through the PDCCH, and when a parameter rrc-ConfiguredUplinkGrant is not present in the CG configuration, the one or more transceivers 106 may transmit the DCI through the PDCCH.
  • rrc-ConfiguredUplinkGrant is not included in the CG configuration (Yes in S 1203 ), in other words, when a CG based on the CG configuration is a type 1 CG, the BS may assume the CG to be assumed based on the CG configuration being transmitted.
  • the BS may receive PUSCH transmission through the configured grant from the UE (S 1205 ).
  • the operation of receiving the PUSCH through the configured grant by the BS may be implemented by, for example, the device of FIG. 2 or 3 .
  • the one or more processors 102 may control the one or more transceivers 106 and/or the one or more memories 104 to receive the PUSCH through the configured grant, and the one or more transceivers 106 may receive the PUSCH through the configured grant.
  • the BS may use only a specific DCI format among a plurality of DCI formats configured for activation, release, and/or retransmission.
  • the specific DCI format may be configured commonly to a plurality of configured grants through higher layer signaling of the BS or separately for each configured grant.
  • the BS may configure a parameter for selecting one value among ⁇ formats0-0-And-0-1, formats0-0-And-0-2, and formats0-0-And-0-1-And-0-2 ⁇ to the UE and may limit a DCI format to be used in the configured grant.
  • the BS informs the UE to use formats0-0-And-0-1 among ⁇ formats0-0-And-0-1, formats0-0-And-0-2, and formats0-0-And-0-1-And-0-2 ⁇
  • only a DCI format 0_0 and a DCI format 0_1 may be limited to be used to activation/release a type 2 CG.
  • the BS may transmit a parameter for selecting a DCI format to be used to transmit a configured grant among a plurality of DCI formats to the UE, and the UE may select a specific DCI format to be applied to transmission of the configured grant based on the parameter received from the BS.
  • the same DCI format may be applied to transmissions of the plurality of configured grants or different DCI formats may be applied thereto.
  • an applied DCI format may be limited to a specific DCI format included in a set of specific DCI formats.
  • the BS may transmit the set of the DCI formats to be applied separately for each of the configured grants or commonly to the configured grants to the UE, and the UE may select one of the DCI formats included in the received set and may apply the selected DCI format to transmission of the configured grant.
  • the BS may transmit a parameter value indicating each of the DCI formats to be applied to transmission of the configured grant to the UE, and the UE may select a specific DCI format to be applied to transmission of the configured grant by selecting a specific parameter value among the received parameter values.
  • the DCI formats may be DCI formats included in the DCI format set including the DCI formats to be applied to the configured grant.
  • the BS may transmit a DCI format set ⁇ formats0-0-And-0-1, formats0-0-And-0-2, and formats0-0-And-0-1-And-0-2 ⁇ or may transmit parameter values indicating the respective DCI formats included in the DCI format set to the UE.
  • the UE may select a specific DCI format in the DCI format set and may apply the selected DCI format to the configured grant.
  • the UE may select one of the parameter values and may apply a specific DCI format indicated by the selected parameter value to the configured grant.
  • the specific DCI format may be a DCI format that satisfies the following conditions.
  • the BS When the BS semi-statically allocates type 2 CG PUSCH transmission to the UE through valid activation DCI, the BS may use DCI having certain characteristics to be used for activation and release.
  • the BS may consider transmission in a specific CORESET and/or search space during PDCCH transmission for activation or release. For example, when a priority of transmission through the corresponding configured grant is configured in a certain CG configuration and a priority of dynamic scheduling is determined according to the CORESET and/or the search space on which the DCI of the dynamic scheduling is transmitted, the BS may transmit valid activation or release DCI for a certain CG configuration only in a CORESET and/or a search space having the same priority of dynamic scheduling as the priority configured in the CG configuration. In other words, the BS may transmit the valid activation DCI or the release DCI to the US in the CORESET and/or the search space having the same priority as the priority in the CG configuration.
  • the BS may use RRC parameter(s) included in the CG configuration in DCI generation.
  • the specific DCI format may be a DCI format having each field with higher configurability than an existing DCI format, for example, a DCI format 0_2.
  • an implementation A2-1 and/or an implementation A2-2 may be considered.
  • the corresponding parameter may be applied to DCI interpretation for the CG configuration.
  • the DCI field may be interpreted using the same method as a method of interpreting a corresponding field when a corresponding DCI format is used in dynamic scheduling (e.g., a DCI format 0_2 having a CRC scrambled by a C-RNTI).
  • the BS may use an RA type used in the corresponding DCI format, not the RA type of the CG configuration. That is, when the RA type based on the CG configuration and the RA type based on the DCI format are different from each other, the BS may use the RA type based on the DCI format.
  • a resource assignment field of the time or frequency domain may be generated using the same method as a method when the corresponding DCI format is used in dynamic scheduling.
  • the BS may omit the corresponding DCI field even if the corresponding DCI format is used in the CG configuration.
  • the omitted DCI field value is assumed to be ‘0’ or ‘1’ and is not interpreted and the corresponding DCI format is used in dynamic scheduling (e.g., a DCI format 0_2 with CRC scrambled by a C-RNTI)
  • the same value or operation as a value or operation assumed when the corresponding DCI field is omitted may be used for the corresponding field.
  • an RRC parameter or a determination method used when the specific DCI format is used in dynamic scheduling (e.g., DCI format 0_2 with CRC scrambled by a C-RNTI) may be used.
  • the BS may use a predefined/configured MCS table or a mcs-table parameter configured to determine the same may be used for a DCI format 0_2 with CRC scrambled by a C-RNTI, with respect to the DCI format 0_2 with CRC scrambled by the C-RNTI.
  • the BS when transmitting parameter(s) that is different from or is not included in the CG configuration through RRC signaling, the BS may perform PUSCH reception using the parameter(s) transmitted through RRC signaling.
  • the DCI field may be partially omitted through RRC signaling.
  • the BS may use an RRC parameter or interpretation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format 0_2 with CRC scrambled by a C-RNTI) rather than using the RRC parameter included in the CG configuration in DCI generation.
  • the specific DCI format may be a DCI format (e.g., a DCI format 0_2) having each field with higher configurability than an existing DCI format. More specifically, the following may be considered.
  • the BS may exceptionally use the RRC parameter included in the CG configuration with respect to the specific RRC parameter related to a certain field.
  • the specific RRC parameter may be at least one of the following:
  • the BS may freely configure an RRC parameter for dynamic scheduling while multiplexing different configured grants with each other or allocating the same resource as a configured grant to a plurality of UEs by using the same RRC parameter as dynamic scheduling for ease of DCI interpretation and also maintaining some flexibility and configurability of the configured grant.
  • the BS may assume a specific DCI format in order to generate the specific RRC parameter.
  • the specific DCI format may be configured commonly to a plurality of configured grants or separately for each configured grant, through higher layer signaling of the BS.
  • the BS may configure a parameter for selecting one value among ⁇ formats0-0, formats0-1, and formats0-2 ⁇ to the UE and may assume the corresponding configured DCI format for interpretation of rrc-ConfiguredUplinkGrant of the configured grant.
  • the BS may assume a specific DCI format (e.g., a DCI format 0_1) for this as a default. That is, when the BS does not transmit the parameter for selecting the specific DCI format from the BS, the UE may assume a specific DCI format (e.g., a DCI format 0_1) in order to generate rrc-ConfiguredUplinkGrant of the configured grant.
  • the specific DCI format may be a DCI format that satisfies the following condition.
  • the specific DCI format when a plurality of DCI formats satisfy the corresponding condition, may be assumed to be a DCI format having a larger size or a DCI format 0_1.
  • the specific RRC parameter may be a set of a plurality of parameters that refer to respective fields of a certain DCI format.
  • the specific RRC parameter is a set of certain RRC parameters, different sets may be used according to the selected specific DCI format.
  • the BS may use an RRC parameter or interpretation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format with CRC scrambled by a C-RNTI) rather than using an RRC parameter included in the CG configuration to generate a parameter based on the specific DCI format.
  • a specific parameter e.g., rrc-ConfiguredUplinkGrant
  • the BS may use an RRC parameter or interpretation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format with CRC scrambled by a C-RNTI) rather than using an RRC parameter included in the CG configuration to generate a parameter based on the specific DCI format.
  • the BS may use an RRC parameter or generation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format with CRC scrambled by a C-RNTI) rather than using an RRC parameter included in the CG generation to generate a parameter based on the corresponding DCI format.
  • a specific parameter e.g., rrc-ConfiguredUplinkGrant
  • the BS may use an RRC parameter or generation method used when the specific DCI format is used in dynamic scheduling (e.g., a DCI format with CRC scrambled by a C-RNTI) rather than using an RRC parameter included in the CG generation to generate a parameter based on the corresponding DCI format.
  • the BS may generate the specific parameter based on an RRC parameter referenced when the DCI format A is used in dynamic scheduling in the case in which the specific RRC parameter needs to be interpreted based on the DCI format A and the BS may generate the specific parameter with reference to an RRC parameter included in the corresponding CG configuration when the specific parameter needs to be interpreted based on the DCI format B.
  • the BS may generate the specific parameter based on a parameter in an RRC configuration for the DCI format 0_1, and when the BS informs the UE that some parameters (e.g., a resource allocation type in the frequency domain) are not configured by RRC and the DCI format 0_0 using a predefined value (e.g., a resource allocation type 0) is a DCI format related to a CG configuration, the BS may generate the specific parameter with reference to the RRC parameter (e.g., a resource allocation type included in a CG configuration) included in the CG configuration.
  • the RRC parameter e.g., a resource allocation type included in a CG configuration
  • an RRC parameter applied when the DCI format 0_1 is used for dynamic scheduling i.e., when the DCI format 0_1 is transmitted through a PDCCH
  • the specific DCI format may be a DCI format (e.g., a DCI format 0_2) having each field with higher configurability than an existing DCI format.
  • an RRC parameter related to the specific DCI format may not be included in the specific RRC parameter.
  • the certain parameter may be an optional parameter.
  • the BS may perform the same operation as the case in which a DCI field related to the omitted parameter is omitted.
  • the BS may also perform the same operation when an RRC parameter indicating the corresponding field is omitted.
  • the specific field when a specific field of a specific DCI format is omitted by an RRC parameter, the specific field may be recognized by the BS as being a default. Similarly, even if the RRC parameter for omitting the specific field is not transmitted or is not included in the CG configuration, the BS may interpret the specific field in the same way as in the case in which the specific field is omitted by the RRC parameter.
  • the BS that allocates a plurality of configured grant configurations may use the following RRC parameter or RRC parameter set.
  • RRC parameter or RRC parameter set When a value of each field included in the DCI is generated, interpreted, and assumed, different options may be used.
  • a joint activation/release operation for simultaneously activating/releasing a plurality of configured grants may be considered.
  • the BS may transmit one DCI to release resource allocation of one or more configured grant configurations that is previously activated for the UE.
  • a plurality of configured grant configurations may be related to one DCI.
  • an RRC parameter e.g., entry of Type2Configuredgrantconfig-ReleaseStateList
  • a value indicated by an HARQ process number field included in DCI may include one or more configured grant indexes.
  • the BS and the UE may use the following RRC parameter or RRC parameter set in order to generate and interpret DCI.
  • RRC parameter or RRC parameter set When a value of each field included in the DCI is generated, interpreted, and assumed, different options may be used
  • the BS may also determine the length of a DCI field using the same RRC parameter/parameter set. For example, when the same ConfiguredGrantConfig as an HARQ ID included in DCI is assumed for DCI interpretation, the length of the FDRA field may be determined through the resourceAllocation, rbg-Size included in ConfiguredGrantConfig and the length of an RB of a UL bandwidth part. In this case, when a DCI format 0_2 is used, an additional parameter (e.g., resourceAllocation-ForDCIFormat0_2, resourceAllocationType1GranularityForDCI-Format0-2-r16) included in the pusch-config may be exceptionally used. According to this, the RRC parameter used is included in only in 0_2, and thus the UE may assume a more accurate DCI length, and the BS may not introduce an unnecessary parameter in order to adjust a DCI size.
  • the RRC parameter used is included in only in 0_2, and thus the UE may assume a more accurate
  • the UE may not expect that the size of a corresponding field of DCI for a configured grant configuration is larger than the size of a corresponding field of dynamic scheduling, and may expect that a field is padded to ‘0’ to have the same value of the corresponding field of dynamic scheduling when the size of each field of DCI for the configured grant configuration and DCI for dynamic scheduling is small.
  • the BS may not configure the size of a corresponding field of DCI of a configured grant configuration to be larger than the size of a corresponding field of dynamic scheduling and may expect the size of the corresponding field of DCI of the configured grant configuration is the same as the corresponding field of dynamic scheduling by padding ‘0’ to the field when the size of the corresponding field of DCI of the configured grant configuration is smaller than the corresponding field of dynamic scheduling.
  • the length of the DCI field determined for activation/release DCI of the SPS/CG may also be different from the length of the corresponding DCI field that is based on dynamic scheduling. In this case, the BS may make the lengths of fields using the following method.
  • the UE performs padding of ‘0’ when performing bit padding in the corresponding field in activation/release DCI of a configured grant.
  • the UE performs padding of ‘1’ when performing bit padding in the corresponding field in activation/release DCI of a configured grant.
  • the UE performs padding of ‘1’ when performing bit padding in a corresponding field in activation/release DCI of a configured grant.
  • the UE and the BS may perform activation/release DCI interpretation and validation without need to determine the accurate length of a DCI field during generation, interpretation, and validation of activation/release DCI.
  • FIG. 13 illustrates a flow of signal transmission/reception between a UE and a BS according to some implementations of the present disclosure.
  • the UE may receive an RRC configuration for each of a plurality of DCI formats and a CG configuration from the BS (S 1301 a , S 1301 b , and S 1301 c ).
  • the UE may assume a specific DCI format and may interpret the specific parameter to determine a resource for a configured grant according to some implementation(s) of the present disclosure ( 51303 a ).
  • the UE may receive activation DCI from the BS through a PDCCH and may interpret the activation DCI to determine the resource for the configured grant according to some implementation(s) of the present disclosure ( 51303 b ).
  • the UE may perform PUSCH transmission using the determined resource (S 1305 ).
  • the BS and the UE may expect DCI used in configured scheduling to be generated/interpreted and transmitted/received according to some implementations of the present disclosure.
  • the BS may minimize an unnecessary RRC configuration to reduce signaling overhead and may prevent malfunction between the UE and the BS during a process of generating and transmitting DCI.
  • implementation complexity may be reduced, and the UE may receive and interpret DCI for a grant configured with ambiguity.
  • Implementations of the present disclosure may be separately applied or one or more implementations may be combined and applied.
  • the UE may perform operations for transmission of a PUSCH according to some implementations of the present disclosure.
  • the UE may include at least one transceiver, at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure.
  • a processing device for the UE may include at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure.
  • a computer-readable storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processors to perform the operations according to some implementations of the present disclosure.
  • the operations may comprise, for example: receiving an RRC configuration including first configuration information for a first DCI format and second configuration information for a second DCI format, receiving a configured grant configuration including a repetition scheme and resource allocation information, determining resource allocation of a configured grant based on i) configuration information including the same repetition scheme as the repetition scheme in the configured grant configuration among the first configuration information and the second configuration information, and ii) the resource allocation information, and performing PUSCH transmission based on the resource allocation.
  • Each of the first configuration information and the second configuration information may include a TDRA table.
  • the configured grant may be a type 1 configured grant.
  • the BS may perform operations in order to receive a PUSCH from the UE according to some implementations of the present disclosure.
  • the BS may include at least one transceiver, at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure.
  • a processing device for the BS may include at least one processor, and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processors to perform operations according to some implementations of the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
US17/735,930 2019-11-08 2022-05-03 Method, user equipment, apparatus, and computer-readable storage medium for PUSCH transmission, and method and base station for PUSCH reception Active US11638282B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/735,930 US11638282B2 (en) 2019-11-08 2022-05-03 Method, user equipment, apparatus, and computer-readable storage medium for PUSCH transmission, and method and base station for PUSCH reception

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR20190142607 2019-11-08
KR10-2019-0142607 2019-11-08
US202062978807P 2020-02-19 2020-02-19
US202062982026P 2020-02-26 2020-02-26
PCT/KR2020/015638 WO2021091350A1 (ko) 2019-11-08 2020-11-09 Pusch 전송 방법, 사용자기기, 장치, 및 컴퓨터 판독 가능 저장 매체, 그리고 pusch 수신 방법 방법 및 기지국
US17/735,930 US11638282B2 (en) 2019-11-08 2022-05-03 Method, user equipment, apparatus, and computer-readable storage medium for PUSCH transmission, and method and base station for PUSCH reception

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/015638 Continuation WO2021091350A1 (ko) 2019-11-08 2020-11-09 Pusch 전송 방법, 사용자기기, 장치, 및 컴퓨터 판독 가능 저장 매체, 그리고 pusch 수신 방법 방법 및 기지국

Publications (2)

Publication Number Publication Date
US20220264608A1 US20220264608A1 (en) 2022-08-18
US11638282B2 true US11638282B2 (en) 2023-04-25

Family

ID=75848984

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/735,930 Active US11638282B2 (en) 2019-11-08 2022-05-03 Method, user equipment, apparatus, and computer-readable storage medium for PUSCH transmission, and method and base station for PUSCH reception

Country Status (6)

Country Link
US (1) US11638282B2 (ja)
EP (1) EP4057750A4 (ja)
JP (1) JP7304490B2 (ja)
KR (1) KR102541190B1 (ja)
CN (1) CN114651513A (ja)
WO (1) WO2021091350A1 (ja)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220183021A1 (en) * 2019-03-25 2022-06-09 Telefonaktiebolaget Lm Ericsson (Publ) Resource allocation in mu-mimo ofdma wireless systems
US11758551B2 (en) * 2020-04-24 2023-09-12 Qualcomm Incorporated Cancellation of transmission occasions
US20220039070A1 (en) * 2020-07-29 2022-02-03 Qualcomm Incorporated Techniques for releasing multiple sets of semi-persistent scheduling and configured grant resources
US20220303995A1 (en) * 2021-03-19 2022-09-22 Qualcomm Incorporated Frequency multiplexing for control information over shared channel resources
US11778626B2 (en) * 2021-04-08 2023-10-03 Qualcomm Incorporated CBG grouping and multiple MCS based CBG in downlink single DCI TRP transmission for a full-duplex UE
WO2023204924A1 (en) * 2022-04-19 2023-10-26 Qualcomm Incorporated Multi-shared channel scheduling for extended reality
WO2024011380A1 (en) * 2022-07-11 2024-01-18 Shenzhen Tcl New Technology Co., Ltd. Wireless communication method and base station for extended reality traffic
WO2024019407A1 (ko) * 2022-07-19 2024-01-25 주식회사 케이티 상향링크 데이터 처리 방법 및 그 장치
CN117768072A (zh) * 2022-07-29 2024-03-26 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190132862A1 (en) 2017-10-26 2019-05-02 Comcast Cable Communications, Llc Activation and Deactivation of Configured Grant
US20190149365A1 (en) 2018-01-12 2019-05-16 Intel Corporation Time domain resource allocation for mobile communication
US20210007087A1 (en) * 2019-07-01 2021-01-07 FG Innovation Company Limited Method and apparatus for performing repetition transmissions in wireless communication system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3954147B1 (en) 2019-07-17 2023-02-15 Fg Innovation Company Limited Method and apparatus for handling repetitions of physical uplink shared channel (pusch) transmission in wireless communication system
CN111246582B (zh) 2020-01-20 2023-04-07 展讯半导体(南京)有限公司 信息发送方法及装置、信息接收方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190132862A1 (en) 2017-10-26 2019-05-02 Comcast Cable Communications, Llc Activation and Deactivation of Configured Grant
US20190149365A1 (en) 2018-01-12 2019-05-16 Intel Corporation Time domain resource allocation for mobile communication
US20210007087A1 (en) * 2019-07-01 2021-01-07 FG Innovation Company Limited Method and apparatus for performing repetition transmissions in wireless communication system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Ericsson, "Enhancement of Configured Grant for NR URLLC", 3GPP TSG RAN WG1 Meeting #98bis, Oct. 14-20, 2019, R1-1910550.
Huawei, HiSilicon, "Enhanced UL configured grant transmission", 3GPP TSG RAN WG1 meeting #98bis, Oct. 14-20, 2019, R1-1910071.
Nokia, Nokia Shanghai Bell, "On Enhanced UL Configured Grant Transmission for NR URLLC and activation/release of multiple SPS configurations", 3GPP TSG RAN WG1 Meeting #98bis, Oct. 14-20, 2019, R1-1910869.

Also Published As

Publication number Publication date
JP7304490B2 (ja) 2023-07-06
KR20220097936A (ko) 2022-07-08
KR102541190B1 (ko) 2023-06-13
US20220264608A1 (en) 2022-08-18
WO2021091350A1 (ko) 2021-05-14
EP4057750A1 (en) 2022-09-14
JP2023500887A (ja) 2023-01-11
EP4057750A4 (en) 2024-01-10
CN114651513A (zh) 2022-06-21

Similar Documents

Publication Publication Date Title
US20220159692A1 (en) Method for transmitting harq-ack codebook, user equipment, device and storage medium, method for receiving harq-ack codebook, and base station
US11638282B2 (en) Method, user equipment, apparatus, and computer-readable storage medium for PUSCH transmission, and method and base station for PUSCH reception
US20220191903A1 (en) Method, user equipment, device, and storage medium for transmitting pusch, and method and base station for receiving pusch
US20230006798A1 (en) Method for transmitting harq-ack codebook, user equipment, device and storage medium, and method and base station for receiving harq-ack codebook
US20210409182A1 (en) Method for transmitting harq-ack information, and communication device
US20220399960A1 (en) Method, user equipment, apparatus and computer-readable storage medium for transmitting harq-ack codebook, and method and base station for receiving harq-ack codebook
US20230155744A1 (en) Harq-ack transmission method, user equipment and storage medium, and harq-ack reception method and base station
US20230035066A1 (en) Method, user device and storage medium for transmitting uplink channel, and method and base station for receiving uplink channel
US11737119B2 (en) Method and base station for transmitting downlink control information, and user equipment, apparatus, and storage medium for receiving downlink control information
US11855783B2 (en) Method for transmitting HARQ-ACK information, and communication device
US20220132495A1 (en) Method and user equipment for performing uplink transmission, and method for performing uplink reception
US11770825B2 (en) Method, user equipment, processing device, storage medium, and computer program for transmitting uplink channel, and method and base station for receiving uplink channel
US12021633B2 (en) Method, user equipment, processing device, storage medium, and computer program for receiving downlink channel, and method and base station for transmitting downlink channel
US20230309090A1 (en) Method for transmitting uplink channel, user device, processing device, storage medium and computer program, and method for receiving uplink channel, and base station
US20210345370A1 (en) Method and communication apparatus for transmitting scheduling request information
US20230180245A1 (en) Method, user equipment, processing device, storage medium, and computer program for transmitting uplink channel, and method and base station for receiving uplink channel
US11882571B2 (en) Method, user equipment, processing device, storage medium, and computer program for receiving downlink channel, and method and base station for transmitting downlink channel
US20230396298A1 (en) Method, user equipment, processing device, storage medium and computer program for transmitting channel state information report, and method and base station for receiving channel state information report
US20230261807A1 (en) Method and user equipment for transmitting harq-ack information, and base station for receiving harq-ack information
US20240073887A1 (en) Method for monitoring uplink cancellation instruction, user equipment, apparatus, computer-readable storage medium, method for transmitting uplink cancellation instruction, and base station
US20230092884A1 (en) Method for transmitting power headroom report, user equipment, processing device, storage medium, and computer program
US20230036564A1 (en) Harq-ack information transmission method, user equipment, and storage medium, and harq-ack information reception method and base station
US11742996B2 (en) Method, user equipment and processing device for receiving downlink channel, and method for transmitting downlink channel
US20220329391A1 (en) Method, user equipment, processing device, storage medium and computer program for transmitting harq-ack information, and method and base station for receiving harq-ack information
US20230300829A1 (en) Method, user equipment, processing device, storage medium, and computer program for transmitting pusch, and method and base station for receiving pusch

Legal Events

Date Code Title Description
AS Assignment

Owner name: LG ELECTRONICS INC., KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAE, DUCKHYUN;LEE, HYUNHO;KIM, SEONWOOK;SIGNING DATES FROM 20211206 TO 20211214;REEL/FRAME:059802/0036

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction