Apparatus and method for data collection

Abstract

Various aspects of the present disclosure relate to data collection. In one aspect, a user equipment receives, via a transceiver, at least one measurement configuration determined by at least one network equipment from a first network equipment, and the at least one measurement configuration is associated with data collection for model training. The user equipment performs a measurement on a reference signal associated with the data collection for model training based on the at least one measurement configuration. In this way, the user equipment can be configured to ensure continuous training data collection as the UE moves across cells or gNBs. As a result, communication performance is improved.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to data collection. Background Technology

[0002] With the development of communication technology, artificial intelligence / machine learning (AI / ML) technologies have been introduced to optimize physical layer operations for some use cases. Examples include Channel State Information (CSI) feedback compression, CSI temporal prediction, beam spatial prediction, beam temporal prediction, AI / ML-assisted localization estimation, and direct AI / ML localization.

[0003] For AI-based positioning use cases, the Location Management Function (LMF) collects training data from the User Equipment (UE) to train the AI ​​model, and the AI ​​model can be an LMF-side model or a UE-side model. For AI-based CSI / Beam Management (BM) / positioning use cases, the gNB collects training data from the UE to train the AI ​​model, and the AI ​​model can be a gNB-side model or a UE-side model. However, there are some issues that need to be addressed regarding data collection. Summary of the Invention

[0004] This disclosure relates to methods, apparatus, and systems that support data collection, particularly data collection for AI / ML training with regard to mobility.

[0005] Some implementations of the methods and apparatus described herein include: receiving from a first network device at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and performing measurements on reference signals associated with the data collection for model training based on the at least one measurement configuration. In this way, data collection can be uninterrupted when the user equipment moves across at least one network device.

[0006] Some implementations of the methods and devices described herein may further include: sending first information to a second network device in at least one network device indicating that a data collection session has been triggered, wherein the second network device serves a user device.

[0007] Some implementations of the methods and apparatus described herein may also include: transmitting first information via Radio Resource Control (RRC) messages.

[0008] Some implementations of the methods and devices described herein may also include: receiving a first configuration of the radio bearer of the user equipment from a second network device.

[0009] Some implementations of the methods and devices described herein may also include sending a first request for at least one measurement configuration to either a second network device or a first network device.

[0010] Some implementations of the methods and devices described herein may further include: receiving at least one measurement configuration from a second network device, wherein, in response to receiving a first request from the second network device, one or more measurement configurations in the at least one measurement configuration are sent by one or more network devices other than the second network device.

[0011] Some implementations of the methods and apparatus described herein may further include: receiving a second configuration of the radio bearer of a user equipment from a second network device, wherein the second configuration is transmitted by a third network device among at least one network device via a handover response.

[0012] Some implementations of the methods and devices described in this article may also include: sending collected data to a first network device.

[0013] Some implementations of the methods and devices described in this paper may also include: receiving a third configuration from a second network device, the third configuration being used to send collected data for model training associated with artificial intelligence / machine learning (AI / ML) based localization, channel state information compression, channel state information prediction, or beam prediction.

[0014] Some implementations of the methods and devices described herein may also include: receiving from a third network device a second request for collected data that has not yet been sent after a handover to the third network device.

[0015] Some implementations of the methods and devices described herein may also include: sending to a third network device one of collected data that has not yet been sent or tracking information associated with the collected data.

[0016] Some implementations of the methods and devices described in this article may also include: discarding collected data that has not yet been sent if the second request is not received within the time period.

[0017] In some implementations of the methods and apparatus described herein, at least one measurement configuration may include one of the following: a type of reference signal; resource information for the reference signal; a type of ground truth; validity information indicating the validity time of a data collection session; or area information indicating the area in which the user equipment performs data collection.

[0018] In some implementations of the methods and devices described herein, the area information may include one of the following: one or more identifiers (IDs) of one or more cells; one or more IDs of one or more regions associated with geographic coordinates; one or more IDs of one or more regions associated with a cell list; one or more Tracking Area Codes (TACs) associated with a cell list; or one or more Tracking Area Identifiers (TAIs) associated with a cell list.

[0019] In some implementations of the methods and apparatus described herein, the first information may include one of the following: an indication that a data collection session is triggered by a first network device; the data collection session is executed via a Long Term Evolution (LTE) Positioning Protocol (LPP) message on the control plane (CP); the data collection session is executed via an LPP message on the user plane (UP); area information indicating the area in which the user equipment performs data collection; or validity information indicating the validity period of the data collection session.

[0020] In some implementations of the methods and apparatus described herein, the first request may include one of the following: the type of reference signal requested by the user equipment; validity information indicating the validity period of the data collection session; or area information indicating the area in which the user equipment performs data collection.

[0021] In some implementations of the methods and devices described herein, a second configuration may be sent when a third network device receives a handover request from a second network device to switch the user equipment to the third network device.

[0022] In some implementations of the methods and devices described herein, a handover request may include one of the following: an indication that a data collection session is triggered by a first network device; a data collection session being executed via an LPP message on a CP; a data collection session being executed via an LPP message on a UP; area information indicating the area in which the user equipment performs data collection; or validity information indicating the validity period of the data collection session.

[0023] In some implementations of the methods and apparatus described herein, one of the first or second configurations may include one of the following: a signaling radio bearer (SRB) configured for the user equipment when the data collection session is executed via an LPP message on the CP; or a data radio bearer (DRB) configured for the user equipment when the data collection session is executed via an LPP message on the UP.

[0024] In some implementations of the methods and devices described herein, if the user equipment is located in the area after a handover to a third network device, the collected data can be sent to the first network device.

[0025] In some implementations of the methods and devices described herein, the third configuration includes one of the following: a period for sending collected data; a period for recording measurements; an event that triggers the sending of collected data; an event that triggers the recording of measurements; an indication that the user equipment will not discard collected data that has not yet been sent; or tracking information including a tracking reference or a tracking recording session reference.

[0026] In some implementations of the methods and devices described herein, the switching request may also include one of the following: an indication that the user equipment is configured not to discard collected data that has not yet been sent; or tracking information.

[0027] In some implementations of the methods and devices described herein, collected data that has not yet been sent can be further sent from a third network device to a second network device.

[0028] In some implementations of the methods and devices described herein, the time period may include one of the following: a pre-configured time period after the collected data is generated; the period of an inactive timer; or the period of a timer configured by a second network device.

[0029] Some implementations of the methods and apparatus described herein include: sending to a user equipment at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and receiving collected data from the user equipment. In this way, data collection can be uninterrupted when the user equipment moves across at least one network device.

[0030] Some implementations of the methods and apparatus described herein may also include sending first information to a second network device in at least one network device, indicating that a data collection session has been triggered, wherein the second network device serves the user equipment.

[0031] Some implementations of the methods and apparatus described herein may further include: sending a first request to at least one network device for at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and receiving at least one measurement configuration from at least one network device.

[0032] Some implementations of the methods and devices described herein may also include: receiving a request from a user equipment for at least one measurement configuration.

[0033] In some implementations of the methods and apparatus described herein, at least one measurement configuration may include one of the following: the type of reference signal associated with positioning; resource information for the reference signal; the type of ground truth; validity information indicating the validity time of a data collection session; or area information indicating the area in which the user equipment performs data collection.

[0034] In some implementations of the methods and devices described herein, the area information may include one of the following: one or more identifiers (IDs) of one or more cells; one or more IDs of one or more regions associated with geographic coordinates; one or more IDs of one or more regions associated with a cell list; one or more Tracking Area Codes (TACs) associated with a cell list; or one or more Tracking Area Identifiers (TAIs) associated with a cell list.

[0035] In some implementations of the methods and apparatus described herein, the first information may include one of the following: an indication that a data collection session is triggered by a first network device; the data collection session is executed via a Long Term Evolution (LTE) Positioning Protocol (LPP) message on the control plane (CP); the data collection session is executed via an LPP message on the user plane (UP); area information indicating the area in which the user equipment performs data collection; or validity information indicating the validity period of the data collection session.

[0036] In some implementations of the methods and devices described herein, the request may include one of the following: the type of reference signal requested by the user equipment; validity information indicating the validity period of the data collection session; or area information indicating the area in which the user equipment performs data collection.

[0037] In some implementations of the methods and devices described herein, the first information may be transmitted via New Radio (NR) Positioning Protocol A (NRPPa) messages.

[0038] Some implementations of the methods and apparatus described herein include: sending a handover request to a third network device, the handover request including first information associated with data collection for beam prediction, wherein the second and third network devices are located in an area where the user equipment performs data collection; and receiving a handover response from the third network device, the handover response including radio resource control (RRC) configuration for the handover process. In this way, beam prediction can be used in the handover process to improve communication performance.

[0039] Some implementations of the methods and devices described herein may also include sending a first request to a third network device in connection with data collection from the user equipment.

[0040] Some implementations of the methods and devices described herein may also include sending RRC configuration to the user equipment; and receiving beam measurements from the third network device after the user equipment switches from the second network device to the third network device.

[0041] Some implementations of the methods and devices described herein may also include: receiving a second request associated with data collection from a third network device for a user equipment.

[0042] In some implementations of the methods and apparatus described herein, the first request may include one of the following: requesting a third network device to provide an indication of beam measurement for the user equipment after the user equipment switches from a second network device to the third network device; an identifier (ID) for the beam measurement; a duration for the user equipment to perform the beam measurement; a duration for the user equipment to record the beam measurement; a duration for the user equipment to transmit the beam measurement; a period for performing the beam measurement; a period for recording the beam measurement; a period for transmitting the beam measurement; second information associated with at least one beam to be measured requested by the second network device; or the type of beam measurement requested by the second network device.

[0043] In some implementations of the methods and devices described herein, the type may include one of the following: an index of a first number of beams having a strong reference signal received power (RSRP) among a plurality of beams of a third network device; or an index of one or more beams having one or more RSRPs above a first threshold.

[0044] In some implementations of the methods and apparatus described herein, the first information may include one of the following: a beam measurement identifier (ID); the ID of the target cell to which the user equipment is to hand over; or third information for beam prediction.

[0045] In some implementations of the methods and apparatus described herein, the third information for beam prediction may include one of the following: an index associated with the beam predicted to have the strongest RSRP among a plurality of beams of the second network device; a list of a second number of beams with relatively strong RSRP among a plurality of beams of the second network device; a list of at least one beam predicted to have at least one RSRP above a second threshold; at least one value indicating the probability of being associated with at least one predicted beam; at least one predicted beam measurement associated with at least one predicted beam; or a predicted value of the dwell time of at least one predicted beam.

[0046] In some implementations of the methods and apparatus described herein, the first information may also include one of the following: second information if the first request does not include second information associated with at least one beam to be measured; or the type of beam measurement if the first request does not include the type of beam measurement.

[0047] In some implementations of the methods and devices described herein, the RRC configuration may include one of the following: a first configuration for a user equipment to perform random access to a target cell using a predicted beam with the strongest RSRP among multiple beams of a third network device; a second configuration for a user equipment to perform beam measurements based on a handover request and a first request; a third configuration for a user equipment to record beam measurements based on a handover request and a first request; or a fourth configuration for a user equipment to transmit beam measurements based on a handover request and a first request.

