Apparatus and method for positioning

Abstract

Embodiments of the present disclosure relate to positioning. The terminal device obtains a rare event parameter, where the rare event parameter indicates one or more sets of conditions corresponding to one or more rare events, and where the one or more rare events indicate one or more events that are considered as anomalous wireless conditions for localization. The terminal device identifies the rare event based on one or more sets of conditions indicated by the rare event parameter. Therefore, the positioning accuracy can be improved.

Description

Technical Field

[0001] Various embodiments relate to the field of telecommunications, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for positioning. Background Art

[0002] With the development of communication technology, artificial intelligence (AI) / machine learning (ML) for the new radio (NR) air interface has been introduced to improve positioning accuracy. AI / ML models can be used, for example, to identify common and specific characteristics for frame surveys.

[0003] Some examples include: characterizing the definition phase of AI / ML-related algorithms and associated complexity; identifying the various levels of collaboration between user equipment (UE) and gNodeB related to selected use cases; characterizing the lifecycle management of AI / ML models; model training, model deployment, model inference, model monitoring, model updates; (multiple) datasets for training, validation, testing, and inference; identifying common symbols and terminology for AI / ML-related functions, processes, and interfaces, etc.

[0004] Currently, in order to further improve positioning accuracy, the AI / ML models used for positioning still need to be further improved. Summary of the Invention

[0005] Generally speaking, example embodiments of the present disclosure provide a solution for positioning.

[0006] In a first aspect, a terminal device is provided. The terminal device includes: one or more transceivers; and one or more processors coupled to the one or more transceivers, wherein the one or more transceivers are configured to, together with the one or more processors, cause the terminal device to: obtain rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning; and identify the rare events based on the one or more condition sets indicated by the rare event parameters.

[0007] In a second aspect, a terminal device is provided. The terminal device includes: one or more transceivers; and one or more processors coupled to the one or more transceivers, wherein the one or more transceivers are configured to, together with the one or more processors, cause the terminal device to: receive rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; send the rare event parameters to another terminal device; and receive a report associated with the identified rare event from the other terminal device.

[0008] In a third aspect, a network device is provided. The network device includes: one or more transceivers; and one or more processors coupled to the one or more transceivers, wherein the one or more transceivers are configured to, together with the one or more processors, cause the network device to: send rare event parameters to a terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning purposes.

[0009] In a fourth aspect, a method at a terminal device is provided. The method includes: obtaining a rare event parameter, wherein the rare event parameter indicates one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning; and identifying the rare event based on the one or more condition sets indicated by the rare event parameter.

[0010] In a fifth aspect, a method at a terminal device is provided. The method comprises: receiving rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; sending the rare event parameters to another terminal device; and receiving a report associated with the identified rare event from the other terminal device.

[0011] In a sixth aspect, a method at a network device is provided, comprising: sending a rare event parameter to a terminal device, wherein the rare event parameter indicates one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

[0012] In a seventh aspect, an apparatus of a terminal device is provided. The apparatus includes: means for obtaining a rare event parameter, wherein the rare event parameter indicates one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; and means for identifying the rare event based on the one or more condition sets indicated by the rare event parameter.

[0013] In an eighth aspect, an apparatus of a terminal device is provided. The apparatus includes: means for receiving rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; means for sending the rare event parameters to another terminal device; and means for receiving a report associated with the identified rare event from the other terminal device.

[0014] In a ninth aspect, an apparatus of a network device is provided. The apparatus includes: means for sending rare event parameters to a terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning purposes.

[0015] In a tenth aspect, a terminal device is provided. The terminal device includes: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: obtain a rare event parameter, wherein the rare event parameter indicates one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning; and identify the rare event based on the one or more condition sets indicated by the rare event parameter.

[0016] In an eleventh aspect, a terminal device is provided. The terminal device includes: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: receive rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; send the rare event parameters to another terminal device; and receive a report associated with the identified rare event from the other terminal device.

[0017] In a twelfth aspect, a network device is provided. The network device includes: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause a terminal device to: send rare event parameters to the terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

[0018] In a thirteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus to at least execute a method according to any one of the fourth to sixth aspects above.

[0019] In a fourteenth aspect, there is provided a computer program comprising instructions that, when executed by an apparatus, cause the apparatus to at least: obtain rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare event indications are one or more events that are considered abnormal wireless conditions for positioning; and identify the rare event based on the one or more condition sets indicated by the rare event parameters.

[0020] In a fifteenth aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to at least: receive rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare event indications are one or more events that are considered abnormal wireless conditions for positioning; send the rare event parameters to another terminal device; and receive a report associated with the identified rare event from the other terminal device.

[0021] In a sixteenth aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to at least: send rare event parameters to a terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare event indications are one or more events that are considered to be abnormal wireless conditions for positioning.

[0022] In a seventeenth aspect, a terminal device is provided. The terminal device includes: an obtaining circuit configured to obtain rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; and an identifying circuit configured to identify the rare event based on the one or more condition sets indicated by the rare event parameters.

[0023] In an eighteenth aspect, a terminal device is provided. The terminal device includes: a receiving circuit configured to receive rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; a transmitting circuit configured to transmit the rare event parameters to another terminal device; and another receiving circuit configured to receive a report associated with the identified rare event from the other terminal device.

[0024] In a nineteenth aspect, a network device is provided. The network device includes: a transmitting circuit configured to transmit rare event parameters to a terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning.

[0025] It should be understood that this summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0027] Figure 1 shows an example communication network in which embodiments of the present disclosure may be implemented;

[0028] Figure 2a shows an example signaling diagram illustrating an example procedure according to some embodiments of the present disclosure;

[0029] Figure 2b shows another example signaling diagram illustrating an example process according to some embodiments of the present disclosure;

[0030] Figure 3 shows an example process according to some embodiments of the present disclosure;

[0031] Figure 4 Another example process according to some embodiments of the present disclosure is shown;

[0032] Figure 5 shows yet another example process according to some embodiments of the present disclosure;

[0033] Figure 6 shows yet another example process according to some embodiments of the present disclosure;

[0034] Figure 7 shows yet another example process according to some embodiments of the present disclosure;

[0035] Figure 8 A flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure is shown;

[0036] Figure 9 A flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure is shown;

[0037] Figure 10A flowchart illustrating a method implemented at a network device according to some embodiments of the present disclosure is shown;

[0038] Figure 11 shows a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure; and

[0039] Figure 12 A block diagram of an example computer-readable medium is shown, according to some embodiments of the present disclosure.

[0040] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0041] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure without implying any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways except for the manner described below.

[0042] In the following description and claims, unless defined otherwise, 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 belongs.

[0043] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is understood that it is within the knowledge of those skilled in the art to also incorporate such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0044] It should be understood that although the terms "first" and "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0045] The terms used herein are only used to describe the purpose of specific embodiments and are not intended to limit example embodiments. As used herein, the singular forms "one", "an" and "the" are also intended to include plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise", "comprising", "having", "having", "including" and / or "including" specify the presence of the features, elements and / or components described when used in this article, but do not exclude the presence or increase of one or more other features, elements, components and / or their combinations. As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar wording (wherein the list of two or more elements is combined by "and" or "or") mean at least any one of the elements, or at least any two or more of the elements, or at least all elements.

[0046] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuits); and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any portion of a hardware processor (including a digital signal processor) with software, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions; and (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate, but which may not be present when the software is not needed for operation.

[0047] This definition of circuitry applies to all uses of the term in this application, including any claims. As another example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit, or a processor (or multiple processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers (e.g., if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0048] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable generation communication protocol, including but not limited to the fourth generation (4G), 4.5G, future fifth generation (5G) communication protocol and / or any future 5G and later protocols. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communications, there will certainly be future types of communication technologies and systems that can embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to the aforementioned systems.

[0049] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from it. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a repeater, a low-power node (such as a femto, pico, etc.).

[0050] The term "terminal device" refers to any terminal device capable of wireless communication. As an 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 may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback facilities, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), 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 process chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0051] In Release 18, research on AI / ML for the NR air interface includes the use case of positioning accuracy enhancement, and the objectives of the Study Item (SI) are as follows:

[0052]

[0053] Lifecycle management of positioning / ML models often requires, among other things, periodic model updates, where the periodicity depends on either: 1. Inference frequency, that is, how often the model is used after deployment; 2. The type of UE using the model. This is because different UEs have different capabilities to collect data and / or update the model accordingly; 3. What localization task is the model solving, e.g., line of sight (LOS) detection, position estimation, etc. 4. The availability of training data, i.e., how much data can be collected, the diversity and frequency of the training data; or 5. Reliability of the training data, i.e., the training data well characterizes the conditions under which the ML model was trained.

[0054] While features 1-3 are intrinsic to the ML functionality and / or UE type and are therefore relatively easy to control, features 4-5 are extrinsic and generally depend on the propagation and interference conditions in which the UE finds itself.

[0055] Therefore, if only features 1-3 are considered when managing ML model updates, while features 4 and 5 are ignored, the ML model may be updated to learn a set of unique or rare channel conditions that poorly represent average, everyday conditions. In other words, training is performed based on abnormal scenarios rather than typical wireless conditions, resulting in an overall unrealistic model that does not generalize well. As a result, the ML model may forget how to handle average conditions and exhibit poor performance in most situations. This phenomenon is known as catastrophic forgetting and is one of the caveats of continuous learning / updating of ML features.

[0056] Exemplary rare conditions that may lead to catastrophic forgetting of the positioning ML functionality are associated with those situations in which the positioning link towards the TRP set is temporarily blocked or severely attenuated due to aberrations in the wireless channel. Most commonly, such aberrations occur due to very high velocities and / or the presence of structures that create a Faraday cage / shield around the positioning receiver or transmitter, such as: - Buildings covered in metal scaffolding during renovation, etc. - Large temporary structures associated with construction sites, outdoor concerts, road work, etc.

[0057] In the above scenario, the positioning measurements will not be a good representation of the reflector distribution for that set of TRPs relative to the UE's position, and therefore they can be considered rare events, i.e., those events that are considered abnormal radio conditions for positioning. However, some rare events may prove useful for ML functionality, while others may be completely detrimental.

[0058] Therefore, in order to further enhance positioning accuracy, the AI / ML model for positioning still needs to be further improved. The present disclosure addresses the problem of rare events when training ML models for positioning functions.

[0059] According to some embodiments of the present disclosure, a solution for positioning is provided. In this solution, a terminal device obtains rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare event indications are one or more events that are considered to be abnormal wireless conditions for positioning. In addition, the terminal device identifies rare events based on the one or more condition sets indicated by the rare event parameters. Thereafter, based on the identified rare events, the terminal device can perform appropriate operations, such as stopping ML or updating the ML model. Rare event identification can be used for lifecycle management of positioning, in particular AI / ML model management.

[0060] In this way, in embodiments of the present disclosure, the types of rare events can be identified. Furthermore, by correctly distinguishing between average conditions and rare events, the model can be robustly trained, optimized processing can be utilized to enhance positioning performance, and robustness against unforeseen circumstances that negatively impact ML performance can be enhanced. Consequently, positioning accuracy can be improved.

[0061] For the purpose of illustration, the following reference will be made to Figures 1 to 12 Example embodiments of the present disclosure are described for small data transmission.

[0062] Figure 1 An example network environment 100 is shown in which example embodiments of the present disclosure may be implemented. The environment 100 may be part of a communication network, including terminal devices, network devices, and the like. Figure 1As shown, communication network 100 may include terminal device 110 (hereinafter also referred to as first terminal device 110 or UE 110), terminal device 120 (hereinafter also referred to as second terminal device 120 or UE 120), and network device 130 (hereinafter also referred to as gNB 130). Network device 130 may manage cell 101. Network device 130, terminal device 110, and terminal device 120 may communicate with each other within the coverage area of ​​cell 101. The link from terminal device 110 or terminal device 120 to network device 130 is called an uplink (UL), and the link from network device 130 to terminal device 110 or terminal device 120 is called a downlink (DL).

[0063] It should be understood that the number of network devices and terminal devices is for illustrative purposes only and does not imply any limitation. System 100 may include any suitable number of network devices and terminal devices suitable for implementing the embodiments of the present disclosure. Although not shown, it should be understood that one or more terminal devices may be located in cell 101.

[0064] Communications in the communication system 100 may be implemented according to any suitable communication protocol, including but not limited to fourth generation (4G) and fifth generation (5G) and beyond 5G cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future. In addition, communications may utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology currently known or developed in the future.

[0065] exist Figure 1 In the embodiment of the present invention, the terminal device 110 may obtain a rare event parameter. The rare event parameter indicates one or more condition sets corresponding to one or more rare events, and the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning. The terminal device 110 may also identify the rare event based on the one or more condition sets indicated by the rare event parameter.

[0066] The rare event parameters may be received from the network device 130. The network device 130 may define or set the rare event parameters and send the rare event parameters to the terminal device 110.

[0067] The rare event parameters may also be received from another terminal device 120. The terminal device 120 may receive the rare event parameters from the network device 130. The terminal device 120 may then send the rare event parameters to the terminal device 110; and then receive a report associated with the identified rare event from the terminal device 110.

[0068] For illustrative purposes, Figure 2a and Figure 2b Two example signaling diagrams for different scenarios according to some embodiments of the present disclosure are shown, and the example signaling procedures as proposed herein will be described with reference to them.

[0069] Figure 2a A signaling diagram illustrating an example process 200-1 according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 The process 200-1 is described. The process 200-1 may involve the terminal device 110 and the network device 130. It should be understood that although Figure 1 The process 200-1 is described in the communication environment 100 of FIG. 1 , but the process can also be applied to other communication scenarios with similar problems.

[0070] In process 200-1, terminal device 110 receives 203 rare event parameters 202 from network device 130. In other words, rare event parameters 202 may be configured by network device 130 and thus sent 201 from network device 130. Alternatively, these rare event parameters 202 may also be predefined in a standard.

[0071] In some embodiments, the rare event parameters 202 may indicate one or more condition sets corresponding to one or more rare events, and the one or more rare events indicate that the one or more events are considered abnormal radio conditions for positioning.

[0072] In some embodiments, the one or more rare events may include a transient rare event (TRE) that occurs instantaneously, a periodic rare event (PRE) that occurs periodically, or any combination of two or more of the above items. The TRE can be skipped by the terminal device or the ML model. The terminal device 110 benefits from the PRE by updating the ML model to adapt to the PRE.

[0073] In some embodiments, the condition set corresponding to the TRE may include one or more of the following: - The Doppler shift is greater than a first threshold, and the delay variation of the line of sight LOS at two measurement time points is greater than a value, wherein the value is based on the Doppler shift, the carrier frequency and the measurement time interval between the two measurement time points. septate; - The probability that the LOS condition changes at two measurement time points within the coherence time is greater than a second threshold; or - The change in the received power of the reference signal at two measurement time points within the coherence time is greater than a third threshold.

[0074] For example, if any aberration occurs between two consecutive positioning measurements, then the LOS TRE can be identified. Such an aberration is identified when any one of the following conditions is satisfied, for example: 1. TRE condition set 1: a. The Doppler shift fd of the terminal device is greater than FD, where FD is a threshold defined by the Location Management Function (LMF), for example, FD = 150 Hz; and b. The delay D2 of the LOS path at the current time t2 follows the following rule regarding the delay D1 of the LOS path measured at the past time t1: |D2 - D1| > fd / fc * |t2 - t1|, where fc is the carrier frequency. 2. TRE condition set 2: a. The probability p2 of the LOS at the current time t2 follows the following rule regarding the LOS probability p1 measured at time t1: |p2 - p1| > E, where E is a threshold defined by the LMF, for example, E = 0.3; and b. |t2 - t1| < Tc, where Tc is the coherence time of the channel, for example, Tc ~ 1 / (4fd). 3. TRE condition set 3: a. |t2 - t1| < Tc, where Tc is the coherence time of the channel, for example, Tc ~ 1 / (4fd); b. |RSRP2 - RSRP1| > R, where RSRP2 is the received signal strength reference power (RSRP) collected at time t2, and R is a threshold selected by the LMF.

