Method of model data format configuration

Abstract

The present disclosure describes method of model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling of using the pre-configured AI / ML (artificial intelligence / machine learning) based model identification with ML identifiers in wireless mobile communication system including base station e.g., gNB, TN, NTN and mobile station e.g., UE. In AI / ML model is applied to radio access network, signaling overhead can be significantly increased for varying types of associated IDs along with model identification. Therefore, model operation e.g., model training / inferencing / monitoring / updating can be set up between network and UE by using a list of multiple ML identifier format types for ML operation.

Description

[0001] 202404734

[0002] - 1 -

[0003] TITLE

[0004] Method of model data format configuration

[0005] TECHNICAL FIELD

[0006] The present disclosure relates to AI / ML based model operation with data format type of ML identifiers signaling, where techniques for pre-configuring and signaling the specific information about model identification with ML identifiers applicable to radio access network are presented.

[0007] BACKGROUND

[0008] In 3GPP (Third Generation Partnership Project), one of the selected study items as the approved Release 18 package is AI / ML (artificial intelligence / machine learning) as described in the related document (RP-213599) addressed in 3GPP TSG (Technical Specification Group) RAN (Radio Access Network) meeting #94e. The official title of AI / ML study item is “Study on AI / ML for NR Air Interface”. The goal of this study item is to identify a common AI / ML framework and areas of obtaining gains using AI / ML based techniques with use cases. According to 3GPP, the main objective of this study item is to study AI / ML framework for air-interface with target use cases by considering performance, complexity, and potential specification impact. In particular, AI / ML model, terminology and description to identify common and specific characteristics for framework are included as one of key work scopes. Regarding AI / ML framework, various aspects are under consideration for investigation and one of key items is about lifecycle management of AI / ML model where multiple stages are included as mandatory for model training, model deployment, model inference, model monitoring, model updating etc.

[0009] Also in 3GPP, two-sided (AI / ML) model is defined as a paired AI / ML model(s) over which joint inference is performed, where joint inference comprises AI / ML Inference whose inference is performed jointly across the UE and the network. Also for onesided (AI / ML) model, UE-side (AI / ML) model is defined as an AI / ML model whose inference is performed entirely at the UE and network-side (AI / ML) model is defined 202404734

[0010] - 2 - as an AI / ML model whose inference is performed entirely at the network. Currently, AI / ML specification work is at the stage of work item discussion for Release 19. Earlier, in 3GPP TR 37.817 for Release 17, titled as Study on enhancement for Data Collection for NR and EN-DC, UE (user equipment) mobility was also considered as one of AI / ML use cases and one of scenarios for model training / inference is that both functions are located within RAN node. Followingly, in Release 18 the new work item of “Artificial Intelligence (AI)ZMachine Learning (ML) for NG-RAN” was initiated to specify data collection enhancements and signaling support within existing NG-RAN interfaces and architecture. For the above active standardization works, RAN-based AI / ML model is considered very significant for both network and UE to meet any desired model operations (e.g., model training, inference, selection, switching, update, monitoring, etc.). Model information can be signaled to pair both networkside and UE-side models for various lifecycle management (LCM) operations.

[0011] However, signaling overhead indicating model information can be very high especially when model based LCM is processed between base station (BS / gNB) and multiple UEs. In LCM, model training is one of the most important parts for model deployment and currently there is no specification defined for signaling methods and network-UE behaviors so as to identify the required dataset when model updating / re- training as any activated model can be also impacted due to model / data drift. When ML condition changes, the enabled AI / ML model(s) can be impacted for model performance due to data / model drift. In this case, model re-training / updating can be executed.

[0012] US 2022400373 describes the method of determining neural network functions and configuring models for performing wireless communications management procedures.

[0013] US 2022108214 explains ML model management method for network data analytics function device, and US 2022337487 shows that a network entity determines at least one model parameter of a model for digitally analyzing input data depending on the at least one model parameter of a model, the network entity being configured to receive a model request. 202404734

[0014] - 3 -

[0015] WO 2023277780 contains a method of downloading of a compiled machine code version of a ML model to a wireless communication device.