[0048] In some implementations of the methods and apparatus described herein, the second request may include one of the following: requesting the second network device to provide an indication of the user equipment's historical beam measurements after the user equipment switches from the second network device to the third network device; a duration, wherein the second network device is requested to provide historical beam measurements during a duration prior to the user equipment switching from the second network device to the third network device; the type of historical beam measurements requested by the third network device; the ID of the target cell from which the user equipment wants to switch; or the ID of the source cell from which the user equipment wants to switch.

[0049] In some implementations of the methods and devices described herein, historical beam measurements may be sent to a third network device via a handover request; or historical beam measurements may be sent to a third network device after the handover is completed.

[0050] In some implementations of the methods and apparatus described herein, the first information may also include one of the following: a timestamp of a historical beam measurement; or a value of the dwell time of one or more beams in a historical beam measurement.

[0051] Some implementations of the methods and apparatus described herein include: receiving a handover request from a second network device, the handover request including first information associated with data collection for beam prediction, wherein the second and third network devices are located in the area where the user equipment performs data collection; and sending a handover response to the second network device, the handover response including radio resource control (RRC) configuration for the handover procedure. In this way, data collection can be uninterrupted when the user equipment moves across at least one network device.

[0052] Some implementations of the methods and devices described herein may also include: receiving a first request associated with data collection from a third network device for a user equipment.

[0053] Some implementations of the methods and devices described herein may also include: receiving beam measurements from the user equipment after the user equipment switches from the second network device to the third network device; and sending beam measurements to the second network device.

[0054] Some implementations of the methods and devices described herein may also include sending a second request to a second network device in connection with data collection from the user equipment.

[0055] In some implementations of the methods and apparatus described herein, the first request may include one of the following: requesting a third network device to provide an indication of beam measurement for the user equipment after the user equipment switches from a second network device to the third network device; an identifier (ID) for the beam measurement; a duration for the user equipment to perform the beam measurement; a duration for the user equipment to record the beam measurement; a duration for the user equipment to transmit the beam measurement; a period for performing the beam measurement; a period for recording the beam measurement; a period for transmitting the beam measurement; second information associated with at least one beam requested to be measured by the second network device; or the type of beam measurement requested by the second network device.

[0056] In some implementations of the methods and apparatus described herein, this type may include one of the following: an index of a first number of beams having a strong reference signal received power (RSRP) among a plurality of beams of a third network device; an index of one or more beams having one or more RSRPs above a first threshold; the RSRP of one or more beams; the RSRP of an available beam for beam measurement; or the RSRP of a beam indicated by a second network device.

[0057] In some implementations of the methods and apparatus described herein, the first information includes one of the following: a beam measurement identifier (ID); the ID of the target cell to which the user equipment is to hand over; or third information regarding beam prediction requested by a second network device.

[0058] In some implementations of the methods and devices described herein, the third information for beam prediction may include one of the following: an index associated with the beam predicted to have the strongest RSRP among a plurality of beams of a third network device; a list of at least one beam predicted to have at least one RSRP above a second threshold; at least one value representing the probability of being associated with at least one predicted beam; at least one predicted beam measurement associated with at least one predicted beam; or a predicted value of the dwell time of at least one predicted beam.

[0059] In some implementations of the methods and devices described herein, the switching response may also include one of the following: second information if the first request does not include second information associated with at least one beam to be measured; or type of beam measurement if the first request does not include the type of beam measurement.

[0060] In some implementations of the methods and devices described herein, the RRC configuration may include one of the following: a first configuration for a user equipment to perform random access to a target cell using a predicted beam with the strongest RSRP among multiple beams of a third network device; a second configuration for a user equipment to perform beam measurements based on a handover request and a first request; a third configuration for a user equipment to record beam measurements based on a handover request and a first request; or a fourth configuration for a user equipment to transmit beam measurements based on a handover request and a first request.

[0061] In some implementations of the methods and apparatus described herein, the second request may include one of the following: requesting the second network device to provide an indication of the user equipment's historical beam measurements after the user equipment switches from the second network device to the third network device; a duration, wherein the second network device is requested to provide historical beam measurements during a duration prior to the user equipment switching from the second network device to the third network device; the type of historical beam measurements requested by the third network device; the ID of the target cell from which the user equipment wants to switch; or the ID of the source cell from which the user equipment wants to switch.

[0062] In some implementations of the methods and devices described herein, historical beam measurements may be sent to a third network device via a handover request; or historical beam measurements may be sent to a third network device after the handover is completed.

[0063] In some implementations of the methods and apparatus described herein, the first information may also include one of the following: a timestamp of a historical beam measurement; or a value of the dwell time of one or more beams in a historical beam measurement. Attached Figure Description

[0064] Figure 1 An example of a wireless communication system supporting data collection according to various aspects of this disclosure is illustrated.

[0065] Figure 2A An example signaling diagram is shown, illustrating an example process according to various aspects of this disclosure.

[0066] Figure 2B Another example signaling diagram is illustrated, which illustrates example processes according to various aspects of this disclosure.

[0067] Figure 3 An example process for sending collected training data according to various aspects of this disclosure is illustrated.

[0068] Figure 4 Example processes according to various aspects of this disclosure are illustrated.

[0069] Figure 5 Another example process according to various aspects of this disclosure is illustrated.

[0070] Figure 6 The illustration shows yet another example process according to various aspects of this disclosure.

[0071] Figure 7 The illustration shows yet another example process according to various aspects of this disclosure.

[0072] Figure 8 The illustration shows yet another example process according to various aspects of this disclosure.

[0073] Figure 9 An example of a device supporting data collection according to various aspects of this disclosure is illustrated.

[0074] Figure 10 An example of a processor supporting data collection according to various aspects of this disclosure is illustrated.

[0075] Figure 11 A flowchart illustrating a method for collecting supporting data according to various aspects of this disclosure is shown.

[0076] Figure 12 A flowchart illustrating a method for collecting supporting data according to various aspects of this disclosure is shown.

[0077] Figure 13 A flowchart illustrating a method for collecting supporting data according to various aspects of this disclosure is shown.

[0078] Figure 14 A flowchart illustrating a method for collecting supporting data according to various aspects of this disclosure is shown.

[0079] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

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

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

[0082] References to "an embodiment," "an exemplary embodiment," and "an embodiment," etc., in this disclosure indicate that the described embodiments may include a particular feature, structure, or characteristic, but not every embodiment is required to include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) affecting such a feature, structure, or characteristic is within the scope of their knowledge.

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

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

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

[0086] As used herein, the term "network device" generally refers to a node in a communication network through which user equipment can access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), Radio Access Network (RAN) nodes, Evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), infrastructure equipment for V2X (Vehicle-to-Everything) communication, Transmitter Receiver Point (TRP), Receiver Point (RP), Remote Radio Header End (RRH), relay, Integrated Access and Backhaul (IAB) nodes, and low-power nodes (such as femtoBS, picoBS, etc.), depending on the terminology and technology applied. Network devices can also refer to network functions (NFs) in the core network, such as SMF, AMF, PCF, UPF, or devices with similar functions in future network architectures.

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

[0088] Figure 1An example of a wireless communication system 100 supporting data collection according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Furthermore, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0089] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0090] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more wireless access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0091] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0092] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1 The diagram illustrates some examples of UE 104. UE 104 is capable of communicating with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1 As shown. Alternatively or additionally, UE 104 may support communication with other network entities 102 or UE 104 that can be used as relays in wireless communication system 100.

[0093] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidechain. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0094] Network entity 102 may support communication with core network 106 or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). An ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0095] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of a Central Unit (CU), Distributed Unit (DU), Radio Unit (RU), RAN Intelligent Controller (RIC) (e.g., near real-time RIC, non-real-time RIC), Service Management and Orchestration (SMO) system, or any combination thereof.

[0096] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0097] The functional decomposition between CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional decomposition can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0098] Alternatively or additionally, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU, or between the DU and RU, can be within a protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different items in the CU, DU, or RU).

[0099] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the mid-range or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by the respective network entity 102 communicating via such communication links.

[0100] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) of one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0101] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0102] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0103] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0104] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0105] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technique. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technique. It should be understood that the first digital technique (e.g., quantity) associated with the first subcarrier spacing (e.g., 15kHz) can be... μ The reference of =0 can be used interchangeably between subframes and time slots.

[0106] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, along with other devices or apparatuses, for short-range, high data rate capabilities.

[0107] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ =2), which includes a 60kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120kHz.

[0108] "Layer 1 (L1)" refers to the physical layer, which is primarily used to provide wireless physical channels for the transmission of higher-level services. In this disclosure, "L1 measurement" refers to any of the following that can be used to train AI / ML models: CSI compression, CSI prediction, beam prediction, and localization.

[0109] In CSI compression, for UE-side Type 1 training and UE-priority Type 3 training, L1 measurement can refer to ground truth CSI from the NW, used for scaler quantization and / or codebook-based quantization (e.g., similar to Type II e); or auxiliary information used to classify data, distinguishing data characteristics caused by specific configurations, scenarios, sites, etc. For network (NW)-priority training in training collaboration Type 3, L1 measurement can refer to the CSI-generated model training dataset (e.g., the original channel or feature vector as model input, and the latent space vector before and after quantization as model output) or auxiliary information used to classify data, distinguishing data characteristics caused by specific configurations, scenarios, sites, etc. For UE-side proxy model training in monitoring, L1 measurement can refer to the proxy model training dataset (e.g., the quantized latent space vector as proxy model input, and the target CSI to be recovered as proxy model output) or auxiliary information used to classify data, distinguishing data characteristics caused by specific configurations, scenarios, sites, etc.

[0110] In CSI prediction, L1 measurement can refer to continuous CSI (i.e., historical CSI and future CSI), and the type of CSI includes the original channel matrix, PMI, or eigenvectors, etc. L1 measurement can also refer to auxiliary information used for model management, such as site / scene / dataset related information.

[0111] In beam prediction, for set B, L1 measurement can refer to L1-RSRP measurements based on set B or a subset of set B. For tag data, L1 measurement can refer to L1-RSRP measurements based on set A or a subset of set A, partial L1-RSRP measurements and beam indicators based on set A or a subset of set A, or top-k beam indicators. For time-related information, L1 measurement can refer to timestamps. For auxiliary information including one or more sources, L1 measurement can refer to site / scene / dataset-related information (e.g., dataset ID), gNB-side auxiliary information, or UE-side auxiliary information.