[0075] In some embodiments, the set of conditions corresponding to the PRE includes one or more of the following: - The change in the number of multipath components measured over a predetermined measurement interval is greater than a fourth threshold, and the change in the delay spread at two measurement time points is within a predetermined margin; - The power distribution (power profile) measured over a predetermined measurement interval follows a different attenuation pattern; or - Any combination of two or more of the above items.

[0076] For example, when the LOS distribution changes between, for example, urban, suburban, or rural distributions, the LOS PRE is identified. For example, if the following conditions are satisfied, the LOS PRE occurs: 1. PRE - condition set 1: a. the number of multipath components L2 measured at time t2 is a percentage "g" of the number of multipath components measured at time t1, where g is selected by the LMF, e.g., g=40%; and b. |t2-t1|>T, where T is a duration selected by the LMF, e.g., T=400ms; and c. the delay spread S2 measured at t2 is within a margin M from the delay spread S1 measured at t2, where M is selected by the LMF, e.g., M=+ / -3 microseconds. 2. Precondition set 2: a. The power profile P2 measured at time t2 follows a uniform or exponential decay, and the power profile P1 follows a different decay, ie exponential or uniform decay, respectively; and b. |t2-t1|>T, where T is the duration chosen by the LMF, eg T=400ms.

[0077] In some embodiments, the rare event parameter may be included within a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields respectively indicating one or more condition sets.

[0078] For example, a first IE may be defined as follows to assist with the proposed solution: Example LTE Positioning Protocol (LPP) ProvideAssistanceData IE

[0079] Return Reference Figure 2a , the terminal device 110 identifies 205 a rare event based on one or more sets of conditions indicated by the rare event parameters 202 .

[0080] In some embodiments, terminal device 110 may send 207 a report associated with identified rare event 204 to network device 130. After receiving 209 the report associated with identified rare event 204 from terminal device 110, network device 130 may obtain the rare event type.

[0081] In some embodiments, the report may include a start marker indicating the start of the rare event, an end marker indicating the end of the rare event, or any combination of two or more of the foregoing.

[0082] In some embodiments, the start flag for a TRE may include a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has satisfied. The start flag for a PRE may include an ID of the PRE indicating an ID of a set of conditions that the PRE has satisfied.

[0083] In some embodiments, the report may be included within a second IE in another RRC message, and the second IE includes a field indicating one or both of a start flag and an end flag.

[0084] For example, the second IE may be defined as follows to assist the proposed solution; ExampleLPP ProvideLocationInformation

[0085] In some embodiments, the terminal device 110 may obtain 211 an action configuration for one or more rare events. Based on the action configuration, the terminal device 110 may determine 213 an action corresponding to the identified rare event. In some embodiments, the terminal device 110 may apply 215 the action corresponding to the identified rare event.

[0086] In some embodiments, network device 130 may send 217 an action indication 206 corresponding to the identified rare event to terminal device 110. After receiving 219 the action indication 206, terminal device 110 may perform 221 an action corresponding to the identified rare event based on the action indication 206.

[0087] In some embodiments, the terminal device may send 223 a confirmation message 208 based on the determination that the action has been applied. The action may include updating the positioning model, deploying a new positioning model, or any combination of two or more of the above items. On the other side of the communication, the network device 130 may receive 225 the confirmation message 208 from the terminal device 110.

[0088] Figure 2b Another signaling diagram illustrating an example process 200-2 according to some embodiments of the present disclosure is shown. The example process 200-2 may be applicable to a scenario in which the terminal device 120 requests other terminal devices to perform rare event identification due to some reasons (eg, the terminal device does not have the capability for rare event identification).

[0089] For the purpose of this discussion, reference will be made to Figure 1 The process 200-2 is described. The process 200-2 may involve the terminal device 110, the terminal device 120 and the network device 130. It should be understood that although Figure 1 The process 200-2 is described in the communication environment 100 of FIG. 1 , but the process can also be applied to other communication scenarios with similar problems.

[0090] In process 200-2, network device 130 sends 227 rare event parameters 202 to terminal device 120. Rare event parameters 202 indicate one or more condition sets corresponding to one or more rare events, and the one or more rare events indicate one or more events considered as abnormal radio conditions for positioning.

[0091] After receiving 229 the rare event parameters 202 from the network device 130 , the terminal device 120 sends 231 the rare event parameters 202 to the terminal device 110 .

[0092] On the terminal device 110 side, the terminal device 110 receives 233 rare event parameters 202 from the terminal device 120. Based on one or more condition sets indicated by the rare event parameters 202, the terminal device 110 identifies 235 the rare event. The terminal device 110 may then send 237 a report associated with the identified rare event 210 to the terminal device 120. Thereafter, the terminal device 120 may receive 239 a report associated with the identified rare event 210 from the terminal device 110.

[0093] In some embodiments, terminal device 110 may send 241 an action indication 212 corresponding to the identified rare event to terminal device 120. In some embodiments, after receiving 243 the action indication 212 from terminal device 110, terminal device 120 may apply 245 an action corresponding to the identified rare event based on the action indication.

[0094] Process 200-2 and Figure 2a The difference from the process 200-1 in FIG is that the terminal device 120 can request the peer terminal device 110 to perform an operation related to positioning, and the terminal device 110 reports the identified rare event and sends an action to the terminal device 120. With respect to other operations and information communicated, the process 200-2 is similar to the process 200-1. Therefore, more details can be found in reference Figure 2a Description.

[0095] Figure 3 An example process 300 according to some embodiments of the present disclosure is shown. For discussion purposes, reference will be made to Figure 1 The process 300 is described. The process 300 may involve the terminal device 110 and the network device 130. It should be understood that although Figure 1 The process 300 is described in the communication environment 100 of FIG. 3 , but the process can also be applied to other communication scenarios with similar problems.

[0096] A framework for managing localization rare events that occur during ML-based localization tasks (both during training and inference) is proposed. In this context, localization rare events are related to situations where the localization link towards a set of TRPs is temporarily blocked or severely distorted due to aberrations in the wireless channel. Such aberrations can occur, for example, due to very high velocities or accelerations, or due to the presence of physical structures that create a Faraday cage around the localization transmitter and / or receiver.

[0097] like Figure 3 As shown, network device 130 may define 305 a positioning rare event identifier: for example, TRE condition set(s) and PRE condition set(s). Network device 130 may also define 310 a rare event management policy: actions to be applied during a TRE: A1, A2, etc.; actions to be applied during a PRE: Ak, Aj, etc. Network device 130 may then send 315 the positioning rare event identifier and the rare event management policy to the terminal device. For example, a new IE LTE Positioning Protocol (LPP) ProvideAssistanceData may be sent to terminal device 110. LPP ProvideAssistanceData may include, for example, TRE condition set(s) and PRE condition set(s), action(s) to be applied during a TRE, and action(s) to be applied during a TRE. By sending the new IE LPP ProvideAssistanceData, network device 130 may indicate the TRE / PRE condition set(s) to terminal device 110, request that terminal device 110 notify the occurrence of a TRE / PRE, and request that terminal device 110 apply the corresponding actions.

[0098] Based on the condition set indicated in the new IE LPP ProvideAssistanceData, the terminal device 110 may test for PRE or TRE 320. The terminal device 110 may then send 325 a rare event report, for example in a new UE LPP ProvideLocationInformation. The new UE LPP ProvideLocationInformation may include a TRE / PRE start flag and a TRE / PRE ID.

