Method and apparatus for performing communication using artificial intelligence and machine learning

Abstract

The present embodiments relate to a method and apparatus for performing communication using artificial intelligence and machine learning, and provide a method comprising the steps of: receiving, from a base station, a message instructing a change in data collection corresponding to at least one associated ID for an AI / ML model; determining whether the at least one associated ID matches an associated ID for the AI / ML model stored in a terminal; and if the at least one associated ID matches the stored associated ID for the AI / ML model, performing data collection corresponding to the matched associated ID to update the AI / ML model for the matched associated ID.

Description

Method and device for performing communication using artificial intelligence and machine learning

[0001] The present embodiments propose a method and apparatus for performing communication using artificial intelligence and machine learning in a next-generation wireless access network (in this disclosure, “5G,” “NR [New Radio],” “5G-Advanced,” “6G,” or a subsequent 3GPP wireless access network).

[0002] Next-generation wireless communication technology is evolving beyond 5G to 6G, aiming to achieve faster data transmission speeds and ultra-low latency compared to 5G in ultra-high frequency ranges such as the terahertz (THz) band. Therefore, technology is advancing toward incorporating artificial intelligence (AI) and machine learning (ML) technologies from the communication system design stage. Consequently, wireless communication systems are establishing a technological foundation to support new services and applications in ultra-high-performance, ultra-low latency, and hyper-connected environments.

[0003] In particular, AI / ML technologies are being introduced in wireless communication networks to optimize network operations and ensure real-time quality. AI / ML can perform a variety of roles, including situational awareness through big data analysis, adaptive utilization of network resources and data, and intelligent, data-driven system optimization. These capabilities can enable efficient resource management and improved service quality in complex wireless environments, where conventional methods have proven limited.

[0004] As part of this aspect, a specific design is needed to enable wireless communication using AI / ML models.

[0005] Embodiments of the present disclosure can provide a method and device for performing communication using artificial intelligence and machine learning in a next-generation wireless access network.

[0006] In one aspect, the present embodiments may provide a method for a user equipment (UE) to perform communication using artificial intelligence and machine learning (AI / ML), the method including: receiving, from a base station, a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model; determining whether the at least one associated ID matches an associated ID for an AI / ML model stored in the UE; and, if the at least one associated ID matches the associated ID for the stored AI / ML model, performing data collection corresponding to the matched associated ID to update the AI / ML model for the matched associated ID.

[0007] In another aspect, the present embodiments may provide a method in which a base station performs communication using artificial intelligence and machine learning (AI / ML), the method including the steps of transmitting a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model to a terminal, transmitting data collection-related configuration information corresponding to the at least one associated ID to the terminal, and transmitting data for data collection of the terminal based on the data collection-related configuration information.

[0008] In another aspect, the present embodiments provide a user equipment (UE) that performs communication using artificial intelligence and machine learning (AI / ML), including a transmitter, a receiver, and a control unit that controls operations of the transmitter and the receiver, wherein the control unit receives, from a base station, a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model, determines whether the at least one associated ID matches an associated ID for an AI / ML model stored in the UE, and, if the at least one associated ID matches an associated ID for the stored AI / ML model, performs data collection corresponding to the matched associated ID to update the AI / ML model for the matched associated ID.

[0009] In another aspect, the present embodiments provide a base station that performs communication using artificial intelligence and machine learning, including a transmitter, a receiver, and a control unit that controls operations of the transmitter and the receiver, wherein the control unit transmits a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model to a terminal, transmits data collection-related configuration information corresponding to at least one associated ID to the terminal, and transmits data for data collection of the terminal based on the data collection-related configuration information.

[0010] According to the present embodiments, a method and device for performing communication using artificial intelligence and machine learning in a next-generation wireless access network can be provided.

[0011] Additionally, according to the present embodiments, when the network-side conditions applied by the terminal for model training are changed, the change is notified prior to model inference, thereby enabling the model to perform an efficient update.

[0012] In addition, according to the present embodiments, by performing model update before performing model inference, it is possible to prevent model performance degradation during model inference that may occur due to different network-side condition settings between model training and inference.

[0013] FIG. 1 is a schematic diagram illustrating the structure of an NR wireless communication system to which the present embodiment can be applied.

[0014] FIG. 2 is a drawing for explaining a frame structure in an NR system to which the present embodiment can be applied.

[0015] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0016] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0017] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0018] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0019] Figure 7 is a drawing for explaining CORESET.

[0020] FIG. 8 is a diagram illustrating a procedure in which a terminal performs communication using artificial intelligence and machine learning according to one embodiment.

[0021] FIG. 9 is a diagram illustrating a procedure in which a base station performs communication using artificial intelligence and machine learning according to one embodiment.

[0022] FIG. 10 is a diagram for explaining an operation when a related ID is applied to one cell according to one embodiment.

[0023] FIG. 11 is a diagram for explaining an operation when a related ID is applied to multiple cells according to one embodiment.

[0024] FIG. 12 is a diagram for explaining an operation when an association ID according to one embodiment is applied to multiple cells and a change instruction message is configured for multiple cells.

[0025] Fig. 13 is a drawing showing the configuration of a terminal according to another embodiment.

[0026] Fig. 14 is a drawing showing the configuration of a base station according to another embodiment.

[0027] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to exemplary drawings. When adding reference numerals to components in each drawing, identical components may have the same numerals as much as possible even if they are shown in different drawings. In addition, when describing the present embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the technical idea of ​​the present invention, the detailed description may be omitted. When "includes," "has," "consists of," etc. are used in this specification, other parts may be added unless "only" is used. When a component is expressed in the singular, it may include a case in which the plural is included unless specifically stated otherwise.

[0028] Additionally, terms such as first, second, A, B, (a), (b), etc. may be used to describe components of the present disclosure. These terms are only intended to distinguish the components from other components, and the nature, order, sequence, or number of the components are not limited by the terms.

[0029] In a description of the positional relationship of components, when it is described that two or more components are "connected," "combined," or "connected," it should be understood that the two or more components may be directly "connected," "combined," or "connected," but that the two or more components may also be further "interposed" with another component to be "connected," "combined," or "connected." Here, the other component may be included in one or more of the two or more components that are "connected," "combined," or "connected" to each other.

[0030] In the description of the temporal flow relationship related to components, operation methods, or manufacturing methods, for example, when the temporal or flow relationship is described as “after”, “following”, “next to”, “before”, etc., it may also include cases where it is not continuous, unless “immediately” or “directly” is used.

[0031] Meanwhile, when numerical values ​​or corresponding information (e.g., levels, etc.) for components are mentioned, even without separate explicit description, the numerical values ​​or corresponding information may be interpreted as including an error range that may occur due to various factors (e.g., process factors, internal or external impact, noise, etc.).

[0032] The wireless communication system in this specification refers to a system for providing various communication services such as voice, data packets, etc. using wireless resources, and may include a terminal, a base station, or a core network.

[0033] The embodiments disclosed below can be applied to wireless communication systems using various wireless access technologies. For example, the embodiments can be applied to various wireless access technologies such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), or NOMA (non-orthogonal multiple access). In addition, the wireless access technology may not only refer to a specific access technology, but also to each generation of communication technologies established by various communication agreement organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTSterrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink. Thus, the present embodiments can be applied to currently disclosed or commercialized wireless access technologies, as well as wireless access technologies currently under development or to be developed in the future.

[0034] Meanwhile, the term "terminal" in this specification is a comprehensive concept that refers to a device that includes a wireless communication module that performs communication with a base station in a wireless communication system, and should be interpreted as a concept that includes not only UE (User Equipment) in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio), but also MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), and wireless device in GSM. In addition, the terminal may be a user portable device such as a smartphone depending on the usage type, and in a V2X communication system, it may mean a vehicle, a device including a wireless communication module in the vehicle, etc. In addition, in the case of a Machine Type Communication system, it may mean an MTC terminal, M2M terminal, URLLC terminal, etc. that is equipped with a communication module to perform machine type communication.

[0035] The base station or cell in this specification refers to an end that communicates with a terminal in terms of a network, and includes various coverage areas such as Node-B, eNB (evolved Node-B), gNB (gNode-B), LPN (Low Power Node), Sector, Site, various types of antennas, BTS (Base Transceiver System), Access Point, Point (e.g., Transmission Point, Reception Point, Transmission / Reception Point), Relay Node, Mega Cell, Macro Cell, Micro Cell, Pico Cell, Femto Cell, RRH (Remote Radio Head), RU (Radio Unit), and Small Cell. In addition, a cell may mean including a BWP (Bandwidth Part) in the frequency domain. For example, a serving cell may mean an Activation BWP of a terminal.

[0036] Since the various cells listed above have a base station that controls one or more cells, the base station can be interpreted in two meanings. 1) It can be a device itself that provides a mega cell, macro cell, micro cell, pico cell, femto cell, or small cell in relation to a wireless area, or 2) it can indicate the wireless area itself. In 1), all devices that provide a given wireless area are controlled by the same entity or that interact to cooperatively configure the wireless area are all indicated as a base station. Depending on how the wireless area is configured, a point, a transceiver point, a transmission point, a reception point, etc. can be an embodiment of a base station. In 2), the wireless area itself that receives or transmits a signal from the perspective of a user terminal or a neighboring base station can also be indicated as a base station.

[0037] In this specification, a cell may mean a component carrier having coverage of a signal transmitted from a transmission / reception point or a transmission / reception point itself.

[0038] Uplink (UL, or uplink) refers to a method of transmitting and receiving data from a terminal to a base station, and downlink (DL, or downlink) refers to a method of transmitting and receiving data from a base station to a terminal. Downlink may refer to communication or a communication path from multiple transmission / reception points to a terminal, and uplink may refer to communication or a communication path from a terminal to multiple transmission / reception points. In this case, in the downlink, the transmitter may be part of the multiple transmission / reception points, and the receiver may be part of the terminal. In addition, in the uplink, the transmitter may be part of the terminal, and the receiver may be part of the multiple transmission / reception points.

[0039] Uplink and downlink transmit and receive control information through control channels such as PDCCH (Physical Downlink Control CHannel) and PUCCH (Physical Uplink Control CHannel), and transmit and receive data by configuring data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel). Hereinafter, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also expressed in the form of 'transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH'.

[0040] For clarity of explanation, the technical idea of ​​this invention is described below mainly with reference to the 3GPP LTE / LTE-A / NR (New RAT) communication system, but the technical features of this invention are not limited to the communication system.

[0041] After researching 4G (4th-Generation) communication technology, 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of the next-generation wireless access technology of the ITU-R. Specifically, 3GPP develops LTE-A pro, which enhances LTE-Advanced technology to meet the requirements of the ITU-R, and NR, a new communication technology separate from 4G communication technology. Both LTE-A pro and NR refer to 5G communication technology, and in the following, 5G communication technology will be explained with NR as the focus, unless a specific communication technology is specifically mentioned.