[0016] WO 2022258149 provides a way for training a model in a server device based on training data in a user device, and WO 2022228666 shows about influencing training of a ML model based on a training policy provided by an actor node.

[0017] WO 2022161624 describes the method of receiving a request for retrieving or executing a ML model or a combination of ML models.

[0018] The present disclosure solves the cited problem above by the proposed embodiments and describes method of model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling of using the pre-configured AI / ML (artificial intelligence / machine learning) based model identification with ML identifiers in wireless mobile communication system including base station e.g., gNB, TN, NTN and mobile station e.g., UE. In AI / ML model is applied to radio access network, signaling overhead can be significantly increased for varying types of associated IDs along with model identification. Therefore, model operation e.g., model training / inferencing / monitoring / updating can be set up between network and UE by using a list of multiple ML identifier format types for ML operation.

[0019] In the first embodiment, the method of model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling in a wireless communication system is characterized by comprising the steps, setting ML identifiers for multiple ML ID elements; configuring bitmap for different combinations of ML ID elements; adapting data format type of ML identifiers; containing varying ML identifier format types and the associated sub-types.

[0020] In some embodiments of the method according to the first aspect, the method is characterized by that ML identifiers consist of {model ID, dataset ID, functionality ID, 202404734

[0021] - 4 - condition ID, LCM ID, etc.} so that any subset of the grouped ID elements within ML identifiers is configured as different format types.

[0022] In some embodiments of the method according to the first aspect, the method is characterized by that the data format type of ML identifiers indicates the relationship between ML parameter and ML identifiers.

[0023] In some embodiments of the method according to the first aspect, the method is characterized by that the corresponding ML assistance information and / or device behavior after configuring a specific data format type of ML identifiers is determined based on the aligned ML identifiers for use.

[0024] In some embodiments of the method according to the first aspect, the method is characterized by that the associated data format type with the determined specific ML use case or application is configured for indication signaling about data format type for use between network side and UE side and the related assistance information is sent along with the indicated format type message.

[0025] In some embodiments of the method according to the first aspect, the method is characterized by that each bit of the bitmap indicates what the associated ML ID(s) needs to be extracted for activation within the configured data format type.

[0026] In some embodiments of the method according to the first aspect, the method is characterized by that bitmap index is applied to enable / disable different combinations of ML IDs for using a single data format type representing ML identifiers or using multiple data format types representing ML identifiers.

[0027] In some embodiments of the method according to the first aspect, the method is characterized by that data format type information representing ML identifiers is signaled as part of RRC message or L1 / L2 signaling.

[0028] In some embodiments of the method according to the first aspect, the method is characterized by that adaptation of ML data format type or ML ID is performed 202404734

[0029] - 5 -

[0030] (semi-)statically such that ML data format type / ML ID is applied to UE with RRC reconfiguration.

[0031] In some embodiments of the method according to the first aspect, the method is characterized by that adaptation of ML data format type or ML ID is performed dynamically where ML data format type / ML ID is applied to UE with L1 or L2 message, which is PDCCH or MAC CE.

[0032] In some embodiments of the method according to the first aspect, the method is characterized by that any part of ML identifiers within a given data format type is allowed for updating or switching via L1 or L2 signaling.

[0033] In some embodiments of the method according to the first aspect, the method is characterized by that selection of ML data format type or ML ID is performed to reduce signaling overhead depending on monitoring of network traffic load status.

[0034] In some embodiments of the method according to the first aspect, the method is characterized by that a specific Information Element (IE) within the RRC message is used to convey both specific format type and the associated parameter information for messaging ML identifier data format type.

[0035] In some embodiments of the method according to the first aspect, the method is characterized by that a specific ML identifier format type with any given specific combinations of ML use case, LCM phase, RRC state and / or ML model is indicated to UE via L1 or L2 or RRC signaling.

[0036] In some embodiments of the method according to the first aspect, the method is characterized by that the corresponding ML operation associated with the indicated ML identifier format type is activated at UE along with the identified model and / or dataset collection.