[0099] Afterwards, the terminal device 110 may apply 330 actions during the TRE / PRE. For example, the terminal device 110 may suspend model training, suspend ML-based positioning inference, update the ML-based positioning model, or (re)deploy the ML-based positioning model, etc. After the rare event ends, the terminal device 110 may send 335 another UE LPP ProvideLocationInformation. The new UE LPP ProvideLocationInformation includes a TRE / PRE end flag.

[0100] In an embodiment of the present disclosure, the current LPP protocol may be enhanced with the following new elements: ■ Define conditions to identify different types of positioning rare events related to ML positioning functions, where such functions are A) LOS detection, or B) position estimation. For example, rare events can be classified into the following types: a.Category #1: Transient Rare Events (TREs) are those channel aberrations that are unlikely to occur for the corresponding terminal device and for which the terminal device should not learn or employ an ML model, for example: i. Onboard terminal equipment does not benefit from using measurements collected at FR2 frequencies and very high speeds to update or use ML-based LOS detectors, as the reception of such signals is severely distorted by the aggressive Doppler effect. ii. End devices in a Faraday cage accidentally created by, for example, scaffolding wire mesh on the exterior of a building. Similarly, such end devices should avoid updating / using ML-based functions A) or B). b. Category #2 Periodic Rare Events (PRE) are those events that occur with large periodicity, but for which the end device can benefit from updating the ML model, e.g. an ML LOS detector for a large square during an open air concert. ■ Define actions or action policies to manage each type of rare event for the UE. For example, actions may include: a. For TRE, the collected measurements can be discarded, or the collection process can be stopped entirely. Furthermore, if the measurements are collected for training, they are not transmitted back to the NW. Conversely, if the measurements are collected for inference, inference is stopped. b. For PRE, a rare event ML model customized for the event can: i. is updated (i.e., refined during training using measurements collected during PRE), and / or ii. Deployed (if the model is currently in use). ■ Signaling to detect, communicate and manage the occurrence of each type of rare event. The UE can identify rare events autonomously (or with the help of the NW) and communicate this information to the NW or other UEs (directly via a sidelink or indirectly via the LMF).

[0101] Figure 4 Another example process according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 The process 400 is described. The process 400 may involve the terminal device 110 and the network device 130. It should be understood that although Figure 1 The process 400 is described in the communication environment 100 of FIG. 1 , but the process can also be applied to other communication scenarios with similar problems.

