Method and apparatus for uplink power control based on on-demand SSB in a wireless communication system

The on-demand SS/PBCH block method optimizes uplink power control in wireless systems, addressing inefficiencies in high-frequency bands by dynamically adjusting transmission power, enhancing connectivity and performance.

WO2026235325A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005781
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-04-03
Filing Date
2026-04-30
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing uplink power control, particularly in high-frequency bands like mmWave and terahertz bands, to support enhanced services and increased device connectivity, especially for devices with varying power consumption and coverage needs.

Method used

Implementing on-demand synchronization signal and physical broadcast channel block (SS/PBCH block or SSB) for dynamic power control, allowing devices to request and adjust transmission based on specific configurations and beamforming techniques.

Benefits of technology

Enhances power efficiency and coverage by optimizing power usage based on demand, supporting higher frequency bands and increased device connectivity with reduced latency and improved network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005781_12112026_PF_FP_ABST
    Figure KR2026005781_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Apparatuses and methods for uplink power control based on on-demand synchronization signal block (SSB). A method performed by a user equipment includes receiving a set of higher layer parameters for a secondary cell (SCell) and identifying, based on the set of higher layer parameters, first and second configurations for first and second synchronization signal and physical broadcast channel (SS / PBCH) blocks, respectively, the first and second configurations including, first and second frequency locations for the first and second SS / PBCH blocks, respectively, and first and second indications of first and second sets of actually transmitted SS / PBCH block indexes for the first and second SS / PBCH block, respectively. The method further includes determining a SS / PBCH block index to be associated with a transmission control information (TCI) state and determining, when applying the TCI state, that transmission of the second SS / PBCH block corresponding to the SS / PBCH block index is not deactivated.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR UPLINK POWER CONTROL BASED ON ON-DEMAND SSB IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure is related to a method and apparatus for uplink power control based on on-demand synchronization signal and / or physical broadcast channel block (SS / PBCH block or SSB) in a wireless communication system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure is related to a method and apparatus for uplink power control based on on-demand synchronization signal and / or physical broadcast channel block (SS / PBCH block or SSB) in a wireless communication system.

[0009] According to an aspect of an exemplary embodiment, there is provided a communication method in a wireless communication system.

[0010] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0011] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0012] FIG. 1 illustrates an example wireless network according to embodiments of the present disclosure;

[0013] FIG. 2 illustrates an example BS according to embodiments of the present disclosure;

[0014] FIG. 3 illustrates an example UE according to embodiments of the present disclosure;

[0015] FIGS. 4A and 4B illustrate an example of a wireless transmit and receive paths according to embodiments of the present disclosure;

[0016] FIG. 5 illustrates an example method performed by a UE in a wireless communication system according to embodiments of the present disclosure;

[0017] FIG. 6 illustrates an example of an on-demand SS / PBCH block (OD-SSB) based operation using a different beam according to embodiments of the present disclosure;

[0018] FIG. 7 illustrates an example method performed by a UE in a wireless communication system according to embodiments of the present disclosure;

[0019] FIG. 8 is a block diagram of a terminal or user equipment (UE) according to an embodiment of the disclosure.

[0020] FIG. 9 is a block diagram of a base station (BS) according to an embodiment of the disclosure.

[0021] FIG. 10 is a block diagram of a network entity according to an embodiment of the disclosure.

[0022] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0023] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0024] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0025] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0026] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0027] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0028] As used in embodiments of the disclosure, a “~unit” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit” does not always have a meaning limited to software or hardware. The “~unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit” may be either combined into a smaller number of components and a “~unit,” or divided into additional components and a “~unit.” Moreover, the components and “~units” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit” may include one or more processors.

[0029] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0030] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural 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, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio 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 the like.

[0031] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0032] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0033] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0034] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0035] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0036] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0037] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0038] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0039] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0040] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0041] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0042] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0043] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0044] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0045] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure.

[0046] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0047] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0048] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0049] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0050] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0051] The drawings or flowcharts described below illustrate exemplary methods that may be implemented according to 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, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0052] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0053] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0054] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) where appropriate.

[0055] Hereinafter, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a BS controller, or a node on a network.

[0056] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0057] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.

[0058] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a UE, and an uplink (UL) refers to a radio link through which a UE transmits a signal to a BS.

[0059] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0060] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0061] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling.

[0062] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0063] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0064] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0065] The present application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 63 / 801,449 filed on May 7, 2025; U.S. Provisional Patent Application No. 63 / 863,063 filed on August 13, 2025; U.S. Provisional Patent Application No. 63 / 906,803 filed on October 28, 2025; U.S. Provisional Patent Application No. 63 / 929,295 filed on December 2, 2025; and U.S Non-Provisional Patent Application No. 19 / 639,026 filed on April 3, 2026, which are hereby incorporated by reference in their entirety.

[0066] Wireless communication has been one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeded five billion and continues to grow quickly. The demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, “note pad” computers, net books, eBook readers, and machine type of devices. In order to meet the high growth in mobile data traffic and support new applications and deployments, improvements in radio interface efficiency and coverage are of paramount importance.

[0067] The present disclosure relates to a method and apparatus for uplink power control based on on-demand SSB.

[0068] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes a transceiver configured to receive a set of higher layer parameters for a secondary cell (SCell) and a processor operably coupled to the transceiver. The processor is configured to identify, based on the set of higher layer parameters a first configuration for a first synchronization signal and physical broadcast channel (SS / PBCH) block, the first configuration including a first frequency location for the first SS / PBCH block and a first indication of a first set of actually transmitted SS / PBCH block indexes for the first SS / PBCH block, and a second configuration for a second SS / PBCH block, the second configuration including a second frequency location for the second SS / PBCH block and a second indication of a second set of actually transmitted SS / PBCH block indexes for the second SS / PBCH block; determine a SS / PBCH block index to be associated with a transmission control information (TCI) state; and determine, when applying the TCI state, that transmission of the second SS / PBCH block corresponding to the SS / PBCH block index is not deactivated.

[0069] In another embodiment, a method performed by a UE in a wireless communication system is provided. The method includes receiving a set of higher layer parameters for a SCell and identifying, based on the set of higher layer parameters, a first configuration for a first SS / PBCH block, the first configuration including, a first frequency location for the first SS / PBCH block, and a first indication of a first set of actually transmitted SS / PBCH block indexes for the first SS / PBCH block, and a second configuration for a second SS / PBCH block, the second configuration including, a second frequency location for the second SS / PBCH block, and a second indication of a second set of actually transmitted SS / PBCH block indexes for the second SS / PBCH block. The method further includes determining a SS / PBCH block index to be associated with a TCI state and determining, when applying the TCI state, that transmission of the second SS / PBCH block corresponding to the SS / PBCH block index is not deactivated.

[0070] In yet another embodiment, a base station (BS) in a wireless communication system is provided. The BS includes a processor configured to determine a first configuration for a first SS / PBCH block, the first configuration including, a first frequency location for the first SS / PBCH block, and a first indication of a first set of actually transmitted SS / PBCH block indexes for the first SS / PBCH block, and determine a second configuration for a second SS / PBCH block, the second configuration including, a second frequency location for the second SS / PBCH block, and a second indication of a second set of actually transmitted SS / PBCH block indexes for the second SS / PBCH block. The BS further includes a transceiver operably coupled to the processor. The transceiver is configured to transmit, to a UE, a set of higher layer parameters for a SCell, the set of higher layer parameters including the first configuration and the second configuration. The processor is further configured to, determine a SS / PBCH block index to be associated with a TCI state and determine, when applying the TCI state, that transmission of the second SS / PBCH block corresponding to the SS / PBCH block index is not deactivated.

[0071] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0072] Before undertaking the present disclosure, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and / or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0073] Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0074] Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.

[0075] FIGS. 1-10 discussed below, and the various, non-limiting embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0076] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. The 5G / NR communication system is implemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60GHz bands, so as to accomplish higher data rates or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G / NR communication systems.

[0077] In addition, in 5G / NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancelation and the like.

[0078] The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems, or the frequency bands associated therewith, and embodiments of the present disclosure may be utilized in connection with any frequency band. For example, aspects of the present disclosure may also be applied to deployment of 5G communication systems, 6G, or even later releases which may use terahertz (THz) bands.

[0079] The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v16.6.0, “NR; Physical channels and modulation” (herein, “REF 1”); 3GPP TS 38.212 v16.6.0, “NR; Multiplexing and channel coding” (herein, “REF 2”); 3GPP TS 38.213 v16.6.0, “NR; Physical layer procedures for control” (herein, “REF 3”); 3GPP TS 38.214 v16.6.0, “NR; Physical layer procedures for data” (herein, “REF 4”); and 3GPP TS 38.331 v16.5.0, “NR; Radio Resource Control (RRC) protocol specification” (herein, “REF 5”).

[0080] FIGS. 1-3 below describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGS. 1-3 are not meant to imply physical or architectural limitations to how different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0081] FIG. 1 illustrates an example wireless network 100 according to embodiments of the present disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 could be used without departing from the scope of the present disclosure.

[0082] As shown in FIG. 1, the wireless network 100 includes a BS 101 (e.g., base station, eNB, gNB), a BS 102, and a BS 103. The BS 101 communicates with the BS 102 and the BS 103. The BS 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0083] The BS 102 provides wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within a coverage area 120 of the BS 102. The first plurality of UEs includes a UE 111, which may be located in a small business; a UE 112, which may be located in an enterprise; a UE 113, which may be a WiFi hotspot; a UE 114, which may be located in a first residence; a UE 115, which may be located in a second residence; and a UE 116, which may be a mobile device, such as a cell phone, a wireless laptop, a wireless PDA, or the like. The BS 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the BS 103. The second plurality of UEs includes the UE 115 and the UE 116. In some embodiments, one or more of the BSs 101-103 may communicate with each other and with the UEs 111-116 using 5G / NR, long term evolution (LTE), long term evolution-advanced (LTE-A), WiMAX, WiFi, or other wireless communication techniques.

