Method and apparatus for configuring request operation for system information in wireless communication

Abstract

The present embodiments provide a method by which a terminal configures a request operation for system information in wireless communication, the method comprising the steps of: confirming, by a base station, that a system information block is not transmitted after transmission of a synchronization signal block; receiving configuration information including uplink resource information for transmitting a request signal for system information; and transmitting the request signal for the system information on the basis of the configuration information.

Description

Method and device for configuring a request operation for system information in wireless communication

[0001] The present embodiments propose a method and apparatus for configuring a request operation for system information in a wireless access network (“5G”, “NR [New Radio]”) or a next-generation wireless access network (“5G-Advanced”, “6G” or a subsequent 3GPP wireless access network).

[0002] 3GPP continues to conduct research and development on wireless communication technologies. In wireless communication systems, energy efficiency is also a crucial consideration, in addition to latency, reliability, and availability.

[0003] To enable terminal connection, the base station must transmit synchronization signals and certain system information. This operation must be performed regardless of the number of terminals available to the network. Consequently, unnecessary operations must be performed even when there are few available terminals.

[0004] Therefore, a specific design is needed for a method to transmit and receive system information more efficiently.

[0005] Embodiments of the present disclosure may provide a method and apparatus for configuring a request operation for system information in wireless communication.

[0006] In one aspect, the present embodiments may provide a method for configuring a request operation for system information by a terminal in wireless communication, the method including: a step of confirming that a system information block is not transmitted after transmission of a synchronization signal block from a base station; a step of receiving configuration information including uplink resource information for transmitting a request signal for system information; and a step of transmitting a request signal for system information based on the configuration information.

[0007] In another aspect, the present embodiments may provide a method for a base station to configure a request operation for system information in wireless communication, the method including a step of notifying a terminal that a system information block is not transmitted after transmission of a synchronization signal block from the base station, a step of transmitting configuration information including uplink resource information for receiving a request signal for system information, and a step of receiving a request signal for system information based on the configuration information.

[0008] In another aspect, the present embodiments provide a terminal configuring a request operation for system information in wireless communication, including a transmitter, a receiver, and a control unit for controlling operations of the transmitter and the receiver, wherein the control unit confirms that a system information block is not transmitted after transmission of a synchronization signal block from a base station, receives configuration information including uplink resource information for transmitting a request signal for system information, and transmits a request signal for system information based on the configuration information.

[0009] In another aspect, the present embodiments provide a base station that configures a request operation for system information in wireless communication, including a transmitter, a receiver, and a control unit that controls operations of the transmitter and the receiver, wherein the control unit notifies a terminal that a system information block is not transmitted after transmission of a synchronization signal block from the base station, transmits configuration information including uplink resource information for receiving a request signal for system information, and provides a base station that receives a request signal for system information based on the configuration information.

[0010] According to the present embodiments, a method and device for configuring a request operation for system information in wireless communication capable of efficiently transmitting system information can be provided.

[0011] Additionally, the base station can reduce power consumption for operation in environments with few users by not transmitting system information until requested.

[0012] FIG. 1 is a schematic diagram illustrating the structure of an NR wireless communication system to which the present embodiment can be applied.

[0013] FIG. 2 is a drawing for explaining a frame structure in an NR system to which the present embodiment can be applied.

[0014] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0015] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0016] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0017] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0018] Figure 7 is a drawing for explaining CORESET.

[0019] FIG. 8 is a diagram illustrating a procedure for a terminal to configure a request operation for system information in wireless communication according to one embodiment.

[0020] FIG. 9 is a diagram illustrating a procedure for a base station to configure a request operation for system information in wireless communication according to one embodiment.

[0021] Fig. 10 is a drawing showing the configuration of a terminal according to another embodiment.

[0022] Fig. 11 is a drawing showing the configuration of a base station according to another embodiment.

[0023] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to exemplary drawings. When adding reference numerals to components in each drawing, identical components may have the same numerals as much as possible even if they are shown in different drawings. In addition, when describing the present embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the technical idea of ​​the present invention, the detailed description may be omitted. When "includes," "has," "consists of," etc. are used in this specification, other parts may be added unless "only" is used. When a component is expressed in the singular, it may include a case in which the plural is included unless specifically stated otherwise.

[0024] Additionally, terms such as first, second, A, B, (a), (b), etc. may be used to describe components of the present disclosure. These terms are only intended to distinguish the components from other components, and the nature, order, sequence, or number of the components are not limited by the terms.

[0025] In a description of the positional relationship of components, when it is described that two or more components are "connected," "combined," or "connected," it should be understood that the two or more components may be directly "connected," "combined," or "connected," but that the two or more components may also be further "interposed" with another component to be "connected," "combined," or "connected." Here, the other component may be included in one or more of the two or more components that are "connected," "combined," or "connected" to each other.

[0026] In the description of the temporal flow relationship related to components, operation methods, or manufacturing methods, for example, when the temporal or flow relationship is described as “after”, “following”, “next to”, “before”, etc., it may also include cases where it is not continuous, unless “immediately” or “directly” is used.

[0027] Meanwhile, when numerical values ​​or corresponding information (e.g., levels, etc.) for components are mentioned, even without separate explicit description, the numerical values ​​or corresponding information may be interpreted as including an error range that may occur due to various factors (e.g., process factors, internal or external impact, noise, etc.).

[0028] The wireless communication system in this specification refers to a system for providing various communication services such as voice, data packets, etc. using wireless resources, and may include a terminal, a base station, or a core network.

[0029] The embodiments disclosed below can be applied to wireless communication systems using various wireless access technologies. For example, the embodiments can be applied to various wireless access technologies such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), or NOMA (non-orthogonal multiple access). In addition, the wireless access technology may not only refer to a specific access technology, but also to each generation of communication technology established by various communication agreement organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTSterrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink. Thus, the present embodiments can be applied to currently disclosed or commercialized wireless access technologies, as well as wireless access technologies currently under development or to be developed in the future.

[0030] Meanwhile, the term "terminal" in this specification is a comprehensive concept that refers to a device that includes a wireless communication module that performs communication with a base station in a wireless communication system, and should be interpreted as a concept that includes not only UE (User Equipment) in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio), but also MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), and wireless device in GSM. In addition, the terminal may be a user portable device such as a smartphone depending on the usage type, and in a V2X communication system, it may mean a vehicle, a device including a wireless communication module in the vehicle, etc. In addition, in the case of a Machine Type Communication system, it may mean an MTC terminal, M2M terminal, URLLC terminal, etc. that is equipped with a communication module to perform machine type communication.

[0031] The base station or cell in this specification refers to an end that communicates with a terminal in terms of a network, and includes various coverage areas such as Node-B, eNB (evolved Node-B), gNB (gNode-B), LPN (Low Power Node), Sector, Site, various types of antennas, BTS (Base Transceiver System), Access Point, Point (e.g., Transmission Point, Reception Point, Transmission / Reception Point), Relay Node, Mega Cell, Macro Cell, Micro Cell, Pico Cell, Femto Cell, RRH (Remote Radio Head), RU (Radio Unit), and Small Cell. In addition, a cell may mean including a BWP (Bandwidth Part) in the frequency domain. For example, a serving cell may mean an Activation BWP of a terminal.

[0032] Since the various cells listed above have a base station that controls one or more cells, the base station can be interpreted in two meanings. 1) It can be a device itself that provides a mega cell, macro cell, micro cell, pico cell, femto cell, or small cell in relation to a wireless area, or 2) it can indicate the wireless area itself. In 1), all devices that provide a given wireless area are controlled by the same entity or that interact to cooperatively configure the wireless area are all indicated as a base station. Depending on how the wireless area is configured, a point, a transceiver point, a transmission point, a reception point, etc. can be an embodiment of a base station. In 2), the wireless area itself that receives or transmits a signal from the perspective of a user terminal or a neighboring base station can also be indicated as a base station.

[0033] In this specification, a cell may mean a component carrier having coverage of a signal transmitted from a transmission / reception point or a transmission / reception point itself.