[0042] The operating scenario in NR defines various operation scenarios by adding considerations for satellites, automobiles, and new verticals to the existing 4G LTE scenario, and in terms of service, it supports the eMBB (Enhanced Mobile Broadband) scenario, the mMTC (Massive Machine Communication) scenario that has high terminal density but is deployed over a wide area and requires low data rate and asynchronous access, and the URLLC (Ultra Reliability and Low Latency) scenario that requires high responsiveness and reliability and can support high-speed mobility.

[0043] To meet these scenarios, NR introduces a wireless communication system that incorporates new waveform and frame structure technologies, low latency technologies, support for ultra-high frequency bands (mmWave), and forward compatibility technologies. In particular, NR systems offer various technological changes in terms of flexibility to ensure forward compatibility. The key technical features of NR are described below with reference to the drawings.

[0044]

[0045] <NR 시스템 일반>

[0046] Figure 1 is a schematic diagram illustrating the structure of an NR system to which the present embodiment can be applied.

[0047] Referring to Fig. 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and the NG-RAN is composed of gNBs and ng-eNBs that provide user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for UE (User Equipment). gNBs or gNBs and ng-eNBs are interconnected via the Xn interface. gNBs and ng-eNBs are each connected to the 5GC via the NG interface. The 5GC can be configured to include an AMF (Access and Mobility Management Function) that is responsible for the control plane such as terminal access and mobility control functions, and an UPF (User Plane Function) that is responsible for the control function for user data. NR includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).

[0048] gNB refers to a base station that provides NR user plane and control plane protocol termination to terminals, and ng-eNB refers to a base station that provides E-UTRA user plane and control plane protocol termination to terminals. The base station described in this specification should be understood to encompass both gNB and ng-eNB, and may also be used to refer to gNB or ng-eNB separately as needed.

[0049] <NR 웨이브 폼, 뉴머롤러지 및 프레임 구조>

[0050] NR uses the CP-OFDM waveform with a cyclic prefix for downlink transmission, and CP-OFDM or DFT-s-OFDM for uplink transmission. OFDM technology is easily combined with MIMO (Multiple Input Multiple Output) and offers the advantages of high spectral efficiency and low-complexity receivers.

[0051] Meanwhile, in NR, the requirements for data rates, latency, and coverage differ across the three scenarios mentioned above. Therefore, it is necessary to efficiently satisfy these requirements across the frequency bands that comprise any NR system. To this end, technologies have been proposed to efficiently multiplex radio resources based on multiple different numerologies.

[0052] Specifically, the NR transmission numerator is determined based on the sub-carrier spacing and the cyclic prefix (CP), and is changed exponentially with the μ value being an exponent value of 2 based on 15 kHz, as shown in Table 1 below.

[0053] μ서브캐리어 간격Cyclic prefixSupported for dataSupported for synch015NormalYesYes130NormalYesYes260Normal, ExtendedYesNo3120NormalYesYes4240NormalNoYes

[0054] As shown in Table 1 above, the numerology of NR can be divided into five types according to the subcarrier spacing. This is different from the fixed subcarrier spacing of LTE, one of the 4G communication technologies, at 15 kHz. Specifically, the subcarrier spacing used for data transmission in NR is 15, 30, 60, and 120 kHz, and the subcarrier spacing used for synchronization signal transmission is 15, 30, 12, and 240 kHz. In addition, the extended CP is applied only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR is defined as a 10 ms frame consisting of 10 subframes with the same length of 1 ms. One frame can be divided into half frames of 5 ms, and each half frame contains 5 subframes. In the case of a 15 kHz subcarrier spacing, one subframe consists of one slot, and each slot consists of 14 OFDM symbols. FIG. 2 is a diagram for explaining the frame structure in an NR system to which the present embodiment can be applied. Referring to FIG. 2, a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length of the slot in the time domain may vary depending on the subcarrier spacing. For example, in the case of a numerology with a 15 kHz subcarrier spacing, a slot is composed of 1 ms, which is the same length as a subframe. In contrast, in the case of a numerology with a 30 kHz subcarrier spacing, a slot is composed of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, a subframe and a frame are defined with a fixed time length, and a slot is defined by the number of symbols, so the time length may vary depending on the subcarrier spacing.Meanwhile, NR defines slots as the basic scheduling unit and also introduces mini-slots (or sub-slots, or non-slot-based scheduling) to reduce transmission delay in the wireless section. Using wider subcarrier spacing reduces transmission delay in the wireless section by shortening the length of each slot inversely. Mini-slots (or sub-slots) are designed to efficiently support URLLC scenarios and allow scheduling in units of 2, 4, or 7 symbols.

[0055] Furthermore, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within a single slot. To reduce HARQ delay, a slot structure was defined that allows HARQ ACK / NACKs to be transmitted directly within the transmission slot. This slot structure is referred to as a self-contained structure and will be described in detail.

[0056] NR is designed to support a total of 256 slot formats, of which 62 are used in 3GPP Rel-15. It also supports a common frame structure that configures FDD or TDD frames through various combinations of slots. For example, it supports a slot structure in which all symbols in a slot are set to downlink, a slot structure in which all symbols are set to uplink, and a slot structure in which downlink and uplink symbols are combined. NR also supports data transmission being distributed and scheduled across one or more slots. Therefore, a base station can use a slot format indicator (SFI) to inform a UE whether a slot is a downlink slot, an uplink slot, or a flexible slot. The base station can indicate the slot format by indicating an index of a table configured through UE-specific RRC signaling using the SFI, and can also indicate it dynamically through DCI (Downlink Control Information) or statically or semi-statically through RRC.

[0057] <NR 물리 자원 >

[0058] In relation to physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, and bandwidth parts are considered.

[0059] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be quasi co-located (or quasi co-located) if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on the other antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0060] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0061] Referring to Figure 3, a resource grid may exist for each numeral, as NR supports multiple numerals on the same carrier. Furthermore, resource grids may exist based on antenna ports, subcarrier spacing, and transmission direction.

[0062] A resource block (RB) consists of 12 subcarriers and is defined solely in the frequency domain. Furthermore, a resource element (RE) consists of one OFDM symbol and one subcarrier. Therefore, as shown in Figure 3, the size of a single RB can vary depending on the subcarrier spacing. NR also defines "Point A," which serves as a common reference point for the RB grid, as well as common RBs and virtual RBs.

[0063] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0064] Unlike LTE, where the carrier bandwidth is fixed at 20 MHz, NR sets the maximum carrier bandwidth from 50 MHz to 400 MHz for each subcarrier interval. Therefore, it is not assumed that all terminals will use the entire carrier bandwidth. Accordingly, NR allows terminals to designate bandwidth parts (BWPs) within the carrier bandwidth, as illustrated in Figure 4. Furthermore, bandwidth parts are associated with a single numerology, consist of a subset of consecutive common resource blocks, and can be dynamically activated over time. Each terminal is configured with up to four bandwidth parts for both the uplink and downlink, and data is transmitted and received using the bandwidth parts activated at a given time.

[0065] In the case of a paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of an unpaired spectrum, the downlink and uplink bandwidth parts are set in pairs so that they can share a center frequency to prevent unnecessary frequency re-tuning between downlink and uplink operations.

[0066] <NR 초기 접속>

[0067] In NR, a terminal performs cell search and random access procedures to connect to a base station and perform communication.

[0068] Cell search is a procedure in which a terminal synchronizes to the cell of a corresponding base station, obtains a physical layer cell ID, and obtains system information using the synchronization signal block (SSB) transmitted by the base station.

[0069] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0070] Referring to FIG. 5, SSB is composed of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), each occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

[0071] The terminal receives SSB by monitoring SSB in the time and frequency domain.

[0072] SSB can be transmitted up to 64 times in 5ms. Multiple SSBs are transmitted in different transmission beams within 5ms, and the terminal performs detection assuming that SSBs are transmitted every 20ms based on a specific beam used for transmission. The number of beams that can be used for SSB transmission within 5ms can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted below 3GHz, up to 8 in the frequency band between 3GHz and 6GHz, and up to 64 different beams can be used for SSB transmission in the frequency band above 6GHz.

[0073] SSB contains two symbols in one slot, and the starting symbol and number of repetitions within the slot are determined as follows depending on the subcarrier spacing.

[0074] Meanwhile, unlike SS in conventional LTE, SSB is not transmitted at the center frequency of the carrier bandwidth. This means that SSB can be transmitted even in locations other than the center of the system bandwidth, and when supporting wideband operation, multiple SSBs can be transmitted in the frequency domain. Accordingly, the terminal monitors SSB using the synchronization raster, which is a candidate frequency location for monitoring SSB. The carrier raster, which is the center frequency location information of the channel for initial access, and the synchronization raster are newly defined in NR. The synchronization raster has a wider frequency interval than the carrier raster, which can support the terminal's fast SSB search.

[0075] A UE can obtain the MIB through the PBCH of the SSB. The MIB (Master Information Block) includes the minimum information required for the UE to receive the remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network. In addition, the PBCH may include information on the position of the first DM-RS symbol in the time domain, information for the UE to monitor SIB1 (e.g., SIB1 numerology information, information related to SIB1 CORESET, search space information, PDCCH-related parameter information, etc.), offset information between the common resource block and the SSB (the absolute position of the SSB within the carrier is transmitted through SIB1), etc. Here, the SIB1 numerology information is also applied equally to some messages used in the random access procedure for the UE to access the base station after completing the cell search procedure. For example, the numerology information of SIB1 may be applied to at least one of messages 1 to 4 for the random access procedure.

[0076] The aforementioned RMSI may refer to SIB1 (System Information Block 1), and SIB1 is broadcast periodically (e.g., every 160 ms) in the cell. SIB1 contains information necessary for the UE to perform the initial random access procedure and is periodically transmitted via PDSCH. In order for the UE to receive SIB1, it must receive numerology information used for SIB1 transmission and CORESET (Control Resource Set) information used for SIB1 scheduling via PBCH. The UE checks scheduling information for SIB1 using SI-RNTI in CORESET and acquires SIB1 on PDSCH according to the scheduling information. The remaining SIBs, excluding SIB1, may be transmitted periodically or upon request of the UE.

[0077] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0078] Referring to FIG. 6, once cell search is complete, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted via the PRACH. Specifically, the random access preamble is transmitted to the base station via the PRACH, which consists of consecutive radio resources in a specific slot that is periodically repeated. Generally, when a terminal initially accesses a cell, a contention-based random access procedure is performed, and when performing random access for beam failure recovery (BFR), a non-contention-based random access procedure is performed.

[0079] The terminal receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), an UL Grant (uplink radio resource), a temporary C-RNTI (Temporary Cell - Radio Network Temporary Identifier), and a TAC (Time Alignment Command). Since one random access response may include random access response information for one or more terminals, the random access preamble identifier may be included to indicate which terminal the included UL Grant, temporary C-RNTI, and TAC are valid for. The random access preamble identifier may be an identifier for the random access preamble received by the base station. The TAC may be included as information for the terminal to adjust uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, i.e., an RA-RNTI (Random Access - Radio Network Temporary Identifier).

[0080] Upon receiving a valid random access response, the terminal processes the information contained in the random access response and performs scheduled transmission to the base station. For example, the terminal applies TAC and stores a temporary C-RNTI. Furthermore, using the UL Grant, the terminal transmits data stored in its buffer or newly generated data to the base station. In this case, information that identifies the terminal must be included.