[0084] Depending on the network type, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G / NR 3rd generation partnership project (3GPP) NR, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term "user equipment" or "UE" can refer to any component such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receive point," or "user device." For the sake of convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine).

[0085] The dotted lines show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with BSs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the BSs and variations in the radio environment associated with natural and man-made obstructions.

[0086] As described in more detail below, one or more of the UEs 111-116 include circuitry, programing, or a combination thereof for supporting uplink power control based on on-demand SSB. In certain embodiments, one or more of the BSs 101-103 include circuitry, programing, or a combination thereof to enable uplink power control based on on-demand SSB.

[0087] Although FIG. 1 illustrates one example of a wireless network, various changes may be made to FIG. 1. For example, the wireless network 100 could include any number of BSs and any number of UEs in any suitable arrangement. Also, the BS 101 could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each BS 102-103 could communicate directly with the network 130 and provide UEs with direct wireless broadband access to the network 130. Further, the BSs 101, 102, and / or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0088] FIG. 2 illustrates an example BS 102 according to embodiments of the present disclosure. The embodiment of the BS 102 illustrated in FIG. 2 is for illustration only, and the BSs 101 and 103 of FIG. 1 could have the same or similar configuration. However, BSs come in a wide variety of configurations, and FIG. 2 does not limit the scope of the present disclosure to any particular implementation of a BS.

[0089] As shown in FIG. 2, the BS 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0090] The transceivers 210a-210n receive, from the antennas 205a-205n, incoming radio frequency (RF) signals, such as signals transmitted by UEs in the wireless network 100. The transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0091] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-converts the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0092] The controller / processor 225 can include one or more processors or other processing devices that control the overall operation of the BS 102. For example, the controller / processor 225 could control the reception of uplink (UL) channels or signals and the transmission of downlink (DL) channels or signals by the transceivers 210a-210n in accordance with well-known principles. The controller / processor 225 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller / processor 225 could support beam forming or directional routing operations in which outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. As another example, the controller / processor 225 could support methods for enabling uplink power control based on on-demand SSB. Any of a wide variety of other functions could be supported in the BS 102 by the controller / processor 225.

[0093] The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as processes to enable uplink power control based on on-demand SSB. The controller / processor 225 can move data into or out of the memory 230 as required by an executing process.

[0094] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the BS 102 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 could support communications over any suitable wired or wireless connection(s). For example, when the BS 102 is implemented as part of a cellular communication system (such as one supporting 5G / NR, LTE, or LTE-A), the interface 235 could allow the BS 102 to communicate with other BSs over a wired or wireless backhaul connection. When the BS 102 is implemented as an access point, the interface 235 could allow the BS 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or transceiver.

[0095] The memory 230 is coupled to the controller / processor 225. Part of the memory 230 could include a RAM, and another part of the memory 230 could include a Flash memory or other ROM.

[0096] Although FIG. 2 illustrates one example of BS 102, various changes may be made to FIG. 2. For example, the BS 102 could include any number of each component shown in FIG. 2. Also, various components in FIG. 2 could be combined, further subdivided, or omitted and additional components could be added according to particular needs.

[0097] FIG. 3 illustrates an example UE 116 according to embodiments of the present disclosure. The embodiment of the UE 116 illustrated in FIG. 3 is for illustration only, and the UEs 111-115 of FIG. 1 could have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIG. 3 does not limit the scope of the present disclosure to any particular implementation of a UE.

[0098] As shown in FIG. 3, the UE 116 includes antenna(s) 305, a transceiver(s) 310, and a microphone 320. The UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0099] The transceiver(s) 310 receives from the antenna(s) 305, an incoming RF signal transmitted by a BS of the wireless network 100. The transceiver(s) 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in the transceiver(s) 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to the speaker 330 (such as for voice data) or is processed by the processor 340 (such as for web browsing data).

[0100] TX processing circuitry in the transceiver(s) 310 and / or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver(s) 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna(s) 305.

[0101] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channels or signals and the transmission of UL channels or signals by the transceiver(s) 310 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0102] The processor 340 is also capable of executing other processes and programs resident in the memory 360. For example, the processor 340 may execute processes for supporting uplink power control based on on-demand SSB as described in embodiments of the present disclosure. The processor 340 can move data into or out of the memory 360 as required by an executing process. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS 361 or in response to signals received from BSs or an operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0103] The processor 340 is also coupled to the input 350, which includes, for example, a touchscreen, keypad, etc., and the display 355. The operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites.

[0104] The memory 360 is coupled to the processor 340. Part of the memory 360 could include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0105] Although FIG. 3 illustrates one example of UE 116, various changes may be made to FIG. 3. For example, various components in FIG. 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver(s) 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Also, while FIG. 3 illustrates the UE 116 configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices.

[0106] FIG. 4A and FIG. 4B illustrate an example of wireless transmit and receive paths 400 and 450, respectively, according to embodiments of the present disclosure. For example, a transmit path 400 may be described as being implemented in a BS (such as BS 102), while a receive path 450 may be described as being implemented in a UE (such as UE 116). However, it will be understood that the receive path 450 can be implemented in a BS and that the transmit path 400 can be implemented in a UE. In some embodiments, the transmit path 400 and / or the receive path 450 is configured for supporting uplink power control based on on-demand SSB as described in embodiments of the present disclosure.

[0107] As illustrated in FIG. 4A, the transmit path 400 includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size N Inverse Fast Fourier Transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path 450 includes a down-converter (DC) 455, a remove cyclic prefix block 460, a S-to-P block 465, a size N Fast Fourier Transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

[0108] In the transmit path 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as a low-density parity check (LDPC) coding), and modulates the input bits (such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel block 410 converts (such as de-multiplexes) the serial modulated symbols to parallel data in order to generate N parallel symbol streams, where N is the IFFT / FFT size used in the BS and the UE. The size N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate time-domain output signals. The parallel-to-serial block 420 converts (such as multiplexes) the parallel time-domain output symbols from the size N IFFT block 415 in order to generate a serial time-domain signal. The add cyclic prefix block 425 inserts a cyclic prefix to the time-domain signal. The up-converter 430 modulates (such as up-converts) the output of the add cyclic prefix block 425 to a RF frequency for transmission via a wireless channel. The signal may also be filtered at a baseband before conversion to the RF frequency.

[0109] As illustrated in FIG. 4B, the down-converter 455 down-converts the received signal to a baseband frequency, and the remove cyclic prefix block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. The serial-to-parallel block 465 converts the time-domain baseband signal to parallel time-domain signals. The size N FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. The (P-to-S) block 475 converts the parallel frequency-domain signals to a sequence of modulated data symbols. The channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0110] Each of the BSs 101-103 may implement a transmit path 400 that is analogous to transmitting in the downlink to UEs 111-116 and may implement a receive path 450 that is analogous to receiving in the uplink from UEs 111-116. Similarly, each of UEs 111-116 may implement a transmit path 400 for transmitting in the uplink to the BSs 101-103 and may implement a receive path 450 for receiving in the downlink from the BSs 101-103.

[0111] Each of the components in FIGS. 4A and 4B can be implemented using only hardware or using a combination of hardware and software / firmware. As a particular example, at least some of the components in FIGS. 4A and 4B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For instance, the FFT block 470 and the IFFT block 415 may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

[0112] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed to limit the scope of the present disclosure. Other types of transforms, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be appreciated that the value of the variable N may be any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFT functions, while the value of the variable N may be any integer number that is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT and IFFT functions.

[0113] Although FIGS. 4A and 4B illustrate examples of wireless transmit and receive paths 400 and 450, respectively, various changes may be made to FIGS. 4A and 4B. For example, various components in FIGS. 4A and 4B can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. Also, FIGS. 4A and 4B are meant to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architectures can be used to support wireless communications in a wireless network.

[0114] In new radio (NR), for a secondary cell (SCell) implemented with periodic synchronization signal / physical broadcast channel (SS / PBCH) block transmission, or always-on SSB (AO-SSB), a UE can be provided with a configuration for radio resource management (RRM) measurement based on the periodic SS / PBCH block, wherein the configuration can be provided by a RRC parameter. After the RRM measurement, the gNB can provide a configuration of the SCell, e.g., by another RRC parameter. The UE can be further provided with a medium access control (MAC) control element (CE) indicating an activation of the SCell, and by using the periodic SS / PBCH blocks on the SCell, or tracking reference signal (TRS) if configured, or the SS / PBCH blocks on the primary cell (PCell) when the SCell is without periodic SS / PBCH block transmission, the UE can get synchronized with the SCell and get ready to transmit or receive on the SCell. After activation of the SCell, if the SCell gets loss of synchronization, the UE can use the periodic SS / PBCH block for resynchronization. Since SS / PBCH block is transmitted on the SCell periodically, the power consumption for SS / PBCH block can be significantly large. To reduce the power consumption, on-demand SS / PBCH block (OD-SSB) can be supported on the SCell. This disclosure focuses on the procedure for uplink power control (e.g., PUSCH, PUCCH, SRS, and / or PRACH) based on the OD-SSB, as well as radio link monitoring and / or link recovery procedure based on the OD-SSB.

[0115] For one example, this disclosure can be applicable for RRC_CONNECTED mode.

[0116] For another example, this disclosure can be applicable for RRC_IDLE mode.

[0117] For yet another example, this disclosure can be applicable for RRC_INACTIVE mode.