[0034] Uplink (UL, or uplink) refers to a method of transmitting and receiving data from a terminal to a base station, and downlink (DL, or downlink) refers to a method of transmitting and receiving data from a base station to a terminal. Downlink may refer to communication or a communication path from multiple transmission / reception points to a terminal, and uplink may refer to communication or a communication path from a terminal to multiple transmission / reception points. In this case, in the downlink, the transmitter may be part of the multiple transmission / reception points, and the receiver may be part of the terminal. In addition, in the uplink, the transmitter may be part of the terminal, and the receiver may be part of the multiple transmission / reception points.

[0035] Uplink and downlink transmit and receive control information through control channels such as PDCCH (Physical Downlink Control CHannel) and PUCCH (Physical Uplink Control CHannel), and transmit and receive data by configuring data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel). Hereinafter, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also expressed in the form of 'transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH'.

[0036] For clarity of explanation, the technical idea of ​​this invention is described below mainly with reference to the 3GPP LTE / LTE-A / NR (New RAT) communication system, but the technical features of this invention are not limited to the communication system.

[0037] After researching 4G (4th-Generation) communication technology, 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of the next-generation wireless access technology of the ITU-R. Specifically, 3GPP develops LTE-A pro, which enhances LTE-Advanced technology to meet the requirements of the ITU-R, and NR, a new communication technology separate from 4G communication technology. Both LTE-A pro and NR refer to 5G communication technology, and in the following, 5G communication technology will be explained with NR as the focus, unless a specific communication technology is specifically mentioned.

[0038] The operating scenario in NR defines various operating scenarios by adding considerations for satellites, automobiles, and new verticals to the existing 4G LTE scenario, and in terms of service, it supports the eMBB (Enhanced Mobile Broadband) scenario, the mMTC (Massive Machine Communication) scenario that has high terminal density but is deployed over a wide area and requires low data rate and asynchronous access, and the URLLC (Ultra Reliability and Low Latency) scenario that requires high responsiveness and reliability and can support high-speed mobility.

[0039] To meet these scenarios, NR introduces a wireless communication system that incorporates new waveform and frame structure technologies, low latency technologies, support for ultra-high frequency bands (mmWave), and forward compatibility technologies. In particular, NR systems offer various technological changes in terms of flexibility to ensure forward compatibility. The key technical features of NR are described below with reference to the drawings.

[0040]

[0041] <NR 시스템 일반>

[0042] Figure 1 is a schematic diagram illustrating the structure of an NR system to which the present embodiment can be applied.

[0043] Referring to Fig. 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and the NG-RAN is composed of gNBs and ng-eNBs that provide user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for UE (User Equipment). gNBs or gNBs and ng-eNBs are interconnected via the Xn interface. gNBs and ng-eNBs are each connected to the 5GC via the NG interface. The 5GC can be configured to include an AMF (Access and Mobility Management Function) that is responsible for the control plane such as terminal access and mobility control functions, and an UPF (User Plane Function) that is responsible for the control function for user data. NR includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).

[0044] gNB refers to a base station that provides NR user plane and control plane protocol termination to terminals, and ng-eNB refers to a base station that provides E-UTRA user plane and control plane protocol termination to terminals. The base station described in this specification should be understood to encompass both gNB and ng-eNB, and may also be used to refer to gNB or ng-eNB separately as needed.

[0045] <NR 웨이브 폼, 뉴머롤러지 및 프레임 구조>

[0046] NR uses the CP-OFDM waveform with a cyclic prefix for downlink transmission, and CP-OFDM or DFT-s-OFDM for uplink transmission. OFDM technology is easily combined with MIMO (Multiple Input Multiple Output) and offers the advantages of high spectral efficiency and low-complexity receivers.

[0047] Meanwhile, in NR, the requirements for data rates, latency, and coverage differ across the three scenarios mentioned above. Therefore, it is necessary to efficiently satisfy these requirements across the frequency bands that comprise any NR system. To this end, technologies have been proposed to efficiently multiplex radio resources based on multiple different numerologies.

[0048] Specifically, the NR transmission numerator is determined based on the sub-carrier spacing and the cyclic prefix (CP), and is changed exponentially with the μ value being an exponent value of 2 based on 15 kHz, as shown in Table 1 below.

[0049] μ서브캐리어 간격Cyclic prefixSupported for dataSupported for synch015NormalYesYes130NormalYesYes260Normal, ExtendedYesNo3120NormalYesYes4240NormalNoYes

[0050] As shown in Table 1 above, the numerology of NR can be divided into five types according to the subcarrier spacing. This is different from the fixed subcarrier spacing of LTE, one of the 4G communication technologies, at 15 kHz. Specifically, the subcarrier spacing used for data transmission in NR is 15, 30, 60, and 120 kHz, and the subcarrier spacing used for synchronization signal transmission is 15, 30, 12, and 240 kHz. In addition, the extended CP is applied only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR is defined as a 10 ms frame consisting of 10 subframes with the same length of 1 ms. One frame can be divided into half frames of 5 ms, and each half frame contains 5 subframes. In the case of a 15 kHz subcarrier spacing, one subframe consists of one slot, and each slot consists of 14 OFDM symbols. FIG. 2 is a diagram for explaining the frame structure in an NR system to which the present embodiment can be applied. Referring to FIG. 2, a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length of the slot in the time domain may vary depending on the subcarrier spacing. For example, in the case of a numerology with a 15 kHz subcarrier spacing, a slot is composed of 1 ms, which is the same length as a subframe. In contrast, in the case of a numerology with a 30 kHz subcarrier spacing, a slot is composed of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, a subframe and a frame are defined with a fixed time length, and a slot is defined by the number of symbols, so the time length may vary depending on the subcarrier spacing.

[0051] Meanwhile, NR defines slots as the basic scheduling unit and also introduces mini-slots (or sub-slots, or non-slot-based scheduling) to reduce transmission delay in the wireless section. Using wider subcarrier spacing reduces transmission delay in the wireless section by shortening the length of each slot inversely. Mini-slots (or sub-slots) are designed to efficiently support URLLC scenarios and allow scheduling in units of 2, 4, or 7 symbols.

[0052] Furthermore, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within a single slot. To reduce HARQ delay, a slot structure was defined that allows HARQ ACK / NACK to be transmitted directly within the transmission slot. This slot structure is referred to as a self-contained structure and will be described in detail.

[0053] NR is designed to support a total of 256 slot formats, of which 62 are used in 3GPP Rel-15. It also supports a common frame structure that configures FDD or TDD frames through various combinations of slots. For example, it supports a slot structure in which all symbols in a slot are set to downlink, a slot structure in which all symbols are set to uplink, and a slot structure in which downlink and uplink symbols are combined. NR also supports data transmission being distributed and scheduled across one or more slots. Therefore, a base station can use a slot format indicator (SFI) to inform a UE whether a slot is a downlink slot, an uplink slot, or a flexible slot. The base station can indicate the slot format by indicating an index of a table configured through UE-specific RRC signaling using the SFI, and can also indicate it dynamically through DCI (Downlink Control Information) or statically or semi-statically through RRC.

[0054] <NR 물리 자원 >

[0055] In relation to physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, and bandwidth parts are considered.

[0056] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be quasi co-located (or quasi co-located) if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on the other antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0057] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0058] Referring to Figure 3, a resource grid may exist for each numeral, as NR supports multiple numerals on the same carrier. Furthermore, resource grids may exist based on antenna ports, subcarrier spacing, and transmission direction.

[0059] A resource block (RB) consists of 12 subcarriers and is defined solely in the frequency domain. Furthermore, a resource element (RE) consists of one OFDM symbol and one subcarrier. Therefore, as shown in Figure 3, the size of a single RB can vary depending on the subcarrier spacing. NR also defines "Point A," which serves as a common reference point for the RB grid, as well as common RBs and virtual RBs.