[0081] Finally, the terminal receives a downlink message for contention resolution.

[0082] <NR CORESET>

[0083] The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) with a length of 1 to 3 symbols, and transmits uplink / downlink scheduling information, SFI (Slot format Index), and TPC (Transmit Power Control) information.

[0084] To ensure system flexibility, NR introduced the CORESET concept. CORESET (Control Resource Set) refers to time-frequency resources for downlink control signals. A terminal can decode control channel candidates using one or more search spaces within the CORESET time-frequency resources. A QCL (Quasi CoLocation) assumption is established for each CORESET, which is used to inform the characteristics of analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay assumed by the conventional QCL.

[0085] Figure 7 is a drawing for explaining CORESET.

[0086] Referring to Figure 7, a CORESET can exist in various forms within the carrier bandwidth within a single slot, and in the time domain, a CORESET can consist of up to three OFDM symbols. In addition, a CORESET is defined as a multiple of six resource blocks up to the carrier bandwidth in the frequency domain.

[0087] The first CORESET is indicated via the MIB as part of the initial bandwidth part configuration, allowing the terminal to receive additional configuration and system information from the network. After establishing a connection with the base station, the terminal can receive and configure one or more CORESET information via RRC signaling.

[0088] In this specification, the terms frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals or various messages related to NR (New Radio) may be interpreted in the past or present meaning or in various meanings used in the future.

[0089] Wider bandwidth operations

[0090] Existing LTE systems supported scalable bandwidth operation for any LTE Component Carrier (CC). That is, depending on the deployment scenario, any LTE operator could configure a single LTE CC with a bandwidth ranging from a minimum of 1.4 MHz to a maximum of 20 MHz, and a normal LTE terminal supported transmission and reception capabilities of 20 MHz bandwidth for a single LTE CC.

[0091] However, in the case of NR, the design is made to support NR terminals with different transmission and reception bandwidth capabilities through a single wideband NR CC, and accordingly, it is required to configure one or more bandwidth parts (BWP, bandwidth part(s)) consisting of segmented bandwidths for any NR CC, and to support flexible wider bandwidth operation through different bandwidth part configurations and activations for each terminal.

[0092] Specifically, in NR, one or more bandwidth parts can be configured through one serving cell configured from the terminal's perspective, and the terminal is defined to activate one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) in the serving cell to use them for uplink / downlink data transmission and reception. In addition, when multiple serving cells are configured in the terminal, that is, for the terminal to which CA is applied, it is defined to activate one downlink bandwidth part and / or uplink bandwidth part for each serving cell to use the radio resources of the serving cell to use them for uplink / downlink data transmission and reception.

[0093] Specifically, an initial bandwidth part for an initial access procedure of a terminal in an arbitrary serving cell is defined, one or more UE-specific bandwidth part(s) are configured for each terminal through dedicated RRC signaling, and a default bandwidth part for a fallback operation can also be defined for each terminal.

[0094] However, it can be defined that multiple downlink and / or uplink bandwidth parts can be activated and used simultaneously depending on the capability and bandwidth part(s) configuration of the terminal in any serving cell, but in NR rel-15, it is defined that only one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) can be activated and used in any terminal at any time.

[0095]

[0096] The present disclosure relates to a method for ensuring consistency of network (NW) or UE conditions between training and inference in a system that performs wireless communication using an AI / ML model, when a model trained based on data collected from the network (NW) is applied to inference. In particular, the present disclosure proposes a method for notifying a terminal of a change in a network-side additional condition corresponding to a specific associated ID. The terminal, upon receiving this change, performs a model update for the relevant model.

[0097] The following terms can be defined for AI / ML-based wireless communications:

[0098] Data collection refers to the process by which network nodes, management entities, or UEs collect data for the purpose of AI / ML model training, data analysis, and inference.

[0099] An AI / ML model (hereinafter also referred to as a "model") is a data-driven algorithm that applies AI / ML technology to generate a series of outputs based on a series of inputs. AI / ML model training refers to the process of training an AI / ML model in a data-driven manner by learning input / output relationships and obtaining a trained AI / ML model for inference. AI / ML model inference refers to the process of using a trained AI / ML model to generate a series of outputs based on a series of inputs. AI / ML model validation refers to the subprocess of training that evaluates the quality of an AI / ML model using a dataset different from the one used for model training. AI / ML model testing refers to the subprocess of training that evaluates the performance of the final AI / ML model using a dataset different from the one used for model training and validation. Unlike AI / ML model validation, testing does not assume subsequent adjustments to the model.

[0100] The UE-side (AI / ML) model refers to an AI / ML model where inference is performed entirely in the UE. The Network-side (AI / ML) model refers to an AI / ML model where inference is performed entirely in the network. The One-sided (AI / ML) model refers to either the UE-side (AI / ML) model or the network-side (AI / ML) model. The Two-sided (AI / ML) model refers to a pair of AI / ML models where joint inference is performed. Here, joint inference consists of AI / ML inference where inference is performed jointly across the UE and the network. That is, the first part of inference is performed first by the UE and the remaining part by the gNB or vice versa.

[0101] AI / ML model transfer refers to the transmission of an AI / ML model over a wireless interface, either with parameters of a model structure known to the receiver or with a new model with parameters. The transfer may include a complete model or a partial model. Model download refers to the transmission of a model from the network to the UE. Model upload refers to the transmission of a model from the UE to the network.

[0102] Federated learning / federated training refers to a machine learning technique that trains AI / ML models on multiple distributed edge nodes (e.g., UEs, gNBs), each performing local model training using local data samples. This requires multiple model interactions but does not require the exchange of local data samples. Offline field data refers to data collected in the field and used for offline training of AI / ML models. Online field data refers to data collected in the field and used for online training of AI / ML models.

[0103] Model monitoring refers to the process of monitoring the inference performance of AI / ML models.

[0104] Supervised learning refers to the process of training a model using inputs and their corresponding labels. Unsupervised learning refers to the process of training a model without labeled data. Semi-supervised learning refers to the process of training a model using a mixture of labeled and unlabeled data. Reinforcement learning (RL) refers to the process of training an AI / ML model from inputs (i.e., states) and feedback signals (i.e., rewards) resulting from the model's outputs (i.e., actions) in an environment in which the model interacts.

[0105] Model activation refers to activating an AI / ML model for a specific function. Model deactivation refers to deactivating an AI / ML model for a specific function. Model switching refers to deactivating the currently activated AI / ML model and activating a different AI / ML model for a specific function.

[0106] When applying AI / ML models, the following network-UE collaboration levels are considered.

[0107] 1. Level x: No collaboration.

[0108] 2. Level y: Signaling-based collaboration without model transfer.

[0109] 3. Level z: Signal-based collaboration through model transfer.

[0110] In relation to life cycle management (LCM) procedures for AI / ML models, an AI / ML model may have a model ID with relevant information and / or model functionality for at least some AI / ML operations.

[0111] Model selection, activation, deactivation, switching, and replacement for both UE-side and bilateral models may be initiated by the network, if determined by the network, or initiated by the UE and requested by the network. If determined by the UE, the UE's decision may be reported to the network based on events configured by the network.

[0112] For AI / ML-based features / FGs (feature groups), additional conditions refer to all aspects assumed for model learning, but are not part of the terminal capabilities (UE) for the AI / ML-based features / FGs. This does not necessarily mean that additional conditions are explicitly specified. Additional conditions can be divided into two categories: network-side additional conditions and UE-side additional conditions.

[0113] For the inference of the UE-side model, the following options can be taken as possible approaches to ensure consistency between learning and inference with respect to additional NW-side conditions (if identified):

[0114] - Identification of a model to achieve alignment for additional conditions on the NW side between the NW side and the UE side.

[0115] - The model learned under additional conditions is trained in NW and transferred to UE.

[0116] - Provide information and / or instructions to the UE regarding additional conditions on the NW side.

[0117] - Consistency is supported by monitoring (model / feature selection through performance of candidate models / features on UE side by UE and / or NW).

[0118] - Other approaches are not ruled out.

[0119] - It is not denied that different approaches can achieve the same function.

[0120] In relation to data collection, it can be defined as follows:

[0121] For the UE-side AI / ML model on the UE side, the UE reports to the NW its support / preference configuration for downlink reference signal (DL RS) transmission. Regarding data collection trigger / start, data collection can be initiated / triggered by the NW's configuration or by the UE's request for data collection.

[0122] Signaling aspects for data collection, for example, signaling aspects relate to assistance information (if supported), reference signals, content / type of data collected, configuration related to Set A and / or Set B, and information about the association / mapping of Set A and Set B.

[0123] Support information (if available) provided by the network to the UE for UE data collection to classify data for the purpose of differentiating data characteristics. Support information must protect privacy / proprietary information.

[0124] For NW-side AI / ML models on the NW side, reporting-related mechanisms, additional information about the report content, reporting overhead reduction, signals / configuration / measurement / reporting for data collection, e.g., signal aspects are related to support information (if supported), reference signals.

[0125] Regarding data collection for the NW-side AI / ML models of BM-Case1 and BM-Case2, the following approaches for overhead reduction are identified:

[0126] - Omission / selection of collected data

[0127] - Compression of collected data

[0128] - If the purpose of data collection is different, the overhead reduction mechanism and the resulting specification impact may be different.

[0129] - For each LCM purpose, which mechanisms are supported (if any) and their potential specification implications (if any) are the subject of separate discussion.

[0130] Regarding data collection for the NW-side AI / ML models of BM-Case1 and BM-Case2, the following reporting signals for beam-specific aspects may be applied:

[0131] - L1 signal to report collected data

[0132] - Higher-layer signals to report collected data

[0133] - At least not applicable to AI / ML model inference

[0134] - Existing signaling principles (e.g. RSRP reporting on L1) can be reused.

[0135] RAN1 studies model identification type A, including more details related to use cases.

[0136] RAN1 explores the following options for model identification type B as a starting point, including more details relevant to all use cases:

[0137] - MI-Option 1: Model identification along with data collection related configuration and / or instructions.

[0138] - MI-Option 2: Model Identification with Dataset Transfer

[0139] - MI-Option 3: Model identification in model transfer from NW to UE

[0140] - The names (MI-Option 1, MI-Option 2, MI-Option 3) are used for discussion purposes only.

[0141] - Other options are proposed for model identification type B:

[0142] - MI-Option 4: Model Identification through Standardization of Reference Models (for CSI Compression)

[0143] - MI-Option 5: Model Identification through Model Monitoring

[0144] Regarding MI-Option 1 (Model Identification with Data Collection Related Configuration and / or Instructions) of Model Identification Type B, RAN1 further explores the following aspects:

[0145] - Relationship between model ID and data collection related configuration and / or instructions.

[0146] - Information transmitted from NW to UE (if any)

[0147] - Information transmitted from UE to NW (if any)

[0148] - Related procedures

[0149] - Use cases / applicable uses of MI-Option 1

[0150] For Model Identification Type B of MI-Option 1 (including data collection configuration and / or instructions related to model identification), RAN1 further studies the following aspects:

[0151] - Relationship between model ID and data collection related configuration and / or instructions.

[0152] - Information transmitted from the network (NW) to the UE (if any)

[0153] - Information transmitted from UE to network (NW) (if any)

[0154] - Use cases where MI-Option 1 is used or applicable

[0155] From a RAN1 perspective, for a UE-side model developed (e.g., trained, updated) on the UE side, the following procedure is an example (AI-Example 1) for further study (including feasibility / necessity) of MI-Option 1.

[0156] - A: For data collection, NW signals the data collection related configuration and its / their associated ID.

[0157] An association ID for each sub-use case associated with the NW-side additional conditions.

[0158] - B: UE collects data corresponding to the associated ID.

[0159] - C: AI / ML models are developed (e.g., trained, updated) on the UE side based on collected data corresponding to the associated ID.

[0160] - D: The UE reports its AI / ML model information corresponding to the associated ID to the NW. A model ID is determined / assigned for each AI / ML model.

[0161] Relationship between Model ID and Association ID

[0162] How the model ID is determined / assigned, e.g., NW assigns the model ID, UE assigns / reports the model ID, or the association ID is considered as the model ID, and "for each AI / ML model, a model ID is determined / assigned" in D is not required, and the model ID is determined according to predefined rules.

[0163] D is to facilitate AI / ML model inference.

[0164] Additional interactions of steps A / B / C and association IDs between UE and NW can be considered as other solutions for consistency resolution without model identification.

[0165] With respect to the association ID, the UE assumes that the NW-side additional conditions with the same association ID are consistent at least within the cell. Further research is needed to determine whether and how the UE's assumption can be applied across multiple cells (including feasibility studies).

[0166] To ensure consistency of NW-side additional conditions throughout the learning and inference of the UE-side models for BM-Case 1 and BM-Case 2, either association ID-based or performance monitoring-based methods can be defined.

[0167]

[0168] Currently, 3GPP is considering an associated ID-based scheme to ensure the consistency of network-side additional conditions applied between UE-sided model inference and training. Associated IDs are associated with NW-side additional conditions associated with data used to train AI / ML models. If there are data sets for different NW-side additional conditions, this means that they are mapped to different associated IDs. Associated IDs are defined as consistent within at least one cell and can be applied to multiple cells. The term "associated ID" in this disclosure is merely an example and is not limited to that term.

[0169] Following discussions on model IDs, an example procedure for associated IDs was agreed upon. According to this procedure, a terminal entering a cell receives the associated ID provided by the cell and related data collection configuration information from the base station, and performs model training / update by collecting the data. If the terminal identifies data information for an associated ID for which training has not been performed, the terminal can perform data collection and train a new model based on the collected data corresponding to the new associated ID. However, if a trained model corresponding to the associated ID for the NW-side additional condition of the cell exists among the models stored in the terminal's storage, the terminal can perform communication using the model by sharing this information with the base station. However, if some of the settings for the NW-side additional condition for the associated ID are changed on the NW side, the terminal operation according to the base station's associated ID operation method needs to be newly defined.

[0170] According to the discussion so far, a terminal develops (i.e., trains) arbitrary models by collecting data corresponding to arbitrary associated IDs and stores them in its storage. Before the terminal performs communication using a specific model inference, it first checks whether the condition(s) of the corresponding NW are identical to the settings assumed during the training of the corresponding model. At this time, the associated ID corresponding to the trained model (stored in the terminal) can be used to check for additional NW-side conditions. In other words, the terminal and the base station will share applicable associated ID information in advance before model inference. In other words, the terminal needs to notify the base station of the associated ID information for its trained model, and the base station needs to notify the terminal of the associated ID information applicable to the NW-side condition information that it can currently provide to the terminal. If the base station determines that it can guarantee the same conditions / configurations as the conditions for the associated ID(s) corresponding to the trained model of the terminal, it provides the terminal with configuration information for model inference based on settings consistent with the conditions for the corresponding associated ID.

[0171] However, if the NW side changes the NW-side additional condition for any associated ID, it is necessary to notify the terminal(s) of the change in the NW-side additional condition(s) for models trained with data corresponding to the associated ID. The terminals will need to update already trained / stored AI / ML models based on the received information. Accordingly, we will describe in detail the update method for models trained based on associated IDs.

[0172] Below, a method of performing communication using artificial intelligence and machine learning will be described with reference to relevant drawings.

[0173] FIG. 8 is a diagram illustrating a procedure (800) in which a terminal performs communication using artificial intelligence and machine learning according to one embodiment.

[0174] Referring to FIG. 8, the terminal can receive a change instruction message for data collection corresponding to at least one associated ID for the AI / ML model from the base station (S810).

[0175] As described above, the terminal stores one or more trained AI / ML models corresponding to one or more associated IDs. The terminal can train the AI / ML model by collecting data corresponding to at least one associated ID. When an additional network-side condition indicated by at least one associated ID assumed during the training of the AI / ML model changes, the terminal can receive a change instruction message for data collection corresponding to at least one associated ID from the base station. In one example, the change instruction message for data collection may include an indicator indicating update information or version information of the associated ID.

[0176] A change instruction message for data collection may be received via a specified system information block or paging message, or as a terminal-specific message.

[0177] For example, a terminal may receive system information, including associated ID information that it can support and corresponding version information or update information, broadcast from a base station. If the associated ID and its corresponding version information or update information are broadcast through system information, they may be transmitted through a newly configured SIB-x for the AI / ML model. Alternatively, the associated ID and its corresponding version information or update information may be configured and transmitted within a message of one of the existing SIBs. Alternatively, the associated ID and its corresponding version information or update information may be transmitted via a paging message.

[0178] Version information can be defined as n bits in size, and its size can be defined in various ways depending on the amount of information, the update frequency, or the scope of application of the associated ID. That is, if only the update for the corresponding associated ID is indicated, the version information can be defined as a 1-bit instruction, where a 1 indicates that the information for the associated ID has been updated, and a 0 indicates that there has been no update.

[0179] Alternatively, the presence of an association ID can be indicated by the inclusion of an association ID in a message indicating an update, i.e., a change instruction message for data collection. If an association ID is included in the message, this indicates an update for that ID; if not, this indicates no update for that ID. Alternatively, n-bit version information can be used to indicate an update to terminals, meaning that the version information for the association ID changes with each update.

[0180] In addition, when whether or not to update an associated ID is transmitted as system information, the method of transmitting the update information may be indicated in one step or in two separate steps. When indicated in one step, the system information may include updated associated ID information and / or configuration information for transmitting data associated therewith. The updated associated ID information may be expressed as ID information for the updated associated ID, or may be set to 1 only for the updated ID using a bitmap. The data collection-related configuration information for the updated associated ID may include data transmission start / end time and window information, and data-related resource information for each associated ID for which an update is indicated. Here, the term data collection-related configuration information is not limited thereto and may be referred to as other terms such as configuration information for data transmission, data collection-related configuration information, etc.

[0181] When instructed in two steps, the system information only includes information notifying that there is an update to the associated ID, and the terminal receiving this can receive the updated associated ID and the associated data collection-related configuration information by receiving an additional SIB or RRC message related thereto. That is, when notifying whether or not an update to the associated ID is made using a broadcast message such as paging, a 1-bit indicator indicating that there is an update to the associated ID can be included in the paging message. The terminal receiving this can confirm which ID has been specifically changed by receiving a related additional message, and if an update to the associated ID corresponding to the model stored in the terminal is confirmed, the terminal can perform a model update by receiving the related data configuration information. Here, the updated associated ID information and the associated data collection-related configuration information included in the second message can be identical to the contents instructed in the single step.

[0182] While the above description describes that change instructions for data collection are received via broadcast messages, this is not limited to this scenario. If necessary, the base station may transmit a message containing version or update information regarding the base station's associated ID to a terminal supporting the AI / ML model in a UE-specific manner.

[0183] Referring again to FIG. 8, the terminal determines whether at least one association ID matches the association ID for the AI / ML model stored in the terminal (S820), and if at least one association ID matches the association ID for the stored AI / ML model, data collection corresponding to the matched association ID can be performed to update the AI / ML model for the matched association ID (S830).

[0184] For example, if the association ID is applied only within one cell, the terminal may check whether at least one of the association IDs in the change instruction message for data collection matches an association ID corresponding to a model stored in the terminal.

[0185] In this case, if the base station determines that there is a change in the network-side condition information corresponding to at least one associated ID, it may transmit a data collection change instruction message including an indicator indicating that there is an update to the associated ID. The data collection change instruction message may include updated associated ID information, including one bit of instruction information or indicating whether to update by including the ID.

[0186] Additionally, the base station may transmit data collection-related configuration information corresponding to the updated association ID, including data transmission start / end time information or window information. This configuration information may be transmitted simultaneously with or sequentially with the data collection change instruction message.

[0187] If a matching ID exists, the terminal can receive configuration information related to data collection for the associated ID and perform data collection based on the received configuration information. The terminal can then perform model updates based on the collected data.

[0188] For example, if at least one association ID is applied in multiple cells, i.e., if one association ID is applied identically in multiple cells, the terminal can determine whether the version information of at least one association ID matches the version information of the association ID for the AI / ML model stored in the terminal.

[0189] In this case, the base station may periodically broadcast a change instruction message for data collection that includes the supported association IDs and version information for each ID.

[0190] If an association ID with a different version exists, the terminal may transmit a message to the base station requesting configuration information related to data collection for that association ID. The base station may transmit configuration information related to data collection corresponding to the updated association ID, including data transmission start / end time information or window information. The terminal may perform data collection based on the configuration information received from the base station. In this case, the base station may transmit data for data collection by the terminal based on the transmitted configuration information.

[0191] The terminal can perform model updates based on collected data. The terminal can change / save / update the version information associated with the updated model ID to the most recent version.

[0192] For example, if at least one association ID is applied in multiple cells and a change instruction message for data collection is configured for multiple cells, i.e., if the change instruction message for data collection includes information on whether to change the association ID for all of the multiple cells, the terminal can determine whether the association ID supported in the serving cell among at least one association ID matches the association ID for the AI / ML model stored in the terminal.

[0193] In this case, the terminal can receive a change instruction message for data collection from the base station, including whether to update all association IDs. That is, if there is information about at least one updated association ID from all base stations that can apply the same association ID, the message can be broadcast regardless of whether the serving cell can support data transmission corresponding to the updated association ID. If the total number of association IDs is M, it can be indicated by bitmap information of size M bits, or it can be indicated based on whether ID information for the updated association ID is included.

[0194] The terminal can check whether the updated association ID received matches the association ID corresponding to the stored model. If a matching association ID exists, the terminal can turn on an internal parameter indicating that data collection / transmission corresponding to that association ID is required.

[0195] The terminal can then receive information about the association ID supported by the serving base station from the base station. An association ID supported by the base station may indicate that the base station is capable of providing data corresponding to that association ID. The terminal can verify whether the association ID for which the update requirement for the stored / trained model is ON matches the association ID supported by the base station.

