Method and device for performing uplink transmission and reception in wireless communication system

Abstract

Disclosed are a method and a device for performing uplink transmission and reception in a wireless communication system. The method according to an embodiment of the present disclosure may comprise the steps of: receiving first configuration information related to a system information block request from a base station by a terminal, wherein the first configuration information includes parameters associated with each of a plurality of neighboring cell groups; transmitting, by the terminal to the base station, a first uplink channel including a first parameter associated with a first neighboring cell group among the plurality of neighboring cell groups; and receiving, by the terminal from the base station, a first system information block for the first neighboring cell group.

Description

Method and device for performing uplink transmission and reception in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing uplink transmission and reception in a wireless communication system.

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

[0003] The 6G wireless communication system is being developed with the goals of (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity. Considering the requirements of the 6G system, such as a peak data rate of 1 Tbps per device, an end-to-end latency of 1 ms, a maximum spectrum efficiency of 100 bps / Hz, support for mobility of 1000 km / h, satellite integration, artificial intelligence (AI), autonomous vehicles, extended reality (XR), and haptic communication, various technologies are being researched.

[0004] The technical problem of the present disclosure is to provide a method and device for performing uplink transmission and reception in a wireless communication system.

[0005] In addition, an additional technical problem of the present disclosure is to provide a method and device for transmitting and receiving a random access preamble.

[0006] In addition, an additional technical problem of the present disclosure is to provide a method and device for performing on-demand synchronization signal block (SSB) and / or system information block (SIB) transmission and reception operations.

[0007] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0008] A method according to one aspect of the present disclosure may include: receiving, by a terminal, from a base station first configuration information related to a system information block request, the first configuration information including parameters related to each of a plurality of neighboring cell groups; transmitting, by the terminal, to the base station a first uplink channel including a first parameter related to a first neighboring cell group among the plurality of neighboring cell groups; and receiving, by the terminal, from the base station a first system information block for the first neighboring cell group.

[0009] A method according to another aspect of the present disclosure may include the steps of: transmitting, by a base station, first configuration information related to a system information block request to a terminal, wherein the first configuration information includes parameters related to each of a plurality of neighboring cell groups; receiving, by the base station, from the terminal a first uplink channel including a first parameter related to a first neighboring cell group among the plurality of neighboring cell groups; and transmitting, by the base station, a first system information block for the first neighboring cell group to the terminal.

[0010] According to various embodiments of the present disclosure, a method and apparatus for performing uplink transmission and reception in a wireless communication system can be provided.

[0011] Additionally, various embodiments of the present disclosure may provide a method and device for transmitting and receiving a random access preamble.

[0012] Additionally, various embodiments of the present disclosure may provide methods and devices for performing on-demand SSB and / or SIB transmission and reception operations.

[0013] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0014] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0015] Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.

[0016] FIG. 2 illustrates an example of a communication system to which some examples of the present disclosure may be applied.

[0017] FIG. 3 illustrates an example of a wireless device to which some examples of the present disclosure may be applied.

[0018] FIG. 4 exemplarily illustrates a communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

[0019] FIG. 5 illustrates a functional framework for AI operations to which some examples of the present disclosure may be applied.

[0020] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0021] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0022] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0023] FIG. 9 illustrates an electromagnetic spectrum to which some examples of the present disclosure may be applied.

[0024] FIG. 10 illustrates an example of a system information transmission / reception procedure to which some examples of the present disclosure may be applied.

[0025] FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.

[0026] Figures 12 and 13 illustrate examples of NTN scenarios to which some examples of the present disclosure may be applied.

[0027] FIG. 14 illustrates examples of sensing operations to which some examples of the present disclosure may be applied.

[0028] FIG. 15 illustrates an example of cell DTX / DRX operation to which some examples of the present disclosure may be applied.

[0029] FIG. 16 illustrates an example of carrier aggregation (CA) operation including an SSB-less cell to which some examples of the present disclosure may be applied.

[0030] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.

[0031] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.

[0032] FIG. 19 illustrates an example of an on-demand SIB1 transmission procedure to which some examples of the present disclosure may be applied.

[0033] FIG. 20 illustrates an example of an on-demand SI transmission and reception procedure within a RACH procedure to which some examples of the present disclosure may be applied.

[0034] FIG. 21 illustrates an RO according to SSB ID to which some examples of the present disclosure may be applied.

[0035] FIG. 22 illustrates an example of a Msg. 1 based SI request procedure to which some examples of the present disclosure may be applied.

[0036] FIG. 23 is a flowchart illustrating a method for a terminal to perform a communication procedure according to one embodiment of the present disclosure.

[0037] FIG. 24 is a flowchart illustrating a method for a base station to perform a communication procedure according to one embodiment of the present disclosure.

[0038] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

[0039] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0040] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0041] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0042] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

[0043] In this disclosure, "A or B" can mean "only A," "only B," or "both A and B." In other words, "A or B" in this disclosure can be interpreted as "A and / or B." For example, "A, B or C" in this disclosure can mean "only A," "only B," "only C," or "any combination of A, B and C."

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

[0045] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0046] Additionally, in the present disclosure, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0047] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be described as an example of "control information." In other words, "control information" in the present disclosure is not limited to "PDCCH," and "PDCCH" may be described as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be described as an example of "control information."

[0048] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0049] Technical features individually described in one drawing in this disclosure may be implemented individually or simultaneously.

[0050] In the present disclosure, a terminal or user equipment (UE) may be a portable device and may be a first node that receives a signal from a base station / second node / IAB (integrated access backhaul) node.

[0051] In the present disclosure, a base station (BS) may be a second node / IAB node / Transmission-Reception Point (TRP).

[0052] In the present disclosure, higher layer parameters may be parameters configured, pre-configured, or pre-defined for the terminal. For example, a base station or a network may transmit higher layer parameters to the terminal. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0053] In the present disclosure, "setting or defining" may be interpreted as being set to a device through predefined signaling (e.g., SIB (system information block), MAC, RRC) from a base station or network. In the present disclosure, "setting or defining" may be interpreted as being set to a device through separate signaling or being defined in advance without separate signaling.

[0054] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

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

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

[0057] Network structure

[0058] Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.

[0059] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as integrated access backhaul (IAB) nodes, relays, and radio frequency (RF) repeaters, as illustrated in Figure 1, may be applied, or a non-terrestrial network (NTN) may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, or in the case of a network-controlled repeater, it may not only amplify and forward signals but also adjust its transmission and reception settings based on information provided by the network. For example, NTN nodes could be satellites or aircraft that provide NTN coverage that terrestrial networks struggle to provide. Beyond these examples, various intermediate points can be introduced to improve the network topology.

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

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

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

[0063] As such, in some examples of the present disclosure, for the sake of simplicity of explanation, the subjects of the operation may be referred to as terminals and / or base stations (or first nodes and / or second nodes). In addition, the terms terminal and / or base station (or first node and / or second node) may also be interpreted / replaced as in the following examples: For example, the terminal (or first node) and the base station (or second node) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.

[0064] In the present disclosure, there may be zero or more intermediate points between the base station and the terminal. If an intermediate point exists, it may correspond to an IAB node / relay / RF repeater / NTN node, or a node supporting other functions. The intermediate point may be a node with a fixed location or a node with an unfixed location.

[0065] Systems applicable to this disclosure

[0066] FIG. 2 illustrates an example of a communication system to which some examples of the present disclosure may be applied.

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

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

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

[0070] Device applicable to the present disclosure

[0071] FIG. 3 illustrates an example of a wireless device to which some examples of the present disclosure may be applied.

[0072] 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).

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

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

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

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

[0077] At least one transceiver (206) can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed in this document from at least one other device. For example, at least one transceiver (206) can be connected to at least one processor (202) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. Additionally, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document via at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using at least one processor (202).At least one transceiver (206) may convert user data, control information, wireless signals / channels, etc. processed by at least one processor (202) from a baseband signal to an RF band signal. For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

[0078] 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).

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

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

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

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

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

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

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

[0086] Communication procedures

[0087] FIG. 4 exemplarily illustrates a communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

[0088] FIG. 4 illustrates operations of a first node (110) (e.g., a terminal) and a second node (120) (e.g., a base station) transmitting and / or receiving data and operations performed prior thereto.

[0089] In step S101, the first node (110) and the second node (120) can perform synchronization. For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect at least one synchronization signal transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals (e.g., a primary synchronization signal, a secondary synchronization signal) classified according to a structure or purpose. Through this, the terminal (110) can confirm the boundaries of the frame, subframe, slot, and / or symbol of the base station (120) and obtain information (e.g., a cell identifier) ​​about the base station (120).

[0090] In step S103, the first node (110) can obtain system information transmitted from the second node (120). For example, the system information is information related to the properties, characteristics, and / or capabilities of the base station (120) required to access the base station (120) and use the service, and can be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., the channel used, whether it is provided in an on-demand manner), etc., and can be classified into, for example, a master information block (MIB) and a system information block (SIB). If necessary, the terminal (110) can transmit a signal requesting system information before receiving the system information. Such requesting and providing of system information may be performed after a random access procedure described below.

[0091] In step S105, the first node (110) and the second node (120) can perform a random access procedure. For example, the terminal (110) can transmit and / or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for a random access procedure based on information related to a random access channel of the base station (120) obtained through system information (e.g., channel position, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) may transmit a preamble (e.g., message 1 (MSG1)) over a random access channel, receive a random access response (RAR) message (e.g., message 2 (MSG2)), transmit a message (e.g., message 3 (MSG3)) including information related to the terminal (110) (e.g., identification information) using scheduling information included in the RAR message to the base station (120), and receive a message for contention resolution and / or connection establishment (e.g., message 4 (MSG4)). As another example, MSG1 and MSG3 may be transmitted and received as one message (e.g., message A (MSG A)), or MSG2 and MSG4 may be transmitted and received as one message (e.g., message B (MSG B)).

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

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

[0094] 6G system core technologies

[0095] As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, free space optics (FSO) backhaul network, massive MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0096] artificial intelligence

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

[0098] FIG. 5 illustrates a functional framework for AI operations to which some examples of the present disclosure may be applied.

[0099] Below, to explain AI (or AI / ML (machine learning)) in more detail, the terms can be defined as follows.

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

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

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

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

[0104] Referring to FIG. 5, the data collection function (10) is a function that collects input data and provides processed input data to the model training function (20) and the model inference function (30).

[0105] Examples of input data may include measurements from terminals or other network entities, feedback from actors, and output from AI models.

[0106] The data collection function (10) performs data preparation based on input data and provides input data processed through the data preparation. Here, the data collection function (10) does not perform data preparation specific to each AI algorithm (e.g., data pre-processing and cleaning, formatting, and transformation), but can perform data preparation common to all AI algorithms.

[0107] After the data preparation process is performed, the data collection function (10) may provide training data (11) to the model training function (20) and may provide inference data (12) to the model inference function (30). Here, the training data (11) may correspond to data required as input for the AI ​​model training function (20), and the inference data (12) may correspond to data required as input for the AI ​​model inference function (30).

[0108] The data collection function (10) may be performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), but may also be performed by multiple entities. In this case, training data (11) and inference data (12) may be provided to the model training function (20) and model inference function (30), respectively, from multiple entities.

[0109] The model training function (20) may correspond to a function that performs AI model training, validation, and testing, which can generate model performance metrics as part of the AI ​​model testing procedure. If necessary, the model training function (20) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation, etc.) based on training data (11) provided by the data collection function (10).

[0110] Here, model deployment / update (13) can be used to initially deploy a trained, validated and tested AI model to the model inference function (30) or to provide an updated model to the model inference function (30).

[0111] The model inference function (30) may correspond to a function that provides AI model inference output (16) (e.g., prediction or decision). If applicable, the model inference function (30) may provide model performance feedback (14) to the model training function (20). In addition, the model inference function (30) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting and transformation, etc.) based on inference data (12) provided by the data collection function (10), if necessary.

[0112] Here, output (16) refers to the inference output of the AI ​​model generated by the model inference function (30), and the details of the inference output may vary depending on the use case.

[0113] Model performance feedback (14) can be used to monitor the performance of the AI ​​model, if available, and this feedback may be omitted.

[0114] An actor function (40) is a function that receives an output (16) from a model inference function (30) and triggers or performs a corresponding task / action. The actor function (40) can trigger tasks / actions for other entities (e.g., one or more terminals, one or more RAN nodes, one or more network nodes, etc.) or for itself.

[0115] Feedback (15) can be used to derive training data (11), inference data (12), or to monitor the performance of the AI ​​model, its impact on the network, etc.

[0116] Meanwhile, the definitions of training / validation / test in data sets used in AI / ML can be distinguished as follows.

[0117] - Training data: refers to a data set for learning a model.

[0118] - Validation data: This refers to a dataset used to validate a model that has already completed training. Validation data can typically be used to prevent overfitting of the training data set. It can also be used to select the best model among the various models learned during the training process. Therefore, validation can be considered a type of learning.

[0119] - Test data: This refers to the data set for final evaluation. This data is unrelated to learning.

[0120] For example, the training and validation data can be divided into an 8:2 or 7:3 ratio within the entire data set. Alternatively, the training data:validation data:test data can be divided into a 6:2:2 ratio within the entire data set.

[0121] The level of cooperation can be defined as follows depending on whether the base station and the terminal have capabilities for AI / ML functions, and variations due to combination of multiple levels or separation of any one level are also possible.

[0122] Category 0a: This category corresponds to a no-collaboration framework. In this case, AI / ML algorithms are purely implementation-based and may not require any changes to the wireless interface.

[0123] Category 0b: Frameworks that involve a wireless interface modified to fit efficient implementation-based AI / ML algorithms, but without collaboration.

[0124] Category 1: This category applies to cases where inter-node support is required to improve the AI / ML algorithms of each node. For example, this applies when a terminal receives support from a base station (for training, adaptation, etc.), and vice versa. At this level, model exchange between network nodes is not required.

[0125] Category 2: This applies to cases where joint ML tasks can be performed between terminals and base stations. This level requires exchange of AI / ML model commands or network nodes.

[0126] The functions exemplified in FIG. 5 above may be implemented in a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.), a network node, an OAM (operation administration maintenance) of a network operator, or a terminal.

[0127] Alternatively, two or more entities, such as a RAN, a network node, a network operator's OAM, or a terminal, may cooperate to implement the functions illustrated in FIG. 5. For example, one entity may perform some of the functions of FIG. 5, and another entity may perform the remaining functions. In this way, since some of the functions illustrated in FIG. 5 are performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), the transmission / provision of data / information between each function may be omitted. For example, if the model training function (20) and the model inference function (30) are performed by the same entity, the transmission / provision of model deployment / update (13) and model performance feedback (14) may be omitted.