[0118] For one example, this disclosure can be applicable for a PCell.

[0119] For another example, this disclosure can be applicable for a SCell.

[0120] For yet another example, this disclosure can be applicable for a primary secondary cell (PSCell).

[0121] For one example, this disclosure can be applicable for AO-SSB as cell-defining SSB (e.g., with associated SIB1 transmission).

[0122] For another example, this disclosure can be applicable for AO-SSB as non-cell-defining SSB (e.g., without associated SIB1 transmission).

[0123] For one example, this disclosure can be applicable for AO-SSB located at a frequency layer given by a synchronization raster entry.

[0124] For another example, this disclosure can be applicable for AO-SSB located at a frequency layer not given by a synchronization raster entry.

[0125] As introduced above, this disclosure focuses on the UE procedures based on on-demand SSB (OD-SSB), including an uplink power control procedure. More precisely, the following aspects, among others, are included in this disclosure:

[0126] - General considerations on UE procedures based on on-demand SSB

[0127] - Uplink power control with unified transmission configuration indicator (TCI) state operation

[0128] - Uplink power control without unified TCI state operation

[0129] -- Common SSB Type(s) for Uplink Channels

[0130] -- Separate SSB Type(s) for physical uplink shared channel (PUSCH)

[0131] -- Separate SSB Type(s) for physical uplink control channel (PUCCH)

[0132] -- Separate SSB Type(s) for sounding reference signal (SRS)

[0133] - Power control for physical random access channel (PRACH) based on on-demand SSB

[0134] - Radio link monitoring based on on-demand SSB

[0135] - Link recovery procedure based on on-demand SSB

[0136] As for the general considerations on UE procedures based on on-demand SSB, in one embodiment, for a serving configured with on-demand SS / PBCH block (OD-SSB), a UE can perform operations based on the OD-SSB, e.g., when the OD-SSB is transmitted, according to at least one of the following example operations.

[0137] - Example 1: L1 measurement

[0138] - Example 2: L3 measurement

[0139] - Example 3: uplink power control (e.g., downlink pathloss calculation)

[0140] - Example 4: radio link monitoring

[0141] - Example 5: link recovery procedure

[0142] For one example, the uplink power control can be for a PUSCH.

[0143] For another example, the uplink power control can be for a PUCCH.

[0144] For yet another example, the uplink power control can be for an SRS.

[0145] For yet another example, the uplink power control can be for a PRACH.

[0146] In one example, the OD-SSB can be used as the RS for calculating the downlink pathloss estimate in dB in the uplink power control, e.g., the term PLb,f,c(qd).

[0147] For one example, in a first case (Case 1) that there is no always-on SS / PBCH block (AO-SSB) transmission (or periodic SSB transmission) on the same cell as the OD-SSB, the example procedure (e.g., from Example 1 to Example 5) can be based on the OD-SSB only.

[0148] - For one further implementation, the higher layer parameter providing the center frequency of the AO-SSB (e.g., absoluteFrequencySSB) can be absent for Case 1.

[0149] - For another further implementation, the RS resource corresponding to a SS / PBCH block configured for the example procedure refers to the OD-SSB configured for the cell.

[0150] - For yet another further implementation, the example of using OD-SSB only for the example UE procedure can be based on a configuration by the higher layer parameters, e.g., according to embodiments and examples of the present disclosure.

[0151] For another example, in a second case (Case 2) that there is always-on SS / PBCH block (AO-SSB) transmission (or periodic SSB transmission) on the same cell as the OD-SSB, the example procedure (e.g., from Example 1 to Example 5) can be based on the OD-SSB only, or AO-SSB only, or both the OD-SSB and the AO-SSB, according to embodiments and examples of the present disclosure.

[0152] - For one further implementation, the higher layer parameter providing the center frequency of the AO-SSB (e.g., absoluteFrequencySSB) can be present for Case 2.

[0153] For one further implementation, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) the UE determines for one example procedure (e.g., from Example 1 to Example 5), e.g., according to examples of the present disclosure, can be used for another example procedure (e.g., from Example 1 to Example 5).

[0154] In the present disclosure, uplink power control with unified TCI state operation is provided.

[0155] In one embodiment, a UE can be provided by higher layer parameters (e.g., PathlossReferenceRS) to configure a reference signal (RS) to be used for pathloss estimation for PUSCH, PUCCH and SRS for the unified TCI state operation, and when the RS is a SS / PBCH block, the SS / PBCH block can be an OD-SSB; or determines a SS / PBCH block for pathloss estimation for PUSCH, PUCCH and SRS, e.g., when the higher layer parameters are not provided, and the SS / PBCH block can also be an OD-SSB.

[0156] For one example, the configuration for the RS (e.g., PathlossReferenceRS) can include a field indicating that when the RS is a SSB, which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the pathloss estimation.

[0157] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0158] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0159] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0160] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0161] - For yet another further implementation, the field is only applicable for Case 2.

[0162] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0163] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0164] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0165] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0166] For another example, the higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used at least for the pathloss estimation.

[0167] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0168] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0169] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0170] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0171] - For yet another further implementation, the field is only applicable for Case 2.

[0172] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0173] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0174] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0175] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0176] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for L1 measurement.

[0177] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for radio link monitoring (RLM), and / or link recovery procedure.

[0178] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation can be determined as the same type(s) of SSB for L1 measurement.

[0179] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for pathloss estimation.

[0180] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for pathloss estimation.

[0181] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation can be determined as OD-SSB only.

[0182] - For one further implementation, this example is applicable at least for Case 1.

[0183] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0184] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0185] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0186] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation can be determined as both AO-SSB and OD-SSB.

[0187] - For one further implementation, this example is applicable at least for Case 2.

[0188] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0189] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0190] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0191] For one example, when a UE identifies to perform pathloss estimation based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may maintain two pathloss estimates when calculating the total number of maintained pathloss estimates.

[0192] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for pathloss estimation.

[0193] For another example, when a UE identifies to perform pathloss estimation based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may select OD-SSB, or AO-SSB, or OD-SSB and AO-SSB for pathloss estimation.

[0194] For one example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) the UE determined for the pathloss estimation (e.g., according to example of the present disclosure) can also be applicable to PRACH power control (e.g., pathloss estimation for PRACH).

[0195] Further in the present disclosure, uplink power control without unified TCI state operation is provided.

[0196] In various embodiments, common SSB type(s) for uplink channels are provided.

[0197] In one embodiment, a UE can be provided by higher layer parameters to configure a reference signal (RS) to be used for pathloss estimation for PUSCH, PUCCH, or SRS, respectively, and when the RS is a SS / PBCH block, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) can be common at least for one of PUSCH, PUCCH, or SRS; or determines a SS / PBCH block for pathloss estimation for PUSCH, PUCCH, or SRS, respectively, e.g., when the higher layer parameters are not provided, then the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) can also be common at least for one of PUSCH, PUCCH, or SRS.

[0198] For one example, the higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used at least for the pathloss estimation at least for one of PUSCH, PUCCH, or SRS.

[0199] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0200] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0201] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0202] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0203] - For yet another further implementation, the field is only applicable for Case 2.

[0204] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0205] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0206] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0207] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0208] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for L1 measurement.

[0209] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for radio link monitoring (RLM), and / or link recovery procedure.

[0210] - For yet another further implementation, there can be multiple higher layer parameter providing indications on which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for each of PUSCH, PUCCH, or SRS, and the UE can expect the indications are the same (e.g., indicating same type(s) of SSB).

[0211] - For yet another further implementation, the higher layer parameter can be same as the one providing the indication on which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for pathloss estimation for PUSCH, PUCCH and SRS for the unified TCI state operation.

[0212] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation at least for one of PUSCH, PUCCH, or SRS can be determined as the same type(s) of SSB for L1 measurement.

[0213] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for pathloss estimation at least for one of PUSCH, PUCCH, or SRS.

[0214] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for pathloss estimation at least for one of PUSCH, PUCCH, or SRS.

[0215] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation at least for one of PUSCH, PUCCH, or SRS can be determined as OD-SSB only.

[0216] - For one further implementation, this example is applicable at least for Case 1.

[0217] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0218] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0219] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0220] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation at least for one of PUSCH, PUCCH, or SRS can be determined as both AO-SSB and OD-SSB.

[0221] - For one further implementation, this example is applicable at least for Case 2.

[0222] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0223] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0224] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0225] For one example, when a UE identifies to perform pathloss estimation at least for one of PUSCH, PUCCH, or SRS based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may maintain two pathloss estimates when calculating the total number of maintained pathloss estimates.

[0226] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for pathloss estimation.

[0227] For another example, when a UE identifies to perform pathloss estimation at least for one of PUSCH, PUCCH, or SRS based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may select OD-SSB, or AO-SSB, or OD-SSB and AO-SSB for pathloss estimation at least for one of PUSCH, PUCCH, or SRS.

[0228] For one example, the determined type(s) of SSB (e.g., according to example of the present disclosure) is applicable to at least one of the following instances.

[0229] - For one instance, the determined type(s) of SSB is applicable to the SSB for PUSCH pathloss estimation, when the RS for PUSCH pathloss estimation is configured as a SSB by higher layer parameter (e.g., PUSCH-PathlossReferenceRS).

[0230] - For another instance, the determined type(s) of SSB is applicable to the determined SSB for PUSCH pathloss estimation, e.g., when the RS for PUSCH pathloss estimation by higher layer parameter (e.g., PUSCH-PathlossReferenceRS) is not provided.

[0231] - For yet another instance, the determined type(s) of SSB is applicable to the SSB for PUCCH pathloss estimation, when the RS for PUCCH pathloss estimation is configured as a SSB by higher layer parameter (e.g., PUCCH-PathlossReferenceRS, and / or PUCCH-SpatialRelationInfo).