[0196] If a matching association ID exists, the terminal may transmit a message to the base station requesting configuration information related to data collection for the corresponding association ID. The base station may transmit data collection-related configuration information corresponding to the updated association ID, including data transmission start / end time information or window information. The terminal may perform data collection based on the configuration information received from the base station. In this case, the base station may transmit data for data collection by the terminal based on the transmitted configuration information.

[0197] The terminal can perform model updates based on collected data. The terminal can store / change an internal parameter to OFF, indicating the need to collect / transmit data related to the updated model's associated ID.

[0198] According to this, a method and device for performing communication using artificial intelligence and machine learning in a next-generation wireless access network can be provided. Furthermore, if the network conditions applied by a terminal for model training change, the change is notified prior to model inference, enabling efficient model updates. Furthermore, by performing model updates prior to model inference, model performance degradation during model inference, which can occur due to differing network-side condition settings between model training and inference, can be prevented.

[0199]

[0200] FIG. 9 is a diagram illustrating a procedure (900) for a base station to perform communication using artificial intelligence and machine learning according to one embodiment. The descriptions previously described in FIG. 8 may be omitted to avoid redundant explanations. In this case, the omitted content may be substantially equally applied to the base station, as long as it does not conflict with the technical spirit of the invention.

[0201] Referring to FIG. 9, the base station can transmit a change instruction message for data collection corresponding to at least one associated ID for the AI / ML model to the terminal (S910).

[0202] As described above, the terminal stores one or more trained AI / ML models corresponding to one or more associated IDs. The terminal can train the AI / ML model by collecting data corresponding to at least one associated ID. When an additional network-side condition indicated by at least one associated ID assumed during the training of the AI / ML model changes, the base station can transmit a change instruction message for data collection corresponding to at least one associated ID to the terminal. In one example, the change instruction message for data collection may include an indicator indicating update information or version information of the associated ID.

[0203] A change instruction message for data collection may be received via a specified system information block or paging message, or as a terminal-specific message.

[0204] For example, a base station may broadcast system information, including information about the associated IDs it can support and corresponding version information or update information. When the associated ID and its corresponding version information or update information are broadcast via system information, they may be transmitted via a newly configured SIB-x for the AI / ML model. Alternatively, the associated ID and its corresponding version information or update information may be configured and transmitted within a message of one of the existing SIBs. Alternatively, the associated ID and its corresponding version information or update information may be transmitted via a paging message.

[0205] Version information can be defined as n bits in size, and its size can be defined in various ways depending on the amount of information, the update frequency, or the scope of application of the associated ID. That is, if only the update for the corresponding associated ID is indicated, the version information can be defined as a 1-bit instruction, where a 1 indicates that the information for the associated ID has been updated, and a 0 indicates that there has been no update.

[0206] Alternatively, the presence of an association ID can be indicated by the inclusion of an association ID in a message indicating an update, i.e., a change instruction message for data collection. If an association ID is included in the message, this indicates an update for that ID; if not, this indicates no update for that ID. Alternatively, n-bit version information can be used to indicate an update to terminals, meaning that the version information for the association ID changes with each update.

[0207] In addition, when whether or not to update an associated ID is transmitted as system information, the method of transmitting the update information may be indicated in one step or in two separate steps. When indicated in one step, the system information may include updated associated ID information and / or configuration information for transmitting data associated therewith. The updated associated ID information may be expressed as ID information for the updated associated ID, or may be set to 1 only for the updated ID using a bitmap. The data collection-related configuration information for the updated associated ID may include data transmission start / end time and window information, and data-related resource information for each associated ID for which an update is indicated. Here, the term data collection-related configuration information is not limited thereto and may be referred to as other terms such as configuration information for data transmission, data collection-related configuration information, etc.

[0208] When instructed in two steps, the system information only includes information notifying that there is an update to the associated ID, and the terminal receiving this can receive the updated associated ID and the associated data collection-related configuration information by receiving an additional SIB or RRC message related thereto. That is, when notifying whether or not an update to the associated ID is made using a broadcast message such as paging, a 1-bit indicator indicating that there is an update to the associated ID can be included in the paging message. The terminal receiving this can confirm which ID has been specifically changed by receiving a related additional message, and if an update to the associated ID corresponding to the model stored in the terminal is confirmed, the terminal can perform a model update by receiving the related data configuration information. Here, the updated associated ID information and the associated data collection-related configuration information included in the second message can be identical to the contents instructed in the single step.

[0209] While the above description describes that change instructions for data collection are received via broadcast messages, this is not limited to this scenario. If necessary, the base station may transmit a message containing version or update information regarding the base station's associated ID to a terminal supporting the AI / ML model in a UE-specific manner.

[0210] Referring again to FIG. 9, the base station transmits data collection-related configuration information corresponding to at least one associated ID to the terminal (S920), and based on the data collection-related configuration information, can transmit data for data collection of the terminal (S930).

[0211] For example, if the association ID is applied only within one cell, the terminal may check whether at least one of the association IDs in the change instruction message for data collection matches an association ID corresponding to a model stored in the terminal.

[0212] In this case, if the base station determines that there is a change in the network-side condition information corresponding to at least one associated ID, it may transmit a data collection change instruction message including an indicator indicating that there is an update to the associated ID. The data collection change instruction message may include updated associated ID information, including one bit of instruction information or indicating whether to update by including the ID.

[0213] Additionally, the base station may transmit data collection-related configuration information corresponding to the updated association ID, including data transmission start / end time information or window information. This configuration information may be transmitted simultaneously with or sequentially with the data collection change instruction message.

[0214] If a matching ID exists, the terminal can receive configuration information related to data collection for the associated ID and perform data collection based on the received configuration information. The terminal can then perform model updates based on the collected data.

[0215] For example, if at least one association ID is applied in multiple cells, i.e., if one association ID is applied identically in multiple cells, the terminal can determine whether the version information of at least one association ID matches the version information of the association ID for the AI / ML model stored in the terminal.

[0216] In this case, the base station may periodically broadcast a change instruction message for data collection that includes the supported association IDs and version information for each ID.

[0217] If an association ID with a different version exists, the base station may receive a message from the terminal requesting configuration information related to data collection for that association ID. The base station may transmit configuration information related to data collection corresponding to the updated association ID, including data transmission start / end time information or window information. The terminal may perform data collection based on the configuration information received from the base station. In this case, the base station may transmit data for data collection by the terminal based on the transmitted configuration information.

[0218] The terminal can perform model updates based on collected data. The terminal can change / save / update the version information associated with the updated model ID to the most recent version.

[0219] For example, if at least one association ID is applied in multiple cells and a change instruction message for data collection is configured for multiple cells, i.e., if the change instruction message for data collection includes information on whether to change the association ID for all of the multiple cells, the terminal can determine whether the association ID supported in the serving cell among at least one association ID matches the association ID for the AI / ML model stored in the terminal.

[0220] In this case, the base station can transmit a change instruction message for data collection to the terminal, including whether to update all association IDs. That is, if there is information about at least one updated association ID from all base stations that can apply the same association ID, the message can be broadcast regardless of whether the serving cell can support data transmission corresponding to the updated association ID. If the total number of association IDs is M, it can be indicated by bitmap information of size M bits, or it can be indicated based on whether ID information for the updated association ID is included.

[0221] The terminal can check whether the updated association ID received matches the association ID corresponding to the stored model. If a matching association ID exists, the terminal can turn on an internal parameter indicating that data collection / transmission corresponding to that association ID is required.

[0222] The base station can then transmit information about the association IDs supported by the serving base station to the terminal. A supported association ID by the base station may indicate that the base station is capable of providing data corresponding to that association ID. The terminal can verify whether the association ID for which the update requirement for the stored / trained model is ON matches the association ID supported by the base station.

[0223] If a matching association ID exists, the base station may receive a message from the terminal requesting configuration information related to data collection for the corresponding association ID. The base station may transmit data collection-related configuration information corresponding to the updated association ID, including data transmission start / end time information or window information. The terminal may perform data collection based on the configuration information received from the base station. In this case, the base station may transmit data for data collection to the terminal based on the transmitted configuration information.

[0224] The terminal can perform model updates based on collected data. The terminal can store / change an internal parameter to OFF, indicating the need to collect / transmit data related to the updated model's associated ID.

[0225] According to this, a method and device for performing communication using artificial intelligence and machine learning in a next-generation wireless access network can be provided. Furthermore, if the network conditions applied by a terminal for model training change, the change is notified prior to model inference, enabling efficient model updates. Furthermore, by performing model updates prior to model inference, model performance degradation during model inference, which can occur due to differing network-side condition settings between model training and inference, can be prevented.

[0226]

[0227] Below, with reference to the relevant drawings, each embodiment related to a method of performing communication using artificial intelligence and machine learning will be described in detail.

[0228] The associated ID associated with data collection used to train the AI / ML model of a terminal proposed in this disclosure assumes that the same configuration and network-side additional conditions (NW-side additional conditions) apply to one or more cells. This assumes that the same configuration and NW-side additional conditions apply within the same Public Land Mobile Network (PLMN), or that the same information is shared in advance between each base station through predefined configuration information within the specification, or through reception of predefined configuration information from a specific server.

[0229] In more detail, the terminal proposed in the present disclosure can collect data corresponding to any associated ID, and perform model inference after verifying performance through model performance monitoring for an AI / ML model trained using the collected data when entering a cell that provides data for the same associated ID. In addition, the terminal proposed in the present disclosure can perform beam management based on the new model after performing new model training when moving to a cell that does not have a data collection-related setting for the same associated ID, or can operate in fallback mode (i.e., NR beam management mode that does not use the AI / ML model). If the associated ID(s) corresponding to the model stored / trained in the terminal are not supported by the target base station but support data corresponding to a new associated ID for the same functionality / feature, the terminal can perform model training by collecting data for the new associated ID, and the model trained in this way can be defined as a new model. If the target base station does not support the associated ID for the trained model and does not support new associated ID-based data corresponding to the same functionality / feature for the trained model, the terminal may operate in a fallback mode that does not use the AI / ML model.

[0230] The present disclosure proposes a method for notifying a terminal of a change in an NW-side additional condition corresponding to an associated ID provided by the NW side when information corresponding to NW-side conditions assumed during training of a terminal-side AI / ML model is indicated as an associated ID.

[0231] More specifically, the present disclosure provides a method in which a base station, which provides data for terminal-side model training / inference, transmits a message to terminal(s) containing an indicator indicating version (or update) information corresponding to associated ID(s). The terminal(s) receiving this message further collects data corresponding to the received associated ID(s), thereby performing a model update based on the newly collected data.

[0232] The base station proposed in this disclosure broadcasts system information including associated ID(s) information that it can support and corresponding version / update information. Idle / connected UEs check whether the information corresponding to the associated ID(s) for models in their storage matches the version / update information for the associated IDs received. If the version information for any associated ID is different or an update is required, the UE decides to update the corresponding model. If the UE decides to update the model, the UE can transmit a message requesting data transmission / collection including the associated ID to the base station for data collection for the determined associated ID. Based on the request message received from the UE, the base station transmits configuration information for data collection / transmission for the associated ID to the UE, and the UE performs data collection based on the received configuration information, thereby performing a model update.

