Method performed by terminal or network in wireless communication system, and device therefor

Abstract

A method performed by a terminal, according to one embodiment of the present disclosure, comprises the steps of: acquiring system information in a first cell; transmitting, to a second cell, a random access preamble for requesting system information block 1 (SIB1) transmission of the second cell; and monitoring, in the second cell, downlink control information (DCI) related to a random access response on the basis of a random access-radio network temporary identifier (RA-RNTI), wherein the system information acquired in the first cell can include configuration information about a search space set of the second cell for the monitoring of the DCI.

Description

Method performed by a terminal or network in a wireless communication system and device therefor

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing wireless communication between terminals or networks in a wireless communication system.

[0002] The 5G mobile communications system, the successor to LTE (long-term evolution), is a new, clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. 6G mobile communications systems are being developed based on the underlying technologies of 5G mobile communications.

[0003] In NR, there is a cell defining (CD)-SSB (system information block) that provides configuration information for SIB1 (system information block1) scheduling, and a non-cell defining (NCD)-SSB that does not provide configuration information for SIB1 scheduling. The NCD-SSB provides information on the frequency location (e.g., sync raster) of the CD-SSB based on the parameter Kssb. The terminal can acquire SIB1 based on the CD-SSB at the corresponding frequency location.

[0004] Recently, in the NR Rel-19 standardization, on-demand SIB1 is being discussed as one of the topics for NES, and unlike the cell (hereinafter, Cell A) that transmits SIB1 periodically / fixedly, a cell (hereinafter, NES cell) that supports on-demand SIB1 transmission based on terminal request / base station judgment may be newly introduced.

[0005] The technical task to be achieved in the present disclosure is to provide a method and a device for efficiently performing a wireless signal transmission and reception process. As an example, a method for a terminal to request an On-Demand SIB1 from a cell supporting On-Demand SIB1 transmission and a network configuration for this purpose are provided.

[0006] In addition to the technical challenges described above, other technical challenges can be inferred from the description below.

[0007] According to one aspect of the present disclosure, a method performed by a terminal includes: acquiring system information from a first cell; transmitting a random access preamble to the second cell for requesting transmission of a system information block 1 (SIB1) of the second cell; and monitoring downlink control information (DCI) related to a random access response based on a random access-radio network temporary identifier (RA-RNTI) in the second cell, wherein the system information acquired from the first cell may include configuration information for a search space set of the second cell for monitoring the DCI.

[0008] The terminal can obtain information about the frequency location of the first SSB (synchronization signal block) of the first cell based on the second SSB (synchronization signal block) of the second cell.

[0009] The above terminal includes parameter k in the second SSB. SSB Based on the value being set to 30 for the first frequency range or 14 for the second frequency range, information on the frequency position of the first SSB can be obtained.

[0010] The terminal may determine a frequency offset value based on a first parameter for CORESET (control resource set) 0 included in the second SSB and a second parameter for search space set 0, and determine that the first SSB is provided at a position offset by an integer multiple of the frequency offset value from the frequency position of the second SSB.

[0011] The integer values ​​for the above integer multiples may be different for each of the first frequency range and the second frequency range.

[0012] The terminal can receive the first SSB in the first cell based on information about the frequency location of the first SSB.

[0013] The system information of the first cell can be obtained based on the first SSB.

[0014] The system information acquired from the first cell may further include at least one of information on whether the SIB1 is being transmitted on the second cell, a start time of the SIB1 transmission, and an end time of the SIB 1 transmission.

[0015] Transmission of the random access preamble for requesting the SIB1 transmission may be triggered based on a system information update in the second cell.

[0016] The terminal may receive a PDSCH (physical downlink shared channel) related to the random access response based on the DCI, and may receive the SIB1 in the second cell.

[0017] According to another aspect of the present disclosure, a non-transitory computer-readable recording medium having recorded thereon a program for performing the method described above may be provided.

[0018] According to another aspect of the present disclosure, a device comprises a memory configured to store instructions; and a processor configured to perform operations by executing the instructions, wherein the operations of the processor include obtaining system information from a first cell; transmitting a random access preamble to a second cell for requesting transmission of a system information block 1 (SIB1) of a second cell; and monitoring downlink control information (DCI) related to a random access response based on a random access-radio network temporary identifier (RA-RNTI) in the second cell, wherein the system information obtained from the first cell may include configuration information for a search space set of the second cell for monitoring the DCI.

[0019] The above device may further include a transmitter and receiver.

[0020] The above device may be a terminal operating in a wireless communication system.

[0021] The above device may be a processing device configured to control a terminal operating in a wireless communication system.

[0022] According to another aspect of the present disclosure, a method performed by a base station includes transmitting system information in a first cell; receiving a random access preamble requesting transmission of a system information block 1 (SIB1) of a second cell in the second cell; and transmitting downlink control information (DCI) related to a random access response based on a random access-radio network temporary identifier (RA-RNTI) in the second cell, wherein the system information transmitted in the first cell may include configuration information for a search space set of the second cell for transmission of the DCI.

[0023] According to another aspect of the present disclosure, a base station comprises a memory configured to store instructions; and a processor configured to perform operations by executing the instructions, wherein the operations of the processor include transmitting system information on a first cell; receiving a random access preamble requesting a system information block (SIB) 1 from a terminal in a second cell that provides the SIB 1 on an on-demand basis; and transmitting downlink control information (DCI) related to a random access response based on a random access-radio network temporary identifier (RA-RNTI) in the second cell, wherein the system information transmitted in the first cell may include configuration information for a search space set of the second cell for transmission of the DCI.

[0024] According to the present disclosure, signal transmission and reception can be efficiently performed in a wireless communication system. For example, by providing information for an OD SSB1 request to a second cell (e.g., NES cell) through system information of a first cell (e.g., Cell A), the OD SSB1 request procedure of a terminal can be performed more efficiently.

[0025] In addition to the technical effects described above, other technical effects can be inferred from the description below.

[0026] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

[0027] FIG. 2 illustrates an example of a communication system applicable to the present disclosure.

[0028] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0029] FIG. 4 illustrates 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.

[0030] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0031] Figure 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0032] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0033] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies.

[0034] Figure 9 illustrates a beam management procedure applicable to the present disclosure.

[0035] FIG. 10 illustrates an example of a sensing operation according to one embodiment of the present disclosure.

[0036] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present specification.

[0037] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification.

[0038] Figure 13 illustrates an example of the operation procedure of a base station supporting NES technology.

[0039] Figure 14 illustrates an example of a procedure for cell DTX / DRX operation.

[0040] Figure 15 illustrates an example of a procedure for CA operation using SSB-less SCell.

[0041] Figure 16 illustrates an example of a conditional handover (CHO) procedure.

[0042] Figure 17 illustrates an example of on-demand SSB transmission.

[0043] Figure 18 illustrates an example of SSB transmission of a base station operating multiple frequency bands.

[0044] Figure 19 illustrates a SIB1 transmission and reception procedure between a network and a terminal according to one embodiment.

[0045] FIG. 20 illustrates a flow of a method performed by a terminal according to one embodiment.

[0046] FIG. 21 illustrates a flow of a method performed by a base station according to one embodiment.

[0047] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0048] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0049] In this specification, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted identically to "at least one of A and B".

[0050] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0051] Additionally, parentheses used herein may mean "for example." Specifically, when "control information (ABC)" is indicated, "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" in this specification is not limited to "ABC," and "ABC" may be described as an example of "control information." Furthermore, even when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."

[0052] Additionally, in this specification, terms such as “first,” “second,” etc. are used only for the purpose of distinguishing one component from another component and are not used to limit the components, and do not limit the order or importance between the components unless specifically limited. Accordingly, a first component in one embodiment of this specification may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0053] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

[0054] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0055] In this specification, a terminal is a user equipment (UE) or a consumer-side device, and may also be referred to as a base station / second node / IAB node / first node that receives / transmits signals from / to a Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to an endpoint on the user side, or may correspond to an intermediate point between other endpoints. In communication between two points that are 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. A terminal may be a node with a fixed location, or a node with an unfixed location (or mobile).

[0056] In this specification, a base station (BS) is a device on the network side, and may also be called a second node / IAB node / x-NodeB (x-NodeB, x may be an abbreviation related to radio access technology (RAT)) / Transmission-Reception Point (TRP). A BS may correspond to a physical node or a logical node. A BS may correspond to an endpoint on the network side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a BS may correspond to a serving node. A BS may be a node with a fixed location, or a node with an unfixed location.

[0057] In this specification, higher layer parameters may be set for the terminal, preset, or predefined. For example, the base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capabilities to the base station as higher layer parameters. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0058] In this specification, the information / state / parameter being “configured or pre-configured” can be interpreted as the information / state / parameter being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, the information / state / parameter being “defined or pre-defined” can be interpreted as the information / state / parameter being known in advance or pre-stored at the base station and the terminal without signaling between the base station and the terminal.

[0059] The technology described in this specification can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0060] The technology described in this specification can be implemented with 6G wireless technology and applied to various 6G systems. For example, the 6G system can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0061] <Symbols, Abbreviations, Terms>

[0062] - PDCCH: Physical Downlink Control CHannel

[0063] - DCI: Downlink Control Information

[0064] - PDSCH: Physical Downlink Shared CHannel

[0065] - PUSCH: Physical Uplink Shared CHannel

[0066] - CSI: Channel state information

[0067] - RRM: Radio resource management

[0068] - SCS: Sub-carrier spacing

[0069] - RLM: Radio link monitoring

[0070] - DCI: Downlink Control Information

[0071] - CAP: Channel Access Procedure

[0072] - Ucell: Unlicensed cell

[0073] - TBS: Transport Block Size

[0074] - TDRA: Time Domain Resource Allocation

[0075] - SLIV: Starting and Length Indicator Value (This is an indicator value for the starting symbol index and number of symbols within the slot of the PDSCH and / or PUSCH, and can be set as a component of the entry that constitutes the TDRA field within the PDCCH that schedules the corresponding PDSCH and / or PUSCH.)

[0076] - BWP: BandWidth Part (can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). In addition, multiple BWPs can be configured on one carrier (the number of BWPs per carrier can also be limited), but the number of activated BWPs can be limited to a part of it (e.g., 1) per carrier.)

[0077] - CORESET: COntrol REsourse SET (refers to the time-frequency resource area where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0078] - REG: Resource element group

[0079] - SFI: Slot Format Indicator (An indicator indicating the symbol level DL / UL direction within a specific slot(s), transmitted through the group common PDCCH.)

[0080] - COT: Channel occupancy time

[0081] - SPS: Semi-persistent scheduling

[0082] - QCL: Quasi-Co-Location (QCL relationship between two reference signals means that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and Spatial Rx parameter obtained from one reference signal can be applied to another reference signal (or antenna port(s) of the corresponding RS). In the NR system, four QCL types are defined as follows. 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter} For any DL RS antenna port(s), the first DL RS is set as a reference for QCL type X (X=A, B, C, or D), and additionally, the second DL RS is set as a reference for QCL type Y (Y=A, B, C, or D but X≠Y) ) can be set as a reference to

[0083] - TCI: Transmission Configuration Indication (A TCI state includes the QCL relationship between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For the 'Transmission Configuration Indication' field in the DCI that schedules the PDSCH, the TCI state index corresponding to each code point that constitutes the field is activated by the MAC CE, and the TCI state setting for each TCI state index is set through RRC signaling. In the Rel-16 NR system, the TCI state is set between DL RSs, but in future releases, setting between DL RS and UL RS or UL RS and UL RS may be allowed. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0084] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields in the DCI that schedules the PUSCH. When transmitting a PUSCH, the UE can transmit the PUSCH using the same spatial domain transmission filter used for transmitting and receiving the reference signal linked to the corresponding SRS resource. At this time, the reference RS is set by RRC signaling through the SRS-SpatialRelationInfo parameter for each SRS resource, and SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0085] - TRP: Transmission and Reception Point

[0086] - TAG: Timing advance group

[0087] - PBCH: Physical Broadcast Channel

[0088] - SS: Synchronization Signal

[0089] - SSB: PBCH / SS block

[0090] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

[0091] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as IAB nodes, relays, and RF repeaters, as illustrated in the example in Figure 1, may be applied, or NTNs 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, or in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, while a network-controlled repeater may not only amplify and forward signals but also adjust transmission and reception settings based on information provided by the network. For example, an NTN node may correspond to a satellite or aircraft that provides 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.

[0092] Referring to Figure 1, a split RAN can support the division of a base station into a centralized unit (CU) and one or more distributed units (DUs). The CU and DU can correspond to logical units. The CU can be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DUs, various intermediate points can be introduced to compensate for this.

[0093] An intermediate point may correspond to a terminal or a base station, depending on its relationship to other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a unit (DU). The MT may connect the IAB node to a donor node. The unit (DU) of an IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to the terminal. In other words, an IAB node may correspond to a base station in its relationship to a user-side node, and to a terminal in its relationship to a network-side node.

[0094] In some examples of this specification, the description of a terminal can be equally applied not only to a user-side endpoint, but also to an intermediate point corresponding to a terminal in a relative relationship with a network-side endpoint. Similarly, in some examples of this specification, the description of a base station can be equally applied not only to a network-side endpoint, but also to an intermediate point corresponding to a base station in a relative relationship with a user-side endpoint. However, in most cases where there is no additional description of the operations of three or more entities, the communicating entities in this specification are briefly described as terminals and / or base stations (or first nodes and / or second nodes), and the terms terminal and / or base stations (or first nodes and / or second nodes) are interpreted to include / replace any endpoint or any intermediate point in relation to other nodes.

[0095] That is, in some examples of this specification, for the sake of simplicity of explanation, the subjects of the operation may be referred to as a base station and / or a terminal (or a first node and / or a second node). In addition, the terms base station and / or terminal (or a first node and / or a second node) may also be interpreted / replaced as in the following examples: For example, the base station (or a first node) and the terminal (or a second node) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.

[0096] In this specification, there may be zero or more intermediate points between the base station and the terminal. If intermediate points exist, they may be IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. An intermediate point may be a node with a fixed location or a node with an unfixed location.

[0097] Figure 2 illustrates a communication system applicable to the present disclosure.

