UE mobility awareness for data pairing used for location

By coordinating the validity duration of measurement information between network entities and UEs, the problem of pairing measurement information and tag information under UE mobility is solved, thereby improving the positioning accuracy of AI/ML models.

CN123075657APending Publication Date: 2026-11-10NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610635010.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-09
Publication Date
2026-11-10

Smart Images

  • Figure CN123075657A_ABST
    Figure CN123075657A_ABST
Patent Text Reader

Abstract

Example embodiments of this disclosure relate to user equipment mobility sensing for data pairing for location purposes. One method includes: receiving configuration information from a network entity at a first device, the configuration information indicating a configuration for the validity duration of measurement information; receiving a request from a second device at the first device for the validity duration of measurement information associated with the first device; determining the validity duration of the measurement information at the first device based on the configuration and the mobility state of the first device; and transmitting information indicating the validity duration of the measurement information to the second device at the first device.
Need to check novelty before this filing date? Find Prior Art

Description

Cross-references to related applications

[0001] This application claims priority and benefit to EP application No. 25175230.9, filed on May 9, 2025, the contents of which are incorporated herein by reference in their entirety.

[0002] field Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more particularly to methods, apparatuses, devices, and computer-readable storage media for data pairing for user equipment mobility sensing for location purposes. Background Technology

[0003] Artificial intelligence / machine learning (AI / ML) models are widely used for user equipment (UE) localization. During the training process of an AI / ML model, the training data samples can consist of two parts from different entities. These two information parts can include different measurements required to train the AI / ML model, which may change over time. A timestamp indicating the time instance in which the information was generated is used to pair these parts. Summary of the Invention

[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: receive configuration information from a network entity, the configuration information indicating a configuration for the validity duration of measurement information; receive a request from a second apparatus for the validity duration of measurement information associated with the first apparatus; determine the validity duration of the measurement information based on the mobility state of the first apparatus according to the configuration; and transmit information indicating the validity duration of the measurement information to the second apparatus.

[0005] In a second aspect of this disclosure, a network entity is provided. The network entity includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network entity to: determine a configuration for the validity duration of measurement information based on capability information of a first device; transmit configuration information instructing the configuration to the first device; and transmit an instruction to a second device instructing the first device to determine the capability of the validity duration.

[0006] In a third aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to: receive from a network entity an instruction instructing a first apparatus to determine the validity duration of measurement information; transmit to the first apparatus a request for the validity duration of the measurement information; receive from the first apparatus information instructing the validity duration of the measurement information; and determine a pairing between measurement information and tag information based on the validity duration of the measurement information, a timestamp associated with the measurement information, and a timestamp associated with the tag information, according to tag information received for positioning of the first apparatus.

[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving configuration information from a network entity, the configuration information indicating a configuration for the validity duration of measurement information; receiving a request from a second device for the validity duration of measurement information associated with a first device; determining the validity duration of the measurement information based on the mobility state of the first device according to the configuration; and transmitting information indicating the validity duration of the measurement information to the second device.

[0008] In a fifth aspect of this disclosure, a method is provided. The method includes: determining a configuration for the validity duration of measurement information based on capability information of a first device; transmitting configuration information instructing the configuration to the first device; and transmitting an instruction to a second device instructing the first device to determine the validity duration.

[0009] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving from a network entity an indication of the ability of a first device to determine the validity duration of measurement information; transmitting to the first device a request for the validity duration of the measurement information; receiving from the first device information indicating the validity duration of the measurement information; and determining a pairing between measurement information and tag information based on the validity duration of the measurement information, a timestamp associated with the measurement information, and a timestamp associated with the tag information, according to tag information received for positioning of the first device.

[0010] In a seventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: means for receiving configuration information from a network entity, the configuration information indicating a configuration for the validity duration of measurement information; means for receiving a request from a second means for a validity duration of measurement information associated with the first means; means for determining the validity duration of the measurement information based on the mobility state of the first means, according to the configuration; and means for transmitting information indicating the validity duration of the measurement information to the second means.

[0011] In an eighth aspect of this disclosure, a network entity is provided. The network entity includes: components for determining a configuration for the validity duration of measurement information based on capability information of a first device; components for transmitting configuration information indicating the configuration to the first device; and components for transmitting an indication to a second device indicating the capability of the first device to determine the validity duration.

[0012] In a ninth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving from a network entity an indication of the capability of a first apparatus to determine the validity duration of measurement information; components for transmitting a request to the first apparatus for the validity duration of the measurement information; components for receiving from the first apparatus information indicating the validity duration of the measurement information; and components for determining a pairing between measurement information and tag information based on the validity duration of the measurement information, according to received tag information for positioning of the first apparatus.

[0013] In a tenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect.

[0014] In the eleventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fifth aspect.

[0015] In a twelfth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a sixth aspect.

[0016] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 The signaling flow illustrates an example procedure for determining the duration of validity according to some example embodiments of this disclosure; Figure 3 Example configurations of the validity duration according to some example embodiments of this disclosure are shown; Figure 4 The signaling flow illustrates an example procedure for determining the duration of validity according to some example embodiments of this disclosure; Figure 5 The signaling flow illustrates an example procedure for determining the duration of validity according to some example embodiments of this disclosure; Figure 6 The signaling flow illustrates an example procedure for determining the duration of validity according to some example embodiments of this disclosure; Figure 7 A flowchart is shown illustrating a method implemented at a terminal device according to some example embodiments of the present disclosure; Figure 8 A flowchart is shown illustrating a method implemented at a network entity according to some example embodiments of the present disclosure; Figure 9 A flowchart is shown illustrating a method implemented at a network device according to some example embodiments of the present disclosure; Figure 10 A flowchart is shown illustrating a method implemented at a terminal device according to some example embodiments of the present disclosure; Figure 11 A flowchart is shown illustrating a method implemented at a network device according to some example embodiments of the present disclosure; Figure 12 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 13 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0018] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0019] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0020] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0021] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments, whether explicitly described or not, to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0022] It should be understood that although terms such as "first," "second," etc., preceding nouns may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another, and they do not restrict the order of the nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0023] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0024] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0026] As used in this application, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementations in analog, digital and / or quantum circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog, digital, and / or quantum hardware circuitry with software / firmware, and (ii) Any or all portions of a hardware processor (including digital and / or quantum signal processors(s) with software, and memory that works together to enable devices such as mobile devices, computing devices, or servers to perform various functions), and (c) Any or all parts of the hardware circuitry, such as microprocessors, processors and / or quantum processors, that require software (e.g., firmware) to operate, but which may not exist when no software is required to operate.

[0027] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used herein, the term "circuit" also encompasses only hardware circuitry or a processor (or multiple processors) or a portion thereof and its accompanying software and / or firmware implementation. The term "circuit" also encompasses, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0028] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. The scope of this disclosure should not be construed as limited to the aforementioned systems.

[0029] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header End (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femto, pico, or non-terrestrial network (NTN)) or non-terrestrial network equipment (such as satellite network equipment), low Earth orbit (LEO) satellites and geostationary Earth orbit (GEO) satellites, spacecraft network equipment, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves as a UE toward the parent node, and the DU portion of the IAB node behaves as a base station toward the next-hop IAB node.

[0030] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal equipment may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.

[0031] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0032] Artificial intelligence (AI) can be broadly defined as enabling computers to perform tasks that mimic the human brain. Machine learning (ML) is a class of AI technologies: computer algorithms that can automatically improve their performance without explicit programming. AI / ML can help tune and optimize radio access network (RAN) parameters and settings using (real-time) monitoring and prediction of network performance, quality, and demand. Furthermore, AI / ML can identify and diagnose network performance degradation and provide protection against network attacks. AI / ML can be used for energy saving, load balancing, mobility optimization, link adaptation, and security, to name just a few.

[0033] It is conceivable that AI / ML will enable real-time analysis and automated operation and control of RANs in 5G and beyond. This requires the availability of data streaming from wireless devices in a timely manner, especially in extremely time-critical applications such as real-time video surveillance and extended reality (XR). This can be reflected in network architecture, such as by placing and moving ML agents to desired locations within the network, for example, for data collection. User equipment (mobile devices) can assist the network in making decisions in resource management, thus acting as an infrastructure resource.

[0034] As networks evolve to programmable and flexible cloud-native implementations, AI / ML-based network automation will be used to simplify network management and optimization. Support for the air interface, particularly signal processing algorithms, is expected, and eventually, even machine learning models will be used. Therefore, 6G wireless communication standards will natively support AI-based air interfaces.