[0112] In positioning, for the measurement type, L1 measurements can refer to Channel Impulse Response (CIR), Power Delay Distribution (PDP), Delay Distribution (DP), Downlink Positioning Reference Signal (DL-PRS) RSRP, DL-PRS RSRPP, UL SRS RSRP, UL SRS RSRPP, Downlink Reference Signal Time Difference (DL-RSTD), UE Rx-Tx Time Difference, gNB Rx-Tx Time Difference, Uplink Relative Time of Arrival (UL-RTOA), Uplink Angle of Arrival (UL AoA), Downlink Angle of Departure (DL-AoD), SSB RSRP, or CSI-RS RSRP. For tag type, L1 measurements can refer to location coordinates, timing estimation, line-of-sight (LOS), or non-line-of-sight (NLOS). For auxiliary information, L1 measurements can refer to timestamps, quality indicators, or reference signal (RS) configuration.

[0113] "Layer 3 (L3)" refers to the network layer, which includes the RRC sublayer in the access layer and the mobility management (MM) and call control (CC) layers in the non-access layer. In this disclosure, "L3 measurement" refers to Radio Resource Management (RRM) measurement, which is filtered by a Layer 3 filter and conventionally reported to the gNB via RRC messages.

[0114] AI / ML technology has been introduced to optimize physical layer operations, also known as AI over the air interface. For AI-based positioning use cases, the LMF collects training data from the UE to train the AI ​​model, and this AI model can be either an LMF-side model or a UE-side model. For AI-based CSI / BM / positioning use cases, the gNB collects training data from the UE to train the AI ​​model, and this AI model can be either a gNB-side model or a UE-side model. However, UE mobility factors have not yet been considered during data collection. Several issues regarding data collection need to be addressed.

[0115] In the first question, regarding AI-based localization, depending on the scalability of the AI ​​model, the LMF may want to train an AI model capable of AI-based localization (e.g., fingerprint recognition) within a specific area comprised of a list of cells. The LMF can collect data from one or more UEs, and ideally, data collection should not be interrupted by UE mobility as long as the UEs are within the area. Traditional data collection processes do not support this.

[0116] In the second question, assuming the UE is configured by the source gNB to periodically report training data (e.g., a set of recorded L1 measurements) to the source gNB, the following situation may occur when the UE switches to another gNB: Recorded L1 measurements remain in the buffer that should, but have not yet, been sent to the source gNB. It is currently unclear whether or how the recorded L1 measurements are transmitted to the source gNB.

[0117] In the third issue, in future versions, in addition to predicting cell-level link quality, the source gNB can also predict the optimal beam after the UE hands over to the target gNB when making a handover decision. In this way, when two cells have equal (predicted) link quality, the source gNB will hand over the UE to the cell with the better predicted beam quality. The target gNB can also use the beam prediction results to configure the UE to perform random access via the optimal predicted beam in the handover command. Furthermore, L1 / L2 trigger mobility (LTM) decisions can be made, and the UE can be configured to connect to another cell via the predicted optimal beam in the LTM command media access control (MAC) control element (CE). Traditional data collection procedures do not support the above.

[0118] In the fourth issue, in future versions, the target gNB itself can perform optimal beam prediction and configure the UE to perform random access via the optimal predicted beam in the handover command sent to the UE. However, the conventional data collection process does not support the above.

[0119] In view of the foregoing discussion, some embodiments of this disclosure provide a data collection solution. In one aspect of the solution, a user equipment receives from a first network device at least one measurement configuration determined by at least one network device, and the at least one measurement configuration is associated with data collection for model training; and based on the at least one measurement configuration, performs measurements on a reference signal associated with the data collection for model training. In this way, the user equipment can be configured to ensure continuous training data collection when the UE moves across cells or gNBs. Therefore, communication performance is improved. Reference will be made below. Figures 2A to 14 The principles and implementation of the embodiments of this disclosure are described in detail.

[0120] Figure 2A A signaling diagram is illustrated, which illustrates an example process 200A according to various aspects of this disclosure. Process 200A may involve user equipment 201 and a first network device 202. Figure 2A User equipment 201 in the middle can be Figure 1 Example of UE104 in the example. Figure 2A The first network device 202 in the middle can be Figure 1 Examples of network entity 102 or core network 106 in the example. It should be understood that although process 200A is applied... Figure 1 In the communication environment 100, this process can also be applied to other communication scenarios with similar problems.

[0121] In process 200A, the first network device 202 sends 205 at least one measurement configuration 207 determined by at least one network device to the user equipment 201. The at least one measurement configuration is associated with data collection for model training. The first network device can receive the at least one measurement configuration from the at least one network device. The at least one network device may be located in the area of ​​the user equipment 201 in which data collection is performed. It should be understood that when the model is trained for an AI-based localization model, the first network device 202 may be a Location Management Function (LMF), and when the model is trained for AI-based CSI or beam management, the first network device 202 may be a gNB.

[0122] Alternatively or additionally, the first network device 202 may send a request for at least one measurement configuration to at least one network device. The at least one measurement configuration is determined by the at least one network device and is associated with data collection for model training. The first network device 202 may then receive the at least one measurement configuration from the at least one network device. In other words, the first network device 202 may collect measurement configurations from multiple network devices in the area where the user equipment 201 performs data collection, and then the first network device 202 may send the measurement configuration to the user equipment.

[0123] In some embodiments, at least one measurement configuration may include the type of reference signal, resource information for the reference signal, the type of ground truth, validity information indicating the validity time of the data collection session, area information indicating the area in which the user equipment performs data collection, or any combination of two or more of the above items.

[0124] For example, at least one measurement configuration may include the type of measurement that the user equipment 201 needs to measure, such as PRS, SSB, CSI-RS, or other DL reference signals in the area. Optionally and additionally, at least one measurement configuration may include resource information of the PRS, SSB, or other DL reference signals in the area (i.e., at what time and frequency the resources are measured). The LMF may collect the resource information in advance from the gNB in ​​the area, and then the resource information may be provided to the UE. Examples of time and frequency information may include comb size (M, N) expressed as the number of symbols M with comb N-mode, RE offset, slot offset, period, and configured transmission bandwidth, which may be associated with a set of resources (e.g., DL-PRS resources).

[0125] In the example, at least one measurement configuration may include intermediate ground truth labels associated with a combination of radio access technology (RAT)-dependent measurements and UE / PRU location-based UE / PRU positioning.

[0126] In another example, at least one measurement configuration may include time-based validity information indicating the validity of the data collection session based on a timer / expiration timer / validity time / measurement response time associated with the received DL-PRS positioning assistance data. Data collection performed outside the expiration or validity time or within the measurement response time may depend on the LMF to determine whether the data should be used for training or inference. Alternatively, the LMF may explicitly or implicitly terminate the data collection session based on an inactivity timer or when the UE moves out of the desired area.

[0127] Alternative or additional locations may include: one or more identifiers (IDs) of one or more cells, one or more IDs of one or more regions associated with geographic coordinates, one or more IDs of one or more regions associated with a cell list, one or more Tracking Area Codes (TACs) associated with a cell list, one or more Tracking Area Identifiers (TAIs) associated with a cell list, or any combination of two or more of the above items.

[0128] For example, area information can be in any of the following forms: one or more cells, each represented by a cell ID (e.g., PCI, CGI, or ARFCN, or a combination thereof); one or more regions, each represented by a region ID, and the region ID is associated with a specific geographic area calculated based on geographic coordinates; one or more regions, each represented by a region ID, and the region ID is associated with a list of cells. This association is predefined or preconfigured by the NW; one or more location area codes, tracking area codes (TACs), or tracking area identifiers (TAIs), for example, consisting of several cells grouped together to form a tracking area.

[0129] Additionally, user equipment 201 may send first information indicating that a data collection session has been triggered to a second network device among at least one network device, and the second network device serves the user equipment. Alternatively or additionally, first network device 202 may send the first information to the second network device. The second network device may be a serving gNB of user equipment 201 capable of providing services to user equipment 201.

[0130] Furthermore, if the first information is sent by user equipment 201, it is sent via Radio Resource Control (RRC) messages. If the first information is sent by first network device 202, it is sent via New Radio Positioning Protocol A (NRPPa) messages.

[0131] In some embodiments, the first information may include: an indication that the data collection session is triggered by a first network device, the data collection session being executed via a Long Term Evolution (LTE) Positioning Protocol (LPP) message on the control plane (CP), the data collection session being executed via an LPP message on the user plane (UP), area information indicating the area in which the user equipment performs data collection, validity information indicating the validity period of the data collection session, or any combination of two or more of the above items.

[0132] For example, an NRPPa message or an RRC message may include: an indication that the LMF has triggered a data collection session from user equipment 201; information about whether the data collection session is performed via LPP on the CP or LPP on the UP; region information related to region-based training data collection (as described above); time-based criteria for deriving auxiliary data for the measurements used in the data collection; or any combination of two or more of the above items.

[0133] Alternatively or additionally, user equipment 201 may receive a first configuration of the user equipment’s radio bearer from a second network device.

[0134] In some embodiments, user equipment 201 may receive a second configuration of its radio bearer from a second network device. The second configuration is transmitted by a third network device (at least one of the network devices) via a handover response. The third network device may be a target gNB that user equipment 201 can hand over to.

[0135] Additionally, if the third network device receives a handover request from the second network device to switch user equipment 201 to the third network device, the second configuration is sent. In other words, the second network device can send a handover request to the third network device. If the handover request is accepted by the third network device, the third network device can send the second configuration via a handover request acknowledgment message.

[0136] Additionally, the handover request may include: an indication that the data collection session is triggered by a first network device; the data collection session is executed via an LPP message on the CP; the data collection session is executed via an LPP message on the UP; area information indicating the area in which the user equipment performs data collection; validity information indicating the validity period of the data collection session; or any combination of two or more of the above items.

[0137] In one example, a handover request may include: an indication that the LMF has triggered a data collection session from the UE; information about whether the data collection session is performed via LPP on the CP or LPP on the UP; area information related to area-based training data collection (as described above); and time-based criteria for deriving auxiliary data for the measurements used in the data collection.

[0138] In some embodiments, if the data collection session is performed via LPP messages on the CP, the first or second configuration may include a signaling radio bearer (SRB) configured for user equipment 201. In some embodiments, if the data collection session is performed via LPP messages on the UP, the first or second configuration may include a data radio bearer (DRB) configured for user equipment.

[0139] In one example, the first network device 202 may be an LMF (Local Management Function). The first network device 202 can initiate training data collection by generating an LPP (Local Power Propagation) message and sending the LPP message to the UE via a CP (Content Provider) or UP (Upload Provider). If the LPP message is sent to the UE via a CP, the LPP message is carried in Network Attached Memory (NAS) via a Signaling Radio Bearer (SRB). If the LPP message is sent to the UE via an UP, the LPP message is carried as regular data via a Data Radio Bearer (DRB). In another example, the first network device 202 may be a gNB (Garden Network Attached Memory), and the first network device 202 may send at least one measurement configuration via an RRC (Redirect Reduction Code) message.

[0140] In one example, if the data collection session is executed via an LPP message on the CP, the serving gNB will configure SRB4, SBR5, or a new SRB (if it has not yet been configured) at user equipment 201. In another example, if the data collection session is executed via an LPP message on the UP, the serving gNB will configure a dedicated DRB with a specific priority lower than other DRBs.

