Method and apparatus for supporting network-controlled ai / ML data collection and transfer in a wireless communication system

The method and apparatus for network-controlled AI/ML data collection and transfer in wireless communication systems address the challenges of efficient data management in 6G systems by optimizing network entity selection for data transfer, enhancing communication efficiency and coverage.

WO2026235496A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096676
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-04-07
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing network-controlled AI/ML data collection and transfer, particularly in 6G communication systems, which require advanced technologies to handle the increased number of connected devices and demanding performance requirements such as high data rates and low latency.

Method used

A method and apparatus are provided for network-controlled AI/ML data collection and transfer, involving a second network entity that receives a data transfer request from a first network entity and transmits it to selected third network entities based on predefined criteria, enabling efficient data collection and transfer in a wireless communication system.

Benefits of technology

This approach enhances the efficiency of AI/ML data collection and transfer, optimizing network operations and ensuring seamless communication in 6G systems by selecting appropriate network entities for data transfer, thereby improving coverage and spectral efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096676_12112026_PF_FP_ABST
    Figure KR2026096676_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G communication system or a 6G communication system for supporting higher data rates beyond a 4G communication system such as long term evolution (LTE). There is provided a method of a second network entity (e.g. core NF) in a wireless communication network, the method comprising: receiving, from a first network entity (e.g. AIML entity, AIML model training server), a first data transfer request; and transmitting, to one or more selected third network entities (e.g. base station, UE), a second data transfer request based on the first data transfer request.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR SUPPORTING NETWORK-CONTROLLED AI / ML DATA COLLECTION AND TRANSFER IN A WIRELESS COMMUNICATION SYSTEM

[0001] Certain examples of the present disclosure provide various techniques relating to support of network controlled AIML data collection and transfer, for example within 3rdGeneration Partnership Project (3GPP) 5th Generation (5G) New Radio (NR) and NR-based networks.

[0002] Considering the development of wireless communication from generation to generation, the technologies have been developed mainly for services targeting humans, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th generation) communication systems, it is expected that the number of connected devices will exponentially grow. Increasingly, these will be connected to communication networks. Examples of connected things may include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machines, and factory equipment. Mobile devices are expected to evolve in various form-factors, such as augmented reality glasses, virtual reality headsets, and hologram devices. In order to provide various services by connecting hundreds of billions of devices and things in the 6G (6th generation) era, there have been ongoing efforts to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as beyond-5G systems.

[0003] 6G communication systems, which are expected to be commercialized around 2030, will have a peak data rate of tera (1,000 giga)-level bit per second (bps) and a radio latency less than 100μsec, and thus will be 50 times as fast as 5G communication systems and have the 1 / 10 radio latency thereof.

[0004] In order to accomplish such a high data rate and an ultra-low latency, it has been considered to implement 6G communication systems in a terahertz (THz) band (for example, 95 gigahertz (GHz) to 3THz bands). It is expected that, due to severer path loss and atmospheric absorption in the terahertz bands than those in mmWave bands introduced in 5G, technologies capable of securing the signal transmission distance (that is, coverage) will become more crucial. It is necessary to develop, as major technologies for securing the coverage, Radio Frequency (RF) elements, antennas, novel waveforms having a better coverage than Orthogonal Frequency Division Multiplexing (OFDM), beamforming and massive Multiple-input Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and multiantenna transmission technologies such as large-scale antennas. In addition, there has been ongoing discussion on new technologies for improving the coverage of terahertz-band signals, such as metamaterial-based lenses and antennas, Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS).

[0005] Moreover, in order to improve the spectral efficiency and the overall network performances, the following technologies have been developed for 6G communication systems: a full-duplex technology for enabling an uplink transmission and a downlink transmission to simultaneously use the same frequency resource at the same time; a network technology for utilizing satellites, High-Altitude Platform Stations (HAPS), and the like in an integrated manner; an improved network structure for supporting mobile base stations and the like and enabling network operation optimization and automation and the like; a dynamic spectrum sharing technology via collision avoidance based on a prediction of spectrum usage; an use of Artificial Intelligence (AI) in wireless communication for improvement of overall network operation by utilizing AI from a designing phase for developing 6G and internalizing end-to-end AI support functions; and a next-generation distributed computing technology for overcoming the limit of UE computing ability through reachable super-high-performance communication and computing resources (such as Mobile Edge Computing (MEC), clouds, and the like) over the network. In addition, through designing new protocols to be used in 6G communication systems, developing mechanisms for implementing a hardware-based security environment and safe use of data, and developing technologies for maintaining privacy, attempts to strengthen the connectivity between devices, optimize the network, promote softwarization of network entities, and increase the openness of wireless communications are continuing.

[0006] It is expected that research and development of 6G communication systems in hyper-connectivity, including person to machine (P2M) as well as machine to machine (M2M), will allow the next hyper-connected experience. Particularly, it is expected that services such as truly immersive eXtended Reality (XR), high-fidelity mobile hologram, and digital replica could be provided through 6G communication systems. In addition, services such as remote surgery for security and reliability enhancement, industrial automation, and emergency response will be provided through the 6G communication system such that the technologies could be applied in various fields such as industry, medical care, automobiles, and home appliances.

[0007] The present disclosure provides method and apparatus for supporting network-controlled ai / ml data collection and transfer in a wireless communication system.

[0008] According to an aspect of an exemplary embodiment, there is provided method and apparatus for supporting network-controlled ai / ml data collection and transfer in a wireless communication system.

[0009] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0010] Embodiments / examples of the present disclosure are further described hereinafter with reference to the accompanying drawings, in which:

[0011] FIG. 1 illustrates a procedure for UE / RAN node selection for AIML data collection and / or transfer according to examples of the present disclosure.

[0012] FIG. 2 illustrates a procedure for UE AIML data collection and transfer according to examples of the present disclosure.

[0013] FIG. 3 illustrates an example method of a second network entity (e.g. core NF) in a wireless communication network.

[0014] FIG. 4 illustrates an example method of a third network entity (e.g. base station, UE) in a wireless communication network.

[0015] FIG. 5 illustrates an example method of a first network entity (e.g. AIML entity, AIML model training server) in a wireless communication network.

[0016] FIG. 6 an exemplary network entity that may be used in examples of the present disclosure.

[0017] FIG. 7 is a block diagram of a terminal or user equipment (UE) according to an embodiment of the disclosure.

[0018] FIG. 8 is a block diagram of a base station (BS) according to an embodiment of the disclosure.

[0019] FIG. 9 is a block diagram of a network entity according to an embodiment of the disclosure.

[0020] It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein.

[0021] The present invention is defined in the independent claims. Advantageous features are defined in the dependent claims.

[0022] Embodiments or examples disclosed in the description and / or figures falling outside the scope of the claims are to be understood as examples useful for understanding the present invention.

[0023] According to a first aspect of the disclosure, there is provided a method of a second network entity (e.g. core NF) in a wireless communication network, the method comprising: receiving, from a first network entity (e.g. AIML entity, AIML model training server), a first data transfer request; and transmitting, to one or more selected third network entities (e.g. base station, UE), a second data transfer request based on the first data transfer request.

[0024] According to an example, the first data transfer request includes information indicating one or more candidate third network entities, and wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises: determining the one or more selected third network entities based on the information indicating one or more candidate third network entities, and transmitting, to the one or more selected third network entities, the second data transfer request.

[0025] According to an example, the method further comprises determining the one or more selected third network entities based on at least one of: information on one or more candidate third network entities collected from the corresponding one or more candidate third network entities and / or other network entities (e.g. AMF, LMF, GLMC, UDM, PCF, NWDAF, OAM), at least one criteria (e.g. preconfigured, provisioned, indicated).