[0060] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0061] Unlike LTE, where the carrier bandwidth is fixed at 20 MHz, NR sets the maximum carrier bandwidth from 50 MHz to 400 MHz for each subcarrier interval. Therefore, it is not assumed that all terminals will use the entire carrier bandwidth. Accordingly, NR allows terminals to designate bandwidth parts (BWPs) within the carrier bandwidth, as illustrated in Figure 4. Furthermore, bandwidth parts are associated with a single numerology, consist of a subset of consecutive common resource blocks, and can be dynamically activated over time. Each terminal is configured with up to four bandwidth parts for both the uplink and downlink, and data is transmitted and received using the bandwidth parts activated at a given time.

[0062] In the case of a paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of an unpaired spectrum, the downlink and uplink bandwidth parts are set in pairs so that they can share a center frequency to prevent unnecessary frequency re-tuning between downlink and uplink operations.

[0063] <NR 초기 접속>

[0064] In NR, a terminal performs cell search and random access procedures to connect to a base station and perform communication.

[0065] Cell search is a procedure in which a terminal synchronizes to the cell of a corresponding base station, obtains a physical layer cell ID, and obtains system information using the synchronization signal block (SSB) transmitted by the base station.

[0066] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0067] Referring to FIG. 5, SSB is composed of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), each occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

[0068] The terminal receives SSB by monitoring SSB in the time and frequency domain.

[0069] SSB can be transmitted up to 64 times in 5ms. Multiple SSBs are transmitted in different transmission beams within 5ms, and the terminal performs detection assuming that SSBs are transmitted every 20ms based on a specific beam used for transmission. The number of beams that can be used for SSB transmission within 5ms can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted below 3GHz, up to 8 in the frequency band between 3GHz and 6GHz, and up to 64 different beams can be used for SSB transmission in the frequency band above 6GHz.

[0070] SSB contains two symbols in one slot, and the starting symbol and number of repetitions within the slot are determined as follows depending on the subcarrier spacing.

[0071] Meanwhile, unlike SS in conventional LTE, SSB is not transmitted at the center frequency of the carrier bandwidth. This means that SSB can be transmitted even in locations other than the center of the system bandwidth, and when supporting wideband operation, multiple SSBs can be transmitted in the frequency domain. Accordingly, the terminal monitors SSB using the synchronization raster, which is a candidate frequency location for monitoring SSB. The carrier raster, which is the center frequency location information of the channel for initial access, and the synchronization raster are newly defined in NR. The synchronization raster has a wider frequency interval than the carrier raster, which can support the terminal's fast SSB search.

[0072] A UE can obtain the MIB through the PBCH of the SSB. The MIB (Master Information Block) includes the minimum information required for the UE to receive the remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network. In addition, the PBCH may include information on the position of the first DM-RS symbol in the time domain, information for the UE to monitor SIB1 (e.g., SIB1 numerology information, information related to SIB1 CORESET, search space information, PDCCH-related parameter information, etc.), offset information between the common resource block and the SSB (the absolute position of the SSB within the carrier is transmitted through SIB1), etc. Here, the SIB1 numerology information is also applied equally to some messages used in the random access procedure for the UE to access the base station after completing the cell search procedure. For example, the numerology information of SIB1 may be applied to at least one of messages 1 to 4 for the random access procedure.

[0073] The aforementioned RMSI may refer to SIB1 (System Information Block 1), and SIB1 is broadcast periodically (e.g., every 160 ms) in the cell. SIB1 contains information necessary for the UE to perform the initial random access procedure and is periodically transmitted via PDSCH. In order for the UE to receive SIB1, it must receive numerology information used for SIB1 transmission and CORESET (Control Resource Set) information used for SIB1 scheduling via PBCH. The UE checks scheduling information for SIB1 using SI-RNTI in CORESET and acquires SIB1 on PDSCH according to the scheduling information. The remaining SIBs, excluding SIB1, may be transmitted periodically or upon request of the UE.

[0074] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0075] Referring to FIG. 6, once cell search is complete, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted via the PRACH. Specifically, the random access preamble is transmitted to the base station via the PRACH, which consists of consecutive radio resources in a specific slot that is periodically repeated. Generally, when a terminal initially accesses a cell, a contention-based random access procedure is performed, and when performing random access for beam failure recovery (BFR), a non-contention-based random access procedure is performed.

[0076] The UE receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), an UL Grant (uplink radio resource), a temporary C-RNTI (Temporary Cell - Radio Network Temporary Identifier), and a TAC (Time Alignment Command). Since one random access response may include random access response information for one or more UEs, the random access preamble identifier may be included to indicate which UE the included UL Grant, temporary C-RNTI, and TAC are valid for. The random access preamble identifier may be an identifier for the random access preamble received by the base station. The TAC may be included as information for the UE to adjust uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, i.e., an RA-RNTI (Random Access - Radio Network Temporary Identifier).

[0077] Upon receiving a valid random access response, the terminal processes the information contained in the random access response and performs scheduled transmission to the base station. For example, the terminal applies TAC and stores a temporary C-RNTI. Furthermore, using the UL Grant, the terminal transmits data stored in its buffer or newly generated data to the base station. In this case, information that identifies the terminal must be included.

[0078] Finally, the terminal receives a downlink message for contention resolution.

[0079] <NR CORESET>

[0080] The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) with a length of 1 to 3 symbols, and transmits uplink / downlink scheduling information, SFI (Slot format Index), and TPC (Transmit Power Control) information.

[0081] To ensure system flexibility, NR introduced the CORESET concept. CORESET (Control Resource Set) refers to time-frequency resources for downlink control signals. A terminal can decode control channel candidates using one or more search spaces within the CORESET time-frequency resources. A QCL (Quasi CoLocation) assumption is established for each CORESET, which is used to inform the characteristics of analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay assumed by the conventional QCL.

[0082] Figure 7 is a drawing for explaining CORESET.

[0083] Referring to Figure 7, a CORESET can exist in various forms within the carrier bandwidth within a single slot, and in the time domain, a CORESET can consist of up to three OFDM symbols. In addition, a CORESET is defined as a multiple of six resource blocks up to the carrier bandwidth in the frequency domain.

[0084] The first CORESET is indicated via the MIB as part of the initial bandwidth part configuration, allowing the terminal to receive additional configuration and system information from the network. After establishing a connection with the base station, the terminal can receive and configure one or more CORESET information via RRC signaling.

[0085] Wider bandwidth operations

[0086] Existing LTE systems supported scalable bandwidth operation for any LTE Component Carrier (CC). That is, depending on the deployment scenario, any LTE operator could configure a single LTE CC with a bandwidth ranging from a minimum of 1.4 MHz to a maximum of 20 MHz, and a normal LTE terminal supported transmission and reception capabilities of 20 MHz bandwidth for a single LTE CC.

[0087] However, in the case of NR, the design is made to support NR terminals with different transmission and reception bandwidth capabilities through a single wideband NR CC, and accordingly, it is required to configure one or more bandwidth parts (BWP, bandwidth part(s)) consisting of segmented bandwidths for any NR CC, and to support flexible wider bandwidth operation through different bandwidth part configurations and activations for each terminal.

[0088] Specifically, in NR, one or more bandwidth parts can be configured through one serving cell configured from the terminal's perspective, and the terminal is defined to activate one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) in the serving cell to use them for uplink / downlink data transmission and reception. In addition, when multiple serving cells are configured in the terminal, that is, for the terminal to which CA is applied, it is defined to activate one downlink bandwidth part and / or uplink bandwidth part for each serving cell to use the radio resources of the serving cell to use them for uplink / downlink data transmission and reception.

[0089] Specifically, an initial bandwidth part for an initial access procedure of a terminal in an arbitrary serving cell is defined, one or more UE-specific bandwidth part(s) are configured for each terminal through dedicated RRC signaling, and a default bandwidth part for a fallback operation can also be defined for each terminal.

[0090] However, it can be defined that multiple downlink and / or uplink bandwidth parts can be activated and used simultaneously depending on the capability and bandwidth part(s) configuration of the terminal in any serving cell, but in NR rel-15, it is defined that only one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) can be activated and used in any terminal at any time.

[0091] In this specification, the terms frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals or various messages related to NR (New Radio) may be interpreted in the past or present meaning or in various meanings used in the future.