[0233] The base station may periodically inform UEs of the associated IDs it can support using broadcast messages, such as system information, but is not limited to this. If necessary, the base station may transmit a message containing version / update information about the base station's associated ID(s) to UEs supporting AI / ML models in a UE-specific manner.

[0234] When the associated ID(s) and version / update information thereof proposed in this disclosure are broadcast via system information, they may be transmitted via one of the following messages.

[0235] 1. Transmit via a new SIB-x defined for transmitting AI / ML models; or

[0236] 2. Defined and transmitted within a message of one of the existing SIBs; or

[0237] 3. Transmitted via paging message.

[0238] The proposed version information can be defined as an n-bit size, and its size can be defined in various ways depending on the amount of information, the update frequency, or the scope of application of the associated ID. That is, if only whether the associated ID is updated is indicated, the version information can be defined as a 1-bit indication, and if the indication is 1, it indicates that the information for the associated ID has been updated, and if it is 0, it indicates that there has been no update.

[0239] Alternatively, the presence of an associated ID in the update notification message can be used to indicate whether an update is available. That is, if the message includes an ID for the associated ID, it indicates that an update is available for that ID. If not included, it indicates that there is no update available for that ID. Alternatively, n-bit version information can be used to notify terminals of an update, which means that the version information for the associated ID changes with each update. Upon recognizing a version change, a terminal will receive additional data for the associated ID to update the model, update the version information for the associated ID for the model, and then store it in its storage.

[0240] Additionally, if the update information for the associated ID is transmitted as system information, the method of transmitting the update information can be defined in one of the following two ways.

[0241] 1. 1-step indication method

[0242] A. System information includes updated associated ID information and / or configuration information for data transmission associated therewith.

[0243] i. Updated associated ID information can be expressed as ID information for the updated associated ID, or can be notified by using a bitmap and setting it to 1 only for the updated ID.

[0244] ii. Setting information for data transmission for updated associated ID

[0245] 1. Using the above method, the data transmission start / end time and window information, as well as data-related resource information, can be included for each associated ID for which an update is instructed.

[0246] 2. 2-step indication method

[0247] A. The system information only includes information notifying that there is an update to the associated ID, and the terminal receiving this receives the updated associated ID and the data-related configuration information associated with it through receiving additional SIB or RRC messages related thereto.

[0248] B. That is, when notifying whether an update to the associated ID is available using a broadcast message such as paging, the base station includes a 1-bit indicator in the paging message indicating that the associated ID(s) have been updated. The terminal receiving this confirms which ID(s) have been specifically changed through receiving a related additional message, and if an update to the associated ID(s) corresponding to the model stored in the terminal is confirmed, the terminal performs a model update by receiving related data configuration information.

[0249] C. Here, the updated associated ID information included in the second message and the configuration information for data transmission associated therewith may be identical to those described in the 1-step indication method.

[0250] The following describes embodiments of terminal and base station operations according to the technology of the present disclosure. This describes different operations depending on the method of transmitting updated associated IDs in a cell.

[0251] First, this is Example 1 for a case where the associated ID is applied only within a cell. FIG. 10 is a diagram for explaining the operation when the associated ID is applied in one cell according to one embodiment.

[0252] [Terminal operation]

[0253] - The terminal stores one or more trained model(s) corresponding to one or more associated ID(s).

[0254] - Receive a message containing an indicator (1-bit indication or associated ID) indicating that there is an update for the associated ID(s) from the base station.

[0255] - The terminal checks whether there is an ID among the received ID(s) that matches the associated ID corresponding to its trained / stored model.

[0256] - If the same ID exists, data transmission-related configuration information for the associated ID(s) is received and data collection is performed based on the configuration information.

[0257] - Perform model updates based on collected data.

[0258] [Base station operation]

[0259] - The base station confirms that there is a change in the NW-side condition information corresponding to at least one ID among one or more associated ID(s).

[0260] - The base station transmits a message containing an indicator indicating that there is an update for the associated ID(s).

[0261] This message contains at least one of the following pieces of information:

[0262] Updated associated ID(s) information;

[0263] In this case, it can be defined to include 1-bit indication information or to indicate whether to update with ID.

[0264] Configuration information related to data transmission corresponding to the updated associated ID(s) above.

[0265] Data transmission start / end time information or window information

[0266] The configuration information may be transmitted simultaneously or sequentially with a message containing an indicator indicating whether an update is required.

[0267] - Transmit data to assist in collecting data from the terminal based on the information set above.

[0268] In the case of Example 1, since the associated ID is applicable only within the cell, terminals within the cell can receive change information about it and immediately perform model updates. In order for terminals within the cell to receive all changes to the associated ID, an indicator indicating the change needs to be continuously transmitted within the system information update cycle, and it is desirable to perform data transmission for related data collection after the cycle.

[0269] Next, there is embodiment 2 for a case where an associated ID can be applied in more than one cell (e.g., multiple cells or PLMN or globally) and the base station only transmits whether or not to update the ID supported in the cell. FIG. 11 is a diagram for explaining the operation when an associated ID is applied in multiple cells according to one embodiment.

[0270] [Terminal operation]

[0271] - The terminal stores one or more trained model(s) corresponding to one or more associated ID(s) and version information therefor.

[0272] - Periodically receives a message containing version information for the associated ID(s) from the base station.

[0273] - The terminal checks whether there is an ID among the received ID(s) that does not match the version information for the associated ID(s) corresponding to its trained model.

[0274] - If there are associated ID(s) with different version information, a message requesting data collection / transmission corresponding to the associated ID(s) is transmitted to the base station.

[0275] This contains the relevant associated ID(s) to perform model updates.

[0276] - The terminal receives data transmission-related configuration information corresponding to the associated ID requested from the base station in response to the above request message, and performs data collection based on the configuration information.

[0277] - Perform model updates based on collected data, and change / save / update the version information of the associated ID for the updated model to the most recent information.

[0278] [Base station operation]

[0279] - The base station periodically broadcasts a message containing the associated ID(s) it supports and version information for each ID.

[0280] This message contains at least one of the following pieces of information:

[0281] Information about the associated ID(s) supported by the base station and version information for each associated ID;

[0282] - The base station receives a message from the terminal requesting data collection / transmission corresponding to the associated ID, including at least one associated ID information.

[0283] - The base station transmits to the terminal a message including data transmission-related setting information corresponding to the associated ID received in response to the above request message.

[0284] - Transmit data to assist in collecting data from the terminal based on the information set above.

[0285] In Example 2, although an associated ID can be applied to more than one cell, any base station only reports changes to the associated ID(s) corresponding to the data supported by that cell, and terminals requiring model updates update their models by collecting updated data within that cell. This implies that version information for each associated ID must be continuously / periodically transmitted, even for terminals newly entering the cell.

[0286] Next, there is embodiment 3 for a case where an associated ID can be applied in more than one cell (e.g., defined as Data Area hereinafter) and a base station transmits whether or not to update an associated ID that has changed within the Data Area. FIG. 12 is a diagram for explaining an operation when an associated ID according to one embodiment is applied in multiple cells and a change instruction message is configured for multiple cells.

[0287] [Terminal operation]

[0288] - The terminal stores one or more trained model(s) corresponding to one or more associated ID(s).

[0289] - The terminal receives a message from the base station including whether all associated ID(s) are updated.

[0290] This means that the associated ID(s) must be transmitted to all terminals within the applicable cell.

[0291] That is, this means that if there is information about at least one updated associated ID from all base stations that can apply the same associated ID(s), it is broadcast regardless of whether or not the data transmission corresponding to the updated associated ID is supported.

[0292] If the total number of configurable associated IDs is M, this can be indicated by an M-bit bitmap or by including ID information for updated associated IDs. If the latter method is used, an unincluded associated ID can be understood as indicating no update.

[0293] - The terminal checks whether there is an ID among the updated associated ID(s) received above that matches the associated ID(s) corresponding to its trained model.

[0294] - If a matching associated ID(s) exists, the terminal internal parameter indicating that data collection / transmission corresponding to the associated ID(s) is required is stored as ON.

[0295] - The terminal receives information about the associated ID(s) supported by the serving base station (currently camping on or for which connection setup has been completed) from the base station.

[0296] The associated ID supported by the above base station means that the base station is in a state where it can provide data corresponding to the associated ID.

[0297] - The terminal checks whether the associated ID for its stored / trained model needs to be updated and whether the associated ID that is ON matches the supported associated ID of the base station.

[0298] - If a matching associated ID exists, the terminal transmits a message to the base station requesting data transmission / collection for the associated ID.

[0299] This contains the relevant associated ID(s) to perform model updates.

[0300] - The terminal receives data transmission-related configuration information corresponding to the associated ID requested from the base station in response to the above request message, and performs data collection based on the configuration information.

[0301] - Perform model update based on collected data and save / change to OFF the terminal internal parameter indicating that data collection / transmission for the associated ID for the updated model is required.

[0302] [Base station operation]

[0303] - The base station receives information from another NW entity indicating that there is an update for any associated ID(s).

[0304] - The base station broadcasts a message containing whether or not to update all associated ID(s).

[0305] This means that the associated ID(s) must be transmitted to all terminals within the applicable cell.

[0306] That is, this means that if there is information about at least one updated associated ID from all base stations that can apply the same associated ID(s), it is broadcast regardless of whether or not the data transmission corresponding to the updated associated ID is supported.

[0307] If the total number of configurable associated IDs is M, this can be indicated by an M-bit bitmap or by including ID information for updated associated IDs. If the latter method is used, an unincluded associated ID can be understood as indicating no update.

[0308] - The base station broadcasts information about the associated ID(s) supported by the cell separately from the above update information.

[0309] The associated ID supported by the above base station means that the base station is in a state where it can provide data corresponding to the associated ID to the terminal.

[0310] - The base station receives a message from the terminal requesting data collection / transmission corresponding to the associated ID, including at least one associated ID information.

[0311] - The base station transmits to the terminal a message including data transmission-related setting information corresponding to the associated ID received in response to the above request message.

[0312] - Transmit data to assist in collecting data from the terminal based on the information set above.

[0313] In the case of Example 3, if the associated ID is applicable to one or more cells, and the NW-side settings / conditions for at least one of the associated IDs have changed, the update is notified in all cells to which the associated ID is applicable. In other words, even if the serving cell of the terminal is a cell that cannot support data for the associated ID for which an update is notified, the terminal is notified in advance of whether the associated ID is updated, so that when the terminal enters a cell where data collection is possible in the future, information for updating the model for this is stored in the terminal. When the terminal confirms that it has entered a cell that supports data collection of the model corresponding to the associated ID requiring update, the terminal can perform a model update by transmitting a message to the base station to request data collection for this.

[0314] As described above, the present disclosure enables efficient model updates by notifying the terminal of changes in the network-side conditions applied for model training prior to model inference. This prevents model performance degradation during model inference that may occur due to different network-side condition settings between model training and inference by performing model updates before model inference.

[0315]

[0316] Hereinafter, the configuration of a terminal and a base station capable of performing some or all of the embodiments described with reference to FIGS. 1 to 12 will be described with reference to the drawings. The above description may be omitted to avoid redundant description, and in this case, the omitted content may be substantially equally applied to the following description, as long as it does not contradict the technical spirit of the invention.