[0141] Referring again to Figure 2, after receiving at least one measurement configuration 210 from the first network device 202, the user equipment 201 performs a measurement 215 on a reference signal associated with data collection for model training based on at least one measurement configuration 207. Then, the user equipment 201 sends 220 the collected data 223 of the user equipment 201 to the first network device 202. Accordingly, the first network device 202 receives 225 the collected data of the user equipment 201.

[0142] In addition, user equipment 201 may send collected data to the first network device. Alternatively or additionally, if the user equipment is still in the area after a handover to a third network device, the collected data is sent to the first network device. For example, if area-based data collection is configured, such as if area information is provided, the UE user equipment 201 may first check whether it is still in the area after a handover to another cell / gNB. If the user equipment 201 is still in the area, it continues to collect and report the requested training data.

[0143] In some embodiments, user equipment 201 may send a first request for at least one measurement configuration to a second network device or a first network device 202. Accordingly, the second network device or the first network device 202 may receive the first request from user equipment 201. The AI / ML model used for positioning may be located on the user equipment side, and user equipment 201 may collect data without sending the collected data to the gNB. For example, user equipment 201 may send an LPP message to the LMF or an RRC request message to the serving gNB.

[0144] Alternatively or additionally, user equipment 201 may receive at least one measurement configuration from a second network device. In response to receiving a first request from the second network device, one or more of the at least one measurement configuration may be sent by one or more network devices other than the second network device. In other words, the second network device may send the first request to a third network device. If the first request is accepted by the third network device, the third network device may send one or more measurement configurations to the second network device. The second network device then sends at least one measurement configuration to user equipment 201.

[0145] For example, the LMF or serving gNB can accordingly provide the UE with the requested PRS / SSB / other reference signaling configuration. If area information is provided in the first request for area-based data collection, the LMF or serving gNB can coordinate with other gNBs in that area to collect the requested PRS / SSB / other reference signaling configuration within that area. In one example, the LMF can request the PRS / SSB / other reference signaling configuration from other gNBs via the NRPPa procedure. In another example, the serving gNB can request the PRS / SSB / other reference signaling configuration from other gNBs via the Xn AP procedure. The LMF or serving gNB can also indicate the area information used for area-based data collection, causing another gNB to provide the PRS / SSB / other reference signaling configuration accordingly within that area.

[0146] In addition, the first request may include the type of reference signal requested by the user equipment, validity information indicating the validity period of the data collection session, area information indicating the area in which the user equipment performs data collection, or any combination of two or more of the above items.

[0147] For example, different AI / ML models may have different input requirements; some AI / ML models use SSB, while others use PRS. The first request may include requesting the LMF or serving gNB to provide PRS, SSB, or other reference signaling configurations for the UE to measure and train its AI model itself (e.g., by reusing existing LPPs). RequestAssistanceData The message indicates that the request to NW can be configured and provides a configuration related to the reference signaling required as input for a specific AIML model.

[0148] Examples of time and frequency information may include comb size (M, N) expressed as the number of symbols M with comb N-mode, RE offset, slot offset, period, and configured transmission bandwidth, which may be associated with a set of resources (e.g., DL-PRS resources). Measurements of PRS, SSB, CSI-RS, or other reference signaling will be used by the UE itself as training data for the AI ​​model and are not expected to be reported to the LMF or any gNB. The implementation of area information and validity information can be the same as described above.

[0149] In some embodiments, user equipment 201 may receive a third configuration from a second network device. The third configuration may be used to send collected data for model training related to location or channel state information compression, channel state information prediction, or beam prediction based on artificial intelligence / machine learning (AI / ML).

[0150] In one example, User Equipment 201 may be configured by the serving gNB to perform training data collection and reporting for AI / ML model training for AI-based CSI / BM. After handover and separation of the UE from the serving gNB, training data for records that have not yet been sent to the serving gNB may be cached in the UE.

[0151] Figure 3 An example process 300 for transmitting collected training data according to various aspects of this disclosure is illustrated. For example... Figure 3 As shown, User Equipment 201 can be configured to periodically send collected training data to the gNB. Between two reports, User Equipment 201 can be configured to record multiple instances of L1 or L3 measurements. It is possible that User Equipment 201 records few instances, and a handover is triggered before User Equipment 201 reports them to the serving gNB. In this case, since these instances can be valuable samples measured at the cell edge, it can be advantageous for the serving gNB to still be able to acquire recorded but not yet reported measurement instances after the handover.

[0152] The second network device (i.e., the serving gNB) can configure user equipment 201 to perform L1 / L3 measurement logging and report the recorded measurement instances to the serving gNB via RRC signaling. The serving gNB can then generate... RRCReconfiguration The message is then sent to user equipment 201.

[0153] Additionally, the third configuration may include a period for sending collected data, a period for recording measurements, an event that triggers the sending of collected data, an event that triggers the recording of measurements, an indication that the user equipment will not discard collected data that has not yet been sent, tracking information including a tracking reference or a tracking recording session reference, or any combination of two or more of the above items.

[0154] In some embodiments, the switching request may further include: an indication that the user equipment is configured not to discard collected data that has not yet been sent, tracking information, or any combination of two or more of the above items.

[0155] For example, RRCReconfiguration The message may include: a period / event for reporting, a period / event for measurement recording, an indication that the user equipment should not discard any recorded measurements that have not yet been sent from the buffer; tracking information, such as a tracking reference or tracking record session reference in cases where training data collected from the user equipment will eventually be sent to Operations Administration and Maintenance (OAM); or any combination of two or more of the above items.

[0156] Alternatively or additionally, user equipment 201 may receive a second request for collected data that has not yet been sent after a handover to a third network device. The second request may be sent from the third network device.

[0157] In one example, after user equipment 201 is switched over and connected to another gNB (i.e., a third network device), the other gNB can trigger a UE information procedure to obtain any possible recorded L1 / L3 measurements that have not yet been sent at the UE. Another gNB can generate... UEInformationRequest The message is sent to the UE, and includes an indication requesting any recorded L1 / L3 measurement results that the UE has not yet sent. It should be understood that if the other gNB is the same as the serving gNB, then the handover between the second and third network devices can be an intra-gNB handover. If the other gNB is different from the serving gNB, then the handover of user equipment 201 can be an inter-gNB handover.

[0158] Additionally, user equipment 201 may send at least one of the following to a third network device: collected data that has not yet been sent or tracking information associated with the collected data. For example, if any L1 / L3 measurement records are available at the UE, the UE will generate... UEInformationResponse The message serves as a response to other gNBs. UEInformationResponse The message can include L1 / L3 measurements for records that have not yet been sent. If configured in a third configuration, then... UEInformationResponse The message may also include associated tracking information, such as tracking references or tracking record session references.

[0159] Furthermore, collected data that has not yet been sent can be further transmitted from a third network device to a second network device. For example, another gNB can send the received recorded L1 / L3 measurements to the (legacy) serving gNB via an XnAP message, and another gNB can also send the received recorded L1 / L3 measurements and associated tracking information to the OAM.

[0160] If the second request is not received within the time period, user equipment 201 may discard the collected data that has not yet been sent. Furthermore, the time period may include: a pre-configured time period after the collected data is generated, the period of an inactive timer, the period of a timer configured by the second network device, or any combination of two or more of the above items.

[0161] For example, the time period can be a defined time period after the collected data is generated (e.g., 48 hours), a defined inactive timer within a certain time period, or a timer configured by the service gNB, such as an expiration timer.

[0162] Figure 2BA signaling diagram is illustrated, which illustrates an example process 200B according to various aspects of this disclosure. Process 200B may involve a second network device 203 and a third network device 204. Figure 2B The second network device 203 in the middle can be Figure 1 Example of network entity 102 in the example. Figure 2B The third network device 204 in the middle can be Figure 1 Example of network entity 102 in the example. It should be understood that although process 200B is applied to Figure 1 In the communication environment 100, this process can also be applied to other communication scenarios with similar problems.

[0163] In process 200B, the second network device 203 sends a handover request 237 to the third network device 204. The handover request includes first information associated with data collection for beam prediction, wherein the second and third network devices are located in the area where the user equipment performs data collection.

[0164] The second network device 203 can be a source gNB that provides services to the user equipment, and the third network device 204 can be a target gNB that the user equipment can switch to. After deciding to switch the user equipment to the target gNB, the source gNB can send a handover request message to the target gNB.

[0165] In some embodiments, the second network device 203 may send a first request associated with data collection from the user equipment to the third network device 204. The AI / ML model for optimal beam prediction may be located on the second network device side, and the second network device 203 may collect data from the third network device 204. Prior to user equipment handover, the source gNB may trigger a data collection report initiation process and send a data collection request message to the target gNB.

[0166] Additionally, the first request may include: a request for the third network device to provide, after the user equipment switches from the second network device to the third network device, an indication of beam measurement for the user equipment, a beam measurement ID, a duration for the user equipment to perform beam measurements, a duration for the user equipment to record beam measurements, a duration for the user equipment to transmit beam measurements, a period for performing beam measurements, a period for recording beam measurements, a period for transmitting beam measurements, second information associated with at least one beam to be measured as requested by the second network device, the type of beam measurement requested by the second network device, or any combination of two or more of the above items. On the other side of the communication, the third network device 204 may receive the first request from the third network device.

[0167] In addition, this type may include: an index of a first number of beams with a strong reference signal received power (RSRP) among multiple beams of a third network device, an index of one or more beams with one or more RSRPs above a first threshold, or a combination of the above.

[0168] In one example, a data collection request may include: a request for the target gNB to provide an indication of L1 / L3 beam measurements after a handover; a duration during which the target gNB should configure the UE to measure / record / report L1 / L3 beam measurements; a reporting period; a period for measurement / recording instances; information related to the specific beam to be measured, such as an SSB index; information related to the type of measurement, such as an index of the top K beams with the strongest RSRP among multiple beams, or the RSRP of the top K beams, the RSRP of all available beams, or the RSRP of a specific beam; the measurement ID of the L1 / L3 beam measurement; or any combination of two or more of the above items.

[0169] In some embodiments, the first information may include: the ID of the beam measurement, the ID of the target cell to which the user equipment is to hand over, third information of the beam prediction, or any combination of two or more of the above items. For example, a handover request message includes: the measurement ID, target cell ID, beam prediction information, or any combination of two or more of the above items included in a corresponding data collection request message.

[0170] Additionally, the third information for beam prediction may include: an index associated with the beam predicted to have the strongest RSRP among the plurality of beams of the second network device; a list of a second number of beams with relatively strong RSRP among the plurality of beams of the second network device; a list of at least one beam predicted to have at least one RSRP above a second threshold; at least one value indicating the probability of being associated with at least one predicted beam; at least one predicted beam measurement associated with at least one predicted beam; a predicted value of the dwell time of at least one predicted beam; or any combination of two or more of the above items.

[0171] For example, for a target cell, the beam prediction information may take the form of: a predicted best beam (e.g., SSB index), a list of possible predicted best beams (e.g., SSP index), a probability value (e.g., 0-100) indicating the likelihood associated with each predicted best beam (as described above), a predicted L1 / L3 measurement (e.g., RSRP) associated with each predicted best beam, a predicted value of the dwell time of the user equipment in the predicted best beam, or any combination of two or more of the above items.