[0092]

[0093] The present disclosure provides a method for a terminal to request transmission of system information from a wireless base station in a 3GPP NR system. In particular, the present disclosure provides a method for a terminal to request transmission of system information in an environment where energy saving functions are implemented and the base station does not transmit system information by default after a synchronization signal block. This will be described in detail below.

[0094] In the past, 3GPP NR transmitted more than ten types of system information in formats such as SIB1 (System Information Block 1) and SIB2. Information after SIB2 can be transmitted upon request from the terminal. However, SIB1, which transmits essential information for connection configuration such as the terminal's transmission and reception bands, SCS, and random access resource space, must always be transmitted in the space specified in the standard after the synchronization signal. Therefore, terminals that fail to receive the information for various reasons cannot perform subsequent procedures for network access. However, SIB1, which must be transmitted with every synchronization signal, requires continuous transmission as long as the synchronization signal is sent even when there are no terminals available to access the network, increasing power consumption. Analysis has shown that, depending on the scenario, power savings of up to 50% or more can be achieved when a base station with low traffic does not send SIB1.

[0095] Accordingly, a specific method for requesting information about cells that are not currently in a connected state is needed.

[0096] The SSB (Synchronization Signal Block) of the conventional NR includes the MIB (Master Information Block) and some additional information in the payload, which is largely composed of frequency location, selection of PSS / SSS (primary synchronization signal / secondary synchronization signal), location and value of DMRS (DeModulation Reference Signal) in PBCH (Physical Broadcast Channel), and contents in PBCH. Among these, the PSS and SSS mainly provide cell ID-related information, and the MIB provides frame number, subcarrier spacing information, bandwidth location information, barring information, and location information of CORESET zero to convey scheduling information of PDSCH on which SIB1 is transmitted for SIB1 transmission in addition to basic information for user cell access. The additional information mainly includes some of the remaining bits of the frame number or remaining bandwidth location information that were not included in the MIB.

[0097] In particular, the information named k_SSB determines the offset value from the start frequency of the current synchronization signal and Point A, which is the reference point of the band, and transmits this value as 5-bit information in FR1 (frequency range 1) and 4-bit information in FR2. At this time, if the value of k_SSB is 24 or more in FR1 and 12 or more in FR2, the terminal determines that SIB1 is not transmitted, and at this time, if k_SSB is a specific value, that is, between 24 and 29 in FR1 and between 12 and 13 in FR2 (frequency range 2), the terminal can inform the alternative SSB frequency location information at which SIB1 can be received through the existing CORESET zero location related information.

[0098] Existing NR systems require that all synchronization signals either include SIB1 configuration information or, if not, support alternative synchronization signals that include SIB1 location information. If the alternative synchronization signal also does not include valid SIB1 configuration information, the UE will not access the cell. Therefore, if SIB1 is not continuously transmitted on at least one band, regardless of the presence of users, the UE cannot establish a connection with the base station.

[0099] The present disclosure provides a method for a base station to provide a space for a terminal to request system information transmission from a wireless base station through synchronization signal information in a 3GPP NR system. In particular, a method is provided for notifying a terminal that an on-demand SIB request is possible, or for notifying a terminal of a space for requesting SIB1 transmission without receiving SIB1.

[0100]

[0101] Below, a method for a terminal to configure a request operation for system information in wireless communication will be described with reference to related drawings.

[0102] FIG. 8 is a diagram illustrating a procedure (800) for a terminal to configure a request operation for system information in wireless communication according to one embodiment.

[0103] Referring to FIG. 8, the terminal can confirm that the system information block is not transmitted after the base station transmits the synchronization signal block (S810).

[0104] Typically, a terminal receives a synchronization signal block (SSB) from a base station to connect to the base station. The synchronization signal block is configured to include a Master Information Block (MIB) and certain additional information. The MIB provides location information of CORESET 0, which is used to convey scheduling information of the PDSCH on which System Information Block 1 (SIB1) among system information blocks is transmitted. The terminal can receive SIB1 and perform connection operations with the base station using the information in SIB1.

[0105] However, if the cell to which the terminal is trying to connect is set to On-Demand SIB1, that is, to transmit SIB1 upon the terminal's request, the terminal cannot receive SIB1 unless it makes a separate request.

[0106] In this case, the terminal can confirm that the system information block is not transmitted by receiving information indicating that the cell is transmitting the system information block upon request (On-Demand SIB1). In this case, the information indicating that the cell is transmitting the SIB1 on-demand may include either information that prevents legacy terminals that do not support the On-Demand SIB1 function from accessing the base station, or information that informs terminals that support the On-Demand SIB1 function whether the base station supports the On-Demand SIB1 function.

[0107] For example, information indicating that a system information block is a cell transmitted upon request may include that a frequency offset for a synchronization signal block is configured to be equal to or greater than a first reference value in frequency range 1 (FR1) and equal to or greater than a second reference value in frequency range 2 (FR2). Specifically, the value of k_SSB, which is a parameter indicating the frequency offset, may be configured to be an invalid value, that is, an integer equal to or greater than 24 in FR1 and equal to or greater than 12 in FR2. For example, if a base station transmits a value of k_SSB as 30 in FR1 or a value of k_SSB as 14 in FR2, the terminal may determine that the value is invalid and determine that the base station requires a SIB1 request. Alternatively, for example, the first reference value may be set to be greater than the second reference value.

[0108] Referring again to FIG. 8, the terminal can receive configuration information including uplink resource information for transmitting a request signal for system information (S820).

[0109] For example, the configuration information may be configured based on the configuration information of a cell to which the terminal has previously accessed. That is, the base station may acquire the configuration information based on the cell configuration information received from the previous cell. The cell configuration information may include information related to the SSB setting value of the On-Demand SIB1 applied cell and information such as the relative uplink resource location and format. In this case, the configuration information may include at least one of the following information: a frequency band used for transmitting a request signal for system information, a frequency-domain location, a time-domain location, a subcarrier spacing, a signal format, and a sequence.

[0110] Specifically, the configuration information may include at least one piece of uplink resource information, such as uplink transmission space band information for which a SIB request can be sent, frequency location information within the uplink transmission space band for which a SIB request can be sent, time location information within the uplink transmission space band for which a SIB request can be sent, or uplink transmission space band subcarrier spacing information for which a SIB request can be sent.

[0111] In addition, the configuration information may further include at least one of the following information: signal format information to be used for a SIB request, such as PRACH format, sequence, PUCCH, MCS, etc.; types of SIBs that can be requested; PDSCH resource allocation information on which SIB will be transmitted upon request; new CORESET information on which SIB scheduling information will be transmitted upon request or whether the current CORESET will be reused; resource allocation information on which ACK / NACK or other feedback will be transmitted when a terminal sends a SIB request; or RNTI to be used when a terminal sends a request.

[0112] Referring again to FIG. 8, the terminal can transmit a request signal for system information based on the configuration information (S830).

[0113] The terminal can configure a request signal for system information based on the received configuration information and transmit the request signal using uplink resources.

[0114] For example, the terminal may configure the format of a request signal for system information as a random access preamble (RA Preamble) or a portion thereof. That is, at least some of the PRACH resources may be used for the SIB1 request. In this case, according to an example, at least one of information regarding which of a plurality of preset sequences is selected, which of a plurality of pre-RACH occasion spaces defined by a cyclic shift value and a transmission resource space, or a combination thereof, may be included.

[0115] When the base station receives a SIB1 request from a terminal, it can transmit SIB1 to the terminal.

[0116] Accordingly, a method and device for configuring a system information request operation in wireless communications capable of efficiently transmitting system information can be provided. Furthermore, by not transmitting system information until a request is made, the base station can reduce power consumption for operation in environments with few users.

[0117] FIG. 9 is a diagram illustrating a procedure (900) for a base station to configure a request operation for system information in wireless communication according to one embodiment. The description given above in FIG. 8 may be omitted to avoid redundant explanation. In this case, the omitted content may be substantially equally applied to the base station, as long as it does not conflict with the technical spirit of the invention.

