Data collection method and device for training beam prediction model in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. More specifically, a method performed by a terminal in a wireless communication system may comprise the steps of: receiving, from a base station, configuration information related to beam prediction-based beam management; on the basis of the configuration information, performing measurements related to the beam prediction-based beam management at a plurality of measurement time points, respectively; and transmitting, to the base station, a measurement report including results of the measurements performed at the plurality of measurement time points, respectively.

Description

Data collection method and device for learning a beam prediction model in a wireless communication system

[0001] The present disclosure relates to a data collection method and device for training an Artificial Intelligence (AI) and Machine Learning (ML) model for predicting beam information between a base station and a terminal in a mobile communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of radio interface architecture / protocols for technologies such as intelligent factories (Industrial Internet of Things, IoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover (CHO) and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures is also in progress, and standardization of system architecture / services for 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal is also in progress.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] As described above and with the development of mobile communication systems, various services have become available, and methods for effectively providing these services are required.

[0009] Based on the discussion described above, the present disclosure provides a device and method capable of effectively providing a service in a wireless communication system.

[0010] In a method performed by a terminal in a wireless communication system, the method may include: receiving, from a base station, configuration information related to beam management based on beam prediction; performing, based on the configuration information, measurements related to the beam management based on beam prediction at a plurality of measurement points in time; and transmitting, to the base station, a measurement report including results of measurements performed at each of the plurality of measurement points in time.

[0011] In a method performed by a base station in a wireless communication system, the method may include: receiving, from a terminal, configuration information related to beam management based on beam prediction; and, based on the configuration information, receiving, from the terminal, a measurement report including results of measurements related to the beam management based on beam prediction performed at each of a plurality of measurement points in time.

[0012] In a wireless communication system, a terminal includes a transceiver; and a controller connected to the transceiver, wherein the controller is configured to receive, from a base station, configuration information related to beam prediction-based beam management, perform measurements related to the beam prediction-based beam management at a plurality of measurement points based on the configuration information, and transmit, to the base station, a measurement report including results of measurements performed at each of the plurality of measurement points.

[0013] In a wireless communication system, a base station includes a transceiver; and a controller connected to the transceiver, wherein the controller is configured to receive, from a terminal, configuration information related to beam prediction-based beam management, and, based on the configuration information, receive, from the terminal, a measurement report including results of measurements related to beam prediction-based beam management performed at each of a plurality of measurement points in time.

[0014] The present disclosure provides a device and method capable of effectively providing a service in a wireless communication system.

[0015] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.

[0016] FIG. 2 is a diagram illustrating a wireless protocol structure in an LTE and NR system according to one embodiment of the present disclosure.

[0017] FIG. 3 is a diagram illustrating a beam management process between a base station and a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 4 is a diagram illustrating a use case of utilizing an AI / ML model for beam information prediction in a wireless communication system according to one embodiment of the present disclosure and a learning or deployment process of the AI / ML model.

[0019] FIG. 5 is a flowchart of a process in which a base station instructs a terminal in an RRC_CONNECTED state to perform continuous beam measurements and reports the results to learn a model for predicting beam information in the time domain, according to one embodiment of the present disclosure.

[0020] FIG. 6 is a flowchart of a process in which a base station instructs an RRC_CONNECTED state terminal to measure all beams or a specific beam combination and reports the results in order to learn a model for predicting beam information in a spatial domain, according to one embodiment of the present disclosure.

[0021] FIG. 7 is a flowchart of a process in which a base station instructs a terminal to measure a beam in an RRC_IDLE / RRC_INACTIVE state and reports the result to learn a model for predicting beam information in a spatial domain and / or a time domain, according to one embodiment of the present disclosure.

[0022] FIG. 8 is a flowchart of a process for instructing a terminal to continue beam measurement even after transitioning from an RRC_IDLE / RRC_INACTIVE state to an RRC_CONNECTED state in order to learn a model for predicting beam information in the time domain, according to one embodiment of the present disclosure.

[0023] FIG. 9 is a diagram illustrating a terminal device according to one embodiment of the present disclosure.

[0024] FIG. 10 is a diagram illustrating a base station device according to one embodiment of the present disclosure.

[0025] FIG. 11 is a block diagram showing an example of a configuration of a terminal according to one embodiment of the present disclosure.

[0026] FIG. 12 is a block diagram showing an example of a configuration of a base station according to one embodiment of the present disclosure.

[0027] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, in describing the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of the present disclosure, such detailed description will be omitted. This is to ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanation.

[0028] The terms described below are defined based on the functions of this disclosure, and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this disclosure.

[0029] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size.

[0030] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the disclosure.

[0031] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0032] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0033] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0034] In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

[0035] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0036] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH can also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" can be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."

[0037] Hereinafter, in the present disclosure, upper signaling refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer. Upper signaling can be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).

[0038] For the convenience of explanation below, this disclosure uses terms and names defined in the 3rd Generation Partnership Project NR (New Radio) or 3rd Generation Partnership Project Long Term Evolution (LTE) standards. However, this disclosure is not limited by the above terms and names, and can be equally applied to systems conforming to other standards. In this disclosure, gNB may be used interchangeably with eNB for the convenience of explanation. That is, a base station described as an eNB may represent a gNB. In addition, the term terminal may represent not only a mobile phone, an MTC device, an NB-IoT device, a sensor, but also other wireless communication devices.

[0039] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNodeB (gNB), an eNode B (eNB), a NodeB, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Of course, the present invention is not limited to the above examples.

[0040] In this disclosure, downlink (DL) refers to a wireless transmission path for a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path for a signal transmitted from a terminal to a base station. In addition, although LTE, LTE-A, or 5G systems may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, the fifth generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a scope that does not significantly deviate from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0041] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0042] As a representative example of the above broadband wireless communication system, the LTE system adopts the Orthogonal Frequency Division Multiplexing (OFDM) method in the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0043] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0044] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by utilizing a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz bands.

[0045] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, due to the nature of the service. This may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, very long battery lifespans, such as 10 to 15 years, may be required.

[0046] Finally, URLLC refers to cellular-based wireless communication services used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, services supporting URLLC must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0047] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0048] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.

[0049] Referring to FIG. 1, a wireless communication system may be composed of multiple base stations (e.g., gNB (105), ng-eNB (110), ng-eNB (115), gNB (120)), an Access and Mobility Management Function (AMF) (125), and a User Plane Function (UPF) (130). A user equipment (hereinafter referred to as UE or terminal) (135) may access an external network through the base stations (e.g., gNB (105), ng-eNB (110), ng-eNB (115), gNB (120)) and the UPF (130).

[0050] In Fig. 1, base stations (e.g., gNB (105), ng-eNB (110), ng-eNB (115), gNB (120)) can provide wireless access to terminals accessing the network as access nodes of a cellular network. That is, the base stations (e.g., gNB (105), ng-eNB (110), ng-eNB (115), gNB (120)) can collect status information such as buffer status, available transmission power status, and channel status of terminals to schedule them in order to service user traffic, thereby supporting a connection between the terminals and a core network (CN; in particular, the CN of NR is referred to as 5GC). Meanwhile, in communication, a user plane (UP) related to transmission of actual user data and a control plane (CP) such as connection management can be configured separately, and in this drawing, gNB (105) and gNB (120) use UP and CP technologies defined in NR technology, and ng-eNB (110) and ng-eNB (115) can use UP and CP technologies defined in LTE technology even though they are connected to 5GC.

[0051] The above AMF (125) is a device that is responsible for various control functions as well as mobility management functions for terminals and is connected to multiple base stations, and the UPF (130) may refer to a type of gateway device that provides data transmission. Although not illustrated in Fig. 1, the NR wireless communication system may also include a Session Management Function (SMF). The SMF can manage packet data network connections, such as PDU (protocol data unit) sessions provided to terminals.

[0052] FIG. 2 is a diagram illustrating a wireless protocol structure in an LTE and NR system according to one embodiment of the present disclosure.

[0053] Referring to FIG. 2, the wireless protocol of the LTE system may be composed of Packet Data Convergence Protocol (PDCP) (205)(240), Radio Link Control (RLC) (210)(235), and Medium Access Control (MAC) (215)(230) in the terminal and the eNB, respectively. Packet Data Convergence Protocol (PDCP) (205)(240) is responsible for operations such as IP header compression / reconstruction, and Radio Link Control (RLC, hereinafter referred to as RLC) (210)(235) reconfigures PDCP Protocol Data Unit (PDU) to an appropriate size. MAC (215)(230) is connected to multiple RLC layer devices configured in one terminal, and multiplexes RLC PDUs into MAC PDUs and demultiplexes RLC PDUs from MAC PDUs. The physical (PHY) layer (220)(225) performs an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer. In addition, the physical layer also uses HARQ (Hybrid ARQ) for additional error correction, and the receiver transmits 1 bit to indicate whether or not the packet transmitted by the transmitter was received. This is called HARQ ACK / NACK information. In the case of LTE, downlink HARQ ACK / NACK information for uplink data transmission is transmitted through the PHICH (Physical Hybrid-ARQ Indicator Channel) physical channel, and in the case of NR, it can be determined through the PDCCH (Physical Dedicated Control Channel), which is a channel through which downlink / uplink resource allocation, etc. are transmitted, whether retransmission is necessary or new transmission can be performed through the scheduling information of the corresponding terminal. This is because NR applies asynchronous HARQ.Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted via a physical channel, such as a PUCCH (Physical Uplink Control Channel) or a PUSCH (Physical Uplink Shared Channel). The PUCCH is typically transmitted on the uplink of the PCell, which will be described later. However, if the base station supports this, it may additionally transmit the PUCCH to the SCell, which will be described later, to the UE. This is referred to as a PUCCH SCell.