[0317] Fig. 13 is a drawing showing the configuration of a terminal (1300) according to another embodiment.

[0318] Referring to FIG. 13, a terminal (1300) according to another embodiment includes a transmitter (1320), a receiver (1330), and a control unit (1310) that controls the transmitter and receiver.

[0319] The control unit (1310) controls the overall operation of the terminal (1300) according to the method of performing communication using artificial intelligence and machine learning necessary to perform the aforementioned embodiments.

[0320] The transmitter (1320) and receiver (1330) are used to transmit and receive signals, messages, and data necessary to perform the above-described embodiments to and from the base station.

[0321] The control unit (1310) may receive, from the base station, a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model. The control unit (1310) may collect data corresponding to at least one associated ID for the AI / ML model to train the AI / ML model. When an additional network-side condition indicated by at least one associated ID assumed during training of the AI / ML model changes, the control unit (1310) may receive, from the base station, a change instruction message for data collection corresponding to at least one associated ID. In one example, the change instruction message for data collection may include an indicator that notifies update information or version information of the associated ID.

[0322] A change instruction message for data collection may be received via a specified system information block or paging message, or as a terminal-specific message.

[0323] For example, the control unit (1310) may receive system information including associated ID information that it can support and corresponding version information or update information broadcast from the base station. When the associated ID and the corresponding version information or update information are broadcast through the system information, they may be transmitted through a newly configured SIB-x for the AI / ML model. Alternatively, the associated ID and the corresponding version information or update information may be configured and transmitted within a message of one of the existing SIBs. Alternatively, the associated ID and the corresponding version information or update information may be transmitted through a paging message.

[0324] Version information can be defined as n bits in size, and its size can be defined in various ways depending on the amount of information, the update frequency, or the scope of application of the associated ID. That is, if only the update for the corresponding associated ID is indicated, the version information can be defined as a 1-bit instruction, where a 1 indicates that the information for the associated ID has been updated, and a 0 indicates that there has been no update.

[0325] Alternatively, the presence of an association ID can be indicated by the inclusion of an association ID in a message indicating an update, i.e., a change instruction message for data collection. If an association ID is included in the message, this indicates an update for that ID; if not, this indicates no update for that ID. Alternatively, n-bit version information can be used to indicate an update to terminals, meaning that the version information for the association ID changes with each update.

[0326] In addition, when whether or not to update an associated ID is transmitted as system information, the method of transmitting the update information may be indicated in one step or in two separate steps. When indicated in one step, the system information may include updated associated ID information and / or configuration information for transmitting data associated therewith. The updated associated ID information may be expressed as ID information for the updated associated ID, or may be set to 1 only for the updated ID using a bitmap. The data collection-related configuration information for the updated associated ID may include data transmission start / end time and window information, and data-related resource information for each associated ID for which an update is indicated. Here, the term data collection-related configuration information is not limited thereto and may be referred to as other terms such as configuration information for data transmission, data collection-related configuration information, etc.

[0327] When instructed in two steps, the system information only includes information notifying that there is an update to the associated ID, and the control unit (1310) receiving this can receive the updated associated ID and the data collection-related configuration information associated therewith through receiving an additional SIB or RRC message related thereto. That is, when notifying whether or not an update to the associated ID is made using a broadcast message such as paging, a 1-bit indicator indicating that there is an update to the associated ID can be included in the paging message. The control unit (1310) receiving this can confirm which ID has been specifically changed through receiving a related additional message, and if it confirms an update to the associated ID corresponding to the model stored in the terminal, it can perform a model update by receiving data configuration information related thereto. Here, the updated associated ID information and the data collection-related configuration information associated therewith included in the second message can be identical to the contents instructed in the single step.

[0328] While the above description describes that change instructions for data collection are received via broadcast messages, this is not limited to this scenario. If necessary, the base station may transmit a message containing version or update information regarding the base station's associated ID to a terminal supporting the AI / ML model in a UE-specific manner.

[0329] The control unit (1310) can determine whether at least one associated ID matches the associated ID for the AI / ML model stored in the terminal. Furthermore, if at least one associated ID matches the associated ID for the stored AI / ML model, the control unit (1310) can perform data collection corresponding to the matched associated ID and update the AI / ML model for the matched associated ID.

[0330] For example, if the association ID is applied only within one cell, the control unit (1310) can check whether at least one of the association IDs of the change instruction message for data collection matches the association ID corresponding to the model stored in the terminal.

[0331] In this case, if the base station determines that there is a change in the network-side condition information corresponding to at least one associated ID, it may transmit a data collection change instruction message including an indicator indicating that there is an update to the associated ID. The data collection change instruction message may include updated associated ID information, including one bit of instruction information or indicating whether to update by including the ID.

[0332] Additionally, the base station may transmit data collection-related configuration information corresponding to the updated association ID, including data transmission start / end time information or window information. This configuration information may be transmitted simultaneously with or sequentially with the data collection change instruction message.

[0333] If a matching ID exists, the control unit (1310) can receive configuration information related to data collection for the corresponding associated ID and perform data collection based on the received configuration information. The control unit (1310) can perform a model update based on the collected data.

[0334] For example, when at least one association ID is applied in multiple cells, i.e., when one association ID is applied identically in multiple cells, the control unit (1310) can determine whether the version information of at least one association ID matches the version information of the association ID for the AI / ML model stored in the terminal.

[0335] In this case, the base station may periodically broadcast a change instruction message for data collection that includes the supported association IDs and version information for each ID.

[0336] If an associated ID with a different version exists, the control unit (1310) may transmit a message to the base station requesting configuration information related to data collection for the associated ID. The base station may transmit configuration information related to data collection corresponding to the updated associated ID, including data transmission start / end time information or window information. The control unit (1310) may perform data collection based on the configuration information received from the base station. In this case, the base station may transmit data for data collection of the terminal based on the transmitted configuration information.

[0337] The control unit (1310) can perform a model update based on the collected data. The control unit (1310) can change / save / update the version information of the associated ID for the updated model to the most recent information.

[0338] For example, if at least one association ID is applied in multiple cells and a change instruction message for data collection is configured for multiple cells, i.e., if the change instruction message for data collection includes information on whether to change the association ID for all of the multiple cells, the control unit (1310) can determine whether an association ID supported in a serving cell among at least one association ID matches an association ID for an AI / ML model stored in a terminal.

[0339] In this case, the control unit (1310) can receive a change instruction message for data collection including whether to update all association IDs from the base station. That is, if there is information about at least one updated association ID from all base stations that can apply the same association ID, the message can be broadcast regardless of whether the serving cell can support data transmission corresponding to the updated association ID. If the total number of association IDs is M, it can be indicated by bitmap information of size M bits, or it can be indicated according to whether ID information for the updated association ID is included.

[0340] The control unit (1310) can check whether an ID among the received updated association IDs matches the association ID corresponding to the stored model. If a matching association ID exists, the control unit (1310) can store an internal terminal parameter indicating the need for data collection / transmission corresponding to the corresponding association ID as ON.

[0341] Thereafter, the control unit (1310) may receive information about the association ID supported by the serving base station from the base station. The association ID supported by the base station may indicate that the base station is in a state capable of providing data corresponding to the association ID. The control unit (1310) may check whether the association ID for which the need for updating the association ID for the stored / trained model is ON matches the association ID supported by the base station.

[0342] If a matching association ID exists, the control unit (1310) may transmit a message to the base station requesting configuration information related to data collection for the corresponding association ID. The base station may transmit configuration information related to data collection corresponding to the updated association ID, including data transmission start / end time information or window information. The control unit (1310) may perform data collection based on the configuration information received from the base station. In this case, the base station may transmit data for data collection of the terminal based on the transmitted configuration information.

[0343] The control unit (1310) can perform a model update based on the collected data. The control unit (1310) can store / change an internal terminal parameter to OFF, indicating that data collection / transmission for the associated ID for the updated model is required.

[0344] According to this, a method and device for performing communication using artificial intelligence and machine learning in a next-generation wireless access network can be provided. Furthermore, if the network conditions applied by a terminal for model training change, the change is notified prior to model inference, enabling efficient model updates. Furthermore, by performing model updates prior to model inference, model performance degradation during model inference, which can occur due to differing network-side condition settings between model training and inference, can be prevented.

[0345] Fig. 14 is a drawing showing the configuration of a base station (1400) according to another embodiment.

[0346] Referring to FIG. 14, a base station (1400) according to another embodiment includes a transmitter (1420), a receiver (1430), and a control unit (1410) that controls the transmitter and receiver.

[0347] The control unit (1410) controls the overall operation of the base station (1400) and the operation of the repeater according to the method of performing communication using artificial intelligence and machine learning necessary to perform the aforementioned embodiments.

[0348] The transmitter (1420) and receiver (1430) are used to transmit and receive signals, messages, and data necessary for performing the aforementioned embodiments to and from the terminal.

[0349] The control unit (1410) may transmit a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model to the terminal. The terminal may collect data corresponding to at least one associated ID for the AI / ML model to train the AI / ML model. If an additional network-side condition indicated by at least one associated ID assumed during training of the AI / ML model changes, the control unit (1410) may transmit a change instruction message for data collection corresponding to at least one associated ID to the terminal. In one example, the change instruction message for data collection may include an indicator notifying update information or version information of the associated ID.

[0350] A change instruction message for data collection may be received via a specified system information block or paging message, or as a terminal-specific message.

[0351] For example, the control unit (1410) may broadcast system information including associated ID information that it can support and corresponding version information or update information. When the associated ID and its corresponding version information or update information are broadcast through the system information, they may be transmitted through a newly configured SIB-x for the AI / ML model. Alternatively, the associated ID and its corresponding version information or update information may be configured and transmitted within a message of one of the existing SIBs. Alternatively, the associated ID and its corresponding version information or update information may be transmitted through a paging message.

[0352] Version information can be defined as n bits in size, and its size can be defined in various ways depending on the amount of information, the update frequency, or the scope of application of the associated ID. That is, if only the update for the corresponding associated ID is indicated, the version information can be defined as a 1-bit instruction, where a 1 indicates that the information for the associated ID has been updated, and a 0 indicates that there has been no update.

[0353] Alternatively, the presence of an association ID can be indicated by the inclusion of an association ID in a message indicating an update, i.e., a change instruction message for data collection. If an association ID is included in the message, this indicates an update for that ID; if not, this indicates no update for that ID. Alternatively, n-bit version information can be used to indicate an update to terminals, meaning that the version information for the association ID changes with each update.

[0354] In addition, when whether or not to update an associated ID is transmitted as system information, the method of transmitting the update information may be indicated in one step or in two separate steps. When indicated in one step, the system information may include updated associated ID information and / or configuration information for transmitting data associated therewith. The updated associated ID information may be expressed as ID information for the updated associated ID, or may be set to 1 only for the updated ID using a bitmap. The data collection-related configuration information for the updated associated ID may include data transmission start / end time and window information, and data-related resource information for each associated ID for which an update is indicated. Here, the term data collection-related configuration information is not limited thereto and may be referred to as other terms such as configuration information for data transmission, data collection-related configuration information, etc.