[0118] Referring to FIG. 9, the base station can notify the terminal that the system information block is not transmitted after the base station transmits the synchronization signal block (S910).

[0119] If the base station is set to transmit SIB1 on-demand, i.e., upon request from a terminal, the base station does not transmit SIB1 unless the terminal makes a separate request.

[0120] In this case, the base station can notify the terminal that the system information block is not being transmitted by transmitting information indicating that the cell is a cell that transmits the system information block upon request (On-Demand SIB1). In this case, the information indicating that the cell is a cell that transmits the SIB1 on-demand may include either information that prevents legacy terminals that do not support the On-Demand SIB1 function from accessing the base station, or information that informs terminals that support the On-Demand SIB1 function whether the base station supports the On-Demand SIB1 function.

[0121] For example, information indicating that a system information block is a cell transmitted upon request may include that a frequency offset for a synchronization signal block is configured to be equal to or greater than a first reference value in frequency range 1 (FR1) and equal to or greater than a second reference value in frequency range 2 (FR2). Specifically, the value of k_SSB, which is a parameter indicating the frequency offset, may be configured to be an invalid value, that is, an integer equal to or greater than 24 in FR1 and equal to or greater than 12 in FR2. For example, if a base station transmits a value of k_SSB as 30 in FR1 or a value of k_SSB as 14 in FR2, the terminal may determine that the value is invalid and determine that the base station requires a SIB1 request. Alternatively, for example, the first reference value may be set to be greater than the second reference value.

[0122] Referring again to FIG. 9, the base station may transmit configuration information including uplink resource information for receiving a request signal for system information (S920).

[0123] For example, the configuration information may be configured based on the configuration information of a cell to which the terminal has previously accessed. That is, the base station may acquire the configuration information based on the cell configuration information received from the previous cell. The cell configuration information may include information related to the SSB setting value of the On-Demand SIB1 applied cell and information such as the relative uplink resource location and format. In this case, the configuration information may include at least one of the following information: a frequency band used for transmitting a request signal for system information, a frequency-domain location, a time-domain location, a subcarrier spacing, a signal format, and a sequence.

[0124] Specifically, the configuration information may include at least one piece of uplink resource information, such as uplink transmission space band information for which a SIB request can be sent, frequency location information within the uplink transmission space band for which a SIB request can be sent, time location information within the uplink transmission space band for which a SIB request can be sent, or uplink transmission space band subcarrier spacing information for which a SIB request can be sent.

[0125] In addition, the configuration information may further include at least one of the following information: signal format information to be used for a SIB request, such as PRACH format, sequence, PUCCH, MCS, etc.; types of SIBs that can be requested; PDSCH resource allocation information on which SIB will be transmitted upon request; new CORESET information on which SIB scheduling information will be transmitted upon request or whether the current CORESET will be reused; resource allocation information on which ACK / NACK or other feedback will be transmitted when a terminal sends a SIB request; or RNTI to be used when a terminal sends a request.

[0126] Referring again to FIG. 9, the base station can receive a request signal for system information based on the configuration information (S930).

[0127] The base station can receive a request signal for system information configured based on configuration information from a terminal using uplink resource information included in the configuration information.

[0128] For example, the terminal may configure the format of a request signal for system information as a random access preamble (RA Preamble) or a portion thereof. That is, at least some of the PRACH resources may be used for the SIB1 request. In this case, according to an example, at least one of information regarding which of a plurality of preset sequences is selected, which of a plurality of pre-RACH occasion spaces defined by a cyclic shift value and a transmission resource space, or a combination thereof, may be included.

[0129] When the base station receives a SIB1 request from a terminal, it can transmit SIB1 to the terminal.

[0130] Accordingly, a method and device for configuring a system information request operation in wireless communications capable of efficiently transmitting system information can be provided. Furthermore, by not transmitting system information until a request is made, the base station can reduce power consumption for operation in environments with few users.

[0131]

[0132] Below, with reference to the relevant drawings, each embodiment related to a method for configuring a request operation for system information in wireless communication will be specifically described.

[0133] The present disclosure provides a method for notifying a cell that is sending SIB1 on-demand, and a method for notifying a space for sending a request signal to a terminal.

[0134]

[0135] Example 1. How to notify that a cell is sending SIB1 on-demand.

[0136] The method can be divided into a method of preventing legacy terminals that do not support the SIB1 request function from accessing the base station, and a method of notifying terminals that support the SIB1 request function whether the base station supports the SIB1 request function.

[0137] ① How to block access to legacy terminals

[0138] Base stations that do not send SIB1 need to instruct barring, that is, block access to cells, during the synchronization process to prevent legacy terminals that do not support the function from malfunctioning. This can be instructed by setting cellBarred in the MIB to Enabled. Alternatively, a method can be used in which the value of k_SSB, which indicates the frequency offset, is invalid, that is, a value greater than or equal to 24 for FR1 and greater than or equal to 12 for FR2. Alternatively, even if k_SSB is valid, a method can be used in which the values ​​of controlResourceSetZero and searchSpzceZero, which are location-related parameters of CORESET zero indicated in table format, are pointed to as reserved areas not provided in the existing table. Alternatively, a combination of two or more of the above methods can be used.

[0139] ② How to tell whether the base station supports the SIB1 request function

[0140] A UE supporting On-Demand SIB1 can use a specific combination of information that a base station can transmit via SSB to recognize that the corresponding indication is a base station requiring a SIB1 request. For greater efficiency, this can be a combination that existing UEs recognize as Barring. For example, if k_SSB is transmitted as a specific value or one of the values, or additionally cellBarred is set to Enabled, or if k_SSB is a specific value or one of the values ​​and controlResourceSetZero and searchSpzceZero have a specific value or one of the values, the UE can determine that this is a base station requiring a SIB1 request. The specific value referred to here can be a constant, or a value determined depending on the cell ID, k_SSB, system frame number, or other values ​​transmitted via SSB. In determining the combination, factors that are not involved in the existing user's Barring, such as the GSCN (Global Synchronization Channel Number) value, cell ID, frame number, SSB index, and SSB placement pattern, may be additionally or independently involved.

[0141] - Example 1: In FR1, the base station can transmit k_SSB as 30 to let the terminal know that it is the base station that needs to request SIB1.

[0142] - Example 2: In FR1, if the SCS of SS / PBCH is 15 kHz and the SCS of PDCCH is 15 kHz, the base station can transmit the value of controlResourceSetZero as 15 to let the terminal recognize that it is a base station that requires a SIB1 request.

[0143] - Example 3: The base station can use a specific value for the GSCN value of SSB and set cellBarred to Enabled to make the terminal recognize that it is a base station that requires a SIB1 request.

[0144]

[0145] Example 2. Method for notifying a space to send a request signal to a terminal

[0146] This method can be divided into a method in which the terminal needs to recognize whether the base station transmitting the SSB through Example 1 is a base station requiring a SIB1 request, and a method in which the terminal does not necessarily need to recognize it.

[0147] ① A method that requires recognizing whether a base station requires a SIB1 request

[0148] If the terminal knows that the base station is receiving a SIB1 request through the embodiment 1 or other means, the terminal can transmit a SIB1 request signal through a space indicated by the k_SSB value, the controlResourceSetZero value, and the searchSpzceZero value. For example, the location of the uplink resource can be specified through the controlResourceSetZero value, and the format of the signal can be specified through the searchSpzceZero value. The location of the uplink resource can be the same space indicated for the existing CORESET zero, or can be expressed in a separate table.

[0149] Another approach is to specify the relative location of the SSBs in a standardized manner. For example, a specific SSB can always be transmitted in the uplink slot ahead, and the location of the SIB1 request transmission resource within that slot can be specified. Whether this method is used can be determined based on bandwidth conditions, and when not used, a method that eliminates the need to recognize whether a base station requires a SIB1 request can be applied instead.

[0150] - Example 1: Band or slot information can be transmitted via controlResourceSetZero and / or searchSpzceZero. For example, if the space where SSB exists is a TDD (Time Division Duplex) band, slot offset information can be included, and if it is an FDD (Frequency Division Duplex) band, band information can be included, and the two can be transmitted in the form of a multiplexing. The information can be organized in the form of a table, or expressed in the form of a band number or a band index within a pair band.