[0172] Alternatively or additionally, if the first request does not include the second information, the first information may also include the second information associated with at least one beam to be measured (e.g., SSB index). Alternatively, if the first request does not include the type, the first information may also include the type of beam measurement, such as the index of the first K beams, the RSRP of the first K beams, the RSRP of all available beams, or the RSRP of a specific beam.

[0173] In some embodiments, the third network device 204 may send a second request associated with data collection from the user equipment to the second network device 203. Accordingly, the second network device 203 may receive the second request from the third network device 204. The AI / ML model for optimal beam prediction may be located on the third network device side, and the third network device 204 may collect data from the second network device 203. For example, the target gNB may collect training data from the source gNB for optimal beam prediction, such as during the initial phase after handover execution for service beam selection. Before handover, the target gNB triggers a data collection report initiation process and sends a data collection request message to the source gNB.

[0174] Additionally, the second request may include: requesting the second network device to provide an indication of the user equipment's historical beam measurements after the user equipment switches from the second network device to the third network device; a duration during which the second network device is requested to provide historical beam measurements during the duration prior to the user equipment switching from the second network device to the third network device; the type of historical beam measurements requested by the third network device; the ID of the target cell from which the user equipment is to switch; or the ID of the source cell from which the user equipment is to switch; or any combination of two or more of the above items.

[0175] In one example, the data collection request includes: an indication that the source gNB provides historical L1 / L3 beam measurements of the UE when a handover is triggered; a duration during which the source gNB should provide historical L1 / L3 beam measurements of the UE before the handover; information related to the type of measurement, such as the serving beam index, the index of the top K beams, or the RSRP of the top K beams, the RSRP of all available beams, or the RSRD of a specific beam; cell A ID, where cell A of the target gNB is the target cell if the UE is handing over from the source gNB to cell A of the target gNB; cell B ID, where cell B is the source cell if the UE is handing over from cell B of the source gNB to the target gNB; or any combination of two or more of the above items.

[0176] Furthermore, historical beam measurements can be sent to a third network device 204 via a handover request. For example, after deciding to hand over the UE to the target gNB, the source gNB sends a handover request message to the target gNB. The handover request message may include the requested historical L1 / L3 beam measurements. Each historical L1 / L3 beam measurement instance may be associated with a timestamp of the measurement. For the serving beam, the dwell time value may also be provided in the handover request message.

[0177] Alternatively, historical beam measurements can be sent to a third network device after the handover is complete. For example, the source gNB can send historical L1 / L3 beam measurements to the target gNB after the handover is complete, and the historical L1 / L beam measurements can be sent via a data collection update message.

[0178] Alternatively or additionally, the first information may also include: timestamps of historical beam measurements, dwell times of one or more beams in historical beam measurements, or combinations thereof.

[0179] After receiving a handover request 237 (240) from the second network device 203, the third network device 204 sends a handover response 257 (250) to the second network device 203. The handover response 247 includes Radio Resource Control (RRC) configuration for the handover process. Accordingly, the second network device 203 receives a handover response 247 (260) from the third network device 204. In other words, the target gNB can utilize the predicted optimal beam to configure user equipment for random access to the target gNB via the predicted optimal beam.

[0180] In some embodiments, the RRC configuration may include: a first configuration for a user equipment to perform random access to a target cell using a predicted beam with the strongest RSRP among a plurality of beams of a third network device; a second configuration for a user equipment to perform beam measurements based on a handover request and a first request; a third configuration for a user equipment to record beam measurements based on a handover request and a first request; a fourth configuration for a user equipment to transmit beam measurements based on a handover request and a first request; or any combination of two or more of the above items.

[0181] For example, the target gNB can configure user equipment to perform random access to the target cell via a predicted optimal beam. The target gNB can also configure user equipment to perform L1 / L3 beam measurements / recordings requested by the source gNB in ​​a data collection request or data collection handover request message.

[0182] Alternatively or additionally, the second network device 203 can send RRC configuration to the user equipment. After the user equipment switches from the second network device to the third network device, the second network device 203 can receive beam measurements from the third network device 204.

[0183] On the other side of the communication, after the user equipment switches from the second network device 203 to the third network device 204, the third network device 204 can receive beam measurements. Alternatively, the third network device 204 can send beam measurements to the second network device 203. For example, the target gNB can also send L1 / L3 beam measurements to the source gNB via a data collection update message.

[0184] Through embodiments of procedures 200A and 200B, a user equipment (UE) can be configured to ensure continuous training data collection when the UE moves across cells or gNBs. If training data reporting is interrupted due to UE mobility, and the UE has already recorded measurements in a buffer that were not sent to the serving gNB at the time of handover, the UE can retain the recorded measurements (i.e., not discard them) and send them to another gNB after the handover. Furthermore, the serving gNB can collect training data for optimal beam prediction from the target gNB. The target gNB can also collect training data for optimal beam prediction from the source gNB. It should be understood that embodiments of procedures 200A and 200B can be used individually or in combination.

[0185] Figure 4 An example process 400 according to various aspects of this disclosure is illustrated. Process 400 may involve UE 401, LMF 402, serving gNB 403, and other gNBs 404. Figure 4 UE 401 in the context can be Figure 1 UE 104 or Figure 2A Example of user equipment 201 in the example. Figure 4 LMF 402 in the text can be Figure 1 The core network 106 or Figure 2A Example of the first network device 202 in the example. Figure 4 The service gNB 403 can be Figure 1 Example of network entity 102 in the example. Other gNB 404s can be... Figure 1 An example of network entity 102 in the example. It should be understood that process 400 can be considered as... Figure 2A A more specific example of process 200A.

[0186] In process 400, the collection of training data from UE 401 is initiated and configured by LMF 402, and the training data is sent from UE 401 to LMF 402. The training data can be used for AIML model training on the LMF side.

[0187] At 410, LMF 402 initiates training data collection by generating an LPP data collection configuration message and sending it to UE 401 via CP or UP. The LPP message may include: information related to the training data requested by LMF 402, area information, area information for UE 401 to collect the requested training data when UE 401 is located within that area (also known as area-based data collection), or a combination of the above. Accordingly, UE 401 receives the LPP data collection configuration message from LMF 402.

[0188] The message indicating that data collection has been triggered is generated and sent by either LMF 402 or UE 401. At 415, LMF 402 generates the message and sends it to serving gNB 403. At 420, UE 401 generates the message and sends it to serving gNB 403. When the message is sent by UE 401, it is carried in an RRC message; when the message is sent by LMF 402, it is carried in an NRPPa message.

[0189] At 425, after knowing that a training data collection session has been initiated at the UE, the serving gNB configures a dedicated radio bearer for training data collection. The dedicated radio bearer is indicated to the UE by the RRC configuration at 401. The dedicated radio bearer can be configured to have a specific priority lower than SRB1 or the regular DRB.

[0190] At 430, UE 401 begins collecting and reporting the requested training data via the LPP configured by the LMF. UE 401 sends an LPP data collection report to LMF 402, which includes ground truth and relevant L1 measurements. Accordingly, LMF 402 receives the LPP data collection report from UE 401.

[0191] At 435, for inter-gNB handover, the serving gNB 403 wants to hand over UE 401 to another gNB 404 and sends a handover request message to the other gNB 404 via the Xn interface.

[0192] At 440, after receiving a handover request message from serving gNB 403, other gNBs 404 send a handover request confirmation message to serving gNB 403 in response. The handover request confirmation message includes the RRC configuration applied by UE 401 when accessing other gNBs 404, and the RRC configuration may include the configuration of a dedicated radio bearer for training data collection. The dedicated radio bearer may be configured to have a specific priority lower than SRB1 or the regular DRB.

[0193] At 445, UE 401 receives RRC configuration, including dedicated radio bearer configuration, from serving gNB 403.

[0194] At 450, after switching from serving gNB 403 and accessing another gNB 404, UE 401 continues to collect the requested training data and reports it to LMF 402 via the LPP previously configured by LMF 402, without re-initiating a new LPP session.

[0195] In summary, for training the LMF side model for AI-based positioning, in order to perform training data collection for AI-based positioning that takes mobility into account, the UE is configured to ensure continuous collection of training data when the UE moves across gNBs or cells.

[0196] Figure 5 Another example process 500 according to various aspects of this disclosure is illustrated. Process 500 may involve UE 501, LMF / serving gNB 502 and other gNBs 503. Figure 5 UE 501 in the context can be Figure 1 UE 104 or Figure 2A Example of user equipment 201 in the example. Other gNB 503 may be Figure 1 An example of network entity 102 in the example. It should be understood that process 500 can be considered as... Figure 2A A more specific example of process 200A.

[0197] At 510, UE 501 sends an LPP / RRC message to LMF / Serving gNB 502. The LPP / RRC message requests reference signaling configuration for data collection. The LPP / RRC message may include an indication to request PRS / SSB, additional reference signaling configuration area information for area-based data collection, or a combination of the above items.

[0198] At 520, the LMF / serving gNB 502 accordingly provides the requested PRS / SSB / other reference signaling configuration to the UE 501. If the area information at 510 is provided for area-based data collection, the LMF / serving gNB 502 can coordinate with other gNBs 503 within that area to collect the requested PRS / SSB / other reference signaling configuration within that area. At 515, after receiving an LPP / RRC message, the LMF / serving gNB 502 can forward the information included in the LPP / RRC message to other gNBs 503. The LMF can request PRS / SSB / other reference signaling configuration from other gNBs 503 via an NRPPa message. The serving gNB can request PRS / SSB / other reference signaling configuration from other gNBs 503 via an Xn AP message. LMF / Service gNB 502 can also indicate area information for area-based data collection, so that other gNBs 503 will provide the PRS / SSB / other reference signaling configurations for that area accordingly.

[0199] Based on the configuration provided by LMF / Serving gNB 502, UE 501 begins measuring PRS / SSB / other reference signaling.

[0200] In summary, for UE-side model training for AI-based positioning, in order to perform training data collection for AI-based positioning that takes mobility into account, training data collection is performed by the UE itself with the assistance of the LMF or the serving gNB.

[0201] Figure 6 Another example process 600 according to various aspects of this disclosure is illustrated. Process 600 may involve UE 601, serving gNB 602, and other gNBs 603. Figure 6 UE 601 in the context can be Figure 1 UE 104 or Figure 2A Example of user equipment 201 in the example. Figure 6 The service gNB 602 in the middle can be Figure 1 Example of network entity 102 in the example. Other gNB 603 can be... Figure 1 Example of network entity 102 in the example.

[0202] In procedure 600, it is assumed that UE 601 is configured by serving gNB 602 to perform training data collection and training data collection reporting for AIML model training based on AI CSI / BM. After handover and detachment of UE 601 from serving gNB 602, training data for records that have not yet been sent to serving gNB 602 may be cached in UE 601.