[0035] To facilitate understanding of the terminology, some definitions for the AI / ML terminology list are provided below.

[0036] AI / ML Models: Data-driven algorithms that apply AI / ML techniques to generate a set of outputs based on a set of inputs.

[0037] AI / ML model training: The process of training an AI / ML model in a data-driven manner [by learning input / output relationships] and obtaining a trained AI / ML model for inference.

[0038] Data collection: The process by which network nodes, management entities, or UEs collect data for use in AI / ML model training, data analysis, model inference, and monitoring.

[0039] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure can be implemented is shown. For example... Figure 1 As shown, the communication environment 100 may include multiple communication devices, such as terminal device 110-1, terminal device 110-2, ..., terminal device 110-N. Terminal device 110-1, terminal device 110-2, ..., terminal device 110-N may be collectively referred to as "terminal device 110". The number N can be any suitable integer. The communication environment 100 may also include a network device 120, which can communicate with terminal device 110.

[0040] The communication environment 100 may also include network devices, such as a Location Management Function (LMF) 130 that may be included in the core network (CN). The LMF 130 and the terminal device 110 may communicate with each other. In some example embodiments, one or more AI / ML models may be trained and used by one or more terminal devices 110. AI / ML models can be trained to implement specific functions at the terminal device 110, network device 120, or LMF 130.

[0041] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement some of the example embodiments.

[0042] In some example embodiments, operations described in conjunction with a terminal device can be implemented at a network device or other device, and operations described in conjunction with a network device such as an LMF can be implemented at other network functions or other devices.

[0043] Different AI / ML models can be configured to implement the same or different algorithms. In a positioning scenario, the AI / ML model can be configured for direct or assisted positioning of terminal devices within a communication network. Inference, testing, training, and / or validation of the AI / ML model can be performed on terminal device 110, network device 120, and / or other entities such as LMF 130. LMF 130 can be an entity implementing location management services. LMF 130 can be a network node in the RAN or core network, or it can be an external entity. In some example embodiments, LMF 130 may be able to communicate with network node 130 (e.g., RAN network device).

[0044] AI / ML models can be delivered from one entity to another in any way. AI / ML models are delivered over the air interface in a manner opaque to 3GPP signaling, and the parameters of the model structure are known to the receiving end, or the model itself is a new model with parameters. Delivery can contain a complete model or a partial model.

[0045] In some example embodiments, AI / ML models are configured for AI / ML-based or AI / ML-enabled localization. AI / ML-enabled localization is one of the selected use cases for research projects in communication network development. In some example embodiments, two localization methods have been proposed. The first method is direct AI / ML localization, where the output inferred by the AI / ML model is the UE location. The model input has several options, including channel observations such as Channel Impulse Response (CIR), Power Delay Distribution (PDP), Reference Signal Received Power (RSRP), Reference Signal Received Path Power (RSRPP), etc. The second method is AI / ML-assisted localization, where the output inferred by the AI / ML model is a new measurement and / or enhancement to existing measurements, and this new measurement and / or enhancement can be referred to as an intermediate feature as it is input to a second function to ultimately estimate the UE location. These measurements include, for example, Line-of-Sight (LOS) / Non-Line-of-Sight (NLOS) identification, Time of Arrival (ToA), Time Difference of Arrival (TDoA), Path Phase, Reference Signal Time Difference (RSTD), etc. For enhanced positioning accuracy, both direct AI / ML positioning and AI / ML-assisted positioning are considered. These enhancements include the following scenarios.

[0046] Under direct AI / ML localization, the following cases are defined: Case 1 is the first priority enhancement, in which the UE-side AI / ML model can be used to perform localization at the UE.

[0047] Case 2b is the second priority enhancement, where localization can be UE-assisted or LMF-based. The AI / ML model can be deployed at the LMF.

[0048] Case 3b is another first-priority enhancement, where localization can be assisted by NG-RAN nodes. The AI / ML model can be deployed at the LMF.

[0049] In AI / ML-assisted localization, the following situations are included: Case 2a is the second priority enhancement, where the localization can be UE-assisted or LMF-based, and the AI / ML model can reside at the UE.

[0050] Case 3a is the highest priority enhancement, where localization can be assisted by NG-RAN nodes. The AI / ML model can be deployed at the gNB.

[0051] AI / ML model lifecycle management (LCM) can include model training, model deployment, model inference, model monitoring, and model updates.

[0052] As part of the LCM of the AI / ML model, performance monitoring of the gNB-side model may be required. If model monitoring of the gNB-side model requires and is provided with ground truth labels (or their approximations), the monitoring metrics may include statistics on the difference between the model output and the provided ground truth labels, examples of which may include the mean, standard deviation, instantaneous value, or threshold of the ground truth labels (or their approximations). To monitor the gNB-side model used for AI / ML-based localization, signaling from the monitoring entity to request ground truth labels (if needed), signaling from the monitoring entity to request model output (if needed), and / or potential request / reporting signaling for monitoring metrics (if needed) may be required.

[0053] In the context of data collection for AI / ML training of UE positioning, the collected training data can be categorized into two component sets, referred to as Part A and Part B. Part A may include measurement information, which can be provided as model input for AI / ML-based positioning. Examples of such measurement information may include, but are not limited to, channel measurements, quality indicators of channel measurements, and timestamps. Part B may include label information, which may be referred to as label data corresponding to the measurement information, and can be used as the expected model output for AI / ML-based positioning. Examples of such label information may include ground reality labels or their approximations, quality indicators of the labels, and timestamps associated with the labels. Note that the names "Part A" and "Part B" may only be used to describe the way the training data is categorized, and the training data can be categorized in any appropriate manner. The corresponding contents of Part A and Part B may be generated by different entities, and the applicability of any one or both sets may vary between different use cases.

[0054] If the training data sample includes both part A and part B, these components can be considered to correspond to the same UE (location reference UE, PRU, or non-PRU UE). Furthermore, it can be assumed that the training data sample containing both part A and part B is associated with the same location of the UE indicated by part B.

[0055] Timestamp information can be used to support the pairing of Part A and Part B. Timestamp information can indicate the time corresponding to the generation of Part A or Part B. For timestamps associated with Part A, when reporting or sending channel measurements, the channel measurement timestamp can indicate the time instance in which the channel measurement was performed. For timestamps associated with Part B, when reporting or sending tags, the tag timestamp can be estimated to indicate the time instance in which the tag is valid.

[0056] For data collection for AI / ML training used in UE positioning, in some cases (e.g., cases 3a and / or 3b), if part A and part B are generated by different entities, then in order to pair part A with part B, timestamp information of part A (if part A was transmitted) and timestamp information of part B (if part B was transmitted) are required. Additionally, other information can be used to pair part A and part B.

[0057] For example, for use cases such as case 3a (where the model can be deployed at the gNB) and case 3b (where the model can be deployed at the LMF, and parts A and B can be generated by different entities), timestamps associated with part A and parts B may be needed to facilitate pairing. To collect labeled datasets to train AI / ML models for localization, it is necessary to obtain information from different entities in the network (e.g., UE, PRU) and then match them; this is often referred to as part A and part B pairing.

[0058] Specifically, for cases 3a and 3b, the measurement (part A) can be generated by the gNB / TRP associated with a given UE (i.e., case 3a) or by the UE (i.e., case 3b), while the tag (part B) can be generated by another entity (such as the LMF or the UE) and delivered to the gNB by the LMF. In this case, timestamp information can be used to match these two information parts.

[0059] As mentioned above, the measurement information is collected for a specific UE. Measurement information collected from different sources can obviously lead to different types of latency or delay. More importantly, the UE can be mobile, which directly affects the validity of the information under consideration (part A or part B) relative to the indicated timestamp information.

[0060] For example, at a time instance, part A or part B can be generated and assigned a timestamp based on the time instance. Part A and part B can indicate the state of the UE at the time part A or part B was generated. However, parts A and part B are generated from different entities, which may cause delays and latency when they are delivered to the entity that can pair the two parts. For example, if the UE is moving, the information obtained at a certain time instance may be invalid when pairing information from different sources due to changes in the UE's location and state. Therefore, especially when the UE is moving, more information than timestamps is needed to pair parts A and part B for data collection during the training of AI / ML models used for positioning.

[0061] According to some example embodiments of this disclosure, a solution is provided for determining the validity duration for pairing portions from different sources. In the solution provided herein, a first device receives configuration from a network entity. This configuration is used for the validity duration of measurement information. Then, when the first device receives a request from a second device for the validity duration of measurement information associated with the first device, the first device determines the validity duration of the measurement information based on mobility status according to the configuration. The first device then transmits the validity duration to the second device.