[0151] - Example 2: For FDD bands, or when the GSCN falls within a set of specific values / specific ranges, the method may not be used, but instead a method may be used that does not require the base station to recognize whether a SIB1 request is required.

[0152] ② A method that does not require recognition of whether a base station requires a SIB1 request

[0153] The method is applicable to both the base station that recognizes or does not recognize whether a SIB1 request is required through the method provided in Embodiment 1 or other means. For this purpose, the base station can additionally define a new DCI that can be sent through the CORESET zero transmission space indicated by the ControlResourceSetZero value and the searchSpzceZero value. This can be newly defined, for example, in DCI format 2-x, and can be scrambled with an SI-RNTI or other predefined constants, or an RNTI that can be derived from information obtainable from SSB, such as a cell ID. The DCI can include one or more of the following information:

[0154] - Uplink transmission space bandwidth information for which the terminal can send a SIB request

[0155] - Frequency location information within the uplink transmission space band where the terminal can send a SIB request

[0156] - Time location information within the uplink transmission space band where the terminal can send a SIB request.

[0157] - Uplink transmission space band subcarrier spacing information in which the terminal can send a SIB request

[0158] - Signal format to be used by the terminal for SIB request - PRACH (Physical Random Access Channel) format, sequence to be used, PUCCH (Physical uplink control channel) type, MCS (Modulation Coding Scheme), etc.

[0159] - Types of SIBs that can be requested by the terminal

[0160] - PDSCH resource allocation information to which SIB will be transmitted upon request from the terminal

[0161] - New CORESET information to be transmitted when the terminal requests SIB scheduling information or whether to reuse the current CORESET

[0162] - Resource allocation information to be transmitted as ACK / NACK or other feedback when the terminal sends a SIB request

[0163] - RNTI to be used by the terminal when transmitting a request

[0164] Alternatively, the base station can obtain one or more of the above information related to the transmission space based on cell configuration information received from a previous cell. The cell configuration information may include information related to the SSB settings of the On-Demand SIB1-applied cell, as well as information such as the relative uplink resource location and format.

[0165] This method does not require the terminal to be aware of whether the base station requires a SIB1 request, but can be applied even when the terminal is aware of it.

[0166]

[0167] Additionally, the present disclosure provides a method for a terminal to request transmission of system information from a wireless base station in a 3GPP NR system and a method for the base station to transmit SIB1 upon request. In particular, the present disclosure provides a format of a request message and a method for setting up SIB1 transmission according to the request.

[0168] Accordingly, the present disclosure provides a method for configuring a SIB1 request signal and a method for transmitting SIB1 by a base station according to a SIB1 request.

[0169]

[0170] Example 3. Method for configuring a SIB1 request signal

[0171] The method provides the signal format and content to be transmitted through the resource by the UE that received the uplink resource information sending the SIB request.

[0172] ① Format of SIB1 request signal

[0173] First, the signal format may be a Random Access (RA) preamble or a part of it. Alternatively, the signal format may be in the form of a Sounding Reference Signal (SR). Alternatively, the signal format may be a newly defined Uplink Control Information (UCI). Alternatively, the signal format may reuse existing UCI, such as a Scheduling Request (SR). Alternatively, the request signal may be transmitted on a PUSCH by selecting an MCS designated or preset by the base station, for example, an MCS with index 0. In this case, the RNTI (Radio Network Temporary Identifier) ​​may be the SI-RNTI or another predefined constant RNTI. Alternatively, the RNTI notified in advance by the base station may be used, or an RNTI calculated based on information transmitted by the SSB or information included in the SIB1 resource configuration information may be used.

[0174] If the payload of the terminal is 1 or more, the payload can be expressed by selecting one of the preset multiple sequences in the case of PRACH, and selecting one of the multiple pre-RACH occasion spaces defined by the cyclic shift value and transmission resource space for it, or a combination thereof. Similarly, in the case of SRS, the payload can be expressed by selecting one of the preset multiple sequences, and selecting the cyclic shift value and transmission resource space for it, or a combination thereof. In the case of PUCCH, the method of configuring the payload and the method of encoding it in the existing PUCCH format 0, 1, 2, 3, etc. can be applied, and in particular, if information related to the payload size is indicated in the request signal scheduling process of the base station, the PUCCH format can be determined accordingly.

[0175] ② How to configure SIB1 request signal payload

[0176] If the content payload size of the request signal transmitted by the terminal is 0 or there is no field related to whether or not an SIB is requested within the payload, the base station performs SIB1 transmission when detecting the request signal. Or, if it is 1 or more, the request signal may include one or more of the following information.

[0177] - Whether to request SIB1 transmission

[0178] - Whether to request ACK (Acknowledgement) for SIB1 transmission request

[0179] - Preferred band information

[0180] - Preferred time offset (minimum or maximum interval between request signal and SIB1 signal)

[0181] - Information related to the time or number of times the base station requests to maintain SIB1 transmission.

[0182] - Priority

[0183] - Some information related to terminal capabilities: terminal category, available bandwidth, HD (Half-Duplex)-FDD, etc.

[0184] - CRC (Cyclic Redundancy Check) (using SI-RNTI or new constant RNTI or RNTI indicated to the base station)

[0185]

[0186] Example 4. Subsequent operation method of a base station upon SIB1 request

[0187] This method is a follow-up operation method when the base station receives the request signal transmitted by Example 3. It can be broadly divided into a method of sending an ACK for the request, a method of resending an SSB containing SIB1 configuration information, and a method of sending only SIB1 without an SSB.

[0188] ① How to send an ACK for a request

[0189] The base station can send a preset ACK to the terminal to support rapid feedback on whether the base station will transmit SIB1. This can be done by sending a special SSB of a preset format or by sending a DCI of a preset format in CORESET zero. Alternatively, scheduling information for the ACK can be notified in advance by the base station. The transmission of the ACK can always be performed when a SIB1 is requested, or can be performed upon the terminal's request. In addition to the ACK, a NACK (Negative Acknowledgement) indicating that SIB1 will not be transmitted can also be transmitted. If the ACK payload is 1 or more, it can include one or more of the following:

[0190] - Whether ACK / NACK

[0191] - Information related to the CORESET space where SIB1 scheduling DCI will be transmitted

[0192] - Information about the time when SIB1 scheduling DCI will be transmitted

[0193] - Information related to SSB transmission time including SIB1 configuration information

[0194] - SSB band-related information including SIB1 configuration information

[0195] - Uplink resource information for alternative SIB1 requests

[0196] Depending on the ACK message, the terminal may not access the cell, receive SIB1 information at the location notified by the base station, or retransmit the SIB1 transmission request message in the same or an improved form than the first one.

[0197] ② How to resend SSB

[0198] The base station can perform legacy operation including SIB1 for the next SSB in response to a request from a terminal. Here, the next SSB may mean the earliest SSB after receiving a request within the same band. Alternatively, it may be the SSB at the same position (index) in the next cycle (20 ms). In other words, this means that the first SSB referenced by the terminal and the SSB containing SIB1 configuration information are transmitted with a 20 ms difference. Alternatively, it may be the first SSB at the same position (index) after the terminal request signal or the ACK signal for the request. This may apply, for example, when the time gap between the first SSB and the end of transmission of the terminal request signal is 20 ms or more. Alternatively, the SIB1 scheduling information may be included in an SSB that is not the first, is defined in the standard, or is later than the time requested by the terminal. The minimum or maximum required time gap between the terminal request signal and the SSB containing SIB1 configuration information may be defined in the standard, notified by the base station, or requested by the terminal.