[0054] Although not shown in this drawing, an RRC (Radio Resource Control) layer exists above the PDCP layer of each terminal and base station, and the RRC layer can exchange connection and measurement-related setting control messages for radio resource control.

[0055] Meanwhile, the above PHY layer can be composed of one or more frequencies / carriers, and the technology that sets and uses multiple frequencies simultaneously is called carrier aggregation (CA). CA technology can dramatically increase the transmission capacity by the number of secondary carriers by additionally using the primary carrier and one or more secondary carriers instead of using only one carrier for communication between a terminal (or User Equipment, UE) and a base station (E-UTRAN NodeB, eNB). Meanwhile, in LTE, a cell within a base station that uses a primary carrier is called a primary cell or PCell (Primary Cell), and a cell within a base station that uses a secondary carrier is called a subcell or SCell (Secondary Cell).

[0056] FIG. 3 is a diagram illustrating a beam management process between a base station and a terminal in a next-generation mobile communication system according to one embodiment of the present disclosure.

[0057] Referring to FIG. 3, the base station (305) can instruct the terminal (300) to measure Layer 1 (L1) and Layer 3 (L3) layers beams and report the results to the terminal in order to select (or manage) beams to be used for DL ​​and UL transmission with the terminal. The specific procedures for each step are as follows.

[0058] In step 310, the terminal and the base station can acquire initial Tx and Rx beams to be used for DL ​​and UL transmission through a random access procedure.

[0059] In step 320, the base station can instruct the terminal to perform beam measurement and report the results through the RRCReconfiguration procedure in order to appropriately change the beam to be used for DL ​​and UL transmission based on the movement of the terminal and changes in the channel environment. At this time, the base station can instruct beam measurement and report at the L1 layer together with beam measurement and report at the L3 layer. In addition, the base station can set various Transmission Configuration Indicator state (TCI state) information used to indicate beam information to be used for DL ​​and UL transmission to the terminal. This TCI state information can be utilized by the base station to indicate beam information to be used for DL ​​and UL transmission to the terminal in step 143 below.

[0060] In step 330, the terminal performs signal measurement for a specific frequency, cell, or beam according to the base station instruction in step 320, and if the L3 layer MeasurementReport transmission condition is satisfied, the terminal can transmit the MeasurementReport. At this time, if the terminal has an L3 beam measurement result for a specific cell, it can include it in the MeasurementReport (330) as in 333. The L3 beam measurement result can include a list of SSB and CSI-RS indices transmitted using multiple beams, and at least one of an L3 Reference Signal Received Power (RSRP) measurement result, an L3 Reference Signal Received Quality (RSRQ) measurement result, or an L3 Signal to Interference plus Noise Ratio (SINR) measurement result corresponding to each index. At this time, the terminal can include measurement results for up to 64 SSB and CSI-RS indices.

[0061] In step 340, the terminal can measure the beam for the serving cell according to the base station instructions in step 320 and periodically report the results to the base station via a CSI-report. Depending on the base station settings in step 320, the terminal can include up to four SSBRIs (SS / PBCH Block Resource Indications) or CRIs (CSI Reference Signal Resource Indicators) and corresponding L1 RSRP information in the periodically transmitted CSI-report (341), as shown in 349. At this time, the SSBRIs and CRIs included in the CSI-report can be selected in order of beam quality.

[0062] At step 343, the optimal beam to be used for DL ​​and UL transmission to the terminal may change depending on the movement of the terminal or changes in the wireless channel environment.

[0063] At step 345, the terminal can report the measurement results for the changed optimal beam to the base station through CSI-report.

[0064] In step 347, the base station can determine that the optimal beam to be used for DL ​​and UL transmission between the base station and the terminal has changed based on the CSI report transmitted by the terminal in step 145, and can instruct the terminal to change the DL and UL beams. For this purpose, MAC CE (e.g., TCI State Indication for UE-specific PDCCH MAC CE or TCI State Activation / Deactivation for UE-specific PDSCH MAC CE, etc.) and DCI (e.g., DCI Format 1_1) can be used.

[0065] FIG. 4 is a diagram illustrating a use case of utilizing an AI / ML model for beam information prediction in a next-generation mobile communication system according to one embodiment of the present disclosure and a learning or deployment process of the AI / ML model.

[0066] Referring to FIG. 4, the AI / ML model can be utilized to predict beam information in the spatial and temporal domains.

[0067] In a use case (440) for predicting beam information in a spatial domain, an AI / ML model can be trained to output prediction results (445) for all beams requiring measurement (e.g., L1 / L3 RSRP prediction results for all beams) when measurement information (441) for some beams (e.g., L1 / L3 RSRP measurement results for some beams) is input. At this time, the measurement information (441) for some beams may include a subset (442) of the entire beam set to be predicted or another beam set (443) that does not belong to the entire beam set to be predicted. When an AI / ML model for predicting beam information in the spatial domain is deployed and used at the base station, even if the terminal does not include the entire beam measurement results in the beam measurement result report (333) included in the L3 measurementReport (330) in FIG. 3 and reports only the measurement results for some beams, the base station can use the AI / ML model to predict the L1 / L3 measurement results for the entire beam set, thereby reducing the signaling load for beam measurement and result reporting. In addition, when the terminal reports the measurement results (349) for a limited beam set through the CSI-report (341) in FIG. 3, the base station can use the AI / ML model to predict the L1 / L3 measurement results for the entire beam set and more accurately determine the optimal beam to be used for DL ​​and UL transmission.

[0068] In a use case (450) for predicting beam information in the time domain, the AI / ML model can be trained to output prediction results (455) for all beams in the future (e.g., L1 / L3 RSRP prediction results for all beams during times t_k+1 to t_k+F) when measurement information (453) for some beams acquired in the past (e.g., L1 / L3 RSRP measurement results for some beams measured during times t_1 to t_k) is input. At this time, the measurement information (453) for some beams in the past can be a subset of the future entire beam set to be predicted or a different beam set that does not belong to the entire beam set to be predicted. When an AI / ML model for predicting beam information in the time domain is deployed and used at the base station, the base station can more quickly predict an optimal beam for a fast-moving terminal and change the beams used for DL ​​and UL transmission at an appropriate time. More specifically, in FIG. 1C, the base station periodically receives a CSI-report from the terminal, and can change the beam to be used for DL ​​and UL transmission based on the beam information included in the CSI-report. However, since the base station receives the CSI-report according to the CSI-report reporting cycle, a delay time (hereinafter referred to as “beam change delay”) may occur between the time point (443) when the optimal beam is actually changed due to a change in the channel environment and the time point (445) when the actual base station receives the CSI-report from the terminal and determines the change in the optimal beam. In addition, when the terminal moves quickly, this beam change delay may cause beam management failure. According to an embodiment of the present disclosure, a beam information prediction method can prevent beam management failure by predicting the optimal beam change in advance by using AI / ML that predicts beam information in the time domain when the terminal moves quickly, and changing the beam to be used for DL ​​and UL transmission at an appropriate time.

[0069] In the present disclosure, as a use case of using an AI / ML model for beam information prediction in the spatial and temporal domains, an embodiment in which a beam prediction AI / ML model is used in a base station has been described. However, this is merely an example and the beam prediction AI / ML model can also be used in a terminal. In this case, the terminal can reduce the beam measurement load by performing measurements for only some beam combinations rather than all beam combinations in the beam measurement operation and predicting the measurement results for all beam combinations using the beam prediction model in the spatial domain. In addition, the terminal can predict the optimal beam in advance using the beam prediction model in the temporal domain and report this to the base station in advance, thereby helping the base station to change the beam at an appropriate time.

[0070] According to one embodiment of the present disclosure, a spatial / temporal domain beam prediction AI / ML model can be trained in a network (405). To this end, as in step 410, the network can instruct the terminal to measure and report data necessary for training the beam prediction AI / ML model. Thereafter, in step 415, the terminal can perform beam measurement according to the network instruction in step 410 and report the result to the network. In step 420, the network can train the spatial / temporal domain beam prediction AI / ML model based on the beam measurement result information collected from the terminal in step 415. According to one embodiment, the training of the model can be performed in a network entity other than a base station (gNB) (e.g., an Operation, Administration, Maintenance (OAM) server, a Trace Collection Entity (TCE) server, etc.). If the training of the model is performed in a network entity other than the base station, the base station can transfer the beam measurement result information collected from the terminal to another network entity in step 415. Additionally, beam prediction AI / ML models learned from other network entities can be transmitted back to the base station. If the beam prediction AI / ML model learned in step 420 is to be deployed and used on a terminal, the network can transmit the learned model to the terminal in step 430. Thereafter, the beam prediction AI / ML model can be deployed and operated on the terminal (435) or the network (437).

[0071] In FIGS. 5, 6, 7, and 8, specific embodiments of methods and procedures for a network to instruct a terminal to perform beam measurement and reporting necessary for beam prediction AI / ML model learning and to receive a report of the results are described.

[0072] FIG. 5 is a flowchart of a process in which a base station instructs a terminal in an RRC_CONNECTED state to perform continuous beam measurements and reports the results to learn a model for predicting beam information in the time domain, according to one embodiment of the present disclosure.

