Method and device for transmitting or receiving plurality of synchronization signal blocks in secondary cell in wireless communication system
The method and device for determining synchronization signal block indices in 6G wireless communication systems address the challenge of efficient synchronization in secondary cells, enhancing data transmission and reducing latency.
Patent Information
- Application Number
- PCT/KR2025/011856
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-02-06
- Filing Date
- 2025-08-07
- Publication Date
- 2026-02-12
AI Technical Summary
The challenge of efficiently transmitting and receiving multiple synchronization signal blocks in a secondary cell within a wireless communication system, particularly in 6G networks, where high data rates, low latency, and ultra-reliable connectivity are critical, is not adequately addressed by existing technologies.
A method and device for transmitting and receiving a plurality of synchronization signal blocks in a secondary cell, where the index of a half-frame including a second synchronization signal block is determined based on half-frame index information related to a first synchronization signal block, enabling synchronized communication.
Enhances synchronization in 6G wireless communication systems by ensuring efficient and reliable transmission of synchronization signal blocks, supporting high data rates and low latency requirements.
Smart Images

Figure KR2025011856_12022026_PF_FP_ABST
Abstract
Description
Method and device for transmitting or receiving multiple synchronization signal blocks in a secondary cell in a wireless communication system
[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for transmitting or receiving a plurality of synchronization signal blocks in a secondary cell in a wireless communication system.
[0002] The fifth generation (5G) wireless communication system, the successor to 4G LTE (long-term evolution), is a new, clean-slate mobile communication system characterized by high performance, low latency, and high availability. 5G NR (New Radio) can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to intermediate-frequency bands between 1 GHz and 10 GHz, and to high-frequency (or millimeter wave) bands above 24 GHz. 6G wireless communication systems are being developed based on the underlying technologies of 5G wireless communication.
[0003] The 6G wireless communication system is being developed with the goals of (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity. Considering the requirements of the 6G system, such as a peak data rate of 1 Tbps per device, an end-to-end latency of 1 ms, a maximum spectrum efficiency of 100 bps / Hz, support for mobility of 1000 km / h, satellite integration, artificial intelligence (AI), autonomous vehicles, extended reality (XR), and haptic communication, various technologies are being researched.
[0004] The technical problem of the present disclosure is to provide a method and device for transmitting or receiving a plurality of synchronization signal blocks in a secondary cell in a wireless communication system.
[0005] An additional technical problem of the present disclosure is to provide a method and apparatus for performing transmission or reception of a second synchronization signal block in a secondary cell based on information related to a first synchronization signal block in the secondary cell in a wireless communication system.
[0006] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.
[0007] A method according to one aspect of the present disclosure may include the steps of: receiving, by a terminal, information related to a first synchronization signal block on a cell; and receiving, by the terminal, a second synchronization signal block on the cell based on information related to a second synchronization signal block. Based on half-frame index information related to the second synchronization signal block being provided, an index of a half-frame including the second synchronization signal block may be determined based on the half-frame index information.
[0008] A method according to an additional aspect of the present disclosure may include the steps of transmitting, by a base station, information related to a first synchronization signal block on a cell; and, based on information related to a second synchronization signal block, transmitting, by the base station, the second synchronization signal block on the cell. Based on half-frame index information related to the second synchronization signal block being provided, an index of a half-frame including the second synchronization signal block may be determined based on the half-frame index information.
[0009] According to the present disclosure, a method and device for transmitting or receiving a plurality of synchronization signal blocks in a secondary cell in a wireless communication system can be provided.
[0010] According to the present disclosure, a method and device for performing transmission or reception of a second synchronization signal block in a secondary cell based on information related to a first synchronization signal block in the secondary cell in a wireless communication system can be provided.
[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.
[0012] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.
[0013] Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.
[0014] FIG. 2 illustrates an example of a communication system to which some examples of the present disclosure may be applied.
[0015] FIG. 3 illustrates an example of a wireless device to which some examples of the present disclosure may be applied.
[0016] FIG. 4 exemplarily illustrates a communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.
[0017] FIG. 5 illustrates a functional framework for AI operations to which some examples of the present disclosure may be applied.
[0018] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.
[0019] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.
[0020] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.
[0021] FIG. 9 illustrates an electromagnetic spectrum to which some examples of the present disclosure may be applied.
[0022] FIG. 10 illustrates an example of a system information transmission / reception procedure to which some examples of the present disclosure may be applied.
[0023] FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.
[0024] Figures 12 and 13 illustrate examples of NTN scenarios to which some examples of the present disclosure may be applied.
[0025] FIG. 14 illustrates examples of sensing operations to which some examples of the present disclosure may be applied.
[0026] FIG. 15 illustrates an example of cell DTX / DRX operation to which some examples of the present disclosure may be applied.
[0027] FIG. 16 illustrates an example of carrier aggregation (CA) operation including an SSB-less cell to which some examples of the present disclosure may be applied.
[0028] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.
[0029] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.
[0030] FIG. 19 illustrates examples of on-demand SIB1 operation to which some examples of the present disclosure may be applied.
[0031] FIG. 20 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.
[0032] FIG. 21 is a drawing illustrating an example of a method performed by a base station according to the present disclosure.
[0033] FIG. 22 is a drawing for explaining the start time of OD SSB transmission / reception according to the present disclosure.
[0034] FIG. 23 is a drawing for explaining the OD SSB transmission / reception termination point according to the present disclosure.
[0035] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.
[0036] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.
[0037] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.
[0038] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.
[0039] The terminology used in this disclosure is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.
[0040] In this disclosure, "A or B" can mean "only A," "only B," or "both A and B." In other words, "A or B" in this disclosure can be interpreted as "A and / or B." For example, "A, B or C" in this disclosure can mean "only A," "only B," "only C," or "any combination of A, B and C."
[0041] As used herein, a slash ( / ) or a comma may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B, or C."
[0042] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”
[0043] Additionally, in the present disclosure, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”
[0044] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be described as an example of "control information." In other words, "control information" in the present disclosure is not limited to "PDCCH," and "PDCCH" may be described as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be described as an example of "control information."
[0045] In the following description, 'when, if, in case of' can be replaced with 'based on'.
[0046] Technical features individually described in one drawing in this disclosure may be implemented individually or simultaneously.
[0047] In the present disclosure, a terminal or user equipment (UE) may be a portable device and may be a first node that receives a signal from a base station / second node / IAB (integrated access backhaul) node.
[0048] In the present disclosure, a base station (BS) may be a second node / IAB node / Transmission-Reception Point (TRP).
[0049] In the present disclosure, higher layer parameters may be parameters configured, pre-configured, or pre-defined for the terminal. For example, a base station or a network may transmit higher layer parameters to the terminal. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.
[0050] In the present disclosure, "setting or defining" may be interpreted as being set to a device through predefined signaling (e.g., SIB (system information block), MAC, RRC) from a base station or network. In the present disclosure, "setting or defining" may be interpreted as being set to a device through separate signaling or being defined in advance without separate signaling.
[0051] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.
[0052] The technology described in the present disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.
[0053] The technology described in the present disclosure can be implemented with 6G wireless technology and applied to various 6G systems. For example, the 6G system can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.
[0054] Network structure
[0055] Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.
[0056] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as integrated access backhaul (IAB) nodes, relays, and radio frequency (RF) repeaters, as illustrated in Figure 1, may be applied, or a non-terrestrial network (NTN) may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, or in the case of a network-controlled repeater, it may not only amplify and forward signals but also adjust its transmission and reception settings based on information provided by the network. For example, NTN nodes could be satellites or aircraft that provide NTN coverage that terrestrial networks struggle to provide. Beyond these examples, various intermediate points can be introduced to improve the network topology.
[0057] Referring to Figure 1, a split RAN can support the division of a base station into a centralized unit (CU) and one or more distributed units (DUs). The CU and DU can correspond to logical units. The CU can be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DUs, various intermediate points can be introduced to compensate for this.
[0058] An intermediate point may correspond to a terminal or a base station, depending on its relationship to other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a unit (DU). The MT may connect the IAB node to a donor node. The unit (DU) of an IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to the terminal. For example, an IAB node may correspond to a base station in its relationship to a user-side node, and to a terminal in its relationship to a network-side node.
[0059] In some examples of the present disclosure, the description of a terminal may equally apply not only to a user-side endpoint, but also to an intermediate point corresponding to a terminal in a relative relationship with a network-side endpoint. Similarly, in some examples of the present disclosure, the description of a base station may equally apply not only to a network-side endpoint, but also to an intermediate point corresponding to a base station in a relative relationship with a user-side endpoint. In most cases where there is no additional description of the operations of three or more entities, the communicating entities in the present disclosure are briefly described as terminals and / or base stations (or first nodes and / or second nodes), where the terms terminal and / or base stations (or first nodes and / or second nodes) are interpreted to include / replace any endpoint or any intermediate point in relation to other nodes.
[0060] As such, in some examples of the present disclosure, for the sake of simplicity of explanation, the subjects of the operation may be referred to as terminals and / or base stations (or first nodes and / or second nodes). In addition, the terms terminal and / or base station (or first node and / or second node) may also be interpreted / replaced as in the following examples: For example, the terminal (or first node) and the base station (or second node) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.
[0061] In the present disclosure, there may be zero or more intermediate points between the base station and the terminal. If an intermediate point exists, it may correspond to an IAB node / relay / RF repeater / NTN node, or a node supporting other functions. The intermediate point may be a node with a fixed location or a node with an unfixed location.
[0062] Systems applicable to this disclosure
[0063] FIG. 2 illustrates an example of a communication system to which some examples of the present disclosure may be applied.
[0064] The communication system (100) applied to the present disclosure includes a wireless device (110), a network device (120), and a network (130). Here, the wireless device (110) refers to a device that performs communication using a wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Things) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point.The network device (120) may correspond to a base station (or second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may act as a network device (120) to another wireless device (110).
[0065] Wireless devices (110a to 110f) can be connected to a network (130) via a network device (120). AI technology can be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) via a network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR), or a 6G network. The wireless devices (110a to 110f) can communicate with each other via the network device (120) / network (130), but can also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Additionally, an IoT device (110f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or another wireless device (110a to 110f).
[0066] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120), network devices (120) / network devices (120). Here, the wireless communication / connection can be established through various wireless access technologies such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless device and the network device / wireless device, and the network device and the network device can transmit / receive wireless signals to each other. For example, the wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various descriptions of the present disclosure, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc., may be performed.
[0067] Device applicable to the present disclosure
[0068] FIG. 3 illustrates an example of a wireless device to which some examples of the present disclosure may be applied.
[0069] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208).
[0070] The processor (202) controls the memory (204) and / or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including second information / signal via the transceiver (206), and then store information obtained from signal processing of the second information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may store software code including instructions for performing some or all of the processes controlled by the processor (202), or for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via at least one antenna (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF (radio frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.
[0071] Hereinafter, the hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., a functional layer such as physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and service data adaptation protocol (SDAP)). At least one processor (202) may generate at least one Protocol Data Unit (PDU) and / or at least one Service Data Unit (SDU) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) may generate a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) can generate a signal (e.g., a baseband signal) comprising a PDU, an SDU, a message, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this document, and provide the signal to at least one transceiver (206). At least one processor (202) can receive a signal (e.g., a baseband signal) from at least one transceiver (206) and obtain the PDU, SDU, message, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document.
[0072] At least one processor (202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The at least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in the at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be included in the at least one processor (202), or may be stored in at least one memory (204) and driven by the at least one processor (202). The descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.
[0073] At least one memory (204) can be connected to at least one processor (202) and can store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The at least one memory (204) can be configured as a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory, a hard drive, a register, a cache memory, a computer readable storage medium and / or a combination thereof. The at least one memory (204) can be located internally and / or externally to the at least one processor (202). In addition, the at least one memory (204) can be connected to the at least one processor (202) via various technologies such as a wired or wireless connection.
[0074] At least one transceiver (206) can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed in this document from at least one other device. For example, at least one transceiver (206) can be connected to at least one processor (202) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. Additionally, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document via at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using at least one processor (202).At least one transceiver (206) may convert user data, control information, wireless signals / channels, etc. processed by at least one processor (202) from a baseband signal to an RF band signal. For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.
[0075] The components of the wireless device described with reference to FIG. 3 may be referred to by different terms in terms of functionality. For example, the processor (202) may be referred to as a control unit, the transceiver (206) as a communication unit, and the memory (204) as a storage unit. In some cases, the communication unit may be used to mean at least a portion of the processor (202) and the transceiver (206).
[0076] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least a portion of various devices. For example, the structure of the wireless device illustrated in FIG. 3 can be at least a portion of various devices described with reference to FIG. 2 (e.g., a robot (110a), a vehicle (110b-1, 110b-2), an XR device (110c), a portable device (110d), a home appliance (110e), an IoT device (110f), an AI device / server (110g)). Furthermore, according to various embodiments, in addition to the components illustrated in FIG. 3, the device may further include other components.
[0077] For example, the device may be a portable device such as a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), or a portable computer (e.g., a laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., an audio input / output port, a video input / output port), and an input / output unit for inputting and outputting image information / signals, audio information / signals, data, and / or information input from a user.
[0078] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired / wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting, and a position measurement unit that obtains location information of the mobile device through a global positioning system (GPS) and various sensors.
[0079] For example, the device may be an XR device such as an HMD, a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that obtains control information, data, etc. from the outside and outputs the generated XR object, and a sensor unit that senses status information, environmental information, and user information of the device or the surroundings of the device.
[0080] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc. types depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a driving unit that performs various physical actions, such as moving the robot joints.
[0081] For example, the device may be an AI device such as a TV, a projector, a smartphone, a PC, a laptop, a digital broadcasting terminal, a tablet PC, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, digital signage, a robot, a vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a training unit that trains a model composed of an artificial neural network using learning data.
[0082] The structure of the wireless device illustrated in FIG. 3 may be understood as a part of a terminal (or first node), or as a part of an intermediate point, or as a part of a base station (or second node). If the device illustrated in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and / or back haul communications. If the front haul and / or back haul communications are based on wireless communications, at least one transceiver (206) illustrated in FIG. 3 may be used for front haul and / or backhaul communications, and a wired transceiver may not be included.
[0083] Communication procedures
[0084] FIG. 4 exemplarily illustrates a communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.
[0085] FIG. 4 illustrates operations of a first node (110) (e.g., a terminal) and a second node (120) (e.g., a base station) transmitting and / or receiving data and operations performed prior thereto.
[0086] In step S101, the first node (110) and the second node (120) can perform synchronization. For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect at least one synchronization signal transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals (e.g., a primary synchronization signal, a secondary synchronization signal) classified according to a structure or purpose. Through this, the terminal (110) can confirm the boundaries of the frame, subframe, slot, and / or symbol of the base station (120) and obtain information (e.g., a cell identifier) about the base station (120).
[0087] In step S103, the first node (110) can obtain system information transmitted from the second node (120). For example, the system information is information related to the properties, characteristics, and / or capabilities of the base station (120) required to access the base station (120) and use the service, and can be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., the channel used, whether it is provided in an on-demand manner), etc., and can be classified into, for example, a master information block (MIB) and a system information block (SIB). If necessary, the terminal (110) can transmit a signal requesting system information before receiving the system information. Such requesting and providing of system information may be performed after a random access procedure described below.
[0088] In step S105, the first node (110) and the second node (120) can perform a random access procedure. For example, the terminal (110) can transmit and / or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for a random access procedure based on information related to a random access channel of the base station (120) obtained through system information (e.g., channel position, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) may transmit a preamble (e.g., message 1 (MSG1)) over a random access channel, receive a random access response (RAR) message (e.g., message 2 (MSG2)), transmit a message (e.g., message 3 (MSG3)) including information related to the terminal (110) (e.g., identification information) using scheduling information included in the RAR message to the base station (120), and receive a message for contention resolution and / or connection establishment (e.g., message 4 (MSG4)). As another example, MSG1 and MSG3 may be transmitted and received as one message (e.g., message A (MSG A)), or MSG2 and MSG4 may be transmitted and received as one message (e.g., message B (MSG B)).
[0089] In step S107, the first node (110) and the second node (120) can perform signaling of control information. For example, the control information can be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.
[0090] In step S109, the first node (110) and the second node (120) can transmit and / or receive data. For example, the terminal (110) and the base station (120) can process, transmit, and / or receive data based on signaling of control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on information bits. For example, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.
[0091] 6G system core technologies
[0092] As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, free space optics (FSO) backhaul network, massive MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.
[0093] artificial intelligence
[0094] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.
[0095] FIG. 5 illustrates a functional framework for AI operations to which some examples of the present disclosure may be applied.
[0096] Below, to explain AI (or AI / ML (machine learning)) in more detail, the terms can be defined as follows.
[0097] - Data collection: Data collected from network nodes, management entities, or terminals as a basis for AI model training, data analysis, and inference.
[0098] - AI model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.
[0099] - AI / ML training: An online or offline process of training an AI model by learning features and patterns that best represent the data and obtain a trained AI / ML model for inference.
[0100] - AI / ML inference: The process of making predictions or inducing decisions based on collected data and the AI model using a trained AI model.
[0101] Referring to FIG. 5, the data collection function (10) is a function that collects input data and provides processed input data to the model training function (20) and the model inference function (30).
[0102] Examples of input data may include measurements from terminals or other network entities, feedback from actors, and output from AI models.
[0103] The data collection function (10) performs data preparation based on input data and provides input data processed through the data preparation. Here, the data collection function (10) does not perform data preparation specific to each AI algorithm (e.g., data pre-processing and cleaning, formatting, and transformation), but can perform data preparation common to all AI algorithms.
[0104] After the data preparation process is performed, the data collection function (10) may provide training data (11) to the model training function (20) and may provide inference data (12) to the model inference function (30). Here, the training data (11) may correspond to data required as input for the AI model training function (20), and the inference data (12) may correspond to data required as input for the AI model inference function (30).
[0105] The data collection function (10) may be performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), but may also be performed by multiple entities. In this case, training data (11) and inference data (12) may be provided to the model training function (20) and model inference function (30), respectively, from multiple entities.
[0106] The model training function (20) may correspond to a function that performs AI model training, validation, and testing, which can generate model performance metrics as part of the AI model testing procedure. If necessary, the model training function (20) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation, etc.) based on training data (11) provided by the data collection function (10).
[0107] Here, model deployment / update (13) can be used to initially deploy a trained, validated and tested AI model to the model inference function (30) or to provide an updated model to the model inference function (30).
[0108] The model inference function (30) may correspond to a function that provides AI model inference output (16) (e.g., prediction or decision). If applicable, the model inference function (30) may provide model performance feedback (14) to the model training function (20). In addition, the model inference function (30) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting and transformation, etc.) based on inference data (12) provided by the data collection function (10), if necessary.
[0109] Here, output (16) refers to the inference output of the AI model generated by the model inference function (30), and the details of the inference output may vary depending on the use case.
[0110] Model performance feedback (14) can be used to monitor the performance of the AI model, if available, and this feedback may be omitted.
[0111] An actor function (40) is a function that receives an output (16) from a model inference function (30) and triggers or performs a corresponding task / action. The actor function (40) can trigger tasks / actions for other entities (e.g., one or more terminals, one or more RAN nodes, one or more network nodes, etc.) or for itself.
[0112] Feedback (15) can be used to derive training data (11), inference data (12), or to monitor the performance of the AI model, its impact on the network, etc.
[0113] Meanwhile, the definitions of training / validation / test in data sets used in AI / ML can be distinguished as follows.
[0114] - Training data: refers to a data set for learning a model.
[0115] - Validation data: This refers to a dataset used to validate a model that has already completed training. Validation data can typically be used to prevent overfitting of the training data set. It can also be used to select the best model among the various models learned during the training process. Therefore, validation can be considered a type of learning.
[0116] - Test data: This refers to the data set for final evaluation. This data is unrelated to learning.
[0117] For example, the training and validation data can be divided into an 8:2 or 7:3 ratio within the entire data set. Alternatively, the training data:validation data:test data can be divided into a 6:2:2 ratio within the entire data set.
[0118] The level of cooperation can be defined as follows depending on whether the base station and the terminal have capabilities for AI / ML functions, and variations due to combination of multiple levels or separation of any one level are also possible.
[0119] Category 0a: This category corresponds to a no-collaboration framework. In this case, AI / ML algorithms are purely implementation-based and may not require any changes to the wireless interface.
[0120] Category 0b: Frameworks that involve a wireless interface modified to fit efficient implementation-based AI / ML algorithms, but without collaboration.
[0121] Category 1: This category applies to cases where inter-node support is required to improve the AI / ML algorithms of each node. For example, this applies when a terminal receives support from a base station (for training, adaptation, etc.), and vice versa. At this level, model exchange between network nodes is not required.
[0122] Category 2: This applies to cases where joint ML tasks can be performed between terminals and base stations. This level requires exchange of AI / ML model commands or network nodes.
[0123] The functions exemplified in FIG. 5 above may be implemented in a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.), a network node, an OAM (operation administration maintenance) of a network operator, or a terminal.
[0124] Alternatively, two or more entities, such as a RAN, a network node, a network operator's OAM, or a terminal, may cooperate to implement the functions illustrated in FIG. 5. For example, one entity may perform some of the functions of FIG. 5, and another entity may perform the remaining functions. In this way, since some of the functions illustrated in FIG. 5 are performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), the transmission / provision of data / information between each function may be omitted. For example, if the model training function (20) and the model inference function (30) are performed by the same entity, the transmission / provision of model deployment / update (13) and model performance feedback (14) may be omitted.
[0125] Alternatively, any one of the functions illustrated in FIG. 5 may be performed collaboratively by two or more entities, including a RAN, a network node, a network operator's OAM, or a terminal. This may be referred to as a split AI operation.
[0126] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.
[0127] For example, the AI model training function may be performed by a network node (e.g., a core network node, an OAM of a network operator, etc.), and the AI model inference function may be performed by a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.).
[0128] Step 1: RAN node 1 and RAN node 2 can transmit input data (e.g., training data) for AI model training to the network node. Here, RAN node 1 and RAN node 2 can also transmit data collected from the terminal (e.g., terminal measurements related to RSRP (reference signal received power), RSRQ (reference signal received quality), SINR (signal to interference-plus-noise ratio) of the serving cell and neighboring cells, terminal location, speed, etc.) to the network node.
[0129] Step 2: Network nodes can train AI models using the received training data.
[0130] Step 3: The network node may distribute / update the AI model to RAN node 1 and / or RAN node 2. RAN node 1 (and / or RAN node 2) may also continue model training based on the received AI model.
[0131] For convenience of explanation, we assume that the AI model is deployed / updated only to RAN node 1.
[0132] Step 4: RAN node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN node 2.
[0133] Step 5: RAN node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).
[0134] Step 6: If applicable, RAN node 1 may send model performance feedback to the network nodes.
[0135] Step 7: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.
[0136] Step 8: RAN node 1 and RAN node 2 can transmit feedback information to the network nodes.
[0137] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.
[0138] For example, both AI model training functions and AI model inference functions can be performed by RAN nodes (e.g., base stations, TRPs, CUs of base stations, etc.).
[0139] Step 1: The terminal and RAN node 2 can transmit input data (e.g., training data) for AI model training to RAN node 1.
[0140] Step 2: RAN node 1 can train an AI model using the received training data.
[0141] Step 3: RAN node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN node 2.
[0142] Step 4: RAN node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).
[0143] Step 5: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.
[0144] Step 6: RAN node 2 may transmit feedback information to RAN node 1.
[0145] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.
[0146] For example, the AI model training function may be performed by a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.), and the AI model inference function may be performed by a terminal.
[0147] Step 1: The terminal may transmit input data (e.g., training data) for AI model training to the RAN node. Here, the RAN node may collect data (e.g., terminal measurements related to RSRP, RSRQ, SINR of the serving cell and neighboring cells, terminal location, speed, etc.) from various terminals and / or from other RAN nodes.
[0148] Step 2: RAN nodes can train AI models using the received training data.
[0149] Step 3: The RAN node can distribute / update the AI model to the terminal. The terminal can also continue model training based on the received AI model.
[0150] Step 4: Input data (e.g., inference data) for AI model inference can be received from the terminal and RAN node (and / or from another terminal).
[0151] Step 5: The terminal can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).
[0152] Step 6: If applicable, the terminal may send model performance feedback to the RAN node.
[0153] Step 7: The terminal and RAN node can perform actions based on the output data.
[0154] Step 8: The terminal may transmit feedback information to the RAN node.
[0155] THz communication (terahertz communication)
[0156] Data transmission rates can be increased by increasing bandwidth. This can be achieved by utilizing sub-THz communications with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (the sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase 6G cellular capacity. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.
[0157] FIG. 9 illustrates an electromagnetic spectrum to which some examples of the present disclosure may be applied.
[0158] Key characteristics of THz communications include (i) the widely available bandwidth to support very high data rates, and (ii) the high path loss at high frequencies (which necessitates highly directional antennas). The narrow beamwidths generated by highly directional antennas reduce interference. The small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.
[0159] Transmitting system information (e.g., MIB) in a cell in the THz frequency band can be inefficient because the beam width in high-frequency bands narrows, requiring more beam sweeps to cover the entire cell area. This method is particularly inefficient when there are only a few users within the cell.
[0160] FIG. 10 illustrates an example of a system information transmission / reception procedure to which some examples of the present disclosure may be applied.
[0161] The example of Fig. 10 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applicable. Furthermore, the procedure illustrated in Fig. 10 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Fig. 10.
[0162] In step S1010, the second node (120) (e.g., base station) can transmit system information of cell #1 via cell #2. For example, the base station provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one of an SFN (system frame number), a PDCCH configuration for SIB1, cell barring, cell re-selection, and subcarrier spacing generated in a higher layer, and may include at least one of an SFN, a half frame indicator, and an SSB index (synchronization signal / PBCH (physical broadcast channel) block index) generated in a physical layer. For this purpose, as an example, cell #1 and cell #2 may have a relationship of a secondary cell and a primary cell.
[0163] At step S1030, the first node (110) (e.g., terminal) can acquire synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information, but since the system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, the terminal can acquire synchronization based on the system information. Alternatively, synchronization acquisition can be performed before step S1010.
[0164] At step S1050, the first node (110) may transmit a signal for accessing cell #1. For example, the signal may include a random access preamble. The structure of this signal and the resources (e.g., channels) for transmitting the signal may be identified through system information. Thereafter, at step S1070, the first node (110) and the second node (120) may perform an access procedure for cell #1 and communicate.
[0165] The procedure described with reference to FIG. 10 may be performed when the first node (110) initially connects to cell #1 of the second node (120). Alternatively, a similar procedure may be performed when the first node (110) hands over to cell #1 of the second node (120). However, in the case of handover, the system information of cell #1 may be received from a cell of a base station other than cell #2 of the second node (120).
[0166] Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations may be required to use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control in addition to beamforming, and the number of beams used increases significantly. Consequently, it takes a very long time to align the transmit and receive beams between the base station and terminals. Furthermore, if the beam alignment between the base station and terminals is misaligned due to movement or movement of the terminals, frequent re-alignment is required, which can lead to link instability.
[0167] FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.
[0168] Although FIG. 11 illustrates an example of a procedure for searching and / or selecting beams for THz communication, this procedure is not limited to a THz environment and can also be applied to a 6G communication environment where THz communication is not applied.
[0169] Here, beam may be interpreted as other terms having equivalent technical meanings that can distinguish beams, such as 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', reference signal (RS) resource that distinguishes beams, SSB index, etc.
[0170] In step S1110, the second node (120) (e.g., base station) can set resources for beam management to the first node (110) (e.g., terminal). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from an existing downlink signal / channel for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can be a different port from a port for transmitting an existing downlink signal / channel (e.g., SSB, PDSCH (physical downlink shared channel), etc.). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. For example, a signal transmitted based on a dedicated port defined / set for beam search can be included in the technical concept according to the present embodiment.
[0171] In step S1130, the second node (120) (e.g., base station) transmits measurement signals using a plurality of transmission beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams that require measurement, and may also be transmitted in a multi-beam transmission method that forms a plurality of beams simultaneously to reduce sweeping time. Here, the multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).
[0172] In step S1050, a first node (110) (e.g., a terminal) may transmit a feedback signal to a second node (120) (e.g., a base station). The feedback signal may indicate at least one beam selected by the terminal. The terminal may select at least one preferred beam based on the measurement signals received in step S1030.
[0173] In step S1070, the first node (110) and the second node (120) can perform communication. For example, the second node (120) can perform transmission to the first node (110) using the reception beam of the first node (110) selected in step S1050. If channel reciprocity is established, the transmission beam of the first node (110) can also be determined through steps S1030 and S1050, so that the transmission operation from the first node (110) can also be performed using a beam that has a reciprocal relationship with the beam selected in step S1050. If channel reciprocity is not established, a procedure including transmission of measurement signal(s) by the first node (110) and transmission of feedback signal(s) by the second node (120) may be performed first to determine the transmission beam of the first node (110).
[0174] non-terrestrial networks (NTN)
[0175] Figures 12 and 13 illustrate examples of NTN scenarios to which some examples of the present disclosure may be applied.
[0176] NTN can represent a network or network segment that uses radio frequency (RF) resources mounted on a satellite (or unmanned aerial system (UAS) platform).
[0177] Figure 12 shows an example of a typical scenario of NTN based on transparent payload, and Figure 13 shows an example of a typical scenario of NTN based on regenerative payload.
[0178] Referring to Figure 12, a satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) can be connected to a gateway via a feeder link. The satellite can be connected to a data network via the gateway. The beam footprint can refer to the area where the signal transmitted by the satellite can be received.
[0179] Referring to Figure 13, a satellite (or UAS platform) can establish a service link with a terminal. A satellite (or UAS platform) connected to a terminal can be connected to another satellite (or UAS platform) via an inter-satellite link (ISL). The other satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on the regenerated payload, the satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.
[0180] Figures 12 and 13 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios. For example, a satellite (or UAS platform) can implement a transparent or regenerative (e.g., with onboard processing) payload. For example, a satellite (or UAS platform) can generate multiple beams across a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) can vary depending on the onboard antenna diagram and the minimum elevation angle.
[0181] For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may remain unchanged.
[0182] For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, a regenerative payload may be substantially equivalent to mounting all or part of a base station function on a satellite (or UAS platform).
[0183] Integrated Sensing and Communication (ISAC)
[0184] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (or range) of an object, and thus obtain information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a networked device to connect to the object, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, such as sensing operations, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing offers an opportunity to enhance existing communication systems from a communications network to a wireless communication and sensing network.
[0185] FIG. 14 illustrates examples of sensing operations to which some examples of the present disclosure may be applied.
[0186] Specifically, Fig. 14(a) shows an example of a monostatic sensing operation using a sensing receiver and a sensing transmitter located in the same location. Fig. 14(b) shows an example of a bistatic sensing operation using a sensing receiver and a sensing transmitter located in separate locations. A sensing signal transmitted from a sensing transmitter is reflected / scattered by a sensing object, and the sensing receiver can receive the signal, and extract / obtain sensing data based on the received signal. A sensing result can be generated / determined through appropriate processing of the sensing data. The sensing result can be provided to a trusted third-party entity / service outside the 3GPP system through an entity / service within the 3GPP system.
[0187] Network Energy Saving (NES)
[0188] Energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing operational expenditures (OPEX) for telecommunications providers. In particular, the introduction of 5G communications will require higher transmission rates, necessitating base stations to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached as high as 20% of total OPEX. For example, various technologies for reducing energy consumption in 5G wireless communication systems are being discussed under the term "network energy savings" (NES).
[0189] Depending on the application of NES technology, the base station can perform operations such as controlling on / off for a certain time duration in the time domain, controlling transmission / reception resources for terminal-common or terminal-specific signals / channels, changing the amount of frequency domain resources, controlling transmission power, or turning on / off an antenna port, transmission-reception point (TRP), etc. in the spatial domain.
[0190] For example, a base station may identify the NES solution(s) to be applied, perform signaling to the NES, and perform actions on the NES.
[0191] NES solution(s) may be related to control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement, and reporting. The NES solution(s) to be applied may be adaptively selected or predefined based on current conditions (e.g., cell load level, characteristics of connected terminals, etc.).
[0192] A base station that has identified NES solution(s) performs signaling for the NES. The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information about the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of NES operation to at least one terminal. In addition, the base station may receive capability information related to the NES from at least one terminal.
[0193] Based on the signaled NES-related information, the base station can perform operations for the NES. For example, based on system information, configuration information, and control information conveyed via signaling, the base station can turn on / off transmission and reception of specific signals, turn on / off elements in the spatial domain, or adjust resources for transmission and reception of measurement signals.
[0194] Examples of NES solutions that can be implemented using these procedures include:
[0195] Intra-system energy saving: A RAN node may request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or may perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).
[0196] Inter-system energy savings: NG-RAN nodes that own capacity booster cells can autonomously transition those cells to an inactive state.
[0197] SSB-less cells: If SSB or SSB-based RRM (radio resource management) measurement timing configuration (SMTC) configuration is not provided for a specific cell (e.g., secondary cell (SCell) or primary cell (PCell)), the UE may obtain timing reference and automatic gain control (AGC) source from another serving cell. In frequency range 1 (FR1) or FR2, the base station may configure intra-band carrier aggregation (CA) or inter-band CA including cells without SSB transmission, in which case SSB / SIB transmission may be triggered by a wake up signal (WUS) of the UE. Accordingly, since the period of common channels / signals such as SSB is increased, the base station may stay in sleep state for a longer time.
[0198] Cell DTX (discontinuous transmission) / DRX (discontinuous reception): In order to reduce the downlink transmission / uplink reception activity time of the base station, a periodic cell DTX / DRX pattern (e.g., active and inactive periods) may be commonly configured for terminals within a cell having the feature. Here, the cell DTX pattern and the cell DRX pattern may be configured and activated separately, and up to two cell DTX / DRX patterns may be configured per MAC entity. When cell DTX is configured and activated, at least one of monitoring for a semi-persistent scheduling (SPS) opportunity or monitoring a PDCCH may be stopped during the cell DTX inactivity period. When cell DRX is configured and activated, at least one of transmission on a configured grant (CG) resource or transmission of a scheduling request (SR) may be stopped during the cell DRX inactivity period. Cell DTX / DRX can be activated / deactivated via RRC signaling or L1 (layer 1) group common signaling.
[0199] Parameters such as active duration and cycle may be configured for cell DTX / DRX. Active duration is the period during which the UE receives a PDCCH or SPS opportunity and waits to transmit SR or CG, and cycle may specify the periodic repetition of the active duration and inactive duration. When both cell DTX and cell DRX are configured, parameters such as active duration and cycle may be common. If the base station recognizes an emergency call or a public safety-related service (e.g., multimedia priority service (MPS) or mission critical service (MCS)), the network may release or deactivate the cell DTX / DRX configuration so as not to affect the service. In addition, at least some overlap may be required between the active period of the connected mode DRX of the UE and the active period of the cell DTX / DRX. For example, the connected mode DRX cycle of the UE may be a multiple of the cell DTX / DRX cycle, or vice versa.
[0200] Conditional handover (CHO): A CHO procedure performed in a manner in which the execution of a handover is determined by the UE may be used while NES technology is applied (e.g., when the cell activates or deactivates cell DTX / DRX). In this case, the UE may use an NES-specific CHO event to initiate CHO to a candidate cell, and reception of a DCI activating the CHO condition(s) set by the NES event indication may be applied as an additional triggering condition for this.
[0201] Spatial and Power Domain Adaptation: To support the base station for transceiver muting and / or transmit power adaptation, the UE may be configured to report multiple CSI quantities in a CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset between a data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, the CSI configuration, measurement, and / or reporting behavior may be affected.
[0202] Cell DTX / DRX
[0203] To enable base stations to operate in sleep mode for relatively long periods of time without frequent wake-ups, base station DTX / DRX has been introduced for NES purposes. The base station can reduce energy consumption by utilizing DTX transmission under low system load conditions by configuring cell DTX and setting the on-duration of terminals' C-DRX within the active period of the cell DTX.
[0204] FIG. 15 illustrates an example of cell DTX / DRX operation to which some examples of the present disclosure may be applied.
[0205] A second node (120) (e.g., a base station) can transmit system information to a first node (110) (e.g., a terminal). Accordingly, the first node (110) can check information related to the cell DTX / DRX of the second node (120).
[0206] For example, system information may include MIB, SIB1, etc. In relation to NES technology, MIB may include information related to cell barring (e.g., cellBarred), and SIB1 may include information related to cell barring state (e.g., cellBarredNES). For example, if cellBarred included in MIB is set to a value indicating that it is not barred (e.g., notBarred), a terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. For example, if cellBarred included in received MIB is set to a value indicating that the cell is barred (e.g., barred), a terminal that does not support NES cell DTX / DRX may determine that the cell is barred.
[0207] For example, if a terminal has a capability to support NES cell DTX / DRX, the terminal can check SIB1 to determine a cell barring status. For example, if cellBarred of MIB is set to barred and cellBarredNES is absent in SIB1, a terminal supporting NES cell DTX / DRX can treat the cell as barred and perform cell reselection to another cell. For example, if cellBarred of MIB is set to barred and cellBarredNES is included in SIB1, a terminal supporting NES cell DTX / DRX can determine that the cell is not barred.
[0208] In the example of FIG. 15, it is assumed that the terminal has the capability to support NES cell DTX / DRX, and cellBarred of MIB is set to notBarred, or cellBarred of MIB is set to barred and SIB1 includes cellBarredNES. Accordingly, the terminal can perform a random access procedure to connect to the base station, and then perform communication. For example, the base station can perform a cell DTX / DRX operation, and transmit configuration information related to the cell DTX / DRX operation to the terminal. The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). Additionally, the configuration information may further include information for receiving and interpreting cell DRX / DRX-related control information (e.g., cellDTRX-RNTI included in physicalCellGroupConfig, DCI-related information such as the size of DCI format 2_9, etc.).
[0209] Thereafter, the base station can transmit control information related to cell DTX / DRX to the terminal. The control information related to cell DTX / DRX can include DCI having a designated format (e.g., DCI format 2_9). If an operation for a serving cell according to at least one of a cell DTX operation and a cell DRX operation is configured by configuration information (e.g., cellDTXDRX-Config included in servingcell-config), the terminal can check a set of search spaces (e.g., a Type3-PDCCH CSS set) for monitoring a PDCCH conveying control information of a designated format during an active time through a higher layer parameter (e.g., SearchSpace included in PDCCH-Config), and can obtain a location of information about the serving cell within the control information through a higher layer parameter (e.g., positionInDCI-cellDTRX included in ServingCell-config). Then, the terminal can obtain control information based on the identified set of search spaces and the location.
[0210] Control information related to cell DTX / DRX may be used to indicate activation or deactivation of cell DTX and / or cell DRX, and / or to provide NES-mode indicators (e.g., NES-specific CHO execution conditions, etc.), and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, when the serving cell is configured as a supplementary uplink (SUL) carrier, the indication of activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the uplink (UL) carrier and the SUL carrier.
[0211] After that, the terminal and the base station can perform communication based on the cell DTX / DRX. Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, so that the terminal can selectively monitor the signal from the base station. During the DTX-OFF duration, the base station can enter a sleep mode to reduce energy consumption. For example, the base station DTX cycle can be aligned with the cycle of the terminal DRX. The base station DTX-ON duration can completely cover the DRX-ON duration of the terminal. Furthermore, the base station can align the transmission on Xn (base station-to-base station interface) / NG (interface between 5G RAN and 5G core network) and the transmission on Uu (interface between terminal and network) for NES purposes. The DTX / DRX mechanism triggers switching of reference signal resource sets, and the base station can perform a dormancy-like behavior of rarely or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. The terminal can rarely or not receive downlink signals / channels depending on the configuration of the base station. Once the base station DTX / DRX operation is triggered, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH during the DTX / DRX OFF duration.
[0212] SSB-less cells
[0213] FIG. 16 illustrates an example of carrier aggregation (CA) operation including an SSB-less cell to which some examples of the present disclosure may be applied.
[0214] In the example of Figure 16, it is assumed that the SSB-less cell is an SCell in the CA, but the SSB-less cell may also be a PCell in the CA.
[0215] A second node (120) (e.g., a base station) can transmit configuration information for an SCell to a first node (110) (e.g., a terminal). For example, the base station can transmit configuration information for CA to provide a service to the terminal through a CA operation. Here, the CA operation may be an intra-band CA or an inter-band CA. For example, the configuration information for an SCell may include information (e.g., sCellToAddModList) including information for adding an SCell, and specifically, may include a cell index, a physical cell identifier, information related to DL-UL configuration, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Accordingly, the terminal can determine the configuration for the CA operation and perform communication using the PCell and SCell of the base station.
[0216] For example, the terminal can determine that the SCell is an SSB-less SCell based on information related to the downlink frequency included in the configuration information, and can check related parameters. For example, the terminal can determine that the SCell is an SSB-less SCell by checking the presence of a parameter indicating that the SCell is an SSB-less SCell (e.g., SSBlessSCell), and can check the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the example of Fig. 16, the reference cell can be the PCell. Therefore, the terminal can use the PCell as a timing reference and AGC source for communication in the SCell. For example, the reference of the SSB-less cell can be (another) cell, TRP, CORESET pool (control resource set pool), (additional) PCI (physical cell ID), etc.
[0217] Conditional Handover (CHO)
[0218] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.
[0219] The order of the operations illustrated in Fig. 17 may vary depending on the case.
[0220] A second node (120) (e.g., a base station) can transmit configuration information for CHO to a first node (110) (e.g., a terminal). The configuration information for CHO can include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList), information related to configuration for reporting (e.g., ReportConfigNR). For example, the information related to configuration for reporting can include information related to events related to reporting, identifiers of the events (e.g., condEventId), information indicating whether it is a NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 17, it is assumed that event information indicating that it is a NES-specific CHO event is received.
[0221] A base station may transmit information for enabling an NES-specific CHO execution condition to a terminal. The information for enabling the NES-specific CHO execution condition may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information for enabling the NES-specific CHO execution condition may be referred to as an NES-mode indicator, and may be, for example, 1-bit information that indicates enabling the NES-specific CHO execution condition when a related upper layer parameter (e.g., nesEvent) is set and a serving cell of a related block in the DCI is a primary cell.
[0222] Afterwards, the terminal can perform measurements and transmit a measurement report to the base station. The base station can determine a CHO based on the measurement report and perform signaling for a handover request with the adjacent / neighboring base station(s) indicated by the measurement report. The base station can determine the adjacent base station(s) that have confirmed admission through signaling as candidate base station(s) and transmit information about the candidate base station(s) to the terminal. Accordingly, the terminal can evaluate the CHO execution conditions for the candidate base station(s). Based on the evaluation result, if a candidate cell satisfying the conditions is determined, the terminal can perform detachment for the old cell and synchronization for the new cell.
[0223] For example, based on event information indicating that the event is an NES-specific CHO event received by the terminal in the previous procedure and information enabling an NES-specific CHO execution condition, the terminal can determine whether the event is satisfied. For example, if an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that the event is an NES-specific CHO event (e.g., nesEvent), the terminal can determine that the event associated with the corresponding measurement identifier (e.g., measId) is satisfied, and thus, determine that the CHO execution condition is satisfied.
[0224] Channel State Information (CSI) Measurement and Reporting
[0225] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.
[0226] A second node (120) (e.g., a base station) can transmit configuration information for CSI to a first node (110) (e.g., a terminal). The configuration information for CSI can include information related to a reference signal (e.g., a CSI-RS) resource or a resource set for CSI (e.g., time-frequency resource information, sequence information, power information, etc.), information related to CSI reporting (e.g., report item (quantity) information, report type information, report resource information, codebook information, etc.), information related to CSI measurement, etc.
[0227] For example, to assist the base station with transceiver muting and / or transmit power adaptation of the base station, the terminal may be configured to report multiple CSI entries in a CSI report based on multiple sub-configurations. For example, each sub-configuration may correspond to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset. With respect to CSI reporting, a higher layer parameter included in the configuration information (e.g., CSI-ReportConfig) may include a list of sub-configurations, and each sub-configuration may be identified by an identifier (e.g., csi-ReportSubConfigID). For example, each sub-configuration may correspond to a list of at least one CSI-RS resource, or may correspond to a subset of CSI-RS antenna ports, and / or may correspond to power-related parameters of the CSI-RS resource(s) (e.g., power control offset-related parameters (e.g., powerControlOffset) and / or power offset for a PDSCH associated with the CSI-RS).
[0228] For example, an information element (IE) for an aperiodic trigger state list for CSI may include a trigger list parameter for a CSI reporting sub-configuration. This parameter may include a list of sub-configuration ID(s) of N sub-configuration(s) among L configured sub-configurations within a CSI reporting configuration that are associated with triggering states for aperiodic CSI reporting on an uplink data channel (e.g., a physical uplink shared channel (PUSCH)).
[0229] For example, an IE for a CSI reporting configuration may include parameters for a list of CSI reporting sub-configuration ID(s) to be added / modified or released. Port subset indicators and a list of non-zero power (NZP) CSI-RS resources may not be configured simultaneously in the same CSI reporting configuration.
[0230] For example, an IE for a CSI reporting sub-configuration may include a port-subset indicator parameter, an NZP CSI-RS resource list parameter, and a power offset parameter.
[0231] The port-subset indicator parameter may indicate the number of ports of the NZP CSI-RS resources indicated in the NZP CSI-RS resource list (the value of which is equal to the number of ports of the corresponding NZP CSI-RS resources) and the (sub)set of CSI-RS antenna ports used for CSI calculation of the sub-configuration. Each bit in the bit string of the port-subset indicator corresponds to an antenna port, and if any bit is set to 1, the corresponding port may be enabled for CSI calculation corresponding to the sub-configuration, and if any bit is set to 0, the corresponding port may not be enabled for CSI calculation corresponding to the sub-configuration.
[0232] The NZP CSI-RS resource list parameter may indicate a list of NZP CSI-RS resources for a sub-configuration, which is a (sub)set of NZP CSI-RS resource(s) of a CSI-RS resource set for channel measurements associated with the sub-configuration of the CSI reporting configuration. The values 0, 1, 2, ... may mean the first, second, third, ... NZP CSI-RS resources of the CSI-RS resource set.
[0233] When the power offset parameter is set for an NZP CSI-RS resource, it may indicate that a power offset is applied between the PDSCH RE (resource element) and the NZP CSI-RS RE by the difference in the value of the power offset parameter from the value of the power control offset parameter.
[0234] When a configuration for CSI includes multiple sub-configurations, when interpreting the configuration information for CSI, the terminal may determine CSI-RS resources, CSI-RS port mapping, power offset, codebook type, report items, etc. by considering the sub-configurations. When configuration information related to CSI reporting including sub-configurations (e.g., CSI-ReportConfig) is provided to the terminal, the terminal may not expect that a higher layer parameter related to a report item (e.g., reportQuantity) is set to 'cri-RSRP', 'cri-SINR', 'cri-SINR-Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', 'ssb-Index-SINR-Index' or 'tdcp' (wherein CRI corresponds to a CSI-RS resource index, and tdcp corresponds to time domain channel properties). Additionally, when the type of CSI reporting is set to semi-persistent CSI reporting or aperiodic CSI reporting, the base station can activate / trigger only some of the sub-configurations configured for the UE through MAC-CE (control element) or DCI (downlink control information). For example, the trigger state of aperiodic CSI reporting can be configured as needed, and whether semi-static CSI reporting is activated can be controlled by an activation command.
[0235] For example, with respect to the configuration of a report quantity, the terminal may determine the CSI-RS port index(es) for each CSI-RS resource based on information related to a port subset per sub-configuration (hereinafter referred to as a "port subset indicator"). The port subset indicator may include a bitmap for specifying some of the antenna ports for the corresponding CSI-RS resource. Accordingly, the terminal may identify at least one antenna port for the corresponding sub-configuration based on the positions of bits set to positive values (e.g., 1) in the port subset indicator.
[0236] For example, with respect to the configuration of report items (report quantity), the terminal may determine the codebook type based on the presence or absence of sub-configurations. Specifically, if sub-configurations are configured for CSI reporting, the terminal may exclude the configuration of at least one codebook type. For example, if the terminal's capabilities support it, at least one codebook type may be configured.
[0237] For example, in relation to the configuration of the report quantity, a power offset value and an NZP CSI-RS resource set may be configured for each sub-configuration. For example, depending on whether a power offset value is configured for each sub-configuration and whether an NZP CSI-RS resource set is configured, the interpretation of the NZP CSI-RS resource set for each sub-configuration may vary.
[0238] When determining the channel quality indicator (CQI), a higher-layer parameter related to time restrictions for channel measurements (e.g., timeRestrictionForChannelMeasurements) may be configured. In this case, the terminal can derive a channel estimate for determining CSI based on the most recent CSI reference resource. For example, if cell DTX is activated for the base station, the cell DTX activation time, etc., may be considered to determine the CSI reference resource, etc.
[0239] CSI is derived based on CSI reference resources. A CSI reference resource is defined as a group of downlink physical resource blocks corresponding to a band related to the CSI derived in the frequency domain, and is defined as a single downlink slot determined based on higher-layer parameters and subcarrier spacing in the time domain. After receiving a CSI-RS, a UE can transmit a CSI report no later than the CSI reference resource. For example, if sub-configurations are configured for a CSI report, a CSI reference resource may be considered for each sub-configuration.
[0240] When at least one of a CQI index, a precoding matrix index (PMI), and a rank indicator (RI) is set to be reported, in the CSI reference resource, the terminal may assume specific values for the symbol positions and number occupied by control signaling, the number of PDSCH and demodulation reference signal (DMRS) symbols, the subcarrier spacing of the bandwidth part (BWP), the bandwidth for CQI reporting, the length and subcarrier spacing of the cyclic prefix (CP) of the reference resource, and the redundancy version (RV), for the purpose of deriving at least one of the CQI index, PMI, and RI. At this time, when sub-configurations are set for the CSI reporting, assumptions about the antenna port, EPRE (energy per resource element), etc. may be determined based on the sub-configurations.
[0241] Based on the aforementioned configuration, the base station can transmit at least one CSI-RS to the terminal. Based on the aforementioned configuration, the terminal can receive at least one CSI-RS and perform measurement on it. For example, the at least one CSI-RS can be transmitted via a CSI-RS resource or resource set configured by the configuration information.
[0242] When the terminal is set to DRX (discontinuous reception), the terminal can perform measurements as follows. For example, when the terminal is set to monitor power saving related control information (e.g., DCI format 2_6) and the DRX related timer (e.g., drx-onDurationTimer) has not been started by a higher layer parameter (e.g., ps-TransmitOtherPeriodicCSI), and is set to report CSI using a reporting configuration type set to periodic reporting and a reporting item set to an item other than cri-RSRP and ssb-index-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer in the DRX related configuration information (e.g., DRX-Config) other than the DRX active time or the DRX active time for the CSI to be reported. As another example, if the terminal is configured to monitor power saving related control information (e.g., DCI format 2_6) and is configured to report L1-RSRP using a report configuration type set to periodic reporting and a report item set to cri-RSRP in a situation where drx-onDurationTimer has not started by a higher layer parameter (e.g., ps-TransmitPeriodicL1-RSRP), the most recent CSI measurement opportunity occurs during a time indicated by drx-onDurationTimer in DRX-related configuration information (e.g., DRX-Config) other than the DRX active time or the DRX active time for the CSI to be reported. In addition, the most recent CSI measurement opportunity occurs within the DRX active time for the CSI to be reported.
[0243] A base station may perform cell DTX and / or cell DRX operations. In this case, during the inactive period of cell DTX, a terminal configured as cell DTX may not expect to receive periodic CSI-RS and semi-static CSI-RS, at least as configured in a CSI reporting configuration associated with a report item including RI. When cell DTX is activated for a serving cell, the most recent CSI measurement opportunity of a semi-static CSI-RS resource or a periodic CSI-RS resource may occur within the active periods of cell DTX for CSI reporting, at least as configured by configuration information (e.g., CSI-ReportConfig) related to CSI reporting associated with a report item including RI.
[0244] A terminal that receives at least one CSI-RS can determine CSI. For example, the terminal can perform CSI calculations. The terminal can perform CSI calculations based on CSI processing criteria. The terminal can indicate the number of supported concurrent CSI calculations, for example, the number of CSI processing units (CPUs) that can be performed simultaneously, called NCPUs. The terminal can determine the number of CPUs for a given CSI report based on at least one of the NCPUs, the number of CPUs for each CSI report, the number of CPUs currently occupied, and the settings of the report items. For example, for configuration information (e.g., CSI-ReportConfig) related to CSI reporting that includes a report item parameter (e.g., reportQuantity) that is not set to 'none', the CPU(s) may be occupied for at least one orthogonal frequency division multiplexing (OFDM) symbol, wherein the number of at least one symbol may be determined based on CSI-RS resources or CSI-IM (interference measurement) resources associated with the sub-configurations.
[0245] When configuration information related to CSI reporting (e.g., CSI-ReportConfig) includes multiple sub-configurations, the number of CPUs occupied by the CSI report may be determined based on the number of CSI-RS resources corresponding to the sub-configurations. For example, the number of CSI-RS resources may be determined based on the number of times they are referred in the configuration information related to CSI reporting (e.g., CSI-ReportConfig) or the number of sub-configurations referencing the corresponding CSI-RS resources.
[0246] A terminal that has determined CSI can transmit a CSI report to a base station. The terminal can transmit CSI(s) for at least one sub-configuration according to a report item parameter (e.g., reportQuantity) configured for configuration information related to the CSI report (e.g., CSI-ReportConfig). For example, the CSI report can include at least one of PMI, CQI, RI, CRI, SSBRI (SSB resource index), LI (layer indicator), and RSRP. In this case, the CSI report can include a Part 1 CSI report and a Part 2 CSI report. In addition, the CSI report can be transmitted via at least one of a physical uplink control channel (PUCCH) or a PUSCH.
[0247] When a terminal multiplexes a CSI report including a Part 2 CSI report on a PUCCH resource, the terminal determines the number of PUCCH resources and physical resource blocks (PRBs) for the PUCCH resource or the number of Part 2 CSI reports, assuming that each CSI report or each CSI sub-report included in the CSI report indicates rank 1 or the rank combination {1, 1}. When a higher layer parameter related to the CSI reporting mode (e.g., csi-ReportMode) is set to 'Mode2', the terminal determines the PUCCH resource and the number of PRBs for the PUCCH resource or the number of Part 2 CSI reports, assuming that each CRI of the CSI report is associated with a resource pair.
[0248] When a CSI report on PUSCH includes two parts, the UE may omit some of the Part 2 CSI. The omission of Part 2 CSI is in priority order. When omitting Part 2 CSI information for a particular priority level, the UE shall exclude all information for that priority level, except when the corresponding CSI report includes at least one CSI sub-report including Part 2, which corresponds to a sub-configuration from a list of sub-configurations provided by a higher layer parameter (e.g., csi-ReportSubConfigList) included in information related to the CSI report (e.g., CSI-ReportConfig).
[0249] For a report configuration related to information related to a CSI report (e.g., CSI-ReportConfig) that includes a list of sub-configurations, the following processing is possible: For a corresponding CSI report that includes at least one CSI sub-report, omission of Part 2 CSI is performed at the sub-configuration level within the same priority level, where a sub-configuration with a lower index value has a higher priority.
[0250] If a CSI report consists of two parts, a UE may omit some of the Part 2 CSI. The omission of Part 2 CSI is based on a priority order. For a report configuration related to information related to a CSI report (e.g., CSI-ReportConfig) that includes a list of sub-configurations, for a given CSI report that includes at least one CSI sub-report, the omission of Part 2 CSI may be applied according to the CSI reporting procedure using PUSCH. Part 2 CSI may be omitted starting from the lowest priority level up to the Part 2 CSI coding rate that is less than or equal to the coding rate set by the higher layer parameter (e.g., maxCodeRate).
[0251] Additionally, if the CQI request (or CSI request) field in the DCI triggers CSI report(s) on the PUSCH, the first uplink symbol carrying the CSI report(s) may not precede a symbol specified after a certain interval from the last symbol of the PDCCH carrying the corresponding DCI. Accordingly, the CSI calculation time may be guaranteed. For example, if multiple sub-configurations are configured for the CSI report, the starting position of the aforementioned certain interval may be determined based on all triggered sub-configurations.
[0252] CSI is transmitted via PUCCH or PUSCH and can be expressed as a bit string of a fixed size. When CSI is transmitted via PUCCH, if a parameter (e.g., csi-ReportSubConfig) indicating sub-configuration-specific settings for CSI reports is configured, the mapping order of CSI fields for each CSI sub-report can be applied according to predefined rules.
[0253] When CSI is transmitted via PUSCH, if a parameter indicating sub-configuration-specific configuration for CSI reporting (e.g., csi-ReportSubConfig) is set, for each CSI sub-report, the mapping order of CSI fields can be applied according to a predefined rule.
[0254] Some or all of the examples of FIGS. 1 to 18 described above may be combined with some or all of the examples of the present disclosure described below, and such combined examples are included within the scope of the present disclosure.
[0255] Improved NES
[0256] For enhancement of NES technology, on-demand SSB, on-demand SIB1, and adaptation of common signal / channel transmissions are being discussed.
[0257] Below we describe on-demand SSB.
[0258] On-demand SSB is a NES scheme that transmits SSB when triggered in a specific cell and does not transmit SSB when not triggered. Existing NR systems require periodic, constant transmission of SSB for purposes such as time / frequency synchronization and RRM measurement, making it difficult to reduce energy consumption even when the base station has no data to receive or send. Considering this, energy consumption at the base station can be reduced by not performing SSB transmission at all and only performing SSB transmission when the on-demand SSB process is performed.
[0259] These on-demand SSB processes can be triggered by one or more of the following examples:
[0260] - The terminal requests SSB transmission from the base station by transmitting an uplink signal / channel (e.g., PRACH (physical random access channel), PUCCH, PUSCH, SRS (sounding reference signal) in the 5G NR system, and may be a signal / channel with a different name in the 6G system).
[0261] - The first base station (or TRP) requests SSB transmission from the second base station (or TRP) through an interface between base stations (e.g., Xn interface in 5G NR system, interface with different name in 6G system) or backhaul signaling, etc.
[0262] - Signaling whether SSB transmission of the corresponding SCell is possible through SCell activation / deactivation signaling.
[0263] Considering coexistence with existing NR terminals, on-demand SSB operation may be limited to connected mode terminals and SCells. In subsequent releases or next-generation communication systems, on-demand SSB operation considering inactive or idle mode terminals or initially connected terminals (e.g., on-demand SSB support on PCell) may be defined. In addition, carrier aggregation (CA) including SCells applicable to on-demand SSB may be applied to both intra-band CA and inter-band CA. SSB on SCells transmitted through on-demand SSB may be utilized at least for time / frequency synchronization, L1 / L3 measurements, SCell activation, etc.
[0264] Below, we describe On-Demand SIB1.
[0265] On-demand SIB1 corresponds to a NES scheme that transmits SIB1 when triggered on a specific cell and does not transmit SIB1 when not triggered. In the existing NR system, in order to support access to a cell by an initial access terminal or an idle mode terminal, it is required to periodically and always transmit SIB1 containing system information, random access information, etc., so it was difficult to reduce energy consumption even when the base station had no data to receive or send. By having the base station not perform SIB1 transmission and perform SIB1 transmission only when the on-demand SIB1 process is performed, the energy consumption of the base station can be reduced.
[0266] This on-demand SIB1 process may include the terminal transmitting an uplink signal / channel (e.g., PRACH in a 5G NR system, or a signal / channel with a different name in a 6G system) that triggers the base station's SIB1 transmission.
[0267] FIG. 19 illustrates examples of on-demand SIB1 operations to which some examples of the present disclosure may be applied. FIG. 19 merely illustrates examples, and on-demand SIB1 operations are not limited to the examples of FIG. 19.
[0268] In (a) of FIG. 19, the terminal may receive an SSB (and / or other downlink signal / channel) from the first cell (cell#1) and recognize that SIB1 is not transmitted on the corresponding cell#1. The terminal may trigger SIB1 transmission on cell#1 by transmitting a signal requesting SIB1 (e.g., a wake-up signal (WUS)) based on information provided in the SSB (and / or other downlink signal / channel) and / or predetermined information. For example, the base station that received the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#1 in response thereto and transmit SIB1 on cell#1. Alternatively, the base station may transmit SIB1 on cell#1 without transmitting a specific DL signal / channel (e.g., ACK).
[0269] In (b) of FIG. 19, the terminal may receive an SSB (and / or other downlink signal / channel such as SIB1) from the first cell (cell#1) and recognize that SIB1 is not transmitted from the second cell (cell#2). The terminal may attempt to camp on cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal (e.g., WUS) requesting SIB1 on cell#1 based on information provided in the SSB (and / or other downlink signal / channel such as SIB1) received from cell#1 and / or predetermined information. For example, the base station receiving the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#1 (or on cell#2) in response thereto, and transmit SIB1 for cell#2 on cell#1 (or on cell#2). Alternatively, the base station may transmit SIB1 for cell#2 on cell#1 (or on cell#2) without transmitting a specific DL signal / channel (e.g., ACK).
[0270] In (c) of FIG. 19, the terminal may receive an SSB (and / or other downlink signal / channel such as SIB1) from the first cell (cell#1) and recognize that SIB1 is not transmitted from the second cell (cell#2). The terminal may attempt to camp on cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal (e.g., WUS) requesting SIB1 on cell#2 based on information provided in the SSB (and / or other downlink signal / channel such as SIB1) received from cell#1 and / or predetermined information. For example, the base station receiving the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#2 (or on cell#1) in response thereto, and transmit SIB1 for cell#2 on cell#2 (or on cell#1). Alternatively, the base station may transmit SIB1 for cell#2 on cell#2 (or on cell#1) without transmitting a specific DL signal / channel (e.g., ACK).
[0271] Below we describe the adaptation of common signal / channel transmission.
[0272] Base stations can apply NES schemes that control the transmission of common signals / channels such as SSB, PRACH, and paging. Energy consumption can be reduced more significantly when SSB is not transmitted completely but is transmitted as needed. However, if SSB that supports time / frequency synchronization or RRM measurement is not transmitted completely, stable operation of terminals for the corresponding cell may not be guaranteed. Considering this, energy saving effects of the base station can be achieved by controlling / changing the SSB transmission pattern (e.g., transmission period, period by SSB candidate index(es), SSB candidate index(es) transmitted within one transmission period, transmission power, etc.) according to the situation.
[0273] In the case of PRACH resources, in the case of contention-based random access, since the base station does not know when the terminal will transmit the PRACH, it is required to always attempt reception within the PRACH resources set for the terminal, which may increase network energy consumption. Considering this, a method for controlling the amount of PRACH resources can be applied. For example, the period of the PRACH resources can be adjusted to be longer so that the base station attempts PRACH reception less frequently. For example, the number of PRACH resources can be adjusted to be smaller, such as a method of pre-configuring PRACH resource sets #1 and #2 and activating only one of the two sets or activating both sets. For example, the amount of RACH resources corresponding to each SSB index can be provided uniformly or non-uniformly.
[0274] In the case of paging, it is defined that paging frames (PF) and / or paging occasions (PO) are distributed on the time axis within a DRX cycle (or paging cycle), and the terminal attempts to receive paging at a specific PF / PO derived from a formula based on its own identification information. If the base station wants to transmit paging to multiple terminals simultaneously, it may need to frequently transmit paging messages according to various terminal identification information values. As a method for reducing the base station energy consumption due to this, a method such as arranging the PF and / or PO as close as possible on the time axis or arranging them on distinct frequency resources within the same time resource can be applied.
[0275] Types of synchronization signals
[0276] The examples of the present disclosure assume two types of synchronization signals and explain them. While the term "SSB" is used as an example of a synchronization signal in the following description, the scope of the present disclosure is not limited by that term, and other units with different names that include synchronization signals may replace "SSB."
[0277] For example, assuming on-demand SSB on a specific cell where transmission is initiated by a base station instruction or a terminal request, Type-1 SSB and Type-2 SSB can be distinguished as follows.
[0278] Type-1 SSB may refer to an SSB transmitted periodically on a first cell or on a second cell. If a period, etc. for the SSB is determined / defined / set, the SSB may be continuously transmitted according to the period. Continuous transmission may include transmission without distinction between on and off periods for SSB transmission, or without activation or deactivation. If Type-1 SSB refers to an SSB transmitted on a first cell, the first cell may correspond to a timing reference cell. If Type-1 SSB refers to an SSB transmitted on a second cell, the second cell may be in an intra-band CA or inter-band CA relationship with the first cell. For example, (especially in an inter-band CA environment) the second cell may be set as a timing reference cell for the first cell, or (in an intra-band CA environment) the second cell may be determined / defined as a timing reference cell for the first cell (e.g., a specific cell within the same timing advance group or a PCell or PSCell (primary secondary cell, i.e., a primary cell within a secondary cell group (SCG)). Also, only Type-2 SSBs may be transmitted on a specific cell without Type-1 SSBs.
[0279] Type-2 SSB may refer to an SSB in which transmission on a specific cell is activated through a configuration / instruction of the base station (via RRC / MAC-CE / DCI, etc.) or upon a request of the terminal. For an activated SSB, SSB deactivation may be explicitly configured / instructed via RRC / MAC-CE / DCI, etc. Alternatively, for an SSB in which the number of transmissions or transmission intervals are configured / instructed in the RRC / MAC-CE / DCI instructing SSB activation, the SSB may be deactivated when the corresponding number of transmissions or transmission intervals have expired. Alternatively, if there is a pre-configured / defined number of transmissions or transmission intervals, the SSB may be deactivated when the corresponding number of transmissions or transmission intervals have expired after SSB activation. Alternatively, (if a specific cell is an SCell) the SSB may be deactivated when activation for the specific cell is completed (or when CSI reporting for the specific cell is successfully completed). Alternatively, SSB may be deactivated when the specific cell is deactivated (if the specific cell is an SCell). Alternatively, SSB may be deactivated after a handover from the specific cell to another cell (if the specific cell is a PCell). Alternatively, SSB may be deactivated at the request of the UE.
[0280] As another example, it can be assumed that one or more SSB configurations are configured among different SSB configurations with at least different SSB cycle values, and an SSB corresponding to one of the SSB configurations is transmitted at the base station's instruction or the terminal's request. In this case, adaptation to the SSB cycle can be performed by varying the activated SSB configuration. In this case, Type-1 SSB and Type-2 SSB can be distinguished as follows.
[0281] Type-1 SSB may refer to a reference SSB setting among the configured SSB setting(s). For example, the reference SSB setting may correspond to the SSB setting having the largest SSB period value. For example, if an SSB setting corresponding to a Type-2 SSB is not activated, an SSB setting corresponding to a Type-1 SSB may be activated. Alternatively, if an SSB setting corresponding to a Type-2 SSB is activated, an SSB setting corresponding to a Type-1 SSB may be deactivated. Alternatively, if SSB opportunities specified based on a particular SSB setting (e.g., the reference SSB setting) among the configured SSB settings are a subset of SSB opportunities specified based on other SSB settings (e.g., "extended SSB opportunities"), the reference SSB opportunities may be defined as a Type-1 SSB (regardless of the actual activated SSB setting). In this case, Type-2 SSB can be defined as the remaining SSB opportunities among the extended SSB opportunities (included in the actual activated SSB configuration) excluding the reference SSB opportunities.
[0282] For Type-2 SSB, in addition to the SSB configuration corresponding to Type-1 SSB, one or more SSB configurations for Type-2 SSB can be configured. When an SSB configuration corresponding to Type-2 SSB is activated, all SSBs belonging to the activated SSB configuration can be defined as Type-2 SSBs. Alternatively, if SSB opportunities configured based on a specific SSB configuration (e.g., a reference SSB configuration) among the configured SSB configurations (hereinafter, referred to as "reference SSB opportunities" for convenience) are a subset of SSB opportunities configured based on other configurations (hereinafter, referred to as "extended SSB opportunities" for convenience), the reference SSB opportunities can be defined as Type-1 SSBs (regardless of the actual activated SSB configuration), in which case Type-2 SSBs can be defined as the remaining SSB opportunities among the extended SSB opportunities (in the actual activated configuration) excluding the reference SSB opportunities. One or more SSB configurations may be activated by a configuration / instruction (via RRC / MAC-CE / DCI) of the base station or by a request of the terminal. For an activated SSB configuration, SSB deactivation may be explicitly configured / instructed via RRC / MAC-CE / DCI, etc. Alternatively, for an SSB activated by configuring / instructing the number of transmissions or transmission intervals in the RRC / MAC-CE / DCI instructing the activation of the SSB configuration, when the corresponding number of transmissions or transmission intervals expire, the SSB may be deactivated. Alternatively, if there is a pre-configured / defined number of transmissions or transmission intervals, the SSB may be deactivated when the corresponding number of transmissions or transmission intervals expire after the SSB is activated. Alternatively, (if a specific cell is an SCell) the SSB may be deactivated when activation for the specific cell is completed (or CSI reporting for the specific cell is successfully completed). Alternatively, (if a specific cell is an SCell) the SSB may be deactivated when the specific cell is deactivated.Alternatively, SSB may be deactivated after a handover from a specific cell to another cell (if the specific cell is a PCell). Alternatively, SSB may be deactivated at the request of the terminal.
[0283] As another example, it can be assumed that one or more SSB configurations are configured and an SSB corresponding to one of the SSB configuration(s) is transmitted at the instruction of the base station or upon the request of the terminal. In this case, there is an SSB (e.g., Type-1 SSB) that continues to be transmitted periodically regardless of the activation / deactivation of the corresponding SSB configuration(s), and an SSB configuration to be transmitted in addition to this SSB can be activated / deactivated. At least the SSB period value or SSB time pattern can be different between different SSB configurations. In this case, adaptation to the SSB period can be performed by varying the activated SSB configuration. In this case, Type-1 SSB and Type-2 SSB can be distinguished as follows.
[0284] Type-1 SSB may mean an SSB corresponding to the default SSB setting, and continuous periodic transmission may be guaranteed for Type-1 SSB regardless of the activation / deactivation of the SSB setting(s) corresponding to Type-2 SSB.
[0285] One or more SSB configurations for Type-2 SSB can be configured. One of the one or more SSB configurations can be activated by a configuration / instruction from a base station (via RRC / MAC-CE / DCI) or a request from a terminal. For an activated SSB configuration, SSB deactivation can be explicitly configured / instructed via RRC / MAC-CE / DCI, etc. Alternatively, for an SSB activated by configuring / instructing the number of transmissions or transmission intervals in the RRC / MAC-CE / DCI indicating the activation of the SSB configuration, when the number of transmissions or transmission intervals has expired, the SSB can be deactivated. Alternatively, if there is a pre-configured / defined number of transmissions or transmission intervals, the SSB can be deactivated when the number of transmissions or transmission intervals has expired after the SSB is activated. Alternatively, the SSB can be deactivated when activation for the specific cell is completed (or when CSI reporting for the specific cell is successfully completed) (if the specific cell is an SCell). Alternatively, SSB may be deactivated when the specific cell is deactivated (if the specific cell is an SCell). Alternatively, SSB may be deactivated after a handover from the specific cell to another cell (if the specific cell is a PCell). Alternatively, SSB may be deactivated at the request of the UE.
[0286] In the various examples described above, Type-1 SSB may correspond to an SSB that can assume continuous periodic transmission, and Type-2 SSB may correspond to an SSB that cannot assume continuous periodic transmission. In some of the examples described below, the always-on SSB may correspond to or be replaced by the Type-1 SSB described above, and the on-demand SSB may correspond to or be replaced by the Type-2 SSB described above.
[0287] Multiple synchronization signal blocks in the secondary cell
[0288] This disclosure describes a method for providing OD SSB-related settings to a terminal. For example, the minimum parameters required for OD SSB transmission / reception, limitations or special features regarding the setting of the parameter(s), and the information included in the OD SSB-related settings can be configured. Furthermore, a method for reducing signaling overhead and increasing efficiency is also described. Accordingly, the terminal can clearly interpret the meaning of the corresponding parameter(s), understand how the OD SSB will be transmitted from the base station, and perform appropriate actions accordingly.
[0289] For example, various examples are described in which parameter(s) of OD SSB related configurations may be included and signaled differently depending on whether SSB (e.g., conventional SSB or legacy SSB) is transmitted from a base station. Accordingly, various examples of OD SSB related configurations are described in the configuration / reconfiguration process in which a secondary cell (SCell) is added / activated.
[0290] In the following description, activation / triggering for transmission of OD SSB corresponds to the operation of the base station, and activation / triggering for reception of OD SSB can be interpreted as the operation of the terminal.
[0291] In the following description, the omission of a specific parameter from the OD SSB related settings may mean that the parameter is not included in the parameter set or information element corresponding to the OD SSB related settings.
[0292] FIG. 20 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.
[0293] In step S2010, the terminal can receive information related to the first synchronization signal block on the cell.
[0294] In some examples, the cell may be a secondary cell (SCell).
[0295] In some examples, the terminal may receive the first synchronization signal block on the cell based on information related to the first synchronization signal block.
[0296] In step S2020, the terminal can receive the second synchronization signal block on the corresponding cell based on information related to the second synchronization signal block.
[0297] In some examples, when half-frame index information related to a second synchronization signal block is provided, the index of a half-frame including the second synchronization signal block can be determined by the provided half-frame index information. For example, the index of a half-frame including the second synchronization signal block can be indicated by the provided half-frame index information.
[0298] Alternatively, if half-frame index information is not provided, the index of the half-frame containing the second synchronization signal block may be a predefined index. For example, the predefined index may be 0. For example, the predefined index 0 may correspond to the first half-frame among two half-frames within the frame.
[0299] In some examples, when system frame number (SFN) offset information related to a second synchronization signal block is provided, a frame including the second synchronization signal block may be determined by an SFN index based on the SFN offset information. For example, a frame including the second synchronization signal block may be indicated by an SFN index based on the provided SFN offset information.
[0300] For example, a frame including a second synchronization signal block can be generated based on the values of the SFN index and SFN offset information related to the period (P) of transmission of the second synchronization signal block.
[0301] For example, the value of the SFN offset information may correspond to an offset value from an SFN index that satisfies the value 0 obtained by applying a modulo P operation to the value obtained by multiplying the SFN index by 10.
[0302] For example, the SFN index associated with a frame including a second synchronization signal block can be calculated based on the result of applying a modulo P operation to the sum of the values of the SFN index and the SFN offset information multiplied by 10, which is 0.
[0303] Alternatively, if no SFN offset information related to the second synchronization signal block is provided, the value of the SFN offset information may be 0.
[0304] In some examples, the half-frame index may be associated with one of two half-frames in a frame containing a second synchronization signal block (e.g., a frame corresponding to an SFN based on the SFN offset described above).
[0305] In some examples, when position in burst information related to a second synchronization signal block is provided, the index of the second synchronization signal block may be determined by the position in burst information. For example, the index of the second synchronization signal block may be indicated by the value of the position in burst information.
[0306] Alternatively, if position information within the second burst associated with the second synchronization signal block is not provided, the index of the second synchronization signal block may be determined by the value of the position information within the first burst associated with the first synchronization signal block. For example, the index of the second synchronization signal block may be indicated by the value of the position information within the first burst associated with the first synchronization signal block.
[0307] In some examples, when second frequency position information related to a second synchronization signal block is provided, the frequency position of the second synchronization signal block can be determined by the value of the second frequency position information. For example, the frequency position of the second synchronization signal block can be indicated by the value of the second frequency position information.
[0308] Alternatively, if the second frequency position information related to the second synchronization signal block is not provided, the frequency position of the second synchronization signal block may be determined by the value of the first frequency position information related to the first synchronization signal block. For example, the frequency position of the second synchronization signal block may be indicated by the value of the first frequency position information related to the first synchronization signal block.
[0309] In some examples, when second subcarrier spacing (SCS) information related to a second synchronization signal block is provided, the SCS setting of the second synchronization signal block may be determined by the value of the second SCS information. For example, the SCS setting of the second synchronization signal block may be indicated by the value of the second SCS information.
[0310] Alternatively, if the second SCS setting information related to the second synchronization signal block is not provided, the SCS setting of the second synchronization signal block may be determined by the value of the first SCS information related to the first synchronization signal block. For example, the SCS setting of the second synchronization signal block may be indicated by the value of the first SCS information related to the first synchronization signal block.
[0311] In some examples, when second power information related to a second synchronization signal block is provided, the power of the second synchronization signal block may be determined by the value of the second power information. For example, the power of the second synchronization signal block may be indicated by the value of the second power information.
[0312] Alternatively, if the second power information related to the second synchronization signal block is not provided, the power of the second synchronization signal block may be determined by the value of the first power information related to the first synchronization signal block. For example, the power of the second synchronization signal block may be indicated by the value of the first power information related to the first synchronization signal block.
[0313] In some examples, when burst count information related to the second synchronization signal block is provided, the number of transmissions of the second synchronization signal block may be determined by the value of the burst count information. For example, the number of transmissions of the second synchronization signal block may be indicated by the value of the burst count information related to the second synchronization signal block.
[0314] Alternatively, if no burst count information is provided for the second synchronization signal block, transmission of the second synchronization signal block may occur (periodically) until deactivated.
[0315] In some examples, the first synchronization signal block may be an SSB or AO SSB, and the second synchronization signal block may be an on-demand (OD) SSB.
[0316] In some examples, half-frame index information, SFN offset information, position information within the second burst, and / or burst number information related to the second synchronization signal block may be provided via MAC-CE.
[0317] The method described in the example of FIG. 20 may be performed by the wireless device (200) of FIG. 3 corresponding to the first node (110) of FIG. 2 described above. For example, one or more processors (202) of the wireless device (200) of FIG. 3 may be configured to receive information related to a first synchronization signal block on a cell through one or more transceivers (206), and to receive a second synchronization signal block on the cell through one or more transceivers (206) based on information related to a second synchronization signal block. Furthermore, one or more memories (204) of the wireless device (200) may store commands for performing the method described in the example of FIG. 20 or the examples described below when executed by one or more processors (202).
[0318] FIG. 21 is a drawing illustrating an example of a method performed by a base station according to the present disclosure.
[0319] In step S2110, the base station may transmit information related to the first synchronization signal block to one or more terminals on the cell.
[0320] In step S2120, the base station may transmit the second synchronization signal block to one or more terminals on the cell based on information related to the second synchronization signal block.
[0321] The first synchronization signal block, the second synchronization signal block, information related to the first synchronization signal block, information related to the second synchronization signal block, and specific characteristics of the cell are the same as the description referring to the example of FIG. 20, so redundant descriptions are omitted.
[0322] The method described in the example of FIG. 21 may be performed by the wireless device (200) of FIG. 3 corresponding to the second node (120) of FIG. 2 described above. For example, one or more processors (202) of the wireless device (200) of FIG. 3 may be configured to transmit information related to a first synchronization signal block over a cell via one or more transceivers (206), and to transmit a second synchronization signal block over a cell via one or more transceivers (206) based on information related to a second synchronization signal block. Furthermore, one or more memories (204) of the wireless device (200) may store commands for performing the method described in the example of FIG. 21 or the examples described below when executed by one or more processors (202).
[0323] Hereinafter, various examples of the present disclosure for transmitting or receiving various types of synchronization signal blocks (or SSBs) will be described. In the examples below, the terms Always-On SSB (or AO SSB or simply SSB) and On-Demand SSB (or OD SSB) are primarily used for description, but these are representative examples of the aforementioned Type-1 SSB and Type-2 SSB, and the scope is not limited by the names of the terms.
[0324] In the present disclosure, it is generally assumed that the transmission of OD SSB and AO SSB is transmitted in the form of SSB burst. For example, one SSB burst transmission may correspond to a method of transmitting (e.g., sweeping) SSBs of one or more indices (e.g., SSB#0 to SSB#x) once within a predetermined time interval (e.g., 5 ms, which is half of a 10 ms frame). Different SSB indices may correspond to different beam directions, and the same SSB index may correspond to the same beam direction (or be quasi-co-located (QCL)). That is, an SSB burst may correspond to a set of one or more SSB beams within a predetermined time interval (e.g., 5 ms), which may be referred to as an SSB group in the examples below. For example, in the sub 6 GHz band, up to 8 beams can be included in one SSB burst, and for frequency range 2 (FR2) or millimeter wave (mmwave), up to 64 beams can be included in one SSB burst. Which beam / SSB among the beam IDs or SSB indices within one SSB burst / group is transmitted can be set / indicated in bitmap form by information about the SSB time domain position (e.g., SSB-PositionInBurst parameter) signaled via SIB or RRC (re)configuration. In addition, the 5 ms period during which all SSBs / beams within one SSB burst are transmitted once within the cell (i.e., swept) can correspond to the first 5 ms or the last 5 ms of a 10 ms period. For AO SSB, the terminal can find out whether the SSB burst is in the first 5ms or the last 5ms of a 10ms frame (i.e., the half-frame index) in a blind detection manner without instructions from the base station.
[0325] OD SSB can be applied during the addition process of SCell, the activation process, or even when the SCell is already activated (e.g., after the activation process is completed). An SCell may transmit SSB all the time (e.g., periodically) on its own. Alternatively, if an SSB is always (periodically) transmitted in a cell that is collocated with the SCell in frequency or time, such as an SpCell (e.g., a primary cell (PCell) of a master cell group or a primary cell (PSCell) of a secondary cell group) or a reference cell, SSB may not always be transmitted in that SCell. Alternatively, even in an SCell that is not completely collocated with a SpCell or a reference cell but does not always transmit SSB, OD SSB may need to be transmitted only temporarily depending on the situation. If an SSB is always transmitted, the SSB may be simply referred to as an SSB or an AO SSB. An SSB that is not always transmitting, but is transmitting temporarily (or until deactivated) under certain circumstances, can be called an OD SSB.
[0326] The present disclosure describes various examples of parameter(s) that may be included in the OD SSB related settings. For example, considering the case where an AO SSB exists in the current SCell, the case where an AO SSB does not exist, and even if there is no AO SSB, the case where a reference cell (or an SSB that is always transmitted in the reference cell) is designated (by a higher layer such as RRC) and the case where it is not designated, etc., the following describes a higher layer signaling method for the SSB index (or position within an SSB burst), frequency, SCS, half frame, power, number of transmissions (or number of bursts), period, time offset, etc. required for the setting of the OD SSB.
[0327] In the examples of the present disclosure, if the AO SSB (or the first SSB) does not exist or the parameter(s) for it are not provided to the terminal, all of the various parameters described above for the OD SSB (or the second SSB) may need to be provided to the terminal.
[0328] In the examples of the present disclosure, when an AO SSB (or a first SSB) exists or parameter(s) therefor are provided to the terminal, the terminal may reuse or use identically the values of the parameter(s) of the AO SSB (or the first SSB) for the various parameters described above for the OD SSB (or the second SSB).
[0329] In the examples of the present disclosure, when there is no AO SSB (or first SSB) and a reference cell is designated, the parameter(s) provided for the reference cell may be reused for the OD SSB (or second SSB). For the reference cell, the parameter(s) provided for the reference cell may be reused for specific parameter(s) of the OD SSB (or second SSB) depending on whether the frequency location relationship between the reference cell and a serving cell (e.g., SCell) to which the OD SSB can be transmitted is inter-band or intra-band.
[0330] In the present disclosure, a reference cell may mean, for example, a timing reference cell. In addition, in the present disclosure, the designation of a reference cell for a non-SSB SCell may correspond to: i) designating a PCell or PSCell or any serving cell within the same timing advance group (TAG) in intra-band carrier aggregation (CA), or ii) designating it through a specific parameter (e.g., referenceCell-r18) in inter-band CA. In the examples of the present disclosure, the designation of a reference cell for a non-AO SSB SCell (i.e., non-SSB) may be applied to both the aforementioned cases i) and ii).
[0331] Hereinafter, specific examples of the present disclosure for transmission or reception of a first synchronization signal block (hereinafter, referred to as AO SSB (or simply SSB if distinguished from OD SSB) for convenience of explanation) and a second synchronization signal block (hereinafter, referred to as OD SSB for convenience of explanation) on an SCell are described.
[0332] Example 1
[0333] This embodiment is about frequency setting of OD SSB.
[0334] The parameter for the frequency of the OD SSB may actually indicate the frequency location at which the OD SSB is transmitted. Even if an AO SSB is transmitted in that cell, the frequency location of the OD SSB may not necessarily be the same as the frequency location of the AO SSB.
[0335] For example, a list of candidates for frequency positions of OD SSB may be set for the terminal, and an index corresponding to one of the frequency positions may be provided to the terminal. The index may be provided to the terminal via RRC (or L3) signaling, or may be provided to the terminal via MAC CE (or L2) signaling or DCI (or L1) signaling.
[0336] Example 1-1
[0337] The same frequency setting as that of the AO SSB or the SSB of the reference cell may be used for the OD SSB. In this case, a separate parameter for the frequency position of the OD SSB may not be provided. For example, if a first parameter (e.g., absoluteFrequencySSB) for the frequency position of the AO SSB or the SSB of the reference cell is provided, and a second parameter (e.g., od-absoluteFrequencySSB) for the frequency position of the OD SSB is not provided, the frequency position of the OD SSB may be indicated by the first parameter.
[0338] Example 1-2
[0339] A different frequency setting from that of the AO SSB or the SSB of the reference cell may be used for the OD SSB. In this case, a separate parameter for the frequency position of the OD SSB may be required.
[0340] If the same frequency position is applied to multiple OD SSB configurations, the frequency information may be omitted for each index of the multiple OD SSB configurations. For example, the same frequency information may be used for multiple OD SSB configuration indices, and the frequency information may be included in one of the multiple OD SSB configurations or may be provided separately. The OD SSB frequency parameter may be set to a different value from the frequency parameter of the AO SSB.
[0341] Example 1-3
[0342] The frequency location of the OD SSB may also be provided to the terminal as an offset value relative to the frequency location of the AO SSB. For example, instead of providing the frequency location of the OD SSB directly, it may be provided as a relative value to the frequency location of the AO SSB.
[0343] Example 1-4
[0344] The parameter for the frequency position of the OD SSB can be applied only when there is no AO SSB within the active BWP where the OD SSB is set. If there is an AO SSB within the active BWP, the AO SSB may be applied and the OD SSB may not be applied. Alternatively, the OD SSB may be preset even when there is an AO SSB within the active BWP.
[0345] The above example of whether OD SSB is applicable considering AO SSB can be applied to SCell or SpCell. In addition, the above example of whether OD SSB is applicable considering AO SSB can be applied to all RRC states without distinguishing between various RRC states of the UE (e.g., INACTIVE, IDLE, CONNECTED).
[0346] Example 1-5
[0347] The frequency location of the OD SSB can be set at the cell level or at the BWP level. For example, the OD SSB frequency location can be set for a dedicated BWP. For example, the OD SSB frequency location can be set for one or more units of the serving cell and / or BWP.
[0348] When the OD SSB frequency position is set at the BWP level, the frequency position of the OD SSB may be included within that BWP (or dedicated BWP).
[0349] If a parameter for frequency position (e.g., od-absoluteFrequencySSB) is not provided for an OD SSB configured for a specific BWP or corresponding to a specific BWP, a parameter for frequency position of an AO SSB configured within the specific BWP or an AO SSB configured for a cell to which the specific BWP belongs (e.g., absoluteFrequencySSB) can be (re)used as the frequency position of the OD SSB.
[0350] Example 2
[0351] This embodiment is about setting the SSB index of OD SSB.
[0352] An SSB index can correspond to a position within an SSB burst (e.g., the value of the ssb-positioninBurst parameter). The SSB index can be used to set / indicate whether an SSB at a specific position within the burst is to be transmitted. For example, the ssb-positioninBurst parameter can be included in the SIB1 or ServingCellConfigCommon information element.
[0353] For example, the ssb-positioninBurst parameter in ServingCellConfigCommon can specify the time domain position at which an SSB is transmitted within a half frame, and can be defined in the form of a bitmap. Each bit position in the bitmap can correspond to a specific SSB index (the index value starts from 0). A bit value of 1 indicates that the SSB at the corresponding index / position is transmitted, and a bit value of 0 indicates that the SSB at the corresponding index / position is not transmitted. In addition, the ssb-positioninBurst parameter can have the formats of a 4-bit short bitmap, an 8-bit medium-length bitmap, and a 64-bit long bitmap. The short bitmap can be applied when the number of SSBs per half frame is 4 or less. The medium-length bitmap can be applied when the number of SSBs per half frame is 8 or less. The long bitmap can be applied when the number of SSBs per half frame is 64 or less.
[0354] For example, the ssb-positioninBurst parameter in SIB1 can be set together with the groupPresence field and the inOneGroup field. The groupPresence field is used when the number of SSBs per half frame is at most 64, and it consists of an 8-bit bitmap, where each bit can indicate the presence or absence of a group of 8 SSBs. The inOneGroup field can indicate whether an individual SSB within the group is transmitted. When the maximum number of SSBs per half frame is 4, only 4 bits of the inOneGroup field are valid, and the remaining 4 bits can be ignored. When the maximum number of SSBs per half frame is 8, all 8 bits of the inOneGroup field are valid, and each bit can correspond to an SSB index 0 to 7. When the maximum number of SSBs per half frame is 64, all 8 bits of the inOneGroup field are valid, and each bit can indicate the relative position of an SSB within the group.
[0355] For example, a list of parameter(s) related to the SSB index for OD SSB is set for the terminal, and one parameter from the list can be indicated to the terminal via RRC / MAC-CE / DCI signaling.
[0356] Example 2-1
[0357] The same intra-burst position setting as the intra-burst position setting of the AO SSB or the reference cell may be used for the OD SSB. In this case, a separate parameter for the intra-burst position of the OD SSB may not be provided. For example, if a first parameter (e.g., ssb-PositionsInBurst) for the intra-burst position of the AO SSB or the reference cell is provided, and a second parameter (e.g., od-ssb-PositionsInBurst) for the frequency position of the OD SSB is not provided, the frequency position of the OD SSB may be indicated by the first parameter.
[0358] If a reference cell is specified, the above example may be limited to intra-band CA.
[0359] Example 2-2
[0360] An intra-burst position setting different from the intra-burst position setting of the AO SSB or the SSB of the reference cell may be used for the OD SSB. In this case, a separate parameter for the intra-burst position of the OD SSB may be required.
[0361] If the SSB indices of the OD SSB are located within the same burst as the SSBs of the AO SSB or the reference cell, the parameters related to the SSB indices of the OD SSB may be omitted. For example, if a reference cell related to the SSB is specified, the above example may be limited to the case of intra-band CA.
[0362] Example 2-3
[0363] When an AO SSB exists, an SSB burst including a candidate for the SSB index / ID of the OD SSB can be set among the SSB indexes / IDs actually transmitted from the AO SSB.
[0364] For example, if only SSB indices 0 / 1 / 2 / 3 are signaled to be transmitted for AO SSB via the ssb-PositionsInBurst parameter, the SSB indices constituting the OD SSB may be all or some of 0 / 1 / 2 / 3. Accordingly, index(es) other than SSB indices 0 / 1 / 2 / 3 may not be included for the OD SSB.
[0365] The above example can also be applied to intra-band CA.
[0366] Example 2-4
[0367] The index or burst position of an OD SSB can be set at the cell level or at the BWP level. For example, the OD SSB index or burst position can be set for a dedicated BWP. For example, the OD SSB index or burst position can be set for one or more units of the serving cell and / or BWP.
[0368] When an OD SSB index or position within a burst is set at the BWP level, the frequency position of the OD SSB may be included within that BWP (or a dedicated BWP).
[0369] If a parameter (e.g., od-ssb-PositionsInBurst) for an index or position within a burst is not provided for an OD SSB configured for a specific BWP or corresponding to a specific BWP, the parameter (e.g., ssb-PositionsInBurst) for an index or position within a burst of an AO SSB configured for the specific BWP or the cell to which the specific BWP belongs can be (re)used as the index or position within a burst of an OD SSB.
[0370] Example 2-5
[0371] If both the SSB or SSB burst of the AO SSB and the SSB or SSB burst of the OD SSB are contained within one frame (e.g., 10 ms), the OD SSB can be dropped from that half frame.
[0372] Example 3
[0373] This embodiment relates to setting the number of transmissions of OD SSB. The number of transmissions of OD SSB may correspond to the number of transmissions of a burst of OD SSB, and transmissions of different SSB indices within a burst may not correspond to the number of transmissions.
[0374] The parameter for the number of transmissions of OD SSBs may be included in the same information element together with the parameter for the frequency position and the parameter for the SSB index (or position within the burst) within each OD SSB-related setting in the list of OD SSB-related settings, or may be included in a separate information element independently of these parameters.
[0375] When the number of OD SSB transmissions is set by being included in the same information element, the number of transmissions may be set / indicated together with other parameters of the OD SSB (e.g., frequency position, index (or position within burst), period, etc.) when the OD SSB is indicated via RRC / MAC-CE / DCI.
[0376] When the OD SSB transmission count is set by being included in a separate information element, an independent transmission count value that is not associated with other parameters (e.g., frequency position, index (or position within burst), period, etc.) may be set / indicated.
[0377] The value to which the transmission count parameter can be set may include 0. When the OD SSB transmission count information set to a value of 0 is provided via RRC signaling, this may correspond to a case where the OD SSB is not transmitted. Alternatively, when the OD SSB transmission count information set to a value of 0 is provided via RRC signaling, this may correspond to a case where the OD SSB is triggered via lower layer signaling (e.g., MAC-CE / DCI). For example, the OD SSB may not be triggered via RRC signaling.
[0378] If the number of transmissions parameter for OD SSB is not provided, it may be either 0 or permanent transmission is set / indicated. Permanent transmission may include the case where (periodic) OD SSB transmissions are maintained until OD SSB is deactivated. For example, if the number of transmissions parameter (e.g., od-ssb-nrofburst) is not provided for OD SSB, OD SSB transmissions may occur until deactivated by RRC / MAC-CE / DCI.
[0379] Information about the number of transmissions may be replaced by timer information or window size information.
[0380] Example 3-1
[0381] Assuming that triggering of OD SSB via RRC signaling is permitted, if OD SSB is configured for the SCell during the SCell addition process, the transmission count parameter can be set to a specific value as a way to prevent OD SSB from being triggered via RRC signaling.
[0382] For example, the number of OD SSB transmissions can be provided to the terminal via RRC signaling as one of the combinations such as {0, 1, 2, persistent} or {lower layer setting, 1, 2, persistent} or {5, 10, 20, persistent}.
[0383] Here, persistent means that the OD SSB continues to be transmitted until the OD SSB is deactivated, or until the state of the SCell changes (e.g., state transition such as activation start, activation complete, deactivation start, deactivation end, or SCell release).
[0384] Lower layer setting may refer to a case where the number of OD SSB transmissions is not provided via RRC, but is provided via MAC-CE / DCI. If a value corresponding to the lower layer setting is not defined, and OD SSB is triggered via MAC-CE / DCI signaling according to the number of OD SSB transmissions set via RRC signaling, the number of OD SSB transmissions cannot be changed and must be followed as set by RRC. In addition, if MAC-CE / DCI signaling includes fields such as the number of transmissions or window size, the value of the corresponding field may need to be set to a null value.
[0385] If information about the number of OD SSB transmissions is not provided, lower layers may perform OD SSB transmissions assuming an infinite case of persistent transmission (e.g., until OD SSB is disabled).
[0386] Example 3-2
[0387] Instead of a transmission count, a timer corresponding to the transmission window size or the length of the transmission time interval can be used. The time size / length can be expressed in various units, such as frames, slots, or milliseconds, and the time size / length can be given as a value based on the corresponding unit, such as 0, 1, 2, etc.
[0388] Example 3-3
[0389] Examples of transmission counts for SSB bursts are described below.
[0390] FIG. 22 is a drawing for explaining the start time of OD SSB transmission / reception according to the present disclosure.
[0391] A method for counting whether an OD SSB transmission is performed a given number of times is described. One OD SSB burst may include one or more SSB indices (e.g., beam directions), and transmission (e.g., beam sweeping) may be performed once in the beam direction of each SSB ID / index at each location(s) within each OD SSB burst.
[0392] When an OD SSB transmission is initiated, it may not always start at the beginning of the SSB burst, but may start at any point within the SSB burst. If the time point at which the terminal assumes that the OD SSB transmission is performed is T, the time point at which the terminal receives and recognizes the RRC / MAC-CE / DCI signaling that triggers the OD SSB may correspond to a specific SSB index / ID / position within the burst.
[0393] For example, in the example of FIG. 22, if there are 4 SSB indexes / IDs / locations within one burst, it can be assumed that the OD SSB is triggered just before the 4th SSB index / ID / location. In addition, it can be assumed that the number of SSB transmissions is set / indicated to 3. Accordingly, the terminal can expect that 3 OD SSB bursts are transmitted, and several examples can be considered as to how the 3 OD SSB bursts are counted.
[0394] In the example of Fig. 22, an SSB burst in which only some of the SSB indices / IDs / locations within the burst can be received is called a partial SSB burst, and an SSB burst in which all of the SSB indices / IDs / locations within the burst can be received is called a full SSB burst.
[0395] For example, if at least one SSB index / ID / position within a partial SSB burst is receivable, the corresponding SSB burst may be included in the transmission count. In this case, in the example of FIG. 22, T corresponds to the fourth SSB index position of the first SSB burst, and the terminal may assume that up to the third SSB burst is transmitted.
[0396] Alternatively, if the number of SSB indexes / IDs / locations that the terminal can receive within a partial SSB burst is equal to or greater than the number of SSB indexes / IDs / locations that the terminal has not received (already passed), the partial SSB burst may be counted. If the number of SSB indexes / IDs / locations that the terminal can receive within a partial SSB burst is less than or equal to the number of SSB indexes / IDs / locations that the terminal has not received (already passed), the partial SSB burst may not be counted. In this case, since the first SSB burst in the example of FIG. 22 is not included in the count of the number of transmissions, the terminal may assume that T corresponds to the first SSB index position of the second SSB burst, and is transmitted up to the fourth SSB burst.
[0397] Alternatively, partial SSB bursts may not be counted, and only entire SSB bursts may be counted. In this case, in the example of FIG. 22, T corresponds to the first SSB index position of the second SSB burst, and the terminal may assume that up to the fourth SSB burst is transmitted.
[0398] Alternatively, counting can be performed by SSB index / ID / location within an SSB burst. Accordingly, counting is possible for each SSB index, and the terminal can assume that the SSB transmission is completed when the counts for all SSB indices satisfy the given number of transmissions. In the example of Fig. 22, if the number of SSB transmissions is given as 3, the terminal can assume that the count of the 4th SSB index in the first SSB burst is 1, and in the fourth SSB burst, the 4th SSB index is not counted and only the 1st to 3rd SSB indices are transmitted. In the second and fourth SSB bursts, each SSB index can be counted once.
[0399] Example 3-4
[0400] For cases where deactivation is set / instructed via RRC / MAC-CE / DCI for OD SSB, several examples can be considered for when the terminal stops receiving OD SSB.
[0401] FIG. 23 is a drawing for explaining the OD SSB transmission / reception termination point according to the present disclosure.
[0402] As illustrated in Fig. 23, it is assumed that four SSB indices / IDs / locations are included in one SSB burst and that the OD SSB is activated.
[0403] For example, OD SSB deactivation can be applied based on SSB index / ID / location. In the example of Fig. 23, if the terminal receives and decodes deactivation-related information from the base station at the time of completion of reception of the third SSB index among the four SSB indices within one SSB burst, the terminal can stop OD SSB reception even before receiving the fourth SSB index.
[0404] Alternatively, OD SSB deactivation may be applied based on SSB burst. In the example of Fig. 23, if the terminal receives and decodes deactivation-related information from the base station at a time when the terminal has completed reception up to the third SSB index among the four SSB indices within one SSB burst, the terminal may stop OD SSB reception after receiving up to the fourth SSB index. If the terminal is performing measurement based on OD SSB, if OD SSB deactivation is set / instructed during OD SSB burst reception, the measurement may be terminated after reception up to the last SSB index of the OD SSB burst.
[0405] Example 3-5
[0406] The number of OD SSB transmissions can be set at the cell level or at the BWP level. For example, the number of OD SSB transmissions can be set for a dedicated BWP. For example, the number of OD SSB transmissions can be set for one or more units of the serving cell and / or BWP.
[0407] When the number of OD SSB transmissions is set at the BWP level, the frequency location of the OD SSB can be included within that BWP (or a dedicated BWP).
[0408] The value of the number of transmissions of OD SSB can be set as single or multiple, or can be set to a value indicating other information such as persistent transmission (until deactivated), lower layer settings, etc., as in the examples described above.
[0409] Example 4
[0410] The present embodiment relates to SCS, half frame index, and / or power of OD SSB.
[0411] When multiple OD SSB configurations are provided for a terminal, information such as SCS, half-frame, and power may have the same values applied to multiple OD SSB configurations. Therefore, parameters such as SCS, half-frame, and power of the OD SSB may be provided as a single parameter commonly applied to multiple OD SSB configurations.
[0412] In the scope of the present disclosure, it is not excluded that parameters such as SCS, half frame, and power of OD SSB are individually / independently set / indicated for each OD SSB setting.
[0413] Example 4-1
[0414] The same SCS settings as the SCS settings of the AO SSB or the SSB of the reference cell may be used for the OD SSB. In this case, a separate parameter for the SCS settings of the OD SSB may not be provided. For example, if a first parameter (e.g., ssbSubcarrierSpacing) for the SCS settings of the AO SSB or the SSB of the reference cell is provided, and a second parameter (e.g., od-ssbSubcarrierSpacing) for the SCS settings of the OD SSB is not provided, the SCS settings of the OD SSB may be indicated by the first parameter. If a reference cell is specified, the above example may be limited to be applied in the case of intra-band CA.
[0415] Alternatively, a different SCS configuration from the SCS configuration of the AO SSB or the SSB of the reference cell may be used for the OD SSB. In this case, separate parameters for the SCS configuration of the OD SSB may be required. This example may be limited to cases where the reference cell and the cell in which the OD SSB is configured are inter-band CAs.
[0416] Alternatively, the same SCS settings as the SCS settings of the BWP in which the OD SSB is configured may be used for the OD SSB. In this case, separate parameters for the SCS settings of the OD SSB may not be provided.
[0417] Alternatively, if no SCS configuration parameter (e.g., od-ssbSubcarrierSpacing) is provided for the OD SSB, the SCS configuration parameter (e.g., ssbSubcarrierSpacing) of the AO SSB within the same BWP or cell as the OD SSB can be (re)used as the SCS configuration of the OD SSB.
[0418] Example 4-2
[0419] The half-frame index of the OD SSB indicates in which half-frame the OD SSB is transmitted, for example, in the first half-frame (e.g., half-frame index 0, or the first 5 sub-frames) or the second half-frame (e.g., half-frame index 1, or the last 5 sub-frames) within a radio frame in which the OD SSB exists.
[0420] For example, the same half-frame index as the half-frame index of the SSB of the AO SSB or reference cell may be used for the OD SSB. Alternatively, the opposite half-frame index as the half-frame index of the SSB of the AO SSB or reference cell may be used for the OD SSB. If a reference cell is specified, the above example may be limited to applying to the case of intra-band CA.
[0421] Alternatively, a specific parameter specifying the first or second half-frame for the OD SSB may be provided, and this information may be included in multiple OD SSB configurations. If an AO SSB or reference cell is specified, this parameter may be omitted. If a reference cell is specified, the above example may be limited to applying to the case of intra-band CA.
[0422] Alternatively, it may be predefined as the first half frame for the half frame index of the OD SSB (for example, half frame index 0 may be set to be applied without separate signaling). Alternatively, it may be predefined as the second half frame for the half frame index of the OD SSB (for example, half frame index 1 may be set to be applied without separate signaling). For example, if a specific parameter for the half frame index is omitted in the OD SSB configuration, the terminal may find a half frame in which the OD SSB is transmitted through blind detection, or may assume that a half frame of a specific predefined index (for example, 0 or 1) as in the example above is defined as a default half frame index and attempt to detect the OD SSB in the corresponding half frame.
[0423] In this way, if a half-frame index parameter (e.g., od-ssb-halfFrameIndex) for OD SSB is provided, the terminal can receive OD SSB in the half-frame according to the parameter. If a half-frame index parameter (e.g., od-ssb-halfFrameIndex) for OD SSB is not provided, the terminal can assume / expect that a predefined specific half-frame index (e.g., 0) is applied and receive OD SSB in the corresponding half-frame (e.g., the first half-frame). Alternatively, if a half-frame index parameter for OD SSB is not provided, examples such as blind detection, reuse of the half-frame index of AO SSB or reference cell may be applied. If a reference cell is specified, the above examples may be limited to those applicable in the case of intra-band CA.
[0424] Example 4-3
[0425] The same power as that of the AO SSB may be used for the OD SSB. In this case, a separate parameter for the power of the OD SSB may not be provided. For example, if a first parameter for the power of the AO SSB (e.g., ss-PBCH-BlockPower) is provided and a second parameter for the power of the OD SSB (e.g., od-ss-PBCH-BlockPower) is not provided, the power of the OD SSB may be indicated by the first parameter.
[0426] When a reference cell is specified, the power of the OD SSB can be set / indicated through a specific parameter. If the same power as the reference cell is applied to the OD SSB, the parameter can be omitted. The above example may be limited to cases of intra-band CA.
[0427] Alternatively, if a power parameter (e.g., od-ss-PBCH-BlockPower) is not provided for the OD SSB, the power parameter (e.g., ss-PBCH-BlockPower) of the AO SSB within the same BWP or cell as the OD SSB may be (re)used as the power value of the OD SSB.
[0428] Example 4-4
[0429] The SCS / half-frame / power of the OD SSB can be set at the cell level or at the BWP level. For example, the OD SSB SCS / half-frame / power can be set for a dedicated BWP. For example, the OD SSB SCS / half-frame / power can be set for one or more units of the serving cell and / or BWP.
[0430] When OD SSB SCS / Half Frame / Power is set at BWP level, the frequency location of OD SSB can be included within that BWP (or dedicated BWP).
[0431] Example 5
[0432] This embodiment is about additional considerations when providing OD SSB related information to a terminal.
[0433] For example, a list of the aforementioned parameters may be arranged / assigned for each of multiple OD SSB configurations. If parameter(s) that can be commonly applied to multiple OD SSB configurations (e.g., do not or only slightly change depending on the channel environment) are provided separately, they may be signaled only once rather than repeatedly provided for each OD SSB configuration.
[0434] Example 5-1
[0435] When an AO SSB or an SSB of a reference cell is specified, information such as a period and / or time offset based on the timing of the corresponding SSB may be applied to the OD SSB. The values of the time domain parameters of these OD SSBs may be included for each of the multiple OD SSB settings, or may be included as a single parameter value common to the multiple OD SSBs.
[0436] The parameter for the time offset of the OD SSB may correspond to the SFN (system frame number) of the radio frame in which the OD SSB is transmitted / included. When the terminal determines the SFN of the radio frame in which the OD SSB is transmitted, the terminal can receive the OD SSB in one of the two half frames within the radio frame (see Example 4-2 for an example).
[0437] For example, if information about the time offset of the OD SSB is not provided to the terminal, the terminal may consider the value of the time offset to be 0. For example, the reference point in time for the time offset may be the transmission point in time of the reference SSB (e.g., AO SSB).
[0438] Alternatively, the time offset of the OD SSB may be determined without a specific reference point in time (e.g., regardless of the time resource location of the SSB on the AO SSB or the reference cell). For example, if SFN offset information related to the OD SSB is provided, the SFN of the frame containing the OD SSB may be determined based on the SFN offset information.
[0439] As a more specific example, let the period of OD SSB be P, and the SFN of a frame including OD SSB can be provided to the terminal with an SFN offset (SFN_offset) based on a point in time that satisfies the formula of (SFN * 10) mod P = 0. Here, mod means modulo operation. To express the same meaning differently, the frame including OD SSB can be a frame corresponding to an SFN that satisfies the formula of ((SFN + SFN_offset) * 10) mod P = 0.
[0440] For example, the unit of the SFN offset may be 5ms or 10ms. If the unit of the offset is 10ms, additional setting / instruction for the half-frame index may be required, and if the unit of the offset is 5ms, additional setting / instruction for the half-frame index may not be required.
[0441] In this way, if a parameter for SFN offset (e.g., od-ssb-sfn-Offset) is provided for OD SSB, the SFN of the frame in which OD SSB is transmitted / included can be determined according to the value of the parameter and the formula as above. Alternatively, if a parameter for SFN offset (e.g., od-ssb-sfn-Offset) is not provided for OD SSB, the terminal can apply 0 as the value of SFN offset and determine the SFN of the frame in which OD SSB is transmitted / included according to the formula as above.
[0442] These examples may apply in cases where there is no AO SSB or SSB of the reference cell, or in cases where there is an AO SSB or SSB of the reference cell.
[0443] Example 5-2
[0444] If the period of the OD SSB is the same as the period of the AO SSB or the period of the SSB of the reference cell, the parameter for the period of the OD SSB may be omitted.
[0445] The period of the OD SSB may be limited to be less than or equal to the period of the AO SSB, if an AO SSB is present.
[0446] A non-zero time offset between the AO SSB and the OD SSB may be provided so that the AO SSB and the OD SSB are transmitted without overlapping each other in the time domain. Alternatively, the values of related information such as the SFN index and half-frame index through which the AO SSB and the OD SSB are transmitted may be set to a limited extent so that they do not have the same values.
[0447] Example 6
[0448] This embodiment describes a method for applying a time offset to an OD SSB. For example, various methods for setting the time domain position of an OD SSB are described.
[0449] It can be assumed that the AO SSB is within the same cell / BWP as the OD SSB, or not. The positioning in the time domain can include, as mentioned above, a period, a half-frame, an SFN, etc. In particular, for the SFN, a time offset from a specific reference point (e.g., SFN_offset) can be applied.
[0450] For example, the value of SFN_offset can be set to one of the values from 0 to 15. Here, the values of 1, 2, 3, ... can correspond to 10ms, 20ms, 30ms. That is, the SFN offset can be provided from 0ms to 150ms from the reference point in time, and accordingly, the value of the SFN_offset parameter can be set / indicated within the range of 0 to 15.
[0451] Various examples are provided on how to determine the position of the OD SSB in the time domain based on the SFN_offset relative to a point in time, for cases where the AO SSB is within a cell / BWP and cases where the AO SSB is not within a cell / BWP.
[0452] For example, SFN_offset can be applied based on the SFN position that satisfies the formula of (SFN_index * 10) mod P = 0. If the value of SFN_offset is not set / indicated or is not required, the terminal can assume / apply the value of SFN_offset as 0.
[0453] The above examples may be limited to cases where the AO SSB is not within the cell / BWP or where the frequency locations of the AO SSB and OD SSB are different.
[0454] Alternatively, in the case where the AO SSB is within the cell / BWP, the SFN_offset is applied based on the AO SSB transmission SFN as a reference point, and the range of the SFN_offset value can be defined differently depending on whether the periods of the AO SSB and the OD SSB are the same. For example, if the periods of the AO SSB and the OD SSB are the same, SFN_offset = (0), 1, ..., P_ODSSB / 20 (or P_AOSSB / 20) (wherein P_ODSSB corresponds to the period of the OD SSB, P_AOSSB corresponds to the period of the AO SSB, and / (division) can be replaced by a floor operation (the largest integer less than or equal to the result of the division)). If the periods of the AO SSB and the OD SSB are different, SFN_offset = (0), 1, ..., P_ODSSB / 10 (or P_AOSSB / 10). Alternatively, if the periods of AO SSB and OD SSB are different, SFN_offset = (0), 1, ..., P_ODSSB / 10 - 1 (or P_AOSSB / 10 - 1).
[0455] The reason why the SFN_offset range is different depending on the cycle is that when the cycles of the two SSBs are different, an SFN_offset of 10ms in units of OD SSB cycle is possible, but when the cycles are the same, the two SSB transmission patterns can be the same even if the range is set to only half the cycle, so a value of SFN_offset exceeding half the cycle only increases the signaling overhead.
[0456] If SFN_offset is not set / indicated or is not required, and the periods of the two SSBs are the same, SFN_offset can be P_ODSSB / 20 (or P_AOSSB / 20) based on the AO SSB transmission SFN. For example, it can be assumed that the periods of the two SSBs are the same as 40ms, and the AO SSBs are transmitted at SFN 0, 40, 80ms, ..., and the OD SSBs are transmitted at SFN 20, 60, 100ms, ... by applying 20ms as the value of SFN_offset. In this case, there may be an advantage of doubling the SSB density since the two SSBs are transmitted at the same interval.
[0457] If the periods of the AO SSB and the OD SSB are different, it can be assumed that the SFN_offset from the transmission SFN of the AO SSB is 0. For example, it can be assumed that the period of the AO SSB is 40 ms and it is transmitted at SFN 0, 40, 80 ms, ..., and the period of the OD SSB is 20 ms and SFN_offset=0 is applied from the transmission SFN of the AO SSB, so it is transmitted at SFN 0, 20, 40, 60, 80 ms, .... This corresponds to the case where the transmission of the AO SSB and the transmission of the OD SSB can overlap each other in the time domain.
[0458] Also, when the frequencies of two SSBs are the same, the value of SFN_offset can be set to 0 to make the two SSBs overlap in the time domain, or the value of SFN_offset can be set to a non-zero value to prevent them from overlapping in the time domain. For example, assuming that the AO SSB has a period of 80 ms and the SFN_offset is 0, the AO SSB can be transmitted at SFN index values of 0, 8, 16, 24, ..., and if the period of the OD SSB is also 80 ms, the SFN_offset from the transmitted SFN of the OD SSB can be provided as one of (0), 1, 2, 3, or (0), 1, 2, 3, 4. If the period of the OD SSB is 40 ms, the SFN_offset can be provided as one of (0), 1, 2, 3, or (0), 1, 2, 3, 4.
[0459] When the AO SSB is within a cell / BWP, the period may be taken into account for setting / indicating half frames. For example, when the periods of the AO SSB and OD SSB are the same, the same half frame as the half frame of the AO SSB may be applied to the OD SSB. When the periods of the AO SSB and OD SSB are different, a half frame different from the half frame of the AO SSB may be predefined to be applied to the OD SSB, or the half frame index of the OD SSB may be set / indicated regardless of whether it is within a cell / BWP or not.
[0460] If the period of AO SSB is too short, transmitting OD SSB may hinder the application of half frames and power savings, so OD SSB can be restricted to be used only when AO SSB is longer than a certain period. For example, OD SSB can be applied only when the period of AO SSB is longer than 20ms or 40ms. Alternatively, the minimum supported period of AO SSB that can use OD SSB can be defined as either 20ms or 40ms.
[0461] Instead of setting / indicating two things, SFN_offset and half-frame index, for setting / indicating time-related offset of OD SSB, one time offset in units of 5 ms (e.g., OD-SSB_TimeOffset) can be applied similarly to SFN_offset from the transmission point of AO SSB (e.g., transmission point considering half-frame). Here, the reference of the time offset can be defined as a time offset based on the transmission position in units of 5 ms considering half-frame of AO SSB. In this case, the range of the time offset can be (0), 1, 2, ..., P_ODSSB / 5 (or P_AOSSB / 5). Alternatively, the range of the time offset can be (0), 1, 2, ..., P_ODSSB / 5 - 1 (or P_AOSSB / 5 - 1).
[0462] If the time offset value in units of 5ms is not set / indicated or is not required, the value of the time offset can be assumed to be 0. If the periods of the AO SSB and OD SSB are the same, it can be assumed that the OD SSB is transmitted at the middle position of the AO SSB transmission period.
[0463] When the frequency positions of the AO SSB and OD SSB are set differently, the center frequency of the OD SSB can be set to have a difference in the frequency direction higher or lower than the center frequency of the AO SSB by a certain number of PRBs. For example, the frequency difference between the AO SSB and the OD SSB can be set to be 20 PRBs or more based on the center frequency.
[0464] If there is no AO SSB in the cell / BWP, the SFN offset and half-frame index for the OD SSB can be set by individual parameters. For the SFN offset, an offset value of the SFN level from the reference point can be set based on the reference point. If the SFN offset value is not set, the terminal can assume that it is set to 0. In this case, the reference point can be a plurality of SFNs satisfying the formula of (SFN index * 10) mod P = 0, where P is the period of the OD SSB. For example, if the period of the OD SSB is 40 ms, all SFNs having a multiple of 4 can be reference points, and the OD SSB can be transmitted at the SFNs that are separated by the SFN offset value from the reference point. For example, if the SFN offset value is set to 1, the OD SSB can be transmitted at the SFNs corresponding to SFN indices 1, 5, 9, 13, ... Additionally, the half-frame index can also be set as an individual parameter, with a value of 0 or 1, or if no separate setting is made, the terminal can assume 0.
[0465] When AO SSB exists in a cell / BWP, specific methods for the terminal to determine the SFN offset and half-frame index are described below.
[0466] In a similar way to when AO SSB exists in a cell / BWP, when the SFN offset value and half-frame index are set separately, the default value when there is no separate setting value can be defined as follows. When the SFN offset value is not set separately, different rules can be applied depending on whether the period values between AO SSB and OD SSB are the same or different.
[0467] First, when the periods of the AO SSB and the OD SSB are the same, the SFN offset of the OD SSB can be determined so that the AO SSB and the OD SSB can intersect at equal intervals. For example, when the period of the AO SSB is 40 m and it is transmitted at every SFN that is a multiple of 4 (e.g., the AO SSB is transmitted at SFN 0, 4, 8, 12, ...), if the SFN offset value for the OD SSB is not separately set, the terminal can assume that the OD SSB is transmitted at every SFN that satisfies the condition of (a multiple of 4 + 2) (e.g., the OD SSB is transmitted at SFN 2, 6, 10, 14, ...). This allows the AO SSB and the OD SSB to be transmitted at equal intervals at every 2 SFNs, which can simplify the implementation when the terminal performs SSB-based measurements.
[0468] Next, when the periods of the AO SSB and the OD SSB are different values, the SFN offset value of the OD SSB can be determined so that an inclusive relationship is created between the AO SSB and the OD SSB. For example, when the period of the AO SSB is 80 ms and it is transmitted at every SFN that is a multiple of 8 (e.g., when the AO SSB is transmitted at SFN 0, 8, 16, ...), and the OD SSB period is 40 ms and the SFN offset value for the OD SSB is not separately set, the terminal can assume that the OD SSB is transmitted at every SFN that is a multiple of 4 (e.g., when the OD SSB is transmitted at SFN 0, 4, 8, 12, 16, ...).
[0469] When an AO SSB exists in a cell / BWP and the half-frame index value is not set separately, different rules may be applied depending on whether the period values between the AO SSB and OD SSB are the same or different.
[0470] First, when the periods of the AO SSB and the OD SSB are the same value (and the SFN index value for the OD SSB is not set either), the half-frame index of the OD SSB can be determined to be the same value as the half-frame index of the AO SSB. As in the example above, when the period of the AO SSB is 40 ms and is transmitted at every SFN that is a multiple of 4 (for example, the AO SSB is transmitted at SFN 0, 4, 8, 12, ...), and the OD SSB is transmitted at every SFN that satisfies the condition of (a multiple of 4 + 2) (for example, the OD SSB is transmitted at SFN 2, 6, 10, 14, ...), the half-frame index value of the AO SSB can be applied as the half-frame index value of the OD SSB as it is (for example, if the half-frame index value of the AO SSB is 0, the half-frame index value of the OD SSB is also determined to be 0). This allows AO SSB and OD SSB to be transmitted at equal intervals of every 20 ms, simplifying the implementation of SSB-based measurements at the terminal.
[0471] Next, when the periods of the AO SSB and the OD SSB are different values (and the SFN index value for the OD SSB is not set), the half-frame index of the AO SSB and the half-frame index of the OD SSB can be determined to different values. As in the example above, when the period of the AO SSB is 80 ms and is transmitted at every SFN that is a multiple of 8 (i.e., the AO SSB is transmitted at SFN 0, 8, 16, ...), and the period of the OD SSB is 40 ms and is transmitted at every SFN that is a multiple of 4 (e.g., the OD SSB is transmitted at SFN 0, 4, 8, 12, 16, ...), the half-frame index of the OD SSB can be determined to a different value from the half-frame index of the AO SSB (e.g., when the half-frame index value of the AO SSB is 0, the half-frame index value of the OD SSB can be determined to 1). This avoids collisions even when AO SSB and OD SSB are transmitted in the same SFN.
[0472] Alternatively, when an AO SSB exists in a cell / BWP, and the periods of the AO SSB and OD SSB are the same, the half-frame index value of the OD SSB may be set to be the same as or different from the half-frame index value of the AO SSB. When an AO SSB exists in a cell / BWP, and the periods of the AO SSB and OD SSB are different, the half-frame index value of the OD SSB may be determined to be the same as the half-frame index value of the AO SSB, and a separate setting may not be allowed.
[0473] Example 7
[0474] This embodiment is about a method for setting OD SSB and applying parameters in BWP units.
[0475] Although the examples described above primarily describe OD SSB-related setting parameters at the cell level, the examples of the present disclosure can also be applied to OD SSB setting and parameter configuration at the BWP level, and OD SSB setting and parameter configuration when OD SSB is activated or deactivated.
[0476] As mentioned above, parameters included in the OD SSB related configuration may include SCS configuration, frequency position, offset, period, number of transmissions (or window or timer), index (or SSB-positioninBurst in bitmap form), half frame, power, etc. One or more RRC information elements are provided for candidate(s) of these parameter(s), and one of the candidate(s) may be indicated / activated / triggered via RRC / MAC-CE / DCI signaling after (re)configuration. This configuration / indication may be provided on a BWP basis rather than a cell basis.
[0477] For example, assume that K parameter groups for OD SSB-related settings are included in a single RRC information element set. One or more sets may be included in RRC signaling related to SCell addition / modification. In this case, one or more sets may be configured within a feature BWP.
[0478] If only one set is configured for each BWP, the OD SSB may be predefined / preconfigured to be automatically activated according to the OD SSB settings of the set when the BWP is activated, or the OD SSB settings of the set may be applied to the BWP, and activation of the OD SSB may be signaled through a separate RRC / MAC-CE / DCI.
[0479] If multiple sets are set for each BWP, the OD SSB can be activated through information on which ID / index setting among the multiple OD SSB settings is applied when the BWP is activated.
[0480] Example 7-1
[0481] When multiple OD SSB configuration sets are provided for a specific BWP, one of the multiple OD SSB configuration sets (e.g., an index of the OD SSB configuration set) may be indicated when transmission of the OD SSB associated with the BWP is indicated via RRC / MAC-CE / DCI signaling.
[0482] When a single OD SSB configuration set is provided for a specific BWP, and when transmission of the OD SSB associated with that BWP is indicated via RRC / MAC-CE / DCI signaling, a separate set index may not be provided, and the values of the parameters included in the single OD SSB configuration set may be applied to the OD SSB transmission.
[0483] If required, the BWP index value may also be included as a separate field within the RRC / MAC-CE / DCI signaling indicating OD SSB transmission.
[0484] If OD SSB is triggered while SCell is inactive, the MAC-CE related to activation / triggering of OD SSB may include BWP ID / index of the cell together with information indicating a specific cell. Alternatively, if no separate BWP ID / index is indicated in the RRC / MAC-CE / DCI signaling indicating OD SSB transmission, it may be predefined or preset that OD SSB transmission is indicated for a reference BWP. For example, the reference BWP may correspond to the first active downlink BWP (firstActiveDownlinkBWP), the initial BWP, the default BWP, the BWP with the highest index, or the BWP with the lowest index. For example, if no BWP is indicated in the signaling related to OD SSB transmission, the OD SSB of the BWP corresponding to firstActiveDownlinkBWP-ID may be predefined or preset to be activated / triggered. If the BWP specified by firstactiveDownlinkBWP-ID does not have an OD SSB configured, the terminal may utilize the AO SSB configured for that BWP, or may expect the OD SSB to be received from one of the default BWPs with the lowest or highest BWP index in that order, or from one of the default BWPs with an OD SSB configured.
[0485] If only one OD SSB configuration set is associated with a dedicated BWP, then that set applies, but if multiple OD SSB configuration sets are associated, then in addition to the information indicating the BWP, information indicating one of the multiple OD SSB configuration sets (e.g., configuration ID or configuration index) may be included in the OD SSB activation / triggering signaling.
[0486] If the SCell is in an activated state (e.g., in the process of being activated or activated), only when the dedicated BWP becomes the active BWP, one of the configuration indexes or configuration IDs from among the configuration sets of multiple OD SSBs can be provided via RRC / MAC-CE / DCI signaling. If there is only one OD SSB configuration set, OD SSBs according to the corresponding OD SSB configuration set can be transmitted and received immediately when the corresponding BWP is applied, or transmission and reception of OD SSBs according to the corresponding OD SSB configuration set can be activated / triggered via additional signaling.
[0487] If a single OD SSB configuration set is associated with an individual BWP, the currently active BWP may be forced to remain disabled (for the OD SSB) when switching BWPs. Alternatively, if the OD SSB is enabled / disabled in the active BWP, the corresponding state may be reapplied to enable / disable the OD SSB in the indicated BWP as well.
[0488] In the case of BWP switching, the activation of the OD SSB may be indicated in the indicated BWP. For example, the activation / deactivation of the OD SSB in the active BWP may be indicated via L1 DCI signaling, and during BWP switching, an instruction related to the activation of the OD SSB in the indicated BWP may also be included.
[0489] Example 7-2
[0490] In the case of OD SSB configuration, some of the K parameters required for OD SSB may be set at the cell level, and others may be set for a dedicated BWP.
[0491] For example, OD SSB related parameters may include period, number of transmissions, frequency position, offset, half frame, output power, SSB index (or positioninBurst), SCS setting, etc. Some parameter(s) among these may be set at the cell level, and other parameter(s) may be set at the BWP level in some cases. For example, period, number of transmissions, etc. may be defined to be set at the cell level, and multiple lists may be set through RRC signaling. For a dedicated BWP, one RRC IE including parameters such as half frame, power, SSB index (or positioninBurst), SCS setting, etc. may be set. Mainly, only one OD SSB parameter setting set is set for a dedicated BWP, and when multiple OD SSB parameter setting sets are set, index information for each setting set may be defined. In the BWP, activation / triggering of OD SSB can be indicated by one configuration index / ID from a list of multiple cell level configuration parameters (e.g., transmission period, number of transmissions, etc.) via RRC / MAC-CE / DCI control signaling.
[0492] Accordingly, by setting only one OD SSB configuration set for a dedicated BWP and signaling one of multiple transmission periods or transmission counts at the cell level, the terminal can recognize when it can receive OD SSB. In addition, if necessary, the BWP index value can be included as a separate field in the RRC / MAC-CE / DCI signaling indicating OD SSB transmission.
[0493] If OD SSB is triggered while SCell is disabled, the OD SSB activation / triggering MAC CE may include the BWP ID of the cell along with information indicating a specific cell. Alternatively, if no separate BWP index is indicated in the RRC / MAC-CE / DCI signaling indicating OD SSB transmission, it may be predefined or preconfigured that OD SSB transmission is indicated for a reference BWP. The reference BWP may correspond to, for example, firstActiveDownlinkBWP-ID, the first BWP, the default BWP, the BWP with the lowest index, or the BWP with the highest index. For example, if no BWP is indicated in the signaling related to OD SSB transmission, the OD SSB of the BWP corresponding to firstActiveDownlinkBWP-ID may be predefined or preconfigured to be activated / triggered. If the BWP specified by firstactiveDownlinkBWP-ID does not have an OD SSB configured, the terminal may utilize the AO SSB configured for that BWP, or may expect the OD SSB to be received from one of the default BWPs with the lowest or highest BWP index in that order, or from one of the default BWPs with an OD SSB configured.
[0494] In this case, if only one OD SSB configuration set is associated with the dedicated BWP from the beginning, that set is applied, but if multiple OD SSB configuration sets are associated, in addition to the information indicating the BWP, information indicating one of the multiple OD SSB configuration sets (e.g., configuration ID or configuration index) may be included in the OD SSB activation / triggering signaling.
[0495] When multiple OD SSB configuration sets are configured for a dedicated BWP, information indicating one of the multiple OD SSB configuration sets may be included in addition to information indicating the corresponding BWP in RRC / MAC-CE / DCI signaling.
[0496] If one OD SSB configuration set is associated with each BWP, the currently active BWP may be kept disabled (for the OD SSB) unconditionally when switching BWPs, or if the OD SSB is in an enabled / disabled state in the active BWP, the state may be reapplied as is to apply OD SSB enable / disable to the indicated BWP as well.
[0497] In the case of BWP switching, whether or not to activate the OD SSB in the indicated BWP may be indicated. For example, whether to activate / deactivate the OD SSB in the active BWP may be indicated via L1 DCI signaling, and when BWP switching is performed, an instruction related to the activation of the OD SSB in the indicated BWP may also be included.
[0498] Example 7-3
[0499] In case there is no AO SSB for the (dedicated) BWP, the OD SSB may be limited to being set to that (dedicated) BWP level.
[0500] Example 8
[0501] This embodiment relates to a method for applying the number of OD SSB transmissions according to BWP switching.
[0502] Switching to an active BWP may occur after the SCell activation command. Assuming that the number of OD SSB transmissions set before BWP switching is N, it is necessary to define how the number of OD SSB transmissions will be applied when BWP switching occurs.
[0503] When a BWP switching occurs, the OD SSB being transmitted in the previous BWP may be unconditionally disabled. If the newly instructed BWP requires OD SSB, it may be necessary to re-enable OD SSB in the BWP. Alternatively, if OD SSB is enabled in the previous BWP during BWP switching, the enabled state of OD SSB may be maintained / applied in the newly instructed BWP as well. If OD SSB is not set for the newly instructed BWP, the deactivation of OD SSB may be maintained / applied along with the BWP switching. For example, for a finite number of transmissions N, counting of the number of transmissions may be applied continuously before and after BWP switching, or, if the activation of OD SSB is applied / maintained in the instructed BWP, the number of transmissions N may be applied infinitely or permanently (e.g., OD SSB may be transmitted until deactivated). Alternatively, if a finite number of transmissions N is set before BWP switching, the OD SSB being transmitted during BWP switching may be disabled.
[0504] If switching to an active BWP occurs after the SCell activation command, the following may be applied to the number of OD SSB transmissions N set before BWP switching.
[0505] Example 8-1
[0506] When a BWP switching occurs, the OD SSB being transmitted by the BWP prior to the switching may be unconditionally disabled. If a newly designated BWP requires an OD SSB, the BWP may need to re-enable the OD SSB.
[0507] Example 8-2
[0508] When switching BWPs, if the OD SSB is activated in the previous BWP, the activated state can be maintained / applied in the newly designated BWP. If the OD SSB is not set for the newly designated BWP, the OD SSB can be maintained / applied inactive along with the BWP switching. If an AO SSB exists for the newly designated BWP, the AO SSB can be used, or the OD SSB of the previous BWP can continue to be used by taking advantage of a measurement gap, etc.
[0509] For example, for a finite number of transmissions N in a BWP before switching, the counting of N may continue in the OD SSB of the BWP after switching. Alternatively, if the OD SSB is not set in the BWP after switching and the AO SSB exists, the counting value for the number of transmissions N before switching may be maintained while receiving the AO SSB in the BWP after switching. Alternatively, if the OD SSB is not set in the BWP after switching, the OD SSB may be automatically deactivated. Alternatively, the terminal may receive the OD SSB of the BWP before switching through a measurement gap, etc., until the finite number of transmissions N expires.
[0510] For example, if the number of transmissions N in the BWP before switching is an infinite / permanent / non-numerical value, OD SSBs can be continuously received in the BWP after switching. If the number of transmissions N in the BWP before switching is a finite value, the corresponding OD SSBs may be deactivated when the BWP is switched.
[0511] According to the examples of the present disclosure, when a configuration for OD SSB for SCell is provided, a signaling / application method for various parameters that may be included in the OD SSB configuration may be provided. It may be specifically defined whether a value is applied when it is provided for each parameter and when it is not provided, and in particular, by clearly defining cases in which a parameter for AO SSB is used for OD SSB and cases in which a default value of a parameter is used for OD SSB, transmission and reception operations of OD SSB can be performed accurately and efficiently while reducing signaling overhead.
[0512] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.
[0513] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.
[0514] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.
[0515] Here, the wireless communication technology implemented in the device of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.
[0516] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A, 5G, and 6G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A, 5G, and 6G systems.
Claims
A step of receiving information related to a first synchronization signal block on a cell by a terminal; and A step of receiving the second synchronization signal block on the cell by the terminal based on information related to the second synchronization signal block, A method wherein, based on the half-frame index information related to the second synchronization signal block being provided, the index of the half-frame including the second synchronization signal block is determined by the half-frame index information. In the first paragraph, A method wherein the index of the half frame including the second synchronization signal block is a predefined index based on the fact that the half frame index information is not provided. In the second paragraph, The above predefined index is 0, how. In the third paragraph, The above predefined index 0 corresponds to the first half frame among two half frames within the frame. In the first paragraph, A method wherein a frame including the second synchronization signal block is determined by an SFN index based on the SFN offset information, based on the system frame number (SFN) offset information related to the second synchronization signal block. In paragraph 5, A method in which a frame including the second synchronization signal block is based on a value of the SFN index and the SFN offset information related to a period (P) of transmission of the second synchronization signal block. In paragraph 6, A method in which the value of the above SFN offset information is an offset value from the SFN index that satisfies the value 0 obtained by applying a modulo P operation to the value obtained by multiplying the SFN index by 10. In paragraph 6, A method based on the fact that the SFN index related to the frame including the second synchronization signal block is 0 when the result of applying a modulo P operation to the sum of the values of the SFN index and the SFN offset information multiplied by 10 is 0. In the first paragraph, A method wherein the value of the SFN offset information is 0 based on the fact that the SFN offset information related to the second synchronization signal block is not provided. In the first paragraph, A method wherein the half-frame index relates to one of two half-frames in a frame containing the second synchronization signal block. In the first paragraph, Based on the position information within the second burst related to the second synchronization signal block being provided, the index of the second synchronization signal block is determined by the value of the position information within the second burst, A method wherein the index of the second synchronization signal block is determined by the value of the position information within the first burst related to the first synchronization signal block, based on the fact that position information within the second burst related to the second synchronization signal block is not provided. In the first paragraph, Based on the second frequency position information related to the second synchronization signal block being provided, the frequency position of the second synchronization signal block is determined by the value of the second frequency position information, A method wherein the frequency position of the second synchronization signal block is determined by the value of the first frequency position information related to the first synchronization signal block, based on the fact that the second frequency position information related to the second synchronization signal block is not provided. In the first paragraph, Based on the second subcarrier spacing (SCS) information related to the second synchronization signal block being provided, the SCS setting of the second synchronization signal block is determined by the value of the second SCS information, A method wherein the SCS setting of the second synchronization signal block is determined by the value of the first SCS information related to the first synchronization signal block, based on the fact that the second subcarrier spacing (SCS) setting information related to the second synchronization signal block is not provided. In the first paragraph, Based on the second power information related to the second synchronization signal block being provided, the power of the second synchronization signal block is determined by the value of the second power information, A method wherein the power of the second synchronization signal block is determined by the value of the first power information related to the first synchronization signal block, based on the second power information related to the second synchronization signal block not being provided. In the first paragraph, Based on the burst number information related to the second synchronization signal block being provided, the number of transmissions of the second synchronization signal block is determined by the value of the burst number information, A method in which transmission of the second synchronization signal block occurs until it is deactivated based on the fact that burst number information related to the second synchronization signal block is not provided. In the first paragraph, The above first synchronization signal block is an SSB (synchronization signal / PBCH (physical broadcast channel) block), A method wherein the second synchronization signal block is an on-demand SSB. In the first paragraph, A method wherein the above cell is a secondary cell (SCell). In the first paragraph, A method wherein at least one of the half-frame index information, SFN offset information, position information within the second burst, or burst number information related to the second synchronization signal block is provided through a MAC-CE (medium access control-control element). one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving information related to the first synchronization signal block on the cell through the one or more transceivers; and Based on information related to the second synchronization signal block, the second synchronization signal block is set to be received on the cell through the one or more transceivers, A terminal, wherein the index of a half frame including the second synchronization signal block is determined by the half frame index information, based on the half frame index information related to the second synchronization signal block. A step of transmitting information related to the first synchronization signal block on a cell by a base station; and A step of transmitting the second synchronization signal block on the cell by the base station based on information related to the second synchronization signal block, A method wherein, based on the half-frame index information related to the second synchronization signal block being provided, the index of the half-frame including the second synchronization signal block is determined by the half-frame index information. one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting information related to the first synchronization signal block on the cell via the one or more transceivers; and Based on information related to the second synchronization signal block, the second synchronization signal block is set to be transmitted on the cell via the one or more transceivers, A base station, wherein the index of a half frame including the second synchronization signal block is determined by the half frame index information, based on the half frame index information related to the second synchronization signal block. one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 17 based on execution by said one or more processors. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control the performance of a method according to any one of claims 1 to 17.
Citation Information
Patent Citations
Lubricating powder production system capable of producing high-purity lubricating powder through cooling and filtration
KR1020230146308A
Passive component plating method
KR102210873B1
Method for transmitting and receiving synchronization signal block and apparatus therefor
US20210092696A1
Random access method, communications apparatus, chip, and storage medium
US20240179751A1
Transmission mechanism with 120 KHZ subcarrier spacing in fr1 for wireless communications
WO2024138671A1