[0026] According to an example, the method further comprises transmitting, to the one or more selected third network entities, an indication that the one or more selected third network entities have been selected, and receiving, from the one or more selected third network entities, a response to the indication that the one or more selected third network entities have been selected.

[0027] According to an example, the first data transfer request includes information indicating an area of interest, and wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting, to the one or more selected third network entities, the second data transfer request based on the area of interest.

[0028] According to an example, transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting the second data transfer request to at least one base station associated with the one or more selected third network entities, and wherein the at least one base station determines a configuration for the associated one or more selected third network entities.

[0029] According to an example, transmitting the second data transfer request to at least one base station associated with the one or more selected third network entities comprises transmitting the second data transfer request to at least one base station associated with the one or more selected third network entities via AMF.

[0030] According to an example, the first data transfer request includes at least one identifier (ID) related to the data, and wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting, to the one or more selected third network entities, the second data transfer request based on the at least one ID related to the data.

[0031] According to an example, the second data transfer request includes the at least one ID related to the data.

[0032] According to an example, the method further comprises receiving, from the one or more selected third network entities, data based on the second data transfer request.

[0033] According to an example, the method further comprises transferring data to the first network entity based on the received data.

[0034] According to an example, transferring data to the first network entity based on the received data comprises determining whether, when and / or what type of data will be transferred to the first network entity.

[0035] According to a second aspect of the present disclosure, there is provided a method of a third network entity (e.g. base station, UE) in a wireless communication network, the method comprising: receiving, from a second network entity (e.g. core NF), a second data transfer request based on a first data transfer request received at the second network entity from a first network entity (e.g. AIML entity, AIML model training server); collecting data based on the second data transfer request; and transmitting, to the second network entity, the collected data.

[0036] According to an example, the third network entity is a UE; and receiving, from the second network entity, the second data transfer request comprises receiving the second data transfer request via a base station.

[0037] According to an example, the third network entity is a base station; and collecting data based on the second data transfer request comprises configuring data collection at one or more UEs based on the second data transfer request.

[0038] According to an example, the second data transfer request is transmitted via a user plane connection.

[0039] According to an example, the data is transmitted from the third network entity to the second network entity via a user plane connection.

[0040] According to a third aspect of the present disclosure, there is provided a method of a first network entity (e.g. AIML entity, AIML model training server) in a wireless communication network, the method comprising: transmitting, to a second network entity (e.g. core NF), a first data transfer request; and receiving, from the second network entity, data in response to the first data transfer request.

[0041] According to an example, the first data transfer request and / or the second data transfer request include at least one of: information indicating one or more candidate third network entities, information indicating an area of interest, at least one identifier (ID) related to the data, information indicating a data purpose, information indicating accuracy requirements, information indicating criteria for selection of the one or more selected third network entities, and control and configuration information.

[0042] According to a fourth aspect of the present disclosure, there is provided a second network entity configured to operate according to a method of the first aspect or any one of the above described examples related to the first aspect, and / or to cooperate with a first network entity according to the method of the third aspect or any one of the above described examples related to the third aspect and / or a third network entity according to the method of the second aspect or any one of the above described examples related to the second aspect.

[0043] According to a fifth aspect of the present disclosure, there is provided a third network entity configured to operate according to a method of the second aspect or any one of the above described examples related to the second aspect, and / or to cooperate with a second network entity according to a method of the first aspect or any one of the above described examples related to the first aspect and / or a first network entity according to the method of the third aspect or any one of the above described examples related to the third aspect.

[0044] According to a sixth aspect of the present disclosure, there is provided a first network entity configured to operate according to the method of the third aspect or any one of the above described examples related to the third aspect, and / or to cooperate with a second network entity according to a method of the first aspect or any one of the above described examples related to the first aspect and / or a third network entity according to a method of the second aspect or any one of the above described examples related to the second aspect.

[0045] According to a seventh aspect of the present disclosure, there is provided a network (e.g. 6G network) or wireless communication system comprising a second network entity according to the fourth aspect, a third network entity according to the fifth aspect, and / or a first network entity according to the sixth aspect.

[0046] According to an eighth aspect of the present disclosure, there is provided a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any one of the first to third aspects or any of the above described examples related to the first to third aspects.

[0047] According to a ninth aspect of the present disclosure, there is provided a computer or processor-readable data carrier having stored thereon a computer program according to the eighth aspect.

[0048] Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings.

[0049] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0050] In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.

[0051] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0052] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0053] Herein, it will be understood that each block of flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0054] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0055] As used in embodiments of the disclosure, a “~unit / module” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit / module” does not always have a meaning limited to software or hardware. The “~unit / module” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit / module” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit / module” may be either combined into a smaller number of components and a “~unit / module,” or divided into additional components and a “~unit / module.” Moreover, the components and “~units / modules” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit / module” may include one or more processors.

[0056] The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0057] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.

[0058] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0059] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0060] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0061] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0062] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0063] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0064] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0065] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0066] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0067] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0068] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0069] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0070] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0071] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0072] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g. transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as “in case that ~” or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state “~” (e.g. a bit length is above X), and then perform the method step in response to said determination.

[0073] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0074] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0075] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0076] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0077] In the embodiments of the present disclosure described herein, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0078] The drawings or flowcharts described herein illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0079] The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.

[0080] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0081] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0082] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0083] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms describedherein, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from the European telecommunications standards institute (ETSI), where appropriate.

[0084] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network.

[0085] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.

[0086] A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0087] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0088] Furthermore, hereinafter, 5G mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0089] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0090] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), RRC, or MAC control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0091] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), DCI, UE-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0092] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0093] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0094] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention.

[0095] AIML related items in 3GPP RAN working groups

[0096] 3GPP RAN working groups started to work on Artificial Intelligence (AI) / Machine Learning (ML) for NR Air Interface since Release 18. The objectives for the SI were documented in RP-221348 and listed below. The outcome of the study item was documented in TR 38.843.

[0097] Study the 3GPP framework for AI / ML for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact.

[0098] Use cases to focus on:

[0099] - Initial set of use cases includes:

[0100] -- CSI feedback enhancement, e.g., overhead reduction, improved accuracy, prediction [RAN1]

[0101] -- Beam management, e.g., beam prediction in time, and / or spatial domain for overhead and latency reduction, beam selection accuracy improvement [RAN1]

[0102] -- Positioning accuracy enhancements for different scenarios including, e.g., those with heavy NLOS conditions [RAN1]

[0103] - Finalize representative sub use cases for each use case for characterization and baseline performance evaluations by RAN#98

[0104] -- The AI / ML approaches for the selected sub use cases need to be diverse enough to support various requirements on the gNB-UE collaboration levels

[0105] Note: the selection of use cases for this study solely targets the formulation of a framework to apply AI / ML to the air-interface for these and other use cases. The selection itself does not intend to provide any indication of the prospects of any future normative project.

[0106] AI / ML model, terminology and description to identify common and specific characteristics for framework investigations:

[0107] - Characterize the defining stages of AI / ML related algorithms and associated complexity:

[0108] -- Model generation, e.g., model training (including input / output, pre- / post-process, online / offline as applicable), model validation, model testing, as applicable

[0109] -- Inference operation, e.g., input / output, pre- / post-process, as applicable

[0110] - Identify various levels of collaboration between UE and gNB pertinent to the selected use cases, e.g.,

[0111] -- No collaboration: implementation-based only AI / ML algorithms without information exchange [for comparison purposes]

[0112] -- Various levels of UE / gNB collaboration targeting at separate or joint ML operation.

[0113] - Characterize lifecycle management of AI / ML model: e.g., model training, model deployment, model inference, model monitoring, model updating