[0128] Alternatively, any one of the functions illustrated in FIG. 5 may be performed collaboratively by two or more entities, including a RAN, a network node, a network operator's OAM, or a terminal. This may be referred to as a split AI operation.

[0129] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0130] For example, the AI ​​model training function may be performed by a network node (e.g., a core network node, an OAM of a network operator, etc.), and the AI ​​model inference function may be performed by a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.).

[0131] Step 1: RAN node 1 and RAN node 2 can transmit input data (e.g., training data) for AI model training to the network node. Here, RAN node 1 and RAN node 2 can also transmit data collected from the terminal (e.g., terminal measurements related to RSRP (reference signal received power), RSRQ (reference signal received quality), SINR (signal to interference-plus-noise ratio) of the serving cell and neighboring cells, terminal location, speed, etc.) to the network node.

[0132] Step 2: Network nodes can train AI models using the received training data.

[0133] Step 3: The network node may distribute / update the AI ​​model to RAN node 1 and / or RAN node 2. RAN node 1 (and / or RAN node 2) may also continue model training based on the received AI model.

[0134] For convenience of explanation, we assume that the AI ​​model is deployed / updated only to RAN node 1.

[0135] Step 4: RAN node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN node 2.

[0136] Step 5: RAN node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0137] Step 6: If applicable, RAN node 1 may send model performance feedback to the network nodes.

[0138] Step 7: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.

[0139] Step 8: RAN node 1 and RAN node 2 can transmit feedback information to the network nodes.

[0140] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0141] For example, both AI model training functions and AI model inference functions can be performed by RAN nodes (e.g., base stations, TRPs, CUs of base stations, etc.).

[0142] Step 1: The terminal and RAN node 2 can transmit input data (e.g., training data) for AI model training to RAN node 1.

[0143] Step 2: RAN node 1 can train an AI model using the received training data.

[0144] Step 3: RAN node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN node 2.

[0145] Step 4: RAN node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0146] Step 5: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.

[0147] Step 6: RAN node 2 may transmit feedback information to RAN node 1.

[0148] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0149] For example, the AI ​​model training function may be performed by a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.), and the AI ​​model inference function may be performed by a terminal.

[0150] Step 1: The terminal may transmit input data (e.g., training data) for AI model training to the RAN node. Here, the RAN node may collect data (e.g., terminal measurements related to RSRP, RSRQ, SINR of the serving cell and neighboring cells, terminal location, speed, etc.) from various terminals and / or from other RAN nodes.

[0151] Step 2: RAN nodes can train AI models using the received training data.

[0152] Step 3: The RAN node can distribute / update the AI ​​model to the terminal. The terminal can also continue model training based on the received AI model.

[0153] Step 4: Input data (e.g., inference data) for AI model inference can be received from the terminal and RAN node (and / or from another terminal).

[0154] Step 5: The terminal can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0155] Step 6: If applicable, the terminal may send model performance feedback to the RAN node.

[0156] Step 7: The terminal and RAN node can perform actions based on the output data.

[0157] Step 8: The terminal may transmit feedback information to the RAN node.

[0158] THz communication (terahertz communication)

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

[0160] FIG. 9 illustrates an electromagnetic spectrum to which some examples of the present disclosure may be applied.

[0161] Key characteristics of THz communications include (i) the widely available bandwidth to support very high data rates, and (ii) the high path loss at high frequencies (which necessitates highly directional antennas). The narrow beamwidths generated by highly directional antennas reduce interference. The small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

[0162] Transmitting system information (e.g., MIB) in a cell in the THz frequency band can be inefficient because the beam width in high-frequency bands narrows, requiring more beam sweeps to cover the entire cell area. This method is particularly inefficient when there are only a few users within the cell.

[0163] FIG. 10 illustrates an example of a system information transmission / reception procedure to which some examples of the present disclosure may be applied.

[0164] The example of Fig. 10 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applicable. Furthermore, the procedure illustrated in Fig. 10 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Fig. 10.

[0165] In step S1010, the second node (120) (e.g., base station) can transmit system information of cell #1 via cell #2. For example, the base station provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one of an SFN (system frame number), a PDCCH configuration for SIB1, cell barring, cell re-selection, and subcarrier spacing generated in a higher layer, and may include at least one of an SFN, a half frame indicator, and an SSB index (synchronization signal / PBCH (physical broadcast channel) block index) generated in a physical layer. For this purpose, as an example, cell #1 and cell #2 may have a relationship of a secondary cell and a primary cell.

[0166] At step S1030, the first node (110) (e.g., terminal) can acquire synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information, but since the system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, the terminal can acquire synchronization based on the system information. Alternatively, synchronization acquisition can be performed before step S1010.

[0167] At step S1050, the first node (110) may transmit a signal for accessing cell #1. For example, the signal may include a random access preamble. The structure of this signal and the resources (e.g., channels) for transmitting the signal may be identified through system information. Thereafter, at step S1070, the first node (110) and the second node (120) may perform an access procedure for cell #1 and communicate.

[0168] The procedure described with reference to FIG. 10 may be performed when the first node (110) initially connects to cell #1 of the second node (120). Alternatively, a similar procedure may be performed when the first node (110) hands over to cell #1 of the second node (120). However, in the case of handover, the system information of cell #1 may be received from a cell of a base station other than cell #2 of the second node (120).

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

[0170] FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.

[0171] Although FIG. 11 illustrates an example of a procedure for searching and / or selecting beams for THz communication, this procedure is not limited to a THz environment and can also be applied to a 6G communication environment where THz communication is not applied.

[0172] Here, beam may be interpreted as other terms having equivalent technical meanings that can distinguish beams, such as 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', reference signal (RS) resource that distinguishes beams, SSB index, etc.

[0173] In step S1110, the second node (120) (e.g., base station) can set resources for beam management to the first node (110) (e.g., terminal). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from an existing downlink signal / channel for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can be a different port from a port for transmitting an existing downlink signal / channel (e.g., SSB, PDSCH (physical downlink shared channel), etc.). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. For example, a signal transmitted based on a dedicated port defined / set for beam search can be included in the technical concept according to the present embodiment.

[0174] In step S1130, the second node (120) (e.g., base station) transmits measurement signals using a plurality of transmission beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams that require measurement, and may also be transmitted in a multi-beam transmission method that forms a plurality of beams simultaneously to reduce sweeping time. Here, the multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

[0175] In step S1050, a first node (110) (e.g., a terminal) may transmit a feedback signal to a second node (120) (e.g., a base station). The feedback signal may indicate at least one beam selected by the terminal. The terminal may select at least one preferred beam based on the measurement signals received in step S1030.

[0176] In step S1070, the first node (110) and the second node (120) can perform communication. For example, the second node (120) can perform transmission to the first node (110) using the reception beam of the first node (110) selected in step S1050. If channel reciprocity is established, the transmission beam of the first node (110) can also be determined through steps S1030 and S1050, so that the transmission operation from the first node (110) can also be performed using a beam that has a reciprocal relationship with the beam selected in step S1050. If channel reciprocity is not established, a procedure including transmission of measurement signal(s) by the first node (110) and transmission of feedback signal(s) by the second node (120) may be performed first to determine the transmission beam of the first node (110).

[0177] non-terrestrial networks (NTN)

[0178] Figures 12 and 13 illustrate examples of NTN scenarios to which some examples of the present disclosure may be applied.

[0179] NTN can represent a network or network segment that uses radio frequency (RF) resources mounted on a satellite (or unmanned aerial system (UAS) platform).

[0180] Figure 12 shows an example of a typical scenario of NTN based on transparent payload, and Figure 13 shows an example of a typical scenario of NTN based on regenerative payload.

[0181] Referring to Figure 12, a satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) can be connected to a gateway via a feeder link. The satellite can be connected to a data network via the gateway. The beam footprint can refer to the area where the signal transmitted by the satellite can be received.

[0182] Referring to Figure 13, a satellite (or UAS platform) can establish a service link with a terminal. A satellite (or UAS platform) connected to a terminal can be connected to another satellite (or UAS platform) via an inter-satellite link (ISL). The other satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on the regenerated payload, the satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.

[0183] Figures 12 and 13 are only examples of NTN scenarios, and NTN can be implemented based on various scenarios. For example, a satellite (or UAS platform) can implement a transparent or regenerative (e.g., with onboard processing) payload. For example, a satellite (or UAS platform) can generate multiple beams across a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) can vary depending on the onboard antenna diagram and the minimum elevation angle.

[0184] For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may remain unchanged.

[0185] For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, a regenerative payload may be substantially equivalent to mounting all or part of a base station function on a satellite (or UAS platform).

[0186] Integrated Sensing and Communication (ISAC)

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

[0188] FIG. 14 illustrates examples of sensing operations to which some examples of the present disclosure may be applied.

[0189] Specifically, Fig. 14(a) shows an example of a monostatic sensing operation using a sensing receiver and a sensing transmitter located in the same location. Fig. 14(b) shows an example of a bistatic sensing operation using a sensing receiver and a sensing transmitter located in separate locations. A sensing signal transmitted from a sensing transmitter is reflected / scattered by a sensing object, and the sensing receiver can receive the signal, and extract / obtain sensing data based on the received signal. A sensing result can be generated / determined through appropriate processing of the sensing data. The sensing result can be provided to a trusted third-party entity / service outside the 3GPP system through an entity / service within the 3GPP system.

[0190] Network Energy Saving (NES)

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

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

[0193] For example, a base station may identify the NES solution(s) to be applied, perform signaling to the NES, and perform actions on the NES.

[0194] NES solution(s) may be related to control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement, and reporting. The NES solution(s) to be applied may be adaptively selected or predefined based on current conditions (e.g., cell load level, characteristics of connected terminals, etc.).

[0195] A base station that has identified NES solution(s) performs signaling for the NES. The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information about the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of NES operation to at least one terminal. In addition, the base station may receive capability information related to the NES from at least one terminal.

[0196] Based on the signaled NES-related information, the base station can perform operations for the NES. For example, based on system information, configuration information, and control information conveyed via signaling, the base station can turn on / off transmission and reception of specific signals, turn on / off elements in the spatial domain, or adjust resources for transmission and reception of measurement signals.

[0197] Examples of NES solutions that can be implemented using these procedures include:

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

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

[0200] SSB-less cells: If SSB or SSB-based RRM (radio resource management) measurement timing configuration (SMTC) configuration is not provided for a specific cell (e.g., secondary cell (SCell) or primary cell (PCell)), the UE may obtain timing reference and automatic gain control (AGC) source from another serving cell. In frequency range 1 (FR1) or FR2, the base station may configure intra-band carrier aggregation (CA) or inter-band CA including cells without SSB transmission, in which case SSB / SIB transmission may be triggered by a wake up signal (WUS) of the UE. Accordingly, since the period of common channels / signals such as SSB is increased, the base station may stay in sleep state for a longer time.

[0201] Cell DTX (discontinuous transmission) / DRX (discontinuous reception): In order to reduce the downlink transmission / uplink reception activity time of the base station, a periodic cell DTX / DRX pattern (e.g., active and inactive periods) may be commonly configured for terminals within a cell having the feature. Here, the cell DTX pattern and the cell DRX pattern may be configured and activated separately, and up to two cell DTX / DRX patterns may be configured per MAC entity. When cell DTX is configured and activated, at least one of monitoring for a semi-persistent scheduling (SPS) opportunity or monitoring a PDCCH may be stopped during the cell DTX inactivity period. When cell DRX is configured and activated, at least one of transmission on a configured grant (CG) resource or transmission of a scheduling request (SR) may be stopped during the cell DRX inactivity period. Cell DTX / DRX can be activated / deactivated via RRC signaling or L1 (layer 1) group common signaling.

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

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

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

[0205] Cell DTX / DRX

[0206] To enable base stations to operate in sleep mode for relatively long periods of time without frequent wake-ups, base station DTX / DRX has been introduced for NES purposes. The base station can reduce energy consumption by utilizing DTX transmission under low system load conditions by configuring cell DTX and setting the on-duration of terminals' C-DRX within the active period of the cell DTX.

[0207] FIG. 15 illustrates an example of cell DTX / DRX operation to which some examples of the present disclosure may be applied.

[0208] A second node (120) (e.g., a base station) can transmit system information to a first node (110) (e.g., a terminal). Accordingly, the first node (110) can check information related to the cell DTX / DRX of the second node (120).

[0209] For example, system information may include MIB, SIB1, etc. In relation to NES technology, MIB may include information related to cell barring (e.g., cellBarred), and SIB1 may include information related to cell barring state (e.g., cellBarredNES). For example, if cellBarred included in MIB is set to a value indicating that it is not barred (e.g., notBarred), a terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. For example, if cellBarred included in received MIB is set to a value indicating that the cell is barred (e.g., barred), a terminal that does not support NES cell DTX / DRX may determine that the cell is barred.

[0210] For example, if a terminal has a capability to support NES cell DTX / DRX, the terminal can check SIB1 to determine a cell barring status. For example, if cellBarred of MIB is set to barred and cellBarredNES is absent in SIB1, a terminal supporting NES cell DTX / DRX can treat the cell as barred and perform cell reselection to another cell. For example, if cellBarred of MIB is set to barred and cellBarredNES is included in SIB1, a terminal supporting NES cell DTX / DRX can determine that the cell is not barred.

[0211] In the example of FIG. 15, it is assumed that the terminal has the capability to support NES cell DTX / DRX, and cellBarred of MIB is set to notBarred, or cellBarred of MIB is set to barred and SIB1 includes cellBarredNES. Accordingly, the terminal can perform a random access procedure to connect to the base station, and then perform communication. For example, the base station can perform a cell DTX / DRX operation, and transmit configuration information related to the cell DTX / DRX operation to the terminal. The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). Additionally, the configuration information may further include information for receiving and interpreting cell DRX / DRX-related control information (e.g., cellDTRX-RNTI included in physicalCellGroupConfig, DCI-related information such as the size of DCI format 2_9, etc.).

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

[0213] Control information related to cell DTX / DRX may be used to indicate activation or deactivation of cell DTX and / or cell DRX, and / or to provide NES-mode indicators (e.g., NES-specific CHO execution conditions, etc.), and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, when the serving cell is configured as a supplementary uplink (SUL) carrier, the indication of activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the uplink (UL) carrier and the SUL carrier.