[0062] Using the solution provided in this disclosure, measurement information (part A) and tag information (part B) can be associated with validity duration and a timestamp. The network device can then know the UE's mobility and the validity duration used for pairing. This allows the network device to pair measurements and tags based on validity duration, avoiding degradation of the training data for the AI / ML model used for localization. Therefore, the accuracy of localization using the AI / ML model can be improved.

[0063] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0064] Figure 2 Signaling flow 200 is shown as an example procedure for determining the validity duration according to some example embodiments of this disclosure. Reference will be made to this document for discussion purposes. Figure 1 To describe Figure 2 For example, by using terminal device 110, network device 120 and LMF 130.

[0065] In signaling flow 200, it is assumed that an AI / ML model for localization will be deployed at network device 120. Network device 120 may perform the collection of training data for the AI / ML model used for localization of terminal device 110. The training data may include training data samples consisting of measurement information (also referred to as part A) and label information (also referred to as part B). Measurement information may be associated with terminal device 110 and may be collected by network device 120. Label information is generated and provided by LMF 130 for localization of terminal device 110. Network device 120 may require both measurement information and label information and then pair them using timestamp information and validity duration for pairing as proposed in this disclosure. The different entities providing measurement information and label information (i.e., network device 120 and LMF 130) may be associated with use case (case 3a).

[0066] Based on the need for validity duration, network device 120 may transmit (202) a request for configuration to LMF 130. This configuration is for the validity duration of measurement information associated with terminal device 110. Accordingly, LMF 130 may receive (204) a request from network device 120. For example, network device 120 may explicitly indicate to LMF 130 that paired part A and part B require validity duration to invoke the procedure for determining validity duration.

[0067] Based on this request, LMF 130 can transmit (206) a request for capability information to terminal device 110. The capability information can indicate to terminal device 110 the capability to determine the validity duration of measurement information. Accordingly, terminal device 110 can receive (208) a request for capability information from LMF 130. In response to this request, terminal device 110 can analyze its capabilities and transmit (212) capability information to LMF 130. Accordingly, LMF 130 can receive (214) capability information from terminal device 110.

[0068] For example, when LMF 130 receives a request from network device 120 to configure the validity duration, LMF 130 may not know whether terminal device 110 is able to determine the validity duration based on its mobility. Therefore, LMF 130 and terminal device 110 may exchange capability information before determining the configuration of the validity duration. The capability information may specifically indicate whether terminal device 110 is able to determine the validity duration in response to a request from another entity (e.g., network device 120 or another network device).

[0069] Based on the capability information of terminal device 110, LMF 130 determines (216) the configuration of the validity duration of the measurement information. LMF can analyze the capabilities of terminal device 110 and determine an appropriate configuration of the validity duration aligned with the indication from the terminal device. In addition, LMF 130 can also determine the configuration based on available resources to assist other terminal devices in the serving cell provided by network device 120 that can simultaneously request data collection.

[0070] LMF 130 transmits (218) configuration information indicating the configuration to terminal device 110. Accordingly, terminal device 110 receives (222) configuration information from LMF 130.

[0071] The following will refer to Figure 3 A detailed example of configuring the validity duration.

[0072] LMF 130 transmits (224) an indication to network device 120 instructing terminal device 110 to determine the duration of validity. Accordingly, network device 120 receives (226) this indication from LMF 130. In some example embodiments, LMF 130 may transmit an indication of the capabilities of terminal device 110 after receiving capability information from terminal device 110. This indication can be considered a response to a request from network device 120. Alternatively, LMF 130 may transmit the indication when transmitting configuration to terminal device 110.

[0073] Based on the indication of the capabilities of terminal device 110, network device 120 can know that terminal device 110 is able to determine the duration of validity of measurement information. In some example embodiments, network device 120 may perform the collection of training data for locating an AI / ML model of terminal device 110. The training data may include at least one training data sample, which may consist of measurement information and label information.

[0074] In this scenario, the measurement information is measured by network device 120 itself, and the tag information is generated by LMF 130. The measurement information may include channel measurements, a quality indicator for the channel measurements, and a timestamp for the channel measurements. The timestamp indicates the time instance in which network device 120 generated the measurement information.

[0075] In some example embodiments, network device 120 can collect measurement information by performing measurements on uplink reference signals transmitted from terminal device 110 to network device 120. For example, network device 120 can perform measurements on sounding reference signals (SRS) transmitted from terminal device 110.

[0076] When network device 120 performs training data collection from different entities, the measurement information and label information can come from different entities, allowing network device 120 to request a pairing validity duration for pairing.

[0077] Network device 120 transmits (228) a request for the validity duration of the measurement information. Accordingly, terminal device 110 receives (232) a request from network device 120. In response to receiving the request, terminal device 110 determines (234) the validity duration of the measurement information based on the mobility state of the first device according to the configuration. The validity duration of the measurement information may be applicable to tag information for the location of terminal device 110.

[0078] Terminal device 110 can determine a mobility state in order to determine the duration of validity. In some example embodiments, terminal device 110 can determine the mobility state based on at least one of the following: a change in reference received power (RSRP) measured by the terminal device, the number of handovers by the terminal device, or the cell reselection rate of the terminal device. For example, if the number of handovers by terminal device 110 is high, terminal device 110 can determine that the speed of terminal device 110 is relatively high.

[0079] In some example embodiments, the capability information transmitted to LMF 130 may also indicate a mode applied by terminal device 110 for determining the mobility state. This mode may be a method or algorithm that terminal device 110 can use to determine the mobility state. For example, the mode may be based on RSRP changes to determine the mobility state. The capability information may indicate that the terminal device can determine the mobility state based on RSRP changes. Alternatively, the mode may be a method that terminal device 110 can use to determine the mobility state based on the Doppler shift in the frequency of a reference signal due to mobility. It should be understood that other methods or algorithms may be used as the mode for determining the mobility state. In such cases, LMF 130 may also determine the configuration based on the mode applied by terminal device 110.

[0080] In some example embodiments, the configuration of the validity duration can indicate the relationship between the mobility state of the terminal device and the validity duration of the measurement information. The terminal device 110 can determine the validity duration of the measurement information based on this relationship. For example, the relationship can be a function of mobility state and validity duration, such that the terminal device 110 can determine the validity duration of the measurement information by calculating this function. Alternatively, the relationship can be based on a table of mobility state and validity duration, such that the terminal device 110 can select a validity duration from the table based on its measured mobility.

[0081] Additionally, in some example embodiments, terminal device 110 may also determine the validity duration of the measurement information based on the mobility stability of terminal device 110. Mobility stability can indicate changes in the mobility state of terminal device 110. For example, if mobility stability is low, terminal device 110 may determine that it is experiencing rapid changes in mobility, allowing terminal device 110 to determine that the validity duration may be relatively short. On the other hand, if mobility stability is high, the validity duration may be determined to be longer.

[0082] Additionally, in some example embodiments, the terminal device 110 may also determine the validity duration of the measurement information based on a reference validity duration. The reference validity duration may be determined relative to a reference distance or a reference time period.

[0083] Additionally, in some example embodiments, terminal device 110 may receive an indication of a quality requirement for at least one of the measurement information or tag information. Terminal device 110 may also determine the validity duration based on the relationship between the quality requirement and the validity duration. For example, the relationship between the quality requirement and the validity duration may be indicated to terminal device 110 in association with a configuration for the validity duration. Alternatively, the relationship between the quality requirement and the validity duration may be pre-configured to terminal device 110 or specified. For example, if the quality of at least one of the measurement information or tag information is low, terminal device 110 may take this into account and adjust the validity duration accordingly.

[0084] Based on the determination of the validity duration, terminal device 110 transmits (236) information indicating the validity duration to network device 120. Accordingly, network device 120 receives (238) information indicating the validity duration from terminal device 110. On the other hand, LMF 130 can generate tag information for locating terminal device 110 and transmit the tag information to network device 120.

[0085] Based on the tag information received from LMF 130, network device 120 determines (242) the pairing between measurement information and tag information based on the validity duration. For example, network device 120 may pair measurement information and tag information based on the corresponding timestamp and validity duration within the information. In some example embodiments, the timestamps of the measurement information and tag information may be included in the measurement information and tag information, respectively. Alternatively, LMF 130 may transmit the timestamp of the tag information to network device 120 separately.