[0114] - Dataset(s) for training, validation, testing, and inference

[0115] - Identify common notation and terminology for AI / ML related functions, procedures and interfaces

[0116] - Note: Consider the work done for FS_NR_ENDC_data_collect when appropriate

[0117] For the use cases under consideration:

[0118] 1) Evaluate performance benefits of AI / ML based algorithms for the agreed use cases in the final representative set:

[0119] - Methodology based on statistical models (from TR 38.901 and TR 38.857 [positioning]), for link and system level simulations.

[0120] -- Extensions of 3GPP evaluation methodology for better suitability to AI / ML based techniques should be considered as needed.

[0121] -- Whether field data are optionally needed to further assess the performance and robustness in real-world environments should be discussed as part of the study.

[0122] -- Need for common assumptions in dataset construction for training, validation and test for the selected use cases.

[0123] -- Consider adequate model training strategy, collaboration levels and associated implications

[0124] -- Consider agreed-upon base AI model(s) for calibration

[0125] -- AI model description and training methodology used for evaluation should be reported for information and cross-checking purposes

[0126] - KPIs: Determine the common KPIs and corresponding requirements for the AI / ML operations. Determine the use-case specific KPIs and benchmarks of the selected use-cases.

[0127] -- Performance, inference latency and computational complexity of AI / ML based algorithms should be compared to that of a state-of-the-art baseline

[0128] -- Overhead, power consumption (including computational), memory storage, and hardware requirements (including for given processing delays) associated with enabling respective AI / ML scheme, as well as generalization capability should be considered.

[0129] 2) Assess potential specification impact, specifically for the agreed use cases in the final representative set and for a common framework:

[0130] - PHY layer aspects, e.g., (RAN1)

[0131] -- Consider aspects related to, e.g., the potential specification of the AI Model lifecycle management, and dataset construction for training, validation and test for the selected use cases

[0132] -- Use case and collaboration level specific specification impact, such as new signalling, means for training and validation data assistance, assistance information, measurement, and feedback

[0133] - Protocol aspects, e.g., (RAN2) - RAN2 only starts the work after there is sufficient progress on the use case study in RAN1

[0134] -- Consider aspects related to, e.g., capability indication, configuration and control procedures (training / inference), and management of data and AI / ML model, per RAN1 input

[0135] -- Collaboration level specific specification impact per use case

[0136] 3) Interoperability and testability aspects, e.g., (RAN4) - RAN4 only starts the work after there is sufficient progress on use case study in RAN1 and RAN2

[0137] - Requirements and testing frameworks to validate AI / ML based performance enhancements and ensuring that UE and gNB with AI / ML meet or exceed the existing minimum requirements if applicable

[0138] - Consider the need and implications for AI / ML processing capabilities definition

[0139] Note 1: specific AI / ML models are not expected to be specified and are left to implementation. User data privacy needs to be preserved.

[0140] Note 2: The study on AI / ML for air interface is based on the current RAN architecture and new interfaces shall not be introduced.

[0141] RAN WGs started the normative work on Artificial Intelligence (AI) / Machine Learning (ML) for NR Air Interface in Release 19. The WID was agreed as RP-234039 with the following objectives:

[0142] - AI / ML general framework for one-sided AI / ML models within the realm of what has been studied in the FS_NR_AIML_Air project [RAN2]:

[0143] -- Signalling and protocol aspects of Life Cycle Management (LCM) enabling functionality and model (if justified) selection, activation, deactivation, switching, fallback

[0144] --- Identification related signalling is part of the above objective

[0145] -- Necessary signalling / mechanism(s) for LCM to facilitate model training, inference, performance monitoring, data collection (except for the purpose of CN / OAM / OTT collection of UE-sided model training data) for both UE-sided and NW-sided models

[0146] -- Signalling mechanism of applicable functionalities / models

[0147] - Beam management - DL Tx beam prediction for both UE-sided model and NW-sided model, encompassing [RAN1 / RAN2]:

[0148] -- Spatial-domain DL Tx beam prediction for Set A of beams based on measurement results of Set B of beams (“BM-Case1”)

[0149] -- Temporal DL Tx beam prediction for Set A of beams based on the historic measurement results of Set B of beams (“BM-Case2”)

[0150] -- Specify necessary signalling / mechanism(s) to facilitate LCM operations specific to the Beam Management use cases, if any

[0151] -- Enabling method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE

[0152] NOTE: Strive for common framework design to support both BM-Case1 and BM-Case2

[0153] - Positioning accuracy enhancements, encompassing [RAN1 / RAN2 / RAN3]:

[0154] -- Direct AI / ML positioning:

[0155] --- (1st priority) Case 1: UE-based positioning with UE-side model, direct AI / ML positioning

[0156] --- (2nd priority) Case 2b: UE-assisted / LMF-based positioning with LMF-side model, direct AI / ML positioning

[0157] --- (1st priority) Case 3b: NG-RAN node assisted positioning with LMF-side model, direct AI / ML positioning

[0158] -- AI / ML assisted positioning

[0159] --- (2nd priority) Case 2a: UE-assisted / LMF-based positioning with UE-side model, AI / ML assisted positioning

[0160] --- (1st priority) Case 3a: NG-RAN node assisted positioning with gNB-side model, AI / ML assisted positioning

[0161] -- Specify necessary measurements, signalling / mechanism(s) to facilitate LCM operations specific to the Positioning accuracy enhancements use cases, if any

[0162] -- Investigate and specify the necessary signalling of necessary measurement enhancements (if any)

[0163] -- Enabling method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE for relevant positioning sub use cases

[0164] - Core requirements for the above two use cases for AI / ML LCM procedures and UE features [RAN4]:

[0165] -- Specify necessary RAN4 core requirements for the above two use cases.

[0166] -- Specify necessary RAN4 core requirements for LCM procedures including performance monitoring.

[0167] Study objectives with corresponding checkpoints in RAN#105 (Sept ’24):

[0168] - CSI feedback enhancement [RAN1]:

[0169] -- For CSI compression (two-sided model), further study ways to:

[0170] --- Improve trade-off between performance and complexity / overhead

[0171] ---- e.g., considering extending the spatial / frequency compression to spatial / temporal / frequency compression, cell / site specific models, CSI compression plus prediction (compared to Rel-18 non-AI / ML based approach), etc.

[0172] --- Alleviate / resolve issues related to inter-vendor training collaboration.

[0173] while addressing other aspects requiring further study / conclusion as captured in the conclusions section of the TR 38.843.

[0174] -- For CSI prediction (one-sided model), further study performance gain over Rel-18 non-AI / ML based approach and associated complexity, while addressing other aspects requiring further study / conclusion as captured in the conclusions section of the TR 38.843 (e.g., cell / site specific model could be considered to improve performance gain).

[0175] - Necessity and details of model Identification concept and procedure in the context of LCM [RAN2 / RAN1]

[0176] - CN / OAM / OTT collection of UE-sided model training data [RAN2 / RAN1]:

[0177] -- For the FS_NR_AIML_Air study use cases, identify the corresponding contents of UE data collection

[0178] -- Analyse the UE data collection mechanisms identified during the FS_NR_AIML_Air (TR 38.843 section 7.2.1.3.2) study along with the implications and limitations of each of the methods

[0179] - Model transfer / delivery [RAN2 / RAN1]:

[0180] -- Determine whether there is a need to consider standardised solutions for transferring / delivering AI / ML model(s) considering at least the solutions identified during the FS_NR_AIML_Air study

[0181] - Testability and interoperability [RAN4]:

[0182] -- Finalize the testing framework and procedure for one-sided models and further analyse the various testing options for two-sided models, in collaboration with RAN1, and including at least:

[0183] --- Relation to legacy requirements

[0184] --- Performance monitoring and LCM aspects considering use-case specifics

[0185] --- Generalization aspects

[0186] --- Static / non-static scenarios / conditions and propagation conditions for testing (e.g., CDL, field data, etc.)

[0187] --- UE processing capability and limitations

[0188] --- Post-deployment validation due to model change / drift

[0189] -- RAN5 aspects related to testability and interoperability to be addressed on a request basis

[0190] NOTE: offline training is assumed for the purpose of this project.

[0191] NOTE: the outcome of the study objectives should be captured in TR 38.843 for future reference.

[0192] NOTE: Coordination with SA / SA WGs of the ongoing study / work as it may relate to their required work.

[0193] In Dec 2024, the Study objectives agreed in RP-234039 was removed the agreed WID / SID and agreed as a new SID in RP-243245 - Study on Artificial Intelligence (AI) / Machine Learning (ML) for NR air interface Phase 2. The remaining work items in RP-234039 was agreed as an updated WID in RP-243244 Revised WID: Artificial Intelligence (AI) / Machine Learning (ML) for NR Air Interface.

[0194] Analysis on RAN led topic - AIML for NR air interface

[0195] There are 3 major AIML use cases identified by RAN. The detailed scenarios / types of the 3 major uses were also discussed.

[0196] 1. CSI feedback enhancement,

[0197] a. CSI compression, e.g. Spatial-frequency domain CSI compression using two-sided AI model.

[0198] i. Type 1: Joint training of the two-sided model at a single side / entity, e.g., UE-sided or Network-sided.

[0199] ii. Type 2: Joint training of the two-sided model at network side and UE side, respectively.

[0200] iii. Type 3: Separate training at network side and UE side, where the UE-side CSI generation part and the NW-side CSI reconstruction part are trained by UE side and network side, respectively.

[0201] b. CSI prediction, e.g. Time domain CSI prediction using UE-side model

[0202] 2. Beam management

[0203] 3. Positioningaccuracy enhancementsor

[0204] SA2 approved 5GA R20 study item

[0205] SA2 approved the study item on Core Network Enhanced Support for Artificial Intelligence (AI) / Machine Learning (ML) Phase 2 in during SA2#167 meeting, Feb 2025. As documented in SP-250068 / S2-2502788, the SA2 objectives include:

[0206] -WT#1: Study whether and how to support the standardized transfer of standardized data over UP for UE data collection to meet requirements for AI / ML for NR air interface operation with UE-side model training.

[0207] Note 1: The WT#1 scope is based on UP Data Collection for Option2 documented in RAN LSs RP-243316 and RP-242389.

[0208] Note 2: The requirements are elaborated in LSs RP-242389 and R2-2411152 which will be considered during the study phase.

[0209] Note 3: WT#1 impact on user consent and privacy will be addressed in cooperation with SA3.

[0210] The detailed issues to be address by SA2 are documented in clause 5.2 of TR 23.700-04, including:

[0211] This key issue aims to provide solutions for UE data collection to meet the requirements for AI / ML for NR air interface with UE-side model training. This process requires the transfer of training data from the UE to the 5G core and then to the OTT server.

[0212] This key issue will investigate the following aspects:

[0213] - How to support the standardized transfer of standardized data over UP for UE data collection including how to initiate, terminate and manage UE data transfer over the UP connection.

[0214] - How to support in 5GC the full visibility of standardized UE data contents.

[0215] - How 5GC can support the full controllability of standardized UE data transfer.

[0216] - How to differentiate the traffic for UE data collection from the UE regular traffic in the 5GC.

[0217] - Whether and how the UE knows about what the standardized data to be transferred are.

[0218] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the present invention, as defined by the claims. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the invention or disclosure.

[0219] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0220] Detailed descriptions of techniques, structures, constructions, functions or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0221] The terms and words used herein are not limited to the bibliographical or standard meanings, but, are merely used to enable a clear and consistent understanding of the disclosure.

[0222] Throughout the description of this specification, the words “comprise”, “include” and “contain” and variations of the words, for example “comprising” and “comprises”, means “including but not limited to”, and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof.

[0223] Throughout the description and claims, the singular form, for example “a”, “an” and “the”, encompasses the plural unless the context otherwise requires. For example, reference to “an object” includes reference to one or more of such objects.

[0224] Throughout the description, the expression “at least one of A, B and / or C” (or the like), the expression “and / or”, and the expression “one or more of A, B and / or C” (or the like) should be seen to separately include all possible combinations, for example: A, B, C, A and B, A and C, A and B and C.

[0225] Throughout the description and claims, language in the general form of “X for Y” (where Y is some action, process, function, activity or step and X is some means for carrying out that action, process, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.

[0226] Features, elements, components, integers, steps, processes, functions, characteristics, and the like, described in conjunction with a particular aspect, embodiment, example or claim are to be understood to be applicable to any other aspect, embodiment, example or claim disclosed herein unless incompatible therewith.

[0227] Certain examples of the present disclosure relate to methods, apparatus and / or systems for UE / RAN node selection for AIML data collection and / or transfer and methods, apparatus and / or systems for UE AIML data collection and transfer.

[0228] The following examples are applicable to, and use terminology associated with, 3GPP 5G. However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 5G, and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards. The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 5G NR or any other relevant standard. For example, the functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in other communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function, operation or purpose within the network. In particular, the following disclosure should be considered at least in relation to 6G also, which is expected to use at least part of the 5G architecture, or equivalent, and to which the present disclosure also relates.

[0229] A particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0230] The skilled person will appreciate that the present disclosure is not limited to the specific examples disclosed herein. For example:

[0231] - The techniques disclosed herein are not limited to 3GPP 5G, B5G or 6G.

[0232] - One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations.

[0233] - One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information.

[0234] - One or more further elements, entities and / or messages may be added to the examples disclosed herein.

[0235] - One or more non-essential elements, entities and / or messages may be omitted in certain examples.

[0236] - The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example.

[0237] - The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example.

[0238] - Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example.

[0239] - Information carried by two or more separate messages in one example may be carried by a single message in an alternative example.

[0240] - The order in which operations are performed may be modified, if possible, in alternative examples.

[0241] - The transmission of information between network entities is not limited to the specific form, type and / or order of messages described in relation to the examples disclosed herein.

[0242] Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Such an apparatus / device / network entity may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). Certain examples of the present disclosure may be provided in the form of a system (e.g., a network) comprising one or more such apparatuses / devices / network entities, and / or a method therefor.

[0243] It will be appreciated that examples of the present disclosure may be realized in the form of hardware, software or a combination of hardware and software. Certain examples of the present disclosure may provide a computer program comprising instructions or code which, when executed, implement a method, system and / or apparatus in accordance with any aspect, example and / or embodiment disclosed herein. Certain embodiments of the present disclosure provide a machine-readable storage storing such a program.

[0244] A network according to one or more of the examples disclosed herein may include one or more of a OAM entity, UE, NG-RAN entity (e.g. gNB), AMF entity, UDM entity, PCF entity, NWDAF entity, DCF entity, NEF entity, and an AIML entity (e.g. a server, such as a training server). The network may include one or more service consumers (including one or more of the entities mentioned above and / or one or more other entities) that receive analytics from NWDAF. The skilled person will appreciate that a network may omit one or more of the entities mentioned above and / or may comprise one or more additional entities.

[0245] AIML modeling training for the use cases related NR air interface performance required training data to be collected from multiple UEs. However, currently it is not clear:

[0246] - which entity and how to select the UEs to perform data collection for AIML model training;

[0247] - which entity is responsible for the configuration of radio signal transmission and / or collection;