[0203] At position 610, serving gNB 602 sends a data collection configuration to UE 601, and the data collection configuration includes an instruction not to discard collected data after handover. Serving gNB 602 generates... RRCReconfiguration The message (i.e., the data collection configuration) is sent to UE 601 to configure UE 601 to perform L1 / L3 measurement recording and report the recorded measurement instances to serving gNB 602 via RRC signaling. Alternatively, if the training data collected from UE 601 will eventually be sent to OAM, the data collection configuration may also include tracking information, such as tracking references or tracking recording session references.

[0204] At 615, for inter-gNB handover, the serving gNB 602, for example, sends a handover request message to other gNBs 603 using the New Xn Application Protocol (XnAP) Information Element (IE) in the handover request message. The handover request message includes an indication that UE 601 has been configured to collect L1 / L3 measurements and report them to the serving gNB 602. The other gNBs 603 can then understand that UE 601 may have some recorded L1 / L3 measurements in its buffer, which is useful to the source gNB 602. Alternatively, if the training data collected from UE 601 will eventually be sent to the OAM, the handover request message may also include tracking information.

[0205] At point 620, after receiving the handover request message from serving gNB 602, other gNBs 603 send a handover request confirmation to serving gNB 602.

[0206] At 625, UE 601 initiates a random access procedure to switch to another gNB 603.

[0207] At 630, after connecting to another gNB 603, the other gNB 603 generates a UE Information Request message and sends it to the UE. This UE Information Request message includes an indication requesting any recorded L1 / L3 measurement results that the UE has not yet sent. Additionally or alternatively, before receiving the UE Information Request message (i.e., before 630), the UE 601 may indicate to the other gNB 603 via signaling that the recorded measurements are available on the UE 601 side.

[0208] At 635, if any L1 / L3 measurement records are available at UE 601, UE 601 generates a UE Information Response message and sends it to the other gNB 603. The UE Information Response message includes the L1 / L3 measurements for the records that have not yet been sent. Alternatively, if tracking information is sent at 610, the UE Information Response message may also include associated tracking information, such as a tracking reference or a tracking record session reference.

[0209] At 640, for inter-gNB handover, i.e., when another gNB 603 is different from the serving gNB 602, the other gNB 603 sends the received L1 / L3 measurements of the records to the serving gNB 602 via an XnAP message. Alternatively, the other gNB 603 may send the received L1 / L3 measurements of the records and associated tracking information to the OAM.

[0210] Alternatively, if the recorded L1 / L3 measurements buffered at UE 601 are not retrieved by other gNB 603 after a handover to another gNB 603, UE 601 will discard the recorded L1 / L3 measurements after a certain time period.

[0211] In summary, to address the training data reporting interruption issue caused by UE mobility, when a UE is configured by the serving gNB to measure, record, and report certain L1 / L3 measurements to the serving gNB in ​​RRC connected state, and if the UE has already recorded measurements in its buffer that have not yet been sent to the serving gNB during handover, the UE will retain the recorded measurements (i.e., not discard them) and send them to the other gNB after handover. The other gNB can also forward the recorded measurements from the UE to the (old) serving gNB or OAM.

[0212] Figure 7 Another example process 700 according to various aspects of this disclosure is illustrated. Process 700 may involve UE 701, source gNB 702, and target gNB 703. Figure 7 UE 701 in the text can be Figure 1 Example of UE 104 in the example. Figure 7 The source gNB 702 in the middle can be Figure 1 Network entity 102 or Figure 2B Example of the second network device 203 in the example. The target gNB 703 can be Figure 1 Network entity 102 or Figure 2B An example of the third network device 204. It should be understood that process 700 can be considered as... Figure 2B A more specific example of process 200B.

[0213] At 710, the source gNB 702 sends a data collection request message to the target gNB 703 to trigger a data collection report initiation process. The data collection request message includes an indication that the target gNB 703 is requesting L1 / L3 beam measurements after a handover. The data collection request message may also include: at least one measurement ID, i.e., at least one ID for at least one beam measurement; the duration for which the target gNB 703 should configure the UE 701 to measure / record / report L1 / L3 beam measurements; the reporting period; the period for measurement / recording instances; information related to the specific beam to be measured, such as the SSB index; information related to the type of measurement, such as the top K beam indices, or the RSRP of the top K beams, or the RSCP of all available beams, or the RSMP of the specific beam; or any combination of two or more of the above items.

[0214] At point 715, if the data collection request is accepted by the target gNB 703, the target gNB 703 sends a data collection response message to the source gNB 702.

[0215] At 720, after deciding to hand over UE 701 to target gNB 703, source gNB 702 sends a handover request message to target gNB 703. The handover request message includes at least one measurement ID, UE ID, target cell ID, a list of possible best-predicted beams, additional information about the beam to be measured after the handover, or any combination of two or more of the above items.

[0216] The target gNB 703 can use the predicted optimal beam to configure UE 701 to initiate random access to the target gNB 703 via the optimal beam. At 725, the target gNB 703 sends a handover request confirmation message to the source gNB 702. The handover request confirmation message generated by the target gNB 703 may include RRC reconfiguration for UE 701 to perform handover, and the target gNB 703 can configure UE 701 to measure a specific beam.

[0217] At 730, the source gNB 702 forwards the RRC reconfiguration to UE 701. At 735, UE 701 performs random access to the target gNB 703. At 740, after a successful handover, UE 701 performs L1 / L3 beam measurements, records the L1 / L3 beam measurements, and sends an L1 or L3 message including the L1 / L3 beam measurement results to the target gNB 703 according to the configuration.

[0218] At position 745, the target gNB 703 sends a data collection update message to the source gNB 702. The data collection message may include L1 / L3 beam measurements requested after a handover. The data collection message may also include at least one measurement ID, UE ID, or a combination of the above.

[0219] In summary, when the source gNB collects training data for optimal beam prediction used in handover decisions, for inter-gNB handovers, the source gNB will pre-configure a data collection request associated with a measurement ID to request the target gNB to provide the requested specific L1 / L3 beam measurements for the UE to be handed over after a successful handover. The target gNB can configure the UE to measure the requested L1 / L3 beam measurements accordingly after the handover and send the measurement results back to the source gNB.

[0220] Figure 8 Another example process 800 according to various aspects of this disclosure is illustrated. Process 800 may involve a source gNB 801 and a target gNB 802. Figure 8 The source gNB 801 in the middle can be Figure 1 Network entity 102 or Figure 2B Example of the second network device 203 in the example. The target gNB 802 can be Figure 1 Network entity 102 or Figure 2B An example of the third network device 204. It should be understood that process 800 can be considered as... Figure 2B A more specific example of process 200B.

[0221] At point 810, prior to the UE handover, the target gNB 802 triggers a data collection report initiation procedure and sends a data collection request message to the source gNB 801. The data collection request message includes at least one measurement ID, a request for L1 / L3 beam measurements prior to the handover, or a combination of the above.

[0222] At point 815, if the source gNB 801 accepts the data collection request, then the source gNB 801 sends a data collection response message to the target gNB 802.

[0223] At point 820, after deciding to hand over the UE to the target gNB 802, the source gNB 801 sends a handover request message to the target gNB 802. The handover request message includes the UE ID, the target cell ID, and the requested historical L1 / L3 beam measurements.

[0224] At position 825, the target gNB 802 sends a handover request confirmation message to the source gNB 801.

[0225] In summary, the target gNB can collect training data from the source gNB to perform optimal beam prediction. In the initial phase after the handover execution, the optimal beam prediction can be used for service beam selection.

[0226] Figure 9 An example of a device 900 supporting data collection according to various aspects of this disclosure is illustrated. Device 900 may be an example of a user equipment 201, a first network device 202, a second network device 203, or a third network device 204 as described herein. Device 900 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 900 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 902, memory 904, transceiver 906, and optional I / O controller 908). These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., a bus).

[0227] Processor 902, memory 904, transceiver 906, or various combinations thereof, or various components thereof, may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 902, memory 904, transceiver 906, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0228] In some implementations, processor 902, memory 904, transceiver 906, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 902 and memory 904 coupled to processor 902 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 904 by processor 902).

[0229] For example, according to the examples disclosed herein, processor 902 may support wireless communication at device 900. Processor 902 may be configured to operate to support: means for receiving from a first network device at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and means for performing measurements on a reference signal associated with the data collection for model training based on the at least one measurement configuration. Processor 902 may be configured to operate to support means for other implementations of method 1100.

[0230] For example, according to the examples disclosed herein, processor 902 may support wireless communication at device 900. Processor 902 may be configured to support: means for receiving from a first network device at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and means for transmitting to a user equipment at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and means for receiving collected data from the user equipment. Processor 902 may be configured to support means for other implementations of method 1200.

[0231] For example, according to the examples disclosed herein, processor 902 may support wireless communication at device 900. Processor 902 may be configured to operate to support: means for receiving from a first network device at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and means for sending a handover request to a third network device, the handover request including first information associated with data collection for beam prediction, wherein the second and third network devices are located in an area where the user equipment performs data collection; and means for receiving a handover response from the third network device, the handover response including Radio Resource Control (RRC) configuration for the handover process. Processor 902 may be configured to operate to support other implementations of method 1300.

[0232] For example, according to the examples disclosed herein, processor 902 may support wireless communication at device 900. Processor 902 may be configured to operate to support: means for receiving from a first network device at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and means for receiving from a second network device a handover request, the handover request including first information associated with data collection for beam prediction, wherein the second and third network devices are located in an area where the user equipment performs data collection; and means for sending a handover response to the second network device, the handover response including Radio Resource Control (RRC) configuration for the handover procedure. Processor 902 may be configured to operate to support other implementations of method 1400.

[0233] Processor 902 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 902 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 902. Processor 902 may be configured to execute computer-readable instructions stored in memory (e.g., memory 904) to cause device 900 to perform various functions of this disclosure.

[0234] Memory 904 may include random access memory (RAM) and read-only memory (ROM). Memory 904 may store computer-readable, computer-executable code, including instructions that, when executed by processor 902, cause device 900 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 902, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 904 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0235] I / O controller 908 can manage the input and output signals of device 900. I / O controller 908 can also manage peripheral devices not integrated into device 900. In some implementations, I / O controller 908 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 908 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, Linux®, or other known operating systems. In some implementations, I / O controller 908 can be implemented as part of a processor, such as processor 902. In some implementations, a user can interact with device 900 via I / O controller 908 or via hardware components controlled by I / O controller 908.

[0236] In some implementations, device 900 may include a single antenna 910. However, in other implementations, device 900 may have more than one antenna 910 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 906 may communicate bidirectionally via one or more antennas 910, wired or wireless links, as described herein. For example, transceiver 906 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 906 may also include a modem for modulating packets, providing modulated packets to one or more antennas 910 for transmission, and demodulating packets received from one or more antennas 910. Transceiver 906 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0237] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 910 for transmitting the amplified signal into the air or wireless medium.

