Initial cell connection method, device, and system in a wireless communication system
A method for initial cell connection and frequency hopping in reduced capability terminals in wireless communication systems, using separate configuration and synchronization signals, addresses the challenge of connecting reduced capability terminals in cellular networks, ensuring smooth and conflict-free communication.
Patent Information
- Application Number
- KR1020227040018
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-05-21
- Filing Date
- 2021-08-04
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2041-08-04
AI Technical Summary
The existing technologies fail to address the issue of providing an effective method for initial connection of devices with reduced capability terminals in a wireless communication system, particularly in cellular networks, and frequency hopping for uplink data transmission.
A first terminal with reduced capability is provided in a wireless communication system, configured to receive specific configuration information and indicators for bandwidth parts and synchronization signal blocks, allowing it to perform initial connection procedures through separate bandwidth parts and synchronization signals, distinct from legacy terminals.
Enables smooth initial cell connection and random access procedures without conflicts with legacy terminals, facilitating communication through various frequency hopping designs.
Smart Images

Figure R1020227040018_ABST
Abstract
Description
Technology Field
[0001] The present invention relates to a wireless communication system, and more specifically, to an initial cell connection method, device, and system in a wireless communication system. Background Technology
[0002] Since the commercialization of 4G (4th generation) communication systems, efforts have been made to develop new 5G (5th generation) communication systems to meet the increasing demand for wireless data traffic. 5G communication systems are referred to as beyond 4G network communication systems, post-LTE systems, or NR (new radio) systems. To achieve high data transmission rates, 5G communication systems include systems operating in the mmWave band above 6 GHz, and implementations at base stations and terminals are being considered to include communication systems operating in the frequency band below 6 GHz in order to secure coverage.
[0003] 3GPP (3rd generation partnership project) NR systems improve network spectrum efficiency, enabling telecommunications operators to provide more data and voice services within a given bandwidth. Therefore, 3GPP NR systems are designed to meet the demands for high-speed data and media transmission in addition to supporting high-volume voice. The advantages of NR systems include high throughput, low latency, support for FDD (frequency division duplex) and TDD (time division duplex), an enhanced end-user experience, and low operating costs due to a simple architecture, all within the same platform.
[0004] For more efficient data processing, dynamic TDD in NR systems may use a method that varies the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols available for uplink and downlink based on the direction of data traffic from cell users. For example, when a cell's downlink traffic is greater than its uplink traffic, the base station may allocate multiple downlink OFDM symbols to a slot (or subframe). Information regarding the slot configuration must be transmitted to the terminals.
[0005] In order to mitigate path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, beamforming, massive array multiple input / output (massive MIMO), full dimensional multiple input / output (full dimensional MIMO, FD-MIMO), array antenna, analog beamforming, hybrid beamforming combining analog beamforming and digital beamforming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the network of the system, technology development is underway in 5G communication systems regarding advanced small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), vehicle-to-everything communication (V2X), wireless backhaul, non-terrestrial network communication (NTN), moving networks, cooperative communication, CoMP (coordinated multi-points), and interference cancellation.In addition, advanced coding modulation (ACM) methods such as FQAM (hybrid FSK and QAM modulation) and SWSC (sliding window superposition coding), as well as advanced access technologies such as FBMC (filter bank multi-carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.
[0006] The Internet is evolving from a human-centric network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with big data processing techniques via connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks for connecting objects, machine-to-machine (M2M) communication, and machine-type communication (MTC) are currently being researched. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.
[0007] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier can also be considered an example of the convergence of 5G and IoT technologies. Generally, mobile communication systems were developed to provide voice services while ensuring user mobility.
[0008] In the 3GPP study on "Self-Assessment of IMT-2020 Submissions," it was confirmed that NB IoT and LTE M meet the IMT-2020 requirements for mMTC and can be certified as 5G technologies. To support URLLC, URLLC capabilities were introduced in Rel-15 for both LTE and NR, and in Rel-16, URLLC in NR systems was further advanced through enhanced URLLC (eURLLC) and the Industrial IoT work item. Additionally, Rel-16 introduced support for Time-Sensitive Networking (TSN) and 5G integration for TSC usage.
[0009] One of the key goals of 5G is to enable connected industries. 5G connectivity acts as a catalyst for next-generation industrial innovation and digitalization, enhancing flexibility, improving productivity and efficiency, reducing maintenance costs, and enhancing operational safety. For devices in these environments, it is desirable to connect, for example, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, and actuators to 5G wireless access and core networks. Use cases and requirements for large-scale industrial wireless sensor networks include not only highly demanding URLLC services but also relatively inexpensive services with small device format requirements. Additionally, devices must be able to operate wirelessly using batteries for several years. Examples of such services include industrial wireless sensors, video surveillance, and wearable devices. These services have requirements higher than Low Power Wide Area (LPWA) (i.e., LTE-M / NB-IoT) but lower than URLLC and eMBB. The problem to be solved
[0010] The technical problem of the present invention is to provide an initial cell connection method and device in a wireless communication system, particularly in a cellular wireless communication system.
[0011] Another technical objective of the present invention is to provide a frequency hopping method for uplink data transmission in a wireless communication system, particularly in a cellular wireless communication system, and an apparatus for the same. means of solving the problem
[0012] According to one aspect of the present invention, a first terminal (reduced capability UE) with reduced capability is provided in a wireless communication system. The first terminal comprises a communication module configured to receive configuration information for configuring a first downlink bandwidth part (DL BWP) and a first uplink bandwidth part (Uplink BWP) used in an initial connection procedure, receive an indicator indicating that the first terminal is unable to access the BWP (BWP access barring) at a second UL BWP and a second DL BWP for a legacy type second terminal, and perform an initial connection procedure through at least one of the first DL BWP, the first UL BWP, the second DL BWP, and the second UL BWP based on the indicator, and a processor that controls the reception of the configuration information, the execution of the initial connection procedure, and the reception of the indicator, wherein the first UL BWP and the second UL BWP are each configured individually, the initial connection procedure includes a random access procedure, and the first UL BWP includes a first resource for the random access procedure of the first terminal, and the The first resource may be identical to the second resource for an arbitrary connection procedure on the second UL BWP of the second terminal.
[0013] In one aspect, the communication module may be configured to obtain information regarding a control resource set (CORESET) from a second synchronization signal block (SSB) regarding the second terminal.
[0014] In another aspect, the communication module may be configured to receive information regarding a CORESET for the first terminal, which is defined separately from the CORESET for the second terminal, through a system information block (system information block 1: SIB1).
[0015] In another aspect, the communication module is configured to receive SIB1 for the second terminal, wherein SIB1 may include scheduling information regarding system information for performing the initial connection procedure of the first terminal.
[0016] In another aspect, the scheduling information may include information regarding the start PRB (physical resource block) of the first DL BWP activated for the execution of the initial connection procedure of the first terminal.
[0017] In another aspect, the communication module is configured to receive SIB1 for the second terminal, wherein SIB1 may include configuration information for an optional connection procedure for the initial connection of the first terminal.
[0018] In another aspect, the communication module may be configured to obtain information regarding a CORESET for the first terminal through a first SSB defined separately from a second SSB regarding the second terminal.
[0019] In another aspect, the information regarding the basic CORESET is composed of 8 bits, and in the information regarding the basic CORESET, 4 bits indicate information about the frequency range in which the basic CORESET is set, and the remaining 4 bits may indicate information about a symbol for monitoring the basic CORESET.
[0020] In another aspect, the 8 bits constituting the information regarding the basic CORESET can be recognized as different information by the first terminal and the second terminal, respectively.
[0021] In another aspect, the communication module may receive information from the base station indicating the first resource for the first terminal.
[0022] In another aspect, some of the random access preamble sequences available in the cell provided by the base station may be used for the first terminal, and some of the remaining may be used for the second terminal.
[0023] In another aspect, the communication module can obtain information regarding a CORESET for the first terminal based on information regarding the basic CORESET.
[0024] In another aspect, within the above basic CORESET, a first PDCCH candidate for the first terminal is defined separately from a second PDCCH candidate for the second terminal, and the communication module may be configured to monitor the first PDCCH candidate within the above basic CORESET.
[0025] According to another aspect of the present invention, a method for operating a first terminal with reduced capability (reduced capability UE) in a wireless communication system is provided. The method comprises the steps of: receiving configuration information for setting a first downlink bandwidth part (DL BWP) and a first uplink bandwidth part (Uplink BWP) used in an initial connection procedure; receiving an indicator indicating that the first terminal cannot access the BWP (BWP access barring) in a second UL BWP and a second DL BWP for a legacy type second terminal; and performing an initial connection procedure through at least one of the first DL BWP, the first UL BWP, the second DL BWP, and the second UL BWP based on the indicator. Here, the first UL BWP and the second UL BWP are each configured individually, and the initial access procedure includes a Random Access procedure, and the first UL BWP includes a first resource for the Random Access procedure of the first terminal, and the first resource may be identical to the second resource for the Random Access procedure on the second UL BWP of the second terminal.
[0026] In one aspect, the method may further include the step of obtaining information regarding a control resource set (CORESET) from a second synchronization signal block (SSB) regarding the second terminal.
[0027] In another aspect, the above method may further include the step of receiving information regarding a CORESET for the first terminal, which is defined separately from the CORESET for the second terminal, through a system information block (system information block 1: SIB1).
[0028] In another aspect, the method further comprises the step of receiving SIB1 for the second terminal, wherein the SIB1 may include scheduling information regarding system information for performing the initial connection procedure of the first terminal.
[0029] In another aspect, the scheduling information may include information regarding the start PRB (physical resource block) of the first DL BWP activated for the execution of the initial connection procedure of the first terminal.
[0030] In another aspect, the method further comprises the step of receiving SIB1 for the second terminal, wherein the SIB1 may include configuration information for an optional connection procedure for the initial connection of the first terminal.
[0031] In another aspect, information regarding the CORESET for the first terminal can be obtained through the first SSB defined separately from the second SSB regarding the second terminal. Effects of the invention
[0032] According to an embodiment of the present invention, a RedCap terminal can smoothly perform initial cell connection, perform random connection procedures without conflict with existing legacy type terminals, and perform communication based on various frequency hopping designs.
[0033] The effects obtainable from the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below. Brief explanation of the drawing
[0034] Figure 1 shows an example of a wireless frame structure used in a wireless communication system. Figure 2 shows an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. Figure 3 is a diagram illustrating a physical channel used in a 3GPP system and a general signal transmission method using said physical channel. Figure 4 illustrates an SS / PBCH block for initial cell connection in a 3GPP NR system. Figure 5 illustrates a procedure for transmitting control information and control channels in a 3GPP NR system. Figure 6 is a diagram showing a CORESET (control resource set) through which a PDCCH (physical downlink control channel) can be transmitted in a 3GPP NR system. Figure 7 is a diagram illustrating a method for setting up a PDCCH search space in a 3GPP NR system. Figure 8 is a conceptual diagram explaining carrier aggregation. Figure 9 is a diagram illustrating single-carrier communication and multi-carrier communication. Figure 10 is a diagram illustrating an example where a cross-carrier scheduling technique is applied. FIG. 11 is a block diagram showing the configuration of a terminal and a base station, respectively, according to an embodiment of the present invention. Figure 12 shows an initial connection method according to an example. FIG. 13 is a diagram showing an initial cell connection method according to one embodiment of the present invention. FIG. 14 is a diagram showing an initial cell connection method and PRACH resource setting according to an embodiment of the present invention. FIG. 15 is a diagram showing an initial cell connection method and PRACH resource setting according to another embodiment of the present invention. FIG. 16 is a diagram showing an initial cell connection method and PRACH resource setting according to another embodiment of the present invention. FIG. 17 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention. FIG. 18 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention. FIG. 19 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention. FIG. 20 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention. FIG. 21 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention. FIG. 22 is a diagram showing PRACH resource settings according to another embodiment of the present invention. Figure 23 is a diagram showing the scheduling of a physical uplink shared channel in the time domain. Figure 24 is a diagram showing the scheduling of a physical uplink shared channel in the frequency domain. FIG. 25 is a diagram showing the repeated transmission of a physical uplink shared channel according to an example. Figure 26 is a diagram showing the scheduling of a physical uplink control channel. Figure 27 is a diagram showing the repeated transmission of a physical uplink control channel. Figure 28 is a diagram showing frequency hopping. Figure 29 is a diagram showing broadband frequency hopping. FIG. 30 is a diagram showing broadband frequency hopping according to one embodiment of the present invention. FIG. 31 is a diagram showing broadband frequency hopping according to another embodiment of the present invention. FIG. 32 is a diagram showing broadband frequency hopping according to another embodiment of the present invention. FIG. 33 is a diagram showing broadband frequency hopping according to one embodiment of the present invention. Figure 34 shows a PUSCH repetition type B according to an example. FIG. 35 is a diagram showing a gap symbol placed in a preceding nominal repetition in a type-B PUSCH repetition according to one embodiment of the present invention. FIG. 36 is a diagram showing a gap symbol placed in a trailing nominal repetition in a type-B PUSCH repetition according to one embodiment of the present invention. FIG. 37 is a diagram showing gap symbols distributed in a type-B PUSCH repetition according to one embodiment of the present invention. FIG. 38 is a diagram showing gap symbols placed in a large number of nominal repetitions in a type-B PUSCH repetition according to one embodiment of the present invention. FIG. 39 is a diagram showing gap symbols placed in nominal repetitions with a small number in a type-B PUSCH repetition according to one embodiment of the present invention. FIG. 40 is a diagram showing gap symbols arranged so that no orphan symbols occur in a type-B PUSCH repetition according to one embodiment of the present invention. FIG. 41 is a diagram showing the addition of a gap symbol after a nominal repetition in a type-B PUSCH repetition according to one embodiment of the present invention. FIG. 42 is a diagram showing gap symbols considering invalid UL symbols and orphan symbols in a type-B PUSCH iteration according to one embodiment of the present invention. Specific details for implementing the invention
[0035] The terms used in this specification have been selected to be as widely used as possible, taking into account their functions in the present invention; however, these may vary depending on the intent, convention, or emergence of new technologies of those skilled in the art. In addition, in certain cases, terms have been arbitrarily selected by the applicant, and in such cases, their meanings will be described in the relevant description of the invention. Therefore, it should be noted that the terms used in this specification should be interpreted based on their actual meanings and the overall content of this specification, rather than merely their names.
[0036] Throughout the specification, when a configuration is described as being "connected" to another configuration, this includes not only cases where they are "directly connected," but also cases where they are "electrically connected" with other components interposed between them. Furthermore, when a configuration is described as "including" a specific component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. In addition, the limitation "greater than or equal to" or "less than or equal to" based on a specific threshold value may be appropriately replaced with "greater than" or "less than," respectively, depending on the embodiment.
[0037] The following technologies can be used in various wireless access 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 using radio technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented using radio 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 radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of the UMTS (universal mobile telecommunications system). 3GPP LTE (long term evolution) is part of E-UMTS (evolved UMTS) using E-UTRA, and LTE-A (LTE-advanced) is an evolved version of 3GPP LTE. It is a system designed separately from 3GPP NR LTE / LTE-A to support the services of eMBB (enhanced Mobile BroadBand), URLLC (Ultra-Reliable and Low Latency Communication), and mMTC (massive Machine Type Communication), which are requirements of IMT-2020.For clarity of explanation, the description is based primarily on 3GPP NR, but the technical concept of the present invention is not limited thereto.
[0038] Unless otherwise specified in this specification, a base station may include a gNB (next generation node B) as defined in 3GPP NR. Additionally, unless otherwise specified, a terminal may include a UE (user equipment).
[0039] Figure 1 shows an example of a radio frame structure used in a wireless communication system. Referring to Figure 1, a radio frame (or radio frame) used in a 3GPP NR system is 10 ms (Δf max N f / 100) * T c It can have a length of ). In addition, the wireless frame consists of 10 subframes (SF) of equal size. Here, Δf max =480*10 3 Hz, N f =4096, T c =1 / (Δf ref *N f,ref ), Δf ref =15*10 3 Hz, N f,ref = 2048. Ten subframes within a single radio frame can each be numbered from 0 to 9. Each subframe has a length of 1ms and can consist of one or more slots depending on the subcarrier spacing (SCS). More specifically, the available subcarrier spacing in the 3GPP NR system is 15*2 μ It is kHz. μ is the subcarrier spacing configuration factor (SCS configuration), and μ can have values from 0 to 4. That is, 15kHz, 30kHz, 60kHz, 120kHz, or 240kHz can be used as the subcarrier spacing. A 1ms subframe is 2μ It can be composed of slots. In this case, the length of each slot is 2 -μ It is ms. 2 within one subframe μ The slots are each from 0 to 2 μ Numbers from 0 to 1 can be assigned. Additionally, the slots within a single wireless frame can be assigned from 0 to 10*2 respectively. μ - Numbers up to 1 may be assigned. Time resources may be distinguished by at least one of a wireless frame number (also called a wireless frame index), a subframe number (also called a subframe index), and a slot number (or slot index).
[0040] FIG. 2 illustrates an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. In particular, FIG. 2 illustrates the structure of a resource grid in a 3GPP NR system. There is one resource grid per antenna port. Referring to FIG. 2, a slot contains multiple orthogonal frequency division multiplexing (OFDM) symbols in the time domain and multiple resource blocks (RB) in the frequency domain. An OFDM symbol may also refer to a single symbol interval. Unless otherwise specified, an OFDM symbol may simply be referred to as a symbol. Referring to FIG. 2, the signal transmitted in each slot is N size,μ grid,x * N RB sc N subcarriers and N slot symb It can be represented as a resource grid composed of OFDM symbols. Here, x=DL for the downlink resource grid and x=UL for the uplink resource grid. N size,μ grid,xrepresents the number of resource blocks (RB) according to the subcarrier spacing factor μ (where x is DL or UL), and N slot symb represents the number of OFDM symbols in the slot. N RB sc is the number of subcarriers constituting a single RB, N RB sc = 12. Depending on the multiple access method, OFDM symbols can be referred to as CP-OFDM (cyclic prefix OFDM) symbols or DFT-S-OFDM (discrete Fourier transform spread OFDM) symbols.
[0041] The number of OFDM symbols included in a single slot may vary depending on the length of the cyclic prefix (CP). For example, in the case of a normal CP, a single slot may contain 14 OFDM symbols, whereas in the case of an extended CP, a single slot may contain 12 OFDM symbols. In a specific embodiment, the extended CP may be used only at a 60 kHz subcarrier interval. Although FIG. 2 illustrates a case where a single slot consists of 14 OFDM symbols for convenience of explanation, embodiments of the present invention can be applied in the same manner to slots having a different number of OFDM symbols. Referring to FIG. 2, each OFDM symbol is, in the frequency domain, N size,μ grid,x * N RB sc It includes several subcarriers. The types of subcarriers can be divided into data subcarriers for data transmission, reference signal subcarriers for the transmission of reference signals, and guard bands. The carrier frequency is also called the center frequency (fc).
[0042] One RB is N in the frequency domainRB sc It can be defined as 12 consecutive subcarriers. For reference, a resource consisting of one OFDM symbol and one subcarrier can be referred to as a resource element (RE) or tone. Therefore, one RB is N slot symb * N RB sc It can be composed of resource elements. Each resource element within the resource grid can be uniquely defined by an index pair (k, l) within a single slot. k ranges from 0 to N in the frequency domain. size,μ grid,x * N RB sc It is an index assigned up to 1, where l ranges from 0 to N in the time domain. slot symb - It can be an index assigned up to 1.
[0043] In order for a terminal to receive a signal from a base station or transmit a signal to a base station, the terminal's time / frequency synchronization may need to be aligned with the base station's time / frequency synchronization. This is because only when the base station and the terminal are synchronized can the terminal determine the time and frequency parameters necessary to perform the demodulation of the DL signal and the transmission of the UL signal at the correct time.
[0044] Each symbol of a radio frame operating in TDD (time division duplex) or unpaired spectrum may consist of at least one of a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol. In FDD (frequency division duplex) or paired spectrum, a radio frame operating as a downlink carrier may consist of a downlink symbol or a flexible symbol, and a radio frame operating as an uplink carrier may consist of an uplink symbol or a flexible symbol. Downlink transmission is possible with a downlink symbol but not with an uplink symbol, and uplink transmission is possible with an uplink symbol but not with a downlink symbol. Whether a flexible symbol is used for downlink or uplink transmission may be determined based on the signal.
[0045] Information regarding the type of each symbol, that is, information indicating one of downlink symbols, uplink symbols, or flexible symbols, may be composed of a cell-specific (or common) radio resource control (RRC) signal. Additionally, information regarding the type of each symbol may be further composed of a terminal-specific (or dedicated) RRC signal. The base station uses the cell-specific RRC signal to provide i) the period of the cell-specific slot configuration, ii) the number of slots containing only downlink symbols from the beginning of the cell-specific slot configuration period, iii) the number of downlink symbols from the first symbol of the slot immediately following the slot containing only downlink symbols, iv) the number of slots containing only uplink symbols from the end of the cell-specific slot configuration period, and v) the number of uplink symbols from the last symbol of the slot immediately preceding the slot containing only uplink symbols. Here, a symbol that is not composed of either uplink symbols or downlink symbols is a flexible symbol.
[0046] When information regarding the symbol type is configured as a terminal-specific RRC signal, the base station can signal whether the flexible symbol is a downlink symbol or an uplink symbol using a cell-specific RRC signal. In this case, the terminal-specific RRC signal cannot change the downlink symbol or uplink symbol configured by the cell-specific RRC signal to another symbol type. The terminal-specific RRC signal is for each slot, N of the corresponding slot slot symb Number of downlink symbols among the symbols, N of the corresponding slot slot symbThe number of uplink symbols among the symbols can be signaled. In this case, the downlink symbols of the slot can be configured consecutively from the first symbol to the i-th symbol of the slot. Additionally, the uplink symbols of the slot can be configured consecutively from the j-th symbol to the last symbol of the slot (where i <j). 슬롯에서 상향링크 심볼과 하향링크 심볼 어느 것으로도 구성되지 않은 심볼은 플랙서블 심볼이다.
[0047] The type of symbol composed of the RRC signal as described above can be referred to as a semi-static DL / UL configuration. In the semi-static DL / UL configuration composed of the RRC signal mentioned above, a flexible symbol can be indicated as a downlink symbol, an uplink symbol, or a flexible symbol through dynamic SFI (slot format information) transmitted to the physical downlink control channel (PDCCH). In this case, the downlink symbol or uplink symbol composed of the RRC signal is not changed to another symbol type. Table 1 provides examples of dynamic SFI that a base station can indicate to a terminal.
[0048] [Table 1]
[0049]
[0050] In Table 1, D represents the downlink symbol, U represents the uplink symbol, and X represents the flexible symbol. As shown in Table 1, up to two DL / UL switching operations may be allowed within one slot.
[0051] FIG. 3 is a diagram illustrating a physical channel used in a 3GPP system (e.g., NR) and a general signal transmission method using said physical channel. When the power of a terminal is turned on or the terminal newly enters a cell, the terminal performs an initial cell search operation (S101). Specifically, the terminal can synchronize with the base station during the initial cell search. 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. Afterward, the terminal can receive a physical broadcast channel from the base station to obtain broadcast information within the cell.
[0052] A terminal that has completed an initial cell search can obtain more specific system information than the system information obtained through the initial cell search by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to the information carried on the PDCCH (S102).
[0053] When a terminal first connects to a base station or when there are no wireless resources available for signal transmission, the terminal may perform a random access process with respect to the base station (steps S103 to S106). First, the terminal transmits a preamble through a physical random access channel (PRACH) (S103), and may receive a response message for the preamble from the base station through a PDCCH and a corresponding PDSCH (S104). If the terminal receives a valid random access response message, the terminal transmits data including its identifier, etc., to the base station through a physical uplink shared channel (PUSCH) as instructed by an uplink grant transmitted from the base station via the PDCCH (S105). Next, the terminal waits for the reception of a PDCCH as instructed by the base station to resolve collisions. If the terminal successfully receives a PDCCH with its identifier (S106), the random access process is terminated.
[0054] After the procedure described above, the terminal can perform PDCCH / PDSCH reception (S107) and transmission of the physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108) as a general uplink / downlink signal transmission procedure. In particular, the terminal can receive downlink control information (DCI) through the PDCCH. The DCI may include control information such as resource allocation information for the terminal. Additionally, the format of the DCI may vary depending on the purpose of use. The uplink control information (UCI) transmitted by the terminal to the base station via the uplink may include downlink / uplink ACK / NACK signals, CQI (channel quality indicator), PMI (precoding matrix index), RI (rank indicator), etc. Here, CQI, PMI, and RI may be included in CSI (channel state information). In the case of a 3GPP NR system, the terminal can transmit control information such as the aforementioned HARQ-ACK and CSI through PUSCH and / or PUCCH.
[0055] FIGS. 4a and 4b illustrate the SS (synchronization signal) / PBCH (physical broadcast channel) blocks for initial cell connection in a 3GPP NR system. When a terminal is powered on or wishes to connect to a new cell, it can acquire time and frequency synchronization with the cell and perform an initial cell search process. During the cell search process, the terminal [obtains] the cell's physical cell identity N cell IDIt can detect [this]. To do this, the terminal can synchronize with the base station by receiving synchronization signals, for example, a main synchronization signal (PSS) and a secondary synchronization signal (SSS), from the base station. At this time, the terminal can obtain information such as a cell identifier (identity, ID).
[0056] Referring to Figures 4a and 4b, the synchronization signal (SS) is described in more detail. The synchronization signal can be divided into PSS and SSS. PSS can be used to obtain time-domain synchronization and / or frequency-domain synchronization, such as OFDM symbol synchronization and slot synchronization. SSS can be used to obtain frame synchronization and cell group ID. Referring to Figure 4a and Table 2, the SS / PBCH block may consist of 20 RBs (= 240 subcarriers) consecutive in the frequency axis and 4 OFDM symbols consecutive in the time axis. In this case, within the SS / PBCH block, the PSS is transmitted through subcarriers 56 through 182 in the first OFDM symbol, and the SSS is transmitted through subcarriers 56 through 182 in the third OFDM symbol. Here, the lowest subcarrier index of the SS / PBCH block is assigned starting from 0. In the first OFDM symbol where the PSS is transmitted, the base station does not transmit signals through the remaining subcarriers, namely subcarriers 0 through 55 and 183 through 239. Also, in the third OFDM symbol where the SSS is transmitted, the base station does not transmit signals through subcarriers 48 through 55 and 183 through 191. The base station transmits the PBCH (physical broadcast channel) through the remaining REs excluding the above signals in the SS / PBCH block.
[0057] [Table 2]
[0058]
[0059] The SS identifies a total of 1,008 unique physical layer cell IDs through a combination of three PSSs and SSSs. Specifically, to ensure that each physical layer cell ID is part of only one physical layer cell identifier group, they can be grouped into 336 physical layer cell identifier groups, each containing three unique identifiers. Therefore, physical layer cell ID N cell ID = 3N (1) ID + N (2) ID is an index N within the range of 0 to 335 representing a physical layer cell-identifier group. (1) ID and an index N from 0 to 2 representing the physical layer cell-identifier within the physical layer cell-identifier group. (2) ID It can be uniquely defined by. The terminal can detect the PSS to identify one of three unique physical layer cell identifiers. Additionally, the terminal can detect the SSS to identify one of 336 physical layer cell IDs associated with the physical layer cell identifier. In this case, the sequence d of the PSS PSS (n) is as follows.
[0060] d PSS (n)=1-2x(m)
[0061] m=(n+43N (2) ID ) mod 127
[0062] 0≤n<127
[0063] Here, x(i+7)=(x(i+4)+x(i)) mod 2 and,
[0064] [x(6) x(5) x(4) x(3) x(2) x(1) x(0)]=[1 1 1 0 1 1 0] is given.
[0065] Also, the sequence d of the SSS SSS (n) is as follows.
[0066] d SSS (n)=[1-2x0((n+m0) mod 127][1-2x i ((n+m1) mod 127]
[0067] m0=15 floor (N (1) ID / 112)+5N (2) ID
[0068] m1=N (1) ID mod 112
[0069] 0≤n<127
[0070] Here, x0(i+7)=(x0(i+4)+x0(i)) mod 2
[0071] x1(i+7)=(x1(i+1)+x1(i)) mod 2 and,
[0072] [x0(6) x0(5) x0(4) x0(3) x0(2) x0(1) x0(0)]=[0 0 0 0 0 0 1]
[0073] [x1(6) x1(5) x1(4) x1(3) x1(2) x1(1) x1(0)]=[0 0 0 0 0 0 1] is given.
[0074] A wireless frame of length 10 ms can be divided into two half frames of length 5 ms. Referring to FIG. 4b, the slot in which the SS / PBCH block is transmitted within each half frame is described. The slot in which the SS / PBCH block is transmitted can be any one of cases A, B, C, D, or E. In case A, the subcarrier interval is 15 kHz, and the start time of the SS / PBCH block is {2, 8} + 14*n-th symbol. At this time, n can be 0 or 1 at a carrier frequency of 3 GHz or less. Also, at a carrier frequency between 3 GHz and 6 GHz or less, n can be 0, 1, 2, or 3. In case B, the subcarrier interval is 30 kHz, and the start time of the SS / PBCH block is {4, 8, 16, 20} + 28*n-th symbol. At this time, n can be 0 at a carrier frequency of 3 GHz or less. Additionally, at carrier frequencies greater than 3 GHz and less than or equal to 6 GHz, n can be 0 or 1. In case C, the subcarrier interval is 30 kHz, and the start time of the SS / PBCH block is {2, 8} + 14*n-th symbol. At this time, at carrier frequencies less than or equal to 3 GHz, n can be 0 or 1. Additionally, at carrier frequencies greater than 3 GHz and less than or equal to 6 GHz, n can be 0, 1, 2, or 3. In case D, the subcarrier interval is 120 kHz, and the start time of the SS / PBCH block is {4, 8, 16, 20} + 28*n-th symbol. At this time, at carrier frequencies greater than or equal to 6 GHz, n can be 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, or 18. In case E, the subcarrier interval is 240 kHz, and the start time of the SS / PBCH block is {8, 12, 16, 20, 32, 36, 40, 44} + 56*n-th symbol. At this time, at a carrier frequency of 6 GHz or higher, n can be 0, 1, 2, 3, 5, 6, 7, 8.
[0075] FIGS. 5A and 5B illustrate a procedure for transmitting control information and a control channel in a 3GPP NR system. Referring to FIG. 5A, a base station may add a cyclic redundancy check (CRC) masked (e.g., XOR operation) with a radio network temporary identifier (RNTI) to control information (e.g., downlink control information, DCI) (S202). The base station may scramble the CRC with an RNTI value determined according to the purpose / target of each control information. A common RNTI used by one or more terminals may include at least one of SI-RNTI (system information RNTI), P-RNTI (paging RNTI), RA-RNTI (random access RNTI), and TPC-RNTI (transmit power control RNTI). Additionally, a terminal-specific RNTI may include at least one of C-RNTI (cell temporary RNTI) and CS-RNTI. Afterwards, the base station can perform rate-matching according to the amount of resource(s) allocated for PDCCH transmission after performing channel encoding (e.g., polar coding) (S204) (S206). Afterwards, the base station can multiplex DCI(s) based on a CCE (control channel element)-based PDCCH structure (S208).
[0076] Additionally, the base station can apply additional processes (S210), such as scrambling, modulation (e.g., QPSK), and interleaving, to the multiplexed DCI(s) and then map them to the resources to be transmitted. A CCE is the basic resource unit for a PDCCH, and one CCE can be composed of multiple (e.g., 6) REGs (resource element groups). One REG can be composed of multiple (e.g., 12) REs. The number of CCEs used for one PDCCH can be defined as the aggregation level. In a 3GPP NR system, 1, 2, 4, 8, or 16 aggregation levels can be used. FIG. 5b is a diagram regarding CCE aggregation levels and the multiplexing of a PDCCH, showing the types of CCE aggregation levels used for one PDCCH and the CCE(s) transmitted in the control area accordingly.
[0077] FIG. 6 is a diagram illustrating a CORESET (control resource set) through which a PDCCH (physical downlink control channel) can be transmitted in a 3GPP NR system. A CORESET is a time-frequency resource through which a PDCCH, which is a control signal for a terminal, is transmitted. Additionally, the search space described later can be mapped to a single CORESET. Therefore, instead of monitoring all frequency bands to receive a PDCCH, the terminal can decode the PDCCH mapped to the CORESET by monitoring the time-frequency range designated as the CORESET. The base station can configure one or multiple CORESETs per cell for the terminal. A CORESET can be composed of up to three consecutive symbols along the time axis. Additionally, a CORESET can be composed of six consecutive PRBs along the frequency axis. In the embodiment of FIG. 5, CORESET#1 is composed of consecutive PRBs, while CORESET#2 and CORESET#3 are composed of discontinuous PRBs. CORESET can be located at any symbol within the slot. For example, in the embodiment of FIG. 5, CORESET#1 starts at the 1st symbol of the slot, CORESET#2 starts at the 5th symbol of the slot, and CORESET#9 starts at the 9th symbol of the slot.
[0078] FIG. 7 is a diagram illustrating a method for setting up a PDCCH search space in a 3GPP NR system. In order to transmit a PDCCH to a terminal, at least one search space may exist in each CORESET. In an embodiment of the present invention, the search space is a set of all time-frequency resources (hereinafter referred to as PDCCH candidates) where the terminal's PDCCH can be transmitted. The search space may include a common search space (common search space) that 3GPP NR terminals must search in common, and a terminal-specific search space (Terminal-specific or UE-specific search space) that a specific terminal must search for. In the common search space, PDCCHs configured to be searched in common by all terminals in a cell belonging to the same base station can be monitored. Additionally, the terminal-specific search space may be configured per terminal so that PDCCHs assigned to each terminal can be monitored at different search space locations depending on the terminal. In the case of terminal-specific search spaces, search spaces between terminals may partially overlap due to the limited control area where a PDCCH can be allocated. Monitoring a PDCCH involves blind decoding PDCCH candidates within the search space. If blind decoding is successful, it is expressed that the PDCCH is (successfully) detected / received, and if blind decoding fails, it is expressed that the PDCCH is not detected / received or is not successfully detected / received.
[0079] For convenience of explanation, a PDCCH scrambled with a group common (GC) RNTI already known to terminals to transmit downlink control information to one or more terminals is referred to as a group common (GC) PDCCH or a common PDCCH. Additionally, a PDCCH scrambled with a terminal-specific RNTI already known to a specific terminal to transmit uplink scheduling information or downlink scheduling information to a specific terminal is referred to as a terminal-specific PDCCH. The common PDCCH may be included in a common search space, and the terminal-specific PDCCH may be included in a common search space or a terminal-specific PDCCH.
[0080] The base station can notify each terminal or group of terminals via PDCCH of information related to resource allocation for the transmission channels PCH (paging channel) and DL-SCH (downlink-shared channel) (i.e., DL Grant) or information related to resource allocation for UL-SCH and HARQ (hybrid automatic repeat request) (i.e., UL Grant). The base station can transmit PCH transmission blocks and DL-SCH transmission blocks via PDSCH. The base station can transmit data excluding specific control information or specific service data via PDSCH. Additionally, the terminal can receive data excluding specific control information or specific service data via PDSCH.
[0081] A base station may transmit PDSCH data by including information in the PDCCH regarding which terminal (one or more terminals) the data is being transmitted to and how the terminal should receive and decode the PDSCH data. For example, assume that a DCI transmitted to a specific PDCCH is CRC-masked with an RNTI named "A," that the DCI indicates that the PDSCH is allocated to a radio resource named "B" (e.g., frequency location), and indicates transmission format information named "C" (e.g., transmission block size, modulation method, coding information, etc.). The terminal monitors the PDCCH using the RNTI information it possesses. In this case, if there is a terminal that blind-decodes the PDCCH with the "A" RNTI, that terminal receives the PDCCH and, through the information in the received PDCCH, receives the PDSCH indicated by "B" and "C".
[0082] Table 3 shows an example of a PUCCH (physical uplink control channel) used in a wireless communication system.
[0083] [Table 3]
[0084]
[0085] PUCCH can be used to transmit the following uplink control information (UCI).
[0086] - SR (scheduling request): Information used to request uplink UL-SCH resources.
[0087] - HARQ-ACK: A response to a PDCCH (indicating a DL SPS release) and / or a response to a downlink transport block (TB) on the PDSCH. HARQ-ACK indicates whether information transmitted via the PDCCH or PDSCH has been received. HARQ-ACK responses include a positive ACK (simply ACK), a negative ACK (hereinafter NACK), a DTX (discontinuous transmission), or a NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ-ACK / NACK and ACK / NACK. Generally, ACK is represented by a bit value of 1 and NACK can be represented by a bit value of 0.
[0088] - CSI (channel state information): This is feedback information regarding the downlink channel. It is generated by the terminal based on the CSI-RS (reference signal) transmitted by the base station. MIMO (multiple input multiple output) related feedback information includes RI (rank indicator) and PMI (precoding matrix indicator). CSI can be divided into CSI Part 1 and CSI Part 2 depending on the information represented by the CSI.
[0089] In 3GPP NR systems, five PUCCH formats can be used to support various service scenarios, various channel environments, and frame structures.
[0090] PUCCH Format 0 is a format capable of transmitting 1-bit or 2-bit HARQ-ACK information or SR. PUCCH Format 0 can be transmitted via one or two OFDM symbols in the time axis and one RB in the frequency axis. When PUCCH Format 0 is transmitted via two OFDM symbols, the same sequence for both symbols can be transmitted via different RBs. This allows the terminal to obtain frequency diversity gain. More specifically, the terminal M bit Bit UCI (M bit The value of the cyclic shift m depending on = 1 or 2) cs Determine and a base sequence of length 12 with a given value m cs A cyclically shifted sequence can be transmitted by mapping it to 12 REs of 1 OFDM symbol and 1 PRB. The number of cyclic shifts available to the terminal is 12, and M bit When = 1, 1-bit UCI 0 and 1 can be represented as a sequence corresponding to two cyclic shifts with a difference of 6 cyclic shift values. Also, M bit In the case where = 2, 2-bit UCI 00, 01, 11, 10 can be represented as a sequence of four cyclic shifts with a difference of 3 cyclic shift values.
[0091] PUCCH Format 1 can transmit 1-bit or 2-bit HARQ-ACK information or SR. PUCCH Format 1 can be transmitted via consecutive OFDM symbols in the time axis and a single PRB in the frequency axis. Here, the number of OFDM symbols occupied by PUCCH Format 1 can be one of 4 to 14. More specifically, M bit = A single UCI can be modulated with BPSK. The terminal is M bitA UCI with =2 can be modulated by QPSK (quadrature phase shift keying). A signal is obtained by multiplying the modulated complex valued symbol d(0) by a sequence of length 12. The terminal transmits the obtained signal by spreading it as a time-axis orthogonal cover code (OCC) onto the even-numbered OFDM symbols assigned to PUCCH format 1. In PUCCH format 1, the maximum number of different terminals multiplexed into the same RB is determined by the length of the OCC used. A demodulation reference signal (DMRS) can be spread as an OCC and mapped to the odd-numbered OFDM symbols of PUCCH format 1.
[0092] PUCCH Format 2 can transmit UCIs exceeding 2 bits. PUCCH Format 2 can be transmitted via one or two OFDM symbols in the time axis and one or multiple RBs in the frequency axis. When PUCCH Format 2 is transmitted via two OFDM symbols, the same sequence can be transmitted via different RBs through the two OFDM symbols. This allows the terminal to obtain frequency diversity gain. More specifically, M bit Bit UCI (M bit >2) is bit-level scrambled and QPSK modulated and mapped to RB(s) of one or two OFDM symbols. Here, the number of RBs can be one of 1 to 16.
[0093] PUCCH Format 3 or PUCCH Format 4 can transmit a UCI exceeding 2 bits. PUCCH Format 3 or PUCCH Format 4 can be transmitted via consecutive OFDM symbols in the time axis and a single PRB in the frequency axis. The number of OFDM symbols occupied by PUCCH Format 3 or PUCCH Format 4 can be one of 4 to 14. Specifically, the terminal is M bit Bit UCI (M bit Modulate >2) with π / 2-BPSK (Binary Phase Shift Keying) or QPSK to obtain complex number symbols d(0)~d(M symb -1) can be generated. Here, if π / 2-BPSK is used, M symb =M bit and if you use QPSK, M symb =M bit / 2. The terminal may not apply block-unit spreading to PUCCH format 3. However, the terminal may apply block-unit spreading to one RB (i.e., 12 subcarriers) using a PreDFT-OCC of length 12 so that PUCCH format 4 can have two or four multiplexing capacities. The terminal may transmit the spread signal by transmitting precoding (or DFT-precoding) the spread signal and mapping it to each RE.
[0094] At this time, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 can be determined by the length of the UCI transmitted by the terminal and the maximum code rate. When the terminal uses PUCCH format 2, the terminal can transmit HARQ-ACK information and CSI information together through PUCCH. If the number of RBs that the terminal can transmit is greater than the maximum number of RBs available for PUCCH format 2, PUCCH format 3, or PUCCH format 4, the terminal may transmit only the remaining UCI information without transmitting some UCI information according to the priority of the UCI information.
[0095] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured via an RRC signal to indicate frequency hopping within a slot. When frequency hopping is configured, the index of the RB to be frequency-hopped can be configured via an RRC signal. When PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted over N OFDM symbols in the time axis, the first hop may have floor (N / 2) OFDM symbols and the second hop may have ceil (N / 2) OFDM symbols.
[0096] PUCCH format 1, PUCCH format 3, or PUCCH format 4 may be configured to be transmitted repeatedly across multiple slots. In this case, the number of slots K in which PUCCH is transmitted repeatedly may be configured by an RRC signal. The PUCCH transmitted repeatedly must start at the same position of the OFDM symbol within each slot and have the same length. If any of the OFDM symbols in the slot in which the terminal is to transmit the PUCCH is indicated as a DL symbol by the RRC signal, the terminal may not transmit the PUCCH in that slot but may defer transmission to the next slot.
[0097] Meanwhile, in a 3GPP NR system, a terminal can perform transmission and reception using a bandwidth that is less than or equal to the bandwidth of the carrier (or cell). To this end, the terminal may receive a bandwidth part (BWP) composed of a continuous portion of the carrier's bandwidth. A terminal operating under TDD or in unpaired spectrum may receive up to four DL / UL BWP pairs for one carrier (or cell). Additionally, the terminal may activate one DL / UL BWP pair. A terminal operating under FDD or in paired spectrum may receive up to four DL BWPs for the downlink carrier (or cell) and up to four UL BWPs for the uplink carrier (or cell). The terminal may activate one DL BWP and one UL BWP for each carrier (or cell). The terminal may not receive or transmit on time-frequency resources other than the active BWP. The active BWP may be referred to as the active BWP.
[0098] A base station may indicate the active BWP among the configured BWPs to the terminal via downlink control information (DCI). The BWP indicated by the DCI is activated, and the other configured BWP(s) are deactivated. In a carrier (or cell) operating in TDD, the base station may include a bandwidth part indicator (BPI) indicating the active BWP in the DCI that schedules the PDSCH or PUSCH to change the terminal's DL / UL BWP pair. The terminal receives the DCI that schedules the PDSCH or PUSCH and can identify the active DL / UL BWP pair based on the BPI. In the case of a downlink carrier (or cell) operating in FDD, the base station may include a BPI indicating the active BWP in the DCI that schedules the PDSCH to change the terminal's DL BWP. In the case of an uplink carrier (or cell) operating as an FDD, the base station may include a BPI that indicates the BWP to be activated in the DCI that schedules the PUSCH to change the terminal's UL BWP.
[0099] Figure 8 is a conceptual diagram explaining carrier aggregation.
[0100] Carrier aggregation refers to a method in which a terminal uses multiple frequency blocks or (in a logical sense) cells composed of uplink resources (or component carriers) and / or downlink resources (or component carriers) to form one large logical frequency band, in order for a wireless communication system to use a wider frequency band. A single component carrier may also be referred to as a PCell (Primary cell), SCell (Secondary Cell), or PScell (Primary SCell). However, for the convenience of explanation, the term component carrier will be used consistently below.
[0101] Referring to FIG. 8, as an example of a 3GPP NR system, the entire system band may include up to 16 component carriers, and each component carrier may have a bandwidth of up to 400 MHz. A component carrier may include one or more physically contiguous subcarriers. FIG. 8 is illustrated as if each component carrier has the same bandwidth, but this is merely an example, and each component carrier may have different bandwidths. Additionally, although each component carrier is illustrated as being adjacent to each other in the frequency axis, the figure is illustrated in a logical sense, and each component carrier may be physically adjacent to each other or separated.
[0102] Different center frequencies may be used in each component carrier. Additionally, a single common center frequency may be used in physically adjacent component carriers. In the embodiment of FIG. 8, assuming that all component carriers are physically adjacent, center frequency A may be used in all component carriers. Additionally, assuming that each component carrier is not physically adjacent, center frequency A and center frequency B may be used in each component carrier.
[0103] When the total system bandwidth is expanded through carrier aggregation, the frequency band used for communication with each terminal can be defined in terms of component carriers. Terminal A can use the total system bandwidth of 100 MHz and performs communication using all five component carriers. Terminals B1 through B5 can use only a 20 MHz bandwidth and perform communication using a single component carrier. Terminals C1 and C2 can use a 40 MHz bandwidth and each perform communication using two component carriers. The two component carriers may or may not be logically or physically adjacent. The embodiment of FIG. 8 illustrates a case where Terminal C1 uses two non-adjacent component carriers, and Terminal C2 uses two adjacent component carriers.
[0104] FIG. 9 is a diagram illustrating single-carrier communication and multi-carrier communication. In particular, FIG. 9(a) illustrates a subframe structure of a single carrier, and FIG. 9(b) illustrates a subframe structure of a multi-carrier.
[0105] Referring to FIG. 9(a), a typical wireless communication system can perform data transmission or reception through one DL band and a corresponding UL band in the case of FDD mode. In another specific embodiment, in the case of TDD mode, the wireless communication system can divide the wireless frame into uplink time units and downlink time units in the time domain and perform data transmission or reception through the uplink / downlink time units. Referring to FIG. 9(b), three 20MHz component carriers (CCs) can be aggregated in the UL and DL, respectively, to support a bandwidth of 60MHz. Each CC can be adjacent or non-adjacent to one another in the frequency domain. FIG. 9(b) illustrates a case where the bandwidths of the UL CC and the DL CC are both identical and symmetrical for convenience, but the bandwidths of each CC can be determined independently. Additionally, asymmetric carrier aggregation is possible where the number of UL CCs and the number of DL CCs are different. A DL / UL CC assigned / configured to a specific terminal via RRC can be referred to as the serving DL / UL CC of the specific terminal.
[0106] A base station can communicate with a terminal by activating some or all of the terminal's serving CCs or by deactivating some of the CCs. The base station may change the CCs that are activated / deactivated and may change the number of CCs that are activated / deactivated. If the base station allocates available CCs to the terminal in a cell-specific or terminal-specific manner, at least one of the CCs once allocated may not be deactivated unless the CC allocation to the terminal is completely reconfigured or the terminal undergoes a handover. One CC that is not deactivated to the terminal is referred to as the primary CC (PCC) or PCell (primary cell), and the CC that the base station can freely activate / deactivate is referred to as the secondary CC (SCC) or SCell (secondary cell).
[0107] Meanwhile, 3GPP NR uses the concept of a cell to manage radio resources. A cell is defined as a combination of downlink and uplink resources, that is, a combination of a DL CC and an UL CC. A cell can consist of a DL resource alone or a combination of a DL resource and an UL resource. Where carrier aggregation is supported, the linkage between the carrier frequency of a DL resource (or DL CC) and the carrier frequency of a UL resource (or UL CC) can be indicated by system information. The carrier frequency refers to the center frequency of each cell or CC. A cell corresponding to a PCC is referred to as a PCell, and a cell corresponding to an SCC is referred to as a SCell. In the downlink, the carrier corresponding to a PCell is a DL PCC, and in the uplink, the carrier corresponding to a PCell is an UL PCC. Similarly, in the downlink, the carrier corresponding to a SCell is a DL SCC, and in the uplink, the carrier corresponding to a SCell is an UL SCC. Depending on the terminal capability, the serving cell(s) may consist of one PCell and zero or more SCells. For a UE in the RRC_CONNECTED state but where carrier aggregation is not enabled or does not support carrier aggregation, there is only one serving cell consisting only of PCells.
[0108] As previously mentioned, the term "cell" used in carrier aggregation is distinguished from the term "cell" which refers to a specific geographical area where communication services are provided by a single base station or a single antenna group. That is, a component carrier may also be referred to as a scheduling cell, a scheduled cell, a PCell (Primary cell), a SCell (Secondary Cell), or a PScell (Primary SCell). However, in order to distinguish between a cell referring to a specific geographical area and a cell in carrier aggregation, the present invention refers to a cell in carrier aggregation as CC, and a cell in a geographical area as a cell.
[0109] FIG. 10 is a diagram illustrating an example in which a cross-carrier scheduling technique is applied. When cross-carrier scheduling is configured, a control channel transmitted through the first CC can schedule a data channel transmitted through the first CC or the second CC using a carrier indicator field (CIF). The CIF is included within the DCI. In other words, a scheduling cell is configured, and DL grants / UL grants transmitted in the PDCCH area of the scheduling cell schedule the PDSCH / PUSCH of the scheduled cell. That is, a search area for multiple component carriers exists in the PDCCH area of the scheduling cell. A PCell is basically a scheduling cell, and a specific SCell can be designated as a scheduling cell by an upper layer.
[0110] In the embodiment of FIG. 10, it is assumed that three DL CCs are merged. Here, DL component carrier #0 is assumed to be a DL PCC (or PCell), and DL component carrier #1 and DL component carrier #2 are assumed to be DL SCCs (or SCell). Additionally, it is assumed that the DL PCC is configured as a PDCCH monitoring CC. If cross-carrier scheduling is not configured by terminal-specific (or terminal-group-specific or cell-specific) upper-layer signaling, the CIF is disabled, and each DL CC can transmit only the PDCCH that schedules its own PDSCH without a CIF according to the NR PDCCH rule (non-cross-carrier scheduling, self-carrier scheduling). On the other hand, when cross-carrier scheduling is configured by terminal-specific (or terminal-group-specific or cell-specific) upper-layer signaling, CIF is enabled, and a specific CC (e.g., DL PCC) can use CIF to transmit not only the PDCCH that schedules the PDSCH of DL CC A but also the PDCCH that schedules the PDSCH of another CC (cross-carrier scheduling). On the other hand, no PDCCH is transmitted from other DL CCs. Therefore, depending on whether cross-carrier scheduling is configured for the terminal, the terminal monitors the PDCCH that does not contain CIF to receive the self-carrier scheduled PDSCH, or monitors the PDCCH that contains CIF to receive the cross-carrier scheduled PDSCH.
[0111] Meanwhile, FIGS. 9 and 10 illustrate the subframe structure of a 3GPP LTE-A system, but the same or similar configuration may also be applied to a 3GPP NR system. However, in a 3GPP NR system, the subframes of FIGS. 9 and 10 may be replaced with slots.
[0112] FIG. 11 is a block diagram illustrating the configuration of a terminal and a base station, respectively, according to an embodiment of the present disclosure. In an embodiment of the present disclosure, the terminal may be implemented as various types of wireless communication devices or computing devices that ensure portability and mobility. The terminal may be referred to as a User Equipment (UE), Station (STA), Mobile Subscriber (MS), etc. Additionally, in an embodiment of the present disclosure, the base station may control and manage cells (e.g., macro cells, femto cells, pico cells, etc.) corresponding to a service area, and perform functions such as signal transmission, channel assignment, channel monitoring, self-diagnosis, and relay. The base station may be referred to as a Next Generation Node (gNB) or Access Point (AP), etc.
[0113] As described, a terminal (100) according to one embodiment of the present disclosure may include a processor (110), a communication module (120), a memory (130), a user interface (140), and a display unit (150).
[0114] First, the processor (110) can execute various commands or programs and process data within the terminal (100). Additionally, the processor (110) can control the overall operation including each unit of the terminal (100) and control the transmission and reception of data between the units. Here, the processor (110) may be configured to perform operations according to the embodiments described in the present disclosure. For example, the processor (110) may receive slot configuration information, determine the configuration of the slot based thereon, and perform communication according to the determined slot configuration.
[0115] Next, the communication module (120) may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module (120) may be equipped with a plurality of network interface cards (NICs), such as cellular communication interface cards (121, 122) and unlicensed band communication interface cards (123), either internally or externally. Although the communication module (120) is depicted as an integrated module in the drawing, each network interface card may be arranged independently according to circuit configuration or purpose, unlike in the drawing.
[0116] A cellular communication interface card (121) can transmit and receive wireless signals with at least one of a base station (200), an external device, and a server using a mobile communication network, and can provide cellular communication services in a first frequency band based on instructions from a processor (110). According to one embodiment, the cellular communication interface card (121) may include at least one NIC module using a frequency band of less than 6 GHz. At least one NIC module of the cellular communication interface card (121) can independently perform cellular communication with at least one of a base station (200), an external device, and a server according to a cellular communication standard or protocol of a frequency band of less than 6 GHz supported by the NIC module.
[0117] A cellular communication interface card (122) can transmit and receive wireless signals with at least one of a base station (200), an external device, and a server using a mobile communication network, and can provide cellular communication services in a second frequency band based on instructions from a processor (110). According to one embodiment, the cellular communication interface card (122) may include at least one NIC module using a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card (122) can independently perform cellular communication with at least one of a base station (200), an external device, and a server according to a cellular communication standard or protocol of a frequency band of 6 GHz or higher supported by the NIC module.
[0118] The unlicensed band communication interface card (123) transmits and receives wireless signals with at least one of a base station (200), an external device, and a server using a third frequency band which is an unlicensed band, and provides unlicensed band communication services based on instructions from a processor (110). The unlicensed band communication interface card (123) may include at least one NIC module that uses the unlicensed band. For example, the unlicensed band may be a band of 2.4 GHz or 5 GHz. At least one NIC module of the unlicensed band communication interface card (123) may perform wireless communication with at least one of a base station (200), an external device, and a server independently or dependently according to the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.
[0119] Next, the memory (130) stores a control program used in the terminal (100) and various data associated therewith. This control program may include a specific program required for the terminal (100) to perform wireless communication with at least one of a base station (200), an external device, and a server.
[0120] Next, the user interface (140) includes various types of input / output means provided in the terminal (100). That is, the user interface (140) can receive user input using various input means, and the processor (110) can control the terminal (100) based on the received user input. In addition, the user interface (140) can perform output based on the command of the processor (110) using various output means.
[0121] Next, the display unit (150) outputs various images to the display screen. The display unit (150) can output various display objects, such as content executed by the processor (110) or a user interface based on control commands of the processor (110).
[0122] Additionally, a base station (200) according to one embodiment of the present disclosure may include a processor (210), a communication module (220), and a memory (230).
[0123] First, the processor (210) can execute various commands or programs and process data within the base station (200). Additionally, the processor (210) can control the overall operation including each unit of the base station (200) and control the transmission and reception of data between the units. Here, the processor (210) may be configured to perform operations according to the embodiments described in the present disclosure. For example, the processor (210) may signal slot configuration information and perform communication according to the signaled slot configuration.
[0124] Next, the communication module (220) may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module (120) may be equipped with a plurality of network interface cards, such as cellular communication interface cards (221, 222) and unlicensed band communication interface cards (223), in an internal or external form. Although the communication module (220) is shown as an integrated module in the drawing, each network interface card may be arranged independently according to circuit configuration or purpose, unlike in the drawing.
[0125] A cellular communication interface card (221) can transmit and receive wireless signals with at least one of the above-described terminal (100), external device, and server using a mobile communication network, and can provide cellular communication services in a first frequency band based on instructions from a processor (210). According to one embodiment, the cellular communication interface card (221) may include at least one NIC module using a frequency band of less than 6 GHz. At least one NIC module of the cellular communication interface card (221) can independently perform cellular communication with at least one of the terminal (100), external device, and server according to a cellular communication standard or protocol of a frequency band of less than 6 GHz supported by the NIC module.
[0126] A cellular communication interface card (222) can transmit and receive wireless signals with at least one of a terminal (100), an external device, and a server using a mobile communication network, and can provide cellular communication services in a second frequency band based on instructions from a processor (210). According to one embodiment, the cellular communication interface card (222) may include at least one NIC module using a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card (222) can independently perform cellular communication with at least one of a terminal (100), an external device, and a server according to a cellular communication standard or protocol of a frequency band of 6 GHz or higher supported by the NIC module.
[0127] The unlicensed band communication interface card (223) transmits and receives wireless signals with at least one of a terminal (100), an external device, and a server using a third frequency band which is an unlicensed band, and provides unlicensed band communication services based on instructions from a processor (210). The unlicensed band communication interface card (223) may include at least one NIC module that uses the unlicensed band. For example, the unlicensed band may be a band of 2.4 GHz or 5 GHz. At least one NIC module of the unlicensed band communication interface card (223) may perform wireless communication with at least one of a terminal (100), an external device, and a server independently or dependently according to the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.
[0128] The terminal (100) and base station (200) illustrated in FIG. 11 are block diagrams according to an embodiment of the present disclosure, wherein the separated blocks represent logically distinguished elements of the device. Accordingly, the elements of the device described above may be mounted as a single chip or as a plurality of chips depending on the design of the device. Additionally, some components of the terminal (100), such as a user interface (140) and a display unit (150), may be optionally provided in the terminal (100). Furthermore, the user interface (140) and the display unit (150), etc., may be additionally provided in the base station (200) as needed.
[0129] I. Initial Connection Method for RedCap Terminal
[0130] FIG. 12 illustrates an initial connection method according to an example. Hereinafter, terminals of Rel-15 to Rel-16 are referred to as legacy type terminals (legacy UE), and FIG. 12 is a general initial connection process performed by a legacy type terminal.
[0131] Referring to FIG. 12, the terminal receives an SSB from the base station. At this time, a frequency and time domain in which the SSB can be transmitted may be defined. The terminal can receive the SSB within the said frequency and time domain. The SSB consists of a PSS, an SSS, and a PBCH. By receiving the PSS and the SSS, the terminal synchronizes the downlink and can determine the physical cell ID. Additionally, by receiving the PBCH, the terminal can receive the master information block (MIB) included in the PBCH.
[0132] The above MIB contains the most basic information of the cell and configuration information of the basic CORESET (i.e., CORESET0) and Type-0 search space. The terminal can monitor and receive PDCCH based on the configuration information of CORESET0 and Type-0 search space. The above PDCCH can transmit DCI format 1_0 with a scrambled CRC as SI-RNTI. The above DCI format 1_0 can schedule PDSCH. The above PDSCH can transmit SIB1 to the terminal, which contains cell common information necessary for the terminal to connect to the cell.
[0133] The terminal can receive cell common information from SIB1 transmitted by the PDSCH and receive configuration information of the PRACH. The terminal can transmit the PRACH according to the configuration information of the PRACH. Through the transmission of the PRACH and the subsequent random connection process, the terminal can achieve uplink synchronization and receive terminal-specific information.
[0134] However, a new type of terminal (hereinafter referred to as RedCap terminal) having reduced capability (reduced capability: RedCap) compared to a legacy type terminal may be unable to establish a cell connection using the initial cell connection process according to FIG. 12. This is due to the following reasons.
[0135] 1) The bandwidth that a RedCap terminal can receive may be limited. This is because the RedCap terminal may only support a small bandwidth to keep the product price low. On the other hand, the bandwidth of the terminal was not considered during the initial cell connection process as shown in FIG. 12. For example, the bandwidth of CORESET0 (indicated as CORESET0 BW in FIG. 12) may be greater than the bandwidth of the RedCap terminal.
[0136] 2) RedCap terminals may require higher coverage. The initial cell connection process according to Fig. 12 was determined based on the link budget of the legacy type terminal. Therefore, for the RedCap terminal to succeed in the initial cell connection, the initial cell connection process according to Fig. 12 needs to be further improved. For example, the PDCCH received at CORESET0 must be able to satisfy sufficient coverage.
[0137] The following embodiments disclose an improved initial connection process for such RedCap terminals.
[0138] (1) First embodiment
[0139] In a first embodiment of the present invention, a RedCap terminal can receive control channel information for initial cell connection of the RedCap terminal through SIB1.
[0140] FIG. 13 is a diagram showing an initial cell connection method according to one embodiment of the present invention.
[0141] Referring to FIG. 13, the RedCap terminal can receive the cell's SS / PBCH (or SSB). Through the SS / PBCH, the RedCap terminal can receive information in the frequency domain of CORESET0 (indicated as CORESET0 BW in FIG. 13) or information in the time domain of the Type-0 search space. The RedCap terminal can receive a PDCCH scrambled with SI-RNTI within the CORESET0 to Type-0 search space. The RedCap terminal can receive DCI format 1_0 through the PDCCH. The DCI format 1_0 may include scheduling information for a PDSCH (indicated as PDSCH for SIB1 in FIG. 13) that transmits SIB1. Therefore, the RedCap terminal can receive SIB1 through the PDSCH.
[0142] The RedCap terminal can check whether there is information for the initial cell connection of the RedCap terminal in the received SIB1. The information for the initial cell connection of the RedCap terminal may include information regarding the CORESET (hereinafter CORESET-Red) or search space (hereinafter search space-Red) for the initial cell connection of the RedCap terminal.
[0143] The RedCap terminal can receive frequency resource allocation information, length, REG, REG bundle, and CCE configuration information of the RedCap terminal's CORESET (indicated as CORESET-Red in FIG. 13). The RedCap terminal can receive a search space corresponding to CORESET-Red separately from CORESET0. To set the search space (search space-Red), the terminal can receive information such as the period and offset at which the PDCCH must be monitored, the aggregation level of PDCCH candidates, and the number of PDCCH candidates per aggregation level.
[0144] If the SIB1 received by the RedCap terminal does not have a CORESET-Red setting for the RedCap terminal or a search space setting corresponding to CORESET-Red, the RedCap terminal may perform at least one of the following operations.
[0145] The first operation includes determining that the RedCap terminal cannot connect to the cell if the RedCap terminal does not receive the settings of CORESET-Red and search space-Red through SIB1.
[0146] The second operation includes, if the RedCap terminal does not receive the configuration of CORESET-Red through SIB1, an operation that assumes the frequency resource allocation information, length, REG, REG bundle, and CCE configuration information of CORESET-Red are identical to the configuration information of CORESET0.
[0147] The third operation includes, if the RedCap terminal has not received some of the configurations of CORESET-Red through SIB1 but has received some of the configurations of CORESET-Red, the operation assumes that the configuration information of CORESET-Red that has not been received is identical to the configuration information of CORESET0. For example, if the RedCap terminal has received the frequency resource allocation information of CORESET-Red through SIB1 but has not received the length or REG, REG bundle, or CCE configuration information, it may assume that the length or REG, REG bundle, or CCE configuration information is identical to the length or REG, REG bundle, or CCE configuration information of CORESET0.
[0148] The fourth operation includes, if the RedCap terminal does not receive the configuration of search space-Red through SIB1, an operation that assumes that the period and offset of search space-Red, the aggregation level of PDCCH candidates, and the number of PDCCH candidates per aggregation level are identical to the configuration of the Type-0 search space of the cell. Here, the Type-0 search space is a search space for monitoring PDCCHs with CRCs scrambled with SI-RNTI.
[0149] The fifth operation includes, if the RedCap terminal receives some of the configurations of search space-Red through SIB1 and does not receive some of them, the operation of assuming that the configuration information of search space-Red that was not received is identical to the configuration information of Type-0 search space. For example, if the RedCap terminal receives the period and offset of search space-Red through SIB1 but does not receive the aggregation level of PDCCH candidates and the number of PDCCH candidates per aggregation level, it can be assumed that the aggregation level of PDCCH candidates and the number of PDCCH candidates per aggregation level are identical to the aggregation level of PDCCH candidates and the number of PDCCH candidates per aggregation level of search space-Red.
[0150] Additionally, the RedCap terminal can receive an indicator from SIB1 indicating whether the RedCap terminal can connect to the cell.
[0151] As an example, the indicator may indicate whether the RedCap terminal can connect to a cell or not. If the indicator indicates that the RedCap terminal cannot connect to a cell, the RedCap terminal cannot perform a cell connection using the PRACH resource received from SIB1.
[0152] As another example, the indicator may indicate whether cell connection is possible or impossible using the CORESET-Red or search space-Red of the RedCap terminal. If the indicator indicates that cell connection is impossible using the CORESET-Red or search space-Red of the RedCap terminal, the RedCap terminal may perform cell connection using the PRACH resource received from SIB1.
[0153] As another example, the indicator may indicate whether the RedCap terminal can establish a cell connection using the PRACH configured in SIB1. If the indicator indicates that the RedCap terminal can establish a cell connection using the PRACH configured in SIB1, the RedCap terminal can establish a cell connection using the PRACH resources received from SIB1.
[0154] The method by which the RedCap terminal receives information on CORESET-Red and search space-Red via SIB1 is as follows.
[0155] As a first method, the information for CORESET-Red and search space-Red regarding the RedCap terminal may be in the same manner as setting the CORESET0 to Type-0 search space in the PBCH. That is, the information for CORESET-Red and search space-Red may be 8 bits. Of the 8 bits, 4 bits may represent the information for CORESET-Red, and the remaining 4 bits may represent the information for search space-Red. The 4-bit information for CORESET-Red indicates one combination out of 16 combinations. The 4-bit search space-Red indicates one combination out of 16 combinations. Although described here as 8 bits, if 8 bits are insufficient, it may be extended to any integer bits.
[0156] As a second method, the information on CORESET-Red and search space-Red regarding the RedCap terminal can take the same method as configuring the existing CORESET and search space.
[0157] As an example, the information of CORESET-Red may include the frequency information of CORESET-Red.
[0158] In one aspect, the frequency information of CORESET-Red may include the offset of the PRB relative to CORESET0. That is, the frequency information of CORESET-Red (assigned PRBs) may be the PRBs obtained by adding the offset to the PRBs of CORESET0.
[0159] In another aspect, the frequency information of CORESET-Red may include the cell's common PRB index. Here, the cell's common PRB index is a PRB index commonly used by the cell's terminals, and the frequency corresponding to common PRB index 0 can be received at SIB1. The terminal can assign an index from the common PRB index 0. The information of CORESET-Red can indicate the starting index of the PRBs using the common PRB index.
[0160] As another example, the information of CORESET-Red may include the length (number of symbols) of CORESET-Red. The length may include 1, 2 to 3 symbols. The length may additionally include 6 to 12 symbols. The length (number of symbols) of CORESET-Red may include a value compared with CORESET0. For example, the length (number of symbols) of CORESET-Red may include information indicating whether it is the same or different when compared to the length (number of symbols) of CORESET0. The length (number of symbols) of CORESET-Red may be represented as the difference from the length (number of symbols) of CORESET0. That is, it may include information corresponding to the length (number of symbols) of CORESET-Red minus the length (number of symbols) of CORESET0. Generally, since the length (number of symbols) of CORESET-Red is greater than or equal to the length (number of symbols) of CORESET0, the difference (length (number of symbols) of CORESET-Red - length (number of symbols) of CORESET0) can only contain non-negative integers.
[0161] As another example, the information in CORESET-Red may include information regarding whether interleaving is performed for REG-to-CCE mapping. If interleaving is not performed, REGs (REG bundles) for RedCap terminals can be bundled into CCEs in order. If interleaving is performed, the indices of REGs (REG bundles) for RedCap terminals are interleaved, and the interleaved indices can be bundled into CCEs in order.
[0162] As another example, the information in CORESET-Red may include REG bundle size setting information. The REG bundle size indicates the number of REGs included in a single REG bundle. REGs can be grouped according to the REG bundle size. The RedCap terminal can assume that the same precoding has been applied to the REGs included in the REG bundle. Therefore, the RedCap terminal can reduce channel estimation errors by jointly detecting the DM-RS of the REGs included in the REG bundle.
[0163] For higher channel estimation performance, CORESET-Red may include additional information. Based on this additional information, the RedCap terminal may assume that the same precoding was used between different CCEs. Here, the different CCEs may be adjacent CCEs in the frequency domain. For example, when the indices of the CCEs in the frequency domain are sequentially assigned as 0, 1, 2,..., according to the additional information, the RedCap terminal may assume that adjacent CCEs in the frequency domain, e.g., CCE0 and CCE1, used the same precoding. Then, it may assume that the next adjacent CCEs, e.g., CCE2 and CCE3, used the same precoding. By assuming that the same precoding was used for multiple adjacent CCEs in the frequency domain, channel estimation performance can be improved.
[0164] Here, the application of the same precoding may be limited to the CCEs included in a single PDCCH candidate. That is, the RedCap terminal may assume that the same precoding is used only for the CCEs included in a single PDCCH candidate. Furthermore, the RedCap terminal may assume that different precodings are used for the CCEs included in different PDCCH candidates.
[0165] For example, search space-Red may include period and offset information. The period and offset may include at least one time unit among a slot unit, a set of slots unit, a symbol unit, and a set of symbols unit. The RedCap terminal may additionally be instructed to the index of the symbol at which monitoring of the PDCCH begins within each of the time units. If the unit of the period and offset information is a slot unit, the index of the starting symbol may be indicated by a 14-bit bitmap. The MSB (most significant bit) of the bitmap indicates the first symbol of the slot, and the LSB (least significant bit) indicates the last symbol of the slot. If the unit of the period and offset information is a time unit other than a slot, a bitmap corresponding to the number of symbols included in the time unit may be instructed. And the MSB of the bitmap may indicate the first symbol among the symbols included in the time unit, and the LSB may indicate the last symbol among the symbols included in the time unit. The RedCap terminal can determine a monitoring occasion in which the PDCCH must be monitored through the above period and offset value or start index. The RedCap terminal must blind decode the PDCCH at the symbols corresponding to the monitoring occasion.
[0166] As another example, search space-Red may include information about additional monitoring opportunities where PDCCHs monitored by the RedCap terminal in a monitoring opportunity can be repeatedly received. The terminal can monitor and receive a first PDCCH in a monitoring opportunity. However, if sufficient reception is not possible with only one first PDCCH, the reception performance of the PDCCH can be improved by repeatedly receiving the first PDCCH in another monitoring opportunity. Therefore, information about additional monitoring opportunities where the first PDCCH can be repeatedly received may be required.
[0167] Additional monitoring opportunities may be provided by the following methods.
[0168] As a first method, additional monitoring opportunities are repeated every time unit and may be indicated by the number of time units. Here, a time unit may include at least one of a slot, a set of slots, a symbol, or a set of symbols. For example, let us assume that the time unit is a slot. According to the first method, additional monitoring opportunities may be indicated by the number of slots (K). In this case, the first PDCCH monitored and received by the RedCap terminal during the monitoring opportunity of the first slot may be received repeatedly in the next slot at the same symbol start position as the first slot. The RedCap terminal may receive the PDCCH repeatedly as many times as the number of slots (K) indicated in this way. The same method may be used for time units other than slots.
[0169] As a second method, additional monitoring opportunities are repeated at the symbol immediately following the monitoring opportunity, and can be indicated by the number of repetitions (K). For example, assuming a monitoring opportunity is set in one slot, an additional monitoring opportunity may be located at the symbol immediately following the symbol where the monitoring opportunity ends in said slot. And an additional monitoring opportunity may be located at the symbol immediately following the symbol where the additional monitoring opportunity ends. In this way, additional monitoring opportunities can be located consecutively according to the number of repetitions (K).
[0170] Again in FIG. 13, a RedCap terminal that has received information from CORESET-Red to search space-Red from SIB1 can receive PDCCH within CORESET-Red and search space-Red. The PDCCH can schedule PDSCH. The PDSCH can carry SIB1 (hereinafter SIB1-Red), which contains system information that the RedCap terminal additionally needs to receive. Accordingly, the RedCap terminal receives PDCCH according to the information from CORESET-Red to search space-Red, and by receiving the PDSCH scheduled by the PDCCH, it can receive SIB1-Red, which is system information required for the initial cell connection of the RedCap terminal. SIB1-Red may contain information regarding PRACH for the cell connection of the RedCap terminal. For convenience, the PRACH used by the RedCap terminal for cell connection may be referred to as PRACH-Red.
[0171] To receive SIB1-Red, the RedCap terminal must be instructed by the PDSCH via the PDCCH on the scheduled time-frequency resources. To schedule frequency resources (i.e., PRBs), the RedCap terminal must know the active downlink BWP. Alternatively, the RedCap terminal must establish the active downlink BWP. The methods related to this are as follows.
[0172] As a first method, the RedCap terminal may not receive a separate active downlink BWP from SIB1. And the CORESET-Red indicated by SIB1 cannot determine that the frequencies from the lowest frequency PRB to the highest frequency PRB are the active downlink BWP of the RedCap terminal.
[0173] As a second method, the terminal can receive an active downlink BWP for the RedCap terminal from SIB1. Here, the active downlink BWP includes the band of CORESET-Red.
[0174] As explained above, SS / PBCH, CORESET0, CORESET-Red, etc., are downlink signals or channels. Therefore, the said downlink signals or channels can be included within the downlink BWP of a downlink cell. On the other hand, since PRACH to PRACH-Red are uplink channels, they can be included within the uplink BWP of an uplink cell. Therefore, in addition to the information of CORESET-Red and search space-Red, information in the time-frequency domain may be required for the transmission of PRACH-Red.
[0175] Furthermore, the subcarrier spacing used for PRACH may vary. For example, PRACH may have a smaller subcarrier spacing to accommodate longer symbol lengths. While PUSCH and PUCCH, which transmit uplink data or control information, use subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, or 120 kHz, PRACH may have a subcarrier spacing of 1.25 kHz to 5 kHz. Consequently, signals or channels with different subcarrier spacings may coexist within an uplink cell. In this case, a guard band is required to suppress interference between signals or channels with adjacent subcarrier spacings. Therefore, if PRACH is distributed across time-frequency resources, uplink resources may be wasted due to the guard band. To prevent this, it is necessary to place the PRACH used by legacy type terminals and the PRACH used by RedCap terminals in time-frequency resources as close as possible.
[0176] The present embodiment discloses a method for arranging PRACH of a legacy type terminal and PRACH-Red of a RedCap terminal into adjacent time-frequency resources in an uplink cell.
[0177] The first method is described with reference to FIG. 14, the second method is described with reference to FIG. 15, and the third method is described with reference to FIG. 16.
[0178] FIG. 14 is a diagram showing an initial cell connection method and PRACH resource setting according to an embodiment of the present invention.
[0179] Referring to FIG. 14, the RedCap terminal can determine that PRACH-Red is located at a time adjacent to the PRACH of the legacy type terminal (refer to the TDM notation in FIG. 14). In this case, there may not be a separate frequency information setting for PRACH-Red. In this case, the frequency information of PRACH-Red may be the same as the frequency information of PRACH. That is, the frequency occupied by PRACH and the frequency occupied by PRACH-Red may be the same. The RedCap terminal may receive a separate time information setting for PRACH-Red.
[0180] Here, the time information may include whether PRACH-Red is at the position immediately preceding or immediately following PRACH. If it is at the position immediately following, PRACH-Red may start at the time immediately following when PRACH ends (or the next slot). If it is at the position immediately preceding, PRACH-Red may end at the time immediately preceding when PRACH starts (or the next slot).
[0181] Alternatively, the time information may represent the time difference between PRACH and PRACH-Red. More specifically, the time information may include the time difference or interval (number of symbols to number of slots) between the last time point of PRACH and the first time point of PRACH-Red. Alternatively, the time information may include the time difference or interval (number of symbols to number of slots) between the last time point of PRACH-Red and the first time point of PRACH. Alternatively, the time information may include the time difference or interval (number of symbols to number of slots) between the first time point of PRACH and the first time point of PRACH-Red.
[0182] FIG. 15 is a diagram showing an initial cell connection method and PRACH resource setting according to another embodiment of the present invention.
[0183] Referring to FIG. 15, the RedCap terminal can determine that PRACH-Red is located at a frequency adjacent to the PRACH of the legacy type terminal. Here, there may be no separate time information set for PRACH-Red. In this case, the time information of PRACH-Red may be the same as the time information of PRACH. That is, the time (slots and symbols) occupied by PRACH and the time (slots and symbols) occupied by PRACH-Red may be the same. The RedCap terminal may receive separate frequency information set for PRACH-Red.
[0184] Here, the frequency information may include information on whether PRACH-Red is the frequency immediately below or immediately above PRACH.
[0185] Alternatively, the frequency information may represent the frequency difference between PRACH and PRACH-Red. More specifically, the frequency information may include the frequency difference or interval between the highest frequency of PRACH and the lowest frequency of PRACH-Red (the number of subcarriers according to the unit of the PRB number or the subcarrier spacing of PRACH, or the number of subcarriers according to the unit of the subcarrier spacing of the uplink BWP of the uplink cell). Alternatively, the frequency information may include the frequency difference or interval between the highest frequency of PRACH-Red and the lowest frequency of PRACH (the number of subcarriers according to the unit of the PRB number or the subcarrier spacing of PRACH, or the number of subcarriers according to the unit of the subcarrier spacing of the uplink BWP of the uplink cell). Alternatively, frequency information may include the frequency difference or interval between the lowest frequency of PRACH and the lowest frequency of PRACH-Red (the number of subcarriers according to the unit of the subcarrier interval of PRB or PRACH to the number of subcarriers according to the unit of the subcarrier interval of the uplink BWP of the uplink cell).
[0186] FIG. 16 is a diagram showing an initial cell connection method and PRACH resource setting according to another embodiment of the present invention.
[0187] Referring to FIG. 16, the RedCap terminal can determine that PRACH-Red is located at the same time-frequency as the PRACH of the legacy type terminal. The RedCap terminal may not have separate time-frequency information set for PRACH-Red. In this case, the time-frequency information of PRACH-Red may be the same as the time-frequency information of PRACH. The RedCap terminal may use some of the PRACHs of the above time-frequency. For example, the PRACHs of the legacy type terminal may consist of multiple PRACH preamble sequences. At this time, some of the multiple PRACH preamble sequences may be used by the RedCap terminal.
[0188] To this end, the RedCap terminal may be set to the index (or ID) of an available sequence among the PRACH preamble sequences. More specifically, the RedCap terminal may be set to the lowest index (or ID) among the available sequence indices (or IDs), and may use a sequence having that index (or ID) and an index (or ID) after that index (or ID).
[0189] As another example, a RedCap terminal can be configured to have the number of available sequences set, and can use as many sequences as the number of available sequences that have a high index (or ID) among all sequences.
[0190] (2) Second embodiment
[0191] According to a second embodiment of the present invention, a RedCap terminal can receive scheduling information for system information for the initial cell connection of the RedCap terminal from SIB1. Here, the system information for the initial cell connection of the RedCap terminal is referred to as SIB1-Red. This is illustrated in FIG. 17.
[0192] FIG. 17 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention.
[0193] Referring to FIG. 17, the RedCap terminal can receive the SS / PBCH (or SSB) of the cell. The RedCap terminal can receive information in the frequency domain of CORESET0 or information in the time domain of the Type-0 search space through the SS / PBCH. The RedCap terminal can receive a PDCCH scrambled to SI-RNTI from the CORESET0 to the Type-0 search space. The RedCap terminal can receive DCI format 1_0 through the PDCCH. The DCI format 1_0 may include scheduling information for a PDSCH that transmits SIB1. Thus, the RedCap terminal can receive SIB1 (indicated as PDSCH for SIB1 in FIG. 17).
[0194] The SIB1 received by the RedCap terminal may contain information for cell connection of the legacy type terminal. In the case of the legacy type terminal, there is no need to receive system information for the RedCap terminal separately. Therefore, if system information for the RedCap terminal is added to the existing SIB1, the overhead of the SIB1 may increase. To prevent this, it is desirable for the system information required by the RedCap terminal to be transmitted separately. Accordingly, the SIB1 may include time-frequency information of the PDSCH that allows the RedCap terminal to receive the system information required by the RedCap terminal. The RedCap terminal can receive the PDSCH according to the above time-frequency information. The received PDSCH may include SIB1-Red (indicated as PDSCh for SIB1-Red in FIG. 17). By receiving SIB1-Red, the RedCap terminal can receive information for initial cell connection. For example, the RedCap terminal can determine the settings of the PDSCH-Red for initial cell connection based on SIB1-Red.
[0195] In order for a RedCap terminal to be allocated frequency resources (i.e., PRBs) for which a PDSCH for SIB1-Red is scheduled, the terminal must know the active downlink BWP (indicated as RedCap BW in Fig. 17) for which the PDSCH is scheduled. Therefore, the RedCap terminal must obtain the active downlink BWP.
[0196] For example, the RedCap terminal can receive the index and length of the starting PRB (the PRB with the lowest frequency) of the active downlink BWP from SIB1. Here, the PRB index can be represented by a common PRB index. Alternatively, the PRB index can be represented by the frequency interval (number of PRBs) with respect to CORESET0. That is, since the RedCap terminal knows the frequency range occupied by CORESET0, it can determine the starting PRB of the active downlink BWP by adding the frequency interval (number of PRBs) given to the said frequency range.
[0197] The length can be set to at least one of 24 PRBs, 48 PRBs, or 96 PRBs. As another example, the length can be equal to the number of PRBs included in CORESET0. In this case, information regarding the length of the active downlink BWP in SIB1 can be omitted.
[0198] The RedCap terminal can assume that a PDSCH transmitting SIB1-Red is received within the active downlink BWP configured above.
[0199] (3) Third embodiment
[0200] According to a third embodiment of the present invention, a RedCap terminal can receive configuration information for a PRACH for initial cell connection of the RedCap terminal from SIB1. Here, the PRACH for initial cell connection of the RedCap terminal is referred to as PRACH-Red. This is illustrated in FIG. 18.
[0201] FIG. 18 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention.
[0202] Referring to FIG. 18, the RedCap terminal can receive the cell's SS / PBCH (or SSB). The RedCap terminal can receive frequency domain information of CORESET0 or time domain information of the Type-0 search space through the SS / PBCH. The RedCap terminal can receive a PDCCH scrambled to SI-RNTI from the CORESET0 to Type-0 search space. The RedCap terminal can receive DCI format 1_0 through the PDCCH. The DCI format 1_0 may include scheduling information for the PDSCH for SIB1. Therefore, the RedCap terminal can receive SIB1 (indicated as PDSCH for SIB1 in FIG. 18).
[0203] The SIB1 received by the RedCap terminal may include information for cell connection of the legacy type terminal. Additionally, the SIB1 may additionally include system information for the RedCap terminal. Therefore, the RedCap terminal can obtain information regarding the initial cell connection of the RedCap terminal through the SIB1 without needing to receive separate system information (e.g., SIB1-Red of FIG. 17). For example, the SIB1 may include configuration information for PRACH-Red for the initial cell connection.
[0204] The RedCap terminal may receive an uplink BWP for the configuration of the above PRACH-Red and cell connection. PRACH-Red may be transmitted within the uplink BWP. Therefore, the configuration of PRACH-Red is included in the uplink BWP. The uplink BWP for the RedCap terminal in SIB1 may be configured as follows.
[0205] (4) 4th embodiment
[0206] According to the fourth embodiment of the present invention, a RedCap terminal can receive an SS / PBCH that is exclusive to the RedCap terminal. This can be distinguished from the SS / PBCH received by legacy type terminals. The method of distinction will be described later. For convenience, the SS / PBCH that can be received only by the RedCap terminal is referred to as SSB-Red. This is illustrated in FIG. 19.
[0207] FIG. 19 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention.
[0208] Referring to FIG. 19, a RedCap terminal can receive SSB-Red, which is an SS / PBCH for a RedCap terminal only, from a BWP for a RedCap terminal only (indicated as RedCap BW in FIG. 19). By receiving the SSB-Red, the RedCap terminal can receive the synchronization of the downlink signal, the cell ID, and the Master Information Block (MIB) transmitted by the PBCH. By receiving the SSB-Red, the RedCap terminal can obtain configuration information for CORESET-Red or search space-red to monitor the PDCCH that schedules the PDSCH transmitting SIB1-Red. The RedCap terminal can monitor and receive the PDCCH from CORESET-Red or search space-red. By receiving the PDCCH, the RedCap terminal can receive the PDSCH transmitting SIB1-Red (indicated as PDSCH for SIB1-Red in FIG. 19). The RedCap terminal can receive configuration information for PRACH-Red for cell connection from SIB1-Red and can transmit PRACH according to the configuration information of PRACH-Red.
[0209] In the fourth embodiment, the RedCap terminal must receive SSB-Red from a separate BWP different from the downlink BWP of the legacy type terminal. However, since the timing of receiving SSB-Red is prior to cell connection, the RedCap terminal cannot know when and at which frequency SSB-Red is transmitted. Additionally, the RedCap terminal must be able to distinguish between the SS / PBCH received by the legacy type terminal and the SSB-Red. A method for this is disclosed below.
[0210] The first method includes a process in which a RedCap terminal performs an initial cell connection process, similar to a legacy type terminal. For example, the RedCap terminal may receive the cell's SS / PBCH (or SSB). The RedCap terminal may receive information in the frequency domain of CORESET0 or information in the time domain of the Type-0 search space through the SS / PBCH. The RedCap terminal may receive a PDCCH scrambled to SI-RNTI using the information from CORESET0 to the Type-0 search space. The RedCap terminal may receive DCI format 1_0 through the PDCCH. The DCI format 1_0 may include scheduling information for the PDSCH that transmits SIB1. Thus, the RedCap terminal may receive SIB1. The SIB1 may include information regarding the frequency and time at which SSB-Red is transmitted. That is, the terminal may receive information for receiving SSB-Red for the RedCap terminal through SIB1.
[0211] The frequency of SSB-Red can be indicated using the ARFCN (absolute Radio Frequency Channel Number). Alternatively, the frequency of SSB-Red can be indicated by the common PRB index. Alternatively, the frequency of SSB-Red can be indicated by the interval from the frequency of the SSB. Here, the interval can be expressed in terms of frequency. Here, the interval can be expressed in terms of the number of PRBs. Here, the interval can be expressed in terms of the number of subcarriers. Here, the interval can be expressed in terms of the number of channel rasters or synchronization rasters between the SSB and SSB-Red.
[0212] The time of SSB-Red can be the same as that of SSB. That is, SSB and SSB-Red can be transmitted at the same time (slot and symbol). As another example, the time of SSB-Red can have a time interval from that of SSB. For example, the aforementioned time interval can be given as 5ms (length of a half frame). Through the time interval between SSB and SSB-Red, the RedCap terminal can receive SSB in the first time interval and SSB-Red in the second time interval. By doing so, it can receive two synchronization blocks to achieve more accurate downlink synchronization.
[0213] The second method includes the SSB-Red having a structure different from the SSB of the legacy type terminal.
[0214] As an example, SSB-Red can be designed to include a larger frequency band to improve the reception performance of the PBCH. For instance, SSB-Red can be designed to have 4 more PRBs than the SSB of a legacy type terminal. That is, SSB-Red can be designed to occupy 24 PRBs. More specifically, SSB-Red can have 4 symbols. For the 4 symbols, the first symbol transmits the PSS, and the third symbol transmits the SSS. The PBCH can then transmit from resources other than those mapped to the SSS among the 24 PRBs of the second and fourth symbols and the 24 PRBs of the third symbol. Although the example above describes 24 PRBs, it can be extended to more PRBs.
[0215] The RedCap terminal can receive the PSS and SSS to obtain the synchronization of the downlink signal and the cell ID. Then, to determine whether it is an SS / PBCH (SSB) composed of 20 PRBs or an SS / PBCH designed with more PRBs (SSB-Red), the RedCap terminal can decode the PBCH by assuming 20 PRBs and decode it as a PBCH designed with more PRBs. If the PBCH decoding by assuming 20 PRBs is successful, the terminal knows that the SS / PBCH is the SSB of a legacy terminal. If the PBCH decoding by assuming more PRBs is successful, the RedCap terminal knows that the SS / PBCH is the SSB-Red of RedCap.
[0216] As another example, SSB-Red can be designed to include more symbols to improve the reception performance of PBCH. For example, SSB-Red can be designed to have one or two more symbols than legacy type terminals. That is, SSB-Red can be designed to include 5 to 6 symbols. The first symbol transmits the PSS, and the third symbol transmits the SSS. And the PBCH can be transmitted at the second and fourth symbols, and the fifth and sixth symbols.
[0217] The RedCap terminal can receive the PSS and SSS to obtain the downlink signal synchronization and cell ID. Then, to determine whether it is an SS / PBCH consisting of four symbols (SSB) or a PBCH designed with more symbols (SSB-Red), the RedCap terminal can decode the PBCH by assuming four symbols and decode it as a PBCH designed with more symbols. If the PBCH decoding by assuming four symbols is successful, the terminal knows that the SS / PBCH is the SSB of a legacy terminal. If the PBCH decoding by assuming more symbols is successful, the terminal knows that the SS / PBCH is the SSB-Red of a RedCap.
[0218] As another example, SSB and SSB-Red can be distinguished based on the order of symbols to which SS / PBCH is mapped. For instance, unlike SSB, SSB-Red places the PSS in the first symbol and can move the position of the SSS to the second or fourth symbol. If the SSS is moved to the second symbol, the PBCH can be transmitted in the 20 PRBs of the third and fourth symbols, and in the PRBs of the 20 PRBs of the second symbol that are not occupied by the SSS. If the SSS is moved to the fourth symbol, the PBCH can be transmitted in the 20 PRBs of the second and third symbols, and in the PRBs of the 20 PRBs of the fourth symbol that are not occupied by the SSS.
[0219] The RedCap terminal can receive the PSS. The RedCap terminal can determine the symbol at which the SSS is transmitted in order to determine whether the SSB is the SSB of a legacy type terminal or the SSB-Red of the RedCap terminal. If the SSS is received at the third symbol, the terminal knows that the SS / PBCH is the SSB of a general terminal (legacy). If the SSS is received at the second to fourth symbol, the terminal knows that the SS / PBCH is the SSB-Red of RedCap.
[0220] As another example, SSB and SSB-Red can be distinguished using the physical cell ID obtained from the SS / PBCH. For instance, the SS / PBCH can have up to 1,008 physical cell IDs. The RedCap terminal can determine it as SSB-Red if it has a specific value among the maximum 1,008 physical cell IDs. For instance, the specific value could be a physical cell ID that leaves a remainder of 0 when divided by 3. As another example, the physical cell ID is N cell ID = 3*N (1) ID + N (2) ID Since it has the form of, N (1) ID N (2) ID If the value is specific, it can be determined as SSB-Red. As another example, the number of physical cell IDs that an SS / PBCH can have can be increased to 1008 or more. In this case, the RedCap terminal can determine that the SS / PBCH is SSB-Red if the physical cell ID is 1008 or greater.
[0221] As another example, SSB and SSB-Red can be distinguished based on the RE mapping order of the PBCH in SS / PBCH. For example, if the PBCH of the SSB of a legacy type terminal is mapped in a first direction (e.g., from low frequency RE to high frequency RE), the PBCH of the SSB-Red of a RedCap terminal may be mapped in a second direction (e.g., the opposite direction is mapped from high frequency RE to low frequency RE). Here, the second direction may be different from the first direction. The terminal can determine from the RE mapping of the PBCH whether the corresponding SSB is the SSB of the legacy type terminal or the SSB-Red of the RedCap terminal.
[0222] The RedCap terminal can receive the PSS and SSS to obtain the synchronization of the downlink signal and the cell ID. Then, to determine whether the SS / PBCH (SSB) mapped to the first direction or the PBCH designed for the second direction (SSB-Red) is the RedCap terminal, it can decode the PBCH by assuming the first direction and decode it into the PBCH designed for the second direction. If the PBCH decoding by assuming the first direction is successful, the terminal can know that the SS / PBCH is the SSB of a legacy terminal. If the PBCH decoding by assuming the second direction is successful, the terminal can know that the SS / PBCH is the SSB-Red of RedCap.
[0223] As another example, in SS / PBCH, SSB and SSB-Red can be distinguished based on the CRC of the PBCH. For example, if the PBCH of the SSB of a legacy type terminal is scrambled with a first CRC, the PBCH of the SSB-Red of a RedCap terminal may be scrambled with a second CRC different from the first CRC. The terminal can determine whether the corresponding SSB is the SSB of a legacy type terminal or the SSB-Red of a RedCap terminal by checking the CRC value of the PBCH.
[0224] A RedCap terminal can receive PSS and SSS to obtain the synchronization of the downlink signal and the cell ID. Then, to determine whether it is an SS / PBCH (SSB) scrambled with a first CRC or a PBCH (SSB-Red) scrambled with a second CRC, the RedCap terminal can decode the PBCH by assuming the first CRC and decode the PBCH by assuming the second CRC. If the PBCH decoding by assuming the first CRC is successful, the terminal can know that the SS / PBCH is the SSB of a legacy type terminal. If the PBCH decoding by assuming the second CRC is successful, the terminal can know that the SS / PBCH is the SSB-Red of a RedCap.
[0225] As another example, in SS / PBCH, SSB and SSB-Red can be distinguished based on the 1-bit of the PBCH. The PBCH of the SSB of a legacy type terminal may have an unused 1-bit. Therefore, it can be determined whether it is an SSB of a legacy type terminal or an SSB-Red of a RedCap terminal based on the value of the said 1-bit. For example, if the value of the said 1-bit in the PBCH is '0', the RedCap terminal determines that the corresponding SSB is an SSB of a legacy type terminal, and if it is '1', it determines that it is an SSB-Red of a RedCap terminal.
[0226] In the previous example, the RedCap terminal must complete the reception of the PSS, SSS, and PBCH to determine whether the signal is an SSB of the legacy type terminal or the RedCap terminal. This may result in overhead and battery consumption for additional reception.
[0227] As another example, the frequency at which SSB-Red can be transmitted may differ from the frequency at which SSB is transmitted. For instance, a terminal may receive SSB at specific frequency intervals to receive the correct SSB. Here, the specific frequency interval can be defined as a synchronization raster. This allows the terminal to receive SSB sparsely at specific frequency intervals (e.g., tens of kHz to hundreds of kHz) rather than receiving SSB at all frequencies to reduce battery consumption. The base station transmits SSB at specific frequency intervals to ensure the terminal receives the correct SSB. In other words, there may be frequency bands where the terminal does not monitor for SSB. The base station may transmit SSB-Red in the aforementioned frequency band, and the RedCap terminal may receive SSB-Red in the aforementioned frequency band.
[0228] As another example, the time interval during which SSB-Red can be transmitted may differ from the time interval during which SSB is transmitted. For example, a terminal may receive the SSB within a 5ms half frame of a 10ms radio frame to receive the correct SSB. In other words, there may be a time interval during which the terminal does not monitor the SSB. For example, if the SSB is transmitted in a 5ms half frame of a 10ms radio frame, the remaining time interval is a period during which the SSB is not monitored. The base station may transmit SSB-Red during the above time interval, and the RedCap terminal may receive SSB-Red during the above time interval.
[0229] (5) 5th embodiment
[0230] According to the fifth embodiment of the present invention, a RedCap terminal can interpret information indicated by the SS / PBCH differently from a legacy type terminal. Here, the SS / PBCH can receive both the legacy type terminal and the RedCap terminal. That is, the structure of the SS / PBCH can be identical to the SSB of the legacy type terminal. This is illustrated in FIG. 20.
[0231] FIG. 20 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention.
[0232] Referring to FIG. 20, the legacy type terminal and the RedCap terminal can receive SS / PBCH. By receiving PSS and SSS, they can receive downlink signal synchronization and physical cell ID. Also, the legacy type terminal and the RedCap terminal can receive PBCH. At this time, the legacy type terminal and the RedCap terminal can interpret PBCH in different ways.
[0233] A legacy type terminal can receive configuration information of CORESET0 and configuration information of the Type-0 search space through the 8 bits of the PBCH. At this time, the 4 bits representing the frequency configuration information of CORESET0 can indicate one combination out of 16 combinations. And the 4 bits representing the configuration information of the Type-0 search space can indicate one combination out of 16 combinations. If the above 4 bits indicate '0000', it indicates the first combination out of 16 combinations. In this way, through the 4 bits and 4 bits, a total of 8 bits, the terminal can receive a PDCCH that schedules a PDSCH transmitting SIB1.
[0234] The Redcap terminal may interpret the above 8 bits of the PBCH differently. The 4 bits representing the configuration information of CORESET0 can be reinterpreted and used as the configuration information of CORESET-Red. That is, the configuration information of CORESET-Red is indicated by 4 bits and can indicate one of 16 combinations. The 4 bits representing the configuration information of the Type-0 search space can be reinterpreted and used as the configuration information of search space-Red.
[0235] For example, when the 4-bit representing the configuration information of CORESET0 indicates '0000', the operation of the terminal is as follows. If the terminal is a legacy type terminal, the above 4-bit is determined to indicate one of the 16 combinations representing the configuration information of CORESET0. That is, if the 4-bit is '0000', it is determined to be the first combination among the 16 combinations representing the configuration information of CORESET0. If the terminal is a RedCap terminal, the above 4-bit is determined to indicate one of the 16 combinations representing the configuration information of CORESET-Red. That is, if the 4-bit is '0000', it is determined to be the first combination among the 16 combinations representing the configuration information of CORESET-Red.
[0236] The terminal may be instructed whether to perform the above reinterpretation. For example, it may be instructed whether it is possible for the RedCap terminal to reinterpret the information received from the PBCH to suit the RedCap terminal using 1 bit of the PBCH. If the above 1 bit is '0', the RedCap terminal must not reinterpret the information received from the PBCH. If the above 1 bit is '1', the RedCap terminal may reinterpret the information received from the PBCH.
[0237] (6) 6th embodiment
[0238] According to the sixth embodiment of the present invention, a RedCap terminal can determine the configuration information of CORESET-Red based on CORESET0. More specifically, the RedCap terminal can obtain the configuration information of CORESET0 by receiving SS / PBCH. The RedCap terminal can infer the configuration information of CORESET-Red based on the configuration information of CORESET0.
[0239] For example, it can be assumed that CORESET-Red starts at the symbol immediately following the symbol where CORESET0 ends. Here, CORESET-Red can have the same configuration as CORESET0. That is, the number of PRBs, the positions of the PRBs, or the length of the CORESET can be the same as CORESET0. Alternatively, it can be assumed that CORESET-Red starts in the slot immediately following the slot to which CORESET0 belongs. Here, CORESET-RED can have the same configuration as CORESET0. That is, the number of PRBs, the positions of the PRBs, or the length of the CORESET can be the same as CORESET0. Furthermore, the position of the symbol where CORESET-Red starts within the slot can be the same as the position where CORESET0 starts within the slot. Although expressed here as the immediately following symbol or the immediately following slot, this can be further extended to apply to a certain number of symbols or slots later. Additionally, while only the location of CORESET-Red after CORESET0 has been described here, conversely, CORESET-Red can be located before CORESET0.
[0240] As another example, it can be assumed that CORESET-Red starts at the PRB immediately above the PRB where CORESET0 ends. Here, CORESET-Red can have the same configuration as CORESET0. That is, the number of PRBs or the length of CORESET can be the same as CORESET0. Although it is stated here that CORESET-Red starts at the PRB immediately above, this can be extended further so that CORESET-Red can start after a certain number of PRBs. Additionally, CORESET-Red can be located immediately below the PRB where CORESET0 starts.
[0241] (7) 7th embodiment
[0242] As a seventh embodiment of the present invention, a legacy type terminal and a RedCap terminal can monitor different PDCCH candidates in CORESET0. Here, CORESET0 is indicated in SS / PBCH. The legacy type terminal and the RedCap terminal can receive CORESET0 configuration information in the same way without distinction. This is illustrated in FIG. 21.
[0243] FIG. 21 is a diagram illustrating an initial cell connection method according to another embodiment of the present invention.
[0244] Referring to FIG. 21, a legacy type terminal can receive a PDCCH that schedules SIB1 in CORESET0. This PDCCH can transmit DCI format 1_0.
[0245] For RedCap terminals, a PDCCH carrying SIB1-Red can be received from CORESET0. This PDCCH can carry DCI format X. The method for configuring DCI format X is as follows.
[0246] As a first method, the lengths of DCI format 1_0 and DCI format X may differ. That is, a legacy type terminal blind decodes DCI format 1_0 of the first length, so it may receive DCI format 1_0 but may not receive DCI format X. Conversely, a RedCap terminal blind decodes DCI format X of the second length, so it may receive DCI format X but may not receive DCI format 1_0. Additionally, the RedCap terminal blind decodes DCI format 1_0 of the first length to receive DCI format 1_0 and may receive SIB1 scheduled by DCI format 1_0.
[0247] As a second method, the CRCs of DCI format 1_0 and DCI format X can be scrambled with different values. For example, the CRC of DCI format 1_0 is scrambled with SI-RNTI, but DCI format X can be scrambled with a value different from SI-RNTI. That is, a legacy type terminal blind decodes DCI format 1_0 scrambled with SI-RNTI, so it may receive DCI format 1_0 but may not receive DCI format X. Conversely, a RedCap terminal blind decodes DCI format X scrambled with a different value, so it may receive DCI format X but may not receive DCI format 1_0. Additionally, the RedCap terminal blind decodes DCI format 1_0 scrambled with SI-RNTI to receive DCI format 1_0 and may receive SIB1 scheduled by DCI format 1_0.
[0248] As a third method, the legacy type terminal and the RedCap terminal can receive DCI format 1_0 and DCI format X, and DCI format 1_0 and DCI format X can be distinguished by a 1-bit indicator. The 1-bit indicator may be located at the same position in DCI format 1_0 and DCI format X. If the value of the 1-bit is '0', it can be determined as DCI format 1_0, and if the value of the 1-bit is '1', it can be determined as DCI format X. Although described as 1-bit for convenience, it can be distinguished by multiple bits or determined by a combination of specific code points.
[0249] II. PRACH Configuration and RAR Reception Method for RedCap Terminals
[0250] The present embodiment relates to a method for receiving a plurality of PRACH settings and a RAR (random access response) resulting from the plurality of PRACH settings during the initial cell connection and random access processes of a terminal.
[0251] Typically, the terminal can receive a single PRACH setting for random access from the base station via the SIB. For reference, the System Information Block can set a single Uplink Initial BWP. Here, the Uplink Initial BWP is the BWP used by the terminal during the random access process. The above single Uplink Initial BWP includes a single PRACH setting.
[0252] The above PRACH setting may include at least one of the following information.
[0253] - Slots where PRACH opportunities are transmitted in the time domain
[0254] - Symbol indicating that the PRACH opportunity starts within the slot where the PRACH opportunity is transmitted in the time domain
[0255] - Subcarrier where the PRACH opportunity is located in the frequency domain
[0256] - The number of RACH opportunities, which is the set of PRACH opportunities in the frequency domain
[0257] - The sequence used by preambles in the chord area
[0258] Here, one PRACH opportunity can consist of up to 64 preambles. Each preamble can be indexed with a value of 0, 1, ..., 63.
[0259] A base station may configure an additional uplink carrier to provide higher coverage to a terminal. This is called a supplementary UL carrier (SUL carrier). The base station may also configure a PRACH on the SUL, and the terminal may be able to connect to an uplink cell through the SUL's PRACH. For reference, the SIB may configure one Uplink Initial BWP on the SUL. Here, the Uplink Initial BWP is the BWP used by the terminal during the random connection process. One PRACH configuration may be included in the above one Uplink Initial BWP.
[0260] Hereinafter, in order to distinguish between SUL and a general uplink carrier in the present invention, the general uplink carrier is referred to as a normal UL carrier (NUL carrier). Unless otherwise noted, the embodiments disclosed in the present invention may be applied without distinction between NUL and SUL.
[0261] If the terminal receives both the PRACH setting from the NUL carrier and the PRACH setting from the SUL carrier, the terminal can establish a random connection via the NUL carrier's PRACH and a random connection via the SUL carrier's PRACH. That is, the terminal can perform the random connection process by transmitting either the NUL carrier's PRACH or the SUL carrier's PRACH to the base station.
[0262] The terminal can select a preamble based on the above PRACH information and transmit the selected preamble to the base station. Subsequently, the approximate process of random access is as follows.
[0263] The terminal can monitor the PDCCH transmitted from the base station for a certain period of time after the transmission of the preamble. Here, the terminal can monitor the PDCCH that is scrambled with RA-RNTI. Here, the value of RA-RNTI is determined based on the preamble transmitted by the terminal, and the method for calculating the specific value of RA-RNTI will be described later. When the terminal receives the PDCCH that is scrambled with RA-RNTI, it can receive the PDSCH scheduled by the said PDCCH. The said PDSCH may include information for scheduling the message 3 PUSCH and a TC-RNTI value. The terminal can transmit the message 3 PUSCH to the base station according to the said scheduling information. Then, the terminal can receive the PDCCH that schedules the message 4 PDSCH from the base station. Here, the said PDCCH may be scrambled with a TC-RNTI value. When the terminal receives a PDCCH scrambled with TC-RNTI values, it can receive a message 4 PDSCH scheduled by the PDCCH, and can transmit a HARQ-ACK to the base station depending on whether the reception of the PDSCH is successful.
[0264] The method by which the terminal obtains RA-RNTI in the random access process described above is as follows.
[0265] [Mathematical Formula 1]
[0266]
[0267] Here, s_id is the index of the first OFDM symbol of the PRACH opportunity (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH opportunity in the system frame (0 ≤ t_id < 80), f_id is the index of the PRACH opportunity in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the index of the uplink carrier used for random access preamble transmission (0 for NUL carrier and 1 for SUL carrier).
[0268] The terminal and the base station can calculate the RA-RNTI based on Equation 1. If two terminals transmit a preamble at different PRACH opportunities, at least one of the values of s_id, t_id, or f_id for each terminal is different. Therefore, since two terminals that transmit a preamble at different PRACH opportunities monitor the PDCCH scrambled with different RA-RNTIs, it is possible to distinguish between the preamble and the corresponding PDCCH. Additionally, even if different terminals have the same s_id, t_id, and f_id, if one terminal transmits the preamble on a NUL carrier and the other terminal transmits the preamble on a SUL carrier, the two terminals can monitor the PDCCH scrambled with different RA-RNTIs depending on the ul_carrier_id value. Thus, the preamble and the corresponding PDCCH of the two terminals can be distinguished.
[0269] The case where the RA-RNTI values of two terminals become the same is when a preamble is transmitted on the same carrier (one of NUL and SUL) during a PRACH opportunity where s_id, t_id to f_id are identical. In this case, if the preambles transmitted by the two terminals during the PRACH opportunity are different from each other, the preambles can be distinguished according to the ID of the preamble. More specifically, since the two terminals have the same RA-RNTI value, they monitor the PDCCH scrambled with the same RA-RNTI value. If the two terminals receive the PDCCH scrambled with the RA-RNTI value, they can receive the PDSCH scheduled by the PDCCH. Here, the PDSCH may include a RAPID (random access preamble identifier). If the RAPID is identical to the index of the preamble transmitted by the terminal, the terminal can determine that it is a RAR (random access response) corresponding to the preamble sent by the terminal. Therefore, two terminals that have transmitted different preambles can be distinguished through the RAPID.
[0270] In this way, each terminal can receive a RAR sent to it based on the PRACH opportunity and the index of the preamble of the PRACH it has sent. However, there may be cases where the terminal cannot determine the RAR sent to it based on the PRACH opportunity and the index of the preamble of the PRACH it has sent. An embodiment that solves this problem is disclosed below.
[0271] The base station may additionally configure new PRACH settings for RedCap terminals to support new types of terminals, such as RedCap terminals. For convenience, the PRACH settings for legacy type terminals will be referred to as legacy PRACH settings below, and the PRACH settings newly configured for RedCap terminals will be referred to as new PRACH settings. The basis or motivation for the base station providing new PRACH settings to RedCap terminals is as follows.
[0272] - Basis 1: The base station may perform different scheduling methods during the random connection process depending on the type of terminal. For example, to increase the downlink coverage of a RedCap terminal, the base station may repeatedly transmit a PDSCH containing RAR and a Message 4 PDSCH containing Message 4. Additionally, to increase the uplink coverage of a RedCap terminal, the base station may instruct the repeated transmission of a Message 3 PUSCH containing Message 3. As such, the base station must know the type of terminal for scheduling for a RedCap terminal. This is possible by the RedCap terminal transmitting a PRACH according to a separate new PRACH configuration.
[0273] - Basis 2: Base stations may use different PRACH formats depending on the type of terminal. For example, to increase the uplink coverage of RedCap terminals, a PRACH format with high coverage may be used, while general terminals may use a PRACH format with low coverage. To this end, a separate new PRACH setting may be provided to RedCap terminals.
[0274] - Basis 3: Typically, the number of RedCap terminals may be greater than the number of general terminals. Consequently, if general terminals and RedCap terminals attempt random connections using the same PRACH settings, the random connection attempts by a large number of RedCap terminals will make it difficult for a small number of general terminals to connect. Therefore, to ensure successful random connections for general terminals, the random connections of RedCap terminals and general terminals need to be separated. This is possible by providing RedCap terminals with separate new PRACH settings.
[0275] - Basis 4: In the case of RedCap terminals, there are applications that periodically transmit data. For example, wireless sensors transmit measured data at regular intervals. Therefore, it is highly likely that the aforementioned terminals will periodically attempt random connections. The base station can reduce PRACH overhead by configuring PRACH settings that are suitable for the characteristics of the RedCap terminals. To this end, new PRACH settings can be provided to the RedCap terminals.
[0276] A method for a base station to provide a new PRACH setting to a RedCap terminal is disclosed below.
[0277] FIG. 22 is a diagram showing a PRACH resource setting according to another embodiment of the present invention. FIG. 22(a) is a diagram relating to a first method, and FIG. 22(b) is a diagram relating to a second method.
[0278] According to the first method, the RedCap terminal can receive a new PRACH setting through an SIB transmitted from a base station.
[0279] More specifically, the SIB can set one Uplink Initial BWP for one Uplink Cell (NUL or SUL). Here, the Uplink Initial BWP is the BWP used by the terminal during the random connection process and may also be called the Initial Uplink BWP. The above-mentioned one Uplink Initial BWP may include existing legacy PRACH settings and new PRACH settings. For reference, there may be one or multiple new PRACH settings. For convenience, if there are multiple new PRACH settings, an index may be assigned to distinguish each new PRACH setting. For convenience, the index may start from 0.
[0280] According to the second method, a RedCap terminal can receive multiple uplink initial BWPs through a SIB transmitted from a base station. Here, each uplink initial BWP may include a PRACH setting. More specifically, the SIB may set an existing uplink initial BWP and a new uplink initial BWP in a single uplink cell (NUL or SUL). Here, each uplink initial BWP may include a single PRACH setting. Specifically, the existing uplink initial BWP may include a legacy PRACH setting, and the new uplink initial BWP may include a new PRACH setting. The terminal may select one of the multiple uplink initial BWPs and transmit the PRACH. At this time, the selected uplink initial BWP is the BWP used by the terminal during the random connection process. For reference, there may be one or multiple new uplink initial BWPs. For convenience, if there are multiple new uplink initial BWPs, an index may be assigned to distinguish the new PRACH setting of each new uplink initial BWP. For convenience, the above index can start from 0.
[0281] Through the first or second method, the RedCap terminal may receive one or more new PRACH settings. Here, the RedCap terminal may perform an arbitrary connection through one of the multiple new PRACH settings.
[0282] Let us assume that a base station has provided a legacy PRACH configuration and a new PRACH configuration to the terminals. One of the two terminals may transmit a preamble according to the legacy PRACH configuration, while the other terminal may transmit a preamble according to the new PRACH configuration. The preambles transmitted by the two terminals according to the legacy PRACH configuration and the new PRACH configuration may differ in at least one of the time, frequency, or code, and accordingly, the base station can distinguish the preambles transmitted by the two terminals. Therefore, the base station must transmit a RAR for random access to each of the two terminals.
[0283] As described above, a terminal can determine which RAR it should receive by using the RA-RNTI corresponding to its preamble or the index of the preamble. However, when one terminal transmits a preamble according to a legacy PRACH setting and another terminal transmits a preamble according to a new PRACH setting, the two terminals cannot determine which RAR they should receive in the following situations.
[0284] For example, if the s_id, t_id, and f_id of a preamble selected according to the legacy PRACH settings of one terminal are the same as the s_id, t_id, and f_id of a preamble selected according to the new PRACH settings of another terminal, the two terminals monitor a PDCCH that schedules a RAR based on the same RA-RNTI value. At this time, if the index of the preamble selected by one terminal according to the legacy PRACH settings is the same as the index of the preamble selected by the other terminal according to the new PRACH settings, the two terminals determine the RAR with the same RAPID. Therefore, the two terminals determine the above RAR as their own RAR, and accordingly, have the same message 3 PUSCH scheduling grant and TC-RNTI value.
[0285] As a problem may occur when a base station provides a new PRACH setting as described above, methods to resolve this are disclosed below.
[0286] According to the first method, the RA-RNTI value can be determined depending on which PRACH setting preamble is transmitted. If the terminal transmits a legacy PRACH setting preamble, the terminal can determine the RA-RNTI value as follows.
[0287] [Mathematical Formula 2]
[0288]
[0289] Here, s_id is the index of the first OFDM symbol of the PRACH opportunity (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH opportunity in the system frame (0 ≤ t_id < 80), f_id is the index of the PRACH opportunity in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the index of the uplink carrier used for random access preamble transmission (0 for NUL carrier and 1 for SUL carrier).
[0290] To reduce the latency of the random access process through legacy PRACH settings, the terminal can perform a simplified random access process using new PRACH settings. This process is called the 2-step random access process. For convenience, the PRACH settings in the 2-step random access process are referred to as 2-step PRACH. The 2-step random access process is approximately as follows.
[0291] The terminal can transmit a selected preamble and data to the base station using PRACH information configured for the 2-step random access process. Subsequently, the terminal can monitor the PDCCH transmitted from the base station for a certain period of time. Here, the terminal can monitor the PDCCH that is scrambled with MsgB-RNTI. Here, the value of MsgB-RNTI is determined based on the preamble transmitted by the terminal, and the method for calculating the specific value of MsgB-RNTI will be described later. When the terminal receives the PDCCH that is scrambled with MsgB-RNTI, it can receive the PDSCH scheduled by the PDCCH, and depending on whether the reception of the PDSCH is successful, it can transmit a HARQ-ACK to the base station.
[0292] The MsgB-RNTI described above can be interpreted as the RA-RNTI of a terminal performing a 2-step random access process. Therefore, if the index of the preamble selected by one terminal according to the 2-step PRACH setting is the same as the index of the preamble selected according to another new PRACH setting, the two terminals determine the RAR with the same RAPID, resulting in a problem where they cannot determine the RAR they need to receive.
[0293] If the terminal transmits a preamble of a 2-step PRACH configuration, the terminal can determine the MsgB-RNTI value as follows.
[0294] [Mathematical Formula 3]
[0295]
[0296] Here, s_id is the index of the first OFDM symbol of the PRACH opportunity (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH opportunity in the system frame (0 ≤ t_id < 80), f_id is the index of the PRACH opportunity in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the index of the uplink carrier used for random access preamble transmission (0 for NUL carrier and 1 for SUL carrier).
[0297] In one aspect, if the terminal transmits a preamble of a new PRACH setting, the terminal can determine the RA-RNTI value as follows.
[0298] [Mathematical Formula 4]
[0299]
[0300] Here, the new PRACH setting index is an index assigned to each new PRACH setting and can start from 0. Here, X can be determined according to the maximum value that Equation 2, which calculates RA-RNTI, can take. If s_id=13, t_id=79, f_id=7, and ul_carrier_id = 1 are possible, X can be determined as X=17920, which is the maximum value that can be taken according to Equation 2.
[0301] The RA-RNTI obtained according to this example has the following characteristics.
[0302] When a terminal transmits a preamble for a legacy PRACH setting, the value of RA-RNTI has a value between 1 and X=17920 according to Equation 2. When a terminal transmits a preamble for a new PRACH setting, the value of RA-RNTI has a value greater than or equal to X+1 according to Equation 4. Therefore, the terminal that transmitted the preamble for the legacy PRACH setting and the terminal that transmitted the preamble for the new PRACH setting can monitor PDCCH with different RA-RNTI values. Accordingly, the base station can schedule different RARs for the two terminals using the different RA-RNTI values.
[0303] In another aspect, the mathematical formula for calculating RA-RNTI can also be expressed as follows.
[0304] [Mathematical Formula 5]
[0305]
[0306] The content indicated by the ID here is as follows.
[0307] - ID = 0 : Legacy PRACH within NUL Carrier
[0308] - ID = 1 : Legacy PRACH within SUL Carrier
[0309] - ID = 2 : New PRACH with 1st index
[0310] - ID = 3 : New PRACH with 2nd index
[0311] - ID= ...
[0312] In this example, when multiple new PRACH settings are provided, the maximum number of new PRACH settings is 5. That is, the index of the new PRACH is one of the values 0, 1, 2, 3, or 4. For reference, the first index is the lowest index, and the second index is the second lowest index. Here, the index can be uniquely assigned to each new PRACH. The index can be set in the upper layer signal (or RRC signal) that selects each new PRACH, or can be derived according to the setting of each new PRACH. The index can be derived based on at least one of the time and frequency information of the new PRACH setting.
[0313] In another aspect, when the terminal transmits a preamble of a new PRACH setting, the terminal can determine the RA-RNTI value as follows.
[0314] [Mathematical Formula 6]
[0315]
[0316] Here, the new PRACH setting index is an index assigned to each new PRACH setting and can start from 0. Here, X can be determined based on the maximum value that Equation 3, which calculates RA-RNTI, can take. If s_id=13, t_id=79, f_id=7, and ul_carrier_id = 1 are possible, then X can be determined as 35840 according to Equation 3.
[0317] The RA-RNTI obtained according to this example has the following characteristics.
[0318] When a terminal transmits a preamble for a new PRACH setting, the value of RA-RNTI has a value between 1 and X=35840 according to Equation 3. When a terminal transmits a preamble for a new PRACH setting, the value of RA-RNTI has a value greater than or equal to X+1 according to Equation 6. Therefore, the terminal that transmitted the preamble for the existing PRACH setting and the terminal that transmitted the preamble for the new PRACH setting can monitor the PDCCH with different RA-RNTI values. Accordingly, the base station can schedule different RARs for the two terminals using the different RA-RNTI values.
[0319] In another aspect, the mathematical formula for calculating RA-RNTI can also be expressed as follows.
[0320] [Mathematical Formula 7]
[0321]
[0322] The content indicated by the ID here is as follows.
[0323] - ID = 0 : Legacy PRACH within NUL Carrier
[0324] - ID = 1 : Legacy PRACH within SUL Carrier
[0325] - ID = 2 : 2-step PRACH within NUL carrier
[0326] - ID = 3 : 2-step PRACH within SUL carrier
[0327] - ID = 4 : New PRACH with the 1st index
[0328] - ID = 5 : New PRACH with 2nd index
[0329] In the above embodiment, when a plurality of new PRACH settings are provided, the maximum number of new PRACH settings is 2. That is, the index of the new PRACH is a value of either 0 or 1. For reference, the first index is the lowest index, and the second index is the second lowest index. Here, the index can be uniquely assigned to each new PRACH. The index can be set in an upper-level signal (or RRC signal) that selects each new PRACH, or can be derived according to the setting of each new PRACH. The index can be derived based on at least one of the time and frequency information of the setting of the new PRACH.
[0330] For reference, the RedCap terminal may be configured to use a method for calculating RA-RNTI through the SIB. For example, it may be configured to use one of the above mathematical formulas 4 to 6 (or mathematical formulas 5 to 7) through the SIB. As another example, even without a separate instruction from the SIB, it may be configured to use one of the above mathematical formulas 4 to 6 (or mathematical formulas 5 to 7) according to the 2-step RACH setting. For example, if 2-step RACH is set, the RA-RNTI value may be calculated using the above mathematical formula 6 (or mathematical formula 7), and otherwise, the RA-RNTI value may be calculated using the above mathematical formula 4 (or mathematical formula 5). Furthermore, if a 2-step RACH is set and the PRACH resource of the 2-step RACH overlaps with the PRACH resource of the RedCap terminal, the RA-RNTI value can be calculated using Equation 6 (or Equation 7), and if not, the RA-RNTI value can be calculated using Equation 4 (or Equation 5).
[0331] According to the second method, the search space (search space) for monitoring the PDCCH may be determined differently depending on which PRACH setting preamble is transmitted. If the terminal transmits the legacy PRACH setting preamble, the terminal can monitor the PDCCH in the first search space based on the RA-RNTI value to receive the RAR. If the terminal transmits the new PRACH setting preamble, the terminal can monitor the PDCCH in the second search space based on the RA-RNTI value to receive the RAR. Here, the RA-RNTI value can be determined based on Equation 1 for calculating RA-RNTI. That is, different terminals can all monitor the PDCCH with the same RA-RNTI value, but by monitoring the PDCCH in different search spaces, they can receive the RAR corresponding to the preamble they transmitted.
[0332] More specifically, the terminal can receive signaling as follows. The terminal can receive a new PRACH setting for random access and a search space setting corresponding to the new PRACH setting through an SIB transmitted from the base station. Here, through the search space setting, the terminal can know the following information.
[0333] - A slot where the search space is set based on information regarding the period and offset.
[0334] - Number of consecutive slots where the search space is set
[0335] - Symbol where the search space begins within the slot
[0336] - PDCCH aggregation levels (ALs) to monitor in the search space and the number of PDCCH candidates per AL
[0337] - DCI formats to be monitored in the search space
[0338] The search space corresponding to the above new PRACH setting is associated with CORESET#0. Therefore, the search space corresponding to the preamble of the legacy PRACH setting and the search space corresponding to the preamble of the new PRACH setting can be associated with the same CORESET#0, and thus can have the same frequency domain information, CCE-to-REG mapping, and CORESET duration.
[0339] If a separate search space corresponding to the new PRACH is not set, the terminal can monitor the PDCCH for receiving RAR in the search space corresponding to the legacy PRACH. At this time, when monitoring the PDCCH, the RA-RNTI value may be based on the RA-RNTI calculation formulas proposed in the first method to the first method for calculating RA-RNTI.
[0340] According to the third method, the CORESET monitoring the PDCCH may be determined differently depending on which PRACH setting preamble the terminal has transmitted. If the terminal transmits a legacy PRACH setting preamble, the terminal may monitor the PDCCH based on the RA-RNTI value in the search space of the first CORESET to receive the RAR. If the terminal transmits a new PRACH setting preamble, the terminal may monitor the PDCCH based on the RA-RNTI value in the search space of the second CORESET to receive the RAR. Here, the RA-RNTI value may be determined based on Equation #1 for calculating RA-RNTI. That is, the terminal monitors the PDCCH with the same RA-RNTI value, but by monitoring the PDCCH in the search spaces of different CORESETs, it can receive the RAR corresponding to the preamble it transmitted.
[0341] More specifically, the terminal can receive signaling as follows. The terminal can receive a new PRACH setting for random access and a CORESET setting corresponding to the new PRACH setting through an SIB transmitted from the base station. Here, through the CORESET setting, the terminal can obtain the following information.
[0342] - Frequency information where the CORESET is located. This can be determined as a set of 6 consecutive PRBs.
[0343] - Mapping between REGs and CCEs included in the CORESET. This can be either a localized mapping or a distributed mapping.
[0344] - The number of symbols included in the CORESET. This can be 1 symbol or 2 to 3 consecutive symbols.
[0345] According to the fourth method, the downlink initial BWP (DL initial BWP) performing random access may be determined differently depending on which PRACH setting preamble the terminal transmits. If the terminal transmits a legacy PRACH setting preamble, the terminal may monitor the PDCCH based on the RA-RNTI value in the first downlink initial BWP to receive the RAR. If the terminal transmits a new PRACH setting preamble, the terminal may monitor the PDCCH based on the RA-RNTI value in the second downlink initial BWP to receive the RAR. Here, the RA-RNTI value may be determined based on Equation 1 for calculating RA-RNTI. In each downlink initial BWP, a CORESET and a search space (search space) for monitoring the PDCCH may be configured. That is, the terminal monitors the PDCCH with the same RA-RNTI value, but by monitoring the PDCCH at different downlink initial BWPs, it can receive the RAR corresponding to the preamble it transmitted.
[0346] III. Frequency Hopping Method of RedCap Terminal
[0347] FIG. 23 is a diagram showing the scheduling of a physical uplink shared channel in the time domain, and FIG. 24 is a diagram showing the scheduling of a physical uplink shared channel in the frequency domain.
[0348] A method for a terminal to transmit a physical uplink shared channel (PUSCH) is described through FIGS. 23 and 24.
[0349] The terminal can transmit uplink data through a physical uplink shared channel. The terminal can transmit uplink data by a method of scheduling transmission on the physical uplink shared channel (DG, dynamic grant) from downlink control information (DCI) transmitted through reception of the physical downlink control channel (PDCCH), or by a method of transmitting on the physical uplink shared channel according to resources and transmission methods pre-configured from the base station (CG, configured grant).
[0350] Downlink control information (DCI) transmitted to the terminal via PDCCH reception may include scheduling information for PUSCH. This scheduling information may include information regarding the time domain (hereinafter TDRA, time-domain resource assignment) and information regarding the frequency domain (hereinafter FDRA, frequency-domain resource assignment). The terminal may interpret the DCI transmitted via PDCCH reception based on information regarding the control resource set and the search space, and perform an operation indicated by the DCI. The DCI may include one of DCI formats 0_0, 0_1, to 0_2 for scheduling a physical uplink shared channel (PUSCH).
[0351] The time domain information of the PUSCH indicated in the TDRA field within DCI format 0_0, 0_1, to 0_2 includes the following: K2 is an offset value between the slot in which the PDCCH is received from the base station and the slot in which the terminal transmits the PUSCH. SLIV (Start and length indication value) is a joint-coded value of the PUSCH start symbol index (S) and the PUSCH symbol length (L) within the slot indicated by K2.
[0352] When the terminal receives DCI format 0_0, 0_1, to 0_2 scheduling PUSCH in slot n, slot floor(n*2 μPUSCH / n*2 μPDCCH It is determined to be a )+K2 slot. Here, μPUSCH and μPDCCH are the subcarrier spacing (SCS) of the cell where PUSCH is scheduled and the cell that received PDCCH, respectively.
[0353] For example, referring to FIG. 23(a), since the subcarrier interval of the cell receiving the PDCCH and the cell scheduled for PUSCH are the same, when the terminal receives the PDCCH in slot n and is instructed, for example, that the K2 value is 4, the terminal determines that the slot scheduled for PUSCH is slot n+K2=n+4.
[0354] The physical uplink shared channel transmitted by the terminal can apply two mapping types, A and B. The range of values that a SLIV, in which the PUSCH start symbol index and symbol length are jointly encoded, can have varies depending on the PUSCH mapping type. PUSCH mapping type A allows only resource allocation containing DMRS symbols, and DMRS symbols are located in the third or fourth OFDM symbol of the slot according to the value indicated by the upper layer. That is, for PUSCH mapping type A, the index (S) of the PUSCH start symbol can be 0, and the PUSCH length (L) can have one of the values from 4 to 14 (12 for extended CP) depending on the DMRS symbol position. For PUSCH mapping type B, since the DMRS symbol is always the first symbol of the PUSCH, S can have one of the values from 0 to 13 (11 for extended CP), and L can have one of the values from 1 to 14 (12 for extended CP). Also, since one PUSCH cannot cross the boundaries of the slot, the values of S and L must satisfy S+L14 (12 for extended CP).
[0355] Examples of PUSCH according to PUSCH mapping types are illustrated in FIG. 23(b). From top to bottom, the terminal determines that a PUSCH of mapping type A, in which the third symbol is a DMRS symbol, the index (S) of the start symbol is 0, and the length (L) is 7, a PUSCH of mapping type A, in which the fourth symbol is a DMRS symbol, the index (S) of the start symbol is 0, and the length (L) is 7, and a PUSCH of mapping type B, in which the first symbol is a DMRS symbol, the index (S) of the start symbol is 5, and the length (L) is 5, are scheduled. The frequency domain information of the PUSCH indicated in the FDRA field within DCI format 0_0, 0_1, to 0_2 can be divided into two types depending on the frequency resource allocation type.
[0356] The first type is frequency resource allocation type 0, in which a fixed number of PRBs are grouped to form a resource block group (RBG) based on the number of RBs included in the BWP configured for the terminal, and the terminal receives a bitmap in RBG units to determine whether to use the corresponding RBG. The number of PRBs included in a single RBG is configured from the upper layer, and the larger the number of RBs included in the BWP configured for the terminal, the more PRBs are configured. For example, referring to FIG. 24(a), when the BWP size configured for the terminal is 72 PRBs and one RBG is composed of 4 PRBs, the terminal determines 4 PRBs in ascending order starting from PRB 0 as one RBG. That is, if RBG 0 is mapped from PRB 0 to PRB 3, and RBG 1 is mapped from PRB 4 to PRB 7 up to RBG 17, 1 bit (0 to 1) is received for each RBG, for a total of 18 bits, to determine whether the PRB within the corresponding RBG is in use. At this time, if the bit value is 0, it is determined that PUSCH is not scheduled on any of the PRBs within the corresponding RBG, and if the bit value is 1, it is determined that PUSCH is scheduled on all PRBs within the corresponding RBG. Alternatively, the bit values may be applied in reverse.
[0357] The second type is frequency resource allocation type 1, which can indicate information on consecutive PRBs allocated according to the size of the terminal's initial BWP or active BWP. This information is a resource indication value (RIV) in which the start index (S) and length (L) of the consecutive PRBs are jointly encoded. For example, referring to FIG. 24(b), when the terminal's BWP size is 50 PRBs and PUSCH is scheduled from PRB 2 to PRB 11, the start index of the consecutive PRBs is 2 and the length is 10. The terminal has RIV = N size BWPBy receiving *(L-1)+S = 50*(10-1)+2 = 452, the starting index and length of consecutive PRBs scheduled for PUSCH can be determined to be 2 and 10, respectively.
[0358] Limited to DCI formats 0_1 and 0_2 for scheduling PUSCH, the terminal may be configured by the upper layer to use only one of the two frequency resource allocation types of PUSCH or to use both types dynamically. If configured to use both types dynamically, the terminal may determine which type it is through the MSB (most significant bit) 1 bit of the FDRA field in DCI formats 0_1 and 0_2 for scheduling PUSCH.
[0359] It supports a grant-based uplink shared channel transmission method configured to support uplink URLLC transmission, and this method is also referred to as grant-free transmission. In the configured grant-based uplink transmission method, the base station configures resources available for uplink transmission to the terminal via the upper layer, namely RRC signaling, and the terminal then transmits the uplink shared channel using those resources. This method can be divided into two types depending on whether activation or deactivation is possible via DCI.
[0360] Type 1 configured grant-based transmission is a method of setting resources and transmission methods for grant-based transmission that are pre-configured at the upper layer.
[0361] Type 2 configured grant-based transmission method is a method that establishes grant-based transmission configured at the upper layer, and receives instructions from the DCI, which transmits resources and methods for transmission through the physical downlink control channel.
[0362] Since the configured grant-based uplink transmission method supports URLLC transmission, it supports repetitive transmission across multiple slots to ensure high reliability. In this case, the redundancy version (RV) sequence is set to one of the values {0, 0, 0, 0}, {0, 2, 3, 1}, or {0, 3, 0, 3}, and the RV corresponding to the mod(n-1, 4)+1 value is used for the n-th repetitive transmission. Additionally, a terminal configured for repetitive transmission can only initiate repetitive transmission in the slot where the RV value is 0. However, if the RV sequence is {0, 0, 0, 0} and repetitive transmission occurs across 8 slots, repetitive transmission cannot be initiated in the 8th slot. The terminal terminates repetitive transmission when it reaches the number of repetitive transmissions set by the upper layer, exceeds the cycle, or receives a UL grant with the same HARQ process ID. Here, the UL grant refers to the DCI that schedules PUSCH.
[0363] In order to increase the reception and transmission reliability of the physical uplink shared channel between a base station and a terminal in a wireless communication system, the terminal may receive repeated transmission of the uplink shared channel from the base station. This is explained through FIG. 25.
[0364] FIG. 25 is a diagram showing the repeated transmission of a physical uplink shared channel according to an example.
[0365] Referring to Fig. 25, the PUSCH repeated transmissions that a terminal can transmit can be divided into two types.
[0366] First, the transmission process of the terminal's PUSCH repetitive transmission type A is as follows. When the terminal receives DCI formats 0_1 to 0_2 from the base station via a PDCCH that schedules the PUSCH, PUSCH repetitive transmission is possible in K consecutive slots. Here, the terminal can receive the value of K by setting it from an upper layer or by adding it to the TDRA field of the DCI. For example, referring to FIG. 25(a), assuming that the terminal receives a PDCCH that schedules the PUSCH in slot n and receives 2 as the value of K2 and 4 as the value of K from the DCI format received via the PDCCH, the terminal starts transmitting the PUSCH in slot n+K2, i.e., n+2, and the terminal repetitively transmits the PUSCH from slot n+2 to slot n+2+K-1, i.e., n+5. At this time, the time and frequency resources for transmitting the PUSCH in each slot are the same as those indicated in the DCI. That is, PUSCH can be transmitted from the same symbol and PRB(s) within the slot.
[0367] Next, the transmission process of PUSCH repeat transmission type B, which supports low-latency PUSCH repeat transmission to satisfy the requirements of URLLC, is as follows. The terminal can receive instructions from the base station regarding the PUSCH start symbol (S) and the PUSCH length (L) through the TDRA field. The PUSCH obtained from the instructions regarding the start symbol and length is referred to as a nominal PUSCH, as it is a temporarily obtained PUSCH rather than the actual PUSCH transmitted. Additionally, the terminal can receive instructions regarding the nominal repetition count (N) of the aforementioned nominal PUSCH through the TDRA field. The terminal can determine N nominal PUSCHs, including the nominal PUSCH indicated through the TDRA field. Here, the length of the N nominal PUSCHs is the same as L, and they are continuous in the time axis without separate symbols between the nominal PUSCHs.
[0368] The terminal can determine the actual PUSCH from the aforementioned nominal PUSCHs. A single nominal PUSCH can be determined as one or more actual PUSCHs. The terminal may be instructed or set by the base station to symbols that cannot be used in PUSCH repeat transmission type B. These are called invalid symbols. The terminal can exclude invalid symbols from the nominal PUSCHs. As previously mentioned, nominal PUSCHs are determined as a sequence of symbols, but they can be determined discontinuously if invalid symbols are excluded. The actual PUSCH can be determined as a sequence of symbols from a nominal PUSCH excluding invalid symbols. Here, if the sequence of symbols crosses the boundary of a slot, the actual PUSCH can be divided based on that boundary.
[0369] For reference, the invalid symbol may include at least the DL symbol configured by the base station for the terminal.
[0370] For example, with reference to FIG. 25(b), let us assume that the terminal is scheduled to transmit a PUSCH of length 5 symbols starting from the 12th OFDM symbol of the first slot (slot n) and is instructed to transmit four Type B repeats. The nominal PUSCHs are as follows. The first nominal PUSCH (nominal#1) includes symbols (n,11), (n,12), (n,13), (n+1,0), and (n+1,1). The second nominal PUSCH (nominal#2) includes symbols (n+1,2), (n+1,3), (n+1,4), (n+1,5), and (n+1,6). The third nominal PUSCH (nominal#3) includes symbols (n+1,7), (n+1,8), (n+1,9), (n+1,10), and (n+1,11). The fourth nominal PUSCH (nominal#4) includes symbols (n+1,12), (n+1,13), (n+2,0), (n+2,1), and (n+2,2). Here, symbol (n,k) represents symbol k of slot n. The symbol k index ranges from 0 to 13 for normal CP and from 0 to 11 for extended CP.
[0371] Let us assume that invalid symbols are set or directed to symbols 6 and 7 of slot n+1. Depending on the invalid symbols set or directed from the base station, the last symbol of the second nominal PUSCH (nominal#2) is excluded, and the first symbol of the third nominal PUSCH (nominal#3) is excluded.
[0372] The first nominal PUSCH (nominal #1) is divided by the slot boundary into two actual PUSCHs (actual #1 and actual #2). The second nominal PUSCH (nominal #2) and the third nominal PUSCH (nominal #3) are each divided into one actual PUSCH (actual #3 and actual #4) by grouping consecutive symbols excluding invalid symbols. Finally, the fourth nominal PUSCH (nominal #4) is divided by the slot boundary into two actual PUSCHs (actual #5 and actual #6). The terminal ultimately transmits the actual PUSCHs.
[0373] An actual PUSCH must contain at least one DMRS symbol, and when PUSCH repeat transmission type B is set, an actual PUSCH of one symbol length may be omitted without being transmitted. This is because an actual PUSCH of one symbol cannot transmit information other than the DMRS.
[0374] To obtain diversity gain in the frequency domain, frequency hopping can be set in the terminal.
[0375] In the case of PUSCH repetitive transmission type A, frequency hopping can be configured for the terminal as either intra-slot frequency hopping, which performs frequency hopping within a slot, or inter-slot frequency hopping, which performs frequency hopping for each slot. If intra-slot frequency hopping is configured for the terminal, the terminal divides the PUSCH in the time domain in the slot where the PUSCH is transmitted in half; one half is transmitted from the scheduled PRB, and the other half is transmitted from the PRB obtained by adding an offset value to the scheduled PRB. At this time, the offset value is set to two or four values depending on the active BWP size through the upper layer, and one of these values can be instructed to the terminal through the DCI. If inter-slot frequency hopping is configured for the terminal, the PUSCH is transmitted from the scheduled PRB in slots with even slot indices, and the PUSCH is transmitted from the PRB obtained by adding an offset value to the scheduled PRB in odd slots.
[0376] In the case of PUSCH repetitive transmission type B, frequency hopping can be configured as either inter-repetition frequency hopping, which performs frequency hopping at nominal PUSCH boundaries, or inter-slot frequency hopping, which performs frequency hopping at every slot. If inter-repetition frequency hopping is configured for the terminal, the terminal transmits the actual PUSCH(s) corresponding to the odd-numbered nominal PUSCH from the scheduled PRB, and transmits the actual PUSCH(s) corresponding to the even-numbered nominal PUSCH from the PRB obtained by adding an offset value to the scheduled PRB. At this time, the offset value is set to two or four values depending on the active BWP size through the upper layer, and one of these values can be instructed to the terminal through the DCI. When inter-slot frequency hopping is configured for the terminal, the actual PUSCH for slots with even slot indices is transmitted from the scheduled PRB, and the actual PUSCH for slots with odd slot indices is transmitted from the PRB obtained by adding an offset value to the scheduled PRB.
[0377] When the terminal performs repeated PUSCH transmission, if a symbol scheduled for PUSCH transmission in a specific slot overlaps with a semi-statically configured DL symbol or a symbol position set for receiving an SS / PBCH block, the terminal does not transmit the overlapping PUSCH in that slot and does not defer transmission to the next slot.
[0378] A method for a terminal to transmit a physical uplink control channel (PUCCH) is described below through FIG. 26.
[0379] Figure 26 is a diagram showing the scheduling of a physical uplink control channel.
[0380] Referring to FIG. 26, when a terminal receives DCI formats 1_0, 1_1, and 1_2 that schedule a physical uplink control channel, the terminal must transmit the scheduled uplink control channel. The physical uplink control channel may include uplink control information (UCI), and the UCI may include HARQ-ACK, SR, and CSI information. The HARQ-ACK information may be HARQ-ACK information regarding the success of reception of two types of channels. As a first type, if a physical downlink shared channel (PDSCH) is scheduled through the DCI formats 1_0, 1_1, and 1_2, it may be a HARQ-ACK regarding the success of reception of that physical downlink shared channel (PDSCH). In the second type, if the above DCI format 1_0, 1_1, and 1_2 is a DCI that indicates the release of the semi-static physical downlink shared channel (SPS PDSCH), it may be a HARQ-ACK regarding whether the reception of the above DCI format 1_0, 1_1, and 1_2 was successful.
[0381] In order to transmit a PUCCH that conveys a HARQ-ACK, the PDSCH-to-HARQ_feedback timing indicator field included in the DCI formats 1_0, 1_1, and 1_2 may indicate a K1 value, which is a value for information about the slot to be transmitted on the scheduled uplink control channel. Here, the value of K1 may be a non-negative integer. The K1 value of DCI format 1_0 may indicate one of {0, 1, 2, 3, 4, 5, 6, 7}. The K1 values that can be indicated in DCI formats 1_1 and 1_2 may be configured or set by the upper layer.
[0382] The terminal can determine the slot for transmitting an uplink control channel containing HARQ-ACK information of the first type as follows. The terminal can determine an uplink slot that overlaps with the last symbol of the physical downlink shared channel (PDSCH) corresponding to the HARQ-ACK information. When the index of the uplink slot is denoted as m, the uplink slot for transmitting the physical uplink control channel containing the HARQ-ACK information by the terminal may be m+K1. Here, the index of the uplink slot is a value based on the subcarrier interval of the uplink BWP in which the uplink control channel is transmitted.
[0383] For reference, when the terminal receives downlink slot aggregation, the aforementioned ending symbol represents the last symbol of the PDSCH scheduled within the last slot among the slots in which the physical downlink shared channel (PDSCH) is received.
[0384] Referring to FIG. 26, let us assume that the subcarrier interval of the DL BWP in which the PDCCH is received, the subcarrier interval of the DL BWP in which the PDSCH is scheduled, and the subcarrier interval of the UL BWP in which the PUCCH is transmitted are the same. Let us assume that a terminal receives a PDCCH from a base station in slot n in which the PDSCH and PUCCH are scheduled, and that K0=2 and K1=3 indicated in the DCI transmitted by the PDCCH. If the reception of the last symbol of the PDSCH ends in slot n+K0, i.e., n+2, the terminal must transmit the HARQ-ACK of the corresponding PDSCH through the PUCCH in slot n+2+K1, i.e., n+5.
[0385] In order to secure wide coverage in an NR system, a terminal may be configured to repeatedly transmit a long PUCCH (PUCCH format 1, 3, 4) in 2, 4, to 8 slots. When the terminal is configured to repeatedly transmit a PUCCH, the same UCI is repeatedly transmitted in every slot. This is explained with reference to FIG. 27.
[0386] Figure 27 is a diagram showing the repeated transmission of a physical uplink control channel.
[0387] Referring to FIG. 27, when the reception of PDSCH ends in slot n and K1=2, the terminal transmits PUCCH in slot n+K1, i.e., n+2. At this time, the number of repeated transmissions for PUCCH to the terminal is N repeat PUCCH If configured and set to =4, PUCCH is repeatedly transmitted from slot n+2 to slot n+5. The symbol composition of the repeatedly transmitted PUCCHs is identical. That is, the repeatedly transmitted PUCCHs start with the same symbol in each slot and consist of the same number of symbols.
[0388] To obtain diversity gain in the frequency domain, frequency hopping can be configured in the terminal. Frequency hopping can be configured as intra-slot frequency hopping, which performs frequency hopping within a slot, or inter-slot frequency hopping, which performs frequency hopping for each slot. If intra-slot frequency hopping is configured for the terminal, the terminal divides the PUCCH in half in the time domain during the slot where the PUCCH is transmitted, transmitting half at the first PRB and the other half at the scheduled second PRB. At this time, the first PRB and the second PRB can be configured for the terminal through an upper layer that configures PUCCH resources. If inter-slot frequency hopping is configured for the terminal, the terminal transmits the PUCCH at the first PRB in slots with even indices and transmits the PUCCH at the second PRB in slots with odd indices.
[0389] When the terminal performs repeated PUCCH transmission, if the symbol to be transmitted for PUCCH in a specific slot overlaps with a semi-statically configured DL symbol or a symbol position set for receiving an SS / PBCH block, the terminal does not transmit PUCCH in that slot and postpones transmission to the next slot, and if the PUCCH symbol does not overlap with a semi-statically configured DL symbol or a symbol position set for receiving an SS / PBCH block in that slot, the terminal transmits PUCCH.
[0390] When transmitting PUSCH to PUCCH, the terminal may use a frequency hopping method to obtain frequency diversity gain. Here, the frequency hopping method refers to transmitting PUSCH to PUCCH in the 0th PRB set and transmitting PUSCH to PUCCH in the 1st PRB set. For reference, in the description of the present invention, PUSCH to PUCCH transmitted in the 0th PRB set is referred to as hop 0, and PUSCH to PUCCH transmitted in the 1st PRB set is referred to as hop 1. In the present invention, only up to two hops (hop 0 and hop 1) are described, but the number of hops may be increased.
[0391] When a terminal transmits PUSCH or PUCCH, the method for determining the 0th PRB set of hop 0 and the 1st PRB set of hop 1 is as follows.
[0392] The PUCCH prior to the RRC connection can be determined as follows. For reference, the PUCCH prior to the RRC connection is the PUCCH that transmits a HARQ-ACK, which is a successful reception acknowledgment for the PDSCH containing Msg4.
[0393] The terminal selects one PUCCH resource from among 16 PUCCH resources. At this time, the selection is determined based on the PUCCH resource indicator included in the DCI format for scheduling PUCCH or the index of the CCE (control channel element) to which the DCI format was received. The index of the selected PUCCH resource is r PUCCH If so, it can have one of the values 0, 1, ..., 15.
[0394] If r PUCCH If is a value among 0, 1, ..., 7, the index of the 0th PRB set at hop 0 of the selected PUCCH resource is And, the index of the first PRB set of hop 1 is is. If rPUCCH is a value of 8, 9, ..., 15, the index of the 0th PRB set at hop 0 of the selected PUCCH resource is And, the index of the first PRB set of hop 1 is am.
[0395] Here, N size BWP is the number of PRBs included in the active BWP transmitting PUCCH. Here, if PUCCH transmits the HARQ-ACK of Msg4 PDSCH, the active BWP is the initial UL BWP. This initial UL BWP is configured in SIB1 (system information block) as the UL BWP for the terminal to establish cell access. N CS is the number of initial cyclic shift indices, and RB BWP offset The initial cyclic shift index is as shown in Table 4.
[0396] [Table 4]
[0397]
[0398] Here, if the index of the RB where the 0th PRB set of hop 0 begins is 0, it indicates the lowest PRB of the terminal's active BWP. For reference, when PUCCH transmits the HARQ-ACK of Msg4 PDSCH, the active BWP is the initial UL BWP. That is, the index of the RB where the 0th PRB set of hop 0 begins is interpreted as the index of the initial UL BWP.
[0399] For PUCCH after RRC connection, it can be determined as follows.
[0400] The index of the lowest PRB in the 0th PRB set of hop 0 of PUCCH and the index of the lowest PRB in the 1st PRB set of hop 1 of PUCCH may be set as PUCCH resources to the terminal via an RRC signal. That is, when the terminal is instructed to a PUCCH resource, it can transmit hop 0 and hop 1 using the index of the lowest PRB in the 0th PRB set of hop 0 of hop 0 and the index of the lowest PRB in the 1st PRB set of hop 1 of hop 1 that are set in the PUCCH resource. Here, if the index of the PRB is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the PRB is interpreted as the index of the terminal's active BWP.
[0401] In the case of PUSCH, it can be determined as follows.
[0402] The terminal can determine the 0th PRB set of hop 0 through a DCI that schedules PUSCH or a DCI / RRC signal that activates PUSCH. Here, the DCI that schedules PUSCH or the DCI / RRC signal that activates PUSCH may include a frequency domain resource assignment (FDRA) field. The FDRA field may include the index of the RB where the 0th PRB set of hop 0 starts and the number of consecutive RBs. Here, if the index of the RB where the 0th PRB set of hop 0 starts is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the RB where the 0th PRB set of hop 0 starts is interpreted as the index of the terminal's active BWP. The terminal must determine the index of the RB where the 1st PRB set of hop 1 starts. This can be determined through the following equation.
[0403]
[0404] Here, RB start (0) represents the index of the RB where the 0th PRB set of hop 0 begins, and RB start (1) indicates the index of the RB where the first PRB set of hop 1 begins. RB offset represents the PRB interval between the 0th PRB set of hop 0 and the 1st PRB set of hop 1. The base station sends RB to the terminal. offset It can set and instruct, and the above RB offset The values are 0, 1, ..., N BWP size It can be one of the values -1. N BWP sizerepresents the number of PRBs included in the terminal's active BWP. If the index of the RB where the first PRB set of hop 1 begins, calculated using the above formula, is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the RB where the first PRB set of hop 1 begins (RB start (1)) is interpreted as the index of the active BWP of the terminal.
[0405] When PUSCH transmits Msg3, RBoffset can have one of the following values. If the initial UL BWP size is less than 50 RBs, RB offset silver and It can be one of the values, and if the initial UL BWP size is greater than 50RBs, RB offset silver , and - It can be one of the values. Here, in the case of Msg3 PUSCH, since the initial UL BWP is the active BWP, N BWP size is the number of RBs included in the initial UL BWP.
[0406] In the frequency hopping method discussed earlier, the 0th PRB set of hop 0 and the 1st PRB set of hop 1 are located within the active BWP. For reference, in the case of the PUSCH prior to the RRC connection (i.e., Msg3 PUSCH) and PUCCH (i.e., the PUCCH transmitting the HARQ-ACK of Msg4 PDSCH), the active BWP is the initial UL BWP. However, the terminal may require frequency hopping in a frequency band other than the active BWP in the following situations.
[0407] As a first example, this is the case where the RF bandwidth supported by the terminal is significantly smaller than the bandwidth supported by the cell. For example, refer to FIG. 28.
[0408] Figure 28 is a diagram showing frequency hopping.
[0409] Referring to Fig. 28, let us assume that the RF bandwidth of the terminal supports up to 20 MHz and the bandwidth supported by the cell supports 100 MHz. Since the RF bandwidth of the terminal supports up to 20 MHz, the active BWP of the terminal can only support up to 20 MHz. Therefore, if a frequency hopping method is used according to the above method, the frequency diversity gain that can be obtained may be small.
[0410] - As a second example, even if the RF bandwidth supported by the terminal is not small, the terminal needs to keep the bandwidth of the active BWP small for lower energy consumption. In this case, as in the first example, if a frequency hopping method is used according to the preceding method, the frequency diversity gain that can be obtained may be small.
[0411] To improve the transmission method using frequency hopping within the active BWP as described above, the following frequency hopping methods can be considered.
[0412] Figure 29 is a diagram showing broadband frequency hopping.
[0413] Referring to FIG. 29(a), the first PRB set of hop 0 of the terminal and the second PRB set of hop 1 may be significantly separated from a specific frequency. In this case, one hop may be located within the active BWP. More specifically, the 0th PRB set of hop 0 may be located within the terminal's active BWP, but the 1st PRB set of hop 1 may be located in a frequency band outside the terminal's active BWP. Conversely, the 1st PRB set of hop 1 may be located within the terminal's active BWP, but the 0th PRB set of hop 0 may be located in a frequency band outside the terminal's active BWP. As another example, referring to FIG. 18(b), the first PRB set of hop 0 of the terminal and the second PRB set of hop 1 may be significantly separated from a specific frequency. At this time, the two hops may be located in a frequency band outside the active BWP. More specifically, the 0th PRB set of hop 0 and the 1st PRB set of hop 1 may be located in a frequency band outside the active BWP of the terminal.
[0414] A signaling method is disclosed for a terminal to transmit one or two hops in a frequency band outside the active BWP, as shown in the example of FIG. 29.
[0415] For PUCCH prior to RRC connection, it can be determined as follows.
[0416] If r PUCCH If is a value among 0, 1, ..., 7, the index of the 0th PRB set at hop 0 of the selected PUCCH resource is And, the index of the first PRB set of hop 1 is is. If r PUCCH If is a value among 8, 9, ..., 15, the index of the 0th PRB set at hop 0 of the selected PUCCH resource is And, the index of the first PRB set of hop 1 is is. Here, N BWP size is the number of PRBs included in a specific BWP transmitting PUCCH. Here, if PUCCH transmits the HARQ-ACK of Msg4 PDSCH, the aforementioned specific BWP is the initial UL BWP of a general terminal. The initial UL BWP of a general terminal is configured in SIB1 (system information block) as the UL BWP for the general terminal's cell connection. For reference, the terminal in the preceding first or second example has an active BWP with less bandwidth than the initial UL BWP of the general terminal. That is, the terminal can determine the 0th PRB set of hop 0 and the 1st PRB set of hop 1 based on a bandwidth greater than the bandwidth of the active BWP it can have. Here, if the index of the RB starting the 0th PRB set of hop 0 is 0, it indicates the lowest PRB of the specific BWP. That is, if the index of the RB where the 0th PRB set of hop 0 starts is 0, it represents the lowest PRB of the initial UL BWP of a typical terminal.
[0417] For PUCCH after RRC connection, it can be determined as follows.
[0418] The index of the lowest PRB in the 0th PRB set of hop 0 of PUCCH and the index of the lowest PRB in the 1st PRB set of hop 1 may be set as PUCCH resources to the terminal via an RRC signal. That is, when the terminal is instructed to a PUCCH resource, it may transmit hop 0 and hop 1 using the index of the lowest PRB in the 0th PRB set of hop 0 and the index of the lowest PRB in the 1st PRB set of hop 1 of hop 1, which are set in the said PUCCH resource. Here, if the PRB index is 0, it indicates the lowest PRB of a specific BWP of the terminal. That is, the PRB index is interpreted as the index of a specific BWP of the terminal. Here, the specific BWP may be one of the following.
[0419] As an example of the specific BWP mentioned above, a terminal may receive the specific BWP from a base station. The terminal may receive from the base station an index of the starting RB of the specific BWP or the number of PRBs included in the BWP. At this time, the starting RB index of the specific BWP may be set based on the starting RB index of the terminal's active BWP. That is, the difference between the starting RB index of the specific BWP and the starting RB index of the terminal's active BWP may be set.
[0420] As an example of the specific BWP mentioned above, the terminal may assume that the cell has a maximum BWP. The cell's maximum BWP can be determined as follows. Upon initial connection to the cell, the terminal is set to the frequency position of the PRB corresponding to cell common PRB index 0. The 275 consecutive PRBs starting from the cell common PRB index 0 can be grouped together and determined as the cell's maximum BWP. That is, any BWP is included in the cell's maximum BWP. By utilizing the cell's maximum BWP in this way, the base station can transmit a PUCCH to the terminal by frequency hopping at any frequency of the cell.
[0421] As an example of the specific BWP mentioned above, the terminal may use the initial UL BWP of a general terminal. The initial UL BWP of a general terminal is configured in SIB1 (system information block) as a UL BWP for cell connection of the general terminal. For reference, in the case of the terminal of the preceding first or second example, it has an active BWP with less bandwidth than the initial UL BWP of the general terminal.
[0422] In the case of PUSCH, it can be determined as follows.
[0423] (1) First embodiment
[0424] FIG. 30 is a diagram showing broadband frequency hopping according to one embodiment of the present invention.
[0425] Referring to FIG. 30, the terminal can determine the 0th PRB set of hop 0 through a DCI that schedules PUSCH or a DCI / RRC signal that activates PUSCH. Here, the DCI that schedules PUSCH or the DCI / RRC signal that activates PUSCH may include a frequency domain resource assignment (FDRA) field. The FDRA field may include the index of the RB where the 0th PRB set of hop 0 starts and the number of consecutive RBs. Here, if the index of the RB where the 0th PRB set of hop 0 starts is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the RB where the 0th PRB set of hop 0 starts is interpreted as the index of the terminal's active BWP. The terminal must determine the index of the RB where the first PRB set of hop 1 begins. This can be determined through the following mathematical formula.
[0426]
[0427] Here, RB start (0) represents the index of the RB where the 0th PRB set of hop 0 begins, and RB start (1) indicates the index of the RB where the first PRB set of hop 1 begins. RB offset represents the PRB interval between the 0th PRB set of hop 0 and the 1st PRB set of hop 1. The base station sends RB to the terminal. offset을 It can be set and instructed, and the above RB offset The value of can be a positive number, 0, or one of negative numbers. More specifically, RB offsetThe value of can be one of -274, -273, ..., 0, ..., 273, or 274. If the index of the RB where the first PRB set of hop 1 begins, calculated using the above formula, is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the RB where the first PRB set of hop 1 begins (RB start (1)) is interpreted as the index of the terminal's active BWP. If the index of the RB where the first PRB set of the obtained hop 1 starts is negative, it indicates a PRB in a frequency band lower than the terminal's active BWP. For example, if the index of the RB where the first PRB set of the hop 1 starts is -A, it indicates a PRB that is A PRB lower than the lowest PRB of the terminal's active BWP.
[0428] (2) Second embodiment
[0429] FIG. 31 is a diagram showing broadband frequency hopping according to another embodiment of the present invention.
[0430] Referring to FIG. 31, the terminal can determine the 0th PRB set of hop 0 through a DCI that schedules PUSCH or a DCI / RRC signal that activates PUSCH. Here, the DCI that schedules PUSCH or the DCI / RRC signal that activates PUSCH may include a frequency domain resource assignment (FDRA) field. The FDRA field may include the index of the RB where the 0th PRB set of hop 0 starts and the number of consecutive RBs. Here, if the index of the RB where the 0th PRB set of hop 0 starts is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the RB where the 0th PRB set of hop 0 starts is interpreted as the index of the terminal's active BWP. The terminal must determine the index of the RB where the first PRB set of hop 1 begins. This can be determined through the following equation.
[0431]
[0432] Here, RB start (0) represents the index of the RB where the 0th PRB set of hop 0 begins, and RB start (1) indicates the index of the RB where the first PRB set of hop 1 begins. RB offset represents the PRB interval between the 0th PRB set of hop 0 and the 1st PRB set of hop 1. The base station sends RB to the terminal. offset It can be configured and instructed. The terminal can receive from the base station a specific BWP where the first PRB set of hop 1 may be located. This specific BWP is N VBWP size It may include several PRBs. The specific BWP may include the active BWP of the terminal. RBoffset VBWP represents the difference between the index of the lowest PRB of the terminal's active BWP and the lowest index of the specific BWP.
[0433] If the index of the RB where the first PRB set of hop 1 begins, calculated using the above formula, is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the RB where the first PRB set of hop 1 begins (RB start (1)) is interpreted as the index of the terminal's active BWP. If the index of the RB where the first PRB set of the obtained hop 1 starts is negative, it indicates a PRB in a frequency band lower than the terminal's active BWP. For example, if the index of the RB where the first PRB set of the hop 1 starts is -A, it indicates a PRB that is A PRB lower than the lowest PRB of the terminal's active BWP.
[0434] (3) Third embodiment
[0435] FIG. 32 is a diagram showing broadband frequency hopping according to another embodiment of the present invention.
[0436] Referring to FIG. 32, in the preceding first and second embodiments, the terminal determined the frequency positions of the 0th PRB set of hop 0 and the 1st PRB set of hop 1. At this time, the active BWP of the terminal was fixed. In the third embodiment of the present invention, the terminal proposes a method for shifting the active BWP in the frequency band. The terminal can determine the 0th PRB set of hop 0 through a DCI that schedules PUSCH or a DCI / RRC signal that activates PUSCH. Here, the DCI that schedules PUSCH or the DCI / RRC signal that activates PUSCH may include a frequency domain resource assignment (FDRA) field. The FDRA field may include the index of the RB where the 0th PRB set of hop 0 starts and the number of consecutive RBs. Here, if the index of the RB starting from the 0th PRB set of hop 0 is 0, it represents the lowest PRB of the terminal's active BWP. That is, the index of the RB starting from the 0th PRB set of hop 0 is interpreted as the index of the terminal's active BWP. The terminal must determine the index of the RB starting from the 1st PRB set of hop 1. To this end, the frequency domain of the terminal's active BWP can be changed as follows.
[0437]
[0438] Here, N BWP start,μ (0) represents the lowest PRB index of the active BWP that transmitted hop 0, and N BWP start,μ (1) represents the lowest PRB index of the new active BWP for transmitting hop 1. RB offset BWPrepresents the interval between the lowest PRB index of the active BWP that transmitted hop 0 and the lowest PRB index of the new active BWP to transmit hop 1. N cell-BW size is the number of PRBs contained in the cell. The RB index where the first set of PRBs of hop 1 begins is as follows.
[0439]
[0440] That is, the RB index at which the 0th PRB set of hop 0 begins and the RB index at which the 1st PRB set of hop 1 begins are the same. However, since the active BWP that transmitted hop 0 and the active BWP that transmitted hop 1 are different, the two hops are transmitted at different frequencies. That is, if the RB index at which the 1st PRB set of hop 1 begins is 0, it indicates the lowest PRB of the terminal's new active BWP. That is, the RB index at which the 1st PRB set of hop 1 begins is interpreted as the index of the terminal's new active BWP.
[0441] (4) 4th embodiment
[0442] FIG. 33 is a diagram showing broadband frequency hopping according to one embodiment of the present invention.
[0443] Referring to FIG. 33, in the preceding third embodiment, the terminal RB the active BWP offset BWPIt shifted in the frequency domain according to the value. In the fourth embodiment, frequency hopping is enabled by transmitting hop 0 from the 0th active BWP and switching hop 1 to the 2nd active BWP. The terminal can determine the 0th PRB set of hop 0 through a DCI that schedules PUSCH or a DCI / RRC signal that activates PUSCH. Here, the DCI that schedules PUSCH or the DCI / RRC signal that activates PUSCH may include a frequency domain resource assignment (FDRA) field. The FDRA field may include the index of the RB where the 0th PRB set of hop 0 begins and the number of consecutive RBs. Here, if the index of the RB where the 0th PRB set of hop 0 begins is 0, it indicates the lowest PRB of the terminal's active BWP. That is, the index of the RB that starts the 0th PRB set of hop 0 is interpreted as the index of the terminal's active BWP. The terminal must determine the index of the RB that starts the 1st PRB set of hop 1. To determine the index of the RB that starts the 1st PRB set of hop 1, the terminal may be indicated or set a 2nd active BWP. Here, the 2nd active BWP may differ from the active BWP transmitted by hop 0 in at least the frequency domain or subcarrier spacing. The terminal can obtain the index of the 1st PRB set of hop 1 by interpreting the index of the RB indicated by the previously obtained FDRA field as the index of the 2nd active BWP. The number of PRBs included in the first PRB set of hop 1 is the same as the number of PRBs included in the zero PRB set of hop 0.
[0444] In the preceding first and second embodiments, the terminal transmits a channel and a signal in a frequency band outside the RF bandwidth of the terminal. In this case, the RF of the terminal needs to move from transmission in the previous frequency band to transmission in the new frequency band. The time required for this can be called RF switching time (switching time). The terminal requires a sufficient amount of RF switching time. That is, the base station must guarantee a sufficient amount of RF switching time to the terminal.
[0445] The RF switching time can be given in time units. For example, it can be set to x ms (millisecond) or x us (microsecond). Alternatively, it can be given in x samples. In this case, if the time length of one sample is denoted as Ts (second), the value is Ts = 1 / (Δf ref ·N f,ref )), Δf ref =15·10 3 Hz and N f,ref = 2048. In this case, if the time length of one sample is expressed as Tc (second), the value is Tc = 1 / ((Δf max ·N max )) and, Δf max =480·10 3 , N f =4096.
[0446] This time can be set differently for each frequency band. The terminal can determine the number of symbols corresponding to the value given in the above time unit. For example, if the above given value is x ms, the terminal can determine the number of symbols corresponding to x ms by dividing x ms by the length of one symbol (symbol_duration). That is, the number of symbols is x ms / symbol_duration. For reference, symbol_duration can be calculated as follows.
[0447] When using Normal CP, the length of an OFDM symbol may vary per symbol. This is because the length of the cyclic prefix (CP) differs. More specifically, when using Normal CP, the CP length is represented as follows: the OFDM symbol index within the subframe is 0 or 7*2 μ If so, 144*κ*2 -μ It is +16*κ, and for the remaining OFDM symbol index, it is 144*κ*2 -μ is. Here, μ is the subcarrier spacing configuration, which is 0 if the subcarrier spacing is 15 kHz, 1 if 30 kHz, 2 if 60 kHz, and 3 if 120 kHz. And κ = Ts / Tc = 64.
[0448] The shorter of the symbol lengths can be used as the symbol_duration to calculate the number of symbols mentioned above. That is, the symbol_duration is 144*κ*2 -μ It is *Tc (second). Using such a short length is to obtain the minimum number of symbols required to guarantee the RF switching time.
[0449] As another example, when a terminal transmits on an uplink channel, it can obtain beam diversity by transmitting to a different next beam. In this case, time is required for the terminal to switch from the first beam to the second beam. This can be called the beam switching time. The terminal must satisfy the beam switching time. To this end, the base station may set the time required for beam switching to the terminal, similar to the RF switching time, and the terminal may determine the number of symbols required for the beam switching time.
[0450] In the following description of the invention, the number of symbols for ensuring the RF switching time or beam switching time is denoted as G. For reference, if the terminal requires RF switching due to frequency hopping and beam switching due to beam change, the value of G may be determined based on the sum or maximum value of the RF switching time or beam switching time. The terminal cannot transmit an uplink signal during the G symbols.
[0451] The problem to be solved by the present invention is a method for arranging G number of symbols that cannot be transmitted when transmitting an uplink channel or signal. Methods for this are disclosed below.
[0452] In addition, for convenience, the present invention describes a method of arranging G symbols to satisfy the RF switching time between frequency hopping. This can be interpreted as a method of arranging G symbols to satisfy the beam switching time by replacing frequency hopping with beam changing.
[0453] Figure 34 shows a PUSCH repetition type B according to an example.
[0454] Referring to FIG. 34, the terminal is scheduled to repeat PUSCH with a length of 4 (L=4) 4 times (K=4), starting from symbol 8 (S=8) of slot 0. As shown in FIG. 34(a), the terminal can create 4 nominal repetitions by grouping 4 symbols starting from symbol 8 of slot 0. Here, nominal repetition 0 includes symbols 8, 9, 10, and 11 of slot 0; nominal repetition 1 includes symbols 12 and 13 of slot 0 and symbols 0 and 1 of slot 1; nominal repetition 2 includes symbols 2, 3, 4, and 5 of slot 1; and nominal repetition 3 includes symbols 6, 7, 8, and 9 of slot 1.
[0455] As shown in FIG. 34(b), nominal repetitions can be split at the boundaries of slots (although not shown in the figure, splitting may also occur around symbols where UL transmission is invalid) to group consecutive symbols into one slot to create actual repetitions. Referring to FIG. 34(b), nominal repetition 1 can be split into two actual repetitions. Thus, the terminal can transmit PUSCH with five actual repetitions. More specifically, actual repetition 0 includes symbols 8, 9, 10, and 11 of slot 0; actual repetition 1 includes symbols 12 and 13 of slot 0; actual repetition 2 includes symbols 0 and 1 of slot 1; actual repetition 3 includes symbols 2, 3, 4, and 5 of slot 1; and actual repetition 4 includes symbols 6, 7, 8, and 9 of slot 1.
[0456] In subsequent drawings, only the index of the actual iteration is displayed. That is, if it is marked as 0, it is the actual iteration 0.
[0457] In FIG. 34, the terminal performs frequency hopping for every nominal repetition. That is, nominal repetitions of even indices are transmitted from the 0th PRB set of hop 0, and nominal repetitions of odd indices are transmitted from the 1st PRB set of hop 1. For the convenience of explaining the present invention, frequency hopping is performed for every nominal repetition, but the method of the present invention can be applied to other frequency hopping methods.
[0458] The terminal requires G symbols for RF switching during frequency hopping. That is, at least G symbols are required between the transmission in the 0th PRB set of hop 0 and the transmission in the 1st PRB set of hop 1. A method for ensuring G symbols is disclosed. Refer to FIG. 35 for a first embodiment of PUSCH repetition type B of the present invention.
[0459] FIG. 35 is a diagram showing a gap symbol placed in a preceding nominal repetition in a type-B PUSCH repetition according to one embodiment of the present invention.
[0460] Referring to FIG. 35, the terminal may not transmit PUSCH during G symbols immediately before frequency hopping and may use them as a gap. Referring to FIG. 35(a), when G=1, one symbol immediately before frequency hopping may not transmit PUSCH and may use it as a gap for RF switching. Referring to FIG. 35(b), when G=2, two symbols immediately before frequency hopping may not transmit PUSCH and may use them as a gap for RF switching. Frequency hopping occurs between nominal repetition 0 (symbols 8, 9, 10, 11 of slot 0) and nominal repetition 1 (symbols 12, 13 of slot 0 and symbols 0, 1 of slot 1). Therefore, according to an embodiment of the present invention, the last G symbols of nominal repetition 0 immediately before frequency hopping can be determined as symbols that do not transmit PUSCH. Therefore, symbols that do not transmit the above PUSCH may be excluded when determining the actual repetition. (When determining the actual repetition, symbols that do not transmit the above PUSCH are determined to be invalid symbols.)
[0461] Referring to FIG. 35(a), when G=1, Symbol 11 of Slot 0, Symbol 1 of Slot 1, and Symbol 5 of Slot 1 can be determined to be symbols that do not transmit PUSCH. Accordingly, the terminal can group Symbols 8, 9, and 10 of Slot 0 to form Actual Repeat 0, group Symbols 12 and 13 of Slot 0 to form Actual Repeat 1, group Symbols 2, 3, and 4 of Slot 1 to form Actual Repeat 2, and group Symbols 6, 7, 8, and 9 of Slot 1 to form Actual Repeat 3. For reference, Symbol 0 of Slot 1 is a single symbol, so PUSCH is not transmitted. This symbol is called an orphan symbol.
[0462] Referring to FIG. 35(b), when G=2, symbols 10 and 11 of slot 0, symbols 0 and 1 of slot 1, and symbols 4 and 5 of slot 1 can be determined as symbols that do not transmit PUSCH. Accordingly, the terminal can combine symbols 8 and 9 of slot 0 to form actual repetition 0, combine symbols 12 and 13 of slot 0 to form actual repetition 1, combine symbols 2 and 3 of slot 1 to form actual repetition 2, and combine symbols 6, 7, 8, and 9 of slot 1 to form actual repetition 3.
[0463] A second embodiment of the PUSCH repeat type B of the present invention is as shown in FIG. 36.
[0464] FIG. 36 is a diagram showing a gap symbol placed in a trailing nominal repetition in a type-B PUSCH repetition according to one embodiment of the present invention.
[0465] Referring to FIG. 36, the terminal may not transmit PUSCH for G symbols immediately after frequency hopping and may use them as a gap for RF switching. Referring to FIG. 36(a), when G=1, one symbol immediately after frequency hopping may not transmit PUSCH and may use it as a gap for RF switching. Referring to FIG. 36(b), when G=2, two symbols immediately after frequency hopping may not transmit PUSCH and may use them as a gap for RF switching. Frequency hopping occurs between nominal repetition 0 (symbols 8, 9, 10, 11 of slot 0) and nominal repetition 1 (symbols 12, 13 of slot 0 and symbols 0, 1 of slot 1). Therefore, according to an embodiment of the present invention, the first G symbols of nominal repetition 1 immediately after frequency hopping can be determined as symbols that do not transmit PUSCH. Therefore, symbols that do not transmit the above PUSCH may be excluded when determining the actual repetition. (When determining the actual repetition, symbols that do not transmit the above PUSCH are determined to be invalid symbols.)
[0466] Referring to FIG. 36(a), when G=1, Symbol 12 of Slot 0, Symbol 2 of Slot 1, and Symbol 6 of Slot 1 can be determined to be symbols that do not transmit PUSCH. Accordingly, the terminal can group Symbols 8, 9, 10, and 11 of Slot 0 to form Actual Repeat 0, Group Symbols 0 and 1 of Slot 1 to form Actual Repeat 1, Group Symbols 3, 4, and 5 of Slot 1 to form Actual Repeat 2, and Group Symbols 7, 8, and 9 of Slot 1 to form Actual Repeat 3. For reference, Symbol 13 of Slot 0 is Symbol 1, so PUSCH is not transmitted. This symbol is called an orphan symbol.
[0467] Referring to FIG. 36(b), when G=2, symbols 12 and 13 of slot 0, symbols 2 and 3 of slot 1, and symbols 6 and 7 of slot 1 can be determined to be symbols that do not transmit PUSCH. Accordingly, the terminal can group symbols 8, 9, 10, and 11 of slot 0 to form actual repetition 0, group symbols 0 and 1 of slot 1 to form actual repetition 1, group symbols 4 and 5 of slot 1 to form actual repetition 2, and group symbols 8 and 9 of slot 1 to form actual repetition 3.
[0468] The second embodiment has the following advantages compared to the first embodiment. When low latency is required, such as in a URLLC system, it is desirable to transmit PUSCH with many symbols as early as possible (in terms of time). When comparing the number of symbols included in the first actual iteration of the first embodiment and the second embodiment, since the second embodiment does not use symbols as gaps, PUSCH can be transmitted with more symbols. Therefore, the base station has a higher probability of correctly receiving PUSCH at an earlier time.
[0469] However, since the first and second embodiments do not use G symbols for PUSCH transmission in one nominal repetition, the number of symbols between repetitions differs. For example, in FIG. 35(b), actual repetitions 0, 1, and 2 occupy 2 symbols, but actual repetition 3 occupies 4 symbols. Therefore, the reception performance of PUSCH may be degraded due to the difference in the number of symbols between repetitions.
[0470] A third embodiment of the PUSCH repeat type B of the present invention is as shown in FIG. 37.
[0471] FIG. 37 is a diagram showing gap symbols distributed in a type-B PUSCH repetition according to one embodiment of the present invention.
[0472] Referring to FIG. 37, the terminal may not transmit PUSCH in f (G / 2) symbols immediately before frequency hopping, and may not transmit PUSCH in Gf (G / 2) symbols immediately after frequency hopping. f (G / 2) is at least one of floor (G / 2), ceil (G / 2), and round (G / 2). That is, in the third embodiment, the difference in the number of symbols between repetitions can be reduced by not using the same number of symbols for PUSCH transmission in the nominal repetition immediately before and after frequency hopping.
[0473] Referring to FIG. 37, when G=2, symbols 11 and 12 of slot 0, symbols 1 and 2 of slot 1, and symbols 5 and 6 of slot 1 can be determined to be symbols that do not transmit PUSCH. Accordingly, the terminal can group symbols 8, 9, and 10 of slot 0 to form actual repetition 0, group symbols 3 and 4 of slot 1 to form actual repetition 1, and group symbols 7, 8, and 9 of slot 1 to form actual repetition 2. For reference, symbol 13 of slot 0 is a single symbol, so PUSCH is not transmitted. Also, symbol 0 of slot 1 is a single symbol, so PUSCH is not transmitted.
[0474] Referring to FIG. 37, it can be seen that, according to the third embodiment, the number of symbols for each repetition of the terminal is similar. In FIG. 37, actual repetitions 0 and 2 occupy 3 symbols, and actual repetition 1 occupies 2 symbols. However, in FIG. 37, symbol 13 of slot 0 and symbol 0 of slot 1 are orphan symbols for which PUSCH is not transmitted. Therefore, the total number of symbols used for PUSCH is reduced. A method is required to resolve this.
[0475] In a fourth embodiment of the PUSCH repetition type B of the present invention, the terminal can determine G symbols not to transmit PUSCH by comparing the number of symbols in the actual repetition immediately before frequency hopping with the number of symbols in the actual repetition immediately after frequency hopping. Here, some or all symbols in the actual repetition with the larger number can be preferentially determined as symbols not to transmit PUSCH. A specific method is as follows.
[0476] In the first method, the terminal can compare the number of symbols in the actual repetition immediately before frequency hopping with the number of symbols in the actual repetition immediately after frequency hopping, and determine G symbols in the actual repetition with a larger number of symbols as symbols that will not transmit PUSCH. Here, let N1 be the number of symbols in the actual repetition immediately before frequency hopping and N2 be the number of symbols in the actual repetition immediately after frequency hopping, and G symbols can be determined as follows.
[0477] - If N1≥N2, the last G symbols of the actual iteration immediately preceding frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0478] - N1 <N2이면 주파수 호핑 바로 이후 실제 반복의 첫 G개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0479] In a second method, the terminal can compare the number of symbols (N1) of the actual repetition immediately before frequency hopping with the number of symbols (N2) of the actual repetition immediately after frequency hopping, and determine that one symbol in the actual repetition with the larger number of symbols is a symbol that will not transmit PUSCH. If the actual repetition is the actual repetition immediately before frequency hopping, the one symbol is the last symbol of the actual repetition, and if the actual repetition is the actual repetition immediately after frequency hopping, the one symbol is the first symbol of the actual repetition. This operation is repeated until G symbols are obtained. More specifically, they are obtained as follows.
[0480] Let's assume g1=0 and g2=0.
[0481] - g1+g2 <G이면 다음 과정을 반복하여 수행한다. N1-g1≥N2-g2이면 g1=g1+1이다. N1-g1<N2-g2이면 g2=g2+1이다.
[0482] - The last g1 symbols of the actual iteration immediately preceding frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0483] - The first g2 symbols of the actual iteration immediately after frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0484] In another third method, G symbols can be determined as follows.
[0485] - If N1≥N2 and N1-N2≥G, the last G symbols of the actual iteration immediately preceding frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0486] - N1≥N2 and N1-N2 <G이면, 주파수 호핑 바로 이전 실제 반복의 마지막 N1-N2 + f((G-(N1-N2)) / 2 )개 심볼을 PUSCH가 전송되지 않는 심볼로 판정하고, 주파수 호핑 바로 이후 실제 반복의 첫 G-(N1-N2)- f((G-(N1-N2)) / 2 )개 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0487] - N1 <N2이고, N2-N1≥G이면, 주파수 호핑 바로 이후 실제 반복의 첫 G개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0488] - N1 <N2이고 N2-N1<G이면, 주파수 호핑 바로 이전 실제 반복의 마지막 G-(N2-N1)- f((G-(N2-N1)) / 2 )개 심볼을 PUSCH가 전송되지 않는 심볼로 판정하고, 주파수 호핑 바로 이후 실제 반복의 첫 N2-N1+ f((G-(N2-N1)) / 2 )개 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0489] A fourth embodiment of the PUSCH repeat type B of the present invention is as shown in FIG. 38.
[0490] FIG. 38 is a diagram showing gap symbols placed in a large number of nominal repetitions in a type-B PUSCH repetition according to one embodiment of the present invention.
[0491] According to the first method, the terminal determines the symbols for which PUSCH is not transmitted as follows. First, the terminal calculates the actual iterations by assuming G=0 (without considering the gap). The actual iterations calculated here are as shown in FIG. 34(b). The actual iterations calculated here are referred to as intermediate actual iterations for convenience as an intermediate process, and the actual iterations transmitted according to the symbols for which PUSCH is not transmitted are calculated as follows.
[0492] According to Fig. 34(b), there are 5 intermediate actual iterations, with indices 0, 1, 2, 3, and 4. Frequency hopping occurs between intermediate actual iterations 0 and 1, between intermediate actual iterations 2 and 3, and between intermediate actual iterations 3 and 4. First, a gap is determined for the earliest frequency hopping in time. Intermediate actual iteration 0 contains 4 symbols, and intermediate actual iteration 1 contains 2 symbols. Therefore, the last G symbols of intermediate actual iteration 0, which contains more symbols, are determined as symbols for which PUSCH is not transmitted. Next, a gap is determined for the earliest frequency hopping in time. Intermediate actual iteration 2 contains 2 symbols, and intermediate actual iteration 3 contains 4 symbols. Therefore, the first G symbols of intermediate actual iteration 3, which contains more symbols, are determined as symbols for which PUSCH is not transmitted. Finally, a gap for the last-line frequency hopping in time is determined. Intermediate actual iteration 3 contains 3 symbols (when G=1 with reference to FIG. 38(a)) or 2 symbols (when G=2 with reference to FIG. 38(b)), and intermediate actual iteration 4 contains 4 symbols. Therefore, the first G symbols of intermediate actual iteration 4, which contains more symbols, are determined as symbols for which PUSCH is not transmitted. The terminal can determine the actual iteration by excluding the determined symbols for which PUSCH is not transmitted from the intermediate actual iteration.
[0493] According to the fourth embodiment of the PUSCH repetition type B of the present invention, some symbols in an actual repetition with a longer length are determined to be symbols for which PUSCH is not transmitted. Therefore, the overall length of the actual repetition is reduced. Consequently, a single actual repetition cannot have a lower code rate. A method to solve this is required.
[0494] In the fifth embodiment of the PUSCH repetition type B of the present invention, the terminal can determine G symbols not to transmit PUSCH by comparing the number of symbols in the actual repetition immediately before frequency hopping with the number of symbols in the actual repetition immediately after frequency hopping. Here, some or all symbols in the actual repetition with the smaller number can be preferentially determined as symbols not to transmit PUSCH. The specific method is as follows.
[0495] In the first method, the terminal can compare the number of symbols in the actual repetition immediately before frequency hopping with the number of symbols in the actual repetition immediately after frequency hopping, and determine G symbols in the actual repetition with fewer symbols as symbols that will not transmit PUSCH. Here, let N1 be the number of symbols in the actual repetition immediately before frequency hopping and N2 be the number of symbols in the actual repetition immediately after frequency hopping, and G symbols can be determined as follows.
[0496] - If N1≥N2, the first G symbols of the actual iteration immediately following frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0497] - N1 <N2이면 주파수 호핑 바로 이전 실제 반복의 마지막 G개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0498] In a second method, the terminal can compare the number of symbols (N1) of the actual repetition immediately before frequency hopping with the number of symbols (N2) of the actual repetition immediately after frequency hopping, and determine that one symbol in the actual repetition with the smaller number of symbols is a symbol that will not transmit PUSCH. If the actual repetition is the actual repetition immediately before frequency hopping, the one symbol is the last symbol of the actual repetition, and if the actual repetition is the actual repetition immediately after frequency hopping, the one symbol is the first symbol of the actual repetition. This operation is repeated until G symbols are obtained. More specifically, they are obtained as follows.
[0499] Let's assume g1=0 and g2=0.
[0500] - g1+g2 <G이면 다음 과정을 반복하여 수행한다. N1-g1≥N2-g2이면 g2=g2+1이다. N1-g1<N2-g2이면 g1=g1+1이다.
[0501] - The last g1 symbols of the actual iteration immediately preceding frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0502] - The first g2 symbols of the actual iteration immediately after frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0503] In another third method, G symbols can be determined as follows.
[0504] - If N1≥N2 and N2≥G, the first G symbols of the actual iteration immediately following frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0505] - N1≥N2 and N2 <G이면, 주파수 호핑 바로 이후 실제 반복의 모든 N2개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정하고, 주파수 호핑 바로 이전 실제 반복의 마지막 G-N2개 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0506] - N1 <N2이고, N1≥G이면, 주파수 호핑 바로 이전 실제 반복의 마지막 G개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0507] - N1 <N2이고 N1<G이면, 주파수 호핑 바로 이전 실제 반복의 모든 N1개 심볼을 PUSCH가 전송되지 않는 심볼로 판정하고, 주파수 호핑 바로 이후 실제 반복의 첫 G-N1개 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0508] A fifth embodiment of the PUSCH repeat type B of the present invention is as shown in FIG. 39.
[0509] FIG. 39 is a diagram showing gap symbols placed in nominal repetitions with a small number in a type-B PUSCH repetition according to one embodiment of the present invention.
[0510] According to the first method, the terminal determines the symbols for which PUSCH is not transmitted as follows. First, the terminal calculates the actual iterations by assuming G=0 (without considering the gap). The actual iterations calculated here are as shown in FIG. 34(b). The actual iterations calculated here are referred to as intermediate actual iterations for convenience as an intermediate process, and the actual iterations transmitted according to the symbols for which PUSCH is not transmitted are calculated as follows.
[0511] According to Fig. 34(b), there are 5 intermediate actual iterations, with indices 0, 1, 2, 3, and 4. Frequency hopping occurs between intermediate actual iterations 0 and 1, between intermediate actual iterations 2 and 3, and between intermediate actual iterations 3 and 4. First, a gap is determined for the earliest frequency hopping in time. Intermediate actual iteration 0 contains 4 symbols, and intermediate actual iteration 1 contains 2 symbols. Therefore, the first G symbols of intermediate actual iteration 1, which contains fewer symbols, are determined as symbols for which PUSCH is not transmitted. Next, a gap is determined for the earliest frequency hopping in time. Intermediate actual iteration 2 contains 2 symbols, and intermediate actual iteration 3 contains 4 symbols. Therefore, the last G symbols of intermediate actual iteration 2, which contains fewer symbols, are determined as symbols for which no PUSCH is transmitted. Finally, a gap is determined for the frequency hopping that is last in time. Intermediate actual iteration 3 contains 4 symbols, and intermediate actual iteration 4 contains 4 symbols. Therefore, since the number of symbols is the same, the last G symbols of the preceding intermediate actual iteration 3 are determined as symbols for which no PUSCH is transmitted. The terminal can determine the actual iteration by excluding the determined symbols for which no PUSCH is transmitted from the intermediate actual iterations. For reference, when G=1, intermediate actual iterations 1 and 2 each contain one symbol. Therefore, the said one symbol is an orphan symbol for which no PUSCH is transmitted.
[0512] Referring to FIG. 39, it can be seen that the terminal transmits PUSCH with an actual iteration containing more symbols. However, according to FIG. 39(a), if G symbols cannot be used for PUSCH transmission in an intermediate actual iteration containing a small number of symbols, the remaining symbol becomes one, which can become an orphan symbol. Due to this orphan, the total number of symbols used for PUSCH transmission is reduced. A method is needed to resolve this.
[0513] In the sixth embodiment of the PUSCH repetition type B of the present invention, the terminal can determine G symbols for which a PUSCH will not be transmitted by comparing the number of symbols in the actual repetition immediately before frequency hopping with the number of symbols in the actual repetition immediately after frequency hopping. Here, some or all symbols in the actual repetition with the smaller number can be determined as symbols for which a PUSCH will not be transmitted first. However, if the actual repetition has 2 symbols, symbols for which a PUSCH will not be transmitted are not determined in that actual repetition, and symbols for which a PUSCH will not be transmitted are determined in the actual repetition with the larger number. The specific method is as follows.
[0514] In the first method, the terminal can compare the number of symbols in the actual repetition immediately before frequency hopping with the number of symbols in the actual repetition immediately after frequency hopping, and determine G symbols in the actual repetition with fewer symbols as symbols that will not transmit PUSCH. Here, let N1 be the number of symbols in the actual repetition immediately before frequency hopping and N2 be the number of symbols in the actual repetition immediately after frequency hopping, and G symbols can be determined as follows.
[0515] - If N1≥N2 and N2-G≥2, the first G symbols of the actual iteration immediately following frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0516] - If N1≥N2 and N2-G<2, the first N2-2 symbols of the actual iteration immediately following frequency hopping are determined as symbols for which PUSCH is not transmitted. The last G-(N2-2) symbols of the actual iteration immediately preceding frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0517] - N1 <N2이고, N1-G≥2이면 주파수 호핑 바로 이전 실제 반복의 마지막 G개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0518] - N1 <N2이고, N1-G<2이면, 주파수 호핑 바로 이전 실제 반복의 마지막 N1-2개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다. 주파수 호핑 바로 이후 실제 반복의 첫 G-(N1-2)개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0519] In a second method, the terminal can compare the number of symbols (N1) of the actual repetition immediately before frequency hopping with the number of symbols (N2) of the actual repetition immediately after frequency hopping, and determine that one symbol in the actual repetition with the smaller number of symbols is a symbol that will not transmit PUSCH. If the actual repetition is the actual repetition immediately before frequency hopping, the one symbol is the last symbol of the actual repetition, and if the actual repetition is the actual repetition immediately after frequency hopping, the one symbol is the first symbol of the actual repetition. This operation is repeated until G symbols are obtained. More specifically, they are obtained as follows.
[0520] Let's assume g1=0 and g2=0.
[0521] - g1+g2 <G이면 다음 과정을 반복하여 수행한다. N1-g1≥N2-g2≥2이면 g2=g2+1이다. 그렇지 않으면 g1=g1+1이다.
[0522] - The last g1 symbols of the actual iteration immediately preceding frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0523] - The first g2 symbols of the actual iteration immediately after frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0524] In another third method, G symbols can be determined as follows.
[0525] - If N1≥N2 and N2-G≥2, the first G symbols of the actual iteration immediately following frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0526] - If N1≥N2 and N2-G<2, the first N2-2 symbols of the actual iteration immediately following frequency hopping are determined as symbols for which PUSCH is not transmitted, and the last G-(N2-2) symbols of the actual iteration immediately preceding frequency hopping are determined as symbols for which PUSCH is not transmitted.
[0527] - N1 <N2이고, N1-G≥2이면, 주파수 호핑 바로 이전 실제 반복의 마지막 G개의 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0528] - N1 <N2이고 N1-G<2이면, 주파수 호핑 바로 이전 실제 반복의 N1-2개 심볼을 PUSCH가 전송되지 않는 심볼로 판정하고, 주파수 호핑 바로 이후 실제 반복의 첫 G-(N1-2)개 심볼을 PUSCH가 전송되지 않는 심볼로 판정한다.
[0529] The sixth embodiment of the PUSCH repeat type B of the present invention is as shown in FIG. 40.
[0530] FIG. 40 is a diagram showing gap symbols arranged so that no orphan symbols occur in a type-B PUSCH repetition according to one embodiment of the present invention.
[0531] According to the first method, the terminal determines the symbols for which PUSCH is not transmitted as follows. First, the terminal calculates the actual iterations by assuming G=0 (without considering the gap). The actual iterations calculated here are as shown in FIG. 34(b). The actual iterations calculated here are referred to as intermediate actual iterations for convenience as an intermediate process, and the actual iterations transmitted according to the symbols for which PUSCH is not transmitted are calculated as follows.
[0532] According to Fig. 34(b), there are 5 intermediate actual iterations, with indices 0, 1, 2, 3, and 4. Frequency hopping occurs between intermediate actual iterations 0 and 1, between intermediate actual iterations 2 and 3, and between intermediate actual iterations 3 and 4. First, a gap is determined for the frequency hopping that is the earliest in time. Intermediate actual iteration 0 contains 4 symbols, and intermediate actual iteration 1 contains 2 symbols. Therefore, since intermediate actual iteration 1 contains 2 symbols, it cannot contain symbols that are no longer PUSCH transmitted (if it does, an orphan symbol occurs). Therefore, the last G symbols in intermediate actual iteration 0, which contains a larger number, are determined as symbols for which PUSCH is not transmitted. Next, the gap for the earliest frequency hopping in time is determined. Intermediate actual iteration 2 contains 2 symbols, and intermediate actual iteration 3 contains 4 symbols. Since intermediate actual iteration 2, which contains fewer symbols, contains 2 symbols, this intermediate actual iteration can no longer contain symbols for which PUSCH is not transmitted (if it did, an orphan symbol would occur). Therefore, the last G symbols in intermediate actual iteration 3, which contains a larger number, are determined as symbols for which PUSCH is not transmitted. Finally, the gap for the latest frequency hopping in time is determined.Intermediate actual iteration 3 contains 3 symbols (when G=1 in Fig. 40(a)) or 2 symbols (when G=2 in Fig. 40(b)), and intermediate actual iteration 4 contains 4 symbols. If intermediate actual iteration 3 contains 3 symbols (when G=1 in Fig. 40(a)), the last G=1 symbol of intermediate actual iteration 3 is determined as a symbol for which PUSCH is not transmitted. If intermediate actual iteration 3 contains 2 symbols (when G=2 in Fig. 40(b)), the first G=2 symbol of intermediate actual iteration 4 is determined as a symbol for which PUSCH is not transmitted.
[0533] Referring to Fig. 40, it can be confirmed that the actual repetition transmitted by the terminal no longer has any orphan symbols.
[0534] In the first to sixth embodiments of the PUSCH repetition type B of the present invention, some or all symbols in the previously obtained nominal repetition or actual repetition were determined as symbols that are not PUSCH transmitted. However, in this case, the number of symbols actually used by the terminal for PUSCH transmission is reduced. Consequently, the reliability of PUSCH transmission may be reduced. A method for solving this is disclosed.
[0535] According to the seventh embodiment of the PUSCH repetition type B of the present invention, a terminal can determine nominal repetitions by considering G symbols. More specifically, to determine nominal repetitions, the terminal receives instructions or settings from a base station for the starting symbol index (S) of the first nominal repetition, the number of symbols (L) included in the nominal repetition, and the number of nominal repetitions (K). The terminal creates the first nominal repetition by grouping L symbols starting from the starting symbol index (S) of the first nominal repetition. Then, it creates the second nominal repetition by grouping L symbols starting from the next symbol. In this way, K nominal repetitions are generated.
[0536] If a terminal cannot transmit a PUSCH for G symbols during frequency hopping, the terminal can determine nominal repeats as follows. The terminal forms the first nominal repeat by grouping L symbols starting from the starting symbol index (S) of the first nominal repeat. Then, starting from the symbol following the first nominal repeat, it determines G symbols that cannot be transmitted via PUSCH. Then, it forms the second nominal repeat by grouping L symbols starting from the next symbol. Then, starting from the symbol following the first nominal repeat, it determines G symbols that cannot be transmitted via PUSCH. In this way, K nominal repeats are generated.
[0537] FIG. 41 is a diagram showing the addition of a gap symbol after a nominal repetition in a type-B PUSCH repetition according to one embodiment of the present invention.
[0538] Referring to Fig. 41(a), S=8, L=4, K=4, and G=1. The terminal groups symbols 8, 9, 10, and 11 of slot 0 to form the first nominal loop. Then, the next G=1 symbol (symbol 12 of slot 0) is determined to be a symbol for which PUSCH is not transmitted. Next, the terminal groups 13 of slot 0 and symbols 0, 1, and 2 of slot 1 to form the second nominal loop. Then, the next G=1 symbol (symbol 3 of slot 1) is determined to be a symbol for which PUSCH is not transmitted. Then, the terminal groups symbols 4, 5, 6, and 7 of slot 1 to form the third nominal loop. Then, the next G=1 symbol (symbol 8 of slot 1) is determined to be a symbol for which PUSCH is not transmitted. Finally, the terminal groups symbols 9, 10, 11, and 12 of slot 1 to form the fourth nominal loop. The nominal iterations obtained in this way can be divided into actual iterations.
[0539] Referring to Fig. 41(b), S=8, L=4, K=4, and G=2. The terminal groups symbols 8, 9, 10, and 11 of slot 0 to form the first nominal repetition. Then, the next G=2 symbols (symbols 12 and 13 of slot 0) are determined to be symbols for which PUSCH is not transmitted. Then, the terminal groups symbols 0, 1, 2, and 3 of slot 1 to form the second nominal repetition. Then, the next G=2 symbols (symbols 4 and 5 of slot 1) are determined to be symbols for which PUSCH is not transmitted. Then, the terminal groups symbols 6, 7, 8, and 9 of slot 1 to form the third nominal repetition. Then, the next G=2 symbols (symbols 10 and 11 of slot 1) are determined to be symbols for which PUSCH is not transmitted. Finally, the terminal combines symbols 12 and 13 from slot 1 and symbols 0 and 1 from slot 2 to create the fourth nominal iteration. The nominal iterations obtained in this way can be divided into actual iterations.
[0540] The seventh embodiment of the PUSCH repetition type B of the present invention inserts a symbol that is not transmitted via PUSCH between nominal repetitions. However, some symbols in the nominal repetitions may not be transmitted. For example, invalid UL symbols (DL symbols, SSB symbols, CORESET#0 symbols, symbols set to RRC signals) are not transmitted. Additionally, if the number of consecutive symbols in a slot among the symbols of the nominal repetitions is one, said symbol is an orphan symbol and is not transmitted. Therefore, it is not always necessary to insert a symbol that is not transmitted via PUSCH between nominal repetitions. An embodiment for solving this is disclosed below.
[0541] In the eighth embodiment of the PUSCH repetition type B of the present invention, the terminal can determine the nominal repetition and the actual repetition by considering G symbols, invalid UL symbols, and orphan symbols. More specifically, if the terminal cannot transmit a PUSCH for G symbols between frequency hopping, the terminal can determine the first nominal repetition. The terminal creates the first nominal repetition by grouping L symbols starting from the starting symbol index (S) of the first nominal repetition. The terminal obtains the actual repetition from the first nominal repetition. Then, G symbols after the last symbol of the actual repetition are designated as symbols for which a PUSCH cannot be transmitted. Then, the terminal can determine the second nominal repetition by grouping L symbols after the G symbols. The terminal obtains the actual repetition from the second nominal repetition. The terminal designates G symbols after the last symbol of the obtained actual repetition as symbols for which a PUSCH cannot be transmitted. In this way, K nominal repetitions and actual repetitions are created from those K nominal repetitions.
[0542] FIG. 42 is a diagram showing gap symbols considering invalid UL symbols and orphan symbols in a type-B PUSCH iteration according to one embodiment of the present invention.
[0543] Referring to FIG. 42(a), S=8, L=4, K=4, and G=1. The terminal combines symbols 8, 9, 10, and 11 of slot 0 to form the first nominal iteration. The actual iteration is obtained from the first nominal iteration. This actual iteration includes symbols 8, 9, 10, and 11 of slot 0. Next, the G=1 symbol (symbol 12 of slot 0) is determined to be a symbol for which PUSCH is not transmitted. Then, the terminal combines 13 of slot 0 and symbols 0, 1, and 2 of slot 1 to form the second nominal iteration. The actual iteration is obtained from the second nominal iteration. This actual iteration includes symbols 0 and 1 of slot 1. For reference, symbol 13 of slot 0 is excluded from the actual iteration because it is an orphan symbol, and symbol 2 of slot 1 is excluded from the actual iteration because it is an invalid UL symbol. Therefore, the last symbol of the actual iteration is symbol 1 of slot 1. After the above symbol, the G=1 symbol (symbol 2 of slot 1) is determined as a symbol where PUSCH is not transmitted. In this way, K=4 nominal iterations and actual iterations are created from those K=4 nominal iterations.
[0544] Referring to FIG. 42(b), S=8, L=4, K=4, and G=2. The terminal groups symbols 8, 9, 10, and 11 of slot 0 to form the first nominal iteration. The actual iteration is obtained from the first nominal iteration. This actual iteration includes symbols 8, 9, 10, and 11 of slot 0. Next, the G=2 symbols (symbols 12 and 13 of slot 0) are determined to be symbols for which PUSCH is not transmitted. Then, the terminal groups symbols 0, 1, 2, and 3 of slot 1 to form the second nominal iteration. The actual iteration is obtained from the second nominal iteration. This actual iteration includes symbols 0 and 1 of slot 1. For reference, symbol 2 of slot 1 is an invalid UL symbol, so it is excluded from the actual iteration. Also, symbol 3 of slot 1 is an orphan symbol, so it is excluded from the actual iteration. Therefore, the last symbol of the actual iteration is symbol 1 of slot 1. After the above symbol, G=2 symbols (symbols 2 and 3 of slot 1) are determined as symbols for which PUSCH is not transmitted. In this way, K=4 nominal iterations and actual iterations are created from those K=4 nominal iterations.
[0545] The foregoing description of the present invention is for illustrative purposes only, and those skilled in the art will understand that other specific forms can be easily modified without altering the technical spirit or essential features of the present invention. Therefore, the embodiments described above should be understood as illustrative in all respects and not restrictive. For example, each component described as a single unit may be implemented in a distributed manner, and components described as distributed may likewise be implemented in a combined form.
[0546] The scope of the present invention is defined by the claims set forth below rather than by the detailed description above, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts thereof should be interpreted as being included within the scope of the present invention.
Claims
Claim 1 delete Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 delete Claim 6 delete Claim 7 delete Claim 8 delete Claim 9 delete Claim 10 delete Claim 11 delete Claim 12 delete Claim 13 delete Claim 14 delete Claim 15 delete Claim 16 delete Claim 17 delete Claim 18 delete Claim 19 delete Claim 20 delete Claim 21 A RedCap UE (reduced capability user equipment) configured to operate in a 3GPP (3rd generation partnership project)-based wireless communication system, comprising: a communication module; and a processor, wherein the processor receives a SIB1 (system information block 1) containing the following information: - a first RACH (random access channel) configuration for a normal UE, and - RedCap-SIB; and a RedCap UE configured to transmit a RA (random access) preamble over a time-frequency RACH resource, wherein if the RedCap-SIB includes a second RACH configuration, the time-frequency RACH resource is determined using the second RACH configuration, and if the RedCap-SIB does not include a second RACH configuration, the time-frequency RACH resource is determined as one of the time-frequency RACH resources configured using the first RACH configuration for the normal UE. Claim 22 In claim 21, the second RACH configuration comprises a minimum preamble index of RA preambles available for RedCap, and the RA preamble is a RedCap UE selected from the RA preambles available for RedCap determined based on the minimum preamble index. Claim 23 In claim 21, the second RACH configuration comprises a number of RA preambles available for RedCap, and the RA preamble is a RedCap UE selected from the RA preambles available for RedCap determined based on the number of RA preambles. Claim 24 In paragraph 21, the RA preamble is transmitted within an initial UL BWP (uplink bandwidth part) configured for RedCap, and the initial UL BWP is different from the initial UL BWP for a standard UE and is a RedCap UE. Claim 25 In paragraph 21, the above SIB1 further comprises an indicator, and the indicator indicates whether the RedCap UE is allowed to connect to a cell. Claim 26 A method performed by a RedCap UE (reduced capability user equipment) configured to operate in a 3GPP (3rd generation partnership project)-based wireless communication system, comprising the steps of receiving a SIB1 (system information block 1) containing the following information: - a first RACH (random access channel) configuration for a normal UE, and - RedCap-SIB; and transmitting a RA (random access) preamble over a time-frequency RACH resource, wherein if the RedCap-SIB includes a second RACH configuration, the time-frequency RACH resource is determined using the second RACH configuration, and if the RedCap-SIB does not include a second RACH configuration, the time-frequency RACH resource is determined as one of the time-frequency RACH resources configured using the first RACH configuration for the normal UE. Claim 27 In paragraph 26, the second RACH configuration comprises a minimum preamble index of RA preambles available for RedCap, and the RA preamble is selected from the RA preambles available for RedCap determined based on the minimum preamble index. Claim 28 In paragraph 26, the second RACH configuration comprises a number of RA preambles available for RedCap, and the RA preamble is selected from the RA preambles available for RedCap determined based on the number of RA preambles. Claim 29 In paragraph 26, the RA preamble is transmitted within an initial UL BWP (uplink bandwidth part) configured for RedCap, and the initial UL BWP is different from the initial UL BWP for a standard UE. Claim 30 In paragraph 26, the above SIB1 further comprises an indicator, and the indicator indicates whether the RedCap UE is allowed to connect to the cell.
Citation Information
Patent Citations
Method for measuring and reporting signals in a wireless communication system and device therefor
KR1020190017731A
