Beam failure recovery method and device for on demand SSB in wireless communication system
By implementing an on-demand SSB transmission method, the energy consumption of wireless communication systems is reduced, addressing the need for efficient beam failure recovery in 5G/6G technologies.
Patent Information
- Application Number
- PCT/KR2026/005912
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
There is a growing need to reduce energy consumption in wireless communication systems, particularly in terminals and base stations, as the demand for faster and more reliable communication technologies like 5G and 6G increases.
A method is proposed where a base station transmits an on-demand synchronization signal block (SSB) to a terminal upon request, allowing for efficient beam failure recovery and reducing unnecessary energy consumption by optimizing synchronization signal transmission.
This approach enables effective beam failure recovery while minimizing energy usage by only transmitting SSBs when needed, thus enhancing energy efficiency in communication systems.
Smart Images

Figure KR2026005912_12112026_PF_FP_ABST
Abstract
Description
Beam failure recovery method and device for on-demand SSB in wireless communication system
[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method and apparatus for energy saving in a wireless communication system.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.
[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.
[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.
[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.
[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.
[0008] With the recent development of 5G / 6G communication systems that take the environment into account, there is a growing need for methods to reduce energy consumption or save energy in communication systems (e.g., terminals, base stations, networks, etc.).
[0009] The present disclosure proposes a method for reducing energy consumption of communication systems (e.g., terminals, base stations, networks, etc.) in accordance with the development of 5G / 6G communication systems.
[0010] The present disclosure relates to a method performed by a base station in a wireless communication system, comprising: transmitting a synchronization signal to a terminal; receiving request information from the terminal requesting an on-demand synchronization signal block (SSB) associated with the synchronization signal; transmitting at least one on-demand SSB to the terminal in response to the request information; and receiving a message from the terminal reporting an on-demand SSB selected from the terminal among the at least one on-demand SSB.
[0011] The present disclosure enables a terminal to effectively perform beam failure recovery by requesting an on-demand SSB from a base station.
[0012] FIG. 1 illustrates the basic structure of the time-frequency domain, which is a wireless resource domain in a wireless communication system according to one embodiment of the present disclosure.
[0013] FIG. 2 illustrates a slot structure considered in a wireless communication system according to one embodiment of the present disclosure.
[0014] FIG. 3 illustrates an example of a time domain mapping structure of a synchronization signal and a beam sweeping operation according to an embodiment of the present disclosure.
[0015] FIG. 4 illustrates a synchronization signal block considered in a wireless communication system according to one embodiment of the present disclosure.
[0016] FIG. 5 illustrates various transmission cases of a synchronization signal block in a frequency band below 6 GHz considered in a wireless communication system according to one embodiment of the present disclosure.
[0017] FIG. 6 illustrates transmission cases of a synchronization signal block in a frequency band of 6 GHz or higher considered in a wireless communication system according to one embodiment of the present disclosure.
[0018] FIG. 7 illustrates transmission cases of a synchronization signal block according to a subcarrier interval within 5ms in a wireless communication system according to one embodiment of the present disclosure.
[0019] FIG. 8 illustrates an example explaining DMRS patterns (type 1 and type 2) used for communication between a base station and a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0020] FIG. 9 illustrates an example of channel estimation using DMRS received from one PUSCH in the time band of a wireless communication system according to one embodiment of the present disclosure.
[0021] FIG. 10 illustrates a method for resetting SSB transmission through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.
[0022] FIG. 11 illustrates a method for resetting BWP and BW through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.
[0023] FIG. 12 illustrates a method for resetting DRX through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.
[0024] FIG. 13 illustrates an example explaining a DTx method for base station energy saving according to one embodiment of the present disclosure.
[0025] FIG. 14 illustrates an example explaining the operation of a base station according to a gNB wake-up signal according to one embodiment of the present disclosure.
[0026] FIG. 15 illustrates an antenna adaptation method for a base station for energy saving of a wireless communication system according to one embodiment of the present disclosure.
[0027] FIG. 16 illustrates an example of on-demand SSB operation in a situation where an S-cell (secondary cell, SCell) is set up for a terminal but is not yet activated, according to one embodiment of the present disclosure.
[0028] FIG. 17 illustrates an example of on-demand SSB operation in a situation where an activation instruction for an S cell (secondary cell, SCell) is received according to an embodiment of the present disclosure.
[0029] FIG. 18 illustrates an example in which an adaptation of the SSB burst cycle is applied according to one embodiment of the present disclosure.
[0030] FIG. 19 illustrates an example of a method in which a terminal requests an on-demand SSB from a base station to perform beam failure recovery according to an embodiment of the present disclosure.
[0031] FIG. 20 illustrates an example of a method in which a terminal requests an on-demand SSB from a base station to perform beam failure recovery according to an embodiment of the present disclosure.
[0032] FIG. 21 is a flowchart of terminal operations applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.
[0033] FIG. 22 is a flowchart of base station operations applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.
[0034] FIG. 23 is a block diagram of a terminal according to one embodiment of the present disclosure.
[0035] FIG. 24 is a block diagram of a base station according to one embodiment of the present disclosure.
[0036] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0037] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0038] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.
[0039] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.
[0040] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, such terms may be replaced with terms defined in 3GPP Technical Specifications (TS) where appropriate.
[0041] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."
[0042] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.
[0043] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) refers to the wireless transmission path of a signal transmitted by a base station to a terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) and 6th generation mobile communication technology (6G) developed after LTE-A may be included, and the 5G or 6G below may be a concept that includes existing LTE, LTE-A and other similar services. In addition, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0044] Hereinafter, “A or B” as described in the present disclosure may be understood as “A and / or B,” which may be understood to include “A,” or “B,” or “A and B.”
[0045] Additionally, “at least one of A, B, or C” described in the present disclosure may be understood to include “A,” or “B,” or “C,” or “any combination of A, B, and C.”
[0046] Additionally, “A / B” as described in the present disclosure may be understood as “A and / or B,” which may be understood as including “A,” or “B,” or “A and B.”
[0047] Additionally, “A, B” as described in the present disclosure may be understood as “A and / or B,” which may be understood as including “A,” or “B,” or “A and B.”
[0048] Furthermore, the expressions “if” and “in case that” as described in this disclosure or claims may be interpreted, depending on the context, as meaning “when or upon,” “in response to,” “based on,” or “according to,” and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.
[0049] Additionally, the expression in the present disclosure or claims that information can be configured from a base station may mean that a terminal receives said information from a base station depending on the context, and such expression may be replaced with other terms having the same or substantially similar meaning.
[0050] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.
[0051] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the circumstances presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.
[0052] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.
[0053] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.
[0054] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression "A" is used in one embodiment and the expression "B" is used in another embodiment, they may be understood by interchangeably, substituted, or combined.
[0055] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).
[0056] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.
[0057] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.
[0058] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.
[0059] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.
[0060] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0061] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.
[0062] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure.
[0063] Accordingly, various embodiments provide a program comprising code for implementing an apparatus or method according to any one of the claims of the present specification and a non-transient machine-readable storage medium for storing such program.
[0064] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each specific embodiment, and may also be utilized as a combination of all or part of one or more embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope of the present disclosure without significantly departing from the scope of the present disclosure, at the judgment of a person skilled in the art.
[0065] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as 3GPP’s HSPA (high speed packet access), LTE (long term evolution or E-UTRA (evolved universal terrestrial radio access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (high rate packet data), UMB (ultra mobile broadband), and IEEE’s 802.17e communication standards.
[0066] In the LTE system, a representative example of a broadband wireless communication system, the downlink (DL) employs the orthogonal frequency division multiplexing (OFDM) method, and the uplink (UL) employs the single carrier frequency division multiple access (SC-FDMA) method. The uplink refers to a wireless link through which a terminal (hereinafter referred to as user equipment (UE) or terminal) (or mobile station (MS)) transmits data or control signals to a base station (eNode B (eNB) or base station (BS)), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal (UE). Furthermore, the aforementioned multiple access method typically ensures that the time-frequency resources to be used to transmit data or control information for each user do not overlap, that is, that orthogonality is established, thereby allowing the data or control information of each user to be distinguished.
[0067] 5G communication systems, which are communication systems following LTE, must support services that simultaneously satisfy various requirements so as to freely reflect the diverse needs of users and service providers. Services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), or ultra reliability low latency communication (URLC).
[0068] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing the peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, improvements in various transmission and reception technologies, including enhanced multi-input multi-output (MIMO) transmission technology, may be required. Additionally, while LTE systems transmit signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission speeds required by the 5G communication system by using a frequency bandwidth wider than 20 MHz in frequency bands of 3 to 6 GHz or above 6 GHz.
[0069] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for the connection of a large number of terminals within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT provides communication functions by attaching various sensors and diverse devices, a large number of terminals (e.g., 1,000,000 terminals / km²) are required within a cell. 2 It must be able to support mMTC. In addition, terminals supporting mMTC require wider coverage compared to other services provided by the 5G communication system, as they are likely to be located in dead zones where cells cannot cover, such as building basements, due to the nature of the service. Terminals supporting mMTC must be low-cost devices, and because it is difficult to frequently replace the device's battery, they require a very long battery life of 10 to 16 years.
[0070] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, or emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For example, services supporting URLLC must satisfy air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements must be satisfied. Therefore, for services supporting URLLC, 5G systems must provide a transmit time interval (TTI) smaller than other services, and at the same time, allocate a wide resource in the frequency band to ensure the reliability of the communication link.
[0071] Three services of a 5G communication system (hereinafter interchangeable with 5G systems), namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. To satisfy the different requirements of each service, different transmission and reception techniques and transmission and reception parameters may be used between the services.
[0072] The frame structure of a 5G system will be described in more detail below with reference to the drawings. For convenience of explanation, the wireless communication system to which the present disclosure applies will be described below using the configuration of a 5G system as an example; however, the embodiments of the present disclosure may be applied in the same or similar manner to systems of 5G or higher, such as 6G systems or other communication systems to which the present disclosure is applicable.
[0073] FIG. 1 illustrates the basic structure of the time-frequency domain, which is a wireless resource domain in a wireless communication system according to one embodiment of the present disclosure.
[0074] In FIG. 1, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one Orthogonal Frequency Division Multiplexing (OFDM) symbol (or Discrete Fourier Transform Spread OFDM) symbol) (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain, the number of subcarriers per resource block (RB) is indicated. (For example, 12) consecutive REs can form a single resource block (RB, 104). Also, the setting value for subcarrier spacing in the time domain Representing the number of symbols per subframe according to A number of consecutive OFDM symbols can form a subframe (110).
[0075] FIG. 2 illustrates a slot structure considered in a wireless communication system according to one embodiment of the present disclosure.
[0076] FIG. 2 illustrates an example of a slot structure comprising a frame (200), a subframe (201), and slots (202, 203). One frame (200) may be defined as 10 ms. One subframe (201) may be defined as 1 ms, and thus one frame (200) may consist of a total of 10 subframes (201). One slot (202, 203) may be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( ))=14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on μ (204 or 205), which is a setting value for the subcarrier space (SCS).
[0077] The slot structure for cases where the subcarrier spacing setting value is μ=0 (204) and μ=1 (205) is illustrated. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (e.g., including slot (203)). That is, the number of slots per subframe ( )) may vary, and accordingly, the number of slots per frame ( ) may vary. For example, depending on the setting μ for each subcarrier interval. and It can be defined by [Table 1] below.
[0078] 014101114202214404314808414160165143203261464064
[0079] In a 5G wireless communication system, a synchronization signal block (SSB, which may be used interchangeably with SS block or SS / PBCH block) may be transmitted for the initial connection of a terminal, and the synchronization signal block may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). In the initial access phase where the terminal connects to the system, the terminal can first obtain downlink time and frequency domain synchronization from the synchronization signal through a cell search and obtain a cell ID. The synchronization signal may include the PSS and SSS. Furthermore, the terminal can receive a PBCH transmitting a master information block (MIB) from the base station to obtain system information related to transmission and reception, such as system bandwidth or related control information, as well as basic parameter values. Based on this information, the terminal can use the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). The System Information Block (SIB) can be obtained by performing decoding on the Channel. Subsequently, the terminal can exchange identification information with the base station through a random access step and establish initial network access by undergoing registration and authentication steps. Additionally, the terminal can obtain cell-common transmission and reception control information by receiving the System Information Block (SIB) transmitted by the base station.The above cell common transmission and reception control information may include random access control information, paging control information, and common control information for various physical channels.
[0080] The synchronization signal serves as a reference for cell search, and subcarrier spacing can be applied for each frequency band to suit channel environments such as phase noise. In the case of data channels or control channels, as described above, subcarrier spacing may be applied differently depending on the service type to support various services.
[0081] FIG. 3 illustrates an example of a time domain mapping structure of a synchronization signal and a beam sweeping operation according to an embodiment of the present disclosure.
[0082] For the purpose of explanation, the following components may be defined.
[0083] - PSS (Primary Synchronization Signal): A signal that serves as the reference for DL time / frequency synchronization and provides some cell ID information.
[0084] - SSS (Secondary Synchronization Signal): Serves as a reference for DL time / frequency synchronization and provides some of the remaining information, including the cell ID. Additionally, it can serve as a reference signal for PBCH demodulation.
[0085] - PBCH (Physical Broadcast Channel): Provides the Master Information Block (MIB), which is essential system information required for the transmission and reception of the terminal's data and control channels. The said essential system information may include control information related to the search space representing wireless resource mapping information of the control channel, scheduling control information for a separate data channel transmitting system information, and information such as the System Frame Number (SFN), which is a frame-unit index serving as a timing reference.
[0086] - SS / PBCH Block (Synchronization Signal / PBCH Block or SSB): An SS / PBCH block consists of N OFDM symbols and can be formed by a combination of PSS, SSS, PBCH, etc., that is, it may include at least one of PSS, SSS, or PBCH. In systems where beam sweeping technology is applied, the SS / PBCH block is the minimum unit to which beam sweeping is applied. In a 5G system, N can be 4. A base station can transmit up to L SS / PBCH blocks, and said L SS / PBCH blocks are mapped within a half frame (0.5ms). And said L SS / PBCH blocks are repeated periodically in units of a predetermined period P. The base station may notify the terminal of said period P through signaling. If there is no separate signaling for said period P, the terminal applies a pre-agreed default value.
[0087] Referring to FIG. 3, beam sweeping can be applied in units of SS / PBCH blocks over time. In the case of Terminal 1 (305), at time t1 (301), it receives an SS / PBCH block using a beam radiated in the direction of #d0 (303) by beamforming applied to SS / PBCH block #0. Then, at time t2 (302), Terminal 2 (306) receives an SS / PBCH block using a beam radiated in the direction of #d4 (304) by beamforming applied to SS / PBCH block #4. The terminal can obtain an optimal synchronization signal through a beam radiated from the base station in the direction where the terminal is located. For example, it may be difficult for Terminal 1 (305) to obtain time / frequency synchronization and essential system information from an SS / PBCH block through a beam radiated in the direction of #d4 (304), which is far from the location of Terminal 1 (305).
[0088] In addition to the initial connection procedure, the terminal may also receive SS / PBCH blocks to determine whether the radio link quality of the current cell is maintained above a certain level. Furthermore, during the handover procedure in which the terminal moves the connection from the current cell to an adjacent cell, the terminal may receive SS / PBCH blocks of the adjacent cell to determine the radio link quality of the adjacent cell and to obtain time / frequency synchronization with the adjacent cell.
[0089] Below, the cell initial connection operation procedure of a 5G wireless communication system will be explained in more detail with reference to the drawings.
[0090] Synchronization signals serve as reference signals for cell search and can be transmitted with subcarrier spacing applied to suit the channel environment (e.g., phase noise) for each frequency band. 5G base stations can transmit multiple synchronization signal blocks depending on the number of analog beams to be operated. For example, PSS and SSS can be mapped and transmitted across 12 RBs, while PBCH can be mapped and transmitted across 24 RBs. The structure of synchronization signal and PBCH transmission in a 5G communication system is described below.
[0091] FIG. 4 illustrates a synchronization signal block considered in a wireless communication system according to one embodiment of the present disclosure.
[0092] Referring to FIG. 4, the synchronization signal block (SS block, SSB) (400) may include PSS (401), SSS (403), and PBCH (Physical Broadcast Channel) (402).
[0093] The synchronization signal block (400) can be mapped to four OFDM symbols (404) in the time axis. The PSS (401) and SSS (403) can be transmitted at 12 RB (405) in the frequency axis and at the first and third OFDM symbols in the time axis, respectively. In a 5G system, for example, a total of 1008 different cell IDs can be defined. Depending on the physical cell ID (PCI) of the cell, the PSS (401) can have three different values, and the SSS (403) can have 336 different values. The terminal can obtain one of the 1008 cell IDs (336 x 3 = 1008) as a combination through detection of the PSS (401) and SSS (403). This can be expressed by the following [Equation 1].
[0094]
[0095] Here can be estimated from SSS(403) and can have a value between 0 and 335. can be estimated from PSS (401) and can have a value between 0 and 2. The terminal class The cell ID is a combination of The value can be estimated.
[0096] The PBCH (402) can be transmitted from a resource containing 6 RBs (407, 408) on each side excluding the 12 RBs (405) in the middle, with 24 RBs (406) in the frequency axis and SSS (403) in the 2nd to 4th OFDM symbols of the SS block in the time axis being transmitted. The PBCH (402) may include a PBCH payload and a PBCH DMRS (demodulation reference signal), and various system information called MIB may be transmitted in the PBCH payload. For example, the MIB may include information such as that shown in [Table 2] below.
[0097] MIB ::= SEQUENCE {systemFrameNumber BIT STRING (SIZE (6)),subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120},ssb-SubcarrierOffset INTEGER (0..15),dmrs-TypeA-Position ENUMERATED {pos2, pos3},pdcch-ConfigSIB1 PDCCH-ConfigSIB1,cellBarred ENUMERATED {barred, notBarred},intraFreqReselection ENUMERATED {allowed, notAllowed},spare BIT STRING (SIZE (1))}
[0098] - Synchronization signal block information: The frequency domain offset of the synchronization signal block can be indicated through the 4-bit ssb-SubcarrierOffset within the MIB. The index of the synchronization signal block containing the PBCH can be obtained indirectly through PBCH DMRS and PBCH decoding. In one embodiment, in a frequency band below 6 GHz, 3 bits obtained through PBCH DMRS decoding indicate the synchronization signal block index, and in a frequency band above 6 GHz, a total of 6 bits, including 3 bits obtained through PBCH DMRS decoding and 3 bits included in the PBCH payload obtained from PBCH decoding, can indicate the synchronization signal block index containing the PBCH.
[0099] - PDCCH (physical downlink control channel) configuration information: The subcarrier spacing of the common downlink control channel can be indicated via a 1-bit (subCarrierSpacingCommon) within the MIB, and the time-frequency resource configuration information of the CORESET (control resource set) and search space (SS) of Identifier (ID) 0 can be indicated via an 8-bit (pdcch-ConfigSIB1). The CORESET of Identifier 0 can be referred to as controlResourceSetZero, and the search space of Identifier 0 can be referred to as searchspaceZero. In this disclosure, for convenience, the CORESET of Identifier 0 will be referred to as CORESET#0 or control space#0, and the search space of Identifier 0 will be referred to as search space#0. During the initial connection of the cell, the terminal can receive frequency resources indicating the number of RBs of CORESET#0, which includes the common search space set of Type0-PDCCH CSS set, and time resources indicating the number of OFDM symbols, etc., from the pdcch-ConfigSIB1.
[0100] - SFN (system frame number): Within the MIB, 6 bits (systemFrameNumber) can be used to indicate part of the SFN. The 4 bits of the SFN's LSB (Least Significant Bit) are included in the PBCH payload, and the terminal can obtain them indirectly through PBCH decoding.
[0101] - Timing information within a radio frame: With the synchronization signal block index described above and the 1-bit (half frame) obtained through PBCH decoding included in the PBCH payload, the terminal can indirectly check whether the synchronization signal block was transmitted in the first or second half frame of the radio frame.
[0102] Since the transmission bandwidth (12 RB (405)) of PSS (401) and SSS (403) and the transmission bandwidth (24 RB (406)) of PBCH (402) are different, in the first OFDM symbol where PSS (401) is transmitted within the transmission bandwidth of PBCH (402), there are 6 RBs (407, 408) on both sides excluding the 12 RB in the middle where PSS (401) is transmitted, and the area may be used to transmit other signals or be empty.
[0103] - Cell connection permission information: A 1-bit (cellBarred) within the MIB may indicate whether camping to a cell is permitted. Additionally, if camping to the cell with the best reception quality is prohibited (barred), a 1-bit (intraFreqReselection) within the MIB may indicate whether cell reselection to an intra-frequency cell is permitted.
[0104] Synchronization signal blocks can be transmitted using the same analog beam. For example, PSS (401), SSS (403), and PBCH (402) can all be transmitted on the same beam. Since analog beams have the characteristic that they cannot be applied differently in the frequency axis, the same analog beam can be applied to all frequency axis RBs within a specific OFDM symbol to which a specific analog beam is applied. For example, four OFDM symbols in which PSS (401), SSS (403), and PBCH (402) are transmitted can all be transmitted on the same analog beam.
[0105] FIG. 5 illustrates various transmission cases of a synchronization signal block in a frequency band below 6 GHz considered in a wireless communication system according to one embodiment of the present disclosure.
[0106] Referring to FIG. 5, in a 5G communication system, in a frequency band of 6 GHz or lower (or FR1 (frequency range 1), e.g., 410 MHz-7125 MHz), a subcarrier spacing (SCS) of 15 kHz (520) and a subcarrier spacing (SCS) of 30 kHz (530, 540) may be used for the transmission of a synchronization signal block. In the 15 kHz subcarrier spacing (520), there is one transmission case for the synchronization signal block (e.g., Case #1 (501)), and in the 30 kHz subcarrier spacing (530, 540), there may be two transmission cases for the synchronization signal block (e.g., Case #2 (502) and Case #3 (503)).
[0107] In case #1 (501) at a subcarrier interval of 15 kHz (520) in FIG. 5, up to two synchronization signal blocks may be transmitted within a time of 1 ms (504) (or corresponding to the length of one slot if one slot consists of 14 OFDM symbols). In one example of FIG. 5, synchronization signal block #0 (507) and synchronization signal block #1 (508) are shown. For example, synchronization signal block #0 (507) may be mapped to four consecutive symbols starting from the 3rd OFDM symbol, and synchronization signal block #1 (508) may be mapped to four consecutive symbols starting from the 9th OFDM symbol.
[0108] Different analog beams may be applied to synchronization signal block #0 (507) and synchronization signal block #1 (508). Also, the same beam may be applied to all 3rd to 6th OFDM symbols mapped to synchronization signal block #0 (507), and the same beam may be applied to all 9th to 12th OFDM symbols mapped to synchronization signal block #1 (508). For the 7th, 8th, 13th, and 14th OFDM symbols that are not mapped to synchronization signal blocks, the analog beam to be used may be freely determined at the discretion of the base station.
[0109] In case #2 (502) at a subcarrier interval of 30 kHz (530) in FIG. 5, up to two synchronization signal blocks can be transmitted within a time of 0.5 ms (505) (or corresponding to the length of one slot if one slot consists of 14 OFDM symbols), and accordingly, up to four synchronization signal blocks can be transmitted within a time of 1 ms (or corresponding to the length of two slots if one slot consists of 14 OFDM symbols). In one example of FIG. 5, a case is illustrated in which synchronization signal block #0 (509), synchronization signal block #1 (510), synchronization signal block #2 (511), and synchronization signal block #3 (512) are transmitted within a time of 1 ms (i.e., two slots). Synchronization signal block #0 (509) and synchronization signal block #1 (510) can be mapped starting from the 5th OFDM symbol and 9th OFDM symbol of the first slot, respectively, and synchronization signal block #2 (511) and synchronization signal block #3 (512) can be mapped starting from the 3rd OFDM symbol and 7th OFDM symbol of the second slot, respectively.
[0110] Different analog beams may be applied to each of the synchronization signal block #0 (509), synchronization signal block #1 (510), synchronization signal block #2 (511), and synchronization signal block #3 (512). Additionally, the same analog beam may be applied to each of the 5th to 8th OFDM symbols in the first slot where synchronization signal block #0 (509) is transmitted, the 9th to 12th OFDM symbols in the first slot where synchronization signal block #1 (510) is transmitted, the 3rd to 6th symbols in the second slot where synchronization signal block #2 (511) is transmitted, and the 7th to 10th symbols in the second slot where synchronization signal block #3 (512) is transmitted. For OFDM symbols where the synchronization signal block is not mapped, the analog beam to be used may be freely determined at the discretion of the base station.
[0111] In case #3 (503) at a subcarrier interval of 30 kHz (540) in FIG. 5, up to two synchronization signal blocks can be transmitted within a time of 0.5 ms (506) (or corresponding to the length of one slot if one slot consists of 14 OFDM symbols), and accordingly, up to four synchronization signal blocks can be transmitted within a time of 1 ms (or corresponding to the length of two slots if one slot consists of 14 OFDM symbols). In one example of FIG. 5, synchronization signal block #0 (513), synchronization signal block #1 (514), synchronization signal block #2 (515), and synchronization signal block #3 (516) are shown being transmitted within a time of 1 ms (i.e., two slots). Synchronization signal block #0 (513) and synchronization signal block #1 (514) can be mapped starting from the 3rd OFDM symbol and 9th OFDM symbol of the first slot, respectively, and synchronization signal block #2 (515) and synchronization signal block #3 (516) can be mapped starting from the 3rd OFDM symbol and 9th OFDM symbol of the second slot, respectively.
[0112] Different analog beams may be used for each of the synchronization signal block #0 (513), synchronization signal block #1 (514), synchronization signal block #2 (515), and synchronization signal block #3 (516). As described in the examples above, the same analog beam may be used for all four OFDM symbols in which each synchronization signal block is transmitted, and for OFDM symbols in which the synchronization signal block is not mapped, the choice of which beam to use may be freely determined by the base station.
[0113] FIG. 6 illustrates transmission cases of a synchronization signal block in a frequency band of 6 GHz or higher considered in a wireless communication system according to one embodiment of the present disclosure.
[0114] Referring to FIG. 6, in a wireless communication system, in a frequency band of 6 GHz or higher (or FR2, e.g., 24250 MHz-52000 MHz), a subcarrier spacing of 120 kHz (630), as in the example of Case #4 (610), and a subcarrier spacing of 240 kHz (640), as in the example of Case #5 (620), may be used for the transmission of synchronization signal blocks.
[0115] In case #4 (610) of a subcarrier interval of 120 kHz (630), up to four synchronization signal blocks can be transmitted within a time of 0.25 ms (601) (or corresponding to a length of two slots if one slot consists of 14 OFDM symbols). In one example of FIG. 6, a case is illustrated in which synchronization signal block #0 (603), synchronization signal block #1 (604), synchronization signal block #2 (605), and synchronization signal block #3 (606) are transmitted within 0.25 ms (i.e., two slots). Synchronization signal block #0 (603) and synchronization signal block #1 (604) can each be mapped to four consecutive symbols starting from the 5th OFDM symbol of the first slot and to four consecutive symbols starting from the 9th OFDM symbol, and synchronization signal block #2 (605) and synchronization signal block #3 (606) can each be mapped to four consecutive symbols starting from the 3rd OFDM symbol of the second slot and to four consecutive symbols starting from the 7th OFDM symbol.
[0116] As described in the above embodiment, different analog beams may be used for each of the synchronization signal block #0 (603), synchronization signal block #1 (604), synchronization signal block #2 (605), and synchronization signal block #3 (606). In addition, the same analog beam may be used for all four OFDM symbols transmitted by each synchronization signal block, and for OFDM symbols that are not mapped to the synchronization signal block, the choice of which beam to use may be freely determined by the base station.
[0117] In case #5 (620) at a subcarrier interval of 240 kHz (640), up to 8 synchronization signal blocks can be transmitted within a time of 0.25 ms (602) (or corresponding to a length of 4 slots if 1 slot consists of 14 OFDM symbols). In one example of FIG. 6, a case is illustrated in which synchronization signal block #0 (607), synchronization signal block #1 (608), synchronization signal block #2 (609), synchronization signal block #3 (610), synchronization signal block #4 (611), synchronization signal block #5 (612), synchronization signal block #6 (613), and synchronization signal block #7 (614) are transmitted within 0.25 ms (i.e., 4 slots).
[0118] Synchronization signal block #0 (607) and synchronization signal block #1 (608) can each be mapped to four consecutive symbols starting from the 9th OFDM symbol of the first slot and to four consecutive symbols starting from the 13th OFDM symbol, and synchronization signal block #2 (609) and synchronization signal block #3 (610) can each be mapped to four consecutive symbols starting from the 3rd OFDM symbol of the second slot and to four consecutive symbols starting from the 7th OFDM symbol, and synchronization signal block #4 (611), synchronization signal block #5 (612), and synchronization signal block #6 (613) can each be mapped to four consecutive symbols starting from the 5th OFDM symbol of the third slot, to four consecutive symbols starting from the 9th OFDM symbol and to four consecutive symbols starting from the 13th OFDM symbol, and synchronization signal block #7 (614) can be mapped to the 3rd OFDM symbol of the fourth slot It can be mapped to four consecutive symbols starting from the symbol.
[0119] As described in the above embodiment, different analog beams may be used for each of the synchronization signal block #0 (607), synchronization signal block #1 (608), synchronization signal block #2 (609), synchronization signal block #3 (610), synchronization signal block #4 (611), synchronization signal block #5 (612), synchronization signal block #6 (613), and synchronization signal block #7 (614). In addition, the same analog beam may be used for all four OFDM symbols transmitted by each synchronization signal block, and for OFDM symbols that are not mapped to the synchronization signal block, the choice of which beam to use may be freely determined by the base station.
[0120] FIG. 7 illustrates transmission cases of a synchronization signal block according to a subcarrier interval within 5ms in a wireless communication system according to one embodiment of the present disclosure.
[0121] Referring to FIG. 7, in a 5G communication system, a synchronization signal block can be transmitted periodically in units of, for example, a time interval (710) of 5 ms (corresponding to 5 subframes (711) or half frames).
[0122] In the frequency band below 3 GHz, up to 4 synchronization signal blocks can be transmitted within a time of 5 ms (710). In the frequency band between 3 GHz and 6 GHz, up to 8 synchronization signal blocks can be transmitted. In the frequency band above 6 GHz, up to 64 synchronization signal blocks can be transmitted. As described above, subcarrier spacings of 15 kHz and 30 kHz can be used in frequencies below 6 GHz.
[0123] In one example of FIG. 7, in case #1 (501) with a subcarrier interval of 15 kHz consisting of one slot of FIG. 5, a synchronization signal block can be mapped to the first and second slots in the frequency band below 3 GHz, allowing up to 4 (721) to be transmitted, and in the frequency band above 3 GHz and below 6 GHz, a synchronization signal block can be mapped to the first, second, third, and fourth slots, allowing up to 8 (722) to be transmitted. In case #2 (502) or case #3 (503) with a subcarrier interval of 30 kHz consisting of two slots of FIG. 5, a synchronization signal block can be mapped starting from the first slot in the frequency band below 3 GHz, allowing up to 4 (731, 741) to be transmitted, and in the frequency band above 3 GHz and below 6 GHz, a synchronization signal block can be mapped starting from the first and third slots, allowing up to 8 (732, 742) to be transmitted.
[0124] Subcarrier spacing of 120 kHz and 240 kHz can be used at frequencies above 6 GHz. In one example of FIG. 7, in case #4 (610) at a subcarrier spacing of 120 kHz consisting of two slots of FIG. 6, synchronization signal blocks in the frequency band above 6 GHz can be mapped starting from the 1st, 3rd, 5th, 7th, 11th, 13th, 15th, 17th, 21st, 23rd, 25th, 27th, 31st, 33rd, 35th, and 37th slots, so that up to 64 (751) can be transmitted. In one example of FIG. 7, in case #5 (620) at a subcarrier interval of 240 kHz consisting of 4 slots of FIG. 6, synchronization signal blocks in the frequency band above 6 GHz can be mapped starting from the 1st, 5th, 9th, 13th, 21st, 25th, 29th, and 33rd slots, so that up to 64 (761) can be transmitted.
[0125] Next, we will explain in detail the Bandwidth Part (BWP) settings in the 5G communication system.
[0126] In a 5G communication system, the base station can set one or more bandwidth portions for the terminal, and for each bandwidth portion, it can set the information included in [Table 3] below.
[0127] BWP ::= SEQUENCE {bwp-Id BWP-Id,(Bandwidth Identifier)locationAndBandwidth INTEGER (1..65536),(Bandwidth Location)subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},(Subcarrier Spacing)cyclicPrefix ENUMERATED { extended}(Cyclical Prefix)}
[0128] In addition to the above configuration information, various parameters related to bandwidth portions may be configured for the terminal. These information may be transmitted by the base station to the terminal via upper-layer signaling, such as RRC signaling. Among the one or more configured bandwidth portions, at least one bandwidth portion may be activated. Whether a configured bandwidth portion is activated may be transmitted quasi-statically from the base station to the terminal via RRC signaling or dynamically via DCI (downlink control information).
[0129] Before RRC connection, the terminal can receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via the Master Information Block (MIB) or System Information Block 1 (SIB1).
[0130] To explain specifically regarding the configuration of Control Area #0, Search Area #0, and the initial bandwidth portion, the terminal can receive configuration information for Control Area #0 and Search Area #0 through the MIB during the initial connection phase, through which a PDCCH can be transmitted to receive system information required for initial connection (Remaining System Information; which may correspond to RMSI or System Information Block 1; SIB1). The Control Area and Search Area configured by the MIB can each be considered as Identifier (ID) 0. The base station can notify the terminal of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Area #0 through the MIB. Additionally, the base station can notify the terminal of configuration information regarding the monitoring period and occasion for Control Area #0, that is, configuration information for Search Area #0, through the MIB.
[0131] In the method for setting the initial bandwidth part described above, terminals prior to RRC connection (Connected) can receive configuration information for the initial bandwidth part through the Master Information Block (MIB) during the initial connection phase. More specifically, the terminal can receive a Control Resource Set (CORESET) for a downlink control channel through which Downlink Control Information (DCI) scheduling System Information Blocks (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control resource set by the MIB can be considered as the initial bandwidth part, and through the configured initial bandwidth part, the terminal can receive the PDSCH through which the SIB is transmitted. In addition to receiving the SIB, the initial bandwidth part may also be utilized for other system information (OSI), paging, and random access.
[0132] The terminal can obtain SIB1 or SIBx (all SIBs excluding SIB1) after performing decoding of PDCCH and PDSCH based on system information contained in the received MIB. SIB1 may include at least one of uplink cell bandwidth-related information, random access parameters, paging parameters, or parameters related to uplink power control.
[0133] Generally, a terminal can establish a wireless link with a network through a random access procedure based on network synchronization and system information acquired during the cell search process. Random access may utilize contention-based or contention-free methods. When a terminal performs cell selection and re-selection during the initial connection phase of a cell, a contention-based random access method may be used, for example, to transition from the RRC_IDLE state to the RRC_CONNECTED state. Contention-free random access may be used to reset uplink synchronization when downlink data arrives, in the case of a handover, or for location measurement. Table 4 below illustrates the conditions (events) under which the random access procedure is triggered in a 5G system.
[0134] - Initial access from RRC_IDLE;- RRC Connection Re-establishment procedure;- DL or UL data arrival during RRC_CONNECTED when UL synchronization status is "non-synchronised";- UL data arrival during RRC_CONNECTED when there are no PUCCH resources for SR available;- SR failure;- Request by RRC upon synchronous reconfiguration (eg handover);- RRC Connection Resume procedure from RRC_INACTIVE;- To establish time alignment for a secondary TAG;- Request for Other SI;- Beam failure recovery;- Consistent UL LBT failure on SpCell.
[0135] If a terminal successfully completes the random access procedure, it transitions to a connected state (or RRC_CONNECTED state), enabling one-to-one communication between the base station and the terminal. The base station receives UE capability information from the terminal in the connected state (or RRC_CONNECTED state) and can adjust scheduling by referring to that terminal's UE capability information. Through the UE capability information, the terminal can inform the base station of whether it supports specific functions and the maximum allowable value of the functions it supports. Therefore, the UE capability information reported by each terminal to the base station may vary depending on the terminal.
[0136] As an example, the terminal may report terminal capability (UE capability) information to the base station, including at least one of the following control information.
[0137] - Control information related to the frequency bands supported by the terminal
[0138] - Control information related to channel bandwidth supported by the terminal
[0139] - Control information regarding the maximum modulation scheme supported by the terminal
[0140] - Control information regarding the maximum number of beams supported by the terminal
[0141] - Control information regarding the maximum number of layers supported by the terminal
[0142] - Control information related to CSI reporting supported by the terminal
[0143] - Control information on whether the terminal supports frequency hopping
[0144] - Bandwidth-related control information when Carrier Aggregation (CA) is supported
[0145] - Control information on whether cross-carrier scheduling is supported when carrier bundling is supported
[0146] Based on the transmission and reception process of terminal capability information, a terminal connected to a base station can communicate one-to-one with the base station as a terminal in the RRC_CONNECTED state. A terminal in the RRC_CONNECTED state can perform the following operations.
[0147] - Monitoring of the Physical Downlink Control Channel (PDCCH)
[0148] - Radio link monitoring
[0149] - Beam failure detection and beam failure recovery
[0150] First, the monitoring of the downlink control channel of a terminal in the RRC_CONNECTED state is described in detail. If Discontinuous Reception (DRX) is not established from the base station, the terminal's Medium Access Control (MAC) entity can continuously monitor the PDCCH. If DRX is established to the terminal's MAC entity by an upline signal from the base station, the terminal's MAC entity can monitor the PDCCH discontinuously using the DRX operation for all activated serving cells. The terminal receives DRX operation-related parameters (e.g., including at least one of DRX cycle, drx-onDurationTimer, drx-InactivityTimer, or drx-SlotOffset) by an upline signal from the base station and can discontinuously monitor the PDCCH based on said parameters. In the present disclosure, monitoring the PDCCH with DRX by the RRC_CONNECTED terminal above may be described as performing a C-DRX (CONNECTED-DRX) operation or performing C-DRX.
[0151] Next, radio link monitoring by a terminal in the RRC_CONNECTED state is described in detail. The terminal performs radio link monitoring for a serving cell (or a primary serving cell (primary cell), i.e., a P-cell) using CSI-RS (channel state information-reference signal) or SS / PBCH signals. Performing radio link monitoring can be explained as measuring the quality of the radio link using the aforementioned signals to determine whether the radio link is in-sync or out-of-sync. Which signal, CSI-RS or SS / PBCH, is used for radio link monitoring can be configured by receiving a higher-level signal from the base station.
[0152] When measuring the quality of the above radio link, the evaluation period for measuring and evaluating whether it is in-sync or out-of-sync is described. The in-sync evaluation period and the out-of-sync evaluation period may be determined differently depending on whether a DRX is configured for PDCCH monitoring from the base station, and if a DRX is configured, the DRX period value. Next, the indication period is described, during which the terminal's physical layer sends the evaluated in-sync or out-of-sync status to the terminal's upper layer as a result of the measurement and evaluation. If a DRX is not configured, the indication period is determined as the maximum value between the shortest period of the resource for radio link monitoring and Xms. X can be 2 or 10. Conversely, if a DRX is configured, the indication period is determined as the maximum value between the shortest period of the resource for radio link monitoring and the DRX period.
[0153] The above in-sync is explained. When the radio link quality is better than the threshold Q_in received from the base station configuration for any resources in the resource set for radio link monitoring, the physical layer of the terminal transmits an in-sync to the upper layer of the terminal in the frame where the radio link quality is evaluated. To determine the in-sync of the radio link quality, the terminal determines whether the block error rate (BLER) when performing PDCCH decoding from hypothetical downlink control channel (hypothetical PDCCH) parameters is smaller than a predefined value. The predefined value may be, for example, 2%. The above downlink control channel parameters may be determined differently depending on which signal is used to perform radio link monitoring.
[0154] The above out-of-sync is explained. If, for any resources in the resource set for radio link monitoring, the radio link quality is worse than the threshold Q_out received from the base station configuration, the physical layer of the terminal transmits out-of-sync to the upper layer of the terminal in the frame where the radio link quality is evaluated. To determine the out-of-sync of the radio link quality, the terminal determines whether the block error rate when performing PDCCH decoding from virtual downlink control channel parameters is greater than a predefined value. The predefined value may be, for example, 10%. The above downlink control channel parameters may be determined differently depending on which signal is used to perform radio link monitoring.
[0155] The terminal's upper layer (or the terminal) initiates the T310 timer after receiving N310 consecutive out-of-sink signals. If the terminal receives N311 consecutive in-sink signals, the T310 timer is stopped. Otherwise, the terminal declares a Radio Link Failure (RLF) and initiates the T311 timer. The terminal performs cell selection to find a suitable cell. If no suitable cell is found and the T311 timer expires, the terminal transitions to the RRC_IDLE state. If a suitable cell is found, the T311 timer is stopped, the terminal transmits an RRC Reestablishment Request message to the base station of the cell, and initiates the T301 timer. If the RRC Reestablishment operation is not successfully completed and the T301 timer expires, the terminal transitions to the RRC_IDLE state. If the RRC Reestablishment operation is successfully completed within the T301 timer, the terminal transitions to the normal RRC_CONNECTED state.
[0156] Parameters and timers for performing procedures related to radio link monitoring and radio link failure, such as the above N310, T310 timer, N311, T311 timer, T301 timer, etc., can be set to the terminal by a higher signal from the base station.
[0157] Next, Beam Failure Detection (BFD) and Beam Failure Recovery (BFR) for a terminal in the RRC_CONNECTED state are explained in detail. Depending on the configuration of the upper signal from the base station, the terminal can perform Beam Failure Detection for the serving cell using CSI-RS or SS / PBCH signals. Performing Beam Failure Detection can be explained as measuring the quality of the beam using the aforementioned signals to determine whether the reception status of the beam is reliable (for example, whether the virtual downlink control channel block error rate for the measured beam quality is smaller than a predefined value).
[0158] If the reception status of the beam is unreliable, that is, if the virtual downlink control channel block error rate for the measured beam quality is equal to or greater than the predefined value, it is defined as a beam failure instance. Whether to use the CSI-RS or SS / PBCH signal to perform beam failure detection can be configured by receiving an upper signal from the base station. To determine the virtual downlink control channel block error rate, the terminal determines whether the block error rate when performing PDCCH decoding from virtual downlink control channel parameters (e.g., a specific DCI format, the number of OFDM symbols of the PDCCH, the PDCCH aggregation level, the PDCCH bandwidth, subcarrier spacing, the REG (resource element group) bundle size, the CP (cyclic prefix) length, etc.) is greater than the predefined value. The predefined value may be, for example, 10%. The downlink control channel parameters may be determined differently depending on which signal is used to perform beam failure detection.
[0159] When the above beam failure instance increases by 1, the timer (beamFailureDetectionTimer) associated with the beam failure instance is restarted, and if the terminal (or the terminal's MAC layer) fails to detect additional beam failure instances until the timer expires, the accumulated beam failure instances (BFI_COUNTER per Serving cell) are reset.
[0160] If the accumulated number of beam failure instances is equal to or greater than the maximum number of beam failure instances (beamFailureInstanceMaxCount) set by the base station as a higher signal, the terminal (or the terminal's MAC layer) may trigger beam failure recovery for the S-cell if the serving cell is an S-cell, and may trigger random access (for beam failure recovery) in the Sp-cell if the serving cell is an Sp-cell. In the case of duplex, the Sp-cell (Special Cell) may refer to the P-cell of the MCG if the MAC entity is associated with the MCG, and may refer to the PS-cell of the SCG if the MAC entity is associated with the SCG. In the case of non-duplex, the Sp-cell may refer to the P-cell. The Sp-cell supports PUCCH transmission, may support collision-based random access, and may always be active.
[0161] When random access is triggered in the above Sp cell, RA_TYPE is set to 4-stepRA, and the terminal (or the terminal's MAC layer) can perform beam failure recovery in the Sp cell by performing random access to the base station using a random access preamble corresponding to a CSI-RS or SS / PBCH that has an RSRP above the threshold value set by the upper signal among separate CSI-RS or SS / PBCH signals set by the upper signal. The terminal can perform contention-free random access (contention-free random access) (CFRA) using the downlink control channel resource set (CORESET) from the base station and the random access preamble for beam failure recovery. If the above collision-free random access fails, or if there is no best candidate beam allocated to the above collision-free random access, or if a collision-free random access resource or random access preamble is not set, the terminal can recover from the beam failure by performing a collision-free random access (contention-based random access, CBRA).
[0162] When beam failure recovery for the above S-cell is triggered, the best candidate beam can be found during the evaluation period using one of the CSI-RS or SS / PBCH signals set by the upper signal for beam failure detection or a separate CSI-RS or SS / PBCH signal set by the upper signal for beam failure recovery. After finding the best candidate beam, the terminal (or the terminal's MAC layer) can perform beam failure recovery by transmitting a BFR MAC CE containing the best beam to the base station.
[0163] Next, unlike the RRC_CONNECTED state, a terminal that is not connected to the base station may be in the RRC_IDLE state, and a terminal in the RRC_IDLE state can perform the following process.
[0164] - Performing a terminal-specific DRX (Discontinuous Reception) cycle set by the upper layer, and the fact that a terminal in the RRC_IDLE state performs a DRX cycle can be described as performing an I-DRX (IDLE-DRX) operation or performing I-DRX.
[0165] - Receive paging messages from the core network
[0166] - Obtain system information
[0167] - Measurement actions related to the serving cell (or the cell currently being camped) and cell selection / reselection
[0168] - Measurement operation and cell reselection related to surrounding cells
[0169] - Receive PEI (Paging Early Indication)
[0170] The following describes a method for setting measurement times for Radio Resource Management (RRM) based on synchronization signal blocks (SS blocks or SSB) of 5G wireless communication systems.
[0171] The terminal can receive the MeasObjectNR of MeasObjectToAddModList as a setting for SSB-based intra / inter-frequency measurements and CSI-RS (channel state information-reference signal)-based intra / inter-frequency measurements through upper layer signaling. For example, MeasObjectNR can be configured as shown in [Table 5] below.
[0172] MeasObjectNR ::= SEQUENCE {ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSBssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSBsmtc1 SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSBsmtc2 SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnectedrefFreqCSI-RS ARFCN-ValueNR OPTIONAL, -- Cond CSI-RSreferenceSignalConfig ReferenceSignalConfig,absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need RabsThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, -- Need RnrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need RnrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, -- Need RquantityConfigIndex INTEGER (1..maxNrofQuantityConfig),offsetMO Q-OffsetRangeList,cellsToRemoveList PCI-List OPTIONAL, -- Need NcellsToAddModList CellsToAddModList OPTIONAL, -- Need NblackCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NblackCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need NwhiteCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need NwhiteCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N… ,[[freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Need RmeasCycleSCell ENUMERATED {sf160, sf236, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL -- Need R]],[[smtc3list-r16 SSB-MTC3List-r16 OPTIONAL, -- Need Rrmtc-Config-r16 SetupRelease {RMTC-Config-r16} OPTIONAL, -- Need Mt312-r16 SetupRelease { T312-r16} OPTIONAL -- Need M]]}.
[0173] The terms in [Table 5] may perform the following functions, but are not limited thereto.
[0174] - ssbFrequency: Allows setting the frequency position of the synchronization signal associated with MeasObjectNR.
[0175] - ssbSubcarrierSpacing: Sets the subcarrier spacing of the SSB. FR1 can only be applied at 15 kHz or 30 kHz, and FR2 at 120 kHz or 240 kHz.
[0176] - smtc1: Represents the SS / PBCH block measurement timing configuration. It allows you to set the primary measurement timing configuration and configure the timing offset and duration for the SSB.
[0177] - smtc2: Allows setting secondary measurement timing configuration for SSBs associated with MeasObjectNRs having PCIs listed in pci-List.
[0178] In addition to this, it can be configured through other higher-level signaling, for example, SMTC can be configured to the terminal through SIB2 for intra-frequency, inter-frequency, and inter-RAT cell re-selection, or through reconfigurationWithSync for NR PSCell change and NR PCell change, and SMTC can also be configured to the terminal through SCellConfig for NR SCell addition.
[0179] The terminal can set the first SS / PBCH block measurement timing configuration (SMTC) according to periodicityAndOffset (providing Periodicity and Offset) through smtc1 configured via upper layer signaling for SSB measurement. In one embodiment, the first subframe of each SMTC occasion can be started in a subframe of SpCell with a system frame number (SFN) satisfying the conditions of [Table 6] below.
[0180] SFN mod T = (FLOOR (Offset / 10));if the Periodicity is larger than sf5:subframe = Offset mod 10;else:subframe = Offset or (Offset +5);with T = CEIL(Periodicity / 10).
[0181] If smtc2 is configured, for the cells indicated by the pci-List value of smtc2 within the same MeasObjectNR, the terminal may configure additional SMTCs according to the periodicity of the configured smtc2 and the offset and duration of smtc1. In addition, the terminal or IAB MT may configure smtc and measure SSBs through smtc2-LP (with long periodicity) and smtc3list for IAB-MT (integrated access and backhaul - mobile termination) for the same frequency (e.g., a frequency for intra-frequency cell reselection) or a different frequency (e.g., frequencies for inter-frequency cell reselection). In one embodiment, the terminal or IAB MT may not consider SSBs transmitted in subframes other than the SMTC occasion for SSB-based RRM measurement at the configured ssbFrequency.
[0182] Base stations can utilize various multi-TRP (transmit / receive point or transmission / reception point) operation methods depending on the serving cell configuration and physical cell identifier (PCI) configuration. Among these, when two TRPs located at a physically separated distance have different PCIs, there can be two methods for operating the two TRPs.
[0183] [Operation Method 1]
[0184] Two TRPs with different PCIs can be operated in a 2-serving cell configuration.
[0185] The base station can configure channels and signals transmitted from different TRPs to be included within different serving cell configurations through [Operation Method 1]. That is, each TRP has an independent serving cell configuration, and the frequency band values FrequencyInfoDL indicated by DownlinkConfigCommon within each serving cell configuration may indicate at least some overlapping bands. Since the above multiple TRPs operate based on multiple ServCellIndexes (e.g., ServCellIndex #1 and ServCellIndex #2), it is possible for each TRP to use a separate PCI. That is, the base station can allocate one PCI per ServCellIndex.
[0186] In this case, if multiple SSBs are transmitted from TRP 1 and TRP 2, the SSBs have different PCIs (e.g., PCI #1 and PCI #2), and the base station can map the PCI corresponding to each TRP by appropriately selecting the value of ServCellIndex indicated by the cell parameter in QCL-Info, and designate the SSB transmitted from either TRP 1 or TRP 2 as the source reference RS of the QCL configuration information. However, since this configuration applies a single serving cell configuration that can be used for the terminal's carrier aggregation (CA) to multiple TRPs, there is a problem of limiting the degree of freedom of the CA configuration or increasing the signaling burden.
[0187] [Operation Method 2]
[0188] Two TRPs with different PCIs can be operated in a single serving cell configuration.
[0189] The base station can configure channels and signals transmitted from different TRPs through a single serving cell configuration via [Operation Method 2]. Since the terminal operates based on a single ServCellIndex (e.g., ServCellIndex #1), it is impossible for it to recognize the PCI assigned to the second TRP (e.g., PCI #2). [Operation Method 2] may have greater freedom in CA configuration compared to the aforementioned [Operation Method 1], but if multiple SSBs are transmitted from TRP 1 and TRP 2, the SSBs will have different PCIs (e.g., PCI #1 and PCI #2), and the base station may be unable to map the PCI of the second TRP (e.g., PCI #2) through the ServCellIndex indicated by the cell parameter in QCL-Info. The base station may only be able to designate the SSB transmitted from TRP 1 as the source reference RS of the QCL configuration information, and it may be impossible to designate the SSB transmitted from TRP 2.
[0190] As described above, [Operation Method 1] can perform multi-TRP operation for two TRPs with different PCIs through additional serving cell settings without additional specification support, but [Operation Method 2] can operate based on the following additional terminal capability reports and base station configuration information.
[0191] Regarding terminal capability reporting for [Operation Method 2]
[0192] - The terminal can report to the base station via terminal capability that configuration for the serving cell's PCI and other additional PCIs is possible through upper-layer signaling from the base station. Such terminal capability may include two independent numbers, X1 and X2, or each X1 and X2 may be reported as an independent terminal capability.
[0193] - X1 represents the maximum number of additional PCIs that can be configured for the terminal, and the PCI may differ from the PCI of the serving cell; in this case, it refers to a situation where the time domain position and periodicity of the SSB corresponding to the additional PCI are the same as those of the serving cell's SSB.
[0194] - X2 represents the maximum number of additional PCIs that can be configured for the terminal, and in this case, the PCI may differ from the PCI of the serving cell. In this case, the time domain position and periodicity of the SSB corresponding to the additional PCI may differ from the SSB corresponding to the PCI reported as X1.
[0195] - By definition, PCIs corresponding to the values reported as X1 and X2 cannot be set simultaneously.
[0196] - The values reported as X1 and X2 through the terminal capability report can each have one integer value from 0 to 7.
[0197] - The values reported as X1 and X2 may differ from the values reported in FR1 and FR2.
[0198] Regarding upper layer signaling settings for [Operation Method 2]
[0199] - Based on the terminal capability report described above, the terminal may receive an upper layer signaling, SSB-MTCAdditionalPCI-r17, from the base station, and the upper layer signaling may include at least a plurality of additional PCIs having values different from the serving cell, an SSB transmission power corresponding to each additional PCI, and an ssb-PositionInBurst corresponding to each additional PCI, and the maximum number of additional PCIs that can be set may be 7.
[0200] - As an assumption regarding the SSB corresponding to an additional PCI of a different value from the serving cell, the terminal may be assumed to have the same center frequency, subcarrier spacing, and subframe number offset as the SSB of the serving cell.
[0201] - The terminal may assume that the reference RS (e.g., SSB or CSI-RS) corresponding to the PCI of the serving cell is always connected to an active TCI state, and in the case of additionally configured PCIs having values different from the serving cell, when there is one or more PCIs, it may assume that only one of those PCIs is connected to an active TCI state.
[0202] - If a terminal is configured with two different coresetPoolIndexes, and a reference RS corresponding to a serving cell PCI is connected to one or more active TCI states, and a reference RS corresponding to an additionally configured PCI having a different value from the serving cell is connected to one or more active TCI states, the terminal can expect that the active TCI state(s) connected to the serving cell PCI are connected to one of the two coresetPoolIndexes, and the active TCI state(s) connected to the additionally configured PCI having a different value from the serving cell are connected to the other coresetPoolIndex.
[0203] The terminal capability reporting and upper layer signaling of the base station for the above-described [Operation Method 2] can set an additional PCI with a value different from the PCI of the serving cell. If the above setting does not exist, the SSB corresponding to the additional PCI with a value different from the PCI of the serving cell, which cannot be designated as a source reference RS, can be used to designate it as the source reference RS of the QCL setting information. Furthermore, unlike the SSB that can be set for use in purposes such as RRM, mobility, or handover, such as the setting information for the SSB that can be set within the upper layer signaling smtc1 and smtc2, it can be used to serve as a QCL source RS to support multiple TRP operations having different PCIs.
[0204] Next, we will explain in detail the demodulation reference signal (DMRS), which is one of the reference signals in the 5G system.
[0205] A DMRS may consist of multiple DMRS ports, and each port maintains orthogonality using CDM (code division multiplexing) or FDM (frequency division multiplexing) to prevent interference with one another. However, the term DMRS may be expressed using other terms depending on the user's intent and the purpose of use of the reference signal. The term DMRS is provided merely as a specific example to easily explain the technical content of this disclosure and to aid in understanding the disclosure, and is not intended to limit the scope of this disclosure. In other words, it is obvious to those skilled in the art that the technical concept of this disclosure can be implemented with any reference signal.
[0206] FIG. 8 illustrates an example explaining DMRS patterns (type 1 and type 2) used for communication between a base station and a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0207] Two DMRS patterns can be supported in 5G systems.
[0208] Referring to FIG. 8, DMRS type 1 (801, 802) is illustrated, specifically 1 symbol pattern (801) and 2 symbol pattern (802). DMRS type 1 (801, 802) is a DMRS pattern with a comb 2 structure and can be composed of two CDM groups (CDM group 0, CDM group 1), and different CDM groups can be FDMed.
[0209] In 1 symbol pattern (801), frequency-phase CDM is applied to the same CDM group to distinguish two DMRS ports, thus allowing a total of four orthogonal DMRS ports to be configured. 1 symbol pattern (801) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated by the illustrated number + 1000). In 2 symbol pattern (802), time / frequency-phase CDM is applied to the same CDM group to distinguish four DMRS ports, thus allowing a total of eight orthogonal DMRS ports to be configured. 2 symbol pattern (802) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated by the illustrated number + 1000).
[0210] Referring to FIG. 8, DMRS type 2 (803, 804) is illustrated, and as a DMRS pattern structure in which FD-OCC (frequency domain orthogonal cover codes) is applied to frequency-adjacent subcarriers, it can be composed of three CDM groups (CDM group 0, CDM group 1, CDM group 2), and different CDM groups can be FDM.
[0211] In 1 symbol pattern (803), frequency-phase CDM is applied to the same CDM group to distinguish two DMRS ports, thus allowing a total of six orthogonal DMRS ports to be configured. 1 symbol pattern (803) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated as the illustrated number + 1000). In 2 symbol pattern (804), time / frequency-phase CDM is applied to the same CDM group to distinguish four DMRS ports, thus allowing a total of twelve orthogonal DMRS ports to be configured. 2 symbol pattern (804) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated as the illustrated number + 1000).
[0212] As described above, in an NR system, two different DMRS patterns (e.g., DMRS type 1 (801, 802) or DMRS type 2 (803, 804)) can be configured, and each DMRS pattern can be configured to be either a one-symbol pattern (801, 803) or an adjacent two-symbol pattern (802, 804). Additionally, in an NR system, not only are DMRS port numbers scheduled, but the number of CDM groups scheduled together for PDSCH rate matching can also be configured and signaled. Furthermore, in the case of CP-OFDM (cyclic prefix based orthogonal frequency division multiplex), both of the two DMRS patterns described above may be supported in DL and UL, while in the case of DFT-S-OFDM (discrete Fourier transform spread OFDM), only DMRS type 1 (801, 802) among the DMRS patterns described above may be supported in UL.
[0213] Additionally, support may be provided to configure additional DMRS. Front-loaded DMRS refers to the first DMRS transmitted and received at the earliest symbol in the time domain among the DMRS, and additional DMRS refers to the DMRS transmitted and received at a symbol later than the front-loaded DMRS in the time domain. In an NR system, the number of additional DMRS can be configured from a minimum of 0 to a maximum of 3. Additionally, when additional DMRS is configured, the same pattern as the front-loaded DMRS may be assumed. In one embodiment, regarding the front-loaded DMRS, if information is provided on whether the aforementioned DMRS pattern type is type 1 or type 2, whether the DMRS pattern is a one-symbol pattern or an adjacent two-symbol pattern, and information on the number of DMRS ports and CDM groups used, then when additional DMRS is configured, it may be assumed that the additional DMRS has the same DMRS information as the front-loaded DMRS.
[0214] In one embodiment, the aforementioned downlink DMRS setting can be set through RRC signaling as shown in [Table 7] below.
[0215] DMRS-DownlinkConfig ::= SEQUENCE {dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need Sdmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need SmaxLength ENUMERATED {len2} OPTIONAL, -- Need SscramblingID0 INTEGER (0..65535) OPTIONAL, -- Need SscramblingID1 INTEGER (0..65535) OPTIONAL, -- Need SphaseTrackingRS SetupRelease {PTRS-DownlinkConfig} OPTIONAL, -- Need M…}
[0216] Here, dmrs-Type can set the DMRS type, dmrs-AdditionalPosition can set additional DMRS OFDM symbols, maxLength can set a 1-symbol DMRS pattern or a 2-symbol DMRS pattern, scramblingID0 and scramblingID1 can set scrambling IDs, and phaseTrackingRS can set the PTRS (phase tracking reference signal).
[0217] In addition, the aforementioned uplink DMRS settings can be configured through RRC signaling as shown in [Table 8] below.
[0218] DMRS-UplinkConfig ::= SEQUENCE {dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need Sdmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need RphaseTrackingRS SetupRelease { PTRS-UplinkConfig} OPTIONAL, -- Need MmaxLength ENUMERATED {len2} OPTIONAL, -- Need StransformPrecodingDisabled SEQUENCE {scramblingID0 INTEGER (0..65535) OPTIONAL, -- Need SscramblingID1 INTEGER (0..65535) OPTIONAL, -- Need S…} OPTIONAL, -- Need RtransformPrecodingEnabled SEQUENCE {nPUSCH-Identity INTEGER (0..1007) OPTIONAL, -- Need SsequenceGroupHopping ENUMERATED {disabled} OPTIONAL, -- Need SsequenceHopping ENUMERATED {enabled} OPTIONAL, -- Need S…} OPTIONAL, -- Need R…}
[0219] Here, dmrs-Type can set the DMRS type, dmrs-AdditionalPosition (additional DMRS OFDM symbols) can be set, phaseTrackingRS can set PTRS, and maxLength can set a 1-symbol DMRS pattern or a 2-symbol DMRS pattern. scramblingID0 and scramblingID1 can set scrambling IDs, nPUSCH-Identity can set the cell ID for DFT-s-OFDM, sequenceGroupHopping can disable sequence group hopping, and sequenceHopping can enable sequence hopping.
[0220] FIG. 9 illustrates an example of channel estimation using DMRS received from one PUSCH in the time band of a wireless communication system according to one embodiment of the present disclosure.
[0221] Referring to Fig. 9, when performing channel estimation for data decoding using DMRS, in the frequency band, channel estimation can be performed within the precoding resource block group (PRG), which is the bundling unit, by using physical resource blocks (PRB) bundling linked to the system band. In addition, in the time unit, the channel can be estimated by assuming that only DMRS received from a single PUSCH has the same precoding.
[0222] The following describes the time domain resource allocation (TDRA) method for data channels in a 5G communication system. A base station can set a time domain resource allocation information table for a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) for a terminal using upper layer signaling (e.g., RRC signaling).
[0223] The base station may set up a table for PDSCH consisting of a maximum of maxNrofDL-Allocations = 17 entries, and for PUSCH, a table consisting of a maximum of maxNrofUL-Allocations = 17 entries. Time domain resource allocation information may include, for example, PDCCH-to-PDSCH slot timing (corresponding to a slot-unit time interval between the time when PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0) or PDCCH-to-PUSCH slot timing (corresponding to a slot-unit time interval between the time when PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the position and length of the starting symbol for which PDSCH or PUSCH is scheduled within the slot, and at least one of the mapping type of PDSCH or PUSCH.
[0224] In one embodiment, time domain resource allocation information for PDSCH can be set to the terminal through RRC signaling as shown in [Table 9] below.
[0225] PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0 INTEGER(0..32) OPTIONAL, -- Need SmappingType ENUMERATED {typeA, typeB},startSymbolAndLength INTEGER (0..127)repetitionNumber ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL, -- Cond Formats1-0and1-1}
[0226] Here, k0 represents the PDCCH-to-PDSCH timing (i.e., the slot offset between DCI and its scheduled PDSCH) in slots, mappingType represents the PDSCH mapping type, startSymbolAndLength represents the starting symbol and length of the PDSCH, and repetitionNumber represents the number of PDSCH transmission occasions according to the slot-based repetition method.
[0227] In one embodiment, time domain resource allocation information for PUSCH can be set to the terminal through RRC signaling as shown in [Table 10] below.
[0228] PUSCH-TimeDomainResourceAllocation information elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2 INTEGER(0..32) OPTIONAL, -- Need SmappingType ENUMERATED {typeA, typeB},startSymbolAndLength INTEGER (0..127)}PUSCH-Allocation-r16 ::= SEQUENCE {mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbolAndLength-r16 INTEGER (0..127) OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbol-r16 INTEGER (0..13) OPTIONAL, -- Cond RepTypeBlength-r16 INTEGER (1..14) OPTIONAL, -- Cond RepTypeBnumberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, -- Cond Format01-02…}
[0229] Here, k2 represents the PDCCH-to-PUSCH timing (i.e., the slot offset between DCI and the scheduled PUSCH) in slots, mappingType represents the PUSCH mapping type, startSymbolAndLength or StartSymbol and length represents the starting symbol and length of the PUSCH, and numberOfRepetitions represents the number of repetitions applied to the PUSCH transmission.
[0230] A base station may indicate to a terminal at least one of the entries in a table for time domain resource allocation information via L1 signaling (e.g., downlink control information (DCI)) (e.g., by indicating the 'time domain resource allocation' field within the DCI). Based on the DCI received from the base station, the terminal may obtain time domain resource allocation information for PDSCH or PUSCH.
[0231] The following describes the transmission of the physical uplink shared channel (PUSCH) in a 5G system. PUSCH transmission can be dynamically scheduled by a UL grant within the DCI (e.g., referred to as DG (dynamic grant)-PUSCH) or by a configured grant Type 1 or configured grant Type 2 (e.g., referred to as CG (configured grant)-PUSCH). Dynamic scheduling for PUSCH transmission can be indicated, for example, by DCI format 0_0 or 0_1.
[0232] A PUSCH transmission of a Configured grant Type 1 can be configured semi-statically by receiving a configuredGrantConfig containing the rrc-ConfiguredUplinkGrant of [Table 11] via upper-layer signaling, without receiving a UL grant within the DCI. A PUSCH transmission of a Configured grant Type 2 can be scheduled semi-persistently by a UL grant within the DCI after receiving a configuredGrantConfig that does not contain the rrc-ConfiguredUplinkGrant of [Table 11] via upper-layer signaling.
[0233] In one embodiment, when a PUSCH transmission is scheduled by a configured grant, the parameters applied to the PUSCH transmission may be set through the upper-layer signaling configuredGrantConfig of [Table 11], excluding specific parameters provided by the upper-layer signaling pusch-Config of [Table 11] (e.g., dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, or scaling of UCI-OnPUSCH). For example, if a terminal is provided with a transformPrecoder within the upper-layer signaling configuredGrantConfig of [Table 11], the terminal may apply tp-pi2BPSK within the pusch-Config of [Table 12] to the PUSCH transmission operated by the configured grant.
[0234] ConfiguredGrantConfigConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..17),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym17x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym170x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym17x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym170x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..16),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..16) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1..maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),…} OPTIONAL, -- Need R…}.
[0235] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission may be the same as the antenna port for SRS transmission. PUSCH transmission may follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config of [Table 12], the upper signaling, is 'codebook' or 'nonCodebook'. As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can be semi-statically configured by a configured grant.
[0236] If the terminal is instructed to schedule a PUSCH transmission via DCI format 0_0, the terminal may perform beam configuration for the PUSCH transmission using a pucch-spatialRelationInfoID corresponding to a terminal-specific (UE-specific, dedicated) PUCCH resource having the lowest ID within an active uplink bandwidth part (BWP) in the serving cell. In one embodiment, the PUSCH transmission may be performed based on a single antenna port. The terminal may not expect to schedule a PUSCH transmission via DCI format 0_0 within a BWP where a PUCCH resource containing pucch-spatialRelationInfo is not configured. If the terminal is not configured with txConfig within pusch-Config of [Table 12], the terminal may not expect to be scheduled via DCI format 0_1.
[0237] PUSCH-ConfigPUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S…}.
[0238] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via a configured grant. When the PUSCH transmission is dynamically scheduled via Codebook-based PUSCH DCI format 0_1 or semi-statically configured via a configured grant, the terminal can determine a precoder for the PUSCH transmission based on at least one of the SRS resource indicator (SRI), TPMI (transmission precoding matrix indicator), and transmission rank (number of PUSCH transmission layers).
[0239] According to one embodiment of the present disclosure, the SRI may be provided through the field SRS resource indicator within the DCI or set through the higher-level signaling srs-ResourceIndicator. A terminal may receive at least one SRS resource during codebook-based PUSCH transmission, and, as an example, may receive up to two. When the terminal receives the SRI through the DCI, the SRS resource indicated by the said SRI may refer to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the said SRI. Additionally, the TPMI and transmission rank may be provided through the field precoding information and number of layers within the DCI or set through the higher-level signaling precodingAndNumberOfLayers. The TPMI may be used to indicate the precoder applied to the PUSCH transmission.
[0240] A precoder to be used for PUSCH transmission may be selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config. In codebook-based PUSCH transmission, the terminal may determine the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. In one embodiment, the codebookSubset in the upper signaling pusch-Config may be set to 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the terminal to the base station.
[0241] If the terminal reports 'partialAndNonCoherent' as a UE capability, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports within the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.
[0242] A terminal can receive one SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within that SRS resource set can be indicated via SRI. If multiple SRS resources are configured within the SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', the terminal can expect that the value of nrofSRS-Ports within the upper signaling SRS-Resource will be set to the same value for all SRS resources.
[0243] A terminal transmits one or more SRS resources included in an SRS resource set in which the value of usage is set to 'codebook' according to upper signaling to a base station, and the base station may select one of the SRS resources transmitted by the terminal and instruct the terminal to perform PUSCH transmission using the transmit beam information of the corresponding SRS resource. In one embodiment, in codebook-based PUSCH transmission, an SRI is used as information to select the index of one SRS resource and may be included in a DCI. Additionally, the base station may include information in the DCI that instructs the terminal to use for PUSCH transmission, such as the TPMI and rank, and transmit it. The terminal may perform PUSCH transmission by using the SRS resource instructed by the SRI, applying a precoder instructed by the instructed TPMI and rank based on the transmit beam of the corresponding SRS resource.
[0244] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or can operate semi-statically via a configured grant. If at least one SRS resource is configured within an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive a non-codebook-based PUSCH transmission scheduled via DCI format 0_1.
[0245] For an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive an NZP (non-zero power) CSI-RS resource associated with one SRS resource set. The terminal can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource associated with the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource associated with the SRS resource set and the first symbol of the aperiodic SRS transmission at the terminal is less than a specific number of symbols (e.g., 42 symbols), the terminal may not expect the information for the precoder for SRS transmission to be updated.
[0246] If the value of resourceType within the upper signaling SRS-ResourceSet is set to 'aperiodic', the NZP CSI-RS associated with said SRS-ResourceSet may be indicated by the SRS request field within DCI format 0_1 or 1_1. In one embodiment, if the NZP CSI-RS resource associated with the SRS-ResourceSet is an aperiodic NZP CSI resource and the value of the SRS request field within DCI format 0_1 or 1_1 is not '00', it may indicate the existence of the NZP CSI-RS associated with the SRS-ResourceSet. The said DCI may not indicate cross-carrier or cross-BWP scheduling. If the value of the SRS request indicates the existence of the NZP CSI-RS, said NZP CSI-RS may be located in the slot where the PDCCH containing the SRS request field was transmitted. The TCI states set on the scheduled subcarrier may not be set to QCL-TypeD.
[0247] If a periodic or semi-continuous SRS resource set is configured, the NZP CSI-RS associated with said SRS resource set may be indicated through the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmission, the terminal may not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be configured together.
[0248] When a terminal is configured with multiple SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In one embodiment, the SRI may be indicated via a field SRS resource indicator within the DCI or configured via the srs-ResourceIndicator, which is a higher-level signaling. Similar to the codebook-based PUSCH transmission described above, when the terminal receives the SRI via the DCI, the SRS resource indicated by the SRI may refer to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The terminal may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within a single SRS resource set and the maximum number of SRS resources may be determined by the UE capability reported by the terminal to the base station. SRS resources transmitted simultaneously by the terminal may occupy the same RB. The terminal may configure one SRS port for each SRS resource. Only one SRS resource set can be configured with the value of usage in the upper signaling SRS-ResourceSet set set to 'nonCodebook', and up to four SRS resources can be configured for non-codebook-based PUSCH transmission.
[0249] The base station transmits one NZP CSI-RS associated with an SRS resource set to the terminal, and the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the results measured upon receiving the NZP CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, it applies the calculated precoder, and the base station can select one or more SRS resources from among the received one or more SRS resources. In non-codebook-based PUSCH transmission, the SRI may represent an index capable of expressing a combination of one or more SRS resources, and the SRI may be included within the DCI. The number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the terminal can transmit the PUSCH by applying the precoder applied for SRS resource transmission to each layer.
[0250] The following describes the repetitive transmission of the uplink data channel (PUSCH) and the single TB transmission method through multiple slots in a 5G system. A 5G system can support two types of repetitive transmission methods for the uplink data channel (e.g., PUSCH repetitive transmission type A, PUSCH repetitive transmission type B) and TBoMS (TB processing over multi-slot PUSCH), which transmits a single TB across multiple slots using multiple PUSCHs. Additionally, the terminal can receive a setting for either PUSCH repetitive transmission type A or B through upper-layer signaling. Furthermore, the terminal can transmit TBoMS by receiving 'numberOfSlotsTBoMS' through a resource allocation table.
[0251] PUSCH Repeated Transmission Type A
[0252] - As described above, within a single slot, the start symbol and length of the uplink data channel are determined by the time domain resource allocation method, and the base station can transmit the number of repeated transmissions to the terminal via upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI). To determine the TBS, the number of slots N set by numberOfSlotsTBoMS is 1.
[0253] - Based on the number of repeated transmissions received from the base station, the terminal may repeatedly transmit an uplink data channel in consecutive slots that has the same starting symbol and length as the uplink data channel set above. In one embodiment, in a slot set as downlink by the base station to the terminal, or if at least one of the symbols within the slot for repeated uplink data channel transmission set by the terminal is set as downlink, the terminal may omit the transmission of the uplink data channel in that slot. For example, the terminal may not transmit the uplink data channel within the number of repeated uplink data channel transmissions. On the other hand, a terminal supporting Rel-17 repeated uplink data transmission determines a slot capable of repeated uplink data transmission as an available slot, and can count the number of transmissions when repeating the uplink data channel in a slot determined to be an available slot. If repeated uplink data channel transmission determined to be an available slot is omitted, it may be repeated through a slot capable of transmission after postponement. Using the following [Table 13], a redundancy version can be applied according to the redundancy version pattern set for each nth PUSCH transmission occasion.
[0254] PUSCH Repeated Transmission Type B
[0255] - As described above, within a single slot, the start symbol and length of the uplink data channel are determined by the time domain resource allocation method, and the base station can transmit the number of repetitions (number of repetitions) to the terminal via upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI). In one embodiment, the number of slots N set as numberOfSlotsTBoMS to determine the TBS is 1.
[0256] - First, based on the starting symbol and length of the uplink data channel set above, the nominal repetition of the uplink data channel can be determined as follows. Here, nominal repetition may refer to the symbol resources set by the base station for repeated PUSCH transmission, and the terminal can determine the resources available for uplink use from the set nominal repetition. In this case, the slot where the nth nominal repetition starts is The symbol given by and where nominal repetition starts in the above start slot is It can be given by. The slot where the nth nominal repetition ends is The symbol given by and where the nominal repetition ends in the last slot above is It can be given by.
[0257] Here, n=0,…, numberofrepetitions-1, S represents the starting symbol of the configured uplink data channel, and L represents the symbol length of the configured uplink data channel. indicates the slot where the PUSCH transmission starts. can represent the number of symbols per slot.
[0258] - The terminal can determine invalid symbols for PUSCH repeat transmission type B. Symbols configured for the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated can be determined as invalid symbols for PUSCH repeat transmission type B. Additionally, invalid symbols can be set based on upper layer parameters (e.g., InvalidSymbolPattern). As an example, invalid symbols can be set by the upper layer parameters (e.g., InvalidSymbolPattern) providing a symbol-level bitmap spanning one or two slots. In one embodiment, a value marked as 1 in the bitmap may represent an invalid symbol. Additionally, the period and pattern of the bitmap can be set through upper layer parameters (e.g., periodicityAndPattern). If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal may apply the invalid symbol pattern, and if it indicates 0, it may not apply the invalid symbol pattern. Alternatively, if an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal may apply the invalid symbol pattern.
[0259] - After an invalid symbol is determined in each nominal repetition, the terminal may consider the symbols excluding the determined invalid symbol as valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Here, each actual repetition may refer to a symbol actually used for PUSCH repeat transmission among the symbols set in the above-determined nominal repetition, and may include a continuous set of valid symbols that can be used for PUSCH repeat transmission type B within a single slot. Except when the symbol length L of the configured uplink data channel is 1, the terminal may omit the transmission of the actual repetition if an actual repetition having one symbol is set as valid. Using [Table 13] below, a redundancy version may be applied according to the redundancy version pattern configured for each n-th actual repetition.
[0260] TB processing over multiple slots (TBoMS)
[0261] - As described above, the start symbol and length of the uplink data channel are determined by a time domain resource allocation method within a single slot, and the base station can transmit the number of repeated transmissions to the terminal via upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI). In one embodiment, TBS can be determined using a value of N, which is greater than or equal to 1, the number of slots set by numberOfSlotsTBoMS.
[0262] - Based on the number of slots and the number of repeated transmissions for determining the TBS received from the base station, the terminal may transmit an uplink data channel in consecutive slots that has the same starting symbol and length as the uplink data channel set above. In one embodiment, in a slot set as a downlink by the base station to the terminal, or if at least one of the symbols within the slot for repeated transmission of the uplink data channel set by the terminal is set as a downlink, the terminal may omit the transmission of the uplink data channel in that slot. For example, it may be included in the number of repeated transmissions of the uplink data channel but may not be transmitted.
[0263] On the other hand, a terminal supporting Rel-17 uplink data repeat transmission determines that a slot capable of uplink data repeat transmission is an available slot, and the number of transmissions for the slot determined to be an available slot can be counted during uplink data channel repeat transmission. If the uplink data channel repeat transmission determined to be an available slot is omitted, it can be repeated through a slot that is available for transmission after postponement. In one embodiment, using [Table 13] below, a redundancy version may be applied according to the redundancy version pattern set for each nth PUSCH transmission occasion.
[0264] rv id indicated by the DCI scheduling the PUSCHrv id to be applied to n th transmission occasion (repetition Type A) or TB processing over multiple slots) or n thactual repetition (repetition Type B)((n-(n mod N)) / N) mod 4 = 0((n-(n mod N)) / N) mod 4 = 0((n-(n mod N)) / N) mod 4 = 0((n-(n mod N)) / N) mod 4 = 000231223103310211023
[0265] The following describes a method for determining an uplink available slot for a single or multiple PUSCH transmission in a 5G system.
[0266] According to one embodiment of the present disclosure, when a terminal receives AvailableSlotCounting set to enable, the terminal can determine an available slot based on at least one of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, and TDRA (time domain resource allocation) information field value for Type A PUSCH repeated transmission and TBoMS PUSCH transmission. That is, if at least one symbol set as TDRA for PUSCH in a slot for PUSCH transmission overlaps with at least one symbol for a purpose other than uplink transmission, the slot may be determined as an unavailable slot.
[0267] The following describes a method to reduce SSB density through dynamic signaling for base station energy saving in 5G systems.
[0268] FIG. 10 illustrates a method for resetting SSB transmission through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.
[0269] Referring to FIG. 10, the terminal can receive ssb-PositionsInBurst = '11110000' (1002) from the base station through upper layer signaling (SIB1 or ServingCellConfigCommon). At a subcarrier interval of 30 kHz, up to two synchronization signal blocks can be transmitted within a time of 0.5 ms (or corresponding to the length of one slot if one slot consists of 14 OFDM symbols), and accordingly, the terminal can receive four synchronization signal blocks (SSB) within a time of 1 ms (or corresponding to the length of two slots if one slot consists of 14 OFDM symbols). At this time, the base station can reset the SSB transmission setting information by broadcasting the bitmap '1010xxxx' (1004) through the Group / Cell common DCI (1003) having the nwes-RNTI (network energy saving-Radio Network Temporary Identifier) (or es-RNTI) to reduce the density of SSB transmission for energy saving. At this time, the transmission of SS block #1 (1005) and SS block #3 (1006) can be canceled based on the bitmap (1004) set by the Group / Cell common DCI. FIG. 10 illustrates a method (1001) for resetting SSB transmission through the bitmap-based group / Cell common DCI.
[0270] Additionally, the base station can reset the SSB-periodicity set via upper-layer signaling through the Group / Cell common DCI. Furthermore, by additionally setting Timer information to indicate the application time of the Group / Cell common DCI, the base station can transmit SSBs using the SSB transmission information reset via the Group / Cell common DCI during the set timer. After the timer ends, the base station can operate using the SSB transmission information set via the existing upper-layer signaling. This allows the setting to be switched from normal mode to energy-saving mode via the timer, thereby resetting the SSB configuration information. Alternatively, the base station can set the application time and duration of the SSB configuration information reset via the Group / Cell common DCI to the terminal using Offset and Duration information. In this case, the terminal may not monitor SSBs for the Duration period, starting from the moment the Group / Cell common DCI is received and the moment the Offset is applied.
[0271] The following describes BWP or BW adaptation methods through dynamic signaling for base station energy saving in 5G systems.
[0272] FIG. 11 illustrates a method for resetting BWP and BW through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.
[0273] Referring to FIG. 11, the terminal can operate as an activated BWP or BW through upper layer signaling and L1 signaling from the base station (1101). For example, a fixed power PSD B It can operate via a full 100MHz bandwidth. In this case, the base station uses the same power PSD for energy saving. BWith this, the BW and BWP can be adjusted to enable a narrower BW of 40 MHz for the terminal (1102). At this time, the adjustment operation of the BW or BWP for energy saving of the base station can be set to match the BWP and BW settings specifically set for the UE through the Group common DCI and Cell specific DCI (1103). For example, UE#0 and UE#1 may have different BWP configurations and locations. At this time, the BW and BWP of all terminals can be set to one identically to save energy by reducing the BW used by the base station. At this time, the BWP or BW in the operation for energy saving can be set to one or more, and this can be used to set the BWP per UE Group.
[0274] In describing the present disclosure, the term "upper layer signaling" may refer to a signaling corresponding to at least one or a combination of at least one of the following signalings.
[0275] -MIB (Master Information Block)
[0276] -SIB (System Information Block) or SIB
[0277] -RRC (Radio Resource Control)
[0278] -MAC (Medium Access Control) CE (Control Element)
[0279] In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling.
[0280] -PDCCH (Physical Downlink Control Channel)
[0281] -DCI (Downlink Control Information)
[0282] -Terminal-specific (UE-specific) DCI
[0283] - Group common DCI
[0284] - Common DCI
[0285] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)
[0286] - Non-scheduling DCI (e.g., DCI not intended for scheduling downlink or uplink data)
[0287] -PUCCH (Physical Uplink Control Channel)
[0288] -UCI (Uplink Control Information)
[0289] Additionally, in describing the present disclosure, the term "complex signaling" may refer to a signaling corresponding to a combination of the upper layer signaling and the L1 signaling. As an example of a complex signaling, possible candidate values may be set by RRC or MAC CE in the upper layer signaling, and one of the set possible candidate values may be indicated by the L1 signaling. As another example of a complex signaling, possible values may be set by RRC in the upper layer signaling, candidate values among the possible values may be indicated by MAC CE in the upper layer signaling, and one of the candidate values may be indicated by the L1 signaling.
[0290] In the following disclosure, the above examples are described through a plurality of embodiments, but these are not independent and one or more embodiments may be applied simultaneously or in combination.
[0291] The following describes a DRX alignment method using dynamic signaling for base station energy saving in 5G systems.
[0292] FIG. 12 illustrates a method for resetting DRX through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.
[0293] Referring to FIG. 12, the base station can set the DRX specifically for the UE through upper layer signaling. For example, different drx-LongCycle (1202) or drx-ShortCycle, drx-onDurationTimer (1203), and drx-InactivityTimer (1204) can be set for each terminal. Subsequently, for energy saving, the base station can set the UE-specific DRX settings specifically for the UE group or cell through L1 signaling (1201). Through this, the base station can obtain the same effect for energy saving as the terminal saves power through the DRX.
[0294] The following illustrates an example describing Discontinuous transmission (DTx, DTX) operations to reduce energy consumption of base stations in a 5G system.
[0295] FIG. 13 illustrates an example explaining a DTx method for base station energy saving according to one embodiment of the present disclosure.
[0296] Referring to FIG. 13, the base station can set DTx for energy saving through upper layer signaling (e.g., new system information block (SIB) for DTx or RRC signaling) and L1 signaling (e.g., DCI). At this time, the base station may set a dtx-onDurationTimer (1305) for transmitting a reference signal for measuring RRM measurement, beam management, path loss, etc., for scheduling a DL SCH (shared channel) for DTx operation, a dtx-InactivityTimer (1306) for receiving a PDSCH after receiving a PDCCH for scheduling a DL SCH, a dtx-offset (1304) for setting an offset between the synchronization signal (SS) (1303) for synchronization before the dtx-onDurationTimer and the dtx-onDurationTimer after the SS setting information, and a dtx-(Long)Cycle (1302) for DTx to operate periodically based on the setting information (1301). At this time, the dtx-cycle (1302) may be set to multiple long cycles and short cycles. During DTx operation, the base station considers the transmitter to be off (or inactive) and therefore may not transmit DL CCH, SCH, and DL RS. That is, during DTx operation, the base station may transmit downlink (e.g., PDCCH, PDSCH, RS, etc.) only during SS, dtx-onDurationTimer, and dtx-InactivityTimer. At this time, as additional information for the configured SS, SS-gapbetweenBurst (the gap between SS bursts in the time domain) or the number of SS bursts may be additionally configured.
[0297] The following describes a method for activating a base station via a gNB wake-up signal (WUS) during the base station's inactive mode to reduce energy consumption in a 5G system.
[0298] FIG. 14 illustrates an example explaining the operation of a base station according to a gNB WUS according to one embodiment of the present disclosure.
[0299] Referring to FIG. 14, the base station may keep the transmitter in an Off (or inactive) state during the base station's inactive state (or sleep mode) for energy saving (1401). Subsequently, the base station may receive a gNB WUS (1402) from the terminal to activate the base station's sleep mode. Subsequently, when the base station receives a WUS from the terminal via the Rx terminal, it may change the Tx terminal to an On (or active) state (1403). Subsequently, the base station may perform downlink transmission to the terminal. At this time, the base station may perform synchronization after Tx is turned on and perform Control and Data transmission. In addition, various uplink signals, such as PRACH (physical random access channel), scheduling request (SR PUCCH), PUCCH including Ack, etc., may be considered as gNB WUS. Through the above method, the base station can save energy, and at the same time, the terminal can improve latency.
[0300] At this time, the base station may set a WUS occasion for receiving the gNB WUS and a Sync RS for synchronization before the terminal transmits the gNB WUS. At this time, as the Sync RS, an SSB, TRS (tracking reference signal), Light SSB (PSS+SSS), consecutive SSBs, or new RS (continuous PSS + SSS) may be considered, and as the WUS, a PRACH, PUCCH with SR, or sequence-based signal may be considered. The Sync RS (1404) for the terminal to activate the base station's energy-saving disable mode and the WUS occasion for receiving the WUS may be transmitted repeatedly with WUS-RS periodicity (1405). In the case of FIG. 14, one embodiment is described with an example of a 1-to-1 mapping between the Sync RS and the WUS occasion, but the present disclosure is not limited thereto. For example, the Sync and WUS occasion may be N-to-1 mapped, 1-to-N mapped, or N-to-M mapped.
[0301] The following describes a method for dynamically turning on / off the Spatial domain elements (i.e., Antenna, power amplifier (PA), or TxRUs (transceiver units or transmission radio units)) of a base station to save base station energy in a 5G system.
[0302] FIG. 15 illustrates an antenna adaptation method for energy saving of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0303] Referring to FIG. 15, the base station can adjust the number of Tx antenna ports per RU (radio unit) for network energy savings (NWES) (1501). For example, since the power amplifier (PA) of the base station accounts for most of the base station's energy consumption, the base station can turn off the Tx antenna to save energy. At this time, the base station may refer to / use the terminal's RSRP (reference signal received power), CQI (channel quality indicator), and RSRQ (reference signal received quality) to determine whether the Tx antenna can be turned off. The base station can transmit Tx by adjusting the number of activated Tx antennas per UE group or per UE. At this time, the base station can set information including at least one of beam information or Reference Signal information (e.g., at least one of CSI resource, CSI resource set, or CSI report) according to the antenna on / off to the terminal through upper layer signaling (e.g., RRC signaling) or DCI signaling. In addition, the base station can set different antenna information for each BWP and reset the antenna information in response to changes in the BWP. Furthermore, the base station can receive CSI feedback from the terminal to determine the feasibility of spatial domain (SD) adaptation. The base station can determine SD adaptation (based on the CSI feedback). The base station can receive multiple feedback from the terminal through antenna structure hypotheses of various antenna patterns for SD adaptation.
[0304] More specifically, the base station may apply multiple types of SD adaptation (e.g., two types) for energy saving (1502). For example, the multiple types may include Type 1 SD adaptation (1503) and Type 2 SD adaptation (1504).
[0305] When Type 1 SD adaptation (1503) is applied, the base station can adapt the number of antenna ports while maintaining the number of physical antenna elements per antenna port (i.e., logical port). At this time, the RF characteristics (e.g., tx power, beam) per port can be the same. Therefore, the terminal can combine the CSI-RS of the same port during CSI measurements (e.g., L1-RSRP (layer 1-RSRP), L3-RSRP (layer 3-RSRP), etc.).
[0306] In another way, when Type 2 SD adaptation (1504) is applied, the base station can turn on / off physical antenna elements per port with the same number of antenna ports (i.e., logical ports) (1504). In this case, the RF characteristics per port may differ. During CSI measurement, the terminal can distinguish the CSI-RS of the same port and perform measurements for each. The base station can save energy through one or more of a plurality of types of SD adaptation methods, including the two types of SD adaptation methods mentioned above.
[0307] The following describes a method for a base station to vary SSB transmission for energy saving in a 5G or 6G system. The first case involves a situation in which there is no periodic SSB transmission or there is long-period SSB transmission in a cell (a single serving cell, or a Special Cell such as a P-cell or PS-cell, or an S-cell).
[0308] - Fast time / frequency synchronization and cell ID acquisition or
[0309] - Rapid measurement of channels such as CSI (channel state information) / CQI and reporting to the base station or
[0310] - Changing serving cell / beam through measurement / determination of channel status such as radio link / beam and reporting to the base station or
[0311] - Data transmission and reception through rapid activation of the above cell
[0312] This is a method in which the base station instructs the terminal that an on-demand SSB is being transmitted and transmits the on-demand SSB. In the first method above, since on-demand SSB transmission can be performed only when SSB transmission is required, the energy of the base station can be saved.
[0313] The second method involves changing the period (or adapting the SSB) for SSBs that are periodically transmitted from a single serving cell (or P-cell, PS-cell, or S-cell). For example, the period for the SSB can be changed by setting candidate values for changing the SSB transmission period via a higher-level signal and instructing the terminal to select one of these candidate values. Alternatively, the period for the SSB can be changed by setting multiple SSB configuration information, including the transmission period, via a higher-level signal and instructing the terminal to select one of these configurations. In the second method, the base station's energy can be saved by changing the period to a smaller value to transmit SSBs frequently when SSB transmission is required, and changing the period to a longer value to transmit SSBs infrequently when SSB transmission is not required.
[0314] Unless otherwise specifically noted, the on-demand SSB described below may be received by a terminal capable of receiving on-demand SSB settings and instructions and receiving the on-demand SSB, and the on-demand SSB may be transmitted by a base station capable of transmitting settings and instructions for the on-demand SSB and transmitting the on-demand SSB. Additionally, the SSB adaptation described below may be received by a terminal capable of receiving SSB adaptation settings and instructions and receiving the SSB of the changed period, and the said SSB may be transmitted by a base station capable of transmitting settings and instructions for the SSB adaptation and transmitting the SSB of the changed period.
[0315] The on-demand SSB or SSB adaptation mentioned above may always be supported as an essential function for 6G-capable base stations and 6G-capable terminals in a 6G system.
[0316] First, using FIGS. 16 and 17, a method for setting up and receiving instructions for on-demand SSB transmission for energy saving of the base station and on-demand SSB reception of the terminal in the first method above will be explained.
[0317] FIG. 16 illustrates an example of on-demand SSB operation in a situation where an S-cell (secondary cell, SCell) is set up for a terminal but is not yet activated, according to one embodiment of the present disclosure.
[0318] FIG. 16 illustrates a situation in which an on-demand SSB is transmitted after the terminal has connected to a primary cell (PCell) and the terminal, which has carrier aggregation (CA) capability, receives a setting for an S-cell (or information related to the setting) from a base station and before receiving an activation instruction for the S-cell from the base station. Information regarding the transmission of the on-demand SSB (e.g., a set of information for one on-demand SSB transmission, such as the transmission frequency position, transmission position in the time domain, transmission period, number of transmissions, transmission interval, transmission power, etc.) can be set for the terminal by a higher layer signaling (e.g., an RRC message, etc.). For example, when the above S-cell is set by a higher signal, information regarding the on-demand SSB transmission may be set together (i.e., the terminal may receive a higher signal containing information about the S-cell and information about the on-demand SSB), or it may be set by a separate higher signal apart from the S-cell setting.
[0319] According to one embodiment, the upper signal may include a set of information for one on-demand SSB transmission or a set of information for multiple on-demand SSB transmissions. The upper signal for setting the on-demand SSB itself may indicate on-demand SSB transmission, and a signal (or information) for indicating on-demand SSB transmission may be transmitted from the base station to the terminal separately from the upper signal for setting the on-demand SSB. Hereinafter, the signal for indicating on-demand SSB transmission may correspond to information indicating that the base station transmits the on-demand SSB to the terminal, and may correspond to a signal indicating that transmission has started (or is performed) or information indicating or activating the reception of the on-demand SSB. The signal for indicating on-demand SSB transmission may be another upper signal, a MAC signal, or a physical signal. In the above case, when a set of information for multiple on-demand SSB transmissions is set as a higher signal, the signal indicating an on-demand SSB transmission may indicate a specific on-demand SSB transmission by indicating one of the one or more sets or information.
[0320] According to one embodiment, the always-on SSB may correspond to an SSB defined to always be transmitted in the cell (e.g., cell defining SSB, CD-SSB) and may be configured to be transmitted at least one of a specific frequency position (e.g., a frequency position corresponding to an on-sync raster), a specific period, or a specific time. According to one embodiment, depending on the configuration or by default (i.e., by the specification), the always-on SSB may not correspond to an SSB defined to always be transmitted in the cell. According to one embodiment, the on-demand SSB may correspond to an SSB that is not defined to always be transmitted in the cell (e.g., CD-SSB) (e.g., NCD-SSB or an NCD-SSB transmitted in an off-sync raster, etc.). Alternatively, depending on the configuration or by default (i.e., by the specification), the on-demand SSB may correspond to an SSB defined to be transmitted in the cell (e.g., CD-SSB or a CD-SSB transmitted in an on-sync raster).
[0321] In FIGS. 16 and 17, the downward arrow may indicate a downlink transmitted from the base station to the terminal, and the upward arrow may indicate an uplink transmitted from the terminal to the base station.
[0322] In FIG. 16, Case #1 illustrates a situation where the always-on SSB, which is periodically transmitted, is not transmitted from either the S cell or another reference cell for the S cell (for energy saving of the base station, etc.). In Case #1, rapid S cell activation may not be possible because there is no always-on SSB, which is periodically transmitted for the S cell (which may refer to the synchronization signal blocks described in FIG. 4 to 7, specifically the synchronization signal block that indicates the SIB1 reception resource in the PBCH within the synchronization signal block). In this case, an on-demand SSB may be used to rapidly activate the S cell. In Case #1, the terminal receives an on-demand SSB setting and / or instruction from the base station and can perform a measurement on the S cell by receiving the on-demand SSB. By reporting the channel status to the base station through the on-demand SSB measurement, the terminal or the base station can determine that the S cell is in a known state rather than an unknown state. If an activation instruction for the S-cell is received from the base station, rapid S-cell activation may be possible by receiving either a temporary RS or a CSI-RS QCLed to the on-demand SSB and reporting the corresponding CSI to the base station.
[0323] In FIG. 16, Case #2 illustrates a situation where an always-on SSB, which is transmitted periodically, is transmitted from either the S cell or another reference cell for the S cell. In Case #2, although an always-on SSB is always transmitted for the S cell, it is transmitted at a period too long (e.g., longer than the period for S cell measurement according to one embodiment) (for the sake of energy saving at the base station, etc.), making it difficult for the terminal to measure the S cell based on the always-on SSB, and thus rapid S cell activation may not be possible. At this time, an on-demand SSB according to one embodiment of the present disclosure may be used to rapidly activate the S cell. In Case #2, the terminal receives an on-demand SSB setting and / or instruction from the base station and receives the on-demand SSB to perform a measurement of the S cell. By reporting the channel status to the base station through the on-demand SSB measurement, the terminal or the base station can determine that the S cell is in a known state from an unknown state. If an activation instruction for the S-cell is received from the base station, rapid S-cell activation may be possible by receiving either a temporary RS or a CSI-RS QCLed to the on-demand SSB and reporting the corresponding CSI to the base station.
[0324] FIG. 17 illustrates an example of on-demand SSB operation in a situation where an activation instruction for an S cell (secondary cell, SCell) is received according to an embodiment of the present disclosure.
[0325] FIG. 17 illustrates a situation in which, after a terminal has connected to a P-cell, a terminal having carrier aggregation capability receives a configuration for an S-cell from a base station, and then receives an activation instruction for an S-cell from a base station, an instruction that an on-demand SSB is transmitted is transmitted through a time resource (or time position, same OFDM symbol, or same slot) that is the same time resource as the time resource in which the activation instruction was received. Information regarding on-demand SSB transmission (e.g., a set of information for one on-demand SSB transmission, etc.) including at least one of the transmission frequency position of the on-demand SSB, the transmission position in the time domain, the transmission period, the number of transmissions, the transmission interval, and the transmission power of the on-demand SSB may be configured for the terminal by an upper signal. As an example, when the S-cell is configured by an upper signal, the information regarding the on-demand SSB transmission may be configured together (i.e., the terminal may receive an upper signal containing information about the S-cell and information about the on-demand SSB), or it may be configured by a separate upper signal separated from the S-cell configuration.
[0326] According to one embodiment, the upper signal may include a set of information for one on-demand SSB transmission or a set of information for multiple on-demand SSB transmissions. The upper signal for setting the on-demand SSB itself may indicate on-demand SSB transmission, and a signal indicating on-demand SSB transmission may be transmitted from the base station to the terminal separately from the upper signal for setting the on-demand SSB. The signal indicating on-demand SSB transmission may be another upper signal, a MAC signal, or a physical signal. According to one embodiment, information indicating on-demand SSB transmission may be included in a signal indicating the activation of an S-cell, and the signal indicating on-demand SSB transmission may be a separate signal from the signal indicating the activation of an S-cell. In the above case, when a set of information for multiple on-demand SSB transmissions is set as a higher signal, the signal indicating an on-demand SSB transmission may indicate a specific on-demand SSB transmission by indicating any one of the one or more sets or information.
[0327] In FIG. 17, Case #1 illustrates a situation where the always-on SSB, which is periodically transmitted, is not transmitted from either the S-cell or another reference cell for the S-cell (for energy saving of the base station, etc.). In Case #1, because there is no always-on SSB transmitted periodically for the S-cell (which may refer to the synchronization signal blocks described in FIG. 4 to 7, specifically the synchronization signal block that indicates the SIB1 reception resource in the PBCH within the synchronization signal block), rapid S-cell activation may not be possible even if an activation instruction for the S-cell is received. In this case, an on-demand SSB may be used to rapidly activate the S-cell. In Case #1, the terminal may simultaneously receive an activation instruction for the S-cell and an on-demand SSB instruction from the base station. The terminal can then receive the on-demand SSB and perform a measurement on the S-cell. The terminal may enable rapid S-cell activation by reporting the channel status to the base station through the above-mentioned on-demand SSB measurement, or by receiving either a temporary RS or a CSI-RS QCLed to the above-mentioned on-demand SSB and reporting the corresponding CSI to the base station.
[0328] In FIG. 17, Case #2 illustrates a situation where an always-on SSB, which is transmitted periodically, is transmitted from either the S cell or another reference cell for the S cell. In Case #2, although an always-on SSB is always transmitted for the S cell, it is transmitted at a period that is too long (e.g., longer than the period for S cell measurement according to one embodiment) (for the purpose of energy saving of the base station, etc.). Consequently, even if the terminal receives an activation instruction for the S cell, rapid S cell activation may not be possible because it is difficult for the terminal to measure the S cell based on the always-on SSB. In this case, an on-demand SSB according to one embodiment of the present disclosure may be used to rapidly activate the S cell. In Case #2, the terminal may simultaneously receive an activation instruction for the S cell and an on-demand SSB instruction from the base station. The terminal can then receive the on-demand SSB and perform a measurement of the S cell. Rapid S-cell activation may be possible by reporting the channel status to the base station through the above-mentioned on-demand SSB measurement, or by receiving either a temporary RS or a CSI-RS QCLed to the above-mentioned on-demand SSB and reporting the corresponding CSI to the base station.
[0329] Next, using Fig. 18, the method for setting up SSB adaptation of a terminal for energy saving of a base station in the second method and the method for receiving SSB adaptation instructions will be explained.
[0330] FIG. 18 illustrates an example in which an adaptation of the SSB burst cycle is applied according to one embodiment of the present disclosure.
[0331] In one embodiment of FIG. 18, a situation may be considered in which the base station is set to a higher signal so that it can transmit an SSB burst having a period of 5, 20, or 80 ms by changing it to a higher signal to the terminal.
[0332] At least one of the transmission frequency position of the SSB burst, the transmission position in the time domain, the transmission period, the number of transmissions, the transmission interval, the transmission power, etc., and information regarding SSB burst transmission (e.g., the SSB signal actually transmitted within a single SSB burst and the SSB index, etc.) may be set to the terminal by a higher layer signaling (e.g., SIB, RRC message, etc.). According to one embodiment, the higher layer signal may include a set of information for a single SSB burst transmission or a set of information for a plurality of changeable SSB burst transmission candidates. The higher layer signal for setting the SSB burst itself may indicate SSB transmission, and a signal (or information) for indicating SSB transmission separately from the higher layer signal for setting the SSB may be transmitted from the base station to the terminal. Hereinafter, the signal (or information) for indicating SSB transmission may correspond to information indicating that the base station transmits the SSB to the terminal, and may correspond to a signal indicating that transmission has started (or is performed) or information indicating or activating the reception of the SSB. The signal (or information) indicating the above SSB transmission may be another higher-level signal, a MAC signal, or a physical signal. In the above, when a set of information for multiple SSB transmissions is set as a higher-level signal, the signal indicating the SSB transmission may indicate a specific SSB burst transmission by indicating any one of the one or more sets or information.
[0333] According to one embodiment, the SSB may correspond to an SSB defined to always be transmitted in the cell (e.g., cell defining SSB, CD-SSB), and may be configured to be transmitted at a specific frequency location (e.g., a frequency location corresponding to an on-sync raster), a specific period, or a specific time. According to one embodiment, depending on the configuration or by default (i.e., by the standard), the SSB may not correspond to an SSB defined to always be transmitted in the cell. According to one embodiment, the SSB may correspond to an SSB that is not defined to always be transmitted in the cell (e.g., CD-SSB) (e.g., NCD-SSB or NCD-SSB transmitted in an off-sync raster, etc.). According to one embodiment, depending on the configuration or by default (i.e., by the standard), the SSB may correspond to an SSB defined to be transmitted in the cell (e.g., CD-SSB or CD-SSB transmitted in an on-sync raster).
[0334] In FIG. 18, a terminal that has already camped in a cell or is in connection mode may receive an SSB burst with a period of 20ms from the base station. Accordingly, the terminal may receive an SSB burst from the base station according to the above setting. At this time, the transmission period of the SSB burst with a period of 20ms may be adapted (or changed) to a period of 5ms or 80ms by the judgment of the base station.
[0335] FIG. 19 illustrates an example of a method in which a terminal requests an on-demand SSB from a base station to perform beam failure recovery according to an embodiment of the present disclosure.
[0336] In one embodiment, FIG. 19 describes a situation in which a base station in a single serving cell (or an Sp cell or S cell such as a P cell or PS cell) transmits SSB bursts as a broad beam with a long period (e.g., 160ms or more) through SSB adaptation to save energy. As a method to solve the delay problem required to find a new best beam when recovering a beam failure with the long-period SSB and to find a fine beam optimized for data transmission and reception, a first method is proposed in which a terminal requests an on-demand SSB from the base station to perform beam failure recovery. Meanwhile, specific procedures or methods for beam failure detection and beam failure recovery may be based on the above description.
[0337] FIG. 19 illustrates a situation in which beam sweeping is applied when a base station transmits a synchronization signal as described in FIG. 3. According to one embodiment, the base station always transmits a synchronization signal by beam sweeping with a total of four beams, and the terminal assumes a situation in which the synchronization signal is set as a signal for performing beam failure detection or beam failure recovery.
[0338] In order to reduce the transmission energy of the base station when transmitting a synchronization signal by beam sweeping, a small number of broad beam synchronization signals (for example, 4 in FIG. 19) can be transmitted with a long period. In one embodiment of the present invention, if the terminal does not receive instructions from the base station to reset the period and beam sweeping method of the synchronization signal, the terminal may assume that the synchronization signal is transmitted in the same manner (period, beam sweeping) even after the terminal has completed beam failure detection or beam failure recovery.
[0339] [Method for cases where the serving cell is a single serving cell or an Sp cell such as a P cell or PS cell]
[0340] If the number of accumulated beam failure instances is equal to or greater than the maximum number of beam failure instances (beamFailureInstanceMaxCount) set by the base station as an upper signal, the terminal (or the terminal's MAC layer) may trigger random access (for beam failure recovery) for the serving cell to perform beam failure recovery.
[0341] The terminal (or the terminal's MAC layer) can select an SS / PBCH corresponding to the best candidate beam having an RSRP above a threshold value set by the upper signal, based on a separate SS / PBCH signal set by the upper signal or an SS / PBCH signal received in the previous cycle, for beam failure recovery in the serving cell.
[0342] The terminal (or the terminal's MAC layer) can perform beam failure recovery by performing random access to the base station using a random access preamble corresponding to the SS / PBCH.
[0343] In one embodiment of the present invention, a resource including the random access preamble or the time / frequency for transmitting the random access preamble may include information for a terminal to request an on-demand SSB associated with an SS / PBCH corresponding to the best candidate beam. In one embodiment, the information for requesting the on-demand SSB may be included in a message when there is a transmission from the terminal to the base station during the random access procedure (e.g., msg 3). In one embodiment, a setting for whether to include the information for requesting the on-demand SSB may be received via an upper signal from the base station. For example, the inclusion of the information for requesting the on-demand SSB via the upper signal may be enabled only when the base station is performing an SSB transmission for energy saving, and the terminal may perform the procedure for requesting the on-demand SSB. In one embodiment, if the base station is not performing SSB transmission for energy saving, the inclusion of information requesting an on-demand SSB through the upper signal may be disabled, and at this time, the terminal may perform beam failure recovery by transmitting a random access preamble without information requesting an on-demand SSB and performing random access to the base station.
[0344] FIG. 19 illustrates, as an example, that a terminal selects SS / PBCH #2 as the best candidate beam based on the SS / PBCH signal received in the previous cycle, and includes information requesting on-demand SSBs (OD-SSB #4, #5, #6, #7) associated with said SS / PBCH #2. In one embodiment of the present invention, the QCL relationship between said SS / PBCH and on-demand SSBs can be set in advance through an upper signal from a base station. As an example, FIG. 19 illustrates that SS / PBCH #2 has a QCL relationship with OD-SSB #4, #5, #6, #7, and SS / PBCH #1 has a QCL relationship with OD-SSB #0, #1, #2, #3, and said QCL relationship can be received by the terminal through an upper signal from a base station. To explain the above QCL relationship in detail, SS / PBCHs and OD-SSBs having a QCL relationship may have similar or identical characteristics (quasi co-located) with respect to at least one of the Doppler spread, Doppler shift, average gain, average delay, delay spread, and spatial RX parameter.Accordingly, when a terminal receives a setting / instruction by a higher signal or physical signal that a specific signal and channel (or a reference signal port of the signal and channel) is QCL with the SS / PBCH (or an index of the SS / PBCH), the terminal may assume that the signal and channel is also QCL with respect to at least one of the Doppler spread, Doppler shift, average gain, average delay, delay spread, and spatial RX parameter with respect to the OD-SSB that is in a QCL relationship with the SS / PBCH.
[0345] In one embodiment, a base station may receive a random access attempt from a terminal containing information requesting the on-demand SSB, and transmit the on-demand SSB in response. In FIG. 19, the base station may transmit on-demand SSBs (OD-SSB #4, #5, #6, #7) associated with SS / PBCH #2. In one embodiment of the present invention, the transmission time / frequency resources of the on-demand SSBs may be pre-set by a higher signal.
[0346] In one embodiment, the terminal receives on-demand SSBs from a configured on-demand SSB transmission resource and selects the on-demand SSB corresponding to the best candidate beam for the terminal and reports it to the base station. In one embodiment of the present invention, the terminal may report on-demand SSBs having RSRPs above a threshold value set by an upper signal to the base station in RSRP order, or may report only the on-demand SSB having the largest RSRP among the on-demand SSBs having RSRPs above a threshold value set by an upper signal to the base station.
[0347] In one embodiment, the report on the selected on-demand SSB may be included in a message when there is a transmission from the terminal to the base station during a random access procedure (e.g., msg 3). In one embodiment, the time / frequency resources for reporting on the selected on-demand SSB may be scheduled from the base station or set by a higher signal.
[0348] In one embodiment, a base station may receive information regarding a selected on-demand SSB from a terminal and transmit a response thereto to the terminal. In one embodiment, the response may be included in a message when there is a transmission from the base station to the terminal during a random access procedure (e.g., msg 4). In one embodiment, time / frequency resources for the response may be scheduled from the base station or set by a higher signal. In one embodiment, the response may be a downlink signal from the base station that resets QCL information for data transmission and reception, including at least one of the beams for the reported on-demand SSB.
[0349] In one embodiment, the terminal may receive the above response and determine that beam failure recovery is complete.
[0350] Subsequently, the base station can perform data transmission and reception with the terminal by utilizing beam information for the above-mentioned on-demand SSB. The terminal can determine that a downlink control / data channel from the base station will be transmitted by utilizing at least one of the beams for the above-mentioned reported on-demand SSB.
[0351] [Solution for cases where the serving cell is an S cell]
[0352] If the number of accumulated beam failure instances is equal to or greater than the maximum number of beam failure instances (beamFailureInstanceMaxCount) set by the base station as an upper signal, the terminal (or the terminal's MAC layer) can trigger beam failure recovery for the serving cell.
[0353] When beam failure recovery for the above S cell is triggered, the best candidate beam can be found during the evaluation period defined in the specification by using at least one of the SS / PBCH signal received in the previous cycle or a separate SS / PBCH signal set by the upper signal for beam failure recovery.
[0354] The terminal (or the terminal's MAC layer) can select the SS / PBCH corresponding to the best candidate beam having an RSRP above the threshold value set by the upper signal, based on a separate SS / PBCH signal set by the upper signal or an SS / PBCH signal received in the previous cycle, for beam failure recovery in the serving cell during the evaluation period.
[0355] After finding the best candidate beam, the terminal (or the MAC layer of the terminal) can perform beam failure recovery by transmitting a BFR MAC CE or SR (scheduling request) containing the best beam to the base station.
[0356] In one embodiment of the present invention, the BFR MAC CE or SR may include information that the terminal requests an on-demand SSB associated with the SS / PBCH corresponding to the best candidate beam. In one example, the terminal may use the uplink resource for transmitting the BFR MAC CE only when it is available to the terminal, scheduled in advance by an L1 signal, or set by a higher signal. In one example, if the resource for transmitting the BFR MAC CE is not available to the terminal, the terminal may transmit a scheduling request (SR). In one example, the resource for transmitting the SR may be set in advance to the terminal by a higher signal.
[0357] In one embodiment of the present invention, a setting regarding whether to include information requesting the on-demand SSB can be received through an upper signal from a base station. In one embodiment, the inclusion of information requesting the on-demand SSB through the upper signal can be enabled only when the base station is performing SSB transmission for energy saving, and the terminal can perform the procedure of requesting the on-demand SSB. In one embodiment, when the base station is not performing SSB transmission for energy saving, the inclusion of information requesting the on-demand SSB through the upper signal can be disabled, and at this time, the terminal can perform beam failure recovery by transmitting the BFR MAC CE or SR without information requesting the on-demand SSB.
[0358] FIG. 19 illustrates, as an example, that a terminal selects SS / PBCH #2 as the best candidate beam based on the SS / PBCH signal received in the previous cycle, and includes information requesting on-demand SSBs (OD-SSB #4, #5, #6, #7) associated with said SS / PBCH #2. In one embodiment of the present invention, the QCL relationship between said SS / PBCH and on-demand SSBs can be set in advance through an upper signal from a base station. As an example, FIG. 19 illustrates that SS / PBCH #2 has a QCL relationship with OD-SSB #4, #5, #6, #7, and SS / PBCH #1 has a QCL relationship with OD-SSB #0, #1, #2, #3, and said QCL relationship can be received by the terminal through an upper signal from a base station.
[0359] In one embodiment of the present invention, the BFR MAC CE may include at least one of a bit field containing a serving cell index of the S cell and bit field information requesting an on-demand SSB associated with the SS / PBCH corresponding to the best candidate beam. Additionally, the SR may correspond to one or more logical channels, and each logical channel may be associated with information requesting an on-demand SSB associated with the serving cell index of the S cell and / or the SS / PBCH corresponding to the best candidate beam. In one example, one up control channel per BWP may be configured for the terminal for the SR for beam failure recovery of the S cell.
[0360] In one embodiment, a base station may receive a BFR MAC CE or SR from a terminal containing information requesting the on-demand SSB, and transmit the on-demand SSB in response. In FIG. 19, the base station may transmit on-demand SSBs (OD-SSB #4, #5, #6, #7) associated with SS / PBCH #2. In one embodiment of the present invention, the transmission time / frequency resources of the on-demand SSBs may be pre-set by a higher signal.
[0361] In one embodiment, the terminal receives on-demand SSBs from a configured on-demand SSB transmission resource and selects the on-demand SSB corresponding to the best candidate beam for the terminal and reports it to the base station. In one embodiment of the present invention, the terminal may report on-demand SSBs having RSRPs above a threshold value set by an upper signal to the base station in RSRP order, or may report only the on-demand SSB having the largest RSRP among the on-demand SSBs having RSRPs above a threshold value set by an upper signal to the base station.
[0362] In one embodiment, the report on the selected on-demand SSB may be included when there is a transmission from the terminal to the base station during a random access procedure (e.g., msg 1 or msg 3). In one embodiment, the time / frequency resources for reporting on the selected on-demand SSB may be scheduled from the base station or set by a higher signal.
[0363] In one embodiment, a base station may receive information regarding a selected on-demand SSB from a terminal and transmit a response thereto to the terminal. In one embodiment, the response may be included when there is a transmission from the base station to the terminal during a random access procedure (e.g., msg 2 or msg 4). In one embodiment, the time / frequency resources for the response may be scheduled from the base station or set by a higher signal. In one embodiment, the response may be a downlink signal from the base station that resets QCL information for data transmission and reception, including at least one of the beams for the reported on-demand SSB.
[0364] In one embodiment, the terminal may receive the above response and determine that beam failure recovery is complete.
[0365] Subsequently, the base station can perform data transmission and reception with the terminal by utilizing beam information for the above-mentioned on-demand SSB. The terminal can determine that a downlink control / data channel from the base station will be transmitted by utilizing at least one of the beams for the above-mentioned reported on-demand SSB.
[0366] FIG. 20 illustrates an example of a method in which a terminal requests an on-demand SSB from a base station to perform beam failure recovery according to an embodiment of the present disclosure.
[0367] In one embodiment, FIG. 20 proposes a second method for performing beam failure recovery in which a terminal requests an on-demand SSB from the base station to perform beam failure recovery. This method is used to resolve the delay problem required to find a new best beam when recovering a beam failure with the long-period SSB in a situation where a base station in a single cell (single serving cell, or Sp cell or S cell such as a P cell or PS cell) transmits SSB bursts as a broad beam with a long period (e.g., 160ms or more) through SSB adaptation to save energy, and to find a fine beam optimized for data transmission and reception. Meanwhile, specific procedures or methods for beam failure detection and beam failure recovery may be based on the above description.
[0368] FIG. 20 illustrates a situation in which beam sweeping is applied when a base station transmits a synchronization signal as described in FIG. 3. According to one embodiment, the base station always transmits a synchronization signal by beam sweeping with a total of four beams, and the terminal assumes a situation in which the synchronization signal is set as a signal for performing beam failure detection or beam failure recovery.
[0369] In order to reduce the transmission energy of the base station when transmitting a synchronization signal by beam sweeping, a synchronization signal including a small number of broad beams (for example, 4 in FIG. 20) can be transmitted with a long period. In one embodiment of the present invention, if the terminal does not receive instructions from the base station to reset the period and beam sweeping method of the synchronization signal, the terminal may assume that the synchronization signal is transmitted in the same manner (period, beam sweeping) even after the terminal completes beam failure detection or beam failure recovery.
[0370] [Method for cases where the serving cell is a single serving cell or an Sp cell such as a P cell or PS cell]
[0371] If the number of accumulated beam failure instances is equal to or greater than the maximum number of beam failure instances (beamFailureInstanceMaxCount) set by the base station as an upper signal, the terminal (or the terminal's MAC layer) may request an on-demand SSB (for beam failure recovery) for the serving cell to perform beam failure recovery.
[0372] In one embodiment, unlike the first method in FIG. 19, in the second method of FIG. 20, in addition to the synchronization signal always transmitted for beam failure recovery, an on-demand SSB for at least one additional beam direction is requested, and by receiving the synchronization signal for the additional beam direction in addition to the synchronization signal always transmitted, the terminal can transmit information about the best beam direction for data transmission and reception to the base station and perform data transmission and reception with the base station based on the beam. In one embodiment of FIG. 20, in addition to the synchronization signal having four beam directions always transmitted by the request of the on-demand SSB, a synchronization signal having four other beam directions can be additionally transmitted.
[0373] In one embodiment of the present invention, the upstream transmission for requesting an on-demand SSB may be a random access preamble transmission. A resource including the random access preamble or the time / frequency for transmitting the random access preamble may include information for requesting the on-demand SSB. When selecting a random access preamble for the random access preamble transmission, the terminal (or the MAC layer of the terminal) may select an SS / PBCH corresponding to the best candidate beam having an RSRP above a threshold value set by the upper signal, based on a separate SS / PBCH signal set by the upper signal or an SS / PBCH signal received in the previous cycle, and select a random access preamble corresponding to the SS / PBCH. In one embodiment, if there is no SS / PBCH corresponding to the best candidate beam having an RSRP above a threshold value set by the upper signal, the terminal (or the MAC layer of the terminal) may select a random access preamble corresponding to any SS / PBCH. In one embodiment, the terminal (or the MAC layer of the terminal) can select a random access preamble configured for an on-demand SSB request from the base station.
[0374] In one embodiment, a setting regarding whether to transmit information requesting the above-mentioned on-demand SSB can be received via an upper signal from the base station. In one embodiment, the inclusion of information requesting the on-demand SSB via the upper signal can be enabled only when the base station is performing SSB transmission for energy saving, and the terminal can perform the procedure for requesting the on-demand SSB. In one embodiment, when the base station is not performing SSB transmission for energy saving, the inclusion of information requesting the on-demand SSB via the upper signal can be disabled, and at this time, the terminal can perform beam failure recovery by transmitting a random access preamble without information requesting the on-demand SSB and performing random access to the base station.
[0375] In one embodiment, a base station may receive an uplink transmission from a terminal containing information requesting the on-demand SSB and transmit the on-demand SSB in response thereto. In one embodiment of the present invention, the base station may transmit an additional synchronization signal (having another four beam directions) including a synchronization signal having four beam directions that are always transmitted. In another embodiment, the base station may transmit only the additional synchronization signal (having another four beam directions) excluding the synchronization signal having four beam directions that are always transmitted. In one embodiment, whether to include the synchronization signal that is always transmitted through the on-demand SSB request, the number of beams of the SSB having additional beam directions, and transmission time / frequency resources may be pre-set by an upper signal.
[0376] In one embodiment, the terminal receives on-demand SSBs from a configured on-demand SSB transmission resource and selects the on-demand SSB corresponding to the best candidate beam for the terminal and reports it to the base station. In one embodiment of the present invention, the terminal may report on-demand SSBs having RSRPs above a threshold value set by an upper signal to the base station in RSRP order, or may report only the on-demand SSB having the largest RSRP among the on-demand SSBs having RSRPs above a threshold value set by an upper signal to the base station.
[0377] In one embodiment, the report from the terminal regarding the selected on-demand SSB may be included in a message when there is a transmission from the terminal to the base station during a random access procedure (e.g., msg 1 or msg 3). Alternatively, time / frequency resources for reporting on the selected on-demand SSB may be scheduled from the base station or set by a higher signal.
[0378] In one embodiment, a base station may receive information regarding a selected on-demand SSB from a terminal and transmit a response thereto to the terminal. In one embodiment, the response may be included in a message when there is a transmission from the base station to the terminal during a random access procedure (e.g., msg2 or msg4). Alternatively, time / frequency resources for the response may be scheduled by the base station or set by a higher signal. In one embodiment, the response may be a downlink signal from the base station that resets QCL information for data transmission and reception, including at least one of the beams for the reported on-demand SSB.
[0379] In one embodiment, the terminal may receive the above response and determine that beam failure recovery is complete.
[0380] Subsequently, the base station can perform data transmission and reception with the terminal by utilizing beam information for the above-mentioned on-demand SSB. The terminal can determine that a downlink control / data channel from the base station will be transmitted by utilizing at least one of the beams for the above-mentioned reported on-demand SSB.
[0381] In one embodiment of the present invention, a base station receives information about an on-demand SSB selected from a terminal and can change a synchronization signal that is always transmitted, including at least one of the beams for the reported on-demand SSB, and a reset down channel / signal including information on the change of the synchronization signal that is always transmitted is transmitted from the base station and can be received by the terminal.
[0382] [Solution for cases where the serving cell is an S cell]
[0383] If the number of accumulated beam failure instances is equal to or greater than the maximum number of beam failure instances (beamFailureInstanceMaxCount) set by the base station as an upper signal, the terminal (or the terminal's MAC layer) can trigger beam failure recovery for the serving cell.
[0384] In one embodiment, when beam failure recovery for the S cell is triggered, unlike the first method in FIG. 19, the second method in FIG. 20 requests at least one additional beam direction on-demand SSB in addition to the synchronization signal always transmitted for beam failure recovery, and by using the synchronization signal for the additional beam direction in addition to the synchronization signal always transmitted, the best candidate beam can be found during the evaluation period defined in the specification.
[0385] In one embodiment of the present invention, the upstream transmission for requesting an on-demand SSB may be a random access preamble transmission. A resource including the random access preamble or the time / frequency for transmitting the random access preamble may include information for requesting the on-demand SSB. When selecting a random access preamble for the random access preamble transmission, the terminal (or the MAC layer of the terminal) may select an SS / PBCH corresponding to the best candidate beam having an RSRP above a threshold value set by the upper signal based on at least one of a separate SS / PBCH signal set by the upper signal or an SS / PBCH signal received in the previous cycle, and select a random access preamble corresponding to the SS / PBCH. In one embodiment, if there is no SS / PBCH corresponding to the best candidate beam having an RSRP above a threshold value set by the upper signal, the terminal (or the MAC layer of the terminal) may select a random access preamble corresponding to any SS / PBCH. In one embodiment, the terminal (or the MAC layer of the terminal) can select a random access preamble configured for an on-demand SSB request from the base station.
[0386] In one embodiment, a setting regarding whether to transmit information requesting the above-mentioned on-demand SSB can be received through an upper signal from the base station. In one embodiment, the inclusion of information requesting the on-demand SSB through the upper signal can be enabled only when the base station is performing SSB transmission for energy saving, and the terminal can perform the procedure of requesting the on-demand SSB. In one embodiment, when the base station is not performing SSB transmission for energy saving, the inclusion of information requesting the on-demand SSB through the upper signal can be disabled, and at this time, without information requesting the on-demand SSB, the terminal (or the terminal's MAC layer) can perform beam failure recovery by finding the best candidate beam and then transmitting a BFR MAC CE or SR (scheduling request) containing the best beam to the base station.
[0387] In one embodiment, a base station receives an uplink transmission from a terminal containing information requesting the on-demand SSB, and can transmit the on-demand SSB in response thereto. FIG. 20 illustrates the additional transmission of a synchronization signal having four different beam directions in addition to a synchronization signal having four beam directions that is always transmitted in response to a request for the on-demand SSB.
[0388] In one embodiment of the present invention, a base station may transmit additional synchronization signals (having other four beam directions), including a synchronization signal having four beam directions that are always transmitted. In another embodiment, the base station may transmit only additional synchronization signals (having other four beam directions), excluding the synchronization signal having four beam directions that are always transmitted. Whether to include the synchronization signal that is always transmitted, the number of beams of the SSB having additional beam directions, and transmission time / frequency resources may be pre-set by the upper signal through the on-demand SSB request.
[0389] In one embodiment, the terminal receives on-demand SSBs from a configured on-demand SSB transmission resource and can select the on-demand SSB corresponding to the best candidate beam for the terminal and report it to the base station. In one embodiment of the present invention, the terminal can report on-demand SSBs having an RSRP above a threshold value set by an upper signal to the base station in RSRP order, and can report only the on-demand SSB having the largest RSRP among the on-demand SSBs having an RSRP above the threshold value set by the upper signal to the base station.
[0390] In one embodiment, the terminal (or the MAC layer of the terminal) can perform beam failure recovery by transmitting at least one of a BFR MAC CE or SR (scheduling request) containing the best candidate beam to the base station as a method of reporting the best candidate beam to the base station.
[0391] In one embodiment of the present invention, the terminal may use the uplink resource for transmitting the above BFR MAC CE only when it is available to the terminal, scheduled in advance by an L1 signal, or set by an upper signal. In one example, if the resource for transmitting the above BFR MAC CE is not available to the terminal, the terminal may transmit a scheduling request (SR). In one example, the resource for transmitting the above SR may be set to the terminal in advance by an upper signal.
[0392] Figure 20 illustrates, as an example, that a terminal selects one SSB as the best candidate beam based on an on-demand SSB signal and transmits it to a base station.
[0393] In one embodiment of the present invention, the BFR MAC CE may include bit field information including at least one of a bit field containing a serving cell index of an S cell and information regarding an SSB corresponding to the best candidate beam. Additionally, the SR may correspond to one or more logical channels, and each logical channel may be associated with the serving cell index of the S cell and / or information regarding an SSB corresponding to the best candidate beam. In one example, for the SR for beam failure recovery of the S cell, one up control channel per BWP may be configured for the terminal.
[0394] In one embodiment, a base station may receive at least one of BFR MAC CE or SR containing the above information from a terminal and transmit a response thereto. In one embodiment of the present invention, the transmission time / frequency resources for the response may be pre-set by a higher signal.
[0395] In one embodiment, the above response may be a downlink signal from a base station that resets QCL information for data transmission and reception, including at least one of the beams for the above-mentioned on-demand SSB.
[0396] In one embodiment, the terminal may receive the above response and determine that beam failure recovery is complete.
[0397] Subsequently, the base station can perform data transmission and reception with the terminal by utilizing beam information for the reported SSB. The terminal can determine that a downlink control / data channel from the base station will be transmitted by utilizing at least one of the beams for the reported SSB.
[0398] FIG. 21 is a flowchart of terminal operations applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.
[0399] Various modifications may be made to the method illustrated in the flowchart of FIG. 21. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0400] Based on Fig. 21, a method is described in which a terminal requests an on-demand SSB from a base station to perform beam failure recovery during an SSB transmission operation following an SSB change for energy saving.
[0401] Referring to FIG. 21, in step 2101, according to an embodiment of the present invention, the terminal may receive from a base station at least one of a setting for SSB adaptation, a setting related to an on-demand SSB request, and a setting related to beam failure detection (BFD) / beam failure recovery (BFR). The setting for SSB adaptation may include information regarding resources for transmitting SSB, and may include at least one of a plurality of period information and period information to be applied in order to change the period of the SSB. Specific details are the same as those described above and are therefore omitted below.
[0402] In step 2102, according to an embodiment of the present invention, the terminal can trigger beam failure recovery (BFR).
[0403] In step 2103, according to an embodiment of the present invention, the terminal may request an on-demand SSB from the base station.
[0404] In step 2104, according to an embodiment of the present invention, the terminal can perform beam failure recovery based on the on-demand SSB transmitted by the base station.
[0405] Specific details of the terminal operation according to one embodiment of the present disclosure described above may be referenced to the description of one embodiment of the present disclosure described above.
[0406] FIG. 22 is a flowchart of base station operations applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.
[0407] Various modifications may be made to the method illustrated in the flowchart of FIG. 22. For example, although it is illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0408] Referring to FIG. 22, in step 2201, according to an embodiment of the present invention, a base station may transmit to a terminal at least one of a setting for SSB adaptation, a setting related to an on-demand SSB request, and a setting related to beam failure detection / beam failure recovery. The setting for SSB adaptation may include information regarding resources for transmitting SSB, and may include at least one of a plurality of period information and period information to be applied in order to change the period of the SSB. Specific details are the same as those described above and are therefore omitted below.
[0409] In step 2202, according to an embodiment of the present invention, the base station may receive a request for an on-demand SSB from a terminal and transmit the on-demand SSB to the terminal. Subsequently, the base station may transmit feedback to the terminal regarding the recovery of the terminal's beam failure.
[0410] Specific details of the base station operation according to one embodiment of the present disclosure described above may be referenced to the description of one embodiment of the present disclosure described above.
[0411] The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0412] FIG. 23 is a block diagram of a terminal (2300) according to one embodiment of the present disclosure.
[0413] The terminal (2300) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things devices having various form factors, etc., and can perform wireless communication with a base station through a wireless channel.
[0414] Referring to FIG. 23, the terminal (2300) may include at least one transceiver (2301) (hereinafter, transceiver), at least one processor (2302) (hereinafter, processor), and at least one memory (2303) (hereinafter, memory). The transceiver (2301), processor (2302), and memory (2303) of the terminal (2300) may operate according to at least one or a combination thereof of the methods corresponding to the above-described embodiments. However, the components of the terminal (2300) are not limited to the examples of components shown in FIG. 23. In other embodiments, the terminal (2300) may include additional components such as the above-described components or omit some components. Also, in some embodiments, the transceiver (2301), processor (2302), or memory (2303) may be integrated into a single chip.
[0415] The transceiver (2301) may be a communication circuit or communication circuitry that enables the terminal (2300) to transmit and receive signals to and from a base station via cellular wireless communication. For example, the transceiver (2301) may support at least one of various cellular wireless communication technologies including 3G, 4G LTE (long-term evolution), 5G NR (new radio), 6G, etc., and may include all subsequent generations of wireless communication.
[0416] According to one embodiment, the terminal (2300) may include a plurality of transceivers, and if it supports EN-DC (E-UTRA-NR Dual Connectivity), it may include a first transceiver that supports 4G LTE wireless communication and a second transceiver that supports 5G NR wireless communication. According to another embodiment, if the terminal (2300) supports NR-DC (NR Dual Connectivity), the terminal (2300) may include a plurality of transceivers that support 5G NR wireless communication. According to another embodiment, if the terminal (2300) supports short-range wireless communication, the terminal (2300) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth, wireless LAN, or WLAN networks (including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be).
[0417] According to one embodiment, the transceiver (2301) may include various circuit structures used to transmit and receive signals to and from a base station via a wireless channel. The signals may include control information and data. For example, the transceiver (2301) may be configured to include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (2301) may output the signal received via the wireless channel to a processor (2302) and transmit the signal output from the processor (2302) via the wireless channel.
[0418] The processor (2302) can control the overall operation of the terminal (2300) according to the embodiments of the present disclosure described above. The processor (2302) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (2302) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (2303) individually, collectively, or in any combination. Additionally, the processor (2302) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.
[0419] The processor (2302) is electrically, operatively, or communicatively coupled to the transceiver (2301) so as to control the transceiver (2301).
[0420] The processor (2302) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (2302) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (2302) may be included in one chip, and another part of the processor (2302) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (2301) or a memory (2303).
[0421] The processor (2302) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (2302) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (2302) may control other components of the terminal (2300) to perform various operations by executing computer programs, code, or instructions stored in memory (2303).
[0422] Memory (2303) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (2303) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0423] The memory (2303) can be electrically, operatively, or communically coupled with the processor (2302) and can be accessed by the processor (2302).
[0424] A computer program, code, or instruction that can be executed by a processor (2302) may be stored in the memory (2303). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (2302) may be stored in a single memory or separated and distributed across two or more memories. The processor (2302) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (2303).
[0425] The operation of a terminal according to an exemplary embodiment of the present disclosure may be performed individually, collectively, or in any combination of at least one processor, a processing circuitry that does not execute instructions, or a component of a processing circuitry that does not execute instructions, through computer programs, codes, or instructions stored in memory (2303).
[0426] FIG. 24 is a block diagram of a base station (2400) according to one embodiment of the present disclosure.
[0427] The base station (2400) can perform wireless communication with at least one terminal within the area of the base station (2400) through a wireless channel.
[0428] Referring to FIG. 24, a base station (2400) may include at least one transceiver (2401) (hereinafter, transceiver), at least one processor (2402) (hereinafter, processor), and at least one memory (2403) (hereinafter, memory). The transceiver (2401), processor (2402), and memory (2403) of the base station (2400) may operate according to at least one or a combination thereof of the methods corresponding to the above-described embodiments. However, the components of the base station (2400) are not limited to the examples of components shown in FIG. 24. In other embodiments, the base station (2400) may include additional components in addition to the above-described components or omit some components. Also, in some embodiments, the transceiver (2401), processor (2402), or memory (2403) may be integrated into a single chip.
[0429] The transceiver (2401) may be a communication circuit or communication circuitry that enables the base station (2400) to transmit and receive signals to and from the terminal (2300) via cellular wireless communication. For example, the transceiver (2401) may support various cellular wireless communication technologies including 3G, 4G LTE (long-term evolution), 5G NR (new radio), 6G, etc., and may include all subsequent generations of wireless communication. According to one embodiment, the transceiver (2401) may include various circuit structures used to transmit and receive signals to and from the terminal via a wireless channel. The signals may include control information and data. For example, the transceiver (2401) may be configured to include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (2401) can output a signal received through a wireless channel to a processor (2402) and transmit a signal output from the processor (2402) through a wireless channel.
[0430] The processor (2402) can control the overall operation of the base station (2400) according to the embodiments of the present disclosure described above. The processor (2402) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (2402) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (2403) individually, collectively, or in any combination. Additionally, the processor (2402) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.
[0431] The processor (2402) is electrically, operatively, or communicatively coupled to the transceiver (2401) so as to control the transceiver (2401).
[0432] The processor (2402) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (2402) may be included in one chip, and another part of the processor (2402) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a transceiver (2401) or memory (2403).
[0433] The processor (2402) may perform, cause, or control the operation of a base station to perform at least one or a combination of the methods according to the embodiments of the present disclosure. For example, the processor (2402) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (2402) may control other components of the base station (2400) to perform various operations by executing computer programs, codes, and instructions stored in memory (2403).
[0434] Memory (2403) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (2403) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0435] The memory (2403) can be electrically, operatively, or communically coupled with the processor (2402) and can be accessed by the processor (2402).
[0436] A computer program, code, or instruction that can be executed by a processor (2402) may be stored in the memory (2403). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (2402) may be stored in a single memory or separated and distributed across two or more memories. The processor (2402) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (2403).
[0437] The operation of a base station according to an embodiment of the present disclosure may be performed individually, collectively, or in any combination of at least one processor, a processing circuitry that does not execute instructions, or a component of a processing circuitry that does not execute instructions, through computer programs, codes, or instructions stored in memory (2403).
[0438] In one embodiment of the present disclosure, a base station in a wireless communication system can transmit a synchronization signal to a terminal.
[0439] In one embodiment of the present disclosure, a base station in a wireless communication system may receive request information from a terminal requesting an on-demand synchronization signal block (SSB) associated with the synchronization signal.
[0440] In one embodiment of the present disclosure, a base station in a wireless communication system may transmit at least one on-demand SSB to a terminal in response to the request information.
[0441] In one embodiment of the present disclosure, a base station in a wireless communication system may receive a message from a terminal reporting an on-demand SSB selected from the terminal among the at least one on-demand SSB.
[0442] In one embodiment of the present disclosure, a base station in a wireless communication system can transmit quasi-co-located (QCL) relationship information between the synchronization signal and the at least one on-demand SSB to a terminal.
[0443] In one embodiment of the present disclosure, the QCL relationship information may be characteristic information related to at least one of the Doppler spread, Doppler shift, average gain, average delay, delay spread, and spatial RX parameter of the synchronization signal and the at least one on-demand SSB.
[0444] In one embodiment of the present disclosure, when the serving cell of a terminal is a single serving cell or a primary cell, and the terminal detects a beam failure, the request information may correspond to a candidate beam having a reference signal received power (RSRP) above a threshold value set by the upper signal, based on a separate synchronization signal set by the upper signal or a synchronization signal transmitted to the terminal in the previous cycle.
[0445] In one embodiment of the present disclosure, when the serving cell of the terminal is a secondary cell (S cell) and the terminal detects a beam failure, the request information may correspond to a candidate beam having a reference signal received power (RSRP) that is above a threshold value set by the upper signal during an evaluation interval, based on a separate synchronization signal set by the upper signal or a synchronization signal transmitted to the terminal in the previous cycle.
[0446] In one embodiment of the present disclosure, the request information may consist of a beam failure recovery (BFR) MAC-CE (medium access control - control element) or a scheduling request (SR).
[0447] In one embodiment of the present disclosure, a base station in a wireless communication system may transmit a response signal to a terminal in response to the message.
[0448] In one embodiment of the present disclosure, the response signal may be a signal that resets quasi-co-located (QCL) relationship information based on at least one of the beams for an on-demand SSB selected from the terminal.
[0449] In one embodiment of the present disclosure, request information may be included in a random access signal.
[0450] In one embodiment of the present disclosure, a terminal in a wireless communication system can receive a synchronization signal from a base station.
[0451] In one embodiment of the present disclosure, a terminal in a wireless communication system may transmit request information to a base station requesting an on-demand synchronization signal block (SSB) associated with the synchronization signal.
[0452] In one embodiment of the present disclosure, a terminal in a wireless communication system may receive at least one on-demand SSB from a base station in response to the request information.
[0453] In one embodiment of the present disclosure, a terminal in a wireless communication system can select an on-demand SSB among the at least one on-demand SSB.
[0454] In one embodiment of the present disclosure, a terminal in a wireless communication system may transmit a message reporting a selected on-demand SSB to the base station.
[0455] In one embodiment of the present disclosure, the step of selecting an on-demand SSB may include selecting an on-demand SSB having a reference signal received power (RSRP) above a threshold value.
[0456] In one embodiment of the present disclosure, a terminal in a wireless communication system may receive quasi-co-located (QCL) relationship information between the synchronization signal and the at least one on-demand SSB from a base station.
[0457] In one embodiment of the present disclosure, the QCL relationship information may be characteristic information related to at least one of the Doppler spread, Doppler shift, average gain, average delay, delay spread, and spatial RX parameter of the first synchronization signal and the at least one on-demand SSB.
[0458] In one embodiment of the present disclosure, when the serving cell of a terminal is a single serving cell or a primary cell, and the terminal detects a beam failure, the request information may correspond to a candidate beam having a reference signal received power (RSRP) above a threshold value set by the upper signal, based on a separate synchronization signal set by the upper signal or a synchronization signal transmitted to the terminal in the previous cycle.
[0459] The drawings illustrate different examples of user devices / base stations, but various modifications to the drawings may be made. For example, a user device / base station may include any number of individual components in any suitable arrangement. In general, the drawings do not limit the scope of the disclosure to any specific configuration. Furthermore, while the drawings illustrate operating environments in which various user device / base station features disclosed in this patent document may be used, these features may be used in any other suitable system.
[0460] Although the present disclosure has been described by exemplary embodiments, various changes and modifications may be presented to those skilled in the art. The present disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any specific element, step, or function is an essential element to be included in the claims. The scope of the patented subject matter is defined by the claims.
[0461] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.
Claims
1. In a method performed by a base station in a wireless communication system, A step of transmitting a synchronization signal to a terminal; A step of receiving request information from the terminal requesting an on-demand synchronization signal block (SSB) associated with the synchronization signal; A step of transmitting at least one on-demand SSB to the terminal in response to the request information; and A method comprising the step of receiving a message from the terminal reporting an on-demand SSB selected from the terminal among at least one on-demand SSB.
2. In Paragraph 1, A method further comprising the step of transmitting QCL (quasi co-located) relationship information between the synchronization signal and the at least one on-demand SSB to the terminal.
3. In Paragraph 2, The above QCL relationship information is characteristic information related to at least one of the Doppler spread, Doppler shift, average gain, average delay, delay spread, and spatial RX parameter of the synchronization signal and at least one on-demand SSB.
4. In the case of paragraph 1, where the serving cell of the terminal is a single serving cell or a primary cell, if the terminal detects a beam failure, the request information is, A method corresponding to a candidate beam having a reference signal received power (RSRP) above a threshold value set by the upper signal, based on a separate synchronization signal set by the upper signal or a synchronization signal transmitted to the terminal in the previous cycle.
5. In the case of paragraph 1, where the serving cell of the terminal is an S-cell (secondary cell) and the terminal detects a beam failure, the request information is, A method corresponding to a candidate beam having a reference signal received power (RSRP) above a threshold value set by the upper signal during an evaluation interval, based on a separate synchronization signal set by the upper signal or a synchronization signal transmitted to the terminal in the previous cycle.
6. A method according to paragraph 5, wherein the request information consists of a beam failure recovery (BFR) MAC-CE (medium access control - control element) or a scheduling request (SR).
7. In Paragraph 1, The method further includes the step of transmitting a response signal to the terminal that responds to the message. A method in which the above response signal is a signal that resets QCL (quasi co-located) relationship information based on at least one of the beams for the on-demand SSB selected from the terminal.
8. In paragraph 1, the method wherein the request information is included in a random access signal.
9. In a method performed by a terminal in a wireless communication system, A step of receiving a synchronization signal from a base station; A step of transmitting request information to the base station requesting an on-demand synchronization signal block (SSB) associated with the synchronization signal; A step of receiving at least one on-demand SSB from the base station in response to the request information; A step of selecting an on-demand SSB among the at least one on-demand SSB; and A method comprising the step of transmitting a message reporting the selected on-demand SSB to the base station.
10. In claim 9, the step of selecting the on-demand SSB is, A method comprising the step of selecting an on-demand SSB having a reference signal received power (RSRP) above a threshold value.
11. In Paragraph 9, A method further comprising the step of receiving quasi-co-located (QCL) relationship information between the synchronization signal and at least one on-demand SSB from the base station.
12. In Paragraph 11, The above QCL relationship information is characteristic information related to at least one of the Doppler spread, Doppler shift, average gain, average delay, delay spread, and spatial RX parameter of the first synchronization signal and the at least one on-demand SSB.
13. In paragraph 9, where the serving cell of the terminal is a single serving cell or a primary cell, if the terminal detects a beam failure, the request information is, A method corresponding to a candidate beam having a reference signal received power (RSRP) above a threshold value set by the upper signal, based on a separate synchronization signal set by the upper signal or a synchronization signal transmitted to the terminal in the previous cycle.
14. In a base station of a wireless communication system, Transmitter / receiver; and It includes at least one processor; and said at least one processor, Transmit a synchronization signal to the terminal, and Receiving request information from the above terminal requesting an on-demand synchronization signal block (SSB) associated with the synchronization signal, and To the above terminal, in response to the request information, at least one on-demand SSB is transmitted, and A base station configured to receive a message from the terminal reporting an on-demand SSB selected from the terminal among at least one on-demand SSB.
15. In a terminal of a wireless communication system, Transmitter / receiver; and It includes at least one processor; and said at least one processor, Receive a synchronization signal from the base station, and Transmitting request information to the above base station requesting an on-demand synchronization signal block (SSB) associated with the synchronization signal, and From the base station, at least one on-demand SSB is received in response to the request information, and Among the above at least one on-demand SSB, select an on-demand SSB, and A terminal configured to transmit a message reporting the selected on-demand SSB to the base station.