[0232] - For yet another instance, the determined type(s) of SSB is applicable to the determined SSB for PUCCH pathloss estimation, e.g., when the RS for PUCCH pathloss estimation by higher layer parameter (e.g., PUCCH-PathlossReferenceRS, and / or PUCCH-SpatialRelationInfo) is not provided.

[0233] - For yet another instance, the determined type(s) of SSB is applicable to the SSB for SRS pathloss estimation, when the RS for SRS pathloss estimation is configured as a SSB by higher layer parameter (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo).

[0234] - For yet another instance, the determined type(s) of SSB is applicable to the determined SSB for SRS pathloss estimation, e.g., when the RS for SRS pathloss estimation by higher layer parameter (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo) is not provided.

[0235] For one example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) the UE determined for the pathloss estimation at least for one of PUSCH, PUCCH, or SRS (e.g., according to example of the present disclosure) can also be applicable to PRACH power control (e.g., pathloss estimation for PRACH).

[0236] In various embodiments, separate SSB type(s) for PUSCH are provided.

[0237] In one embodiment, a UE can be provided by higher layer parameters (e.g., PUSCH-PathlossReferenceRS) to configure a reference signal (RS) to be used for pathloss estimation for PUSCH, and when the RS is a SS / PBCH block, the SS / PBCH block can be an OD-SSB; or determines a SS / PBCH block for pathloss estimation for PUSCH, e.g., when the higher layer parameters are not provided, and the SS / PBCH block can also be an OD-SSB.

[0238] For one example, the configuration for the RS (e.g., PUSCH-PathlossReferenceRS) can include a field indicating that when the RS is a SSB, which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the pathloss estimation for PUSCH.

[0239] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0240] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0241] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0242] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0243] - For yet another further implementation, the field is only applicable for Case 2.

[0244] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0245] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0246] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0247] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0248] For another example, the higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used at least for the pathloss estimation for PUSCH.

[0249] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0250] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0251] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0252] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0253] - For yet another further implementation, the field is only applicable for Case 2.

[0254] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0255] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0256] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0257] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0258] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for L1 measurement.

[0259] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for radio link monitoring (RLM), and / or link recovery procedure.

[0260] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PUSCH can be determined as the same type(s) of SSB for L1 measurement.

[0261] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for pathloss estimation for PUSCH.

[0262] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for pathloss estimation for PUSCH.

[0263] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PUSCH can be determined as OD-SSB only.

[0264] - For one further implementation, this example is applicable at least for Case 1.

[0265] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0266] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0267] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0268] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PUSCH can be determined as both AO-SSB and OD-SSB.

[0269] - For one further implementation, this example is applicable at least for Case 2.

[0270] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0271] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0272] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0273] For one example, when a UE identifies to perform pathloss estimation based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may maintain two pathloss estimates when calculating the total number of maintained pathloss estimates.

[0274] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for pathloss estimation.

[0275] For another example, when a UE identifies to perform pathloss estimation for PUSCH based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may select OD-SSB, or AO-SSB, or OD-SSB and AO-SSB for pathloss estimation for PUSCH.

[0276] For one example, the determined type(s) of SSB (e.g., according to example of the present disclosure) is applicable to at least one of the following instances.

[0277] - For one instance, the determined type(s) of SSB is applicable to the SSB for PUSCH pathloss estimation, when the RS for PUSCH pathloss estimation is configured as a SSB by higher layer parameter (e.g., PUSCH-PathlossReferenceRS).

[0278] - For another instance, the determined type(s) of SSB is applicable to the determined SSB for PUSCH pathloss estimation, e.g., when the RS for PUSCH pathloss estimation by higher layer parameter (e.g., PUSCH-PathlossReferenceRS) is not provided.

[0279] For one example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) the UE determined for the pathloss estimation for PUSCH (e.g., according to example of the present disclosure) can also be applicable to PRACH power control (e.g., pathloss estimation for PRACH).

[0280] In various embodiments, separate SSB type(s) for PUCCH are provided.

[0281] In one embodiment, a UE can be provided by higher layer parameters (e.g., PUCCH-PathlossReferenceRS, and / or PUCCH-SpatialRelationInfo) to configure a reference signal (RS) to be used for pathloss estimation for PUCCH, and when the RS is a SS / PBCH block, the SS / PBCH block can be an OD-SSB; or determines a SS / PBCH block for pathloss estimation for PUCCH, e.g., when the higher layer parameters are not provided, and the SS / PBCH block can also be an OD-SSB.

[0282] For one example, the configuration for the RS (e.g., PUCCH-PathlossReferenceRS, and / or PUCCH-SpatialRelationInfo) can include a field indicating that when the RS is a SSB, which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the pathloss estimation for PUCCH.

[0283] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0284] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0285] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0286] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0287] - For yet another further implementation, the field is only applicable for Case 2.

[0288] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0289] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0290] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0291] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0292] For another example, the higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used at least for the pathloss estimation for PUCCH.

[0293] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0294] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0295] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0296] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0297] - For yet another further implementation, the field is only applicable for Case 2.

[0298] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0299] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0300] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0301] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0302] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for L1 measurement.

[0303] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for radio link monitoring (RLM), and / or link recovery procedure.

[0304] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PUCCH can be determined as the same type(s) of SSB for L1 measurement.

[0305] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for pathloss estimation for PUCCH.

[0306] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for pathloss estimation for PUCCH.

[0307] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PUCCH can be determined as OD-SSB only.

[0308] - For one further implementation, this example is applicable at least for Case 1.

[0309] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0310] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0311] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0312] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PUCCH can be determined as both AO-SSB and OD-SSB.

[0313] - For one further implementation, this example is applicable at least for Case 2.

[0314] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0315] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0316] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0317] For one example, when a UE identifies to perform pathloss estimation based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may maintain two pathloss estimates when calculating the total number of maintained pathloss estimates.

[0318] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for pathloss estimation.

[0319] For another example, when a UE identifies to perform pathloss estimation for PUCCH based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may select OD-SSB, or AO-SSB, or OD-SSB and AO-SSB for pathloss estimation for PUCCH.

[0320] For one example, the determined type(s) of SSB (e.g., according to example of the present disclosure) is applicable to at least one of the following instances.

[0321] - For one instance, the determined type(s) of SSB is applicable to the SSB for PUCCH pathloss estimation, when the RS for PUCCH pathloss estimation is configured as a SSB by higher layer parameter (e.g., PUCCH-PathlossReferenceRS, and / or PUCCH-SpatialRelationInfo).

[0322] - For another instance, the determined type(s) of SSB is applicable to the determined SSB for PUCCH pathloss estimation, e.g., when the RS for PUCCH pathloss estimation by higher layer parameter (e.g., PUCCH-PathlossReferenceRS, and / or PUCCH-SpatialRelationInfo) is not provided.

[0323] For one example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) the UE determined for the pathloss estimation for PUCCH (e.g., according to example of the present disclosure) can also be applicable to PRACH power control (e.g., pathloss estimation for PRACH).

[0324] In various embodiments, separate SSB type(s) for SRS are provided.

[0325] In one embodiment, a UE can be provided by higher layer parameters (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo) to configure a reference signal (RS) to be used for pathloss estimation for SRS, and when the RS is a SS / PBCH block, the SS / PBCH block can be an OD-SSB; or determines a SS / PBCH block for pathloss estimation for SRS, e.g., when the higher layer parameters are not provided, and the SS / PBCH block can also be an OD-SSB.

[0326] For one example, the configuration for the RS (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo) can include a field indicating that when the RS is a SSB, which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the pathloss estimation for SRS.

[0327] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0328] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0329] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0330] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0331] - For yet another further implementation, the field is only applicable for Case 2.

[0332] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0333] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0334] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0335] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0336] For yet another further implementation, the determined type(s) of SSB is applicable to the SSB for SRS pathloss estimation, when the RS for SRS pathloss estimation is configured as a SSB by higher layer parameter (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo).

[0337] - For yet another further implementation, the determined type(s) of SSB is applicable to the determined SSB for SRS pathloss estimation, e.g., when the RS for SRS pathloss estimation by higher layer parameter (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo) is not provided.

[0338] For another example, the higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used at least for the pathloss estimation for SRS.

[0339] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0340] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0341] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0342] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0343] - For yet another further implementation, the field is only applicable for Case 2.

[0344] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0345] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0346] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0347] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0348] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for L1 measurement.

[0349] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for radio link monitoring (RLM), and / or link recovery procedure.

[0350] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for SRS can be determined as the same type(s) of SSB for L1 measurement.

[0351] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for pathloss estimation for SRS.

[0352] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for pathloss estimation for SRS.

[0353] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for SRS can be determined as OD-SSB only.

[0354] - For one further implementation, this example is applicable at least for Case 1.

[0355] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0356] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0357] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0358] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for SRS can be determined as both AO-SSB and OD-SSB.

[0359] - For one further implementation, this example is applicable at least for Case 2.

[0360] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0361] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0362] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0363] For one example, when a UE identifies to perform pathloss estimation based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may maintain two pathloss estimates when calculating the total number of maintained pathloss estimates.

[0364] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for pathloss estimation.

[0365] For another example, when a UE identifies to perform pathloss estimation for SRS based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may select OD-SSB, or AO-SSB, or OD-SSB and AO-SSB for pathloss estimation for SRS.

[0366] For one example, the determined type(s) of SSB (e.g., according to example of the present disclosure) is applicable to at least one of the following instances.

