Method for transmitting / receiving control information and device therefor

Abstract

A method, according to one embodiment of the present specification, comprises the steps of: receiving first DCI including first part information; and receiving second DCI including second part information from a base station. The first DCI includes information on a time window related to a valid period of the first DCI. In the time window, monitoring related to the first DCI is skipped, and only monitoring related to the second DCI is performed.

Description

Method and apparatus for transmitting and receiving control information

[0001] This specification relates to a method and apparatus for transmitting and receiving control information.

[0002] 5G NR is a successor technology to LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities.

[0004] In conventional 4G / 5G wireless communication systems, control information (e.g., DL / UL scheduling related information) is transmitted through a single DCI. At this time, the following problem occurs. Even when DL / UL scheduling is performed by changing only a part of the control information, the DCI containing the entire control information must be transmitted again.

[0005] The purpose of this specification is to propose a method for solving the aforementioned problems.

[0006] The technical problems to be solved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0007] A method according to an embodiment of the present specification for solving the aforementioned problem comprises the steps of receiving first downlink control information (DCI) containing first part information from a base station and receiving a second DCI containing second part information from the base station. The first DCI includes information regarding a time window related to the validity period of the first DCI. Within the time window, monitoring related to the first DCI is skipped, and monitoring related to the second DCI is performed. Even if there is a partial change in the control information during the time window, only the second DCI is transmitted and only monitoring related to the second DCI is performed. Therefore, an increase in signaling overhead due to the retransmission of the entire control information can be prevented.

[0008] According to an embodiment of the present specification, control information is transmitted through two linked DCIs, and within a specified time window, only monitoring for receiving the second DCI is performed (only the second DCI is transmitted). Accordingly, control information signaling overhead can be reduced compared to existing communication systems. Specifically, DL resource efficiency can be improved by reducing DCI overhead. Additionally, since only monitoring of the second DCI is performed during the period when the first DCI is valid and monitoring of the first DCI is omitted, terminal power consumption can be reduced.

[0009] The effects obtainable in this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0010] Figure 1 shows an example of a frame structure in an NR system.

[0011] Figure 2 shows an example of a resource grid in NR.

[0012] Figure 3 illustrates physical channels used in 3GPP systems and general signal transmission.

[0013] Figure 4 illustrates a single REG structure.

[0014] Figure 5 illustrates a non-interleaved CCE-REG mapping type.

[0015] Figure 6 illustrates an interleaved CCE-REG mapping type.

[0016] Figure 7 illustrates scheduling in the case where multi-cells are merged.

[0017] Figure 8 illustrates the HARQ-ACK process for DL ​​data.

[0018] Figure 9 illustrates the PUSCH transmission process.

[0019] FIG. 10 illustrates the transmission of two linked DCIs according to one embodiment of the present specification.

[0020] FIG. 11 is a flowchart for explaining a method performed by a terminal according to one embodiment of the present specification.

[0021] FIG. 12 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.

[0022] FIG. 13 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0023] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0024] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0025] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0026] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0027] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0028] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0029] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0030] In this specification, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0031] In this specification, "set or defined" may be interpreted as being set or pre-configured to the device through pre-defined signaling (e.g., SIB, MAC, RRC) from a base station or network. In this specification, "set or defined" may be interpreted as being pre-configured to the device.

[0032] In this specification, user equipment (UE) may refer to portable devices, wireless devices, etc. In this specification, base station (BS) may refer to a radio access network (RAN) node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a portable device, a wireless device, etc.

[0033] The technology proposed in this specification can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0034] The technology proposed in this specification can be implemented as 6G wireless technology and applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0035] In the following, the downlink (DL) refers to communication from a base station to a terminal, and the uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter may be part of the base station and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal and the receiver may be part of the base station. The base station may be referred to as the first communication device and the terminal as the second communication device. The base station (BS) may be replaced by terms such as fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), Access Point (AP), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device.

[0036] The following technologies can be used in various wireless access systems such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of the UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0037] For clarity of explanation, the description is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical scope of this specification is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onwards. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is referred to as LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is referred to as LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onwards. LTE / NR may be referred to as 3GPP systems. "xxx" indicates a specific standard document number. LTE / NR may be collectively referred to as 3GPP systems.

[0038] Regarding background technology, terms, abbreviations, etc. used in the description of this specification, reference may be made to matters described in standard documents published prior to this specification. For example, the following documents may be referenced.

[0039] 3GPP NR

[0040] - 3GPP TS 38.211: Physical channels and modulation

[0041] - 3GPP TS 38.212: Multiplexing and channel coding

[0042] - 3GPP TS 38.213: Physical layer procedures for control

[0043] - 3GPP TS 38.214: Physical layer procedures for data

[0044] - 3GPP TS 38.215: Physical layer measurements

[0045] - 3GPP TS 38.300: NR and NG-RAN Overall Description

[0046] - 3GPP TS 38.304: User Equipment (UE) procedures in idle mode and in RRC inactive state

[0047] - 3GPP TS 38.321: Medium Access Control (MAC) protocol

[0048] - 3GPP TS 38.322: Radio Link Control (RLC) protocol

[0049] - 3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

[0050] - 3GPP TS 38.331: Radio Resource Control (RRC) protocol

[0051] - 3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

[0052] - 3GPP TS 37.340: Multi-connectivity; Overall description

[0053] - 3GPP TS 23.287: Application layer support for V2X services; Functional architecture and information flows

[0054] - 3GPP TS 23.501: System Architecture for the 5G System

[0055] - 3GPP TS 23.502: Procedures for the 5G System

[0056] - 3GPP TS 23.503: Policy and Charging Control Framework for the 5G System; Stage 2

[0057] - 3GPP TS 24.501: Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3

[0058] - 3GPP TS 24.502: Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks

[0059] - 3GPP TS 24.526: User Equipment (UE) policies for 5G System (5GS); Stage 3

[0060] As more communication devices require larger communication capacities, the need for enhanced mobile broadband communication compared to existing radio access technology is emerging. Furthermore, massive Machine Type Communications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. In addition, communication system designs that consider services and terminals sensitive to reliability and latency are being discussed. Accordingly, the introduction of next-generation radio access technology considering eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed, and for convenience, this technology is referred to as NR in this specification. NR is an expression representing an example of 5G radio access technology (RAT).

[0061] A new RAT system including NR uses an OFDM transmission method or a similar transmission method. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Or, a single cell may support multiple numerologies. That is, terminals operating with different numerologies can coexist within a single cell.

[0062] Numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing to an integer N.

[0063] NR (New Rat) Numerology and Frame Structure

[0064] In an NR system, multiple numerologies can be supported. Here, a numerology can be defined by subcarrier spacing and CP (Cyclic Prefix) overhead. In this case, the multiple subcarrier spacings are the base subcarrier spacing as an integer N (or, It can be derived by scaling. In addition, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band.

[0065] In addition, various frame structures based on multiple numerologies can be supported in the NR system.

[0066] Below, we examine the OFDM (Orthogonal Frequency Division Multiplexing) numerology and frame structure that can be considered in an NR system.

[0067] Many OFDM numerologies supported by the NR system can be defined as shown in Table 1. The μ and circular prefix for the bandwidth part are obtained from the RRC parameters provided by the BS.

[0068]

[0069] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0070] The NR frequency band is defined by two types of frequency ranges called FR1 and FR2. FR1 is the sub 6 GHz range, and FR2 is the above 6 GHz range, which can refer to millimeter wave (mmW).

[0071] Table 2 below illustrates the definition of the NR frequency band.

[0072]

[0073] Regarding the frame structure in an NR system, the size of various fields in the time domain is It is expressed as a multiple of the time unit of. Here, And, It is. Downlink and uplink transmission is It consists of radio frames having intervals. Here, each radio frame is It consists of 10 subframes having a period of . In this case, there may be one set of frames for the uplink and one set of frames for the downlink.

[0074] The transmission of uplink frame number i from a terminal (User Equipment, UE) is earlier than the start of the corresponding downlink frame at that terminal You must start beforehand.

[0075] Numerology Regarding this, slots within a subframe They are numbered in increasing order, and within the wireless frame They are numbered in increasing order. One slot is It consists of consecutive OFDM symbols, It is determined by the numerology and slot configuration used. Slot in a subframe The start is the OFDM symbol in the same subframe. It is aligned with the start of and time.

[0076] Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in the downlink slot or uplink slot can be used.