[0098] The communication system (100) of FIG. 2 includes a wireless device (110), a network device (120), and a network (130). Here, the wireless device (110) refers to a device that performs communication using a wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G), and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Things) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point.The network device (120) may correspond to a base station (or second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may act as a network device (120) to another wireless device (110).

[0099] Wireless devices (110a to 110f) can be connected to a network (130) via a network device (120). AI technology can be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) via a network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR), or a 6G network. The wireless devices (110a to 110f) can communicate with each other via the network device (120) / network (130), but can also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Additionally, IoT devices (110f) (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (110a to 110f).

[0100] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120), network devices (120) / network devices (120). Here, the wireless communication / connection can be established through various wireless access technologies such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless device and the network device / wireless device, and the network device and the network device can transmit / receive wireless signals to each other. For example, the wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various descriptions of the present disclosure, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.

[0101] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0102] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208).

[0103] The processor (202) controls the memory (204) and / or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including second information / signal via the transceiver (206), and then store information obtained from signal processing of the second information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may store software code including instructions for performing some or all of the processes controlled by the processor (202), or for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. The transceiver (206) may be coupled to the processor (202) and may transmit and / or receive wireless signals via at least one antenna (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF (radio frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0104] Hereinafter, the hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., a functional layer such as physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and service data adaptation protocol (SDAP)). At least one processor (202) may generate at least one Protocol Data Unit (PDU) and / or at least one Service Data Unit (SDU) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) may generate a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) can generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this document, and provide the signal to at least one transceiver (206). At least one processor (202) can receive a signal (e.g., a baseband signal) from at least one transceiver (206) and obtain the PDU, SDU, message, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document.

[0105] At least one processor (202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The at least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in the at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be included in the at least one processor (202), or may be stored in at least one memory (204) and driven by the at least one processor (202). The descriptions, functions, procedures, suggestions, methods and / or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.

[0106] At least one memory (204) can be connected to at least one processor (202) and can store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The at least one memory (204) can be configured as a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory, a hard drive, a register, a cache memory, a computer readable storage medium and / or a combination thereof. The at least one memory (204) can be located internally and / or externally to the at least one processor (202). In addition, the at least one memory (204) can be connected to the at least one processor (202) via various technologies such as a wired or wireless connection.

[0107] At least one transceiver (206) can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed in this document from at least one other device. For example, at least one transceiver (206) can be connected to at least one processor (202) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. In addition, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts 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).For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

[0108] The components of the wireless device described with reference to FIG. 3 may be referred to by different terms in terms of functionality. For example, the processor (202) may be referred to as a control unit, the transceiver (206) as a communication unit, and the memory (204) as a storage unit. In some cases, the communication unit may be used to mean at least a portion of the processor (202) and the transceiver (206).

[0109] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least a portion of various devices. For example, the structure of the wireless device illustrated in FIG. 3 can be at least a portion of various devices described with reference to FIG. 2 (e.g., a robot (110a), a vehicle (110b-1, 110b-2), an XR device (110c), a portable device (110d), a home appliance (110e), an IoT device (110f), an AI device / server (110g)). Furthermore, according to various embodiments, in addition to the components illustrated in FIG. 3, the device may further include other components.

[0110] For example, the device may be a portable device such as a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), or a portable computer (e.g., a laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., an audio input / output port, a video input / output port), and an input / output unit for inputting and outputting image information / signals, audio information / signals, data, and / or information input from a user.

[0111] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired / wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting, and a position measurement unit that obtains location information of the mobile device through a global positioning system (GPS) and various sensors.

[0112] For example, the device may be an XR device such as an HMD, a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that obtains control information, data, etc. from the outside and outputs the generated XR object, and a sensor unit that senses status information, environmental information, and user information of the device or the surroundings of the device.

[0113] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc. types depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a driving unit that performs various physical actions, such as moving the robot joints.

[0114] For example, the device may be an AI device such as a TV, a projector, a smartphone, a PC, a laptop, a digital broadcasting terminal, a tablet PC, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, digital signage, a robot, a vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, and a training unit that trains a model composed of an artificial neural network using learning data.

[0115] The structure of the wireless device illustrated in FIG. 3 may be understood as a part of a terminal (or first node), or as a part of an intermediate point, or as a part of a base station (or second node). If the device illustrated in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and / or back haul communications. However, if the front haul and / or back haul communications are based on wireless communications, at least one transceiver (206) illustrated in FIG. 3 may be used for front haul and / or back haul communications, and a wired transceiver may not be included.

[0116] FIG. 4 illustrates 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.

[0117] The second node of FIG. 4 supports dynamic spectrum sharing (DSS), which can provide connectivity to both nodes implementing 6G technology and nodes implementing pre-6G wireless communication technologies (e.g., 5G, 4G). That is, the first node of FIG. 4 can implement either 6G technology or pre-6G wireless communication technologies (e.g., 5G, 4G). Furthermore, the first node and / or the second node can support full duplex mode as well as non-overlapping full duplex mode.

[0118] 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 operations of the terminal (110) and the base station (120) transmitting and / or receiving data and operations performed prior thereto are illustrated. However, the operations of Fig. 4 are not limited to operations between the terminal and the base station, and may be interpreted as operations between the first node and the second node. In addition, although Fig. 4 illustrates direct wireless signal transmission and reception operations between the terminal (110) and the base station (120), one or more intermediate points may exist between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0119] Referring to FIG. 4, the terminal (110) and the base station (120) can perform synchronization (401). For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect a synchronization signal for connection to at least one base station transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals classified according to structure or purpose (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 (110) can confirm the boundary of a unit (e.g., a frame, a subframe, a slot, and / or a symbol) constituting a wireless signal transmission of the base station (120) and obtain information (e.g., a cell identifier) ​​about the base station (120).

[0120] The terminal (110) can obtain system information transmitted from the base station (120) (403). The system information is information related to the properties, characteristics, and / or capabilities of the base station (120) required to access the base station (120) and use the service, and can be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., channel used, whether provided on-demand), etc., and can be classified into, for example, first system information (e.g., master information block (MIB), primary system information), second system information (e.g., system information block (SIB), secondary system information), etc. If necessary, the terminal (110) can transmit a signal requesting system information before receiving the system information. However, the request and provision of system information can be performed after the random access procedure described below.

[0121] The terminal (110) and the base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for the random access procedure based on information related to a channel for the random access procedure of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) can transmit a first message (e.g., a preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., an RAR message, MSG2), transmit a third message (e.g., MSG3) including information related to the terminal (110) (e.g., identification information) to the base station (120) 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 and third messages may be transmitted and received as one message, or the second and fourth messages may be transmitted and received as one message.

[0122] The terminal (110) and the base station (120) can perform signaling of control information (407). Here, the control information can be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

[0123] The terminal (110) and the base station (120) can transmit and / or receive data (409). In other words, the terminal (110) and the base station (120) can process, transmit, and / or receive data based on signaling of control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0124] <6G System Core Technologies>

[0125] The 6G (wireless) system aims to provide (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0126] As core implementation technologies of the 6G system, 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.

[0127] artificial intelligence

[0128] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0129] The following describes a functional framework for AI / ML operations.

[0130] Below, to explain AI (or AI / ML) more specifically, the terms can be defined as follows.

[0131] - Data collection: Data collected from network nodes, management entities, or terminals as a basis for AI model training, data analysis, and inference.

[0132] - 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.

[0133] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent the data and obtain a trained AI / ML model for inference.

[0134] - AI / ML Inference: The process of making predictions or inducing decisions based on collected data and the AI ​​model using a trained AI model.

[0135] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updates, etc.) can be divided into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identified by the network, and the network can direct the activation / deactivation / fallback / switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified by the network, and the network / terminal can activate / deactivate / select / switch AI / ML models based on the model ID.

[0136] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0137] In particular, Figure 5 illustrates a general functional architecture relevant to both Functionality-based LCM and Model-based LCM. Some of the functions or some of the data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.

[0138] Referring to FIG. 5, a general functional framework can be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).

[0139] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) can perform data preparation based on raw data and 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 (10) may be performed by a single entity (e.g., terminal, network node, etc.) or may be performed by multiple entities.

[0140] Here, training data (11) refers to data required as input for the AI / ML Model Training function (20). Monitoring data (12) refers to data required as input for the Management (30) of the AI / ML model or AI / ML function. Inference data (13) refers to data required as input for the AI / ML Inference function (30).

[0141] The Model Training function (20) 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 the AI / ML model testing procedure. The Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming, and transformation) based on the Training Data (11) transferred from the Data Collection function (10), if necessary.

[0142] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to pass a trained, validated and tested AI / ML model to the Model Storage function (50) or to pass an updated version of the model to the Model Storage function (50).

[0143] The Management function (30) is a function that supervises the operation of the AI / ML model or AI / ML function. In addition, the Management function (30) may perform decisions to ensure appropriate inference operations based on data received from the Data Collection function (10) (i.e., Monitoring Data (12)) and / or data received from the Inference function (40) (i.e., Inference Output (41)).

[0144] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include selection / (de)activation / switching of an AI / ML model or AI / ML-based function, and may also include fallback to non-AI / ML operations (i.e., not relying on the inference process).

[0145] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).

[0146] A Performance Feedback / Retraining Request (31) refers to information required as input to the Model Training function (20) (e.g., for the purpose of (re)training or updating the model).

[0147] The Inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., Inference Data (13)) provided by Data Collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) may also be performed based on the Inference Data (13) delivered by Data Collection (10). If necessary, the Inference function (40) may also perform data preparation (e.g., data preprocessing and cleaning, forming, and transformation) based on the Inference Data (13) provided by Data Collection function (10).

[0148] Inference Output (41) is data used in the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of the AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0149] The Model Storage function (50) stores a learned / updated model that can be used to perform the Inference function (40). The Model Storage function (50) illustrated in FIG. 5 can be used as a reference point (if any) when applicable to protocol termination, model transmission / delivery, and related processes. Furthermore, the Model Storage function (50) is merely an example and is not intended to limit the storage location of actual AI / ML models, and may be omitted.

[0150] Model Transfer / Delivery (51) is used to transfer AI / ML models to inference functions.

[0151] The level of cooperation can be defined as follows depending on the capability of AI / ML functions between multiple nodes, and variations due to combination of multiple levels or separation of any one level are also possible.

[0152] Cat 0a) No collaboration framework: AI / ML algorithms are purely implementation-based and do not require any changes to the wireless interface.

[0153] Cat 0b) This level corresponds to a framework with a modified wireless interface tailored to efficient implementation-based AI / ML algorithms, but without collaboration.

[0154] Category 1) involves inter-node support to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from another node (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0155] Category 2) Joint AI / ML tasks can be performed across multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0156] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and not all functions and / or all data / information / command signals illustrated in FIG. 5 may be performed within a specific node, but only some of them may be performed.

[0157] AI / ML models can be divided 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.

[0158] A one-side model can refer to an AI / ML model in which inference is performed entirely by a single node (e.g., a terminal or network). Here, AI / ML model training can also be performed entirely by a single node. AI / ML model training and inference can be performed by the same node, or they can be performed by separate nodes.

[0159] 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 refers to inference being performed jointly across multiple nodes. For example, the first part of the inference may be performed by a first node, and the remaining part by a second node. Two-side models can be categorized into several types depending on the training method of the AI / ML model, as follows:

[0160] - First type: AI / ML models 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 / objects.

[0161] - 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 part) and model reconstruction (CSI compression by sub-use case) 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).

[0162] - Third type: Separate training of AI / ML models can be performed on multiple nodes (e.g., networks and terminals). Separate training may mean that training begins sequentially on one node and continues on other nodes. In this case, the first node first performs the AI / ML model and shares the training data with the second node. The second node can then use the shared training data to perform the AI / ML model. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0163] Figure 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0164] The operations described below can be described / interpreted based on the AI / ML model proposed in this specification, as shown in Fig. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for the AI / ML model). In addition, unless specifically limited, the AI / ML model can correspond to a one-side model in which inference is entirely performed by a single node, or a two-side model in which joint inference is performed by multiple nodes.

[0165] First signaling (601): In the description below, the signaling (e.g., information / data / channel / signal, etc.) or 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 the first signaling (601) used to perform an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to training data for training (i.e., generation and / or reconstruction) the AI / ML model of FIG. 5, or correspond to inference data used for inference of the AI / ML model, or correspond to feedback for 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 specification, the first signaling (601) may be omitted. If a one-side model is used in the present specification, the one-way / two-way signaling (set) in the present specification may correspond to the signaling of the first signaling (601). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the first signaling (601), and also, a repetitive signaling operation may correspond to the first signaling (601).

[0166] For example, in AI / ML model-based beam management (BM), if a base station predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from a terminal. Furthermore, if a terminal predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0167] AI / ML model-based operation (602): In the description below, an operation (e.g., calculation, selection, prediction, etc.) in a specific node (e.g., terminal, network, etc.) or a joint operation (e.g., calculation, selection, prediction, etc.) in multiple nodes (e.g., terminal, network, etc.) may correspond to an AI / ML model-based operation (602) based on one or more functions in the functional framework of the AI / ML model, even if not mentioned separately. For example, it may correspond to training (i.e., generation and / or reconstruction) of the AI / ML model of FIG. 5 or inference of the AI / ML model, etc. When a one-side model is used, an operation performed by a single node in the present specification may correspond to an AI / ML model-based operation (602), and also, when a two-side model is used, a joint operation performed by multiple nodes in the present specification may correspond to an AI / ML model-based operation (602).

[0168] For example, in an AI / ML model-based BM, the base station can use quality / intensity information for multiple beams received from the terminal as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model. Furthermore, the terminal can measure multiple beams received from the base station and use the measurement results as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model.

[0169] Second signaling (603): In the description 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 a second signaling (603) or a set of signaling generated due to (as a result of) an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to an output resulting from inference of the AI / ML model in FIG. 5. If signaling between nodes is not required as a result of an operation based on an AI / ML model in this specification, the second signaling (603) may be omitted. If a one-side model is used in this specification, a one-way / two-way signaling (set) in this specification may correspond to the second signaling (603). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the second signaling (603), and also, a repetitive signaling operation may correspond to the second signaling (603).