[0037] In some embodiments of the method according to the first aspect, the method is characterized by that candidate identifiers consisting of data format types include 202404734

[0038] - 6 - model ID, dataset ID, functionality ID, condition ID, LCM ID, etc. where each IDs are for identification of ML model, dataset, ML functionality, condition (related to ML configuration), LCM (dataset collection, training, inferencing, monitoring, etc.), respectively.

[0039] In some embodiments of the method according to the first aspect, the method is characterized by that each format types are allowed to have sub-types such as Format type 1-1 , 1-2, etc. so that variants of each format types are supported if applicable.

[0040] In some embodiments of the method according to the first aspect, the method is characterized by that the number of ML identifier format types and the associated sub-types vary according to different deployment scenarios and applications along with network specification.

[0041] In some embodiments of the method according to the first aspect, the method is characterized by that different UE behaviors associated with the indicated ML identifier format type are determined such as dataset collection, model (de- )activation / monitoring / (re-)training / switching, measurement of ML device capability update / model performance.

[0042] According to a second aspect, the present disclosure relates to an apparatus for model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling in a wireless communication system, the apparatus comprising a wireless transceiver, a processor coupled with a memory in which computer program instructions are stored, said instructions being configured to implement steps of the first aspect.

[0043] According to a third aspect, the present disclosure relates to an user Equipment comprising an apparatus according to the second aspect.

[0044] According to a fourth aspect, the present disclosure relates to a gNB comprising an apparatus according to the second aspect. 202404734

[0045] - 7 -

[0046] According to a fifth aspect, the present disclosure relates to a Wireless communication system for model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling, wherein the wireless communication systems comprises user equipment according the third aspect, gNB according the fourth aspect, whereby the user Equipment and the gNB each comprises a processor coupled with a memory in which computer program instructions are stored, said instructions being configured to implement steps of the first aspect.

[0047] BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 is an exemplary data format types of ML identifiers.

[0049] Figure 2 is an exemplary mapping table of bitmap index.

[0050] Figure 3 is an exemplary flow chart of configuring ML identifier format types at network side.

[0051] Figure 4 is an exemplary flow chart of applying ML identifier format type at UE side.

[0052] DETAILED DESCRIPTION

[0053] The detailed description set forth below, with reference to annexed drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In particular, although terminology from 3GPP 5G NR may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the invention. 202404734

[0054] - 8 -

[0055] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0056] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0057] In some embodiments, a more general term “network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and / or with another network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc), Operations & Maintenance (O&M), Operations Support System (OSS), Self Optimized Network (SON), positioning node (e.g. Evolved- Serving Mobile Location 202404734

[0058] - 9 -

[0059] Centre (E-SMLC)), Minimization of Drive Tests (MDT), test equipment (physical node or software), etc.

[0060] In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.

[0061] Additionally, terminologies such as base station / gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general, “gNodeB” could be considered as device 1 and “UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNodeB (gNB), or UE.

[0062] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.

[0063] For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off- the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical 202404734

[0064] - 10 - blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0065] Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and / or program code, referred hereafter as code. The storage devices may be tangible, non- transitory, and / or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code

[0066] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0067] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0068] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and / or machine languages such as assembly languages. The code may execute entirely on the user’s computer, partly on the 202404734

[0069] - 11 - user’s computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user’s computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).

[0070] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment. Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0071] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and / or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that 202404734

[0072] - 12 - each block of the schematic flowchart diagrams and / or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the fimctions / acts specified in the flowchart diagrams and / or block diagrams

[0073] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function / act specified in the flowchart diagrams and / or block diagrams.

[0074] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart diagrams and / or block diagrams.

[0075] The flowchart diagrams and / or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0076] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the 202404734

[0077] - 13 - functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0078] Although various arrow types and line types may be employed in the flowchart and / or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0079] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0080] The detailed description set forth below, with reference to the figures, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. For instance, although 3GPP terminology, from e.g., 5G NR, may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the present disclosure.

[0081] AI / ML Model is a data driven algorithm that applies AI / ML techniques to generate set of outputs based on set of inputs. 202404734