[0086] For example, if the validity duration associated with the timestamp of the measurement information at least partially overlaps with the timestamp of the tag information, network device 120 can pair the measurement information with the tag information. Alternatively, the validity duration can also apply to the tag information. LMF 130 can determine the validity duration of the tag information based on the validity duration of the measurement information. If the validity duration associated with the timestamp of the measurement information and the validity duration associated with the timestamp of the tag information at least partially overlap, network device 120 can pair the measurement information with the tag information.

[0087] Additionally, network device 120 can determine the time difference between the collection of measurement information and the reception of the validity duration of the measurement information. Network device 120 can also determine the pairing between measurement information and tag information based on this time difference.

[0088] For example, the delay between the collection of measurement information and the reception of the validity duration can be estimated and considered for more accurate pairing. Network device 120 can start a specific timer when a measurement is received. After receiving the validity duration from terminal device 110, network device 120 can stop the timer and use it for correction. This method can also be applied to different entities: one starts counting, and the other ends counting.

[0089] As mentioned above, now refer to Figure 3 Provide a detailed description of the configuration for the validity duration. Figure 3 Example configurations of the validity duration according to some example embodiments of this disclosure are shown. For example... Figure 3 As can be seen, the configuration of the validity duration can be a function of the speed of the terminal device 110 and the validity duration used for pairing.

[0090] Typically, the LMF 130 can establish one or more rules to determine the validity duration based on the speed of the terminal device 110. The reason behind this is that the LMF 130 can know other informational characteristics (e.g., source, condition) used to achieve pairing.

[0091] For example, such as Figure 3As shown, this configuration may indicate various reference validity durations and reference speeds corresponding to the reference validity durations. If the terminal device 110 is fixed or static, it is assumed that the information (both measurement information and label information) is valid for a long period of time T0, during which the terminal device 110 is expected to remain fixed. If the speed of the terminal device 110 is lower than V1, for example, the terminal device is carried by a pedestrian, the terminal device 110 may determine the validity duration as T1, whose value is lower than the value of T0. If the speed is between V1 and V2, for example, the terminal device is installed on a bicycle, the validity duration may be determined as T2, where T2<T1<T0. If the speed is between V2 and V3, for example, the terminal device is installed in a car, the validity duration may be determined as T3, where T3<T2. If the speed is higher than V3, the validity duration may be determined as T4 in a short period of time, where T4<T3.

[0092] A simple method may be to indicate the value of the reference validity duration (for example, in ms) according to the range of the estimated speed of the terminal device 110 evaluated by the terminal device 110. The method for estimating the speed may be an implementation of the terminal device 110. Alternatively, the LMF 130 may configure the terminal device 110 with a preferred method to evaluate the speed. For example, the terminal device 110 may determine the speed based on RSRP variation, the number of HOs, or the cell reselection rate. Alternatively, the validity configuration may be set with respect to the parameters used for estimating the speed. For example, the configuration may be expressed as a validity duration that is a function of RSRP variation.

[0093] Additionally, when determining the validity duration, the expected mobility stability of the terminal device 110 may be considered by reducing the validity duration whenever the speed changes and when the confidence of remaining in the same mobility category is low. In addition to the mobility state of the terminal device 110, the terminal device 110 may also consider the mobility stability. For example, if the mobility stability is low, the terminal device 110 may need to reduce the validity duration.

[0094] For example, the terminal device 110 may further determine the validity duration based on the following function :

[0095] where refers to the function for determining the validity duration based on the speed (or mobility) of the terminal device 110, is the estimated speed (m / s) (or mobility), and is the speed variation (or mobility variation). An example of the function may be defined as follows:

[0096] in This refers to the validity duration, such as 1 minute. It should be understood that this is merely an example, and various other functions can be constructed to determine the validity duration based on the speed (or mobility) of the terminal device 110 and optionally on speed stability (or mobility variation).

[0097] Figure 4 Signaling flow 400 of an example procedure for determining the validity duration according to some example embodiments of this disclosure is shown. For discussion purposes, reference will be made to... Figure 1 To describe Figure 4 For example, by using terminal device 110, network device 120 and LMF 130.

[0098] In signaling flow 400, at 401, network device 120 may perform training data collection for an AI / ML model used for localization. At 403, network device 120 may request configuration for validity duration from LMF 130. At 405, LMF 130 may transmit a request to terminal device 110 for capability information to determine the validity duration for pairing.

[0099] At 407, terminal device 110 may respond to a calculation analysis request regarding the validity duration. At 409, terminal device 110 may indicate its capabilities to LMF 130, specifically regarding whether terminal device 110 is capable of calculating the validity duration according to the request from network device 120. Optionally, at 409, terminal device 110 may also inform LMF 130 of the method used to assess its mobility status (e.g., based on HO counts or cell reselection rate). At 411, LMF 130 may analyze the indicated capabilities and determine an appropriate configuration for the paired validity duration that aligns with the indication from terminal device 110.

[0100] At 413, LMF 130 can notify terminal device 110 of the determined configuration to estimate the pairing validity duration. At 415, LMF 130 can also notify network device 120 that terminal device 110 can evaluate the pairing validity duration upon request.

[0101] At 417, network device 120 can perform a UL SRS measurement, which constitutes part A of the collected data. At 419, network device 120 can request the pairing validity duration from terminal device 110 (which will be used for the measurement performed at 417).

[0102] At 421, terminal device 110 can estimate the pairing validity duration based on the configuration received from LMF 130. At 423, terminal device 110 can transmit the validity duration to network device 120. At 425, LMF 130 can transmit the tag information generated by LMF 130 as part B. Finally, at 427, network device 120 can use the corresponding timestamps for parts A and B, as well as the pairing validity duration, to perform pairing between measurement information (part A) and tag information (part B).

[0103] According to some example embodiments of this disclosure, a solution is provided for determining the validity duration for pairing portions from different sources. In the solution provided herein, a first device receives configuration information from a network entity. The configuration information indicates a configuration for the validity duration of measurement information associated with the first device. The measurement information may be associated with and may be collected by terminal device 110. Tag information is generated and provided by LMF 130 for the location of terminal device 110. LMF 130 may need to receive both the measurement information and the tag information, and then pair them using the timestamp information and the validity duration for pairing as presented in this disclosure. The different entities providing the measurement information and tag information (i.e., terminal device 110 and LMF 130) may be associated with use case (case 3b).

[0104] Using the solution provided in this disclosure, measurement information (part A) and tag information (part B) can be associated with validity duration. Network entities can then know the UE's mobility and the validity duration used for pairing. This allows network entities to pair measurements and tags based on validity duration, avoiding degradation of the training data for the AI / ML model used for localization. Therefore, the accuracy of localization using AI / ML models can be improved.

[0105] Figure 5 Signaling flow 500 is shown as an example procedure for determining the duration of validity according to some example embodiments of this disclosure. Reference will be made to this document for discussion purposes. Figure 1 To describe Figure 5 For example, by using terminal device 110 and LMF 130.

[0106] In signaling flow 500, it is assumed that the AI / ML model used for localization will be deployed at LMF 130. LMF 130 can perform the collection of training data for the AI / ML model used for localization of terminal device 110. The training data may include training data samples consisting of measurement information (also known as part A) and label information (also known as part B). The label information is generated by LMF 130 for localization of terminal device 110. LMF 130 may require both measurement information and label information, and then pair them using timestamp information and the validity duration of the pairing.

[0107] Based on the need for validity duration, LMF 130 can transmit (502) a request for capability information to terminal device 110. For example, LMF 130 can explicitly indicate to terminal device 110 that paired part A and part B require validity duration to invoke the process of determining validity duration. Capability information can indicate the capability of terminal device 110 to determine the validity duration of measurement information. Accordingly, terminal device 110 can receive (504) a request for capability information from LMF 130. In response to this request, terminal device 110 can analyze its capabilities and transmit capability information (506) to LMF 130. Accordingly, LMF 130 can receive (508) capability information from terminal device 110.

[0108] For example, LMF 130 may not know the capabilities of terminal device 110, i.e., whether terminal device 110 can determine the validity duration based on its mobility. Therefore, LMF 130 and terminal device 110 may exchange capability information before configuring the determination of the validity duration. The capability information may specifically indicate whether terminal device 110 can determine the validity duration in response to a request from another entity (e.g., LMF 130).

[0109] Based on the capability information of terminal device 110, LMF 130 determines (512) the configuration of the validity duration of the measurement information. LMF can analyze the capabilities of terminal device 110 and determine an appropriate configuration of the validity duration aligned with the indications from the terminal device. Additionally, LMF 130 can also determine the configuration based on available resources to assist other terminal devices in the serving cell provided by network device 120 that can simultaneously request data collection.