[0170] For example, in an AI / ML model-based BM, the base station can transmit to the terminal the beam(s) predicted based on the AI / ML model as candidates so that the terminal can determine the optimal beam. Furthermore, the terminal can report to the base station the beam(s) predicted based on the AI / ML model to request the base station to transmit the candidate beams as candidates for determining the optimal beam.

[0171] THz communication (terahertz communication)

[0172] Data rates can be increased by increasing bandwidth. This can be achieved by utilizing sub-THz communications with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0173] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0174] Transmitting system information (i.e., information related to the properties, characteristics, and / or capabilities of a BS required to use a service, such as MIB, SIB, etc.) in the THz frequency band may be inefficient because, as the beam width becomes narrower in high frequency bands, more beam sweeps must be performed to cover the entire area of ​​the cell. 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 such as that illustrated in FIG. 8 may be used.

[0175] Figure 8 illustrates an example of a procedure for transmitting system information for THz communications to which the present disclosure applies. While this example was developed with THz in mind, it is also applicable to 6G communication environments where THz is not applicable. Furthermore, the procedure illustrated in Figure 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Figure 8.

[0176] Referring to FIG. 8, the base station can transmit system information of cell #1 through cell #2 (801). That is, the base station provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a non-THz frequency band. Here, the system information can include at least one information / state / parameter / setting generated in each of a higher layer and a physical layer. For example, the at least one information / state / parameter / setting generated in the higher layer can include at least one of SFN, 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 subcarrier spacing, and the at least one information / state / parameter / setting generated in the physical layer can include at least one of SFN, half frame indicator, and SSB index. However, this is merely an example, and system information may include information / status / parameters / settings related to Cell #1 / Cell #2 generated from various types of physical layers / upper layers. For this purpose, as an example, Cell #1 and Cell #2 may have a relationship as a secondary cell and a primary cell.

[0177] The UE can acquire synchronization for cell #1 (803). Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information. However, since the system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, the UE can acquire synchronization based on the system information. However, unlike FIG. 8, in another example, synchronization acquisition can be performed before step 801.

[0178] The UE may transmit a signal for accessing cell #1 (805). For example, the signal may include information for accessing cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) may be identified through system information. Thereafter, the UE and the base station may perform an access procedure for cell #1 and communicate (807). During this process, operations according to various embodiments described below may be performed.

[0179] The procedure described with reference to FIG. 8 may be performed when UE (801) first accesses cell #1 of the base station. Alternatively, a similar procedure may be performed when UE (801) hands over to cell #1 of the base station. However, in the case of handover, the system information of cell #1 may be received from a cell of a base station other than cell #2 of the base station.

[0180] Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations must use extremely sharp beams. The use of sharp beams means that terminals and base stations must perform beam control in addition to beamforming, and the number of beams used increases significantly. Consequently, it takes a very long time to align the transmit and receive beams between the base station and terminals. Furthermore, if the beam alignment between the base station and terminals is misaligned due to the movement or movement of the terminals, frequent re-alignment of the beams is required, which can lead to link instability. Accordingly, a beam management procedure, as illustrated in FIG. 9 below, may be employed.

[0181] FIG. 9 illustrates 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 the present disclosure is applicable to a 6G communication environment. In addition, the procedure illustrated in FIG. 9 can be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (setting) information', 'spatial domain filter', 'spatial domain transmission filter', 'spatial domain reception filter', or / and a term having an equivalent technical meaning that can distinguish the 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.).

[0182] Referring to FIG. 9, a base station can configure resources for beam management (901). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from existing downlink signals / channels for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can be a different port from a port for transmitting existing downlink signals / channels (e.g., synchronization signals (e.g., SSB, etc.), data channels (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 can be included in the technical concept according to the present embodiment.

[0183] The base station can transmit measurement signals using multiple transmission beams (903). For example, the measurement signals can include at least one of a reference signal and a synchronization signal. At this time, the measurement signals can be transmitted as many times as the number of beams that require measurement, and can be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, the multi-beam transmission can be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

[0184] The UE may transmit a feedback signal to the base station (905). The feedback signal indicates at least one beam selected by the UE. The UE may select at least one preferred beam based on the received measurement signals. The UE and the base station may communicate (907). At this time, the UE and the base station may communicate using the previously selected beam. If channel reciprocity is established, the transmission beam of the UE may also be determined through operations 903 and 905, and thus the transmission of the UE may also be performed using the beam selected in operation 905. If channel reciprocity is not established, a procedure including transmission of measurement signals by the UE and transmission of a feedback signal by the base station may be performed first to determine the transmission beam of the UE. In operation 907, operations according to various embodiments described below may be performed.

[0185] Integrated Sensing and Communication (ISAC)

[0186] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a networked device to connect to the object, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, i.e., sensing operations, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing offers an opportunity to enhance existing communication systems from a communications network to a wireless communication and sensing network.

[0187] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 can be combined with various embodiments of the present disclosure. Specifically, FIG. 10(a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and sensing transmitter (e.g., bistatic sensing).

[0188] For example, in a wireless communication system based on a 6G network of the present specification, referring to FIG. 10(a), 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. 10(b), the sensing transmitter and the sensing receiver may be configured to be included in different base stations, different terminals, or each terminal and base station.

[0189] In this regard, the following six types of sensing modes can be defined based on whether the sensing transmitter and sensing receiver are included in the base station or the terminal, respectively.

[0190] - Mode 1: A mode in which the sensing transmitter and sensing receiver are contained in a single base station (e.g., base station-based sensing mode in monostatic mode).

[0191] - Second mode: A mode in which the sensing transmitter is included in a 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).

[0192] - Mode 3: 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).

[0193] - Mode 4: 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).

[0194] - Mode 5: A mode in which the sensing transmitter and sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode).

[0195] - 6th mode: A mode in which the sensing transmitter is included in a first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode).

[0196] In a wireless communication system based on a 6G network of the present specification, one or more of the six types of sensing modes described above may be utilized independently / in combination.

[0197] In relation to the sensing operation in FIG. 10, the sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or an environment around 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 a 6G network of the present specification. The sensing receiver may receive a signal scattered / reflected by one or more objects (and / or an environment around the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signals, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing results may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment around the objects). The sensing results generated / obtained in this way may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided in the wireless communication system based on the 6G network of the present specification, or may be provided / disclosed to a trusted third party.

[0198] Additionally, the sensing operation in FIG. 10 is described as a representative example of the operation in a wireless communication system based on a 6G network, but can be extended and applied to cases where terminals / base stations / signals based on networks of previous generations (e.g., 4G, 5G, etc.) are utilized.

[0199] Additionally, with respect to the wireless sensing described herein, in a wireless communication system based on a 6G network of the present specification, time / frequency resources for sensing operations and time / frequency resources for general communications (e.g., UL / DL / sidelink-based communications, etc.) may be scheduled / configured separately.

[0200] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0201] Referring to FIG. 11, time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 10) can be set / allocated separately from time / frequency resources (hereinafter, communication resources) for general communication.

[0202] For example, as illustrated in FIG. 11, sensing resources can be set / allocated in units of symbols in the time domain and / or resource blocks in the frequency domain. Resources other than those for which the sensing resources are set / allocated can be utilized as resources for general communication. That is, sensing resources and communication resources can be set / allocated based on a time-division multiplexing (TDM) scheme and / or a frequency-division multiplexing (FDM) scheme in terms of the operation of the base station / terminal. Additionally or alternatively, unlike what is illustrated in FIG. 10, sensing resources can also be set / allocated based on other units in the time domain (e.g., slots, frames, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarriers, carriers, absolute frequencies (MHz, GHz), etc.).

[0203] Additionally or alternatively, in connection with the setting / allocation / scheduling of resources for general communication as described herein, the relationship between the resources and the aforementioned sensing resources may need to be considered. For example, when setting / allocating resources for general communication according to the embodiment(s) of the present disclosure, the resources may be set / allocated to rate-match or puncture the resource region corresponding to the sensing resource. For example, when scheduling resources for general communication according to the embodiment(s) of the present disclosure, the resources may be scheduled so as not to overlap with the resource region corresponding to the sensing resource. If the resources for general communication according to the embodiment(s) of the present disclosure and the resource region corresponding to the sensing resource are set / allocated / scheduled to overlap, one or both operations may be dropped, skipped, or postponed based on priorities, predefined rules, etc. That is, in the embodiment(s) of the present specification, it may be desirable that resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) are set / allocated / scheduled so as not to overlap with the sensing resources described above.

[0204] Additionally, various channel modeling methods may be applied in connection with the wireless sensing described herein. Channel modeling related to sensing may refer to configuring a path for transmitting and receiving sensing signals and / or scattered / reflected signals, taking into account the object being sensed and / or the environment in which the object resides. Channel modeling may be related to the performance / requirements of sensing in wireless communication systems, and thus may be an important factor in validating the sensing function.

[0205] Channels related to sensing can be divided into channels between an object (e.g., a target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and the sensing transmitter / receiver. In this regard, channel modeling related to sensing can be divided based on the sensing mode (e.g., the six types of modes described above), whether there is an object / 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 the environment in a base station / terminal-based monostatic sensing mode, and channel modeling for the environment in a base station / terminal-based bistatic sensing mode can be configured and optimized differently. For example, when various sensing scenarios are classified, channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios can be divided, etc. 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 geometric channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometric 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 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.

[0206] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0207] For example, in a wireless communication system based on a 6G network of the present specification, in the case of a sensing operation in which a terminal participates, the base station may need to confirm (1205) the capability of the terminal for the sensing operation. In this regard, the terminal may be configured to report capability information on whether it supports the sensing operation to the base station. Additionally or alternatively, if the terminal is defined in advance in the standard as supporting the sensing operation, the procedure may be omitted. In addition, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information on whether it supports the sensing operation to an entity that configures / controls its sensing operation (e.g., a network entity at an upper level / layer of the base station).

[0208] For example, the base station can perform signaling with the terminal to exchange configuration information related to the sensing operation. For example, the base station can set / instruct the terminal about the mode of the sensing operation (e.g., based on the six types of modes described above), the subject of the sensing operation (e.g., sensing transmitter, sensing receiver), the resource of the sensing operation (e.g., sensing resource as in FIG. 11), the target of utilizing the sensing result (e.g., type of wireless sensing service based on 6G network, trusted third party), channel modeling for sensing (e.g., channel between the base station / terminal and object / environment), etc. (1210). For example, the base station can also set / instruct such information from a network entity at an upper level / layer of the base station.

[0209] For example, the base station and / or the terminal may perform a sensing operation based on the set / instructed information (1215). For example, the base station and / or the terminal may, as a sensing transmitter and / or a sensing receiver, perform procedures such as transmitting a sensing signal, receiving a scattered / reflected signal, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, as in FIG. 9 described above. For example, in the operations of the base station / terminal described herein, the sensing result provided through the sensing operation may be utilized.

[0210] < Network Energy Saving, NES >

[0211] Network Energy Saving Technology of Rel-18

[0212] Energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing operational expenditures (OPEX) for telecommunications companies. In particular, the introduction of 5G communications will require higher transmission rates, necessitating base stations to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached as high as 20% of total OPEX. Accordingly, 5G systems are adopting various technologies to reduce energy consumption, known as network energy savings (NES), and the standardization of related technologies will continue.

[0213] Depending on the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time domain, controlling transmission / reception resources for UE-common or UE-specific signals / channels, changing the amount of frequency domain resources, controlling transmission power, or turning on / off antenna ports, transmission-reception points (TRPs), etc. in the spatial domain.

[0214] Figure 13 illustrates an example of the operation procedure of a base station supporting NES technology.

[0215] Referring to Fig. 13, the base station can identify the NES solution(s) to be applied (1305). The NES solution(s) may be related to control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. The NES solution(s) to be applied may be adaptively selected or predefined based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.). The base station that identified the NES solution(s) can perform signaling for the NES (1310). The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information about the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of the NES operation to at least one terminal. In addition, the base station may receive capability information related to the NES from at least one terminal. Thereafter, the base station performs operations for the NES. At this time, the base station can perform operations for the NES based on the previously performed signaling (1315). That is, based on the system information, configuration information, and control information transmitted through the signaling, the base station can turn on / off the transmission and reception of specific signals, turn on / off elements in the spatial domain, or adjust resources for the transmission and reception of measurement signals.

[0216] Through a procedure similar to that in Fig. 13, NES technology can be implemented. Examples of NES solutions that can be implemented through a procedure similar to that in Fig. 13 are as follows.

[0217] - Intra-system energy saving solution: A RAN node can request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or can perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).

[0218] - Inter-system energy saving solution: NG-RAN nodes that own capacity booster cells can autonomously transition those cells to an inactive state.

[0219] - SSB-less SCell solution: If SSB or SMTC (SSB-based RRM measurement timing configuration) configuration is not provided for the SCell, the UE can obtain timing reference and AGC source from another serving cell. In FR1 or FR2, the base station can configure intra-band CA or inter-band CA including the SCell without SSB transmission, in which case the SSB / SIB transmission can be triggered by the WUS (wake up signal) of the UE. Accordingly, since the period of common channels / signals such as SSB is increased, the base station can stay in the sleep state for a longer time.

[0220] - Cell DTX / DRX solution: In order to reduce the downlink transmission / uplink reception activity time of the base station, a common periodic cell DTX / DRX pattern (e.g., active and inactive periods) can be set for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern can be set and activated separately, and up to two cell DTX / DRX patterns can be set per MAC entity. When cell DTX is set and activated, at least one of monitoring for SPS opportunities or monitoring PDCCH can be stopped during the cell DTX inactivity period. When cell DRX is set and activated, at least one of transmission on CG resources or SR transmission can be stopped during the cell DRX inactivity period. Cell DTX / DRX can be activated / deactivated via RRC signaling or L1 group common signaling.