[0367] - For one instance, the determined type(s) of SSB is applicable to the SSB for SRS pathloss estimation, when the RS for SRS pathloss estimation is configured as a SSB by higher layer parameter (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo).

[0368] - For another instance, the determined type(s) of SSB is applicable to the determined SSB for SRS pathloss estimation, e.g., when the RS for SRS pathloss estimation by higher layer parameter (e.g., PathlossReferenceRS-Config in SRS-Config, and / or SRS-SpatialRelationInfo) is not provided.

[0369] For one example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) the UE determined for the pathloss estimation for SRS (e.g., according to example of the present disclosure) can also be applicable to PRACH power control (e.g., pathloss estimation for PRACH).

[0370] Further in the present disclosure, power control for PRACH is provided.

[0371] In one embodiment, a UE can determine a SS / PBCH block for pathloss estimation for PRACH, and the SS / PBCH block can be an OD-SSB.

[0372] For one example, a higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used at least for the pathloss estimation for PRACH.

[0373] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0374] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0375] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0376] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0377] - For yet another further implementation, the field is only applicable for Case 2.

[0378] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is AO-SSB, e.g., at least for Case 2.

[0379] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for pathloss estimation is OD-SSB, e.g., at least for Case 1.

[0380] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0381] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0382] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for L1 measurement.

[0383] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for radio link monitoring (RLM), and / or link recovery procedure.

[0384] For another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PRACH can be determined as the same type(s) of SSB for L1 measurement.

[0385] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for pathloss estimation for PRACH.

[0386] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for pathloss estimation for PRACH.

[0387] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PRACH can be determined as OD-SSB only.

[0388] - For one further implementation, this example is applicable at least for Case 1.

[0389] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0390] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0391] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0392] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the pathloss estimation for PRACH can be determined as both AO-SSB and OD-SSB.

[0393] - For one further implementation, this example is applicable at least for Case 2.

[0394] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0395] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0396] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0397] For one example, when a UE identifies to perform pathloss estimation based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may maintain two pathloss estimates when calculating the total number of maintained pathloss estimates.

[0398] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for pathloss estimation.

[0399] For one example, the determined type(s) of SSB (e.g., according to example of the present disclosure) is applicable to at least one of the following instances.

[0400] - For one instance, the determined type(s) of SSB is applicable to the determined SSB for PRACH pathloss estimation.

[0401] Further in the present disclosure, radio link monitoring is provided.

[0402] In one embodiment, a UE can be provided by higher layer parameters (e.g., RadioLinkMonitoringRS) to configure a reference signal (RS) to be used for radio link monitoring (RLM), and when the RS is a SS / PBCH block, the SS / PBCH block can be an OD-SSB; or determines a SS / PBCH block for radio link monitoring, e.g., when the higher layer parameters are not provided, and the SS / PBCH block can also be an OD-SSB.

[0403] For one example, the configuration for the RS (e.g., RadioLinkMonitoringRS) can include a field indicating that when the RS is a SSB, which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the RLM.

[0404] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0405] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0406] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0407] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0408] - For yet another further implementation, the field is only applicable for Case 2.

[0409] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for RLM is AO-SSB, e.g., at least for Case 2.

[0410] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for RLM is OD-SSB, e.g., at least for Case 1.

[0411] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0412] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0413] For another example, the higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the RLM.

[0414] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0415] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0416] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0417] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0418] - For yet another further implementation, the field is only applicable for Case 2.

[0419] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for RLM is AO-SSB, e.g., at least for Case 2.

[0420] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for RLM is OD-SSB, e.g., at least for Case 1.

[0421] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0422] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0423] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for L1 measurement, and / or uplink power control.

[0424] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the RLM can be determined as the same type(s) of SSB for L1 measurement.

[0425] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for RLM.

[0426] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for RLM.

[0427] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the RLM can be determined as OD-SSB only.

[0428] - For one further implementation, this example is applicable at least for Case 1.

[0429] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0430] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0431] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0432] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the RLM can be determined as both AO-SSB and OD-SSB.

[0433] - For one further implementation, this example is applicable at least for Case 2.

[0434] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0435] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0436] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0437] For one example, when a UE identifies to perform RLM based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may perform two RLM procedures when calculating the total number of RLM procedures.

[0438] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for RLM.

[0439] For another example, when a UE identifies to perform RLM based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may select OD-SSB, or AO-SSB, or OD-SSB and AO-SSB for RLM.

[0440] Further in the present disclosure, a link recovery procedure is provided.

[0441] In one embodiment, a UE can be provided by higher layer parameters (e.g., candidateBeamRSList or candidateBeamRSListExt or candidateBeamRS-List or candidateBeamRS-List2) to configure a reference signal (RS) to be used for radio link quality measurements and / or link recovery procedure, and when the RS is a SS / PBCH block, the SS / PBCH block can be an OD-SSB.

[0442] For one example, the configuration for the RS (e.g., candidateBeamRSList or candidateBeamRSListExt or candidateBeamRS-List or candidateBeamRS-List2) can include a field indicating that when the RS is a SSB, which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the link recovery procedure.

[0443] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0444] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0445] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0446] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0447] - For yet another further implementation, the field is only applicable for Case 2.

[0448] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for link recovery procedure is AO-SSB, e.g., at least for Case 2.

[0449] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for link recovery procedure is OD-SSB, e.g., at least for Case 1.

[0450] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0451] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0452] For another example, the higher layer parameter can provide an explicit field indicating which type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) is used for the link recovery procedure.

[0453] - For one further implementation, the field can indicate the SSB is AO-SSB or OD-SSB.

[0454] - For another further implementation, the field can indicate the SSB is OD-SSB, or both AO-SSB and OD-SSB.

[0455] - For yet another further implementation, the field can indicate the SSB is OD-SSB, or AO-SSB, or both AO-SSB and OD-SSB.

[0456] - For yet another further implementation, for Case 1, the UE expects the field to be configured as OD-SSB only.

[0457] - For yet another further implementation, the field is only applicable for Case 2.

[0458] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for link recovery procedure is AO-SSB, e.g., at least for Case 2.

[0459] - For yet another further implementation, when the field is absent, the UE assumes the type(s) of SSB for link recovery procedure is OD-SSB, e.g., at least for Case 1.

[0460] - For yet another further implementation, the field can be configured as both AO-SSB and OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0461] - For yet another further implementation, the field can be configured as OD-SSB, when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0462] - For yet another further implementation, the indication by the field can also be used for SSB type(s) for other UE procedures, such as L1 measurement, and / or uplink power control.

[0463] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the link recovery procedure can be determined as the same type(s) of SSB for L1 measurement.

[0464] - For one instance, there can be a higher layer parameter indicating which type(s) of SSB is used for L1 measurement, and the UE can apply the same type(s) of SSB for link recovery procedure.

[0465] - For another instance, if a UE determines type(s) of SSB is used for L1 measurement, e.g., based on whether the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same, then the UE can apply the same type(s) of SSB for link recovery procedure.

[0466] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the link recovery procedure can be determined as OD-SSB only.

[0467] - For one further implementation, this example is applicable at least for Case 1.

[0468] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0469] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0470] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0471] For yet another example, the type(s) of SSB (e.g., from AO-SSB, and / or OD-SSB) used for the link recovery procedure can be determined as both AO-SSB and OD-SSB.

[0472] - For one further implementation, this example is applicable at least for Case 2.

[0473] - For another further implementation, this example is applicable for both Case 1 and Case 2.

[0474] - For yet another further implementation, this example is applicable at least when the center frequency of the AO-SSB and the center frequency of the OD-SSB are the same.

[0475] - For yet another further implementation, this example is applicable when the center frequency of the AO-SSB and the center frequency of the OD-SSB are different.

[0476] For one example, when a UE identifies to perform link recovery procedure based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may perform two radio link recovery procedures when calculating the total number of radio link recovery procedures.

[0477] - For one further implementation, this example can be applicable at least when the UE selects both OD-SSB and AO-SSB for link recovery procedure.

[0478] For another example, when a UE identifies to perform link recovery procedure based on both of OD-SSB and AO-SSB (e.g., according to example of the present disclosure), the UE may select OD-SSB, or AO-SSB, or OD-SSB and AO-SSB for link recovery procedure.

[0479] For one example, this embodiment is applicable for link recovery procedure on a SCell.

[0480] FIG. 5 illustrates an example method 500 performed by a UE in a wireless communication system according to embodiments of the present disclosure. More particularly, FIG. 5 illustrates the example method 500 for using on-demand SS / PBCH block for uplink power control. The method 500 of FIG. 5 can be performed by any of the UEs 111-116 of FIG. 1, such as the UE 116 of FIG. 3, and a corresponding method can be performed by any of the BSs 101-103 of FIG. 1, such as BS 102 of FIG. 2. The method 500 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0481] The method 500 beings with the UE receiving higher layer parameters (510). The UE then determines an RS for pathloss estimate as an SSB, based on the higher layer parameters (520). The UE then determines type(s) of the SSB, based on the higher layer parameters (530). The UE then calculates the pathloss estimate based on the type(s) of SSB (540). The UE then determines the uplink power control for a PUSCH, a PUCCH, or a SRS (550).

[0482] Although FIG. 5 illustrates one example method 500 of the actions taken by the UE for using an on-demand SS / PBCH block for uplink power control, various changes may be made to FIG. 5. For example, while shown as a series of steps, various steps in FIG. 5 could overlap, occur in parallel, occur in a different order, or occur any number of times.

[0483] Further in the present disclosure, an OD-SSB with a new beam is provided.

[0484] In one embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform based on the OD-SSB, the UE behavior needs to be specified after the OD-SSB transmission is terminated (e.g., deactivated and / or adapted to be not transmitted). In one further example, the OD-SSB can be based on a different beam of the AO-SSB, as illustrated in FIG. 6.