[0248] - which entity is responsible for triggering AIML data collection at UE and / or RAN node side;

[0249] - which entity is responsible for triggering AIML transfer to core or application layer from at UE and / or RAN node.

[0250] In the present disclosure, AIML data collection is for AIML operation, e.g. for one or more of the following procedures: AIML model training / update, inference, performance / accuracy evaluation, etc.

[0251] The AIML data might be collected by / from UE, RAN node, 5GC NFs (e.g. DCF, NWDAF, etc.), OAM, 3rd party / AIML server, etc.

[0252] The AIML server might be within or outside 3GPP system.

[0253] DCF: data collection function / functionality. It may support the AIML data collection and transfer (trigger), configuration and control, data storage, user consent and privacy check for data collection, data exposure to AIML (training) server, etc.

[0254] In the present disclosure, the DCF is used as an example of any core network function that is responsible for AIML data control and management. The DCF can be replaced by other core NF (e.g. NEF, NWDAF, DCCF, PCF, MATF, ADRF, DCAF, etc) or OAM.

[0255] The AIML data control and management may include trigger AIML data collection and / transfer (e.g. from UE, RAN node, any core NF, OAM, etc.), configure the AIML data collection related radio signal transmission.

[0256] The AIML data collection related radio signal transmission is defined by Ran working groups, it may include CSI related signals, e.g. target CSI, CSI feedback, reconstructed target CSI, beam management related signals, positioning related signals, etc.

[0257] The control and configuration information for AIML data collection and / or transfer, may include:

[0258] - (type of) Radio signals to be transmitted for AIML data measurement, e.g. CSI related signals, beam management related signals, positioning related signals, etc.

[0259] - Time window within which the radio signals are to be transmitted for AIML data measurement and / or AIML data measurement

[0260] - Time window / stamp of AIML data transmission / reporting, e.g. from UE and / or RAN node

[0261] - Determine UEs and / or RAN node(s) to transfer radio signals for AIML data measurement, and / or perform AIML data measurement, and / or perform AIML data transfer / reporting (e.g. to serving RAN node, DCF, AIML server, etc.).

[0262] UE / RAN node selection for AIML data collection and / or transfer

[0263] FIG. 1 illustrates a procedure for UE / RAN node selection for AIML data collection and / or transfer.

[0264] In step 0, the AIML server may request data for AIML process (e.g. AIML model training) from the network.

[0265] AIML server may send request to DCF or any other core network that is responsible for AIML data control and management or to NEF / PCF.

[0266] The NEF may decide whether to authorize the request or not.

[0267] The NEF may assist / perform the UE selection for AIML data collection and transfer.

[0268] If the AIML server is an untrusted AF, the request might be sent via NEF from AIML server.

[0269] The AIML server may indicate one or more of the following AIML data transfer requirement information to the network:

[0270] - The purpose / use case of AIML operation (e.g. AIML model training), e.g. for AIML-based positioning, CSI compression / prediction, beam management, etc.

[0271] - List of candidate UE(s) and / or RAN node to perform data / signal transmission for measurement, AIML data measurement / collection, AIML data transfer.

[0272] - The accuracy requirement of the data collection / measurement, etc.

[0273] - Criteria of UE (s) and / or RAN node(s) selection.

[0274] - Area of interest (AOI)

[0275] The server might also indicate the corresponding AIML service / operation / correlation ID.

[0276] [Optional] In step 1, the NEF or PCF may authorize or reject the AIML data collection and / or transfer request from AIML server.

[0277] The DCF determines that AIML data collection and / or data transfer will be performed, e.g. if the request is authorized by NEF or PCF.

[0278] Based on the AIML data transfer requirement information, e.g. indicated by AIML server, the DCF may determine the control and configuration information for AIML data collection and / or transfer.

[0279] The DCF or NEF may trigger UE and / or RAN node selection for: transferring radio signals for AIML data measurement, performing AIML data measurement, performing AIML data transfer / reporting (e.g. to serving RAN node, OAM, DCF, AIML server, etc.).

[0280] In step 2, the DCF may collect / request information related to candidate UEs and / or RAN node:

[0281] - From the corresponding UEs and / or RAN node (e.g. capability information),

[0282] - From AMF / LMF / GLMC (e.g. for UE location information),