[0221] Parameters such as active duration and cycle may be configured for cell DTX / DRX. The active duration is the period during which the UE receives a PDCCH or SPS opportunity and waits to transmit SR or CG, and the cycle specifies the periodic repetition of the active duration and inactive duration. When both cell DTX and cell DRX are configured, parameters such as active duration and cycle are common. If the base station recognizes an emergency call or a public safety-related service (e.g., MPS or MCS), the network may release or deactivate the cell DTX / DRX configuration so as not to affect the service. In addition, at least some overlap is required between the active duration of the connected mode DRX of the UE and the active duration of the cell DTX / DRX. For example, the connected mode DRX cycle of the UE may be a multiple of the cell DTX / DRX cycle, or vice versa.

[0222] - Conditional handover (CHO) solution: A CHO procedure performed in a way that the execution of the handover is determined by the UE is used while the NES technology is applied (e.g., when the cell activates or deactivates cell DTX / DRX). In this case, the UE can use an NES-specific CHO event to initiate CHO for a candidate cell, and the reception of a DCI that activates the CHO condition(s) set by the NES event indication can be applied as an additional triggering condition for this.

[0223] - Spatial and power domain adaptation solution: To support the gNB for transceiver muting and / or transmit power adaptation, the UE may be configured to report multiple CSI entries in a CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset between a data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, the CSI configuration, measurement, and / or reporting behavior may be affected.

[0224] Cell DTX / DRX

[0225] To operate a base station in sleep mode for a relatively long period of time without frequent wake-ups, a base station DTX / DRX has been proposed for NES purposes. The base station can reduce energy consumption by utilizing DTX transmission in low system load situations by setting a cell DTX and setting the on-duration of the C-DRX of terminals within the active period of the cell DTX. Figure 14 illustrates an example of a procedure for cell DTX / DRX operation.

[0226] Referring to FIG. 14, the base station transmits system information to the terminal (1401), and the terminal checks information related to cell DTX / DRX (1402). For example, the system information may include MIB, SIB1, etc. In relation to NES technology, the MIB may include information related to cell barring (e.g., cellBarred), and the 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 barring status. If cellBarred of MIB is set to barred and cellBarredNES is absent in SIB1, the terminal supporting NES cell DTX / DRX can treat the cell as barred and perform cell reselection to another cell. On the other hand, if cellBarred of 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 barred.

[0227] In the case of FIG. 14, it is assumed that the terminal has the capability to support NES cell DTX / DRX, and the cellBarred of the MIB is set to notBarred, or the cellBarred of the MIB is barred and cellBarredNES is included in SIB1. Accordingly, the terminal performs a random access procedure to connect to the base station (1403), and can perform communication thereafter. 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 (1404). The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). Additionally, the configuration information may further include information for receiving and interpreting cell DRX / DRX-related control information (e.g., DCI-related information).

[0228] Thereafter, the base station transmits control information related to cell DTX / DRX to the terminal (1405). The control information related to cell DTX / DRX may include DCI having a designated format (e.g., format 2_9). If an operation for a serving cell according to at least one of the cell DTX operation and the cell DRX operation is configured by configuration information (e.g., cellDTXDRX-Config), the terminal may check a set of search spaces (e.g., a set of Type3-PDCCH CSS) for monitoring a PDCCH conveying control information of a designated format during an active time through a higher layer parameter (e.g., SearchSpace), and may obtain a location of information about the serving cell within the control information through a higher layer parameter (e.g., positionInDCI-cellDTRX). Then, the terminal may obtain control information based on the identified set of search spaces and location.

[0229] Control information related to cell DTX / DRX may be used to indicate activation or deactivation of cell DTX and / or cell DRX, and / or to provide 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, when the serving cell is configured as a SUL (supplementary uplink) carrier, the indication of activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the SUL carrier.

[0230] Thereafter, the terminal and the base station can perform communication based on the cell DTX / DRX (1406). Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor the signal from the base station. During the DTX-OFF, the base station enters a sleep mode to reduce energy consumption. At this time, the base station DTX cycle can be aligned with the cycle of the terminal DRX. The base station DTX-ON can completely cover the DRX-ON of the terminal. Furthermore, the base station can align the transmission of Xn / NG and the transmission of Uu for the purpose of NES. The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station can perform a dormancy-like behavior of sparsely transmitting or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. The terminal may sparsely receive or not receive a downlink signal / channel depending on the settings of the base station. 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.

[0231] SSB-less SCell

[0232] Figure 15 illustrates an example of a procedure for CA operation using SSB-less SCell.

[0233] Referring to FIG. 15, the base station transmits configuration information for the SCell to the terminal. That is, the base station transmits configuration information for CA to provide a service 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 the SCell may include information including information for adding the SCell (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL configuration, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Then, the terminal can determine the configuration for the CA operation and perform communication using the PCell and SCell of the base station. At this time, the terminal can confirm that the SCell is an SSB-less SCell based on the information related to the downlink frequency included in the configuration information, and check the related parameters. For example, a terminal can determine that an SCell is an SSB-less SCell by checking for the presence of a parameter indicating that it is an SSB-less SCell (e.g., SSBlessSCell), and can determine the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the case of Fig. 15, the reference cell may be a PCell. Therefore, the terminal can use the PCell as a timing reference and AGC source for communication on the SCell.

[0234] Conditional Hand Over (CHO)

[0235] Figure 16 illustrates an example of a Conditional Handover (CHO) procedure. The order of the operations illustrated in Figure 16 may vary depending on the case.

[0236] Referring to FIG. 16, the base station transmits configuration information for CHO to the terminal (1601). The configuration information for CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to configuration for reporting (e.g., ReportConfigNR). Here, the information related to configuration for reporting may include information related to events related to reporting, identifiers of the events (e.g., condEventId), information indicating whether it is an NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 16, event information indicating that it is an NES-specific CHO event is received.

[0237] The base station transmits information for enabling an NES-specific CHO execution condition to the terminal (1602). The information for enabling the NES-specific CHO execution condition may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information for enabling the NES-specific CHO execution condition may be referred to as an NES-mode indicator, and is, for example, 1-bit information that indicates enabling the NES-specific CHO execution condition when a related upper layer parameter (e.g., nesEvent) is set and the serving cell of the related block in the corresponding DCI is a primary cell.

[0238] Thereafter, the terminal performs a measurement (1603) and transmits a measurement report to the base station (1604). The base station determines a CHO based on the measurement report and performs signaling for a handover request with the neighboring base stations indicated by the measurement report (1606). The base station determines the neighboring base stations that have confirmed admission through signaling as candidate base stations and transmits information about the candidate base stations to the terminal (1607). Accordingly, the terminal evaluates the CHO execution conditions for the candidate base stations (1608). Accordingly, when a candidate cell satisfying the condition is determined, the terminal detaches from the old cell and synchronizes to the new cell (1609). At this time, since the terminal has previously received event information indicating that it is a NES-specific CHO event and also received information enabling the NES-specific CHO execution condition, it can determine whether the event is satisfied. In other words, if a NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information (e.g., nesEvent) indicating that the event is a NES-specific CHO event, the terminal can determine that the event associated with the corresponding measurement identifier (e.g., measId) is satisfied, and thus determine that the CHO execution condition is satisfied.

[0239] NES Enhancement

[0240] 3GPP NR release 19 will discuss NES enhancements, with (1) On-demand SSB, (2) On-demand SIB1 transmission, and (3) adaptation of common signal / channel transmissions being considered as key targets.

[0241] (1) On-demand SSB

[0242] A method to reduce energy consumption by having a base station transmit SSB on a specific cell through an on-demand SSB process and not transmit SSB on that cell when an on-demand SSB process is not available can be discussed. In the existing NR system, SSB must be transmitted periodically and constantly for purposes such as time / frequency synchronization or RRM measurement, making it difficult to reduce energy consumption even when the base station has no data to receive or send. Considering this, the base station can reduce base station energy consumption by not performing SSB transmission until the on-demand SSB process is involved and then performing SSB transmission. The on-demand SSB process can be triggered using one of the following methods:

[0243] 1) The terminal requests SSB transmission from the base station by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS in the NR system).

[0244] 2) Requesting SSB transmission from base station (or TRP) #1 to base station (or TRP) #2 through an interface between base stations (e.g., Xn interface in NR system) or backhaul signaling.

[0245] 3) Signaling whether SSB transmission is possible for the corresponding Scell ​​through Scell ​​activation / deactivation signaling.

[0246] Considering coexistence with existing NR terminals, Release 19 is limited to on-demand SSB operation for connected mode terminals and SCells. However, in future releases or next-generation communication systems, on-demand SSB operation (for SSB transmission on PCell) considering inactive or idle mode terminals or initially connected terminals may be defined. In addition, carrier aggregation (CA) including the SCell can be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process can be utilized for at least functionality such as time / frequency synchronization, L1 / L3 measurement, and SCell activation.

[0247] (2) On-demand SIB1 transmission

[0248] A method to reduce energy consumption by having the base station transmit SIB1 for a specific cell through the on-demand SIB1 process and not transmit SIB1 for the cell when there is no on-demand SIB1 process can be discussed. In the existing NR system, SIB1 containing system information, random access information, etc. for initial access or idle mode terminals to access a cell had to be provided periodically, so it was difficult to reduce energy consumption even when the base station had no data to receive or send. Considering this, the base station can reduce base station energy consumption by not performing SIB1 transmission until the on-demand SIB1 process is accompanied and then performing SIB1 transmission. The on-demand SIB1 process can trigger the base station's SIB1 transmission by the terminal transmitting an uplink signal / channel (e.g., PRACH in the NR system). Specifically, the following scenarios can be considered but may not be limited to the following scenarios.

[0249] 1) Scenario 1: As in (a) of Fig. 17, when a UE receives an SSB (and / or other downlink signal / channel) from a cell#1 and recognizes that SIB1 is not transmitted on the cell#1, the UE can trigger SIB1 transmission by transmitting a signal requesting SIB1 (for convenience, the signal is referred to as a WUS (wake-up signal)) based on information provided in the SSB (and / or other downlink signal / channel) and / or predetermined information. The base station that receives the WUS can transmit a specific DL signal / channel on cell#1 in response thereto, and (or) transmit SIB1 on cell#1 (without transmitting the DL signal / channel).

[0250] 2) Scenario 2: As in (b) of Fig. 17, a terminal may attempt to camp on cell#2 when it receives an SSB (and / or other downlink signal / channel such as SIB1) from a cell#1 and recognizes that SIB1 is not transmitted on the corresponding cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal requesting SIB1 (i.e., WUS) on cell#1 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. The base station receiving the WUS may transmit a specific DL signal / channel (on cell#1 or cell#2) in response thereto, and may transmit SIB1 for cell#2 on cell#1 or cell#2 (or without transmitting the DL signal / channel).

[0251] 3) Scenario 3: As in (c) of Fig. 17, a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) from a cell#1 and recognizes that SIB1 is not transmitted on the corresponding cell#2 may attempt to camp on cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal requesting SIB1 (i.e., WUS) on cell#2 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. The base station that receives the WUS may transmit a specific DL signal / channel (on cell#1 or cell#2) in response thereto, and may transmit SIB1 for cell#2 on cell#1 or cell#2 (or without transmitting the DL signal / channel).

[0252] (3) adaptation of common signal / channel transmissions

[0253] Methods for reducing energy consumption by modulating the transmission of common signals / channels such as SSB, PRACH, and paging by the base station can be discussed. While completely disabling SSB can significantly reduce the energy consumption of the base station, the absence of SSB, which performs functions such as time / frequency synchronization and RRM measurement, may not guarantee stable operation for the corresponding cell from the UE's perspective. Considering this, energy savings at the base station can be achieved by varying the SSB transmission pattern (e.g., transmission period, period per SSB candidate index(es), SSB candidate index(es) transmitted within a transmission period, transmission power, etc.) depending on the situation.