[0082] - 14 -

[0083] AI / ML model delivery is a generic term referring to delivery of an AI / ML model from one entity to another entity in any manner. Note is An entity could mean network node / function (e.g., gNB, LMF, etc.), UE, proprietary server, etc.

[0084] AI / ML model Inference is a process of using trained AI / ML model to produce set of outputs based on set of inputs.

[0085] AI / ML model testing is a subprocess of training, to evaluate the performance of final AI / ML model using dataset different from one used for model training and validation. Differently from AI / ML model validation, testing does not assume subsequent tuning of the model.

[0086] AI / ML model training is a process to train an AI / ML Model [by learning the input / output relationship] in data driven manner and obtain the trained AI / ML Model for inference.

[0087] AI / ML model transfer is a delivery of an AI / ML model over the air interface in manner that is not transparent to 3GPP signalling, either parameters of model structure known at the receiving end or new model with parameters. Delivery may contain full model or partial model.

[0088] AI / ML model validation is a subprocess of training, to evaluate the quality of an AI / ML model using dataset different from one used for model training, that helps selecting model parameters that generalize beyond the dataset used for model training.

[0089] Data collection is a process of collecting data by the network nodes, management entity, or UE for the purpose of AI / ML model training, data analytics and inference.

[0090] Federated learning I federated training is a machine learning technique that trains an AI / ML model across multiple decentralized edge nodes e.g., UEs, gNBs each performing local model training using local data samples. The technique requires multiple interactions of the model, but no exchange of local data samples. 202404734

[0091] - 15 -

[0092] Functionality identification is a process / method of identifying an AI / ML functionality for the common understanding between the NW and the UE. Note is Information regarding the AI / ML functionality may be shared during functionality identification. Where AI / ML functionality resides depends on the specific use cases and sub use cases.

[0093] Model activation means enable an AI / ML model for specific AI / ML-enabled feature.

[0094] Model deactivation means disable an AI / ML model for specific AI / ML-enabled feature.

[0095] Model download means Model transfer from the network to UE.

[0096] Model identification is A process / method of identifying an AI / ML model for the common understanding between the NW and the UE. The process / method of model identification may or may not be applicable and regarding the AI / ML model may be shared during model identification.

[0097] Model monitoring is A procedure that monitors the inference performance of the AI / ML model.

[0098] Model parameter update is Process of updating the model parameters of model. Model selection is the process of selecting an AI / ML model for activation among multiple models for the same AI / ML enabled feature. Model selection may or may not be carried out simultaneously with model activation.

[0099] Model switching is deactivating currently active AI / ML model and activating different AI / ML model for specific AI / ML-enabled feature.

[0100] Model update is process of updating the model parameters and / or model structure of model.

[0101] Model upload is Model transfer from UE to the network. 202404734

[0102] - 16 -

[0103] Network-side (AI / ML) model is an AI / ML Model whose inference is performed entirely at the network.

[0104] Offline field data is the data collected from field and used for offline training of the AI / ML model.

[0105] Offline training is an AI / ML training process where the model is trained based on collected dataset, and where the trained model is later used or delivered for inference. Note is This definition only serves as guidance. There may be cases that may not exactly conform to this definition but could still be categorized as offline training by commonly accepted conventions.

[0106] Online field data is the data collected from field and used for online training of the AI / ML model.

[0107] Online training is an AI / ML training process where the model being used for inference) is (typically continuously) trained in (near) real-time with the arrival of new training samples. Note is the notion of (near) real-time vs. non real-time is context- dependent and is relative to the inference time-scale. This definition only serves as guidance.

[0108] There may be cases that may not exactly conform to this definition but could still be categorized as online training by commonly accepted conventions. Note is Fine- tuning / re-training may be done via online or offline training. This note could be removed when we define the term fine-tuning.

[0109] Reinforcement Learning (RL) is a process of training an AI / ML model from input (a.k.a. state) and feedback signal (a.k.a. reward) resulting from the model’s output (a.k.a. action) in an environment the model is interacting with.