[0214] After that, the terminal and the base station can perform communication based on the cell DTX / DRX. Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, so that the terminal can selectively monitor the signal from the base station. During the DTX-OFF duration, the base station can enter a sleep mode to reduce energy consumption. For example, the base station DTX cycle can be aligned with the cycle of the terminal DRX. The base station DTX-ON duration can completely cover the DRX-ON duration of the terminal. Furthermore, the base station can align the transmission on Xn (base station-to-base station interface) / NG (interface between 5G RAN and 5G core network) and the transmission on Uu (interface between terminal and network) for NES purposes. The DTX / DRX mechanism triggers switching of reference signal resource sets, and the base station can perform a dormancy-like behavior of rarely or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. The terminal can rarely or not receive downlink signals / channels depending on the configuration of the base station. Once the base station DTX / DRX operation is triggered, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH during the DTX / DRX OFF duration.

[0215] SSB-less cells

[0216] FIG. 16 illustrates an example of carrier aggregation (CA) operation including an SSB-less cell to which some examples of the present disclosure may be applied.

[0217] In the example of Figure 16, it is assumed that the SSB-less cell is an SCell in the CA, but the SSB-less cell may also be a PCell in the CA.

[0218] A second node (120) (e.g., a base station) can transmit configuration information for an SCell to a first node (110) (e.g., a terminal). For example, the base station can transmit configuration information for CA to provide a service to the terminal through a CA operation. Here, the CA operation may be an intra-band CA or an inter-band CA. For example, the configuration information for an SCell may include information (e.g., sCellToAddModList) including information for adding an SCell, and specifically, may include a cell index, a physical cell identifier, information related to DL-UL configuration, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Accordingly, the terminal can determine the configuration for the CA operation and perform communication using the PCell and SCell of the base station.

[0219] For example, the terminal can determine that the SCell is an SSB-less SCell based on information related to the downlink frequency included in the configuration information, and can check related parameters. For example, the terminal can determine that the SCell is an SSB-less SCell by checking the presence of a parameter indicating that the SCell is an SSB-less SCell (e.g., SSBlessSCell), and can check the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the example of Fig. 16, the reference cell can be the PCell. Therefore, the terminal can use the PCell as a timing reference and AGC source for communication in the SCell. For example, the reference of the SSB-less cell can be (another) cell, TRP, CORESET pool (control resource set pool), (additional) PCI (physical cell ID), etc.

[0220] Conditional Handover (CHO)

[0221] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.

[0222] The order of the operations illustrated in Fig. 17 may vary depending on the case.

[0223] A second node (120) (e.g., a base station) can transmit configuration information for CHO to a first node (110) (e.g., a terminal). The configuration information for CHO can include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList), information related to configuration for reporting (e.g., ReportConfigNR). For example, the information related to configuration for reporting can include information related to events related to reporting, identifiers of the events (e.g., condEventId), information indicating whether it is a NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 17, it is assumed that event information indicating that it is a NES-specific CHO event is received.

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

[0225] Afterwards, the terminal can perform measurements and transmit a measurement report to the base station. The base station can determine a CHO based on the measurement report and perform signaling for a handover request with the adjacent / neighboring base station(s) indicated by the measurement report. The base station can determine the adjacent base station(s) that have confirmed admission through signaling as candidate base station(s) and transmit information about the candidate base station(s) to the terminal. Accordingly, the terminal can evaluate the CHO execution conditions for the candidate base station(s). Based on the evaluation result, if a candidate cell satisfying the conditions is determined, the terminal can perform detachment for the old cell and synchronization for the new cell.

[0226] For example, based on event information indicating that the event is an NES-specific CHO event received by the terminal in the previous procedure and information enabling an NES-specific CHO execution condition, the terminal can determine whether the event is satisfied. For example, if an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that the event is an NES-specific CHO event (e.g., nesEvent), the terminal can determine that the event associated with the corresponding measurement identifier (e.g., measId) is satisfied, and thus, determine that the CHO execution condition is satisfied.

[0227] Channel State Information (CSI) Measurement and Reporting

[0228] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.

[0229] A second node (120) (e.g., a base station) can transmit configuration information for CSI to a first node (110) (e.g., a terminal). The configuration information for CSI can include information related to a reference signal (e.g., a CSI-RS) resource or a resource set for CSI (e.g., time-frequency resource information, sequence information, power information, etc.), information related to CSI reporting (e.g., report item (quantity) information, report type information, report resource information, codebook information, etc.), information related to CSI measurement, etc.

[0230] For example, to assist the base station with transceiver muting and / or transmit power adaptation of the base station, the terminal may be configured to report multiple CSI entries in a CSI report based on multiple sub-configurations. For example, each sub-configuration may correspond to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset. With respect to CSI reporting, a higher layer parameter included in the configuration information (e.g., CSI-ReportConfig) may include a list of sub-configurations, and each sub-configuration may be identified by an identifier (e.g., csi-ReportSubConfigID). For example, each sub-configuration may correspond to a list of at least one CSI-RS resource, or may correspond to a subset of CSI-RS antenna ports, and / or may correspond to power-related parameters of the CSI-RS resource(s) (e.g., power control offset-related parameters (e.g., powerControlOffset) and / or power offset for a PDSCH associated with the CSI-RS).

[0231] For example, an information element (IE) for an aperiodic trigger state list for CSI may include a trigger list parameter for a CSI reporting sub-configuration. This parameter may include a list of sub-configuration ID(s) of N sub-configuration(s) among L configured sub-configurations within a CSI reporting configuration that are associated with triggering states for aperiodic CSI reporting on an uplink data channel (e.g., a physical uplink shared channel (PUSCH)).

[0232] For example, an IE for a CSI reporting configuration may include parameters for a list of CSI reporting sub-configuration ID(s) to be added / modified or released. Port subset indicators and a list of non-zero power (NZP) CSI-RS resources may not be configured simultaneously in the same CSI reporting configuration.

[0233] For example, an IE for a CSI reporting sub-configuration may include a port-subset indicator parameter, an NZP CSI-RS resource list parameter, and a power offset parameter.

[0234] The port-subset indicator parameter may indicate the number of ports of the NZP CSI-RS resources indicated in the NZP CSI-RS resource list (the value of which is equal to the number of ports of the corresponding NZP CSI-RS resources) and the (sub)set of CSI-RS antenna ports used for CSI calculation of the sub-configuration. Each bit in the bit string of the port-subset indicator corresponds to an antenna port, and if any bit is set to 1, the corresponding port may be enabled for CSI calculation corresponding to the sub-configuration, and if any bit is set to 0, the corresponding port may not be enabled for CSI calculation corresponding to the sub-configuration.

[0235] The NZP CSI-RS resource list parameter may indicate a list of NZP CSI-RS resources for a sub-configuration, which is a (sub)set of NZP CSI-RS resource(s) of a CSI-RS resource set for channel measurements associated with a sub-configuration of a CSI reporting configuration. The values ​​0, 1, 2, ... may mean the first, second, third, ... NZP CSI-RS resource of the CSI-RS resource set.

[0236] When the power offset parameter is set for an NZP CSI-RS resource, it may indicate that a power offset is applied between the PDSCH RE (resource element) and the NZP CSI-RS RE by the difference in the value of the power offset parameter from the value of the power control offset parameter.

[0237] When a configuration for CSI includes multiple sub-configurations, when interpreting the configuration information for CSI, the terminal may determine CSI-RS resources, CSI-RS port mapping, power offset, codebook type, report items, etc. by considering the sub-configurations. When configuration information related to CSI reporting including sub-configurations (e.g., CSI-ReportConfig) is provided to the terminal, the terminal may not expect that a higher layer parameter related to a report item (e.g., reportQuantity) is set to 'cri-RSRP', 'cri-SINR', 'cri-SINR-Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', 'ssb-Index-SINR-Index' or 'tdcp' (wherein CRI corresponds to a CSI-RS resource index, and tdcp corresponds to time domain channel properties). Additionally, when the type of CSI reporting is set to semi-persistent CSI reporting or aperiodic CSI reporting, the base station can activate / trigger only some of the sub-configurations configured for the UE through MAC-CE (control element) or DCI (downlink control information). For example, the trigger state of aperiodic CSI reporting can be configured as needed, and whether semi-static CSI reporting is activated can be controlled by an activation command.

[0238] For example, with respect to the configuration of a report quantity, the terminal may determine the CSI-RS port index(es) for each CSI-RS resource based on information related to a port subset per sub-configuration (hereinafter referred to as a "port subset indicator"). The port subset indicator may include a bitmap for specifying some of the antenna ports for the corresponding CSI-RS resource. Accordingly, the terminal may identify at least one antenna port for the corresponding sub-configuration based on the positions of bits set to positive values ​​(e.g., 1) in the port subset indicator.

[0239] For example, with respect to the configuration of report items (report quantity), the terminal may determine the codebook type based on the presence or absence of sub-configurations. Specifically, if sub-configurations are configured for CSI reporting, the terminal may exclude the configuration of at least one codebook type. For example, if the terminal's capabilities support it, at least one codebook type may be configured.

[0240] For example, in relation to the configuration of the report quantity, a power offset value and an NZP CSI-RS resource set may be configured for each sub-configuration. For example, depending on whether a power offset value is configured for each sub-configuration and whether an NZP CSI-RS resource set is configured, the interpretation of the NZP CSI-RS resource set for each sub-configuration may vary.

[0241] When determining the channel quality indicator (CQI), a higher-layer parameter related to time restrictions for channel measurements (e.g., timeRestrictionForChannelMeasurements) may be configured. In this case, the terminal can derive a channel estimate for determining CSI based on the most recent CSI reference resource. For example, if cell DTX is activated for the base station, the cell DTX activation time, etc., may be considered to determine the CSI reference resource, etc.

[0242] CSI is derived based on CSI reference resources. A CSI reference resource is defined as a group of downlink physical resource blocks corresponding to a band related to the CSI derived in the frequency domain, and is defined as a single downlink slot determined based on higher-layer parameters and subcarrier spacing in the time domain. After receiving a CSI-RS, a UE can transmit a CSI report no later than the CSI reference resource. For example, if sub-configurations are configured for a CSI report, a CSI reference resource may be considered for each sub-configuration.

[0243] When at least one of a CQI index, a precoding matrix index (PMI), and a rank indicator (RI) is set to be reported, in the CSI reference resource, the terminal may assume specific values ​​for the symbol positions and number occupied by control signaling, the number of PDSCH and demodulation reference signal (DMRS) symbols, the subcarrier spacing of the bandwidth part (BWP), the bandwidth for CQI reporting, the length and subcarrier spacing of the cyclic prefix (CP) of the reference resource, and the redundancy version (RV), for the purpose of deriving at least one of the CQI index, PMI, and RI. At this time, when sub-configurations are set for the CSI reporting, assumptions about the antenna port, EPRE (energy per resource element), etc. may be determined based on the sub-configurations.

[0244] Based on the aforementioned configuration, the base station can transmit at least one CSI-RS to the terminal. Based on the aforementioned configuration, the terminal can receive at least one CSI-RS and perform measurement on it. For example, the at least one CSI-RS can be transmitted via a CSI-RS resource or resource set configured by the configuration information.

[0245] When the terminal is set to DRX (discontinuous reception), the terminal can perform measurements as follows. For example, when the terminal is set to monitor power saving related control information (e.g., DCI format 2_6) and the DRX related timer (e.g., drx-onDurationTimer) has not been started by a higher layer parameter (e.g., ps-TransmitOtherPeriodicCSI), and is set to report CSI using a reporting configuration type set to periodic reporting and a reporting item set to an item other than cri-RSRP and ssb-index-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer in the DRX related configuration information (e.g., DRX-Config) other than the DRX active time or the DRX active time for the CSI to be reported. As another example, if the terminal is configured to monitor power saving related control information (e.g., DCI format 2_6) and is configured to report L1-RSRP using a report configuration type set to periodic reporting and a report item set to cri-RSRP in a situation where drx-onDurationTimer has not started by a higher layer parameter (e.g., ps-TransmitPeriodicL1-RSRP), the most recent CSI measurement opportunity occurs during a time indicated by drx-onDurationTimer in DRX-related configuration information (e.g., DRX-Config) other than the DRX active time or the DRX active time for the CSI to be reported. In addition, the most recent CSI measurement opportunity occurs within the DRX active time for the CSI to be reported.

[0246] A base station may perform cell DTX and / or cell DRX operations. In this case, during the inactive period of cell DTX, a terminal configured as cell DTX may not expect to receive periodic CSI-RS and semi-static CSI-RS, at least as configured in a CSI reporting configuration associated with a report item including RI. When cell DTX is activated for a serving cell, the most recent CSI measurement opportunity of a semi-static CSI-RS resource or a periodic CSI-RS resource may occur within the active periods of cell DTX for CSI reporting, at least as configured by configuration information (e.g., CSI-ReportConfig) related to CSI reporting associated with a report item including RI.

[0247] A terminal that receives at least one CSI-RS can determine CSI. For example, the terminal can perform CSI calculations. The terminal can perform CSI calculations based on CSI processing criteria. The terminal can indicate the number of supported concurrent CSI calculations, for example, the number of CSI processing units (CPUs) that can be performed simultaneously, called NCPUs. The terminal can determine the number of CPUs for a given CSI report based on at least one of the NCPUs, the number of CPUs for each CSI report, the number of CPUs currently occupied, and the settings of the report items. For example, for configuration information (e.g., CSI-ReportConfig) related to CSI reporting that includes a report item parameter (e.g., reportQuantity) that is not set to 'none', the CPU(s) may be occupied for at least one orthogonal frequency division multiplexing (OFDM) symbol, wherein the number of at least one symbol may be determined based on CSI-RS resources or CSI-IM (interference measurement) resources associated with the sub-configurations.

[0248] When configuration information related to CSI reporting (e.g., CSI-ReportConfig) includes multiple sub-configurations, the number of CPUs occupied by the CSI report may be determined based on the number of CSI-RS resources corresponding to the sub-configurations. For example, the number of CSI-RS resources may be determined based on the number of times they are referred in the configuration information related to CSI reporting (e.g., CSI-ReportConfig) or the number of sub-configurations referencing the corresponding CSI-RS resources.

[0249] A terminal that has determined CSI can transmit a CSI report to a base station. The terminal can transmit CSI(s) for at least one sub-configuration according to a report item parameter (e.g., reportQuantity) configured for configuration information related to the CSI report (e.g., CSI-ReportConfig). For example, the CSI report can include at least one of PMI, CQI, RI, CRI, SSBRI (SSB resource index), LI (layer indicator), and RSRP. In this case, the CSI report can include a Part 1 CSI report and a Part 2 CSI report. In addition, the CSI report can be transmitted via at least one of a physical uplink control channel (PUCCH) or a PUSCH.