[0254] In the case of PRACH resources, since the base station cannot know when the terminal will transmit the PRACH in the case of contention-based random access, energy consumption may increase because the base station always attempts to receive within the configured PRACH resources. Considering this, energy of the base station can be saved by applying a method to adjust the amount of PRACH resources (e.g., adjusting the period of PRACH resources, adjusting the amount of resources through instructions such as pre-configuring PRACH resource set #1 and set #2 and turning on only one set or both sets, or providing the corresponding RACH resource amount uniformly or non-uniformly for each SSB index).

[0255] In the case of paging, previously, paging frames (PF) and / or paging occasions (PO) were distributed along the time axis within a DRX cycle (or paging cycle), and the terminal attempted to receive paging at a specific PF / PO derived from its ID-based formula. From the base station's perspective, if paging was to be transmitted to multiple terminals simultaneously, it may have to wake up frequently to transmit paging. To reduce base station energy consumption due to this, it is possible to consider arranging PFs and / or POs for paging reception as close to the time axis as possible or arranging different frequency resources within the same time.

[0256] Figure 18 illustrates an example of SSB transmission of a base station operating multiple frequency bands.

[0257] From the perspective of a base station operating multiple frequency bands, even when the number of terminals served is small or the traffic load is relatively low, the amount of energy consumed by periodically sending SSB and / or system information can be large.

[0258] Referring to FIG. 18, from the perspective of a base station operating three frequency bands (in the present invention, the frequency bands can be replaced with bands, carriers, serving cells, BWPs, etc.), energy can be saved by periodically transmitting (legacy) SSB and / or SIB1 only in some frequency bands (e.g., F1), transmitting simplified (or modified) S-SSB (simplified SSB) in the remaining frequency bands (e.g., F2), or not transmitting SSB in other frequency bands (e.g., F3), or not transmitting SIB1 on F2 / F3. S-SSB may mean a signaling structure in which some of the signals / channels constituting the existing SSB (e.g., PSS, SSS, PBCH DM-RS, PBCH, etc.) are omitted, the configuration of the signals / channels is modified, or information different from the existing information is transmitted through the PBCH payload.

[0259] For a terminal operating in F2 or F3, it can request SIB1 transmission from a base station in the corresponding frequency band or adaptively resume / adjust SIB1 transmission according to the base station's own judgment. For convenience, the SIB1 transmitted in this manner is called on-demand SIB1.

[0260] This specification includes a proposal for a scenario in which a terminal receives signaling regarding information of F2 and / or F3 via SSB and / or SIB1 transmitted from F1. As an example, a representative scenario is considered in which a terminal receiving such signaling moves from F1 or F2 / F3, performs an on-demand SIB1 process, receives SSB and / or SIB1 for the corresponding F2 or F3 frequency band, performs a RACH procedure, etc., enters connected mode, and transmits DL and / or UL data via F2 or F3.

[0261] Also, for convenience, a frequency band where S-SSB can be transmitted, such as F2, a frequency band where SSB cannot be transmitted, such as F3, and / or a frequency band where SIB1 can be transmitted through the on-demand SIB1 process are collectively referred to as the F2 frequency band, but the proposal can be applied to F3 as well as F2.

[0262] Before explaining the proposed content of this specification, Method #1, Method #2, and Method #3, which can be used as references to help understand the proposed content, are first described.

[0263] [Method #1] Information that can be set by the terminal through SSB (and / or SIB) transmitted in the F1 frequency band (or S-SSB transmitted in the F2 frequency band) and terminal operation based on the information.

[0264] The terminal may be configured to receive at least some or all of the following information via SSB (and / or SIB) transmitted in the F1 frequency band (or S-SSB transmitted in the F2 frequency band).

[0265] (i) A list of frequency bands having an association or QCL relationship with frequency band F1 (e.g., F2 and / or F3): Here, the existence of an association or QCL relationship between two frequency bands (e.g., F1 and F2) means that frequency band F1 can be a timing and / or power control (or path-loss estimation) and / or synchronization reference for frequency band F2. That is, frequency band F1 can be a timing reference for frequency band F2, or frequency band F1 can be a reference for power control (or path-loss estimation) for frequency band F2, or frequency band F1 can be a time / frequency synchronization reference for frequency band F2.

[0266] (ii) When a signal / channel of a terminal requesting SSB and / or SIB1 transmission on the F2 frequency resource of a base station is defined as a UE WUS (wake-up signal), time / frequency resource information on which the UE WUS can be transmitted can be set. The corresponding UE WUS resource may be set within the F2 frequency band or the F1 frequency band. In particular, when the cell DRX inactive period of the base station or the F1 frequency band is not the synchronization reference of the F2 frequency band and even the S-SSB / SIB transmission in the F2 frequency band is turned off, the UE WUS resource may be set within the F1 frequency band. Frequency and / or time and / or sequence-related information (e.g., PRACH preamble index, cyclic shift, (root) sequence index, phase offset, orthogonal cover code, etc.) of the UE WUS may vary depending on the frequency band (e.g., F2 or F3) on which the requested SSB and / or SIB1 will be transmitted. For example, even if a UE WUS is assigned to the F1 frequency band, the frequency and / or time and / or sequence-related information of the UE WUS may be set differently depending on whether the UE requests an SSB to be transmitted on the F2 frequency band or an SSB to be transmitted on the F3 frequency band. Alternatively, the frequency and / or time and / or sequence-related information of the UE WUS may vary depending on the requested SSB index and / or the requested signal (i.e., SSB or SIB1).For example, even if it is an SSB to be transmitted on the F2 frequency resource, the frequency and / or time and / or sequence-related information of the UE WUS may be set differently for each SSB index (group), or the frequency and / or time and / or sequence-related information of the UE WUS may be set differently depending on whether a specific SSB index is requested or beam sweeping for all SSBs is requested. As another example, the frequency and / or time and / or sequence-related information of the UE WUS may be set differently depending on whether the signal requesting transmission to the base station through the UE WUS is an SSB or SIB1. As another example, even if it is an SIB1 requesting transmission to the base station through the UE WUS, the frequency and / or time and / or sequence-related information of the UE WUS may be set differently depending on which SSB index (from a QCL perspective) corresponding to which SIB1 transmission is requested.

[0267] (iii) After a terminal requests a specific signal / channel through UE WUS transmission, the terminal can determine whether the request has been properly transmitted only after receiving the corresponding signal / channel. Therefore, it may be necessary for the base station to set information about the signal / channel corresponding to the UE WUS. For example, when the base station requests SSB and / or SIB1 transmission through UE WUS, information about the time point at which the terminal expects the first reception of SSB and / or SIB1 may be set. The time point may be set as a relative time point from the UE WUS transmission time point (e.g., after X ms or Y slots from the UE WUS transmission time point, or after the nearest sub-frame boundary or half-frame boundary after X ms or Y slots from the UE WUS transmission time point, etc.) or a rule may be defined, or it may be set as an absolute time point (e.g., the first SFN#Z after the UE WUS transmission time point) or a rule may be defined. In the case of SIB1, by setting information similar to the existing SI-window information, SIB1 can be transmitted periodically with a specific period after the base station receives UE WUS (or SIB1 can be received periodically with a specific period after the terminal transmits UE WUS). As another example, for SIB1 reception, in order to receive SIB1 PDCCH (i.e., PDCCH scheduling SIB1 PDSCH) through the F2 frequency band, a configuration for a CORESET transmitted on the F2 frequency band (separate from CORESET#0 on the F1 frequency band) can be received. In addition, a configuration for a search space set for SIB1 reception associated to the corresponding CORESET can also be received. Or, information on PDSCH resources for PDCCH-less SIB1 PDSCH reception can be set.As another example, if the terminal expects msg2 (random access response, RAR in RACH procedure) or HARQ feedback as a response from the base station after the terminal transmits the UE WUS, it can also receive configuration for the CORESET transmitted in the F2 frequency band (separate from CORESET#0 in the F1 frequency band) for the purpose of receiving the msg2 and / or HARQ feedback, and additionally, configuration for the search space set associated with the CORESET.

[0268] (iv) When setting the F1 and F2 frequency bands to the terminal, Opt1) the two frequency bands may be set as a single BWP, which may be set as a set of PRBs that are not consecutive along the frequency axis, or Opt2) each frequency band may be set as a separate BWP, so that the F1 BWP and the F2 BWP may be set separately, or Opt3) the F1 and F2 frequency bands may be set as different DL carriers (but single serving cell), or Opt4) the F1 and F2 frequency bands may be set as separate serving cells.

[0269] The mapping relationship between the (S-)SSB index transmitted in the F2 (or F1) frequency band and the RACH occasion (RO) of the F2 frequency band, as well as the RACH configuration in the F2 frequency band, can be provided through SIB1 transmitted in the F2 frequency band. In addition, a series of processes such as RACH procedure and paging reception can be performed by the terminal on the F2 frequency band, and the configuration of the CORESET transmitted in the F2 frequency band for these operations and the configuration of the search space set associated with the CORESET can also be provided through SIB1 transmitted in the F2 frequency band.

