Devices and methods for data collection
The solution addresses data collection interruptions by implementing measurement configurations and wireless bearer adaptations across network devices, ensuring continuous data acquisition for AI/ML training, thereby improving communication performance in mobile user equipment scenarios.
Patent Information
- Application Number
- JP2026527452
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-11-10
- Publication Date
- 2026-11-19
AI Technical Summary
Existing data collection methods for AI/ML training in wireless communications fail to account for user equipment mobility, leading to interruptions and inefficiencies in data acquisition.
Implementing methods and devices that receive and transmit measurement configurations and configurations of wireless bearers across network devices, ensuring continuous data collection through handovers and beam prediction to maintain data acquisition during user equipment movement.
Ensures uninterrupted data collection for AI/ML training by adapting to user equipment mobility, enhancing communication performance and efficiency in wireless networks.
Smart Images

Figure 2026539096000001_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more particularly, to data collection. BACKGROUND ART
[0002] With the development of communication technologies, the introduction of artificial intelligence / machine learning (AI / ML) technologies has been advanced to optimize physical layer operations for several use cases. Examples include channel state information (CSI) feedback compression, CSI time domain prediction, beam spatial domain prediction, beam time domain prediction, AI / ML assisted positioning estimation, direct AI / ML positioning, and the like.
[0003] For AI-based positioning use cases, a location management function (LMF) collects training data from a user equipment (UE) to train an AI model, and the AI model may be an LMF-sided model or a UE-sided model. For AI-based CSI / beam management (BM) / positioning use cases, a gNB collects training data from a UE to train an AI model, and the AI model may be a gNB-sided model or a UE-sided model. However, data collection has several issues that need to be resolved. SUMMARY OF THE INVENTION PROBLEMS TO BE SOLVED BY THE INVENTION
[0004] The present disclosure relates to methods, apparatuses, and systems that support data collection, particularly data collection for AI / ML training that accounts for mobility. MEANS FOR SOLVING THE PROBLEMS
[0005] Some implementations of the methods and devices described herein include receiving from a first network device at least one measurement configuration determined by at least one network device, the at least one measurement configuration being associated with data acquisition for model training, and performing measurements on a reference signal associated with data acquisition for model training based on the at least one measurement configuration. In this way, data acquisition cannot be interrupted when user equipment moves across at least one network device.
[0006] Some implementations of the methods and devices described herein involve transmitting first information to a second network device among at least one network device indicating that a data collection session has been triggered, the second network device further including servicing and transmitting to user equipment.
[0007] Some implementations of the methods and devices described herein may further include transmitting first information via radio resource control (RRC) messages.
[0008] Some implementations of the methods and devices described herein may further include receiving a first configuration of a wireless bearer to user equipment from a second network device.
[0009] Some implementations of the methods and devices described herein may further include sending a first request to either a second network device or a first network device that requests at least one measurement configuration.
[0010] Some implementations of the methods and devices described herein include receiving at least one measurement configuration from a second network device, and further including receiving one or more of the at least one measurement configurations transmitted by one or more of the at least one network devices other than the second network device in response to receiving a first request from the second network device.
[0011] Some implementations of the methods and devices described herein include receiving a second configuration of a wireless bearer to user equipment from a second network device, the second configuration being transmitted by a third network device, of which at least one network device, via a handover response.
[0012] Some implementations of the methods and devices described herein may further include transmitting the collected data to a first network device.
[0013] Some implementations of the methods and devices described herein may further include receiving a third configuration from a second network device for transmitting collected data for training models related to artificial intelligence / machine learning (AI / ML) based positioning or channel state information compression, channel state information prediction, or beam prediction.
[0014] Some implementations of the methods and devices described herein may further include receiving a second request from a third network device for collected data that has not been transmitted after a handover to the third network device.
[0015] Some implementations of the methods and devices described herein may further include transmitting to a third network device either untransmitted collected data or trace information related to the collected data.
[0016] Some implementations of the methods and devices described herein may further include discarding untransmitted collected data if a second request is not received within a time period.
[0017] In some implementations of the methods and devices described herein, at least one measurement configuration may include one of the following: namely, the type of reference signal, resource information for the reference signal, the type of ground truth, effectiveness information indicating the effective time of the data acquisition session, or area information indicating the area in which the user equipment performs data acquisition.
[0018] In some implementations of the methods and devices described herein, 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 zones associated with geographic coordinates; one or more IDs of one or more areas associated with a list of cells; one or more tracking area codes (TACs) associated with a list of cells; or one or more tracking area identifiers (TAIs) associated with a list of cells.
[0019] In some implementations of the methods and devices described herein, the first information may include, namely, an instruction indicating that a data collection session is triggered by a first network device; an instruction indicating that a data collection session is performed on the control plane (CP) via Long-Term Evolution (LTE) Positioning Protocol (LPP) messages; an instruction indicating that a data collection session is performed on the user plane (UP) via LPP messages; area information indicating the area in which 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 devices described herein, the first requirement may include one of the following: the type of reference signal requested by the user device, validity information indicating the validity period of the data acquisition session, or area information indicating the area in which the user device performs data acquisition.
[0021] In some implementations of the methods and devices described herein, the second configuration may be transmitted when the third network device receives a handover request from the second network device requesting to hand over 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 instruction indicating that a data collection session is triggered by a first network device; an instruction indicating that a data collection session is performed on a CP via an LPP message; an instruction indicating that a data collection session is performed on a UP via an LPP message; 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 devices described herein, one of the first or second configurations may include, namely, a signaling radio bearer (SRB) configured for the user equipment when the data acquisition session is performed on the CP via LPP messages, or a data radio bearer (DRB) configured for the user equipment when the data acquisition session is performed on the UP via LPP messages.
[0024] In some implementations of the methods and devices described herein, the collected data may be transmitted to the first network device if the user device is in the area of the third network device after a handover to that network device.
[0025] In some implementations of the methods and devices described in this specification, the third configuration may include one of the following: a period for transmitting collected data, a period for logging measurements, an event that triggers transmission of collected data, an event that triggers logging of measurements, an indication that the user equipment does not discard untransmitted collected data, or trace information including a trace reference or a trace recording session reference.
[0026] In some implementations of the methods and devices described in this specification, the handover request may further include one of the following: an indication indicating that the user equipment is configured not to discard untransmitted collected data, or trace information.
[0027] In some implementations of the methods and devices described in this specification, the untransmitted collected data may be further transmitted from the third network device to the second network device.
[0028] In some implementations of the methods and devices described in this specification, the time period may include one of the following: a preconfigured time period after the collected data is generated, a period of an inactivity timer, or a period of a timer configured by the second network device.
[0029] Some implementations of the methods and devices described in this specification include 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 receiving collected data of the user equipment from the user equipment. In this way, data collection cannot be interrupted when the user equipment moves across the at least one network device.
[0030] Some implementations of the methods and devices described herein involve transmitting first information to a second network device among at least one network device indicating that a data collection session has been triggered, the second network device further including servicing and transmitting to user equipment.
[0031] Some implementations of the methods and devices described herein may further include transmitting a first request to at least one network device for at least one measurement configuration determined by the at least one network device, the at least one measurement configuration being associated with data acquisition for model training, and receiving at least one measurement configuration from the at least one network device.
[0032] Some implementations of the methods and devices described herein may further include receiving a request from the user's equipment for at least one measurement configuration.
[0033] In some implementations of the methods and devices described herein, at least one measurement configuration may include one of the following: namely, the type of reference signal related to positioning, resource information for the reference signal, the type of ground truth, validity information indicating the validity period of the data acquisition session, or area information indicating the area in which the user equipment performs data acquisition.
[0034] In some implementations of the methods and devices described herein, 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 zones associated with geographic coordinates; one or more IDs of one or more areas associated with a list of cells; one or more tracking area codes (TACs) associated with a list of cells; or one or more tracking area identifiers (TAIs) associated with a list of cells.
[0035] In some implementations of the methods and devices described herein, the first information may include, namely, an instruction indicating that a data collection session is triggered by a first network device; that the data collection session is performed on the control plane (CP) via Long-Term Evolution (LTE) Positioning Protocol (LPP) messages; that the data collection session is performed on the user plane (UP) via LPP messages; 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 requirements may include one of the following: the type of reference signal requested by the user device, validity information indicating the validity period of the data acquisition session, or area information indicating the area in which the user device performs data acquisition.
[0037] In some implementations of the methods and devices described herein, the first information may be transmitted via a New Radio (NR) Positioning Protocol A (NRPPa) message.
[0038] Some implementations of the methods and devices described herein include transmitting a handover request to a third network device, which includes first information relating to data acquisition for beam prediction, the second and third network devices being located in the area where user equipment performs data acquisition, and receiving a handover response from the third network device, which includes a radio resource control (RRC) configuration for the handover procedure. In this way, beam prediction may be used for the handover procedure to improve communication performance.
[0039] Some implementations of the methods and devices described herein may further include transmitting a first request relating to data collection from user equipment to a third network device.
[0040] Some implementations of the methods and devices described herein may further include transmitting the RRC configuration to the user equipment and receiving beam measurements from a third network device after the user equipment has been handed over from the second network device to the third network device.
[0041] Some implementations of the methods and devices described herein may further include receiving a second request from a third network device relating to data collection from user equipment.
[0042] In some implementations of the methods and devices described herein, the first requirement may include, namely, an instruction requesting the third network device to provide beam measurements of the user equipment after the user equipment has been handed over from a second network device to a third network device, a beam measurement identifier (ID), the duration for which the user equipment performs the beam measurement, the duration for which the user equipment logs the beam measurement, the duration for which the user equipment transmits the beam measurement, the period for which the beam measurement is performed, the period for which the beam measurement is logged, the period for which the beam measurement is transmitted, second information relating to at least one beam requested to be measured by the second network device, or one of the types of beam measurements requested by the second network device.
[0043] In some implementations of the methods and devices described herein, the type may include, namely, one of a first number of beam indices having a stronger reference signal received power (RSRP) among a plurality of beams of a third network device, or one or more beam indices having one or more RSRPs higher than a first threshold of a second network device.
[0044] In some implementations of the methods and devices 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 instrument will be handed over, or a third piece of beam prediction information.
[0045] In some implementations of the methods and devices described herein, the third beam prediction information 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 second network device; a list of a second number of beams having stronger RSRPs among a plurality of beams of a second network device; a list of at least one beam predicted to have at least one RSRP higher than a second threshold; at least one value representing the likelihood 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 residence time of at least one predicted beam.
[0046] In some implementations of the methods and devices described herein, the first information may further include, namely, second information relating to at least one beam to be measured when the first requirement does not include the second information, or one of the types of beam measurement when the first requirement does not include the type.
[0047] In some implementations of the methods and devices described herein, the RRC configuration may include one of the following: a first configuration for user equipment to perform random access to a target cell using the predicted beam having the strongest RSRP among multiple beams of a third network device; a second configuration for user equipment to perform beam measurements based on a handover request and a first request; a third configuration for user equipment to log beam measurements based on a handover request and a first request; or a fourth configuration for user equipment to transmit beam measurements based on a handover request and a first request.
[0048] In some implementations of the methods and devices described herein, the second requirement may include, namely, an instruction requesting the second network device to provide past beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, a duration for which the second network device is requested to provide past beam measurements within that duration before the user equipment has been handed over from the second network device to the third network device, the type of past beam measurements requested by the third network device, the ID of the target cell to which the user equipment is handed over, or the ID of the source cell from which the user equipment is handed over.
[0049] In some implementations of the methods and devices described herein, past beam measurements may be transmitted to a third network device via a handover request, or past beam measurements may be transmitted to a third network device after the handover has been completed.
[0050] In some implementations of the methods and devices described herein, the first information may further include, namely, a timestamp of a past beam measurement, or one of the values of the residence time of one or more beams of a past beam measurement.
[0051] Some implementations of the methods and devices described herein include receiving a handover request from a second network device, which includes first information relating to data acquisition for beam prediction, wherein the second and third network devices are located in an area where user equipment performs data acquisition, and transmitting a handover response to the second network device, which includes a radio resource control (RRC) configuration for the handover procedure. In this way, data acquisition cannot be interrupted when user equipment moves across at least one network device.
[0052] Some implementations of the methods and devices described herein may further include receiving a first request from a third network device relating to data collection from user equipment.
[0053] Some implementations of the methods and devices described herein may further include receiving beam measurements from a user device after the user device has been handed over from a second network device to a third network device, and transmitting beam measurements to the second network device.
[0054] Some implementations of the methods and devices described herein may further include transmitting a second request relating to data collection from user equipment to a second network device.
[0055] In some implementations of the methods and devices described herein, the first requirement may include, namely, an instruction requesting the third network device to provide beam measurements of the user equipment after the user equipment has been handed over from a second network device to a third network device, a beam measurement identifier (ID), the duration for which the user equipment performs the beam measurement, the duration for which the user equipment logs the beam measurement, the duration for which the user equipment transmits the beam measurement, the period for which the beam measurement is performed, the period for which the beam measurement is logged, the period for which the beam measurement is transmitted, second information relating to at least one beam requested to be measured by the second network device, or one of the types of beam measurements requested by the second network device.
[0056] In some implementations of the methods and devices described herein, the type may include, namely, one of the following: an index of a first number of beams having a stronger 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; an RSRP of one or more beams; an RSRP of available beams for beam measurement; or an RSRP of beams indicated by the second network device.
[0057] In some implementations of the methods and devices 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 will be handed over, or beam prediction information required by a second network device.
[0058] In some implementations of the methods and devices described herein, the third beam prediction information 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 higher than a second threshold; at least one value representing the likelihood 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 residence time of at least one predicted beam.
[0059] In some implementations of the methods and devices described herein, the handover response may further include, namely, second information relating to at least one beam to be measured when the first requirement does not include second information, or one of the types of beam measurement when the first requirement does not include type.
[0060] In some implementations of the methods and devices described herein, the RRC configuration may include one of the following: a first configuration for user equipment to perform random access to a target cell using the predicted beam having the strongest RSRP among multiple beams of a third network device; a second configuration for user equipment to perform beam measurements based on a handover request and a first request; a third configuration for user equipment to log beam measurements based on a handover request and a first request; or a fourth configuration for user equipment to transmit beam measurements based on a handover request and a first request.
[0061] In some implementations of the methods and devices described herein, the second requirement may include, namely, an instruction requesting the second network device to provide past beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, a duration for which the second network device is requested to provide past beam measurements within that duration before the user equipment has been handed over from the second network device to the third network device, the type of past beam measurements requested by the third network device, the ID of the target cell to which the user equipment is handed over, or the ID of the source cell from which the user equipment is handed over.
[0062] In some implementations of the methods and devices described herein, past beam measurements may be transmitted to a third network device via a handover request, or past beam measurements may be transmitted to a third network device after the handover has been completed.
[0063] In some implementations of the methods and devices described herein, the first information may further include, namely, a timestamp of a past beam measurement, or one of the values of the residence time of one or more beams of a past beam measurement. [Brief explanation of the drawing]
[0064] [Figure 1] This figure shows an example of a wireless communication system that supports data collection according to the aspects of this disclosure. [Figure 2A] This is an exemplary signaling chart illustrating an exemplary process according to the aspects of this disclosure. [Figure 2B] This is another exemplary signaling chart illustrating an exemplary process according to the aspects of this disclosure. [Figure 3] This figure shows an exemplary process for transmitting collected training data according to the aspects of this disclosure. [Figure 4] This figure shows an exemplary process according to an aspect of the present disclosure. [Figure 5] This figure shows another exemplary process according to an aspect of the present disclosure. [Figure 6] This figure shows yet another exemplary process according to an aspect of the present disclosure. [Figure 7] This figure shows yet another exemplary process according to an aspect of the present disclosure. [Figure 8] This figure shows yet another exemplary process according to an aspect of the present disclosure. [Figure 9] This figure shows an example of a device that supports data collection according to the aspects of this disclosure. [Figure 10] This figure shows an example of a processor that supports data collection according to the aspects of this disclosure. [Figure 11] This flowchart shows a method for supporting data collection in the manner of this disclosure. [Figure 12] This flowchart shows a method for supporting data collection in the manner of this disclosure. [Figure 13]This flowchart shows a method for supporting data collection in the manner of this disclosure. [Figure 14] This flowchart shows a method for supporting data collection in the manner of this disclosure. [Modes for carrying out the invention]
[0065] Throughout the drawing, the same or similar reference numbers represent the same or similar elements.
[0066] The principles of this disclosure are described here with reference to several embodiments. These embodiments are described for illustrative purposes only and should be understood as helping those skilled in the art to understand and implement this disclosure, without implying any limitation on the scope of this disclosure. The disclosures described herein may be implemented in various ways other than those described below.
[0067] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by those skilled in the art of the field to which this disclosure belongs.
[0068] References in this disclosure to “one embodiment,” “exemplary embodiment,” “embodiment,” and “some embodiments” indicate that the embodiments described may include certain features, structures, or characteristics, but not all embodiments are required to include such features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when certain features, structures, or characteristics are described in relation to a particular embodiment, it is stated that this is within the scope of what a person skilled in the art would know to affect such features, structures, or characteristics in relation to other embodiments, whether explicitly stated or not.
[0069] Terms such as "first" and "second" may be used herein to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used merely to distinguish one element from another. For example, without departing from the scope of the embodiment, the first element may be called the second element, and similarly, the second element may be called the first element. The term "and / or" as used herein includes any combination of one or more of the listed terms.
[0070] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” as used herein also include the plural form unless the context otherwise explicitly indicates. It should be further understood that, as used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the existence of the described function, element, and / or component, but do not exclude the existence or addition of one or more other functions, elements, components, and / or combinations thereof.
[0071] As used herein, the term “communication network” refers to any network conforming to any appropriate communication standard, such as 5G New Radio (NR), Long-Term Evolution (LTE), LTE Advanced (LTE-A), Broadband Code Division Multiple Access (WCDMA®), High-Speed Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communication between user equipment and network devices within a communication network may be carried out according to any appropriate generation 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 protocols currently known or to be developed in the future. Embodiments of this disclosure may be applied to various communication systems. Given the rapid development in communications, there may be future communication technologies and systems to which this disclosure may be embodied. It should not be considered that the scope of this disclosure is limited to the systems described above.
[0072] As used herein, the term “network device” generally refers to a node in a communication network from which user equipment can access the communication network and receive services. Depending on the terminology and technology applied, a network device may also refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), a Radio Access Network (RAN) node, an Advanced Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), an Infrastructure Device for V2X (vehicle-to-vehicle, road-to-vehicle) communication, a Transmit Receive Point (TRP), a Receive Point (RP), a Remote Radio Head (RRH), a repeater, an Access Backhaul Integration (IAB) node, a low-power node such as a femtoBS or picoBS, etc. A network device may further refer to a network function (NF) within the core network, such as an SMF, AMF, PCF, UPF, or a device having the same function in a future network architecture, etc.
[0073] As used herein, the term “User Equipment (UE)” generally refers to any terminal device that may be capable of wireless communication. User equipment may also be called a communication device, terminal device, end-user device, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). User devices may include, but are 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 devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop embedded 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 surgery devices), industrial devices (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain context), consumer electronic devices, and devices operating in commercial and / or industrial wireless networks. In the following description, the terms “user devices,” “communication devices,” “terminals,” “user devices,” and “UE” may be used interchangeably.
[0074] Figure 1 shows an example of a wireless communication system 100 supporting data collection according to an aspect of this disclosure. The wireless communication system 100 may include one or more network entities 102 (also called network equipment (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 LTE Advanced (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 beyond 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).
[0075] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. One or more of the network entities 102 described herein may be a network node, base station, network element, radio access network (RAN), transceiver base station, access point, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other appropriate terms, or may include them, or may be referred to as such. The network entities 102 and UE 104 may communicate via a communication link 110, which may be wireless or wired. For example, the network entities 102 and UE 104 may perform wireless communication via a Uu interface (e.g., receiving and transmitting signaling).
[0076] Network entity 102 may provide a geographic coverage area 112 that network entity 102 can support for services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within that 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, broadcast, etc.) according to one or more radio access technologies. In some implementations, network entity 102 may be mobile and, 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, or 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 wide variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0077] One or more UEs 104 may be distributed across the geographical area of the wireless communication system 100. The UEs 104 may include, or be referred to as, mobile devices, wireless devices, remote devices, remote units, handheld devices, or subscriber devices, or any other appropriate term. In some implementations, the UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, the UEs 104 may be referred to as Internet of Things (IoT) devices, any Internet of Things (IoE) devices, or machine-type communications (MTC) devices, among other examples. In some implementations, the UEs 104 may be stationary within the wireless communication system 100. In some implementations, the UEs 104 may be mobile within the wireless communication system 100.
[0078] One or more UE104s may be devices of different forms or with different capabilities. Several examples of UE104s are shown in Figure 1. UE104s may be capable of communicating with various types of devices, such as network entities 102, other UE104s, or network equipment (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown in Figure 1. Additionally or alternatively, UE104s may support communication with other network entities 102 or UE104s, which may act as relays in the wireless communication system 100.
[0079] UE104 may also support direct wireless communication with other UE104s via communication link 114. For example, UE104 may support direct wireless communication with another UE104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-infrastructure (V2X) deployments, or cellular V2X deployments, communication link 114 may be called a side link. For example, UE104 may support direct wireless communication with another UE104 via the PC5 interface.
[0080] A network entity 102 may support communication with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via S1, N2, or another network interface). Network entities 102 may communicate with each other through the backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate with each other directly (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via the 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 through one or more other access network transmitting entities, which may be called radio heads, smart radio heads, or transmit / receive points (TRPs).
[0081] In some implementations, the network entity 102 may consist of a decoupled architecture, which may be configured to use a physically or logically distributed protocol stack between two or more network entities 102, such as an Access Backhaul Integration (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of the following: a central unit (CU), distributed units (DU), radio units (RU), RAN intelligent controllers (RICs) (e.g., near real-time RICs (near RT RICs), non-real-time RICs (non-RT RICs)), a service management and orchestration (SMO) system, or any combination thereof.
[0082] RU may also be called a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 102 in a separated RAN architecture may be co-located, or one or more components of network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a separated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0083] The functional division between CUs, DUs, and RUs may be flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed in the CU, DU, or RU. For example, a functional division of the protocol stack may be used between the CU and DU so that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, each of which may host lower protocol layers such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, each of which may be at least partially controlled by the CU160.
[0084] As an addition or alternative, a functional decomposition of the protocol stack may be used between the DU and RU so that the DU can support one or more layers of the protocol stack and the RU can support one or more different layers of the protocol stack. The DU may support one or more different cells (for example, through one or more RUs). In some implementations, the functional decomposition between the CU and the DU, or between the DU and the RU, may be within the protocol layer (for example, some functions for the protocol layer may be performed by one of the CU, DU, or RU, and other functions of the protocol layer may be performed by one of the different CU, DU, or RU).
[0085] A CU may be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and a DU may be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of protocol stacks supported by each network entity 102 communicating via such communication links.
[0086] The core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an advanced 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), an access and mobility management function (AMF)), as well as user plane entities that route packets or interconnect 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 layer (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.
[0087] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (for example, via S1, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UEs 104 may establish a session with the core network 106 (for example, a protocol data unit (PDU) session) via a network entity 102. The core network 106 may use the established session (for example, an established PDU session) to route traffic (for example, control information, data, etc.) between the UEs 104 and the application server 118. The PDU session may be an example of a logical connection between the UEs 104 and the core network 106 (for example, one or more network functions of the core network 106).
[0088] In the wireless communication system 100, the network entities 102 and UE104 can use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entities 102 and UE104 may support different resource structures. For example, the network entities 102 and UE104 may support different frame structures. In some implementations, for example in 4G, the network entities 102 and UE104 may support a single frame structure. In some other implementations, for example in 5G, and in other suitable radio access technologies, the network entities 102 and UE104 may support various frame structures (i.e., multiple frame structures). The network entities 102 and UE104 may support various frame structures based on one or more numerologies.
[0089] One or more numerologies may be supported in the wireless communication system 100, and the numerologies may include subcarrier intervals and cyclic prefixes. A first numerology (e.g., μ=0) may be associated with a first subcarrier interval (e.g., 15 kHz) and a typical cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier interval (e.g., 15 kHz) may use one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier interval (e.g., 30 kHz) and a typical cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier interval (e.g., 60 kHz) and a typical cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier interval (e.g., 120 kHz) and a typical cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier interval (e.g., 240 kHz) and a typical cyclic prefix.
[0090] The time intervals of resources (e.g., communication resources) may be organized according to frames (also called wireless frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, each subframe may have a duration, for example, 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0091] As an addition or alternative, the time intervals of resources (e.g., communication resources) may be organized according to slots. For example, a subframe may contain a certain number (e.g., a quantity) of slots. The number of slots in each subframe may depend on one or more numerologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the respective subcarrier intervals of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may use one slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and sixteen slots per subframe, respectively. Each slot may contain a certain number (e.g., a quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., a quantity) of slots for a subframe may depend on the numerology. For a standard cyclic prefix, a slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier interval), a slot may contain 12 symbols. The relationships between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for standard and extended cyclic prefixes may depend on the numerology. It should be understood that references to a first numerology (e.g., μ=0) associated with a first subcarrier interval (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0092] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various classes, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, network entities 102 and UE 104 may conduct wireless communication over one or more of these operating frequency bands. In some implementations, FR1 may be used by network entities 102 and UE 104, in particular, among other equipment or devices for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by network entities 102 and UE104, in particular, among other equipment or devices for short-range, high-data-rate capabilities.
[0093] FR1 may be associated with one or more numerologies (e.g., at least three). For example, FR1 may be associated with a first numerology including a 15 kHz subcarrier interval (e.g., μ=0), a second numerology including a 30 kHz subcarrier interval (e.g., μ=1), and a third numerology including a 60 kHz subcarrier interval (e.g., μ=2). FR2 may be associated with one or more numerologies (e.g., at least two). For example, FR2 may be associated with a third numerology including a 60 kHz subcarrier interval (e.g., μ=2), and a fourth numerology including a 120 kHz subcarrier interval (e.g., μ=3).
[0094] "Layer 1 (L1)" refers to the physical layer primarily used to provide a wireless physical channel for transmitting high-level services. In this disclosure, "L1 measurement" refers to any of the following, which may be useful for training AI / ML models: CSI compression, CSI prediction, beam prediction, and positioning.
[0095] In CSI compression, for UE-side type 1 training and UE-first type 3 training, the L1 measurement may refer to the ground truth CSI from the NW in scalar quantization and / or codebook-based quantization (e.g., e-type II), or aiding information for classifying the data with the aim of distinguishing data characteristics attributable to a particular configuration, scenario, site, etc. For the first training of the network (NW) in training collaboration type 3, the L1 measurement may refer to the CSI generation model training dataset (e.g., raw channels or eigenvectors as model inputs, and pre-quantized or post-quantized latent space vectors as model outputs), or aiding information for classifying the data with the aim of distinguishing data characteristics attributable to a particular configuration, scenario, site, etc. For UE-side proxy model training in monitoring, the L1 measurement may refer to the proxy model training dataset (e.g., post-quantized latent space vectors as proxy model inputs, and the target CSI to be recovered as proxy model outputs), or aiding information for classifying the data with the aim of distinguishing data characteristics attributable to a particular configuration, scenario, site, etc.
[0096] In CSI prediction, L1 measurements may refer to consecutive CSIs (i.e., past and future CSIs), and the type of CSI may include raw channel matrices, PMIs, or eigenvectors. L1 measurements may further refer to auxiliary information for model management, such as site / scenario / dataset-related information.
[0097] For beam prediction, for set B, the L1 measurement may refer to an L1-RSRP measurement based on set B or a subset of set B. For label data, the L1 measurement may refer to an L1-RSRP measurement based on set A or a subset of set A, a partial L1-RSRP measurement based on set A or a subset of set A and a beam indicator, or a top-k beam indicator. For time-related information, the L1 measurement may refer to a timestamp. For auxiliary information including one or more items, the L1 measurement may refer to site / scenario / dataset-related information (e.g., dataset ID), gNB-side related auxiliary information, or UE-side related auxiliary information.
[0098] For positioning, the measurement type L1 measurement may refer to channel impulse response (CIR), power delay profile (PDP), delay profile (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 arrival time (UL-RTOA), uplink arrival angle (UL-AoA), downlink departure angle (DL-AoD), SSB RSRP, or CSI-RS RSRP. For label types, the L1 measurement may refer to position coordinates, timing estimate, line of sight (LOS), or non-line of sight (NLOS). For auxiliary information, the L1 measurement may refer to a timestamp, quality indicator, or reference signal (RS) configuration.
[0099] "Layer 3 (L3)" refers to the network layer, including the RRC sublayer in the access layer, and the mobility management (MM) and call control (CC) in the non-access layer. In this disclosure, "L3 measurement" refers to radio resource management (RRM) measurements that are filtered by the Layer 3 filter and reported to the gNB along with legacy RRC messages.
[0100] AI / ML technology is introduced to optimize physical layer operation, also known as AI for air interfaces. For AI-based positioning use cases, the LMF collects training data from the UE to train the AI model, which can be an LMF-sided or UE-sided model. For AI-based CSI / BM / positioning use cases, the gNB collects training data from the UE to train the AI model, which can be a gNB-sided or UE-sided model. However, factors of UE mobility have not yet been considered in the data collection procedure. There are several issues in data collection that need to be resolved.
[0101] In the first problem, for AI-based positioning, depending on the scalability of the AI model, the LMF may be required to train an AI model capable of performing AI-based positioning (e.g., fingerprinting) within a specific area consisting of a list of cells. The LMF may collect data from one or more UEs, and in this scenario, data collection should (ideally) not be interrupted by UE mobility as long as the UEs are within the area. The above is not supported by legacy data collection procedures.
[0102] The second problem is that, assuming the UE is configured to periodically report training data (e.g., a set of logged L1 measurements) to the source gNB by the source gNB, this could also happen when the UE is handed over to another gNB. Logged L1 measurements that should have been sent to the source gNB but had not yet been sent remain in the buffer. It is unclear whether, or how, the logged L1 measurements should be forwarded to the source gNB.
[0103] In the third issue, in future releases, in addition to predicted cell-level link quality, the source gNB may also predict the best beam after the UE is handed over to the target gNB when making a handover decision. In this way, the source gNB will hand over the UE to the cell with the better predicted beam quality when the two cells have equal (predicted) link quality. The target gNB may also use the beam prediction results to configure the UE to perform random access via the best predicted beam in the handover command. In addition, an L1 / L2 trigger mobility (LTM) decision may be made, and the UE may be configured to connect to another cell via the best predicted beam in the LTM command medium access control (MAC) control element (CE). The above is not supported by legacy data acquisition procedures.
[0104] In the fourth issue, in a future release, the target gNB itself could be configured to perform the best beam prediction and then perform random access via the best predicted beam in the handover command sent to the UE. However, the above is not supported by the legacy data acquisition procedure.
[0105] In view of the above description, some embodiments of the present disclosure provide solutions for data acquisition. In one embodiment of the solutions of the present disclosure, user equipment receives from a first network device at least one measurement configuration determined by at least one network device, the at least one measurement configuration associated with data acquisition for model training, and performs measurements on a reference signal associated with data acquisition for model training based on the at least one measurement configuration. In this way, user equipment can be configured to ensure continuous training data acquisition as the UE moves across a cell or gNB. Thus, communication performance is improved. The principles and implementations of embodiments of the present disclosure are described in detail below with reference to Figures 2A to 14.
[0106] Figure 2A shows a signaling chart illustrating an exemplary process 200A according to an aspect of this disclosure. Process 200A may include a user device 201 and a first network device 202. The user device 201 in Figure 2A may be an example of the UE 140 in Figure 1. The first network device 202 in Figure 2A may be an example of the network entity 102 or core network 106 in Figure 1. Although process 200A is applied to the communication environment 100 in Figure 1, it should be understood that this process may be similarly applied to other communication scenarios involving similar problems.
[0107] In process 200A, the first network device 202 transmits to the user device 201 at least one measurement configuration 207 determined by at least one network device 205. The at least one measurement configuration is associated with data acquisition for model training. The first network device may receive at least one measurement configuration from at least one network device. At least one network device may be located in the area where the user device 201 performs data acquisition. It will be understood that the first network device 202 may be a location information management function (LMF) when model training is used for an AI-based positioning model, and the first network device 202 may be a gNB when model training is used for an AI-based CSI or beam management.
[0108] Alternatively or additionally, the first network device may send a request to at least one network device for at least one measurement configuration. At least one measurement configuration is determined by at least one network device, and at least one measurement configuration is associated with data acquisition for model training. The first network device 202 may then receive at least one measurement configuration from at least one network device. In other words, the first network device 202 may collect measurement configurations for multiple network devices within the area where the user device 201 performs data acquisition, and then the first network device 202 may transmit the measurement configurations to the user device.
[0109] 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, effectiveness information indicating the effective time of the data acquisition session, area information indicating the area in which the user equipment performs data acquisition, or any combination of two or more of the above items.
[0110] For example, at least one measurement configuration may include the type that the user instrument 201 needs to measure, e.g., a PRS or SSB or CSI-RS or other DL reference signal within the area. Optionally, and additionally, at least one measurement configuration may include resource information for the PRS or SSB or other DL reference signal within the area (i.e., at what time and on what frequency resource to measure). The resource information may be collected in advance from the gNB by an LMF within the area, and then the resource information may be provided to the UE. Examples of time and frequency information may include the comb size (M,N) of a comb-N pattern with a number of symbols M, RE offset, slot offset, periodicity, and configured transmit bandwidth, which may be associated with a set of resources, e.g., DL-PRS resources.
[0111] In one example, at least one measurement configuration may include an intermediate ground truth label related to a combination of radio access technology (RAT)-dependent measurement and UE / PRU location based on UE / PRU location.
[0112] In another example, at least one measurement configuration may include time-based validity information indicating the validity of a data acquisition session based on a timer / timeout timer / validity time / measurement response time associated with the received DL-PRS positioning assistance data. If data acquisition is performed after a timeout, outside the validity time, or outside the measurement response time, it may be up to the LMF to decide whether to use such data for training or inference. Alternatively, the LMF may explicitly terminate the data acquisition session or implicitly terminate the session based on an inactive timer or when the UE moves out of the desired area.
[0113] Alternatively or additionally, area information may include one or more identifiers (IDs) of one or more cells, one or more IDs of one or more zones associated with geographic coordinates, one or more IDs of one or more areas associated with a list of cells, one or more tracking area codes (TACs) associated with a list of cells, one or more tracking area identifiers (TAIs) associated with a list of cells, or any combination of two or more of the items described above.
[0114] For example, area information can take one of the following forms: one or more cells are each represented by a cell ID (e.g., PCI, CGI, ARFCN, or a combination thereof); one or more zones are each represented by a zone ID, the zone ID being associated with a specific geographic area calculated from geographic coordinates; or one or more areas are each represented by an area ID, the area ID being associated with a list of cells. This association is predefined or preconfigured by a network, for example, one or more location area codes, tracking area codes (TACs), or tracking area identifiers (TAIs) consisting of multiple cells grouped together to form a tracking area.
[0115] Additionally, user device 201 may transmit first information indicating that a data collection session has been triggered to a second network device, which is at least one network device, and the second network device serves the user device. Alternatively or additionally, the first network device 202 may transmit the first information to the second network device. The second network device may be a serving gNB of user device 20 that can serve user device 201.
[0116] Additionally, if the first information is transmitted by user device 201, it is transmitted via a Radio Resource Control (RRC) message. If the first information is transmitted by first network device 202, it is transmitted via a New Radio (NR) Positioning Protocol A (NRPPa) message.
[0117] In some embodiments, the first information may include an instruction indicating that a data collection session is triggered by a first network device, that the data collection session is performed on the control plane (CP) via Long-Term Evolution (LTE) Positioning Protocol (LPP) messages, that the data collection session is performed on the user plane (UP) via LPP messages, area information indicating the area in which 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.
[0118] For example, an NRPPa message or RRC message may include instructions that imply the LMF has triggered a data acquisition session from user device 201, information indicating whether the data acquisition session is performed on CP or UP via LPP, area information relating to area-based training data acquisition (as described above), time-based references for auxiliary data used to derive measurements for data acquisition, or any combination of two or more of the above items.
[0119] Alternatively or additionally, user equipment 201 may receive a first configuration of a wireless bearer to the user equipment from a second network device.
[0120] In some embodiments, user device 201 may receive a second configuration of a wireless bearer to the user device from a second network device. The second configuration is transmitted via a handover response by a third network device, which is at least one of the network devices. The third network device may be a target gNB that can be the handover destination for user device 20.
[0121] Additionally, the second configuration is sent when the third network device receives a handover request from the second network device requesting to hand over user device 201 to the third network device. In other words, the second network device may send a handover request to the third network device. If the handover request is accepted by the third network device, the third network device may send the second configuration via a handover request acknowledgment message.
[0122] Additionally, a handover request may include instructions indicating that the data collection session is triggered by the first network device, instructions indicating that the data collection session is performed via LPP messages on the CP, instructions indicating that the data collection session is performed via LPP messages on the UP, area information indicating the area in which the user equipment will perform data collection, validity information indicating the validity period of the data collection session, or any combination of two or more of the above items.
[0123] In one example, a handover request may include instructions implying that the LMF has triggered a data acquisition session from the UE, information indicating whether the data acquisition session is performed on the CP or via the LPP on the UP, area information relating to area-based training data acquisition (as described above), and a time-based reference for auxiliary data used to derive measurements for data acquisition.
[0124] In some embodiments, when a data acquisition session is performed via LPP messages on the CP, the first or second configuration may constitute a signaling radio bearer (SRB) configured for the user device 201. In some embodiments, when a data acquisition session is performed via LPP messages on the UP, the first or second configuration may constitute a data radio bearer (DRB) configured for the user device.
[0125] In one example, the first network device 202 is an LMF, and the first network device 202 may initiate training data collection by generating an LPP message and sending it to the UE via the CP or UP. If the LPP message is sent to the UE via the CP, the LPP message is transmitted to network-attached storage (NAS) via a signaling radio bearer (SRB). If the LPP message is sent to the UE via the UP, the LPP message is transmitted as regular data via a data radio bearer (DRB). In another example, the first network device 202 is a gNB, and the first network device 202 may transmit at least one measurement configuration via an RRC message.
[0126] In one example, if a data acquisition session is performed on CP via LPP messages, the serving gNB configures SRB4 or SBR5, or a new SRB on user device 201 if they are not already configured. In another example, if a data acquisition session is performed on UP via LPP messages, the serving gNB configures a dedicated DRB with a specific priority lower than other DRBs.
[0127] Continuing to refer to Figure 2, after receiving at least one measurement configuration 210 from the first network device 202, the user device 201 performs measurements on a reference signal associated with data acquisition for model training based on at least one measurement configuration 207 215. The user device 201 then transmits its acquired data 223 to the first network device 202 220. Correspondingly, the first network device 202 receives the acquired data from the user device 201 225.
[0128] Additionally, user device 201 may transmit collected data to a first network device. Alternatively or additionally, collected data is transmitted to the first network device if the user device is still in the area after a handover to a third network device. For example, if area-based data collection is configured, e.g., if area information is provided, user device 201 may first check whether user device 201 is still in the area after a handover to another cell / gNB, and if user device 201 is still in the area, continue to collect and report the requested training data.
[0129] In some embodiments, user device 201 may send a first request to a second network device or the first network device 202 requesting at least one measurement configuration. In response, the second network device or the first network device 202 may receive the first request from user device 201. The AI / ML model for positioning may be located on the user device side, and user device 201 may collect data without sending the collected data to the gNB. For example, user device 201 may send an LPP message to the LMF or an RRC request message to the serving gNB.
[0130] Alternatively or additionally, user device 201 may receive at least one measurement configuration from a second network device. One or more of these at least one measurement configurations may be transmitted by one or more of the at least one network devices other than the second network device in response to receiving the first request from the second network device. In other words, the second network device may transmit the first request to a third network device. If the first request is accepted by the third network device, the third network device may transmit one or more measurement configurations to the second network device. The second network device then transmits at least one measurement configuration to user device 201.
[0131] For example, an LMF or serving gNB may provide the requested PRS / SSB / other reference signaling configuration to the UE. If area information is provided in a first request for area-based data collection, the LMF or serving gNB may, in cooperation with other gNBs in the area, collect the requested PRS / SSB / other reference signaling configuration within the area. In one example, the LMF may request the PRS / SSB / other reference signaling configuration from other gNBs via the NRPPa procedure. In one example, the serving gNB may request the PRS / SSB / other reference signaling configuration from other gNBs via the Xn AP procedure. The LMF or serving gNB may also indicate area information for area-based data collection, thereby enabling other gNBs to provide the PRS / SSB / other reference signaling configuration within the area.
[0132] In addition, the first request may include the type of reference signal requested by the user device, validity information indicating the validity period of the data acquisition session, area information indicating the area in which the user device performs data acquisition, or any combination of two or more of the above items.
[0133] For example, because AI / ML models may have different input requirements, for instance, some AI / ML models may use SSB and others may use PRS, the first request may include instructions requesting the LMF or serving gNB to provide the UE with PRS, SSB, or other reference signaling configuration for measuring and training the AI model by the UE itself (for example, by reusing the terminating LPP RequestAssistanceData message). Such a request to the NW would configure and provide the configuration related to the reference signaling that a particular AIML model requires as input.
[0134] Examples of time and frequency information may include the comb size (M,N) of a comb-N pattern with a number of symbols M, RE offset, slot offset, periodicity, and configured transmit bandwidth, which may be associated with a set of resources, such as DL-PRS resources. Measurements of PRS, SSB, CSI-RS, or other reference signaling are used as training data for AI models by the UE itself and are not expected to be reported to LMF or gNB. Implementations of area and effectiveness information may be the same as described above.
[0135] In some embodiments, user equipment 201 may receive a third configuration from a second network device. The third configuration may be used to transmit collected data for model training related to artificial intelligence / machine learning (AI / ML) based positioning or channel state information compression, channel state information prediction, or beam prediction.
[0136] In one example, user device 201 may be configured with a serving gNB to perform training data collection and reporting for training an AI / ML model against an AI-based CSI / BM. After the handover and the UE is disconnected from the serving gNB, there may be buffered, logged training data within the UE that has not yet been sent to the serving gNB.
[0137] Figure 3 shows an exemplary process 300 for transmitting collected training data according to an aspect of the present disclosure. As shown in Figure 3, user instrument 201 may be configured to periodically transmit collected training data to the gNB. Between two reports, user instrument 201 may be configured to log multiple instances of L1 or L3 measurements. It is possible that user instrument 201 has only a few logged instances and a handover is triggered before user instrument 201 reports them to the serving gNB. In this case, it may be beneficial for the serving gNB to still obtain the logged but not yet reported measurement instances after the handover, as these instances may be valuable samples measured at the cell edge.
[0138] A second network device (i.e., a serving gNB) may configure user device 201 to perform L1 / L3 measurement logging and report the logged measurement instances to the serving gNB via RRC signaling, the serving gNB may then generate and send an RRCReconfiguration message to user device 201.
[0139] Additionally, the third configuration may include the period for sending collected data, the period for logging measurements, events that trigger the sending of collected data, events that trigger the logging of measurements, instructions indicating that user equipment should not discard unsent collected data, trace information including trace references or trace recording session references, or any combination of two or more of the items described above.
[0140] In some embodiments, a handover request may include instructions indicating that the user device is configured not to discard any collected data that has not been transmitted, trace information, or any combination of two or more of the items described above.
[0141] For example, an RRCReconfiguration message may include periodicity / events for reporting, periodicity / events for measurement logging, instructions implying that measurements logged in any buffer that have not yet been sent by the user device should not be discarded, trace information, such as a trace reference or trace recording session reference when training data collected from the user device is ultimately sent to Maintenance Operations Management (OAM), or any combination of two or more of the above items.
[0142] Alternatively or additionally, user device 201 may receive a second request for collected data that has not been transmitted after the handover to a third network device. The second request may be transmitted from the third network device.
[0143] In one example, after user device 201 is handed over and connected to another gNB (i.e., a third network device), the other gNB may trigger a UE information procedure to retrieve any possible logged L1 / L3 measurements at the UE that have not yet been sent. The other gNB may generate and send a UEInformationRequest message to the UE, which contains instructions requesting any logged L1 / L3 measurement results that the UE has not yet sent. The other gNB may be the same as the serving gNB, and it will be understood that the handover between the second and third network devices may be an intra-gNB handover. The other gNB may be different from the serving gNB, and the handover of user device 201 may be an inter-gNB handover.
[0144] Additionally, user device 201 may send to a third network device either unsent collected data or trace information related to the collected data. For example, if there are any logged L1 / L3 measurements available on the UE, the UE generates a UEInformationResponse message and responds to the other gNB with that message. The UEInformationResponse message may include logged L1 / L3 measurements that have not yet been sent. If configured in the third configuration, the UEInformationResponse message may further include relevant trace information, such as a trace reference or a trace recording session reference.
[0145] Additionally, any collected data that has not been transmitted may be further transmitted from a third network device to the second network device. For example, another gNB may send the L1 / L3 measurements recorded in the received log to the (older) serving gNB via XnAP messages, and the other gNB may further send the L1 / L3 measurements recorded in the received log, along with the relevant trace information, to the OAM.
[0146] If the second request is not received within the specified time period, user device 201 may discard the untransmitted collected data. Additionally, this time period may include a pre-configured time period after the collected data was 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 items described above.
[0147] For example, the time period could be a defined time period after the collected data was generated (e.g., 48 hours), a defined inactivity timer over a certain period, or a timer configured by the serving gNB, such as a timeout timer.
[0148] Figure 2B shows a signaling chart illustrating an exemplary process 200B according to an aspect of this disclosure. Process 200B may include a second network device 203 and a third network device 204. The second network device 203 in Figure 2B may be an example of network entity 102 in Figure 1. The third network device 204 in Figure 2B may be an example of network entity 102 in Figure 1. Although process 200B is applied to the communication environment 100 in Figure 1, it should be understood that this process may be similarly applied to other communication scenarios involving similar problems.
[0149] In process 200B, the second network device 203 sends a handover request 237 to the third network device 204 230. The handover request includes first information related to data acquisition for beam prediction, and the second and third network devices are positioned in the area where user equipment performs data acquisition.
[0150] The second network device 203 may be a source gNB that provides services to user equipment, and the third network device 204 may be a target gNB to which user equipment can be switched over. After deciding to hand over user equipment to the target gNB, the source gNB may send a HANDOVER REQUEST message to the target gNB.
[0151] In some embodiments, a second network device 203 may send a first request associated with data collection from a user device to a third network device 204. An AI / ML model for best 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. Before the handover of the user device, the source gNB may trigger a data collection reporting start procedure by sending a DATA COLLECTION REQUEST message to the target gNB.
[0152] In addition, the first request may include instructions requesting the third network device to provide beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, the ID of the beam measurement, the duration for which the user equipment will perform the beam measurement, the duration for which the user equipment will log the beam measurement, the duration for which the user equipment will transmit the beam measurement, the period for which the beam measurement will be performed, the period for which the beam measurement will be logged, the period for which the beam measurement will be transmitted, second information relating to at least one beam that the second network device has requested to be measured, the type of beam measurement requested by the second network device, or any combination of two or more of the items described above. On the other side of the communication, the third network device 204 may receive the first request from the third network device.
[0153] Additionally, the type may include the index of a first number of beams of a third network device having a stronger reference signal received power (RSRP) than any of the multiple beams, the index of one or more beams of a second network device having one or more RSRPs higher than a first threshold, or a combination of the above items.
[0154] In one example, a DATA COLLECTION REQUEST may include instructions requesting a target gNB to provide L1 / L3 beam measurements after a handover, a duration for which the target gNB should configure the UE to measure / log / report L1 / L3 beam measurements within the duration, reporting periodicity, measurement / log instance periodicity, information relating to the specific beam to be measured, e.g., SSB index, information relating to the type of measurement, e.g., the indices of the top K beams with the strongest RSRP among multiple beams, or the RSRPs of the top K beams, the RSRPs of all available beams, or the RSRP of the specific beam, the measurement ID of the L1 / L3 beam measurement, or any combination of two or more of the above items.
[0155] In some embodiments, the first information may include a beam measurement ID, a target cell ID to which the user equipment will be handed over, a third piece of beam prediction information, or any combination of two or more of the above items. For example, a HANDOVER REQUEST message may include a measurement ID, a target cell ID, beam prediction information, or any combination of two or more of the above items included in the corresponding DATA COLLECTION REQUEST message.
[0156] In addition, the third piece of information for beam prediction may include an index associated with the beam predicted to have the strongest RSRP among multiple beams of the second network device, a list of a second number of beams with stronger RSRPs among multiple beams of the second network device, a list of at least one beam predicted to have at least one RSRP higher than a second threshold, at least one value representing the likelihood associated with at least one predicted beam, at least one predicted beam measurement associated with at least one predicted beam, a predicted value for the residence time of at least one predicted beam, or any combination of two or more of the above items.
[0157] For example, for a target cell, beam prediction information may include the following forms: the predicted best beam (e.g., SSB index), a list of possible predicted best beams (e.g., SSB index), probability values (e.g., 0-100) representing the likelihood associated with each predicted best beam (as described above), predicted L1 / L3 measurements (e.g., RSRP) associated with each predicted best beam, predicted dwell time values for user equipment in the predicted best beam, or any combination of two or more of the above items.
[0158] Alternatively or additionally, if the first requirement does not include the second information, the first information may further include the second information relating to at least one beam to be measured, for example, the SSB index. Alternatively, if the first requirement does not include the type, the first information may further include the type of beam measurement, for example, the indices of the top K beams, or the RSRPs of the top K beams, or the RSRPs of all available beams, or the RSRP of a particular beam.
[0159] In some embodiments, the third network device 204 may send a second request to the second network device 203 associated with data collection from user equipment. In response, the second network device 203 may receive the request from the third network device 204. An AI / ML model for best 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 best beam prediction, for example, for serving beam selection, in the initial stages after a handover. Before the handover, the target gNB triggers a data collection reporting start procedure and sends a DATA COLLECTION REQUEST message to the source gNB.
[0160] In addition, the second request is an instruction, duration, requesting the second network device to provide past beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, which may include a duration, a type of past beam measurement requested by the third network device, the ID of the target cell to which the user equipment is handed over, the ID of the source cell from which the user equipment is handed over, or any combination of two or more of the above items.
[0161] In one example, a DATA COLLECTION REQUEST includes an instruction requesting a source gNB to provide past L1 / L3 beam measurements of the UE when a handover is triggered, a duration for which the source gNB should provide past L1 / L3 beam measurements of the UE within the duration prior to the handover, information relating 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, or the RSRP of all available beams, or the RSRP of a particular beam, the ID of cell A, where cell A of the target gNB is the target cell when the user instrument is handed over from the source gNB to cell A of the target gNB, the ID of cell A, the ID of cell B, where cell B is the source cell when the UE is handed over from cell B of the source gNB to the target gNB, or any combination of two or more of the above items.
[0162] Additionally, past beam measurements may be sent to a third network device 204 via a handover request. For example, after deciding to hand over the UE to a target gNB, the source gNB sends a HANDOVER REQUEST message to the target gNB. The HANDOVER REQUEST message may include past L1 / L3 beam measurements as requested. Each past L1 / L3 beam measurement instance may be associated with a timestamp of the measurement. For serving beams, dwell time values may also be provided in the HANDOVER REQUEST message.
[0163] Alternatively, past beam measurements may be sent to a third network device after the handover is complete. For example, a source gNB may send past L1 / L3 beam measurements to a target gNB after the handover is complete, and these past L1 / L3 beam measurements may be sent via a DATA COLLECTION UPDATE message.
[0164] Alternatively or additionally, the first information may further include timestamps of past beam measurements, residence time values for one or more beams in past beam measurements, or a combination of the above items.
[0165] After receiving a handover request 237 from the second network device 203 240, the third network device 204 sends a handover response 257 to the second network device 203 250. The handover response 247 includes a radio resource control (RRC) configuration for the handover procedure. In response, the second network device 203 receives the handover response 247 from the third network device 204 260. In other words, the target gNB can utilize the predicted best beam and configure user equipment to randomly access the target gNB via the predicted best beam.
[0166] In some embodiments, the RRC configuration may include a first configuration for user equipment to perform random access to a target cell using a predicted beam having the strongest RSRP among multiple beams of a third network device; a second configuration for user equipment to perform beam measurements based on a handover request and a first request; a third configuration for user equipment to log beam measurements based on a handover request and a first request; a fourth configuration for 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.
[0167] For example, a target gNB may be configured to perform random access to the target cell via the predicted best beam. The target gNB may also be configured to perform L1 / L3 beam measurements / logging / reporting as requested by the source gNB in a DATA COLLECTION REQUEST or DATA COLLECTION HANDOVER REQUEST message.
[0168] Alternatively or additionally, the second network device 203 may transmit the RRC configuration to the user equipment. After the user equipment is handed over from the second network device to the third network device, the second network device 203 may receive beam measurements from device 204 on the third network.
[0169] On the other side of the communication, the third network device 204 may receive beam measurements after the user equipment has been handed over from the second network device 203 to the third network device 204. Alternatively, the third network device 204 may transmit beam measurements to the second network device 203. For example, the target gNB may further transmit L1 / L3 beam measurements to the source gNB via a DATA COLLECTION UPDATE message.
[0170] Through embodiments of Process 200A and Process 200B, the user instrument may be configured to ensure continuous training data collection when the UE is moving across a cell or gNB. If training data reporting is interrupted due to UE mobility and the user instrument has logged measurements in a buffer that have not yet been sent to the serving gNB after the handover, the user instrument may retain (i.e., not discard) the logged measurements and send them to the other gNB after the handover. Additionally, the serving gNB may collect training data for best beam prediction from the target gNB. The target gNB may also collect training data for best beam prediction from the source gNB. It will be understood that embodiments of Process 200A and Process 200B may be used separately or in combination.
[0171] Figure 4 shows an exemplary process 400 according to an aspect of the present disclosure. Process 400 may include a UE401, an LMF402, a serving gNB403, and other gNB404. UE401 in Figure 4 may be an example of UE104 in Figure 1 or user equipment 201 in Figure 2A. LMF402 in Figure 4 may be an example of core network 106 in Figure 1 or first network device 202 in Figure 2A. Serving gNB403 in Figure 4 may be an example of network entity 102 in Figure 1. Other gNB404 may be an example of network entity 102 in Figure 1. It is understood that process 400 may be considered as a more specific example of process 200A in Figure 2A.
[0172] In process 400, training data collection from UE 401 is initiated and configured by LMF402, and the training data is sent from UE401 to LMF402. The training data can be used to train an AIML model on the LMF side.
[0173] At 410, LMF402 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 further include information relating to the training data requested by LMF 402, area information where the requested training data will be collected when UE 401 is within an area also known as area-based data collection, or a combination of the above items. In response, UE401 receives the LPP data collection configuration message from LMF402.
[0174] Information indicating that data collection is triggered is generated and transmitted by either LMF402 or UE401. At 415, LMF402 generates the information and transmits it to serving gNB403. At 420, UE401 generates the information and transmits it to serving gNB403. The information is transmitted by an RRC message when transmitted by UE401, and by an NRPPa message when transmitted by LMF402.
[0175] At 425, after learning that the training data collection session has started at the UE, the serving gNB configures a dedicated radio bearer to perform training data collection. The dedicated radio bearer is indicated to UE 401 by the RRC configuration. The dedicated radio bearer may be configured with a specific priority lower than SRB1 or the regular DRB.
[0176] At step 430, UE 401 begins collecting and reporting the requested training data via LPP, as configured by the LMF. UE 401 sends the LPP data collection report to LMF 402, which includes ground truth and associated L1 measurements. In response, LMF 402 receives the LPP data collection report from UE 401.
[0177] In 435, for inter-gNB handover, serving gNB403 sends a HANDOVER REQUEST message to the other gNB404 via the Xn interface, requesting that UE401 be handed over to the other gNB404.
[0178] In 440, after receiving a HANDOVER REQUEST message from the serving gNB403, other gNB404 responds by sending a HANDOVER REQUEST ACKNOWLEDGE message to the serving gNB403. The HANDOVER REQUEST ACKNOWLEDGE message includes an RRC configuration that UE401 applies when accessing other gNB404s, and the RRC configuration may include a dedicated radio bearer configuration for training data collection. The dedicated radio bearer may be configured with a specific priority lower than SRB1 or the normal DRB.
[0179] At 445, UE401 receives the RRC configuration, including the dedicated radio bearer configuration, from the serving gNB403.
[0180] In 450, following the handover from serving gNB403 and access to other gNB404s, UE401 continues to collect the requested training data and report it to LMF402 via LPP as previously configured by LMF402 without starting a new LPP session again.
[0181] Generally, for LMF-side model training for AI-based positioning, the UE is configured to ensure continuous training data collection as the UE moves across the gNB or cell in order to perform training data collection for AI-based positioning that takes mobility into account.
[0182] Figure 5 shows another exemplary process 500 according to an aspect of this disclosure. Process 500 may include a UE 501, an LMF / serving gNB 502, and other gNBs 503. UE 501 in Figure 5 may be an example of UE 104 in Figure 1 or user equipment 201 in Figure 2A. Other gNBs 503 may be an example of network entity 102 in Figure 1. It is understood that process 500 may be considered as a more specific example of process 200A in Figure 2A.
[0183] In 510, UE501 sends an LPP / RRC message to LMF / serving gNB502. The LPP / RRC message requests a reference signaling configuration for data acquisition. The LPP / RRC message may include instructions requesting a PRS / SSB, other reference signaling configuration area information for area-based data acquisition, or a combination of the above items.
[0184] In 520, the LMF / serving gNB502 appropriately provides the requested PRS / SSB / other reference signaling configuration to the UE501. If area information in 510 is provided for area-based data collection, the LMF / serving gNB502 may, in cooperation with other gNB503s in the area, collect the requested PRS / SSB / other reference signaling configuration within the area. In 515, after receiving an LPP / RRC message, the LMF / serving gNB502 may forward the information consisting of the LPP / RRC message to other gNB503s. The LMF may request the PRS / SSB / other reference signaling configuration from other gNB503s via an NRPPa message. The serving gNB may request the PRS / SSB / other reference signaling configuration from other gNB503s via an Xn AP message. The LMF / serving gNB502 may also indicate area information for area-based data acquisition, thereby allowing other gNB503s to appropriately provide PRS / SSB / other reference signaling configurations within the area.
[0185] Based on the configuration provided by the LMF / serving gNB502, the UE 501 will begin measuring PRS / SSB / other reference signaling.
[0186] Generally, for training UE-side models for AI-based positioning, and for collecting training data for AI-based positioning that takes mobility into account, training data collection is performed by the UE itself with the assistance of an LMF or serving gNB.
[0187] Figure 6 shows another exemplary process 600 according to an aspect of the present disclosure. Process 600 may include a UE 601, a serving gNB 602, and other gNBs 603. The UE 601 in Figure 6 may be an example of the UE 104 in Figure 1 or the user device 201 in Figure 2A. The serving gNB 603 in Figure 6 may be an example of the network entity 102 in Figure 1. Other gNBs 603 may be examples of the network entity 102 in Figure 1.
[0188] Process 600 assumes that UE 601 is configured by serving gNB 602 to perform training data collection and training data collection reporting for AIML model training for AI-based CSI / BM. After the handover and UE601 is detached from serving gNB602, there may be buffered, logged training data within the UE that has not yet been sent to serving gNB602.
[0189] In 610, the serving gNB602 sends a data acquisition configuration to the UE601, which includes instructions indicating that the acquired data should not be discarded after the handover. The serving gNB602 generates an RRCReconfiguration message (i.e., the data acquisition configuration) and sends it to the UE601, configuring the UE601 to perform logging of L1 / L3 measurements and report the logged measurement instances to the serving gNB602 via RRC signaling. Alternatively, if the training data collected from the UE601 is ultimately sent to the OAM, the data acquisition configuration may also include trace information, such as trace references or trace recording session references.
[0190] In 615, for inter-gNB handover, serving gNB602 sends a handover request message to other gNB603, for example, using a new Xn Application Protocol (XnAP) information element (IE) in the handover request message. The handover request message includes instructions implying that UE601 is configured to collect L1 / L3 measurements and report them to serving gNB602. The other gNB603 can then understand that UE601 may have several logged L1 / L3 measurements in its buffer that are useful to source gNB602. Alternatively, if the training data collected from UE601 is ultimately sent to OAM, the handover request message may also include trace information.
[0191] In 620, after receiving a handover request message from serving gNB602, the other gNB603 sends a handover request acknowledgment to serving gNB602.
[0192] At step 625, UE601 initiates a random access procedure to hand over to another gNB603.
[0193] In 630, after connecting to another gNB603, the other gNB603 generates and sends a UE information request message to the UE, which includes instructions requesting any logged 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), UE601 may, via signaling, indicate to the other gNB603 that logged measurements are available on the UE601 side.
[0194] In 635, if there are any logged L1 / L3 measurements available on UE 601, UE 601 generates a UE Information Response message and sends it to other gNB 603. The UE Information Response message includes any logged L1 / L3 measurements that have not yet been sent. Alternatively, if trace information is sent in 610, the UE Information Response message may also include the associated trace information, such as a trace reference or trace recording session reference.
[0195] In 640, for inter-gNB handover, i.e., when another gNB603 is different from the serving gNB602, the other gNB603 sends the L1 / L3 measurements recorded in the received log to the serving gNB602 via an XnAP message. Alternatively, the other gNB603 may send the L1 / L3 measurements recorded in the received log, along with the associated trace information, to the OAM.
[0196] As an addition or alternative, if L1 / L3 measurements recorded in the buffered log on UE601 are not retrieved by another gNB603 after a handover to another gNB603, UE601 will discard the logged L1 / L3 measurements after a certain period of time has elapsed.
[0197] Generally, to resolve training data reporting interruptions caused by UE mobility, when a UE is configured by a serving gNB to measure, log, and report specific L1 / L3 measurements to the serving gNB while the UE is connected to the RRC, if the UE has logged measurements in its buffer that have not yet been sent to the serving gNB after a handover, the UE will retain (i.e., not discard) the logged measurements and send them to the other gNB after the handover. The other gNB may then further forward the logged measurements from the UE to the (old) serving gNB or OAM.
[0198] Figure 7 shows another exemplary process 700 according to an aspect of the present disclosure. Process 700 may include a UE 701, a source gNB 702, and a target gNB 703. UE 701 in Figure 7 may be an example of UE 104 in Figure 1. Source gNB 702 in Figure 7 may be an example of network entity 102 in Figure 1 or a second network device 203 in Figure 2B. Target gNB 703 may be an example of network entity 102 in Figure 1 or a third network device 204 in Figure 2B. It is understood that process 700 may be considered as a more specific example of process 200B in Figure 2B.
[0199] In 710, source gNB702 sends a data acquisition request message to target gNB703 to trigger the data acquisition reporting initiation procedure. The data acquisition request message includes instructions requesting target gNB703 to provide L1 / L3 beam measurements after the handover. The data acquisition request message may further include at least one measurement ID, i.e., at least one ID of at least one beam measurement; duration, for which target gNB703 should configure UE701 to measure / log / report the L1 / L3 beam measurements; reporting periodicity; measurement / log instance periodicity; information relating to the specific beam to be measured, e.g., SSB index; information relating to the type of measurement, e.g., top K beam index, or RSRP of the top K beams, or RSRP of all available beams, or RSRP of the specific beam; or any combination of two or more of the above items.
[0200] In step 715, if the data collection request is accepted by target gNB703, target gNB703 sends a data collection response message to source gNB702.
[0201] In 720, after deciding to hand over UE701 to target gNB703, source gNB702 sends a handover request message to target gNB703. The handover request message includes at least one measurement ID, UE ID, target cell ID, a list of possible predicted best beams including possibilities, additional information about beams to be measured after the handover, or any combination of two or more of the above items.
[0202] Target gNB703 may configure UE701 to initiate random access to target gNB703 via the best beam, utilizing the predicted best beam. At 725, target gNB703 sends a handover request acknowledgment message to source gNB702. The handover request acknowledgment message generated by target gNB703 includes RRC reconfiguration for UE701 to perform the handover, and target gNB703 may configure UE701 to measure a specific beam.
[0203] At 730, source gNB702 transfers the RRC reconstruction to UE701. At 735, UE701 performs random access to target gNB703. At 740, after a successful handover, UE701 performs L1 / L3 beam measurements, logs the L1 / L3 beam measurements, and sends an L1 or L3 message containing the L1 / L3 beam measurement results to target gNB703 as configured.
[0204] In step 745, target gNB703 sends a data acquisition update message to source gNB702. The acquisition message may include the requested L1 / L3 beam measurements after the handover. The acquisition message may include at least one measurement ID, UE ID, or a combination of the above items.
[0205] Generally, in a scenario where a source gNB collects training data for the best beam prediction for a handover decision for an inter-gNB handover, the source gNB pre-configures a data collection request associated with a measurement ID that requests the target gNB to provide the requested specific L1 / L3 beam measurements of the UE that should be handed over after a successful handover. The target gNB may configure the UE to perform the requested L1 / L3 beam measurements after the handover and send the measurement results back to the source gNB.
[0206] Figure 8 shows another exemplary process 800 according to an aspect of the present disclosure. Process 800 may involve a source gNB801 and a target gNB802. Source gNB801 in Figure 8 may be an example of network entity 102 in Figure 1 or a second network device 203 in Figure 2B. Target gNB803 may be an example of network entity 102 in Figure 1 or a third network device 204 in Figure 2B. It is understood that process 800 may be considered as a more specific example of process 200B in Figure 2B.
[0207] In 810, prior to the UE handover, target gNB802 triggers the data acquisition reporting start procedure and sends a data acquisition request message to source gNB801. The data acquisition 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 items.
[0208] In 815, if the data collection request is accepted by source gNB801, source gNB801 sends a data collection response message to target gNB802.
[0209] In 820, after deciding to hand over the UE to target gNB802, source gNB801 sends a handover request message to target gNB802. The handover request message includes the requested UE ID, target cell ID, and past L1 / L3 beam measurements.
[0210] At step 825, the target gNB802 sends a handover request acknowledgment message to the source gNB801.
[0211] Generally, a target gNB can collect training data from a source gNB for the best beam prediction. The best beam prediction can then be used for serving beam selection in the initial stages after handover.
[0212] Figure 9 shows an example of a device 900 supporting data acquisition according to an aspect of this disclosure. Device 900 may be an example of a user device 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 a processor 902, memory 904, transceiver 906, and optionally an I / O controller 908. These components may communicate electronically via one or more interfaces (e.g., buses) or otherwise be coupled (e.g., operably, communicatively, functionally, electronically, electrically).
[0213] The processor 902, memory 904, transceiver 906, or various combinations thereof or various components thereof may be examples of means for carrying out various aspects of the disclosure described herein. For example, the processor 902, memory 904, transceiver 906, or various combinations thereof or components thereof may support a method for carrying out one or more of the operations described herein.
[0214] In some implementations, the processor 902, memory 904, transceiver 906, or various combinations or components thereof, may be implemented in hardware (for example, in a communication management circuit configuration). 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, which may be configured as means for performing the functions described herein or otherwise supporting such means. In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to perform one or more of the functions described herein (for example, the processor 902 executes instructions stored in the memory 904).
[0215] For example, the processor 902 may support wireless communication in device 900 according to the examples disclosed herein. The 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 at least one measurement configuration is associated with data acquisition for model training, and means for performing measurements on a reference signal associated with data acquisition for model training based on at least one measurement configuration. The processor 902 may be configured to operate to support means for other implementations of method 1100.
[0216] For example, the processor 902 may support wireless communication in device 900 according to the examples disclosed herein. The 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 at least one measurement configuration is associated with data acquisition for model training; means for transmitting to a user device at least one measurement configuration determined by at least one network device, wherein at least one measurement configuration is associated with data acquisition for model training; and means for receiving from the user device collected data of the user device. The processor 902 may be configured to operate to support means for other implementations of method 1200.
[0217] For example, the processor 902 may support wireless communication in device 900 according to the examples disclosed herein. The 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, the at least one measurement configuration being associated with data acquisition for model training; means for transmitting to a third network device a handover request including first information relating to data acquisition for beam prediction, the second and third network devices being located in an area where user equipment performs data acquisition; and means for receiving from the third network device a handover response including a radio resource control (RRC) configuration for a handover procedure. The processor 902 may be configured to operate to support means for other implementations of method 1300.
[0218] For example, the processor 902 may support wireless communication in device 900 according to the examples disclosed herein. The 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, the at least one measurement configuration being associated with data acquisition for model training; means for receiving from a second network device a handover request including first information relating to data acquisition for beam prediction, the second and third network devices being located in an area where user equipment performs data acquisition; and means for transmitting to the second network device a handover response including a radio resource control (RRC) configuration for a handover procedure. The processor 902 may be configured to operate to support means for other implementations of method 1300.
[0219] The 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, the processor 902 may be configured to operate a memory array using a memory controller. In some implementations, the memory controller may be integrated into the processor 902. The 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.
[0220] Memory 904 may include random access memory (RAM) and read-only memory (ROM). Memory 904 may store computer-readable computer-executable code, which, when executed by processor 902, causes device 900 to perform various functions described herein. The code may be stored in a non-temporary computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executable by processor 902, but (for example, when compiled and executed) can cause the computer to perform the functions described herein. In some implementations, memory 904 may include a basic input / output system (BIOS) that can control basic hardware or software operations, in particular, interactions with peripheral components or peripheral devices.
[0221] The I / O controller 908 can manage input and output signals for device 900. The I / O controller 908 can also manage peripheral devices not integrated into device 400. In some implementations, the I / O controller 908 may represent physical connections or ports to external peripheral devices. In some implementations, the I / O controller 908 may use an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I / O controller 908 may be implemented as part of a processor, such as processor 902. In some implementations, a user may interact with device 900 via the I / O controller 908 or via hardware components controlled by the I / O controller 908.
[0222] In some implementations, device 900 may include a single antenna 910. However, in other implementations, device 900 may have two or more antennas 910 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, and these antennas may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 906 may communicate bidirectionally with one or more antennas 910, wired or wireless links, as described herein. For example, transceiver 906 may represent a wireless transceiver and communicate bidirectionally with another wireless transceiver. Transceiver 906 may include a modem for modulating packets and providing the modulated packets to one or more antennas 910 for transmission, and for demodulating packets received from one or more antennas 910. Transceiver 906 may include one or more transmit chains, one or more receive chains, or a combination thereof.
[0223] The transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets). The transmit chain may include at least one modulator for modulating data into a carrier signal and preparing the signal for transmission over a wireless medium. The 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 transmit 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 transmit chain may also include one or more antennas 910 for transmitting the amplified signal to air or a wireless medium.
[0224] The receiving chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiving chain may include one or more antennas 910 for receiving signals over air or a wireless medium. The receiving chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiving chain may include at least one demodulator configured to demodulate the received signal and to obtain transmitted data by inverting the modulation technique applied during the transmission of the signal. The receiving chain may include at least one decoder for decoding the demodulated signal to receive transmitted data.
[0225] Figure 10 shows an example of a processor 1000 supporting data acquisition according to an aspect of this disclosure. 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 communicate electronically via one or more interfaces (e.g., buses) or otherwise be coupled (e.g., operationally, communicatively, functionally, electronically, electrically).
[0226] The processor 1000 may be a processor chipset, which may include a protocol stack (e.g., a software stack) that is executed by the processor chipset to perform various operations as described herein (e.g., receive, acquire, retrieve, transmit, output, forward, store, decide, identify, access, write, read). The processor chipset may include one or more cores, one or more caches (e.g., 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., or memory contained therein)).
[0227] The controller 1002 may be configured to manage and coordinate various operations of the processor 1000 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, deciding, identifying, accessing, writing, and reading) so that the processor 1000 supports various operations as described herein. For example, the controller 1002 may act as a control unit for the processor 1000 and generate control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.
[0228] The controller 1002 may be configured to fetch instructions from memory 1004 (e.g., acquire, retrieve, receive) and to determine subsequent instructions to be executed so that the processor 1000 can support various operations as illustrated herein. The controller 1002 may be configured to track the memory address of the instruction associated with memory 1004. The controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1002 may be configured to translate instructions and to determine control signals to be output to other components of the processor 1000 so that the processor 1000 can support various operations as illustrated herein. Additionally or alternatively, the controller 1002 may be configured to manage the flow of data within the processor 1000. The controller 1002 may be configured to control the transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1000.
[0229] Memory 1004 may include one or more caches (for example, memory that is local to or contained within the processor 1000), or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, or flash memory. In some implementations, memory 1004 may be located within or on the processor chipset (for example, local to the processor 1000). In some other implementations, memory 1004 may be located outside the processor chipset (for example, remote to the processor 1000).
[0230] Memory 1004 may store computer-readable executable code, which, when executed by the processor 1000, causes the processor 1000 to perform various functions described herein. The code may be stored in a non-temporary computer-readable medium, such as system memory or another type of memory. The controller 1002 and / or the processor 1000 may be configured to execute computer-readable instructions stored in memory 1004 to cause the processor 1000 to perform various functions (for example, functions or tasks that support transmit power prioritization). For example, the processor 1000 and / or the controller 1002 may be connected to or coupled with memory 1004, and the processor 1000, controller 1002, and memory 1004 may be configured to perform various functions described herein. In some examples, the processor 1000 may include multiple processors, and memory 1004 may include multiple memories. One or more of the processors may be coupled with one or more of the memories, which may be configured individually or collectively to perform various functions as described herein.
[0231] One or more ALU1000s may be configured to support various operations as illustrated in the examples described herein. In some implementations, one or more ALU1000s may be located within or on a processor chipset (e.g., processor 1000). In some other implementations, one or more ALU1000s may be located outside the processor chipset (e.g., processor 1000). One or more ALU1000s may perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU1000s may receive input operands and operation codes, which determine the operation to be performed. One or more ALU1000s may consist of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, for processing and handling data according to the operations. As an addition or alternative, one or more ALU1000s may support logical operations such as AND, OR, exclusive OR (XOR), not-OR (NOR), and not-AND (NAND), enabling one or more ALU1000s to handle conditional operations, comparisons, and bitwise operations.
[0232] Processor 1000 may support wireless communication as illustrated herein. Processor 1002 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, the at least one measurement configuration being associated with data acquisition for model training, and means for performing measurements on a reference signal associated with data acquisition for model training based on the at least one measurement configuration.
[0233] Figure 11 shows a flowchart of method 1100 supporting data acquisition according to an aspect of this disclosure. The operation of method 1100 may be carried out by a device or its components, as described herein. For example, the operation of method 1100 may be carried out by UE 104, as described herein. In some implementations, the device may execute a set of instructions for controlling the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.
[0234] In 1105, the method includes receiving from a first network device at least one measurement configuration determined by at least one network device, the at least one measurement configuration being associated with data acquisition for model training. The operation of 1105 may be carried out according to the examples described herein. In some implementations, the operation of 1105 may be carried out by the device described with reference to Figure 1.
[0235] In 1110, the method includes performing measurements on a reference signal associated with data acquisition for model training based on at least one measurement configuration. The operation of 1110 may be carried out according to the examples described herein. In some implementations, the operation of 1110 may be carried out by the device described with reference to Figure 1.
[0236] In some embodiments, at least one measurement configuration may include one of the following: the type of reference signal, resource information for the reference signal, the type of ground truth, effectiveness information indicating the effective time of the data acquisition session, or area information indicating the area in which the user equipment performs data acquisition.
[0237] In some embodiments, 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 zones associated with geographic coordinates; one or more IDs of one or more areas associated with a list of cells; one or more tracking area codes (TACs) associated with a list of cells; or one or more tracking area identifiers (TAIs) associated with a list of cells.
[0238] In some embodiments, the method involves transmitting, via a transceiver, first information indicating that a data collection session has been triggered to a second network device among at least one network device, the second network device further including servicing, transmitting to user equipment.
[0239] In some embodiments, the first information may include, namely, an instruction indicating that a data collection session is triggered by a first network device; that the data collection session is performed on the control plane (CP) via Long-Term Evolution (LTE) Positioning Protocol (LPP) messages; that the data collection session is performed on the user plane (UP) via LPP messages; area information indicating the area in which user equipment performs data collection; or validity information indicating the validity period of the data collection session.
[0240] In some embodiments, the first information may be transmitted via a radio resource control (RRC) message.
[0241] In some embodiments, the method may further include receiving a first configuration of a wireless bearer for user equipment from a second network device.
[0242] In some embodiments, the method may further include sending a first request to either a second network device or a first network device for at least one measurement configuration.
[0243] In some embodiments, the method may further include receiving at least one measurement configuration from a second network device, one or more of the at least one measurement configurations being transmitted by one or more of the at least one network devices other than the second network device in response to receiving a first request from the second network device.
[0244] In some embodiments, the first request may include one of the following: the type of reference signal requested by the user device, validity information indicating the validity period of the data acquisition session, or area information indicating the area in which the user device performs data acquisition.
[0245] In some embodiments, the method may further include receiving a second configuration of a wireless bearer to user equipment from a second network device, the second configuration being transmitted by a third network device, of which at least one network device, via a handover response.
[0246] In some embodiments, the second configuration may be transmitted when the third network device receives a handover request from the second network device requesting to hand over user equipment to the third network device.
[0247] In some embodiments, a handover request may include one of the following: an instruction indicating that a data collection session is triggered by a first network device; that the data collection session is performed via an LPP message on the CP; that the data collection session is performed via an LPP message on the UP; area information indicating the area in which the user equipment will perform data collection; or validity information indicating the validity period of the data collection session.
[0248] In some embodiments, one of the first or second configurations may include, namely, a signaling radio bearer (SRB) configured for the user device when the data acquisition session is performed on the CP via LPP messages, or a data radio bearer (DRB) configured for the user device when the data acquisition session is performed on the UP via LPP messages.
[0249] In some embodiments, the method may further include transmitting the collected data to a first network device via a transceiver.
[0250] In some embodiments, the collected data may be transmitted to the first network device if the user device is in the area of a third network device after a handover to that network device.
[0251] In some embodiments, the method may further include receiving from a second network device a third configuration for transmitting collected data for training models related to artificial intelligence / machine learning (AI / ML) based positioning or channel state information compression, channel state information prediction, or beam prediction.
[0252] In some embodiments, the third configuration may include one of the following: a period for transmitting collected data, a period for logging measurements, an event that triggers the transmission of collected data, an event that triggers the logging of measurements, an instruction indicating that user equipment should not discard untransmitted collected data, or trace information including a trace reference or a trace recording session reference.
[0253] In some embodiments, the handover request may further include either an instruction indicating that the user device is configured not to discard any collected data that has not been transmitted, or trace information.
[0254] In some embodiments, the method may further include receiving a second request from a third network device for collected data that has not been transmitted after a handover to the third network device.
[0255] In some embodiments, the method may further include transmitting to a third network device either untransmitted collected data or trace information related to the collected data.
[0256] In some embodiments, the collected data that has not been transmitted may be further transmitted from the third network device to the second network device.
[0257] In some embodiments, the method may further include discarding untransmitted collected data if a second request is not received within a time period.
[0258] In some embodiments, the time period may include one of the following: a pre-configured time period after the collected data has been generated, the period of an inactive timer, or the period of a timer configured by a second network device.
[0259] Figure 12 shows a flowchart of method 1200 supporting data acquisition according to an aspect of this disclosure. The operation of method 1200 may be carried out by a device or its components, as described herein. For example, the operation of method 1200 may be carried out by a first network entity 102 or a core network 106, as described herein. In some implementations, a device may execute a set of instructions for controlling the functional elements of the device to perform the described functions. In addition or alternatively, a device may use dedicated hardware to perform aspects of the described functions.
[0260] In 1205, the method includes transmitting, via a transceiver, at least one measurement configuration determined by at least one network device to a user device, wherein the at least one measurement configuration is associated with data acquisition for model training. The operation of 1205 may be carried out according to the examples described herein. In some implementations, the operation of 905 may be carried out by the device described with reference to Figure 1.
[0261] In 1210, the method includes receiving data collected by the user device from the user device via a transceiver. The operation of 1210 may be carried out according to the examples described herein. In some implementations, the operation of 1210 may be carried out by the device described with reference to Figure 1.
[0262] In some embodiments, at least one measurement configuration may include one of the following: the type of reference signal related to positioning, resource information for the reference signal, the type of ground truth, validity information indicating the validity period of the data acquisition session, or area information indicating the area in which the user equipment performs data acquisition.
[0263] In some embodiments, 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 zones associated with geographic coordinates; one or more IDs of one or more areas associated with a list of cells; one or more tracking area codes (TACs) associated with a list of cells; or one or more tracking area identifiers (TAIs) associated with a list of cells.
[0264] In some embodiments, the method involves transmitting, via a transceiver, first information indicating that a data collection session has been triggered to a second network device among at least one network device, the second network device further including servicing, transmitting to user equipment.
[0265] In some embodiments, the first information may include, namely, an instruction indicating that a data collection session is triggered by a first network device; that the data collection session is performed on the control plane (CP) via Long-Term Evolution (LTE) Positioning Protocol (LPP) messages; that the data collection session is performed on the user plane (UP) via LPP messages; area information indicating the area in which user equipment performs data collection; or validity information indicating the validity period of the data collection session.
[0266] In some embodiments, the method may further include transmitting a first request via a transceiver to at least one network device for at least one measurement configuration determined by the at least one network device, the at least one measurement configuration being associated with data acquisition for model training, and receiving the at least one measurement configuration from the at least one network device.
[0267] In some embodiments, the method may further include receiving a request from a user device via a transceiver for at least one measurement configuration.
[0268] In some embodiments, the request may include one of the following: the type of reference signal requested by the user device, validity information indicating the validity period of the data acquisition session, or area information indicating the area in which the user device performs data acquisition.
[0269] In some embodiments, the first information may be transmitted via a New Radio (NR) Positioning Protocol A (NRPPa) message.
[0270] Figure 13 shows a flowchart of method 1300 supporting data acquisition according to an aspect of this disclosure. The operation of method 1300 may be performed by a device or its components, as described herein. For example, the operation of method 1300 may be performed by a second network entity 103, as described herein. In some implementations, the device may execute a set of instructions for controlling the functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.
[0271] In 1305, the method includes transmitting a handover request via a transceiver to a third network device, which includes first information relating to data acquisition for beam prediction, wherein the second and third network devices are located in the area where user equipment performs data acquisition. The operation of 1305 may be carried out according to the examples described herein. In some implementations, the operation of 1305 may be carried out by the device described with reference to Figure 1.
[0272] In 1310, the method includes receiving a handover response from a third network device, which includes a radio resource control (RRC) configuration for the handover procedure. The operation of 1310 may be carried out according to the examples described herein. In some implementations, the operation of 1310 may be carried out by the device described with reference to Figure 1.
[0273] In some embodiments, the method may further include transmitting a first request related to data collection from user equipment to a third network device via a transceiver.
[0274] In some embodiments, the first request may include, namely, an instruction requesting the third network device to provide beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, a beam measurement identifier (ID), the duration for which the user equipment performs the beam measurement, the duration for which the user equipment logs the beam measurement, the duration for which the user equipment transmits the beam measurement, the period for which the beam measurement is performed, the period for which the beam measurement is logged, the period for which the beam measurement is transmitted, second information relating to at least one beam requested by the second network device to be measured, or one of the types of beam measurements requested by the second network device.
[0275] In some embodiments, the type may include, namely, one of a first number of beam indices having a stronger reference signal received power (RSRP) among multiple beams of a third network device, and one or more beam indices having one or more RSRPs higher than a first threshold of a second network device.
[0276] 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 will be handed over, or a third piece of beam prediction information.
[0277] In some embodiments, the third beam prediction information may include, namely, 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 having stronger RSRPs among a plurality of beams of the second network device, a list of at least one beam predicted to have at least one RSRP higher than a second threshold, at least one value representing the likelihood 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 residence time of at least one predicted beam.
[0278] In some embodiments, the first information may further include, namely, second information relating to at least one beam to be measured when the first requirement does not include the second information, or one of the types of beam measurement when the first requirement does not include the type.
[0279] In some embodiments, the RRC configuration may include one of the following: a first configuration for user equipment to perform random access to a target cell using the predicted beam having the strongest RSRP among multiple beams of a third network device; a second configuration for user equipment to perform beam measurements based on a handover request and a first request; a third configuration for user equipment to log beam measurements based on a handover request and a first request; or a fourth configuration for user equipment to transmit beam measurements based on a handover request and a first request.
[0280] In some embodiments, the method may further include transmitting an RRC configuration to user equipment via a transceiver and receiving beam measurements from a third network device via the transceiver after the user equipment has been handed over from the second network device to the third network device.
[0281] In some embodiments, the method may further include receiving a second request from a third network device via a transceiver, relating to data collection from user equipment.
[0282] In some embodiments, the second requirement may include, namely, an instruction requesting the second network device to provide past beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, a duration for which the second network device is requested to provide past beam measurements within that duration before the user equipment has been handed over from the second network device to the third network device, the type of past beam measurements requested by the third network device, the ID of the target cell to which the user equipment is handed over, or the ID of the source cell from which the user equipment is handed over.
[0283] In some embodiments, past beam measurements may be transmitted to a third network device via a handover request, or past beam measurements may be transmitted to a third network device after the handover is completed.
[0284] In some embodiments, the first information may further include, namely, a timestamp of a past beam measurement, or one of the values of the dwell time of one or more beams in a past beam measurement.
[0285] FIG. 14 shows a flowchart of a method 1400 that supports data collection according to aspects of the present disclosure. The operations of method 1400 may be performed by a device or its components as described herein. For example, the operations of method 1400 may be performed by the third network entity 104 as described herein. In some implementations, a 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 implement aspects of the described functions using dedicated hardware.
[0286] At 1405, the method includes receiving, via a transceiver, a handover request from a second network device that includes first information related to data collection for beam prediction, wherein the second network device and a third network device are located in an area where a user equipment performs the data collection. The operations of 1405 may be implemented in accordance with the examples described herein. In some implementations, aspects of the operations of 1405 may be performed by the device described with reference to FIG. 1.
[0287] At 1410, the method includes transmitting, via the transceiver, a handover response to the second network device that includes a radio resource control (RRC) configuration for a handover procedure. The operations of 1410 may be implemented in accordance with the examples described herein. In some implementations, aspects of the operations of 1410 may be performed by the device described with reference to FIG. 1.
[0288] In some embodiments, the method may further include receiving, via the transceiver, a first request related to data collection of the user equipment from the third network device.
[0289] In some embodiments, the first request may include, namely, an instruction requesting the third network device to provide beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, a beam measurement identifier (ID), the duration for which the user equipment performs the beam measurement, the duration for which the user equipment logs the beam measurement, the duration for which the user equipment transmits the beam measurement, the period for which the beam measurement is performed, the period for which the beam measurement is logged, the period for which the beam measurement is transmitted, second information relating to at least one beam requested by the second network device to be measured, or one of the types of beam measurements requested by the second network device.
[0290] In some embodiments, the type may include, namely, one of the following: an index of a first number of beams having a stronger 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; an RSRP of one or more beams; an RSRP of available beams for beam measurement; or an RSRP of beams indicated by a second network device.
[0291] 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 will be handed over, or a third piece of beam prediction information requested by a second network device.
[0292] In some embodiments, the third beam prediction information 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 higher than a second threshold; at least one value representing the likelihood 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 residence time of at least one predicted beam.
[0293] In some embodiments, the handover response may further include, namely, second information relating to at least one beam to be measured when the first request does not include second information, or one of the types of beam measurements when the first request does not include type.
[0294] In some embodiments, the RRC configuration may include one of the following: a first configuration for user equipment to perform random access to a target cell using the predicted beam having the strongest RSRP among multiple beams of a third network device; a second configuration for user equipment to perform beam measurements based on a handover request and a first request; a third configuration for user equipment to log beam measurements based on a handover request and a first request; or a fourth configuration for user equipment to transmit beam measurements based on a handover request and a first request.
[0295] In some embodiments, the method may further include receiving beam measurements from user equipment via a transceiver after the user equipment has been handed over from a second network device to a third network device, and transmitting beam measurements to the second network device via the transceiver.
[0296] In some embodiments, the method may further include transmitting a second request related to data collection from user equipment to a second network device via a transceiver.
[0297] In some embodiments, the second request includes, namely, an instruction requesting the second network device to provide past beam measurements of the user equipment after the user equipment has been handed over from the second network device to the third network device, a duration for which the second network device is requested to provide past beam measurements within that duration before the user equipment has been handed over from the second network device to the third network device, the type of past beam measurements requested by the third network device, the ID of the target cell to which the user equipment is handed over, or the ID of the source cell from which the user equipment is handed over.
[0298] In some embodiments, past beam measurements may be transmitted to a third network device via a handover request, or past beam measurements may be transmitted to a third network device after the handover is completed.
[0299] In some embodiments, the first information may further include, namely, a timestamp of a past beam measurement, or one of the values of the dwell time of one or more beams in a past beam measurement.
[0300] It should be noted that the methods described herein represent possible implementations, that the operations and steps may be rearranged or possibly modified, and that other implementations are possible. Furthermore, two or more embodiments of these methods may be combined.
[0301] The various exemplary blocks and components described in this disclosure may be implemented or carried out using general-purpose processors, DSPs, ASICs, CPUs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, 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 working with a DSP core, or any other such configuration).
[0302] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or a combination thereof. When implemented in software executed by a processor, the functions may be stored in or transmitted through a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of this disclosure and the accompanying claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination thereof. The features implementing the functions may also be physically located in various locations, including the distribution of parts of the functions so that they are implemented in various physical locations.
[0303] Computer-readable media include both non-temporary computer storage media and communication media, including any media that facilitate the transfer of computer programs from one location to another. Non-temporary storage media can be any available media that can be accessed by a general-purpose or dedicated computer. For example, non-temporary computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-temporary media that can be used to carry or store desired program code means in the form of instructions or data structures, and can be accessed by a general-purpose or dedicated computer or a general-purpose or dedicated processor.
[0304] As used herein, including in the claims, the article “a” preceding an element is unrestricted and is understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” used in a list of items (for example, a list of items ending with a phrase such as “at least one of,” “one or more of,” or “one or both of”) indicates an inclusive list, for example, such that 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). Also, as used herein, the phrase “based on” should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be construed in the same way as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” may include one or more elements.
[0305] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications of this disclosure will become 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. Accordingly, this disclosure should be given the broadest scope that is consistent with the principles and novel features disclosed herein, and is not limited to the examples and designs described herein. [Explanation of symbols]
[0306] 20 User Devices 100 Wireless communication systems, communication environments 102 Network Entities, Satellite, BS 103 Second Network Entity 104 User Equipment (UE) 106 Core Network 108 Packet Data Network 110 Communication Link 112 Geographical Coverage Area 114 Communication Link 116 Backhaul Link, Communication Link 118 Application Server 160 CU 200A Process 200B Process 201 User Equipment 202 First Network Device 203 Second Network Device 204 Third Network Device 207 Measurement Configuration 223 Collected Data 237 Handover Request 247 Handover Response 257 Handover Response 300 Process 400 Process 401 UE 402 LMF 403 Serving gNB 404 gNB 500 Process 501 UE 502 LMF / Serving gNB 503 gNB 600 Process 601 UE 602 Serving gNB 603 gNB 700 Process 701 UE 702 Source gNB 703 Target gNB 800 Process 801 Source gNB 802 Target gNB 803 Target gNB 900 devices 902 Processor 904 memory 906 Transceiver 908 I / O Controller 910 Antenna 1000 processors, arithmetic logic units (ALUs) 1002 Controller 1004 memory 1100 methods 1200 methods 1300 methods 1400 methods
Claims
1. Processor and A transceiver coupled to the aforementioned processor and User equipment equipped with, The aforementioned processor, Receiving, via the transceiver, at least one measurement configuration determined by at least one network device from a first network device, wherein the at least one measurement configuration is associated with data acquisition for model training, Performing measurements on a reference signal associated with data acquisition for model training based on the aforementioned at least one measurement configuration, User equipment configured to perform the following actions.
2. The aforementioned at least one measurement configuration is as follows: The type of the aforementioned reference signal, Resource information for the aforementioned reference signal, Grand Truth type, Effectiveness information indicating the effective duration of the data collection session, or Area information indicating the area in which the user device performs the data collection. The user device according to claim 1, comprising one of the following:
3. The aforementioned processor, Transmitting, via the transceiver, first information indicating that the data collection session is triggered to a second network device among the at least one network device, the second network device then services and transmits to the user equipment. The user device according to claim 1, further configured to perform the following:
4. The first piece of information mentioned above is the following, namely: An instruction indicating that the data collection session is triggered by the first network device, The data collection session is performed on the control plane (CP) via Long-Term Evolution (LTE) Positioning Protocol (LPP) messages. The session for the aforementioned data collection is executed on the user plane (UP) via LPP messages. Area information indicating the area in which the user device performs the data collection, or Effectiveness information indicating the effective duration of the session for the aforementioned data collection. The user device according to claim 3, comprising one of the following:
5. The aforementioned processor, Receiving a second configuration of a wireless bearer to the user equipment from a second network device, wherein the second configuration is transmitted and received by a third network device among the at least one network device via a handover response. The user device according to claim 1, further configured to perform the following:
6. The user device according to claim 5, wherein the second configuration is transmitted when the third network device receives a handover request from the second network device requesting the handover of the user device to the third network device.
7. The aforementioned handover request is as follows: An instruction indicating that the data collection session is triggered by the first network device, The session for the aforementioned data collection is executed on the CP via LPP messages. The session for the aforementioned data collection is executed on UP via LPP messages. Area information indicating the area in which the user device performs the data collection, or Effectiveness information indicating the effective duration of the session for the aforementioned data collection. The user device according to claim 6, comprising one of the following.
8. One of the first configuration or the second configuration is the following, namely: A signaling radio bearer (SRB) configured for the user device when the data collection session is executed on the CP via LPP messages, or A data radio bearer (DRB) is configured for the user device when the data collection session is executed via LPP messages on UP. The user device according to claim 5, comprising one of the following.
9. The aforementioned processor, The collected data is transmitted to the first network device via the transceiver. The user device according to claim 1, further configured as follows.
10. The user device according to claim 9, wherein the collected data is transmitted to the first network device when the user device is in the area after a handover to the third network device.
11. The aforementioned processor, The user device according to claim 9, further configured to receive a third configuration from a second network device for transmitting the collected data for model training related to artificial intelligence / machine learning (AI / ML) based positioning, channel state information compression, channel state information prediction, or beam prediction.
12. The third configuration is as follows: The transmission cycle for the aforementioned collected data, The period for recording the above measurement in the log, An event that triggers the transmission of the aforementioned collected data, An event that triggers logging of the aforementioned measurement, An instruction indicating that the user device will not discard the collected data that has not been transmitted, or Trace information including trace references or trace recording session references The user device according to claim 11, comprising one of the following:
13. The handover request is as follows: Instructions indicating that the user device is configured not to discard the collected data that has not been transmitted, or The aforementioned trace information The user device according to claim 12, further comprising one of the following.
14. The aforementioned processor, The user device according to claim 11, further configured to receive a second request from a third network device for the collected data that has not been transmitted after a handover to the third network device.
15. Processor and A transceiver coupled to the aforementioned processor and A first network device comprising, The aforementioned processor, Transmitting to user equipment 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 acquisition for model training. The transceiver receives data collected by the user device from the user device. A first network device configured to perform the following actions.
16. Processor and A transceiver coupled to the aforementioned processor and A second network device comprising, The aforementioned processor, Transmitting a handover request to a third network device via the transceiver, which includes first information relating to data acquisition for beam prediction, wherein the second and third network devices are located in the area where user equipment performs data acquisition. The third network device receives a handover response, including a radio resource control (RRC) configuration for the handover procedure. A second network device configured to perform the following actions.
17. The aforementioned processor, The second network device according to claim 16, further configured to transmit a first request relating to the data collection of the user device to the third network device via the transceiver.
18. The first requirement is as follows: An instruction to request the third network device to provide beam measurement of the user device after the user device has been handed over from the second network device to the third network device, The identifier (ID) of the beam measurement, The duration during which the user equipment performs the beam measurement, The duration for which the user device logs the beam measurement, The duration for which the user device transmits the beam measurement, The period during which the beam measurement is performed, The period for recording the beam measurement in the log, The transmission period for the beam measurement, Second information relating to at least one beam that the second network device has requested to be measured, or The type of beam measurement required by the second network device A second network device according to claim 17, comprising one of the following:
19. The first piece of information mentioned above is the following, namely: Beam measurement identifier (ID), The ID of the target cell to which the user device will be handed over, or Third piece of information on beam prediction A second network device according to claim 16, comprising one of the above.
20. Processor and A transceiver coupled to the aforementioned processor and A third network device comprising, The aforementioned processor, Receiving a handover request from a second network device via the transceiver, which includes first information related to data acquisition for beam prediction, wherein the second and third network devices are located in the area where user equipment performs data acquisition, and receiving The transceiver transmits a handover response to the second network device, including a radio resource control (RRC) configuration for the handover procedure. A third network device configured to perform the following actions.
