Method and apparatus for controlling measurement event prediction operation in wireless communication system
AI and ML-based methods for predicting measurement events in wireless communication systems address inefficiencies in high-frequency bands, improving handover performance and reducing measurement burdens.
Patent Information
- Application Number
- PCT/KR2026/005804
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-06-27
- Filing Date
- 2026-05-04
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in efficiently managing measurement events, particularly in high-frequency bands, leading to potential handover failures and increased measurement overhead due to delays and inefficiencies in predicting cell changes.
Implementing artificial intelligence and machine learning-based methods for predicting measurement events, allowing terminals and base stations to anticipate and adjust to changes in cell measurements, thereby reducing handover failures and measurement burdens.
Enhances handover performance and reduces measurement overhead by accurately predicting cell changes, ensuring timely adjustments and optimizing resource utilization in wireless communication systems.
Smart Images

Figure KR2026005804_12112026_PF_FP_ABST
Abstract
Description
Method and apparatus for controlling measurement event prediction operation in a wireless communication system
[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. More specifically, the present disclosure relates to a method and apparatus for controlling a measurement event prediction operation.
[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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.
[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and Massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacing) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.
[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands that meets various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.
[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.
[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.
[0008] Based on the discussion described above, the present disclosure provides an apparatus and method capable of effectively providing services in a next-generation wireless communication system.
[0009] The technical problems to be solved in the embodiments of the present disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.
[0010] The present disclosure, for solving the above-mentioned problems, proposes a method performed by a terminal in a wireless communication system. More specifically, the method is characterized by comprising the steps of: receiving event prediction setting information from a base station; predicting the occurrence of a measurement event through artificial intelligence and machine learning based on the event prediction setting information; the prediction of the occurrence of the measurement event corresponds to either a direct method or an indirect method; and transmitting information related to the prediction of the occurrence of the measurement event to the base station.
[0011] The present disclosure, for solving the above-mentioned problems, proposes a method performed by a base station in a wireless communication system. More specifically, the method comprises the steps of transmitting event prediction setting information to a terminal and receiving information related to the prediction of the occurrence of a measurement event from the terminal, wherein the occurrence of the measurement event is predicted through artificial intelligence and machine learning based on the event prediction setting information, and the prediction of the occurrence of the measurement event corresponds to either a direct method or an indirect method.
[0012] The present disclosure, for solving the above-mentioned problems, proposes a terminal in a wireless communication system. More specifically, the terminal comprises: a transceiver for transmitting and receiving signals; and a control unit connected to the transceiver. The control unit receives event prediction setting information from a base station and, based on the event prediction setting information, predicts the occurrence of a measurement event through artificial intelligence and machine learning. The prediction of the occurrence of the measurement event corresponds to either a direct method or an indirect method. The terminal is characterized by transmitting information related to the prediction of the occurrence of the measurement event to the base station.
[0013] The present disclosure, for solving the above-mentioned problems, proposes a base station in a wireless communication system. More specifically, the base station comprises: a transceiver for transmitting and receiving signals; and a control unit connected to the transceiver. The control unit transmits event prediction setting information to a terminal and receives information related to the prediction of a measurement event occurrence from the terminal. The occurrence of the measurement event is predicted through artificial intelligence and machine learning based on the event prediction setting information. The prediction of the measurement event occurrence corresponds to either a direct method or an indirect method.
[0014] The present disclosure provides an apparatus and method capable of effectively providing services in a next-generation wireless communication system.
[0015] The effects obtainable in the present disclosure are not limited to those mentioned in the various embodiments, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure pertains from the description below.
[0016] FIG. 1a is a drawing illustrating the structure of a New Radio (NR) system according to one embodiment of the present disclosure.
[0017] FIG. 1b is a diagram showing a wireless protocol structure in a Long Term Evolution (LTE) and New Radio (NR) system according to one embodiment of the present disclosure.
[0018] FIG. 1c is a drawing illustrating a use case utilizing an Artificial Intelligence (AI) and / or Machine Learning (ML) model for predicting cell measurement results in a next-generation mobile communication system according to one embodiment of the present disclosure.
[0019] FIG. 1d is a diagram illustrating a method of utilizing Artificial Intelligence (AI) and / or Machine Learning (ML) models for predicting measurement events in a next-generation mobile communication system according to one embodiment of the present disclosure.
[0020] FIG. 1e is a diagram illustrating a specific method for a terminal to predict a measurement event using an Artificial Intelligence (AI) and / or Machine Learning (ML)-based cell measurement result prediction value according to one embodiment of the present disclosure.
[0021] FIG. 1f is a flowchart of a process in which a base station instructs a terminal to predict a measurement event and the terminal reports the prediction of a measurement event, according to one embodiment of the present disclosure.
[0022] FIG. 1g is a drawing illustrating a specific method in which a terminal performs a measurement event prediction operation according to one embodiment of the present disclosure.
[0023] FIG. 2 is a block diagram of a terminal or user device (User Equipment, UE) according to one embodiment of the present disclosure.
[0024] FIG. 3 is a block diagram of a base station according to one embodiment of the present disclosure.
[0025] FIG. 4 is a block diagram of a network entity performing network functions according to one embodiment of the present disclosure.
[0026] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0027] In describing the embodiments, technical details that are well known in the technical field to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0028] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.
[0029] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely 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. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.
[0030] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).
[0031] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.
[0032] As used in embodiments of the present disclosure, the term “part” refers to a software or hardware component, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part” performs certain roles. However, the term including “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, 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.” In addition, the components and 'parts' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Furthermore, in the embodiment, the 'part' may include one or more processors.
[0033] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.
[0034] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.
[0035] In addition, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0036] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.
[0037] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing a device or method according to any one of the claims of this specification, and a non-transient machine-readable storage medium storing such program.
[0038] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.
[0039] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0040] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.
[0041] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.
[0042] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0043] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0044] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.
[0045] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.
[0046] Furthermore, throughout this specification, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or essentially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same magnitude measured or applied in different situations, or may represent different magnitudes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the specification and claims.
[0047] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.
[0048] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.
[0049] Furthermore, the expressions 'if' and 'in case that' described in this disclosure or claims may be interpreted, depending on the context, as meaning 'when or upon,' 'in response to,' 'based on,' or 'according to,' and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.
[0050] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.
[0051] Additionally, the phrase "transmitting a message containing A and B" as described in this specification may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.
[0052] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.
[0053] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, or even if a component is expressed in the singular form, it may be composed in the plural form.
[0054] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.
[0055] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each specific embodiment, and may also be utilized as a combination of all or part of one or more embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope of the present disclosure without significantly departing from the scope of the present disclosure, at the judgment of a person skilled in the art.
[0056] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they can be understood by interchangeably, substituted, or combined.
[0057] 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 examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in the 3GPP (3rd generation partnership project) Technical Specifications (TS).
[0058] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on a network. Additionally, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for wireless resource processing of the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU as described above.
[0059] The terminal may include UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions.
[0060] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.
[0061] In addition, although a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure, at the discretion of a person with skilled technical knowledge.
[0062] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."
[0063] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, ⪋), RRC (radio resource control), MAC (medium access control), CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).
[0064] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI (downlink control information), a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.
[0065] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.
[0066] The operating principle of the present disclosure will be explained in detail below with reference to the attached drawings.
[0067] FIG. 1a is a drawing illustrating the structure of a New Radio (NR) system according to one embodiment of the present disclosure.
[0068] Referring to FIG. 1a, 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 terminal (User Equipment, hereinafter UE or terminal) (135) can connect to an external network through the base stations (e.g., gNB (105), ng-eNB (110), ng-eNB (115), gNB (120)) and the UPF (130).
[0069] In FIG. 1a, base stations (e.g., gNB (105), ng-eNB (110), ng-eNB (115), gNB (120)) can provide wireless access to terminals connected to 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 support a connection between the terminals and the core network (CN, Core network; specifically, the CN of NR is referred to as 5GC) by collecting state information such as the buffer state, available transmission power state, and channel state of the terminals to service the traffic of the users and performing scheduling.
[0070] Meanwhile, in communication, the User Plane (UP), which is related to the transmission of actual user data, and the Control Plane (CP), which is related to connection management, can be configured separately. In this drawing, gNB (105) and gNB (120) use the UP and CP technologies defined in NR technology, and ng-eNB (110) and ng-eNB (115), although connected to 5GC, can use the UP and CP technologies defined in LTE technology.
[0071] The above AMF (125) is a device responsible for various control functions as well as mobility management functions for the terminal 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 shown in FIG. 1a, the NR wireless communication system may include a Session Management Function (SMF). The SMF can manage packet data network connections, such as protocol data unit (PDU) sessions provided to the terminal.
[0072] FIG. 1b is a diagram showing a wireless protocol structure in a Long Term Evolution (LTE) and New Radio (NR) system according to one embodiment of the present disclosure.
[0073] Referring to FIG. 1b, the wireless protocol of the LTE system can be composed of PDCP (Packet Data Convergence Protocol) (105)(140), RLC (Radio Link Control) (110)(135), and MAC (Medium Access Control) (115)(130) at the terminal and eNB, respectively.
[0074] PDCP (Packet Data Convergence Protocol) (105) (140) is responsible for operations such as IP header compression / recovery, and Radio Link Control (hereinafter referred to as RLC) (110) (135) can reconfigure PDCP PDU (Protocol Data Unit) to an appropriate size.
[0075] MAC (115)(130) is connected to multiple RLC layer devices configured in one terminal and can perform the operation of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs.
[0076] The physical (PHY) layer (120) (125) performs the operation of channel coding and modulating upper layer data, creating OFDM symbols to transmit to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding to transmit to the upper layer. In addition, the physical layer also uses HARQ (Hybrid ARQ) for additional error correction, and the receiving end transmits 1 bit indicating whether the packet transmitted from the transmitting end has been received. This is called HARQ ACK / NACK information. Downlink HARQ ACK / NACK information for uplink data transmission is transmitted through the physical channel PHICH (Physical Hybrid-ARQ Indicator Channel) in the case of LTE, and in the case of NR, it can determine whether retransmission is necessary or if a new transmission should be performed through the scheduling information of the terminal in the PDCCH (Physical Dedicated Control Channel), which is a channel where downlink / uplink resource allocation is transmitted. This is because asynchronous HARQ is applied in NR. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted through the physical channels of PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Channel). The PUCCH is generally transmitted on the uplink of the PCell described later, but if the base station supports it, it may additionally transmit it to the SCell described later to the terminal, which is referred to as the PUCCH SCell.
[0077] Although not shown in this drawing, an RRC (Radio Resource Control) layer exists above the PDCP layer of the terminal and the base station, respectively, and the RRC layer can exchange connection and measurement-related setting control messages for wireless resource control.
[0078] Meanwhile, the above PHY layer can be composed of one or more frequencies / carriers, and the technology of setting and using multiple frequencies simultaneously is called carrier aggregation (hereinafter referred to as CA). CA technology allows for a significant increase in transmission capacity by the number of secondary carriers by using one or more secondary carriers in addition to the main carrier, whereas previously only one carrier was used 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 the main 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 secondary cell or SCell (Secondary Cell).
[0079] FIG. 1c is a diagram illustrating a use case utilizing an Artificial Intelligence (AI) and / or Machine Learning (ML) model for predicting Mac results of cell measurements in a next-generation mobile communication system according to one embodiment of the present disclosure.
[0080] Referring to FIG. 1c, AI and / or ML models can be utilized to predict cell measurement results in the time domain. For reference, the cell measurement results may refer to Reference Signal Received Power (RSRP) and / or Reference Signal Received Quality (RSRQ) and / or Signal to Interference plus Noise Ratio (SINR) values measured by the terminal for each cell. Additionally, for each cell, if there are multiple beams transmitted by the cell, the cell measurement results may include RSRP / RSRQ / SINR values measured by the terminal for each beam. Furthermore, the RSRP / RSRQ / SINR values may refer to one of the following values.
[0081] - RSRP and / or RSRQ and / or SINR measured at Layer 1
[0082] - RSRP and / or RSRQ and / or SINR measured / acquired at Layer 3
[0083] - Values obtained by filtering RSRP and / or RSRQ and / or SINR measured at Layer 1 (e.g., (weighted) average values using measurements over a specified period)
[0084] - Values obtained by filtering RSRP and / or RSRQ and / or SINR measured / acquired at Layer 3 (e.g., (weighted) average values using measurements over a specified period)
[0085] The meaning (or definition) of the cell measurement results above can be applied equally to the embodiments of FIGS. 1d, FIGS. 1e, and FIGS. 1f below.
[0086] When predicting cell measurement results in the time domain, the AI / ML model can be trained such that when past cell measurement results (105) (e.g., Mt cell measurement results measured during time t_k-Mt ~ t_k) are input to the AI / ML model (100), future cell measurement result prediction results (110) (e.g., Pt cell measurement results predicted during time t_k+1 ~ t_k+Pt) are output to the model.
[0087] According to an embodiment of the present invention, an AI / ML model for predicting cell measurement results in the aforementioned time domain can be used at the terminal and / or base station level.
[0088] When an AI / ML model for predicting cell measurement results is used (or inferred) at the base station, the base station may instruct (or set) the terminal to report the necessary past cell measurement results (105) as the input to the AI / ML model (100) for predicting cell measurement results. Subsequently, the base station may perform a model inference operation using the input data and obtain a future cell measurement result prediction result (110) as the output of the model.
[0089] Conversely, when an AI / ML model for predicting cell measurement results is used (or inferred) at the terminal, the terminal can independently obtain (or acquire) the necessary past cell measurement results (105) as input to the AI / ML model (100) for predicting cell measurement results. Subsequently, the terminal can perform a model inference operation using the input data and obtain (or acquire) future cell measurement result prediction results (110) as output to the model. The base station can set and / or instruct the terminal to perform the cell measurement result prediction operation and report the result value.
[0090] Predicted future cell measurement results in the time domain can be used for the following two purposes.
[0091] The first objective is to improve the handover performance of the terminal. Based on predicted future cell measurement results, the base station can predict the optimal cell for a fast-moving terminal in advance and hand over the terminal to the optimal cell at the appropriate time.
[0092] More specifically, a base station periodically receives measurement reports from a terminal to obtain cell measurement results and can hand over the terminal to the optimal cell based on the received results. However, due to changes in the actual channel environment caused by the cell measurement result reporting cycle (measurement report transmission cycle), a delay may occur between the time the optimal cell changes and the time the base station actually receives the measurement report from the terminal and identifies this change. Furthermore, if the terminal moves rapidly, this delay in the change of cell measurement results can cause the terminal to fail to hand over. For example, due to the delay between the base station receiving the measurement report from the terminal, deciding to hand over the terminal, requesting a handover from the adjacent base station corresponding to the target handover cell, and receiving approval, the terminal may not be handed over in a timely manner, and the terminal may fall into a Radio Link Failure (RLF) state. To address this issue, the base station can prevent handover failures by predicting the terminal's change to the optimal cell in advance based on predicted cell measurement results in the time domain and handing over the terminal at an appropriate time.
[0093] The second objective is to reduce the measurement overhead of the terminal. The terminal can reduce the cell measurement overhead while maintaining handover performance by skipping the cell measurement performed during every Synchronization Signal Block (SSB) cycle (Tper) and replacing the cell measurement value at that point with the predicted cell measurement result.
[0094] More specifically, the terminal can measure cell signal strength at every SSB cycle and perform Radio Resource Management (RRM) related operations based on the measured value. The RRM operations may include detecting and reporting RRM measurement events, and detecting Radio Link Failure (RLF). For the RRM operations, instead of using the result measured every Tper at every SSB cycle, the terminal may skip an SSB measurement once in the middle and use the result measured every 2*Tper. If RRM operations are performed using only the result measured every 2*Tper as described above, the cell measurement load on the terminal is reduced by 50%, but the accuracy of the RRM operations may decrease. For example, measurement events and RLF may not be detected in time. Furthermore, this can eventually lead to a degradation of the terminal's handover performance. Therefore, to reduce the cell measurement burden while preventing handover performance degradation, the terminal may predict the cell measurement result at the point where the measurement was skipped and use that result in the RRM operations. By doing this, the terminal can reduce the cell measurement load without degrading the terminal's handover performance.
[0095] Additionally, when the operation of predicting cell measurement results in the time domain using the aforementioned AI / ML is performed at the terminal, the terminal can predict future events by (re)utilizing the predicted future cell measurement result values. The said event may include at least one of RRM measurement event Ax, Radio Link Failure, and Handover Failure. For example, in the case of RRM measurement event A3, if future RSRP prediction values for the current serving cell (Pcell or PSCell) and neighboring cells are given as the result of the AI / ML model for predicting cell measurement results in the time domain, the terminal can determine at what point in time the RSRP value of the neighboring cell becomes higher than the RSRP value of the serving cell by more than a certain offset and maintains that state during the event detection time interval (TTT, tieToTrigger) so that EventA3 is detected. The method of utilizing the result value of the cell measurement result prediction model in the time domain for predicting a specific event (particularly, in the present invention, an RRM measurement event) is described in more detail as Method 2 (Indirect approach) in Fig. 1d below.
[0096] FIG. 1d is a diagram illustrating a specific method of utilizing Artificial Intelligence (AI) and / or Machine Learning (ML) models for predicting measurement events e in a next-generation mobile communication system according to one embodiment of the present disclosure.
[0097] Referring to Fig. 1d, the following methods may be considered as specific ways to utilize an AI / ML model to predict measurement events (e.g., RRM measurement reporting related events A1, A2, A3, A4, A5, A6, etc. defined in the RRC standard).
[0098] ● Method 1 (100, Direct approach): The terminal may learn and use a separate AI / ML model (105) to predict whether a measurement event will occur within a specific time interval in the future (hereinafter referred to as the prediction window). In this case, the input values of the AI / ML model may include cell measurement results (101) measured in a specific time interval in the past (hereinafter referred to as the observation window), event detection related variables (e.g., specific event related variables defined in the RRC standard, such as Ax threshold, timeToTrigger, etc.) (102), current variable values (e.g., when the entering condition for a specific event is satisfied, the time during which the satisfied state is maintained, etc.) (103), and the prediction window length (104). The AI / ML model (105) may be trained to output the probability (106) that a measurement event will occur within the prediction window interval as an output value based on the above input values. Therefore, when a terminal predicts a measurement event in the manner described above using an AI / ML model, the final result of the measurement event prediction can be the probability that the measurement event will occur within the prediction window.
[0099] ● Method 2 (200, Indirect approach): To predict whether a measurement event will occur and when it will occur within a specific future time interval (hereinafter referred to as the prediction window), the terminal can reuse the result value of the AI / ML model for predicting cell measurement results described in FIG. 1c without using a separate AI / ML model. At this time, the cell measurement result value (201) within the observation window interval may be used as the input value of the AI / ML model (203) for predicting cell measurement results. Based on the above input values, the AI / ML model can be trained to output the RSRP prediction value (204) of the terminal's serving cell (Pcell or PSCell) and neighboring cells within the prediction window interval as the output value. Subsequently, the terminal can predict when a specific measurement event will occur within the prediction window interval by using the existing rule-based measurement event detection method (205) as is. More specifically, the terminal can predict whether a measurement event will occur and the expected time of occurrence within the prediction window by applying the existing measurement event detection method to the predicted RSRP value within the prediction window. In other words, when predicting a measurement event in an indirect manner, the final prediction result value can be the expected time (208) when the measurement event occurs. The method of predicting a measurement event in an indirect manner will be described in more detail later in the embodiment of FIG. 1e below.
[0100] FIG. 1e is a diagram illustrating a specific method for a terminal to predict a measurement event using an Artificial Intelligence (AI) and / or Machine Learning (ML)-based cell measurement result prediction value according to one embodiment of the present disclosure.
[0101] Referring to FIG. 1e, the terminal can predict the occurrence of a measurement event by applying the method previously used to detect measurement events to trigger the transmission of a measurement report to future RSRP / RSRQ / SINR values for a serving cell (PCell or PSCell) and neighboring cells predicted by an AI / ML model. At this time, the method previously used to detect measurement events to trigger the transmission of the measurement report can be described as follows.
[0102] - A base station may configure the terminal to perform measurement reporting operations in an event-triggered manner (a method of transmitting a measurement reporting message when a specific event occurs). More specifically, the base station may configure the terminal to report the occurrence of the specific event and the measurement values for serving and neighboring cells at the current time through measurement reporting operations when a specific event requiring a handover occurs. To this end, the RRC standard defines events (e.g., EventA1, A2, A3, A4, A5, A6, etc.) to detect situations where a handover must occur.
[0103] - Entering conditions and leaving conditions can be defined for each event. If the measurement results of serving and neighboring cells satisfy all the entry conditions of a specific event during a specific time interval (timeToTrigger), the terminal may determine that the event has occurred and perform a measurement reporting transmission operation. Conversely, if the measurement results of serving and neighboring cells satisfy all the leaving conditions of a specific event during a specific time interval (timeToTrigger), the terminal may determine that the event has been resolved (or is no longer valid). Additionally, the terminal may perform a measurement reporting transmission operation even if the event is determined to be resolved according to the base station settings.
[0104] - More specifically, taking a specific event Event A2 as an example, the terminal can detect (or determine) the occurrence of Event A2 as described below.
[0105] The terminal can determine that Event A2 has occurred if the L3 RSRP / RSRQ / SINR values, measured from the SSB or CSI-RS transmitted by the serving cell (PCell or PSCell), remain below a specific threshold (104, a2-threshold) for the timeToTrigger (TTT) period. In other words, Event A2 can be detected.
[0106] The terminal can predict Event A2 by applying the existing Event A2 detection method described above to future RSRP values for serving cells predicted through an AI / ML model. More specifically, the terminal can predict RSRP measurement values for serving cells within a prediction window interval (110, from time T1 to time T1 + prediction window length) using a cell measurement result prediction model as in method 2 of FIG. 1d above, at time T1 (100). Subsequently, based on the predicted RSRP values, the terminal can predict that the entry condition for Event A2 is first satisfied at T2 (101) and will continue to be satisfied for a TTT (105, timeToTrigger) period. In this way, the terminal can determine whether Event A2 will occur (107) within the prediction interval based on the RSRP measurement values predicted within the prediction window interval, and if it occurs, predict the time of occurrence T3 (102).
[0107] In FIGS. 1f and 1g below, specific embodiments of a method and procedure for a base station to instruct and control a terminal to predict a measurement event, so that the terminal predicts the measurement event and, if necessary, reports it to the base station or performs a separate terminal operation, as described in FIGS. 1d and 1e above, will be described later.
[0108] FIG. 1f is a flowchart of a process in which a base station instructs a terminal to predict a measurement event and the terminal reports the prediction of a measurement event, according to one embodiment of the present disclosure.
[0109] Referring to FIG. 1f, the terminal (100) reports to the base station (105) whether it supports a cell measurement result prediction function and a measurement event prediction function, and if the terminal supports the function, the base station may instruct (or set) the cell measurement result prediction and measurement event prediction. Subsequently, the terminal may perform a cell measurement result prediction operation and a measurement event prediction operation according to the base station's instruction (or setting). Subsequently, if a measurement event is predicted, the terminal may report this to the base station, and the base station may prepare a handover procedure in advance and instruct a handover at an appropriate time.
[0110] For reference, the measurement event described above may be an event defined to configure the terminal to perform measurement reporting operations in an event-triggered manner (e.g., a method of transmitting a measurement report message when an event requiring a handover occurs). In other words, the above measurement event may refer to events defined in the RRC standard to detect situations where a handover must occur (e.g., Event A1, A2, A3, A4, A5, A6, etc.). The specific step-by-step signaling and operations between the terminal and the base station for the operations described above may be described as follows.
[0111] In step 110, the base station (105) and the terminal (100) can exchange terminal capability information related to cell measurement result prediction and measurement event prediction. The terminal may transmit to the base station at least one combination of the following indicators (or information) representing terminal capability information related to cell measurement prediction and measurement event prediction within an RRC message (e.g., UECapabilityInformation message).
[0112] - Indicator indicating whether RRM measurement prediction is supported: If the terminal supports a cell measurement result prediction operation utilizing an AI / ML model as shown in FIG. 1c above, it may include the corresponding indicator within the RRC message (or set it to True and / or Supported) and transmit it to the base station. For reference, the cell measurement result prediction operation may refer to an operation that predicts RSRP / SINR / RSRQ measurement results by cell and / or beam. More specifically, the indicator may indicate whether the terminal can predict future cell measurement results and report them to the base station.
[0113] - Indicator indicating whether indirect measurement event prediction is supported: If the terminal supports a measurement event prediction operation utilizing predicted cell measurement result values as in Method 2 of FIG. 1d above, it may include the corresponding indicator in the RRC message (or set it to True and / or Supported values) and transmit it to the base station. For reference, the measurement event prediction operation may refer to an operation that predicts measurement events based on (predicted) measurement result values (e.g., RSRP, RSRP, SINR, etc.) for the serving cell and neighboring cells. More specifically, the indicator may indicate whether the terminal can predict the occurrence of future measurement events and report whether they have occurred and the expected time of occurrence to the base station. Additionally, for the terminal to predict measurement events utilizing predicted cell measurement result values as in Method 2 of FIG. 1d above, it must naturally support the cell measurement result prediction operation. Therefore, a constraint may be specified in the standard that a terminal including an indicator indicating whether indirect measurement event prediction is supported (or set it to True / Supported values) must also include an indicator indicating whether RRM measurement prediction is supported (or set it to True / Supported values). In the absence of these constraints, the base station cannot correctly interpret the terminal capability information reported by the terminal and cannot properly configure related functions.
[0114] - Indicator indicating whether direct measurement event prediction is supported: If the terminal supports a measurement event prediction operation using a separate AI / ML model as in Method 1 of FIG. 1d above, it may include the corresponding indicator in the RRC message (or set it to True and / or Supported values) and transmit it to the base station. For reference, the measurement event prediction operation may refer to an operation of predicting measurement events (using an AI / ML model). More specifically, the indicator may indicate whether the terminal can predict the occurrence of a future measurement event and report whether it has occurred and the probability of occurrence to the base station.
[0115] Additionally, it may not be permitted to set the two indicators indicating whether the Indirect measurement event prediction and Direct measurement event prediction mentioned above are supported simultaneously. In other words, since the terminal does not need to support both Indirect measurement event prediction and Direct measurement event prediction simultaneously, a constraint may be specified in the standard prohibiting the inclusion and / or setting of both indicators. In this case, the terminal may include and / or set only one of the two indicators.
[0116] Conversely, the terminal may be allowed to include and / or configure both indicators together without any specific restrictions. In this case, if the terminal supports both Indirect measurement event prediction and Direct measurement event prediction, it may include and / or configure both indicators simultaneously and report them to the base station. If the terminal reports that it supports both methods of measurement event prediction, the base station may configure the terminal to use a method that allows it to report more useful information according to the base station implementation algorithm. For example, if the probability of a measurement event occurring is more useful in the base station implementation algorithm, the base station may instruct the terminal to use Direct measurement event prediction. Conversely, if the expected timing of a measurement event occurrence is more useful from the base station's perspective, the base station may instruct the terminal to use Indirect measurement event prediction.
[0117] Additionally, a single common indicator may be used to indicate whether the operation of predicting future measurement events and reporting them to the base station is supported by combining the terminal capabilities represented by the two indicators indicating whether the Indirect measurement event prediction and Direct measurement event prediction are supported. Even in this case, if it is agreed in the standard that only Indirect measurement event prediction is supported, the standard may specify a constraint that a terminal including (or setting to True / Supported value) a single common indicator to indicate whether the operation of predicting future measurement events and reporting them to the base station is supported must also include (or set to True / Supported value) an indicator indicating whether the RRM measurement prediction is supported.
[0118] For reference, the terminal (100) can report the terminal capability information described above to the base station (105) in units of terminal (UE), frequency range, frequency band, or feature set combination.
[0119] In step 112, the base station (105) may transmit (initial) settings to the terminal to instruct the terminal (100) to perform a cell measurement result prediction operation and a measurement event prediction operation. Refer to FIG. 1c and FIG. 1d for the cell measurement result prediction operation and the measurement event prediction operation.
[0120] For reference, as described below, the base station can be configured to perform an Event-triggered measurement reporting operation based on the actual measurement value of the terminal. In other words, the terminal can be configured to trigger the transmission of a MeasurementReport message when it detects that a specific measurement event (e.g., EventAx) has occurred based on the actual measurement value.
[0121] - Measurement Object Config (MeasObjectNR): This configuration may include information such as the target frequency (ssbFrequency), cells (allowedCellsToAddModList / cellsToAddModList), and Reference Signal resources (including ReferenceSignalConfig, SSB, or CSI-RS resources) for the terminal to perform a measurement reporting operation.
[0122] - Reporting Settings (ReportConfigNR): This setting specifies the method by which the terminal performs measurement reporting (e.g., periodical, eventTriggered, etc.). In the case of the EventTriggered method, it may include variables related to event detection (eventId, timeToTrigger, aX-threshold, etc.). More specifically, the ReportConfigNR IE can specify either periodical or eventTriggered through the reportType field. Furthermore, if the eventTriggered method is specified, the aforementioned event detection-related variables may be configured together within the eventTriggerConfig IE indicated by the eventTriggered field.
[0123] - Measurement ID Setting (MeasId): The base station may set one or more Measurement Object Settings (MeasObjectNR) and one or more Reporting Settings (ReportConfigNR) for the terminal. In this case, the base station may set one or more Measurement ID Settings (MeasId) for the terminal, and each MeasID may instruct one Measurement Object Setting and one Reporting Setting (ReportConfigNR). The terminal may perform measurements on the serving cell and neighboring cells according to the Measurement Object Settings instructed by each MeasID configured according to the base station settings, and may perform measurement reporting operations according to the ReportConfigNR Settings instructed by the corresponding MeasID. For example, if the ReportConfigNR Settings instructed by a specific MeasId include an event-triggered reporting setting, the terminal may perform measurements on the serving cell and neighboring cells according to the Measurement Object Settings instructed by the corresponding MeasId, and when a specific measurement event is detected according to the event-triggered reporting setting, it may trigger the transmission of an Entering Condition, MeasurementReport message. The meaning of the above specific measurement event being detected may include cases where the event's Entering Condition is continuously satisfied for all measurement values for a specific cell(s) during the timeToTrigger period.
[0124] When considering the above-mentioned existing Event-triggered method for setting measurement reporting, there are two main methods to consider for setting the terminal to perform measurement event prediction operations as described in Fig. 1e above.
[0125] - Method 1 (Reuse of existing reportType (eventTriggered)): The base station may reuse an existing eventTriggered type report configuration (i.e., EventTriggerConfig IE) to set up a measurement event prediction action for the terminal. In this case, the base station may include a directive (e.g., reportPredict) within the EventTriggerConfig IE to instruct the terminal to predict the event and perform a measurement reporting action. If the terminal includes such a directive, it may initiate a procedure to report the predicted event to the base station when it is predicted that the entering (entry) condition for the event will be satisfied for all (predicted) measurement results during timeToTrigger.
[0126] In this case, the following event detection-related variables included in the existing EventTriggerConfig IE can be reused as is for event prediction.
[0127] * timeToTrigger: As shown in FIG. 1e above, a time length (TTT, timeToTrigger) setting value used to detect / predict the occurrence of a specific measurement event in the RRC layer of the terminal. The timeToTrigger value can be set in units of ms.
[0128] * EventAx threshold: A threshold value used to detect / predict the occurrence of a specific measurement event in the RRC layer of the terminal, as shown in Figure 1e above (e.g., a2-Threshold in the case of EventA2). The terminal can determine whether the entering / leaving condition of a specific measurement event is satisfied by comparing the predicted RSRP / RSRQ / SINR value with the set ax-Threshold threshold value.
[0129] Additionally, the following variables may be newly included within the above EventTriggerConfig IE for event prediction.
[0130] * Prediction window (PW) length: A variable indicating how far into the future the terminal must predict a measurement event from the current point in time. It can be set in units such as Msec, sec, min, or hour. For example, if the prediction window length value is set to 1 second, the terminal can predict whether the corresponding measurement event (e.g., EventAx) will occur within 1 second from the current point in time and report this to the base station.
[0131] * Instruction for Direct or Indirect Prediction Operation: As described above in Step 110, the terminal may support event prediction operations of the Direct method and the Indirect method separately. In this case, the base station may explicitly instruct the terminal to perform the measurement event prediction operation using either the Direct method or the Indirect method. To this end, an indicator (e.g., reportPredict) for instructing the terminal to predict the corresponding event described above and perform a measurement reporting operation may be defined in an ENUMERATED form to indicate either the Direct or Indirect method. Alternatively, an indicator for instructing the event prediction operation of the Direct method (e.g., directEvent-Predict) and an indicator for instructing the event prediction operation of the Indirect method (e.g., indirectEvent-Predict) may be defined separately, and when the base station sets the measurement event operation, it may include at least one of the two indicators.
[0132] If the base station has instructed the terminal to perform a measurement event prediction operation in a direct manner, when the terminal transmits a message to the base station to report a predicted event (steps 126 and 128 below), the message may include whether the event will occur within the PW and / or a probability value for the event to occur within the PW. In this case, the base station may additionally set a probability threshold for the measurement event prediction operation in a direct manner. If a probability threshold is set, the terminal may report the predicted event only when the probability value for the event to occur within the PW exceeds the probability threshold.
[0133] Conversely, if the base station instructs the terminal to perform a measurement event prediction operation in an indirect manner, when the terminal transmits a message to the base station to report the predicted event in steps 126 and 128 below, the message may include whether the event will occur within the PW and / or the predicted time when the event will occur within the PW. In this way, if the base station can configure the terminal to perform measurement events in a specific manner among direct or indirect methods, the base station may have the advantage of determining whether the probability of the event occurring or the predicted time when the event will occur is more useful for making a handover decision for the terminal according to the base station implementation, and selecting the method that can report information more useful from the base station's perspective to instruct the terminal to perform a measurement event prediction operation.
[0134] According to another embodiment of the present disclosure, the measurement event prediction operation of the Direct method and the Indirect method may not be distinguished by the specifications, and the terminal capability information may simply be reported for the measurement event prediction operation, and the base station may set the operation for the terminal. In this case, when the terminal transmits a message to the base station to report a predicted event (steps 126 and 128 below), it may only report whether the event will occur within the PW in the message.
[0135] However, if the terminal can obtain the probability or predicted time of the event occurring within the PW according to each terminal's internal implementation, it may optionally include this in a message for reporting the predicted event in steps 126 and 128 below and report it to the base station. In this case, the field defined to include the probability or predicted time of the event occurring within the PW in the event prediction report message may be defined as an optional field that the terminal can optionally include.
[0136] According to another embodiment of the present disclosure, the terminal may support only indirect measurement event prediction operations. In this case, the terminal may receive an indicator (e.g., reportPredict) from the base station for setting measurement event prediction without distinguishing between direct and indirect methods. At this time, when the terminal transmits a message to the base station to report the predicted event in steps 126 and 128 below, the message may include whether the event will occur within the PW and / or the predicted time when the event will occur within the PW.
[0137] Additionally, when a base station sets a measurement event prediction operation through the above Method 1, it may become ambiguous whether the existing Measurement Reporting operation (in other words, an operation that detects events based on actual measurement results rather than predictions and performs the transmission of a Measurement Report message) and the new event prediction operation must be performed together, as the existing eventTriggered type reporting settings are reused for the new event prediction operation settings. More specifically, if an indicator (e.g., reportPredict) for instructing the measurement reporting operation to be performed by predicting the events described above is included within the above EventTriggerConfig IE, the terminal may determine whether to perform the existing Measurement Reporting operation using one of the following options. The existing Measurement Reporting operation may refer to an operation that detects events based on measurement results rather than predictions and performs the transmission of a MeasureReport message.
[0138] * Option 1 (Non-performance of existing Measurement Reporting operation): If the terminal includes an indicator (e.g., reportPredict) within the EventTriggerConfig IE to instruct the terminal to perform a measurement reporting operation by predicting the event described above, it may perform only the transmission of a MeasurementReport message based on the event prediction described in FIG. 1e and not perform the existing Measurement Reporting operation (in other words, the operation of detecting a measurement result-based event rather than a prediction-based event and performing the transmission of a MeasurementReport message).
[0139] * Option 2 (Perform existing Measurement Reporting operation together): If the terminal includes an indicator (e.g., reportPredict) within the EventTriggerConfig IE to instruct the terminal to perform a measurement reporting operation by predicting the event described above, it can perform the transmission of a MeasurementReport message based on the event prediction described in FIG. 1e and also perform an existing Measurement Reporting operation (in other words, an operation to detect a measurement result-based event rather than a prediction-based event and perform the transmission of a MeasureReport message).
[0140] * Option 3 (Determination of whether to perform existing Measurement Reporting operation based on base station configuration): The base station may include an indicator (e.g., reportPredict) within the EventTriggerConfig IE to instruct the terminal to perform a measurement reporting operation by predicting the event described above, and may explicitly instruct whether the terminal must also perform an existing Measurement Reporting operation (in other words, an operation to detect a measurement result-based event rather than a prediction-based event and perform the transmission of a MeasureReport message).
[0141] For example, an indicator (e.g., reportPredict) for instructing the performance of a measurement reporting operation by predicting the event described above may be defined as an ENUMARTED type to indicate either "reportPredict" or "reportActualAndPredict". In this case, when the base station sets the value of the indicator to "reportActualAndPredict", the terminal may perform the transmission of a MeasurementReport message based on the event prediction described in FIG. 1e, and also perform the existing Measurement Reporting operation (in other words, the operation of detecting a measurement result-based event rather than a prediction-based event and performing the transmission of a MeasureReport message).
[0142] Conversely, if the base station sets the value of the indicator to “reportPredict,” the terminal may only perform the transmission of a MeasurementReport message based on the event prediction described in FIG. 1e and not perform the existing Measurement Reporting operation (in other words, the operation of detecting a measurement result-based event rather than a prediction-based event and performing the transmission of a MeasureReport message).
[0143] As in Option 3, if the base station can set whether the terminal performs the existing Measurement Reporting operation while also performing the MeasurementReport message transmission based on event prediction, the base station can adaptively set the existing measurement-based measurement reporting operation and the new prediction-based measurement reporting operation to the terminal according to the base station's needs, which has the effect of increasing the freedom of base station implementation and signaling efficiency.
[0144] - Method 2 (Definition of new reportType (eventPredicted)): In order to enable the base station to set the measurement event prediction operation for the terminal, a new reportType (e.g., eventPredicted) may be defined.
[0145] More specifically, the base station may include the eventPredicted field as reportType, and the field may again include eventPredictConfig IE containing configuration information related to measurement event prediction. In this case, instead of including an indicator (e.g., reportPredict) within the EventTriggerConfig IE to instruct the terminal to predict the event and perform a measurement reporting operation as in Method 1, the base station may instruct the terminal to perform a specific measurement event prediction operation by indicating a new type (eventPredicted) as reportType.
[0146] If a new type (eventPredicted) is indicated as reportType and event prediction-related configuration information (e.g., eventPredictConfig IE) is included, the terminal may initiate a procedure to report the predicted event to the base station if it is predicted that the entering (entry) condition for a specific measurement event indicated by said event prediction-related configuration information will be satisfied for all (predicted) measurement results during timeToTrigger. However, if it is predicted that the leaving condition for the event will be satisfied for all (predicted) measurement results during timeToTrigger after the point in time when the entering condition of the event is predicted to be satisfied, the terminal may not initiate the procedure to report the predicted event to the base station.
[0147] When the measurement event prediction behavior is set to Method 2, the following event detection-related variables that were included in the existing EventTriggerConfig IE may also be separately defined and / or included in the new EventPredictConfig IE.
[0148] * timeToTrigger: As shown in FIG. 1e above, a time length (TTT, timeToTrigger) setting value used to detect / predict the occurrence of a specific measurement event in the RRC layer of the terminal. The timeToTrigger value can be set in units of ms.
[0149] * EventAx threshold: A threshold value used to detect / predict the occurrence of a specific measurement event in the RRC layer of the terminal, as shown in Figure 1e above (e.g., a2-Threshold in the case of EventA2). The terminal can determine whether the entering / leaving condition of a specific measurement event is satisfied by comparing the predicted RSRP / RSRQ / SINR value with the set ax-Threshold threshold value.
[0150] Additionally, the following variables may be included in the above EventPredictConfig IE for event prediction.
[0151] * Prediction window (PW) length: A variable indicating how far into the future the terminal must predict a measurement event from the current point in time. It can be set in units such as Msec, sec, min, or hour. For example, if the prediction window length value is set to 1 second, the terminal can predict whether the corresponding measurement event (e.g., EventAx) will occur within 1 second from the current point in time.
[0152] * Instruction for Direct or Indirect Prediction Operation: As described above in Step 110, the terminal may support event prediction operations in the Direct and Indirect methods, respectively. In this case, the base station may explicitly instruct the terminal to perform the measurement event prediction operation using either the Direct or Indirect method. To this end, an indicator (e.g., reportPredict) for instructing the terminal to predict the corresponding event described above and perform a measurement reporting operation may be defined in the form of ENUMERATED to indicate either the Direct or Indirect method.
[0153] Alternatively, an indicator for directing event prediction operation (e.g., directEvent-Predict) and an indicator for indirecting event prediction operation (e.g., indirectEvent-Predict) are defined separately, and when a base station sets a measurement event operation, it may set it by including at least one of the two indicators.
[0154] If the base station has instructed the terminal to perform a measurement event prediction operation in a Direct manner, when the terminal transmits a message to the base station to report a predicted event (steps 126 and 128 below), the message may include whether the event will occur within the PW and / or a probability value of the event occurring within the PW.
[0155] Conversely, if the base station instructs the terminal to perform a measurement event prediction operation in an indirect manner, when the terminal transmits a message to the base station to report the predicted event in steps 126 and 128 below, the message may include whether the event will occur within the PW and / or the predicted time when the event will occur within the PW. In this way, if the base station can configure the terminal to perform measurement events in a specific manner among direct or indirect methods, the base station may have the advantage of determining whether the probability of the event occurring or the predicted time when the event will occur is more useful for making a handover decision for the terminal according to the base station implementation, and selecting the method that can report information more useful from the base station's perspective to instruct the terminal to perform a measurement event prediction operation.
[0156] According to another embodiment of the present disclosure, the measurement event prediction operation of the Direct method and the Indirect method may not be distinguished by the specifications, and the terminal capability information may simply be reported for the measurement event prediction operation, and the base station may set the operation for the terminal. In this case, when the terminal transmits a message to the base station to report a predicted event (steps 126 and 128 below), it may only report whether the event will occur within the PW in the message.
[0157] However, if the terminal can obtain the probability or predicted time of the event occurring within the PW according to each terminal's internal implementation, it may optionally include this in a message for reporting the predicted event in steps 126 and 128 below and report it to the base station. In this case, the field defined to include the probability or predicted time of the event occurring within the PW in the event prediction report message may be defined as an optional field that the terminal can optionally include.
[0158] According to another embodiment of the present disclosure, the terminal may support only an indirect method of measurement event prediction operation. In this case, the terminal may receive an indicator (e.g., reportPredict) for setting measurement event prediction from a base station without distinguishing between direct and indirect methods. At this time, when the terminal transmits a message to the base station to report the predicted event in steps 126 and 128 below, the message may include whether the event will occur within the PW and / or the predicted time when the event will occur within the PW.
[0159] Method 2 described here has the advantage of increasing the degree of freedom in base station implementation compared to Method 1 described above, in that it allows for the independent setting of existing measurement result-based measurement reporting operations and new event prediction-based measurement reporting operations. In other words, it has the advantage that the base station can set existing operations and new operations to the terminal together or separately as needed, based on the base station handover implementation.
[0160] On the other hand, the above-described method 1 has the advantage of being able to set up both the existing measurement result-based measurement reporting operation and the new event prediction-based measurement reporting operation with a low signaling load compared to the above-described method 2, by reusing the EventTriggerConfig IE, which was previously used to set up the measurement reporting operation based on measurement in the existing measurement-based event-triggered method, to set up the measurement reporting operation based on event prediction. That is, when a base station sets up both the existing measurement result-based measurement reporting operation and the new event prediction-based measurement reporting operation with a low signaling load, it has the effect of reducing the signaling load by setting the variables (e.g., aX-threshold and timeToTrigger) that are commonly required for both operations together as a single field.
[0161] For reference, both of the above methods reuse the existing ReportConfigNR IE. The measurement event prediction operation can also be configured such that a specific measID (or a newly defined predictID) directs a specific Measurement object (MeasObjectNR) and a specific reporting setting (ReportConfigNR), similar to the measurement reporting configuration method of the existing Event-triggered method described above. Therefore, the terminal can predict measurement events for cells measured at a specific frequency corresponding to the Measurement object (MeasObjectNR) connected to each measID (or predictID), and report the prediction results to the base station according to the settings within the ReportConfigNR connected to that measID (or predictID).
[0162] In another embodiment of the present disclosure, instead of reusing the existing ReportConfigNR IE, a new IE (e.g., PredictReportCOnfigNR) may be defined for measurement event prediction reporting settings. However, even in this case, the prediction reporting setting information included in the new IE may be the same as the information described as being included in the EventTriggerConfig IE and eventPredictConfig IE in the methods 1 and 2 described above.
[0163] Additionally, the base station may be configured to report applicability information (114) indicating whether the terminal can perform cell measurement result prediction operations and measurement event prediction operations according to the initial settings. More specifically, the base station may provide the terminal with the initial settings an indicator to instruct the terminal to report applicability information via a UEAssistanceInformation or RRCReconfigurationComplete message. If multiple measurement result and measurement event prediction operations are configured for the terminal, the terminal may be configured to report applicability information separately for each prediction operation. More specifically, being configured for each prediction operation means being configured to report applicability information separately for each predictId and / or measId.
[0164] For the above settings, a specific RRC message (e.g., RRCReconfiguration message) may be used.
[0165] In step 114, the terminal (100) may report to the base station (105) whether it can perform a cell measurement result prediction operation and a measurement event prediction operation (in other words, applicability information) according to the cell prediction setting and measurement event prediction setting in step 112. To this end, a 1-bit indicator for indicating whether the cell measurement result prediction operation can be performed and a 1-bit indicator for indicating whether the measurement event prediction operation can be performed may be used separately.
[0166] More specifically, if the terminal (100) has a model available for predicting cell measurement results according to the base station (105) setting in step 112 and can perform cell measurement result prediction using the model, it may report to the base station by including a 1-bit indicator to indicate whether the cell measurement result prediction operation can be performed (or set to 'True' / 'Available' / 'Supported') and enable the prediction operation (setting).
[0167] Additionally, if the terminal (100) has a model available for predicting measurement events according to the base station settings in step 121 and can perform measurement event prediction using said model, it may report to the base station by including a 1-bit indicator (or set to 'True' / 'Available' / 'Supported') to indicate whether the measurement event prediction operation can be performed and activate said prediction operation (setting). If the terminal (100) has no model available for predicting cell measurement results according to the base station settings in step 112, or cannot perform cell measurement result prediction using said model due to terminal constraints, it may report to the base station by omitting a 1-bit indicator (or set to 'False' / 'NotAvailable' / 'NotSupported') to indicate whether the cell measurement result prediction operation can be performed. At this time, terminal constraints may include insufficient memory, overheating, insufficient battery, etc.
[0168] In addition, if the terminal cannot perform measurement event prediction using the model due to terminal constraints (e.g., insufficient memory, heat, insufficient battery, etc.) or if there is no model available for measurement event prediction according to the base station settings in step 112, the terminal may report to the base station by omitting (or setting to 'False' / 'NotAvailable' / 'NotSupported') a 1-bit indicator to indicate whether measurement event prediction operation can be performed.
[0169] If multiple prediction operations are configured for the terminal in step 121 above, the terminal may individually report applicability information (the 1-bit indicator) for each measurement result prediction operation (in other words, for each predictId or measId). More specifically, reporting for each prediction operation may mean individually reporting applicability information for each predictId and / or measId. A predetermined RRC message (e.g., UEAssistanceInformation or RRCReconfigurationComplete) may be used for the above reporting.
[0170] Additionally, if the terminal reports that the cell measurement result prediction operation and the measurement event prediction operation cannot be performed, the base station (105) may return to step 112 and provide new cell measurement result prediction settings and measurement event prediction settings to the terminal (100). Subsequently, the terminal (100) may determine whether the cell measurement result prediction and measurement event prediction can be performed again based on the settings and report the result to the base station (105). Thus, the base station (105) and the terminal (100) may repeat the operations in steps 112 and 114 and discuss an appropriate model (or option) available for the cell measurement result prediction operation and measurement event prediction operation.
[0171] According to another embodiment of the present disclosure, the terminal may request the base station (105) for configuration information necessary to learn an AI model required to perform the prediction operation, while reporting that the cell measurement result prediction operation and the measurement event prediction operation cannot be performed. More specifically, the terminal may require SSB and CSI-RS measurement result values for specific cells operating at a specific frequency in order to learn an AI model for predicting cell measurement results or measurement events. Accordingly, the terminal may request measurement settings for specific frequencies or specific cells (e.g., the Measurement Object settings described in step 112) for learning the cell measurement result and measurement event prediction models. To this end, at least one combination of the variables described below may be included in the message of step 114.
[0172] - Measurement Object Id: The terminal (100) may include an Id value (e.g., MeasObjectId) to indicate one of the Measurement objects (e.g., MeasObjectNR) included in the base station configuration (e.g., RRCReconfiguration IE) in step 112. For example, in step 112, the base station may include a MeasObjectNR X corresponding to the frequency while setting up a measurement result prediction or measurement event prediction for cells operating at a specific frequency X. However, if the terminal does not have the AI model required for the prediction operation, the terminal may report to the base station by omitting (or setting to 'False' / 'NotAvailable' / 'NotSupported') the 1-bit indicator to indicate whether the prediction operation can be performed as described above. Subsequently, the base station may not include the MeasObjectNR X while sending a new RRCReconfiguration message to the terminal in step 114 below to cancel the prediction operation.
[0173] However, in order to train an AI model for predicting measurement results or measurement events for cells operating at a specific frequency X, the terminal may need to measure the Reference signal (e.g., SSB or CSI-RS) transmitted by the cells operating at that frequency X and collect the resulting values. Therefore, in order to inform the base station that a specific MeasObject setting is still required for training a model for predicting cell measurement results or measurement events, the terminal may include an Id value (e.g., MeasObjectId) to indicate one of the Measurement objects (e.g., MeasObjectNR) included in the previous base station setting (e.g., RRCReconfiguration IE) in step 112 in a predetermined RRC message and transmit it to the base station. Subsequently, the base station may include a specific Measurement object (MeasObjectNR) in accordance with the terminal's request while transmitting a new RRCReconfiguration message to the terminal in step 116 below.
[0174] - Measurement frequency: The terminal may request the base station by including information in a predetermined RRC message in step 114 to indicate the frequency band required for measurement for predicting cell measurement results or learning a measurement event prediction model.
[0175] More specifically, a field to indicate a specific frequency band is newly defined within the RRC message, and the field may indicate an ARFCN-ValueNR IE to indicate a specific frequency. Subsequently, the base station transmits a new RRCReconfiguration message to the terminal in step 116 below, and may provide a Measurement object (MeasObjectNR) containing measurement information necessary to measure the Reference signal transmitted by cells operating in the specific frequency band in accordance with the terminal's request.
[0176] - Measurement cell (list): The terminal may request the base station by including information in a predetermined RRC message in step 114 to indicate the cell(s) that need to be measured for predicting cell measurement results or learning a measurement event prediction model.
[0177] More specifically, a field for designating specific cells may be defined, and said field may include the ID(s) of specific cells (e.g., PhysCellId). Subsequently, the base station may transmit a new RRCReconfiguration message to the terminal (step 116 below) and provide a Measurement object (MeasObjectNR) containing measurement information necessary to measure the Reference signal transmitted by the cells requested by the terminal.
[0178] In step 116, the base station (105) may include the measurement setting information requested by the terminal (100) in step 114 to obtain model training data in a predetermined RRC message (e.g., RRCReconfiguration message) and transmit it to the terminal. The measurement setting information may include a specific Measurement object, a Measurement object for a specific frequency, a Measurement object for specific cells, etc., requested by the terminal in step 114. Subsequently, the terminal (100) may measure the Reference signals transmitted by the target cells according to the measurement settings within the Measurement object set by the base station (105), store the result value as model training data, and then use it to directly perform model training or transmit it to another server that performs model training.
[0179] For reference, under current RRC specifications, a terminal can perform measurements only on the Measurement object indicated and / or associated by at least one measId among all Measurement objects included by the base station in the RRCReconfiguration message. In other words, measurements can be performed only on the Measurement object associated with a specific report configuration (e.g., ReportConfigNR) via the measId.
[0180] There may be no reason or motivation for the terminal to perform measurements on a measurement object requested by the terminal for the purpose of collecting model training data and to report the measurement results to the base station. In such cases, the base station may provide a Measurement object containing measurement information for collecting training data in step 116 in accordance with the terminal request in step 114, but may not connect the said Measurement object to a specific reporting configuration (ReportConfigNR). The fact that the said Measurement object may not be connected to a specific reporting configuration (ReportConfigNR) may mean that no measId may point to the said Measurement object.
[0181] However, even in this case, the terminal must be able to perform measurements on the corresponding Measurement object for the purpose of collecting model training data. Therefore, the base station may include an indicator to allow the terminal to measure even on measurement objects not indicated by any measId (i.e., not connected to any ReportConfigNR) within the aforementioned predetermined RRC message (e.g., RRCReconfiguration message) at the terminal, cell group, and measurement object levels, and transmit it to the terminal. If the indicator is included in the RRC message (or is set to 'true / enabled / allowed'), the terminal may perform measurements on measurement objects not indicated by any measId (i.e., not connected to any ReportConfigNR) for the purpose of collecting model training data and store the resulting values.
[0182] If the terminal does not separately request measurement information (e.g., Measurement object) for collecting model training data in step 114 above, the base station setup in step 116 may be omitted.
[0183] In step 114, if the terminal (100) immediately activates a cell measurement result prediction operation or a measurement event prediction operation (setting) according to the base station (105) setting, this step may be omitted.
[0184] In step 118, the terminal (100) can perform measurements to collect model learning data according to the base station settings in step 116 and store the result values.
[0185] Afterward, the terminal (100) can directly train a necessary model using the collected training data, or transmit the collected training data to a model training server and receive the model trained by the server. (It can acquire or receive.)
[0186] In the above step 114, if the terminal immediately activates the cell measurement result prediction operation or the measurement event prediction operation (setting) according to the base station setting, this step may be omitted.
[0187] In step 120, if the terminal (100) has obtained a model necessary for predicting cell measurement results or measurement events in step 118, it may report the changed applicability information to the base station (105). Refer to step 114 for the operation of reporting the applicability information.
[0188] In the above step 114, if the terminal immediately activates the cell measurement result prediction operation or the measurement event prediction operation (setting) according to the base station setting, this step may be omitted.
[0189] In step 122, the base station (105) can set up cell measurement result prediction operations and measurement result prediction operations that the terminal can perform based on the changed applicability information reported by the terminal in step 120. The specific setting method is as described in step 112.
[0190] In the above step 114, if the terminal immediately activates the cell measurement result prediction operation or the measurement event prediction operation (setting) according to the base station setting, this step may be omitted.
[0191] In step 123, if the terminal (100) can perform cell measurement result prediction operation and measurement event prediction operation according to the base station (105) setting in step 122, it can activate the operation (setting) and report applicability information to the base station as described in step 114. The case where cell measurement result prediction operation and measurement event prediction operation can be performed may mean a case where the base station setting prediction operation setting is applicable.
[0192] For reference, in step 114 above, if the terminal immediately activates the cell measurement result prediction operation or the measurement event prediction operation (setting) according to the base station setting, this step may be omitted.
[0193] In step 124, the terminal may perform a measurement event prediction operation as described in FIG. 1e, depending on the base station settings in step 112 or step 122. More specifically, the terminal may perform measurement event prediction (in other words, perform AI model inference and predict whether the corresponding measurement event will occur within the PW interval based on the result value) at specific intervals (or when specific conditions are satisfied). Specific operations for this are as described in the embodiment of FIG. 1g below.
[0194] In step 126, the terminal (100) may predict that a specific measurement event (e.g., EventAx) will occur within PW according to the base station settings in step 112 or step 122, and report the predicted information / result to the base station (105) through a predetermined RRC message (e.g., an existing MeasurementReport message or a newly defined PredictionReport message). More specifically, the terminal may report to the base station by including at least one combination of the following information as the predicted information / result within the RRC message to help the base station optimize future handover settings and instruction timing based on the report.
[0195] * MeasId / PredictID: The terminal may include a MeasId / PredictID value corresponding to the predicted event prediction and reporting action within the RRC message for reporting the prediction result. Based on the ID value, the base station can determine which event (EventAx) the terminal is reporting as a result of predicting according to a specific prediction reporting setting (e.g., ReportConfigNR) associated with the MeasID / PredictID.
[0196] * Prediction indicator (reportPredict): The terminal may reuse existing MeasurementReport messages while reporting predicted measurement events. When reusing, if the base station in step 112 above has set up a measurement event prediction operation using a combination of method 1 and option 2, transmission of MeasurementReport messages may be initiated based on the detection of existing measurement-based events for the same MeasId / PredictId, or transmission of MeasurementReport messages may be initiated based on the prediction of new measurement events.
[0197] When the transmission of a MeasurementReport message is initiated based on the prediction of a new measurement event, the timing of the transmission of the MeasurementReport message may be determined as in Options 1 to 3 below.
[0198] * Option 1: Start sending MeasurementReport messages immediately after the terminal performs the first event prediction.
[0199] * Option 2: After the terminal first performs an event prediction, it starts transmitting a MeasurementReport message when a specific condition is satisfied. At this time, the specific condition may include the case where the terminal continues to predict the event for a specific period after the first event prediction. Or it may include the case where the terminal continues to predict the event N or more times for a specific period after the first event prediction. Or it may include the case where the success rate of the event prediction for a specific period after the first event prediction is above a specific threshold value.
[0200] * Option 3: If the terminal performs an event prediction, start sending MeasurementReport messages a specific time prior to the predicted time of the event occurrence.
[0201] The above specific time may be a value designated (or set) by the base station or a value determined by the terminal, and all values of the range of the above specific time that are greater than or equal to 0 may be considered.
[0202] The above specific time may be determined by considering a specific event parameter value currently in use by the base station. For example, EventAx may include a TTT value, and the specific time may be the same value as TTT. Alternatively, the above specific time may be TTT + HO preparation time, etc. The HO preparation time may be a value designated (or set) by the base station or a value determined by the terminal.
[0203] Here, "TTT time prior to the predicted time of the event occurrence" can be defined as the time of the EventAx's entry. In this way, if the time of the EventAx's entry is defined separately, it may include starting the transmission of the MeasurementReport message by a specific amount of time prior to the time of the EventAx's entry. For example, starting the transmission of the MeasurementReport message by the HO preparation time earlier than the expected time of the EventAx's entry may also be considered.
[0204] If a MeasurementReport message is transmitted a specific time prior to the predicted occurrence of the event according to the method described above, the handover delay can be reduced by triggering the handover preparation procedure early, and handover performance can be improved in situations requiring rapid mobility. In addition, energy efficiency can be improved because unnecessary measurements do not need to be performed.
[0205] From the perspective of the base station, when it receives a MeasurementReport message transmitted by a terminal for a specific MeasId / PredictId, it cannot distinguish whether the MeasurementReport is an existing MeasurementReport transmitted when an event is detected based on measurement information, or a MeasurementReport transmitted when an event is predicted. Therefore, to solve this problem, the terminal may include an indicator within the MeasurementReport message to indicate whether the report message was triggered by event detection based on actual measurement results or by event prediction. If the indicator is included (or set to true), the base station can recognize that the MeasurementReport message transmitted by the terminal was triggered by measurement event prediction.
[0206] * List of target cells for which an event is predicted: When a measurement event (e.g., Event A3, A4, A5, A6) related to the measurement results of a serving cell and neighboring cells is predicted, the terminal (100) may include the target cells for which the event is predicted in the RRC message for reporting the prediction result. More specifically, if the predicted measurement result for a specific neighboring cell is expected to continuously satisfy the entering (entry) condition of a specific event for a timeToTrigger, the terminal may include the neighboring cell in the cell list as the target cell for which the event is predicted and report it to the base station. By receiving the cell list from the terminal, the base station can identify which cells the specific event is predicted for, select the optimal cell among them, and instruct a handover to that cell. To this end, the base station may include an indicator in the event prediction settings of steps 112 and 122 to instruct the terminal to report the cell list information together.
[0207] * Predicted measurement result values: When a measurement event related to the measurement results of a serving cell and neighboring cells is predicted, the terminal (100) may include the predicted measurement result values for the target cells for which the event is predicted in the RRC message for the prediction result report. The measurement event related to the measurement results of neighboring cells may include Event A3, A4, A5, and A6, and the predicted measurement result values for the target cells for which the event is predicted may include multiple RSRP / RSRQ / SINR values predicted in the PW interval.
[0208] More specifically, the terminal may report the predicted cell measurement value(s) within the PW interval for each cell included in the list of target cells where the described event is predicted. By receiving the predicted cell measurement result values for each cell along with the cell list from the terminal, the base station may select the optimal cell among the cells and instruct a handover. To this end, the base station may include an indicator in the event prediction settings of steps 112 and 122 to instruct the terminal to report the predicted measurement result values within the PW interval for each cell along with the cell list information.
[0209] Additionally, if the predicted measurement result values are included for all target cells where the above event is predicted, the signaling load may increase. To solve this problem, the base station may instruct the terminal to report predicted measurement result values for K cells in order of signal strength at the present time or at a specific future time among the target cells where the above event is predicted. To this end, setting information such as the K value and the reference time for selecting K cells in order of signal strength can be included in the event prediction settings of steps 112 and 122.
[0210] * Event prediction probability: The terminal (100) may include a probability value for the predicted event occurring in the PW interval according to the base station settings as described in step 112 above within the RRC message for reporting the prediction result.
[0211] * Event prediction time: The terminal (100) may include the time at which an event is predicted to occur in the PW section according to the base station settings as described in step 112 above within the RRC message for reporting the prediction result.
[0212] In step 128, the terminal (100) can transmit a subsequent event prediction report message to the base station (105).
[0213] More specifically, the terminal (100) may continue to perform predictions for the event even after performing an initial event prediction report in step 126. Depending on the additional prediction results, the terminal may transmit at least one combination of the following indicators to the base station (105) by including them in a predetermined RRC message (e.g., MeasurementReport) or a predetermined MAC CE.
[0214] * Indicator for canceling an existing prediction report (e.g., cancelPredict): Even after the terminal (100) predicts a specific event in step 126 and reports the predicted event through a predetermined RRC message, it may perform a subsequent prediction for the event based on newly obtained cell measurement results. If the result of the subsequent prediction is different from the existing prediction report, the terminal may report to the base station by including an indicator for canceling the existing prediction report in the RRC message or MAC CE. More specifically, this may refer to a case where it was previously reported that a specific event would occur, but it is predicted that the event will not occur. In this case, the terminal may include the measId / PredictId that was included in the prediction report to be canceled, and the base station may understand that the prediction report that was most recently reported has been canceled by including the Id value.
[0215] Additionally, there may be multiple event prediction target cells included in the predicted event report in step 126 above. In this case, since event prediction may be canceled for specific cell(s), target cells for which event prediction has been canceled may be included together with the cancelPredict indicator.
[0216] * Indicator for confirming an existing prediction report (e.g., confirmPredict): The terminal (100) may continue to perform measurements on the target cells where the event was predicted even after predicting a specific event in step 126 and reporting the predicted event through a predetermined RRC message. If it becomes certain that the previously predicted event has actually occurred / detected based on actual measurement values, the terminal may report to the base station by including an indicator for confirming the prediction report content (in other words, the content reported as the occurrence of a specific event) in the RRC message or MAC CE. At this time, the terminal may include the measId / PredictId that was included in the prediction report to be confirmed, and the base station may understand that the prediction report content that was last reported, including the corresponding Id value, has been confirmed. The method including the confirmPredict described above has the effect of reducing signaling load because, compared to the method in step 130 below where the terminal detects the occurrence of a specific actual event based on actual measurement results and resends the MeasurementReport message itself as before, it does not need to report redundant information again. Redundant information may include at least one of the event type, the target cells for the event occurrence, and the measurement values for those cells.
[0217] Additionally, there may be multiple event prediction target cells included in the predicted event report in step 126 above. In this case, since the event prediction can be confirmed for specific cell(s), the target cells for which the event prediction has been confirmed may be included together with the confirmPredict indicator.
[0218] * An indicator (e.g., enteringMet) to indicate whether the event entry condition is satisfied by the actual measurement result: The terminal (100) can continue to perform measurements on the target cells where the event is predicted even after predicting a specific event in step 126 and reporting the predicted event through a predetermined RRC message. The base station (105) can fully trust the predicted event information reported by the terminal in step 126 and, without subsequent reports from the terminal in steps 128 and 130, immediately perform a handover instruction in step 132 below. However, if the base station trusts only the prediction report from the terminal in step 126 and immediately instructs a handover to the target cell where the event is predicted, a handover failure may occur due to too early handover if the event predicted by the terminal is incorrect. Conversely, if the base station does not trust the terminal's prediction report in step 126 above and only instructs a handover after the terminal receives the existing MeasurementReport message reported in step 130 below, which is based on actual measurements and a specific event occurs, a handover failure may occur due to a too late handover, where the terminal has already moved into the range of another cell and cannot properly receive the handover instruction transmitted by the existing cell. To compensate for the disadvantages of these two methods, the base station may instruct a handover when the entry condition for the event predicted by the terminal is satisfied for the first time by actual measurements or is satisfied for a short period of time (e.g., shortTimeToTrigger).However, from the perspective of the base station, additional reporting from the terminal may be required because it is not possible to know when the entry condition for an event predicted by the terminal is first satisfied by the terminal's actual measurement value or satisfied for a short period of time (e.g., shortTimeToTrigger). Therefore, the terminal may report to the base station by including an indicator (e.g., enteringMet) in the RRC message or MAC CE to indicate whether the event entry condition for an event previously predicted and reported (in step 126 above) is first satisfied by the actual measurement result.
[0219] Alternatively, the terminal may report to the base station by including an indicator (e.g., enteringMet) in the RRC message or MAC CE to indicate whether the event entry condition for an event previously predicted and reported (in step 126) has been satisfied for a certain period of time (e.g., shortTimeToTrigger) by the actual measurement result. To this end, the base station may include the aforementioned certain time value (shortTimeToTrigger) in the event prediction settings of steps 112 and 122. Additionally, there may be multiple event prediction target cells included in the predicted event report in step 126. In this case, since the actual measurement result value may satisfy the event entry condition only for specific cell(s), information to indicate the target cells for which the event entry condition has been satisfied may be included together with the enteringMet indicator.
[0220] In step 130, if the terminal (100) is configured to detect an event based on the actual measurement result value and send a measurement report according to the base station settings of steps 112 and 122, it can trigger the transmission of the measurement report based on the actual measurement result value as before.
[0221] More specifically, if the entry (entering) condition for a specific event is satisfied for all measurement values for a specific cell(s) during the timeToTrigger period, the terminal may detect that the event has occurred and start a measurement report transmission operation. At this time, the measurement report message may include measurement values for the target cells that generated the event, and if a cell measurement result prediction operation is also set, it may include predicted measurement values for the cells at a future point in time.
[0222] In step 132, the base station (105) may instruct the terminal (100) to perform a handover. More specifically, the base station (105) may select an optimal handover target cell based on the information reported by the terminal in steps 126, 128, and 130, and instruct the terminal (100) to perform a handover operation at the optimal handover instruction time. A predetermined RRC message (RRCReconfiguration) may be used for the handover instruction.
[0223] FIG. 1g is a drawing illustrating a specific method in which a terminal performs a measurement event prediction operation according to one embodiment of the present disclosure.
[0224] Referring to FIG. 1g, when the terminal performs an event prediction operation in step 124 according to the base station settings in steps 112 and 122 of FIG. 1f described above, it can determine the timing of the event prediction operation and perform the event prediction using a combination of at least one of the following two methods.
[0225] - Method 1 (Performing prediction operation continuously over time): After activating the measurement event prediction operation (setting) according to the base station setting in step 122 of FIG. 1f above, it is possible to periodically predict whether a specific event will occur within the PW (Prediction Window) interval. As the prediction operation period, one or more of the following options 1 to 3 may be used.
[0226] * Option 1 (100, perform prediction operation whenever a new measurement (prediction) result value is obtained): The terminal can periodically perform cell measurements for the measurement event prediction operation. Thus, the terminal can periodically obtain a new cell measurement result value (or cell measurement result prediction value) (103). As described above, whenever the terminal obtains a new cell measurement result value (or new cell measurement result prediction value), the terminal can predict (105) whether a specific event will occur within the PW interval (107) based on the newly obtained measurement (prediction) value. Note that since the terminal may not always be able to perform cell measurements at a constant interval, the actual interval at which measurement event prediction is performed may not be constant.
[0227] * Option 2 (200, perform prediction operation every prediction period): The terminal can periodically predict (205) whether a specific event will occur within the PW interval every prediction period (207, prediction period) set by the base station. To this end, the prediction period may be included in the measurement event prediction setting information provided to the terminal by the base station in steps 112 and 122 of FIG. 1f. When using Option 2, the base station has the advantage of being able to set an appropriate prediction period to the terminal according to the delay time allowed in the terminal's event prediction for base station handover implementation. The terminal can achieve a reduction in power consumption by performing event prediction at a longer period compared to Option 1.
[0228] * Option 3 (300, Prediction operation performed at the PW length period): Whenever the terminal performs an event prediction, it can predict whether an event will occur within a future PW interval based on the current time point. For example, if an event prediction is performed at time t0, it can predict whether an event will occur in the time interval between t0 and t0 + PW length. In this case, to avoid performing duplicate event predictions for the same time interval, the terminal can perform an event prediction again at t0 + PW length. That is, the terminal can use the PW length (307, Prediction window length) included in the base station settings in steps 112 and 122 of FIG. 1f as the event prediction operation period.
[0229] - Method 2 (Perform prediction operation only when the event entering condition is satisfied): If the terminal continuously performs event prediction periodically as in Method 1 above, the terminal may consume too much energy for event prediction. Therefore, the terminal may be configured to perform event prediction only at a time when there is a high probability that the corresponding event will actually occur. More specifically, the terminal may perform event prediction only after the point in time when the entering (entry) condition of the event to be predicted is satisfied by the actual measurement result value. As a specific method for this, a combination of at least one of the following options may be used.
[0230] * Option 1 (Perform event prediction once when the Entering Condition is satisfied for the first time): The terminal may perform a prediction for the event once when the entering (entry) condition of the event to be predicted is satisfied for the first time by the actual measurement result value for a specific cell. In this case, it can be understood that the terminal predicts whether the state in which the Entering Condition is satisfied will continue for timeToTrigger. Therefore, in the measurement event prediction setting information provided to the terminal by the base station in steps 112 and 122 of 1f, a constraint may be added that the PW length must always be set to be equal to the timeToTrigger value, or the timeToTrigger value may be used as the PW length without setting the PW length separately.
[0231] * Option 2 (Perform event prediction once when the Entering Condition is satisfied for a specific time): The terminal may perform a prediction for the event once when the entering (entry) condition of the event to be predicted is satisfied for a specific time (e.g., shortTTT) set by the base station based on the actual measurement result value for a specific cell. In this case, since the terminal performs the event prediction after the Entering Condition of the event to be predicted has already been satisfied for a certain period of time based on the actual measurement value, energy consumption can be further reduced compared to Option 1 by performing the prediction only at a time when the probability of the event occurring is higher. To this end, the specific time value (shortTTT) may be included in the measurement event prediction setting information provided by the base station to the terminal in steps 112 and 122 of 1f.
[0232] * Option 3 (Performing subsequent predictions periodically after the Entering Condition is satisfied): The terminal may perform an event prediction once when the Entering Condition of the event to be predicted is satisfied by the actual measurement result value for the first time or for a certain period of time, as in Option 1 or Option 2 above. However, since the terminal may obtain additional cell measurement result values before the time until the actual event occurs arrives, the terminal may perform a subsequent event prediction operation based on the new measurement result value to increase the accuracy of the event prediction. For example, after the prediction operation for a specific event is first performed by Option 1 and Option 2 above, the terminal may additionally repeat the prediction operation for the corresponding event a specific number of times (e.g., predictAmount) at a specific time interval (e.g., predictInterval). To this end, the specific time interval (predictInterval) and the specific number of times (predictAmount) may be included together within the measurement event prediction setting information provided to the terminal by the base station in steps 112 and 122 of 1f. Alternatively, the terminal may perform a prediction operation periodically as in method 1 after the prediction operation for a specific event is first performed by option 1 and option 2. In addition, the terminal may perform a subsequent prediction report as in step 128 of FIG. 1f whenever a subsequent prediction is performed after the initial event prediction report, or may perform a report only when there is a prediction result different from the prediction report previously transmitted.
[0233] Method 3 (Terminal performs predictive operation according to Method 1 or Method 2 depending on base station settings): Depending on the base station settings, the terminal may determine whether to continuously perform predictive operation periodically as in Method 1 or to perform predictive operation after the Entering Condition of the measured event is satisfied by the actual measurement result as in Method 2. To this end, at least one of the following options (Option 1 and / or Option 2) may be used.
[0234] * Option 1 (The base station explicitly specifies the method the terminal will use): The base station may instruct the terminal to perform an event prediction operation using either Method 1 or Method 2. For example, within the measurement event prediction setting information provided by the base station to the terminal in steps 112 and 122 of FIG. 1f, an indicator (e.g., predictOnlyEntering) may be included that allows the terminal to perform a prediction operation only after the Entering Condition of the event to be predicted is satisfied. If the indicator is included / set in the base station's settings, the terminal may perform a prediction operation as in Method 2; otherwise, it may perform a prediction operation as in Method 1.
[0235] * Option 2 (Base station indirectly / implicitly instructing the terminal on which method to use): The base station may indirectly / implicitly instruct the terminal on which of the above methods, Method 1 or Method 2, to use to perform the event prediction operation. For example, if the PW length included in the measurement event prediction setting information provided by the base station to the terminal in steps 112 and 122 of FIG. 1f is greater than / longer than timeToTrigger, the terminal must perform event prediction before the Entering Condition of the event to be predicted is first satisfied. Therefore, in this case, the terminal can perform the event prediction operation as in Method 1. On the other hand, if the PW length is shorter than / smaller than timeToTrigger, the terminal can perform the prediction operation as in Method 2 after the Entering Condition of the event to be predicted is satisfied by the actual measurement result. In this case, the specific point in time at which the terminal performs the prediction operation can be left to the terminal implementation.
[0236] FIG. 2 is a block diagram of a terminal or user equipment according to one embodiment of the present disclosure.
[0237] The terminal (200) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things (IoT) devices having various form factors, and can perform wireless communication with a base station through a wireless channel.
[0238] Referring to FIG. 2, the terminal (200) may include at least one transceiver (201) (hereinafter, transceiver), at least one processor (202) (hereinafter, processor), and at least one memory (203) (hereinafter, memory). The transceiver (201), processor (202), and memory (203) of the terminal (200) may operate according to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure. However, the components of the terminal (200) are not limited to the examples of components shown in FIG. 2. In other embodiments, the terminal (200) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (201), processor (202), or memory (203) may be integrated into a single component.
[0239] The transceiver (201) may be a basic communication circuit or communication circuitry that enables the terminal (200) to perform wireless communication with a node or entity of a network. For example, the transceiver (201) may enable the terminal (200) to transmit and receive signals via cellular wireless communication with a base station or to transmit and receive signals via cellular wireless communication with another terminal. For example, the transceiver (201) may support at least one of various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the transceiver (201) may include all subsequent generations of wireless communication.
[0240] According to one embodiment, the terminal (200) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (200) supports NR-DC (NR Dual Connectivity), the terminal (200) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, if the terminal (200) supports short-range wireless communication, the terminal (200) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).
[0241] According to one embodiment, the transceiver (201) may include various circuit structures used to transmit and receive signals through a base station and a wireless channel. The signals may include control information and data. For example, the transceiver (201) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (201) may output the signal received through the wireless channel to a processor (202) and transmit the signal output from the processor (202) through the wireless channel.
[0242] The processor (202) can control the overall operation of the terminal (200) according to an embodiment of the present disclosure. The processor (202) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (202) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (203) individually, collectively, or in any combination. Additionally, the processor (202) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.
[0243] The processor (202) is electrically, operatively, or communicatively coupled to the transceiver (201) so as to control the transceiver (201).
[0244] The processor (202) may include at least one processor (or processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (202) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (202) may be included in one chip, and another part of the processor (202) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (201) or a memory (203).
[0245] The processor (202) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (202) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (202) may control other components of the terminal (200) to perform various operations by executing computer programs, code, or instructions stored in memory (203).
[0246] Memory (203) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (203) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0247] The memory (203) can be electrically, operatively, or communically coupled with the processor (202) and can be accessed by the processor (202).
[0248] A computer program, code, or instruction that can be executed by a processor (202) may be stored in the memory (203). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (202) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (202) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (203).
[0249] According to one embodiment of the present disclosure, the operation of the terminal (200) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (203), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.
[0250] FIG. 3 is a block diagram of a base station according to one embodiment of the present disclosure.
[0251] The base station (300) can perform wireless communication with at least one terminal within the area of the base station (300) through a wireless channel.
[0252] Referring to FIG. 3, a base station (300) may include at least one transceiver (301) (hereinafter, transceiver), at least one processor (302) (hereinafter, processor), and at least one memory (303) (hereinafter, memory). The transceiver (301), processor (302), and memory (303) of the base station (300) may be operated according to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure. However, the components of the base station (300) are not limited to the examples of components shown in FIG. 3. In other embodiments, the base station (300) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (301), processor (302), or memory (303) may be integrated into a single component.
[0253] The transceiver (301) may be a communication circuit or communication circuitry that enables the base station (300) to perform wireless communication with a node or entity of the network. For example, the transceiver (301) may enable the base station (300) to transmit and receive signals to and from a terminal (200) via cellular wireless communication or to transmit and receive signals to and from another network entity via wireless communication. For example, the transceiver (301) may support various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the transceiver (301) may include all subsequent generations of wireless communication. According to one embodiment, the transceiver (301) may include various circuit structures used to transmit and receive signals to and from a terminal via a wireless channel. The signals may include control information and data. For example, the transceiver (301) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (301) may output the signal received via the wireless channel to a processor (302) and transmit the signal output from the processor (302) via the wireless channel.
[0254] Meanwhile, according to one embodiment of the present disclosure, a base station (300) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (300) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (300) performs wired communication, the base station (300) may include a separate network interface for wired communication in addition to the transceiver (301). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.
[0255] The processor (302) can control the overall operation of the base station (300) according to an embodiment of the present disclosure. The processor (302) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (302) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (303) individually, collectively, or in any combination. Additionally, the processor (302) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.
[0256] The processor (302) is electrically, operatively, or communicatively coupled to the transceiver (301) so as to control the transceiver (301).
[0257] The processor (302) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (302) may be included in one chip, and another part of the processor (302) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a transceiver (301) or memory (303).
[0258] The processor (302) may perform, cause, or control the operation of a base station to execute at least one or a combination of methods according to embodiments of the present disclosure. For example, the processor (302) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (302) may control other components of the base station (300) to perform various operations by executing computer programs, codes, and instructions stored in memory (303).
[0259] Memory (303) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (303) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0260] The memory (303) can be electrically, operatively, or communically coupled with the processor (302) and can be accessed by the processor (302).
[0261] A computer program, code, or instruction that can be executed by a processor (302) may be stored in the memory (303). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (302) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (302) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (303).
[0262] According to one embodiment of the present disclosure, the operation of a base station (300) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (303), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.
[0263] A terminal or a base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, a terminal can communicate with network entities such as an access and mobility management function (AMF) or a session management function (SMF) through a base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals or relaying them with network entities. The structure of the above-mentioned network entities will be explained in more detail through the drawings below.
[0264]
[0265] FIG. 4 is a block diagram of a network entity performing network functions according to one embodiment of the present disclosure.
[0266] A network entity (400) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (400).
[0267] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.
[0268] The above NF may include any one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).
[0269] Referring to FIG. 4, a network entity (400) may include at least one network interface (401), at least one processor (402) (hereinafter referred to as processor), and at least one memory (403) (hereinafter referred to as memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (400), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 4. In such cases, the instance may be composed of one or more logical functional units and may be logically represented.
[0270] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the network interface (401), processor (402), and memory (403) of the network entity (400) may be operated. However, the components of the network entity (400) are not limited to the examples of components shown in FIG. 4. In other embodiments, the network entity (400) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the network interface (401), processor (402), or memory (403) may be implemented as a single component.
[0271] The network interface (401) is a collective term for the transmitting and receiving parts of a network entity and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or other network entities. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (401) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The network interface (401) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the network interface (401) may be referred to as a communication circuitry, a network interface circuitry, or a communication interface circuitry.
[0272] The processor (402) can control the overall operation of the network entity (400) according to an embodiment of the present disclosure. In one embodiment, the processor (402) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (402) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (403) individually, collectively, or in any combination. Additionally, the processor (402) may include a single-core processor or a multi-core processor, and in a specific implementation method, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (402) may not necessarily be composed of physical hardware when the network function (400) is implemented in an instance form according to another embodiment.
[0273] According to one embodiment, the processor (402) is electrically, operatively, or communicatively coupled to the network interface (401) so as to control the network interface (401).
[0274] The processor (402) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (402) may be included in one chip, and another part of the processor (402) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a network interface (401) or memory (403).
[0275] The processor (402) may perform or control the operation of a network entity (400) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (402) may control the operation of the network entity (400) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (402) may control other components of the network entity (400) to perform various operations by executing computer programs, code, or instructions stored in memory (403).
[0276] Memory (403) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (403) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.
[0277] According to one embodiment, the memory (403) may be electrically, operatively, or communically coupled with the processor (402) and may be accessed by the processor (402).
[0278] A computer program, code, or instruction that can be executed by a processor (402) may be stored in the memory (403). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (402) may be stored in a single memory or separated and distributed across two or more memories. The processor (402) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (403).
[0279] According to one embodiment of the present disclosure, the operation of a network entity (400) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (403), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.
[0280] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0281] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.
[0282] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0283] Additionally, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or 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 through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.
[0284] In the present disclosure, the terms “computer program product” or “computer readable medium” are used to collectively refer to media such as memory, a hard disk installed in a hard disk drive, and signals. These “computer program product” or “computer readable medium” are configurations provided in a method for reporting terminal capability in a wireless communication system according to the present disclosure.
[0285] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory storage medium' simply means that it is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily. For example, a 'non-transitory storage medium' may include a buffer in which data is stored temporarily.
[0286] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through 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., downloadable app) may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.
[0287] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.
[0288] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated together as needed. For example, parts of one embodiment of the present disclosure and another embodiment may 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 variations based on the technical concept of the embodiments may also be possible. For example, the embodiments may be applied to LTE systems, 5G, NR systems, or 6G systems, etc. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.
[0289] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.
Claims
1. A method performed by a terminal in a wireless communication system, A step of receiving event prediction setting information from a base station, Based on the above event prediction setting information, a step of predicting the occurrence of a measurement event through artificial intelligence and machine learning, wherein the prediction of the occurrence of the measurement event corresponds to either a direct method or an indirect method; and A method characterized by including the step of transmitting information related to the prediction of the occurrence of the measurement event to the base station.
2. In Paragraph 1, Information related to the prediction of the occurrence of the above event includes at least one of a list of target cells where the measurement event is predicted or information on the predicted measurement results of the target cells, and If the prediction of the above event occurrence corresponds to the above Direct method, the cell measurement result in the first time interval is used as the input for model learning to obtain the probability of event occurrence in the second time interval as the output, and the information related to the prediction of the above event occurrence includes the probability of event occurrence. If the prediction of the above event occurrence corresponds to the above Indirect method, the cell measurement result in the first time interval is used as the input for model learning to obtain signal quality prediction information in the second time interval as the output, and the information related to the prediction of the above event occurrence includes the time of event occurrence in the second time interval based on the signal quality prediction information. A method characterized in that information related to the prediction of the occurrence of the above event is transmitted via a Prediction Report Message or via a Measurement Report Message containing a Report Predict indicator.
3. In Paragraph 1, A method further comprising the step of transmitting terminal capability information to the base station, wherein the terminal capability information comprises at least one of an indicator indicating whether to support Radio Resource Management (RRM) measurement prediction, an indicator indicating whether to support direct measurement event prediction, and an indicator indicating whether to support indirect measurement event prediction.
4. In Paragraph 1, The above event prediction configuration information includes reporting configuration information (ReportConfig), and The above-mentioned reporting configuration information indicates an event-triggered method and includes an indicator that causes the event-trigger configuration information (eventTriggerConfig) corresponding to the event-triggered method to perform measurement and reporting actions based on event prediction, or The above-mentioned reporting configuration information indicates an event predicted method, and the event predicted configuration information (eventPredictConfig) corresponding to the above-mentioned event predicted method includes at least one of TimeToTrigger, event threshold information, a prediction window, and a prediction operation indicator of a Direct method or an Indirect method. If the above report setting information indicates an event-triggered method, Transmit a first measurement report message based on the prediction of the occurrence of the above measurement event, and do not transmit a second measurement report message based on the measurement; Transmitting the first measurement report message based on the prediction of the occurrence of the above measurement event and the second measurement report message based on the above measurement; or A method characterized by transmitting a first measurement report message based on the prediction of the occurrence of the measurement event or a second measurement report message based on the measurement, based on the settings of the base station.
5. In Paragraph 1, The method further includes the step of transmitting a subsequent event prediction report message to the above base station, A method characterized in that the above-mentioned subsequent event prediction report message includes at least one of information for canceling the predicted event occurrence within the information related to the prediction of the measurement event occurrence, information for confirming the predicted event occurrence, or information for indicating whether the event entry conditions of the predicted event are satisfied.
6. In a method performed by a base station in a wireless communication system, A step of transmitting event prediction setting information to a terminal, The method includes the step of receiving information related to the prediction of a measurement event occurrence from the above terminal, The occurrence of the above measurement event is predicted through artificial intelligence and machine learning based on the above event prediction setting information, and A method characterized in that the prediction of the occurrence of the above-mentioned measurement event corresponds to either a direct method or an indirect method.
7. In Paragraph 6, The method further includes the step of transmitting terminal capability information to the base station, wherein the terminal capability information includes at least one of an indicator indicating whether to support Radio Resource Management (RRM) measurement prediction, an indicator indicating whether to support direct measurement event prediction, and an indicator indicating whether to support indirect measurement event prediction. Information related to the prediction of the occurrence of the above event is transmitted via a Prediction Report Message or via a Measurement Report Message containing a Report Predict indicator, and Information related to the prediction of the occurrence of the above event includes at least one of a list of target cells where the measurement event is predicted or information on the predicted measurement results of the target cells, and If the prediction of the above event occurrence corresponds to the above Direct method, the cell measurement result in the first time interval is used as the input for model learning to obtain the probability of event occurrence in the second time interval as the output, and the information related to the prediction of the above event occurrence includes the probability of event occurrence. A method characterized in that, when the prediction of the occurrence of the above event corresponds to the above indirect method, the cell measurement result in the first time interval is used as the input for model learning to obtain signal quality prediction information in the second time interval as the output, and the information related to the prediction of the occurrence of the above event includes the time of the event occurrence in the second time interval based on the signal quality prediction information.
8. In paragraph 6, the method further includes the step of receiving a subsequent event prediction report message from the terminal, The above subsequent event prediction report message includes at least one of information for canceling the predicted event occurrence within the information related to the prediction of the measurement event occurrence, information for confirming the predicted event occurrence, or information for indicating whether the event entry conditions of the predicted event are satisfied. The above event prediction configuration information includes reporting configuration information (ReportConfig), and The above-mentioned reporting configuration information indicates an event-triggered method and includes an indicator that causes the event trigger configuration information (eventTriggerConfig) corresponding to the event-triggered method to perform measurement and reporting actions based on event prediction, or The above-mentioned reporting configuration information indicates an event predicted method, and the event predicted configuration information (eventPredictConfig) corresponding to the above-mentioned event predicted method includes at least one of TimeToTrigger, event threshold information, a prediction window, and a prediction operation indicator of a Direct method or an Indirect method. If the above report setting information indicates an event-triggered method, Transmit a first measurement report message based on the prediction of the occurrence of the above measurement event, and do not transmit a second measurement report message based on the measurement; Transmitting the first measurement report message based on the prediction of the occurrence of the above measurement event and the second measurement report message based on the above measurement; or A method characterized by transmitting a first measurement report message based on the prediction of the occurrence of the measurement event or a second measurement report message based on the measurement, based on the settings of the base station.
9. In a terminal in a wireless communication system, A transceiver for transmitting and receiving signals; and It includes a control unit connected to the above-mentioned transmitting and receiving unit, and the control unit, Receive event prediction setting information from the base station, and Based on the above event prediction setting information, the occurrence of a measurement event is predicted through artificial intelligence and machine learning, and the prediction of the occurrence of the measurement event corresponds to either a direct method or an indirect method; and A terminal characterized by transmitting information related to the prediction of the occurrence of the measurement event to the above base station.
10. In Paragraph 9, Information related to the prediction of the occurrence of the above event includes at least one of a list of target cells where the measurement event is predicted or information on the predicted measurement results of the target cells, and If the prediction of the above event occurrence corresponds to the above Direct method, the cell measurement result in the first time interval is used as the input for model learning to obtain the probability of event occurrence in the second time interval as the output, and the information related to the prediction of the above event occurrence includes the probability of event occurrence. If the prediction of the above event occurrence corresponds to the above Indirect method, the cell measurement result in the first time interval is used as the input for model learning to obtain signal quality prediction information in the second time interval as the output, and the information related to the prediction of the above event occurrence includes the time of event occurrence in the second time interval based on the signal quality prediction information. A terminal characterized in that information related to the prediction of the occurrence of the above event is transmitted via a Prediction Report Message or via a Measurement Report Message including a Report Predict indicator.
11. In paragraph 9, the control unit is, A terminal characterized by transmitting terminal capability information to the above-mentioned base station, wherein the terminal capability information includes at least one of an indicator indicating whether to support Radio Resource Management (RRM) measurement prediction, an indicator indicating whether to support direct measurement event prediction, and an indicator indicating whether to support indirect measurement event prediction.
12. In Paragraph 9, The above event prediction configuration information includes reporting configuration information (ReportConfig), and The above-mentioned reporting configuration information indicates an event-triggered method and includes an indicator that causes the event trigger configuration information (eventTriggerConfig) corresponding to the event-triggered method to perform measurement and reporting actions based on event prediction, or The above-mentioned reporting configuration information indicates an event predicted method, and the event predicted configuration information (eventPredictConfig) corresponding to the above-mentioned event predicted method includes at least one of TimeToTrigger, event threshold information, a prediction window, and a prediction operation indicator of a Direct method or an Indirect method. If the above report setting information indicates an event-triggered method, Transmit a first measurement report message based on the prediction of the occurrence of the above measurement event, and do not transmit a second measurement report message based on the measurement; Transmitting the first measurement report message based on the prediction of the occurrence of the above measurement event and the second measurement report message based on the above measurement; or A terminal characterized by transmitting a first measurement report message based on the prediction of the occurrence of the measurement event or a second measurement report message based on the measurement, based on the settings of the base station.
13. In Paragraph 9, The method further includes the step of transmitting a subsequent event prediction report message to the above base station, A terminal characterized by the fact that the above-mentioned subsequent event prediction report message includes at least one of information for canceling the predicted event occurrence within the information related to the prediction of the measurement event occurrence, information for confirming the predicted event occurrence, or information for indicating whether the event entry condition of the predicted event is satisfied.
14. In a base station of a wireless communication system, A transceiver for transmitting and receiving signals; and It includes a control unit connected to the above-mentioned transmitting and receiving unit, and the control unit, Transmit event prediction setting information to the terminal, and Information related to the prediction of measurement event occurrence is received from the above terminal, and The occurrence of the above measurement event is predicted through artificial intelligence and machine learning based on the above event prediction setting information, and A base station characterized by the prediction of the occurrence of the above-mentioned measurement event corresponding to either a direct method or an indirect method.
15. In paragraph 14, the control unit is, To the above base station, terminal capability information is transmitted, and the terminal capability information includes at least one of an indicator indicating whether to support Radio Resource Management (RRM) measurement prediction, an indicator indicating whether to support direct measurement event prediction, and an indicator indicating whether to support indirect measurement event prediction. The terminal receives a subsequent event prediction report message, and the subsequent event prediction report message includes at least one of information for canceling the predicted event occurrence within the information related to the prediction of the measurement event occurrence, information for confirming the predicted event occurrence, or information for indicating whether the event entry condition of the predicted event is satisfied. Information related to the prediction of the occurrence of the above event is transmitted via a Prediction Report Message or via a Measurement Report Message containing a Report Predict indicator, and If the prediction of the above event occurrence corresponds to the above Direct method, the cell measurement result in the first time interval is used as the input for model learning to obtain the probability of event occurrence in the second time interval as the output, and the information related to the prediction of the above event occurrence includes the probability of event occurrence. If the prediction of the above event occurrence corresponds to the above Indirect method, the cell measurement result in the first time interval is used as the input for model learning, and signal quality prediction information in the second time interval is obtained as the output, and the information related to the prediction of the above event occurrence includes the time of event occurrence in the second time interval based on the signal quality prediction information. The above event prediction configuration information includes reporting configuration information (ReportConfig), and The above-mentioned reporting configuration information indicates an event-triggered method and includes an indicator that causes the event-trigger configuration information (eventTriggerConfig) corresponding to the event-triggered method to perform measurement and reporting actions based on event prediction, or The above-mentioned reporting configuration information indicates an event predicted method, and the event predicted configuration information (eventPredictConfig) corresponding to the above-mentioned event predicted method includes at least one of TimeToTrigger, event threshold information, a prediction window, and a prediction operation indicator of a Direct method or an Indirect method. If the above report setting information indicates an event-triggered method, Transmit a first measurement report message based on the prediction of the occurrence of the above measurement event, and do not transmit a second measurement report message based on the measurement; Transmitting the first measurement report message based on the prediction of the occurrence of the above measurement event and the second measurement report message based on the above measurement; or A base station characterized by transmitting a first measurement report message based on the prediction of the occurrence of the measurement event or a second measurement report message based on the measurement, based on the settings of the base station.