[0110] LMF 130 transmits (514) configuration information indicating the configuration to terminal device 110. Correspondingly, terminal device 110 receives (516) configuration information from LMF 130. The configuration for the validity duration can be similar to that referenced above. Figure 3 The configuration described.

[0111] Terminal device 110 can perform (518) collection of training data for an AI / ML model for positioning of terminal device 110. The training data may include at least one training data sample, which may consist of measurement information and label information.

[0112] In this scenario, the measurement information is measured by terminal device 110, and the tag information is generated by LMF 130. The measurement information may include channel measurements, a quality indicator for the channel measurements, and a timestamp for the channel measurements. The timestamp indicates the time instance in which terminal device 110 generated the measurement information.

[0113] In some example embodiments, terminal device 110 can collect measurement information by performing measurements on downlink reference signals transmitted from a network device (not shown) to terminal device 110. For example, terminal device 110 can perform measurements on positioning reference signals (PRS) transmitted from a network device (not shown).

[0114] Terminal device 110 determines the validity duration of the measurement information based on its mobility status (522) according to its configuration. The validity duration of the measurement information may be applied to tag information used for the positioning of terminal device 110.

[0115] Terminal device 110 can determine a mobility state in order to determine the duration of validity. In some example embodiments, terminal device 110 can determine the mobility state based on at least one of the following: a change in reference received power (RSRP) measured by the terminal device, the number of handovers by the terminal device, or the cell reselection rate of the terminal device. For example, if the number of handovers by terminal device 110 is high, terminal device 110 can determine that the speed of terminal device 110 is relatively high.

[0116] In some example embodiments, the capability information transmitted to LMF 130 may also indicate a mode applied by terminal device 110 for determining mobility status. For example, the capability information may indicate that the terminal device can determine mobility status based on the number of RSRP changes or handovers. In such cases, LMF 130 may also determine configuration based on the mode applied by terminal device 110.

[0117] In some example embodiments, the configuration for validity duration can indicate the relationship between the mobility state of the terminal device and the validity duration of the measurement information. Terminal device 110 can determine the validity duration of the measurement information based on this relationship. For example, the relationship can be a function of mobility state and validity duration, such that terminal device 110 can determine the validity duration of the measurement information by calculating this function. Alternatively, the relationship can be a table of mobility state and validity duration, such that terminal device 110 can select a validity duration from the table based on its measured mobility state.

[0118] Additionally, in some example embodiments, terminal device 110 may also determine the validity duration of the measurement information based on the mobility stability of terminal device 110. Mobility stability can indicate changes in the mobility state of terminal device 110. For example, if mobility stability is low, terminal device 110 may determine that it is experiencing rapid changes in mobility, allowing terminal device 110 to determine that the validity duration can be relatively short. On the other hand, if mobility stability is high, the validity duration can be determined to be longer.

[0119] In some example embodiments, terminal device 110 may also determine the validity duration of the measurement information based on a reference validity duration. The reference validity duration may be determined relative to a reference distance or a reference time period.

[0120] In some example embodiments, terminal device 110 may receive an indication of a quality requirement for at least one of the measurement information or tag information. Terminal device 110 may also determine the validity duration based on the relationship between the quality requirement and the validity duration. For example, the relationship between the quality requirement and the validity duration may be indicated to terminal device 110 in association with the configuration of the validity duration. Alternatively, the relationship between the quality requirement and the validity duration may be pre-configured to terminal device 110 or specified. For example, if the quality of at least one of the measurement information or tag information is low, terminal device 110 may take this into account and adjust the validity duration accordingly.

[0121] Based on the determination of the validity duration, terminal device 110 transmits (524) information indicating the validity duration to LMF 130 in association with measurement information. Accordingly, LMF 130 receives (526) the information indicating the validity duration and the measurement information from terminal device 110. In some example embodiments, terminal device 110 may also transmit a timestamp associated with the measurement information to LMF 130. In some example embodiments, the timestamp may be included within the measurement information. Alternatively, terminal device 110 may transmit the timestamp to LMF 130 separately. On the other hand, LMF 130 may generate tag information for locating terminal device 110. In some example embodiments, LMF 130 may determine the validity duration of the tag information based on the validity duration of the measurement information.

[0122] Based on the generation of the label information, LMF 130 determines (528) the pairing between measurement information and label information based on the validity duration. For example, LMF 130 may pair measurement information and label information based on the corresponding timestamp and validity duration within the information.

[0123] For example, if the validity duration associated with the timestamp of the measurement information at least partially overlaps with the timestamp of the label information, the LMF 130 can pair the measurement information with the label information. Additionally, the validity duration can also be applied to the label information. The LMF 130 can determine the validity duration of the label information based on the validity duration of the measurement information. If the validity duration associated with the timestamp of the measurement information and the validity duration associated with the timestamp of the label information at least partially overlap, the LMF 130 can pair the measurement information with the label information.

[0124] Terminal device 110 can determine the time difference between the collection of measurement information and the determination of the validity period of the measurement information. Terminal device 110 can transmit this time difference to LMF 130, so that LMF 130 can also determine the pairing between measurement information and tag information based on the time difference.

[0125] For example, the delay between the collection of measurement information and the reception of the validity duration can be estimated and considered for more accurate pairing. Terminal device 110 can start a specific timer when a measurement value is obtained. After determining the validity duration, terminal device 110 can stop the timer and transmit it to LMF 130 to utilize the timer for correction. This method can also be applied to different entities: one starting to count, and the other ending to count.

[0126] Figure 6Signaling flow 600 of an example procedure for determining the duration of validity according to some example embodiments of this disclosure is shown. Reference will be made to this document for discussion purposes. Figure 1 To describe Figure 6 For example, by using terminal device 110, network device 120 and LMF 130.

[0127] At 601, LMF 130 may perform training data collection for the AI / ML model. LMF 130 may require an effective duration for pairing portions A and B of the training data samples. At 603, LMF 130 may transmit a request for capability information to terminal device 110 when determining the effective duration for pairing. At 605, terminal device 110 may request a calculation analysis regarding the effective duration. At 607, terminal device 110 may indicate its capabilities to LMF 130, specifically regarding whether terminal device 110 is capable of calculating the effective duration according to the request from LMF 130. Optionally, at 608, terminal device 110 may also inform LMF 130 of the method used to assess its mobility status (e.g., based on HO counts or cell reselection rate). At 609, LMF 130 may analyze the indicated capabilities and determine an appropriate configuration of the pairing effective duration aligned with the indication from terminal device 110.

[0128] At 611, LMF 130 can notify terminal device 110 of the determined configuration to estimate the pairing validity duration. At 613, terminal device 110 can perform DL PRS measurements, which constitute part A of the collected data.

[0129] At 615, terminal device 110 can determine the pairing validity duration after receiving configuration from LMF 130. At 617, terminal device 110 can transmit the validity duration and measurement information to LMF 130. The measurement information may include a timestamp indicating the time when the measurement information was measured by terminal device 110. At 619, LMF 130 can generate tag information as part B, and finally at 621, LMF 130 can use the corresponding timestamps of part A and part B, as well as the pairing validity duration, to perform pairing between the measurement information (part A) and the tag information (part B).

[0130] Figure 7 A flowchart of an example method 700 implemented at a terminal device for scenario 3a according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Angle description method 700 for terminal device 110 in the middle.

[0131] At box 710, terminal device 110 receives configuration information from LMF, which indicates the configuration for the validity duration of the measurement information.

[0132] At box 720, terminal device 110 receives from network device a request for the validity duration of measurement information associated with terminal device.

[0133] At box 730, terminal device 110 determines the validity duration of measurement information based on the mobility status of the terminal device according to its configuration.

[0134] At box 740, terminal device 110 transmits information to network device indicating the duration of validity of measurement information.

[0135] In some example embodiments, method 700 further includes: determining the validity duration of the measurement information based on the relationship.

[0136] In some example embodiments, method 700 further includes determining the mobility state of the terminal device based on at least one of the following: changes in reference signal received power (RSRP) measured by the terminal device, the number of handovers by the terminal device, or the cell reselection rate of the terminal device.

[0137] In some example embodiments, method 700 further includes: determining the validity duration of the measurement information based on the mobility stability of the terminal device, wherein mobility stability indicates changes in the mobility state of the terminal device.

[0138] In some example embodiments, method 700 further includes: determining the validity duration of the measurement information based on a reference validity duration, wherein the reference validity duration is determined relative to a reference distance or a reference time period.

[0139] In some example embodiments, method 700 further includes: receiving a request for capability information from the LMF, the capability information indicating the capability of the terminal device to determine the duration of validity; and transmitting the capability information to the LMF.