[0077] Table 3 shows the number of OFDM symbols per slot in normal CP ( ), number of slots per wireless frame ( ), number of slots per subframe( Table 3 shows the number of OFDM symbols per slot, the number of slots per wireless frame, and the number of slots per subframe in the extended CP.

[0078]

[0079]

[0080] FIG. 1 illustrates an example of a frame structure in an NR system. FIG. 1 is for convenience of explanation only and is not intended to limit the scope of this specification.

[0081] In the case of Table 4, as an example where μ=2, i.e., the subcarrier spacing (SCS) is 60 kHz, referring to Table 3, one subframe (or frame) may include four slots, and the slots of one subframe={1,2,4} shown in Fig. 1 are examples, and the number of slot(s) that may be included in one subframe can be defined as in Table 3.

[0082] In addition, the mini-slot may consist of 2, 4, or 7 symbols, or more or fewer symbols.

[0083] Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, and carrier parts may be considered.

[0084] Below, we will examine in detail the physical resources mentioned above that can be considered in an NR system.

[0085] Figure 2 shows an example of a supported resource grid in NR.

[0086] Referring to Fig. 2, for each subcarrier interval setting and carrier, N size,μ grid *N RB sc individual subcarriers and A resource grid of OFDM symbols is defined, where N size,μ grid is indicated by RRC signaling from BS. N size,μ grid The subcarrier spacing setting μ can vary not only between the uplink and downlink but also between the uplink and downlink.

[0087] Numerology One resource grid can be configured per antenna port p. Numerical Each element of the resource grid for and antenna port p is referred to as a resource element, and index pairs It is uniquely identified by. Here, is an index in the frequency domain, and refers to the location of a symbol within a subframe. When referring to resource elements in a slot, the index pair This is used. Here, am.

[0088] Numerology resource elements for and antenna port p is a complex value ...corresponds to. Where there is no risk of confusion, or where a specific antenna port or numerology is not specified, the indices p and can be dropped, and the resulting complex value is or This can be. In addition, the physical resource block is in the frequency domain It is defined by continuous subcarriers.

[0089] Considering that the UE may not be able to support the wide bandwidth to be supported in the NR system at once, the UE may be configured to operate in a portion of the cell's frequency bandwidth (hereinafter, bandwidth part, BWP).

[0090] The resource blocks of the NR system include physical resource blocks defined within the bandwidth part and common resource blocks numbered upward from 0 in the frequency domain for the subcarrier spacing setting μ.

[0091] Point A serves as a common reference point for the resource block grid and can be obtained as follows.

[0092] - offsetToPointA for the PCell downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the UE for initial cell selection, and is expressed in resource block units assuming a 15kHz subcarrier interval for FR1 and a 60kHz subcarrier interval for FR2;

[0093] - absoluteFrequencyPointA represents the frequency-location of point A as expressed in ARFCN (absolute radio-frequency channel number).

[0094] Common resource blocks set subcarrier spacing In the frequency domain for , it is numbered from 0 upwards.

[0095] Subcarrier spacing setting The center of subcarrier 0 of common resource block 0 for coincides with 'point A'. Common resource block number in the frequency domain and subcarrier spacing settings The resource elements (k,l) for can be given as shown in Equation 1 below.

[0096]

[0097] Here, Is It can be defined relative to point A to correspond to a subcarrier centered at point A. Physical resource blocks within the bandwidth part (BWP) start from 0 Numbers are assigned up to, is the BWP number. Physical resource block in BWP i and common resource blocks The relationship between them can be given by the following mathematical formula 2.

[0098]

[0099] Here, can be a common resource block that starts relative to common resource block 0.

[0100] A slot contains multiple symbols in the time domain. For example, in the case of a standard CP, one slot contains 14 symbols, and in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interlacs (simply interlacs) can be defined in the frequency domain. An interlac m∈{0, 1, ..., M-1} can be composed of (common) RBs {m, M+m, 2M+m, 3M+m, ...}. M represents the number of interlacs. A Bandwidth Part (BWP) is defined as multiple consecutive RBs (e.g., physical RB, PRB) in the frequency domain and can correspond to a single OFDM numerology (e.g., SCS(u), CP length, etc.). A carrier wave may contain up to N (e.g., 5) BWPs. Data communication is performed through the active BWPs, and only one BWP can be active for a single terminal within a single cell / carrier wave. In the resource grid, each element is referred to as a Resource Element (RE), and one modulation symbol can be mapped to it.

[0101] Physical channels and general signal transmission

[0102] Figure 3 illustrates physical channels used in a 3GPP system and general signal transmission. In a wireless communication system, a terminal receives information from a base station via a downlink (DL) and transmits information to the base station via an uplink (UL). The information transmitted and received by the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.

[0103] When the terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S301). To do this, the terminal receives a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell ID. After that, the terminal receives a Physical Broadcast Channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, during the initial cell search phase, the terminal receives a Downlink Reference Signal (DL RS) to check the downlink channel status.

[0104] A terminal that has completed initial cell search can obtain more specific system information by receiving a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) according to the information carried on the PDCCH (S302).

[0105] Meanwhile, when connecting to a base station for the first time or when there are no wireless resources available for signal transmission, the terminal may perform a Random Access Procedure (RACH) with respect to the base station (S303 to S306). To this end, the terminal transmits a specific sequence as a preamble through a Physical Random Access Channel (PRACH) (S303 and S305), and may receive a response message (RAR (Random Access Response) message) for the preamble through a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, a Contention Resolution Procedure may additionally be performed (S306).

[0106] A terminal that has performed the procedure described above may subsequently perform PDCCH / PDSCH reception (S307) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S308) as a general uplink / downlink signal transmission procedure. In particular, the terminal may receive Downlink Control Information (DCI) through the PDCCH.

[0107] The UE monitors a set of PDCCH candidates at monitoring occasions configured in one or more control element sets (CORESETs) on the serving cell according to the corresponding search space configurations. The set of PDCCH candidates to be monitored by the UE is defined in terms of the search space sets, and the search space sets may be common search space sets or UE-specific search space sets. A CORESET consists of a set of (physical) resource blocks having durations of 1 to 3 OFDM symbols. The network may be configured so that the UE has multiple CORESETs. The UE monitors PDCCH candidates within one or more search space sets. Here, monitoring means attempting to decode the PDCCH candidate(s) within the search space. If the UE succeeds in decoding one of the PDCCH candidates within the search space, the UE determines that it has detected a PDCCH in that candidate and performs PDSCH reception or PUSCH transmission based on the DCI within the detected PDCCH.

[0108] PDCCH can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH. Here, the DCI on PDCCH includes a downlink assignment (i.e., a DL grant) that includes at least modulation and coding formats and resource allocation information associated with a downlink shared channel, or an uplink grant that includes modulation and coding formats and resource allocation information associated with an uplink shared channel. The format of the DCI varies depending on its intended use.

[0109] Meanwhile, control information transmitted by the terminal to the base station via the uplink or received by the terminal from the base station may include downlink / uplink ACK / NACK signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Index), RI (Rank Indicator), etc. The terminal may transmit the control information such as the above-mentioned CQI / PMI / RI via PUSCH and / or PUCCH.

[0110] Downlink (DL) physical channel / signal

[0111] (1) PDSCH

[0112] The PDSCH carries downlink data (e.g., DL-shared channel transport block, DL-SCH TB). The TB is encoded into a CodeWord (CW), then transmitted after undergoing processes such as scrambling and modulation. A CW contains one or more Code Blocks (CBs). One or more CBs can be grouped into a single CBG (CB group). Depending on the cell configuration, the PDSCH can carry up to two CWs. Scrambling and modulation are performed for each CW, and the modulation symbols generated from each CW are mapped to one or more layers. Each layer undergoes precoding, is mapped to a resource along with the DMRS, and is transmitted through the corresponding antenna port. PDSCH can be dynamically scheduled by PDCCH or semi-statically scheduled based on upper-layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)) (Configured Scheduling, CS). Therefore, in dynamic scheduling, PDCCH is involved with PDSCH transmissions, whereas in CS, PDCCH is not involved with PDSCH transmissions. CS includes semi-persistent scheduling (SPS).

[0113] (2) PDCCH

[0114] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of the DL-SCH, frequency / time resource allocation information for the UL-SCH (shared channel), paging information for the PCH (paging channel), system information on the DL-SCH, frequency / time resource allocation information for higher-layer control messages such as Random Access Responses (RAR) transmitted on the PDSCH, transmission power control commands, and information regarding the activation / deactivation of SPS / CS (Configured Scheduling). Various DCI formats are provided depending on the information within the DCI.

[0115] Table 5 shows examples of DCI formats transmitted via PDCCH.

[0116]

[0117] DCI format 0_0 is used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​may be used to schedule TB-based (or TB-level) PUSCH or CBG (Code Block Group)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 may be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0 / 0_1 is referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 may be referred to as DL grant DCI or UL scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic SFI) to terminals, and DCI format 2_1 is used to transmit downlink pre-Emption information to terminals. DCI format 2_0 and / or DCI format 2_1 may be transmitted to terminals within a group through a group common PDCCH, which is a PDCCH transmitted to terminals defined as a group.

[0118] PDCCH / DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with C-RNTI (Cell-RNTI). If the PDCCH is for paging, the CRC is masked with P-RNTI (Paging-RNTI). If the PDCCH is for system information (e.g., System Information Block, SIB), the CRC is masked with SI-RNTI (System Information RNTI). If the PDCCH is for random access acknowledgments, the CRC is masked with RA-RNTI (Random Access-RNTI).