[0238] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 910 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0239] Figure 10 An example of a processor 1000 supporting data collection according to various aspects of this disclosure is illustrated. The processor 1000 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 1000 may include a controller 1002 configured to perform various operations according to the examples described herein. The processor 1000 may optionally include at least one memory 1004. Additionally or alternatively, the processor 1000 may optionally include one or more arithmetic logic units (ALUs) 1000. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0240] Processor 1000 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 1000)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0241] Controller 1002 can be configured to manage and coordinate various operations of processor 1000 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1000 to support various operations according to the examples described herein. For example, controller 1002 can operate as a control unit of processor 1000 to generate control signals for managing the operation of various components of processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0242] Controller 1002 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 1004 and determine subsequent instructions(s) to be executed, enabling processor 1000 to support various operations according to the examples described herein. Controller 1002 may be configured to track the memory addresses of instructions associated with memory 1004. Controller 1002 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1002 may be configured to interpret instructions and determine control signals to be output to other components of processor 1000, enabling processor 1000 to support various operations according to the examples described herein. Additionally or alternatively, controller 1002 may be configured to manage data flow within processor 1000. Controller 1002 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1000.

[0243] Memory 1004 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., local to or included in processor 1000). In some implementations, memory 1004 may reside within or on the processor chipset (e.g., local to processor 1000). In some other implementations, memory 1004 may reside outside the processor chipset (e.g., remote from processor 1000).

[0244] Memory 1004 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1000, cause processor 1000 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 1002 and / or processor 1000 may be configured to execute computer-readable instructions stored in memory 1004 to cause processor 1000 to perform various functions (e.g., functions or tasks for supporting transmit power priority). For example, processor 1000 and / or controller 1002 may be coupled to or coupled to memory 1004, and processor 1000, controller 1002, and memory 1004 may be configured to perform the various functions described herein. In some examples, processor 1000 may include multiple processors, and memory 1004 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0245] One or more ALU 1000s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 1000s may reside within or on a processor chipset (e.g., processor 1000). In some other implementations, one or more ALU 1000s may reside outside the processor chipset (e.g., processor 1000). One or more ALU 1000s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1000s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 1000s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Additionally or alternatively, one or more ALU 1000s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 1000s to handle conditional operations, comparisons, and bitwise operations.

[0246] Based on the examples disclosed herein, processor 1000 may support wireless communication. Processor 1000 may be configured or operable to support: means for receiving from a first network device at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and means for performing measurements on reference signals associated with the data collection for model training based on the at least one measurement configuration.

[0247] Figure 11A flowchart illustrating a method 1100 for supporting data collection according to various aspects of this disclosure is shown. Operation of method 1100 may be implemented by the device or components thereof described herein. For example, operation of method 1100 may be performed by the UE 104 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0248] At 1105, the method includes: receiving from a first network device at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training. The operation of 1105 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1105 can be derived from references... Figure 1 The device described in A is used to perform this action.

[0249] At 1110, the method includes performing a measurement on a reference signal associated with data collection used for model training, based on at least one measurement configuration. The operation of 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1110 can be derived from the reference... Figure 1 The device described in A is used to perform this action.

[0250] In some embodiments, at least one measurement configuration may include one of the following: a type of reference signal; resource information for the reference signal; a type of ground truth; validity information indicating the validity time of a data collection session; or area information indicating the area in which the user equipment performs data collection.

[0251] In some embodiments, the area information may include one of the following: one or more identifiers (IDs) of one or more cells; one or more IDs of one or more regions associated with geographic coordinates; one or more IDs of one or more regions associated with a cell list; one or more Tracking Area Codes (TACs) associated with a cell list; or one or more Tracking Area Identifiers (TAIs) associated with a cell list.

[0252] In some embodiments, the method may further include sending first information via a transceiver to a second network device in at least one network device, indicating that a data collection session has been triggered, wherein the second network device serves the user equipment.

[0253] In some embodiments, the first information may include one of the following: an indication that the data collection session is triggered by a first network device; the data collection session is executed via a Long Term Evolution (LTE) Positioning Protocol (LPP) message on the control plane (CP); the data collection session is executed via an LPP message on the user plane (UP); area information indicating the area in which the user equipment performs data collection; or validity information indicating the validity period of the data collection session.

[0254] In some embodiments, the first information may be transmitted via a Radio Resource Control (RRC) message.

[0255] In some embodiments, the method may further include receiving a first configuration of the radio bearer of the user equipment from a second network device.

[0256] In some embodiments, the method may further include sending a first request for at least one measurement configuration to either a second network device or a first network device.

[0257] In some embodiments, the method may further include receiving at least one measurement configuration from a second network device, wherein in response to receiving a first request from the second network device, one or more of the at least one measurement configurations are sent by one or more network devices other than the second network device.

[0258] In some embodiments, the first request may include one of the following: the type of reference signal requested by the user equipment; validity information indicating the validity period of the data collection session; or area information indicating the area in which the user equipment performs data collection.

[0259] In some embodiments, the method may further include receiving a second configuration of the radio bearer of the user equipment from a second network device, wherein the second configuration is transmitted by a third network device among at least one network device via a handover response.

[0260] In some embodiments, when a third network device receives a handover request from a second network device to switch the user equipment to the third network device, a second configuration may be sent.

[0261] In some embodiments, a handover request may include one of the following: an indication that a data collection session is triggered by a first network device; a data collection session being executed via an LPP message on a CP; a data collection session being executed via an LPP message on a UP; area information indicating the area in which the user equipment performs data collection; or validity information indicating the validity period of the data collection session.

[0262] In some embodiments, one of the first configuration or the second configuration may include one of the following: a signaling radio bearer (SRB) configured for the user equipment when the data collection session is executed via an LPP message on the CP; or a data radio bearer (DRB) configured for the user equipment when the data collection session is executed via an LPP message on the UP.

[0263] In some embodiments, the method may further include sending collected data to a first network device via a transceiver.

[0264] In some embodiments, if the user equipment is located in the area after a switch to a third network device, the collected data can be sent to the first network device.

[0265] In some embodiments, the method may further include receiving a third configuration from a second network device, the third configuration being used to send collected data for model training associated with artificial intelligence / machine learning (AI / ML) based localization, channel state information compression, channel state information prediction, or beam prediction.

[0266] In some embodiments, the third configuration includes one of the following: a period for sending collected data; a period for recording measurements; an event that triggers the sending of collected data; an event that triggers the recording of measurements; an indication that the user equipment will not discard collected data that has not yet been sent; or tracking information including a tracking reference or a tracking recording session reference.

[0267] In some embodiments, the switching request may also include one of the following: an indication that the user equipment is configured not to discard collected data that has not yet been sent; or tracking information.

[0268] In some embodiments, the method may further include receiving a second request from a third network device for collected data that has not yet been sent after a handover to the third network device.

[0269] In some embodiments, the method may further include sending to a third network device either collected data that has not yet been sent or tracking information associated with the collected data.

[0270] In some embodiments, collected data that has not yet been sent can also be sent from a third network device to a second network device.

[0271] In some embodiments, the method may further include discarding the collected data that has not yet been sent if the second request is not received within the time period.

[0272] In some embodiments, the time period may include one of the following: a pre-configured time period after the collected data is generated; the period of an inactive timer; or the period of a timer configured by a second network device.

[0273] Figure 12 A flowchart illustrating a method 1200 for supporting data collection according to various aspects of this disclosure is shown. Operation of method 1200 may be implemented by the device or components thereof described herein. For example, operation of method 1200 may be performed by the first network entity 102 or core network 106 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0274] At 1205, the method includes transmitting via a transceiver to a user equipment at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training. The operation of 1205 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1205 can be derived from references... Figure 1 The device described in A is used to perform this action.

[0275] At 1210, the method includes receiving collected data from the user equipment via a transceiver. The operation of 1210 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1210 can be found in the references. Figure 1 The device described in A is used to perform this action.

[0276] In some embodiments, at least one measurement configuration may include one of the following: the type of reference signal associated with positioning; resource information of the reference signal; the type of ground truth; validity information indicating the validity time of a data collection session; or area information indicating the area in which the user equipment performs data collection.

[0277] In some embodiments, the area information may include one of the following: one or more identifiers (IDs) of one or more cells; one or more IDs of one or more regions associated with geographic coordinates; one or more IDs of one or more regions associated with a cell list; one or more Tracking Area Codes (TACs) associated with a cell list; or one or more Tracking Area Identifiers (TAIs) associated with a cell list.

[0278] In some embodiments, the method may further include sending first information via a transceiver to a second network device in at least one network device, indicating that a data collection session has been triggered, wherein the second network device serves the user equipment.

[0279] In some embodiments, the first information may include one of the following: an indication that the data collection session is triggered by a first network device; the data collection session is executed via a Long Term Evolution (LTE) Positioning Protocol (LPP) message on the control plane (CP); the data collection session is executed via an LPP message on the user plane (UP); area information indicating the area in which the user equipment performs data collection; or validity information indicating the validity period of the data collection session.

[0280] In some embodiments, the method may further include sending a first request via a transceiver to at least one network device for at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; and receiving at least one measurement configuration from at least one network device.

[0281] In some embodiments, the method may further include receiving a request for at least one measurement configuration from a user equipment via a transceiver.

[0282] In some embodiments, the request may include one of the following: the type of reference signal requested by the user equipment; validity information indicating the validity period of the data collection session; or area information indicating the area in which the user equipment performs data collection.

[0283] In some embodiments, the first information may be sent via New Radio (NR) Positioning Protocol A (NRPPa) messages.

[0284] Figure 13 A flowchart illustrating a method 1300 for supporting data collection according to various aspects of this disclosure is shown. Operation of method 1300 may be implemented by the device or components thereof described herein. For example, operation of method 1300 may be performed by the second network entity 103 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0285] At 1305, the method includes sending a handover request to a third network device via a transceiver. The handover request includes first information associated with data collection for beam prediction, wherein the second and third network devices are located in the area where the user equipment performs data collection. The operation of 1305 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1305 can be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0286] At 1310, the method includes receiving a handover response from a third network device, the handover response including Radio Resource Control (RRC) configuration for the handover procedure. The operation of 1310 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1310 can be found in references... Figure 1 The aforementioned device is used to perform this action.

[0287] In some embodiments, the method may further include sending a first request associated with data collection of the user equipment to a third network device via a transceiver.

[0288] In some embodiments, the first request may include one of the following: requesting a third network device to provide an indication of beam measurement for the user equipment after the user equipment switches from the second network device to the third network device; an identifier (ID) for the beam measurement; a duration for the user equipment to perform the beam measurement; a duration for the user equipment to record the beam measurement; a duration for the user equipment to transmit the beam measurement; a period for performing the beam measurement; a period for recording the beam measurement; a period for transmitting the beam measurement; second information associated with at least one beam requested to be measured by the second network device; or the type of beam measurement requested by the second network device.

[0289] In some embodiments, the type may include one of the following: an index of a first number of beams with a strong reference signal received power (RSRP) among a plurality of beams of a third network device; or an index of one or more beams with one or more RSRPs above a first threshold.