[0283] - from UDM (e.g. for UE subscription information of different (AIML) services, UE user consent / privacy information (e.g. related to AIML data collection, transfer),

[0284] - from PCF (e.g. for UE policies, session management and / or access management policies (e.g. related to corresponding UEs),

[0285] - from NWDAF (e.g. for analytics related to UE and / or RAN node performance (e.g. delay, throughput, data rate, packet loss, etc.), workload, congestion, UE mobility / behavior / communication / QoS, etc.),

[0286] - from OAM (e.g. for the service performance / status of AOI / cell / location, the performance of RAN node, etc.)

[0287] In step 3, DCF or NEF may consolidate the collected information related to candidate UE / RAN nodes. Then DFC or NEF determine the UE / RAN node based on criteria and / or the collected information. The criteria might be (pre-)configured (e.g. by operators), provisioned (e.g. by AIML server, PCF), or indicated (e.g. in AIML server request)

[0288] The criteria may include (requirements / threshold) of the following parameters of UE and / or gNB:

[0289] - UE and / or gNB location

[0290] - Qos and / or one or more QoS parameters or attributes as defined in TS 23.501.

[0291] - RAT, frequency (e.g. of serving cell or supporting frequency)

[0292] - Delay / latency, e.g. of data transmission, packet delay, etc. This might be between any of: UE, gNB, UPF, DCF, AIML server.

[0293] - Data / packet loss / error (rate)

[0294] - UE mobility / behavior (e.g. normal, abnormal behaviors)

[0295] - communication (load) of gNB, slice, area, cell, UE, etc.

[0296] - congestion level

[0297] The UE might be determined by a RAN node based on the above criteria. The RAN node might be serving RAN node of the UE(s), or one or more a configured RAN node (e.g. determined by operator, DCF, NEF, OAM, AIML server).

[0298] In steps 4-5, the DCF or NEF sends the decision of the UE / RAN node.

[0299] DCF or NEF may send the decision to the corresponding UE(s) and / or RAN node(s), the serving RAN node(s) of the selected UE(s).

[0300] The UE (or the serving RAN node of the UE) / selected RAN respond to DCF / NEF. The response may include: whether the selected UE / RAN node will join the AIML signal transfer / AIML data collection / AIML data transfer or not; if not, the cause of not joining, etc.

[0301] Step 4 and / or step5 may occur together with AIML data collection and / transfer request; or after the UE / RAN nodes are selected but before the AIML data collection and / transfer request was initiated.

[0302] In step 6, the DCF / NEF may determine to update the selected UE / RAN node, e.g. based on response in step 5, operator’s policy, its internal logic, the availability change of the selected UE / RAN node, UE consent / privacy update, etc.

[0303] The DCF / NEF may repeat one or more of step 2-5 for the update.

[0304] Triggers of AIML data collection and / or transfer

[0305] FIG. 2 illustrates a procedure for UE AIML data collection and transfer.

[0306] The AIML data collection (at UE) and / or transfer (from UE) might be triggered by CN (e.g. DCF), OAM.

[0307] Step 0. This step might be the same as step 0 in as described under ‘UE / RAN node selection for AIML data collection and / or transfer’ above, and / or FIG. 1.

[0308] The AIML server may request data for AIML process (e.g. AIML model training) from the network, e.g. by sending request to OAM or via CN to OAM.

[0309] In step 1, the CN (e.g. DCF) or OAM determines to trigger AIML data collection and / or transfer, e.g. towards (the selected) UEs. The AIML data collection and / or transfer might be for one or more specific AIML services, e.g. represented by AIML service / operation / correlation ID. This ID might be an ID used by one or more of: AIML server, DCF and / or other core NFs, gNB, UE, OAM.

[0310] - The ID might be also used to associated any information related to the AIML service, e.g. the core NF, gNBs, UEs that are involved into the AIML service, and / or associated the collected / transferred data, training model, intermediate results, meta data, etc.

[0311] If the UEs are not selected, any of steps 1-6 as described above under ‘UE / RAN node selection for AIML data collection and / or transfer’ and / or FIG. 1 might be performed,

[0312] In step 2, the CN (e.g. DCF) or OAM triggers AIML data collection and / or transfer request. The request may include the control and configuration information for AIML data collection and / or transfer, AIML service / operation / correlation ID, list of UEs / RAN node to perform data collection and / or transfer, list of RAN node(s) to perform the data transmission for AIML data measurement / collection, etc.

[0313] One or more of the following steps may work in conjunction.

[0314] The following steps may occur in any order.

[0315] Step 2a. For OAM, it may send the AIML data collection and / or transfer request to the serving gNB of the selected UEs.

[0316] Step 2b. for core NF, e.g. DCF, it may send the AIML data collection and / or transfer request to the serving gNB of the selected UEs, e.g. via UP connection between DCF and gNB, AIML protocol / direct interface between DCF and gNB, or interface similar to NRPPa (NR Positioning Protocol A).

[0317] Step 2c. for core NF, e.g. DCF, it may send the AIML data collection and / or transfer request to the serving gNB of the selected UEs, e.g. via CP / AMF. The DCF may send / expose the request to AMF, e.g. via AMF service operation; then the AMF forwards the request to RAN node, e.g. by using NG-AP message.

[0318] Step 2d. the gNB may send UE data collection and / transfer request to the UE.

[0319] The gNB may indicate the measurement configuration of AIML data collection / measurement to UEs that is determined in step 2g.

[0320] Step 2e. for core NF, e.g. DCF, it may send the AIML data collection and / or transfer request to the selected UEs, e.g. via UP connection between DCF and UE (if the UP connection is not established, the UP connection establishment might be triggered); or, DCF sends the request to AMF, then the AMF forward the request to UE via NAS / AIML data transfer / LPP protocol; or a direct (CP / UP) interface between DCF and UE, etc.

[0321] The DCF may indicate the control and configuration information for AIML data collection and / or transfer in this step.

[0322] Step 2f. the UE may send (some of the information) in control and configuration information for AIML data collection and / or transfer to gNB.

[0323] The UE may require the gNB to send configuration information for UE measurement, require the gNB to transmit radio signals for AIML data collection, etc.

[0324] Step 2g. the RAN node determines the radio related measurement configuration, e.g. the configuration of signals to be transmitted for AIML data collection / measurement, the measurement configuration of the UEs that to perform AIML data collection / measurement.

[0325] This step may occur after any step of 2a, 2b, 2c, 2f.

[0326] The RAN node may make the decision based on the (consolidated) information received from one or more of: OAM, UE, AMF, DCF, AIML server, etc.

[0327] The RAN node may also determine the configuration of UE measurement reporting of the collected AIML data.

[0328] Step 2h. this step might be optional. The (serving) gNB starts to transmit the radio signals for AIML data collection measurement. The (type of) radio signals might be determined by gNB (itself), AIML server, DCF, OAM, UE etc.

[0329] Step 2i. this step might be optional. The (serving) gNB may send a request to UE to trigger the UE data collection for AIML.

[0330] The gNB may indicate the radio interface configuration to corresponding UEs.

[0331] In step 3, UE performs data collection, e.g. based on the (consolidated) configuration received from one or more of: gNB, OAM, AMF, DCF, AIML server, etc.

[0332] If the UE data transfer was not requested / triggered in previous steps, it might be triggered in step 4.

[0333] The sub-steps (2a-2i) detailed in step 2 could be reused for UE data transfer request.

[0334] In step 5, the UE determines to transfer AIML data to the network. This might be determined based on UE internal logic (e.g. the buffer for data logging is full), gNB configuration (e.g. the resource configured for UL / AIML data transfer), timing information provided by the network for data transfer (e.g. the network may require the UE to transfer AIML data within a time window or start from a time point, etc.), or upon receiving request from one or more of gNB, OAM, AMF, DCF, AIML server, etc.

[0335] In step 6, the UE performs AIML data transfer to network as configured / requested, e.g. via UP and / or CP.

[0336] In step 7, the CN NF (e.g. DCF) or OAM may consolidate the data reported from one or more UEs.

[0337] The DCF or OAM may then determine whether, when and what type of data will be transferred / exposed to AIML server.

[0338] FIG. 3 illustrates an example method of a second network entity (e.g. core NF) in a wireless communication network.

[0339] In step 302, the method comprises receiving, from a first network entity (e.g. AIML entity, AIML model training server), a first data transfer request.

[0340] In step 304, the method comprises transmitting, to one or more selected third network entities (e.g. base station, UE), a second data transfer request based on the first data transfer request.

[0341] FIG. 4 illustrates an example method of a third network entity (e.g. base station, UE) in a wireless communication network.

[0342] In step 402, the method comprises receiving, from a second network entity (e.g. core NF), a second data transfer request based on a first data transfer request received at the second network entity from a first network entity (e.g. AIML entity, AIML model training server).

[0343] In step 404, the method comprises collecting data based on the second data transfer request.

[0344] In step 406, the method comprises transmitting, to the second network entity, the collected data.

[0345] FIG. 5 illustrates an example method of a first network entity (e.g. AIML entity, AIML model training server) in a wireless communication network.

[0346] In step 502, the method comprises transmitting, to a second network entity (e.g. core NF), a first data transfer request.

[0347] In step 504, the method comprises receiving, from the second network entity, data in response to the first data transfer request.

[0348] FIG. 6 is a block diagram of an exemplary network entity (e.g. OAM, UE, NG-RAN entity (e.g. gNB), AMF, UDM, PCF, NWDAF, DCF, NEF, AIML (training) server) that may be used in examples of the present disclosure. The skilled person will appreciate that the network entity illustrated in FIG. 6 may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0349] The network entity 600 comprises a processor 601 (or controller), a transmitter 603 and a receiver 605. The receiver 605 is configured for receiving one or more messages from one or more other network entities. The transmitter 603 is configured for transmitting one or more messages to one or more other network entities. The processor 601 is configured for performing operations as described above.

[0350] FIG. 7 is a block diagram of a terminal or user equipment (UE) 700 according to an embodiment of the disclosure.

[0351] The terminal is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0352] Referring to FIG. 7, the UE 700 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 701, at least one processor (hereinafter, referred to as simply “processor”) 702, and at least one memory (hereinafter, referred to as simply “memory”) 703. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 701, the processor 702, and the memory 703 of the UE 700 may operate. However, components of the UE 700 are not limited to the example components illustrated in FIG. 7. In another embodiment, the UE 700 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 701, the processor 702, or the memory 703 may be integrated in the form of one component.

[0353] The transceiver 701 may be a communication circuit or communication circuitry that enables the UE 700 to perform wireless communication with a node or an entity of a network. For example, the transceiver 701 may enable the UE 700 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 701 may support at least one of various cellular communication technologies including 3rd generation (3G), 4thgeneration (4G), long term evolution (LTE), 5th generation (5G) NR, 6thgeneration (6G), and various cellular wireless communication technologies supported by the transceiver (701) may include all subsequent generations of evolved wireless communications.

[0354] According to an embodiment, the UE 700 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 700 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 700 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 700 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0355] According to an embodiment, the transceiver 701 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 701 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 701 may output a signal received through a wireless channel to the processor 702 and may transmit, through a wireless channel, a signal output from the processor 702.