[0073] Referring to FIG. 5, the base station can learn a model for predicting beam information in the time domain based on continuous full beam measurement information in the time domain (e.g., measurement results for each full beam at times t_n, t_n+1, t_n+2, ..., t_k) (510). In other words, in order to learn a model for predicting beam information in the time domain, the base station may require continuous full beam measurement information (510) in the time domain.

[0074] To this end, the base station can instruct the terminal in the RRC_CONNECTED state to report the L1 or L3 beam measurement results (more specifically, the L1 or L3 RSRP / RSRQ / SINR values ​​calculated by measuring SSB and CSI-RS transmitted through different beams) through RRC signaling. The basic (typical or conventional) operation flow (520) between the base station and the terminal for this purpose is as follows.

[0075] In step 521, the base station can instruct the terminal to measure and report the results for specific frequencies, cells, and beams through the RRCReconfiguration procedure. More specifically, the base station can instruct the terminal to the frequency, cell, and beam to be measured (i.e., the SSB or CSI-RS transmitted using a specific beam) through the RRCReconfiguration message. Additionally, the base station can include measurement time configuration information (SMTC, SSB Measurement Timing Configuration) in the RRCReconfiguration message to instruct the terminal at what point in time it can measure the SSB or CSI-RS transmitted using a specific beam. Furthermore, the base station can instruct the report type (reportType: periodical or eventTriggered) and the Reference Signal type (rsType: SSB or CSI-RS) for which the measurement results should be reported through the RRCReconfiguration message with respect to the measurement result reporting. At this time, the report cycle (ReportInterval) and the number of reports (reportAmount) can be additionally set.

[0076] In step 522, the terminal can measure SSB and CSI-RS at SMTC cycles (configurable to 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms) (524) according to the beam measurement and result reporting settings provided by the base station in step 521. If the result reporting type is set to periodical, the terminal can perform the first measurement and report the measurement results to the base station by including them in MeasurementReport (523) when the result value reporting becomes possible. Afterwards, the terminal transmits MeasurementReport at a cycle of ReportInterval (e.g., 120ms, 240ms, 480ms, 640ms, 1024ms, 2048ms, 5120ms, 10240ms, 20480ms, 40960ms, 1min, 6min, 12min, 30min) (527) set by the base station in step 521, and when transmitting MeasurementReport (529), the terminal can include the most recently measured SSB and CSI-RS measurement results (525) in the MeasurementReport and report them to the base station. Meanwhile, when the result report type is set to 'eventTriggered', the terminal can measure SSB and CSI-RS at every SMTC cycle and check whether the set event occurrence condition is satisfied. If the event occurrence condition is satisfied, the terminal can start transmitting the MeasurementReport message.