[0270] [Method #2] Criteria for selecting the F2 frequency band (as a frequency band for performing the on-demand SSB / SIB1 procedure)

[0271] [Method #1] The criteria for selecting F2 (rather than F1) as a frequency band for performing an on-demand SSB / SIB1 procedure by a terminal are described, and may be selected by one or a combination of the following criteria. Selecting the F2 frequency band as a frequency band for performing an on-demand SSB / SIB1 procedure means performing a procedure for requesting SSB and / or SIB1 transmission of a base station in the corresponding frequency band, and the UE WUS for the request may be transmitted in the F1 or F2 frequency band.

[0272] (i) Based on RSRP measured through reception of SSB (e.g., SSS and / or PBCH DM-RS) transmitted in frequency band F1: One of frequency bands F1 and F2 may be selected based on a predefined RSRP threshold or based on an RSRP threshold set through SSB (and / or SIB) transmitted in frequency band F1 (or S-SSB transmitted in frequency band F2). For example, if RSRP measured through reception of SSB (e.g., SSS and / or PBCH DM-RS) transmitted in frequency band F1 is equal to or greater than (or less than) the threshold, frequency band F1 may be selected, and if it is equal to or less than (or greater than) the threshold, frequency band F2 may be selected.

[0273] (ii) UE capability-based: UEs with specific capabilities (e.g., NES-capable UEs or UE WUS-capable UEs) can be configured to move to the F2 frequency band instead of the F1 frequency band through base station signaling (which can be configured through SSB (and / or SIB) transmitted in the F1 frequency band (or S-SSB transmitted in the F2 frequency band)). On the other hand, UEs without the corresponding capability can remain in the F1 frequency band and perform RACH procedures, etc.

[0274] (iii) Random selection based: The terminal can randomly select either the F1 frequency band or the F2 frequency band. Alternatively, a weighting factor can be set for a specific frequency band (via SSB (and / or SIB) transmitted in the F1 frequency band (or S-SSB transmitted in the F2 frequency band)), and based on the set weighting factor, the terminal can select a frequency band and perform a RACH procedure or an on-demand SSB / SIB1 procedure (depending on the selected frequency band) through the selected frequency band.

[0275] A combination of threshold-based and random selection-based methods can also be considered. For example, a weighting factor can be set such that if the RSRP measured through reception of SSB (e.g., SSS and / or PBCH DM-RS) transmitted in the F1 frequency band is above (or below) a threshold, a specific F1 or F2 frequency band is selected, whereas if it is below (or above) the threshold, a specific F1 or F2 frequency band is given priority in random selection.

[0276] [Method #3] How to perform on-demand SSB / SIB1 procedures after moving to the F2 frequency band

[0277] (Based on the configuration information suggested in the above [Method #1], etc.) the terminal can transmit the UE WUS signal / channel on the F1 frequency band or the F2 frequency band. At this time, when determining the timing and power control of the corresponding UE WUS transmission, it can be performed based on the SSB received through the F1 frequency band. For example, when transmitting the UE WUS on the F2 frequency band, if an association or QCL relationship between the F1 frequency band and the F2 frequency band is set, the timing and power values ​​of the UE WUS to be transmitted on the F2 frequency band can be determined based on a specific SSB index received on the F1 frequency band.

[0278] (As in the configuration information suggested in the above [Method #1]), frequency and / or time and / or sequence-related information of the UE WUS may be set differently depending on the frequency band in which the requested SSB / SIB1 is to be transmitted, the SSB (group) index to be requested, the type of signal to be requested (i.e., SSB or SIB1), the SSB index corresponding to the requested SIB1, etc. Accordingly, the terminal may attempt UE WUS transmission by selecting an appropriate resource according to the requested SSB / SIB1. If the appropriate UE WUS resource is properly configured in detail according to the requested SSB / SIB1, the terminal may receive only the corresponding base station's response (e.g., a response similar in structure to RAR or msg2 in the RACH procedure) after transmitting the UE WUS, and complete the corresponding SSB / SIB1 procedure. On the other hand, even after receiving the corresponding response from the base station following the UE WUS transmission, the terminal may need to send additional request information (named msg3 for convenience) (including additional request information that was not yet transmitted via the UE WUS). For example, a common UE WUS for SSB / SIB1 may be defined, and the terminal may request whether the actually requested signal / channel is SSB or SIB1 by including it in msg3 after receiving the response from the base station following the UE WUS transmission. As another example, a common UE WUS for SSB (or SIB1) may be defined, and the terminal may request whether the actually requested signal / channel corresponds to a certain (group) index of SSB (or a certain QCL relationship of SIB1) in msg3 after receiving the response from the base station following the UE WUS transmission. Resource information on which msg3 can be transmitted may be included in the response from the base station.

[0279] After the UE WUS is transmitted by the terminal, the terminal can expect that the base station will transmit a signal corresponding to the UE WUS after a certain period of time (and during a certain time window) (taking into account the processing time of the base station and / or the terminal). At this time, the signal corresponding to the UE WUS may mean a specific SSB and / or SIB1 requested through the UE WUS, and may also be msg2 and / or HARQ feedback (as in the configuration information proposed in the above [Method #1]). The certain period of time can be expressed as X msec or Y slots, and the value of X or Y can be preset or defined in the specification. In addition, the terminal can expect to receive a signal corresponding to the UE WUS during a certain time window, and the duration value of the time window (e.g., 20 msec) can also be preset or defined in the specification.

[0280] If the terminal expects to receive a signal corresponding to the UE WUS, but the corresponding signal is determined to not exist, a penalty may be applied. Here, the case where the corresponding signal is determined to not exist here may specifically mean that the corresponding signal is not detected for the duration of a certain timer or time window, or the reception sensitivity of the corresponding signal is below a certain threshold (the threshold value may be a separately preset value or a predefined value). In addition, applying a penalty may mean ramping up the power value and / or count value in the on-demand procedure. If the power value and / or count value reaches the (pre-set) max value, the terminal may proceed with the RACH procedure in the F1 frequency band or select another frequency band (e.g., F3) to start a new on-demand SSB / SIB1 procedure.

[0281] As in F1, a frequency band in which SSB and / or SIB1 are transmitted and information about other frequency bands (e.g., whether SIB1 is currently being transmitted periodically, and if so, transmission time pattern information of SIB1 on the other frequency band, and if not, configuration information about UE WUS resources for on-demand SIB1 procedures, etc.) is provided is conveniently named an anchor cell, and other frequency bands provided through SSB and / or SIB1 on the anchor cell are conveniently named non-anchor cells. In addition, the UE can assume that there is an association or QCL relationship between the anchor cell and the non-anchor cell. Alternatively, a cell in which SIB1 for its own cell is periodically transmitted can be defined as an anchor cell, and a cell that can transmit SIB1 in response to UE WUS, UL WUS, or PRACH from the UE can be defined as a non-anchor cell. In addition, the anchor cell can be replaced with cell A, and the non-anchor cell can be replaced with NES cell.

[0282] On-demand SIB1 operation for idle / inactive UE

[0283] In the following, we propose a method for providing information about a non-anchor cell through SSB and / or SIB1 and / or SIB on an anchor cell, a method for controlling connection of an existing terminal in a non-anchor cell, and a method for providing information about an anchor cell through SSB on a non-anchor cell.

[0284] [Proposal #1] The base station provides information about the second cell (e.g., non-anchor cell) through upper layer signaling (e.g., cell-specific RRC signaling such as SSB and / or SIB1 and / or SIB) on the first cell (e.g., anchor cell).

[0285] When a base station signals information about a non-anchor cell (e.g., whether SIB1 is currently being periodically transmitted, if so, transmission time pattern information of SIB1 on another frequency band, if not, configuration information about UE WUS resources for on-demand SIB1 procedure, etc.) through cell-specific RRC signaling such as SSB and / or SIB1 and / or SIB on an anchor cell, there may be one or more target or associated non-anchor cells. The base station may provide at least one of the following information for each associated non-anchor cell, and each associated non-anchor cell may be distinguished through at least one of the following information.

[0286] (1) Physical cell ID (PCI): A single PCI can be generated by combining the PSS and SSS. For example, up to 1008 PCIs can be generated in a 5G NR system. The base station can designate one of the values ​​(or only a portion of the information). A terminal that moves to the associated non-anchor cell corresponding to the PCI and receives an SSB can expect to receive an SSB containing the corresponding PCI value (or a PCI value corresponding to the indicated portion of the information).

[0287] (2) Global cell ID (GCI): A unique ID that distinguishes a cell / base station, etc. can be defined. For example, in 5G NR, it is defined as NCGI (NR cell global identity), and is generated through the concatenation of PLMN-ID and 36-bit NCI (NR Cell Identity). The base station can designate one of the values ​​(or only part of the information). A terminal receiving an SIB for an associated non-anchor cell corresponding to the GCI can expect to receive an SIB that includes the GCI value (or a GCI value corresponding to the indicated part of the information).

[0288] (3) Frequency location information of SSB: The base station can provide information on the frequency location (e.g., center frequency) of the SSB transmitted on the associated non-anchor cell. For example, in the case of 5G NR, the center frequency of the SSB can be signaled through a parameter called NR-ARFCN. The base station can specify the frequency location information of the SSB (e.g., NR-ARFCN value or offset value from the GSCN of the SSB transmitted on the anchor cell). A terminal that moves to the associated non-anchor cell corresponding to the frequency location information of the SSB and receives the SSB can expect the SSB to be detected based on the frequency location information of the SSB. The center frequency location of the SSB transmitted on the non-anchor cell can be the same as or different from the predefined GSCN (global synchronization channel number). In addition, whether the SSB transmitted on the non-anchor cell is a CD-SSB or an NCD-SSB can be predefined or provided by the anchor cell. The provision of information from the anchor cell (i.e., information on whether the SSB transmitted on the non-anchor cell is a CD-SSB or a NCD-SSB) may be limited when the center frequency location of the SSB transmitted on the non-anchor cell is different from the defined GSCN. Here, a CD-SSB (cell-defining-SSB) refers to an SSB in which configuration information for CORESET #0 and / or search space set zero for SIB1 PDCCH reception is signaled, and a NCD-SSB (non-cell-defining-SSB) refers to an SSB in which, on the contrary, configuration information for CORESET #0 (e.g.,, controlResourceSetZero parameter) and / or search space set zero (e.g., searchSpaceZero parameter) is not signaled. If the SSB on the non-anchor cell is NCD-SSB, configuration information on CORESET #0 and / or search space set zero, and / or configuration information such as ssb-SubcarrierOffset may be provided from the anchor cell. If the SSB on the non-anchor cell is CD-SSB, configuration information on CORESET #0 and / or search space set zero for SIB1 PDCCH reception and / or configuration information such as ssb-SubcarrierOffset may be provided from the anchor cell, or (if not provided from the anchor cell or by configuration / instruction from the anchor cell) the UE may acquire the corresponding configuration information(s) from the SSB on the non-anchor cell.

[0289] When there is one or more non-anchor cells corresponding to the above information, unique ID information (i.e., cell index, TRP index, CORESET pool index, and / or additional PCI) corresponding to each non-anchor cell may be assigned. In various embodiments, the term cell(s) may be replaced with TRP(s). For example, one serving cell may be composed of one or more TRPs. For example, when N CORESET pool indices are configured for a terminal, each CORESET may be associated with a different TRP, and the TRP may be identified based on the CORESET pool index. For example, the TRP may be identified based on the PCI. In the NR system, a function of setting an SSB having a different PCI value from the serving cell PCI has been introduced to support intra-cell or inter-cell multi-TRP operation. For example, when an SSB of PCI#1 is set for one serving cell, and an SSB transmitted on the serving cell is additionally set, the additional SSB may be set to PCI#2. In this way, for a single serving cell configuration, the base station can configure SSBs with different PCIs than the serving cell PCI. In this case, SSB transmission entities with different PCIs may indicate different TRPs.

[0290] In this way, unique ID information (i.e., cell index, TRP index, CORESET pool index, and / or additional PCI) corresponding to a non-anchor cell can be explicitly signaled or implicitly determined by a rule as follows.

[0291] - Explicit method: As described above, the unique ID information (i.e., cell index, TRP index, CORESET pool index, and / or additional PCI) of the non-anchor cell linked to the combination of {PCI, GCI, SSB frequency location information} can be explicitly set. For example, if the unique ID information is cell_index, the base station can signal that the cell index of the non-anchor cell set to {PCI=A, SSB center frequency=F_a} in the base station configuration message is 1, and the cell index of the non-anchor cell set to {PCI=B, SSB center frequency=F_b} is 2.

[0292] - Implicit method: As described above, the unique ID information (i.e., cell index, TRP index, CORESET pool index, and / or additional PCI) of the non-anchor cell linked to the combination of {PCI, GCI, SSB frequency location information} can be determined by the rule. For example, if the unique ID information is cell_index, if there is a non-anchor cell set to {PCI=A, SSB center frequency=F_a} and a non-anchor cell set to {PCI=B, SSB center frequency=F_b} in the base station configuration message, the cell index of the non-anchor cell set to {PCI=A, SSB center frequency=F_a} can be implicitly determined as 1, and the cell index of the non-anchor cell set to {PCI=B, SSB center frequency=F_b} can be implicitly determined as 2 according to the configuration order. As another example, the association relationship between an anchor cell and a non-anchor cell can be predefined in the standard, and the cell_index of the non-anchor cell linked to a specific anchor cell can also be determined.

[0293] The cell_index corresponding to an anchor cell can be predefined or set to a specific value (e.g., cell_index=0).

[0294] By signaling transmitted on the anchor cell (e.g. via cell-specific RRC signaling such as SSB and / or SIB1 and / or SIB), the base station can configure at least one of the following pieces of information for each non-anchor cell:

[0295] (i) Whether SIB1 is being transmitted on the non-anchor cell: Additionally, whether the non-anchor cell can trigger SIB1 transmission via on-demand SIB1 may also be included. If SIB1 is being transmitted, whether it has been transmitted since time T1 may be included, and signaling for that time T1 may be included. Additionally, if SIB1 is being transmitted, whether it will be transmitted until time T2 may be included, and signaling for that time T2 may be included.

[0296] (ii) UE WUS related configuration: UE WUS resource configuration information for requesting SIB1 transmission on the non-anchor cell may be included. In addition, if a downlink signal / channel is defined that can notify the base station whether or not the UE WUS has been received (for convenience, it is called ACK, and if the UE WUS is PRACH, the ACK may be a PDSCH containing DCI scrambled with RA-RNTI and / or MAC-CE in the form of a random access response), information on the CORESET and / or search space (SS) set corresponding to the ACK may be included.

[0297] (iii) Whether SSB is being transmitted on the non-anchor cell: If SSB is being transmitted, it may include signaling for time T1, whether transmission has been ongoing since time T1. Additionally, if SSB is being transmitted, it may include signaling for time T2, whether transmission will continue until time T2.

[0298] (iv) Information about the CORESET and / or search space (SS) set for receiving SIB1 corresponding to the non-anchor cell.

[0299] Information about the CORESET and / or search space (SS) set and / or downlink reception (e.g., PDSCH, PDCCH) and / or uplink transmission (e.g., PUSCH or HARQ-ACK PUCCH) that performs random access and paging procedures after receiving SIB1 corresponding to the non-anchor cell: Here, random access may mean all or part of the following: base station transmission of DCI that triggers PDCCH-order PRACH transmission of the UE in a 4-step random access (or type-1 random access according to the NR standard) procedure, PRACH transmission of the UE, random access response transmission of the base station, msg3 PUSCH transmission of the UE, PDSCH transmission including contention resolution of the base station, and HARQ-ACK transmission for PDSCH of the UE. Alternatively, it may refer to all or part of the following: msgA PRACH and msgA PUSCH transmission by the UE, random access response transmission by the base station, HARQ-ACK transmission corresponding to the random access response by the UE, PUSCH transmission corresponding to the random access response by the UE, PDSCH transmission including contention resolution by the base station, and HARQ-ACK transmission for PDSCH by the UE in a 2-step random access (or type-2 random access according to the NR standard) procedure. In addition, the paging procedure may refer to an operation such as receiving DCI scrambled with P-RNTI through Type2-PDCCH CSS set, receiving PDSCH scheduled through the corresponding DCI, or receiving DCI scrambled with PEI-RNTI through Type2A-PDCCH CSS set.

[0300] When signaling information for each non-anchor cell, a combination of {frequency location information of PCI, GCI, SSB} and / or cell_index information may be included as in the following embodiments (a)-(e).

[0301] (a) Whether SIB1 is being transmitted on the non-anchor cell: Additionally, whether the non-anchor cell can trigger SIB1 transmission through an on-demand SIB1 request may also be included. If SIB1 is being transmitted, whether it has been transmitted since time T1 may be included, and signaling for that time T1 may be included. Additionally, if SIB1 is being transmitted, whether it will be transmitted until time T2 may be included, and signaling for that time T2 may be included.

[0302] - As a method of signaling that a non-anchor cell is transmitting SIB1, a combination of {PCI, GCI, frequency location information of SSB} and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) may be utilized. As an example of cell index, the base station may signal that a non-anchor cell corresponding to {PCI=A, center frequency of SSB=F_a} is transmitting SIB1, and the non-anchor cell corresponding to {PCI=B, center frequency of SSB=F_b} is not transmitting SIB1. As another example, the base station may signal that a non-anchor cell corresponding to cell_index#1 is transmitting SIB1, and the non-anchor cell corresponding to cell_index#2 is not transmitting SIB1.

[0303] - As a method of signaling that a non-anchor cell is capable of triggering SIB1 transmission by the on-demand SIB1 procedure, a combination of {PCI, GCI, frequency location information of SSB} and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) may be utilized. As an example of the cell index, the base station may signal that a non-anchor cell corresponding to {PCI=A, center frequency of SSB=F_a} cannot trigger SIB1 transmission by the on-demand SIB1 procedure, and a non-anchor cell corresponding to {PCI=B, center frequency of SSB=F_b} can trigger SIB1 transmission by the on-demand SIB1 procedure. As another example, the base station may signal that SIB1 transmission cannot be triggered by the on-demand SIB1 procedure in a non-anchor cell corresponding to cell_index#1, and that SIB1 transmission can be triggered by the on-demand SIB1 procedure in a non-anchor cell corresponding to cell_index#2.

[0304] (b) UE WUS related configuration: UE WUS resource configuration information for requesting SIB1 transmission on the non-anchor cell may be included. In addition, if a downlink signal / channel is defined that can notify the base station whether or not the UE WUS has been received (for convenience, it is called ACK, and if the UE WUS is PRACH, the ACK may be a PDSCH containing DCI scrambled with RA-RNTI and / or MAC-CE in the form of a random access response), information on the CORESET and / or search space (SS) set corresponding to the ACK may be included.

[0305] - A method for setting a cell in which UE WUS for a specific non-anchor cell is transmitted may utilize a combination of {PCI, GCI, SSB frequency location information} corresponding to the cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index, and / or additional PCI). Alternatively, a rule may be established to set UE WUS resources on the anchor cell (if no separate configuration is provided).

[0306] - As a method of establishing which non-anchor cell corresponds to the UE WUS for on-demand SIB1 purposes, a combination of {PCI, GCI, SSB frequency location information} for the non-anchor cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) may be utilized.

[0307] - A combination of {PCI, GCI, SSB frequency location information} and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) corresponding to the cell may be utilized as a method of signaling on which cell the CORESET and / or search space (SS) set on which the ACK is transmitted is transmitted. Alternatively, a rule may be defined so that the corresponding CORESET and / or search space (SS) set is configured on the cell on which the UE WUS is transmitted. Alternatively, a rule may be defined so that the corresponding CORESET and / or search space (SS) set is configured on the corresponding non-anchor cell (or on the anchor cell) (if no separate configuration is provided).

[0308] - If the ACK message can include information about whether the base station has successfully received the UE WUS requesting SIB1 transmission for a certain non-anchor cell or has initiated SIB1 transmission for a certain non-anchor cell, a combination of {PCI, GCI, SSB frequency location information} corresponding to the non-anchor cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) can be utilized.

[0309] - When the base station transmits the ACK in the form of a DCI scrambled with RA-RNTI in a random access response format and the UE WUS can be transmitted from one or more non-anchor cells, it is necessary to distinguish the cells in which the UE WUS is transmitted through the RA-RNTI. In this case, the RA-RNTI calculation formula may include unique ID information (i.e., cell index, TRP index, CORESET pool index, and / or additional PCI). For example, the corresponding RA-RNTI value may be calculated differently depending on whether the UE WUS is transmitted on cell_index#1 or cell_index#2. When calculating the RA-RNTI, the cell_index corresponding to the anchor cell may be characteristically 0.

[0310] (c) Whether SSB is being transmitted on the non-anchor cell: If SSB is being transmitted, it may include signaling for time T1, whether transmission has been ongoing since time T1. Additionally, if SSB is being transmitted, it may include signaling for time T2, whether transmission will continue until time T2.

[0311] - As a method of signaling that a non-anchor cell is transmitting SSB, a combination of {PCI, GCI, frequency location information of SSB} corresponding to the non-anchor cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) may be utilized. Alternatively, whether or not to transmit SSB on a non-anchor cell may be determined according to a predefined rule. For example, if the anchor cell and the non-anchor cell belong to the same frequency band or frequency range or the frequency gap is less than a specific value, SSB may not be transmitted on the non-anchor cell (unless otherwise specified). As another example, if the anchor cell and the non-anchor cell belong to different frequency bands or frequency ranges or the frequency gap exceeds a specific value, SSB may be transmitted on the non-anchor cell (unless otherwise specified).

[0312] (d) Information about the CORESET and / or search space (SS) set for receiving SIB1 corresponding to the non-anchor cell.

[0313] - A combination of {PCI, GCI, SSB frequency location information} corresponding to the cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) may be utilized as a method of signaling on which cell the CORESET and / or search space (SS) set is transmitted. Alternatively, a rule may be defined so that the corresponding CORESET and / or search space (SS) set is configured on the cell in which the UE WUS is transmitted. Alternatively, a rule may be defined so that the corresponding CORESET and / or search space (SS) set is configured on the corresponding non-anchor cell (or on the anchor cell) (if no separate configuration is provided).

[0314] - A combination of {PCI, GCI, SSB frequency location information} and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) corresponding to the non-anchor cell may be utilized as a method of signaling which non-anchor cell the CORESET and / or search space (SS) set is intended for SIB1 reception.

[0315] - If the DCI for scheduling SIB1 PDSCH can include information on which non-anchor cell the SIB1 PDSCH is scheduled for, a combination of {PCI, GCI, SSB frequency location information} corresponding to the non-anchor cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) can be utilized.

