Method and apparatus for supporting ai / ML-based positioning in wireless communication networks

Abstract

A User Equipment (UE) for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning is provided. The UE includes at least one processor; and at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to: receive, from a Base Station (BS), a logging configuration, the logging configuration indicating one or more triggering conditions; and in response to determining that the one or more triggering conditions are satisfied, log a measurement result based on the logging configuration. In addition, a method and a Base Station are also provided.

Description

METHOD AND APPARATUS FOR SUPPORTING AI / ML-BASED POSITIONING IN WIRELESS COMMUNICATION NETWORKSThe present disclosure is related to wireless communication and, more specifically, to a User Equipment (UE), Base Station (BS), and method for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning in the wireless communication networks.Various efforts have been made to improve different aspects of wireless communication for the cellular wireless communication systems, such as the 5thGeneration (5G) New Radio (NR), by improving data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types, accommodating various use cases, such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). As the demand for radio access continues to grow, however, there exists a need for further improvements in the next-generation wireless communication systems, such as improvements in a beam management procedure.Summery of InventionThe present disclosure is directed to a User Equipment (UE), a Base Station (BS), and a method for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning in the wireless communication networks.According to a first aspect of the present disclosure, a User Equipment (UE) for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning is provided. The UE includes: at least one processor; and at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to: receive, from a Base Station (BS), a logging configuration, the logging configuration indicating one or more triggering conditions; and in response to determining that the one or more triggering conditions are satisfied, log a measurement result based on the logging configuration.In an implementation of the first aspect, the logging configuration includes a first configuration and indicates a list indicating multiple triggering conditions. The one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: in response to determining that the first configuration is configured to be a first value, log the measurement result based on the logging configuration in response to all of the multiple triggering conditions indicated by the list being satisfied; and in response to determining that the first configuration is configured to be a second value, log the measurement result based on the logging configuration in response to one of the multiple triggering conditions being satisfied.In another implementation of the first aspect, the logging configuration indicates a list including multiple elements. The multiple elements include at least one first-type element and at least one second-type element. Each of the first-type elements indicates a triggering condition. Each of the second-type elements indicates a combination of two or more of the multiple elements.In another implementation of the first aspect, the logging configuration includes a second configuration. The one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: stop logging the measurement result in response to a count of logged instances reaching a value indicated by the second configuration.In another implementation of the first aspect, the logging configuration includes a third configuration. One or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: start a timer in response to a reception of the third configuration, the timer having an initial value indicated by the third configuration; and log a next measurement result in response to an expiry of the timer.In another implementation of the first aspect, the third configuration indicates an interval of two consecutive logged instances.In another implementation of the first aspect, the logging configuration includes a fourth configuration. An interval of two consecutive logged instances is associated with the fourth configuration and a configured measurement periodicity.According to a second aspect of the present disclosure, a BS for supporting AI / ML-based positioning is provided. The BS includes: at least one processor; and at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to: transmit, to a UE, a logging configuration, the logging configuration indicating one or more triggering conditions. The logging configuration causes the UE to: in response to determining that the one or more triggering conditions are satisfied, log a measurement result based on the logging configuration.In an implementation of the second aspect, the logging configuration includes a first configuration and indicates a list indicating multiple triggering conditions. The logging configuration further causes the UE to: in response to determining that the first configuration is configured to be a first value, log the measurement result based on the logging configuration in response to all of the multiple triggering conditions indicated by the list being satisfied; and in response to determining that the first configuration is configured to be a second value, log the measurement result based on the logging configuration in response to one of the multiple triggering conditions being satisfied.In another implementation of the second aspect, the logging configuration indicates a list including multiple elements. The multiple elements include at least one first-type element and at least one second-type element. Each of the first-type elements indicates a triggering condition. Each of the second-type elements indicates a combination of two or more of the multiple elements.In another implementation of the second aspect, the logging configuration includes a second configuration. The logging configuration further causes the UE to: stop logging the measurement result in response to a count of logged instances reaching a value indicated by the second configuration.In another implementation of the second aspect, the logging configuration includes a third configuration. The logging configuration further causes the UE to: start a timer in response to a reception of the third configuration, the timer having an initial value indicated by the third configuration; and log a next measurement result in response to an expiry of the timer.In another implementation of the second aspect, the third configuration is configured for the UE to determine an interval of two consecutive logged instances.In another implementation of the second aspect, the logging configuration includes a fourth configuration. The fourth configuration is configured for the UE to determine an interval of two consecutive logged instances based on the fourth configuration and a configured measurement periodicity.According to a third aspect of the present disclosure, a method performed by a UE for supporting AI / ML-based positioning is provided. The method includes: receiving, from a BS, a logging configuration, the logging configuration indicating one or more triggering conditions; and in response to determining that the one or more triggering conditions are satisfied, logging a measurement result based on the logging configuration.Aspects of the present disclosure are best understood from the following detailed disclosure and the corresponding figures. Various features are not drawn to scale and dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.FIG. 1 is a flowchart illustrating a method / process performed by a User Equipment (UE) for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning, according to an example implementation of the present disclosure.FIG. 2 is a block diagram illustrating a node for wireless communication, according to an example implementation of the present disclosure.The following contains specific information related to implementations of the present disclosure. The drawings and their accompanying detailed disclosure are merely directed to implementations. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be obvious to those skilled in the art.Unless noted otherwise, like or corresponding elements among the drawings may be indicated by like or corresponding reference numerals. Moreover, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative dimensions.For the purposes of consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may be different in other respects and may not be narrowly confined to what is illustrated in the drawings.References to “one implementation,” “an implementation,” “example implementation,” “various implementations,” “some implementations,” “implementations of the present application,” etc., may indicate that the implementation(s) of the present application so described may include a particular feature, structure, or characteristic, but not every possible implementation of the present application necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “In some implementations,” or “in an example implementation,” “an implementation,” do not necessarily refer to the same implementation, although they may. Moreover, any use of phrases like “implementations” in connection with “the present application” are never meant to characterize that all implementations of the present application must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some implementations of the present application” includes the stated particular feature, structure, or characteristic. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising,” when utilized, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in the so-described combination, group, series, and the equivalent.The expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C.” The terms “system” and “network” may be used interchangeably. The term “and / or” is only an association relationship for describing associated objects and represents that three relationships may exist such that A and / or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. The character “ / ” generally represents that the associated objects are in an “or” relationship.For the purposes of explanation and non-limitation, specific details, such as functional entities, techniques, protocols, and standards, are set forth for providing an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures are omitted so as not to obscure the present disclosure with unnecessary details.Persons skilled in the art will immediately recognize that any network function(s) or algorithm(s) disclosed may be implemented by hardware, software, or a combination of software and hardware. Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.A software implementation may include computer-executable instructions and / or Artificial Intelligence (AI) / Machine Learning (ML) module(s) stored on a computer-readable medium, such as memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding computer-executable instructions and perform the disclosed network function(s), AI / ML module(s), or algorithm(s). The AI / ML module(s) may be implemented with a supervised learning approach, a semi-supervised learning approach, an unsupervised learning approach (e.g., Transductive approach and Inductive approach), a federated learning approach, or a reinforcement learning (RL) approach, but the present disclosure is not limited thereto. The computer-executable instructions associated with the AI module(s) and / or the ML module(s) may include but are not limited to, data management instructions (e.g., collection instructions, validation instructions…etc.), model monitoring and management instructions (e.g., NW KPIs monitoring, model input / output monitoring, model selection / switching / update / upload / download, model (de)activation, model identification, functionality selection…etc.), and / or pre-process input instructions.