[0077] In the basic operation flow embodiment (520), when the ReportingInterval (527) value is set to be greater than the SMTC cycle (524), only a part of the result information (SSB / CSI-RA Measurement #1 and SSB / CSI-RA Measurement #K) that the actual terminal measured in the time domain for each SMTC cycle may be reported to the base station. However, the base station can learn the time-domain beam prediction model based on the continuous full beam measurement information measured by the actual terminal for the SMTC cycle. Therefore, the beam measurement and reporting operation basic flow (520) can be improved as in the operation flow (530) so that the base station can receive continuous beam measurement information necessary for learning the time-domain beam prediction model from the terminal. In other words, the base station according to one embodiment of the present disclosure can receive continuous beam measurement information necessary for learning the time-domain beam prediction model from the terminal based on the operation flow (530).

[0078] In step 531, the base station can instruct the terminal to measure and report the results for specific frequencies, cells, and beams through the RRCReconfiguration procedure. At this time, the specific configuration information that the base station transmits to the terminal through the RRCReconfiguration message can include at least some of the measurement target frequency, cell, beam (i.e., SSB or CSI-RS transmitted using a specific beam), measurement time configuration information, report type, Reference Signal type, report cycle, or report count, as described in step 521. In addition, in order for the base station to receive continuous beam measurement information required for learning a time-domain beam prediction model from the terminal, at least some of the following information can be additionally included in the RRCReconfiguration message.

[0079] -ReportInterval (with lower value): A new ReportInterval value that is equal to or smaller than the SMTC cycle (534) can be defined so that the terminal can perform SSB or CSI-RS measurements every SMTC cycle (534) and report all the obtained results to the base station. For example, the values ​​that can be set as the current SMTC cycle (5ms, 10ms, 20ms, 40ms, 80ms, 160ms) can be newly included in the ReportInterval configurable values. For this purpose, a new ReportInterval field and IE can be defined. However, in this case, the terminal sends the L3 MeasurementReport message more frequently, which may degrade the quality of other user data transmission. To avoid this problem, the base station can store (log) the results measured by the terminal every SMTC cycle and configure it to include multiple measurement results in the L3 measurementReport and report them. For this purpose, a Logging directive can be introduced.

[0080] -Logging indicator: A new indicator (e.g., Logging) can be defined to log all measurement results (e.g., SSB / CSI-RA Measurement #2, SSB / CSI-RA Measurement #3, ..., SSB / CSI-RA Measurement #k) between measurement reports (533, 539) so that the terminal can perform SSB or CSI-RS measurements every SMTC cycle (534) and report all obtained results to the base station, and then report them together in the subsequent measurement result report (539). If the base station sets the value of the indicator (Logging) to 'True', the terminal can log all measured results every SMTC cycle (534) and report all logged measurement results to the base station when MeasurementReport is transmitted every ReportInterval (537). After the terminal reports the logged measurement results to the base station, the already reported result values ​​can be erased from the memory and new measurement results can be logged again.

[0081] -LoggingInterval: If the above Logging indicator is set, the base station can set a separate loggingInterval. If LoggingInterval is set, the terminal can log the most recently measured result value at the LoggingInterval cycle. If LoggingInterval is not set, the terminal can perform logging at the SMTC cycle (534).

[0082] -L1 Measurement Indication: If the base station needs to report L1 measurement results (e.g., L1 RSRP / RSRQ / SINR) rather than L3 measurement results filtered in the time domain for beam prediction model training, the base station may include a 1-bit indicator in the RRCReconfiguration message to instruct the UE to report the L1 measurement results. If the base station instructs the UE to report the L1 measurement results through the 1-bit indicator, the UE may include the L1 measurement results rather than the L3 measurement results in the L3 MeasurementReport at step 539 below. (Or, the L1 measurement results may be included in addition to the L3 measurement results.)

[0083] In step 539, the terminal can report to the base station multiple measurement result values ​​that have been logged in the MeasurementReport. At this time, each measurement result can include an L1 or L3 RSRP / RSRQ / SINR value calculated by measuring SSB or CSI-RS transmitted through each beam at a specific point in time. More specifically, each measurement result can include a list of SSB and CSI-RS indices measured at a specific point in time and an L1 or L3 RSRP / RSRQ / SINR measurement result corresponding to each index. When the MeasurementReport includes multiple measurement result values ​​that have been logged at multiple points in time, the terminal can report only the difference (difference in value) between the result value logged at the previous point in time and the result value logged at the next point in time for the corresponding index instead of reporting the absolute value of the L1 or L3 RSRP / RSRQ / SINR measurement value corresponding to each index in order to reduce signaling load. Alternatively, instead of reporting the absolute value of the L1 or L3 RSRP / RSRQ / SINR measurement value corresponding to each SSB / CSI-RS index, the terminal can reduce the signaling load by dividing the range of representable values ​​into several zones, defining each zone and its corresponding index values ​​in a table format, and reporting only the index corresponding to the RSRP / RSRQ / SINR measurement value. In addition, if the MeasurementReport includes multiple measurement result values ​​logged at multiple points in time, the terminal can include time information for the time at which the corresponding result value was logged (in other words, the time at which each measurement was performed) for each measurement result. In addition, the terminal can report the following auxiliary information to the base station to help train the beam prediction model. A request for reporting the following auxiliary information can be performed by the RRCReconfiguration procedure in step 531.

[0084] - Tx and / or Rx beam shape information: Tx / Rx beam pattern information, Tx / Rx beam boresight direction (azimuth and elevation), 3dB beamwidth, etc.

[0085] - UE position information: User location information

[0086] - UE direction / orientation information: User direction information

[0087] - Tx beam usage information: Tx beam usage information

[0088] In connection with the improved operation flow (530) according to one embodiment of the present disclosure, a UE Capability Information parameter may be newly defined. The new UE Capability Information parameter may indicate whether the UE understands the new configuration information included in step 531 (e.g., ReportInterval (with lower value), Logging indicator, L1 measurement indication) and can perform the operations indicated according to the corresponding configuration. A separate UE Capability Information parameter may be defined for each configuration information and its corresponding operation, or a UE Capability Information parameter may be defined for each combination of one or more configurations and operations. The process of exchanging UE Capability Information between the base station and the UE may precede the signaling procedure.

[0089] FIG. 6 is a flowchart of a process in which a base station instructs an RRC_CONNECTED state terminal to measure all beams or a specific beam combination and reports the results in order to learn a model for predicting beam information in a spatial domain, according to one embodiment of the present disclosure.

[0090] Referring to FIG. 6, the base station can learn a model for predicting beam information in the spatial domain based on the entire beam measurement information measured at a specific time (e.g., measurement results for the entire DL transmission beam operated by the base station) (610). In other words, in order to learn a model for predicting beam information in the spatial domain, the base station may require the entire beam measurement information (610) measured at a specific time.

[0091] To this end, the base station can instruct the terminal in the RRC_CONNECTED state to report the L1 or L3 beam measurement results (more specifically, the L1 or L3 RSRP / RSRQ / SINR values ​​calculated by measuring SSB or CSI-RS transmitted through a specific beam) through RRC signaling. The basic operation flow (620) between the base station and the terminal for this purpose is as follows.

[0092] In step 621, the base station can instruct the terminal to measure and report results for specific frequencies, cells, and beams through the RRCReconfiguration procedure. More specifically, the base station can instruct the terminal on the target frequency, cell, and beam (i.e., the SSB or CSI-RS transmitted using a specific beam) through the RRCReconfiguration message. The specific configuration information included in the RRCReconfiguration message is as follows.

[0093] - ReferenceSignalConfig: Information on DL reference signals (SSB and CSI-RS transmitted using a specific beam) for beam measurement. The base station can indicate the DL reference signals that the terminal should measure for beam measurement by including ReferenceSignalConfig information in the RRCReconfiguration message.

[0094] - reportQuantityRS-Indexes: Information that indicates which values ​​should be reported for each RS (Reference Signal) index transmitted using a specific beam when the terminal reports beam measurement results. The base station can instruct reporting for each value of RSRP, RSRQ, and SINR through the reportQuantityRS-Indexes value.

[0095] - maxNrofRS-IndexesToReport: Information indicating the maximum number of RS indexes that the terminal can report for each RS type (SSB or CSI-RS) when reporting beam measurement results.

[0096] - absThreshSS-BlocksConsolidation / absThreshCSI-RS-Consolidation: Information to instruct the UE to include the results of the beam only if the sorting quantity (one of RSRP, RSRQ, and SINR) of each measured beam is greater than or equal to the absThreshSS-BlocksConsolidation or absThreshCSI-RS-Consolidation value for each RS type (SSB or CSI-RS) when reporting the beam measurement results. Note that the absThreshSS-BlocksConsolidation and absThreshCSI-RS-Consolidation values ​​can be set in dBm units. The sorting quantity can be the value indicated in reportQuantityRS-Indexes (e.g., RSRP, RSRQ, SINR) if there is only one value. If there are multiple values ​​indicated in reportQuantityRS-Indexes, the RSRP, RSRQ, and SINR values ​​can be set as the sorting quantity in that order.

[0097] Additionally, the base station can include measurement time configuration information (SMTC, SSB Measurement Timing Configuration) in the RRCReconfiguration message to indicate when the terminal should measure the SSB or CSI-RS transmitted using a specific beam. Furthermore, the base station can indicate the report type (reportType: periodical or eventTriggered) and the Reference Signal type (rsType: SSB or CSI-RS) for which the measurement result should be reported through the RRCReconfiguration message. At this time, the report cycle (ReportInterval) and report count (reportAmount) values ​​can be additionally set.

[0098] In step 622, the terminal can measure SSB and CSI-RS according to the beam measurement and result reporting settings provided by the base station in step 621. More specifically, the terminal can measure the values ​​indicated by reportQuantityRS-Indexes (RSRP, RSRQ, SINR) for the RSs included in the ReferenceSignalConfig set by the base station in step 621. If the result reporting type is set to periodical, the terminal can perform the first measurement and report the result to the base station by including it in MeasurementReport (623). Meanwhile, if the result reporting type is set to 'eventTriggered', the terminal can measure SSB and CSI-RS at every SMTC cycle and check whether the set event occurrence condition is satisfied. If the event occurrence condition is satisfied, the transmission of the MeasurementReport message (623) can be started.

[0099] In step 623, the terminal can report to the base station the beam results measured according to the base station settings in step 621 by including them in the measurementReport. The terminal can include in the measurementReport (123) the index of the best beam for each RS type (SSB and CSI-RS) among the beam results measured in step 622 (in other words, the index of the RS transmitted with the best beam). In addition, if the base station sets the maxNrofRS-IndexesToReport value and the absThreshSS-BlocksConsolidation / absThreshCSI-RS-Consolidation value in step 621, the base station can include additional beam measurement results in the measurementReport (623). At this time, beam measurement results up to maxNrofRS-IndexesToReport(628) for each RS type (SSB and CSI-RS) can be included in measurementReport(623), and among the beams measured in step 622, only the result values ​​for beams whose sorting quantity value is greater than or equal to absThreshSS-BlocksConsolidation or absThreshCSI-RS-Consolidation (627) can be included in measurementReport(623) in descending order of sorting quanity.

[0100] In the case where the base station instructs the terminal to perform beam measurement and reports the result value as in the basic operation flow example (620), only the beam results that satisfy the conditions set by the base station among the entire beam results measured by the actual terminal in the spatial domain can be reported to the base station (629). However, the base station can learn the spatial domain beam prediction model based on the entire beam measurement information measured by the actual terminal at a specific point in time. Therefore, the beam measurement and reporting operation basic flow (620) can be improved as in the operation flow (630) so that the base station can receive the entire beam measurement information necessary for learning the spatial domain beam prediction model from the terminal. In other words, the base station according to one embodiment of the present disclosure can receive the entire beam measurement information necessary for learning the spatial domain beam prediction model from the terminal based on the operation flow (630).

[0101] In step 631, the base station can instruct the terminal to measure and report results for specific frequencies, cells, and beams through the RRCReconfiguration procedure. At this time, the specific configuration information that the base station transmits to the terminal through the RRCReconfiguration message is as described in step 621. In addition, at least some of the following information may be additionally included in the RRCReconfiguration message so that the base station can receive continuous beam measurement information required for learning a time-domain beam prediction model from the terminal.

[0102] -reportAll indicator: The base station can instruct the UE to always report measurement results for all DL RSs included in ReferenceSignalConfig, regardless of whether maxNrofRS-IndexesToReport and absThreshSS-BlocksConsolidation / absThreshCSI-RS-Consolidation are set. For this purpose, a new indicator (e.g., reportAll) can be introduced. The UE can perform measurements for all DL RSs included in ReferenceSignalConfig and include the results in measurementReport (633), regardless of whether maxNrofRS-IndexesToReport and absThreshSS-BlocksConsolidation / absThreshCSI-RS-Consolidation are set, if the reportAll indicator is set to 'True' in the RRCReconfiguration message (631) received from the base station.

[0103] -indexesToReportList: The base station can instruct the UE to report measurement results for some of all DL RSs included in ReferenceSignalConfig, regardless of whether maxNrofRS-IndexesToReport and absThreshSS-BlocksConsolidation / absThreshCSI-RS-Consolidation are set. For this purpose, a new field (e.g., indexesToReportList) can be introduced. If indexesToReportList is set in the RRCReconfiguration message (131) received from the base station, the UE can report the result values ​​for all DL RSs indicated by indexesToReportList by including them in the measurementReport (633), regardless of whether maxNrofRS-IndexesToReport and absThreshSS-BlocksConsolidation / absThreshCSI-RS-Consolidation are set.

[0104] -L1 Measurement Indication: If the base station needs to report L1 measurement results (e.g., L1 RSRP / RSRQ / SINR) rather than L3 measurement results filtered in the time domain for beam prediction model learning, the base station may include a 1-bit indicator in the RRCReconfiguration message to instruct the UE to report the L1 measurement results. If the base station instructs the UE to report the L1 measurement results through the 1-bit indicator, the UE may include the L1 measurement results rather than the L3 measurement results in the L3 MeasurementReport at step 633, or may include the L1 measurement results together with the L3 measurement results.

[0105] In step 633, the terminal may include multiple beam measurement result values ​​in the MeasurementReport and report them to the base station according to the base station configuration in step 631. At this time, each measurement result may include an L1 or L3 RSRP / RSRQ / SINR value calculated by measuring SSB or CSI-RS transmitted through each beam at a specific point in time. More specifically, each measurement result may include a list of SSB and CSI-RS indices measured at a specific point in time and an L1 or L3 RSRP / RSRQ / SINR measurement result corresponding to each index. When the MeasurementReport includes multiple beam measurement result values, the terminal may report only the difference (difference in value) between the measurement value for a reference index and the measurement value for each index instead of reporting the absolute value of the L1 or L3 RSRP / RSRQ / SINR measurement value corresponding to each index in order to reduce signaling load. Alternatively, instead of reporting the absolute value of the L1 or L3 RSRP / RSRQ / SINR measurement value corresponding to each SSB / CSI-RS index, the range of representable values ​​can be divided into several zones, and then each zone and its corresponding index values ​​can be defined in a table format so that the terminal only reports the index corresponding to the RSRP / RSRQ / SINR measurement value, thereby reducing the signaling load.

[0106] In connection with the improved operation flow (630) according to one embodiment of the present disclosure, a new UE Capability Information parameter may be defined. The new UE Capability Information parameter may indicate whether the UE understands the new configuration information included in step 631 (e.g., reportAll directive, indexesToReportList, L1 measurement indication) and can perform the operations indicated according to the corresponding configuration. A separate UE Capability Information parameter may be defined for each configuration information and its corresponding operation, or a UE Capability Information parameter may be defined for each combination of one or more configurations and operations. The process of exchanging UE Capability Information between the base station and the UE may precede the signaling procedure.

[0107] FIG. 7 is a flowchart of a process in which a base station instructs a terminal to measure a beam in an RRC_IDLE / RRC_INACTIVE state and reports the result in order to learn a model for predicting beam information in a spatial domain or a time domain, according to one embodiment of the present disclosure.

[0108] Referring to FIG. 7, the base station can be configured (710) to perform cell and beam measurements and log the results when a terminal in an RRC_CONNECTED state transitions to an RRC_IDLE or RRC_INACTIVE state. The terminal can perform cell and beam measurements and log the results according to the base station settings after transitioning to the RRC_IDLE or RRC_INACTIVE state. Thereafter, when the terminal transitions to the RRC_CONNTECTED state, the base station requests the terminal to report the measurement results logged in the RRC_IDLE or RRC_INACTIVE state, and the terminal can report the cell and beam measurement results to the base station according to the base station request. The specific signaling procedures and operations between the base station and the terminal for the operation are as follows.

[0109] In step 710, the base station may instruct the terminal to perform measurements on cells and beams and log the results when the terminal later transitions to the RRC_IDLE or RRC_INACTIVE state by transmitting a LoggedMeasurementConfiguration message (710). At this time, the LoggedMeasurementConfiguration message may include at least some of the following information.

[0110] -LoggingDuration: This refers to the period during which the LoggedMeasurementConfiguration message configuration information is valid. When the terminal receives the LoggedMeasurementConfiguration message from the base station, the terminal can start the T330 timer and set the timer value to the LoggingDuration value. After the T330 timer expires, as in step 719, the terminal can release all LoggedMeasurementConfiguration message configuration information. In addition, after a certain period of time (e.g., 24 hours) has passed since the T330 timer expired, the terminal can delete the logged measurement results.

[0111] -loggingInterval: This refers to the time interval at which the terminal performs measurements on cells or beams in RRC_IDLE or RRC_INACTIVE mode and periodically logs the results. When the terminal receives a LoggedMeasurementConfiguration message from the base station, it can perform logging operations at a periodic rate (Interval or Period) based on the loggingInterval value included in the message.

[0112] -areaConfiguration: Indicates the range of the area where the terminal will perform measurements on cells or beams in RRC_IDLE or RRC_INACTIVE mode. The base station can indicate the range of the area where the terminal will perform measurements (i.e., areaConfiguration) in the form of a list of CellGlobalIDs, a list of TrackingAreaCode, or a list of TrackingAreaIndentities. Additionally, the base station can indicate the neighboring frequencies and cells where the terminal will perform measurements within the area where the terminal will perform measurements by including InterFreqTargetList information in the areaConfiguration information.

[0113] -plmn-IdentityList: Indicates the Public Land Mobile Networks (PLMNs) for which the UE will perform measurements on cells or beams in RRC_IDLE or RRC_INACTIVE mode. The base station can instruct the UE to perform measurements and logging only for the indicated PLMNs by including the plmn-IdentityList in the LoggedMeasurementConfiguration message. In other words, the base station can instruct the UE to perform measurements and logging only if the UE's current Registered Public Land Mobile Network (RPLMN) is included in the plmn-IdentityList.

[0114] -absoluteTimeInfo: Indicates the absolute time value in the cell at the time the base station transmits the LoggedMeasurementConfiguration message.

[0115] In step 713, the base station can cause the terminal to transition from the RRC_CONNECTED state to the RRC_IDLE or RRC_INACTIVE state by transmitting an RRCRelease message to the terminal. At this time, the terminal can start measurement and logging operations according to the base station settings in step 710 while transitioning to the RRC_IDLE or RRC_INACTIVE state.

[0116] In step 715, the terminal can perform measurement and logging operations at a loggingInterval cycle according to the base station configuration in step 710. More specifically, the terminal can perform logging at a loggingInterval cycle in the cell selection state (i.e., the state in which the terminal is searching for a cell to camp on). In addition, the terminal can perform logging if the current RPLMN is included in the preset plmn-IdentityList in the camped normally state (i.e., the state in which the terminal is camped on an NR cell). However, if the areaConfiguration is configured together with the LoggedMeasurementConfiguration in step 710, the terminal can perform logging only if the current cell belongs to the area configured by the areaConfiguration.

[0117] When the terminal performs measurement and logging operations in RRC_IDLE or RRC_INACTIVE state as in step 717 and the terminal's memory becomes full, the terminal can stop the T330 timer and release all LoggedMeasurementConfiguration message configuration information. In addition, the terminal can delete the logged measurement results after a certain period of time (e.g., 24 hours) has elapsed from the time the T330 timer was stopped.

[0118] When the T330 timer expires, as in step 719, the terminal may release all LoggedMeasurementConfiguration message configuration information. Furthermore, after a certain amount of time (e.g., 24 hours) has elapsed since the T330 timer expired, the terminal may delete logged measurement results.

[0119] In step 720, the terminal can transition back to the RRC_CONNECTED state through the RRC Setup or RRC Resume procedure. At this time, the terminal can stop the measurement and logging operations performed in the RRC_IDLE or RRC_INACTIVE state according to the LoggedMeasurementConfiguration setting in step 710. In addition, the terminal can report to the base station that it has acquired the measurement and logging results in the RRC_IDLE or RRC_INACTIVE state by including the logMeasAvailable indicator in the RRCSetupComplete and RRCResumeComplete messages in the RRC Setup and RRC Resume procedures, respectively. In addition, the terminal can report to the base station that it has the measurement and logging results in the RRC_IDLE or RRC_INACTIVE state by including the logMeasAvailable indicator in the RRCReconfigurationComplete and RRCReestablishmentComplete messages in the RRC Reconfiguration and RRC Reestablishment procedures, respectively.

[0120] In step 723, the base station can instruct the terminal to report the logged measurement results by including the logMeasReportReq indicator in the UEInformationRequest message transmitted to the terminal.

[0121] In step 725, the terminal may transmit the logged measurement results (i.e., the results measured and logged in RRC_IDLE or RRC_INACTIVE state in step 715) to the base station in the form of logMeasReport information in a UEInformationResponse message according to the instructions of the base station in step 123. The logMeasReport may include a LogMeasInfoList (730) composed of multiple LogMeasInfos logged at multiple points in time. Each LogMeasInfo may include the logging results for the serving cell (733, measResultServingCell) and the logging results for the neighboring cell (735, MeasResultNeighborCell). The logging result for the serving cell may include cell measurement results based on multiple SSB measurements for the cell, and may include the best SSB index (i.e., the index information of the SSB transmitted on the best beam and having the best signal strength, best-ssb-Index) and the measurement results associated with it (i.e., the L3 RSRP, RSRQ, SINR values ​​obtained by measuring the corresponding SSB) for the beam. The logging result for the neighbor cell may include cell measurement results based on multiple SSB measurements for the cell, and may not include information related to the beam.

[0122] As described above, the basic (typical or conventional) LogMeasInfo (730) can only include measurement results for one optimal SSB index for a serving cell with respect to beams and cannot include any beam information for neighbor cells. Therefore, the conventional measurement and logging operations in RRC_IDLE and RRC_INACTIVE states may be difficult to use to collect data for learning a beam prediction model in the time domain or space domain. For reference, in order for the base station to learn a beam prediction model in the time domain and / or space domain, continuous full beam measurement results in the time space may be required, as shown in FIGS. 5 and 6. In addition, the base station can collect beam-related measurement information by instructing beam measurement and logging to terminals in RRC_IDLE or RRC_INACTIVE states in order to obtain data for learning a beam prediction model from arbitrary terminals in various states. To this end, the operations of steps 710 (loggedMeasurementConfiguration) and 725 (UEInformationResponse) during the process of instructing the above-described terminal to measure a beam in the RRC_IDLE / RRC_INACTIVE state and reporting the result can be improved as follows.

[0123] In step 710, the base station may instruct the terminal to additionally measure and log beam-related information when performing measurements and logging in the RRC_IDLE or RRC_INACTIVE state. To this end, at least some of the following information may be newly defined and included in the LoggedMeasurementConfiguration message.

[0124] - BeamMeasurementIndicator: A 1-bit indicator can be defined to instruct the terminal to also measure and log beam-related information when performing measurement and logging in RRC_IDLE or RRC_INACTIVE state. When the base station needs to secure data for beam prediction model learning, the base station can include the 1-bit indicator in the loggedMeasurementConfiguration message to instruct the terminal to perform beam measurement and logging operations in RRC_IDLE or RRC_INACTIVE state. When the 1-bit indicator is included (set) in the loggedMeasurementConfiguration message, the terminal can perform beam measurement and logging in RRC_IDLE or RRC_INACTIVE state and report multiple SSB indices and corresponding measurement result values ​​to the base station for each of the serving cell and neighbor cell as in step 125.

[0125] - reportQuantity: The base station can instruct which values ​​to log as beam measurement results when the terminal performs beam measurement and logging operations in RRC_IDLE or RRC_INACTIVE state. For this purpose, new information (e.g., reportQuantity) can be defined to instruct a combination of at least one of RSRP, RSRQ, and SINR. If the base station needs to secure data for beam prediction model learning, it can instruct the terminal to perform beam measurement and logging operations in RRC_IDLE or RRC_INACTIVE state. At this time, the type of measurement result value to be logged as beam measurement result can be instructed by including reportQuantity information in the loggedMeasurementConfiguration message and setting its value appropriately. The terminal can log the result values ​​requested by the base station after beam measurement in RRC_IDLE or RRC_INACTIVE state based on the reportQuantity information included in the loggedMeasurementConfiguration message.

[0126] - reportAll indicator: When the terminal performs beam measurement and logging operations in RRC_IDLE or RRC_INACTIVE state, the base station can instruct the terminal to perform measurement and logging for all beams transmitted by the serving cell and neighbor cells (i.e., all SSB indices). For this purpose, a new indicator (e.g., reportAll) can be introduced. If the reportAll indicator in (710) of the loggedMeasurementConfiguration message received from the base station is set to 'True', the terminal can perform measurement for all beams transmitted by the serving cell and neighbor cells (i.e., all SSB indices) and log the results.

[0127] - indexesToReportList: When the terminal performs beam measurement and logging operations in RRC_IDLE or RRC_INACTIVE state, the base station can instruct the terminal to report measurement results for some of all beams (i.e., all SSB indexes) transmitted by the serving cell and neighbor cells. For this purpose, a new field (e.g., indexesToReportList) can be introduced. If indexesToReportList is set in the loggedMeasurementConfiguration message (710) received from the base station, the terminal can perform measurements for all SSBs indicated through indexesToReportList and log the results.

[0128] - L1 Measurement Indication: If the base station needs to report L1 measurement results (e.g., L1 RSRP / RSRQ / SINR) rather than time-domain filtered L3 measurement results for beam prediction model training, the base station may include a 1-bit indicator in the loggedMeasurementConfiguration message to instruct the terminal to report L1 measurement results. If the base station instructs the terminal to report L1 measurement results through the 1-bit indicator, the terminal may log the L1 measurement results rather than the L3 measurement results after performing beam measurements. (Or, the L1 measurement results may be logged in addition to the L3 measurement results.)

[0129] - maxNrofIndexesToReport: Information indicating the maximum number of SSB indexes that the terminal can report when reporting beam measurement results. The base station can indicate the maximum number of SSB indexes that the terminal can report for each cell when performing beam measurement and logging operations in RRC_IDLE or RRC_INACTIVE state. For this purpose, a new field (e.g., maxNrofIndexesToReport) can be introduced. If maxNrofIndexesToReport is set in the loggedMeasurementConfiguration message (710) received from the base station, the terminal can log the results for SSB indexes for each cell as many as indicated by maxNrofIndexesToReport.

[0130] In step 725, if beam-related measurement and logging configuration information is included in the loggedMeasurementConfiguration message received from the base station in step 710, the terminal may report the beam-related measurement and logging results to the base station through the UEInformationResponse message (725) according to the base station's instructions. To this end, the logMeasReport information included in the UEInformationResponse message (725) may include multiple beam measurement information for a serving cell and a neighbor cell. More specifically, a resultsSSB-measList including beam measurement results for multiple SSB indexes transmitted by the serving cell may be newly defined in the measurement result information (733) for the serving cell included in the logMeasReport. The terminal may include multiple measured SSB indexes and corresponding measurement results (ssb-Results) in the resultsSSB-measList according to the beam-related measurement configuration (or instructions) provided by the base station in step 710. Additionally, a new resultsSSB-measList may be defined in the measurement result information (735) for the neighbor cell included in the logMeasReport, which includes beam measurement results for multiple SSB indexes transmitted by the neighbor cell. The terminal may include multiple SSB indexes measured for each neighbor cell and corresponding measurement results (ssb-Results) in the resultsSSB-measList according to the beam-related measurement settings (or instructions) provided by the base station in step 710.

[0131] In connection with the improved operation according to one embodiment of the present disclosure, a new UE Capability Information parameter may be defined. The new UE Capability Information parameter may indicate whether the UE understands the new configuration information included in step 710 (e.g., BeamMeasurementIndicator, reportQuantity, reportAll indicator, indexesToReportList, L1 measurement Indication, maxNrofIndexesToReport) and can perform the operations indicated according to the corresponding configuration. A separate UE Capability Information parameter may be defined for each configuration information and its corresponding operation, or a UE Capability Information parameter may be defined for each combination of one or more configurations and operations. The process of exchanging UE Capability Information between the base station and the UE may precede the signaling procedure.

[0132] FIG. 8 is a flowchart of a process in which a base station instructs a terminal to continue beam measurement and reports the result even after the terminal transitions from an RRC_IDLE / RRC_INACTIVE state to an RRC_CONNECTED state in order to learn a model for predicting beam information in the time domain, according to one embodiment of the present disclosure.

[0133] Referring to FIG. 8, the base station can be configured to continuously perform measurements on cells and beams in the time domain, regardless of the state of the terminal, when the terminal is in the RRC_IDLE / RRC_INACTIVE state and the RRC_CONNECTED state, in order to learn a model for predicting beam information in the time domain. Thereafter, the base station can receive reports of the results of continuous measurements in the time domain from the terminal. The basic signaling procedure and operation (810) for this can be described as follows.

[0134] In step 812, the base station can instruct the terminal to perform measurements on cells and beams and log the results when the terminal later transitions to the RRC_IDLE or RRC_INACTIVE state by transmitting a LoggedMeasurementConfiguration message (812). At this time, the configuration information included in the LoggedMeasurementConfiguration message is as described for step 710 of the embodiment of FIG. 7.

[0135] In step 813, the base station can cause the terminal to transition from the RRC_CONNECTED state to the RRC_IDLE or RRC_INACTIVE state by transmitting an RRCRelease message to the terminal. At this time, the terminal can start measurement and logging operations according to the base station settings in step 812 at the same time as transitioning to the RRC_IDLE or RRC_INACTIVE state.

[0136] In section 814, the terminal can perform measurement and logging operations at a loggingInterval cycle according to the base station settings in step 812. A more specific description of the terminal measurement and logging operations is omitted as it is the same as that described for step 715 of the embodiment of FIG. 7 above.

[0137] In step 815, the terminal can transition back to the RRC_CONNECTED state through the RRC Setup or RRC Resume procedure. At this time, the terminal can stop the measurement and logging operations performed in the RRC_IDLE or RRC_INACTIVE state depending on the LoggedMeasurementConfiguration setting in step 812.

[0138] In section 816, the terminal may no longer perform beam measurements and logging operations previously performed in the RRC_IDLE or RRC_INACTIVE states. Therefore, beam-related measurement information, which was periodically logged in the time domain, cannot be collected in this section. This means that the base station has limitations in securing the data required for learning the time-domain beam prediction model (i.e., continuous beam measurement information in the time domain).

[0139] In step 817, the base station can instruct the terminal to measure and report results for specific frequencies, cells, and beams through the RRCReconfiguration procedure. More specifically, the base station can instruct the terminal on the frequency, cell, and beam to be measured (i.e., the SSB or CSI-RS transmitted using a specific beam) through the RRCReconfiguration message. A description of the specific configuration information included in the RRCReconfiguration message is omitted as it is the same as that described in step 621 of the embodiment of FIG. 6.

[0140] In section 818, the terminal can perform cell and beam measurements in the RRC_CONNECTED state according to the base station settings in step 817 and then report the measurement results to the base station via measurementReport.

[0141] According to the basic signaling procedure and operation described above, the terminal can perform beam measurement and logging operations during section 814 according to the configuration in the LoggedMeasurementConfiguration message received in step 812 in the RRC_INACTIVE and RRC_IDLE states. In addition, the terminal can perform beam measurement and reporting operations during section 818 according to the configuration in the RRCReconfiguration message received in step 817 in the RRC_CONNECTED state. However, the beam measurement and logging operations can be stopped during the section (816) from the time point (815) when the terminal transitions from the RRC_INACTIVE / RRC_IDLE state to the RRC_CONNECTED state until it receives beam measurement configuration information in the RRC_CONNECTED state through the RRCReconfiguration procedure (817). This may mean that there is a gap period in which the terminal does not perform beam measurements in the time domain, or that the base station has difficulty obtaining data (i.e., continuous beam measurement information in the time domain) from the terminal necessary for learning the time domain beam prediction model. To address this issue, the improved signaling procedure and operation (820) are as follows.

[0142] In step 822, the base station can instruct the terminal to perform cell and beam measurement and log the result value when the terminal transitions to the RRC_IDLE or RRC_INACTIVE state in the future by transmitting a LoggedMeasurementConfiguraion message (822). At this time, a new indicator (e.g., ContinousMeasIndicator) can be defined to instruct the terminal to continue performing the beam measurement and logging operation performed in the RRC_IDLE / RRC_INACTIVE state for a certain period of time even after transitioning to the RRC_CONNECTED state. If the base station needs continuous beam measurement information in the time domain to learn a beam prediction model in the time domain, the base station can set the indicator (ContinousMeasIndicator) value to 'true' in the LoggedMeasurementConfiguraion message. If the indicator (ContinousMeasIndicator) value is set to 'true' in the LoggedMeasurementConfiguraion message, the terminal can continue to perform beam measurement and logging operations performed in the RRC_IDLE / RRC_INACTIVE state even after transitioning to the RRC_CONNECTED state in step 124 below. Additionally, the terminal can set the T330 timer value as the logging duration and start it at the time of receiving the loggedMeasurementConfiguraion message.

[0143] In step 823, the base station can cause the terminal to transition from the RRC_CONNECTED state to the RRC_IDLE or RRC_INACTIVE state by transmitting an RRCRelease message to the terminal. At this time, the terminal can start measurement and logging operations according to the base station settings in step 822 while transitioning to the RRC_IDLE or RRC_INACTIVE state.

[0144] In step 824, the terminal can transition back to the RRC_CONNECTED state through the RRC Setup or RRC Resume procedure. At this time, the terminal can continue or stop beam measurement and logging operations even after transitioning to the RRC_CONNECTED state according to the configuration information in the LoggedMeasurementConfiguration in step 822. If the value of a new indicator (e.g., ContinousMeasIndicator) instructing to continue performing beam measurement and logging operations performed in the RRC_IDLE / RRC_INACTIVE state for a certain period of time even after transitioning to the RRC_CONNECTED state in the LoggedMeasurementConfiguration received by the terminal in step 822 is set to 'True', the terminal can continue performing beam measurement and logging operations even after transitioning to the RRC_CONNECTED state. However, when transitioning to the RRC_CONNTECTED state, the terminal can additionally determine whether the following conditions are satisfied and continue beam measurement and logging operations only if all of the conditions are satisfied.

[0145] - Condition 1: RPLMN must be included in plmn-IdentityList. Note that plmn-IdentityList here is a value set in the LoggedMeasurementConfiguration message (822) as described in step 710 of the embodiment of FIG. 7 and then stored in the VarLogMeasReport information within the terminal.

[0146] - Condition 2: If areaConfiguration is set in the LoggedMeasurementConfiguration message (822), the current primary cell or serving cell of the terminal must be included in the area indicated by areaConfig. On the other hand, if areaConfiguration is not set, condition 2 is satisfied. For reference, areaConfiguration here is a value set in the LoggedMeasurementConfiguration message (822) as described in step 710 of the embodiment of FIG. 7 and then stored in the internal VarLogMeasReport information of the terminal.

[0147] On the other hand, if the new indicator (e.g., ContinousMeasIndicator) is not included in the LoggedMeasurementConfiguration received by the terminal in step 822 (or is included but has a value of 'False'), the terminal may stop the beam measurement and logging operations being performed in the RRC_IDLE / RRC_INACTIVE state.

[0148] If the terminal continues to perform beam measurement and logging operations in the RRC_IDLE / RRC_INACTIVE state even after transitioning to the RRC_CONNECTED state in step 824, the terminal may stop beam measurement and logging operations in the following cases.

[0149] - Case 1 (825): When the base station transmits beam measurement and reporting configuration (e.g., MeasConfig) in the RRC_CONNECTED state to the terminal through the RRCReconfiguration procedure, the terminal can stop the beam measurement and logging operation performed by the LoggedMeasurementConfiguration message (822) configuration. Thereafter, the terminal can perform the beam measurement and reporting operation in the RRC_CONNECTED state according to the MeasConfig configuration included in the RRCReconfiguration message. In addition, the terminal can stop the T330 timer and release all LoggedMeasurementConfiguration message configuration information. In addition, the terminal can delete the logged measurement results after a certain period of time (e.g., 24 hours) has elapsed from that point.

[0150] - Case 2 (826): If the base station requests the terminal to report the measurement information logged in the RRC_IDLE / RRC_INACTIVE state through the UEInformationRequest message and the terminal reports the requested information through the UEInformationResponse message, the terminal may stop the beam measurement and logging operation performed by the LoggedMeasurementConfiguration message (822) configuration. Additionally, the terminal may stop the T330 timer and release all LoggedMeasurementConfiguration message configuration information. In addition, the terminal may delete the logged measurement results after a certain period of time (e.g., 24 hours) has elapsed from that point on.

[0151] - Case 3 (827): When the T330 timer expires, the terminal may stop the beam measurement and logging operation performed by the LoggedMeasurementConfiguration message (822) configuration. Additionally, the terminal may release all LoggedMeasurementConfiguration message configuration information. In addition, the terminal may delete the logged measurement results after a certain period of time (e.g., 24 hours) has elapsed since the T330 timer expired.

[0152] In addition, a new UE Capability Information parameter may be defined in relation to the improved operation. The new UE Capability Information parameter may indicate whether the UE understands the new configuration information included in step 822 (e.g., ContinousMeasIndicator) and can perform the operations indicated by the configuration. A separate UE Capability Information parameter may be defined for each configuration information and its corresponding operation, or a UE Capability Information parameter may be defined for each combination of one or more configurations and operations. The process of exchanging UE Capability Information between the base station and the UE may precede the signaling procedure.

[0153] FIG. 9 is a drawing illustrating a terminal device according to one embodiment of the present disclosure.

[0154] Referring to FIG. 9, the terminal may include an RF (Radio Frequency) processing unit (910), a baseband processing unit (920), a storage unit (930), and a control unit (940). The configuration of the terminal is not limited to the exemplary configuration illustrated in FIG. 9, and may include fewer or more configurations than the configuration illustrated in FIG. 9.

[0155] The RF processing unit (910) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. For example, the RF processing unit (910) can up-convert a baseband signal provided from the baseband processing unit (920) into an RF band signal and transmit it through an antenna, and can down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (910) can include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc., but is not limited to these examples. In FIG. 9, only one antenna is illustrated, but the terminal can be equipped with multiple antennas. In addition, the RF processing unit (910) can include multiple RF chains. Furthermore, the RF processing unit (910) can perform beamforming. For beamforming, the RF processing unit (910) can adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit (910) can perform MIMO and receive multiple layers when performing MIMO operations.

[0156] The baseband processing unit (920) can perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (920) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (920) can restore a reception bit stream by demodulating and decoding a baseband signal provided from the RF processing unit (910). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (920) can generate complex symbols by encoding and modulating a transmission bit stream, map the generated complex symbols to subcarriers, and then configure OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (920) divides the baseband signal provided from the RF processing unit (910) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform) operation, and then restores the received bit string through demodulation and decoding.

[0157] The baseband processing unit (920) and the RF processing unit (910) can transmit and receive signals as described above. Accordingly, the baseband processing unit (920) and the RF processing unit (910) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (920) and the RF processing unit (910) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (920) and the RF processing unit (910) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, different frequency bands may include super high frequency (SHF) (e.g., 2.NRHz, NRhz) bands and millimeter wave (mm wave) (e.g., 60GHz) bands. The terminal may transmit and receive signals with the gNB using the baseband processing unit (920) and the RF processing unit (910), and the signals may include control information and data.

[0158] The storage unit (930) can store data such as basic programs, application programs, and setting information for the operation of the terminal. For example, the storage unit (930) can store data information such as basic programs, application programs, and setting information for the operation of the terminal. In addition, the storage unit (930) can provide the stored data at the request of the control unit (940).

[0159] The storage unit (930) may be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (930) may be configured as a plurality of memories. According to one embodiment of the present disclosure, the storage unit (930) may store a program for performing a handover method according to the present disclosure.

[0160] The control unit (940) can control the overall operations of the terminal. For example, the control unit (940) can transmit and receive signals through the baseband processing unit (920) and the RF processing unit (910).

[0161] In addition, the control unit (940) can record and read data in the storage unit (930). For this purpose, the control unit (940) may include at least one processor. For example, the control unit (940) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. In addition, according to one embodiment of the present disclosure, the control unit (940) may include a multi-connection processing unit (942) configured to process a process that operates in a multi-connection mode. In addition, at least one component within the terminal may be implemented as a single chip.

[0162] FIG. 10 is a diagram illustrating a base station device according to one embodiment of the present disclosure.

[0163] The base station of Fig. 10 may be included in the aforementioned network.

[0164] As illustrated in FIG. 10, the base station may include an RF processing unit (1010), a baseband processing unit (1020), a backhaul communication unit (1030), a storage unit (1040), and a control unit (1050). The configuration of the base station is not limited to the exemplary configuration illustrated in FIG. 10, and the base station may include fewer or more configurations than the configuration illustrated in FIG. 10. The RF processing unit (1010) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. For example, the RF processing unit (1010) may up-convert a baseband signal provided from the baseband processing unit (1020) into an RF band signal and then transmit it through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1010) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. In FIG. 10, only one antenna is illustrated, but the RF processing unit (1010) may have multiple antennas. In addition, the RF processing unit (1010) may include multiple RF chains. Furthermore, the RF processing unit (1010) may perform beamforming. For beamforming, the RF processing unit (1010) may adjust the phase and magnitude of each signal transmitted and received through the multiple antennas or antenna elements. The RF processing unit (1010) may perform a downlink MIMO operation by transmitting one or more layers.