[0119] Table 6 illustrates the uses and transmission channels of the PDCCH according to RNTI. The transmission channel represents the transmission channel associated with the data carried by the PDSCH / PUSCH scheduled by the PDCCH.

[0120]

[0121] The modulation scheme of the PDCCH is fixed (e.g., Quadrature Phase Shift Keying, QPSK), and a single PDCCH consists of 1, 2, 4, 8, or 16 Control Channel Elements (CCEs) depending on the Aggregation Level (AL). A single CCE consists of 6 Resource Element Groups (REGs). A single REG is defined by one OFDMA symbol and one (P)RB.

[0122] FIG. 4 illustrates a REG structure. In FIG. 4, D represents a resource element (RE) to which DCI is mapped, and R represents an RE to which DMRS is mapped. DMRS is mapped to the 1st, 5th, and 9th REs in the frequency domain direction within a single symbol.

[0123] PDCCH is transmitted via CORESET (Control Resource Set). CORESET corresponds to a set of physical resources / parameters used to carry PDCCH / DCI within a BWP. For example, CORESET includes a set of REGs with a given neuromonology (e.g., SCS, CP length, etc.). CORESET can be configured via system information (e.g., MIB) or terminal-specific (UE-specific) upper-layer signaling (e.g., RRC). Examples of parameters / information used to configure CORESET are as follows. One or more CORESETs are configured for a single terminal, and multiple CORESETs may overlap in the time / frequency domain.

[0124] - controlResourceSetId: Represents the identification information (ID) of the CORESET.

[0125] - frequencyDomainResources: Represents the frequency domain resources of the CORESET. It is indicated by a bitmap, where each bit corresponds to an RB group (= 6 consecutive RBs). For example, the MSB (Most Significant Bit) of the bitmap corresponds to the first RB group within the BWP. The RB group corresponding to the bit with a value of 1 is allocated as the frequency domain resource of the CORESET.

[0126] - duration: Represents the time domain resource of the CORESET. It indicates the number of consecutive OFDMA symbols that make up the CORESET. For example, duration has a value of 1 to 3.

[0127] - cce-REG-MappingType: Indicates the CCE-to-REG mapping type. Interleaved and non-interleaved types are supported.

[0128] - precoderGranularity: Represents the precoder granularity in the frequency domain.

[0129] - tci-StatesPDCCH: Represents information (e.g., TCI-StateID) indicating the Transmission Configuration Indication (TCI) state for the PDCCH. The TCI state is used to provide the Quasi-Co-Location (QCL) relationship between the DL RS(s) within the RS set (TCI-state) and the PDCCH DMRS port.

[0130] - tci-PresentInDCI: Indicates whether the TCI field within the DCI is included.

[0131] - pdcch-DMRS-ScramblingID: Represents the information used to initialize the PDCCH DMRS scrambling sequence.

[0132] REGs within a CORESET are numbered based on a time-first mapping manner. That is, REGs are numbered sequentially starting from 0, beginning with the first OFDM symbol in the lowest-numbered resource block within the CORESET.

[0133] The mapping type from CCE to REG is set to one of the following: a non-interleaved CCE-REG mapping type or an interleaved CCE-REG mapping type.

[0134] Figure 5 illustrates a non-interleaved CCE-REG mapping type.

[0135] - Non-interleaved CCE-REG mapping type (or localized mapping type): The 6 REGs for a given CCE form a single REG bundle, and all REGs for a given CCE are consecutive. One REG bundle corresponds to one CCE.

[0136] Figure 6 illustrates an interleaved CCE-REG mapping type.

[0137] - Interleaved CCE-REG mapping type (or Distributed mapping type): 2, 3, or 6 REGs for a given CCE form a single REG bundle, and the REG bundle is interleaved within the CORESET. A REG bundle within the CORESET consisting of 1 OFDM symbol or 2 OFDM symbols consists of 2 or 6 REGs, and a REG bundle within the CORESET consisting of 3 OFDM symbols consists of 3 or 6 REGs. The size of the REG bundle is set per CORESET.

[0138] To receive a PDCCH, the terminal may monitor a set of PDCCH candidates in a CORESET (e.g., blind decoding). A PDCCH candidate represents a CCE(s) that the terminal monitors for receiving / detecting a PDCCH. PDCCH monitoring may be performed on one or more CORESETs on active DL BWPs on each active cell where PDCCH monitoring is configured. The set of PDCCH candidates monitored by the terminal is defined as a set of PDCCH Search Spaces (SS). The SS set may be a set of Common Search Spaces (CSS) or a set of UE-specific Search Spaces (USS).

[0139] Table 7 illustrates the PDCCH search space.

[0140]

[0141] SS sets can be configured via system information (e.g., MIB) or terminal-specific (UE-specific) upper layer (e.g., RRC) signaling. Each DL BWP in a serving cell may have up to S (e.g., 10) SS sets configured. For example, the following parameters / information may be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration may be associated with one or more SS sets.

[0142] - searchSpaceId: Represents the ID of the SS set.

[0143] - controlResourceSetId: Represents the CORESET associated with the SS set.

[0144] - monitoringSlotPeriodicityAndOffset: Represents the PDCCH monitoring period interval (in slots) and the PDCCH monitoring interval offset (in slots).

[0145] - monitoringSymbolsWithinSlot: Represents the first OFDMA symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is configured. It is indicated by a bitmap, where each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDMA symbol within the slot. The OFDMA symbol(s) corresponding to bit(s) with a bit value of 1 correspond to the first symbol(s) of the CORESET within the slot.

[0146] - nrofCandidates: AL={1, 2, 4, 8, 16} represents the number of star PDCCH candidates (e.g., one of 0, 1, 2, 3, 4, 5, 6, 8).

[0147] - searchSpaceType: Indicates whether the SS type is CSS or USS.

[0148] - DCI Format: Indicates the DCI format of the PDCCH candidate.

[0149] Based on the CORESET / SS set configuration, the terminal can monitor PDCCH candidates from one or more SS sets within the slot. An occasion (e.g., time / frequency resources) when PDCCH candidates must be monitored is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities may be configured within the slot.

[0150] Uplink (DL) physical channel / signal

[0151] (1) PUSCH

[0152] PUSCH carries uplink data (e.g., UL-SCH TB) and / or uplink control information (UCI) and is transmitted based on a Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform or a Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform. When PUSCH is transmitted based on a DFT-s-OFDM waveform, the terminal transmits PUSCH by applying transform precoding. For example, if transform precoding is disabled, the terminal transmits PUSCH based on a CP-OFDM waveform, and if transform precoding is enabled, the terminal can transmit PUSCH based on a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH can be dynamically scheduled by PDCCH or semi-statically scheduled based on upper-layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)) (Configured Scheduling, CS). Therefore, in dynamic scheduling, PDCCH accompanies PUSCH transmissions, whereas in CS, PDCCH accompanies PUSCH transmissions. CS includes Type-1 CG (Configured Grant) PUSCH transmissions and Type-2 CG PUSCH transmissions. In Type-1 CG, all parameters for the PUSCH transmission are signaled by the upper layer. In Type-2 CG, some parameters for the PUSCH transmission are signaled by the upper layer, and the remainder are signaled by PDCCH. Essentially, in CS, PDCCH accompanies PUSCH transmissions.

[0153] (2) PUCCH

[0154] PUCCH carries UCI (Uplink Control Information). UCI includes the following:

[0155] - SR(Scheduling Request): Information used to request UL-SCH resources.

[0156] - HARQ-ACK (Hybrid Automatic Repeat and reQuest Acknowledgement): This is a reception acknowledgment signal for a DL signal (e.g., PDSCH, SPS release PDCCH). A HARQ-ACK response may include a positive ACK (simply ACK), a negative ACK (NACK), a DTX (Discontinuous Transmission), or a NACK / DTX. HARQ-ACK may be used interchangeably with A / N, ACK / NACK, HARQ-ACK / NACK, etc. HARQ-ACK may be generated in TB-units / CBG-units.

[0157] - CSI (Channel Status Information): This is feedback information regarding the DL channel. CSI includes CQI (Channel Quality Information), RI (Rank Indicator), PMI (Precoding Matrix Indicator), PTI (Precoding Type Indicator), etc.

[0158] Carrier Aggregation (CA)

[0159] NR can support wider uplink and downlink bandwidths by merging multiple uplink and downlink carriers (i.e., carrier merging). Through carrier merging, it is possible to transmit and receive signals on multiple carriers. When carrier merging is applied, each carrier can be referred to as a component carrier (CC). CCs can be adjacent or non-adjacent to each other in the frequency domain. The bandwidth of each CC can be determined independently. Asymmetric carrier merging is also possible, where the number of UL CCs and DL CCs differs. In NR, radio resources are classified and managed as cells, and a cell can consist of one DL CC and zero to two UL CCs. For example, a cell can consist of (i) only one DL CC, (ii) one DC CC and one UL CC, or (ii) one DL CC and two UL CCs (including one supplementary UL CC). Cells are classified as follows. In this specification, the term "cell" may be interpreted according to the context and may mean, for example, a serving cell. Additionally, unless otherwise stated, the operations of this specification may apply to each serving cell.