[0009] The microprocessors or general-purpose computers may include Application-Specific Integrated Circuits (ASICs), programmable logic arrays, Central Processing Units (CPUs), Tensor Processing Units (TPUs), Graphics Processing Units (GPUs), General-purpose computing on GPUs (GPGPU, or less often GPGP), and / or using one or more Digital Signal Processors (DSPs). Although some of the disclosed implementations are oriented to software installed and executing on computer hardware, alternative implementations implemented as firmware, as hardware, or as a combination of hardware and software are well within the scope of the present disclosure. The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions (e.g., computer-readable instructions related to AI module(s) and / or the ML module(s)), data structures, program modules or data. The computer-readable medium may include, but is not limited to, Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), High Bandwidth Memory (HBM), Magnetoresistive Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Resistive Random Access Memory (RRAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory (or other memory technology), Compact Disc Read-Only Memory (CD-ROM) , Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), or any other equivalent medium capable of storing computer-readable instructions. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions (e.g., computer-readable instructions related to AI module(s) and / or the ML module(s)), data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanisms and include any information delivery media.The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the previously listed components should also be included within the scope of computer-readable media.A radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, a 5G NR Radio Access Network (RAN), 5G-Advanced (5G-A) system, or an open radio access network (O-RAN) may typically include at least one base station (BS), at least one UE, and one or more optional network elements that provide connection within a network. The BS and one or more optional network elements enable the UE to access a radio network. Thus the UE may communicate with the network, such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a Next-Generation Core (NGC), a 5G Core (5GC), or an internet via a RAN established by one or more BSs and the network elements / functions.A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, a virtual reality (VR) device, an augmented (AR) device, an Internet of Things (IoT) device, an unmanned aerial vehicle (UAV), or a Personal Digital Assistant (PDA) with wireless communication capability. The UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN. In some implementations, the UE may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).The BS may be configured to provide communication services according to at least a Radio Access Technology (RAT), such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic Wideband-Code Division Multiple Access (W-CDMA), High-Speed Packet Access (HSPA), LTE, LTE-A, evolved / enhanced LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G), 5G-A, and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM / GERAN, a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next-generation Node B (gNB) in the 5G-RAN (or in the 5G Access Network (5G-AN)), or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface. In some implementations, the BS may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).The BS may be operable to provide radio coverage to a specific geographical area using multiple cells forming the RAN. The BS may support the operations of the cells. Each cell may be operable to provide services to at least one UE within its radio coverage.Each cell (may often referred to as a serving cell) may provide services to one or more UEs within the cell’s radio coverage, such that each cell schedules the DL (and optionally UL resources) to at least one UE within its radio coverage for DL (and optionally UL packet transmissions from the UE). The BS may communicate with one or more UEs in the radio communication system via the cells.A cell may allocate Sidelink (SL) resources for supporting Proximity Service (ProSe), LTE SL services, LTE / NR sidelink communication services, LTE / NR sidelink discovery services, and / or LTE / NR Vehicle-to-Everything (V2X) services. In addition, a cell may allocate DL and / or UL resources for supporting Multicast / Broadcast Service (MBS) services, Non-Terrestrial Networks (NTN) services, positioning services, power serving services and / or Network Energy Saving (NES) services.In Multi-RAT Dual Connectivity (MR-DC) cases, the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) may be referred to as a Special Cell (SpCell). A Primary Cell (PCell) may include the SpCell of an MCG. A Primary SCG Cell (PSCell) may include the SpCell of an SCG. MCG may include a group of serving cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCells). An SCG may include a group of serving cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.As discussed above, the frame structure for NR may support flexible configurations for accommodating various next generation (e.g., 5G) communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), while fulfilling high reliability, high data rate, and low latency requirements. The Orthogonal Frequency-Division Multiplexing (OFDM) technology in the 3GPP may serve as a baseline for an NR waveform. The scalable OFDM numerology, such as adaptive sub-carrier spacing, channel bandwidth, and Cyclic Prefix (CP), may also be used.Two coding schemes may be considered for NR, specifically, Low-Density Parity-Check (LDPC) code and Polar Code. The coding scheme adaption may be configured based on channel conditions and / or service applications.At least the DL transmission data, a guard period, and UL transmission data should be included in a transmission time interval (TTI) of a single NR frame. The respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable based on, for example, the network dynamics of NR. SL resources may also be provided in an NR frame to support ProSe services or V2X services.Any two or more than two of the following paragraphs, (sub)-bullets, points, actions, behaviors, terms, or claims described in the present disclosure may be combined logically, reasonably, and properly to form a specific method.Any sentence, paragraph, (sub)-bullet, point, action, behaviors, terms, or claims described in the present disclosure may be implemented independently and separately to form a specific method.Dependency, e.g., “based on”, “more specifically”, “preferably”, “in one embodiment”, “in some implementations”, etc., in the present disclosure is just one possible example which would not restrict the specific method.In some implementations, all the designs / embodiment / implementations introduced within this disclosure are not limited to be applied for dealing with the problems discussed within this disclosure. For example, the described embodiments may be applied to solve other problems that exist in the RAN of wireless communication systems. In some implementations, all of the numbers listed within the designs / embodiment / implementations introduced within this disclosure are just examples and for illustration, for example, of how the described methods are executed.In a wireless cellular network, applications such as navigation and localized services may need the location information of a mobile device, such as a User Equipment (UE). As such, the positioning method plays an essential role in these applications and services.Currently, positioning mechanisms may be classified into cellular-based (e.g., positioning methods based on the system supported by Long-Term Evolution (LTE) and / or New Radio (NR)) and non-cellular-based (e.g., positioning methods based on the system supported by satellites, such as Global Navigation Satellite System (GNSS), WiFi, and / or Bluetooth). For cellular-based positioning methods, time difference of arrival (TDoA), angle of arrival (AoA), angle of departure (AoD), and multiple Round Trip Time (multi-RTT) may be designed by leveraging the positioning reference signal (PRS). However, these positioning methods may require a line-of-sight (LoS) measurement environment. This means the accuracy of the positioning methods may degrade when there is no LoS path measured by the UE / gNB.Artificial Intelligence (AI) / Machine Learning (ML) has been discussed for application to the cellular network system by the Third Generation Partnership Project (3GPP). Currently, positioning accuracy enhancement is one of the targeted use cases that could be enhanced with the aid of AI / ML. By collecting an adequate amount of data, the UE’s location information may approach a higher accuracy.AI / ML may involve, but is not limited to, data collection, model training, model inference, model monitoring, and life cycle management (LCM). Data collection may be further classified according to different aspects. For example, it may be classified by whether the data is collected for training, for inference, or for monitoring, and whether the data is collected for the model at the UE side, at the next generation Node B (gNB) side, or at the Location Management Function (LMF) side.For a network (NW)-side model, data collection may be realized through measurement and reports from the UE. In positioning use cases, the UE may report the measurement results to the LMF. However, the detailed configuration (e.g., what is included in the report and when to report) is not defined. As a result, the present disclosure discusses the content and the method of the report for data collection for model training purposes.The present disclosure considers the following scenarios. A network may include one or more Radio Access Network (RAN) nodes (e.g., evolved Node B (eNB) and / or gNB), each of which may include one or more cells. Each cell may be associated with one or more Transmission and Reception Points (TRP) and / or Transmission Points (TP). A UE may be capable of receiving PRS from one or more TRPs and / or TPs in the same or different cells. An LMF may reside in the core network. Communication between the UE and the LMF may be facilitated via the RAN nodes, while communication between the UE and the LMF may be transparent to the RAN nodes.For AI / ML, a dataset may be collected with different additional conditions (ACs). These ACs may be further classified into network-side (NW-side) ACs and UE-side ACs. An NW-side AC may be known to the network, and it may be implicitly known to the UE or unknown to the UE. A UE-side AC may be known to the UE, and it may be implicitly known to the network or unknown to the network.The UE may be capable of supporting (e.g., collecting data, training, inferencing, managing) one or more AI / ML models and / or functionalities. A functionality may be associated with one or more NW-side ACs and / or one or more UE-side ACs. Also, a functionality may be associated with one or more models.In some implementations, the LMF may send a first Non-Access Stratum (NAS) signaling to request the UE’s capability for supporting the functions related to AI / ML-based positioning. More specifically, the first NAS signaling may be an LTE Positioning Protocol (LPP) message.In some implementations, as shown in Table 1 below, the first NAS signaling may contain an Information Element (IE) (e.g., a RequestCapabilities IE) to request the UE's capability for supporting the functions related to different positioning methods. The RequestCapabilities IE may contain an IE (e.g., an AIML-RequestCapabilities IE) to request the UE's capability for supporting the functions related to AI / ML-based positioning methods.In some implementations, upon receiving the first NAS signaling, if the AIML-RequestCapabilities IE is present, the UE may consider that the LMF is requesting the capabilities for supporting the functions related to AI / ML-based positioning. The UE may then initiate a transmission of the second NAS signaling to the LMF. Otherwise (e.g., if the AIML-RequestCapabilities IE is absent), the UE may consider that the LMF is not requesting the capabilities for supporting the functions related to AI / ML-based positioning.In some implementations, the UE may send a second NAS signaling to indicate the UE's capabilities for supporting the functions related to AI / ML-based positioning. More specifically, the second NAS signaling may be an LPP message.In some implementations, as shown in Table 2 below, the second NAS signaling may contain an IE (e.g., a ProvideCapabilities IE) to provide the UE's capabilities for supporting the functions related to different positioning methods (e.g., DL TDoA, AoA, multi-RTT).In some implementations, if the UE supports functions related to AI / ML-based positioning, the UE may include an IE (e.g., an AIML-ProvideCapabilities IE) in the ProvideCapabilities IE to indicate that the UE supports the functions related to AI / ML-based positioning.In some implementations, if the UE does not support functions related to AI / ML-based positioning, the UE may not include the AIML-ProvideCapabilities IE in the ProvideCapabilities IE. If the UE does not include the AIML-ProvideCapabilities IE in the ProvideCapabilities IE, the UE does not expect to receive the configurations related to AI / ML-based positioning from the LMF.In some implementations, the UE may further indicate specific AI / ML-based positioning capabilities in the AIML-ProvideCapabilities IE.For example, if the UE supports the inference of a UE-side model, or if the UE supports the inference function, the UE may include an IE (e.g., an AIML-Inference IE) in the AIML-ProvideCapabilities IE to indicate that the UE supports the inference of the UE-side model.For example, if the UE supports the data collection of a NW-side model, the UE may include an IE (e.g., an AIML-DataCollection IE or an AIML-DataCollectionForNW IE) in the AIML-ProvideCapabilities IE to indicate that the UE supports the data collection of the NW-side model.For example, if the UE supports the data collection of a UE-side model, the UE may include an IE (e.g., an AIML-DataCollection IE or an AIML-DataCollectionForUE IE) in the AIML-ProvideCapabilities IE to indicate that the UE supports the data collection of the UE-side model.For example, if the UE supports both the data collection of a UE-side model and the data collection of a NW-side model, the UE may include an IE (e.g., an AIML-DataCollection IE) in the AIML-ProvideCapabilities IE to indicate that the UE supports the data collection of a UE-side model and supports the data collection of a NW-side model.For example, if the UE supports the monitoring of a NW-side model, the UE may include an IE (e.g., an AIML-MonitoringNW IE) in the AIML-ProvideCapabilities IE to indicate that the UE supports the monitoring of the NW-side model.In some implementations, the UE may also provide assistance information, which may help the LMF configure the parameters related to data collection for a NW-side model.For example, the UE may use an IE (e.g., an AIML-SuggestedLoggingCounter IE) to indicate a suggested counter value for logging data collection. The AIML-SuggestedLoggingCounter IE may be used as assistance information provided to the LMF. The UE may obtain the suggested counter value by the UE's implementation (e.g., based on the current memory status of the UE).For example, the AIML-SuggestedLoggingCounter IE may take an integer value, and the LMF may consider setting the configured logging counter value below the integer value.In some implementations, if the UE provides the AIML-SuggestedLoggingCounter IE to the LMF, the UE may not expect to receive a logging counter for data collection with a value larger than the provided value of the AIML-SuggestedLoggingCounter IE.For example, the UE may use an IE (e.g., an AIML-GroundTruthAvailable IE) to indicate whether the UE may obtain a ground truth label (e.g., the location of the UE, the LoS indication, etc.) when obtaining a measurement result. The AIML-GroundTruthAvailable IE may be used as assistance information provided to the LMF. It is noted that the UE may obtain a ground truth label by UE-based positioning methods (e.g., GNSS-based, WLAN-based, TDoA-based, AoD-based, RTT-based, etc.) other than an AIML-based positioning method.For example, the AIML-GroundTruthAvailable IE may take an ENUMERATED value of {true}. If the UE is not able to obtain a ground truth label, the UE may not include the AIML-GroundTruthAvailable IE in the assistance information. Otherwise (e.g., if the UE is able to obtain a ground truth label), the UE may include the AIML-GroundTruthAvailable IE with value “true” in the assistance information.For example, the AIML-GroundTruthAvailable IE may take a Boolean value. If the UE is not able to obtain a ground truth label, the UE may include the AIML-GroundTruthAvailable IE with value “false” in the assistance information. Otherwise (e.g., if the UE is able to obtain a ground truth label), the UE may include the AIML-GroundTruthAvailable IE with value “true” in the assistance information.In some implementations, upon receiving the assistance information, the LMF may consider that the UE is able to obtain the ground truth label if the AIML-GroundTruthAvailable IE is present with value “true”. The LMF may consider that the UE is not able to obtain the ground truth label if the AIML-GroundTruthAvailable IE is absent or is present with value “false”.In some implementations, the AIML-GroundTruthAvailable IE may include an IE (e.g., a PositioningMethod IE) to indicate which positioning method is used by the UE to obtain the ground truth label. In some implementations, the PositioningMethod IE may take an ENUMERATED value, and the LMF may identify which UE-based positioning method is used to obtain the ground truth label according to the ENUMERATED value. For example, if the PositioningMethod IE is set as “gnss”, the LMF may consider that the UE uses a GNSS-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “ecid”, the LMF may consider that the UE uses an enhanced cell ID (ECID)-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “wlan”, the LMF may consider that the UE uses a WLAN-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “tdoa”, the LMF may consider that the UE uses a DL-TDOA-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “aod”, the LMF may consider that the UE uses a DL-AoD-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “rtt”, the LMF may consider that the UE uses a Multi-RTT-based positioning method to obtain the ground truth label.In some implementations, if the UE has provided the capability for supporting other positioning methods (e.g., the UE has transmitted one or more of the following to the LMF: the A-GNSS-ProvideCapabilities and / or OTDOA-ProvideCapabilities and / or ECID-ProvideCapabilities and / or Sensor-ProvideCapabilities and / or TBS-ProvideCapabilities and / or WLAN-ProvideCapabilities and / or BT-ProvideCapabilities), the UE may not include the AIML-GroundTruthAvailable IE in the AIML-ProvideCapabilities IE. In such cases, the LMF may consider that the UE is capable of obtaining the ground truth label by using the corresponding positioning methods.In some implementations, if the UE has provided the capability for supporting other positioning methods, the UE may still need to include the AIML-GroundTruthAvailable IE in the AIML-ProvideCapabilities IE. If the AIML-GroundTruthAvailable IE is absent from the AIML-ProvideCapabilities IE, the LMF may consider that the UE is not capable of obtaining the ground truth label by using the corresponding positioning methods.In some implementations, as shown in Table 2 above, the assistance information may be included in the second NAS signaling. More specifically, the assistance information may be included in the AIML-DataCollection IE.In some implementations, the assistance information may be included in a separate NAS signaling (e.g., an LPP message other than the second NAS signaling).Configuration for NW-side Data Collection - Method 1: Legacy Measurement Configuration with AI / ML-specific Report ConfigurationIn some implementations, the LMF may send a third NAS signaling (e.g., an LPP message) to the UE. The third NAS message may be used to indicate the measurement configuration. The UE may identify the PRS resources and the quantity to be measured according to the IEs included in the third NAS signaling.More specifically, the UE may determine the PRS resources to be measured according to the “NR-DL-PRS-AssistanceData” included in the third NAS signaling.More specifically, the UE may determine the quantity to be measured according to the naming of the IE included in the third NAS signaling. For example, if the third NAS signaling includes the IE “NR-DL-TDOA-ProvideAssistantData”, the UE may consider measuring the time difference between a reference TRP and other TRPs based on the PRS transmitted on the PRS resources. For example, if the third NAS signaling includes the IE “NR-DL-AoD-ProvideAssistanceData”, the UE may consider measuring the signal quality (e.g., the reference signal received power (RSRP)) of the PRS transmitted on the PRS resources. For example, if the third NAS signaling includes the IE “NR-Multi-RTT-ProvideAssistanceData”, the UE may consider measuring the time difference from receiving a PRS from a TRP to transmitting an SRS to the TRP.In some implementations, an AssociationId IE may be used to indicate a situation while performing the PRS measurement. An AssociationId IE may also be a specific PRS resource configuration, and / or a specific UE-side AC, and / or a specific NW-side AC.In some implementations, the UE may consider a situation to be satisfied when the UE performs PRS measurement on PRS resources according to the PRS resource configuration corresponding to the situation.In some implementations, the UE may consider a situation to be satisfied when the UE performs PRS measurement based on an identified UE-side AC corresponding to the situation. In some implementations, the UE may identify that the UE is performing PRS measurement based on a specific UE-side AC by the UE’s implementation.In some implementations, the UE may consider a situation to be satisfied when the UE performs PRS measurement based on an identified NW-side AC corresponding to the situation. In some implementations, the UE may identify that the UE is performing PRS measurement based on a specific NW-side AC via explicit signaling from the NW or via implicit inference from the PRS resource configuration.In some implementations, an AssociationId IE may take an integer value, and the UE may know the indicated situation according to a predefined mapping rule which maps the integer to a situation. For example, the UE may interpret an AssociationId with value 1 to be a high-mobility situation. In some implementations, the predefined mapping rule may be a predefined table stored at the UE.In some implementations, an AssociationId IE may take an ENUMERATED value, and the UE may know the indicated situation according to the ENUMERATED value. For example, the UE may interpret an AssociationId with value “high-mobility” to be a high-mobility situation.In some implementations, the LMF may send a fourth NAS signaling (e.g., an LPP message) to the UE. The fourth NAS message may be used to indicate the logging and reporting configuration. The UE may identify the condition for logging, the dropping rule for logging, the condition for reporting, and the report contents according to the IEs included in the fourth NAS signaling.For example, the fourth NAS signaling may refer to the signaling structure of AIML-RequestLocationInformation, as shown in Table 3 below.In some implementation, the UE may determine the condition for logging according to an IE (e.g., a TriggeredLoggingCriteria IE). In some implementations, the TriggeredLoggingCriteria IE may include an IE (e.g., a LoggingCounter IE), which indicates the value of a logging counter terminating the UE's logging behavior, and / or an IE (e.g., a LoggingInterval IE), which indicates the length or interval between two consecutive logging instances, and / or an IE (e.g., an AssociationIdList IE), which indicates the association IDs that may trigger the logging, and / or an IE (e.g., a CombinedAssociationId IE), which indicates whether or not the UE considers all of the association IDs in the AssociationIdList IE to be the triggering condition.In some implementations, the LoggingCounter IE may take an integer value, and the UE may consider that the UE stops logging the measurement result after a number of logging instances, where the number may be equal to the value. For example, if the LoggingCounter is configured with value 5, the UE may stop logging the measurement results after 5 logging instances.In some implementations, the LoggingInterval IE may take an integer value, and the UE may consider the logging timer threshold to be the value of the LoggingInterval IE with a predefined unit. For example, if the LoggingInterval IE is configured with value 10, the UE may log the measurement result every 10 seconds.In some implementations, the LoggingInterval IE may take an integer value, and the UE may consider the logging periodicity to be the measurement periodicity multiplied by the value of the LoggingInterval IE. For example, if the measurement periodicity is 5 seconds and the LoggingInterval IE is configured with value 10, the UE may log the measurement result every 50 seconds.In some implementations, the LoggingInterval IE may take an ENUMERATED value, and the UE may identify the value and the unit of the logging periodicity according to the ENUMERATED value. For example, if the LoggingInterval IE is configured with value “s10”, the UE may log the measurement result every 10 seconds.In some implementations, the AssociationIdList IE may be a list of “AssociationId” IEs. In some implementations, the UE may consider the situations indicated by the AssociationIdList IE as one of the triggering conditions to start logging the measurement result (e.g., the UE may start logging the measurement results when the UE considers one or all of the situations indicated by the AssociationIdList to be satisfied).More specifically, the UE may start logging the measurement results and start the logging timer upon considering one or all of the situations indicated by the AssociationIdList to be satisfied.More specifically, the UE may start logging the measurement results and start the logging timer upon receiving the first PRS from the TRP after considering one or all of the situations indicated by the AssociationIdList to be satisfied.In some implementations, the CombinedAssociationId IE may take an ENUMERATED value in {“true”, “false”} to indicate whether the UE needs to consider one or all the situations to be the triggering condition for logging. For example, if the CombinedAssociationId IE is present with value “true”, the UE may start logging the measurement results when all of the situations indicated by the AssociationIdList IE are considered to be satisfied. Otherwise (e.g., if the CombinedAssociationId IE is absent or is present with value “false”), the UE may start logging the measurement results when at least one of the situations indicated by the AssociationIdList IE is considered to be satisfied.In some implementations, an AssociationId IE may additionally include one or more AssociationId IEs, and the UE may consider this type of AssociationId IE to be a combination of situations corresponding to the included AssociationId IEs. For example, if an AssociationId includes an ID value 10, an AssociationId IE with ID value 1, and an AssociationId IE with ID value 2, the UE may consider that the situation corresponding to the AssociationId IE with ID value 10 is the situation where both the situation corresponding to the AssociationId IE with ID value 1 and the situation corresponding to the AssociationId IE with ID value 2 occur.In some implementations, the UE may determine the condition for logging according to an IE (e.g., a PeriodicalLoggingCriteria IE). In some implementations, the PeriodicalLoggingCriteria IE may include an IE (e.g., a LoggingCounter IE), which indicates the value of a logging counter terminating the UE's logging behavior, and / or an IE (e.g., a LoggingInterval IE), which indicates the length or interval between two consecutive logging instances.In some implementations, the usage of the LoggingCounter IE and the LoggingInterval IE in the PeriodicalLoggingCriteria IE is the same as the counterpart IEs in the TriggeredLoggingCriteria IE.The LMF may configure only either the PeriodicalLoggingCriteria IE or the TriggeredLoggingCriteria IE in a NAS signaling (e.g., an LPP message). This means the LMF may not configure both the PeriodicalLoggingCriteria IE and the TriggeredLoggingCriteria IE in a single NAS signaling.In some implementations, the UE may determine the dropping rule for logging according to an IE (e.g., a DropLogging IE). In some implementations, the DropLogging may include an IE (e.g., a DropOldest IE), which indicates the UE to drop the oldest logged measurement result (e.g., drop the first logged measurement result in the time domain) when dropping is needed, and / or an IE (e.g., a FreshnessPeriod IE), which indicates a time interval for the UE to determine whether to drop the logged measurement results.In some implementations, the DropOldest IE may take an ENUMERATED value in {“true”, “false”}. If the DropOldest IE is present with value “true”, the UE may drop the oldest logged measurement result (e.g., the first logged measurement result in the time domain) when the UE considers that dropping is needed. In some implementation, a UE may consider dropping is needed when a new measurement result is obtained by the UE and the data size of the stored logged measurement results is too large to further log the new measurement result.In some implementations, the FreshnessPeriod IE may take an integer value, and the UE may consider the value to be the time interval with a predefined unit. For example, if the FreshnessPeriod is set to 1, the UE may consider dropping the logged measurement results which have been logged for more than 1 hour.In some implementations, the FreshnessPeriod IE may take an ENUMERATED value, and the UE may determine the value and the unit of the time interval according to the ENUMERATED value. For example, if the FreshnessPeriod IE is set to “hr1”, the UE may consider dropping the logged measurement results which have been logged for more than 1 hour.In some implementations, the UE may determine the condition for reporting according to an IE “TriggeredReportingCriteria”. In some implementations, the TriggeredReportingCriteria IE may include an IE (e.g., a ReportingCounter IE), which indicates the value of a reporting counter terminating the UE's reporting behavior, and / or an IE (e.g., a ReportingInterval IE), which indicates the length or interval between two consecutive initiations of a measurement report, and / or an IE (e.g., an AssociationIdList IE), which indicates the association IDs that may trigger the reporting, and / or an IE (e.g., a CombinedAssociationId IE), which indicates whether or not the UE considers all of the association IDs in the AssociationIdList IE to be the triggering condition, and / or an IE (e.g., a ReportAtStopLogging IE), which indicates whether the UE may initiate a measurement report when the UE stops logging, and / or an IE (e.g., a ReportAtLeaving IE), which indicates whether the UE may initiate a measurement report when the UE considers a leaving triggering condition to be satisfied.In some implementations, the ReportingCounter IE may take an integer value, and the UE may consider that the UE stops reporting the measurement result after a number of reporting instances, where the number may be equal to the value. For example, if the ReportingCounter is configured with value 5, the UE may stop reporting the measurement results after 5 logging instances.In some implementations, the ReportingInterval IE may take an integer value, and the UE may consider that the UE may report the measurement result with the value of the ReportingInterval IE with a predefined unit. For example, if the ReportingInterval IE is configured with value 10, the UE may report the measurement result every 10 seconds.In some implementations, the ReportingInterval IE may take an integer value, and the UE may consider the reporting periodicity to be the measurement periodicity multiplied by the value of the ReportingInterval IE. For example, if the measurement periodicity is 5 seconds and the ReportingInterval IE is configured with value 10, the UE may report the measurement result every 50 seconds.In some implementations, the ReportingInterval IE may take an ENUMERATED value, and the UE may identify the value and the unit of the reporting periodicity according to the ENUMERATED value. For example, if the ReportingInterval IE is configured with value “s10”, the UE may report the measurement result every 10 seconds.In some implementations, the AssociationIdList IE may be a list of “AssociationId” IEs. In some implementations, the UE may consider the situations indicated by the AssociationIdList IE as one of the triggering conditions to start reporting the measurement result (e.g., the UE may start reporting the measurement results when the UE considers one or all of the situations indicated by the AssociationIdList to be satisfied).In some implementations, the CombinedAssociationId IE may take an ENUMERATED value in {“true”, “false”} to indicate whether the UE needs to consider one or all the situations to be the triggering condition for reporting. For example, if the CombinedAssociationId IE is present with value “true”, the UE may start reporting the measurement results when all of the situations indicated by the AssociationIdList IE are considered to be satisfied. Otherwise (e.g., if the CombinedAssociationId IE is absent or is present with value “false”), the UE may start reporting the measurement results when at least one of the situations indicated by the AssociationIdList IE is considered to be satisfied.In some implementations, the ReportAtStopLogging IE may take an ENUMERATED value in {“true”, “false”}. For example, if the ReportAtStopLogging IE is present with value “true”, the UE may consider that the UE initiates a measurement report when the UE stops logging. Otherwise (e.g., if the ReportAtStopLogging IE is absent or is present with value “false”), the UE may consider that the UE does not initiate a measurement report when the UE stops logging.In some implementations, the ReportAtLeaving IE may take an ENUMERATED value in {“true”, “false”}. For example, if the ReportAtLeaving IE is present with value “true”, the UE may consider that the UE initiates a measurement report when the UE considers the situations indicated by the AssociationIdList which have been considered to be satisfied to be not satisfied. Otherwise (e.g., if the ReportAtLeaving IE is absent or is present with value “false”), the UE may consider that the UE does not initiate a measurement report when the UE considers the situations indicated by the AssociationIdList which have been considered to be satisfied to be not satisfied.In some implementations, the UE may determine the condition for reporting according to an IE (e.g., a PeriodicalReportingCriteria IE). In some implementations, the PeriodicalReportingCriteria IE may include an IE (e.g., a ReportingCounter IE), which indicates the value of a reporting counter terminating the UE’s reporting behavior, and / or an IE (e.g., a ReportingInterval IE), which indicates the length or interval between two consecutive reporting instances. In some implementations, the usage of the ReportingCounter IE and the ReportingInterval IE in the PeriodicalReportingCriteria IE is the same as the counterpart IEs in the TriggeredReportingCriteria IE. The LMF may configure only either the PeriodicalReportingCriteria IE or the TriggeredReportingCriteria IE in a NAS signaling (e.g., an LPP message). This means the LMF may not configure both the PeriodicalReportingCriteria IE and the TriggeredReportingCriteria IE in a single NAS signaling.In some implementations, the UE may determine the condition for reporting according to an IE (e.g., an OnDemandReporting IE). In some implementations, the OnDemandReporting IE may be used to indicate whether on-demand reporting is used for the measurement report, and the OnDemandReporting IE may take an ENUMERATED value in {“true”, “false”}. For example, if the OnDemandReporting IE is present with value “true”, the UE may consider that on-demand reporting may be used, and the UE may expect a further indication from the LMF to trigger the on-demand reporting. Otherwise (e.g., if the OnDemandReporting IE is absent or is present with value “false”), the UE may consider that on-demand reporting may not be used, and the UE may not expect any further indication from the LMF to trigger the on-demand reporting.In some implementations, the fourth NAS signaling may additionally include an IE (e.g., a ReportAssociationId IE) to indicate that the UE may include the AssociationId corresponding to the situation where the UE performs the measurement. In some implementations, the ReportAssociationId IE may take an ENUMERATED value in {“true”, “false”}. If the ReportAssociationId IE is present with value “true”, the UE may consider that the UE includes the AssociationId corresponding to the measurement situation into the measurement report. Otherwise (e.g., the ReportAssociationId IE is absent or is present with value “false”), the UE may consider that the UE does not include the AssociationId corresponding to the measurement situation into the measurement report.In some implementations, the fourth NAS signaling may additionally include an IE (e.g., a ReportGroundTruth IE) to indicate that the UE may include the ground truth label into the measurement report.In some implementations, the ReportGroundTruth IE may take an ENUMERATED value in {“true”, “false”}. If the ReportGroundTruth IE is present with value “true”, the UE may consider that the UE includes the ground truth label into the measurement report. Otherwise (e.g., if the ReportGroundTruth IE is absent or is present with value “false”), the UE may consider that the UE does not include the ground truth label into the measurement report.In some implementations, the ReportGroundTruth IE may include an IE (e.g., a ValidityTimeDifference IE) to indicate the criteria for the UE to determine whether to include the ground truth label. In some implementations, the ValidityTimeDifference IE may indicate a validity time difference value, and the UE may consider that the UE includes the ground truth label into the measurement report if the time difference between the timestamp when the UE acquires the ground truth label and the timestamp when the UE acquires the measurement result is not longer than the validity time difference value. Otherwise (e.g., if the time difference between the timestamp when the UE acquires the ground truth label and the timestamp when the UE acquires the measurement result is longer than the validity time difference value), the UE may consider that the UE does not include the ground truth label into the measurement report.In some implementations, the ValidityTimeDifference IE may take an ENUMERATED value, and the UE may determine the value and the unit of the validity time difference according to the value of the ValidityTimeDifference IE. For example, if the ValidityTimeDifference IE takes the value “ms50”, the UE may determine that the validity time difference is 50 milliseconds.In some implementations, the ValidityTimeDifference IE may take an integer value, and the UE may determine the validity timer difference according to the value of the ValidityTimeDifference IE with a predetermined unit. For example, if the ValidityTimeDifference IE takes the value 50, the UE may determine that the validity time difference is 50 milliseconds.In some implementations, for an AI / ML-based positioning, the ground truth label may be, but is not limited to, the LoS indication which indicates the probability that there is an LoS path between the UE and the reference TRP, and / or the location information which indicates the location (e.g., geographical coordinates of the UE’s location).Configuration for NW-side Data Collection - Method 2: AI / ML-specific Measurement Configuration with AI / ML-specific Report ConfigurationIn some implementations, the third NAS signaling may additionally include an IE (e.g., an AIML-ProvideAssistanceData IE) indicating that the measurement configuration is for the AI / ML-based positioning method (e.g., other than the legacy (e.g., TDoA, AoD, multi-RTT) methods). In some implementations, the AIML-ProvideAssistanceData may include the IEs which can be found in the NR-DL-TDOA-ProvideAssistantData IE, the NR-DL-AoD-ProvideAssistanceData IE, and the NR-Multi-RTT-ProvideAssistanceData IE. The AIML-ProvideAssistanceData IE may include additional IEs indicating the measurement information related to data collection for AI / ML. The additional IEs may be used to indicate the conditions for the UE to start measuring the PRS resources, and / or may be used to indicate the quantity which the UE measures. In some implementations, the signaling structure of AIML-ProvideAssistanceData. For example, the signaling structure AIML-ProvideAssistanceData may be the structure as shown in Table 4 below, with the legacy IEs being omitted in the example.In some implementations, the additional IE may be an IE (e.g., a TriggeredMeasurement IE) to indicate the conditions for the UE to start measuring the PRS resources. In some implementations, the TriggeredMeasurement IE may indicate the situations that the UE may perform the measurement. For example, the TriggeredMeasurement IE may include an AssociationIdList IE and a CombinedAssociationId IE. The AssociationIdList IE may indicate one or more situations (which may be mapped to an AssociationId), and the UE may consider that the UE starts measuring the PRS when at least one or all of the indicated situations are considered to be satisfied, and the UE may consider that the UE stops measuring the PRS when at least one or all of the indicated situations are considered to be not satisfied. The CombinedAssociationId IE may indicate whether the UE determines the starting / stopping condition based on the “at least one” or the “all” of the indicated situations.More specifically, the additional IE may be an IE (e.g., a MeasurementQuantity IE) to indicate which quantity the UE may measure. In some implementations, the MeasurementQuantity IE may take an ENUMERATED format in {“rstd”, “rsrp”, “rtt”} or in {“tdoa”, “aod”, “rtt”}. If the MeasurementQuantity IE is configured with value “tdoa” or “rstd”, the UE may consider that the UE measures the reference signal time difference (RSTD) of the PRS of the TRPs. If the MeasurementQuantity IE is configured with value “aod” or “rsrp”, the UE may consider that the UE measures the RSRP of the PRS of the TRPs. If the MeasurementQuantity IE is configured with value “rtt”, the UE may consider that the UE measures the RTT for the TRPs.In some implementations, the logging and reporting configuration in Method 2 may take a similar structure to Method 1. The logging configuration (e.g., the TriggeredLoggingCriteria IE, the PeriodicalLoggingCriteria IE, and the DropLogging IE) may be configured in the measurement configuration (e.g., the AIML-ProvideAssistanceData IE).Configuration for NW-side Data Collection - Method 3: Measurement Identity Associating Measurement Configuration and Report ConfigurationIn Method 3, measurement and reporting configurations may take similar structures to Method 1 and Method 2, with the modifications described below.In some implementations, an additional IE (e.g., a PositioningMeasurementIdentity IE) may be used to associate a measurement configuration and a reporting configuration. The measurement configuration may be a ProvideAssistanceData IE (e.g., the NR-DL-TDOA-ProvideAssistantData IE, the NR-DL-AoD-ProvideAssistanceData IE, and the NR-Multi-RTT-ProvideAssistanceData IE, and the AIML-ProvideAssistanceData IE), and a report configuration may be a RequestLocationInformation IE (e.g., the NR-DL-TDOA-RequestLocationInformation IE, the NR-DL-AoD-RequestLocationInformation IE, and the NR-Multi-RTT-RequestLocationInformation IE, and the AIML-RequestLocationInformation IE).In some implementations, to associate a measurement configuration and a reporting configuration, a measurement configuration may additionally include an ID to identify the measurement configuration for the association, and a reporting configuration may also additionally include an ID to identify the reporting configuration for the association.For example, the measurement configuration may include an IE (e.g., a MeasurementConfigId IE) to indicate the ID for association. In some implementations, the MeasurementConfigId IE may take an integer value. In another example, the MeasurementConfigId IE may be an AssociationId IE.For example, the reporting configuration may include an IE (e.g., a ReportConfigId IE) to indicate the ID for association. In some implementations, the ReportConfigId IE may take an integer value. In another example, the ReportConfigId IE may be an AssociationId IE.In some implementations, one or multiple measurement configurations may be configured to the UE. In some implementations, one or multiple reporting configurations may be configured to the UE. In some implementations, one or multiple PositioningMeasurementId IEs associating a measurement configuration and a reporting configuration may be configured to the UE.In some implementations, the measurement configurations, the reporting configurations, and the PositioningMeasurementIdentity IEs may be configured within the same or in separate NAS signallings.In some implementations, a PositioningMeasurementIdentity IE may include a PositioningMeasurementId IE as an ID to represent the PositioningMeasurementIdentity IE, a MeasurementConfigId IE to indicate a measurement configuration with a specific ID, and a ReportConfigId IE to indicate a reporting configuration with a specific ID. In some implementations, for the PositioningMeasurementIdentity IE, the UE may consider that the measurement configuration corresponding to the MeasurementConfigId IE is associated with the reporting configuration corresponding to the ReportConfigId IE. For example, the signaling structure of the PositioningMeasurementIdentity IE may take the structure as shown in Table 5 below.In some implementations, a measurement configuration may contain a list of ReportConfigId IEs. In some implementations, the UE may consider that the measurement configuration is associated with the report configurations corresponding to the ReportConfigId IEs in the list.In some implementations, a reporting configuration may contain a list of MeasurementConfigId IEs. In some implementations, the UE may consider that the reporting configuration is associated with the measurement configurations corresponding to the MeasurementConfigId IEs in the list.LMF’s Behavior of UE Capability HandlingIn some implementations, upon the LMF receiving a NAS signaling from the UE including an AIML-ProvideCapabilities IE which also includes an AIML-Inference IE, the LMF may consider one or more of the following:　　　　- The UE supports the inference of the UE-side model;　　　　- The UE supports the inference of the NW-side model; and　　　　- The UE supports the inference function.In some implementations, upon the LMF receiving a NAS signaling from the UE including an AIML-ProvideCapabilities IE which includes an AIML-DataCollection IE, the LMF may consider one or more of the following:　　　　- The UE supports the data collection of the UE-side model;　　　　- The UE supports the data collection of the NW-side model; and　　　　- The UE supports both the data collection of the UE-side model and the NW-side model and could be operated in parallel.In some implementations, upon the LMF receiving a NAS signaling from the UE including an AIML-ProvideCapabilities IE which includes an AIML-DataCollectionForNW IE, the LMF may consider that the UE supports the data collection of the NW-side model.In some implementations, upon the LMF receiving a NAS signaling from the UE including an AIML-ProvideCapabilities IE which includes an AIML-DataCollectionForUE IE, the LMF may consider that the UE supports the data collection of the UE-side model.In some implementations, upon the LMF receiving a NAS signaling from the UE including an AIML-ProvideCapabilities IE which includes an AIML-MonitoringNW IE, the LMF may consider that the UE supports the monitoring of the NW-side model.In some implementations, upon the LMF receiving a NAS signaling from the UE including an AIML-ProvideCapabilities IE which includes an AIML-GroundTruthAvailable IE, the LMF may consider that the UE is capable of obtaining the ground truth label via the positioning method(s) corresponding to the GroundTruthAvailable IE. In contrast, if the NAS signaling from the UE including an AIML-ProvideCapabilities IE does not include an AIML-GroundTruthAvailable IE, the LMF may consider that the UE is not capable of obtaining the ground truth label.In some implementations, the LMF may consider that the UE supports a specific positioning method according to the content of the AIML-GroundTruthAvailable IE. For example, if the PositioningMethod IE is set as “gnss”, the LMF may consider that the UE uses a GNSS-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “ecid”, the LMF may consider that the UE uses an ECID-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “wlan”, the LMF may consider that the UE uses a WLAN-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “tdoa”, the LMF may consider that the UE uses a DL-TDOA-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “aod”, the LMF may consider that the UE uses a DL-AoD-based positioning method to obtain the ground truth label. If the PositioningMethod IE is set as “rtt”, the LMF may consider that the UE uses a Multi-RTT-based positioning method to obtain the ground truth label.In some implementations, if the LMF has received a NAS signaling from the UE including ProvideCapabilities IEs associated with positioning methods other than AI / ML, the LMF may consider that the UE is capable of obtaining the ground truth label via the corresponding positioning methods. In some implementations, the ProvideCapabilities IEs associated with positioning methods other than AI / ML may be A-GNSS-ProvideCapabilities and / or OTDOA-ProvideCapabilities and / or ECID-ProvideCapabilities and / or Sensor-ProvideCapabilities and / or TBS-ProvideCapabilities and / or WLAN-ProvideCapabilities and / or BT-ProvideCapabilities.In some implementations, when the LMF considers that the UE is capable of obtaining the ground truth label via at least one positioning method, the LMF may indicate to the UE to include the ground truth label into the measurement report.In some implementations, the indication may be a ReportGroundTruth IE in the AIML-RequestLocationInformation IE.In some implementations, the LMF may indicate which positioning method is used to obtain the ground truth label.In some implementations, the positioning method indicated by the LMF may be included in the set of the positioning methods via which the LMF considers that the UE is capable of obtaining the ground truth label.In some implementations, the LMF may use the PositioningMethod IE to indicate the positioning method, and the UE may know which positioning method is used to obtain the ground truth label according to the PositioningMethod IE.UE’s Behavior of UE Capability HandlingIn some implementations, the UE may expect to receive one or more NAS signallings (e.g., the third and / or the fourth NAS signaling configuring the measurement and report configurations) configuring AI / ML-based data collection configuration for a NW-side model in one or more of the following conditions. In contrast, the UE may not expect to receive, or may ignore, one or more NAS signallings (e.g., the third and / or the fourth NAS signaling configuring the measurement and report configurations) configuring AI / ML-based data collection configuration for a NW-side model when one or more of the following conditions are not satisfied:　　　　- The UE has transmitted the second NAS signaling including the AIML-ProvideCapabilities IE; and　　　　- The UE has transmitted the second NAS signaling including the AIML-ProvideCapabilities IE which includes the AIML-DataCollection IE.In some implementations, the UE may ignore the received NAS signallings (e.g., an LPP message) from the LMF and / or initiate the transmission of an error / abort message to the LMF if the UE's capability may not fulfill the received configuration.In some implementations, “ignoring the received NAS signallings” may include not performing actions and not storing configurations.For example, the UE may ignore the received NAS signallings (e.g., an LPP message) from the LMF and / or initiate the transmission of an error / abort message to the LMF if the UE has indicated its capability of not supporting AI / ML-based positioning and the received NAS signaling from the LMF includes the configurations related to AI / ML-based positioning.In some implementations, the UE may indicate its capability of not supporting AI / ML-based positioning by transmitting a message including a ProvideCapabilities IE where the AIML-ProvideCapabilities is absent.In some implementations, “the received NAS signaling from the LMF includes the configurations related to AI / ML-based positioning” may include that the received NAS signaling from the LMF includes the AIML-ProvideAssistanceData IE and / or the AIML-RequestLocationInformation IE.In some implementations, the UE may indicate the non-availability of AI / ML-based positioning and optionally the non-availability of a period.For example, the UE may ignore the received NAS signallings (e.g., an LPP message) from the LMF and / or initiate the transmission of an error / abort message to the LMF if the UE has indicated its capability of not supporting data collection for a NW-side model and the received NAS signaling from the LMF includes the configurations related to data collection for a NW-side model.In some implementations, the UE may indicate its capability of not supporting data collection for a NW-side model by transmitting a message including a ProvideCapabilities IE where the AIML-ProvideCapabilities is absent.In some implementations, the UE may indicate its capability of not supporting data collection for a NW-side model by transmitting a message including a ProvideCapabilities IE where the AIML-ProvideCapabilities does not include the AIML-DataCollection IE.In some implementations, “the received NAS signaling from the LMF includes the configurations related to data collection for a NW-side model” may include that the received NAS signaling from the LMF includes the AIML-ProvideAssistanceData IE and / or the AIML-RequestLocationInformation IE.In some implementations, the UE may indicate the non-availability of data collection and optionally the non-availability of a period.For example, the UE may ignore the received NAS signallings (e.g., an LPP message) from the LMF and / or initiate the transmission of an error / abort message to the LMF if the UE has indicated its suggested logging counter value and the received NAS signaling from the LMF configures the logging counter with a value larger than the suggested logging counter value.In some implementations, the UE may indicate its suggested logging counter value by transmitting a NAS signaling (e.g., an LPP message) including the AIML-SuggestedLoggingCounter IE.In some implementations, the received logging counter value from the LMF may be indicated by the LoggingCounter IE.For example, the UE may ignore the received NAS signallings (e.g., an LPP message) from the LMF and / or initiate the transmission of an error / abort message to the LMF if the UE has indicated that the ground truth label is not available and the received NAS signaling from the LMF configures a report configuration indicating that the UE is to report the ground truth label.In some implementations, the UE may indicate that the ground truth label is not available by transmitting a NAS signaling (e.g., an LPP message) where the AIML-GroundTruthAvailable IE is absent (or is present with value “false”) from the AIML-ProvideCapabilities / AIML-DataCollection IE.In some implementations, “the received NAS signaling from the LMF configures a report configuration indicating that the UE is to report the ground truth label” may include that the received NAS signaling from the LMF includes a reporting configuration including a ReportGroundTruth IE, where the ReportGroundTruth IE may be set with value “true”.UE’s Behavior of MeasurementIn some implementations, the UE may start performing measurement for data collection of a NW-side model when the UE considers a condition to be satisfied. Correspondingly, the UE may stop performing measurement for data collection of a NW-side model when the UE considers the condition to be not satisfied.In some implementations, the condition may be configured by the NW (e.g., the LMF). In some implementations, the condition may be configured as a list (i.e., one or more) of situations. In some implementations, the condition may be additionally configured with a CombinedAssociationId IE.In some implementations, the list of situations may be configured as an AssociationIdList IE.For example, if the CombinedAssociationId IE is absent or is present with value “true”, the UE may consider a condition to be satisfied when the UE considers all of the situations to be satisfied.For example, if the CombinedAssociationId IE is absent or is present with value “false”, the UE may consider a condition to be satisfied when the UE considers at least one of the situations to be satisfied.In some implementations, a situation may be configured as an AssociationId IE. The UE may identify the situation by mapping the AssociationId IE according to a preconfigured / predefined table. It is noted that an AssociationId IE may be interpreted as a NW-side AC or a UE-side AC. It is noted that an AssociationId may be an AssociationId-UE IE to be interpreted as a UE-side AC. Similarly, an AssociationId may be an Association-NW IE to be interpreted as a NW-side AC.In some implementations, the UE may consider a situation to be satisfied when the NW (e.g., the LMF) explicitly indicates the situation via a NAS signaling (e.g., an LPP message) or when the UE implicitly infers the situation from the associated configuration (e.g., the PRS measurement configuration).In some implementations, the UE may consider a situation to be satisfied based on the UE’s implementation.In some implementations, when the UE performs the measurement on a PRS resource, the UE may determine the measurement quantity based on the measurement configuration received from the LMF.In some implementations, the UE may determine to measure the RSTD in the following cases:　　　　- The measurement configuration indicating the PRS resource is a NR-DL-TDOA-ProvideAssistanceData IE; and / or　　　　- The measurement configuration indicating the PRS resource is an AIML-ProvideAssistanceData IE including a MeasurementQuantity IE with value “rstd”.In some implementations, the UE may determine to measure the RSRP in the following cases:　　　　- The measurement configuration indicating the PRS resource is a NR-DL-AoD-ProvideAssistanceData IE; and / or　　　　- The measurement configuration indicating the PRS resource is an AIML-ProvideAssistanceData IE including a MeasurementQuantity IE with value “rsrp”.In some implementations, the UE may determine to measure the RTT in the following cases:　　　　- The measurement configuration indicating the PRS resource is a NR-Multi-RTT-ProvideAssistanceData IE; and / or　　　　- The measurement configuration indicating the PRS resource is an AIML-ProvideAssistanceData IE including a MeasurementQuantity IE with value “rtt”.UE’s Behavior of LoggingIn some implementations, the UE may log the measurement result periodically.In some implementations, the UE may log the measurement result periodically if the PeriodicalLoggingCriteria IE is present in the received NAS signaling (e.g., an LPP message) from the LMF. In some implementations, the UE may start logging the measurement result periodically upon receiving the NAS signaling including the PeriodicalLoggingCriteria IE.In some implementations, for periodical logging, the UE may determine the periodicity based on the configuration in the PeriodicalLoggingCriteria IE.In some implementations, the UE may maintain a logging timer. The logging timer is set / reset to the periodicity value when the UE receives the configuration in the PeriodicalLoggingCriteria IE or when the UE logs a new measurement result. The UE may log a new measurement result after the logging timer expires. In some implementations, the UE may set / reset the logging timer to the periodicity value upon receiving the first PRS from the TRP after receiving the configuration in the PeriodicalLoggingCriteria IE.In some implementations, the UE may determine the periodicity of the periodical logging based on the LoggingInterval IE in the PeriodicalLoggingCriteria IE.In some implementations, if the LoggingInterval IE takes an integer value, the UE may determine the periodicity of the periodical logging to be the integer value multiplied by a given unit. For example, if the LoggingInterval IE is 10, the UE may determine the periodicity of the periodical logging to be 10 seconds, or to be 10 times of the measurement periodicity.In some implementations, if the LoggingInterval IE takes an ENUMERATED value, the UE may determine the periodicity of the periodical logging to be the length corresponding to the ENUMERATED value. For example, if the LoggingInterval IE is “s10”, the UE may determine the periodicity of the periodical logging to be 10 seconds.In some implementations, for periodical logging, the UE may determine the logging counter threshold based on the configuration in the PeriodicalLoggingCriteria IE.In some implementations, the UE may determine the logging counter threshold based on the LoggingCounter IE in the PeriodicalLoggingCriteria IE.In some implementations, if the LoggingCounter IE takes an integer value, the UE may determine the logging counter threshold to be the integer value. For example, if the LoggingCounter IE is 10, the UE may determine the logging counter threshold to be 10.In some implementations, upon receiving the PeriodicalLoggingCriteria IE including the LoggingCounter IE, the UE may initialize / set the logging counter to 1 (or 0).In some implementations, upon logging a measurement result, the UE may increase the logging counter by 1.In some implementations, when the logging counter is less than or equal to the logging counter threshold, the UE may keep logging measurement results.In some implementations, when the logging counter is greater than or equal to the logging counter threshold, the UE may stop logging measurement results.In some implementations, when the logging counter is greater than or equal to the logging counter threshold, the UE may drop the oldest measurement result and log the new measurement result.In some implementations, the UE may determine the dropping method according to the configuration received from the LMF.In some implementations, the UE may determine the dropping method according to the IE (e.g., dropOldest) in the AIML-RequestLocationInformation IE received from the LMF.In some implementations, if the UE is configured with a dropOldest IE with value “true”, the UE may only drop the oldest logged measurement result (and then may log the new measurement result). In some implementations, if the UE is not configured with a dropOldest IE or is configured with a dropOldest IE with value “false”, the UE may drop all the logged measurement results.In some implementations, the UE may log the measurement report conditionally (e.g., when the UE considers a condition to be satisfied).In some implementations, the UE may log the measurement result conditionally if the TriggeredLoggingCriteria IE is present in the received NAS signaling (e.g., an LPP message) from the LMF.In some implementations, for triggered logging, the UE may determine the periodicity based on the configuration in the TriggeredLoggingCriteria IE.In some implementations, the UE may maintain a logging timer. The logging timer is set / reset to the periodicity value when the UE receives the configuration in the TriggeredLoggingCriteria IE or when the UE logs a new measurement result. The UE may log a new measurement result after the logging timer expires.In some implementations, the UE may determine the periodicity of the triggered logging based on the LoggingInterval IE in the TriggeredLoggingCriteria IE.In some implementations, if the LoggingInterval IE takes an integer value, the UE may determine the periodicity of the triggered logging to be the integer value multiplied by a given unit. For example, if the LoggingInterval IE is 10, the UE may determine the periodicity of the triggered logging to be 10 seconds, or to be 10 times of the measurement periodicity.In some implementations, if the LoggingInterval IE takes an ENUMERATED value, the UE may determine the periodicity of the triggered logging to be the length corresponding to the ENUMERATED value. For example, if the LoggingInterval IE is “s10”, the UE may determine the periodicity of the triggered logging to be 10 seconds.In some implementations, for triggered logging, the UE may determine the logging counter threshold based on the configuration in the TriggeredLoggingCriteria IE.In some implementations, the UE may determine the logging counter threshold based on the LoggingCounter IE in the TriggeredLoggingCriteria IE.In some implementations, if the LoggingCounter IE takes an integer value, the UE may determine the logging counter threshold to be the integer value. For example, if the LoggingCounter IE is 10, the UE may determine the logging counter threshold to be 10.In some implementations, for triggered logging, the UE may start logging when the UE considers a condition to be satisfied. Correspondingly, the UE may stop logging when the UE considers the condition to be not satisfied. In some implementations, the UE may determine the condition based on the configuration in the TriggeredLoggingCriteria IE.More specifically, the UE may determine the condition based on the AssociationIdList IE and / or the CombinedAssociationId IE in the TriggeredLoggingCriteria IE.In some implementations, the AssociationIdList IE may include a list of situations. In some implementations, a situation may be configured as an AssociationId IE. The UE may identify the situation by mapping the AssociationId IE according to a preconfigured / predefined table. It is noted that an AssociationId IE may be interpreted as a NW-side AC or a UE-side AC.In some implementations, if the CombinedAssociationId IE is absent or is present with value “true”, the UE may consider the condition to be satisfied when the UE considers all of the situations to be satisfied. Correspondingly, if the CombinedAssociationId IE is absent or is present with value “true”, the UE may consider the condition to be not satisfied when the UE considers at least one of the situations to be not satisfied.In some implementations, if the CombinedAssociationId IE is absent or is present with value “false”, the UE may consider the condition to be satisfied when the UE considers at least one of the situations to be satisfied. Correspondingly, if the CombinedAssociationId IE is absent or is present with value “false”, the UE may consider the condition to be not satisfied when the UE considers all of the situations to be not satisfied.In some implementations, the UE may consider a situation to be satisfied when the NW (e.g., the LMF) explicitly indicates the situation via a NAS signaling (e.g., an LPP message) or when the UE implicitly infers the situation from the associated configuration (e.g., the PRS measurement configuration).In some implementations, the UE may consider a situation to be satisfied based on the UE’s implementation.In some implementations, upon receiving the TriggeredLoggingCriteria IE including the LoggingCounter IE, the UE may initialize / set the logging counter to 1 (or 0).In some implementations, if the UE is configured with a TriggeredLoggingCriteria IE including the LoggingCounter IE, the UE may initialize / set the logging counter to 1 (or 0) upon considering the condition to be satisfied.In some implementations, upon logging a measurement result, the UE may increase the logging counter by 1.In some implementations, when the logging counter is less than or equal to the logging counter threshold, the UE may keep logging measurement results.In some implementations, when the logging counter is greater than or equal to the logging counter threshold, the UE may stop logging measurement results.In some implementations, when the logging counter is greater than or equal to the logging counter threshold, the UE may drop the oldest measurement result and log the new measurement result.In some implementations, the UE may drop one or more logged measurement results. In some implementations, the behavior “dropping the logged measurement results” may include clearing / releasing the logged measurement results from the memory used for storing the logged measurement results.In some implementations, the UE may drop the logged measurement results upon the UE considering the memory used for storing the logged measurement results to be full (e.g., no further memory space can be used for storing a new measurement result).In some implementations, the UE may drop the logged measurement results upon receiving a NAS signaling which includes a measurement configuration and / or a reporting configuration and does not include a TriggeredLoggingCriteria IE.In some implementations, the UE may drop the logged measurement results upon deactivating the support of data collection for a NW-side model.In some implementations, the UE may drop the logged measurement results by the UE’s implementation.In some implementations, the UE may drop the logged measurement results which are stored for more than a freshness period.In some implementations, the freshness period is a predefined value in the specification.In some implementations, the UE may determine the freshness period from the configuration of the DropLogging IE. More specifically, the UE may determine the freshness period from the FreshnessPeriod IE of the DropLogging IE.In some implementations, the FreshnessPeriod IE may take an integer value, and the UE may determine the freshness period to be the value with a predefined unit. For example, if the FreshnessPeriod is set to 1, the UE may determine the freshness period to be 1 hour.In some implementations, the FreshnessPeriod IE may take an ENUMERATED value, and the UE may determine the freshness period according to the ENUMERATED value. For example, if the FreshnessPeriod IE is set to “hr1”, the UE may determine the freshness period to be 1 hour.In some implementations, the UE may drop all of the logged measurement results.In some implementations, the UE may determine whether to drop the logged measurement results upon serving cell change (e.g., a handover occurrence) according to the configuration received from the LMF.In some implementations, the UE may determine whether to drop the logged measurement results upon serving cell change according to the IE (e.g., dropAtCellChange) in the AIML-RequestLocationInformation IE received from the LMF.In some implementations, if the UE is configured with a dropAtCellChange IE with value “true”, the UE may drop all the logged measurement results upon serving cell change. In some implementations, if the UE is not configured with a dropAtCellChange IE or is configured with a dropAtCellChange IE with value “false”, the UE may not drop the logged results (e.g., the UE may keep the logged results) upon serving cell change.In some implementations, the UE may drop the oldest (e.g., the first logged measurement result in the time domain) logged measurement result. In some implementations, the UE may drop the oldest logged measurement result according to the configuration in the DropLogging IE. More specifically, the UE may drop the oldest logged measurement result according to the DropOldest IE in the DropLogging IE. In some implementations, if the DropOldest IE is present with value ‘true’, the UE may drop the oldest logged measurement result (e.g., the first logged measurement result in the time domain) when the UE considers that dropping is needed.UE’s Behavior of ReportingIn some implementations, the UE may report the measurement result conditionally (e.g., when the UE considers a condition to be satisfied).In some implementations, the UE may report the measurement result conditionally if the TriggeredReportingCriteria IE is present in the received NAS signaling (e.g., an LPP message) from the LMF.In some implementations, for triggered reporting, the UE may determine the periodicity based on the configuration in the TriggeredReportingCriteria IE.In some implementations, the UE may maintain a reporting timer. The reporting timer is set / reset to the periodicity value when the UE receives the configuration in the TriggeredReportingCriteria IE or when the UE initiates a transmission of a measurement report. The UE may initiate a transmission measurement report after the reporting timer expires.In some implementations, the UE may determine the periodicity of the triggered reporting based on the ReportingInterval IE in the TriggeredReportingCriteria IE.In some implementations, if the ReportingInterval IE takes an integer value, the UE may determine the periodicity of the triggered reporting to be the integer value multiplied by a given unit. For example, if the TriggeringInterval IE is 10, the UE may determine the periodicity of the triggered logging to be 10 seconds, or to be 10 times of the measurement periodicity, or to be 10 times of the logging periodicity.In some implementations, if the ReportingInterval IE takes an ENUMERATED value, the UE may determine the periodicity of the triggered reporting to be the length corresponding to the ENUMERATED value. For example, if the ReportingInterval IE is “s10”, the UE may determine the periodicity of the triggered reporting to be 10 seconds.In some implementations, for triggered reporting, the UE may determine the reporting counter threshold based on the configuration in the TriggeredReportingCriteria IE.In some implementations, the UE may determine the reporting counter threshold based on the ReportingCounter IE in the TriggeredReportingCriteria IE.In some implementations, if the ReportingCounter IE takes an integer value, the UE may determine the reporting counter threshold to be the integer value. For example, if the ReportingCounter IE is 10, the UE may determine the reporting counter threshold to be 10.In some implementations, for triggered reporting, the UE may start reporting when the UE considers a condition to be satisfied. Correspondingly, the UE may stop reporting when the UE considers the condition to be not satisfied. In some implementations, the UE may determine the condition based on the configuration in the TriggeredReportingCriteria IE.In some implementations, the UE may determine the condition based on the AssociationIdList IE and / or the CombinedAssociationId IE in the TriggeredReportingCriteria IE.In some implementations, the AssociationIdList IE may include a list of situations. In some implementations, a situation may be configured as an AssociationId IE. The UE may identify the situation by mapping the AssociationId IE according to a preconfigured / predefined table. It is noted that an AssociationId IE may be interpreted as a NW-side AC or a UE-side AC.In some implementations, if the CombinedAssociationId IE is absent or is present with value “true”, the UE may consider the condition to be satisfied when the UE considers all of the situations to be satisfied. Correspondingly, if the CombinedAssociationId IE is absent or is present with value “true”, the UE may consider the condition to be not satisfied when the UE considers at least one of the situations to be not satisfied.In some implementations, if the CombinedAssociationId IE is absent or is present with value “false”, the UE may consider the condition to be satisfied when the UE considers at least one of the situations to be satisfied. Correspondingly, if the CombinedAssociationId IE is absent or is present with value “false”, the UE may consider the condition to be not satisfied when the UE considers all of the situations to be not satisfied.In some implementations, the UE may consider a situation to be satisfied when the NW (e.g., the LMF) explicitly indicates the situation via a NAS signaling (e.g., an LPP message) or when the UE implicitly infers the situation from the associated configuration (e.g., the PRS measurement configuration).In some implementations, the UE may consider a situation to be satisfied based on the UE’s implementation.In some implementations, upon receiving the TriggeredReportingCriteria IE including the ReportingCounter IE, the UE may initialize / set the reporting counter to 1 (or 0).In some implementations, if the UE is configured with a TriggeredReportingCriteria IE including the ReportingCounter IE, the UE may initialize / set the logging counter to 1 (or 0) upon considering the condition to be satisfied.In some implementations, upon reporting a measurement result, the UE may increase the reporting counter by 1.In some implementations, when the reporting counter is less than or equal to the reporting counter threshold, the UE may keep reporting measurement results.In some implementations, when the reporting counter is greater than the reporting counter threshold, the UE may stop reporting measurement results.In some implementations, the UE may report the measurement results when the UE stops logging.In some implementations, if the UE is configured with an IE (e.g., ReportAtStopLogging), or if the ReportAtStopLogging IE is present with value “true”, the UE may report the measurement results when the UE stops logging.In some implementations, if the UE is not configured with TriggeredLoggingCriteria and / or PeriodicalLoggingCriteria and is configured with ReportAtStopLogging with value “true”, the UE may ignore the ReportAtStopLogging IE and / or initiate the transmission of an error / abort message to the LMF.In some implementations, the UE may report the measurement results when the UE considers the condition changes from satisfied to not satisfied. In some implementations, if the UE is configured with a ReportAtLeaving IE, or if the ReportAtLeaving IE is present with value “true”, the UE may report the measurement results when the UE considers the condition changes from satisfied to not satisfied.In some implementations, the UE may set / reset the logging counter to 1 (or 0) when the UE initiates a measurement report to the LMF.In some implementations, the UE may release / clear the logged measurement results upon transmitting the measurement report to the LMF.In some implementations, the UE may report the measurement result on-demand (e.g., when the UE receives another indication from the LMF).In some implementations, the UE may identify that the measurement result is reported on-demand according to the configuration in the AIML-RequestLocationInformation IE.In some implementations, the UE may identify that the measurement result is reported on-demand according to the IE (e.g., OnDemandReporting) in the AIML-RequestLocationInformation IE.For example, the UE may identify that the measurement result is reported on-demand if the OnDemandReporting IE is present with value “true” in the AIML-RequestLocationInformation IE. For example, the UE may identify that the measurement result is not reported on-demand if the OnDemandReporting IE is absent from or is present with value “false” in the AIML-RequestLocationInformation IE.In some implementations, if the UE identifies that the measurement result is reported on-demand, the UE may report the measurement results upon receiving a NAS signaling from the LMF. For example, the UE may report the measurement results upon receiving an LPP message including an IE “AIML-RequestOnDemandLocationInformation” which indicates that the LMF is requesting the on-demand measurement report.In some implementations, the UE may release / clear the logged measurement results upon transmitting the measurement report to the LMF.In some implementations, the UE may determine the report content (e.g., which quantity is included in the measurement report) according to the measurement configuration, and / or the reporting configuration, and / or the PositioningMeasurementIdentity IE.In some implementations, the UE may determine the reporting quantity based on the naming of the measurement configuration.For example, if the measurement configuration is an NR-DL-TDOA-ProvideAssistantData IE, the UE may determine the RSTD to be the reporting quantity.For example, if the measurement configuration is an NR-DL-AoD-ProvideAssistanceData IE, the UE may determine the RSRP to be the reporting quantity.For example, if the measurement configuration is an NR-Multi-RTT-ProvideAssistanceData IE, the UE may determine the RTT to be the reporting quantity.In some implementations, the UE may determine the reporting quantity based on the configuration in the AIML-ProvideAssistanceData IE.In some implementations, the UE may determine the reporting quantity based on the MeasurementQuantity IE in the AIML-ProvideAssistanceData IE.For example, if the MeasurementQuantity IE is configured with value “tdoa” or “rstd”, the UE may determine the RSTD to be the reporting quantity.For example, if the MeasurementQuantity IE is configured with value “aod” or “rsrp”, the UE may determine the RSRP to be the reporting quantity.For example, if the MeasurementQuantity IE is configured with value ‘rtt’, the UE may determine the RTT to be the reporting quantity.In some implementations, the UE may determine whether to report the situation based on the configuration in the AIML-RequestLocationInformation IE.In some implementations, the UE may determine whether to report the situation based on the ReportAssociationId IE in the AIML-RequestLocationInformation IE.For example, if the ReportAssociationId IE is present with value “true” in the AIML-RequestLocationInformation IE, the UE may include the situation in the measurement report. For example, if the ReportAssociationId IE is absent from or is present with value “false” in the AIML-RequestLocationInformation IE, the UE may not include the situation in the measurement report.In some implementations, the included situation may be an AssociationId IE.In some implementations, the UE may determine whether to report the ground truth label based on the configuration in the AIML-RequestLocationInformation IE.In some implementations, the UE may determine whether to report the ground truth label based on the ReportGroundTruth IE in the AIML-RequestLocationInformation IE.For example, if the ReportGroundTruth IE is present with value “true” in the AIML-RequestLocationInformation IE, the UE may include the ground truth label in the measurement report. For example, if the ReportGroundTruth IE is absent from or is present with value “false” in the AIML-RequestLocationInformation IE, the UE may not include the ground truth label in the measurement report.In some implementations, the UE may determine whether to include the ground truth label according to the time difference from the timestamp when the UE obtains the ground truth label to the timestamp when the UE obtains the measurement result (or from the timestamp when the UE obtains the measurement result to the timestamp when the UE obtains the ground truth label).In some implementations, the UE may include the ground truth label if the time difference is shorter than a threshold (e.g., a validity time difference), and the UE may not include the ground truth label if the time difference is longer than the threshold.In some implementations, the UE may determine the validity time difference according to the ReportGroundTruth IE. More specifically, the UE may determine the validity time difference based on the ValidityTimeDifference IE included in the ReportGroundTruth IE.In some implementations, the ValidityTimeDifference IE may take an ENUMERATED value, and the UE may determine the value and the unit of the validity time difference according to the value of the ValidityTimeDifference IE. For example, if the ValidityTimeDifference IE takes the value “ms50”, the UE may determine that the validity time difference is 50 milliseconds.In some implementations, the ValidityTimeDifference IE may take an integer value, and the UE may determine the validity timer difference according to the value of the ValidityTimeDifference IE with a predetermined unit. For example, if the ValidityTimeDifference IE takes the value 50, the UE may determine that the validity time difference is 50 milliseconds.In some implementations, the UE may report a measurement report including no measurement results but a Cause IE to indicate the reason why there is no measurement result included in the measurement report.For example, the UE may set the Cause IE to value “NoMeasurement” to indicate that there is no available (logged) measurement result upon the initiation of a measurement report.For example, the UE may set the Cause IE to value “SelfDeactivation” to indicate that the UE has already deactivated the support of data collection for a NW-side model.UE’s Behavior for Association of Measurement Configuration and Reporting ConfigurationIn some implementations, the UE may associate one or more measurement configurations with one or more reporting configurations.In some implementations, the UE may associate a measurement configuration with a reporting configuration according to the PositioningMeasurementIdentity IE. For example, upon receiving a PositioningMeasurementIdentity IE including a MeasurementConfigId IE and a ReportConfigId IE, the UE may associate the measurement configuration corresponding to the MeasurementConfigId IE with the report configuration corresponding to the ReportConfigId IE.In some implementations, the UE may associate a measurement configuration with one or more reporting configurations according to the AIML-ProvideAssistanceData IE. For example, upon receiving a measurement configuration containing one or more ReportConfigId IEs, the UE may associate the measurement configuration with the report configurations corresponding to the one or more ReportConfigId IEs.In some implementations, the UE may associate a reporting configuration with one or more measurement configurations according to the AIML-RequestLocationInformation IE. For example, upon receiving a report configuration containing one or more MeasurementConfigId IEs, the UE may associate the report configuration with the measurement configurations corresponding to the one or more MeasurementConfigId IEs.In some implementations, the above-mentioned PositioningMeasurementId, MeasurementConfigId, and ReportConfigId may be AssociationId IEs.FIG. 1 is a flowchart illustrating a method / process performed by a UE for supporting AI / ML-based positioning, according to an example implementation of the present disclosure.In the action 102, the process 100 may start by receiving, from a BS, a logging configuration which indicates one or more triggering conditions. Specifically, the one or more triggering conditions may be configured for triggering logging of measurement result.In some implementations, the logging configuration may be received, by the UE, via a higher layer signalling, such as an RRC signalling or a NAS signalling.In some implementations, the logging configuration may be included in a TriggeredLoggingCriteria IE.In action 104, the process 100 may, in response to determining that the one or more triggering conditions are satisfied, log a measurement result based on the logging configuration. The process 100 may then end. Specifically, the UE may determine whether the one or more triggering conditions are satisfied based on the logging configuration. In response to determining that the one or more triggering conditions are satisfied, the UE may start to log measurement result(s) based on the logging configuration.In some implementations, in response to determining that the one or more triggering conditions are satisfied, the UE may start measurement and log the measurement result(s) based on the logging configuration.In some implementations, the UE may receive the logging configuration that indicates a list indicating multiple (candidates of) triggering conditions (e.g., an AssociationIdList IE), and the one or more triggering conditions are included in the list. In addition, the logging configuration may include a first configuration (e.g., a CombinedAssociationId IE), the UE may determine a value configured in the first configuration, and further determine whether the one or more triggering conditions are satisfied based on the value configured in the first configuration.In some implementations, in response to determining that the first configuration is configured to be a first value (e.g., “true”), the UE may (start to) log the measurement result(s) based on the logging configuration in response to determining that all of the (candidates of) triggering conditions indicated by (included in) the list are satisfied. In some implementations, in response to determining that the first configuration is configured to be a second value (e.g., “false”), the UE may (start to) log the measurement result(s) based on the logging configuration in response to determining that (only) one of the (candidates of) triggering conditions indicated by (included in) the list is satisfied.In some implementations, the multiple (candidates of) triggering conditions may be indicated by the list (e.g., an AssociationIdList IE) in various ways. In some implementations, the list may include multiple elements (e.g., AssociationId IEs) having at least one first-type element and at least one second-type element. Each first-type element may indicate a triggering condition, and each second-type element may indicate a combination of two or more of the elements. For example, a first element of the first-type may be associated with a first condition, a second element of the first-type may be associated with a second condition, and a third element of the second-type may be associated with a combination of the first element and the second element. In other words, the third element may indicate that both the first condition and the second condition have to be satisfied simultaneously. For example, an additional fourth element of the first-type may be associated with a third condition and an additional fifth element of the second-type may be associated with a combination of the third element and the fourth element. In other words, the fifth element may indicate that all the first condition, the second condition, and the third condition have to be satisfied simultaneously.In some implementations, the manner in which the UE logs the measurement result(s) may be configured in the logging configuration.In some implementations, the logging configuration may include a second configuration (e.g., a LoggingCounter IE) which indicates when to stop logging. Specifically, the UE may stop logging the measurement result(s) in response to a count of logged instances reaching a value indicated by the second configuration.In some implementations, the logging configuration may include a third configuration (e.g., a LoggingInterval IE) which indicates an interval of two consecutive logged instances. Specifically, the UE may start a timer in response to a reception of the third configuration or a logging of a new measurement result, and log a next measurement result in response to an expiry of the timer. The timer may have an initial value associated with the interval.In some implementations, the logging configuration may include a fourth configuration (e.g., a LoggingInterval IE) which is associated with an interval of two consecutive logged instances. Specifically, the interval of two consecutive logged instances may be determined by a value indicated by the fourth configuration and a configured measurement periodicity. For example, in a case that the value indicated by the fourth configuration is X (e.g., 10) and the configured measurement periodicity may be Y (e.g., 5) seconds, the interval of two consecutive logged instances may be X*Y (10*5 = 50) seconds. In other words, the UE may log the measurement result(s) every X*Y seconds based on the fourth configuration (e.g., and the configured measurement periodicity).FIG. 2 is a block diagram illustrating a node 200 for wireless communication in accordance with various aspects of the present disclosure. As illustrated in FIG. 2, a node 200 may include a transceiver 220, a processor 228, a memory 234, one or more presentation components 238, and at least one antenna 236. The node 200 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input / Output (I / O) ports, I / O components, and a power supply (not illustrated in FIG. 2).Each of the components may directly or indirectly communicate with each other over one or more buses 240. The node 200 may be a UE or a BS that performs various functions disclosed with reference to FIG. 1.The transceiver 220 has a transmitter 222 (e.g., transmitting / transmission circuitry) and a receiver 224 (e.g., receiving / reception circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 220 may be configured to transmit in different types of subframes and slots including, but not limited to, usable, non-usable, and flexibly usable subframes and slot formats. The transceiver 220 may be configured to receive data and control channels.The node 200 may include a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by the node 200 and include volatile (and / or non-volatile) media and removable (and / or non-removable) media. By way of example, and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media includes both volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, Artificial Intelligence (AI) / Machine Learning (ML) module(s) or data.The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or data.Computer-storage media may include RAM, DRAM, HBM, MRAM, FRAM, RRAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanisms and include any information delivery media.The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above listed components should also be included within the scope of computer-readable media.The memory 234 may include computer-storage media in the form of volatile and / or non-volatile memory. The memory 234 may be removable, non-removable, or a combination thereof. Example memory may include solid-state memory, hard drives, optical-disc drives, etc. As illustrated in FIG. 2, the memory 234 may store a computer-readable and / or computer-executable instructions 232 (e.g., software codes) that are configured to, when executed, cause the processor 228 to perform various functions disclosed herein, for example, with reference to FIG. 1. Alternatively, the instructions 232 may not be directly executable by the processor 228 but may be configured to cause the node 200 (e.g., when compiled and executed) to perform various functions disclosed herein. The AI / ML module(s) may be implemented with a supervised learning approach or an unsupervised learning approach (e.g., Transductive approach and Inductive approach).The processor 228 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU), a Tensor Processing Unit (TPU), a Graphic Processing Unit (GPU), a General-Purpose Graphic Processing Unit (GPGPU), a microcontroller, an ASIC, etc. The processor 228 may include memory. The processor 228 may process the data 230 and the instructions 232 received from the memory 234, and information transmitted and received via the transceiver 220, the baseband communications module, and / or the network communications module. The processor 228 may also process information to send to the transceiver 220 for transmission via the antenna 236 to the network communications module for transmission to a CN.One or more presentation components 238 may present data indications to a person or another device. Examples of presentation components 238 may include a display device, a speaker, a printing component, a vibrating component, etc.In view of the present disclosure, it is obvious that various techniques may be used for implementing the disclosed concepts without departing from the scope of those concepts. Moreover, while the concepts have been disclosed with specific reference to certain implementations, a person of ordinary skill in the art may recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the disclosed implementations are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular implementations disclosed and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A User Equipment (UE) for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning, the UE comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to: 　　　　　　　　receive, from a Base Station (BS), a logging configuration, the logging configuration indicating one or more triggering conditions; and 　　　　　　　　in response to determining that the one or more triggering conditions are satisfied, log a measurement result based on the logging configuration.