[0355] When instructed in two steps, the system information only includes information notifying that there is an update to the associated ID, and the terminal receiving this can receive the updated associated ID and the associated data collection-related configuration information by receiving an additional SIB or RRC message related thereto. That is, when notifying whether or not an update to the associated ID is made using a broadcast message such as paging, a 1-bit indicator indicating that there is an update to the associated ID can be included in the paging message. The terminal receiving this can confirm which ID has been specifically changed by receiving a related additional message, and if an update to the associated ID corresponding to the model stored in the terminal is confirmed, the terminal can perform a model update by receiving the related data configuration information. Here, the updated associated ID information and the associated data collection-related configuration information included in the second message can be identical to the contents instructed in the single step.

[0356] While the above description describes that change instructions for data collection are received via broadcast messages, this is not limited to this. If necessary, the control unit (1410) may transmit a message containing version or update information regarding the base station's associated ID in a UE-specific manner to a terminal supporting the AI / ML model.

[0357] The control unit (1410) can transmit data collection-related configuration information corresponding to at least one associated ID to the terminal. In addition, the control unit (1410) can transmit data for data collection of the terminal based on the data collection-related configuration information.

[0358] For example, if the association ID is applied only within one cell, the terminal may check whether at least one of the association IDs in the change instruction message for data collection matches an association ID corresponding to a model stored in the terminal.

[0359] In this case, if the control unit (1410) determines that there is a change in the network-side condition information corresponding to at least one associated ID, it may transmit a change instruction message for data collection that includes an indicator indicating that there is an update to the associated ID. The change instruction message for data collection may include updated associated ID information that includes one bit of instruction information or indicates whether to update by including or not including the ID.

[0360] Additionally, the control unit (1410) may transmit data collection-related configuration information corresponding to the updated association ID, including data transmission start / end time information or window information. The configuration information may be transmitted simultaneously with or sequentially with a change instruction message for data collection.

[0361] If a matching ID exists, the terminal can receive configuration information related to data collection for the associated ID and perform data collection based on the received configuration information. The terminal can then perform model updates based on the collected data.

[0362] For example, if at least one association ID is applied in multiple cells, i.e., if one association ID is applied identically in multiple cells, the terminal can determine whether the version information of at least one association ID matches the version information of the association ID for the AI / ML model stored in the terminal.

[0363] In this case, the control unit (1410) may periodically broadcast a change instruction message for data collection that includes the supported association ID and version information for each ID.

[0364] If an associated ID with a different version information exists, the control unit (1410) may receive a message from the terminal requesting configuration information related to data collection for the associated ID. The control unit (1410) may transmit configuration information related to data collection corresponding to the updated associated ID, including data transmission start / end time information or window information. The terminal may perform data collection based on the configuration information received from the base station. In this case, the control unit (1410) may transmit data for data collection of the terminal based on the transmitted configuration information.

[0365] The terminal can perform model updates based on collected data. The terminal can change / save / update the version information associated with the updated model ID to the most recent version.

[0366] For example, if at least one association ID is applied in multiple cells and a change instruction message for data collection is configured for multiple cells, i.e., if the change instruction message for data collection includes information on whether to change the association ID for all of the multiple cells, the terminal can determine whether the association ID supported in the serving cell among at least one association ID matches the association ID for the AI / ML model stored in the terminal.

[0367] In this case, the control unit (1410) may transmit a change instruction message for data collection, including whether or not to update all association IDs, to the terminal. That is, if there is information about at least one updated association ID from all base stations that can apply the same association ID, the message may be broadcast regardless of whether the serving cell supports data transmission corresponding to the updated association ID. If the total number of association IDs is M, the instruction may be indicated as bitmap information of size M bits, or may be indicated based on whether ID information for the updated association ID is included.

[0368] The terminal can check whether the updated association ID received matches the association ID corresponding to the stored model. If a matching association ID exists, the terminal can turn on an internal parameter indicating that data collection / transmission corresponding to that association ID is required.

[0369] The control unit (1410) can then transmit information about the association ID supported by the serving base station to the terminal. An association ID supported by the base station may indicate that the base station is capable of providing data corresponding to the association ID. The terminal can verify whether the association ID for which the need for an update for the stored / trained model is ON matches the association ID supported by the base station.

[0370] If a matching association ID exists, the control unit (1410) may receive a message from the terminal requesting data collection-related configuration information for the corresponding association ID. The control unit (1410) may transmit data collection-related configuration information corresponding to the updated association ID, including data transmission start / end time information or window information. The terminal may perform data collection based on the configuration information received from the base station. In this case, the control unit (1410) may transmit data for data collection of the terminal based on the transmitted configuration information.

[0371] The terminal can perform model updates based on collected data. The terminal can store / change an internal parameter to OFF, indicating the need to collect / transmit data related to the updated model's associated ID.

[0372] According to this, a method and device for performing communication using artificial intelligence and machine learning in a next-generation wireless access network can be provided. Furthermore, if the network conditions applied by a terminal for model training change, the change is notified prior to model inference, enabling efficient model updates. Furthermore, by performing model updates prior to model inference, model performance degradation during model inference, which can occur due to differing network-side condition settings between model training and inference, can be prevented.

[0373] The above-described embodiments may be supported by standard documents disclosed in at least one of the wireless access systems, IEEE 802, 3GPP, and 3GPP2. That is, steps, components, and parts not described in the present embodiments to clearly illustrate the technical concepts herein may be supported by the above-described standard documents. Furthermore, all terms disclosed in this specification may be explained by the above-described standard documents.

[0374] The embodiments described above may be implemented through various means. For example, the embodiments may be implemented through hardware, firmware, software, or a combination thereof.

[0375] In the case of hardware implementation, the method according to the present embodiments may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), processors, controllers, microcontrollers, or microprocessors.

[0376] When implemented using firmware or software, the methods according to the present embodiments may be implemented in the form of devices, procedures, or functions that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor using various known means.

[0377] Additionally, terms such as "system," "processor," "controller," "component," "module," "interface," "model," or "unit" as described above may generally refer to a computer-related entity, such as hardware, a combination of hardware and software, software, or software in execution. For example, the aforementioned components may be, but are not limited to, a process driven by a processor, a processor, a controller, a control processor, an object, a thread of execution, a program, and / or a computer. For example, both an application running on a controller or a processor and the controller or the processor may be components. One or more components may be within a process and / or thread of execution, and the components may be located on a single device (e.g., a system, a computing device, etc.) or distributed across two or more devices.

[0378] The above description is merely an illustrative example of the technical idea of ​​the present disclosure, and those skilled in the art to which the present disclosure pertains will appreciate that various modifications and variations can be made without departing from the essential characteristics of the technical idea of ​​the present disclosure. In addition, the present embodiments are not intended to limit the technical idea of ​​the present disclosure but rather to explain it, and therefore the scope of the technical idea of ​​the present disclosure is not limited by these embodiments. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included within the scope of the rights of the present disclosure.

[0379] CROSS-REFERENCE TO RELATED APPLICATION

[0380] This patent application claims priority under 35 USC § 119(a) to Korean Patent Application No. 10-2024-0110036, filed in Korea on August 16, 2024, and Korean Patent Application No. 10-2025-0113585, filed in Korea on August 14, 2025, the entire contents of which are incorporated herein by reference. In addition, if this patent application claims priority in countries other than the United States for the same reasons, the entire contents of which are incorporated herein by reference.

Claims

1. A method for a terminal (user equipment; UE) to perform communication using artificial intelligence and machine learning (AI / ML), A step of receiving, from a base station, a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model; A step of determining whether at least one of the above association IDs matches the association ID for the AI / ML model stored in the terminal; and A method comprising the step of performing data collection corresponding to the matched association ID and updating the AI / ML model for the matched association ID when the at least one association ID matches the association ID for the stored AI / ML model.

2. In paragraph 1, The steps for performing the update of the above AI / ML model are: A method for performing data collection corresponding to the matched association ID based on data collection-related configuration information corresponding to the matched association ID received from the base station.

3. In paragraph 1, The change instruction message for the above data collection is: A method of receiving via a predetermined system information block or paging message, or as a terminal-specific message.

4. In paragraph 1, The step of determining whether the associated ID for the AI / ML model stored in the above terminal matches is as follows: A method for determining whether the version information of the at least one association ID matches the version information of the association ID for the AI / ML model stored in the terminal, when the at least one association ID is applied in multiple cells.

5. In paragraph 1, The step of determining whether the associated ID for the AI / ML model stored in the above terminal matches is as follows: A method for determining whether an association ID supported by a serving cell among the at least one association ID matches an association ID for an AI / ML model stored in the terminal, when the at least one association ID is applied in a plurality of cells and a change instruction message for the data collection is configured for the plurality of cells.

6. In a method in which a base station performs communication using artificial intelligence and machine learning (AI / ML), A step of transmitting a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model to a terminal; A step of transmitting data collection-related configuration information corresponding to at least one associated ID to the terminal; and A method comprising a step of transmitting data for data collection of the terminal based on the configuration information related to the data collection.

7. In paragraph 6, The above data collection related configuration information is: A method for transmitting to the terminal when at least one of the above association IDs matches the association ID for the AI / ML model stored in the terminal.

8. In paragraph 6, The change instruction message for the above data collection is: A method of transmitting via a predetermined system information block or paging message, or as a terminal-specific message.

9. In paragraph 6, The change instruction message for the above data collection is: A method including version information of at least one association ID when the at least one association ID is applied to multiple cells.

10. In paragraph 6, The step of transmitting a change instruction message for the above data collection to the terminal is: A method further comprising the step of transmitting an association ID supported by a serving cell among the at least one association ID, when the at least one association ID is applied in a plurality of cells and the change instruction message for the data collection is configured for the plurality of cells.

11. In a terminal (user equipment; UE) that performs communication using artificial intelligence and machine learning (AI / ML), Transmitter; Receiver; and Including a control unit that controls the operation of the above transmitter and receiver, The above control unit, A terminal receiving, from a base station, a change instruction message for data collection corresponding to at least one associated ID for an AI / ML model, determining whether the at least one associated ID matches an associated ID for an AI / ML model stored in the terminal, and, if the at least one associated ID matches an associated ID for the stored AI / ML model, performing data collection corresponding to the matched associated ID to update the AI / ML model for the matched associated ID.

12. In paragraph 11, The above control unit, A terminal that performs data collection corresponding to the matched association ID based on data collection-related configuration information corresponding to the matched association ID received from the base station.

13. In paragraph 11, The change instruction message for the above data collection is: A terminal that receives a predetermined system information block or paging message, or receives a terminal-specific message.

14. In paragraph 11, The above control unit, A terminal that determines whether the version information of the at least one association ID matches the version information of the association ID for the AI / ML model stored in the terminal, when the at least one association ID is applied in multiple cells.

15. In paragraph 11, The above control unit, A terminal that determines whether the association ID supported by the serving cell among the at least one association ID matches the association ID for the AI / ML model stored in the terminal, when the at least one association ID is applied in a plurality of cells and a change instruction message for the data collection is configured for the plurality of cells.

Images