[0316] (e) Information about CORESET and / or search space (SS) set and / or downlink reception (e.g., PDSCH, PDCCH) and / or uplink transmission (e.g., PUSCH or HARQ-ACK PUCCH) that perform random access and paging procedures after receiving SIB1 corresponding to the non-anchor cell: Here, random access may mean all or part of the following: base station transmission of DCI that triggers PDCCH-order PRACH transmission of the terminal in a 4-step random access (or type-1 random access according to the NR standard) procedure, PRACH transmission of the terminal, random access response transmission of the base station, msg3 PUSCH transmission of the terminal, PDSCH transmission including contention resolution of the base station, and HARQ-ACK transmission for PDSCH of the terminal. Alternatively, it may refer to all or part of the following: msgA PRACH and msgA PUSCH transmission by the UE, random access response transmission by the base station, HARQ-ACK transmission corresponding to the random access response by the UE, PUSCH transmission corresponding to the random access response by the UE, PDSCH transmission including contention resolution by the base station, and HARQ-ACK transmission for PDSCH by the UE in a 2-step random access (or type-2 random access according to the NR standard) procedure. In addition, the paging procedure may refer to an operation such as receiving DCI scrambled with P-RNTI through Type2-PDCCH CSS set, receiving PDSCH scheduled through the corresponding DCI, or receiving DCI scrambled with PEI-RNTI through Type2A-PDCCH CSS set.

[0317] - As a signaling method for a cell performing a random access procedure corresponding to the non-anchor cell, a combination of {PCI, GCI, SSB frequency location information} corresponding to the cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) may be utilized. At this time, the information may be commonly set / applied to the entire random access procedure, may be set / applied differently for each procedure, or may be set / applied differently for the uplink procedure and the downlink procedure. Alternatively, a rule may be set so that the random access procedure is performed through the cell where the UE WUS is transmitted (or the cell where the paging procedure is performed). Alternatively, a rule may be set so that the random access procedure is performed on the non-anchor cell (or on the anchor cell) (if there is no separate setting). Meanwhile, the information may be signaled by a signal transmitted on a non-anchor cell (e.g., SSB and / or SIB1 on a non-anchor cell), rather than a signal transmitted on an anchor cell.

[0318] - As a signaling method for a cell performing a paging procedure corresponding to the non-anchor cell, a combination of {PCI, GCI, SSB frequency location information} corresponding to the cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) may be utilized. At this time, the information may be commonly set / applied to the entire paging procedure, or may be set / applied differently for each procedure. Alternatively, a rule may be set so that the paging procedure is performed through the cell where the UE WUS is transmitted (or the cell where the random access procedure is performed). Alternatively, a rule may be set so that the paging procedure is performed on the non-anchor cell (or on the anchor cell) (if no separate setting is made). Meanwhile, the information may be signaled by a signal transmitted on a non-anchor cell (e.g., SSB and / or SIB1 on the non-anchor cell), rather than a signal transmitted on the anchor cell.

[0319] - If the DCI for scheduling the paging PDSCH includes information on which non-anchor cell the paging PDSCH is scheduled for, information on which non-anchor cell SI is updated, or information on triggering initial access (or random access) on which non-anchor cell, a combination of {PCI, GCI, SSB frequency location information} corresponding to the non-anchor cell and / or unique ID information (i.e., cell index, TRP index, CORESET pool index, and / or additional PCI) may be utilized.

[0320] In utilizing unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) as signaling for a specific cell in the above, unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) can be set in advance through higher layer signaling (e.g., cell-specific or UE group-common or UE-specific RRC signaling), or unique ID information (i.e., cell index, TRP index, CORESET pool index and / or additional PCI) can be dynamically indicated through DCI or MAC-CE, etc.

[0321] In the above paging procedure, the operation when an SI update for a specific non-anchor cell is indicated via paging DCI and / or PDSCH needs to be defined. If the UE is camped on the non-anchor cell, the SI update can trigger an on-demand SIB1 procedure to perform UE WUS transmission. In addition, if the paging procedure is configured to be performed in a cell different from the camped-on non-anchor cell (e.g., anchor cell) through the above configuration, the UE can perform the paging procedure by transitioning to another cell configured to perform the paging procedure in order to check whether the non-anchor cell has an SI update for each SI modification. In addition, in the above paging procedure, when initial access (or random access) is set / indicated on a specific non-anchor cell, the terminal may transmit UE WUS to request SIB1 transmission on the non-anchor cell or perform a random access procedure on the non-anchor cell, and in the latter case, the base station may initiate SIB1 transmission by receiving the corresponding PRACH.