[0250] When a terminal multiplexes a CSI report including a Part 2 CSI report on a PUCCH resource, the terminal determines the number of PUCCH resources and physical resource blocks (PRBs) for the PUCCH resource or the number of Part 2 CSI reports, assuming that each CSI report or each CSI sub-report included in the CSI report indicates rank 1 or the rank combination {1, 1}. When a higher layer parameter related to the CSI reporting mode (e.g., csi-ReportMode) is set to 'Mode2', the terminal determines the PUCCH resource and the number of PRBs for the PUCCH resource or the number of Part 2 CSI reports, assuming that each CRI of the CSI report is associated with a resource pair.

[0251] When a CSI report on PUSCH includes two parts, the UE may omit some of the Part 2 CSI. The omission of Part 2 CSI is in priority order. When omitting Part 2 CSI information for a particular priority level, the UE shall exclude all information for that priority level, except when the corresponding CSI report includes at least one CSI sub-report including Part 2, which corresponds to a sub-configuration from a list of sub-configurations provided by a higher layer parameter (e.g., csi-ReportSubConfigList) included in information related to the CSI report (e.g., CSI-ReportConfig).

[0252] For a report configuration related to information related to a CSI report (e.g., CSI-ReportConfig) that includes a list of sub-configurations, the following processing is possible: For a corresponding CSI report that includes at least one CSI sub-report, omission of Part 2 CSI is performed at the sub-configuration level within the same priority level, where a sub-configuration with a lower index value has a higher priority.

[0253] If a CSI report consists of two parts, a UE may omit some of the Part 2 CSI. The omission of Part 2 CSI is based on a priority order. For a report configuration related to information related to a CSI report (e.g., CSI-ReportConfig) that includes a list of sub-configurations, for a given CSI report that includes at least one CSI sub-report, the omission of Part 2 CSI may be applied according to the CSI reporting procedure using PUSCH. Part 2 CSI may be omitted starting from the lowest priority level up to the Part 2 CSI coding rate that is less than or equal to the coding rate set by the higher layer parameter (e.g., maxCodeRate).

[0254] Additionally, if the CQI request (or CSI request) field in the DCI triggers CSI report(s) on the PUSCH, the first uplink symbol carrying the CSI report(s) may not precede a symbol specified after a certain interval from the last symbol of the PDCCH carrying the corresponding DCI. Accordingly, the CSI calculation time may be guaranteed. For example, if multiple sub-configurations are configured for the CSI report, the starting position of the aforementioned certain interval may be determined based on all triggered sub-configurations.

[0255] CSI is transmitted via PUCCH or PUSCH and can be expressed as a bit string of a fixed size. When CSI is transmitted via PUCCH, if a parameter (e.g., csi-ReportSubConfig) indicating sub-configuration-specific settings for CSI reports is configured, the mapping order of CSI fields for each CSI sub-report can be applied according to predefined rules.

[0256] When CSI is transmitted via PUSCH, if a parameter indicating sub-configuration-specific configuration for CSI reporting (e.g., csi-ReportSubConfig) is set, for each CSI sub-report, the mapping order of CSI fields can be applied according to a predefined rule.

[0257] Some or all of the examples of FIGS. 1 to 18 described above may be combined with some or all of the examples of the present disclosure described below, and such combined examples are included within the scope of the present disclosure.

[0258] On-demand SSB transmission and reception procedures

[0259] In basic communication systems, base stations were defined to periodically transmit SSB for purposes such as time / frequency synchronization and / or radio resource management (RRM). In other words, base stations were defined to transmit SSB even when there was no data to transmit or receive, resulting in unnecessary energy consumption.

[0260] Accordingly, the base station can reduce energy consumption by transmitting SSB to the terminal on a specific cell according to the on-demand SSB procedure and not transmitting SSB to the terminal in a specific cell when the on-demand SSB procedure is not applied. In other words, the base station can reduce energy consumption by performing SSB transmission only when the on-demand SSB procedure is applied / accompanied.

[0261] The on-demand SSB process can be triggered based on at least one of the following actions:

[0262] 1) An operation in which a terminal transmits a request for SSB transmission to a base station through an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS, etc.).

[0263] 2) An action whereby base station #1 (or TRP #1) requests SSB transmission to base station #2 (or TRP #2) through an interface between base stations (e.g., Xn interface, etc.) or backhaul signaling, etc.

[0264] 3) An action in which the base station signals whether to transmit SSB for the corresponding SCell by transmitting SCell activation / deactivation signaling to the terminal.

[0265] The on-demand SSB operation (on PCell and / or SCell) and related information described below can be applied not only to terminals in connected mode, but also to terminals in inactive (or idle) mode or terminals performing initial connection. In other words, the on-demand SSB operation (on PCell and / or SCell) can be applied not only to terminals in basic wireless communication systems but also to terminals in next-generation communication systems.

[0266] Additionally, the on-demand SSB operation applied to carrier aggregation (CA) that includes the SCell can also be applied to intra-band CA or inter-band CAD. The SSB transmitted on the SCell via the on-demand SSB process can be used at least for time / frequency synchronization, L1 / L3 measurements, and SCell activation procedures.

[0267] On-demand system information (e.g., SIB1) transmission procedure

[0268] In basic wireless communication systems, for initial connection or idle mode terminals to access a cell, the terminal is required to periodically transmit system information (e.g., SIB1) containing system information, random access information, etc. to the terminal. In other words, the base station is required to transmit system information even when there is no data to transmit or receive, which leads to the problem of unnecessary energy consumption.

[0269] Accordingly, the base station can reduce energy consumption of the base station by transmitting SIB1 for a specific cell to the terminal through the on-demand SIB1 process and not transmitting SIB1 for a specific cell to the terminal when the on-demand SIB1 process is not applied.

[0270] As an example of the present disclosure, a terminal may trigger SIB1 transmission of a base station by transmitting an uplink signal / channel (e.g., PRACH, etc.) to the base station, and at least one of the scenarios described below may be applied.

[0271] Scenario 1: As illustrated in (a) of FIG. 19, the UE may recognize that SIB1 is not transmitted in cell #1 by receiving an SSB (and / or other downlink signal channel) from the base station in cell #1. The UE may trigger SIB1 transmission by transmitting a signal requesting SIB1 to the base station based on information provided via the SSB (and / or other downlink signal / channel) and / or predetermined information. In describing the present disclosure, the signal requesting SIB1 may be collectively referred to as a WUS (wake-up signal), but is not limited thereto. The base station receiving the WUS may transmit a specific DL signal / channel (e.g., an ACK signal) to the UE on cell #1 in response to the WUS. Additionally or alternatively, the base station may transmit SIB1 to the UE on cell #1 (without a specific DL signal / channel) in response to the WUS.

[0272] Scenario #2: As illustrated in (b) of FIG. 19, the UE may recognize that SIB1 is not transmitted in cell #2 by receiving an SSB (and / or other downlink signaling channel such as SIB1) from the base station in cell #1. The UE may attempt to camp on cell #2. The UE may trigger SIB1 transmission for cell #2 by transmitting a signal (e.g., WUS) requesting SIB1 to the base station on cell #1 based on information provided through the received SSB (and / or other downlink signaling / channel such as SIB1) and / or predetermined information. The base station receiving the WUS may transmit a specific DL signal / channel to the UE (on cell #1 or cell #2) in response to the WUS. Additionally or alternatively, the base station may transmit SIB1 for cell #2 to the UE on cell #1 or cell #2 (without the specific DL signal / channel) in response to the WUS.

[0273] Scenario #3: As illustrated in (c) of FIG. 19, the UE may recognize that SIB1 is not transmitted in cell #2 by receiving an SSB (and / or other downlink signaling channel such as SIB1) from the base station in cell #1. The UE may attempt to camp on cell #2. The UE may trigger SIB1 transmission for cell #2 by transmitting a signal (e.g., WUS) requesting SIB1 to the base station on cell #2 based on information provided through the received SSB (and / or other downlink signaling / channel such as SIB1) and / or predetermined information. The base station receiving the WUS may transmit a specific DL signal / channel to the UE (on cell #1 or cell #2) in response to the WUS. Additionally or alternatively, the base station may transmit SIB1 for cell #2 to the UE on cell #1 or cell #2 (without the specific DL signal / channel) in response to the WUS.

[0274] Adaptation of common signal / channel transmission

[0275] When a common signal / channel is transmitted using the on-demand SSB transmission method, the energy consumption of the base station can be significantly reduced. For example, the base station can transmit SSB on specific cells where the on-demand SSB process is applied, and not transmit SSB on cells where the on-demand SSB process is not applied. In other words, the base station can initially not perform SSB transmission and only perform SSB transmission when the on-demand SSB process is involved.

[0276] However, if SSB, which performs functions such as time / frequency synchronization or RRM measurement, is not transmitted, stable operation of the cell may not be guaranteed from the perspective of the terminal. Considering this, the base station can adjust the transmission of common signals / channels such as SSB, PRACH, and paging. For example, the energy consumption of the base station can be reduced by changing the transmission pattern of SSB (e.g., transmission period, period per SSB candidate index(es), SSB candidate index(es) transmitted within one transmission period, transmission power, etc.) according to the situation.

[0277] For example, in the case of contention-based random access, since the base station does not know the PRACH transmission timing of the terminal, it may attempt to use the PRACH resources from the configured PRACH resources every time, which may increase energy consumption. Considering this, a method for adjusting the amount of PRACH resources can be applied, thereby controlling the energy of the base station. For example, the period of the PRACH resources can be adjusted, the set to be activated among the preset PRACH resource sets #1 and #2 can be indicated, or the amount of RACH resources corresponding to each SSB index can be provided uniformly or non-uniformly.

[0278] PRACH transmission method and parameters

[0279] Before initiating a physical random access procedure, Layer 1 (e.g., Physical Layer) may receive a set of SS / PBCH block indices from upper layers and provide only the corresponding set of RSRP measurements to upper layers.

[0280] Before the physical random access procedure begins, Layer 1 may receive the following information from the upper layer:

[0281] - Setting PRACH transmission parameters (e.g., PRACH preamble format, time resources, frequency resources for PRACH transmission).

[0282] - Parameters for determining the root sequence and cyclic shift in the PRACH preamble sequence set (index to the logical root sequence table, cyclic shift (N CS ), set type (no restrictions, restricted set A or restricted set B).

[0283] From a physical layer perspective, a Type-1 L1 random access procedure may include transmitting a random access preamble (Msg1) on the PRACH, a random access response (RAR) message containing PDCCH / PDSCH (Msg2), a PUSCH transmission reserved by a RAR UL grant if applicable, and a PDSCH transmission for contention resolution. From a physical layer perspective, a Type-2 L1 random access procedure may include transmitting a random access preamble on the PRACH, transmitting a PUSCH (MsgA), receiving a RAR message containing PDCCH / PDSCH (MsgB), and transmitting a PUSCH reserved by a fallback RAR UL grant if applicable, and a PDSCH transmission for contention resolution. If a UE is configured with two UL carriers for its serving cell and detects a PDCCH order, the UE can use the UL / SUL indicator field value of the detected PDCCH order to determine the UL carrier for the corresponding PRACH transmission.

[0284] When a random access procedure for a UE is initiated by a PDCCH command, the PRACH transmission may use the same SCS as the PRACH transmission initiated from a higher layer.

[0285] The physical random access procedure for a terminal may be triggered by a PRACH transmission request from a higher layer or a PDCCH command for a cell. The configuration information for PRACH transmission by the higher layer may include at least one of a configuration for PRACH transmission on a cell, a preamble index, a preamble SCS, power for PRACH transmission, information related to an RA-RNTI corresponding to the PRACH transmission, PRACH resources for the cell, and the number of preamble repetitions for the PRACH transmission.

[0286] The terminal may transmit the PRACH in the cell using the selected PRACH format through the resource set determined using the same spatial filter in case of the indicated PRACH resource or preamble repeat transmission, and the transmission power is P PRACH,b,f,c (i) may be.

[0287] For a Type 1 random access procedure, a UE may be provided with N SS / PBCH block (e.g., SSB) indices associated with a PRACH occasion and R contention-based preambles per SS / PBCH block index for each valid PRACH occasion. For a Type 2 random access procedure with a common set of PRACH opportunities, a UE may be provided with N SS / PBCH block indices associated with a PRACH occasion and Q contention-based preambles per SS / PBCH block index for each valid PRACH occasion. A PRACH transmission may be performed in a subset of PRACH opportunities associated with the same SS / PBCH block index within an SSB-RO mapping period for a UE provided with a PRACH mask index.

[0288] System Information Block (SIB)1 or SS / PBCH block index can be mapped to valid PRACH cases in the following order:

[0289] i) First, the increasing order of the preamble index within a single PRACH opportunity.

[0290] ii Second, ascending order of frequency resource index for frequency multiplexed PRACH opportunities.

[0291] iii) Third, ascending order of time resource index for time-multiplexed PRACH opportunities within a PRACH slot.

[0292] iv) Fourth, ascending order of index for PRACH slots

[0293] The association period starting from frame 0 for mapping SS / PBCH block indices to PRACH opportunities is the smallest integer in the set determined by the PRACH setup period according to Table 1. An SS / PBCH block index can be mapped to a PRACH opportunity at least once within the association period. After an integer number of SS / PBCH block indices for PRACH opportunity mapping cycles within the association period. If there is a PRACH opportunity or a PRACH preamble set that is not mapped to an SS / PBCH block index, the SS / PBCH block index may not be mapped to a PRACH opportunity or a PRACH preamble set.

[0294] PRACH setup period (msec) Association period (number of PRACH setup periods) 10 {1, 2, 4, 8, 16} 20 {1, 2, 4, 8} 40 {1, 2, 4} 80 {1, 2} 160 {1}

[0295] The association pattern period may include one or more association periods, and the pattern between the PRACH opportunity and the SS / PBCH block index may be determined to repeat at most every 160 msec. After an integer number of association periods, PRACH epochs that are not associated with the SS / PBCH block index may not be used for PRACH transmission. PRACH opportunities may be consecutively mapped per corresponding SS / PBCH block index. The indexing of the PRACH opportunity indicated by the mask index value may be reset at every mapping period of consecutive PRACH opportunities per SS / PBCH block index. The UE may select the PRACH opportunity indicated by the PRACH mask index value for the indicated SS / PBCH block index in the first available mapping period for PRACH transmission.