[0485] FIG. 6 illustrates an example of an OD-SSB based operation using a different beam according to embodiments of the present disclosure. For example, the OD-SSB based operation can be implemented by BS 102 of FIG. 1. This example is for illustration only and can be used without departing from the scope of the present disclosure.

[0486] In various embodiments, an OD-SSB for measurement is provided.

[0487] In one embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform measurement at least based on OD-SSB, the UE may stop measurement based on OD-SSB after the transmission of OD-SSB is terminated (e.g., deactivated and / or adapted to be not transmitted).

[0488] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0489] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0490] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0491] - For yet another instance, the index(es) of OD-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure) can be not included in the index(es) of AO-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure), e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0492] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0493] - For yet another instance, the measurement is a L1 measurement (e.g., CSI measurement).

[0494] - For yet another instance, the measurement is a L3 measurement (e.g., RRM measurement).

[0495] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of OD-SSB configured for measurement.

[0496] - For yet another instance, the embodiment can be applicable also for performing measurement report associated with the measurement.

[0497] For yet another further example, if the example instances are not satisfied, the UE may perform measurement based on either AO-SSB or OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated) or both AO-SSB and OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated), based on its implementation.

[0498] For another further example, the UE stops measurement reporting after the OD-SSB transmission is terminated (e.g., deactivated and / or adapted to be not transmitted).

[0499] For yet another further example, the UE reports measurement results based on transmitted OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated).

[0500] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for measurement and / or measurement report corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE can stop perform the measurement and / or stop the measurement report, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0501] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for measurement and / or measurement report corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE can stop perform the measurement and / or stop the measurement report, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0502] In another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform measurement at least based on OD-SSB, the UE may not expect that the index(es) of OD-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure) can be not included in the index(es) of AO-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure), e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0503] For one further example, the index(es) of OD-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure) is same as or a subset of the index(es) of AO-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure).

[0504] In yet another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform measurement at least based on OD-SSB, and the index(es) of OD-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure) can be not included in the index(es) of AO-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure), e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, then at least one of the following UE behavior can apply:

[0505] - In one example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB.

[0506] - In another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB and / or when the cell is active.

[0507] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0508] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0509] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0510] - For yet another instance, the index(es) of OD-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure) can be not included in the index(es) of AO-SSB configured for measurement (e.g., SSB-index or ssb-toMeasure), e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0511] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0512] - For yet another instance, the measurement is a L1 measurement (e.g., CSI measurement).

[0513] - For yet another instance, the measurement is a L3 measurement (e.g., RRM measurement).

[0514] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of OD-SSB configured for measurement.

[0515] - For yet another instance, the embodiment can be applicable also for performing measurement report associated with the measurement.

[0516] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for measurement and / or measurement report corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the measurement or measurement report.

[0517] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for measurement and / or measurement report corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the measurement or measurement report or e.g., when performing the measurement or measurement report.

[0518] In various embodiments, an OD-SSB for an activated or applied TCI state is provided.

[0519] In one embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the indicated (e.g., activated) TCI state is at least based on OD-SSB, the UE may apply at least one of the following examples as the TCI state or QCL source, after the transmission of OD-SSB is terminated (e.g., deactivated and / or adapted to be not transmitted).

[0520] - In one example, the UE can continue to apply the indicated TCI state (e.g., the indicated TCI state is associated with an OD-SSB).

[0521] - In another example, the UE can apply a default TCI state. For one instance, the default TCI state can be the one with the lowest index. For another instance, the default TCI state can be the one with the highest index. For yet another instance, the default TCI state can be an active TCI state with the lowest index. For yet another instance, the default TCI state can be an active TCI state with the highest index. For yet another instance, the default TCI state can be the one associated with CORESET with the lowest index.

[0522] - In yet another example, the UE can apply a default QCL assumption, e.g., as the source RS for TCI state. For one instance, the default QCL assumption can be based on an AO-SSB, e.g., used for synchronization of the cell.

[0523] - In yet another example, the UE can apply the TCI state used or indicated before the indicated TCI state, e.g., the TCI state is associated with an AO-SSB, and / or the TCI state is an activated TCI state.

[0524] - In yet another example, the UE can select and apply a TCI state, e.g., the TCI state is associated with an AO-SSB, and / or the TCI state is an activated TCI state.

[0525] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0526] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0527] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0528] - For yet another instance, the index(es) of SSB associated with the indicated TCI state (e.g., SSB-index) can be included in the actually transmitted OD-SSB index(es) but not included in the actually transmitted AO-SSB index(es), e.g., SSB-index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0529] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0530] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0531] - For yet another instance, the association between the index(es) of SSB and the TCI state can be either in an explicit manner (e.g., SSB-index explicitly included in the TCI state) or in an implicit manner (e.g., the SSB is QCLed with the reference signal included in the TCI state).

[0532] For another further example, the UE applying the examples as the TCI state or QCL source until one of the following instances:

[0533] - For one instance, the UE applying the examples as the TCI state or QCL source until applying an indicated new TCI state (e.g., with an application delay after the indication of the new TCI state), if any.

[0534] - For another instance, the UE applying the examples as the TCI state or QCL source until applying a next TCI state indication (e.g., with an application delay after the next indication of the TCI state), if any.

[0535] For example, for a UE configured with both OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE can continue to apply the indicated TCI state, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0536] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE can continue to apply the indicated TCI state, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0537] In another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, the indicated (e.g., activated) TCI state is at least based on OD-SSB, the UE may not expect that the index(es) of SSB associated with the indicated TCI state (e.g., SSB-index) can be included in the actually transmitted OD-SSB index(es) but not included in the actually transmitted AO-SSB index(es), e.g., SSB-index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0538] For one further example, the index(es) for actually transmitted OD-SSB provided by each od-ssb-PositionsInBurst in the OD-SSB-Config is same as or a subset of the index(es) for actually transmitted AO-SSB provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0539] In yet another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, the indicated (e.g., activated) TCI state is at least based on OD-SSB, and the index(es) of SSB associated with the indicated TCI state (e.g., SSB-index) can be included in the actually transmitted OD-SSB index(es) but not included in the actually transmitted AO-SSB index(es), e.g., SSB-index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, then at least one of the following UE behavior can apply:

[0540] - In one example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted) when applying the indicated (e.g., activated) TCI state, e.g., at least for the transmission of OD-SSB corresponding to the indexes not included in the index(es) of AO-SSB.

[0541] - In another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted) when applying the indicated (e.g., activated) TCI state, e.g., at least for the transmission of OD-SSB corresponding to the indexes not included in the index(es) of AO-SSB and / or when the cell is active.

[0542] - In yet another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted) before applying an indication of a different TCI state (e.g., the different TCI state corresponds to an SSB index not terminated).

[0543] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0544] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0545] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0546] - For yet another instance, the index(es) of SSB associated with the indicated TCI state (e.g., SSB-index) can be included in the actually transmitted OD-SSB index(es) but not included in the actually transmitted AO-SSB index(es), e.g., SSB-index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0547] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0548] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0549] - For yet another instance, the association between the index(es) of SSB and the TCI state can be either in an explicit manner (e.g., SSB-index explicitly included in the TCI state) or in an implicit manner (e.g., the SSB is QCLed with the reference signal included in the TCI state).

[0550] For one example, for a UE configured with both OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, when applying the indicated TCI state, e.g., until applying an indicated new TCI state, if any, and / or when the SCell is activated.

[0551] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with an indicated TCI state corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE does not expect the transmission of SS / PBCH blocks corresponding to a SS / PBCH block index is terminated (e.g., due to deactivation or adaptation), when applying the indicated TCI state, e.g., until applying an indicated new TCI state, if any, and / or when the SCell is activated.

[0552] In various embodiments, an OD-SSB for uplink power control is provided.

[0553] In one embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform uplink power control at least based on OD-SSB (e.g., for downlink pathloss calculation), the UE may stop performing uplink power control based on OD-SSB after the transmission of OD-SSB is terminated (e.g., deactivated and / or adapted to be not transmitted).

[0554] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0555] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0556] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0557] - For yet another instance, the index(es) of OD-SSB configured for uplink power control (e.g., SSB-index) can be not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0558] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0559] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0560] For yet another further example, if the example instances are not satisfied, the UE may perform uplink power control based on either AO-SSB or OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated) or both AO-SSB and OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated), based on its implementation.

[0561] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for uplink power control corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE can stop perform the uplink power control, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0562] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for uplink power control corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE can stop perform the uplink power control, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0563] In another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform uplink power control at least based on OD-SSB (e.g., for downlink pathloss calculation), the UE may not expect that the index(es) of OD-SSB configured for uplink power control (e.g., SSB-index) is not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0564] For one further example, the index(es) for actually transmitted OD-SSB provided by each od-ssb-PositionsInBurst in the OD-SSB-Config is same as or a subset of the index(es) for actually transmitted AO-SSB provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0565] In yet another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform uplink power control at least based on OD-SSB (e.g., for downlink pathloss calculation), and the index(es) of OD-SSB configured for uplink power control (e.g., SSB-index) is not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, then at least one of the following UE behavior can apply:

[0566] - In one example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB.

[0567] - In another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB and / or when the cell is active.

[0568] - In yet another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted) before applying an indication of a different TCI state (e.g., the different TCI state corresponds to an SSB index not terminated).

[0569] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0570] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0571] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0572] - For yet another instance, the index(es) of OD-SSB configured for uplink power control (e.g., SSB-index) can be not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0573] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0574] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0575] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for uplink power control corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the uplink power control.