[0160] - PCell (Primary Cell): In the case of a terminal with carrier aggregation enabled, a cell operating on the primary frequency (e.g., Primary Component Carrier, PCC) where the terminal performs the initial connection establishment procedure or initiates the re-establishment procedure. In the case of DC (Dual Connectivity), an MCG (Master Cell Group) cell operating on the primary frequency where the terminal performs the initial connection establishment procedure or initiates the re-establishment procedure.

[0161] - SCell (Secondary Cell): For terminals with carrier aggregation enabled, a cell that provides additional wireless resources besides the special cell.

[0162] - PSCell (Primary SCG Cell): In the case of a DC, the SCG (Secondary Cell Group) cell where the terminal performs random access during the RRC reconfiguration and synchronization process.

[0163] - Special Cell (SpCell): In the case of DC, the special cell represents the PCell of the MCG or the PSCell of the SCG. Otherwise (i.e., non-DC), the special cell represents the PCell.

[0164] - Serving Cell (ServCell): Represents a cell configured for a terminal in the RRC_CONNECTED state. If CA / DA is not configured, only one serving cell (i.e., PCell) exists. If CA / DA is configured, the serving cell represents a set of cells including special cell(s) and all SCells.

[0165] Meanwhile, control information may be configured to be transmitted and received only through specific cells. For example, UCI may be transmitted only through special cells (e.g., PCell). If a SCell where PUCCH transmission is allowed (hereinafter referred to as PUCCH-SCell) is configured, UCI may also be transmitted through the PUCCH-SCell. As another example, the base station may allocate a scheduling cell (set) to reduce the complexity of PDCCH BD (blinding decoding) at the terminal side. For PDSCH reception / PUSCH transmission, the terminal may perform PDCCH detection / decoding only in the scheduling cell. Additionally, the base station may transmit PDCCH only through the scheduling cell (set). For example, a PDCCH for downlink allocation may be transmitted from cell #0 (i.e., the scheduling cell), and the corresponding PDSCH may be transmitted from cell #2 (i.e., the scheduled cell) (Cross-Carrier Scheduling, CCS). Scheduling cells (sets) can be configured in a terminal-specific, terminal-group-specific, or cell-specific manner. Scheduling cells include special cells (e.g., PCell).

[0166] For CCS, the CIF (carrier indicator field) is used. The CIF is semi-static and can be disabled / enabled by terminal-specific (or terminal group-specific) upper-layer (e.g., Radio Resource Control, RRC) signaling. The CIF field is an x-bit field (e.g., x=3) within the PDCCH (i.e., DCI) and can be used to indicate the (serving) cell index of a scheduled cell.

[0167] - CIF Disabled: CIF is absent within the PDCCH. The PDCCH on the scheduling cell allocates PDSCH / PUSCH resources on the same cell. In other words, the scheduling cell is identical to the scheduled cell.

[0168] - CIF Enabled: A CIF exists within the PDCCH. The PDCCH in scheduling can use the CIF to allocate PDSCH / PUSCH resources on one of multiple cells. The scheduling cell may be the same as or different from the scheduled cell. PDSCH / PUSCH refers to PDSCH or PUSCH.

[0169] Figure 7 illustrates scheduling in the case where multi-cells are merged.

[0170] Referring to Fig. 7, assume that three cells have been merged. When CIF is disabled, each cell can only transmit the PDCCH that schedules its own PDSCH / PUSCH (self-carrier scheduling, SCS). On the other hand, when CIF is enabled by terminal-specific (or terminal-group-specific or cell-specific) upper-layer signaling and Cell A is set as the scheduling cell, Cell A can transmit not only the PDCCH that schedules Cell A's PDSCH / PUSCH but also the PDCCH that schedules the PDSCH / PUSCH of other cells (i.e., scheduled cells) (cross-carrier scheduling, CCS). In this case, Cells B / C do not transmit the PDCCH that schedules their own cells.

[0171] Data transmission and HARQ-ACK process

[0172] Figure 8 illustrates the HARQ-ACK process for DL ​​data.

[0173] Referring to FIG. 8, the terminal can detect PDCCH in slot #n. Here, PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and PDCCH represents the DL assignment-to-PDSCH offset (K0) and the PDSCH-HARQ-ACK reporting offset (K1). For example, DCI format 1_0, 1_1 may include the following information.

[0174] - Frequency domain resource assignment: Represents the set of RBs assigned to PDSCH

[0175] - Time domain resource assignment: K0 indicates the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH within the slot.

[0176] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1

[0177] - HARQ process number (4 bits): Represents the HARQ process ID (Identity) for data (e.g., PDSCH, TB)

[0178] - PUCCH resource indicator (PRI): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources within the PUCCH resource set.

[0179] Subsequently, the terminal may receive a PDSCH at slot #(n+K0) according to the scheduling information of slot #n, and then transmit a UCI via a PUCCH at slot #(n+K1). Here, the UCI includes a HARQ-ACK response for the PDSCH. If the PDSCH is configured to transmit up to 1 TB, the HARQ-ACK response may consist of 1 bit. If the PDSCH is configured to transmit up to 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the time for transmitting HARQ-ACKs for multiple PDSCHs is designated as slot #(n+K1), the UCI transmitted at slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0180] Figure 9 illustrates the PUSCH transmission process.

[0181] Referring to FIG. 9, the terminal can detect PDCCH in slot #n. Here, PDCCH includes uplink scheduling information (e.g., DCI format 0_0, 0_1). DCI format 0_0, 0_1 may include the following information.

[0182] - Frequency domain resource assignment: Indicates the set of RBs assigned to PUSCH

[0183] - Time domain resource assignment: Indicates slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of PUSCH within the slot. The starting symbol and length may be indicated via SLIV (Start and Length Indicator Value) or individually.

[0184] Subsequently, the terminal can transmit PUSCH at slot #(n+K2) according to the scheduling information of slot #n. Here, PUSCH includes UL-SCH TB. If the time of transmission of PUCCH overlaps with the time of transmission of PUSCH, UCI can be transmitted via PUSCH (PUSCH piggyback).

[0185] The contents examined above may be applied in combination with the methods proposed in this specification described below, or may be supplemented to clarify the technical features of the methods proposed in this specification. The methods described below are distinguished merely for the convenience of explanation, and it goes without saying that parts of any one method may be substituted with parts of another method or combined with one another.

[0186] For example, technical terms used in this disclosure may be as follows.

[0187] - SSB: Synchronization Signal Block

[0188] - MIB: Master Information Block

[0189] - RMSI: Remaining Minimum System Information

[0190] - FR1: Frequency Range 1. Refers to the frequency range of 6 GHz or lower (e.g., 450 MHz ~ 6000 MHz).

[0191] - FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) region above 24 GHz (e.g., 24,250 MHz ~ 52,600 MHz).

[0192] - BW: Bandwidth

[0193] - BWP: Bandwidth Part

[0194] - RNTI: Radio Network Temporary Identifier

[0195] - SI-RNTI: System Information Radio-Network Temporary Identifier

[0196] - P-RNTI: Paging RNTI

[0197] - RAR-RNTI: Random Access Response RNTI

[0198] - TC-RNTI: Temporary C-RNTI

[0199] - C-RNTI: Cell RNTI

[0200] - CRC: Cyclic Redundancy Check

[0201] - SIB: System Information Block

[0202] - SIB1: SIB1 for NR devices (i.e., Remaining Minimum System Information (RMSI)). Broadcasts information necessary for cell connection of NR terminals.

[0203] - DCI: Downlink Control Information

[0204] - PDCCH: Physical Downlink Control CHannel

[0205] - PUCCH: Physical Uplink Control CHannel

[0206] - PDSCH: Physical Downlink Shared CHannel

[0207] - PUSCH: Physical Uplink Shared CHannel

[0208] - SS: Search Space

[0209] - SSS: Search Space Set

[0210] - CORESET: Control Resource Set. The time / frequency resource when the NR terminal attempts candidate PDCCH decoding.

[0211] - CORESET#0: CORESET for Type0-PDCCH CSS set for NR devices (configured in MIB)

[0212] - Type0-PDCCH CSS set: a search space set in which an NR UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI

[0213] - MO: PDCCH Monitoring Occasion

[0214] - Cell defining SSB (CD-SSB): An NR SSB that includes RMSI scheduling information

[0215] - Non-cell defining SSB (non-CD-SSB): Refers to an SSB deployed in an NR sync raster that does not include the corresponding cell's RMSI scheduling information for measurement purposes. However, it may include information indicating the location of the cell defining SSB.

[0216] - SCS: subcarrier spacing

[0217] - Camp on: "Camp on" is the UE state in which the UE stays on a cell and is ready to initiate a potential dedicated service or to receive an ongoing broadcast service.

[0218] - TB: Transport Block