[0102] When the ML task is used for LOS detection, the proposed protocol is as follows Figure 4 In the example of using the prior art signaling ( Figure 4 (not shown) When receiving the terminal device capabilities at the network device 130 side, it is proposed that the network device 130 use a new IE as part of the LPP ProvideAssistanceData message to transmit the conditions for LOS TRE and LOS PRE.

[0103] like Figure 4 As shown, the network device 130 may define 405 TRE and PRE conditions. The terminal device 110 then receives the TRE and PRE conditions and performs 410 locating a rare event identifier. For example, after receiving the above conditions, the terminal device 110 may measure the PRS and test whether any condition or set of conditions is met.

[0104] In the case of TRE identification (Cat#1), after identifying TRE based on the TRE condition or condition set, the terminal device 110 may send 415 a message to the network device 130 marking the start of TRE and suspend 420 measurement collection. For example, the message may include: TRE binary flag: 1 = TRE event detected; and / or TRE ID, for example ID: 1 = TRE condition set 1 detected.

[0105] On the network device side, the network device 130 may pause 425 the ML LOS detection training or inference.After the TRE ends, the terminal device 110 may send 430 a message to the network device 130 marking the end of the TRE.

[0106] For example, the message may be a new IE in the LPP ProvideLocationInformation signaling. The TRE flag indicates positioning error, so the terminal device 110 stops the measurement collection process and the network device 130 stops updating or using the model. Once the TRE event ends, the terminal device 110 sends a corresponding flag to the network device 130.

[0107] In the case of PRE identification (Cat#2), after identifying the PRE based on the TRE condition or condition set, the terminal device 110 can send 435 a message to the network device 130 marking the start of the PRE. The network device 130 then provides 440 an updated ML LOS detector customized for the PREID, for example, the deep neural network (DNN) weights of the activation functions of each hidden node in each layer. Alternatively, the network device 130 can indicate to the terminal device 110 that a model update is required, and the terminal device 110 can perform its own training locally or in the cloud. The terminal device 110 can then deploy and run the updated ML LOS detector. In an option, the terminal device 110 can send 450 a confirmation message indicating that the model has been updated. At the end of the PRE, the terminal device 110 sends 430 a message to the network device 130 marking the end of the PRE.

[0108] For example, if a PRE event is identified, terminal device 110 indicates the event ID to network device 130, e.g., PREID: 1, meaning PRE condition set 1 was detected. This can be accomplished by sending a new message in the figure. Such a message can similarly be carried by a new IE in LPP ProvideLocationInformation. Network device 130 then transmits an ML-based LOS detector customized for the identified PRE condition to terminal device 110. Terminal device 110 can then apply the model and optionally confirm the change. The model change persists as long as the PRE condition is met. When the PRE condition is no longer met, terminal device 110 can send a message notifying network device 130 that the condition no longer applies. Terminal device 110 can then revert to the old model (i.e., the model used before the PRE condition was identified) or await further instructions from network device 130.

[0109] Figure 5 Another example process according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 The process 500 is described. The process 500 may involve the terminal device 110 and the network device 130. It should be understood that although Figure 1 The process 500 is described in the communication environment 100 of FIG. 5 , but the process can also be applied to other communication scenarios with similar problems.

[0110] like Figure 5 As shown, network device 130 provides 505 the TRE ID and PRE ID, as well as the conditions that led to each TRE / PRE, to terminal device 110. Terminal device 110 then performs 510 rare event identification. In the case of TRE identification (Cat#1), after the TRE is identified, terminal device 110 may send 515 a message to network device 130 marking the start of the TRE. Terminal device 110 may then ignore 520 the training data or positioning measurements. On the other side of the communication, upon detecting the end of the TRE, network device 130 may send 525 a message to terminal device 110 marking the end of the TRE.

[0111] In the case of PRE identification (Cat#2), after identifying the PRE, the terminal device 110 may provide 530 the identified PRE ID to the network device 130. The network device 130 may then provide 535 an updated ML model customized for the PRE ID. The terminal device 110 may then apply 540 the new ML model. The terminal device 110 may send 545 an acknowledgement message indicating that the model has been updated. After detecting the end of the PRE, the terminal device 110 may send 550 a message marking the end of the PRE to the network device 130. Simultaneously, after the PRE ends, the terminal device 110 may revert 555 to the previous ML detector, i.e., the model used before the PRE was identified.

[0112] exist Figure 5 In the example of FIG, terminal device 110 receives auxiliary information identifying the type of rare event, but terminal device 110 autonomously manages the occurrence of the rare event. Specifically, the process begins with network device 130 indicating to terminal device 110 a set of PREs and TRE IDs, as well as auxiliary information on how each PRE and TRE is defined (i.e., "the conditions that led to each PRE and TRE ID"). Terminal device 110 then measures the DL PRS and, optionally / additionally, other RSs, and identifies the type or rare event.

[0113] If TRE is identified, the terminal device 110 marks the TRE ID and sends it to the network device 130, and stops the PRS measurement process until the network device 130 notifies the end of TRE. Alternatively, the terminal device 110 can identify the end of TRE by itself (in which case 525 becomes optional).

[0114] When a PRE is identified, terminal device 110 notifies network device 130 of the ID and obtains a new ML model customized for the corresponding PREID from network device 130. Terminal device 110 applies the model and optionally confirms the model usage to network device 130. After the PRE terminates, terminal device 110 may mark the end of the PRE and send it to network device 130. Finally, terminal device 110 reverts to the previous ML model.

[0115] For illustration purposes, an example of how to determine and handle “conditions leading to rare events” (specific to the UE ML functionality) is described below. These are radio and non-radio UE conditions that are localized in time and space relative to the serving cell or beam, as defined by the network, such as: - Sudden / rapid changes in UE Reference Signal Received Power (RSRP) level above / below a threshold for a specific time window or within a specific geographical area. - Sudden changes in UE speed (or mobility state) for a specific time window or within a specific geographical area.

[0116] Conditions defined by the network (e.g., via an analytics function) may include: -TRE: Each event ID has been defined, for example, based on reports from some UEs, but does not fit the pattern of any known PRE for the same time-space location. An event is initially declared as a TRE, and other UEs in the same time-space location are configured with corresponding conditions. In the event of regular detection of the same TRE, the event can be declared as a PRE for any subsequent use. -PRE: The event has been detected and identified as fitting the pattern of any known PRE for the same frequency-time-space location. PRE conditions need to be periodically checked and analyzed to verify that they remain PRE, otherwise the event is declared TRE for any subsequent use. - The network may decide to declare a TRE as a PRE, or the UE may decide to report a previously indicated TRE as PRE.

[0117] Each event (and associated condition) is assigned an ID to uniquely identify it in the analysis functions that process it (estimation, verification). The TRE ID can be a temporary ID and is used on the network side. The network stores the IDs for all estimated PREs and provides the relevant subset of PRE IDs to the UE based on the time-space location. - When detecting an existing but previously undetected PRE in the same time-space location, the UE receives a new PRE ID. - When a brand new PRE is detected, its ID and conditions need to be signaled to the UE. - TRE ID and conditions need to be signaled to the UE.

[0118] Figure 6 Another example process 600 according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 The process 600 is described. The process 600 may involve the terminal device 110 and the network device 130. It should be understood that although Figure 1 The process 600 is described in the communication environment 100 of FIG. 1 , but the process can also be applied to other communication scenarios with similar problems.

[0119] Different from Figure 5 , the action to be applied can be indicated by the network device. Figure 6 As shown, the network device 130 may provide 605 the TRE and PRE IDs and the conditions that led to each TRE / PRE to the terminal device 110. The terminal device 110 may then perform 610 rare event identification based on the conditions provided by the network device.

[0120] In the case of TRE identification (Cat#1), after identifying the TRE, the terminal device 110 sends 615 a message marking the start of the TRE to the network device 130. The network device 130 may then instruct 620 the terminal device 110 to take an action, such as stop measuring, which is similar to Figure 5 Different, in Figure 5 The terminal device 110 applies the action autonomously. After receiving the action indication, the terminal device 110 applies the action. At the end of the TRE, the terminal device 110 sends 630 a message to the network device 130 marking the end of the TRE.

[0121] In the case of a PRE identification (Cat#2), after identifying the PRE, the terminal device 110 provides 635 the identified PRD ID to the network device 130. The network device 130 may instruct 640 an action to the terminal device 110, such as switching to an ML model for the identified PRD ID, and the terminal device 110 then applies 645 the new ML model indicated by the network, rather than autonomously applying the new ML model. At the end of the PRE, the terminal device 110 may send 650 a message to the network device 130 marking the end of the PRE. After the PRE ends, the terminal device 110 reverts 655 to the previous ML detector.

[0122] exist Figure 6 In the embodiment, the terminal device 110 identifies the type of event, i.e., TRE or PRE, and notifies the network device 130 of its occurrence. However, it is up to the network device 130 to trigger the action of managing the event, for example: - Action (in 620) = Stop UE measurements until the TRE event is over. - Action (in 640) = Switch to the ML model tuned for the reported PRE ID.

[0123] Figure 7 Another example process according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 The process 700 is described. The process 700 may involve the terminal device 110, the terminal device 120 and the network device 130. It should be understood that although Figure 1 The process 400 is described in the communication environment 100 of FIG. 1 , but the process can also be applied to other communication scenarios with similar problems.

[0124] and Figures 3 to 6 Unlike the process of locating a location, the terminal device 120 may request the peer terminal device 110 to perform operations related to positioning. For example, the terminal device 120 may be a lower-capability device. A report on the identified rare event and / or the action to be applied may be provided from the terminal device 120.

[0125] Specifically, if Figure 7 As shown, network device 130 may provide 705 the TRE ID and PRE ID and the conditions that led to each TRE / PRE to terminal device 120, which may then provide this information to a peer device, namely terminal device 110. Terminal device 110 may then perform 710 rare event identification accordingly.

[0126] In the case of a TRE identification (Cat#1), after identifying the TRE, terminal device 110 may send 715 a message to terminal device 120 marking the start of the TRE. Terminal device 120 may then also indicate 720 an action corresponding to the identified rare event to terminal device 110, such as stopping measurement. After receiving the action indication, terminal device 120 may apply 725 the action indicated by network device 110. At the end of the TRE, terminal device 110 sends 730 a message to terminal device 120 marking the end of the TRE.

[0127] In the case of PRE identification (Cat#2), after identifying the PRE, the terminal device 110 may provide 735 the identified PRE ID to the network device 130. The terminal device 110 may then instruct 740 the terminal device 120 an action, such as switching to an ML model for the identified PRD ID. The terminal device 120 may then apply 745 the new ML model indicated by the network device 110. At the end of the PRE, the terminal device 110 may also send 750 a message to the terminal device 120 marking the end of the PRE. After receiving the message, the terminal device 120 may revert 755 to the previous ML detector.

[0128] exist Figure 7 In an embodiment, the proposed protocol can be applied to sidelink (SL) positioning. Specifically, a first UE (e.g., terminal device 110 in the figure) identifies a rare event type (e.g., Cat#1, Cat#2) and notifies a peer UE (e.g., terminal device 120 in the figure) of the following two: - Event type (Cat#1-TRE, Cat#2-PRE) and its start; - suggest the best action to be taken by the peer UE; -The incident ends.

[0129] Therefore, in embodiments of the present disclosure, the type of rare event can be identified by the terminal device. Furthermore, by correctly distinguishing between average conditions and rare events, the model can be robustly trained, optimizing processing to enhance positioning performance, and enhancing robustness against unforeseen circumstances that negatively impact ML performance. This improves positioning accuracy.

[0130] Figure 8 FIG. 8 is a flow chart illustrating an example method 800 implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to FIG. Figure 1 The method 800 is described from the perspective of the terminal device 110 .

[0131] At block 810 , the terminal device 110 obtains rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

[0132] In some embodiments, the one or more rare events may include: a transient TRE, a periodic PRE, or any combination of two or more of the above. The TRE is skipped by the terminal device or the ML model. The terminal device benefits from the PRE and updates the ML model to adapt to the PRE.

[0133] In some embodiments, the condition set corresponding to TRE may include: the Doppler shift is greater than a first threshold, and the delay change of LOS at two measurement time points is greater than a value, where the value is determined based on the Doppler shift, the carrier frequency and the measurement time interval between the two measurement time points; the probability of the LOS condition at the two measurement time points within the coherence time changing is greater than a second threshold; the reference signal received power change at the two measurement time points within the coherence time is greater than a third threshold; or any combination of two or more of the above items.

[0134] In some embodiments, the condition set corresponding to PRE may include: the change in the number of multipath components measured over a predetermined measurement interval is greater than a fourth threshold, and the delay spread change at two measurement time points is within a predetermined margin; the power distribution measured over a predetermined measurement interval follows a different attenuation mode; or any combination of two or more of the above items.

[0135] In some embodiments, the rare event parameter is included within a first information element (IE) in a radio resource control (RRC) message.The first IE may include one or more fields that respectively indicate one or more condition sets.

[0136] At block 820 , the terminal device 110 identifies a rare event based on one or more sets of conditions indicated by the rare event parameters.

[0137] In some embodiments, the terminal device 110 may also apply an action corresponding to the identified rare event.

[0138] In some embodiments, the action corresponding to the identified rare event may include: discarding the collected measurements; pausing the collection process; updating the positioning model; deploying a new positioning model; or any combination of two or more of the above.

[0139] In some embodiments, the terminal device 110 may obtain an action configuration for one or more rare events. Based on the action configuration, the terminal device 110 may determine an action corresponding to the identified rare event.

[0140] In some embodiments, based on the determination that the action has been applied, the terminal device 110 may send a confirmation message. The action may include: updating the positioning model; or deploying a new positioning model; or any combination of two or more of the above items.

[0141] In some embodiments, the terminal device 110 may receive an action instruction corresponding to the identified rare event from the network device, and then the terminal device 110 performs an action corresponding to the identified rare event based on the action instruction.

[0142] In some embodiments, the terminal device 110 may send a report associated with the identified rare event. In some embodiments, the report may include: a start flag indicating the start of the rare event; an end flag indicating the end of the rare event; or any combination of two or more of the above items.

[0143] In some embodiments, the start flag for a TRE may include a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has satisfied. The start flag for a PRE may include an ID of the PRE indicating an ID of a set of conditions that the PRE has satisfied.

[0144] In some embodiments, the report may be included in a second IE in another RRC message.The second IE may include a field indicating one or both of a start flag and an end flag.

[0145] Figure 9 FIG. 9 is a flow chart illustrating an example method 900 implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to FIG. Figure 1 The method 900 is described from the perspective of the terminal device 120 .

[0146] At block 910 , the terminal device 120 receives rare event parameters from the network device 130 , wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning.

[0147] In some embodiments, the one or more rare events may include: a transient TRE, a periodic PRE, or any combination of two or more of the above. The TRE is skipped by the terminal device or the ML model. The terminal device 110 benefits from the PRE and updates the ML model to adapt to the PRE.

[0148] In some embodiments, the condition set corresponding to TRE may include one or more of the following: the Doppler frequency shift is greater than a first threshold, and the delay change of LOS at two measurement time points is greater than a value, where the value is determined based on the Doppler frequency shift, the carrier frequency and the measurement time interval between the two measurement time points; the probability that the LOS condition at the two measurement time points within the coherence time changes is greater than a second threshold; the reference signal received power change at the two measurement time points within the coherence time is greater than a third threshold; or any combination of two or more of the above items.

[0149] In some embodiments, the condition set corresponding to PRE may include: the change in the number of multipath components measured beyond a predetermined measurement interval is greater than a fourth threshold, and the delay spread change at the two measurement time points is within a margin; the power distribution measured beyond a predetermined measurement interval follows a different attenuation mode; or any combination of two or more of the above items.

[0150] In some embodiments, the rare event parameter is received within a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields that respectively indicate one or more condition sets.

[0151] At block 920 , the terminal device 120 sends the rare event parameters to another terminal device.

[0152] At block 930 , terminal device 120 receives a report from terminal device 110 associated with the identified rare event.

[0153] In some embodiments, terminal device 120 may receive an action indication corresponding to the identified rare event from terminal device 110. Terminal device 120 may then apply an action corresponding to the identified rare event based on the action indication.

[0154] In some embodiments, the action corresponding to the identified rare event may include: discarding the collected measurements; pausing the collection process; updating the positioning model; deploying a new positioning model; or any combination of two or more of the above.

[0155] In some embodiments, the report can include: a start marker indicating the start of the rare event; an end marker indicating the end of the rare event; or any combination of two or more of the above.

[0156] In some embodiments, the start flag for a TRE may include a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has satisfied. The start flag for a PRE may include an ID of the PRE indicating an ID of a set of conditions that the PRE has satisfied.

[0157] Figure 10 FIG. 1 is a flow chart illustrating an example method 1000 implemented at a network device according to some embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1 Method 1000 is described from the perspective of network device 130 .

[0158] At block 1010, the network device 130 sends rare event parameters to the terminal device. The rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

[0159] In some embodiments, the one or more rare events may include: a transient TRE, a periodic PRE, or any combination of two or more of the above. The TRE is skipped by the terminal device or the ML model. The terminal device benefits from the PRE and updates the ML model to adapt to the PRE.

[0160] In some embodiments, the rare event parameter may be included within a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields respectively indicating one or more condition sets.

[0161] In some embodiments, network device 130 may receive a report associated with the identified rare event from the terminal device. In some embodiments, network device 130 may send an action indication corresponding to the identified rare event to the terminal device.

[0162] In some embodiments, the report can include: a start marker indicating the start of the rare event; an end marker indicating the end of the rare event; or any combination of two or more of the above.

[0163] In some embodiments, the start flag for a TRE may include a binary flag indicating that the TRE is identified and the ID of the TRE indicating the set of conditions that the TRE has satisfied. The start flag for a PRE may include the ID of the PRE indicating the ID of the set of conditions that the PRE has satisfied.

[0164] In some embodiments, the report may be included in a second IE in another RRC message, and the second IE may include a field indicating one or both of a start flag and an end flag.

[0165] In some embodiments, a device (e.g., terminal device 110) capable of performing any of the steps of method 800 is provided. The device may include components for performing the corresponding steps of method 800. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0166] In some embodiments, the apparatus includes: means for obtaining rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; and means for identifying the rare events based on the one or more condition sets indicated by the rare event parameters.

[0167] In some embodiments, the one or more rare events may include one or both of the following: a transient rare event (TRE) that occurs instantaneously, where the TRE is skipped for learning by the terminal device or a machine learning (ML) model; or a periodic rare event (PRE) that occurs periodically, whereby the terminal device benefits from updating the ML model to adapt to the PRE.

[0168] In some embodiments, the condition set corresponding to TRE may include one or more of the following: the Doppler shift is greater than a first threshold, and the delay change of LOS at two measurement time points is greater than a value, where the value is determined based on the Doppler shift, the carrier frequency and the measurement time interval between the two measurement time points; the probability that the LOS condition at two measurement time points within the coherence time changes is greater than a second threshold; or the reference signal received power change at two measurement time points within the coherence time is greater than a third threshold.

[0169] In some embodiments, the condition set corresponding to PRE may include one or both of the following: the change in the number of multipath components measured over a predetermined measurement interval is greater than a fourth threshold, and the delay spread change at two measurement time points is within a predetermined margin; or - the power distribution measured over a predetermined measurement interval follows a different attenuation pattern.

[0170] In some embodiments, the rare event parameter may be included within a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields respectively indicating one or more condition sets.

[0171] In some embodiments, the apparatus may further include means for applying an action corresponding to the identified rare event.

[0172] In some embodiments, the action corresponding to the identified rare event may include one or more of: discarding the collected measurements; pausing the collection process; updating the positioning model; or deploying a new positioning model.

[0173] In some embodiments, the apparatus may further include: a component for obtaining an action configuration for one or more rare events; and a component for determining an action corresponding to the identified rare event based on the action configuration.

[0174] In some embodiments, the apparatus may further comprise means for sending a confirmation message based on a determination that an action has been applied, wherein the action comprises one or both of: updating the positioning model; or deploying a new positioning model.

[0175] In some embodiments, the apparatus may further include: means for receiving an action indication corresponding to the identified rare event from the network device; and means for performing an action corresponding to the identified rare event based on the action indication.

[0176] In some embodiments, the apparatus may further include means for transmitting a report associated with the identified rare event.

[0177] In some embodiments, the report may include one or both of: a start marker indicating the start of the rare event; or an end marker indicating the end of the rare event.

[0178] In some embodiments, the start flag for a TRE includes a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has satisfied; and / or the start flag for a PRE includes an ID of the PRE indicating an ID of a set of conditions that the PRE has satisfied.

[0179] In some embodiments, the report is included in a second IE in another RRC message, and the second IE includes a field indicating one or both of a start flag and an end flag.

[0180] In some embodiments, the apparatus further comprises means for performing other steps of some embodiments of method 800. In some embodiments, the means comprises at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause execution of the apparatus.

[0181] In some embodiments, a device (e.g., terminal device 120) capable of performing any of the steps of method 900 is provided. The device may include components for performing the corresponding steps of method 900. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0182] In some embodiments, the apparatus includes: means for receiving rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; means for sending the rare event parameters to another terminal device; and means for receiving a report associated with the identified rare event from the other terminal device.

[0183] In some embodiments, the one or more rare events may include one or both of the following: a transient rare event (TRE) that occurs instantaneously, where the TRE is skipped and learned by the terminal device or the machine learning (ML) model; or a periodic rare event (PRE) that occurs periodically, whereby another terminal device benefits from updating the ML model to adapt to the PRE.

[0184] In some embodiments, the condition set corresponding to TRE may include one or more of the following: the Doppler shift is greater than a first threshold, and the delay change of LOS at two measurement time points is greater than a value, where the value is determined based on the Doppler shift, the carrier frequency and the measurement time interval between the two measurement time points; the probability that the LOS condition at two measurement time points within the coherence time changes is greater than a second threshold; or the reference signal received power change at two measurement time points within the coherence time is greater than a third threshold.

[0185] In some embodiments, the condition set corresponding to PRE includes one or both of the following: the change in the number of multipath components measured over a predetermined measurement interval is greater than a fourth threshold, and the delay spread change at the two measurement time points is within a margin; or the power distribution measured over a predetermined measurement interval follows a different attenuation mode.

[0186] In some embodiments, the rare event parameter is received within a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields that respectively indicate one or more condition sets.

[0187] In some embodiments, the apparatus may further include: means for receiving an action indication corresponding to the identified rare event from another terminal device; and means for applying an action corresponding to the identified rare event based on the action indication.

[0188] In some embodiments, the action corresponding to the identified rare event may include one or more of: discarding the collected measurements; pausing the collection process; updating the positioning model; or deploying a new positioning model.

[0189] In some embodiments, the report may include one or both of: a start marker indicating the start of the rare event; or an end marker indicating the end of the rare event.

[0190] In some embodiments, the start flag for a TRE may include a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has met; and / or the start flag for a PRE may include an ID of the PRE indicating an ID of a set of conditions that the PRE has met.

[0191] In some embodiments, the apparatus further comprises means for performing other steps of some embodiments of method 900. In some embodiments, the means comprises at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause execution of the apparatus.

[0192] In some embodiments, a device (e.g., network device 130) is provided that can perform any of the steps of method 1000. The device may include components for performing the corresponding steps of method 1000. The components may be implemented in any suitable form. For example, the components may be implemented in circuits or software modules.

[0193] In some embodiments, the apparatus comprises means for sending rare event parameters to a terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning.

[0194] In some embodiments, the one or more rare events may include one or both of the following: a transient rare event TRE that occurs instantaneously, where the TRE is skipped and learned by the terminal device or the machine learning ML model; or a periodic rare event PRE that occurs periodically, through which the terminal device benefits from updating the ML model to adapt to the PRE.

[0195] In some embodiments, the rare event parameter may be included within a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields respectively indicating one or more condition sets.

[0196] In some embodiments, the apparatus may further include means for receiving a report associated with the identified rare event from a terminal device.

[0197] In some embodiments, the apparatus further comprises: means for sending an action indication corresponding to the identified rare event to a terminal device.

[0198] In some embodiments, the report may include one or both of: a start marker indicating the start of the rare event; or an end marker indicating the end of the rare event.

[0199] In some embodiments, the start flag for a TRE includes a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has satisfied; and / or the start flag for a PRE includes an ID of the PRE indicating an ID of a set of conditions that the PRE has satisfied.

[0200] In some embodiments, the report may be included within a second IE in another RRC message, and the second IE includes a field indicating one or both of a start flag and an end flag.

[0201] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 1000. In some embodiments, the means comprise: at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause execution of the apparatus.

[0202] Figure 11 is a simplified block diagram of a device 1100 suitable for implementing embodiments of the present disclosure. The device 1100 may be configured to implement a communication device, such as Figure 1 The terminal device 110, the terminal device 120 or the network device 130 is shown. As shown, the device 1100 includes one or more processors 1110, one or more memories 1120 can be coupled to the processor 1110, and one or more communication modules 1140 can be coupled to the processor 1110.

[0203] The communication module 1140 is used for two-way communication. The communication module 1140 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary to communicate with other network elements. The communication module 1140 may be a soft interface or a hard interface for communicating with other modules. For example, the communication interface may be one or more transceivers. One or more transceivers may be coupled to one or more antennas or antenna ports to wirelessly send and / or receive communication signals. The antennas or antenna ports may be of the same or different types. The antennas or antenna ports may be located at different locations on the device. One or more transceivers allow the device to communicate with other devices by wire or wirelessly. The transceiver may support one or more radio technologies. For example, one or more transceivers may include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth subsystem. TMSubsystem. One or more transceivers may include a processor, controller, radio, jack, plug, buffer, and other circuitry to form one or more communication channels to one or more radio frequency units.

[0204] As non-limiting examples, the processor 1110 can be of any type suitable for the local technology network and can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1100 can have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock of a synchronized main processor.

[0205] Memory 1120 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) 1124, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1122 and other volatile memories that will not persist during a power outage.

[0206] Computer program 1130 includes computer-executable instructions executed by associated processor 1110. Program 1130 may be stored in ROM 1020. Processor 1110 may perform any suitable actions and processes by loading program 1130 into RAM 1120.

[0207] The embodiments of the present disclosure can be implemented with the aid of the program 1130, so that the device 1100 can execute the operations described in FIG. Figure 10 Any process of the present disclosure discussed. The embodiments of the present disclosure can also be implemented by hardware or a combination of software and hardware.

[0208] In some embodiments, the program 1130 may be tangibly embodied in a computer-readable medium that may be included in the device 1100 (such as in the memory 1120) or in another storage device accessible to the device 1100. The device 1100 may load the program 1130 from the computer-readable medium into the RAM 1122 for execution. The computer-readable medium may include any type of tangible, non-volatile storage device, such as a ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 12 An example of a computer readable medium 1200 in the form of a CD or DVD is shown. The computer readable medium has a program 1130 stored thereon.

[0209] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0210] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as those included in program modules, that are executed in a device on a target physical or virtual processor to perform the operations described above with reference to Figures 8 to 10 Methods 800, 900, and 1000 are described. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. Machine-executable instructions for program modules can be executed on local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0211] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the function / operation specified in the flow chart and / or block diagram to be realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0212] In the context of the present disclosure, computer program codes 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.

[0213] The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. As used herein, the term "non-transient" is a limitation of the medium itself (i.e., tangible, rather than a signal), rather than a limitation on data storage persistence (e.g., RAM versus ROM).

[0214] In addition, although the operation is described in a specific order, this should not be understood as requiring the specific order shown or to perform such operation in a sequential order, or to perform all operations shown 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 above discussion, these should not be interpreted as limiting the scope of the present disclosure, but should be interpreted as describing the features that can be specific to a particular embodiment. Some features described in the context of a separate embodiment also can be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment also can be realized in multiple embodiments individually or in any suitable subcombination.

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

Claims

1. A terminal device, comprising: one or more transceivers; as well as One or more processors coupled to the one or more transceivers, wherein the one or more transceivers are configured to, together with the one or more processors, cause the terminal device to: obtaining rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning; as well as Rare events are identified based on the one or more sets of conditions indicated by the rare event parameters.

2. The terminal device according to claim 1, wherein the one or more rare events include one or both of the following: A transient rare event (TRE) that occurs instantaneously, wherein the TRE is skipped from being learned by the terminal device or the machine learning (ML) model; or A periodic rare event PRE occurs periodically, through which the terminal device benefits from updating the ML model to adapt to the PRE.

3. The terminal device according to claim 2, wherein the condition set corresponding to the TRE comprises one or more of the following: - a Doppler shift is greater than a first threshold, and a delay variation of the line of sight LOS at two measurement time points is greater than a value, wherein the value is determined based on the Doppler shift, the carrier frequency, and the measurement time interval between the two measurement time points; - the probability that the LOS condition at two measurement time points changes within the coherence time is greater than a second threshold; or - A change in the reference signal received power at two measurement time points within the coherence time is greater than a third threshold.

4. The terminal device according to claim 2 or 3, wherein the condition set corresponding to the PRE comprises one or both of the following: - a change in the number of multipath components measured over a predetermined measurement interval is greater than a fourth threshold, and a change in the delay spread at the two measurement time points is within a predetermined margin; or - The power distribution measured over a predetermined measurement interval follows a different decay pattern.

5. The terminal device according to any one of claims 1 to 4, wherein the rare event parameter is included in a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields respectively indicating the one or more condition sets.

6. The terminal device according to any one of claims 1 to 5, wherein the terminal device is further caused to: An action corresponding to the identified rare event is applied.

7. The first terminal device according to claim 6, wherein the action corresponding to the identified rare event comprises one or more of the following: discard the collected measurements; Pause the collection process; Update the positioning model; or Deploy a new positioning model.

8. The terminal device according to any one of claims 6 to 7, wherein the terminal device is further caused to: obtaining an action configuration for the one or more rare events; Based on the action configuration, the action corresponding to the identified rare event is determined.

9. The terminal device according to any one of claims 6 to 8, wherein the terminal device is further caused to: Sending a confirmation message based on a determination that the action has been applied, wherein the action includes one or both of: Update the positioning model; or Deploy a new positioning model.

10. The terminal device according to claim 6 or 7, wherein the terminal device is further caused to: receiving, from a network device, an action indication corresponding to the identified rare event; and An action corresponding to the identified rare event is performed based on the action indication.

11. The terminal device according to any one of claims 1 to 10, wherein the terminal device is caused to: A report associated with the identified rare event is sent.

12. The terminal device according to claim 11, wherein the report includes one or both of the following: a start marker indicating the start of the rare event; or An end flag indicating the end of the rare event.

13. The terminal device according to claim 12, wherein the start flag for a TRE comprises a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has satisfied; and / or The start flag for a PRE includes an ID of the PRE indicating the ID of the condition set for which the PRE has been satisfied.

14. The terminal device according to any one of claims 10 to 13, wherein the report is included in a second IE in another RRC message, and the second IE includes a field indicating one or both of the start flag and the end flag.

15. A terminal device comprising: one or more transceivers; as well as One or more processors coupled to the one or more transceivers, wherein the one or more transceivers are configured to, together with the one or more processors, cause the terminal device to: receiving rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; Sending the rare event parameter to another terminal device; as well as A report associated with the identified rare event is received from the other terminal device.

16. The terminal device according to claim 15, wherein the one or more rare events include one or both of the following: A transient rare event (TRE) that occurs instantaneously, wherein the TRE is skipped from being learned by the terminal device or the machine learning (ML) model; or A periodic rare event PRE occurs periodically, through which the other terminal device benefits from updating the ML model to adapt to the PRE.

17. The terminal device according to claim 16, wherein the condition set corresponding to the TRE comprises one or more of the following: - a Doppler shift is greater than a first threshold, and a delay variation of the line of sight LOS at two measurement time points is greater than a value, wherein the value is determined based on the Doppler shift, the carrier frequency, and the measurement time interval between the two measurement time points; - the probability that the LOS condition at two measurement time points changes within the coherence time is greater than a second threshold; or - A change in the reference signal received power at two measurement time points within the coherence time is greater than a third threshold.

18. The terminal device according to claim 16 or 17, wherein the condition set corresponding to the PRE comprises one or both of the following: - a change in the number of multipath components measured over a predetermined measurement interval is greater than a fourth threshold, and a change in the delay spread at the two measurement time points is within a margin; or - The power distribution measured over a predetermined measurement interval follows a different decay pattern.

19. The terminal device according to any one of claims 15 to 18, wherein the rare event parameter is received within a first information element (IE) in a radio resource control (RRC) message, and the first IE comprises one or more fields respectively indicating the one or more condition sets.

20. The terminal device according to any one of claims 15 to 19, wherein the terminal device is further caused to: receiving, from the other terminal device, an action instruction corresponding to the identified rare event; and An action corresponding to the identified rare event is applied based on the action indication.

21. The terminal device according to claim 20, wherein the action corresponding to the identified rare event comprises one or more of the following: discard the collected measurements; Pause the collection process; Update the positioning model; or Deploy a new positioning model.

22. The terminal device according to claim 15, wherein the report includes one or both of the following: a start marker indicating the start of the rare event; or An end flag indicating the end of the rare event.

23. The terminal device according to claim 22, wherein the start flag for a TRE comprises a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that the TRE has satisfied; and / or The start flag for a PRE includes an ID of the PRE indicating the ID of the condition set for which the PRE has been satisfied.

24. A network device comprising: one or more transceivers; as well as one or more processors coupled to the one or more transceivers, wherein the one or more transceivers are configured to, together with the one or more processors, cause the network device to: Rare event parameters are sent to the terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

25. The network device of claim 24, wherein the one or more rare events include one or both of the following: A transient rare event (TRE) that occurs instantaneously, wherein the TRE is skipped from being learned by the terminal device or the machine learning (ML) model; or A periodic rare event PRE occurs periodically, through which the terminal device benefits from updating the ML model to adapt to the PRE.

26. The network device according to claim 24 or 25, wherein the rare event parameter is included in a first information element (IE) in a radio resource control (RRC) message, and the first IE includes one or more fields respectively indicating the one or more condition sets.

27. The network device according to any one of claims 24 to 26, wherein the network device is further caused to: A report associated with the identified rare event is received from the terminal device.

28. The network device of claim 27, wherein the network device is further caused to: An action instruction corresponding to the identified rare event is sent to the terminal device.

29. The network device according to claim 27 or 28, wherein the report includes one or both of the following: a start marker indicating the start of the rare event; or An end flag indicating the end of the rare event.

30. The network device of claim 29, wherein the start flag for a TRE comprises a binary flag indicating that the TRE is identified and an identification (ID) of the TRE indicating a set of conditions that have been met for the TRE; and / or The start flag for a PRE includes an ID of the PRE indicating the ID of the condition set for which the PRE has been satisfied.

31. The network device according to any one of claims 24 to 30, wherein the report is included in a second IE in another RRC message, and the second IE includes a field indicating one or both of the start flag and the end flag.

32. A method at a terminal device, comprising: obtaining rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning; as well as Rare events are identified based on the one or more sets of conditions indicated by the rare event parameters.

33. A method at a terminal device, comprising: receiving rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; Sending the rare event parameter to another terminal device; as well as A report associated with the identified rare event is received from the other terminal device.

34. A method at a network device, comprising: Rare event parameters are sent to the terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

35. A terminal device, comprising: means for obtaining rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; as well as Means for identifying a rare event based on the one or more sets of conditions indicated by the rare event parameters.

36. A terminal device comprising: means for receiving rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; means for sending said rare event parameter to another terminal device; as well as Means for receiving a report associated with the identified rare event from the other terminal device.

37. An apparatus for a network device, comprising: Means for sending rare event parameters to a terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

38. A terminal device comprising: at least one processor; as well as at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: obtaining rare event parameters, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning; as well as Rare events are identified based on the one or more sets of conditions indicated by the rare event parameters.

39. A terminal device comprising: at least one processor; as well as at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: receiving rare event parameters from a network device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal wireless conditions for positioning; Sending the rare event parameter to another terminal device; as well as A report associated with the identified rare event is received from the other terminal device.

40. A network device comprising: at least one processor; as well as at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: Rare event parameters are sent to the terminal device, wherein the rare event parameters indicate one or more condition sets corresponding to one or more rare events, and wherein the one or more rare events indicate one or more events that are considered abnormal radio conditions for positioning.

41. A non-transitory computer-readable medium comprising program instructions for causing an apparatus to at least perform the method according to any one of claims 32 to 34.

Images