[0356] The processor 702 may control general operations of the UE 700 according to embodiments of the disclosure. The processor 702 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 702 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 703, individually, collectively or in any combination thereof. Further, the processor 702 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0357] The processor 702 may be electrically, operatively, and / or communicatively coupled to the transceiver 701 to control the transceiver 701.

[0358] The processor 702 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 702 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 702 may be included in one chip (or IC) and the other part of the processor 702 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 701 or the memory 703.

[0359] The processor 702 may perform or control or cause an operation of the UE 700 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 702 may control operations of the UE 700 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 702 may execute a computer program, codes, or instructions stored in the memory 703, so as to control other components of the UE 700 to enable execution of various operations.

[0360] The memory 703 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 703 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0361] The memory 703 may be electrically, operatively, and / or communicatively coupled to the processor 702 and may be accessed by the processor 702.

[0362] The memory 703 may store a computer program, codes, or instructions executable by the processor 702. According to an embodiment, a computer program, codes, or instructions executable by the processor 702 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 703, the processor 702 may perform various functions according to an embodiment of the disclosure.

[0363] According to an embodiment of the disclosure, operations of the UE 700 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 703 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0364] FIG. 8 is a block diagram of a base station (BS) 800 according to an embodiment of the disclosure.

[0365] The BS 800 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 800 through a wireless channel. The BS 800 may perform communication with a node or an entity of a network through wired or wireless communication.

[0366] Referring to FIG. 8, the BS 800 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 801, at least one processor (hereinafter, referred to as simply “processor”) 802, and at least one memory (hereinafter, referred to as simply “memory”) 803. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 801, the processor 802, and the memory 803 of the BS 800 may operate. However, components of the BS 800 are not limited to the example components illustrated in FIG. 8. In another embodiment, the BS 800 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 801, the processor 802, or the memory 803 may be integrated in the form of one component.

[0367] The transceiver 801 may be a communication circuit or communication circuitry that enables the BS 800 to perform wireless communication with a node or an entity of a network. For example, the transceiver 801 may enable the BS 800 to transmit or receive a signal to or from the UE 700 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 801 may support various cellular communication technologies including 3rd generation (3G), 4thgeneration (4G), long term evolution (LTE), 5th generation (5G) NR, 6thgeneration (6G), and various cellular wireless communication technologies supported by the transceiver (801) may include all subsequent generations of evolved wireless communications. According to an embodiment, the transceiver 801 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 801 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 801 may output a signal received through a wireless channel to the processor 802 and may transmit, through a wireless channel, a signal output from the processor 802.

[0368] Meanwhile, according to an embodiment of the present disclosure, the BS 800 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 800 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 8, when the BS 800 performs wired communication, the BS 800 may further include a separate network interface for wired communication in addition to the transceiver 801. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0369] The processor 802 may control general operations of the BS 800 according to embodiments of the disclosure. The processor 802 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 802 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 803, individually, collectively or in any combination thereof. Further, the processor 802 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0370] The processor 802 may be electrically, operatively, and / or communicatively coupled to the transceiver 801 to control the transceiver 801.

[0371] The processor 802 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 802 may be included in one chip (or IC) and the other part of the processor 802 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 801 or the memory 803.

[0372] The processor 802 may perform or control or cause an operation of the BS 800 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 802 may control operations of the BS 800 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 800 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 802 may execute a computer program, codes, or instructions stored in the memory 803, so as to control other components of the BS 800 to enable execution of various operations.

[0373] The memory 803 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 803 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0374] The memory 803 may be electrically, operatively, and / or communicatively coupled to the processor 802 and may be accessed by the processor 802.

[0375] The memory 803 may store a computer program, codes, or instructions executable by the processor 802. According to an embodiment, a computer program, codes, or instructions executable by the processor 802 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 803, the processor 802 may perform various functions according to an embodiment of the disclosure.

[0376] According to an embodiment of the disclosure, operations of the BS 800 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 803 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0377] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), rtc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0378] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0379] FIG. 9 is a block diagram of a network entity 900 according to an embodiment of the disclosure.

[0380] The network entity 900 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 900. Furthermore, the network entity 900 of FIG.9 may correspond to the network entity 600 of FIG.6.

[0381] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0382] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN), etc.

[0383] Referring to FIG. 9, the network entity 900 may include at least one network interface 901, at least one processor 902 (hereinafter, “processor”), and at least one memory 903 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 900, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 9. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0384] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 901, the processor 902, and the memory 903 of the network entity 900 may operate. However, components of the network entity 900 are not limited to the example components illustrated in FIG. 9. In another embodiment, the network entity 900 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 901, the processor 902, or the memory 903 may be integrated in the form of one component.

[0385] The network interface 901 is a collective term for a transmitter part of the network entity 900 and a receiver part of the network entity 900, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 901 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 901 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 901 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0386] The processor 902 may control general operations of the network entity 900 according to embodiments of the disclosure. The processor 902 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 902 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 903, individually, collectively or in any combination thereof. Further, the processor 902 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0387] According to an embodiment, the processor 902 may be electrically, operatively, and / or communicatively coupled to the network interface 901 to control the network interface 901.

[0388] The processor 902 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 902 may be included in one chip (or IC) and the other part of the processor 902 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 901 or the memory 903.

[0389] The processor 902 may perform or control or cause an operation of the network entity 900 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 902 may control operations of the network entity 900 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 902 may execute a computer program, codes, or instructions stored in the memory 903, so as to control other components of the network entity 900 to enable execution of various operations.

[0390] The memory 903 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 903 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0391] The memory 903 may be electrically, operatively, and / or communicatively coupled to the processor 902 and may be accessed by the processor 902.

[0392] The memory 903 may store a computer program, codes, or instructions executable by the processor 902. According to an embodiment, a computer program, codes, or instructions executable by the processor 902 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 903, the processor 902 may perform various functions according to an embodiment of the disclosure.

[0393] According to an embodiment of the disclosure, operations of the network entity 900 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 903 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0394] The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment or example disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.

[0395] It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like.

[0396] It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment and / or aspect disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

[0397] While the present disclosure has been shown, illustrated and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the disclosure.

[0398] The reader's attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

[0399] In a first example, there is provided a method of a second network entity (e.g. core NF) in a wireless communication network, the method comprising: receiving, from a first network entity (e.g. AIML entity, AIML model training server), a first data transfer request; and transmitting, to one or more selected third network entities (e.g. base station, UE), a second data transfer request based on the first data transfer request.

[0400] In a second example, there is provided the method of the first example, wherein the first data transfer request includes information indicating one or more candidate third network entities, and wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises: determining the one or more selected third network entities based on the information indicating one or more candidate third network entities, and transmitting, to the one or more selected third network entities, the second data transfer request.

[0401] In a third example, there is provided the method of the second example, further comprising determining the one or more selected third network entities based on at least one of: information on one or more candidate third network entities collected from the corresponding one or more candidate third network entities and / or other network entities (e.g. AMF, LMF, GLMC, UDM, PCF, NWDAF, OAM), at least one criteria (e.g. preconfigured, provisioned, indicated).

[0402] In a fourth example, there is provided the method of any one of the first to third examples, further comprising transmitting, to the one or more selected third network entities, an indication that the one or more selected third network entities have been selected, and receiving, from the one or more selected third network entities, a response to the indication that the one or more selected third network entities have been selected.

[0403] In a fifth example, there is provided the method of any one of the first to fourth examples, wherein the first data transfer request includes information indicating an area of interest, and wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting, to the one or more selected third network entities, the second data transfer request based on the area of interest.