[0199] An SSB performing SIB1 legacy operation may be transmitted in a different band from the SSB initially received by the UE. In this case, the alternative SSB frequency location communicated through controlResourceSetZero and searchSpzceZero can become the SSB band performing legacy operation, i.e., when k_SSB is a specific value, i.e., between 24 and 29 for FR1 and between 12 and 13 for FR2, in the way that other bands were previously indicated. Alternatively, the SSB performing SIB1 legacy operation may be one of the previously unused SSB indices. For example, a base station that previously sent SSBs only in the first index to save power may send an SSB containing SIB1 indication information in the second index. These index offset values ​​may be predefined or notified by the base station. In addition, a QCL (Quasi Co-Location) relationship may be maintained between the SSB initially recognized by the UE and the SSB containing SIB1 information in the request response.

[0200] ③ How to not resend SSB

[0201] Alternatively, a DCI can be issued to schedule SIB1 in CORESET zero defined in the existing SSB upon request. This DCI can use the same format as the DCI for scheduling existing SIB1 transmissions and can be transmitted at a defined time, after a time, or within a time, which can be defined in physical units or in slots, and its value can be defined in the standard, notified by the base station, or requested by the terminal.

[0202] This SIB1 transmission may occur only once per request, or may occur for a predetermined time period as defined by the standard. For example, all SSBs in the frame following the request may contain SIB1 information. Alternatively, it may occur periodically under the same conditions, as defined by the standard, as previously notified by the base station, or as requested by the terminal.

[0203] Example 1: When a terminal transmits its priority information in a request, the base station can transmit SIB1 a number of times equal to the number of times the base station transmits SIB1 within a time determined by a value dependent on the priority from the terminal's request.

[0204] Each of the embodiments provided in this disclosure may be applied independently or may be combined and operated in any form. Furthermore, the terminology used in this disclosure is intended to be easily understood when referring to new terms. In practice, the technical concepts of this disclosure may be equally applicable even when other terms with the same meaning are used.

[0205]

[0206] Hereinafter, the configuration of a terminal and a base station capable of performing some or all of the embodiments described with reference to FIGS. 1 through 9 will be described with reference to the drawings. The above description may be omitted to avoid redundant description, and in this case, the omitted content may be substantially equally applied to the description below, as long as it does not conflict with the technical spirit of the invention.

[0207] Fig. 10 is a drawing showing the configuration of a terminal (1000) according to another embodiment.

[0208] Referring to FIG. 10, a terminal (1000) according to another embodiment includes a transmitter (1020), a receiver (1030), and a control unit (1010) that controls the operations of the transmitter and receiver.

[0209] The control unit (1010) controls the overall operation of the terminal (1000) according to the method of configuring a request operation for system information in wireless communication required to perform the present invention described above.

[0210] The control unit (1010) can confirm that the system information block is not transmitted after the synchronization signal block is transmitted from the base station.

[0211] If the cell that the control unit (1010) wants to connect is set to transmit On-Demand SIB1, i.e., SIB1 upon request of the terminal, SIB1 cannot be received unless the control unit (1010) makes a separate request.

[0212] In this case, the control unit (1010) can receive information indicating that the cell is transmitting the system information block upon request (On-Demand SIB1), and can confirm that the system information block is not transmitted. In this case, the information indicating that the cell is transmitting the SIB1 on-demand may include either information that prevents a legacy terminal that does not support the On-Demand SIB1 function from accessing the base station, or information that informs a terminal that supports the On-Demand SIB1 function whether the base station supports the On-Demand SIB1 function.

[0213] For example, information indicating that a system information block is a cell transmitted upon request may include that a frequency offset for a synchronization signal block is configured to be equal to or greater than a first reference value in frequency range 1 (FR1) and equal to or greater than a second reference value in frequency range 2 (FR2). Specifically, the value of k_SSB, which is a parameter indicating the frequency offset, may be configured to be an invalid value, that is, an integer equal to or greater than 24 in the case of FR1 and equal to or greater than 12 in the case of FR2. For example, if a base station transmits a value of k_SSB as 30 in FR1 or a value of k_SSB as 14 in FR2, the control unit (1010) may determine that the value is invalid and determine that the base station requires a SIB1 request. Alternatively, for example, the first reference value may be set to be greater than the second reference value.

[0214] The control unit (1010) may receive configuration information including uplink resource information for transmitting a request signal for system information. For example, the configuration information may be configured based on configuration information of a cell to which the terminal has previously accessed. That is, the base station may obtain configuration information based on cell configuration information received from a previous cell. The cell configuration information may include information related to SSB setting values ​​of a cell to which On-Demand SIB1 is applied, and information such as relative uplink resource locations and formats. In this case, the configuration information may include at least one of information on a frequency band, frequency-domain location, time-domain location, subcarrier spacing, signal format, and sequence used for transmitting a request signal for system information.

[0215] Specifically, the configuration information may include at least one piece of uplink resource information, such as uplink transmission space band information for which a SIB request can be sent, frequency location information within the uplink transmission space band for which a SIB request can be sent, time location information within the uplink transmission space band for which a SIB request can be sent, or uplink transmission space band subcarrier spacing information for which a SIB request can be sent.

[0216] In addition, the configuration information may further include at least one of the following information: signal format information to be used for a SIB request, such as PRACH format, sequence, PUCCH, MCS, etc.; types of SIBs that can be requested; PDSCH resource allocation information on which SIB will be transmitted upon request; new CORESET information on which SIB scheduling information will be transmitted upon request or whether the current CORESET will be reused; resource allocation information on which ACK / NACK or other feedback will be transmitted when a terminal sends a SIB request; or RNTI to be used when a terminal sends a request.

[0217] The control unit (1010) can transmit a request signal for system information based on configuration information. The control unit (1010) can configure a request signal for system information based on the received configuration information and transmit the request signal using uplink resources.

[0218] For example, the control unit (1010) may configure the format of the request signal for system information as a random access preamble (RA Preamble) or a portion thereof. That is, at least some of the PRACH resources may be utilized for the SIB1 request. In this case, for example, at least one of information regarding which of a plurality of preset sequences is selected, which of a plurality of pre-RACH occasion spaces defined by a cyclic shift value and a transmission resource space, or a combination thereof, may be included.

[0219] When the base station receives a SIB1 request from a terminal, it can transmit SIB1 to the terminal.

[0220] Accordingly, a method and device for configuring a system information request operation in wireless communications capable of efficiently transmitting system information can be provided. Furthermore, by not transmitting system information until a request is made, the base station can reduce power consumption for operation in environments with few users.

[0221] Fig. 11 is a drawing showing the configuration of a base station (1100) according to another embodiment.

[0222] Referring to FIG. 11, a base station (1100) according to another embodiment includes a transmitter (1120), a receiver (1130), and a control unit (1110) that controls the operations of the transmitter and receiver.

[0223] The control unit (1110) can notify the terminal that the system information block is not transmitted after the base station transmits the synchronization signal block. If the base station is configured to transmit On-Demand SIB1, i.e., SIB1 upon the terminal's request, the control unit (1110) does not transmit SIB1 unless the terminal makes a separate request.

[0224] In this case, the control unit (1110) can transmit information indicating that the cell transmits the system information block upon request (On-Demand SIB1) to inform the terminal that the system information block is not transmitted. In this case, the information indicating that the cell transmits the SIB1 on-demand may include either information that prevents a legacy terminal that does not support the On-Demand SIB1 function from accessing the base station or information that informs a terminal that supports the On-Demand SIB1 function whether the base station supports the On-Demand SIB1 function.

[0225] For example, information indicating that a system information block is a cell transmitted upon request may include that a frequency offset for a synchronization signal block is configured to be equal to or greater than a first reference value in frequency range 1 (FR1) and equal to or greater than a second reference value in frequency range 2 (FR2). Specifically, the value of k_SSB, which is a parameter indicating the frequency offset, may be configured to be an invalid value, that is, an integer equal to or greater than 24 in FR1 and equal to or greater than 12 in FR2. For example, if a base station transmits a value of k_SSB as 30 in FR1 or a value of k_SSB as 14 in FR2, the terminal may determine that the value is invalid and determine that the base station requires a SIB1 request. Alternatively, for example, the first reference value may be set to be greater than the second reference value.