[0110] Semi-supervised learning is a process of training model with mix of labelled data and unlabelled data. 202404734

[0111] - 17 -

[0112] Supervised learning is a process of training model from input and its corresponding labels.

[0113] Two-sided (AI / ML) model is a paired AI / ML Model(s) over which joint inference is performed, where joint inference comprises AI / ML Inference whose inference is performed jointly across the UE and the network, i.e, the first part of inference is firstly performed by UE and then the remaining part is performed by gNB, or vice versa.

[0114] UE-side (AI / ML) model is an AI / ML Model whose inference is performed entirely at the UE.

[0115] Unsupervised learning is a process of training model without labelled data.

[0116] Proprietary-format models is ML models of vendor-Zdevice-specific proprietary format, from 3GPP perspective. They are not mutually recognizable across vendors and hide model design information from other vendors when shared.

[0117] Open-format models is ML models of specified format that are mutually recognizable across vendors and allow interoperability, from 3GPP perspective. They are mutually recognizable between vendors and do not hide model design information from other vendors when shared.

[0118] The disclosure is related to wireless communication system, which may be for example a 5G NR wireless communication system. More specifically, it represents a RAN of the wireless communication system, which is used exchange data with UEs via radio signals. For example, the RAN may send data to the UEs (downlink, DL), for instance data received from a core network (CN). The RAN may also receive data from the UEs (uplink, UL), which data may be forwarded to the CN.

[0119] In the examples illustrated, the RAN comprises one base station, BS. Of course, the RAN may comprise more than one BS to increase the coverage of the wireless 202404734

[0120] - 18 - communication system. Each of these BSs may be referred to as NB, eNodeB (or eNB), gNodeB (or gNB, in the case of a 5G NR wireless communication system), an access point or the like, depending on the wireless communication standard(s) implemented.

[0121] The UEs are located in a coverage of the BS. The coverage of the BS corresponds for example to the area in which UEs can decode a PDCCH transmitted by the BS.

[0122] An example of a wireless device suitable for implementing any method, discussed in the present disclosure, performed at a UE corresponds to an apparatus that provides wireless connectivity with the RAN of the wireless communication system, and that can be used to exchange data with said RAN. Such a wireless device may be included in a UE. The UE may for instance be a cellular phone, a wireless modem, a wireless communication device, a handheld device, a laptop computer, or the like. The UE may also be an Internet of Things (loT) equipment, like a wireless camera, a smart sensor, a smart meter, smart glasses, a vehicle (manned or unmanned), a global positioning system device, etc., or any other equipment that may run applications that need to exchange data with remote recipients, via the wireless device.