[0296] For the indicated preamble index, the order of PRACH opportunities is:

[0297] - First, the ascending order of the index of frequency resources for frequency multiplexed PRACH opportunities.

[0298] - Second, ascending order of time resource index for time-multiplexed PRACH opportunities within a PRACH slot.

[0299] - Third, the index for the PRACH slot can be in ascending order.

[0300] For a PRACH transmission using a specific number of preamble repetitions, the set associated with the preamble repetition transmissions consists of a specific number of valid PRACH opportunities that are temporally consecutive, use the same frequency resources, and are associated with the same one or more SS / PBCH block indices, and each SS / PBCH block index can be associated with the same preamble index in all valid PRACH opportunities within the set.

[0301] Random access procedure

[0302] As an example of the present disclosure, the random access procedure may include a 4-step RACH procedure and an S-step RACH procedure. The 4-step RACH procedure may include steps in which four messages are transmitted and received, and the 2-step RACH procedure may include steps in which two messages are transmitted and received.

[0303] As an example of the present disclosure, in the case of a 4-step RACH procedure, a terminal may transmit message 1 including a preamble to a base station. The terminal may transmit message 1 to the base station to perform an access procedure with the base station based on the time and frequency resources of the RACH and the preamble ID. The base station may transmit message 2 to the terminal in response to message 1. Message 2 includes a response to the preamble included in message 1, and is a downlink channel that is transmitted to the terminal first in the RACH procedure from the base station's perspective. Here, a PDCCH scrambled by RA-RNTI may be transmitted to the terminal, and transmission of a PDSCH including message 2 may be scheduled by the PDCCH. The terminal may transmit message 3 including an access reason, etc. to the base station through RRC signaling. The base station may transmit a response to the terminal via message 4 regarding whether an access request based on message 1 / 3 is appropriate. Afterwards, unicast terminals and base stations can transmit and receive necessary information according to the C-RNTI instructions.

[0304] As an example of the present disclosure, in the case of a 2-step RACH procedure, a terminal may transmit message A to a base station. Message A may include information included in messages 1 and 3 of a 4-step RACH procedure. Message B may have a different configuration depending on the type of content RAR (e.g., fallback RAR or success RAR). As an example, message B may be a PDSCH including information included in messages 2 and 4 of the 4-step RAR procedure, but is not limited thereto. In the case of contention-based random access (CBRA), an RNTI associated with message B may be a message B-RNTI similar to an RA-RNTI. In the case of contention-free random access (CFRA), an RNTI associated with message B may be a C-RNTI.

[0305] On-demand SI operation in basic wireless communication systems

[0306] On-demand SI operation in a basic wireless communication system may include requesting SI via the PRACH preamble ID of Msg. 1 and the PUSCH of Msg. 3 (or Msg. A).

[0307] For example, in a basic wireless communication system, a base station may always transmit SSB and / or SIB1 (e.g., RMSI) to a terminal. When a terminal transmits a signal requesting on-demand system information related to at least one of SIB2 to SIBx (where x is a natural number greater than or equal to 2) to the base station through a PRACH procedure, the base station may transmit at least one of SIB2 to SIBx to the terminal according to the signal. The number of cycles in which the base station transmits the corresponding SIB may be an implementation feature of the base station. For example, the base station may transmit the corresponding SIB to the terminal for one or more cycles or permanently.

[0308] When SI request-based MSG1 transmission is applied within the 4-step RACH illustrated in (a) of FIG. 20, the base station may transmit preamble allocation information for the SI request to the terminal (S305-1). The terminal may transmit an RA preamble for the SI request to the base station (via Msg. 1) (S310-1).

[0309] Specifically, each SI (e.g., SIB group) transmission can be linked based on the RACH opportunity of Msg. 1 and the configuration of the preamble. Accordingly, SI transmission can be determined by frequency / time resources and preamble configuration. That is, information about the SI requested by the terminal can be determined based on the frequency location and / or time resource location where the preamble ID and SI request are transmitted. Accordingly, the base station can transmit an RAR including a RAPID to the terminal based on the PDCCH addressed to the RA-RNTI (S315-1). Then, the base station can transmit the SI requested by the terminal to the terminal (S320-1).

[0310] When SI request-based MSG3 transmission is applied within the 4-step RACH illustrated in (a) of FIG. 20, the terminal may transmit a random access preamble to the base station via Msg. 1 (S305-2). The base station may transmit an RAR including RAPID to the terminal based on a PDCCH addressed to the RA-RNTI (S310-2). The terminal may transmit Msg. 3 PUSCH including SI request information to the base station (S315-2). For example, the SI request information may include the type of system information to be requested, etc. The base station may transmit Msg. 4 to the terminal (S320-2) and transmit system information according to the SI request information to the terminal (S325-2).

[0311] The base station may transmit configuration information (e.g., "SI-SchedulingInfo") related to SI scheduling information, which includes information necessary for obtaining an SI message, to the terminal via upper layer signaling (e.g., SIB1, RRC message, etc.). The configuration information related to SI scheduling information may be included in the information that the base station broadcasts to the terminal(s) via SIB1.

[0312] For example, the configuration information related to SI scheduling information may include: setting up a dedicated RACH opportunity for SI (e.g., "rach-OccasionsSI"), information related to the periodicity of SI request setup in number of association periods (e.g., "si-RequestPeriod"), information about resources related to SI requests, an association period index of an SI request period in which the UE can send an SI request for SI message(s) corresponding to the information related to the SI-request (e.g., "ra-AssociationPeriodIndex"), information about a preamble (start) index (e.g., "ra-PreambleStartIndex"), etc.

[0313] As illustrated in FIG. 21, a method of allocating each RO (e.g., frequency and time resource configuration) and preamble according to the transmission of SSB based on the configuration information for the MSG 1-based SI request can be applied. That is, FIG. 21 exemplifies a method of allocating RO according to SSB ID (e.g., beam direction). Here, "msg1-FDM" means information on the number of FDM PRACH period opportunities within one time instance, and "ssb-perRACH-Occasion" means the number of SSBs per RACH opportunity.

[0314] For example, if the "msg1-FDM" value and "ssb-perRACH-Occasion" are each set to 1 as in (a) of FIG. 21, the number of FDM PRACH period opportunities within one time instance may be 1 and the number of SSBs per each RACH opportunity may be 1. If the "msg1-FDM" value and "ssb-perRACH-Occasion" are each set to 2 and 1 as in (b) of FIG. 21, the number of FDM PRACH period opportunities within one time instance may be 2 and the number of SSBs per each RACH opportunity may be 1. If the "msg1-FDM" value and "ssb-perRACH-Occasion" are each set to 2 and 1 / 2 as in (c) of FIG. 21, the number of FDM PRACH period opportunities within one time instance may be 2 and the number of SSBs per each 2 RACH opportunities may be 1. As shown in (d) of Fig. 21, when the "msg1-FDM" value and "ssb-perRACH-Occasion" are set to 2 and 4, respectively, the number of FDM PRACH period opportunities within one time instance can be 2 and the number of SSBs per RACH opportunity can be 4.

[0315] As an example of the present disclosure, as illustrated in (a) and (b) of FIG. 22, the location of each SI can be determined based on the location of the period in which the configuration information related to the SI scheduling information is transmitted by setting a dedicated RACH opportunity for the SI (e.g., “rach-OccasionsSI”).

[0316] For example, if the information related to the periodicity of the SI request setting (e.g., "si-RequestPeriod") is 640 ms, the period set related to the SI can be composed of four periods of 160 ms, and the transmission of the corresponding SI can be determined based on which time zone the preamble request is. Depending on the pre-allocated frequency location and preamble ID transmitted in the corresponding period for each index, it can be determined which SI will be transmitted.

[0317] For example, if there is a preamble received within the cycle by setting information related to the cycle, SI set according to SIB1 can be transmitted to the RO / preamble ID.

[0318] In case of Msg. 1 based SI request, since it is highly likely that one PRACH resource (RO and preamble ID(s)) will be allocated to one SI, simultaneous requests for SI(s) may be limited. Therefore, for simultaneous allocation of multiple SI(s), a method of simultaneously triggering SI information in parallel in the form of MAC CE or / and RRC signaling using bitmap information, etc. may be applied. When the Msg. 1 based SI request is applied, triggering SI in parallel may be more efficient than triggering SI one by one.

[0319] As an example of the present disclosure, a terminal may transmit a message (e.g., "RRCSystemInfoRequest") to a base station for requesting an SI message. That is, the message may include an RRC message related to a PUSCH that the terminal transmits to the base station for the first time in a RACH procedure. The message for requesting the SI message may include a requested SI message list (e.g., "requested-SI-List") set by a scheduling information list (e.g., "SchedulingInfoList") in scheduling information related to SI included in SIB1 (e.g., "si-SchedulingInfo"), etc.

[0320] A bitmap may be formed by mapping SI to each bit included in the above-mentioned requested SI message list (e.g., "requested-SI-List"), and the bitmap may be signaled by the terminal to the base station. For example, when a Msg. 1-based SI request is applied, the base station may perform a procedure to check whether a RAPID corresponding to the transmission preamble ID exists by transmitting Msg. 2 to the terminal. After this, the transmission and reception procedures of Msg. 3 and Msg. 4 may not be necessary.

[0321] However, when performing an SI request through RRC signaling on PUSCH, procedures up to Msg. 4 (e.g., 4-step RACH) may be required. These two PRACH procedures for SI requests can also be applied to the on-demand SIB1 transmission procedure. For example, when a UE in RRC_IDLE state wants to receive SIB1 for a neighboring cell, the on-demand SIB1 procedure can be applied in a similar manner to the on-demand SSB procedure in a CA situation.

[0322] On-demand SIB and / or SSB transmission procedures in next-generation wireless communication systems

[0323] The present disclosure relates to a method for requesting SSB of an SCell in a bitmap form via a PRACH preamble ID and Msg. 3 PUSCH or / and Msg. A PUSCH.

[0324] Specifically, in the case of SCell in a CA situation, it may be efficient from a NES perspective for the base station to transmit on-demand SSB to the UE only when the UE requests on-demand SSB. Accordingly, an SCell index or multiple SCell indices may be mapped one by one to the RO (or preamble) for preamble transmission of Msg. 1, and a SSB transmission request on the corresponding SCell may be performed through bitmap information included in Msg. 3 PUSCH or Msg. A PUSCH. As an example of the present disclosure, the index ID of the SCell may be mapped bit by bit on the bitmap. If the index ID of a specific SCell is mapped to a specific bit of the bitmap, this may mean that SSB transmission is requested on the specific SCell.

[0325] Additionally, a UE in RRC IDLE (or INACTIVE) state can receive a list of neighboring cells from the base station in a serving cell. The UE may need to confirm the SIB1 (reception) of the neighboring cell(s). Similarly to the on-demand SSB procedure on the SCell, the on-demand SIB procedure may also include a method in which neighboring cell indices are mapped to RACH-related information.

[0326] In describing the present disclosure, a cell / carrier / BWP that provides information about another cell / carrier / BWP where SSB and / or SIB1 is transmitted is referred to as Cell A (SIB-transmitting). Here, the information about the other cell / carrier / BWP may include information about whether SSB and / or SIB1 is currently being transmitted periodically, transmission time pattern information of SSB and / or SIB1 on the cell / carrier / BWP if SSB and / or SIB1 is being transmitted, configuration information about uplink resources such as PRACH for on-demand SSB / SIB1 procedure if SSB and / or SIB1 is not being transmitted, etc.

[0327] And, a cell / carrier / BWP where SSB and / or SIB1 is not transmitted or where SSB and / or SIB1 can be transmitted after performing an on-demand SSB / SIB1 procedure is expressed as a NES cell (or SIB1-less or NES neighbor cell).

[0328] FIG. 23 is a flowchart illustrating a method for a terminal to perform a communication procedure according to one embodiment of the present disclosure.

[0329] The terminal can receive first configuration information related to a system information block request from the base station (via the serving cell) (S2310).

[0330] As an example of the present disclosure, the terminal may receive first configuration information from the base station through a second system information block, which is a system information block x for obtaining (or requesting) a system information block (e.g., SIB1). That is, the second system information block may include the first configuration information. However, this is merely an embodiment, and the terminal may receive the first configuration information from the base station through separate upper layer signaling (e.g., RRC signaling, MAC CE, etc.).

[0331] Additionally or alternatively, the second system information block may include third configuration information for at least one opportunity for uplink channel transmission. Based on the first uplink channel being a physical random access channel (PRACH), the third configuration information may include information related to at least one RO (or PRACH opportunity), such as the number of at least one RO, time and frequency resources of each of the at least one RO, a period of the at least one RO, and / or SSB to RO mapping parameters.

[0332] That is, the third configuration information may include at least one of the number of opportunities, the time and frequency resources of each of the at least one opportunity, or the period of the at least one opportunity.

[0333] Here, a neighboring cell group may include at least one neighboring cell (e.g., a secondary cell) relative to a serving cell. For example, a neighboring cell group may include a single neighboring cell, and in this case, the neighboring cell group may correspond to the single neighboring cell.

[0334] For example, the first configuration information may include parameters associated with each of a plurality of neighboring cell groups. Specifically, the parameters associated with each of the plurality of neighboring cell groups may include at least one of a random access preamble (start) index (e.g., "ra-PreambleStartIndex"), an association period index (e.g., "ra-AssociationPeriodIndex"), or a physical random access channel (PRACH) mask index (e.g., "ra-ssb-OccasionMaskIndex") mapped to each of the plurality of neighboring cell groups. The PRACH mask may be valid for all SSB resources.

[0335] For example, the first parameter may include at least one of a random access preamble index, an index of an association period, or a PRACH mask index associated with the first neighboring cell group.

[0336] For example, the terminal may receive the first configuration information from the base station via a serving cell, and the serving cell may be, but is not limited to, a primary cell or a secondary cell.

[0337] Additionally or alternatively, the terminal may receive second configuration information for a plurality of neighboring cell groups from the base station. The second configuration information may include information about at least one secondary cell included in each of the plurality of neighboring cell groups. For example, the second configuration information may include at least one of a list of at least one secondary cell included in each of the plurality of neighboring cell groups, information related to the activation status of each of the at least one secondary cell, or information related to whether a system information block is transmitted for the at least one secondary cell. In this case, the second configuration information may be included in the second system information block, but is not limited thereto, and may also be transmitted and received through separate upper layer signaling.