[0165] The baseband processing unit (1020) can perform a conversion function between a baseband signal and a bit stream according to a physical layer standard. For example, when transmitting data, the baseband processing unit (1020) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1020) can restore a reception bit stream by demodulating and decoding a baseband signal provided from the RF processing unit (1010). For example, in the case of following the OFDM method, when transmitting data, the baseband processing unit (1020) can generate complex symbols by encoding and modulating a transmission bit stream, map the generated complex symbols to subcarriers, and then configure OFDM symbols through an IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (1020) can divide the baseband signal provided from the RF processing unit (1010) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operation, and then restore the received bit string through demodulation and decoding. The baseband processing unit (1020) and the RF processing unit (1010) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1020) and the RF processing unit (1010) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit. The base station can transmit and receive signals with the terminal using the baseband processing unit (1020) and the RF processing unit (1010), and the signals may include control information and data.

[0166] The backhaul communication unit (1030) may provide an interface for communicating with other nodes within the network. For example, the backhaul communication unit (1030) may convert a bit stream transmitted from the primary base station to another node, such as an auxiliary base station or core network, into a physical signal, and may convert a physical signal received from another node into a bit stream.

[0167] The storage unit (1040) can store data such as basic programs, application programs, and setting information for the operation of the main base station. For example, the storage unit (1040) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, etc. In addition, the storage unit (1040) can store information that serves as a basis for determining whether to provide or terminate multiple connections to the terminals. In addition, the storage unit (1040) can provide the stored data according to a request from the control unit (1050). The storage unit (1040) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (1040) can be configured as a plurality of memories. According to one embodiment of the present disclosure, the storage unit (1040) can also store a program for performing a handover according to the present disclosure.