[0576] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for uplink power control corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the measurement or measurement report or e.g., when performing the uplink power control.

[0577] In various embodiments, an OD-SSB for radio link monitoring is provided.

[0578] In one embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform radio link monitoring at least based on OD-SSB, the UE may stop performing radio link monitoring based on OD-SSB after the transmission of OD-SSB is terminated (e.g., deactivated and / or adapted to be not transmitted).

[0579] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0580] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0581] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0582] - For yet another instance, the index(es) of OD-SSB configured for radio link monitoring (e.g., SSB-index) can be not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0583] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0584] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0585] In various embodiments, an OD-SSB for uplink power control is provided.

[0586] For yet another further example, if the example instances are not satisfied, the UE may perform radio link monitoring based on either AO-SSB or OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated) or both AO-SSB and OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated), based on its implementation.

[0587] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link monitoring corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE can stop perform the radio link monitoring, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0588] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link monitoring corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE can stop perform the radio link monitoring, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0589] In another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform radio link monitoring at least based on OD-SSB, the UE may not expect that the index(es) of OD-SSB configured for radio link monitoring (e.g., SSB-index) is not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0590] For one further example, the index(es) for actually transmitted OD-SSB provided by each od-ssb-PositionsInBurst in the OD-SSB-Config is same as or a subset of the index(es) for actually transmitted AO-SSB provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0591] In yet another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform radio link monitoring at least based on OD-SSB, and the index(es) of OD-SSB configured for radio link monitoring (e.g., SSB-index) is not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, then at least one of the following UE behavior can apply:

[0592] - In one example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB.

[0593] - In another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB and / or when the cell is active.

[0594] - In yet another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted) before applying an indication of a different TCI state (e.g., the different TCI state corresponds to an SSB index not terminated).

[0595] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0596] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0597] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0598] - For yet another instance, the index(es) of OD-SSB configured for radio link monitoring (e.g., SSB-index) can be not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0599] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0600] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0601] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link monitoring corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the radio link monitoring.

[0602] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link monitoring corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the measurement or measurement report or e.g., when performing the radio link monitoring.

[0603] In various embodiments, an OD-SSB for link recovery procedure is provided.

[0604] In one embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform radio link recovery at least based on OD-SSB, the UE may stop performing radio link recovery based on OD-SSB after the transmission of OD-SSB is terminated (e.g., deactivated and / or adapted to be not transmitted).

[0605] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0606] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0607] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0608] - For yet another instance, the index(es) of OD-SSB configured for radio link recovery (e.g., SSB-index) can be not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0609] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0610] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0611] For another further example, the UE may start to perform radio link recovery based on another RS.

[0612] - For one instance, the RS can be selected by the UE as an AO-SSB.

[0613] For yet another further example, if the example instances are not satisfied, the UE may perform radio link recovery based on either AO-SSB or OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated) or both AO-SSB and OD-SSB (e.g., OD-SSB corresponding to other index(es) which are not terminated), based on its implementation.

[0614] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link recovery corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE can stop perform the radio link recovery, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0615] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link recovery corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE can stop perform the radio link recovery, when the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, until applying an indicated new TCI state, if any.

[0616] In another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform radio link recovery at least based on OD-SSB, the UE may not expect that the index(es) of OD-SSB configured for radio link recovery (e.g., SSB-index) is not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0617] For one further example, the index(es) for actually transmitted OD-SSB provided by each od-ssb-PositionsInBurst in the OD-SSB-Config is same as or a subset of the index(es) for actually transmitted AO-SSB provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0618] In yet another embodiment, if a UE is configured with both AO-SSB and OD-SSB in the same cell, and the UE is configured to perform radio link recovery at least based on OD-SSB, and the index(es) of OD-SSB configured for radio link recovery (e.g., SSB-index) is not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, then at least one of the following UE behavior can apply:

[0619] - In one example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB.

[0620] - In another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted), e.g., at least for the indexes not included in the index(es) of AO-SSB and / or when the cell is active.

[0621] - In yet another example, the UE does not expect the transmission of OD-SSB to be terminated (e.g., deactivated and / or adapted to be not transmitted) before applying an indication of a different TCI state (e.g., the different TCI state corresponds to an SSB index not terminated).

[0622] For one further example, the embodiment is applicable when at least one of the following instances is satisfied.

[0623] - For one instance, the UE is provided with a configuration of a frequency location of AO-SSB on the cell, e.g., provided with a higher layer parameter absoluteFrequencySSB.

[0624] - For another instance, the UE is provided with a configuration of OD-SSB on the cell, e.g., provided with a higher layer parameter OD-SSB-Config.

[0625] - For yet another instance, the index(es) of OD-SSB configured for radio link monitoring (e.g., SSB-index) can be not included in the index(es) of transmitted AO-SSB, e.g., the index(es) corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB.

[0626] - For yet another instance, the frequency location of AO-SSB (e.g., provided by absoluteFrequencySSB) is different from the frequency location of OD-SSB (e.g., provided by od-ssb-absoluteFrequency in OD-SSB-Config).

[0627] - For yet another instance, the terminated transmission of OD-SSB corresponds to the index(es) of the actually transmitted OD-SSB index(es).

[0628] For example, for a UE configured with both od-ssb-absoluteFrequency in OD-SSB-Config and absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link recovery corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config but not corresponds to an actually transmitted SS / PBCH block index provided by ssb-PositionsInBurst associated with the absoluteFrequencySSB, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the radio link recovery.

[0629] For another example, for a UE configured with OD-SSB-Config and not configured with absoluteFrequencySSB for a SCell, if a SS / PBCH block index associated with a configuration for radio link recovery corresponds to an actually transmitted SS / PBCH block index provided by od-ssb-PositionsInBurst in the OD-SSB-Config, the UE does not expect the transmission of SS / PBCH blocks corresponding to the SS / PBCH block index is terminated due to deactivation or adaptation, e.g., until applying an indicated new TCI state, if any, or e.g., when performing the measurement or measurement report or e.g., when performing the radio link recovery.

[0630] FIG. 7 illustrates an example method 700 performed by a UE in a wireless communication system according to embodiments of the present disclosure. The method 700 of FIG. 7 can be performed by any of the UEs 111-116 of FIG. 1, such as the UE 116 of FIG. 3, and a corresponding method can be performed by any of the BSs 101-103 of FIG. 1, such as BS 102 of FIG. 2. The method 700 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0631] The method 700 begins with the UE receiving a set of higher layer parameters for a SCell (710). The UE then identifies, based on the set of higher layer parameters, a first configuration for a first SS / PBCH block and a second configuration for a second SS / PBCH block (720). For example, in 720, the first configuration includes a first frequency location for the first SS / PBCH block and a first indication of a first set of actually transmitted SS / PBCH block indexes for the first SS / PBCH block. The second configuration includes a second frequency location for the second SS / PBCH block and a second indication of a second set of actually transmitted SS / PBCH block indexes for the second SS / PBCH block. In various embodiments, the SS / PBCH block index is included in the second set of actually transmitted SS / PBCH block indexes and not included in the first set of actually transmitted SS / PBCH block indexes. In various embodiments, the first frequency location is different from the second frequency location.

[0632] The UE then determines a SS / PBCH block index to be associated with a TCI state (730). In various embodiments, the SS / PBCH block index is based on an index for a SS / PBCH block included in the TCI state or QCLed with a reference signal included in the TCI state. The UE then determines, when applying the TCI state, that transmission of the second SS / PBCH block corresponding to the SS / PBCH block index is not deactivated (740). In various embodiments, the UE determines to perform an uplink power control based on the second SS / PBCH block corresponding to the SS / PBCH block index and determines, when performing the uplink power control, that a transmission of the second SS / PBCH block corresponding to the SS / PBCH block index is not deactivated. In various embodiments, the uplink power control is for a PUCCH, a PUSCH, a SRS, or a PRACH. In various embodiments, the second SS / PBCH block is an on-demand SS / PBCH block.

[0633] FIG. 8 is a block diagram of a terminal or user equipment (UE) 800 according to an embodiment of the disclosure.

[0634] The terminal is an electronic device capable of wireless communication, may include a User Equipment (UE), a portable phone, a smartphone, a tablet, an Internet of things (IoT) device, etc., having various form factors, and may perform wireless communication with a base station (BS) through a wireless channel. Furthermore, the UE of FIG. 8 corresponds to the UE of FIG. 1 and FIG. 3.

[0635] Referring to FIG. 8, the UE 800 may include at least one transceiver (hereinafter, referred to as simply "transceiver") 801, at least one processor (hereinafter, referred to as simply "processor") 802, and at least one memory (hereinafter, referred to as simply "memory") 803. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 801, the processor 802, and the memory 803 of the UE 800 may operate. However, components of the UE 800 are not limited to the exemplary components illustrated in FIG. 8. In another embodiment, the UE 800 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 801, the processor 802, or the memory 803 may be integrated in the form of one component.

[0636] The transceiver 801 may be a communication circuit or communication circuitry that enables the UE 800 to perform wireless communication with a node or an entity of a network. For example, the transceiver 801 may enable the UE 800 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 801 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (801) may include all subsequent generations of evolved wireless communications.

[0637] According to an embodiment, the UE 800 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) sual connectivity (EN-DC), the UE 800 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 800 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 800 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0638] According to an embodiment, the transceiver 801 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 801 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 801 may output a signal received through a wireless channel to the processor 802 and may transmit, through a wireless channel, a signal output from the processor 802.

[0639] The processor 802 may control general operations of the UE 800 according to embodiments of the disclosure. The processor 802 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 802 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 803, individually, collectively or in any combination thereof. Further, the processor 802 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0640] The processor 802 may be electrically, operatively, or communicatively coupled to the transceiver 801 to control the transceiver 801.