[0322] [Proposal #2] Access control of existing terminals in a second cell (e.g., non-anchor cell)

[0323] Considering that the non-anchor cell may not transmit SIB1 and may start transmitting SIB1 after the on-demand SIB1 procedure, a method may be needed to prevent existing terminals and / or terminals without on-demand SIB1 functionality from accessing the non-anchor cell. If the existing terminal and / or terminal without on-demand SIB1 functionality detects SSBs, etc. transmitted on the non-anchor cell and attempts to receive SIB1, the non-anchor cell may not actually receive SIB1, resulting in having to attempt access through another cell, which may increase the initial access delay time.

[0324] Therefore, it is possible to prevent existing terminals and / or terminals without on-demand SIB1 functionality from accessing the non-anchor cell by utilizing at least one of the following methods.

[0325] - The base station can transmit the SSB by setting the frequency location of the SSB transmitted on the non-anchor cell to an unspecified frequency location for existing terminals and / or terminals that do not have the on-demand SIB1 function. For example, in the NR system, the standard defines a frequency location that can be the center frequency of the SSB so that the terminal can attempt SSB detection during the initial connection, and this is called the GSCN (Global Synchronization Channel Number). In other words, the SSB transmitted on the non-anchor cell can be specified not to be transmitted on the GSCN. In addition, a separate set of GSCNs can be defined (for terminals with the on-demand SIB1 function).

[0326] - The base station can notify that the cell is a non-anchor cell through the SIB1 PDSCH scheduling DCI (or SSB) transmitted on the non-anchor cell. For example, the base station can notify that the cell is a non-anchor cell by filling the FDRA (Frequency Domain Resource Allocation) field of the SI-RNTI-scrambled DCI with all zeros or all ones. As another example, the base station can notify that the cell is a non-anchor cell by utilizing a 1-bit flag among the reserved bits of the SI-RNTI-scrambled DCI.

[0327] [Proposal #3] A method for providing information about a first cell (e.g., anchor cell) through SSB, etc. on a second cell (e.g., non-anchor cell)

[0328] A base station can indicate that a cell is a non-anchor cell through cell-specific RRC signaling, such as SSB and / or SIB1 and / or SIB, on a non-anchor cell. In this case, information about an on-demand SIB1 procedure (which may include information about UE WUS configuration, etc., and may be at least one of the information listed in [Proposal #1]) may be required for the UE to trigger SIB1 transmission on the non-anchor cell.

[0329] Accordingly, the base station can inform the terminal of the location of the anchor cell that signals the corresponding information. Specifically, the base station can provide at least one of the following information about the anchor cell via cell-specific RRC signaling, such as SSB and / or SIB1 and / or SIB, on the corresponding non-anchor cell.

[0330] (1) Physical cell ID (PCI): A single PCI can be generated by combining the PSS and SSS. For example, up to 1008 PCIs can be generated in a 5G NR system. The base station can designate one of the values ​​(or only a portion of the information). A terminal that moves to the associated anchor cell corresponding to the PCI and receives an SSB can expect to receive an SSB containing the corresponding PCI value (or a PCI value corresponding to the indicated portion of the information).

[0331] (2) Global cell ID (GCI): A unique ID that distinguishes a cell / base station, etc. can be defined. For example, in 5G NR, it is defined as NCGI (NR cell global identity), and is generated through the concatenation of PLMN-ID and 36-bit NCI (NR Cell Identity). The base station can designate one of the values ​​(or only part of the information). A terminal that moves to the associated anchor cell corresponding to the GCI and receives an SIB can expect to receive an SIB that includes the GCI value (or a GCI value corresponding to the indicated part of the information).

[0332] (3) Frequency location information of SSB: The base station can report the frequency location (e.g., center frequency) of the SSB transmitted on the associated anchor cell. For example, in the case of 5G NR, the center frequency of the SSB can be signaled through a parameter called NR-ARFCN. The base station can specify the frequency location information of the SSB. A terminal that moves to the associated anchor cell corresponding to the frequency location information of the SSB and receives the SSB can expect the SSB to be detected based on the frequency location information of the SSB.

[0333] At least one of the frequency location information of PCI, GCI, and SSB as described above can be indicated through the PBCH payload. Specifically, k in Table 1 below SSB =30 reserved states and k in Table 2 SSB =At least one of the frequency location information of PCI, GCI, and SSB of the first cell (e.g., Anchor cell / Cell A) can be indicated through the reserved states for 14.

[0334] Tables 1 and 2 are excerpts from Tables 13-16 and 13-17 in the current NR standard document, TS 38.213. Table 1 is k SSB and the combination of the controlResourceSetZero parameter and the searchSpaceZero parameter included in pdcch-ConfigSIB1 and the N of FR1 (frequency range 1). GSCN Offset Table 2 shows the mapping between k SSB and the combination of the controlResourceSetZero parameter and the searchSpaceZero parameter included in pdcch-ConfigSIB1 and the N of FR1 (frequency range 1). GSCNOffset It shows the mapping between the liver.

[0335] k SSB 16ХcontrolResourceSetZero +searchSpaceZeroN GSCN Offset 240, 1, ..., 2551, 2, ..., 256250, 1, ..., 255257, 258, ..., 512260, 1, ..., 255513, 514, ...., 768270, 1, ..., 255-1, -2, ..., -256280, 1, ..., 255-257, -258, ..., -512290, 1, ..., 255-513, -514, ...., -768300, 1, ..., 255Reserved, Reserved, ..., Reserved

[0336] k SSB 16ХcontrolResourceSetZero +searchSpaceZeroN GSCN Offset 120, 1, ..., 2551, 2, ..., 256130, 1, ..., 255-1, -2, ..., -256140, 1, ..., 255Reserved, Reserved, ..., Reserved

[0337] According to the current NR standard, for FR1 k SSB 0 to 23 are used to indicate the subcarrier offset for CORESET when it is provided for SIB1, and k SSB 24 to 29 are used to indicate the GSCN offset from the GSCN of the current SSB to the GSCN of the CD-SSB. For example, if the 16ХcontrolResourceSetZero +searchSpaceZero value calculated based on the current SSB is 1, and k SSB If 24 is indicated, the terminal can receive CD-SSB at the GSCN + 2 position of the current SSB and receive SIB1 based on it. Meanwhile, k of FR1SSB =30 and k of FR2 SSB =14 is not used for GSCN offset indication purposes as it is a reserved state in the current NR standard.

[0338] Therefore, as an example of the present disclosure, k in FR1 SSB When the value (or the value set / indicated by the higher layer parameter ssb-SubcarrierOffset carried in the MIB) is 30, at least one of the frequency location information of PCI, GCI, and SSB for the anchor cell can be signaled by utilizing all or part of the 256 reserved states corresponding to [16*{controlResourceSetZero value carried in the MIB} + {searchSpaceZero value carried in the MIB}].

[0339] For example, in FR2 k SSB When the value (or the value set / indicated by the ssb-SubcarrierOffset, which is a higher layer parameter carried in the MIB) is 14, at least one of the frequency location information of PCI, GCI, and SSB for the anchor cell can be signaled by utilizing all or part of the 256 reserved states corresponding to [16*{controlResourceSetZero value carried in the MIB} + {searchSpaceZero value carried in the MIB}]. Here, controlResourceSetZero and searchSpaceZero are each 4 bits of information, and are higher layer parameters that configure the PDCCH-ConfigSIB1 IE in the MIB of the SSB.

[0340] All or part of the reserved states are the interval from the GSCN (corresponding to the SSB on the non-anchor cell) to the GSCN corresponding to the SSB transmitted on the anchor cell (associated with the non-anchor cell) (the interval is conveniently called GSCN distance (named as ) can be signaled. Specifically, k in FR1 from the SSB detected by the terminal SSB The value is 30 or k in FR2 SSB If the signaling that the value is 14 is received, the terminal can recognize that the corresponding cell from the SSB is a non-anchor cell. Also, when [16*{controlResourceSetZero value carried in MIB} + {searchSpaceZero value carried in MIB}] (or some of the corresponding values ​​from 0 to 255) is N (N value can be an integer value from 0 to 255), the N corresponding to N GSCN Offset When the value is defined as K, the GSCN of the detected SSB (the corresponding GSCN is N GSCN Reference GSCN (i.e. N) moved by Interval*K (or 3*K in FR2-2) from GSCN Reference + Interval*K or N GSCN Reference The terminal can recognize that the SSB corresponding to the anchor cell is being transmitted at +3*K. Or N GSCN Reference - Interval*K to N GSCN Reference + Interval*K range (or N GSCN Reference + Interval*(K-1) or more / exceeds N GSCN Reference + Interval*K less than / less than range or N GSCN Reference+ Interval*K or more / exceeds N GSCN Reference The terminal can recognize that an SSB corresponding to an anchor cell is being transmitted from any GSCN within a range (less than or equal to + Interval*(K+1)). The Interval value above can be a positive integer value greater than or equal to 1 (e.g., 3), and can be a value defined in advance or set from the anchor cell. The reason why a value greater than 1 is considered is that a maximum of 256 may not be enough to inform the location of the anchor cell.

[0341] Alternatively, some of the 8 bits of information corresponding to the Reserved states (e.g., N1 bits) are used to configure CORESET 0 and / or type0-PDCCH CSS set for SIB1 reception for the non-anchor cell, and the remaining some (e.g., 8-N1 bits) are used to specify the interval from the GSCN (corresponding to the SSB on the non-anchor cell) to the GSCN corresponding to the SSB transmitted on the anchor cell (associated with the non-anchor cell) (the interval is conveniently called GSCN distance (named as ) can be signaled. Specifically, k in FR1 from the SSB detected by the terminal SSB The value is 30 or k in FR2 SSBIf the signaling that the value is 14 is received, the terminal can recognize that the corresponding cell from the SSB is a non-anchor cell. It sets CORESET 0 (or type0-PDCCH CSS set) by using N1 bits (e.g., N1=4 and the 4 bits of information are in the controlResourceSetZero field) carried in the MIB, and uses the remaining 8-N1 bits (e.g., 8-N1=4 and the 4 bits of information are in the {searchSpaceZero field carried in the MIB}) to set GSCN. distance Related information can be set. Specifically, when {searchSpaceZero value included in MIB} is N (N value can be an integer value from 0 to 15), N corresponding to N GSCN Offset When the value is defined as K, the GSCN of the detected SSB (the corresponding GSCN is N GSCN Reference GSCN (i.e. N) moved by Interval*K (or 3*K in FR2-2) from GSCN Reference + Interval*K or N GSCN Reference The terminal can recognize that the SSB corresponding to the anchor cell is being transmitted at +3*K. Or N GSCN Reference - Interval*K to N GSCN Reference + Interval*K range (or N GSCN Reference + Interval*(K-1) or more / exceeds N GSCN Reference + Interval*K less than / less than range or N GSCN Reference + Interval*K or more / exceeds N GSCN Reference+ Interval*(K+1) less than / less than) the range) can recognize that the SSB corresponding to the anchor cell is being transmitted in any GSCN. The Interval value in the above can be a positive integer greater than or equal to 1, and can be a value defined in advance or set from the anchor cell. The reason why a value greater than 1 is considered is that it may not be enough to inform the location of the anchor cell with only 16 at most. If the CORESET 0 and / or type0-PDCCH CSS set configuration information for SIB1 reception for a non-anchor cell acquired from the reserved state is insufficient (e.g., when only the CORESET 0 configuration information is set from the reserved state), the remaining information (e.g., type0-PDCCH CSS set configuration information) can be received by the terminal from the SIB on the anchor cell, etc.

[0342] Alternatively, all or some of the reserved states are {GSCN distance , PCI} can be signaled. For example, [16*{controlResourceSetZero value carried in MIB} + {searchSpaceZero value carried in MIB}] (or some of the corresponding values ​​from 0 to 255) or {searchSpaceZero value carried in MIB} is N1, then {GSCN distance =3, PCI=500}, N2 side {GSCN distance =10, PCI=400} can be defined in advance. If the terminal detects an SSB and recognizes that the corresponding cell from the SSB is a non-anchor cell, if [16*{controlResourceSetZero value carried in MIB} + {searchSpaceZero value carried in MIB}] is N1, then N GSCN Reference + Interval*K or NGSCN Reference It can be seen that the SSB corresponding to the anchor cell is being transmitted at +3*K and the PCI value of the SSB is 500. At this time, the Interval value can be a positive integer value greater than or equal to 1, and can be a value defined in advance or set from the anchor cell. The reason why a value greater than 1 is considered is because it may not be enough to inform the location of the anchor cell with only a maximum of 256. Alternatively, all or some of the reserved states may be {CORESET 0 and / or type0-PDCCH CSS set setting for SIB1 reception for non-anchor cells, GSCN distance} can signal a combination of .

[0343] When the terminal detects an SSB and recognizes that the corresponding cell from the SSB is a non-anchor cell (i.e., k in FR1 from the SSB detected by the terminal), SSB The value is 30 or k in FR2 SSB If a signaling value of 14 is received), if an SSB is detected that does not match the information corresponding to [16*{controlResourceSetZero value carried in MIB} + {searchSpaceZero value carried in MIB}], the terminal can consider that the cell is not an anchor cell corresponding to the previously discovered non-anchor cell.

[0344] The terminal transmits SSB in FR1 from the non-anchor cell. SSB The value is 30 or k in FR2 SSBIf a signaling value of 14 is received, then information about the anchor cell can be transmitted by utilizing the reserved state as suggested above if the SSB is transmitted from the synchronization raster, whereas if the SSB is not transmitted from the synchronization raster, {controlResourceSetZero value carried in MIB} and {searchSpaceZero value carried in MIB} (in FR1 k SSB Value is less than 23 or k in FR2 SSB Each CORESET 0 and type0-PDCCH CSS set configuration information can be transmitted (such as when the value is 11 or less).

[0345] The GSCN through which the SSB is transmitted on the non-anchor cell may be a GSCN value defined for existing terminals and / or terminals that do not have the on-demand SIB1 function, or (as in the above [Proposal #2]) may not be a GSCN value that is not defined for existing terminals and / or terminals that do not have the on-demand SIB1 function. In the latter case, a separate set of GSCNs may be defined for terminals that have the on-demand SIB1 function, and information on whether the cell is a non-anchor cell or not may be transmitted through the SSB (and / or associated SIB) corresponding to the GSCN.

[0346] Figure 19 illustrates a SIB1 transmission and reception procedure between a network and a terminal according to one embodiment.

[0347] Referring to FIG. 19, the terminal can receive configuration information (e.g., SSB, SIB1, SIBx and / or dedicated / common RRC signaling, etc.) from the first cell (e.g., Cell A) (1901). The configuration information may include at least one of information about the second cell (e.g., NES cell), a cell index, a TRP index, a CORESET pool index and / or PCI for the second cell, a configuration for PRACH resources as a UE WUS for requesting SIB1 transmission on the second cell, a search space set on the second cell for RAR-related PDCCH (DCI) reception and / or configuration information for CORESET, as proposed in [Proposal #1].

[0348] The terminal may perform a random access procedure (1902) in the second cell to request SIB1 transmission on the second cell. Upon receiving a response (e.g., RAR and / or Msg4) to the SIB1 transmission request from the base station through the random access procedure, the terminal may receive SIB1 in the second cell (1903).

[0349] When there are multiple frequency bands operated by a base station, for the purpose of NES, SSB and / or system information may be periodically transmitted only in a specific frequency band, and the corresponding signals / channels may not be periodically transmitted in the remaining frequency bands. In order to support such operation of the base station while supporting stable communication of the terminal in the corresponding frequency band, this specification proposes an on-demand SIB1 operation method (specifically, a method for providing information about a non-anchor cell through SSB and / or SIB1 on an anchor cell, a method for controlling access of an existing terminal in a non-anchor cell, and a method for providing information about an anchor cell through SSB, etc. on a non-anchor cell).

[0350] FIG. 20 illustrates a flow of a method performed by a terminal according to one embodiment.

[0351] Referring to FIG. 20, the terminal can obtain system information from the first cell (2005).

[0352] The terminal may transmit a random access preamble to the second cell to request transmission of SIB1 (system information block 1) of the second cell (2010).

[0353] The terminal can monitor DCI (downlink control information) related to random access response in the second cell based on RA-RNTI (random access-radio network temporary identifier) ​​(2015).

[0354] The system information acquired from the first cell may include configuration information for a search space set of the second cell for monitoring the DCI.

[0355] The terminal can obtain information about the frequency location of the first SSB (synchronization signal block) of the first cell based on the second SSB (synchronization signal block) of the second cell.

[0356] The terminal can obtain information on the frequency position of the first SSB based on the value of the parameter kSSB included in the second SSB being set to 30 for the first frequency range or 14 for the second frequency range.

[0357] The terminal may determine a frequency offset value based on a first parameter for CORESET (control resource set) 0 included in the second SSB and a second parameter for search space set 0, and determine that the first SSB is provided at a position offset by an integer multiple of the frequency offset value from the frequency position of the second SSB.

[0358] The integer values ​​for the above integer multiples may be different for each of the first frequency range and the second frequency range.

[0359] The terminal can receive the first SSB in the first cell based on information about the frequency location of the first SSB.

[0360] The system information of the first cell can be obtained based on the first SSB.

[0361] The system information acquired from the first cell may further include at least one of information on whether the SIB1 is being transmitted on the second cell, a start time of the SIB1 transmission, and an end time of the SIB 1 transmission.

[0362] Transmission of the random access preamble for requesting the SIB1 transmission may be triggered based on a system information update in the second cell.

[0363] The terminal may receive a PDSCH (physical downlink shared channel) related to the random access response based on the DCI, and may receive the SIB1 in the second cell.

[0364] FIG. 21 illustrates a flow of a method performed by a base station according to one embodiment.

[0365] Referring to FIG. 21, the base station can transmit system information in the first cell (2105).

[0366] The base station can receive a random access preamble requesting transmission of SIB1 (system information block 1) of the second cell from the second cell (2110).

[0367] The base station can transmit DCI (downlink control information) related to a random access response in the second cell based on a random access-radio network temporary identifier (RA-RNTI) (2115).

[0368] The system information transmitted from the first cell may include configuration information for a search space set of the second cell for transmission of the DCI.

[0369] The base station can provide information on the frequency location of the first SSB (synchronization signal block) of the first cell based on the second SSB (synchronization signal block) of the second cell.

[0370] The base station can provide information on the frequency position of the first SSB by setting the value of the parameter kSSB included in the second SSB to 30 for the first frequency range or to 14 for the second frequency range.

[0371] The base station may indicate a frequency offset value based on a first parameter for CORESET (control resource set) 0 included in the second SSB and a second parameter for search space set 0, and provide the first SSB at a position offset by an integer multiple of the frequency offset value from the frequency position of the second SSB.

[0372] The integer values ​​for the above integer multiples may be different for each of the first frequency range and the second frequency range.

[0373] The base station can transmit the first SSB in the first cell based on information about the frequency location of the first SSB.

[0374] The system information of the first cell may be provided based on the first SSB.

[0375] The system information transmitted from the first cell may further include at least one of information on whether the SIB1 is being transmitted on the second cell, a start time of the SIB1 transmission, and an end time of the SIB 1 transmission.

[0376] The random access preamble requesting the above SIB1 transmission may be transmitted based on a system information update in the second cell.

[0377] The base station can transmit a PDSCH (physical downlink shared channel) related to the random access response based on the DCI, and transmit the SIB1 in the second cell.

[0378] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0379] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the scope of the present disclosure. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0380] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method performed by a terminal, Obtain system information from cell 1; Transmitting a random access preamble to the second cell to request transmission of SIB1 (system information block 1) of the second cell; and Including monitoring DCI (downlink control information) related to random access response based on RA-RNTI (random access-radio network temporary identifier) ​​in the second cell, A method wherein the system information acquired from the first cell includes configuration information for a search space set of the second cell for monitoring the DCI.

2. In paragraph 1, A method in which the terminal obtains information on the frequency location of the first SSB (synchronization signal block) of the first cell based on the second SSB (synchronization signal block) of the second cell.

3. In paragraph 2, The above terminal includes parameter k in the second SSB. SSB A method for obtaining information on the frequency position of the first SSB, based on the value of which is set to 30 for the first frequency range or 14 for the second frequency range.

4. In paragraph 2, the terminal, Determine a frequency offset value based on a first parameter for CORESET (control resource set) 0 included in the second SSB and a second parameter for search space set 0, A method for determining that the first SSB is provided at a position offset by an integer multiple of the frequency offset value from the frequency position of the second SSB.

5. In paragraph 4, The integer values ​​for the above integer multiples are different for each of the first frequency range and the second frequency range.

6. In paragraph 2, Further comprising receiving the first SSB in the first cell based on information about the frequency location of the first SSB, A method in which the system information of the first cell is obtained based on the first SSB.

7. In paragraph 1, A method wherein the system information obtained from the first cell further includes at least one of information on whether the SIB1 is being transmitted on the second cell, a start time of the SIB1 transmission, and an end time of the SIB 1 transmission.

8. In paragraph 1, A method wherein transmission of the random access preamble for requesting the SIB1 transmission is triggered based on a system information update in the second cell.

9. In paragraph 1, Receiving a PDSCH (physical downlink shared channel) related to the random access response based on the DCI; and A method further comprising receiving the SIB1 in the second cell.

10. A non-transitory computer-readable recording medium having recorded thereon a program for performing the method described in paragraph 1.

11. In the device, a memory configured to store instructions; and A processor configured to perform operations by executing the above instructions, The operations of the above processor are: Obtain system information from cell 1; Transmitting a random access preamble to the second cell to request transmission of SIB1 (system information block 1) of the second cell; and Including monitoring DCI (downlink control information) related to random access response based on RA-RNTI (random access-radio network temporary identifier) ​​in the second cell, A method wherein the system information acquired from the first cell includes configuration information for a search space set of the second cell for monitoring the DCI.

12. In paragraph 11, Including a transmitter and receiver, The above device is a terminal operating in a wireless communication system.

13. In paragraph 11, The above device is a processing device configured to control a terminal operating in a wireless communication system.

14. In a method performed by a base station, Transmit system information from cell 1; Receiving a random access preamble requesting transmission of SIB1 (system information block 1) of the second cell from the second cell; and Including transmitting DCI (downlink control information) related to a random access response based on RA-RNTI (random access-radio network temporary identifier) ​​in the second cell, A method wherein the system information transmitted from the first cell includes configuration information for a search space set of the second cell for transmission of the DCI.

15. At the base station, a memory configured to store instructions; and A processor configured to perform operations by executing the above instructions, The operations of the above processor are: Transmit system information on the first cell; Receiving a random access preamble requesting SIB1 from a terminal in a second cell that provides SIB1 on an on-demand basis; and Including transmitting DCI (downlink control information) related to a random access response based on RA-RNTI (random access-radio network temporary identifier) ​​in the second cell, A base station, wherein the system information transmitted from the first cell includes configuration information for a search space set of the second cell for transmission of the DCI.

Images