[0219] - SIB1-PDSCH: PDSCH transmitting SIB1

[0220] - SIB1-DCI: DCI scheduling SIB1-PDSCH. DCI format 1_0 with CRC scrambled by SI-RNTI.

[0221] - SIB1-PDCCH: PDCCH transmitting SIB1-DCI

[0222] - MCS: Modulation and Coding Scheme

[0223] - FDRA: Frequency Domain Resource Allocation

[0224] - TDRA: Time Domain Resource Allocation

[0225] - RA: Random Access

[0226] - MSGA: preamble and payload transmissions of the random access procedure for 2-step RA type.

[0227] - MSGB: response to MSGA in the 2-step random access procedure. MSGB may consist of response(s) for contention resolution, fallback indication(s), and backoff indication.

[0228] - RO: 4-step RACH and 2-step RACH(if configured)를 위한 RO(RACH Occasion)

[0229] - PG: MsgA-Preambles Group

[0230] - RAR: Randoma Access Response

[0231] - RAR window: the time window to monitor RA response(s)

[0232] - FH: Frequency Hopping

[0233] - DL: Downlink

[0234] - UL: Uplink

[0235] - iBWP: initial BWP

[0236] - iBWP-DL(-UL): initial DL(UL) BWP

[0237] - CS: Cyclic shift

[0238] - NB: Narrowband

[0239] - TO: Traffic Offloading

[0240] - mMTC; massive Machine Type Communications

[0241] - eMBB: enhanced Mobile Broadband Communication

[0242] - URLLC: Ultra-Reliable and Low Latency Communication

[0243] - FDD: Frequency Division Duplex

[0244] - HD-FDD: Half-Duplex-FDD

[0245] - DRX: Discontinuous Reception

[0246] - MAC (CE): Medium Access Control (Control Element)

[0247] - MAC CE

[0248] - RRC: Radio Resource Control

[0249] - RRM: Radio Resource Management

[0250] - MM: Mobility Management

[0251] - IWSN: Industrial Wireless Sensor Network

[0252] - LPWA: Low Power Wide Area

[0253] - RB: Resource Block

[0254] - CCE: Control Channel Element

[0255] - AL: Aggregation Level

[0256] - PRG: Physical Resource-block Group

[0257] - DFT-s-OFDM: DFT-spread OFDM

[0258] - PBCH: Physical Broadcast Channel

[0259] - BD: blind detection

[0260] - EPRE: Energy Per RE

[0261] - SNR: Signal-to-Noise Ratio

[0262] - TDM: Time Division Multiplexing

[0263] - FDM: Frequency Division Multiplexing

[0264] - DMRS: DeModulation Reference Signal

[0265] - TDD: Time Division Duplex

[0266] - PCI: Physical layer Cell ID

[0267] - UE: User Equipment. In the case of LTE, NR, or next-generation communication systems, it refers to the LTE, NR, or next-generation communication system UE / terminal, respectively.

[0268] - F-gap: Frequency gap

[0269] - T-gap: Time gap

[0270] - TD: Time Domain

[0271] - FD: Frequency Domain

[0272] - PEI: Paging Early Indication

[0273] - LP-WUS: Low-Power Wake-Up Signal

[0274] - LP-SS: Low-Power Synchronization Signal

[0275] - RSRP: Reference Signal Received Power

[0276] - PRB: Physical Resource Block

[0277] - VRB: Virtual Resource Block

[0278] - PHR: Power Headroom Report

[0279] - BPF: Band-Pass Filter

[0280] - SFO: Sampling Frequency Offset

[0281] - ASK: Amplitude Shift Keying

[0282] - DSB-ASK: Double-SideBand ASK

[0283] - SSB-ASK: Single-SideBand ASK

[0284] - PR-ASK: Phase-Reversal ASK

[0285] - OOK: On-Off Keying

[0286] - PSK: Phase-Shift Keying

[0287] - BPSK: Binary-PSK

[0288] - FSK: Frequency-Shift Keying

[0289] - B-FSK: Binary FSK

[0290] - M-FSK: M-ary FSK

[0291] - Ncp-ofdm, Ncp, Nu: Sample unit lengths of the CP-OFDM symbol segment, CP segment, and useful OFDM symbol segment, respectively, in the CP-OFDM symbol. Ncp-ofdm = Ncp + Nu

[0292] - ME: Manchester Encoding

[0293] - OH: Overhead

[0294] - HARQ: Hybrid Automatic Repeat Request

[0295] - DAI: Downlink Assignment Index

[0296] - RV: Redundancy Version

[0297] - NDI: New Data Indicator

[0298] - PRI: PUCCH Resource Indicator

[0299] - XR: eXtended Reality

[0300] - SR: Scheduling Request

[0301] - A / N: Ack / Nack

[0302] A DCI split transmission method is proposed in which control information (e.g., DL / UL scheduling-related information) that was transmitted as a single DCI in a conventional 4G / 5G wireless communication system is divided / separated into multiple DCIs, for example, a first DCI and a second DCI, for transmission. Here, the multiple DCIs that are divided / separated are referred to as associated DCIs, or paired DCIs if there are two associated DCIs. For example, according to the DCI split transmission method described above, control information (e.g., fields related to DL / UL scheduling / control) is divided into long-term control information and short-term control information.

[0303] In addition, this method includes a case where the first DCI and the second DCI configured in the above manner constitute a two-stage DCI (for example, from the perspective of a terminal, performing a second DCI and / or subsequent DL / UL reception / transmission operation based on the first DCI, or performing a DL / UL reception / transmission operation with a combination of control information transmitted to the first DCI and the second DCI).

[0304] This DCI split transmission method allows each of the linked DCIs (e.g., a first DCI and a second DCI) to 1) indicate the validity period of itself (the control information it transmits), and / or 2) indicate the transmission / existence or monitoring operation of another linked DCI (specific information(s) transmitted through it), and / or 3) indicate whether there is an update of another linked DCI (specific information(s) transmitted through it). At this time, different validity periods and / or transmission cycles can be set / indicated for each of the linked DCIs. These methods can be used to reduce the average DL control signal OH compared to the conventional method of transmitting all control information with a single DCI (e.g., every Y ms), by, for example, configuring the number of linked DCIs to two, setting the validity period of the first DCI (e.g., X ms) to be larger than the validity period of the second DCI (e.g., X=5, Y=1), and transmitting the DCI only once within the validity period. The transmission of the first and second DCIs based on the above-described DCI split transmission method will be explained with reference to FIG. 10.

[0305] FIG. 10 illustrates the transmission of two linked DCIs according to one embodiment of the present specification.

[0306] Referring to FIG. 10, long-term information can be transmitted through the first DCI (10A) (large period), and short-term information can be transmitted through the second DCI (10B) (small period). Specifically, during the large period (10D) of the first DCI, the first DCI (10A) is transmitted only once, and the second DCI (10B) can be transmitted based on a period (e.g., slot) smaller than the large period (10D). Here, the large period (10D) may refer to a time window associated with the validity period of the first DCI (10A).

[0307] A shared channel (10C) (e.g., PDSCH, PUSCH) can be transmitted and received in each slot based on the first DCI (10A) and the second DCI (10B). For example, a terminal can receive a shared channel (10C) (e.g., PDSCH) from a base station based on the first DCI (10A) and the second DCI (10B). For example, a terminal can transmit a shared channel (10C) (e.g., PUSCH) to a base station based on the first DCI (10A) and the second DCI (10B).

[0308] As explained earlier, long-term and short-term are relative concepts and do not necessarily refer to absolute time. For example, if the short term is every slot (e.g., 1 ms), the long term could be a few slots (e.g., 5 ms). For example, if the short term is a mini slot (e.g., 2 OFDM symbol durations), the long term could be 1 slot or a few slots. For example, long-term control information may include the carrier / BWP indicator, VRB-to-PRB mapping, and PRB bundling size indicator. Depending on the channel environment and scenario, long-term control information may also include MCS, FDRA, TDRA, etc. For example, short-term control information may include FDRA, TDRA, HARQ ID, DAI, RV, NDI, PRI, etc. In addition, when the DCI split transmission method is implemented as a two-stage DCI method, the first DCI may include information necessary for receiving the second DCI (e.g., second DCI transmission T / F resource, MCS, DCI format).

[0309] In this specification, DCI can be interpreted / replaced with DCI format. For example, the first DCI can be replaced with the first DCI format, and the second DCI can be replaced with the second DCI format.

[0310] [Method #1: Method of indicating the validity period of itself (transmitted control information) in DCI]

[0311] For example, for the purpose of setting / instructing a relatively large DCI transmission period, a DCI (for example, a first DCI and / or a second DCI) may include an expiration period instruction. Based on the said DCI, the expiration period of itself (control information transmitted through the said DCI) may be indicated. Here, the expiration period may be defined from the perspective of the terminal based on at least one of the following 1) to 3).

[0312] 1) A period during which it is assumed that there are no updates to the DCI (control information transmitted through it).

[0313] 2) Period during which DCI monitoring can be skipped.