2. The UE of claim 1, wherein the logging configuration comprises a first configuration, and indicates a list indicating a plurality of triggering conditions, and the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　in response to determining that the first configuration is configured to be a first value, log the measurement result based on the logging configuration in response to all of the plurality of triggering conditions indicated by the list being satisfied; and 　　　　in response to determining that the first configuration is configured to be a second value, log the measurement result based on the logging configuration in response to one of the plurality of triggering conditions being satisfied.

3. The UE of claim 1, wherein: 　　　　the logging configuration indicates a list comprising a plurality of elements, the plurality of elements comprising at least one first-type element and at least one second-type element, 　　　　each of the first-type element indicates a triggering condition, and 　　　　each of the second-type elements indicates a combination of two or more of the plurality of elements.

4. The UE of claim 1, wherein the logging configuration comprises a second configuration, and the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　stop logging the measurement result in response to a count of logged instances reaching a value indicated by the second configuration.

5. The UE of claim 1, wherein the logging configuration comprises a third configuration, and one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　start a timer in response to a reception of the third configuration, the timer having an initial value indicated by the third configuration; and 　　　　log a next measurement result in response to an expiry of the timer.

6. The UE of claim 5, wherein the third configuration indicates an interval of two consecutive logged instances.

7. The UE of claim 1, wherein the logging configuration comprises a fourth configuration, and an interval of two consecutive logged instances is associated with the fourth configuration and a configured measurement periodicity.