[0140] In some example embodiments, the capability information also indicates the mode applied by the terminal device to determine the mobility state.

[0141] In some example embodiments, the measurement information is paired with tag information at the network device, and the tag information is used for the positioning of the terminal device.

[0142] In some example embodiments, method 700 further includes: receiving from the LMF an indication of a quality requirement for at least one of the following: measurement information or tag information for positioning of a terminal device; and further determining the validity duration of the measurement information based on the relationship between the quality requirement and the validity duration.

[0143] In some example embodiments, the terminal device is a terminal device or is included in a terminal device, and the LMF implements or includes a location management function LMF, and the network device is a network device serving the terminal device or is included in a network device serving the terminal device.

[0144] Figure 8 A flowchart of an example method 800 implemented at the LMF for case 3a according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The LMF 130 angular description method 800.

[0145] At box 810, the LMF 130 determines the configuration for the validity duration of the measurement information based on the capability information of the terminal device.

[0146] At box 820, LMF 130 transmits configuration information indicating the configuration to the terminal device.

[0147] At box 830, LMF 130 transmits to the network device an indication of the terminal device's ability to determine the duration of validity.

[0148] In some example embodiments, the configuration of validity duration indicates the relationship between the mobility status of the terminal device and the validity duration of the measurement information.

[0149] In some example embodiments, method 800 further includes: transmitting a request for capability information to a terminal device, the capability information indicating a capability for which the terminal device determines the duration of validity; and receiving capability information from the terminal device; and wherein a configuration is determined based on the capability information of the terminal device.

[0150] In some example embodiments, method 800 further includes: determining a configuration for validity duration based on a pattern applied by the terminal device to determine mobility status.

[0151] In some example embodiments, method 800 further includes receiving a request from a network device for configuring the validity duration of the measurement information.

[0152] In some example embodiments, method 800 further includes: generating tag information for locating terminal devices, wherein the tag information will be paired with measurement information; and transmitting the tag information to a network device.

[0153] In some example embodiments, method 800 further includes: determining the validity duration of label information based on the validity duration of measurement information.

[0154] In some example embodiments, method 800 further includes transmitting to a terminal device an indication of quality requirements for at least one of measurement information or tag information.

[0155] Figure 9 A flowchart is shown illustrating an example method 900 implemented at a network device for scenario 3a according to some example embodiments of the present disclosure. For discussion purposes, [the following will be discussed]. Figure 1 Method 900 describes the network device 120 from the perspective of network device 120.

[0156] At box 910, network device 120 receives from LMF an indication of the terminal device’s ability to determine the validity duration of measurement information.

[0157] At box 920, network device 120 transmits a request to terminal device for the validity duration of the measurement information.

[0158] At box 930, network device 120 receives information from terminal device indicating the duration of validity of measurement information.

[0159] At box 940, based on the received tag information for locating the terminal device, the pairing between the measurement information and the tag information is determined based on the validity duration of the measurement information, the timestamp associated with the measurement information, and the timestamp associated with the tag information.

[0160] In some example embodiments, method 900 further includes transmitting to the LMF a request for configuring the validity duration of measurement information associated with the terminal device.

[0161] In some example embodiments, method 900 further includes: collecting training data for an artificial intelligence / machine learning (AI / ML) model used to locate a terminal device, wherein the training data includes training data samples consisting of measurement information and label information.

[0162] In some example embodiments, method 900 further includes collecting measurement information by performing measurements on uplink reference signals transmitted from the terminal device to the network device.

[0163] In some example embodiments, method 900 further includes: determining the time difference between the collection of measurement information and the reception of the validity duration of the measurement information; and also determining a pairing between measurement information and tag information based on the time difference.

[0164] Figure 10 A flowchart illustrating an example method 1000 implemented at a terminal device for scenario 3b according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Angle description method 1000 for terminal device 110 in the middle.

[0165] At box 1010, configuration information is received from the LMF, which indicates the configuration for the validity duration of measurement information associated with the terminal device.

[0166] At box 1020, based on the collection of measurement information, the validity duration of the measurement information is determined according to the mobility status of the terminal device and the configuration.

[0167] At box 1030, information associated with the measurement information is transmitted to the LMF, indicating the duration of validity of the measurement information.

[0168] In some example embodiments, method 1000 further includes: determining the validity duration of the measurement information based on the relationship.

[0169] In some example embodiments, method 1000 further includes determining the mobility state of the terminal device based on at least one of the following: changes in reference signal received power (RSRP) measured by the terminal device, the number of handovers by the terminal device, or the cell reselection rate of the terminal device.

[0170] In some example embodiments, method 1000 further includes collecting measurement information by performing measurements on downlink reference signals transmitted from a network device to a terminal device.

[0171] In some example embodiments, method 1000 further includes: receiving a request from the LMF for the validity duration of the measurement information; and in response to the request, determining the validity duration of the measurement information.

[0172] In some example embodiments, method 1000 further includes: determining the validity duration of the measurement information based on the mobility stability of the terminal device, wherein mobility stability indicates changes in the mobility state of the terminal device.

[0173] In some example embodiments, method 1000 further includes: determining the validity duration of the measurement information based on a reference validity duration, wherein the reference validity duration is determined relative to a reference distance or a reference time period.

[0174] In some example embodiments, method 1000 further includes: receiving a request for capability information from the LMF, the capability information indicating the capability of the terminal device to determine the duration of validity; and transmitting the capability information to the LMF.

[0175] In some example embodiments, the capability information also indicates the pattern used by the terminal device application to determine the mobility status.

[0176] In some example embodiments, method 1000 further includes: determining a time difference between the collection of measurement information and the validity duration of the measurement information; and transmitting information indicating the time difference to the LMF in association with the validity duration of the measurement information; In some example embodiments, the measurement information is paired with tag information at the LMF, and the tag information is used for the positioning of the terminal device.

[0177] In some example embodiments, method 1000 further includes: receiving from LMF an indication of a quality requirement that indicates at least one of the following: measurement information or tag information for positioning of the first device; and further determining the validity duration of the measurement information based on the relationship between the quality requirement and the validity duration.

[0178] In some example embodiments, the terminal device is a terminal device or is included in a terminal device, and the LMF implements or includes the location management function LMF.

[0179] Figure 11 A flowchart of an example method 1100 implemented at the LMF for case 3b according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The LMF 130 angular description method 1100.

[0180] At box 1110, the LMF 130 determines the configuration of the validity duration of measurement information related to the terminal device based on the terminal device's capability information.

[0181] At box 1120, LMF 130 transmits configuration information indicating the configuration to the terminal device, and At box 1130, LMF 130 receives information from the terminal device in association with the measurement information, indicating the duration of validity of the measurement information.

[0182] At box 1140, based on the generation of tag information for the positioning of the terminal device, LMF 130 determines the pairing between measurement information and tag information based on the validity duration of the measurement information, the timestamp associated with the measurement information, and the timestamp associated with the tag information.

[0183] In some example embodiments, the configuration of validity duration indicates the relationship between the mobility status of the terminal device and the validity duration of the measurement information.

[0184] In some example embodiments, method 1100 further includes: transmitting a request for capability information to a terminal device, the capability information indicating a capability for which the terminal device determines a validity duration; and receiving capability information from the terminal device, wherein a configuration is determined based on the capability information of the terminal device.

[0185] In some example embodiments, method 1100 further includes: determining the validity duration based on a configuration by which a terminal device application determines a pattern for determining mobility status.

[0186] In some example embodiments, method 1100 further includes: collecting training data for an artificial intelligence / machine learning (AI / ML) model for locating a terminal device, wherein the training data includes at least one training data sample consisting of measurement information and label information.

[0187] In some example embodiments, method 1100 further includes: determining the validity duration of the label information based on the validity duration of the measurement information.

[0188] In some example embodiments, method 1100 further includes transmitting a request to the terminal device for the validity duration of the measurement information.

[0189] In some example embodiments, method 1100 further includes transmitting to a terminal device an indication of quality requirements for at least one of the measurement information or tag information.

[0190] In some example embodiments, method 1100 further includes: receiving from the terminal device the time difference between the collection of measurement information and the validity period of receiving the measurement information at the terminal device; and further determining a pairing between the measurement information and tag information based on the time difference.