[0338] That is, multiple neighboring cell groups can be set for the terminal through the second setting information, but this is not limited thereto, and the configuration of multiple neighboring cell groups can be defined in advance.

[0339] The terminal can transmit a first uplink channel including a first parameter related to a first neighboring cell group among multiple neighboring cell groups to the base station (S2320).

[0340] For example, assume that a terminal requests a system information block for a first neighboring cell group. The terminal may transmit a first uplink channel containing parameters related to the first neighboring cell group to the base station (via the serving cell). The first uplink channel may include, but is not limited to, a PRACH with Msg. 1.

[0341] As an example of the present disclosure, a terminal may receive from a base station a parameter set related to resources for uplink channel transmission for each of a plurality of neighboring cell groups. The terminal may transmit a first uplink channel to the base station based on parameters for uplink channel transmission for a first neighboring cell group among the parameter set. At this time, the terminal may be in an RRC_idle or RRC_inactive state.

[0342] As another example, based on the terminal being in an RRC (radio resource control) connected state, parameters for uplink channel transmission to the first neighboring cell group may include parameters related to dedicated random access channel resources. That is, when the terminal is in an RRC connected state, the terminal may transmit the first uplink channel to the base station based on dedicated random access channel resources.

[0343] For example, parameters for a first uplink channel transmission for a first neighboring cell group may include at least one of a parameter related to a time resource of the first uplink channel, a parameter related to a frequency resource, and a spatial parameter.

[0344] The terminal can receive a first system information block for the first neighboring cell group from the base station (S2330).

[0345] That is, the terminal can request transmission of a first system information block (e.g., SIB1) for the first neighboring cell group by transmitting a first parameter related to the first neighboring cell group to the base station via the first uplink channel. Accordingly, the terminal can receive the first system information block from the base station. For example, the terminal can receive the first system information block from the base station via the first neighboring cell group (or at least one SCell included in the first neighboring cell group).

[0346] The method described in the example of FIG. 23 may be performed by the device (200) of FIG. 3. For example, one or more processors (202) of the device (200) of FIG. 3 may receive first configuration information related to obtaining a system information block through one or more transceivers (206). The one or more transceivers (202) may receive, from a base station through one or more transceivers (206), a first uplink channel including a first parameter related to a first neighboring cell group among a plurality of neighboring cell groups. The one or more processors (202) may receive, from the base station through one or more transceivers (206), a first system information block for the first neighboring cell group.

[0347] Furthermore, one or more memories (204) of the device (200) may store instructions for performing the method described in the example of FIG. 23 or the examples described below when executed by one or more processors (202).

[0348] FIG. 24 is a flowchart illustrating a method for a base station to perform a communication procedure according to one embodiment of the present disclosure.

[0349] The base station can transmit first configuration information related to a system information block request to the terminal (S2410).

[0350] For example, the base station may transmit a second system information block containing first configuration information to the terminal via the serving cell. Additionally or alternatively, the base station may transmit third configuration information to the terminal for at least one opportunity for uplink channel transmission. The configuration of the first configuration information has been described with reference to FIG. 23, so a redundant description will be omitted.

[0351] The base station can receive a first uplink channel including a first parameter related to a first neighboring cell group among a plurality of neighboring cell groups from the terminal (S2420).

[0352] The base station can identify that the terminal requests transmission of a system information block to a first neighboring cell group among a plurality of neighboring cell groups based on the first parameter.

[0353] Accordingly, the base station can transmit the first system information block for the first neighboring cell group to the terminal (S2430).

[0354] The method described in the example of FIG. 24 may be performed by a specific device. For example, one or more processors of the specific device may transmit first configuration information related to acquisition of a system information block to the terminal via one or more transceivers. The one or more processors may receive, from the terminal via one or more transceivers, a first uplink channel including a first parameter related to a first neighboring cell group among a plurality of neighboring cell groups. The one or more processors may transmit, to the terminal via one or more transceivers, a first system information block for the first neighboring cell group.

[0355] Furthermore, one or more memories of a particular device may store instructions for performing the method described in the example of FIG. 24 or the examples described below when executed by one or more processors.

[0356] Below, the on-demand SIB and / or SSB transmission procedure in the next generation wireless communication system is described in detail.

[0357] Example 1

[0358] Example 1 relates to a method of mapping an index corresponding to an SCell to a Msg. 1 resource for on-demand SSB in a CA situation.

[0359] Specifically, Embodiment 1 relates to a method for mapping SCell indices to PRACH resources, and the PRACH resources can be divided and operated into RACH opportunities and preambles based on frequency and time. That is, a specific time / frequency and preamble can be mapped to an SCell index desired by a terminal. In addition, when an allocated preamble of a specific frequency range is transmitted (by the terminal) during a corresponding period, it can be recognized (by the base station) as a request for an SSB of the corresponding SCell index.

[0360] For example, a UE may receive from a base station a configuration for Msg. 1 based on an SSB request for an SCell. Within the entire period in which information for an SSB request (e.g., an associated period index related to a RACH procedure, etc.) for multiple SCells can be transmitted, on-demand SSB for a specific SCell may be indicated based on the index or / and time pattern information.

[0361] As an example of the present disclosure, at least one of the {"ra-PreambleStartIndex", "ra-AssociationPeriodIndex", and "ra-ssb-OccasionMaskIndex"} parameters may be mapped differently for each SCell. Here, "ra-ssb-OccasionMaskIndex" refers to a parameter related to a PRACH mask index explicitly signaled for RA resource selection.

[0362] That is, a combination based on at least one of {"ra-PreambleStartIndex", "ra-AssociationPeriodIndex", and "ra-ssb-OccasionMaskIndex"} can be set / defined, and the SCell index requesting on-demand SSB can be different depending on whether a PRACH corresponding to a certain combination is transmitted.

[0363] For example, within a specific RO, "ra-PreambleStartIndex=0" may be set by the base station to correspond to SCell index #1, and "ra-PreambleStartIndex=1" may be set by the base station to correspond to SCell index #2. The UE may transmit a PRACH corresponding to preamble index 1 in the RO to the base station to request on-demand SSB for SCell index #2.

[0364] Example 2

[0365] Example 2 relates to a method of mapping SCells to bitmaps of Msg. 3 for on-demand SSB in a CA situation.

[0366] When SCell index mapping is performed via Msg. 1 in the 4-step RACH procedure, PRACH resources must be allocated in proportion to the number of SCells, making it difficult to simultaneously request multiple SCells on-demand. A new information element (IE) can be defined within the RRC associated with Msg. 3. This IE can contain specific parameters. These specific parameters can be configured in bitmap form, and these parameters can be mapped to SCell indices, etc. in bitmap form.

[0367] The method according to Embodiment 2 can be applied when simultaneous transmission is performed in parallel, unlike Embodiment 1. In this case, at least one of Embodiment 2-1, Embodiment 2-2, Embodiment 2-3, and Embodiment 2-4 can be applied and considered.

[0368] Example 2-1

[0369] As an example of the present disclosure, up to n SCells (e.g., 31) excluding PCells can be configured / defined, and signaling (e.g., RRC signaling, etc.) including the above-described bitmap having a size of n bits can be configured / defined.

[0370] That is, a new n-bit bitmap (e.g., a bitmap related to an SSB request) can be defined, such as parameters related to a list of requested SI messages (e.g., "requested-SI-List"). Each bit of the bitmap can be mapped / corresponded to an index of a configured / defined / added SCell. The terminal can transmit a message including the bitmap to the base station.

[0371] For example, if a specific SCell index is mapped to a specific bit of an n-bit bitmap transmitted by the terminal to the base station, this may mean that on-demand SSB transmission of a specific SCell is requested by the terminal.

[0372] Example 2-2

[0373] As an example of the present disclosure, a bitmap for on-demand SSB transmission / request can be transmitted / received via MAC CE or the like instead of RRC signaling. Each bit of the bitmap can correspond to a transmission / request for SSB of an index of one SCell. In this case, as in Example 2-1, the size of the bitmap can be n bits (e.g., n is 31, etc.), and n can be the number of SCells that can be configured / defined.

[0374] Embodiment 2-1 relates to a method for transmitting and receiving the bitmap (e.g., a bitmap for indicating on-demand SSB request / transmission per SCell) as an L2 RRC message, and Embodiment 2-2 relates to a method for transmitting and receiving the bitmap via a PUSCH including an L2 MAC CE. Since SSB transmission does not need to be transmitted up to L3, unlike SI transmission, a method for transmitting and receiving the bitmap via a PUSCH including an L2 MAC CE can be applied.

[0375] As described above, it is assumed that one SCell index ID (e.g., the index ID of the SCell to which on-demand SSB transmission / request is indicated) is connected / mapped for each single bit of the bitmap. In this case, since up to n SCells (e.g., non-SSB SCells) can be set / added, in order to reduce the number of bits of the bitmap, the SCell(s) (e.g., non-SSB SCells) can be classified into one or more groups, and the groups can be mapped / connected for each single bit of the bitmap.

[0376] For example, let's assume that 16 SSB-less SCells are configured / defined. The 16 SSB-less SCells can be classified into groups of two, and two groups of SSB-less SCells can be mapped per bit of the bitmap. If the index of the SSB-less SCell is mapped per bit, the size of the bitmap is 16 bits. However, if the index of the group of SSB-less SCells is mapped per bit, the size of the bitmap can be 8 bits.

[0377] Here, the SCell index mapping order within the bitmap can be distinguished by the order in which the lowest SCell index is mapped from the MSB of the bitmap (e.g., descending order) or the order in which the lowest SCell index is mapped from the LSB of the bitmap (e.g., ascending order).

[0378] Example 2-3

[0379] As an example of the present disclosure, one or more SCell(s) configured by a base station may be grouped, and one SCell group may be mapped to each bit of the bitmap. For example, when an index of a specific SCell group is mapped to a specific bit of the bitmap, on-demand SSB transmission / request of the SCell(s) included in the specific SCell group may be indicated.

[0380] There is no need for the same number of SCells to be grouped in a SCell group, and the base station can transmit information about the SCell group (e.g., pre-configuration information, etc.) (e.g., the number of SCells per group, etc.) to the terminal.

[0381] Example 2-4