8. A Base Station (BS) for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning, the BS comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to: 　　　　　　　　transmit, to a User Equipment (UE), a logging configuration, the logging configuration indicating one or more triggering conditions, 　　　　wherein the logging configuration causes the UE to: 　　　　　　　　in response to determining that the one or more triggering conditions are satisfied, log a measurement result based on the logging configuration.

9. The BS of claim 8, wherein: 　　　　the logging configuration comprises a first configuration and indicates a list indicating a plurality of triggering conditions, and 　　　　the logging configuration further causes the UE to: 　　　　　　　　in response to determining that the first configuration is configured to be a first value, log the measurement result based on the logging configuration in response to all of the plurality of triggering conditions indicated by the list being satisfied; and 　　　　　　　　in response to determining that the first configuration is configured to be a second value, log the measurement result based on the logging configuration in response to one of the plurality of triggering conditions being satisfied.

10. The BS of claim 8, wherein: 　　　　the logging configuration indicates a list comprising a plurality of elements, the plurality of elements comprising at least one first-type element and at least one second-type element, 　　　　each of the first-type element indicates a triggering condition, and 　　　　each of the second-type elements indicates a combination of two or more of the plurality of elements.

11. The BS of claim 8, wherein: 　　　　the logging configuration comprises a second configuration, and 　　　　the logging configuration further causes the UE to: 　　　　　　　　stop logging the measurement result in response to a count of logged instances reaching a value indicated by the second configuration.

12. The BS of claim 8, wherein: 　　　　the logging configuration comprises a third configuration, and 　　　　the logging configuration further causes the UE to: 　　　　　　　　start a timer in response to a reception of the third configuration, the timer having an initial value indicated by the third configuration; and 　　　　　　　　log a next measurement result in response to an expiry of the timer.

13. The BS of claim 12, wherein the third configuration is configured for the UE to determine an interval of two consecutive logged instances.

14. The BS of claim 8, wherein the logging configuration comprises a fourth configuration, and the fourth configuration is configured for the UE to determine an interval of two consecutive logged instances based on the fourth configuration and a configured measurement periodicity.

15. A method performed by a User Equipment (UE) for supporting Artificial Intelligence (AI) / Machine Learning (ML)-based positioning, the method comprising: 　　　　receiving, from a Base Station (BS), a logging configuration, the logging configuration indicating one or more triggering conditions; and 　　　　in response to determining that the one or more triggering conditions are satisfied, logging a measurement result based on the logging configuration.

Images