[0191] In some example embodiments, a first device capable of performing any method 700 (e.g., Figure 1 The first device 110 may include components for performing the corresponding operation of method 700. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.

[0192] In some example embodiments, the first device includes: components for receiving configuration information from a network entity, the configuration information indicating a configuration for the validity duration of measurement information; components for receiving a request from a second device for the validity duration of measurement information associated with the first device; components for determining the validity duration of the measurement information based on the mobility state of the first device according to the configuration; and components for transmitting information indicating the validity duration of the measurement information to the second device.

[0193] In some example embodiments, the first device further includes a component for determining the duration of validity of the measurement information based on the relationship.

[0194] In some example embodiments, the first device further includes: a component for determining the mobility state of the first device based on at least one of the following: a change in the reference signal received power (RSRP) measured by the first device, the number of handovers by the first device, or the cell reselection rate of the first device.

[0195] In some example embodiments, the first device further includes a component for determining the duration of validity of the measurement information based on the mobility stability of the first device, wherein the mobility stability indicates a change in the mobility state of the first device.

[0196] In some example embodiments, the first apparatus further includes a component for determining the validity duration of the measurement information based on a reference validity duration, wherein the reference validity duration is determined relative to a reference distance or a reference time period.

[0197] In some example embodiments, the first apparatus further includes: a component for receiving a request for capability information from a network entity, the capability information indicating a capability for which the first apparatus determines the duration of validity; and a component for transmitting the capability information to the network entity.

[0198] In some example embodiments, the capability information also indicates a mode applied by the first device for determining the mobility state.

[0199] In some example embodiments, the measurement information is paired with tag information at the second device, and the tag information is used for the positioning of the first device.

[0200] In some example embodiments, the first device further includes: components for receiving from a network entity an indication of a quality requirement for at least one of the following: measurement information or tag information for positioning the first device; and components for determining the validity duration of the measurement information based on the relationship between the quality requirement and the validity duration.

[0201] In some example embodiments, the first device is a terminal device or is included in a terminal device, and the network entity implements or includes a location management function (LMF), and the second device is a network device serving the first device or is included in a network device serving the first device.

[0202] In some example embodiments, network entities capable of performing any method 800 (e.g., Figure 1 The network entity 130 in the method 800 may include components for performing the corresponding operations of the method. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or software module. The network entity may be implemented as or included in... Figure 1 Among network entities 130.

[0203] In some example embodiments, the network entity includes: components for determining a configuration for the validity duration of measurement information based on capability information of a first device; components for transmitting configuration information indicating the configuration to the first device; and components for transmitting an indication to a second device indicating the capability of the first device to determine the validity duration.

[0204] In some example embodiments, the configuration of the validity duration indicates the relationship between the mobility state of the first device and the validity duration of the measurement information.

[0205] In some example embodiments, the network entity further includes: components for transmitting a request for capability information to the first device, the capability information indicating the capability of the first device to determine the duration of validity; and components for receiving capability information from the first device; and wherein the configuration is determined based on the capability information of the first device.

[0206] In some example embodiments, the network entity further includes a component for determining the duration of validity based on a configuration applied by the first means to determine the mobility state.

[0207] In some example embodiments, the network entity further includes a component for receiving a request from the second device for configuring the validity duration of the measurement information.

[0208] In some example embodiments, the network entity further includes: components for generating tag information for locating the first device, wherein the tag information will be paired with measurement information; and components for transmitting the tag information to the second device.

[0209] In some example embodiments, the network entity further includes a component for determining the validity duration of the tag information based on the validity duration of the measurement information.

[0210] In some example embodiments, the network entity further includes a component for transmitting to the first device an indication of a quality requirement for at least one of measurement information or tag information.

[0211] In some example embodiments, a second device capable of performing any method 900 (e.g., Figure 1 The second device 120 may include components for performing the corresponding operation of method 900. This device may be implemented in any suitable form. For example, it may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.

[0212] In some example embodiments, the second device includes: components for receiving from a network entity an indication of the ability of the first device to determine the validity duration of measurement information; components for transmitting a request for the validity duration of the measurement information to the first device; components for receiving from the first device information indicating the validity duration of the measurement information; and components for determining a pairing between measurement information and tag information based on the validity duration of the measurement information, a timestamp associated with the measurement information, and a timestamp associated with the tag information, according to tag information received for positioning of the first device.

[0213] In some example embodiments, the second device further includes a component for transmitting to a network entity a request for configuring the validity duration of measurement information associated with the first device.

[0214] In some example embodiments, the second device further includes: a component for collecting training data for an artificial intelligence / machine learning (AI / ML) model for positioning of the first device, wherein the training data includes training data samples consisting of measurement information and label information.

[0215] In some example embodiments, the second device further includes a component for collecting measurement information by performing measurements on an uplink reference signal transmitted from the first device to the second device.

[0216] In some example embodiments, the second apparatus further includes: a component for determining the time difference between the collection of measurement information and the reception of the validity duration of the measurement information; and a component for further determining a pairing between the measurement information and tag information based on the time difference.

[0217] In some example embodiments, a first device capable of performing any method 1000 (e.g., Figure 1 The first device 110 may include components for performing the corresponding operation of method 1000. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.

[0218] In some example embodiments, the first device includes: components for receiving configuration information from a network entity, the configuration information indicating a configuration for the validity duration of measurement information associated with the first device; components for determining the validity duration of the measurement information based on the collection of measurement information, the mobility state of the first device, and the configuration; and components for transmitting information associated with the measurement information to the network entity, the information indicating the validity duration of the measurement information.

[0219] In some example embodiments, the first device further includes a component for determining the validity duration of the measurement information based on the relationship.

[0220] In some example embodiments, the first device further includes: a component for determining the mobility state of the first device based on at least one of the following: a change in the reference signal received power (RSRP) measured by the first device, the number of handovers by the first device, or the cell reselection rate of the first device.

[0221] In some example embodiments, the first device further includes a component for collecting measurement information by performing measurements on a downlink reference signal transmitted from the second device to the first device.

[0222] In some example embodiments, the first apparatus further includes: a component for receiving a request from a network entity for the validity duration of measurement information; and a component for determining the validity duration of the measurement information in response to the request.

[0223] In some example embodiments, the first device further includes a component for determining the validity duration of the measurement information based on the mobility stability of the first device, wherein mobility stability indicates changes in the mobility state of the first device.

[0224] In some example embodiments, the first apparatus further includes a component for determining the validity duration of the measurement information based on a reference validity duration, wherein the reference validity duration is determined relative to a reference distance or a reference time period.

[0225] In some example embodiments, the first apparatus further includes: a component for receiving a request for capability information from a network entity, the capability information indicating a capability for which the first apparatus determines the duration of validity; and a component for transmitting the capability information to the network entity.

[0226] In some example embodiments, the capability information also indicates a pattern applied by the first device to determine the mobility state.

[0227] In some example embodiments, the first apparatus further includes: a component for determining a time difference between the collection of measurement information and the determination of the validity duration of the measurement information; and a component for transmitting information indicating the time difference to a network entity in association with the validity duration of the measurement information; In some example embodiments, the measurement information is paired with tag information at the network entity, and the tag information is used for the positioning of the first device.

[0228] In some example embodiments, the first device further includes: a component for receiving from a network entity an indication of a quality requirement that includes at least one of the following: measurement information or tag information for positioning the first device; and a component for determining the validity duration of the measurement information based on the relationship between the quality requirement and the validity duration.

[0229] In some example embodiments, the first device is a terminal device or is included in a terminal device, and the network entity implements or includes a location management function (LMF).

[0230] In some example embodiments, network entities capable of performing any method 1100 (e.g., Figure 1 The network entity 130 may include components for performing the corresponding operations of method 1100. This device can be implemented in any suitable form. For example, the device can be implemented in a circuit or software module. The network entity can be implemented as or included in... Figure 1 Among network entities 130.

[0231] In some example embodiments, the network entity includes: components for determining a configuration for the validity duration of measurement information associated with the first device based on capability information of the first device; components for transmitting configuration information indicating the configuration to the first device; components for receiving information indicating the validity duration of the measurement information from the first device in association with the measurement information; and components for determining a pairing between measurement information and tag information based on the validity duration of the measurement information, a timestamp associated with the measurement information, and a timestamp associated with the tag information, according to the generation of tag information for positioning of the first device.

[0232] In some example embodiments, the configuration of the validity duration indicates the relationship between the mobility state of the first device and the validity duration of the measurement information.

[0233] In some example embodiments, the network entity further includes: components for transmitting a request for capability information to the first device, the capability information indicating the capability of the first device to determine the duration of validity; and components for receiving capability information from the first device, wherein the configuration is determined based on the capability information of the first device.

[0234] In some example embodiments, the network entity further includes a component for determining the duration of validity based on a configuration applied by the first means to determine the mobility state.

[0235] In some example embodiments, the network entity further includes: a component for collecting training data for an artificial intelligence / machine learning (AI / ML) model for positioning of the first device, wherein the training data includes at least one training data sample consisting of measurement information and label information.

[0236] In some example embodiments, the network entity further includes a component for determining the validity duration of the tag information based on the validity duration of the measurement information.

[0237] In some example embodiments, the network entity further includes a component for transmitting a request to the first device for the duration of validity of the measurement information.

[0238] In some example embodiments, the network entity further includes a component for transmitting to the first device an indication of a quality requirement for at least one of measurement information or tag information.

[0239] In some example embodiments, the network entity further includes: a component for receiving from the first device the time difference between the collection of measurement information and the effective duration of receiving the measurement information at the first device; and a component for further determining a pairing between the measurement information and tag information based on the time difference.

[0240] Figure 12 This is a simplified block diagram of a device 1200 suitable for implementing an example embodiment of the present disclosure. The device 1200 can be provided to implement a communication device, such as... Figure 1 The terminal device 110 or network device 120 shown. As shown, device 1200 includes one or more processors 1210, one or more memories 1220 coupled to processor 1210, and one or more communication modules 1240 coupled to processor 1210.

[0241] Communication module 1240 is used for bidirectional communication. Communication module 1240 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 1240 may include at least one antenna.

[0242] As a non-limiting example, processor 1210 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1200 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with a main processor.

[0243] Memory 1220 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1224, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1222 and other volatile memories that will not persist for the duration of a power outage.

[0244] Computer program 1230 includes computer-executable instructions that are executed by an associated processor 1210. The instructions of program 1230 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1230 may be stored in memory (e.g., ROM 1224). Processor 1210 can perform any suitable actions and processes by loading program 1230 into RAM 1222.

[0245] The exemplary embodiments of this disclosure can be implemented by program 1230, enabling device 1200 to execute as described in the reference. Figures 2 to 11 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0246] In some example embodiments, program 1230 may be tangibly contained in a computer-readable medium, which may be included in device 1200 (such as memory 1220) or other storage device accessible by device 1200. Device 1200 may load program 1230 from the computer-readable medium into RAM 1222 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0247] Figure 13 An example of a computer-readable medium 1300 is shown, which may be in the form of a CD, DVD, or other optical storage disc. A program 1230 is stored on the computer-readable medium 1300.

[0248] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0249] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.

[0250] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0251] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0252] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0253] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0254] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