[0641] The processor 802 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 802 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer) . In a specific embodiment, at least a part of the processor 802 may be included in one chip and the other part of the processor 802 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 801 or the memory 803.

[0642] The processor 802 may perform or control or cause an operation of the UE 800 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 802 may control operations of the UE 800 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 802 may execute a computer program, codes, or instructions stored in the memory 803, so as to control other components of the UE 800 to enable execution of various operations.

[0643] The memory 803 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 803 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0644] The memory 803 may be electrically, operatively, or communicatively coupled to the processor 802 and may be accessed by the processor 802.

[0645] The memory 803 may store a computer program, codes, or instructions executable by the processor 802. According to an embodiment, a computer program, codes, or instructions executable by the processor 802 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 803, the processor 802 may perform various functions according to an embodiment of the disclosure.

[0646] According to an embodiment of the disclosure, operations of the UE 800 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 803 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0647] FIG. 9 is a block diagram of a base station (BS) 900 according to an embodiment of the disclosure.

[0648] The BS 900 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 900 through a wireless channel. Furthermore, the BS of FIG. 9 corresponds to the BS of FIG. 1 and FIG. 2.

[0649] Referring to FIG. 9, the BS 900 may include at least one transceiver (hereinafter, referred to as simply "transceiver") 901, at least one processor (hereinafter, referred to as simply "processor") 902, and at least one memory (hereinafter, referred to as simply "memory") 903. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 901, the processor 902, and the memory 903 of the BS 900 may operate. However, components of the BS 900 are not limited to the exemplary components illustrated in FIG. 9. In another embodiment, the BS 900 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 901, the processor 902, or the memory 903 may be integrated in the form of one component.

[0650] The transceiver 901 may be a communication circuit or communication circuitry that enables the BS 900 to perform wireless communication with a node or an entity of a network. For example, the transceiver 901 may enable the BS 900 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 901 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (901) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 901 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 901 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 901 may output a signal received through a wireless channel to the processor 902 and may transmit, through a wireless channel, a signal output from the processor 902.

[0651] Meanwhile, according to an embodiment of the present disclosure, the BS 900 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 900 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 9, when the BS 900 performs wired communication, the BS 900 may further include a separate network interface for wired communication in addition to the transceiver 901. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0652] The processor 902 may control general operations of the BS 900 according to embodiments of the disclosure. The processor 902 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 902 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 903, individually, collectively or in any combination thereof. Further, the processor 902 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0653] The processor 902 may be electrically, operatively, or communicatively coupled to the transceiver 901 to control the transceiver 901.

[0654] The processor 902 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 902 may be included in one chip and the other part of the processor 902 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 901 or the memory 903.

[0655] The processor 902 may perform or control or cause an operation of the BS 900 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 902 may control operations of the BS 900 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 900 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 902 may execute a computer program, codes, or instructions stored in the memory 903, so as to control other components of the BS 900 to enable execution of various operations.

[0656] The memory 903 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 903 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0657] The memory 903 may be electrically, operatively, or communicatively coupled to the processor 902 and may be accessed by the processor 902.

[0658] The memory 903 may store a computer program, codes, or instructions executable by the processor 902. According to an embodiment, a computer program, codes, or instructions executable by the processor 902 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 903, the processor 902 may perform various functions according to an embodiment of the disclosure.

[0659] According to an embodiment of the disclosure, operations of the BS 900 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 903 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0660] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with network entity such as an Access and Mobility Management Function (AMF) or a Session Management Function (SMF) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0661] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0662] FIG. 10 is a block diagram of a network entity 1000 according to an embodiment of the disclosure.

[0663] The network entity 1000 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1000. Furthermore, the network entity of FIG. 10 corresponds to a network entity in the network of FIG. 1.

[0664] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0665] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0666] Referring to FIG. 10, the network entity 1000 may include at least one network interface 1001, at least one processor 1002 (hereinafter, "processor"), and at least one memory 1003 (hereinafter, "memory"). As described above, a NF may be implemented in the form of a physical device such as the network entity 1000, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 10. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0667] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1001, the processor 1002, and the memory 1003 of the network entity 1000 may operate. However, components of the network entity 1000 are not limited to the exemplary components illustrated in FIG. 10. In another embodiment, the network entity 1000 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1001, the processor 1002, or the memory 1003 may be integrated in the form of one component.

[0668] The network interface 1001 is a collective term for a transmitter part of the network entity 1000 and a receiver part of the network entity 1000, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1001 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1001 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1001 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0669] The processor 1002 may control general operations of the network entity 1000 according to embodiments of the disclosure. The processor 1002 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1002 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1003, individually, collectively or in any combination thereof. Further, the processor 1002 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0670] According to an embodiment, the processor 1002 may be electrically, operatively, or communicatively coupled to the network interface 1001 to control the network interface 1001.

[0671] The processor 1002 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1002 may be included in one chip and the other part of the processor 1002 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the network interface 1001 or the memory 1003.

[0672] The processor 1002 may perform or control or cause an operation of the network entity 1000 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1002 may control operations of the network entity 1000 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1002 may execute a computer program, codes, or instructions stored in the memory 1003, so as to control other components of the network entity 1000 to enable execution of various operations.

[0673] The memory 1003 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1003 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0674] The memory 1003 may be electrically, operatively, or communicatively coupled to the processor 1002 and may be accessed by the processor 1002.

[0675] The memory 1003 may store a computer program, codes, or instructions executable by the processor 1002. According to an embodiment, a computer program, codes, or instructions executable by the processor 1002 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1003, the processor 1002 may perform various functions according to an embodiment of the disclosure.

[0676] According to an embodiment of the disclosure, operations of the network entity 1000 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1003 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0677] Any of the above variation embodiments can be utilized independently or in combination with at least one other variation embodiment. The above flowchart(s) illustrate example methods that can be implemented in accordance with the principles of the present disclosure and various changes could be made to the methods illustrated in the flowcharts herein. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

[0678] Although the figures illustrate different examples of user equipment, various changes may be made to the figures. For example, the user equipment can include any number of each component in any suitable arrangement. In general, the figures do not limit the scope of the present disclosure to any particular configuration(s). Moreover, while figures illustrate operational environments in which various user equipment features disclosed in this patent document can be used, these features can be used in any other suitable system.

[0679] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the descriptions in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.

[0680] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from 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 and equivalents thereof.

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving, from a base station, a first configuration information on a first synchronization signal and physical broadcast channel (SS / PBCH) block (SSB) and a second configuration information on an absolute frequency of a second SSB for a secondary cell (SCell), wherein the first SSB is an on-demand (OD)-SSB;identifying an SSB index associated with a transmission control information (TCI) state; andidentifying whether a transmission of an SSB corresponding to the SSB index is deactivated, based on whether the SSB index corresponds to at least one of a first actually transmitted SSB index provided by the first configuration information, or a second actually transmitted SSB index provided by the second configuration information.2.The method of claim 1, wherein the identifying whether the transmission is deactivated comprises:if the SSB index corresponds to the first actually transmitted SSB index, and does not correspond to the second actually transmitted SSB index, identifying that the transmission is not deactivated.3.The method of claim 1, wherein the first actually transmitted SSB index is provided by an od-ssb-PositionsInBurst in the first configuration information.4.The method of claim 1, wherein the second actually transmitted SSB index is provided by an ssb-PosisionsInBurst associated with the absolute frequency of the second SSB.5.The method of claim 1, wherein the SSB index is identified based on an SSB-index parameter in the TCI state, or quasi-co-located (QCLed) with a reference signal in the TCI state.6.The method of claim 1, further comprising:identifying a reference signal (RS) for estimating a pathloss as an SSB;identifying a type of the SSB for the estimation;estimating the pathloss for an uplink power control based on the type of the SSB; andperforming the uplink power control based on the estimated pathloss.7.The method of claim 6, wherein the type of the SSB is identified based on an higher layer parameter.8.The method of claim 6, wherein the uplink power control is for a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), or a physical random access channel (PRACH).9.A user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:receive, from a base station, a first configuration information on a first synchronization signal and physical broadcast channel (SS / PBCH) block (SSB) and a second configuration information on an absolute frequency of a second SSB for a secondary cell (SCell), wherein the first SSB is an on-demand (OD)-SSB,identify an SSB index associated with a transmission control information (TCI) state, andidentify whether a transmission of an SSB corresponding to the SSB index is deactivated, based on whether the SSB index corresponds to at least one of a first actually transmitted SSB index provided by the first configuration information, or a second actually transmitted SSB index provided by the second configuration information.10.The UE of claim 9, wherein the instructions cause the UE to:if the SSB index corresponds to the first actually transmitted SSB index, and does not correspond to the second actually transmitted SSB index, identifying that the transmission is not deactivated.11.The UE of claim 9, wherein the first actually transmitted SSB index is provided by an od-ssb-PositionsInBurst in the first configuration information.12.The UE of claim 9, wherein the second actually transmitted SSB index is provided by an ssb-PosisionsInBurst associated with the absolute frequency of the second SSB.13.The UE of claim 9, wherein the SSB index is identified based on an SSB-index parameter in the TCI state, or quasi-co-located (QCLed) with a reference signal in the TCI state.14.The UE of claim 9, wherein the instructions further cause the UE to:identify a reference signal (RS) for estimating a pathloss as an SSB,identify a type of the SSB for the estimation,estimate the pathloss for an uplink power control based on the type of the SSB, andperform the uplink power control based on the estimated pathloss.15.The UE of claim 14,wherein the type of the SSB is identified based on an higher layer parameter,wherein the uplink power control is for a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), or a physical random access channel (PRACH).