[0314] 3) The next monitoring occasion or next update time of DCI.

[0315] Here, the DCI may be a DCI containing an expiration date indication (for example, a first DCI and / or a second DCI).

[0316] As a method for setting / indicating the DCI validity period size, a timer method and / or a timing indication method may be considered. For example, a timer value or a timing (e.g., ms / symbol / slot / (sub-)frame offset) indication value may be set / indicated based on a semi-static signaling (e.g., RRC signaling, SIB, SIB1) method. For example, a timer value or a timing (e.g., ms / symbol / slot / (sub-)frame offset) indication value may be set / indicated based on a dynamic signaling (e.g., MAC CE, 1st DCI, 2nd DCI) method.

[0317] During the above validity period, the terminal may be required / configured to skip monitoring for a DCI (e.g., a first DCI) that includes a validity period instruction and to perform only monitoring for other associated DCI(s) (e.g., a second DCI).

[0318] After the expiration of the validity period, the terminal may resume monitoring of the DCI containing the validity period instruction (e.g., the first DCI). In this case, the terminal may skip monitoring of other linked DCI(s) (e.g., the second DCI) until the DCI containing the validity period instruction (e.g., the first DCI) is detected. When the DCI containing the validity period instruction (e.g., the first DCI) is detected through the monitoring, the terminal may perform monitoring of other linked DCI(s) (e.g., the second DCI) by applying the indicated validity period.

[0319] In certain service / application / use cases (e.g., XR, URLLC), an update may be required even within the validity period. To this end, the terminal may be configured to perform monitoring of a DCI containing a validity period instruction (e.g., a first DCI) even within the validity period. In this case, the validity period (timer) may be reset whenever a DCI containing a validity period instruction (e.g., a first DCI) is detected. In this case, the terminal may skip monitoring of other linked DCI(s) (e.g., a second DCI) until a DCI containing a validity period instruction (e.g., a first DCI) is detected after the validity period (timer) expires.

[0320] An operation to enable the terminal to monitor a DCI (e.g., a first DCI) including an expiration period instruction even within the expiration period can be performed as follows.

[0321] For example, the terminal can monitor a DCI containing an expiration period indication for the entire expiration period.

[0322] For example, the terminal can divide the validity period and monitor a DCI containing a validity period instruction only for a portion of the validity period.

[0323] As a specific example, the validity period may be divided into a first validity period and a second validity period. The terminal may not perform monitoring during the first validity period after detecting a DCI containing a validity period instruction (e.g., a first DCI), and may perform monitoring during the second validity period thereafter. The above-described operation may be performed in reverse. As a specific example, the terminal may perform monitoring during the first validity period and may not perform monitoring during the second validity period thereafter. In this case, within the validity period triggered by the detection of a DCI containing a validity period instruction (e.g., a first DCI), it may be assumed that the previous DCI information is valid prior to the detection of a DCI containing a new validity period instruction (e.g., a first DCI).

[0324] In the example of a two-stage DCI among the above DCI split transmission methods, if the second DCI indicates its own validity period (control information transmitted through the second DCI), it may be assumed that the first DCI monitoring occasion arrives within the validity period of the second DCI. Within the validity period, the terminal may be required / configured to perform an operation based on one of the following 1) to 5).

[0325] 1) The terminal can only perform 1st DCI monitoring.

[0326] 2) The terminal can perform both the first DCI monitoring and the second DCI monitoring.

[0327] 3) The terminal performs the first DCI monitoring, and the second DCI monitoring can be performed only when the first DCI is successfully received.

[0328] 4) The terminal is not required to perform both the first DCI monitoring and the second DCI monitoring, and the terminal may start DCI monitoring from the first first DCI MO after the expiration of the validity period.

[0329] 5) The terminal is not required to perform both the first DCI monitoring and the second DCI monitoring, and the terminal may start DCI monitoring from the first first DCI MO or the second DCI MO after the expiration of the validity period.

[0330] If the second DCI MO arrives first after the validity period and the terminal receives the second DCI first through it, the terminal may be configured to operate as follows.

[0331] For example, the terminal can operate based on the previously / recently received first DCI.

[0332] For example, default behavior and / or default parameter value(s) for cases such as the above may be separately defined or set in advance. The terminal may perform an action based on the default behavior and / or default parameter value(s).

[0333] [Method #2: Method for indicating whether to transmit and / or monitor other DCI(s) (control information transmitted by them) at a DCI]

[0334] A method may be considered in which the transmission and / or monitoring of the m (≠n) DCI(s) (control information transmitted by them) is indicated based on the nth DCI. For example, in the example of a two-stage DCI among the DCI split transmission methods, the transmission and / or monitoring of the second DCI may be indicated based on the first DCI. Depending on the target to be controlled in the nth DCI, the following detailed methods may be considered.

[0335] [Method #2-1: A method for controlling the configuration of all or specific fields (e.g., FDRA, TDRA) of other DCI(s) in a DCI and / or indicating their existence]

[0336] For example, a specific DCI field may include at least one of FDRA and TDRA. For example, the configuration of a specific DCI field may include the size of the field, the mapping order within the DCI format, etc. For example, when applying Method #2-1 in the example of a two-stage DCI among the DCI split transmission methods above, the terminal may receive a second DCI based on the first DCI after receiving the first DCI. As a specific example, the terminal may receive the second DCI (fields) by referring to configuration information regarding the existence of specific field(s) of the second DCI indicated by the first DCI and / or if they exist. As a specific example, if specific field(s) of the second DCI do not exist according to the indication of the first DCI, the terminal may assume a previously / recently received value for the field(s) or assume a value that is pre-set / defined (e.g., default value).

[0337] [Example #2-1]

[0338] With the overall size of the first DCI fixed in consideration of the first DCI BD, the field of the first DCI may be composed of long-term control field(s) + a bitmap for controlling the second DCI. For example, the bitmap field for controlling the second DCI may be composed of a 2-bit bitmap {TDRA presence / update, FDRA presence / update}, which may indicate whether the TDRA field is present / updated and whether the FDRA field is present / updated, respectively. For example, if the bitmap value is "10", the second DCI may contain only TDRA information. For example, if the bitmap value is "11", the second DCI may contain both TDRA and FDRA information. Based on this information, the terminal may determine the size and / or field configuration of the second DCI and receive / decode the second DCI. At this time, information not included in the second DCI (e.g., TDRA / FDRA information) may be assumed to be a previously / recently received value, or a value that is set / defined in advance (e.g., default value).

[0339] [Method #2-2: Indicate whether the DCI transmits to other DCI(s) and / or monitors the other DCI(s)]

[0340] For example, when Method #2-2 is applied to the example of a two-stage DCI among the above DCI split transmission methods, the terminal receives the first DCI and can skip the second DCI monitoring according to the second DCI control information indicated by the first DCI. In this case, when the second DCI monitoring operation is skipped by a base station instruction, the terminal can be configured to operate as follows.

[0341] For example, the terminal may operate based on previously / recently received second DCI information (for example, in the case of TDRA / FDRA, by applying previously / recently received TDRA / FDRA values).

[0342] For example, default behavior and / or default parameter value(s) may be separately defined or set in preparation for cases such as the above. The terminal may perform an action based on the default behavior and / or default parameter value(s).

[0343] In Method #2, if specific field(s) of another DCI are not transmitted, or if monitoring is skipped and a previously / recently received value is assumed, or if a pre-set / defined value (e.g., default value) is assumed, the terminal may base the application criteria / application time on the first DCI or the second DCI. For example, the terminal may apply an assumption regarding specific field(s) based on the first DCI. For example, the terminal may apply an assumption regarding specific field(s) based on the second DCI, even though they were not actually transmitted or detected.

[0344] For example, it may be assumed that a specific field is a TDRA that schedules PDSCH / PUSCH. When based on the first DCI, the terminal may apply symbol and / or slot offsets, etc. based on the (last or first) OFDM symbol(s) received of the first DCI. When based on the second DCI, the terminal may apply symbol and / or slot offsets, etc. based on the (last or first) OFDM symbol(s) received of the second DCI. For example, the reference DCI reception time resource may be based on i) the transmitted OFDM symbol(s) of the first DCI or the second DCI, or ii) the smallest / largest OFDM symbol index among the CORESET / SS containing the transmission of the first DCI or the second DCI.

[0345] An example is given for an FDRA that schedules PDSCH / PUSCH, and for which the FDRA is indicated based on a DCI received frequency resource (for example, in the form of a frequency offset and a size). For example, a terminal can determine the starting point and size of a PDSCH / PUSCH transmission resource by applying a frequency offset based on a frequency resource that received a first DCI. For example, a terminal can determine the starting point and size of a PDSCH / PUSCH transmission resource by applying a frequency offset based on a frequency resource that received a second DCI. For example, the reference DCI received frequency resource may be based on i) the smallest / largest RB index among the transmission RBs of the first DCI or the second DCI, or ii) the smallest / largest RB index among the CORESET / SS containing the transmission of the first DCI or the second DCI.