[0255] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0256] Clause 1. A first device for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: receive configuration information from a network entity, the configuration information indicating a configuration for a validity duration of measurement information; receive a request from a second device for a validity duration of measurement information associated with the first device; determine the validity duration of the measurement information based on a mobility state of the first device according to the configuration; and transmit information indicating the validity duration of the measurement information to the second device.

[0257] Clause 2. The first device according to Clause 1, wherein the configuration for the validity duration indicates a relationship between the mobility state of the first device and the validity duration of the measurement information, and wherein the first device is configured to: determine the validity duration of the measurement information based on the relationship.

[0258] Clause 3. The first apparatus according to Clause 1, wherein the first apparatus is further configured to: determine the mobility state of the first apparatus based on at least one of the following: a change in reference signal received power (RSRP) measured by the first apparatus, the number of handovers by the first apparatus, or the cell reselection rate of the first apparatus.

[0259] Clause 4. The first device according to Clause 1, wherein the first device is configured to: further determine the validity duration of the measurement information based on the mobility stability of the first device, wherein the mobility stability indicates a change in the mobility state of the first device.

[0260] Clause 5. The first device according to any one of Clauses 1 to 4, wherein the first device is configured to: further determine the validity duration of the measurement information based on a reference validity duration, wherein the reference validity duration is determined relative to a reference distance or a reference time period.

[0261] Clause 6. The first apparatus according to any one of Clauses 1 to 4, wherein the first apparatus is further configured to: receive from the network entity a request for capability information, the capability information indicating the capability of the first apparatus to determine the duration of the validity; and transmit the capability information to the network entity.

[0262] Clause 7. The first device as described in Clause 6, wherein the capability information further indicates a mode applied by the first device to determine the mobility state.

[0263] Clause 8. The first device according to any one of Clauses 1 to 4, wherein the measurement information is paired with tag information at the second device, and wherein the tag information is used for positioning of the first device.

[0264] Clause 9. The first device according to Clause 8, wherein the first device is further configured to: receive from the network entity an indication of a quality requirement for at least one of the following: the measurement information or the tag information for positioning the first device; and further determine the validity duration of the measurement information based on a relationship between the quality requirement and the validity duration.

[0265] Clause 10. The first device according to any one of Clauses 1 to 4, wherein the first device is a terminal device or is included in a terminal device, and wherein the network entity implements or includes a Location Management Function (LMF), and wherein the second device is a network device serving the first device or is included in a network device serving the first device.

[0266] Clause 11. A network entity for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network entity to: determine a configuration for a validity duration of measurement information based on capability information of a first device; transmit configuration information indicating the configuration to the first device; and transmit an indication to a second device indicating the capability of the first device to determine the validity duration.

[0267] Clause 12. A second means for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second means to: receive from a network entity an instruction instructing a first means to determine the validity duration of measurement information; transmit to the first means a request for the validity duration of the measurement information; receive from the first means information instructing the validity duration of the measurement information; and determine a pairing between the measurement information and the tag information based on the validity duration of the measurement information, a timestamp associated with the measurement information, and a timestamp associated with the tag information, according to tag information received for positioning of the first means.

[0268] Clause 13. A method for communication, comprising: receiving configuration information from a network entity, the configuration information indicating a configuration for a validity duration of measurement information; receiving a request from a second device for a validity duration of measurement information associated with a first device; determining the validity duration of the measurement information based on a mobility state of the first device according to the configuration; and transmitting information indicating the validity duration of the measurement information to the second device.

[0269] Clause 14. A method for communication, comprising: determining a configuration for a validity duration of measurement information based on capability information of a first device; transmitting configuration information indicating the configuration to the first device; and transmitting an indication to a second device indicating the capability of the first device to determine the validity duration.

[0270] Clause 15. A method for communication, comprising: receiving from a network entity an indication of an ability of a first device to determine the validity duration of measurement information; transmitting to the first device a request for the validity duration of the measurement information; receiving from the first device information indicating the validity duration of the measurement information; and determining a pairing between the measurement information and the tag information based on the validity duration of the measurement information, according to received tag information for positioning of the first device.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: Receive configuration information from a network entity, the configuration information indicating a configuration for the validity duration of the measurement information; Receive a request from the second device for the validity duration of measurement information associated with the first device; According to the configuration, the validity duration of the measurement information is determined based on the mobility status of the first device; as well as The second device transmits information indicating the duration of the validity of the measurement information.

2. The first device according to claim 1, wherein the configuration for the validity duration indicates a relationship between the mobility state of the first device and the validity duration of the measurement information, and wherein the first device is configured such that: Based on the relationship, the validity duration of the measurement information is determined.

3. The first device according to claim 1, wherein the first device is further configured to: The mobility state of the first device is determined based on at least one of the following: The change in the reference signal received power RSRP measured by the first device, The number of times the first device switches, or The cell reselection rate of the first device.

4. The first device according to claim 1, wherein the first device is configured to: The validity duration of the measurement information is also determined based on the mobility stability of the first device, wherein the mobility stability indicates changes in the mobility state of the first device.

5. The first device according to any one of claims 1 to 4, wherein the first device is configured to: The validity duration of the measurement information is also determined based on a reference validity duration, wherein the reference validity duration is determined relative to a reference distance or a reference time period.

6. The first device according to any one of claims 1 to 4, wherein the first device is further configured to: Receive a request for capability information from the network entity, the capability information indicating the capability of the first device to determine the duration of the validity period; and The capability information is transmitted to the network entity.

7. The first apparatus of claim 6, wherein the capability information further indicates a mode applied by the first apparatus to determine the mobility state.

8. The first device according to any one of claims 1 to 4, wherein the measurement information is paired with tag information at the second device, and wherein the tag information is used for positioning of the first device.

9. The first device according to claim 8, wherein the first device is further configured to: Receive from the network entity an indication of quality requirements for at least one of the following: the measurement information or the tag information used for positioning the first device; and The validity duration of the measurement information is also determined based on the relationship between quality requirements and validity duration.

10. The first device according to any one of claims 1 to 4, wherein the first device is a terminal device or is included in a terminal device, and wherein the network entity implements or includes a location management function (LMF), and wherein the second device is a network device serving the first device or is included in a network device serving the first device.