[0168] The control unit (1050) can control the overall operations of the base station. For example, the control unit (1050) can transmit and receive signals through the baseband processing unit (1020) and the RF processing unit (1010) or through the backhaul communication unit (1030). In addition, the control unit (1050) can record and read data in the storage unit (1040). For this purpose, the control unit (1050) can include at least one processor. In addition, according to one embodiment of the present disclosure, the control unit (1050) can include a multi-connection processing unit (1052) configured to process a process operating in a multi-connection mode.

[0169] FIG. 11 is a block diagram showing an example of a configuration of a terminal according to one embodiment of the present disclosure.

[0170] As illustrated in FIG. 11, the terminal of the present disclosure may include a control unit (control unit) (1130), a transceiver (1110), and a storage unit (memory) (1120). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the control unit (1130), the transceiver (1110), and the storage unit (1120) may be implemented in the form of a single chip. According to one embodiment, the transceiver (1110) of FIG. 11 may include a transmitter and a receiver. In addition, the control unit (1130) of FIG. 11 may include at least one processor or controller.

[0171] According to one embodiment, the control unit (1130) may control a series of processes that enable the terminal to operate according to the embodiments of the present disclosure described above. For example, according to the embodiments of the present disclosure, the components of the terminal may be controlled to perform a transmission and reception method of the terminal depending on whether the base station mode is the base station energy saving mode or the base station normal mode. There may be one or more control units (1130), and the control units (1130) may perform transmission and reception operations of the terminal in a wireless communication system that applies the carrier bundle of the present disclosure described above by executing a program stored in the storage unit (1120).