[0346] In Method #2 and the detailed methods, the method of indicating the presence or absence of other DCI(s) (control information transmitted by them) or monitoring status at the DCI can be performed by setting / indicating a validity period as in Method #1. In this case, the validity period can be set / indicated by a timer or timing indication method as mentioned in Method #1.

[0347] [Method #3: Method for indicating / displaying update information of other DCI(s) (control information transmitted by them) in a DCI]

[0348] When there are interconnected DCIs, as in Method #1 above, the DCI may not only indicate the validity period and / or update information of itself (the control information it transmits), but also simultaneously indicate / display the update information of other DCI(s) (among the interconnected DCIs). According to this method, the overall L1 signaling OH can be reduced by varying the update cycles between the interconnected DCIs. For example, according to the present embodiment, rapid updates may be possible for DCI(s) with a large transmission cycle among the interconnected DCIs as needed (Example #3-1). For example, the present embodiment may be applied to resolve the ambiguity problem between the base station and the terminal that may occur when the reception of some DCIs among the interconnected DCIs is missed (Example #3-2).

[0349] [Example #3-1]

[0350] Method #3 may be used to enable DCI updates by indicating the reception of the DCI (or indicating an update) even within the DCI validity period. For example, in the above two-stage DCI example, when the first DCI transmission period is longer than the second DCI transmission period, an operation based on Method #3 may be performed for the first DCI update. As a specific example, the base station may urgently update the first DCI in the form of an interruption within the validity period. The base station may transmit a second DCI containing update information for the first DCI.

[0351] As a specific example, in order to effectively support cases where a first DCI update is required at a interval shorter than the validity period (at low frequency), the base station may direct the first DCI update information through the second DCI.

[0352] At this time, when the terminal receives information that the first DCI has been updated through the second DCI within the validity period, it may be required / configured to BD the first DCI at the linked first DCI MO (in the same slot where the second DCI was received or in the slot immediately following that slot). For example, the "linked" first DCI MO may be a fallback DCI MO (for receiving the first DCI) that is pre-configured in preparation for the above case. For example, the "linked" first DCI MO may be a first DCI MO for receiving updated first DCI update information that is transmitted together in the same slot or the next slot when the base station transmits the first DCI update information through the second DCI.

[0353] [Example #3-2]

[0354] In a two-stage DCI, if the first DCI transmission period is longer than the second DCI transmission period, if the reception of the updated first DCI is missed, ambiguity may exist between the base station and the terminal for a considerable amount of time until the updated first DCI information is detected. To resolve this problem in the shortest possible time, Method #3 may be applied.

[0355] For example, update information of the first DCI can be indicated / displayed based on the second DCI. The update information can be configured as an X-bit counter (X>=1) method or simply a 1-bit flag method.

[0356] In the case of the X-bit counter (X>=1) method, the base station increments the counter value by 1 for every update of the first DCI and then applies an X-bit modulo operation. The terminal can detect whether there is an update and the number of updates through whether the counter value changes and the amount of change.

[0357] In the case of a 1-bit flag method, bit "0" (or bit "1") can be mapped to no update, and bit "1" (or bit "0") can be mapped to update. The terminal can determine whether to update based on the absolute value (0 or 1) of the flag.

[0358] [Method #3-1: Fallback Action of Method #3]

[0359] In the case where the first DCI is missing as in Example #3-2 above, the terminal becomes aware of the situation through the second DCI using the methods presented above, but the base station may still have to continue transmitting (for the time being) even though the terminal cannot receive the PDSCH scheduled by the combination of the first DCI and the second DCI. To minimize such waste of resources / power on the base station side, operations based on the following embodiments may be performed.

[0360] According to one embodiment, when a terminal recognizes a first DCI missing through a second DCI, it may transmit feedback regarding the first DCI missing (in the form of A / N or SR, etc.) to a base station through a feedback resource (PUCCH) indicated through the first DCI and / or the second DCI, regardless of whether the scheduled PDSCH reception is successful (i.e., even if PDSCH reception is successful). At this time, the information fed back by the terminal may be information regarding whether the first DCI is received / missed or information requesting the retransmission of the first DCI (due to the first DCI missing). For example, based on this terminal feedback information, the base station may perform operations such as DL / UL scheduling by assuming / applying updated first DCI information and second DCI information only in cases where the first DCI is not missing and / or there is no request for retransmission of the first DCI. After the terminal provides feedback on information indicating a first DCI missing and / or information requesting retransmission, it may expect retransmission of the first DCI at a first DCI MO that arrives after a specific time (including the time required for the base station to decode the feedback + the time to prepare for the first DCI retransmission + the time until the first DCI transmission resource is available thereafter) or from that time (thus, it may perform BD for the first DCI). Specifically, during the specific time interval, the terminal may omit BD for the first DCI.

[0361] According to one embodiment, a method may be considered in which a base station / terminal applies a first DCI update based on feedback (e.g., A / N) regarding the reception of first DCI update information. For example, a base station may transmit a first DCI containing update information and apply the updated first DCI information based on the feedback regarding the reception of the first DCI. For example, the feedback regarding the reception of first DCI update information may be feedback (e.g., A / N) information regarding whether the reception of the first DCI containing update information was successful. For example, the feedback regarding the reception of first DCI update information may be A / N feedback information regarding whether the reception of a PDSCH scheduled through the first DCI and / or second DCI containing update information was successful. The timing of the application of the first DCI update information may be defined based on one of the following examples. For example, from the perspective of the base station, the first DCI update information may be applied immediately after receiving the feedback regarding the reception of the first DCI update information. For example, by setting / instructing a period in advance, the updated information of the first DCI transmitted at period n and the terminal feedback thereon can be applied from period n+1.

[0362] [Method #4: Setting different SS cycles for DCI monitoring among linked DCIs]

[0363] In the example of a two-stage DCI among the above DCI split transmission methods, the SS period may be set differently for each DCI for the purpose of setting / instructing the first DCI transmission period to be relatively larger than the second DCI. For example, the SS period for first DCI monitoring (first SS) may be set to a value relatively larger than the SS period for second DCI monitoring (second SS). At this time, the size of the first SS period may be set to a value equivalent to the size of the validity period of Method #1 above. For example, the first SS period may be set to N times the second SS period (e.g., N is an integer greater than 1). In other words, the first SS period may be set using the second SS period as a unit. As a specific example, if the value set for the first SS period is N, the corresponding first SS period may be N times the second SS period.

[0364] For example, a monitoring slot offset value can be set individually for each of the first SS and the second SS. This allows the terminal to monitor the same or different slots. This embodiment can be used for the purpose of transmitting linked DCIs by distributing them as much as possible within the terminal's BD capability.

[0365] For example, the location of the monitoring symbol within the slot can be set individually for the first SS and the second SS, respectively. The terminal can monitor the same or different symbols within the slot.

[0366] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations based on at least one of methods 1 to 4) can be processed by the device of FIG. 13 (e.g., the processor (110, 210) of FIG. 13) to be described later.

[0367] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations based on at least one of methods 1 to 4) may be stored in memory (e.g., 140, 240 of FIG. 13) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 13).

[0368] The embodiments described above will be explained in detail below with reference to FIGS. 11 and FIGS. 12 in terms of the operation of the terminal / base station. The methods described below are distinguished only for convenience of explanation, and it is understood that a part of one method may be substituted with a part of another method or combined with one another and applied.

[0369] FIG. 11 is a flowchart for explaining a method performed by a terminal according to one embodiment of the present specification.

[0370] Referring to FIG. 11, a method performed by a terminal according to one embodiment of the present specification includes a first DCI receiving step (S1110) and a second DCI receiving step (S1120).

[0371] In S1110, the terminal receives first downlink control information (DCI) containing first part information from the base station.

[0372] In S1120, the terminal receives a second DCI containing second part information from the base station.

[0373] The first DCI and the second DCI may be based on at least one of methods #1 to #4. For example, the first DCI may be based on 10A of FIG. 10, and the second DCI may be based on 10B of FIG. 10.

[0374] According to one embodiment, the first DCI may include information regarding a time window (e.g., 10D in FIG. 10) associated with the validity period of the first DCI. Within the time window, monitoring associated with the first DCI may be skipped, and only monitoring associated with the second DCI may be performed. In other words, during the time window, the first DCI may be received only once, and the second DCI may be received one or more times. This embodiment may be based on Method #1. The time window may be based on at least one of the following 1) to 3) in terms of terminal operation.

[0375] 1) The above time window may be a period during which it is assumed that there is no update of the first DCI.

[0376] 2) The above time window may be a period during which monitoring of the first DCI can be skipped.

[0377] 3) The above time window may be a period up to the next monitoring occasion or next update time of the first DCI. In other words, the end time of the above time window may be based on the next monitoring occasion or next update time of the first DCI.

[0378] For example, the above monitoring may refer to monitoring for receiving DCI (or DCI format). Specifically, the above monitoring may refer to monitoring a set of PDCCH candidates.