[0123] The wireless device comprises one or more processors and one or more memories. The one or more processors may include for instance a central processing unit (CPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc. The one or more memories may include any type of computer readable volatile and non-volatile memories (magnetic hard disk, solid-state disk, optical disk, electronic memory, etc.). The one or more memories may store a computer program product, in the form of a set of programcode instructions to be executed by the one or more processors to implement all or part of the steps of a method for exchanging data, performed at a UE’s side, according to any one of the embodiments disclosed herein.

[0124] The wireless device can comprise also a main radio, MR, unit. The MR unit corresponds to a main wireless communication unit of the wireless device, used for 202404734

[0125] - 19 - exchanging data with BSs of the RAN using radio signals. The MR unit may implement one or more wireless communication protocols, and may for instance be a 3G, 4G, 5G, NR, WiFi, WiMax, etc. transceiver or the like. In preferred embodiments, the MR unit corresponds to a 5G NR wireless communication unit.

[0126] The following explanation will provide the detailed description of the mechanism about pre-configuring and signaling the specific information about model online training by configuring a set of UE behaviors. AI / ML based techniques are currently applied to many different applications and 3GPP also started to work on its technical investigation to apply to multiple use cases based on the observed potential gains. AI / ML lifecycle can be split into several stages such as data collection / pre- processing, model training, model testing / validation, model deployment / update, model monitoring etc., where each stage is equally important to achieve target performance with any specific model(s).

[0127] In applying AI / ML model for any use case or application, one of the challenging issues is to manage the lifecycle of AI / ML model. It is mainly because the data / model drift occurs during model deployment / inference and it results in performance degradation of AI / ML model. Fundamentally, the dataset statistical changes occur after model is deployed and model inference capability is also impacted with unseen data as input. In a similar aspect, the statistical property of dataset and the relationship between input and output for the trained model can be changed with drift occurrence. In this context, model training or re-training is one of key issues for model performance maintenance as model performance such as inferencing and / or training is dependent on different model execution environment with varying configuration parameters.

[0128] To handle this issue, collaboration between UE and gNB is highly important to track model performance and re-configure model corresponding to different environments. AI / ML model needs model monitoring after deployment because model performance cannot be maintained continuously due to drift and update feedback is then provided to re-train / update the model or select alternative model. When AI / ML model enabled wireless communication network is deployed, it is then important to consider how to 202404734

[0129] - 20 - handle AI / ML model in activation with re-configuration for wireless devices under operations such as model training, inference, updating, etc. When model-ID based LCM is operated, any matched model ID(s) need to be valid between entities (e.g., NW-UE, UE-UE). If the requested model ID is not available, model itself need to be transferred and hence the related signaling overhead can heavily increase depending on model type / structure. In this method, a list of multiple ML identifier data format types for ML operation related signaling between network side and UE side are configured.

[0130] Firstly, ML identifiers for use are set, e.g., ML ID set = {model ID, dataset ID, functionality ID, condition ID, LCM ID, etc.}. The data format type of ML identifiers is also intended to describe the relationship between ML parameter and ML identifiers. Specifically, after configuring a specific data format type of ML identifiers, the corresponding ML assistance information and / or device behavior follows based on the aligned ML identifiers for use. ML identifiers consist of {model ID, dataset ID, functionality ID, condition ID, LCM ID, etc.} where any subset of the grouped ID elements can be configured as different format types.

[0131] When any specific ML use case or application is set, the associated data format type can be configured for indication signaling about data format type for use between network side and UE side. The related assistance information can be sent along with the indicated format type message. By adopting bitmap, each bit of the bitmap indicates what the associated ML ID(s) needs to be extracted for activation within the configured data format type. Bitmap index can be applied to enable / disable different combinations of ML IDs for using a single data format type representing ML identifiers or using multiple data format types representing ML identifiers. Data format type information can be signaled as part of RRC message or L1 / L2 signaling. LCM phases and / or RRC states can be associated with specific format types if applicable. Adaptation of ML data format type or ML ID can be performed (semi-)statically where ML data format type / ML ID is applied to UE with RRC re-configuration or it can be performed dynamically where ML data format type / ML ID is applied to UE with L1 or L2 message (e.g., PDCCH or MAC CE). In addition, any part of ML identifiers within a given data format type can be allowed for updating or switching via L1 or L2 202404734

[0132] - 21 - signaling. Depending on monitoring of network traffic load status, selection of ML data format type or ML ID can be performed to reduce signaling overhead. For messaging ML identifier data format type, a specific Information Element (IE) within the RRC message can be used to convey both specific format type and the associated parameter information.

[0133] For example, the new IE includes Field 1 specifying the format type with high priority and Field 2 specifying the format type with low priority. As an example scenario, a set of ML identifier format types for ML operation are configured at network side, each associated with different combinations of ML use cases, LCM phases, RRC states and / or ML models. ML configuration information with ML identifier format types is then sent to UE via system information or RRC signaling. With any given specific combinations of ML use case, LCM phase, RRC state and / or ML model, a specific ML identifier format type is indicated to UE via L1 or L2 or RRC signaling. Based on the indicated ML identifier format type, the corresponding ML operation is activated at UE along with the identified model and / or dataset collection. Candidate identifiers consisting of data format types include model ID, dataset ID, functionality ID, condition ID, LCM ID, etc. where each IDs are for identification of ML model, dataset, ML functionality, condition (related to ML configuration), LCM (dataset collection, training, inferencing, monitoring, etc.), respectively.

[0134] Especially, condition ID can vary such as identification of site, device capability, ML configuration, etc. depending on implementation scenarios. Data format type of ML identifiers can represent the relationship between ML parameter and ML identifiers. Optionally, for each format types, there can be sub-types such as Format type 1-1 , 1- 2, etc. so that variants of each format types can be supported if applicable. The number of ML identifier format types and the associated sub-types can vary according to different deployment scenarios and applications along with network specification. Depending on the indicated ML identifier format type, different UE behaviors follows such as dataset collection, model (de-)activation / monitoring / (re- )training / switching, measurement of ML device capability update / model performance, etc. 202404734

[0135] - 22 -

[0136] The gNB or network entity configures and transmits ML-related signaling using multiple ML identifier data format types to indicate different types of ML operations or functionalities such as training, inference, or model switching. Each ML identifier is assigned a unique encoding format and size. The identifiers and their respective descriptions, for example, are listed such as model ID (MID) for encoding a unique identifier for an ML model, dataset ID (DID) for encoding the identity of a dataset, functionality ID (FID) referring to ML functionality type (e.g., classification, regression), condition ID (CID) referring to operational or environmental conditions, and LCM phase ID (LCMID) indicating life cycle phase (e.g., training, inference, monitoring). These IDs are defined in a structured format and each format type uses a specific composition rule. For representation of format types, an ML identifier data format type is defined for composing a message structure from the above identifiers. For example, format type 1 includes MID, DID, and FID. Format type 2 includes MID, CID, LCMID. Format type 3 includes DID, CID. Bitmaps are used to indicate which IDs are active within a given format type.

[0137] Figure 1 shows an exemplary data format types of ML identifiers. In this example, a set of ML identifier format types for ML operation are configured at network side. Candidate identifiers consisting of data format types include model ID, dataset ID, functionality ID, condition ID, LCM ID, etc. where each IDs are for identification of ML model, dataset, ML functionality, condition (related to ML configuration), LCM (dataset collection, training, inferencing, monitoring, etc.), respectively. Especially, condition ID can vary such as identification of site, device capability, ML configuration, etc. depending on implementation scenarios. Data format type of ML identifiers can represent the relationship between ML parameter and ML identifiers. Optionally, for each format types, there can be sub-types such as Format type 1-1 , 1- 2, etc. so that variants of each format types can be supported if applicable. The number of ML identifier format types and the associated sub-types can vary according to different deployment scenarios and applications along with network specification. 202404734

[0138] - 23 -

[0139] Figure 2 shows an exemplary mapping table of bitmap index. In this example, by adopting bitmap, each bit of the bitmap indicates what the associated ML ID(s) needs to be extracted for activation within the configured data format type.

[0140] Bitmap index can be applied to enable / disable different combinations of ML IDs using a single data format type representing ML identifiers or using multiple data format types representing ML identifiers. For bitmap index configuration, either single-bit or multi-bit bitmap can be used for varying deployment / application scenarios.

[0141] Figure 3 shows an exemplary flow chart of configuring ML identifier format types at network side. In this example, a set of ML identifier format types for ML operation are configured at network side, each associated with different combinations of ML use cases, LCM phases, RRC states and / or ML models. ML configuration information with ML identifier format types is then sent to UE via system information or RRC signaling. With any given specific combinations of ML use case, LCM phase, RRC state and / or ML model, a specific ML identifier format type is indicated to UE via L1 or L2 or RRC signaling.

[0142] Figure 4 shows an exemplary flow chart of applying ML identifier format type at UE side. In this example, based on the indicated ML identifier format type, the corresponding ML operation is activated at UE along with the identified model and / or dataset collection. Depending on the indicated ML identifier format type, different UE behaviors follows such as dataset collection, model (de-)activation / monitoring / (re- )training / switching, measurement of ML device capability update / model performance, etc.

Claims

202404734- 24 -CLAIMS1. A method of model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling in a wireless communication system, comprising:• Setting ML identifiers for multiple ML ID elements;• Configuring bitmap for different combinations of ML ID elements;• Adapting data format type of ML identifiers;• Containing varying ML identifier format types and the associated subtypes.

2. The method according to previous claim 1 , wherein ML identifiers consist of {model ID, dataset ID, functionality ID, condition ID, LCM ID, etc.} so that any subset of the grouped ID elements within ML identifiers is configured as different format types.

3. The method according to one of the previous claims, wherein the data format type of ML identifiers indicates the relationship between ML parameter and ML identifiers.

4. The method according to one of the previous claims, wherein the corresponding ML assistance information and / or device behavior after configuring a specific data format type of ML identifiers is determined based on the aligned ML identifiers for use.

5. The method according to one of the previous claims, wherein the associated data format type with the determined specific ML use case or application is configured for indication signaling about data format type for use between network side and UE side and the related assistance information is sent along with the indicated format type message.202404734- 25 -6. The method according to one of the previous claims, wherein each bit of the bitmap indicates what the associated ML ID(s) needs to be extracted for activation within the configured data format type.

7. The method according to one of the previous claims, wherein bitmap index is applied to enable / disable different combinations of ML IDs for using a single data format type representing ML identifiers or using multiple data format types representing ML identifiers.

8. The method according to one of the previous claims, wherein data format type information representing ML identifiers is signaled as part of RRC message or L1 / L2 signaling.

9. The method according to one of the previous claims, wherein adaptation of ML data format type or ML ID is performed (semi-)statically such that ML data format type / ML ID is applied to UE with RRC re-configuration.

10. The method according to one of the previous claims, wherein adaptation of ML data format type or ML ID is performed dynamically where ML data format type / ML ID is applied to UE with L1 or L2 message, which is PDCCH or MAC CE.11 . The method according to one of the previous claims, wherein any part of ML identifiers within a given data format type is allowed for updating or switching via L1 or L2 signaling.

12. The method according to one of the previous claims, wherein selection of ML data format type or ML ID is performed to reduce signaling overhead depending on monitoring of network traffic load status.

13. The method according to one of the previous claims, wherein a specific Information Element (IE) within the RRC message is used to convey both specific format type and the associated parameter information for messaging ML identifier data format type.202404734- 26 -14. The method according to one of the previous claims, wherein a specific ML identifier format type with any given specific combinations of ML use case, LCM phase, RRC state and / or ML model is indicated to UE via L1 or L2 or RRC signaling.

15. The method according to one of the previous claims, wherein the corresponding ML operation associated with the indicated ML identifier format type is activated at UE along with the identified model and / or dataset collection.

16. The method according to one of the previous claims, wherein candidate identifiers consisting of data format types include model ID, dataset ID, functionality ID, condition ID, LCM ID, etc. where each IDs are for identification of ML model, dataset, ML functionality, condition (related to ML configuration), LCM (dataset collection, training, inferencing, monitoring, etc.), respectively.

17. The method according to one of the previous claims, wherein each format types are allowed to have sub-types such as Format type 1 -1 , 1 -2, etc. so that variants of each format types are supported if applicable.

18. The method according to one of the previous claims, wherein the number of ML identifier format types and the associated sub-types vary according to different deployment scenarios and applications along with network specification.

19. The method according to one of the previous claims, wherein different UE behaviors associated with the indicated ML identifier format type are determined such as dataset collection, model (de-)activation / monitoring / (re- )training / switching, measurement of ML device capability update / model performance.

20. Apparatus for model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling in a wireless communication system, the apparatus comprising a wireless transceiver, a202404734- 27 - processor coupled with a memory in which computer program instructions are stored, said instructions being configured to implement steps of the claims 1 to 19. 21 . User Equipment comprising an apparatus according to claim 20.

22. gNB comprising an apparatus according to claim 20.

23. Wireless communication system method of model data format configuration by configuring a list of multiple ML identifier data format types for ML operation related signaling, wherein the wireless communication systems comprises user equipment according to claim 21 , gNB according to claim 22, whereby the user Equipment and the gNB each comprises a processor coupled with a memory in which computer program instructions are stored, said instructions being configured to implement steps of the claims 1 to 19.

Images