[0290] In some embodiments, the first information may include one of the following: a beam measurement identifier (ID); the ID of the target cell to which the user equipment is to switch; or third information for beam prediction.

[0291] In some embodiments, the third information for beam prediction may include one of the following: an index associated with the beam predicted to have the strongest RSRP among a plurality of beams of the second network device; a list of a second number of beams with relatively strong RSRP among a plurality of beams of the second network device; a list of at least one beam predicted to have at least one RSRP above a second threshold; at least one value indicating the probability of being associated with at least one predicted beam; at least one predicted beam measurement associated with at least one predicted beam; or a predicted value of the dwell time of at least one predicted beam.

[0292] In some embodiments, the first information may further include one of the following: second information if the first request does not include second information associated with at least one beam to be measured; or the type of beam measurement if the first request does not include the type of beam measurement.

[0293] In some embodiments, the RRC configuration may include one of the following: a first configuration for a user equipment to perform random access to a target cell using a predicted beam with the strongest RSRP among a plurality of beams of a third network device; a second configuration for a user equipment to perform beam measurements based on a handover request and a first request; a third configuration for a user equipment to record beam measurements based on a handover request and a first request; or a fourth configuration for a user equipment to transmit beam measurements based on a handover request and a first request.

[0294] In some embodiments, the method may further include sending RRC configuration to the user equipment via a transceiver; and receiving beam measurements from the third network device via a transceiver after the user equipment switches from the second network device to the third network device.

[0295] In some embodiments, the method may further include receiving a second request associated with data collection of a user equipment from a third network device via a transceiver.

[0296] In some embodiments, the second request may include one of the following: requesting the second network device to provide an indication of historical beam measurements of the user equipment after the user equipment switches from the second network device to the third network device; a duration during which the second network device is requested to provide historical beam measurements before the user equipment switches from the second network device to the third network device; the type of historical beam measurements requested by the third network device; the ID of the target cell from which the user equipment wants to switch; or the ID of the source cell from which the user equipment wants to switch.

[0297] In some embodiments, historical beam measurements may be sent to a third network device via a handover request; or historical beam measurements may be sent to a third network device after the handover is completed.

[0298] In some embodiments, the first information may further include one of the following: a timestamp of a historical beam measurement; or the dwell time value of one or more beams in a historical beam measurement.

[0299] Figure 14 A flowchart illustrating a method 1400 for supporting data collection according to various aspects of this disclosure is shown. Operation of method 1400 may be implemented by the device or components thereof described herein. For example, operation of method 1400 may be performed by a third network entity 104 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0300] At 1405, the method includes receiving a handover request from a second network device via a transceiver. The handover request includes first information associated with data collection for beam prediction, wherein the second and third network devices are located in an area where the user equipment performs data collection. The operation of 1405 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1405 can be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0301] At 1410, the method includes sending a handover response to a second network device via a transceiver, the handover response including Radio Resource Control (RRC) configuration for the handover procedure. The operation of 1410 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1410 can be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0302] In some embodiments, the method may further include receiving a first request associated with data collection of a user equipment from a third network device via a transceiver.

[0303] In some embodiments, the first request may include one of the following: requesting a third network device to provide an indication of beam measurement for the user equipment after the user equipment switches from the second network device to the third network device; an identifier (ID) for the beam measurement; a duration for the user equipment to perform the beam measurement; a duration for the user equipment to record the beam measurement; a duration for the user equipment to transmit the beam measurement; a period for performing the beam measurement; a period for recording the beam measurement; a period for transmitting the beam measurement; second information associated with at least one beam requested to be measured by the second network device; or the type of beam measurement requested by the second network device.

[0304] In some embodiments, the type may include one of the following: an index of a first number of beams having a strong reference signal received power (RSRP) among a plurality of beams of a third network device; an index of one or more beams having one or more RSRPs higher than a first threshold; the RSRP of one or more beams; the RSRP of an available beam for beam measurement; or the RSRP of a beam indicated by a second network device.

[0305] In some embodiments, the first information may include one of the following: a beam measurement identifier (ID); the ID of the target cell to which the user equipment is to switch; or third information on beam prediction requested by a second network device.

[0306] In some embodiments, the third information for beam prediction may include one of the following: an index associated with the beam predicted to have the strongest RSRP among a plurality of beams of the third network device; a list of at least one beam predicted to have at least one RSRP above a second threshold; at least one value indicating the probability of being associated with at least one predicted beam; at least one predicted beam measurement associated with at least one predicted beam; or a predicted value of the dwell time of at least one predicted beam.

[0307] In some embodiments, the switching response may further include one of the following: second information if the first request does not include second information associated with at least one beam to be measured; or type of beam measurement if the first request does not include the type of beam measurement.

[0308] In some embodiments, the RRC configuration may include one of the following: a first configuration for a user equipment to perform random access to a target cell using a predicted beam with the strongest RSRP among a plurality of beams of a third network device; a second configuration for a user equipment to perform beam measurements based on a handover request and a first request; a third configuration for a user equipment to record beam measurements based on a handover request and a first request; or a fourth configuration for a user equipment to transmit beam measurements based on a handover request and a first request.

[0309] In some embodiments, the method may further include receiving beam measurements from the user equipment via a transceiver after the user equipment switches from a second network device to a third network device; and transmitting beam measurements to the second network device via a transceiver.

[0310] In some embodiments, the method may further include sending a second request associated with data collection of the user equipment to a second network device via a transceiver.

[0311] In some embodiments, the second request includes one of the following: requesting the second network device to provide an indication of historical beam measurements of the user equipment after the user equipment switches from the second network device to the third network device; duration, wherein the second network device is requested to provide historical beam measurements during the duration prior to the user equipment switching from the second network device to the third network device; type of historical beam measurements requested by the third network device; ID of the target cell from which the user equipment wants to switch; or ID of the source cell from which the user equipment wants to switch.

[0312] In some embodiments, historical beam measurements may be sent to a third network device via a handover request; or historical beam measurements may be sent to a third network device after the handover is completed.

[0313] In some embodiments, the first information may further include one of the following: a timestamp of historical beam measurements; or a value of the dwell time of one or more beams in historical beam measurements. It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods may be combined.

[0314] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0315] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0316] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0317] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0318] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: Receive from a first network device via the transceiver at least one measurement configuration determined by at least one network device, wherein the at least one measurement configuration is associated with data collection for model training; as well as Based on the at least one measurement configuration, measurements are performed on the reference signal associated with the data collection used for model training.

2. The user equipment according to claim 1, wherein the at least one measurement configuration includes one of the following: The type of the reference signal; Resource information used for the reference signal; The type of ground truth value; Validity information indicating the validity period of the session in which the data was collected; or The area information indicating the region in which the user equipment performs the data collection.

3. The user equipment according to claim 1, wherein the processor is further configured to: The transceiver sends a first message to a second network device among the at least one network device, indicating that the data collection session has been triggered, via the transceiver, wherein the second network device serves the user equipment.

4. The user equipment according to claim 3, wherein the first information includes one of the following: The data collection session was triggered by an indication from the first network device; The data collection session is performed via Long Term Evolution LTE Location Protocol (LPP) messages on the control plane (CP). The data collection session is performed via LPP messages on the user plane UP; Regional information indicating the area in which the user equipment performs the data collection; or The validity information indicates the validity period of the session for which the data is collected.

5. The user equipment according to claim 1, wherein the processor is further configured to: The user equipment receives a second configuration for the radio bearer from the second network device, wherein the second configuration is transmitted by a third network device among the at least one network device via a handover response.

6. The user equipment according to claim 5, wherein the second configuration is sent when the third network device receives a handover request from the second network device to hand over the user equipment to the third network device.

7. The user equipment of claim 6, wherein the handover request includes one of the following: The data collection session was triggered by an indication from the first network device; The data collection session is executed via LPP messages on the CP; The data collection session is executed via LPP messages on the UP; Regional information indicating the area in which the user equipment performs the data collection; or The validity information indicates the validity period of the session for which the data is collected.

8. The user equipment of claim 5, wherein one of the first configuration or the second configuration includes one of the following: The signaling radio bearer SRB configured for the user equipment when the session of the data collection is executed via LPP messages on the CP; or The data radio bearer (DRB) configured for the user equipment when the session for data collection is executed via an LPP message on the UP.

9. The user equipment according to claim 1, wherein the processor is further configured to: The collected data is sent to the first network device via the transceiver.

10. The user equipment of claim 9, wherein, if the user equipment is in the area after a handover to the third network device, the collected data is sent to the first network device.

11. The user equipment of claim 9, wherein the processor is further configured to: Receive a third configuration from the second network device, the third configuration being used to send the collected data for model training associated with AI / ML-based localization, channel state information compression, channel state information prediction, or beam prediction.

12. The user equipment of claim 11, wherein the third configuration comprises one of the following: The period for sending the collected data; Used to record the period of the measurement; The event that triggers the sending of the collected data; The event that triggers the recording of the measurement; The user equipment will not discard the instruction to collect data that has not yet been sent; or This includes tracking information such as tracking references or tracking record session references.

13. The user equipment of claim 12, wherein the handover request further comprises one of the following: The user equipment is configured not to discard an indication that the collected data has not yet been transmitted; or The tracking information.

14. The user equipment of claim 11, wherein the processor is further configured to: Receive a second request from the third network device for the collected data that has not yet been sent after the handover to the third network device.

15. A first network device, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: The transceiver transmits at least one measurement configuration determined by at least one network device to the user equipment, wherein the at least one measurement configuration is associated with data collection for model training; as well as The transceiver receives the user equipment's collected data from the user equipment.

16. A second network device, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: A handover request is sent to a third network device via the transceiver. The handover request includes first information associated with data collection for beam prediction, wherein the second network device and the third network device are located in the area where the user equipment performs data collection. as well as The handover response is received from the third network device, the handover response including Radio Resource Control (RRC) configuration for the handover process.

17. The second network device of claim 16, wherein the processor is further configured to: A first request related to the data collection of the user equipment is sent to the third network device via the transceiver.

18. The second network device of claim 17, wherein the first request includes one of the following: The third network device is requested to provide an indication of beam measurement for the user equipment after the user equipment switches from the second network device to the third network device; The identification ID of the beam measurement; The duration for which the user equipment performs the beam measurement; Used by the user equipment to record the duration of the beam measurement; The duration for which the user equipment transmits the beam measurement; The period used to perform the beam measurement; Used to record the period of the beam measurement; The period used to transmit the beam measurement; Second information associated with at least one beam that was requested to be measured by the second network device; or The type of beam measurement requested by the second network device.

19. The second network device according to claim 16, wherein the first information includes one of the following: The identification ID of the beam measurement; The ID of the target cell to which the user equipment needs to switch; or The third piece of information for beam prediction.

20. A third network device, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: A handover request is received from a second network device via the transceiver. The handover request includes first information associated with data collection for beam prediction, wherein the second network device and the third network device are located in the area where the user equipment performs data collection. as well as The handover response is sent to the second network device via the transceiver, the handover response including Radio Resource Control (RRC) configuration for the handover process.

Images