[0226] The control unit (1110) may transmit configuration information including uplink resource information for receiving a request signal for system information. For example, the configuration information may be configured based on configuration information of a cell to which the terminal has previously accessed. That is, the control unit (1110) may acquire configuration information based on cell configuration information received from a previous cell. The cell configuration information may include information related to SSB setting values ​​of a cell to which On-Demand SIB1 is applied, and information such as relative uplink resource locations and formats. In this case, the configuration information may include at least one of information on a frequency band, frequency-domain location, time-domain location, subcarrier spacing, signal format, and sequence used for transmitting a request signal for system information.

[0227] Specifically, the configuration information may include at least one piece of uplink resource information, such as uplink transmission space band information for which a SIB request can be sent, frequency location information within the uplink transmission space band for which a SIB request can be sent, time location information within the uplink transmission space band for which a SIB request can be sent, or uplink transmission space band subcarrier spacing information for which a SIB request can be sent.

[0228] In addition, the configuration information may further include at least one of the following information: signal format information to be used for a SIB request, such as PRACH format, sequence, PUCCH, MCS, etc.; types of SIBs that can be requested; PDSCH resource allocation information on which SIB will be transmitted upon request; new CORESET information on which SIB scheduling information will be transmitted upon request or whether the current CORESET will be reused; resource allocation information on which ACK / NACK or other feedback will be transmitted when a terminal sends a SIB request; or RNTI to be used when a terminal sends a request.

[0229] The control unit (1110) can receive a request signal for system information based on configuration information. The control unit (1110) can receive a request signal for system information configured based on the configuration information from a terminal using uplink resource information included in the configuration information.

[0230] For example, the terminal may configure the format of a request signal for system information as a random access preamble (RA Preamble) or a portion thereof. That is, at least some of the PRACH resources may be used for the SIB1 request. In this case, according to an example, at least one of information regarding which of a plurality of preset sequences is selected, which of a plurality of pre-RACH occasion spaces defined by a cyclic shift value and a transmission resource space, or a combination thereof, may be included.

[0231] When the control unit (1110) receives a SIB1 request from a terminal, it can transmit SIB1 to the terminal.

[0232] Accordingly, a method and device for configuring a system information request operation in wireless communications capable of efficiently transmitting system information can be provided. Furthermore, by not transmitting system information until a request is made, the base station can reduce power consumption for operation in environments with few users.

[0233] The above-described embodiments may be supported by standard documents disclosed in at least one of the wireless access systems, IEEE 802, 3GPP, and 3GPP2. That is, steps, components, and parts not described in the present embodiments to clearly illustrate the technical concepts herein may be supported by the above-described standard documents. Furthermore, all terms disclosed in this specification may be explained by the above-described standard documents.

[0234] The embodiments described above may be implemented through various means. For example, the embodiments may be implemented through hardware, firmware, software, or a combination thereof.

[0235] In the case of hardware implementation, the method according to the present embodiments may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), processors, controllers, microcontrollers, or microprocessors.

[0236] When implemented using firmware or software, the methods according to the present embodiments may be implemented in the form of devices, procedures, or functions that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor using various known means.

[0237] Additionally, terms such as "system," "processor," "controller," "component," "module," "interface," "model," or "unit" as described above may generally refer to a computer-related entity, such as hardware, a combination of hardware and software, software, or software in execution. For example, the aforementioned components may be, but are not limited to, a process driven by a processor, a processor, a controller, a control processor, an object, a thread of execution, a program, and / or a computer. For example, both an application running on a controller or a processor and the controller or the processor may be components. One or more components may be within a process and / or thread of execution, and the components may be located on a single device (e.g., a system, a computing device, etc.) or distributed across two or more devices.

[0238] The above description is merely an illustrative example of the technical idea of ​​the present disclosure, and those skilled in the art to which the present disclosure pertains will appreciate that various modifications and variations can be made without departing from the essential characteristics of the technical idea of ​​the present disclosure. In addition, the present embodiments are not intended to limit the technical idea of ​​the present disclosure but rather to explain it, and therefore the scope of the technical idea of ​​the present disclosure is not limited by these embodiments. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included within the scope of the rights of the present disclosure.

[0239]

[0240] CROSS-REFERENCE TO RELATED APPLICATION

[0241] This patent application claims priority under 35 USC §119(a) to Korean Patent Application No. 10-2024-0016172, filed in Korea on February 2, 2024, and Korean Patent Application No. 10-2025-0011317, filed in Korea on January 24, 2025, the entire contents of which are incorporated herein by reference. In addition, this patent application claims priority in countries other than the United States for the same reasons, the entire contents of which are incorporated herein by reference.

Claims

1. In a method for configuring a request operation for system information by a terminal in wireless communication, A step of verifying that a system information block is not transmitted after transmission of a synchronization signal block from a base station; A step of receiving configuration information including uplink resource information for transmitting a request signal for the above system information; and A method comprising the step of transmitting a request signal for the system information based on the configuration information.

2. In paragraph 1, The step of verifying that the above system information block is not transmitted is: A method of receiving information indicating that the above system information block is a cell transmitted upon request.

3. In paragraph 2, Information indicating that the above system information block is a cell transmitted upon request, The frequency offset for the above synchronization signal block is configured to be greater than or equal to a first reference value in frequency range 1 (FR1) and greater than or equal to a second reference value in frequency range 2 (FR2). A method wherein the first reference value is set to 24 or more, and the second reference value is set to 12 or more.

4. In paragraph 1, The above configuration information is, A method comprising at least one piece of information from among a frequency band, a frequency domain location, a time domain location, a subcarrier spacing, a signal format, and a sequence used for transmitting a request signal for the above system information.

5. In paragraph 1, The above configuration information is, A method in which the terminal is configured based on configuration information of a cell to which the terminal was previously connected.

6. In a method for configuring a request operation of system information by a base station in wireless communication, A step of notifying a terminal that a system information block is not transmitted after transmission of a synchronization signal block from a base station; A step of transmitting configuration information including uplink resource information for receiving a request signal for the above system information; and A method comprising the step of receiving a request signal for the system information based on the configuration information.

7. In paragraph 6, The step of notifying the terminal that the above system information block is not transmitted is as follows: A method of transmitting information indicating that the above system information block is a cell transmitted upon request.

8. In paragraph 7, Information indicating that the above system information block is a cell transmitted upon request, The frequency offset for the above synchronization signal block is configured to be greater than or equal to a first reference value in frequency range 1 (FR1) and greater than or equal to a second reference value in frequency range 2 (FR2). A method wherein the first reference value is set to 24 or more, and the second reference value is set to 12 or more.

9. In paragraph 6, The above configuration information is, A method comprising at least one piece of information from among a frequency band, a frequency domain location, a time domain location, a subcarrier spacing, a signal format, and a sequence used for transmitting a request signal for the above system information.

10. In paragraph 6, The above configuration information is, A method in which the terminal is configured based on configuration information of a cell to which the terminal was previously connected.

11. In a terminal configuring a request operation for system information in wireless communication, Transmitter; Receiver; and Including a control unit that controls the operation of the above transmitter and receiver, The above control unit, A terminal that confirms that a system information block is not transmitted after transmission of a synchronization signal block from a base station, receives configuration information including uplink resource information for transmitting a request signal for the system information, and transmits a request signal for the system information based on the configuration information.

12. In paragraph 11, The above control unit, A terminal that receives information indicating that the above system information block is a cell transmitted upon request, and confirms that the above system information block is not transmitted.

13. In paragraph 12, Information indicating that the above system information block is a cell transmitted upon request, The frequency offset for the above synchronization signal block is configured to be greater than or equal to a first reference value in frequency range 1 (FR1) and greater than or equal to a second reference value in frequency range 2 (FR2). A terminal in which the first reference value is set to 24 or more and the second reference value is set to 12 or more.

14. In paragraph 11, The above configuration information is, A terminal including at least one piece of information among a frequency band, a frequency domain location, a time domain location, a subcarrier spacing, a signal format, and a sequence used for transmitting a request signal for the above system information.

15. In paragraph 11, The above configuration information is, A terminal configured based on the configuration information of the cell to which the terminal was previously connected.

Images