[0172] The transceiver (1110) can transmit and receive signals with a base station. The signals transmitted and received with the base station can include control information and data. The transceiver (1110) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts the frequency, etc. However, the transceiver (1110) is only one embodiment, and the components of the transceiver (1110) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1110) can receive a signal through a wireless channel and output it to the control unit (1130), and transmit a signal output from the control unit (1130) through the wireless channel.

[0173] According to one embodiment, the storage unit (1120) can store programs and data necessary for the operation of the terminal. In addition, the storage unit (1120) can store control information or data included in signals transmitted and received by the terminal. The storage unit (1120) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (1120) can be provided in multiple numbers. According to one embodiment, the storage unit (1120) can store a program for performing transmission and reception operations of the terminal depending on whether the base station mode of the embodiments of the present disclosure described above is a base station energy saving mode or a base station normal mode.

[0174] FIG. 12 is a block diagram showing an example of a configuration of a base station according to one embodiment of the present disclosure.

[0175] As illustrated in FIG. 12 , the base station of the present disclosure may include a control unit (control unit) (1230), a transceiver (1210), and a storage unit (memory) (1220). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the control unit (1230), the transceiver (1210), and the storage unit (1220) may be implemented in the form of a single chip. The control unit (1230) of FIG. 12 may include at least one processor or controller.

