Method and device for transmitting and receiving synchronization signal and physical broadcast channel block (SSB) in on-demand method in wireless communication system
By establishing a quasi-co-located relationship between SSBs, the method allows terminals to efficiently receive on-demand SSBs, reducing power consumption and enabling energy-saving SSB transmissions in wireless communication systems.
Patent Information
- Application Number
- PCT/KR2026/096555
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-20
- Filing Date
- 2026-05-04
- Publication Date
- 2026-11-12
AI Technical Summary
In wireless communication systems, the frequent transmission of always-on synchronization signals (AO-SSBs) leads to high power consumption and delays in terminal synchronization and measurement, especially with the introduction of on-demand SSBs (OD-SSBs) causing rapid power consumption and measurement delays.
The method involves determining a quasi-co-located (QCL) relationship between SSBs, allowing terminals to reuse previous receiving beams and synchronization information, reducing unnecessary power consumption by transmitting OD-SSBs only when necessary.
This approach reduces terminal power consumption and enables efficient reception of OD-SSBs, while also contributing to energy savings at the base station by minimizing unnecessary SSB transmissions.
Smart Images

Figure KR2026096555_12112026_PF_FP_ABST
Abstract
Description
Method and apparatus for transmitting and receiving synchronization signals and physical broadcast channel blocks (SSBs) on-demand in a wireless communication system
[0001] The following description relates to a wireless communication system and to a method and apparatus for transmitting and receiving an SSB (synchronization signal / physical broadcast channel block) on-demand in a wireless communication system.
[0002] The 5G mobile communication system is a successor technology to LTE (Long Term Evolution) and is a new clean-slate type of mobile communication system characterized by high performance, low latency, and high availability. In the case of 5G NR, all available spectrum resources can be utilized, ranging from low-frequency bands below 1 GHz to intermediate frequency bands between 1 GHz and 10 GHz, and high-frequency bands above 24 GHz (e.g., millimeter wave). Based on the underlying technology of 5G mobile communication, 6G systems are being developed.
[0003] The 6G system aims for (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 IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.
[0004] In wireless communication systems, building eco-friendly networks by reducing carbon emissions and lowering the operational expenditure (OPEX) of telecommunications operators has become a major issue. For example, as the introduction of 5G communication requires high transmission rates, base stations must be equipped with a larger number of antennas and provide services through wider bandwidths and frequency bands. As a result, according to recent studies, the energy costs of base stations have reached 20% of total OPEX.
[0005] In this regard, energy conservation for base stations is a very important issue, and as one solution, the transmission of on-demand synchronization signal and physical broadcast channel block (OD-SSB) by the base station may be considered. OD-SSB refers to an SSB that is not transmitted regularly but is intermittently transmitted when transmission is activated by need or request. In contrast, in the prior art, SSBs were not transmitted when transmission was activated by need or request but were transmitted regularly; in this sense, the prior art SSB can be referred to as AO (always-on)-SSB.
[0006] Meanwhile, with the introduction of OD-SSB, dynamic changes in SSBs transmitted from a specific cell may occur. In this case, if the terminal performs synchronization and reset of the receiving beam every time to receive / measure the changing SSB, there is a problem of rapid increase in the terminal's power consumption and delays in measurement and handover.
[0007] The present disclosure aims to provide a method and apparatus for transmitting and receiving OD-SSB in a wireless communication system.
[0008] The present disclosure relates to a method and apparatus for assuming / determining the quasi-co-located (QCL) relationship of SSBs in a wireless communication system.
[0009] The present disclosure relates to a method and apparatus for measuring and reporting channel state information (CSI) for an SSB received in a wireless communication system.
[0010] The technical objectives to be achieved in this disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art to which the technical configuration of this disclosure applies, based on the embodiments of this disclosure described below.
[0011] As an example of the present disclosure, a method performed by a terminal in a wireless communication system is characterized by receiving on-demand SSB (OD-SSB) configuration information and receiving at least one SS / PBCH block (SSB) based on the OD-SSB configuration information, wherein the terminal determines that the SS / PBCH blocks are QCL based on the fact that among the specific SS / PBCH blocks provided by the OD-SSB configuration information, the SS / PBCH blocks have the same SS / PBCH block index.
[0012] In another aspect, a terminal, device, or computer-readable medium is provided to execute the above method.
[0013] The embodiments of the present disclosure described above are merely some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure can be derived and understood by those skilled in the art based on the detailed description of the present disclosure set forth below.
[0014] According to the present disclosure, power consumption of a terminal can be reduced. Since OD-SSBs are generally transmitted less frequently than AO-SSBs or only when necessary, if the terminal must find a new receiving beam and precisely synchronize it every time, the RF element must be kept on for a long time. On the other hand, according to the present disclosure, by assuming that the OD-SSB is QCL with the previously received SSB, the terminal can immediately reuse the receiving beam direction and synchronization information that the terminal already knows, and consequently, unnecessary power consumption of the terminal can be prevented by reducing meaningless search time.
[0015] In addition, through the QCL relationship, the terminal can immediately receive and measure the short burst of OD-SSB without missing it.
[0016] In addition, according to the present disclosure, by enabling the terminal to receive OD-SSB more effectively, the base station can reduce the number of SSB transmissions, and consequently contribute to energy saving of the base station.
[0017] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by a person skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by a person skilled in the art from the embodiments of the present disclosure.
[0018] FIG. 1 illustrates an example of a flexible network topology applicable to the present disclosure.
[0019] FIG. 2 illustrates an example of the structure of a wireless communication system applicable to the present disclosure.
[0020] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.
[0021] FIG. 4 illustrates an example of a communication procedure between a first node and a second node applicable to the present disclosure.
[0022] Figure 5 illustrates an example of a general functional architecture related to both functionality-based life cycle management (LCM) and model-based LCM.
[0023] FIG. 6 illustrates an example of an operation procedure based on an AI (artificial intelligence) / ML (machine learning) model applicable to the present disclosure.
[0024] FIG. 7 illustrates an example of an electromagnetic spectrum applicable to the present disclosure.
[0025] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication applicable to the present disclosure.
[0026] FIG. 9 illustrates an example of a beam management procedure applicable to the present disclosure.
[0027] FIG. 10 illustrates an example of a general scenario for a non-terrestrial network (NTN) based on a transparent payload applicable to the present disclosure.
[0028] FIG. 11 illustrates an example of a general NTN scenario based on a regenerated payload applicable to the present disclosure.
[0029] Figure 12 illustrates examples of the components of the OPE (orbital parameter ephemeris) format.
[0030] Figure 13 illustrates examples of offsets in links related to satellites.
[0031] Figure 14 illustrates examples of TA (timing advanced) values in a link related to a satellite.
[0032] FIGS. 15 and FIGS. 16 illustrate examples of sensing operations applicable to the present disclosure.
[0033] FIG. 17 illustrates an example of a time / frequency resource for a sensing operation applicable to the present disclosure.
[0034] FIG. 18 illustrates an example of a procedure related to a sensing operation applicable to the present disclosure.
[0035] FIG. 19 illustrates an example of the operation procedure of a base station supporting network energy saving (NES) technology applicable to the present disclosure.
[0036] Figure 20 shows an example of a procedure for cell DTX / DRX operation.
[0037] FIG. 21 illustrates an example of a procedure for carrier aggregation (CA) operation using a secondary cell (SCell) without a synchronization signal / physical broadcast channel block (SSB) applicable to the present disclosure.
[0038] FIG. 22 illustrates an example of a Conditional HandOver (CHO) procedure.
[0039] Figure 23 shows an example of a procedure for CSI measurement and reporting.
[0040] Figure 24 shows an example (Scenario 1) of an on-demand SIB1 process.
[0041] Figure 25 shows another example (Scenario 2) of the on-demand SIB1 process.
[0042] Figure 26 shows another example of an on-demand SIB1 process (Scenario 3).
[0043] FIG. 27 illustrates a case where two SSB bursts overlap in the time domain when the center frequencies of AO-SSB and OD-SSB are different.
[0044] FIG. 28 illustrates a case where the center frequencies of AO-SSB and OD-SSB are different, and the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB are the same.
[0045] FIG. 29 illustrates a case where the center frequencies of AO-SSB and OD-SSB are different, the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB are the same, and the SSB bursts overlap / overlap in the time domain.
[0046] Figure 30 shows an example of setting up OD-SSB.
[0047] Figure 31 shows another example of setting OD-SSB.
[0048] FIG. 32 illustrates a terminal operation according to the present disclosure.
[0049] FIG. 33 illustrates a method of operation of a terminal related to OD-SSB reception.
[0050] FIG. 34 illustrates the signaling process and operation of a base station and a terminal related to OD-SSB transmission and reception.
[0051] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."
[0052] A slash ( / ) or a comma used in the present disclosure 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."
[0053] 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 as synonymous with "at least one of A and B."
[0054] Additionally, in the present disclosure, "at least one of A, B and C" may 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" may mean "at least one of A, B and C."
[0055] Additionally, parentheses used in this disclosure may mean "for example." Specifically, when indicated as "control information (ABC)," "ABC" may be described as an example of "control information." For example, "control information" may include DEF as another example. In other words, "control information" of this disclosure is not limited to "ABC," and "ABC" may be described as an example of "control information." Also, when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."
[0056] In addition, in this disclosure, terms such as "first," "second," etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor are they used to limit the order or importance of the components unless specifically limited. Accordingly, a first component in one embodiment of this disclosure may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.
[0057] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.
[0058] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.
[0059] In the present disclosure, a terminal is a user-side device (user equipment, UE) or a consumer-side device, and may also be referred to as a first node that receives / transmits signals from / to a base station / second node / integrated access and backhaul (IAB) node / Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to a user-side endpoint or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a terminal may correspond to a served node. The terminal may be a node with a fixed location, or a node with an unfixed location (or mobile).
[0060] In the present disclosure, a base station (BS) is a device on the network side and may be referred to as a second node / IAB node / x-nodeB (x-NodeB, where x may be an abbreviation related to Radio Access Technology (RAT)) / Transmission-Reception Point (TRP). A base station may correspond to a physical node or a logical node. A base station may correspond to an endpoint on the network side or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a base station may correspond to a serving node. A base station may be a node with a fixed location or a node without a fixed location.
[0061] In the present disclosure, higher layer parameters may be set for the terminal, pre-set, or pre-defined. For example, a base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit a parameter related to capability to the base station as a higher layer parameter. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.
[0062] In the present disclosure, information / state / parameters being "configured or pre-configured" may be interpreted as information / state / parameters being provided or pre-provided to the terminal through pre-defined signaling from the base station (e.g., system information block (SIB), media access control (MAC)-control element (CE), radio resource control (RRC) information element (IE)). In the present disclosure, information / state / parameters being "defined or pre-defined" may be interpreted as being known or stored in advance by the base station and the terminal without signaling between the base station and the terminal.
[0063] The technology described in this 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), SC-FDMA (single carrier frequency division multiple access), etc. 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), 5G NR, etc.
[0064] The technology described in this disclosure can be implemented as 6G wireless technology and applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.
[0065] A. 6G Network Architecture
[0066] FIG. 1 illustrates an example of a flexible network topology applicable to the present disclosure.
[0067] To compensate for incomplete areas of network coverage, a network topology in which the split wireless access network (RAN) is configured more flexibly and resiliently may be considered. To this end, various nodes such as Integrated Access and Backhaul (IAB) nodes, relays, and RF repeaters, as exemplified in Fig. 1, may be applied, and 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 performs simple signal amplification and forwarding functions, and in the case of a network-controlled repeater, it may adjust transmit / receive settings based on information provided by the network as well as signal amplification and forwarding. For example, NTN nodes can correspond to satellites or aircraft that provide NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.
[0068] Referring to Fig. 1, a split RAN can support the division of a base station into one centralized unit (CU) and one or more distributed units (DU). The CU and DU may correspond to logical units. The CU may be further divided into a control plane (CP) portion and one or more user planes (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DU, various intermediate points may be introduced to compensate for this.
[0069] An intermediate point may correspond to a terminal or a base station depending on its relative relationship with other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a DU. The MT can connect the IAB node to a donor node. The DU of the IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to terminals. In other words, an IAB node may correspond to a base station in its relative relationship with user-side nodes and to a terminal in its relative relationship with network-side nodes.
[0070] In some examples of the present disclosure, the description of a terminal may apply equally to an intermediate point corresponding to a terminal in relation to a network-side endpoint as well as to a user-side endpoint. Similarly, in some examples of the present disclosure, the description of a base station may apply equally to an intermediate point corresponding to a base station in relation to a user-side endpoint as well as to a network-side endpoint. However, in most cases where there is no additional description of the operation of three or more entities, the communication entities in the present disclosure are briefly described by the term terminal and / or base station (or first node and / or second node), wherein the term terminal and / or base station (or first node and / or second node) is interpreted to include or replace any endpoint or any intermediate point in relation to other nodes.
[0071] That is, for the sake of brevity of description in some examples of the present disclosure, the subject of the operation may be referred to as a base station and / or terminal (or a first node and / or a second node). Additionally, the term base station and / or terminal (or a first node and / or a second node) may be interpreted or substituted as in the following examples: for example, the base station (or the first node) and the terminal (or the second node) may correspond to a first endpoint and a second endpoint, respectively; may correspond to an endpoint and an intermediate point, respectively; may correspond to an intermediate point and an endpoint, respectively; and may correspond to a first intermediate point and a second intermediate point, respectively.
[0072] In the present disclosure, there may be no intermediate points between a base station and a terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.
[0073] Systems applicable to the present disclosure
[0074] FIG. 2 illustrates an example of the structure of a wireless communication system applicable to the present disclosure. The communication system (100) of FIG. 2 applicable to the present disclosure includes a wireless device, a network device (120), and a network (130). Here, the wireless device refers to a device that performs communication using 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 may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (extended reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI (artificial intelligence) device / server (100g). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle (100b-1, 100b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (100c) 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 (100d) may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance (100e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (100f) may include a sensor, a smart meter, etc.The wireless device 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, and a specific wireless device (120a) may operate as a network device (120) to another wireless device.
[0075] Wireless devices (100a to 100f) can be connected to a network (130) through a network device (120). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (100g) through the network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. The wireless devices (100a to 100f) may communicate with each other through the network device (120) / network (130), but may also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Also, an IoT device (100f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or other wireless devices (100a to 100f).
[0076] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) / network devices (120) and between network devices (120). Here, 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 wireless communication / connection (150a, 150b, 150c), wireless devices and network devices / wireless devices, and network devices and network devices can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various descriptions of the present disclosure, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), a resource allocation process, etc.
[0077] Devices applicable to the present disclosure
[0078] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.
[0079] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals through 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).
[0080] 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 sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a second information / signal through the transceiver (206) and then store information obtained from the 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, memory (204) may store software code containing 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 sequences of operation disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through at least one antenna (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with a radio frequency (RF) unit. In this disclosure, a wireless device may mean a communication modem / circuit / chip.
[0081] Hereinafter, 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., functional layers such as PHY (physical), MAC (media access control), RLC (radio link control), PDCP (packet data convergence protocol), RRC (radio resource control), and SDAP (service data adaptation protocol). At least one processor (202) may generate at least one PDU (Protocol Data Unit) and / or at least one SDU (service data unit) according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to at least one transceiver (206). At least one processor (202) may receive a signal (e.g., baseband signal) from at least one transceiver (206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document.
[0082] At least one processor (202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. 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 at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in at least one processor (202) or stored in at least one memory (204) and driven by at least one processor (202). The descriptions, functions, procedures, proposals, 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.
[0083] At least one memory (204) may be connected to at least one processor (202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. At least one memory (204) may be composed of ROM (read-only memory), RAM (random access memory), EPROM (erasable programmable read-only memory), flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. At least one memory (204) may be located inside and / or outside of at least one processor (202). Additionally, at least one memory (204) may be connected to at least one processor (202) via various technologies, such as wired or wireless connections.
[0084] At least one transceiver (206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this document to at least one other device. At least one transceiver (206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this document from at least one other device. For example, at least one transceiver (206) may be connected to at least one processor (202) and may transmit and receive wireless signals. For example, at least one processor (202) may control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Additionally, at least one processor (202) may 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., as described in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document through 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 the processed user data, control information, wireless signals / channels, etc., from baseband signals to RF band signals using at least one processor (202).To this end, at least one transceiver (206) may include an (analog) oscillator and / or filter.
[0085] The components of the wireless device described with reference to FIG. 3 may be referred to by other terms in terms of their function. For example, the processor (202) may be referred to as the control unit, the transceiver (206) as the communication unit, and the memory (204) as the storage unit. In some cases, the communication unit may be used to mean at least a part of the processor (202) and the transceiver (206).
[0086] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least part of various devices. For example, the structure of the wireless device illustrated in FIG. 3 may be at least part of the various devices described with reference to FIG. 2 (e.g., robot (100a), vehicle (100b-1, 100b-2), XR device (100c), portable device (100d), home appliance (100e), IoT device (100f), AI device / server (100g)). Furthermore, according to various embodiments, the device may include other components in addition to the components illustrated in FIG. 3.
[0087] For example, the device may be a portable device such as a smartphone, smartpad, wearable device (e.g., smart watch, smart glasses), or portable computer (e.g., 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., audio input / output port, video input / output port), and an input / output unit for inputting and outputting video information / signals, audio information / signals, data, and / or information input by a user.
[0088] For example, the device may be a mobile device such as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), or ship. In this case, the device may further include at least one of a drive unit comprising at least one of an engine, motor, power train, wheel, brake, and steering device of the device; a power supply unit that supplies power and includes a wired / wireless charging circuit, battery, etc.; a sensor unit that senses state 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 acquires position information of the moving body through a GPS (global positioning system) and various sensors.
[0089] For example, the device may be an XR device such as an HMD, a HUD (head-up display) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, 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 acquires control information, data, etc. from the outside and outputs a generated XR object, and a sensor unit that senses state information, environment information, and user information of the device or the surroundings of the device.
[0090] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc., 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 state information, environmental information, and user information of the device or its surroundings, and a drive unit that performs various physical actions, such as moving robot joints.
[0091] For example, the device may be an AI device such as a TV, projector, smartphone, PC, laptop, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, 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 state information, environmental information, and user information of the device or its surroundings, and a training unit that learns a model composed of an artificial neural network using training data.
[0092] The structure of the wireless device exemplified in FIG. 3 may be understood as part of a terminal (or first node), or part of an intermediate point, or part of a base station (or second node). If the device exemplified 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 communication. However, if the front haul and / or back haul communication is based on wireless communication, at least one transceiver (206) exemplified in FIG. 3 is used for front haul and / or back haul communication, and the wired transceiver may not be included.
[0093] B. Communication Procedures
[0094] FIG. 4 illustrates an example of a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.
[0095] Referring to FIG. 4, the second node supports dynamic spectrum sharing (DSS) and can provide connectivity to both nodes where 6G technology is implemented and nodes where pre-6G wireless communication technology (e.g., 5G, 4G) is implemented. The first node may have 6G technology implemented or pre-6G wireless communication technology (e.g., 5G, 4G) implemented. Additionally, the first node and / or the second node may support full duplex mode as well as non-overlapping full duplex mode.
[0096] In FIG. 4, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and the operation of the terminal (410) and the base station (420) transmitting and / or receiving data, and the operation performed prior to this, are illustrated. However, the operation of FIG. 4 is not limited to the operation between the terminal and the base station, but can be interpreted as the operation between the first node and the second node. Additionally, FIG. 4 illustrates the operation of direct transmission and reception of wireless signals between the terminal (410) and the base station (420), but there may be one or more intermediate points between the terminal (410) and the base station (420), and wireless signals may be transmitted and received via one or more intermediate points.
[0097] Referring to FIG. 4, in step 401, the terminal (410) and the base station (420) perform synchronization. For example, the terminal (410) performs an initial cell search operation. Specifically, the terminal (410) can detect a synchronization signal for at least one base station connection transmitted from the base station (420) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals classified according to structure or use (e.g., a first synchronization signal (e.g., a primary synchronization signal), a second synchronization signal (e.g., a secondary synchronization signal), etc.). Through this, the terminal (410) can identify the boundary of the unit (e.g., frame, subframe, slot and / or symbol) constituting the wireless signal transmission of the base station (420) and obtain information about the base station (420) (e.g., a cell identifier).
[0098] In step 403, the terminal (410) obtains system information transmitted from the base station (420). The system information is information related to the attributes, characteristics, and / or capabilities of the base station (420) required to connect to the base station (420) and use the service, and can be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., channel used, whether it is provided on-demand), etc., and can be classified, for example, into first system information (e.g., MIB (master information block), primary system information), second system information (e.g., SIB (system information block), secondary system information), etc. If necessary, the terminal (410) may transmit a signal requesting system information prior to receiving the system information. However, the request and provision of system information may be performed after the random access procedure described later.
[0099] In step 405, the terminal (410) and the base station (420) perform a random access procedure. The terminal (410) may transmit and / or receive at least one message for a random access procedure (e.g., a random access preamble, a RAR (random access response) message, etc.) based on information related to the channel for the random access procedure of the base station (420) obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal (410) may transmit a first message (e.g., a preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., a RAR message, MSG2), transmit a third message (e.g., MSG3) containing information related to the terminal (410) (e.g., identification information) using scheduling information included in the second message, and receive a fourth message (e.g., MSG4) for contention resolution and / or connection establishment. As another example, the first message and the third message can be transmitted and received as a single message, or the second message and the fourth message can be transmitted and received as a single message.
[0100] In step 407, the terminal (410) and the base station (420) perform signaling of control information. Here, the control information may be defined in various layers, such as a layer that controls the 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 (410) and the base station (420) may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.
[0101] In step 409, the terminal (410) and the base station (420) transmit and / or receive data. That is, the terminal (410) and the base station (420) can process, transmit and / or receive data based on the signaling of control information. For example, when transmitting data, the terminal (410) or the base station (420) may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (410) or the base station (420) may perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.
[0102] C. 6G System Core Technology
[0103] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, FSO backhaul network, massive MIMO 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.
[0104] C-1. Artificial Intelligence
[0105] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). 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.
[0106] [Functional Framework]
[0107] The following describes a functional framework for AI / ML (Artificial Intelligence / Machine Learning) operations.
[0108] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.
[0109] Data collection: Collecting data from network nodes, management entities, or terminals, etc., as a basis for AI model training, data analysis, and inference.
[0110] 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.
[0111] AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and obtain an AI / ML model trained for inference.
[0112] AI / ML Inference: A process of making predictions or deriving decisions based on collected data and AI models using trained AI models.
[0113] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updating, etc.) can be classified into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identifiable within the network, and the network can direct the activation, deactivation, fallback, or switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified within the network, and the network or terminal can activate, deactivate, select, or switch AI / ML models via the model ID.
[0114] Figure 5 illustrates an example of a general functional architecture related to both function-based LCM and model-based LCM. Some functions or some data / information / command flows (i.e., arrows) exemplified in Figure 5 may be omitted.
[0115] Referring to FIG. 5, a general functional framework may be configured to include a data collection function (510), a model training function (520), a management function (530), an inference function (540), and a model storage function (550).
[0116] The data collection function (510) is a function that provides input data to the model training function (520), management function (530), and inference function (540). The data collection function (510) performs data preparation based on raw data and can provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The data collection function (510) may be performed by a single entity (e.g., terminal, network node, etc.) but may also be performed by multiple entities.
[0117] Here, training data (501) refers to data required as input for the AI / ML model training function (520). monitoring data (503) refers to data required as input for the management (530) of the AI / ML model or AI / ML function. inference data (505) refers to data required as input for the AI / ML inference function (540).
[0118] The model training function (520) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of an AI / ML model testing procedure. If necessary, the model training function (520) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on training data (501) delivered from the data collection function (510).
[0119] Trained / Updated Model (513): If there is a model storage function (550), it is used to transfer the trained, validated, and tested AI / ML model to the model storage function (550) or to transfer an updated version of the model to the model storage function (550).
[0120] The management function (530) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the management function (530) may make decisions to ensure appropriate inference behavior based on data received from the data collection function (510) (i.e., Monitoring Data (503)) and / or data received from the inference function (540) (i.e., Inference Output (509)).
[0121] Management Instruction (511) is information required as input to manage the inference function (540). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).
[0122] A Model Transfer / Delivery Request (515) can be used to request model(s) from the Model Store (550).
[0123] A Performance Feedback / Retraining Request (507) refers to information required as input to a model training function (520) (e.g., for the purpose of retraining or updating the model).
[0124] The inference function (540) is a function that provides an output from the process of applying an AI / ML model or an AI / ML function using the data provided by the data collection (510) (i.e., inference data (505)) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (505) delivered by the data collection (510). If necessary, the inference function (540) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (505) provided by the data collection function (510).
[0125] Inference Output (509) is data used by the management function (530) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (509) may include the inference output of an AI / ML model generated by the inference function (540), and the details of the inference output may vary depending on the use case.
[0126] The model storage function (550) is a function that stores a trained / updated model that can be used to perform an inference function (540). The model storage function (550) exemplified in FIG. 5 can be used as a reference point (if any) applicable to protocol termination, model transmission / delivery, and related processes. Additionally, the model storage function (550) is an example and is not intended to restrict the storage location of the actual AI / ML model and may be omitted.
[0127] Model Transfer / Delivery (517) is used to transfer an AI / ML model to an inference function.
[0128] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of multiple levels or the separation of any one level are also possible.
[0129] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.
[0130] Cat 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.
[0131] Cat 1) Inter-node support is involved to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from other nodes (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.
[0132] Cat 2) Collaborative AI / ML tasks can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.
[0133] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and all functions and / or all data / information / command signals illustrated in FIG. 5 may not be performed within a specific node, and only some may be performed.
[0134] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.
[0135] A one-side model can refer to an AI / ML model where inference is performed entirely by a single node (e.g., a terminal or a network). Here, the training of the AI / ML model can also be performed entirely by a single node. The training and inference of the AI / ML model may be performed by the same node, or they may be performed by different nodes.
[0136] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference means that inference is performed collaboratively across multiple nodes; for example, the first part of the inference may be performed by the first node, and the remainder by the second node. Two-side models can be classified into various types as follows, depending on the training method of the AI / ML model.
[0137] First type: An AI / ML model can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / entities.
[0138] Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation) and model reconstruction (CSI compression by sub-use cases) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).
[0139] Third type: Separate training of AI / ML models can be performed at multiple nodes (e.g., networks and terminals). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node performs the AI / ML model first and shares the training data with the second node, the second node can perform the AI / ML model using the shared training data. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.
[0140] The operations described in the present disclosure below may be explained / interpreted based on an AI / ML model as shown in FIG. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for an AI / ML model). FIG. 6 illustrates an example of an operation procedure based on an AI / ML model applicable to the present disclosure.
[0141] Additionally, unless specifically limited in the description of the present disclosure, an AI / ML model may correspond to a one-side model in which inference is performed entirely by a single node or a two-side model in which joint inference is performed by multiple nodes.
[0142] Step 1: In the description of the present disclosure below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or a set of signaling of Step 1 used to perform an operation based on an AI / ML model, unless otherwise noted. For example, it may correspond to training data for training (i.e., generation and / or reconstruction) the AI / ML model of FIG. 5, or to inference data used for inference of the AI / ML model, or to feedback to the AI / ML model, etc. If signaling between nodes is not required prior to an operation based on an AI / ML model in the present disclosure, Step 1 may be omitted. If a one-side model is used in the present disclosure, unidirectional / bidirectional signaling (set) in the present disclosure may correspond to the signaling of Step 1. In addition, when a two-side model is used in the present disclosure, unidirectional / bidirectional signaling in the present disclosure may correspond to one stage of signaling, and repetitive signaling operations may also correspond to one stage of signaling.
[0143] For example, in AI / ML model-based beam management, when a base station predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from the terminal. Additionally, when a terminal predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the terminal can receive multiple beams from the base station.
[0144] Step 2: In the description of the present disclosure below, operations (e.g., computation, selection, prediction, etc.) at a specific node (e.g., terminal, network, etc.) or joint operations (e.g., computation, selection, prediction, etc.) at multiple nodes (e.g., terminal, network, etc.) may correspond to operations of Step 2 based on one or more functions in the functional framework of an AI / ML model, unless otherwise noted. For example, they may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5 or to inference of the AI / ML model. When a one-side model is used, operations performed by a single node in the present disclosure may correspond to operations of Step 2, and when a two-side model is used, joint operations performed by multiple nodes in the present disclosure may correspond to operations of Step 2.
[0145] For example, in an AI / ML model-based BM, a base station can predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using quality / intensity information for multiple beams received from a terminal as inference data. Additionally, a terminal can measure multiple beams received from a base station and predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using the measurement results as inference data.
[0146] Step 3: In the description of the present disclosure below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or set of signaling of Step 3 generated as a result of an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to the output resulting from the inference of the AI / ML model of FIG. 5. If signaling between nodes is not required as a result of an operation based on an AI / ML model in the present disclosure, Step 3 may be omitted. If a one-side model is used in the present disclosure, unidirectional / bidirectional signaling (set) in the present disclosure may correspond to the signaling of Step 3. Furthermore, if a two-side model is used in the present disclosure, unidirectional / bidirectional signaling in the present disclosure may correspond to the signaling of Step 3, and repetitive signaling operations may also correspond to the signaling of Step 3.
[0147] For example, in an AI / ML model-based BM, the base station may transmit beam(s) predicted based on the AI / ML model as candidates to the terminal so that the terminal can determine the optimal beam. Additionally, the terminal may report the beam(s) predicted based on the AI / ML model to the base station to request the base station to transmit candidate beams as candidates for determining the optimal beam.
[0148] C-2. THz communication
[0149] Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz–300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz–3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz–3 THz band is part of the broadband, it lies at the boundary of the broadband and immediately following the RF band. Therefore, this 300 GHz–3 THz band exhibits similarities to RF.
[0150] FIG. 7 illustrates an example of an electromagnetic spectrum applicable to the present disclosure. The embodiment of FIG. 7 can be combined with various embodiments. Key characteristics of THz communication include (i) a widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array techniques that can overcome range limitations.
[0151] Transmitting system information (i.e., information related to the attributes, characteristics, and / or capabilities of the BS required to use the service, etc.) (e.g., MIB, SIB, etc.) in the THz frequency band can be inefficient because, in the case of high frequency bands, beam sweeping must be performed more frequently to cover the entire area of the cell as the beam width becomes narrow. In particular, transmitting system information in this manner is even more inefficient when there are not many users in the cell. Accordingly, a system information transmission procedure as shown in FIG. 8 below may be used.
[0152] (Method for receiving system information)
[0153] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication applicable to the present disclosure. Although this example is written with THz conditions in mind, it is also applicable to 6G communication environments where THz is not applied. Furthermore, the procedure exemplified in FIG. 8 can be combined with various embodiments of the present disclosure described below. For example, embodiments described below may be performed based on system information obtained by the procedure exemplified in FIG. 8.
[0154] Referring to FIG. 8, in step 801, the base station (820) transmits system information of cell #1 through cell #2. That is, the base station (820) 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 information / state / parameter / setting generated at the higher layer and the physical layer, respectively. For example, at least one information / state / parameter / setting generated at the higher layer may include at least one of an SFN, a control information setting for SIB1 (e.g., PDCCH configuration for SIB1, etc.), information related to cell selection / entry (e.g., cell barring, cell re-selection, etc.), and a subcarrier spacing (SCS), and at least one information / state / parameter / setting generated at the physical layer may include at least one of an SFN (system frame number), a half frame indicator, and an SSB index. However, this is merely an example, and system information may include information, status, parameters, and settings related to Cell #1 / Cell #2 generated at various types of physical layers / upper layers. To this end, as an example, Cell #1 and Cell #2 may have a secondary cell and primary cell relationship.
[0155] In step 803, the UE (810) obtains synchronization for cell #1. Synchronization can be obtained by detecting a synchronization signal. Generally, synchronization is obtained prior to receiving system information, but since the system information for cell #1 is received in cell #2, synchronization for cell #1 can be obtained after receiving system information. For example, the UE (810) can obtain synchronization based on system information. However, unlike FIG. 8, synchronization may be obtained prior to step 801 according to other examples.
[0156] In step 805, the UE (810) transmits a signal to connect to Cell #1. For example, the signal may include information for connecting to Cell #1 (e.g., a random access preamble). The structure of the signal and the resource for transmitting the signal (e.g., a channel) can be identified through system information. Subsequently, in step 807, the UE (810) and the base station (820) perform a connection procedure to Cell #1 and perform communication. In this step, operations according to various embodiments described below may be performed.
[0157] The procedure described with reference to FIG. 8 may be performed when the UE (801) first connects to cell #1 of the base station (820). Alternatively, a similar procedure may be performed when the UE (801) handovers to cell #1 of the base station (820). However, in the case of a handover, the system information of cell #1 may be received from a cell of a different base station other than cell #2 of the base station (520).
[0158] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations must use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control along with beamforming, and the number of beams used becomes very large. Therefore, it takes a very long time to align the transmit and receive beams between the base station and the terminal. In addition, if the beam alignment between the base station and the terminal is misaligned due to the movement of the terminal, time is frequently required to realign the beams, which may result in an unstable link. Accordingly, a beam management procedure as shown in Fig. 9 below may be used.
[0159] (Beam search procedure in a THz communication environment)
[0160] FIG. 9 illustrates an example of a beam management procedure applicable to the present disclosure. FIG. 9 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but is not limited to a THz environment and is applicable to a 6G communication environment. Additionally, the procedure exemplified in FIG. 9 may be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (configuration) information', 'spatial domain filter', 'spatial domain transmission filter', 'spatial domain reception filter', or / and a term having an equivalent technical meaning capable of distinguishing a beam (e.g., Reference signal, SSB (Synchronization Signal Block) Index, TRP (transmission reception point), panel, cell, TP (transmission point), base station, control resource-related information (e.g., CORESET (control resource set)-related information, etc.).
[0161] Referring to FIG. 9, in step 901, the base station (920) configures resources for beam management. Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station (920) may utilize a beam search signal (BSS) that is spatially separated from the existing downlink signal / channel and transmitted for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a port different from the port for transmitting the existing downlink signal / channel (e.g., synchronization signal (e.g., SSB, etc.), data channel (e.g., PDSCH, 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. That is, a signal transmitted based on a dedicated port defined / configured for beam search may be included in the technical concept according to the present embodiment.
[0162] In step 903, the base station (920) transmits measurement signals using multiple 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 requiring measurement, and may be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).
[0163] In step 905, the UE (910) transmits a feedback signal to the base station (920). The feedback signal indicates at least one beam selected by the UE (910). The UE (910) can select at least one preferred beam based on the measurement signals received in step 903.
[0164] In step 907, the UE (910) and the base station (920) communicate. At this time, the UE (910) and the base station (920) may communicate using the beam selected in step 905. If channel reciprocity is established, the transmission beam of the UE (910) can also be determined through steps 903 and 905, so the transmission operation of the UE (910) can also be performed using the beam selected in step 905. If channel reciprocity is not established, a procedure including the transmission of measurement signals by the UE (910) and the transmission of feedback signals by the base station (920) may be performed first to determine the transmission beam of the UE (910). In step 907, operations according to various embodiments described later may be performed.
[0165] C-3. Non-terrestrial networks (NTN)
[0166] NTN may represent a network or network segment utilizing RF (radio frequency) resources mounted on a satellite (or UAS (unmanned aerial system) platform). The use of NTN services has been considered to secure wider coverage or to provide wireless communication services in locations where the installation of wireless communication base stations is difficult. NTN services may collectively refer to wireless communication systems that provide services to terminals by installing base stations on satellites rather than on the ground (e.g., geostationary-orbit, low-Earth orbit, medium-geometry orbit satellites, etc.), airplanes, unmanned airships, drones, etc. The satellite described in this disclosure can move at high speed from a specific location on Earth, and the satellite beam directed toward Earth may correspond to an area on Earth where the satellite can provide services to users.
[0167] As an example of the present disclosure, NTN scenarios may be classified into Earth-fixed cell scenarios and Earth-moving cell scenarios depending on the type of cell supported by the satellite. An Earth-fixed cell scenario refers to a scenario in which a cell is maintained permanently within a specific position on the Earth's surface or for a specific service period based on the satellite's beam steering function. An Earth-moving cell scenario refers to a scenario in which a cell within the Earth's surface continues to move as it is serviced by a fixed beam without the satellite's beam steering function being utilized.
[0168] As another example of the present disclosure, NTN scenarios can be classified into a typical scenario based on a transparent payload and a typical scenario based on a regenerative payload, depending on the characteristics of the payload.
[0169] FIG. 10 illustrates an example of a general NTN scenario based on a transparent payload applicable to the present disclosure.
[0170] Referring to Fig. 10, the satellite (or UAS platform) can establish a service link with the UE. The satellite (or UAS platform) can be connected to a (NTN) gateway via a feeder link. The satellite can be connected to a data network via the gateway. The beam footprint may refer to the area where signals transmitted by the satellite can be received.
[0171] FIG. 11 illustrates an example of a general NTN scenario based on a regenerated payload applicable to the present disclosure.
[0172] Referring to Fig. 11, a satellite (or UAS platform) can establish a service link with a UE. A satellite (or UAS platform) connected to a UE can be connected to another satellite (or UAS platform) via inter-satellite links (ISL). Another satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on a replay payload, the satellite can be connected to a data network via another satellite and a gateway. If no ISL exists between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.
[0173] The embodiment of FIG. 10 or FIG. 11 may be combined with various embodiments of the present disclosure.
[0174] FIGS. 10 and 11 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 regenerative (with on-board 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) may vary depending on the on-board antenna diagram and the minimum elevation angle. For example, a regenerative payload may include radio frequency filtering, frequency conversion, and amplification. Thus, the waveform signal repeated by the payload may not be altered. 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, the playback payload can be substantially the same as carrying all or part of the base station functions on a satellite (or UAS platform).
[0175] The following describes procedures for maintaining network service continuity and satellite coverage in wireless communication systems utilizing NTN elements (e.g., initial cell selection, mobility management in idle mode, and mobility management in connected mode).
[0176] - Initial cell selection procedure
[0177] The terminal can search for the first satellite-based NTN cell (or the satellite broadcasting the cell) upon power turn-on. At this time, if the terminal possesses satellite orbit information (i.e., ephemeris data) and / or round-to-trip (RTT) information available for performing a cell entry procedure (e.g., random access procedure), the terminal can use such information to shorten the time required for the cell search procedure and cell search. To this end, the terminal may require (initial) system information containing satellite ephemeris data to identify the precise location of the cell, and (initial) system information may be established / determined / generated based on orbital plane information already possessed by the terminal. For example, satellite-level orbit parameters for all satellites capable of providing services to the terminal via a terminal uSIM (Universal Subscriber Identity Module) containing a satellite ID (identity / identifier) or index may be provided in advance. Subsequently, since the satellite ID of the service satellite is included in the system information and broadcast, the terminal can use this to derive the orbital data (ephemeris data) and / or the location coordinates of the service satellite associated with the service satellite stored in the uSIM. Additionally, to assist with mobility handling, the terminal can obtain information related to neighboring satellites through the system information and / or dedicated RRC signaling.
[0178] Here, satellite ephemeris information transmitted to the terminal via system information and / or RRC signaling may be implemented / supported in i) position and velocity state vector orbital format and ii) orbital parameter ephemeris format. For example, the position and velocity state vector orbital format may consist of 17 bytes or less (e.g., 132 bits). The field size for position (x, y, z)(m) may be 78 bits, and the field size for velocity (vx, vy, vz)(m / s) may be 54 bits.
[0179] The orbital parameter ephemeris format can be composed of 21 bytes or less (e.g., 164 bits).
[0180] FIG. 12 illustrates examples of the components of an orbital parameter ephemeris format. The components of the orbital parameter ephemeris format illustrated in FIG. 12 are as follows.
[0181] Semi-major axis (half of the major axis of an elliptical satellite orbit) "α" [m] (e.g., 33 bits).
[0182] Eccentricity "e" (in an elliptical satellite orbit, 0 <e<1)(예: 20 비트).
[0183] Periapsis (argument of periapsis) (refers to the angle from the orbital periapsis, the point where an object is closest to the center body as it orbits, to the ascending node, and determines the direction of the ellipse in the orbital plane) " ω (e.g., 28 bits)[rad].
[0184] Longitude of ascending node (angle measured counterclockwise from a reference point (e.g., the reference point in the solar system is the vernal equinox)) "Ω" (e.g., 28 bits)[rad].
[0185] (Orbit) Inclination (refers to the degree of tilt of an ellipse relative to a reference plane, measured as the angle between the orbit plane and the reference plane at the ascending node) "i" (e.g., 27 bits)[rad].
[0186] Mean anomaly (an angle that changes continuously over time; mathematically convenient but does not correspond to a geometric angle) "M0" = M(t0) at epoch t0 [JD] (e.g., 28 bits) [rad].
[0187] Mobility management in idle mode.
[0188] During idle mode, the location of the terminal can be identified at the tracking area level / unit. Here, a tracking area is defined as a set of cells, and each cell may belong to a tracking area identified by a tracking area code (TAC). The TAC may be transmitted via system information on a broadcast channel. Multiple cells may belong to the same tracking area, and the same TAC corresponding to that same tracking area may be broadcast. The location of the terminal may be known to the network when the terminal's power is first turned on (i.e., when the registration procedure is performed). The registration request message transmitted by the terminal for the registration procedure may include the TAC of the cell the terminal is currently camped in. If the terminal changes cells as it moves, the tracking area of that cell can be determined by decoding the system information of the changed cell. The terminal may move within the same tracking area without performing updates. When a terminal enters a new cell using a different TAC, the terminal can register in the new cell and transmit a new TAC to update the network regarding its location. Accordingly, as the tracking area becomes larger, signaling from the terminal to the network is reduced, which can minimize terminal power consumption. If the network needs to reach a terminal in idle mode (e.g., incoming call), the network can page the terminal from all cells within the last tracking area where the terminal registered. If the tracking area is very large and contains many cells, the number of pages may increase because the network pages the terminal from all cells within the TAC. If the same model is used in the satellite system and each satellite broadcasts the TAC, the tracking area can sweep across the ground as the satellite orbits the Earth.In this case, even a stationary terminal must frequently perform registration updates, which may affect the terminal's battery life and increase uplink signal. To address this, the system can be designed so that the tracking area does not change its geographical location on Earth. Instead of the tracking area shifting when the satellite moves, the satellite changes the tracking area as it enters a new geographical area, and the TAC broadcast by the satellite can be updated to reflect the corresponding new geographical area. Simultaneously, if the terminal detects a new TAC on the broadcast channel, it can perform a tracking area update procedure. Accordingly, the tracking area of the terminal can remain fixed unless its physical location on Earth changes.
[0189] Mobility management in connected mode.
[0190] While the terminal is in Connected Mode, mobility management procedures may be handled by handover. For terrestrial / NTN networks, a handover may be triggered by the network based on measurements reported by the terminal regarding the signal quality of the current cell and adjacent cells (i.e., measurement handover triggering). Within the handover procedure, the downtime is defined as the time from when the terminal stops transmitting and receiving with the source base station until when it resumes transmitting and receiving with the target base station. Meanwhile, the downtime may differ for the uplink and downlink. For the downlink, the downtime can be defined as the time from when the network transmits a synchronized RRC reset message until the target base station receives a Reconfiguration Complete message. The base station cannot send data after the time it transmits the RRC reset message and can resume communication after receiving the Reconfiguration Complete message. For the uplink, the terminal may potentially continue transmitting data to the source base station until the synchronized RRC reset message is received. In addition, the interruption time can be defined as the time from when the terminal receives a synchronized RRC reset message until the target base station receives an RRC reset completion message.
[0191] Since the propagation delay of satellite-based NTN is much greater than that of ground systems, additional latency may occur for mobility signals such as measurement reporting, reception of HO (handover) commands, and HO requests / ACKs (if the target cell originates from a different satellite). Geostationary Earth Orbit (GEO) scenarios are characterized by much greater propagation delay than low Earth Orbiting (LEO) scenarios, although the latter must account for satellite movement. To prevent extended service interruptions, latency associated with mobility signals must be addressed in both cases. In addition to the measurement-triggered handover described above, handover triggering based on the location of the terminal and satellite (or the distance between the terminal and the satellite), handover triggering based on the timing advance (TA) of the target cell, handover triggering based on deterministic satellite movement / local time, and handover triggering based on the elevation angle of the source / target cell may be utilized. Additionally or alternatively, the terminal may be provided in advance with handover settings and conditions that trigger the handover (e.g., location of the terminal / satellite, signal strength transmitted by the terminal / satellite, etc.). For example, the terminal may receive handover settings and conditions that trigger the handover through information regarding the new cell that serves as the handover target. Accordingly, the terminal can monitor the handover conditions and, if the conditions are satisfied, perform a handover to the target cell.
[0192] Meanwhile, as mentioned above, since wireless communication systems utilizing NTN elements have very large RTT values compared to terrestrial communication systems, various types of offsets and TA values can be set, defined, indicated, or signaled for efficient time / frequency synchronization. Below, offsets (e.g., K_offset and k_mac), TA values, validity duration, and epoch time for time / frequency synchronization in NTN-based wireless communication systems are described.
[0193] K_offset and k_mac.
[0194] Figure 13 illustrates examples of offsets in links related to satellites.
[0195] K_offset shown in FIG. 13 is an offset value representing the RTT of the uplink time synchronization reference point (RP). Here, K_offset may correspond to the sum of the service link RTT and the common TA (if indicated). k_mac shown in FIG. 13 is an offset value representing the RTT between the RP and the base station. For example, K_offset may be applied to i) DCI and PUSCH transmission timing scheduled by the DCI, ii) random access response (RAR) and PUSCH transmission timing based on the RAR, iii) PUSCH transmission timing based on a set grant, iv) PUCCH transmission timing according to MsgB, v) non-periodic SRS / CSI resource transmission timing, etc. For example, k_mac may be applied to terminal actions and assumptions regarding downlink configuration indicated by the MAC-CE command in PDSCH. In the beam failure recovery procedure, for the transmission of PRACH in uplink slot n, the terminal can monitor the corresponding PDCCH starting from downlink slot "n+k_mac+4" within the corresponding RAR window.
[0196] The cell-specific K_offset can be signaled via system information associated with the NTN (e.g., NTN-specific SIB). A value range for the cell-specific K_offset (0 to 1023 ms) covering all scenarios may be used. The differential terminal-specific K_offset can be signaled via MAC CE, and the corresponding differential terminal-specific value range is 0 to 63 ms. The total terminal-specific K_offset value is equal to the cell-specific K_offset value minus the differential terminal-specific K_offset value. k_mac can be provided from the network when downlink and uplink frame timings are not aligned at the base station. Updates to k_mac are not supported, and the value range may be 1 to 512 ms. If the terminal does not receive the k_mac value from the network, the terminal may assume k_mac to 0. The reference SCS value for the unit of K_offset in FR1 can be 15 kHz.
[0197] UE-specific TA and common TA.
[0198] In an NTN-based communication system, a terminal can calculate Timing Advance (TA) based on the terminal's GNSS (global navigation satellite system) capability (e.g., terminal location) and higher-layer parameters related to satellite orbits (ephemeris) transmitted from the base station, and this is the terminal-specific TA (N UE TA,adjIt is named as ). If upper-layer parameters related to satellite orbit are not received from the base station, the terminal-specific TA may be set to 0. Then, the TA calculated based on common TA parameters (e.g., TACommon, TACommonDrift, and / or TACommonDriftVariation), which are upper-layer parameters transmitted from the base station, is the common TA(N common TA,adj It is named as ). If common TA parameters are not transmitted from the base station, the common TA can be set to 0. Accordingly, in an NTN-based communication system, the total TA value (T_TA) is N_TA + N_TA,offset + N common TA,adj + N UE TA,adj It can be calculated as follows. N_TA,offset refers to the TA offset value provided to the terminal per serving cell, and N_TA refers to the value derived based on the timing advance command.
[0199] Figure 14 illustrates examples of TA (timing advanced) values in a link related to a satellite.
[0200] As shown in FIG. 14, terminal-specific TA is calculated to compensate for transmission delays for the service link, and common TA is calculated to compensate for transmission delays between the RP and the satellite.
[0201] Valid interval and epoch time.
[0202] The valid period refers to the (maximum) time interval during which the terminal can apply previously acquired support information (from the epoch time) without acquiring new support information (e.g., serving and / or neighboring satellite orbits (ephemeris) and common TA parameters, etc.). Configuration information related to the valid period may be broadcast from the base station via NTN-related system information (e.g., SIB19) per cell. For example, the valid period length range may be configured as {5s, 10s, 15s, 20s, 25s, 30s, 35s, 40s, 45s, 50s, 55s, 60s, 120s, 180s, 240s, 900s}, but is not limited thereto. Here, s means seconds. A valid timer with a valid period value set may (re)start at the epoch time of the support information. If new or additional support information is not available within the applicable validity period, the terminal may assume that uplink synchronization has been lost.
[0203] Serving satellite ephemeris and common TA parameters are signaled in the same System Information Block (SIB) message and may have the same epoch time. If the epoch time is explicitly provided via the SIB, the epoch time of the support information (i.e., satellite ephemeris and common TA parameters) is the start time of the downlink (DL) subframe, indicated by the System Frame Number (SFN), and the subframe number signaled along with the support information. If the epoch time is not explicitly indicated via the SIB, the epoch time of the support information may be implicitly known as the end of the SI window in which NTN-specific system information (e.g., SIB19) is transmitted. If the epoch time is provided via dedicated signaling, the epoch time of the support information is the start time of the DL subframe and may be indicated by the SFN and the subframe number.
[0204] In the case of a serving cell, if the epoch time is explicitly indicated by the SFN and subframe number, the terminal may consider the frame as the next SFN after the frame in which the message indicating the epoch time was received. In the case of a neighboring cell, if the epoch time is explicitly indicated by the SFN and subframe number, the terminal may consider the frame as the frame closest to the frame in which the message indicating the epoch time was received.
[0205] C-4. Integrated Sensing and Communication (ISAC)
[0206] Wireless sensing is a technology that utilizes radio frequencies to determine the instantaneous linear velocity, angle, and distance (range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within that environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, 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 various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable 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 may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, that is, the sensing operation, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks into wireless communication and sensing networks.
[0207] FIGS. 15 and 16 illustrate examples of sensing operations applicable to the present disclosure. The embodiments of FIGS. 15 and 16 may be combined with various embodiments of the present disclosure. Specifically, FIG. 15 illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same position (e.g., monostatic sensing), and FIG. 16 illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).
[0208] For example, in a wireless communication system based on a 6G network of the present disclosure, referring to FIG. 15, the sensing transmitter and the sensing receiver may be configured to be included in a single base station (i.e., the same base station) or a single terminal (i.e., the same terminal). Alternatively, referring to FIG. 16, the sensing transmitter and the sensing receiver may be configured to be included in different base stations, in different terminals, or in a terminal and a base station, respectively.
[0209] In this regard, based on whether the sensing transmitter and the sensing receiver are each included in a base station or a terminal, the following six types of sensing modes can be defined.
[0210] First mode: A mode in which the sensing transmitter and the sensing receiver are contained in a single base station (e.g., base station-based sensing mode in monostatic mode).
[0211] Second mode: A mode in which the sensing transmitter is included in the first base station and the sensing receiver is included in a second base station different from the first base station (e.g., base station-based sensing mode in bistatic mode).
[0212] Third mode: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode).
[0213] 4th mode: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode).
[0214] Fifth mode: A mode in which the sensing transmitter and the sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode).
[0215] 6th mode: A mode in which the sensing transmitter is included in the first terminal and the sensing receiver is included in the second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode).
[0216] In a wireless communication system based on a 6G network of the present disclosure, one or more of the six types of sensing modes described above may be utilized independently or in combination.
[0217] In relation to the sensing operation in FIGS. 15 and 16, a sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or the environment surrounding the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on the 6G network of the present disclosure. A sensing receiver may receive a signal that is scattered / reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signal, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). The sensing result thus generated / acquired may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided by a wireless communication system based on the 6G network of the present disclosure, or may be provided / disclosed to a trusted third party.
[0218] Additionally, the sensing operation in FIGS. 15 and 16 is described using a wireless communication system based on a 6G network as a representative example, but it can be extended and applied to cases where terminals / base stations / signals based on previous generations (e.g., 4G, 5G, etc.) networks are utilized.
[0219] Additionally, in relation to the wireless sensing described in the present disclosure, in a wireless communication system based on a 6G network of the present disclosure, time / frequency resources for sensing operations and time / frequency resources for general communication (e.g., UL / DL / sidelink-based communication, etc.) may be scheduled / configured separately.
[0220] FIG. 17 illustrates an example of a time / frequency resource for a sensing operation applicable to the present disclosure. The embodiment of FIG. 17 can be combined with various embodiments of the present disclosure.
[0221] Referring to FIG. 17, the time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 15 and FIG. 16) can be set / assigned separately from the time / frequency resources (hereinafter, communication resources) for general communication.
[0222] For example, as illustrated in FIG. 17, sensing resources may be configured / assigned in units of symbols in the time domain and / or in units of resource blocks in the frequency domain. Resources other than those configured / assigned to the sensing resources may be utilized as resources for general communication. That is, sensing resources and communication resources may be configured / assigned based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) methods in terms of base station / terminal operation. Additionally, or alternatively, unlike that illustrated in FIG. 17, sensing resources may be configured / assigned based on other units in the time domain (e.g., slot, frame, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarrier, carrier, absolute frequency (MHz, GHz), etc.).
[0223] Additionally or alternatively, in relation to the configuration / allocation / scheduling of resources for general communication described in this disclosure, it may be necessary to consider the relationship between said resources and the aforementioned sensing resources. For example, when configuring / allocating resources for general communication according to the embodiments of this disclosure, said resources may be configured / allocated to rate-match or puncturing resource areas corresponding to the sensing resources. For example, when scheduling resources for general communication according to the embodiments of this disclosure, said resources may be scheduled so as not to overlap with resource areas corresponding to the sensing resources. If resources for general communication and resource areas corresponding to the sensing resources are configured / allocated / scheduled to overlap according to the embodiments of this disclosure, either one or both operations may be dropped, skipped, or postponed based on priority, predefined rules, etc. That is, in the embodiments of the present disclosure, resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) may be configured / assigned / scheduled so as not to overlap with the aforementioned sensing resources.
[0224] Additionally, various channel modeling methods may be applied in relation to the wireless sensing described in this disclosure. Channel modeling related to sensing may mean constructing a path for transmitting and receiving sensing signals and / or scattered / reflected signals by considering the object to be sensed and / or the environment to which the object belongs. Since channel modeling may be related to the performance / requirements of sensing in a wireless communication system, it may be an important matter for verifying the validity of the sensing function.
[0225] Channels related to sensing can be classified into channels between an object (e.g., target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and a sensing transmitter / receiver. In this regard, channel modeling related to sensing can be classified based on the sensing mode (e.g., the six types of modes mentioned above), whether it is an object or an environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for an environment in a base station / terminal-based monostatic sensing mode, and channel modeling for an environment in a base station / terminal-based bistatic sensing mode can be configured with different optimizations. For example, when various sensing scenarios are classified, they can be divided into channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of the present disclosure may be based on stochastic geometry channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometry channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In the case of a hybrid approach, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.
[0226] FIG. 18 illustrates an example of a procedure related to a sensing operation applicable to the present disclosure. An embodiment of FIG. 18 may be combined with various embodiments of the present disclosure.
[0227] For example, in a wireless communication system based on a 6G network of the present disclosure, in the case of a sensing operation in which a terminal participates, the base station may need to verify the terminal's capability for said sensing operation. In this regard, the terminal may be configured to report capability information regarding whether it supports the sensing operation to the base station. Additionally, or alternatively, if the terminal is defined in advance in the specification as supporting the sensing operation, such procedure may be omitted. Furthermore, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information regarding whether it supports the sensing operation to an entity that sets / controls its sensing operation (e.g., a network entity at the upper layer / level of the base station).
[0228] For example, a base station may perform signaling with a terminal to exchange configuration information related to a sensing operation. For example, the base station may set / instruct the terminal information regarding the mode of the sensing operation (e.g., based on the six types of modes mentioned above), the subject of the sensing operation (e.g., a sensing transmitter, a sensing receiver), the resource for the sensing operation (e.g., a sensing resource as shown in FIG. 17), the target for utilizing the sensing result (e.g., a type of wireless sensing service based on a 6G network, a trusted third party), and channel modeling for sensing (e.g., a channel between the base station / terminal and an object / environment). For example, the base station may receive such information from a network entity at a higher level / layer of the base station.
[0229] For example, a base station and / or terminal may perform a sensing operation on information that has been set or instructed. For example, the base station and / or terminal may perform procedures such as transmitting a sensing signal as described in FIGS. 15 and 16, receiving scattered / reflected signals, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, in the role of a sensing transmitter and / or sensing receiver. As an example, in the operation of the base station / terminal described in this disclosure, the sensing result provided through the sensing operation may be utilized.
[0230] D. NES (network energy saving)
[0231] Energy conservation in base stations is considered a critical factor in wireless communication systems, including 3GPP, as it contributes to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditures (OPEX) of telecommunications operators. In particular, as the introduction of 5G communication demands high transmission rates, base stations must be equipped with a greater number of antennas and provide services across wider bandwidths and frequency bands. Consequently, recent studies indicate that energy costs for base stations have reached 20% of total OPEX. Accordingly, 5G systems are adopting various technologies to reduce energy consumption under the name of Network Energy Savings (NES), and the standardization of related technologies is expected to continue. Specifically, the recent Rel-18 session discussed the following techniques.
[0232] 1. Where deemed feasible in the RAN4 study, SCell operation without SSB for interband CA for FR1 and same-location cells is specified, wherein the UE measures SSB transmitted from a PCell or another SCell for SCell time / frequency synchronization (including downlink AGC) and L1 / L3 measurements, and includes potential enhancements to the SCell activation procedure if necessary.
[0233] 2. Specify improvements to the cell DTX / DRX mechanism, including inter-node information exchange for cell DTX / DRX and alignment of cell DTX / DRX and UE DRX in RRC_CONNECTED mode.
[0234] Note: No changes to SSB transmission due to Cell DTX / DRX.
[0235] Note: The above improvements should be avoided in relation to IDLE / INACTIVE UEs.
[0236] 3. The following technologies are implemented in the space and power domains.
[0237] To enable efficient adaptation of spatial elements (e.g., antenna ports, active transceiver chains), specify necessary improvements to CSI and beam management-related procedures, including measurement, reporting, and signaling.
[0238] To enable efficient adaptation of power offset values between PDSCH and CSI-RS, necessary improvements to CSI-related procedures, including measurement, reporting, and signaling, are specified.
[0239] Note: The above objectives apply only to UE-specific channels / signals.
[0240] Note: Considering the total number and requirements of all CSI reports, conventional UE CSI / CSI-RS capabilities apply.
[0241] 4. If necessary, a mechanism to prevent camping of conventional UEs in cells adopting Rel-18 NES technology is specified.
[0242] 5. If the source / target cell is in NES mode, specify the CHO procedure improvement.
[0243] 6. Specify improvements to limiting paging in restricted areas and beam activation between nodes.
[0244] 7. If necessary, specify the relevant RRM / RF core requirements for the above features.
[0245] With the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time axis, controlling transmit / receive resources for UE-common or UE-specific signals / channels, changing the amount of resources in the frequency axis, controlling transmission power, or turning on / off antenna ports, TRPs (transmission-reception points), etc. in the spatial domain.
[0246] FIG. 19 illustrates an example of an operation procedure of a base station supporting NES technology applicable to the present disclosure.
[0247] Referring to FIG. 19, the base station identifies the NES solution(s) to be applied. The NES solution(s) may be related to the control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. Which NES solution(s) to apply may be adaptively selected based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.) or may be predefined. The base station that has identified the 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 regarding the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of the NES operation to at least one terminal. Additionally, the base station may receive capability information related to the NES from at least one terminal. Subsequently, the base station performs operations for the NES. At this time, the base station may perform operations for the NES based on the signaling performed earlier. That is, depending on the system information, configuration information, and control information transmitted through signaling, the base station can turn the transmission and reception of specific signals on / off, turn elements of the spatial domain on / off, or adjust resources for the transmission and reception of measurement signals.
[0248] NES technology can be performed through a procedure as shown in Fig. 19. Examples of NES solutions that can be performed by a procedure as shown in Fig. 19 are as follows.
[0249] Intra-system energy saving solution: A RAN node may request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).
[0250] Inter-system energy saving solution: An NG-RAN node owning a capacity booster cell can autonomously switch the cell to an inactive state.
[0251] SSB-less SCell solution: If no SSB or SMTC (SSB-based RRM measurement timing configuration) settings are provided for the SCell, the terminal can obtain timing reference and AGC sources from other serving cells. In FR1 or FR2, the base station can set up intra-band CA or inter-band CA including an SSB-less SCell, in which case SSB / SIB transmission can be triggered by the terminal's WUS (wake-up signal). Accordingly, as the period of common channels / signals such as SSB increases, the base station can remain in a sleep state for a longer period of time.
[0252] Cell DTX / DRX (discontinuous transmission / discontinuous reception) solution: To reduce the downlink transmission / uplink reception activity time of a base station, periodic cell DTX / DRX patterns (e.g., active and inactive periods) may be set commonly for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern may be set and activated separately, and up to two cell DTX / DRX patterns may be set per MAC entity. When cell DTX is set and activated, at least one of monitoring SPS opportunities or PDCCH monitoring may be suspended during the cell DTX inactive period. When cell DRX is set and activated, at least one of transmission from CG resources or SR transmission may be suspended during the cell DRX inactive period. Cell DTX / DRX may be enabled / disabled via RRC signaling or L1 group common signaling.
[0253] Parameters such as active duration and cycle may be set for the cell DTX / DRX. The active duration is the period during which the terminal waits to transmit an SR or CG after receiving a PDCCH or SPS opportunity, and the cycle specifies the periodic repetition of the active duration and the inactive duration. When both the cell DTX and cell DRX are set, parameters such as the active duration and cycle are common. If the base station recognizes an emergency call or public safety-related service (e.g., MPS or MCS), the network may release or disable the cell DTX / DRX settings so as not to affect the service. Additionally, at least some overlap is required between the active duration of the terminal's connected mode DRX and the active duration of the cell DTX / DRX. For example, the period of the terminal's connected mode DRX may be a multiple of the cell DTX / DRX period, or vice versa.
[0254] Conditional Handover (CHO) Solution: A CHO procedure, performed in such a way that the execution of a handover is determined by the terminal, is used while NES technology is applied (e.g., when a cell enables or disables Cell DTX / DRX). In this case, the terminal may use an NES-specific CHO event to execute a CHO for a candidate cell, and as an additional triggering condition for this, the reception of a DCI that enables CHO condition(s) set as an NES event indication may be applied.
[0255] Spatial and power domain adaptation solution: To support the gNB for transceiver muting and / or transmission power adaptation, the terminal may be configured to report multiple CSI entries in the 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 data channel (e.g., PDSCH) and a power offset between CSI and RS. Depending on the application of the spatial and power domain adaptation solution, CSI configuration, measurement, and / or reporting behavior may be affected.
[0256] Cell DTX / DRX
[0257] Base station DTX / DRX was proposed for NES purposes to operate the base station in sleep mode for a relatively long period without frequent wake-ups. By configuring the cell DTX and setting the on-duration of the terminals' C-DRX within the active period of the cell DTX, the base station can reduce energy consumption by utilizing DTX transmission under low system load conditions.
[0258] Figure 20 shows an example of a procedure for cell DTX / DRX operation.
[0259] Referring to FIG. 20, the base station transmits system information to the terminal, and the terminal checks information related to cell DTX / DRX. For example, the 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 the cell barring status (e.g., cellBarredNES). Specifically, if cellBarred included in the MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. Conversely, if cellBarred included in the 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. However, if the terminal has the capability to support NES cell DTX / DRX, the terminal checks SIB1 to determine the cell blocking status. If cellBarred in the MIB is set to barred and cellBarredNES is absent in SIB1, the terminal supporting NES cell DTX / DRX treats the cell as blocked and can perform cell reselection to another cell. On the other hand, if cellBarred in the MIB is set to barred and cellBarredNES is included in SIB1, the terminal supporting NES cell DTX / DRX can determine that the cell is not blocked.
[0260] In the case of FIG. 20, the terminal has the capability to support NES cell DTX / DRX, and it is assumed that the cellBarred in the MIB is set to notBarred or the cellBarred in the MIB is set to barred, and the cellBarredNES in SIB1 is included. Accordingly, the terminal can perform a random access procedure to connect to the base station and then perform communication. At this time, the base station performs a cell DTX / DRX operation and transmits 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). In addition, the configuration information may further include information for receiving and interpreting control information related to cell DRX / DRX (e.g., DCI-related information).
[0261] Subsequently, the base station transmits control information related to cell DTX / DRX to the terminal. The control information related to cell DTX / DRX may include DCI having a specified format (e.g., format 2_9). When an operation for a serving cell is configured according to at least one of cell DTX operation and cell DRX operation by configuration information (e.g., cellDTXDRX-Config), the terminal can identify a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring PDCCHs that transmit control information of the specified format during the active time through upper-level parameters (e.g., SearchSpace), and obtain the location of information regarding the serving cell within the control information through upper-level parameters (e.g., positionInDCI-cellDTRX). Then, the terminal can obtain the control information based on the identified set of search spaces and location.
[0262] Control information related to cell DTX / DRX may be used to indicate the activation or deactivation of cell DTX and / or cell DRX, and / or to provide an NES-mode indicator, and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, if the serving cell is set to a supplementary uplink (SUL) carrier, the indication for activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the SUL carrier.
[0263] Subsequently, the terminal and the base station can communicate based on the cell DTX / DRX. Specifically, the base station can turn the transmission and reception of signals on or off according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor signals from the base station. During DTX-OFF, the base station enters sleep mode to reduce energy consumption. At this time, the base station DTX cycle can be aligned with the terminal DRX cycle. The base station DTX-ON can fully cover the terminal's DRX-ON. Furthermore, the base station can align the transmission of Xn / NG with the transmission of Uu for NES purposes. The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station can perform dormancy-like behavior, such as transmitting SSB, SIB, and CSI-RS sparingly or not transmitting them at all, to reduce energy consumption. The terminal can receive downlink signals / channels sparingly or not receive them at all, depending on the base station's settings. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF period, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH.
[0264] SCell without SSB
[0265] FIG. 21 illustrates an example of a procedure for CA operation using an SSB-free SCell applicable to the present disclosure.
[0266] Referring to FIG. 21, the base station transmits configuration information for SCell to the terminal. That is, the base station transmits configuration information for CA to provide services to the terminal through CA operation. Here, the CA operation may be intra-band CA or inter-band CA. For example, the configuration information for SCell may include information containing information for adding SCell (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL settings, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Subsequently, the terminal determines the settings for CA operation and can perform communication using the base station's PCell and SCell. At this time, the terminal can confirm that the SCell is an SSB-free SCell based on the information related to the downlink frequency included in the configuration information and can check the related parameters. For example, the terminal determines that the SCell is an SSB-less SCell by confirming the existence of a parameter (e.g., SSBlessSCell) indicating that it is an SSB-less SCell, and can identify the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the case of Fig. D03, the reference cell may be a PCell. Therefore, the terminal can use the PCell as the timing reference and AGC source for communication in the SCell.
[0267] Conditional Hand Over (CHO)
[0268] FIG. 22 illustrates an example of a Conditional HandOver (CHO) procedure.
[0269] The order of the operations exemplified in Fig. 22 may vary depending on the case.
[0270] Referring to FIG. 22, the base station transmits configuration information for the CHO to the terminal. The configuration information for the CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to the configuration for reporting (e.g., ReportConfigNR). Here, the information related to the configuration for reporting may include information related to events related to reporting, identifiers of events (e.g., condEventId), and information indicating whether it is an NES-specific CHO event (e.g., nesEvent). In the example of FIG. 22, event information indicating that it is an NES-specific CHO event may be received.
[0271] The base station transmits information to the terminal that enables NES-specific CHO execution conditions. The information that enables NES-specific CHO execution conditions may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information that enables NES-specific CHO execution conditions may be referred to as an NES-mode indicator, and, for example, as 1-bit information, indicates that NES-specific CHO execution conditions are enabled if the associated upper layer parameter (e.g., nesEvent) is set and the serving cell of the associated block in the corresponding DCI is the primary cell.
[0272] Subsequently, the terminal performs a measurement and transmits the measurement report to the base station. Based on the measurement report, the base station determines the CHO and performs signaling for a handover request with the adjacent base stations indicated by the measurement report. The base station determines the adjacent base stations that have affirmed admission through signaling as candidate base stations and transmits information regarding the candidate base stations to the terminal. Accordingly, the terminal evaluates the CHO execution conditions for the candidate base stations. Once a candidate cell satisfying the conditions is determined, the terminal detaches from the old cell and synchronizes with the new cell. At this point, since the terminal previously received event information indicating that it is an NES-specific CHO event, as well as information enabling the NES-specific CHO execution conditions, it can determine whether the event is satisfied. In other words, when an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that it is an NES-specific CHO event (e.g., nesEvent), the terminal determines that an event associated with a corresponding measurement identifier (e.g., measId) is satisfied, and accordingly, can determine that the CHO execution condition is satisfied.
[0273] CSI Measurement and Reporting
[0274] Figure 23 shows an example of a procedure for CSI measurement and reporting.
[0275] Referring to FIG. 23, the base station transmits configuration information for CSI to the terminal. The configuration information for CSI may include information related to CSI-RS resources or resource sets (e.g., time-frequency resource information, sequence information, power information, etc.), information related to CSI reporting (e.g., quantity information, reporting type information, reporting resource information, codebook information, etc.), and information related to CSI measurement. Here, to assist the base station with base station transceiver muting and / or transmit power adaptation, the terminal may be configured to report multiple CSI entries in the CSI report based on a plurality of sub-configurations. Here, each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset. Additionally, regarding CSI reporting, a higher-level parameter (e.g., CSI-ReportConfig) included in the configuration information may include a list of sub-configurations, each sub-configuration being identified by an identifier (e.g., csi-ReportSubConfigID) and corresponding to a list of at least one CSI-RS resource, corresponding to a subset of CSI-RS antenna ports, and / or, in addition to a parameter related to the power control offset of the CSI-RS resource(s) (e.g., powerControlOffset), it may correspond to a power offset for a PDSCH related to the CSI-RS.
[0276] In this case, the configuration related to CSI may include multiple sub-configurations. Accordingly, when interpreting configuration information for CSI, the terminal can determine CSI-RS resources, CSI-RS port mapping, power offset, codebook type, report items, etc. by considering the sub-configurations. When the terminal is configured with configuration information related to CSI reporting that includes sub-configurations (e.g., CSI-ReportConfig), the terminal does not expect the upper-level parameter related to the report item (e.g., reportQuantity) to be 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'. Additionally, if the CSI reporting type is set to semi-persistent CSI reporting or aperioditic CSI reporting, the base station may activate / trigger only some of the sub-settings configured for the terminal via MAC-CE or DCI. That is, the trigger state for aperioditic CSI reporting can be set as needed, and the activation of semi-persistent CSI reporting can be controlled by an activation command.
[0277] For example, regarding the configuration of a report item, the terminal can determine the CSI-RS port index(s) for each CSI-RS resource based on information related to a port-subset per sub-configuration (hereinafter referred to as the '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 can identify at least one antenna port for the corresponding sub-configuration based on the positions of bits set to a positive value (e.g., 1) in the port-subset indicator.
[0278] For example, regarding the settings for a report item, the terminal can determine the codebook type based on the existence of sub-settings. Specifically, if sub-settings are configured for a CSI report, the terminal may exclude the configuration of at least one codebook type. However, depending on the capabilities of the terminal, it is possible to configure the said at least one codebook type.
[0279] For example, regarding the settings for a report item, a power offset value and an NZP (Non-Zero Power) CSI-RS resource set may be set for each sub-setting. In this case, the interpretation of the NZP CSI-RS resource set for each sub-setting may vary depending on whether the power offset value and the NZP CSI-RS resource set are set for each sub-setting.
[0280] In determining CQI, a higher-level parameter related to the time limit for channel measurements (e.g., timeRestrictionForChannelMeasurements) may be set. In this case, the terminal may need to derive a channel estimate to determine the CSI based on the most recent CSI reference resource. At this time, if Cell DTX is enabled for the base station, the Cell DTX activation time may be taken into account.
[0281] The CSI is derived based on the CSI reference resource. The CSI reference resource is defined as a group of downlink physical resource blocks corresponding to the bands related to the CSI derived in the frequency domain, and is defined as a single downlink slot determined in the time domain based on upper-layer parameters and subcarrier spacing. After receiving the CSI-RS, the terminal must transmit the CSI report no later than the CSI reference resource. In this case, if sub-configurations are set for the CSI report, the CSI reference resource is considered for each sub-configuration.
[0282] When configured to report at least one of the CQI index, PMI (Precoding Matrix Indicator), and RI (Rank Indicator), in a CSI reference resource, the terminal may assume specific values for the symbol position and number occupied in control signaling, the number of PDSCH and DMRS symbols, the subcarrier spacing of BWP, the bandwidth for CQI reporting, the CP length and subcarrier spacing of the reference resource, and the redundancy version (RV), for the purpose of deriving at least one of the CQI index, PMI, and RI. In this case, when sub-settings are configured for CSI reporting, assumptions regarding the antenna port, EPRE (Energy Per Resource Element), etc., may be determined based on the sub-settings.
[0283] Subsequently, the base station transmits at least one CSI-RS. Accordingly, the terminal can receive at least one CSI-RS and perform a measurement. At least one CSI-RS may be transmitted through a CSI-RS resource or resource set configured by configuration information.
[0284] In this case, if the terminal is configured as a DRX, the terminal may perform measurements as follows. For example, if the terminal is configured to monitor power saving-related control information (e.g., DCI format 2_6) and, in a situation where the DRX-related timer (e.g., drx-onDurationTimer) is not started by the upper-level parameter (e.g., ps-TransmitOtherPeriodicCSI), and is configured 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), in addition to 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, under conditions where drx-onDurationTimer is not initiated by a higher-level parameter (e.g., ps-TransmitPeriodicL1-RSRP), is configured to report L1-RSRP using a report setting type set to periodic reporting and a report item set to cri-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer within the DRX-related setting information (e.g., DRX-Config), excluding the DRX active time or the DRX active time for the CSI to be reported. Additionally, the most recent CSI measurement opportunity occurs within the DRX active time for the CSI to be reported.
[0285] Meanwhile, the base station may perform cell DTX / DRX operations. In this case, during the non-active period of the cell DTX, the terminal configured as the cell DTX is not expected to receive periodic CSI-RS and semi-static CSI-RS configured in the CSI reporting configuration associated with a reporting item including at least an RI (rank indicator). When the cell DTX is activated for a serving cell, the most recent CSI measurement opportunity of the semi-static CSI-RS resource or periodic CSI-RS resource occurs within the active periods of the cell DTX for CSI reporting, configured by the configuration information related to CSI reporting associated with at least an RI (e.g., CSI-ReportConfig).
[0286] A terminal that has received at least one CSI-RS determines the CSI. In other words, the terminal performs a CSI calculation. At this time, the terminal may perform the CSI calculation based on CSI processing criteria. The terminal may indicate the number of supported concurrent CSI calculations, i.e., the number of concurrently run CSI processing units (CPUs), called NCPU. The terminal may determine the number of CPUs for a corresponding CSI report based on at least one of the NCPU, the number of CPUs for each CSI report, the number of currently occupied CPUs, and the settings of the report item. For example, for configuration information related to a CSI report (e.g., CSI-ReportConfig) containing a report item parameter (e.g., reportQuantity) that is not set to 'none', the CPU(s) may be occupied for at least one OFDM symbol, where the number of at least one symbol may be determined based on the CSI-RS resources or CSI-IM resources associated with the sub-settings.
[0287] If configuration information related to CSI reporting (e.g., CSI-ReportConfig) includes multiple sub-configurations, the number of CPUs occupied by CSI reporting may be determined based on the number of CSI-RS resources corresponding to the sub-configurations. In this case, the number of CSI-RS resources may be determined based on the number of times the configuration information related to CSI reporting (e.g., CSI-ReportConfig) is referred or the number of sub-configurations referencing the said CSI-RS resources.
[0288] The terminal that has determined the CSI transmits the CSI report to the base station. The terminal may transmit CSI(s) for at least one sub-configuration according to the report item parameter (e.g., reportQuantity) configured for the configuration information (e.g., CSI-ReportConfig) related to the CSI (Channel State Information) report. For example, the CSI report may include at least one of PMI (Precoding Matrix Indicator), CQI (Channel Quality Indicator), RI (Rank Indicator), CRI (CSI-RS Resource Indicator), SSBRI (SS / PBCH Block Resource Indicator), LI (Layer Indicator), and RSRP (Reference Signal Received Power). In this case, the CSI report may include a Part 1 CSI report and a Part 2 CSI report. Additionally, the CSI report may be transmitted via at least one of PUCCH or PUSCH.
[0289] When a terminal multiplexes CSI reports containing Part 2 CSI reports to a PUCCH resource, the terminal determines the number of PRBs or Part 2 CSI reports for the PUCCH resource and PUCCH resource, assuming that each CSI report or each CSI sub-report included in the CSI report indicates Rank 1 or a Rank combination {1, 1}. When a higher-level parameter related to the CSI report mode (e.g., csi-ReportMode) is set to 'Mode2', the terminal determines the number of PRBs or Part 2 CSI reports for the PUCCH resource and PUCCH resource, assuming that each CRI of the CSI report is associated with a resource pair.
[0290] If a CSI report in PUSCH contains two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows the priority order. Except where the corresponding CSI report contains at least one CSI sub-report including Part 2 that corresponds to a sub-configuration from a list of sub-configurations provided by a higher-level parameter (e.g., csi-ReportSubConfigList) included in the information related to the CSI report (e.g., CSI-ReportConfig), if the terminal omits Part 2 CSI information for a specific priority level, the terminal must exclude all information for that priority level.
[0291] For report configurations related to information (e.g., CSI-ReportConfig) concerning a CSI report 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, the omission of Part 2 CSI is performed at the sub-configuration level within the same priority level. Here, the sub-configuration having a lower index value has a higher priority.
[0292] If a CSI report consists of two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows the priority order. For a given CSI report containing at least one CSI sub-report, the omission of the Part 2 CSI is defined in Section 5.2.3, for a report configuration associated with information related to the CSI report (e.g., CSI-ReportConfig) that includes a list of sub-configurations. The Part 2 CSI is omitted starting from the lowest priority level up to a Part 2 CSI code rate that is less than or equal to the code rate set by the upper-level parameter (e.g., maxCodeRate).
[0293] Additionally, when a CQI request field within a DCI triggers CSI report(s) in a PUSCH, the first uplink symbol carrying the CSI report(s) does not precede a symbol specified after a certain interval from the last symbol of the PDCCH that carried the DCI. This can be understood as a measure to guarantee the CSI calculation time. In this case, 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.
[0294] CSI is transmitted via PUCCH or PUSCH and can be represented as a bit sequence of a fixed size. When CSI is transmitted via PUCCH, if a parameter (e.g., csi-ReportSubConfig) specifying sub-configuration settings for the CSI report is configured, the mapping order of CSI fields for each CSI sub-report may follow a defined order.
[0295] When a CSI is transmitted via PUSCH, if a parameter (e.g., csi-ReportSubConfig) that specifies settings per sub-configuration for the CSI report is configured, the mapping order of CSI fields for each CSI sub-report may follow a predetermined order.
[0296] Meanwhile, in 3GPP NR release 19, a work item titled “Enhancements of network energy savings for NR” was additionally approved. Specifically, as shown below, the following enhancement techniques are being considered in 3GPP NR release 19.
[0297] 1. Specify procedures and signaling methods to support on-demand SSB SCell operation for both in-band and cross-band CA for a UE in connection mode configured as CA.
[0298] For example, specify the triggering method(s). (Select from UE uplink wake-up signal using existing signal / channel, cell on / off indication via backhaul, and Scell enable / disable signaling.)
[0299] Note 1: On-demand SSB transmission can be used by the UE for minimum SCell time / frequency synchronization, L1 / L3 measurements, and SCell activation, and is supported for FR1 and FR2 in the non-shared spectrum.
[0300] 2. Investigate procedure and signaling method(s) for supporting on-demand SIB1 for UEs in idle / inactive mode as follows:
[0301] Triggering method by uplink wake-up signal using existing signal / channel.
[0302] Provides wake-up signal settings to the UE.
[0303] If necessary, information exchange between gNBs for setting the wake-up signal at a minimum.
[0304] 3. Specify the adaptation of common signal / channel transmission.
[0305] For example, adaptation of SSB in the time domain, e.g., adaptation of periodicity.
[0306] PRACH adaptation in the time domain.
[0307] Adaptation of PRACH in the spatial domain, for example, studies non-uniform PRACH resources per SSB, and materializes if found to be beneficial.
[0308] Coordination of paging opportunities, including limiting paging opportunities in the time domain.
[0309] In this case, paging latency must not increase, and there should be no negative impact on existing UEs unless significant benefits are demonstrated.
[0310] On-demand SSB
[0311] A method to reduce energy consumption can be discussed in which the base station transmits SSB to a specific cell through an on-demand SSB process, and does not transmit SSB to that cell when the on-demand SSB process is not present. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, as SSB had to be transmitted periodically at all times for purposes such as time / frequency synchronization or RRM measurement. Considering this, the base station can reduce energy consumption by refraining from transmitting SSB and only performing transmission when the on-demand SSB process is involved. The on-demand SSB process can be triggered through one of the following methods.
[0312] 1) The terminal transmits an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS, etc. in an NR system) to request SSB transmission from the base station.
[0313] 2) Base station (or TRP) #1 requests SSB transmission from base station (or TRP) #2 via an interface between base stations (e.g., Xn interface in an NR system) or backhaul signaling.
[0314] 3) Signal whether to transmit an SSB for the corresponding Scell through Scell (secondary cell) activation / deactivation signaling.
[0315] Considering coexistence with existing NR terminals, the on-demand SSB operation for connected mode terminals and SCells in Release 19 is limited, but in future releases or next-generation communication systems, on-demand SSB operation (for SSB transmission on a PCell) may be defined considering inactive or idle mode terminals or initial connection terminals. Additionally, carrier aggregation (CA) including the SCell may be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process may be utilized for functions such as at least time / frequency synchronization, L1 / L3 measurement, and SCell activation.
[0316] On-demand SIB1 transmission
[0317] A method to reduce energy consumption can be discussed in which the base station transmits a SIB1 for a specific cell through an on-demand SIB1 process, and does not transmit the SIB1 for that cell when the on-demand SIB1 process is not present. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, because it was always necessary to periodically provide a SIB1 containing system information and random access information for initial access or idle mode terminals to connect to a cell. Considering this, the base station's energy consumption can be reduced by allowing it to refrain from transmitting SIB1 and only transmit it when the on-demand SIB1 process is involved. The base station's SIB1 transmission can be triggered by the terminal transmitting an uplink signal / channel (e.g., PRACH in an NR system), and specifically, the following scenarios can be considered, but may not be limited to them.
[0318] Figure 24 shows an example (Scenario 1) of an on-demand SIB1 process.
[0319] 1) Scenario 1: As shown in FIG. 24, a terminal that receives an SSB (and / or other downlink signal / channel) at cell #1 and recognizes that SIB1 is not being transmitted on cell #1 can trigger the transmission of SIB1 by transmitting a signal requesting SIB1 (referred to as WUS, wake-up signal, for convenience in this disclosure) based on information provided by the SSB (and / or other downlink signal / channel) and / or predetermined information. A base station that receives the WUS can transmit a specific DL signal / channel on cell #1 in response thereto, or transmit SIB1 on cell #1 (or without transmitting the DL signal / channel).
[0320] Figure 25 shows another example (Scenario 2) of the on-demand SIB1 process.
[0321] 2) Scenario 2: As shown in FIG. 25, a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. Based on the information provided by the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information, the terminal may transmit a signal requesting SIB1 (i.e., WUS) onto cell #1 to trigger the transmission of SIB1 to cell #2. Upon receiving the WUS, the base station may transmit a specific DL signal / channel (on cell #1 or cell #2) in response, or transmit SIB1 to cell #1 or cell #2 (or without transmitting the DL signal / channel).
[0322] Figure 26 shows another example of an on-demand SIB1 process (Scenario 3).
[0323] 3) Scenario 3: As shown in FIG. 26, a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. Based on the information provided by the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information, the terminal may transmit a signal requesting SIB1 (i.e., WUS) onto cell #2 to trigger the transmission of SIB1 for cell #2. A base station that receives the WUS may transmit a specific DL signal / channel (on cell #1 or cell #2) in response, or transmit SIB1 for cell #2 onto cell #1 or cell #2 (or without transmitting the DL signal / channel).
[0324] Methods to reduce energy consumption by controlling common signal / channel transmissions such as SSB, PRACH, and paging can be discussed. However, for example, while completely turning off the SSB can significantly reduce the energy consumption of the base station, the absence of an SSB that performs functions such as time / frequency synchronization or RRM measurement may result in unstable operation for the corresponding cell from the terminal's perspective. Considering this, energy saving effects for the base station can be achieved by changing the transmission pattern of the SSB (e.g., transmission period, period per SSB candidate index, SSB candidate index transmitted within one transmission period, transmission power, etc.) depending on the situation.
[0325] In the case of PRACH resources, in the case of contention-based random access, energy consumption can increase because the base station always attempts to receive from the configured PRACH resources since it is unknown when the terminal will transmit PRACH. Considering this, the energy of the base station can be saved by applying methods to adjust the amount of PRACH resources (e.g., adjusting the cycle of PRACH resources, adjusting the amount of resources by pre-configuring PRACH resources set #1 and set #2 and giving instructions to turn on only one set or both sets, or providing the corresponding amount of PRACH resources for each SSB index uniformly or non-uniformly).
[0326] In the case of paging, conventionally, paging frames (PF) and / or paging occasions (PO) were distributed along the time axis within a DRX cycle (or paging cycle), and terminals attempted to receive paging at specific PF / POs derived from their ID-based formulas. From the base station's perspective, if it intended to transmit paging to multiple terminals simultaneously, it may have to wake up frequently to transmit paging. To reduce the resulting energy consumption of the base station, it may be considered to place the PF and / or PO for paging reception as close to the time axis as possible, or to place them using different frequency axis resources within the same timeframe.
[0327] Specific embodiments of the present disclosure
[0328] The present disclosure describes an on-demand SSB (OD-SSB). As previously mentioned, in the prior art, the SSB was always transmitted over the cell / carrier / BWP, but in future technology, the operation of the SSB temporarily upon request or need may be considered.
[0329] In the following, to distinguish between two types of SSBs, the type of SSB that is transmitted almost always while the cell / carrier is on (i.e., the SSB in the prior art) is called Always-On SSB (abbreviated as AO-SSB), and the type of SSB that can be transmitted by a temporary activation / indication / triggering command or signaling, and by an explicit / implicit signaling or command (e.g., an instruction to transmit N times) is called On-demand SSB (OD-SSB).
[0330] In some carriers / cells, only OD-SSB can be transmitted, and the center frequencies of AO-SSB and OD-SSB can be transmitted at the same location or at different locations.
[0331] In the case of AO-SSB and OD-SSB, they can be used as reference signals for the source for measurement / reporting and can be transmitted from the same dedicated or active BWP.
[0332] In this case, regarding the relevant CSI measurement / reporting, we explain how to perform measurement / reporting based on the quasi-co-located (QCL) relationship between SSB IDs and the measurement target (SINR or RSRP), and how to establish associations for the CSI reporting settings for measurement / reporting.
[0333] Below, we specifically present various methods for how to perform CSI measurement / reporting within a cell / carrier / BWP when the AO-SSB and OD-SSB are in the same cell / carrier / BWP.
[0334] For example, regarding whether to apply both AO-SSB or OD-SSB or only one of them when performing CSI-related measurements / reporting, we propose how the two different types of SSB operate under specific conditions.
[0335] In addition, for the transmission beams of AO-SSBs and OD-SSBs, additional consideration and definition may be required regarding the relationship between beams known as QCL, that is, the direction and characteristics of the beams.
[0336] Finally, when performing CSI measurement / reporting, various methods can be applied depending on whether the measurement / report is intended to measure RSRP or SINR.
[0337] In the case of SSB, a 'sweeping' process is performed to sequentially transmit SSB beams to cover the entire cell. In other words, the base station performs a 'beam sweeping' process in which it alternately transmits SSB beams in multiple directions, and the bundle of SSBs transmitted during this process is called an SSB burst. For example, a single SSB burst is transmitted within 5ms (half-frame) and can be transmitted repeatedly at regular intervals.
[0338] The maximum number of SSBs that can be included in a single SSB burst can be determined according to the frequency band, for example, 4, 8, 64, etc.
[0339] The base station does not always transmit the maximum number of SSBs, but may transmit a smaller number of SSBs. In this case, the base station can provide information in the form of a bitmap (bit string) regarding which SSBs are actually transmitted (which beam is used for transmission). This information may exist for AO-SSB and OD-SSB respectively, which can be referred to as ssb-PositionsInBurst for AO-SSB and od-ssb-PositionsInBurst for OD-SSB. ssb-PositionsInBurst / od-ssb-PositionsInBurst can indicate which location (location of which index) among the candidate locations within the SSB burst the SSB is transmitted from (e.g., the location in the time domain of the transmitted SSB within a half-frame containing the SSB).
[0340] For example, regarding AO-SSB, ssb-PositionsInBurst can indicate which AO-SSB is being transmitted, and regarding OD-SSB, od-ssb-PositionsInBurst can indicate which OD-SSB is being transmitted (if od-ssb-PositionsInBurst is not configured / provided, ssb-PositionsInBurst can indicate). Hereinafter, ssb-PositionsInBurst may refer to ssb-PositionsInBurst and / or od-ssb-PositionsInBurst, and may also be referred to as PositionInBurst.
[0341] In addition, time information for SSB transmission includes SFN_Offset information related to placement in the time domain based on a time reference for where the SFN is located in units of 10ms, and half frame index information related to where it is located within 10ms.
[0342] For example, if the half-frame index is 0, the SSB is located in the first 5ms of a 10ms unit length, and if it is 1, the SSB is located in the second 5ms.
[0343] In the case of an SSB burst, no matter how many bits the bitmap of ssb-PositionsInBurst has, it will be swept once for all directions of the beams within the cell's full coverage within 5ms.
[0344] Additionally, for different SSBs (AO-SSB or OD-SSB), if they have the same SSB ID, it may be assumed / determined that they are actually in a QCL relationship, or that they have the same beam direction or beam characteristics. In this disclosure, the meaning of such expressions may be broadly used to mean that they are in the same position in terms of “Doppler spread, Doppler shift, average gain, average delay, delay spread, and, if applicable, spatial RX parameters.” These matters may apply equally to AO-SSB and OD-SSB. For example, if the SSB IDs of AO-SSB and OD-SSB are the same, it may be assumed / determined that they are in a QCL relationship. Alternatively, if the SSB IDs between OD-SSBs are the same, it may be assumed / determined that they are in a QCL relationship. This will be described in detail later with reference to FIGS. 32 to 34.
[0345] Proposal 1: Method of associating AO-SSB and / or OD-SSB to a single CSI reporting setting based on frequency / ssb-PositionsInBurst / time location.
[0346] In the case of a cell / carrier containing both AO-SSB and OD-SSB, two different types of SSBs may exist within the same BWP. In this case, even if the frequency positions differ within the same BWP, it can be assumed / expected / judged that the SSB IDs of the individual beams actually transmitting have the same beam direction and characteristics (it can be assumed / expected / judged that they are QCL).
[0347] In this case, from the UE's perspective, there may not be a need to measure or report to each different SSB. This is because, when the SSB IDs are the same, the direction and characteristics of the beams may not differ significantly.
[0348] Based on this assumption, in certain cases, it may be more efficient to associate a single CSI reporting setting with each of the two types of SSBs, rather than individually configuring different CSI reporting settings for each. This proposal explains, along with specific examples, under what cases, situations, or conditions, different SSBs or only one of the two SSBs can be associated with a single CSI reporting setting.
[0349] Method 1: If the center frequencies of the AO-SSB and OD-SSB are the same, the two SSBs can be associated with a single CSI reporting setup.
[0350] This can be applied in a limited way, for example, when the values of the bitmap information (e.g., ssb-PositionsInBurst parameter) representing the combination of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB are the same.
[0351] For example, if the ssb-PositionsInBurst of the AO-SSB is 01010101 and the od-ssb-PositionsInBurst of the OD-SSB is 01010101, two different types of SSBs can be associated with a single CSI reporting setting. However, if the od-ssb-PositionsInBurst of the OD-SSB is 01010100, the OD-SSB cannot be placed at the same frequency because it is not the same value as the ssb-PositionsInBurst of the AO-SSB, and thus cannot be associated with a single CSI reporting setting. That is, if the center frequency of AO-SSB and the center frequency of OD-SSB are the same, and the ssb-PositionsInBurst parameter set for AO-SSB and the od-ssb-PositionsInBurst parameter set for OD-SSB are the same, then AO-SSB and OD-SSB can be associated in a single CSI reporting setting.
[0352] Or, if the center frequency of AO-SSB and the center frequency of OD-SSB are the same, and the ssb-PositionsInBurst parameter set for AO-SSB and the od-ssb-PositionsInBurst parameter set for OD-SSB are different, then AO-SSB and OD-SSB cannot be associated in a single CSI reporting setting, and only OD-SSB can be associated in a single CSI reporting setting.
[0353] If the center frequencies are the same and the actual transmitted SSB ID bitmap (let's collectively call this PositionInBurst) is identical, both AO-SSB and OD-SSB can be associated in a single CSI report configuration for efficiency. Exceptionally, if the bitmap information is different, the two SSBs cannot be associated simultaneously, and only OD-SSB can be associated.
[0354] Method 2: When the center frequencies of the AO-SSB and OD-SSB are different, the two SSBs can be associated with a single CSI reporting setup under specific conditions.
[0355] For example, the above specific condition may be limited to cases where the two SSBs are in the same BWP.
[0356] FIG. 27 illustrates a case where two SSB bursts overlap in the time domain when the center frequencies of AO-SSB and OD-SSB are different.
[0357] Referring to Fig. 27, AO-SSB and OD-SSB overlap in some time domains.
[0358] When the center frequencies of AO-SSB and OD-SSB are different, the specific condition for associating the two SSBs with a single CSI reporting setting can be limited to cases where the two SSB bursts overlap or overlap each other in the time domain (SFN_Offset or half-frame index) as illustrated in FIG. 27 (or cases where the SFN_Offset or half-frame index information in the time domain is the same for AO-SSB and OD-SSB).
[0359] FIG. 28 illustrates a case where the center frequencies of AO-SSB and OD-SSB are different, and the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB are the same.
[0360] Referring to FIG. 28, in AO-SSB and OD-SSB with different center frequencies, the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB may be identical. For example, ssb-PositionsInBurst of AO-SSB may indicate "00111100", and od-ssb-PositionsInBurst of OD-SSB may also indicate "00111100".
[0361] When the center frequencies of AO-SSB and OD-SSB are different, the specific condition for associating the two SSBs with a single CSI reporting setting can be limited to cases where the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB (e.g., the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related od-ssb-PositionsInBurst parameter, or the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related ssb-PositionsInBurst parameter (if od-ssb-PositionsInBurst is not provided)) are the same, as illustrated in FIG. 28.
[0362] FIG. 29 illustrates a case where the center frequencies of AO-SSB and OD-SSB are different, the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB are the same, and the SSB bursts overlap / overlap in the time domain.
[0363] Referring to FIG. 29, in AO-SSB and OD-SSB with different center frequencies, the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB may be identical. For example, ssb-PositionsInBurst of AO-SSB may indicate "00111100", and od-ssb-PositionsInBurst of OD-SSB may also indicate "00111100". Additionally, AO-SSB and OD-SSB overlap in some time domains.
[0364] When the center frequencies of the AO-SSB and OD-SSB are different, the specific condition for associating the two SSBs with a single CSI reporting configuration is, as illustrated in FIG. 29, when the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of the AO-SSB and OD-SSB (e.g., the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related od-ssb-PositionsInBurst parameter, or the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related ssb-PositionsInBurst parameter (if od-ssb-PositionsInBurst is not provided)) are the same and the SSB bursts overlap in the time domain (SFN_Offset or half-frame index), or when the SFN_Offset or half-frame index information in the time domain is AO-SSB and Regarding OD-SSB, it can be limited to cases where they are the same.
[0365] The embodiment of FIG. 29 can be considered as a combination of the two preceding embodiments, namely the embodiments of FIG. 27 and 28.
[0366] In the limited cases as described above, both AO-SSB and OD-SSB may be associated with a single CSI reporting setting, while in other cases, only OD-SSB may be associated with a single CSI reporting setting.
[0367] Even if AO-SSB and OD-SSB exist within the same BWP, if their center frequencies differ, there may be no need to measure / report for both SSBs simultaneously if the individual beam SSB IDs actually transmitted within the SSB burst are identical for both AO-SSB and OD-SSB. This is because the UE can assume / expect / judge that the two beam characteristics and directions are the same, allowing a single CSI reporting setting to be associated only with the OD-SSB—which is more likely to have a smaller period than the AO-SSB—from the outset for CSI measurement / reporting. Even if the AO-SSB is present within the BWP from the beginning, the UE does not need to consider it, and only the OD-SSB is set as the reference RS for CSI measurement / reporting, thereby reducing complexity in terms of measurement / reporting execution without the need for the terminal to consider two SSBs.
[0368] For example, even if the center frequencies are different, both AO-SSB and OD-SSB can be associated with a single CSI report configuration if one of the following conditions is satisfied: i) the time domains (SFN Offset, Half Frame index) overlap or are identical, ii) the transmitted SSB ID bitmaps (PositionInBurst) are identical, or iii) a combination of the two conditions above (time overlap + identical bitmaps). Otherwise, only OD-SSB can be associated.
[0369] Method 3: When the center frequencies of the AO-SSB and OD-SSB are different (which can be limited to within the same BWP), only the OD-SSB can be associated with (a single) CSI reporting setup. The CSI reporting setup for the measurement / reporting of the AO-SSB within the same BWP can be not considered, so association and setup may not be considered.
[0370] For example, it can be limited to cases where two SSB bursts do not overlap or overlap with each other in the time domain (SFN_Offset or half-frame index) or where the SFN_Offset or half-frame index information in the time domain is different for AO-SSB and OD-SSB.
[0371] For example, the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB (e.g., the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related od-ssb-PositionsInBurst parameter, or the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related ssb-PositionsInBurst parameter (if od-ssb-PositionsInBurst is not provided)) can be limited to cases where they are different.
[0372] For example, it may be limited to cases where the combination / bitmap of SSB IDs actually transmitted within the AO-SSB and OD-SSB SSB bursts (e.g., the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related od-ssb-PositionsInBurst parameter, or the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related ssb-PositionsInBurst parameter (if od-ssb-PositionsInBurst is not provided)) are different from each other and there is no overlap / overlapping of SSB bursts in the time domain (SFN_Offset or half-frame index), or where the SFN_Offset or half-frame index information in the time domain is not the same for AO-SSB and OD-SSB. This embodiment can be considered as a combination of the two preceding embodiments.
[0373] According to the embodiment, the period of OD-SSB can be limited to a case where it is smaller than the period of AO-SSB.
[0374] In the limited cases as described above, only OD-SSB may be associated with a single CSI reporting setting, while in other cases, both AO-SSB and OD-SSB may be associated with a single CSI reporting setting.
[0375] If the center frequencies are different, only the OD-SSB can be associated with a single CSI reporting setup depending on the following conditions (e.g., i) time domains (SFN Offset, etc.) are different or do not overlap, ii) transmitted SSB ID bitmaps are different, or iii) the period of the OD-SSB is shorter than that of the AO-SSB). Complexity can be reduced by excluding existing AO-SSBs from measurement / reporting considerations.
[0376] Method 4: When the center frequencies of the AO-SSB and OD-SSB are different (which can be limited to within the same BWP), only the OD-SSB can be associated with (a single) CSI reporting setup. The CSI reporting setup for the measurement / reporting of the AO-SSB within the same BWP is not considered, so association and setup may not be considered.
[0377] For example, it can be limited to cases where two SSB bursts overlap each other in the time domain (SFN_Offset or half-frame index) or where the SFN_Offset or half-frame index information in the time domain is the same for AO-SSB and OD-SSB.
[0378] For example, the combination / bitmap of SSB IDs actually transmitted within the SSB bursts of AO-SSB and OD-SSB (e.g., the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related od-ssb-PositionsInBurst parameter, or the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related ssb-PositionsInBurst parameter (if od-ssb-PositionsInBurst is not provided)) can be limited to cases where they are the same.
[0379] For example, the combination / bitmap of SSB IDs actually transmitted within the AO-SSB and OD-SSB SSB bursts (e.g., the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related od-ssb-PositionsInBurst parameter, or the AO-SSB related ssb-PositionsInBurst parameter and the OD-SSB related ssb-PositionsInBurst parameter (if od-ssb-PositionsInBurst is not provided)) may be equal to each other, and the SSB bursts overlap / overlap in the time domain (SFN_Offset or half-frame index), or the SFN_Offset or half-frame index information in the time domain may be equal to each other for AO-SSB and OD-SSB. This embodiment may be considered as a combination of the two preceding embodiments.
[0380] According to the embodiment, the period of OD-SSB can be limited to a case where it is smaller than the period of AO-SSB.
[0381] When the center frequencies are different, the OD-SSB can be associated with the priority CSI reporting setting under specific conditions. The aforementioned specific conditions may be cases where the time domains overlap or the bitmaps are identical, similar to Method 2 described above. In this case, since the characteristics of the two beams can be expected to be the same, only the OD-SSB, which is advantageous due to its shorter period, can be associated with the CSI reporting setting exclusively. Method 4 is similar to Method 2 in terms of conditions, but ultimately, only the OD-SSB is set as the reporting target to minimize the complexity of the terminal.
[0382] Proposal 2: Method for considering QCL and beam characteristics (direction) for each SSB ID within different OD-SSBs.
[0383] For individual SSB IDs of AO-SSB and OD-SSB, information (ssb-PositionsInBurst, od-ssb-PositionsInBurst, etc.) in the form of a bitmap within the aforementioned SSB burst is provided so that the UE can determine whether the corresponding SSB ID is actually transmitted. For example, an SSB burst may be composed of 8 bits. In this case, if the ssb-PositionsInBurst of AO-SSB (actual SSB transmission bitmap parameter) is “01111111” and the od-ssb-PositionsInBurst of OD-SSB is “01010101”, the UE can assume / expect / judge that AO-SSB and OD-SSB have the same beam direction and beam characteristics among the SSB ID numbers that are actually transmitted for IDs from SSB 0 to SSB 7. This helps the UE determine the transmission and reception direction.
[0384] In the case of the od-ssb-PositionsInBurst parameter of the OD-SSB, multiple candidate values are set at the upper layer and notified to the UE in advance. When the network (base station) directs actual transmission, one of the multiple values can be provided through enable / instruct / triggering signaling or commands (L1 / L2 / L3). At this time, it is necessary to define the QCL relationship between individual SSB IDs, as well as beam characteristics and directions, not only for the AO-SSB and OD-SSB QCL relationships but also for cases where only the OD-SSB exists in a cell / carrier without an AO-SSB.
[0385] Method 1: When the od-ssb-PositionsInBurst (or ssb-PositionsInBurst if od-ssb-PositionsInBurst is not provided) bitmap information, which indicates the ID information of the beam actually transmitted in the OD-SSB, consists of multiple candidate values, the UE can assume / expect / judge that the individual bit fields of the bitmap information for the multiple setting values have the same beam direction and beam characteristics.
[0386] For example, regarding OD-SSB, if ssb-PositionsInBurst={1010, 1111, 1101, 1100} is composed of 4 bits, then among the bitmap values of each candidate, some bit fields are '0' and some bit fields are '1'. In this case, for each bit field that is set to 1, i.e., SSB ID (=0 ~ 3), the UE can assume / expect / judge that they have the same beam characteristics and direction even among different candidate bitmap values.
[0387] Among all candidate values (1011, 1111, 1101, 1100), the first bit field of each candidate (SSB ID=0) is set to '1'. In this case, it can be assumed / considered that the beams of each SSB ID=0 have the same characteristics and direction.
[0388] For example, in the first candidate value (1011) and the second candidate value (1111) of ssb-PositionsInBurst, the third bit field (i.e., in the case of SSB ID=2) is '1', but in the third candidate value (1101) and the fourth candidate value (1100) of ssb-PositionsInBurst, the third bit field (i.e., in the case of SSB ID=2) is '0'. Therefore, in this case, regarding the first and second candidate values, the UE can assume / expect / judge that the third bit field, i.e., SSB ID=2, has the same beam direction and the same beam characteristics.
[0389] For a single serving cell / BWP, when multiple OD-SSB settings are configured (without AO-SSB), the terminal can assume that a QCL relationship is established between the SSB index n of one OD-SSB setting and the SSB index n of another OD-SSB setting.
[0390] Alternatively, for a single serving cell / BWP, one OD-SSB configuration may be configured (without AO-SSB) and one or more PositionInBurst (od-ssb-PositionsInBurst or ssb-PositionsInBurst) parameters for the OD-SSB may be configured. In this case, the terminal may assume that a QCL relationship exists between an SSB index k belonging to a PositionInBurst parameter and an SSB index k belonging to another PositionInBurst parameter.
[0391] Proposal 3: Measurement operation method when AO-SSB and OD-SSB are the same, depending on the measurement target of OD-SSB.
[0392] Once the reference RS is determined, the target for CSI measurement / reporting is decided. Generally, in the case of SSB, RSRP (Reference Signal Received Power) or SINR (Signal to Interference plus Noise Ratio) is measured. When the upper layer (e.g., RRC signaling) informs the terminal of the target to be measured (e.g., RSRP or SINR) through information called reportQuantity, the terminal can determine whether to measure RSRP or SINR.
[0393] For example, if the reportQuantity is determined within the CSI reporting settings of the OD-SSB, the terminal can measure the RSRP or SINR of the OD-SSB. The base station simply needs to inform the reportQuantity information, which distinguishes whether to measure the RSRP of the OD-SSB or the SINR, by specifying either OD-SSB-RSRP or OD-SSB-SINR. In this way, if there are two different types of SSBs, such as AO-SSB and OD-SSB, within the cell / carrier, signaling / commands can be controlled to measure / report only one of the two. Conversely, if the reportQuantity information specifies either AO-SSB-RSRP or AO-SSB-SINR, SINR or RSRP measurement for the AO-SSB can be performed.
[0394] Method 1: When setting up CSI reporting, if the measurement / reporting target is specified as the measurement target (Target) of OD-SSB through a specific parameter setting called reportQuantity, it means that only OD-SSB (not AO-SSB) is associated with the CSI reporting setting, and the terminal can perform measurement / reporting using only OD-SSB.
[0395] For example, if the reportQuantity within a CSI reporting configuration is set to OD-SSB-RSRP (or od-ssb-Index-RSRP) or OD-SSB-SINR (or od-ssb-Index-SINR), SINR or RSRP measurement / reporting is performed using only OD-SSB. It can be assumed that both AO-SSB and OD-SSB are configured / connected in relation to CSI-Resource within a single CSI reporting configuration. In this case, even if two different types of SSBs are associated with a single CSI reporting configuration, the UE can be instructed / configured to determine which SSB or RS is being measured / reported based on the reportQuantity information / instructions. Based on the instructions / configurations of the corresponding reportQuantity, the UE identifies which RS or SSB is involved and can perform RSRP or SINR-related measurement / reporting based on that SSB or RS. Table 1 shows an example of the instruction / setting of reportQuantity. Through reportQuantity, you can instruct RSRP or SINR for a specific od-SSB.
[0396] [Table 1]
[0397]
[0398] Proposal 4: Configuration / Operation Plan for OD-SSB Cycle Information
[0399] In the case of OD-SSB, multiple SSB burst period information (multiple SSB burst period candidate values) is configured at the upper layer, and one of the multiple SSB burst period information (multiple SSB burst period candidate values) can be designated or designated by the OD-SSB's activation / instruction / triggering signaling or command. At this time, the UE can assume / expect / judge that the OD-SSB is being transmitted at the period of the single designated or designated value. During transmission, the OD-SSB's period information can be changed by the activation / instruction / triggering signaling or command. However, there may be cases where the period information is not configured at the upper layer. Considering such cases, methods are required for the UE to estimate the period value of an OD-SSB that has not been configured.
[0400] The following describes such methods.
[0401] Method 1: If AO-SSB is in the corresponding cell / carrier, the period of AO-SSB can be assumed to be the period of OD-SSB.
[0402] For example, if the period of AO-SSB is K ms, the terminal can assume / expect / judge that the period of OD-SSB is also K ms when the period information of OD-SSB is not set. In this case, for a specific time range in the SCell deactivation / deactivated state, additional methods can be applied to save power by using the corresponding period value when the period of AO-SSB exceeds a specific X reference period value (e.g., 10 ms or 20 ms) and using the specific X reference period value when it is less than or equal to the said specific X reference period value.
[0403] Specifically, if the SCell deactivation state is in a specific time range and the specific X reference period is 20ms, and the period information of the OD-SSB is not set, and the period of the AO-SSB is 5ms, the UE can assume / expect / judge that the period of the OD-SSB is 20ms, and if the period of the AO-SSB is 20ms, the UE can assume / expect / judge that the period of the OD-SSB is 20ms. Outside of the specific time interval of the SCell deactivation state (e.g., including the SCell activation interval), the UE can assume / expect / judge that the period of the AO-SSB is Kms as the period of the OD-SSB without considering the specific X reference period value.
[0404] Method 2: If AO-SSB is not present in the cell / carrier, the period of OD-SSB can be assumed to a specific default value (e.g., 5ms, 10ms, or 20ms).
[0405] For example, the default period value is defined / instructed as K ms (e.g., 5 ms, 10 ms, or 20 ms), and in cases where the period information of the OD-SSB is not set in the upper layer, the corresponding default period value can be assumed / expected / determined as the period of the OD-SSB.
[0406] At this time, for a specific time range in the SCell disabled state, in order to save power, if the default period value is greater than or exceeds a specific X reference period (e.g., 10ms or 20ms), the corresponding period value is used, and if it is less than or equal to the specific X reference period value, the specific X reference period value can be used.
[0407] Specifically, if SCell is disabled and the specific X reference period for a specific time range is 20ms and the OD-SSB period information is not set, and the default period value is 5ms, the UE can assume / expect / judge that the OD-SSB period is 20ms only for that time range. If the default period is 20ms, the UE can assume / expect / judge that the OD-SSB period is 20ms only for that time range. Outside of the specific time interval when SCell is disabled (including the SCell enabled interval), the UE can assume / expect / judge that the OD-SSB period is K ms regardless of the specific X reference period value.
[0408] Proposal 5: Method of operation for measurement when there are multiple OD-SSBs within a dedicated BWP.
[0409] If an OD-SSB can be set for each dedicated BWP, two different OD-SSBs may be set. In this case, a special principle may be required to determine which OD-SSB should be used as the basis for measurement for each BWP. In this case, at least one of the following methods may be used.
[0410] Method 1: When an OD-SSB can be set for each dedicated BWP, an OD-SSB can be set for a BWP only if there is no overlapping OD-SSB of another BWP for that BWP. The terminal can perform measurements using the set OD-SSB to generate / report CSI.
[0411] Figure 30 shows an example of setting up OD-SSB.
[0412] Referring to FIG. 30, when an OD-SSB is set in a specific BWP (e.g., BWP 0), the OD-SSB may also be included in BWP1. In this case, after one OD-SSB is set in BWP0, an OD-SSB may not be set in BWP1.
[0413] Method 2: When an OD-SSB can be configured for each dedicated BWP, only the BWP linked (associated) to that BWP can be used for measurement, even if there is an overlapping OD-SSB of another BWP in that BWP. For example, an OD-SSB configured together with the configuration of that BWP can be considered as an OD-SSB linked (or associated) to that BWP.
[0414] Figure 31 shows another example of setting OD-SSB.
[0415] Referring to FIG. 31, even if there are two OD-SSBs within a specific BWP, L1 / L2 / L3 commands (signaling) for OD-SSB activation / instruction / triggering may be directed only to the linked (or associated) OD-SSB when configuring the BWP. The terminal can perform measurements using the activated / instructed / triggered OD-SSB to generate / report CSI.
[0416] Proposal 6: Setup and operation plan for L1 / L3 measurement / reporting performed by OD-SSB.
[0417] There may be two types of OD-SSB configuration / instruction / (activation / instruction / triggering): i) a case where it is RRC-based through OD-SSB-Config, and ii) a case where it is MAC CE-based, in which one of the multiple lists of OD-SSB-Config (index of the said one list) is indicated through MAC CE.
[0418] In performing CSI-RS measurement / reporting of OD-SSB, when reportConfigType, a parameter indicating the time domain behavior of the reporting configuration, is set to periodic, conventionally, activation / deactivation of AO-SSB / CSI-RS was always performed based on RRC.
[0419] Regarding CSI-RS measurement / reporting of OD-SSB, OD-SSB is different from AO-SSB, which is always transmitted. If OD-SSB is configured based on RRC and then OD-SSB is enabled / instructed via MAC CE, the UE cannot expect periodic transmission of OD-SSB. Therefore, when performing CSI-RS reporting / measurement, if periodic CSI-reporting is configured, it is possible to limit the activation / instruction / triggering of periodic (periodic=ReportConfiguTYpe) OD-SSB CSI reporting / measurement by minimizing the activation of OD-SSB, SCELL activation, and OD-SSB configuration based on RRC.
[0420] In addition, when the UE periodically performs CSI measurements / reporting of the OD-SSB, if the transmission of the OD-SSB is deactivated, the OD-SSB can be deactivated only via RRC. By doing so, the operation of periodic CSI measurements / reporting of the OD-SSB can be consistently matched with the operation of the legacy AO-SSB, and no additional considerations may be required.
[0421] For example, if OD-SSB transmission via RRC is disabled, periodic CSI-report measurements / reports can also be disabled. Regarding the above / related matters, whether measurements continue even if OD-SSB reporting is discontinued can be considered a matter of UE implementation.
[0422] Semi-persistent CSI reporting / measurement and aperiodic CSI reporting / measurement can be performed simultaneously by activating / instructing OD-SSB through MAC CE.
[0423] Additionally, consideration can be made only when reportConfigType is set to 'Periodic'. If the CSI report / measurement is set to 'Semi-persistent' or 'aperiodic', you can enable / instruct / trigger OD-SSB only with MAC, and restrict disabling to MAC CE or RRC, or limit it to MAC only.
[0424] Method 1: When OD-SSB's reportConfigType is 'Periodic', measurements and reporting can always be enabled after CSI reporting settings are instructed / configured / defined along with RRC-based OD-SSB activation / instruction, and CSI reporting / measurements can also be disabled along with RRC-based OD-SSB deactivation, or the operation can be limited to be performed in this way.
[0425] Method 2: When triggering OD-SSB in RRC or thereafter, if a periodic reportConfigType related to CSI reporting is not set for the CSI measurement, OD-SSB cannot be disabled by RRC, or only MAC CE can disable OD-SSB. Alternatively, OD-SSB transmission can be disabled by RRC.
[0426] FIG. 32 illustrates a terminal operation according to the present disclosure.
[0427] Referring to Fig. 32, the SSB (=SS / PBCH block) can be classified into two types as described above (let's call them the first SSB and the second SSB for convenience). The first SSB is an SSB transmitted according to the existing method (e.g., an SSB transmitted at a frequency location provided by the absoluteFrequencySSB, which indicates the frequency of the SSB to be used for the corresponding serving cell), and the aforementioned AO-SSB may correspond to this.
[0428] The second SSB is an SSB that is transmitted upon need / request, for example, and is an SSB in which the activation of transmission is indicated by separate signaling (e.g., od-ssb-config or MAC CE).
[0429] First, regarding SSB, ssb-PositionsInBurst indicates the time-domain location where an SSB (SS-blocks) is transmitted within a half frame containing SS / PBCH blocks. ssb-PositionsInBurst may be provided in the form of a bit string (or bitmap) and may have a size of 4 bits, 8 bits, or 64 bits. Each bit of ssb-PositionsInBurst may correspond to an SS / PBCH block index in such a way that the first bit (leftmost bit) of the bit string (bitmap) corresponds to SS / PBCH block index 0 and the next bit corresponds to SS / PBCH block index 1. If a specific bit of ssb-PositionsInBurst is 1, it means that the SSB of the corresponding SS / PBCH block index is transmitted, and if the specific bit is 0, it means that the SSB of the corresponding SS / PBCH block index is not transmitted.
[0430] Regarding the second SSB, od-SSB-PositionsInBurst (which may also be denoted as od-ssb-PositionsInBurst) indicates the time-domain location where the OD-SSB (SS-blocks for the OD-SSB) is transmitted within a half frame containing SS / PBCH blocks. od-SSB-PositionsInBurst may be provided in the form of a bit string (or bitmap) and may have a size of 4 bits, 8 bits, or 64 bits. As described in ssb-PositionsInBurst, each bit of od-SSB-PositionsInBurst corresponds to an SS / PBCH block index. If a specific bit of od-SSB-PositionsInBurst is 1, it means that the OD-SSB of the corresponding SS / PBCH block index is transmitted, and if the specific bit is 0, it means that the OD-SSB of the corresponding SS / PBCH block index is not transmitted. Meanwhile, if od-SSB-PositionsInBurst is not provided, ssb-PositionsInBurst may indicate the time-domain location where the OD-SSB (SS-blocks for the OD-SSB) is transmitted within a half-frame containing SS / PBCH blocks.
[0431] As exemplified in FIG. 32 (a), when ssb-PositionsInBurst has, for example, an 8-bit size and its value is, for example, "01001100", the first SSBs (AO-SSBs) having SS / PBCH block indices 1, 4, and 5 are transmitted.
[0432] In this case, the transmission of OD-SSB is enabled (e.g., the activation of transmission for the second SSBs in the configured downlink BWP of the secondary cell is indicated by od-ssb-config or MAC CE), and if od-SSB-PositionsInBurst is given, for example, "11010100", then the second SSBs (OD-SSBs) having SS / PBCH block indices 0, 1, 3, or 5 will be transmitted. At this time, the terminal can receive the second SSB (OD-SSB) having an SS / PBCH block index 1 or 5, by assuming (determining in an equivalent sense) that the second SSB (OD-SSB) having an SS / PBCH block index 1 or 5 is quasi-co-located with respect to at least one of the Doppler shift, Doppler spread, average gain, average delay, delay spread, and spatial RX parameters, respectively. For example, the terminal assumes (determines) that the second SSB (OD-SSB) having SS / PBCH block index 1 is QCL with the first SSB (AO-SSB) having SS / PBCH block index 1, and the terminal assumes (determines) that the second SSB (OD-SSB) having SS / PBCH block index 5 is QCL with the first SSB (AO-SSB) having SS / PBCH block index 5.
[0433] In other words, if a specific second SS / PBCH block among the second (which may be expressed as 'second') SS / PBCH blocks provided by OD-SSB configuration information (e.g., OD-SSB-PositionsInBurst or a list of OD-SSB-Configs), has the same SS / PBCH block index as a specific first SS / PBCH block among the first (which may be expressed as 'first') SS / PBCH blocks of frequency location provided by a parameter (e.g., absoluteFrequencySSB) that indicates the frequency of the SS / PBCH block (SSB) to be used for the serving cell, the terminal assumes / determines that the specific first SS / PBCH block and the specific second SS / PBCH block are quasi-co-located (QCL).
[0434] The second SSB (OD-SSB) may be transmitted very infrequently or kept off for extended periods to conserve energy. If the terminal had to find a new beam or re-synchronize precisely every time the second SSB was activated, unnecessary energy consumption would occur. On the other hand, by assuming / determining that the second SSB, which has the same SS / PBCH block index as the first SSB, is QCLed with the first SSB, the reception success rate of the second SSB can be increased and energy consumption reduced by utilizing the synchronization / beam information obtained from the first SSB, which is always on (or more frequently). Furthermore, since the terminal can utilize the optimal reception beam direction used when receiving the first SSB when receiving the second SSB as well, it can reduce power consumption and increase measurement speed.
[0435] Meanwhile, in FIG. 32 (a), among the second SS / PBCH blocks, the second SSBs (OD-SSBs) with SS / PBCH block index 0 or 3 are in a state where the first SSB (AO-SSB) in QLC relationship has not been transmitted.
[0436] In this state, let us assume that the transmission of a new OD-SSB is activated as shown in Fig. 32 (b). For example, let us assume that "11010100" is indicated by od-SSB-PositionsInBurst (#1) and "11000101" is indicated by od-SSB-PositionsInBurst (#2). In this case, the terminal can assume / determine that the second SSB (OD-SSB) having SS / PBCH block index 0, 1, or 5 by od-SSB-PositionsInBurst (#2) is in a QCL relationship with the second SSB (OD-SSB) having SS / PBCH block index 0, 1, or 5 by od-SSB-PositionsInBurst (#1). For example, the second SSB (OD-SSB) having SS / PBCH block index 0 according to od-SSB-PositionsInBurst (#2) is in a QCL relationship with the second SSB (OD-SSB) having SS / PBCH block index 0 according to od-SSB-PositionsInBurst (#1), and the second SSB (OD-SSB) having SS / PBCH block index 1 according to od-SSB-PositionsInBurst (#2) is in a QCL relationship with the second SSB (OD-SSB) having SS / PBCH block index 1 according to od-SSB-PositionsInBurst (#1).
[0437] Here, according to ssb-PositionsInBurst, since the SSB (first SSB, AO-SSB) having SS / PBCH block index 0 is not transmitted, the second SSB (OD-SSB) having SS / PBCH block index 0 according to od-SSB-PositionsInBurst (#2) has no AO-SSB with which it has a QCL relationship. In this case, according to the method of the present disclosure, the terminal can assume / determine that the second SSB (OD-SSB) having SS / PBCH block index 0 according to od-SSB-PositionsInBurst (#2) has a QCL relationship with the second SSB (OD-SSB) having SS / PBCH block index 0 according to od-SSB-PositionsInBurst (#1). Through this, the terminal can receive / measure the OD-SSB efficiently while saving energy without a separate complex search process.
[0438] FIG. 33 illustrates a method of operation of a terminal related to OD-SSB reception.
[0439] Referring to FIG. 33, the terminal receives on-demand Synchronization Signal Block (OD-SSB) configuration information (S331).
[0440] The OD-SSB configuration information may be, for example, an OD-SSB-Config containing the aforementioned od-SSB-PositionsInBurst or a list of OD-SSB-Configs (od-SSB-ConfigToAddModList).
[0441] The terminal receives at least one SS / PBCH (Synchronization Signal / Physical Broadcast Channel) block (SSB) based on the OD-SSB configuration information, and based on the fact that among the specific SS / PBCH blocks provided by the OD-SSB configuration information (e.g., second SS / PBCH blocks), the SS / PBCH blocks have the same SS / PBCH block index, the terminal assumes / determines that the SS / PBCH blocks are quasi-co-located (QCL) (S332). Here, assuming and determining are used with the same meaning.
[0442] The terminal can determine that the SS / PBCH blocks having the same SS / PBCH index are quasi-co-located with respect to at least one of, for example, Doppler shift, Doppler spread, average gain, average delay, delay spread, and spatial RX parameters.
[0443] Regarding such terminal operation (in other words, a method of considering QCL (and / or beam characteristics) based on SSB ID), it has been described in Proposal 2.
[0444] The above OD-SSB setting information may include position information (e.g., od-SSB-PositionsInBurst) indicating the time domain positions of SS / PBCH blocks transmitted for OD-SSB within a half frame containing SS / PBCH blocks.
[0445] According to an embodiment, the OD-SSB setting information may include half-frame index information (od-SSB-HalfFrameIndex) indicating whether the OD-SSB is in the first half or the second half of the frame.
[0446] According to an embodiment, the OD-SSB setting information may include an offset (od-SSB-SFN-Offset) related to a system frame number (SFN).
[0447] According to an embodiment, the OD-SSB setting information may include information on the period of the SS / PBCH block (od-SSB-Periodicity).
[0448] When the aforementioned specific SS / PBCH blocks are referred to as second (i.e., second) SS / PBCH blocks, the terminal may assume / determine that the first SS / PBCH block and the second SS / PBCH block are quasi-co-located (QCL) based on the fact that the second SS / PBCH block among the second SS / PBCH blocks provided by the OD-SSB setting information has the same SS / PBCH block index as the first SS / PBCH block among the first (i.e., first) SS / PBCH blocks at the frequency location provided by the parameter (e.g., the aforementioned absoluteFrequencySSB) that indicates the frequency of the SS / PBCH block (SS / PBCH block: SSB) to be used for the serving cell.
[0449] Subsequently, the terminal may measure at least one SSB and generate and feed back a CSI (e.g., at least one of SSBRI, RSRP, or SINR). Depending on the embodiment, the method described in Proposal 3 or 5 may be applied to determine which SSB the terminal selects. Depending on the embodiment, the method described in Proposal 3 may be applied to determine which measurement is performed on the selected SSB. Additionally, depending on the embodiment, the setup and operation of L1 / L3 measurement / reporting for the SSB may be applied based on the method described in Proposal 6.
[0450] According to the present disclosure, power consumption of a terminal can be reduced. Since OD-SSBs are generally transmitted less frequently than AO-SSBs or only when necessary, if the terminal must find a new receiving beam and precisely synchronize it every time, the RF element must be kept on for a long time. On the other hand, according to the present disclosure, by assuming that the OD-SSB is QCL with the previously received SSB, the terminal can immediately reuse the receiving beam direction and synchronization information that the terminal already knows, and consequently, unnecessary power consumption of the terminal can be prevented by reducing meaningless search time.
[0451] In addition, through the QCL relationship, the terminal can immediately receive and measure the short burst of OD-SSB without missing it.
[0452] In addition, according to the present disclosure, by enabling the terminal to receive OD-SSB more effectively, the base station can reduce the number of SSB transmissions, and consequently contribute to energy saving of the base station.
[0453] Furthermore, through the present disclosure, the UE can perform CSI reporting settings without ambiguity regarding how to associate (configure) the measurement / reporting of OD-SSBs. From the perspective of the UE performing the measurement / reporting, if the beam characteristics and orientation are the same through QCL relationships, it may not be necessary to measure / report both SSBs, thereby providing operational convenience to the UE. To achieve this convenience, the UE's measurement / reporting operation can be simply controlled through proposals / methods for simple instruction / setting.
[0454] Regarding the setting of parameters related to OD-SSB transmission, the effects of signaling overhead reduction and power saving can also be expected.
[0455] FIG. 34 illustrates the signaling process and operation of a base station and a terminal related to OD-SSB transmission and reception.
[0456] Referring to FIG. 34, the base station transmits on-demand SSB (OD-SSB) configuration information to the terminal (S341). The OD-SSB configuration information may be, for example, an OD-SSB-Config or a list of OD-SSB-Configs including the aforementioned od-SSB-PositionsInBurst.
[0457] The base station transmits SSB#1 (e.g., an SSB having SS / PBCH block index #3) to the terminal (S342). Here, SSB#1 may be an AO-SSB having SS / PBCH block index #3 or an OD-SSB having SS / PBCH block index #3.
[0458] After that, the base station can transmit SSB#2 (e.g., an SSB having SS / PBCH block index #3) to the terminal (S343). Here, SSB#2 may be an OD-SSB having SS / PBCH block index #3.
[0459] In this case, the terminal assumes / determines that the SSB#1 and the SSB#2 have the same SS / PBCH block index (SS / PBCH block index #3), and that the SSB#1 and the SSB#2 are in a QCL relationship with respect to at least one of the Doppler shift, Doppler spread, average gain, average delay, delay spread, and spatial reception parameters (if applicable), and performs reception of SSB#2 (S344).
[0460] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.
Claims
1. Regarding the method, The terminal receives On-demand Synchronization Signal Block (OD-SSB) configuration information; and The terminal receives at least one SS / PBCH (Synchronization Signal / Physical Broadcast Channel) block based on the OD-SSB configuration information, A method characterized by the terminal determining that the SS / PBCH blocks are quasi-co-located (QCL) based on the fact that among the specific SS / PBCH blocks provided by the OD-SSB setting information, the SS / PBCH blocks have the same SS / PBCH block index.
2. A method according to claim 1, wherein the terminal determines that the SS / PBCH blocks having the same SS / PBCH index are quasi-co-located with respect to at least one of Doppler shift, Doppler spread, average gain, average delay, delay spread, and spatial RX parameters.
3. The method according to claim 1, wherein the OD-SSB setting information includes position information indicating the time domain positions of SS / PBCH blocks transmitted for OD-SSB within a half frame containing SS / PBCH blocks.
4. A method according to claim 1, wherein the OD-SSB setting information includes half-frame index information indicating whether the OD-SSB is located in the first half or the second half of the frame.
5. A method according to claim 1, wherein the OD-SSB setting information includes an offset related to a system frame number (SFN).
6. A method according to claim 1, wherein the OD-SSB setting information includes information regarding the period of the SS / PBCH block.
7. A method according to claim 1, wherein, when the specific SS / PBCH blocks are referred to as second SS / PBCH blocks, the terminal determines that the first SS / PBCH block and the second SS / PBCH block are quasi-co-located (QCL) based on the fact that the second SS / PBCH block among the second SS / PBCH blocks provided by the OD-SSB setting information has the same SS / PBCH block index as the first SS / PBCH block among the first SS / PBCH blocks at a frequency location provided by a parameter that indicates the frequency of the SS / PBCH block (SS / PBCH block: SSB) to be used for the serving cell.
8. The terminal (user equipment: UE) is, At least one transceiver; At least one memory; and It includes at least one processor operably coupled with the above-mentioned at least one memory and the above-mentioned at least one transceiver, The above at least one memory includes instructions that are executed by the at least one processor and cause the at least one processor to perform operations, wherein The above operations are: Receive On-demand Synchronization Signal Block (OD-SSB) configuration information; and It includes receiving at least one SS / PBCH (Synchronization Signal / Physical Broadcast Channel) block based on the above OD-SSB configuration information, A terminal characterized by determining that the SS / PBCH blocks are quasi-co-located (QCL) based on the fact that among the specific SS / PBCH blocks provided by the above OD-SSB configuration information, the SS / PBCH blocks have the same SS / PBCH block index.
9. A terminal according to claim 8, characterized in that the terminal determines that the SS / PBCH blocks having the same SS / PBCH index are quasi-co-located with respect to at least one of Doppler shift, Doppler spread, average gain, average delay, delay spread, and spatial RX parameters.
10. A terminal according to claim 8, wherein the OD-SSB setting information includes position information indicating the time domain positions of SS / PBCH blocks transmitted for OD-SSB within a half frame containing SS / PBCH blocks.
11. A terminal according to claim 8, wherein the OD-SSB setting information includes half-frame index information indicating whether the OD-SSB is located in the first half or the second half of a frame.
12. A terminal according to claim 8, wherein the OD-SSB setting information includes an offset related to a system frame number (SFN).
13. A terminal according to claim 8, wherein the OD-SSB setting information includes information regarding the period of the SS / PBCH block.
14. A terminal according to claim 8, wherein, when the specific SS / PBCH blocks are referred to as second SS / PBCH blocks, the second SS / PBCH block among the second SS / PBCH blocks provided by the OD-SSB setting information has the same SS / PBCH block index as the first SS / PBCH block among the first SS / PBCH blocks at a frequency location provided by a parameter indicating the frequency of the SS / PBCH block (SS / PBCH block: SSB) to be used for the serving cell, and the terminal determines that the first SS / PBCH block and the second SS / PBCH block are quasi-co-located (QCL).
15. The device is, At least one memory; and It includes at least one processor operably coupled to the above at least one memory, wherein The above at least one memory includes instructions that are executed by the at least one processor and cause the at least one processor to perform operations, wherein The above operations are: Receive On-demand Synchronization Signal Block (OD-SSB) configuration information; and It includes receiving at least one SS / PBCH (Synchronization Signal / Physical Broadcast Channel) block based on the above OD-SSB configuration information, An apparatus characterized by determining that the SS / PBCH blocks are quasi-co-located (QCL) based on the fact that the SS / PBCH blocks among the specific SS / PBCH blocks provided by the above OD-SSB setting information have the same SS / PBCH block index.
16. At least one computer-readable medium (CRM) comprising instructions that cause operations to be performed based on execution by at least one processor, wherein said operations are, Receive On-demand Synchronization Signal Block (OD-SSB) configuration information; and It includes receiving at least one SS / PBCH (Synchronization Signal / Physical Broadcast Channel) block based on the above OD-SSB configuration information, A CRM characterized by determining that the SS / PBCH blocks are quasi-co-located (QCL) based on the fact that among the specific SS / PBCH blocks provided by the above OD-SSB configuration information, the SS / PBCH blocks have the same SS / PBCH block index.