[0404] In a sixth example, there is provided the method of any one of the first to fifth examples, wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting the second data transfer request to at least one base station associated with the one or more selected third network entities, and wherein the at least one base station determines a configuration for the associated one or more selected third network entities.

[0405] In a seventh example, there is provided the method of the sixth example, wherein transmitting the second data transfer request to at least one base station associated with the one or more selected third network entities comprises transmitting the second data transfer request to at least one base station associated with the one or more selected third network entities via AMF.

[0406] In an eighth example, there is provided the method of any one of the first to seventh examples, wherein the first data transfer request includes at least one identifier (ID) related to the data, and wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting, to the one or more selected third network entities, the second data transfer request based on the at least one ID related to the data.

[0407] In a ninth example, there is provided the method of the eighth example, wherein the second data transfer request includes the at least one ID related to the data.

[0408] In a tenth example, there is provided the method of any one of the first to ninth examples, further comprising receiving, from the one or more selected third network entities, data based on the second data transfer request.

[0409] In an eleventh example, there is provided the method of the tenth example, further comprising transferring data to the first network entity based on the received data.

[0410] In a twelfth example, there is provided the method of the eleventh example, wherein transferring data to the first network entity based on the received data comprises determining whether, when and / or what type of data will be transferred to the first network entity.

[0411] In a thirteenth example, there is provided a method of a third network entity (e.g. base station, UE) in a wireless communication network, the method comprising: receiving, from a second network entity (e.g. core NF), a second data transfer request based on a first data transfer request received at the second network entity from a first network entity (e.g. AIML entity, AIML model training server); collecting data based on the second data transfer request; and transmitting, to the second network entity, the collected data.

[0412] In a fourteenth example, there is provided the method of the thirteenth example, wherein the third network entity is a UE; and wherein receiving, from the second network entity, the second data transfer request comprises receiving the second data transfer request via a base station.

[0413] In a fifteenth example, there is provided the method of the thirteenth example, wherein the third network entity is a base station; and wherein collecting data based on the second data transfer request comprises configuring data collection at one or more UEs based on the second data transfer request.

[0414] In a sixteenth example, there is provided the method of any one of the first to fifteenth examples, wherein the second data transfer request is transmitted via a user plane connection.

[0415] In a seventeenth example, there is provided the method of any one of the tenth to sixteenth examples, wherein the data is transmitted from the third network entity to the second network entity via a user plane connection.

[0416] In a eighteenth example, there is provided a method of a first network entity (e.g. AIML entity, AIML model training server) in a wireless communication network, the method comprising: transmitting, to a second network entity (e.g. core NF), a first data transfer request; and receiving, from the second network entity, data in response to the first data transfer request.

[0417] In a nineteenth example, there is provided the method of any one of the first to eighteenth examples, wherein the first data transfer request and / or the second data transfer request include at least one of: information indicating one or more candidate third network entities, information indicating an area of interest, at least one identifier (ID) related to the data, information indicating a data purpose, information indicating accuracy requirements, information indicating criteria for selection of the one or more selected third network entities, and control and configuration information.

[0418] In a twentieth example, there is provided a second network entity configured to operate according to a method of any one of the first to twelfth or eighteenth examples, and / or to cooperate with a first network entity and / or third network entity according to a method of any one of the thirteenth to eighteenth examples.

[0419] In a twenty-first example, there is provided a third network entity configured to operate according to a method of any one of the thirteenth to fifteenth or eighteenth examples, and / or to cooperate with a second network entity and / or a first network entity according to a method of any one of the first to twelfth or sixteenth to eighteenth claims.

[0420] In a twenty-second example, there is provided a first network entity configured to operate according to a method of the eighteenth or nineteenth example, and / or to cooperate with a second network entity and / or a third network entity according to a method of any one of the first to fifteenth or eighteenth examples.

[0421] In a twenty-third example, there is provided a network (e.g. 6G network) or wireless communication system comprising a second network entity according to the twentieth example, a third network entity according to the twenty-first example, and / or a first network entity according to the twenty-second example.

[0422] In a twenty-fourth example, there is provided a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any one of the first to nineteenth examples.

[0423] In a twenty-fifth example, there is provided a computer or processor-readable data carrier having stored thereon a computer program according to the twenty-fourth example.

[0424] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

[0425]

Claims

1.A method of a second network entity (e.g. core NF) in a wireless communication network, the method comprising:receiving, from a first network entity (e.g. AIML entity, AIML model training server), a first data transfer request; andtransmitting, to one or more selected third network entities (e.g. base station, UE), a second data transfer request based on the first data transfer request.2.The method of claim 1, wherein the first data transfer request includes information indicating one or more candidate third network entities, andwherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises:determining the one or more selected third network entities based on the information indicating one or more candidate third network entities, andtransmitting, to the one or more selected third network entities, the second data transfer request.3.The method of claim 2, further comprising determining the one or more selected third network entities based on at least one of:information on one or more candidate third network entities collected from the corresponding one or more candidate third network entities and / or other network entities (e.g. AMF, LMF, GLMC, UDM, PCF, NWDAF, OAM),at least one criteria (e.g. preconfigured, provisioned, indicated).4.The method of claim 1, further comprising transmitting, to the one or more selected third network entities, an indication that the one or more selected third network entities have been selected, andreceiving, from the one or more selected third network entities, a response to the indication that the one or more selected third network entities have been selected.5.The method of claim 1, wherein the first data transfer request includes information indicating an area of interest, andwherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting, to the one or more selected third network entities, the second data transfer request based on the area of interest.6.The method of claim 1, wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting the second data transfer request, via AMF, to at least one base station associated with the one or more selected third network entities, andwherein the at least one base station determines a configuration for the associated one or more selected third network entities.7.The method of claim 1, wherein the first data transfer request includes at least one identifier (ID) related to the data,wherein transmitting, to the one or more selected third network entities, the second data transfer request based on the first data transfer request comprises transmitting, to the one or more selected third network entities, the second data transfer request based on the at least one ID related to the data, andwherein the second data transfer request includes the at least one ID related to the data.8.The method of claim 1, further comprising:receiving, from the one or more selected third network entities, data based on the second data transfer request; andtransferring data to the first network entity based on the received data,wherein transferring data to the first network entity based on the received data comprises determining whether, when and / or what type of data will be transferred to the first network entity.9.The method of claim 1, wherein the second data transfer request is transmitted via a user plane connection.10.The method of claim 1, wherein the first data transfer request and / or the second data transfer request include at least one of:information indicating one or more candidate third network entities,information indicating an area of interest,at least one identifier (ID) related to the data,information indicating a data purpose,information indicating accuracy requirements,information indicating criteria for selection of the one or more selected third network entities, andcontrol and configuration information.11.A method of a third network entity (e.g. base station, UE) in a wireless communication network, the method comprising:receiving, from a second network entity (e.g. core NF), a second data transfer request based on a first data transfer request received at the second network entity from a first network entity (e.g. AIML entity, AIML model training server);collecting data based on the second data transfer request; andtransmitting, to the second network entity, the collected data.12.The method of claim 11, wherein the third network entity is a UE; andwherein receiving, from the second network entity, the second data transfer request comprises receiving the second data transfer request via a base station.13.The method of claim 11, wherein the third network entity is a base station; andwherein collecting data based on the second data transfer request comprises configuring data collection at one or more UEs based on the second data transfer request.14.The method of claim 11, wherein the data is transmitted from the third network entity to the second network entity via a user plane connection.15.A method of a first network entity (e.g. AIML entity, AIML model training server) in a wireless communication network, the method comprising:transmitting, to a second network entity (e.g. core NF), a first data transfer request; andreceiving, from the second network entity, data in response to the first data transfer request.