[0382] As an example of the present disclosure, when the number of groups of SCell(s) is 1 or more (e.g., when SCell groups #1 and #2 exist), PRACH resources corresponding to each SCell group may be created and configured. The UE may indicate a specific SCell group through Msg. 1, and indicate a specific SCell within the specific SCell group through Msg. 3 PUSCH.

[0383] For example, assume that SCell group #1 includes {cell (e.g., SCell) #1, cell #2, cell #3}, and SCell group #2 includes {cell #4, cell #5, cell #6}. When a UE requests cell #2 (e.g., requests on-demand SSB transmission in cell #2), the UE may transmit a PRACH mapped to SCell group #1 to the base station. At this time, as described in Embodiment 1, reconfiguration of an index related to RO / preamble for the SCell group may be performed for Msg. 1 (e.g., a message corresponding to PRACH) transmitted by the UE. That is, the UE may receive (re)configuration information related to an index related to RO / preamble for the SCell group from the base station.

[0384] In addition, the terminal can transmit the bitmap (e.g., a bitmap for indicating on-demand SSB request / transmission for each SCell) to the base station via Msg. 3 PUSCH. At this time, the bitmap can be set to "010" (e.g., a value corresponding to cell #2 of SCell group #1).

[0385] Example 3

[0386] Embodiment 3 relates to a method for mapping an SCell to a bitmap of a PUSCH of Msg. A for on-demand SSB in a CA situation. Embodiments 1 and 2 relate to a method performed based on a 4-step RACH, and Embodiment 3 relates to a method for requesting SSB transmission of an SCell in a CA situation in connection with a 2-step RACH procedure.

[0387] Unlike the 4-step RACH procedure, the 2-step RACH procedure does not have an SSB request by the preamble of Msg. A, and only a request for parallel SCell SSB transmission by the PUSCH of Msg. A can exist. As described in Embodiment 2, the SCell index can be mapped on the bitmap transmitted via the Msg. A PUSCH. That is, the SSB transmission on the SCell index corresponding to each bit of the bitmap can be triggered / instructed. In this case, Embodiment 3-1 and / or Embodiment 3-2 can be applied and considered.

[0388] Example 3-1

[0389] As an example of the present disclosure, the terminal may transmit the bitmap to the base station via Msg. 3 PUSCH or / and Msg. A PUSCH. At this time, the bitmap may be configured in the form of MAC CE or RRC signaling. Each bit of the bitmap may correspond to an index for an SCell. For example, if an index for a specific SCell is mapped to a specific bit of the bitmap, the terminal may request (on-demand) SSB transmission for the specific SCell.

[0390] As described in Example 2, SCell(s) can be grouped, and each bit of the bitmap can be mapped to a SCell group(s). That is, the bitmap corresponding to the SCell group(s) described in Example 2 can also be reused / applied to Msg. A PUSCH transmission.

[0391] Example 3-2

[0392] As an example of the present disclosure, when the number of groups of SCell(s) is 1 or more (e.g., when SCell groups #1 and #2 exist), PRACH resources corresponding to each SCell group may be created and configured. The UE may indicate a specific SCell group through a PRACH (e.g., Msg. A or Msg. 1), and may indicate a specific SCell within the specific SCell group through a Msg. 3 PUSCH or a Msg. A PUSCH.

[0393] For example, assume that SCell group #1 includes {cell (e.g., SCell) #1, cell #2, cell #3}, and SCell group #2 includes {cell #4, cell #5, cell #6}. When a UE requests cell #2 (e.g., requests on-demand SSB transmission in cell #2), the UE may transmit a PRACH mapped to SCell group #1 to the base station. At this time, a reconfiguration of an index related to RO / preamble for the SCell group may be performed as described in Embodiment 1 for Msg. 1 or Msg. A (e.g., a message corresponding to PRACH) transmitted by the UE. That is, the UE may receive (re)configuration information related to an index related to RO / preamble for the SCell group from the base station.

[0394] In addition, the terminal can transmit the bitmap (e.g., a bitmap for indicating on-demand SSB request / transmission per SCell) to the base station via Msg. 3 or Msg. A PUSCH. At this time, the bitmap can be set to "010" (e.g., a value corresponding to cell #2 of SCell group #1).

[0395] Example 4

[0396] Embodiment 4 relates to an SSB triggering method of an SCell for on-demand SSB when a dedicated RACH resource is allocated. Embodiments 1 to 3 relate to procedures and parameters related to CBRA, and Embodiment 4 relates to operations when RACH resources are allocated based on configuration information related to dedicated RACH resources rather than SIB1 within a CFRA procedure.

[0397] In an uplink CA situation, if an uplink resource of a SCell other than a SpCell (special cell) of a general PCell or PSCell exists / is allocated, a bitmap in which a specific SCell index is mapped based on the uplink resource (e.g., a bitmap indicating an (on-demand) SSB transmission request in a specific SCell) can be transmitted to the base station by the terminal.

[0398] For example, the bitmap may be configured in the form of L2 MAC CE or L3 RRC signaling, and the bitmap may be transmitted to the base station via Msg. A PUSCH. The above-described procedure may also be applied to a 4-step RACH procedure that transmits a preamble via Msg. 1.

[0399] Example 4-1

[0400] As an example of the present disclosure, in the case of a dedicated RACH, unlike a common RACH broadcasted through SIB1, the preamble transmission method of Msg. 1 and the bitmap transmission method of PUSCH of Msg. A described above can be applied to a CFRA in which an uplink CA of an SCell, not an SpCell, exists.

[0401] And, unlike the 2-step RACH procedure, when CFRA is applied in the 4-step RACH, Msg. 3 is transmitted based on the C-RNTI, but TC-RNTI may be applied to enable reuse by other terminals for SSB transmission. And, when the message in the 2-step RACH includes a fallback RAR, the same method as message 3 of the 4-step RACH may be applied. In this case, TC-RNTI may also be applied to the message, and the PUSCH transmission through the fallback RAR may include a bitmap of MAC CE or a bitmap in the form of RRC signaling. The bitmap may include a bitmap indicating an (on-demand) SSB transmission request in the specific SCell described above.

[0402] Example 5

[0403] Embodiment 5 relates to a method for mapping an NES cell index to Msg. 1 for on-demand SIB1 in RRC Idle (or Inactive) state. A method for requesting / triggering on-demand SSB transmission for SCell(s) in CA state may be applied similarly to the method for requesting / triggering on-demand SIB1 transmission for neighboring cell(s).

[0404] When neighboring cell list information is received from cell A in RRC idle state, an on-demand SIB1 request can be performed / instructed from cell A based on the on-demand SI method. For example, the terminal can receive configuration information for SSB request-based Msg. 1 for neighboring cell(s) from the base station via SIB1. The terminal can transmit information indicating a neighboring cell requesting SIB1 transmission among the neighboring cell(s) to the base station.

[0405] For example, the terminal may transmit information for requesting SIB1 transmission from neighboring cells (e.g., an index of a neighboring cell (e.g., "ra-AssciationPeriodIndex") for triggering on-demand SIB1 transmission to the base station in a time pattern within the entire period in which the RACH can be transmitted. For example, at least one parameter combination among {"ra-PreambleStartIndex", "ra-AssociationPeriodIndex", and "ra-ssb-OccasionMaskIndex"} may be set differently for each neighboring cell.

[0406] That is, the neighboring cell for which transmission of on-demand SIB1 is requested may be configured / indicated differently depending on which combination of parameters (e.g., a combination based on at least one of {"ra-PreambleStartIndex", "ra-AssociationPeriodIndex", "ra-ssb-OccasionMaskIndex"}) corresponding to which PRACH is transmitted from the terminal to the base station.

[0407] For example, within a specific RO, "ra-PreambleStartIndex = 0" may be set by the base station to correspond to NES neighboring cell #1, and within a specific RO, "ra-PreambleStartIndex = 1" may be set by the base station to correspond to neighboring cell #2. The UE may transmit a PRACH corresponding to preamble index 1 in the RO to the base station to request on-demand SIB1 for NES neighboring cell #2.

[0408] That is, the terminal can receive SIB1 of a specific neighboring cell from the base station by transmitting a PRACH including a preamble from cell A (e.g., a PRACH including a preamble index corresponding to a specific neighboring cell, etc.) to the base station. Additionally or alternatively, PRACH information transmitted and received from cell A can be applied to a neighboring NES cell. The terminal can receive SIB1 from the base station by transmitting a PRACH to the neighboring NES cell.

[0409] Example 6

[0410] Example 6 relates to a method for mapping an NES cell index to Msg. 3 for on-demand SIB1 in RRC idle (or inactive) state.

[0411] Let's assume that an on-demand SIB1 (request) for a neighboring cell is mapped to Msg. 1 (e.g., the index of a neighboring cell is mapped to Msg. 1 to request on-demand SIB1 transmission from the neighboring cell). In this case, a problem may arise in that there is no defined method for requesting on-demand SIB transmission to multiple neighboring cells simultaneously, such as on-demand SSB for SCell in CA.

[0412] Accordingly, Msg. 3 based on an L3 or L2 control command, such as RRC signaling or MAC CE, can be transmitted to the base station. Msg. 3 can include information in the form of a bitmap, and through the bitmap information, a request signal for an on-demand SIB can be simultaneously transmitted to the base station in parallel. As described above, each bit of the bitmap can correspond to a neighboring cell for which on-demand SIB transmission is to be requested.

[0413] For example, the number of bits in the bitmap may be equal to the maximum value of the neighboring cell list that the base station can inform or set. For example, if the maximum value of the neighboring cell list is m (e.g., the number of neighboring cells is m), the number of bits in the bitmap may be m.

[0414] Additionally or alternatively, assume that more than one group of neighboring cells is configured / exist (e.g., NES neighboring cell group #1 and NES neighboring cell group #2 exist). PRACH resources corresponding to each neighboring cell group can be first generated by the terminal / base station. That is, the terminal can transmit a PRACH containing information associated with a specific neighboring cell group to the base station. The terminal can inform the base station via a bitmap via Msg. 3 PUSCH which neighboring cell among the specific neighboring cell groups it will request on-demand SIB transmission for. Here, the group of NES neighboring cells can be predefined or configured by the base station.

[0415] For example, assume that neighboring cell group #1 is {cell #1, cell #2, cell #3}, and neighboring cell group #2 is {cell #4, cell #5, cell #6}. When a terminal requests neighboring cell #2 (e.g., requests on-demand SIB transmission in neighboring cell #2), the terminal can transmit a PRACH mapped to neighboring cell group #1 (e.g., a PRACH including information mapped to neighboring cell group #1) to the base station.

[0416] For example, for Msg. 1 transmitted by the terminal (e.g., a message corresponding to PRACH), a reset may be performed for an index related to the RO / preamble for the SCell group as described in Embodiment 1. Then, the terminal may transmit the bitmap (e.g., a bitmap for indicating on-demand SIB request / transmission for each SCell) to the base station via Msg. 3 or Msg. A PUSCH. At this time, the bitmap may be set to "010" (e.g., a value corresponding to cell #2 of neighboring cell group #1).

[0417] For example, a terminal can transmit Msg. 3 (containing information related to a SIB1 request) from Cell A (e.g., a serving cell) to a base station, thereby receiving all SIB1s for multiple NES neighboring cells from the base station. That is, when a terminal transmits information related to a SIB1 request from a serving cell to a base station, the terminal can receive SIB1s for all neighboring cells from the base station.

[0418] Additionally or alternatively, the NES may transmit Msg. 3 (containing information related to the SIB1 request) to the neighboring cell, thereby receiving all SIB1s of multiple neighboring cells from the base station.

[0419] Example 7

[0420] Embodiment 7 relates to a method for mapping an NES cell index to Msg. A for transmission / reception and / or request of on-demand SIB1 in RRC idle (or disabled).

[0421] When a 2-step RACH is applied / performed as well as a 4-step RACH, Msg. A PUSCH may include information for an on-demand SIB request, like MSG. 3 PUSCH. For example, Msg. A PUSCH may include information elements such as RRC signaling or L3 or L2 control commands of MAC CE, and the information elements may be configured in the form of a bitmap as described in Embodiment 6, etc.

[0422] At this time, the early indication of Example 6 can be applied to the 2-step RACH, and information indicating a specific NES neighbor cell for transmitting SIB through Msg. A PUSCH can be transmitted and received.

[0423] Example 8

[0424] Example 8 relates to a method for triggering SIB1 of a NES neighboring cell for transmission / request of on-demand SIB1 when allocating dedicated RACH resources.

[0425] As described above, the UE can request and receive on-demand SIB1 in the RRC_IDLE or RRC_DEACTIVATE state. As another example, the UE can receive configuration information related to dedicated RACH resources from the base station in the RRC_CONNECTED state. Based on the dedicated RACH resources, the UE can transmit information requesting on-demand SIB1 for NES neighboring cells(s) for SIB1 to the base station.

[0426] As an example of the present disclosure, in the case of a 4-step RACH, unlike a 2-step RACH procedure, in a CFRA situation, Msg. 3 may be transmitted to the base station based on the C-RNTI, but TC-RNTI may be used for SSB or SIB1 transmission for reuse by other terminals. As another example, if a fallback RAR is included in the message in the 2-step RACH procedure, the same method as Msg. 3 of the 4-step RACH may be applied. In this case, TC-RNTI may also be applied to Msg. 3 of the 4-step RACH, and the PUSCH through the fallback RAR may include bitmap information in the form of MAC CE or bitmap information in the form of RRC signaling.

[0427] Example 9

[0428] Example 9 relates to information to be applied when performing procedures related to on-demand SSB or SIB1.

[0429] As described above, the UE can request SSB transmission of a specific SCell or SIB1 transmission of a NES neighboring cell via Msg. 1. As another example, the UE can transmit a bitmap to the base station via Msg. 3 or Msg. A PUSCH, and each bit of the bitmap can be mapped to an SCell index. That is, the UE can indicate a specific NES neighboring cell index via the bitmap, and accordingly, SSB or SIB1 transmission can be requested on the specific NES neighboring cell.

[0430] Additionally or alternatively, the MAC CE, which is an RRC signaling or L2 control command including the bitmap, may be transmitted to the base station via an uplink-only PUSCH based on C-RNTI without PUSCH transmission on a RACH procedure.

[0431] A terminal in the RRC idle (or inactive) state can perform the on-demand SIB1 request and transmission procedures. Furthermore, the terminal can transmit the remaining minimum SI, such as SIB1, to the base station in an RRC connected state.

[0432] For example, a terminal may request SSB and SIB1 transmission regardless of the RRC state. In this case, it is assumed that the terminal requests SSB transmission for an SCell and SIB1 transmission for an NES neighboring cell. In the case of requesting SSB transmission on-demand for each of a plurality of SCell(s) or / and requesting SIB1 transmission on-demand for each of a plurality of NES neighboring cell(s), the terminal may transmit a bitmap in the form of MAC CE or RRC signaling (e.g., a bitmap for requesting SIB or / and SSB transmission for each cell) to the base station regardless of the RACH procedure. Here, at least one of Embodiments 9-1 to 9-13 may be applied.

[0433] Example 9-1

[0434] The PUSCH message (Message 3 or Message A) transmitted by the terminal to the base station may include bitmap information in the form of MAC CE or RRC signaling. This bitmap information may be transmitted to the base station directly via a unicast-based dedicated PUSCH without triggering the RACH procedure.

[0435] At this time, there is insufficient or no physical resource allocation for uplink, but SR resources may be allocated to the terminal. The terminal may transmit the bitmap to the base station through MAC CE or RRC signaling based on the uplink physical resources (e.g., SR resources). For example, if SR resources are not allocated to the terminal, the terminal may perform all RACH procedures (e.g., transmission of Msg. 1 to Msg. 4 in the case of a 4-step RACH) and then be allocated uplink physical resources, and perform uplink transmission including the MAC CE or RRC signaling based on the allocated physical resources.

[0436] For example, if a large amount of uplink data to be transmitted is required even when SR resources are allocated to a terminal, the terminal may transmit an additional BSR and then transmit the bitmap to the base station. In this case, the bitmap may be transmitted to the base station via RRC signaling.

[0437] For each request for on-demand SSB in RRC connected state and each request for on-demand SIB1 in RRC idle (or deactivated) state, the UE may transmit RRC IE signaling with different bitmaps to the base station via Msg. 1 (or / and Msg. 3) or Msg. A PUSCH. That is, by transmitting RRC signaling with different bitmaps for on-demand SSB or on-demand SIB1 to the base station, it can be distinguished whether the UE requests on-demand SSB or on-demand SIB1.

[0438] However, the index period may be determined by the combination of {"ra-PreambleStartIndex", "ra-AssociationPeriodIndex", "ra-ssb-OccasionMaskIndex"} depending on the time / frequency of Msg. 1 and the preamble. Hereinafter, embodiments (e.g., embodiments 9-2, 9-3, and 9-4) for distinguishing the indexes for each of the on-demand SSB and the on-demand SIB1 will be described.

[0439] Example 9-2

[0440] In one embodiment of the present disclosure, for a request / transmission procedure of an on-demand SSB, the above-described parameter combinations related to preamble transmission, etc. may be included in the configuration information related to a dedicated RACH rather than a common RACH. For a request / transmission procedure of an on-demand SIB1, the above-described parameter combinations related to preamble transmission, etc. may be included in the configuration information related to a common RACH.

[0441] Example 9-3

[0442] In one embodiment of the present disclosure, the configurations for preamble RACH-related combinations of the request / transmission procedure of the on-demand SSB may be different from the configurations for preamble RACH-related combinations of the request / transmission procedure of the on-demand SIB1. For example, the configurations for ROs related to the request / transmission procedure of the on-demand SSB and the request / transmission procedure of the on-demand SIB1 may be different, respectively.

[0443] Example 9-4

[0444] In one embodiment of the present disclosure, multiple periodic index(es) may be generated for each of on-demand SSB and on-demand SIB1 by combining {"ra-PreambleStartIndex", "ra-AssociationPeriodIndex", "ra-ssb-OccasionMaskIndex"}. In this case, an index of a specific period may be mapped to a specific SCell (e.g., SSB-less) ID, and an index of another period may be mapped to a specific NES neighboring (e.g., SIB1-less) cell ID.

[0445] RACH Msg. 1 associated with on-demand SSB and on-demand SIB1 can share the same RO (e.g., location of time and frequency resources), and the periodic index value(s) generated by the three indices can be assigned differently. Accordingly, the UE can perform SSB transmission requests and / or SIB1 transmission requests for various NES neighboring cells and multiple SCell(s).

[0446] For example, RACH information that can additionally request on-demand SI from a NES neighboring cell can be transmitted and received between the terminal and the base station. As another example, information for each NES neighboring cell that can request multiple on-demand SIs can be transmitted by the terminal to the base station in the form of parameters using Msg. 3 or Msg. A PUSCH.

[0447] As an example of the present disclosure, when cell A (e.g., a base station through cell A) provides a list of NES neighboring cells to a terminal in the form of an index in an RRC idle (or inactive) state, one NES cell or a group of NES cells (e.g., a group of cells composed of one or more NES cells) can be designated / mapped for one index.

[0448] Information related to the NES neighboring cell(s) index (transmitted by the base station to the terminal) may include information on whether the cell or group of cells always transmits SIB1 or whether it is a cell that transmits SIB1 after receiving a request for on-demand SIB1. In this case, information related to the NES neighboring cell(s) index may be transmitted and received in the form of system information from Cell A.

[0449] Example 9-5

[0450] In one embodiment of the present disclosure, for a NES terminal that is first powered on, a cell that cannot transmit SIB1 (e.g., a cell that transmits SIB1 only upon request of on-demand SIB1) may not become Cell A (e.g., a serving cell). However, the cell may become a serving cell through a cell reselection process. In the case of a basic (or legacy) cell, the cell (re)selection operation for the cell may not be performed.

[0451] Example 9-6

[0452] In one embodiment of the present disclosure, in relation to an on-demand SIB request, a terminal in RRC idle state can know in advance whether or not the NES neighboring cell is accessible in cell A, and can attempt a RACH procedure or the like without receiving SIB1 for suitable cells except for barred cells (without cell reselection process), if necessary.

[0453] In the RRC_IDLE state, a serving cell may refer to a cell that receives SI and attempts RACH when necessary, excluding barred cells among suitable cells whose received SSB strength exceeds a reference value. A neighboring cell may collectively refer to a cell existing within a predefined range based on the serving cell. The terminal may receive information about neighboring cell(s) from the base station. At this time, information on whether the neighboring cell transmits SIB1 may be transmitted to the terminal in advance through SIB information.

[0454] In cell A, PRACH resources related to transmission of SIB1 of an NES neighboring cell (e.g., a SIB1-less cell of the present disclosure) may be allocated. The on-demand SI procedure described above for triggering SIB1 for preamble and Msg. 3 may be applied.

[0455] For example, in case of Msg. 1 or Msg. A RACH of preamble 1, the UE can request the NES neighboring cell SIB1 from the base station, and can request the corresponding NES on-demand SI from the base station through Msg. 3 or Msg. A PUSCH. In cell A, the SIB1-related PRACH resources of the NES neighboring cells and the Msg. 1 or Msg. A RACH-related resources can be allocated to the UE. Additionally, the base station can additionally inform the UE of the on-demand SI information of the corresponding NES neighboring cells. However, a lot of information can be added to the information of SIB1 of cell A. Hereinafter, embodiments of the configuration of SIB1 of cell A will be described.

[0456] Example 9-7

[0457] In one embodiment of the present disclosure, all or part of the on-demand SI related information and / or on-demand SI allocation information of an NES neighboring cell in cell A may be transmitted and received via a new SIBx (where x is a natural number greater than or equal to 2) rather than SIB1. For example, a transmission request operation for SIB1 and / or SIBx in Msg. 1 of the preamble may correspond to a request for SIB1 and SIBx for multiple (SIB1-less) cells rather than a single NES neighboring cell.

[0458] Example 9-8

[0459] In one embodiment of the present disclosure, when an on-demand SI request is made in Msg. A PUSCH or Msg. 3, a specific bit (e.g., 1 bit) may be added to a bitmap containing a request for SIB1. The specific bit may be mapped with information related to the on-demand SI of the corresponding NES neighboring cells.

[0460] At this time, the request for SIB1 can be performed according to the RACH procedure. As another example, the request for SIB1 can be indicated by a specific bit in the bitmap of Msg. A PUSCH or Msg. 3 PUSCH. The request for transmission of SIB1 can be performed in multiple cells (e.g., cells without SIB1), and the request for transmission of SIB1 can be configured to be configurable. The request for the above-described procedure (e.g., the request for transmission of SIB1) can be performed in Cell A or a NES neighboring cell. The request for the above-described procedure can be configurable or predefined.

[0461] When requesting SIB1 or SIBx through Msg. A PUSCH or Msg. 3 PUSCH, the UE may transmit information about an index for a cell requesting SIB1 or SIBx to the base station through Msg. A PUSCH or Msg. 3 PUSCH. The information requesting SIB1 and SIBx for multiple cells may be configured in the form of a bitmap. That is, the UE may transmit to the base station a bitmap including an index for at least one cell and / or information requesting SIB1 and / or SIBx for at least one cell.

[0462] Example 9-9

[0463] In one embodiment of the present disclosure, a terminal may receive dedicated PRACH configuration information for transmission of SIB1 per NES cell from a base station. The terminal may request on-demand SI transmission from the base station via Msg. 3 (based on the dedicated PRACH configuration information). Note that even when a dedicated PRACH is applied, a RAR message (e.g., MAC CE) may be required in addition to RAPID in the RAR.

[0464] The above-described method can also be applied to a two-step RACH. For example, a UE can transmit a message A PRACH for a specific NES cell to the base station. The UE can request on-demand SI for the specific NES cell from the base station through the bitmap in the message A PUSCH.

[0465] Example 9-10

[0466] In one embodiment of the present disclosure, a common PRACH resource may be configured for one or more NES cells. The terminal may request the base station to transmit information about the NES cell index (or ID) and on-demand SI via Msg. 3. Here, the cell index may indicate whether transmission of SIB1 and / or additional SI is required. For example, the terminal may transmit to the base station a bitmap in which each bit corresponds to a cell index.

[0467] The above-described method can also be applied to a two-step RACH procedure. The UE can transmit a common Msg. A PRACH for one or more NES cells to the base station. The UE can request on-demand SI transmission for a specific NES cell by indicating the specific NES cell through the Msg. A PRACH.

[0468] Example 9-11

[0469] In one embodiment of the present disclosure, for an NES cell, the base station may transmit SIB1 to the terminal only when it receives on-demand SIB1. If the NES cell becomes a serving cell, the terminal may also transmit information about SIB1 requests for other NES neighboring cell(s) to the base station via SIB1 or SIBx.

[0470] Specifically, the terminal may transmit information requesting on-demand SIB1 of another neighboring NES cell to the base station via the NES cell. Additionally or alternatively, the terminal may request SIB1 transmission for multiple NES cells via PRACH, Msg. 3, or Msg. A PUSCH.

[0471] Additionally or alternatively, the base station may transmit PRACH resource allocation information to the terminal for on-demand SIB1 transmission requests from other neighboring NES cells. On-demand SIB1 triggering based on the corresponding PRACH resources may only be possible in the corresponding cell.

[0472] Additionally or alternatively, if information about neighboring cells is transmitted and received via higher layer signaling, the neighboring cell list(s) of NES cells (e.g., a list including IDs and / or indices of neighboring cells) may be included in the SIB. As another example, the base station may transmit a newly defined SIBx (where x is a natural number greater than or equal to 2) to the terminal, and the SIBx may include reselection information about the neighboring cell list. A new SIBx may be defined / configured to provide information about the NES neighboring cell list.

[0473] Additionally or alternatively, the NES neighbor cell list parameter may be included on SIB 2, SIB 3 and / or SIB 4.

[0474] Additionally or alternatively, information about PRACH resource allocation that can trigger SIB1 transmission for each of the NES neighboring cells may be transmitted to the terminal, and the information about PRACH resource allocation may be configured in the form of parameters for each of the listed neighboring cells.

[0475] Additionally or alternatively, the information about PRACH resource allocation may include PRACH information that may additionally request on-demand SI from a NES neighboring cell. As another example, the information about PRACH resource allocation may include information for each NES neighboring cell that may request multiple on-demand SIs via Msg. 3 or Msg. A PUSCH.

[0476] Example 9-12

[0477] In one embodiment of the present disclosure, when performing reselection in an RRC idle state or an RRC inactive state, a parameter providing priority in an NES cell or cell A, etc. may be defined. The network (or base station) may control reselection of an NES cell or cell A, etc.

[0478] As an example of the present disclosure, the base station can be configured to allow the NES terminal to preferentially reselect to the NES cell or to reselect to cell A.

[0479] For example, a new offset value for the Q value (e.g., a value related to the cell reselection criterion) may be added, or a new Q value may be defined. Another example is that a new formula or threshold for performing reselection using the Q value may be added or changed. The basic neighbor cell list may not include information related to NES cells to prevent basic terminals from accessing it.

[0480] In describing the present disclosure, an NES cell is defined as a cell that transmits SIB1 only upon receiving an on-demand SIB1 request. However, if the cell does not transmit SSB, SSB may also be transmitted for a certain period of time even when an SIB1 request is made. Furthermore, the terminal may receive configuration information regarding the transmission timing and method of SSB and / or SIB1 related to the cell in advance from another cell.

[0481] Example 9-13

[0482] In one embodiment of the present disclosure, in a CA situation, in relation to a request for on-demand SSB, a terminal may select the number of transmissions or density of SSBs associated with SCell(s).

[0483] When a PRACH request is made for a specific SCell, resource allocation per SCell can be divided into one or more groups, and the number of transmissions or transmission density for each group can be set differently depending on the RO / preamble. Accordingly, the UE can select the RO / preamble depending on the situation.

[0484] For example, RACH resources can be divided into two groups, and a UE can request resources from one of the groups. The UE can make an SSB request by transmitting a PRACH to the base station. In addition, the UE can request the corresponding transmission count or transmission density through Msg. 3 or Msg. A PUSCH. For example, the SSB request and / or transmission count / density request can be performed in the form of a preset index.

[0485] In one embodiment of the present disclosure, when an on-demand SSB or SIB1 procedure is applied, transmission of SSB or SIB1 to a specific cell may be performed by the base station only at the moment when the terminal needs it, for energy saving or interference mitigation.

[0486] At this time, the base station may include a method for indicating information related to on-demand SSB and / or SIB1 using the RACH procedure of on-demand SI of the basic wireless communication system. The above-described method can be extended to SCells without SSB or neighboring cells without SIB1 by various embodiments of the present disclosure.

[0487] The methods, embodiments or descriptions for implementing the method proposed in the present disclosure may be applied separately, or one or more methods (or embodiments or descriptions) may be applied in combination.

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

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

[0490] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0491] Here, the wireless communication technology implemented in the device of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0492] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A and 5G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A step in which first configuration information related to a system information block request is received by a terminal from a base station, wherein the first configuration information includes parameters related to each of a plurality of neighboring cell groups; A step of transmitting a first uplink channel including a first parameter related to a first neighboring cell group among the plurality of neighboring cell groups to the base station by the terminal; and A method comprising the step of receiving, by the terminal, from the base station a first system information block for the first neighboring cell group.

2. In paragraph 1, The parameters associated with each of the plurality of neighboring cell groups include at least one of a random access preamble index, an association period index, or a physical random access channel (PRACH) mask index mapped to each of the plurality of neighboring cell groups, A method wherein the first parameter comprises at least one of a random access preamble index, an index of an association period, or a PRACH mask mapped to the first neighboring cell group.

3. In paragraph 1, A parameter set for uplink channel transmission for each of the plurality of neighboring cell groups is transmitted from the base station to the terminal, A method in which the first uplink channel is transmitted to the base station based on parameters for the first uplink channel transmission for the first neighboring cell group among the parameter sets.

4. In paragraph 3, A method wherein, based on the terminal being in an RRC (radio resource control) connected state, the parameters for the first uplink channel transmission for the first neighboring cell group include parameters related to dedicated random access channel resources associated with the first neighboring cell group.

5. In paragraph 3, A method wherein the parameters for the first uplink channel transmission for the first neighboring cell group include at least one of a parameter related to a time resource of the first uplink channel, a parameter related to a frequency resource, and a spatial parameter.

6. In paragraph 1, A method in which the first uplink channel is transmitted from the terminal to the base station through the serving cell.

7. In paragraph 1, A method in which the first system information block is transmitted from the base station to the terminal via at least one secondary cell included in the first neighboring cell group.

8. In paragraph 1, Second configuration information for the plurality of neighboring cell groups is transmitted from the base station to the terminal, A method according to claim 1, wherein the second configuration information comprises at least one of a list of at least one secondary cell included in each of the plurality of neighboring cell groups, information related to an activation status of each of the at least one secondary cell, or information related to whether a system information block is transmitted for the at least one secondary cell.

9. In paragraph 1, A second system information block including the first setting information is transmitted from the base station to the terminal, The above first system information block is system information block 1 for the first neighboring cell group, A method wherein the second system information block is a system information block x (x is a natural number greater than or equal to 1) for the serving cell group.

10. In paragraph 9, The second system information block includes third configuration information for at least one opportunity for uplink channel transmission, A method wherein the first uplink channel is transmitted from the terminal to the base station in at least one opportunity.

11. In paragraph 10, A method wherein the third configuration information comprises at least one of the number of the at least one opportunity, time and frequency resources of each of the at least one opportunity, or a period of the at least one opportunity.

12. In paragraph 1, A method wherein the first uplink channel includes a PRACH.

13. In paragraph 1, A method wherein the terminal is in an RRC_idle or RRC_inactive state.

14. One or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: First configuration information related to a system information block request is received from a base station via the one or more transceivers, wherein the first configuration information includes parameters related to each of a plurality of neighboring cell groups; Transmitting a first uplink channel including a first parameter related to a first neighboring cell group among the plurality of neighboring cell groups to the base station through the one or more transceivers; and A terminal configured to receive a first system information block for the first neighboring cell group from the base station through the one or more transceivers.

15. A step in which first configuration information related to a system information block request is transmitted by a base station to a terminal, wherein the first configuration information includes parameters related to each of a plurality of neighboring cell groups; A step of receiving, by the base station, from the terminal a first uplink channel including a first parameter related to a first neighboring cell group among the plurality of neighboring cell groups; and A method comprising the step of transmitting a first system information block for the first neighboring cell group to the terminal by the base station.

16. In the base station, the base station: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: First configuration information related to a system information block request is transmitted to a terminal via the one or more transceivers, wherein the first configuration information includes parameters related to each of a plurality of neighboring cell groups; Receiving a first uplink channel including a first parameter related to a first neighboring cell group among the plurality of neighboring cell groups from the terminal through the one or more transceivers; and A base station configured to transmit a first system information block for the first neighboring cell group to the terminal via the one or more transceivers.

17. In a processing device configured to control a terminal, the processing device: one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions that, when executed by said one or more processors, perform a method according to any one of claims 1 to 13.

18. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more commands are executed by one or more processors to control a device to perform a method according to any one of claims 1 to 13.

Images