[0176] The control unit (1230) can control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. For example, the control unit (1230) can control the components of the base station to perform a method for scheduling a terminal according to whether the base station mode is the base station energy saving mode or the base station normal mode according to the embodiment of the present disclosure. There can be one or more control units (1230), and the control units (1230) can perform a method for scheduling a terminal according to whether the base station mode of the above-described present disclosure is the base station energy saving mode or the base station normal mode by executing a program stored in the storage unit (1220).

[0177] The transceiver (1210) can transmit and receive signals with the terminal. The signals transmitted and received with the terminal can include control information and data. The transceiver (1210) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies the received signal and down-converts the frequency, etc. However, the transceiver (1210) is only one embodiment, and the components of the transceiver (1210) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1210) can receive a signal through a wireless channel and output it to the control unit (1230), and transmit a signal output from the control unit (1230) through the wireless channel.

[0178] According to one embodiment, the storage unit (1220) can store programs and data required for the operation of the base station. In addition, the storage unit (1220) can store control information or data included in signals transmitted and received by the base station. The storage unit (1220) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (1220) can be provided in multiple numbers. According to one embodiment, the storage unit (1220) can store a program for performing a method for scheduling a terminal depending on whether the base station mode of the above-described embodiments of the present disclosure is a base station energy saving mode or a base station normal mode.

[0179] The methods according to the claims or embodiments described in the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0180] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the claims or embodiments of the present disclosure.

[0181] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0182] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0183] In this disclosure, the term "computer program product" or "computer-readable medium" is used to collectively refer to media such as memory, a hard disk installed in a hard disk drive, and signals. These "computer program products" or "computer-readable mediums" are components provided in a method for reporting terminal capabilities in a wireless communication system according to the present disclosure.

[0184] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory storage medium" simply means a tangible device that does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is permanently stored in the storage medium and cases where data is temporarily stored. For example, a "non-transitory storage medium" may include a buffer in which data is temporarily stored.

[0185] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., a downloadable app) may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0186] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0187] Meanwhile, the embodiments of the present disclosure disclosed in this disclosure and the drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modified examples based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined to operate a base station and a terminal. In addition, the embodiments of the present disclosure are applicable to other communication systems, and other modified examples based on the technical idea of ​​the embodiments may also be implemented. For example, the embodiments may be applied to LTE systems, 5G, NR systems, or 6G systems. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

Claims

1. A method performed by a terminal in a wireless communication system, wherein the method comprises: A step of receiving, from a base station, setting information related to beam management based on beam prediction; A step of performing measurements related to beam management based on beam prediction at multiple measurement points based on the above setting information; and A method comprising the step of transmitting, to the base station, a measurement report including the results of measurements performed at each of the plurality of measurement points.

2. In paragraph 1, A method according to claim 1, wherein the setting information includes at least one of information about a period during which the measurement is performed, information about a reporting period of the measurement report, information for instructing the terminal to log the results of the measurement, information about a period during which the logging is performed, or information for instructing the terminal to report the results of the measurement as a result value of layer 1 (L1) measurement.

3. In paragraph 2, A method wherein the information on the above reporting cycle is set to a value equal to or less than the cycle at which the above measurement is performed.

4. In paragraph 1, A method wherein the results of measurements performed at each of the above multiple measurement points each include measurement results for the entire beam and are used for training an artificial intelligence model for beam prediction.

5. A method performed by a base station in a wireless communication system, the method comprising: A step for receiving setting information related to beam management based on beam prediction as a terminal; and A method comprising: receiving, from the terminal, a measurement report including results of measurements related to beam management based on beam prediction performed at each of a plurality of measurement points based on the above setting information.

6. In paragraph 5, A method according to claim 1, wherein the setting information includes at least one of information about a period during which the measurement is performed, information about a reporting period of the measurement report, information for instructing the terminal to log the results of the measurement, information about a period during which the logging is performed, or information for instructing the terminal to report the results of the measurement as a result value of layer 1 (L1) measurement.

7. In paragraph 6, A method wherein the information on the above reporting cycle is set to a value equal to or less than the cycle at which the above measurement is performed.

8. In paragraph 5, A method wherein the results of measurements performed at each of the above multiple measurement points each include measurement results for the entire beam and are used for training an artificial intelligence model for beam prediction.

9. In a wireless communication system, the terminal, transceiver; and Including a controller connected to the above transceiver, The above controller, Receive configuration information related to beam management based on beam prediction from a base station, Based on the above setting information, measurements related to the beam management based on beam prediction are performed at multiple measurement points, respectively. A terminal configured to transmit, to the base station, a measurement report including the results of measurements performed at each of the plurality of measurement points.

10. In paragraph 9, A terminal, wherein the above configuration information includes at least one of information about a cycle in which the measurement is performed, information about a reporting cycle of the measurement report, information for instructing the terminal to log the results of the measurement, information about a cycle in which the logging is performed, or information for instructing the terminal to report the results of the measurement as a result value of layer 1 (L1) measurement.

11. In clause 10, Information about the above reporting cycle is set to a value equal to or less than the cycle at which the above measurement is performed.

12. In paragraph 9, The results of the measurements performed at each of the above multiple measurement points, each of which includes a measurement result for the entire beam, are used for training an artificial intelligence model for beam prediction.

13. In a wireless communication system, at a base station, the base station, transceiver; and Including a controller connected to the above transceiver, The above controller, Receives configuration information related to beam management based on beam prediction as a terminal, A base station configured to receive, from the terminal, a measurement report including results of measurements related to beam management based on beam prediction performed at each of a plurality of measurement points based on the above setting information.

14. In paragraph 13, A base station, wherein the above configuration information includes at least one of information about a cycle in which the measurement is performed, information about a reporting cycle of the measurement report, information for instructing the terminal to log the results of the measurement, information about a cycle in which the logging is performed, or information for instructing the terminal to report the results of the measurement as a result value of layer 1 (L1) measurement.

15. In paragraph 14, The base station, which sets the information on the above reporting cycle to a value equal to or less than the cycle at which the above measurement is performed.

Images