[0379] According to one embodiment, the second DCI may include configuration information of at least one field within the first DCI. This embodiment may be based on Method #2-1. For example, the at least one field may include at least one of a Frequency Domain Resource Assignment (FDRA) field and / or a Time Domain Resource Assignment (TDRA) field. For example, the configuration information of the at least one field may include i) the size (number of bits) of the corresponding field and / or ii) the mapping order within the first DCI (first DCI format).

[0380] According to one embodiment, the second DCI may include information indicating the existence of at least one field within the first DCI. This embodiment may be based on Method #2-1.

[0381] According to one embodiment, the second DCI may include i) information indicating the existence of at least one field in the first DCI and configuration information of at least one field in the first DCI. This embodiment may be based on Method #2-1.

[0382] According to one embodiment, information indicating the skipping of monitoring related to the second DCI may be included. Alternatively, the skipping of monitoring related to another second DCI may be indicated based on the second DCI. Alternatively, the transmission / monitoring status of another second DCI may be indicated based on the second DCI. This embodiment may be based on Method #2-2. An operation based on this embodiment will be described in detail below with reference to FIG. 10.

[0383] In slot #n, the terminal receives a first DCI (10A) and a second DCI (10B). The second DCI (10B) may include information indicating a skip of monitoring related to the second DCI in another slot (e.g., slot #n+1). For example, in the slot (e.g., slot #n+1), the terminal may transmit or receive a shared channel (10C) based on a previously received second DCI (e.g., the second DCI received in slot #n). For example, in the slot (e.g., slot #n+1), the terminal may transmit or receive a shared channel (10C) based on default parameter value(s). For example, in the slot (e.g., slot #n+1), the terminal may perform a predefined default operation.

[0384] According to one embodiment, the second DCI may include information related to the update of the first DCI. This embodiment may be based on Method #3. More specifically, it may be assumed that the first DCI is updated after the terminal receives the first DCI. In this case, even if the previously received first DCI is within a valid time (the time window), the terminal must receive the updated first DCI again. To this end, the second DCI may include information related to the update of the first DCI (information indicating that the first DCI has been updated).

[0385] According to one embodiment, the method may further include a step of transmitting feedback-related information. For example, a terminal may transmit information related to the feedback of the updated first DCI to a base station based on the determination that the reception of the first DCI updated through the second DCI is missing. For example, whether the terminal receives the updated first DCI or does not receive it, the terminal may transmit information related to the feedback of the updated first DCI (e.g., ACK / NACK) to a base station.

[0386] This embodiment is intended to prevent unnecessary signaling in the following situations. Specifically, even though the terminal misses receiving the updated first DCI and thus cannot receive the shared channel based on the updated first DCI, the base station (which is unaware of the terminal's state) may continue to transmit the said shared channel. This embodiment is intended to prevent such unnecessary signaling. This embodiment may be based on Method #3-1.

[0387] According to one embodiment, the first periodicity associated with the first search space for monitoring the first DCI may be set to be larger than the second periodicity associated with the second search space for monitoring the second DCI. This embodiment may be based on Method #4.

[0388] According to one embodiment, the first part information may be related to long-term control. The second part information may be related to short-term control.

[0389] The operation based on the above-described feedback-related information transmission steps S1110 to S1120 can be implemented by the device of FIG. 13. For example, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform the operation based on the feedback-related information transmission steps S1110 to S1120.

[0390] The embodiments described above will be explained in detail below in terms of base station operation.

[0391] The feedback-related information receiving steps S1210 to S1220 described below correspond to the feedback-related information transmission steps S1110 to S1120 described in FIG. 11. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below can be replaced by the description / embodiment of FIG. 11 corresponding to the operation.

[0392] FIG. 12 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.

[0393] Referring to FIG. 12, a method performed by a base station according to another embodiment of the present specification includes a first DCI transmission step (S1210) and a second DCI transmission step (S1220).

[0394] In S1210, the base station transmits first downlink control information (DCI) containing first part information to the terminal.

[0395] In S1220, the base station transmits a second DCI containing second part information to the terminal.

[0396] The first DCI and the second DCI may be based on at least one of methods #1 to #4. For example, the first DCI may be based on 10A of FIG. 10, and the second DCI may be based on 10B of FIG. 10.

[0397] According to one embodiment, the first DCI may include information regarding a time window associated with the validity period of the first DCI. Within the time window, monitoring associated with the first DCI may be skipped, and only monitoring associated with the second DCI may be performed. In other words, during the time window, the first DCI may be transmitted only once, and the second DCI may be transmitted one or more times.

[0398] According to one embodiment, the method may further include a step of receiving feedback-related information. Specifically, the base station may receive information related to the feedback of the updated first DCI from the terminal.

[0399] The operation based on the above-described steps of receiving feedback-related information, S1210 to S1220, can be implemented by the device of FIG. 13. For example, a base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform the operation based on the steps of receiving feedback-related information, S1210 to S1220.

[0400] Hereinafter, an apparatus to which the embodiments of the present specification can be applied (an apparatus implementing the method / operation according to the embodiments of the present specification) will be described with reference to FIG. 13.

[0401] FIG. 13 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0402] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0403] The processor (110) performs baseband-related signal processing and may include an upper layer processing unit (111) and a physical layer processing unit (115). The upper layer processing unit (111) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (115) may process operations of the PHY layer. For example, if the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, if the first device (100) is a first terminal device in terminal-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

[0404] The antenna section (120) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110) and software, operating systems, applications, etc. related to the operation of the first device (100), and may include components such as a buffer.

[0405] The processor (110) of the first device (100) may be configured to implement the operation of the base station in base station-terminal communication (or the operation of the first terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0406] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0407] The processor (210) performs baseband-related signal processing and may include an upper layer processing unit (211) and a physical layer processing unit (215). The upper layer processing unit (211) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (215) may process operations of the PHY layer. For example, if the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, if the second device (200) is a second terminal device in terminal-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0408] The antenna section (220) may include one or more physical antennas, and may support MIMO transmission and reception if it includes multiple antennas. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210) and software, operating systems, applications, etc. related to the operation of the second device (200), and may include components such as a buffer.

[0409] The processor (210) of the second device (200) may be configured to implement the operation of the terminal in base station-terminal communication (or the operation of the second terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0410] In the operation of the first device (100) and the second device (200), the details described in the examples of the present disclosure regarding the base station and terminal (or the first terminal and the second terminal in terminal-to-terminal communication) in base station-to-terminal communication may be applied in the same way, and redundant descriptions are omitted.

[0411] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above.

[0412] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above.

[0413] Additionally or generally, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, but is not limited to the names mentioned above. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be called by various names.

Claims

1. Regarding the method, A step of receiving first downlink control information (DCI) including first part information from a base station; and The method includes the step of receiving a second DCI containing second part information from the base station; The first DCI above includes information regarding a time window related to the validity period of the first DCI, and A method characterized in that, within the above time window, monitoring related to the first DCI is skipped and only monitoring related to the second DCI is performed.

2. In Paragraph 1, A method characterized in that the second DCI includes configuration information of at least one field within the first DCI.

3. In Paragraph 1, A method characterized in that the second DCI includes information indicating whether at least one field exists within the first DCI.

4. In Paragraph 1, A method characterized in that the second DCI includes information indicating the skipping of the monitoring associated with the second DCI.

5. In Paragraph 1, A method characterized in that the second DCI includes information related to the update of the first DCI.

6. In Paragraph 1, A method further comprising the step of transmitting information related to the feedback of the updated first DCI based on the determination that the reception of the first DCI updated through the second DCI is missing.

7. In Paragraph 1, A method characterized in that the first periodicity associated with the first search space for monitoring the first DCI is set to be larger than the second periodicity associated with the second search space for monitoring the second DCI.

8. In Paragraph 1, The above first part information is related to long-term control, and A method characterized by the above second part information being related to short-term control.

9. Regarding the terminal, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A terminal characterized by the above instructions being set so that the terminal performs all steps of the method according to any one of claims 1 to 8, based on execution by the one or more processors.

10. An apparatus comprising one or more memories and one or more processors functionally connected to the one or more memories, An apparatus characterized in that the above one or more memories store instructions that set the one or more processors to perform all steps of the method according to any one of claims 1 to 8, based on execution by the above one or more processors.

11. In one or more non-transitory computer-readable media storing instructions, One or more non-transitory computer-readable media characterized by instructions executable by one or more processors, wherein the one or more processors are configured to perform all steps of the method according to any one of claims 1 through 8.

12. Regarding the method, A step of transmitting first downlink control information (DCI) including first part information to a terminal; and The method includes the step of transmitting a second DCI containing second part information to the terminal; The first DCI above includes information regarding a time window related to the validity period of the first DCI, and A method characterized in that, within the above time window, monitoring related to the first DCI is skipped and only monitoring related to the second DCI is performed.

13. Regarding base stations, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A base station characterized by the above instructions being set so that the one or more processors perform all steps of the method according to claim 11, based on execution by the one or more processors.

Images