Data collection method, communication device, communication system, storage medium, and program product
By utilizing the first and second network elements in the communication system to identify the target terminal and collect its associated data, the problem of low data collection efficiency in machine learning models is solved, thereby improving system performance and communication efficiency.
Patent Information
- Application Number
- PCT/CN2026/089720
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-09
- Publication Date
- 2026-11-12
AI Technical Summary
In existing technologies, machine learning models lack effective data collection methods in communication systems, resulting in poor data correlation and low system performance and communication efficiency.
By receiving and sending information requests, the system collects associated data of specified services or specified data types from the target terminal, and uses the first and second network elements to determine the target terminal from candidate terminals, thereby achieving efficient data collection and association.
It improved system performance, saved costs, enhanced communication efficiency, and ensured the accuracy and timeliness of data.
Smart Images

Figure CN2026089720_12112026_PF_FP_ABST
Abstract
Description
Data collection methods, communication equipment, communication systems, storage media and software products Technical Field
[0001] This application relates to the field of communication technology, and in particular to data collection methods, communication equipment, communication systems, storage media, and program products. Background Technology
[0002] With the continuous development of Artificial Intelligence (AI) technology, the integration of AI and communication is reflected in all aspects of the communication technology field. Utilizing AI technology can effectively improve the overall performance of communication systems. Machine Learning (ML) algorithms are currently one of the most important implementation methods of AI technology. Machine learning can obtain models through large amounts of training data, and these models can then be used to predict events. Summary of the Invention
[0003] This application provides data collection methods, communication devices, communication systems, storage media, and program products.
[0004] A first aspect of this application provides a data collection method, which is executed by a first network element, and the method includes:
[0005] Receive first information sent by a second network element, the first information being used to request the collection of first data and / or second data from at least one target terminal;
[0006] Wherein, the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal;
[0007] The first data and the second data are associated data of a specified service or a specified data type of the target terminal.
[0008] A second aspect of this application provides a data collection method, which is executed by a second network element, and the method includes:
[0009] Send a first message to a first network element, the first message being used to request the collection of first data and / or second data from at least one target terminal;
[0010] Wherein, the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal;
[0011] The first data and the second data are associated data of a specified service or a specified data type of the target terminal.
[0012] A third aspect of this application provides a first network element, which includes:
[0013] The transceiver module is used to receive first information sent by the second network element, wherein the first information is used to request the collection of first data and / or second data from at least one target terminal;
[0014] Wherein, the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal;
[0015] The first data and the second data are associated data of a specified service or a specified data type of the target terminal.
[0016] A fourth aspect of this application provides a second network element, which includes:
[0017] The transceiver module is used to send first information to the first network element, wherein the first information is used to request the collection of first data and / or second data from at least one target terminal;
[0018] Wherein, the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal;
[0019] The first data and the second data are associated data of a specified service or a specified data type of the target terminal.
[0020] The solution proposed in this application involves receiving first information sent by a second network element. This first information requests the collection of first data and / or second data from at least one target terminal. The at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal. The first data and the second data are associated data of a specified service or data type of the target terminal. This enables the access network device to obtain associated first and second data when relevant data collection is required, effectively improving system performance, saving costs, and increasing system communication efficiency. Attached Figure Description
[0021] To more clearly illustrate the technical solutions in the embodiments or background art of this application, the following description of the accompanying drawings is provided. The following drawings are merely some embodiments of this application and do not impose specific limitations on the scope of protection of this application.
[0022] Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;
[0023] Figure 1B is a schematic diagram of a model training method provided in an embodiment of this application;
[0024] Figures 2A-2B are interactive schematic diagrams of a data collection method provided in an embodiment of this application;
[0025] Figures 3A-3B are interactive schematic diagrams of a data collection method provided in an embodiment of this application;
[0026] Figure 4A is a schematic diagram of the structure of a first network element provided in an embodiment of this application;
[0027] Figure 4B is a schematic diagram of the structure of a second network element provided in an embodiment of this application;
[0028] Figure 4C is a schematic diagram of the structure of an access network device provided in an embodiment of this application;
[0029] Figure 5A is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0030] Figure 5B is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation
[0031] This application provides data collection methods, communication devices, communication systems, storage media, and program products.
[0032] In a first aspect, embodiments of this application propose a data collection method, the method comprising:
[0033] The system receives first information sent by a second network element, the first information being used to request the collection of first data and / or second data from at least one target terminal; wherein the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal;
[0034] The first data and the second data are associated data of a specified service or a specified data type of the target terminal.
[0035] Secondly, embodiments of this application propose a data collection method, the method comprising:
[0036] Send a first message to a first network element, the first message being used to request the collection of first data and / or second data from at least one target terminal;
[0037] Wherein, the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal;
[0038] The first data and the second data are associated data of a specified service or a specified data type of the target terminal.
[0039] Thirdly, embodiments of this application propose a data collection method, the method comprising:
[0040] Send a second message to the second network element, the second message being used to instruct the access network device to request the collection of the first data and / or the second data.
[0041] In the above embodiments,
[0042] Fourthly, embodiments of this application propose a first network element, which includes a transceiver module; wherein the first network element is used to execute the first aspect and optional implementations of the first aspect.
[0043] Fifthly, embodiments of this application propose an access network device, which includes a transceiver module; wherein the first network element is used to execute the second aspect and the optional implementation of the second aspect.
[0044] In a sixth aspect, embodiments of this application propose a first network element, which includes one or more processors; wherein the first network element is used to execute the first aspect and optional implementations of the first aspect.
[0045] In a seventh aspect, embodiments of this application provide an access network device, which includes one or more processors; wherein the access network device is used to execute the second aspect and optional implementations of the second aspect.
[0046] Eighthly, embodiments of this application provide a communication device for executing the first aspect and optional implementations of the first aspect, as well as the second aspect and optional implementations of the second aspect.
[0047] Ninthly, embodiments of this application propose a communication system, which includes: a first network element and an access network device; wherein the first network element is configured to perform the method described in the first aspect and the optional implementation of the first aspect, and the access network device is configured to perform the method described in the second aspect and the optional implementation of the second aspect.
[0048] In a tenth aspect, embodiments of this application provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.
[0049] In the eleventh aspect, embodiments of this application provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.
[0050] In a twelfth aspect, embodiments of this application provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its optional implementations, the second aspect and its optional implementations.
[0051] In a thirteenth aspect, embodiments of this application provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the first aspect and its optional implementations, the second aspect, and its optional implementations.
[0052] It is understood that the aforementioned terminals, network devices, communication devices, communication systems, storage media, and program products are all used to execute the methods proposed in the embodiments of this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0053] This application provides data collection methods, communication devices, communication systems, storage media, and program products. In some embodiments, the terms data collection method, information processing method, data processing method, and communication method may be used interchangeably.
[0054] The embodiments in this application are not exhaustive, but merely illustrative of some embodiments, and are not intended to limit the scope of protection of this application. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In the embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0055] The terminology used in the embodiments of this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application.
[0056] In the embodiments of this application, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun after the article can be understood as either a singular expression or a plural expression.
[0057] In the embodiments of this application, "multiple" refers to two or more.
[0058] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0059] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0060] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.
[0061] The prefixes "first," "second," etc., used in the embodiments of this application are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0062] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0063] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0064] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0065] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0066] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.
[0067] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0068] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0069] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0070] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, various embodiments of this application can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.
[0071] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.
[0072] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0073] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0074] Furthermore, each element, each row, or each column in the table of this application embodiment can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0075] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of this application.
[0076] As shown in Figure 1A, the communication system 100 includes a terminal 101, an access network device 102, and a core network device 103.
[0077] In some embodiments, terminal 101 may include, for example, a mobile phone, a wearable device, an Internet of Things (IoT) device, a narrowband Internet of Things (NB-IoT) device, a satellite communication device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in assisted driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, a redcap terminal, and a positioning reference unit (PRU), but is not limited thereto.
[0078] In some embodiments, the access network device 102 may be a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, nodes such as satellites or airborne platforms in non-terrestrial networks, evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), next-generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in Wi-Fi system.
[0079] In some embodiments, the technical solutions of this application can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this application can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0080] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0081] In some embodiments, the core network device 103 may be a single device, including a first network element 1031, a second network element 1032, a third network element 1033, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element 1031, the second network element 1032, the third network element 1033, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
[0082] In some embodiments, the first network element 1031 is, for example, a location management function (LMF), a sensing function (SF), etc.
[0083] In some embodiments, the first network element 1031 is used to "manage specified services (such as location services, sensing services, etc.) or manage related services for obtaining specified data types, etc." The name is not limited to this.
[0084] In some embodiments, the second network element 1032 is, for example, an Access and Mobility Management Function (AMF), etc.
[0085] In some embodiments, the second network element 1032 is used for "managing the access and mobility of users in the network, user access management or user mobility management, realizing signaling interaction between the access network and the core network, etc.", and the name is not limited thereto.
[0086] In some embodiments, the third network element 1033 is, for example, Unified Data Management (UDM), etc.
[0087] In some embodiments, the third network element 1033 is used for "storing and managing user data, storing and managing user privacy inspection data, etc.", and the name is not limited thereto.
[0088] In some embodiments, the first network element 1031 can be independent of the core network device 103.
[0089] In some embodiments, the first network element 1031 may be part of the core network device 103.
[0090] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions proposed in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in the embodiments of this application are also applicable to similar technical problems.
[0091] The following embodiments of this application can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0092] The embodiments of this application can be applied to 4G and 5G NR dual connectivity (E-UTRAN-NR Dual Connectivity, EN-DC), standalone NR carrier aggregation, 5G NR and 4G dual connectivity (NR-E-UTRAN Dual Connectivity, NE-DC), NR-NR Dual Connectivity, NR-DC, Non-terrestrial Network (NTN), Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), 6G new radio (NR), Future Radio Access (FRA), and New-Radio Access technologies. Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20. Ultra-Wideband (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Narrow Band-IoT (NB-IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other data collection methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G / 6G).
[0093] With the continuous development of Artificial Intelligence (AI) technology, the integration of AI with communication is reflected in all aspects of the communication technology field. Utilizing AI technology can effectively improve the overall performance of communication systems. Machine Learning (ML) algorithms are currently one of the most important implementation methods of AI technology. Machine learning can obtain models through large amounts of training data, and these models can then be used to predict events.
[0094] In some embodiments, AI / ML can be used to improve the performance of many communication services, such as location services and sensing services. For example, in location services, AI / ML can be used directly for positioning, or AI / ML can be used to assist in positioning.
[0095] In some embodiments, when using AI / ML to improve service performance, the AI model can be deployed on the terminal side, the access network equipment side, or the core network equipment side.
[0096] In some embodiments, when deploying an AI model on the access network device side, training the AI model requires multiple datasets as training data input into the model, as shown in Figure 1B. A dataset needs to contain two parts: Part A parameters (i.e., measurement-related information, i.e., measurement-related information obtained by the access network device through measurement) and Part B parameters (i.e., information related to the ground truth label, i.e., the ground truth value used as the label during model training). Furthermore, Part A and Part B parameters in a dataset should be correlated. Considering that Part A parameters come from the TRP and Part B parameters come from core network elements, it is also necessary to consider how to correlate the two parts of parameters.
[0097] The data collection method, communication equipment, communication system, storage medium, and program products provided in this application will be described in detail below with reference to the accompanying drawings.
[0098] Figure 2A is an interactive schematic diagram of a data collection method according to an embodiment of this application. As shown in Figure 2A, the embodiment of this application relates to a data collection method, which includes:
[0099] In step S2101, the access network device 102 sends the second information.
[0100] In some embodiments, the second network element 1032 receives the aforementioned second information sent by the access network device 102.
[0101] In some embodiments, the second information described above is used to instruct the access network device 102 to request data collection from the terminal 101.
[0102] In some embodiments, the second information described above is used to instruct the access network device 102 to request the collection of first data and / or second data from the terminal 101.
[0103] In some embodiments, the aforementioned second information is used to indicate the need to collect first data and / or second data from terminal 101.
[0104] Among them, the first data and the second data are related data, and the first data and the second data are data for a specific business or data of a specific data type.
[0105] Optionally, the specified services mentioned above may include, but are not limited to: location services, sensing services, etc.
[0106] Optionally, the specified data types mentioned above may include, but are not limited to: location data, sensing data, data related to location services, data related to sensing services, etc.
[0107] In some embodiments, the first data is the ground truth corresponding to the second data, and the second data is the measurement information of the access network device 102 for the specified service or specified data type of the terminal 101.
[0108] Optionally, the second data may be obtained by the access network device 102 based on measurements; the first data may be the true measurement value corresponding to the second data determined by the first network element 1031.
[0109] As an example, taking a location service as an example, the first data mentioned above can be determined by the first network element 1031 based on the location information of the terminal 101, and the second data mentioned above can be obtained by the access network device 102 performing measurements on the terminal 101 under the location service. The first data and the second data are corresponding and related, and the first data can serve as the true value of the second data.
[0110] Optionally, the first data mentioned above may be obtained by the first network element 1031 in combination with the location information and other information of the terminal 101, such as the location information and environmental information of the physical transmission and reception functions of the configured base station side (such as gNB), such as the Transmission and Reception Point (TRP), or the historical location measurement data of the terminal 101.
[0111] Optionally, the first network element 1031 can determine the location information of the terminal 101 based on the measurement of the access network device 102.
[0112] Optionally, the first network element 1031 can also obtain the location information of the terminal 101 through other means, such as through the Global Navigation Satellite System (GNSS).
[0113] Alternatively, the terminal 101 may also be a positioning reference unit (PRU).
[0114] Optionally, the location information of terminal 101 can be the UE location information obtained in the current positioning process, or it can be the location truth value of the qualified terminal obtained by the first network element triggering a new positioning process, or the location truth value of the qualified terminal obtained through local configuration and implementation (such as the location information of the configured PRU).
[0115] In some embodiments, the access network device 102 may, based on its own implementation, determine that it is necessary to collect the first data and / or the second data of the terminal, and then send the aforementioned second information.
[0116] In some embodiments, the access network device 102 may determine, based on its own implementation, when to trigger the second information and whether to trigger the second information.
[0117] In some embodiments, the second information described above includes at least one of the following:
[0118] Condition information, which is used to indicate the conditions that the collected data needs to meet as the first data and / or the second data.
[0119] A candidate terminal list, which includes at least one candidate terminal.
[0120] Optionally, the candidate terminal list includes at least one identifier for a candidate terminal. The identifier for a candidate terminal may be, for example, a Next Generation Application Protocol User Equipment Identifier (NGAP) user equipment identifier corresponding to the terminal. Alternatively, the identifier for a candidate terminal may be other user temporary identifiers or routing identifiers that can uniquely identify (or determine) the candidate terminal, etc., and this disclosure does not limit this approach.
[0121] Optionally, the aforementioned condition information refers to the fact that the data requested to be collected can serve as a condition required by the first data and / or the second data. For example, the aforementioned condition information may include, but is not limited to, valid time information, valid area information, etc.
[0122] As an example, if the access network device 102 determines the second data itself but needs to request the first data from the first network element 1031, the access network device 102 can indicate in the second information the effective time for synchronizing the first data and the second data. That is, the effective time for the collected data to be used as the measurement truth value corresponding to the second data. For example, the terminal location information obtained within this effective time can be used as a reference for determining the first data corresponding to the second data.
[0123] In some embodiments, the name of the second information is not limited, and may be, for example, “measurement request”, “measurement request message”, “data collection request”, “data collection request message”, “business data collection request”, etc.
[0124] In step S2102, the second network element 1032 determines at least one target terminal.
[0125] In some embodiments, the second network element 1032 determines at least one target terminal based on the received second information.
[0126] The aforementioned target terminal refers to the terminal that participates in the aforementioned data collection.
[0127] In some embodiments, the second network element 1032 determines at least one target terminal from at least one candidate terminal based on the aforementioned second information.
[0128] In some embodiments, the second information includes a list of candidate terminals participating in the location information collection. The second network element 1032 can select a target terminal from the corresponding list or use the candidate terminal list as a reference only, or select a terminal outside the list as the target terminal to participate in the information collection.
[0129] In some embodiments, the second information may not include the candidate terminal list. The second network element 1032 may select the target terminal list for data collection based on its own implementation or based on the condition information included in the second information.
[0130] In some embodiments, the second network element 1032 performs a user consent check based on the aforementioned second information.
[0131] In some embodiments, the second network element 1032 performs a user consent check on the candidate terminal to identify at least one target terminal that participated in the aforementioned data collection.
[0132] In some embodiments, user consent checks may include: user permission checks, user privacy checks, user authorization checks, service privacy profile checks, etc. A user consent check can also be a user privacy check. A user consent check can be included within a user consent privacy check, and vice versa; that is, a user privacy check can be included within a user consent check.
[0133] In some embodiments, the second network element 1032 can determine the purpose information for the access network device 102 to collect the first data and / or the second data based on the aforementioned second information. Further, the second network element 1031 can perform a user consent check based on this purpose information to obtain the user consent check result corresponding to the purpose information.
[0134] It is understood that the aforementioned purpose information can be used to instruct the access network device 102 on the purpose of requesting the collection of the first and / or second data. For example, the purpose for the access network device 102 to request the collection of data may be, for example, for model training on the access network device side, for determining relevant information of the terminal, etc., but is not limited to these.
[0135] In some embodiments, the second information may include the aforementioned objective information.
[0136] In some embodiments, the second network element 1032 stores the user consent check result for the terminal (for example, the second network element 1032 may have previously performed a user consent check for the terminal for other reasons, etc.), and the second network element 1032 can directly obtain the user consent check result of the terminal corresponding to the above-mentioned purpose information.
[0137] In some embodiments, if the second network element 1032 does not store the user consent check result for the terminal, the second network element 1032 can obtain the user consent check result corresponding to the aforementioned purpose information from the third network element 1033 via the first network element 1031. The second network element 1032 can perform the user consent check and obtain the user consent check result corresponding to the purpose information by retrieving, based on the purpose information, information related to user consent stored in the third network element 1033.
[0138] Optionally, the second network element 1032 can store the obtained results.
[0139] Optionally, the second network element 1032 may also store all the information related to user consent of the terminal (for example, the second network element 1032 may obtain and store user consent-related information for other purposes from the third network element 1033).
[0140] In some embodiments, the second network element 1032 can also subscribe to user consent check result change notifications for the terminal through the first network element 1031 to the third network element 1033. When the user consent check result of the terminal changes, the third network element 1033 can send a change notification to the first network element 1032.
[0141] Further, optionally, after receiving the above-mentioned change notification, the second network element 1032 can obtain the user consent check result after the terminal change from the third network element 1033 through the first network element 1031.
[0142] Further, optionally, the second network element 1032 may send information to the access network device 102 to indicate to the access network device 102 that the user of the terminal agrees to the change of the inspection result.
[0143] Furthermore, the access network device 102 can also perform corresponding operations based on the information indicating the change, such as triggering the access network device 102 to perform the above-mentioned step S2101, etc.
[0144] In some embodiments, the user consent check result of the terminal can also be a default value, and the second network element 1032 can determine the user consent check result corresponding to the aforementioned purpose information of the terminal as the default value based on an agreement. Optionally, the default value can be consent or disagreement.
[0145] For example, if the terminal is a PRU, the user's consent check result can be considered as default consent.
[0146] In some embodiments, if the data of the second information request has already been used as the context information of the terminal at the second network element 1032 and can be obtained by the second network element 1032, step S2108 can be executed directly.
[0147] In step S2103, the second network element 1032 sends the first information.
[0148] In some embodiments, after determining at least one target terminal participating in the data collection, the second network element 1032 may send first information to the first network element 1031, the first information being used to request the first network element 1031 to collect first data and / or second data of the target terminal.
[0149] Optionally, the first information may include a list of candidate terminals (sent by the access network device through the second information, or implemented by the second network element itself, or determined based on the condition information included in the second information). The list of candidate terminals includes the identifier of at least one candidate terminal. The identifier of a candidate terminal may be, for example, a Subscription Permanent Identifier (SUPI) corresponding to the candidate terminal, or it may be other generic public subscription identifiers (GPSI), application layer identifiers, temporary user identifiers, or routing identifiers that can uniquely identify (or determine) the candidate terminal, etc. This disclosure does not limit this.
[0150] Optionally, if the second information contains a list of candidate terminals, and the identification information of the candidate terminals in the first information is different from the identification information of the (same) candidate terminals in the second information, after receiving the list of candidate terminals, the second network element can check the locally stored information based on the identification of the candidate terminals contained in the list of candidate terminals and perform identification mapping to convert the identification information of the candidate terminals in the first information into the identification information of the candidate terminals in the second information. For example, the NGAP user equipment identification corresponding to the candidate terminal in the candidate terminal list can be converted into a SUPI that can be recognized by the first network element.
[0151] In some embodiments, the first network element 1031 receives the first information sent by the second network element 1032.
[0152] In some embodiments, the first information is determined by the second network element 1032 based on the second information sent by the access network device 102.
[0153] In some embodiments, the first network element 1031 may configure the access network device 102 to perform related operations to obtain the second data based on the first information described above.
[0154] In some embodiments, the first information described above includes at least one of the following:
[0155] Type information, wherein the type information is used to indicate the type of data collection requested in the first information request;
[0156] Identification of access network device 102;
[0157] The aforementioned users agree to the inspection results.
[0158] Optionally, the above-mentioned data collection types include at least one of the following:
[0159] Collect the aforementioned second data in the specified manner;
[0160] Get the first data.
[0161] As an example, if the type of data collection described above is: the access network device 102 collects the second data, which can be used to request the configuration of the access network device 102 to perform the corresponding measurement, so that the access network device 102 can obtain and use the second data based on its own needs.
[0162] Optionally, if the first data and the second data are not acquired in the same measurement trigger—for example, if the terminal location truth value for acquiring the first data is not acquired through the second data in the same measurement process, but through other means such as another positioning process, configuration information, or information locally stored by the first network element 1031—then the first network element 1031 can configure only the corresponding access network device 102 to perform measurement data collection and store the data in the access network device 102. The access network device 102 does not need to report the measurement data to the first network element 1031, thus completing the collection of the second data by the access network device 102. For example, the location information of the positioning reference unit (PRU) is known, or the terminal location truth value can be obtained using a positioning method that does not require the measurement data requested in a).
[0163] Optionally, the purpose of location information collection can be specified by the type of measurement requested, or by a separate parameter received from access network device 102 indicating the purpose of location information collection. It may also include relevant user privacy check results (e.g., whether the user consents to access network device 102 using the terminal's data for training).
[0164] As an example, if the type of data collection described above is: access network device 102 collects the second data, wherein the second data is not used for model training, but can be used to request the configuration of relevant measurements for access network device 102 to obtain the second data, but cannot be used for model training.
[0165] As an example, if the type of data collection is: access network device 102 collects the second data, and the second data is used by the first network element 1031 to determine the measurement truth value of the terminal, it can be used to request the access network device 102 to configure relevant measurements to obtain the second data, and return the second data to the first network element 1031 to determine the corresponding measurement truth value.
[0166] In some embodiments, the purpose for which the access network device 102 collects the first data and / or the second data can be indicated by the data collection type or by a separate parameter (such as the purpose information mentioned in the foregoing embodiments).
[0167] In some embodiments, the first information may also include the results of relevant user consent checks (e.g., whether the relevant terminal agrees to the access network device 102 using the terminal's data for model training, etc.).
[0168] In some embodiments, the name of the first information is not limited, and may be, for example, "measurement request", "measurement request message", "data collection request", "data collection request message", "business data collection request", "service operation request", etc.
[0169] In step S2104, the first network element 1031 sends the third information.
[0170] In some embodiments, the first network element 1031 can send the aforementioned third information to the access network device 102 through the second network element 1032.
[0171] In some embodiments, the third information is used to configure the access network device 102 to obtain the second data.
[0172] In some embodiments, if the second network element does not perform the user consent check in the aforementioned steps, the first network element 1031 may perform the user consent check before sending the aforementioned third information. It is understood that the steps for performing the user consent check can be described in any embodiment of this application, and will not be repeated here.
[0173] In some embodiments, the third information includes indication information, which is used to indicate that the first network element 1031 is configured with the data collection type of the access network device 102.
[0174] As an example, if the type of data collection indicated by the instruction information is: access network device 102 collects the second data, after receiving the third information, access network device 102 can perform related operations to obtain the second data, and does not need to send the second data to the first network element 1031.
[0175] As an example, if the type of data collection indicated by the instruction information is: access network device 102 collects the second data, wherein the second data is not used for model training, after receiving the third information, access network device 102 can perform relevant operations to obtain the second data, but cannot use it for model training, or cannot collect the second data for model training. However, access network device 102 can send the second data to the first network element 1031 to obtain relevant service information of the terminal (such as location information, etc.).
[0176] As an example, if the type of data collection described above is: access network device 102 collects the second data, and the second data is used by the first network element 1031 to determine the true value of the terminal's measurement, after receiving the third information, access network device 102 can perform relevant operations to obtain the second data. The second data can be used for model training. At the same time, access network device 102 can also collect the second data and report it to the first network element 1031 to obtain relevant service information of the terminal (such as location information, etc.).
[0177] In some embodiments, the name of the aforementioned third information is not limited, and may be, for example, "measurement response", "measurement response message", "data collection response", "data collection response message", "business data collection response", "data collection report", "business data collection report", "data collection instruction", "business data collection instruction", etc.
[0178] In step S2105, the first network element 1031 and / or access network device 102 collect the second data.
[0179] In some embodiments, the first network element 1031 may collect the aforementioned second data.
[0180] Optionally, the first network element 1031 can collect the aforementioned second data to determine the relevant service information of the terminal 101.
[0181] Optionally, the first network element 1031 collects the aforementioned second data that can be used for model training.
[0182] In some embodiments, the access network device 102 may collect the aforementioned second data.
[0183] Optionally, the access network device 102 may perform relevant operations and obtain the second data based on the type indicated in the third information above.
[0184] Optionally, the access network device 102 can collect and store the second data mentioned above, and can use the second data for training the model.
[0185] Optionally, the access network device 102 may also send the acquired second data to the first network element 1031, which will collect the data and return it to the access network device 102 in subsequent steps.
[0186] Step S2106: The first network element 1031 determines the first data.
[0187] In some embodiments, the first network element 1031 acquires the first data corresponding to the second data described above.
[0188] Optionally, the aforementioned first data may be obtained by the first network element 1031 based on the location information and / or other information of the terminal 101, such as the physical transmission and reception functions of the configured base station side (e.g., gNB), such as the location information and environmental information of the TRP, or the historical location measurement data of the terminal 101. The location information of the terminal 101 may be the UE location information obtained in the current positioning process, or it may be the true location value of a qualified terminal obtained by the first network element triggering a new positioning process, or the true location value of a qualified terminal obtained through local configuration and implementation (e.g., the location information of the configured PRU).
[0189] Optionally, the aforementioned first data may be the terminal's location information, or other information derived from the location information.
[0190] In step S2107, the first network element 1031 sends the fourth information.
[0191] In some embodiments, the first network element 1031 may send the aforementioned fourth information to the second network element 1032 based on the acquired data.
[0192] In some embodiments, the fourth information may include at least one of the following: the first data; the second data; and first correlation information (or association information).
[0193] The aforementioned first association information is used to determine the first and second data associated with each target terminal.
[0194] In other words, the access network device 102 can associate the first data and the second data for each target terminal based on the aforementioned first association information. That is, the associated first data and second data can be used as data in a single dataset for model training.
[0195] Optionally, if the target terminal is served by the access network device 102, the aforementioned first association information may include at least one of the following: the measurement ID corresponding to the first network element 1031, the Radio Access Network (RAN) measurement ID, the air interface positioning protocol transaction ID, the identifier of the target terminal, the timestamp, etc.
[0196] Optionally, in some scenarios, the air interface positioning protocol transaction identifier can also be called the New Radio Positioning Protocol A (NRPPa) transaction identifier (NRPPa transaction ID).
[0197] Optionally, in scenarios using other positioning protocols, the air interface positioning protocol transaction identifier can be referred to as the transaction identifier corresponding to the positioning protocol used in that scenario, and this disclosure does not limit this.
[0198] Optionally, if the target terminal is not served by the access network device 102 (e.g., served by a neighboring gNB, rather than a gNB participating in data collection), the aforementioned first association information may include at least one of the following: measurement ID corresponding to the first network element 1031, RAN measurement ID, air interface positioning protocol transaction ID, timestamp, etc.
[0199] In some embodiments, the name of the fourth information is not limited, and may be, for example, "data collection response", "data collection response message", "business data collection response", "data collection report", "business data collection report", "data report", "model training data collection", etc.
[0200] In step S2108, the second network element 1032 sends the fifth message.
[0201] In some embodiments, the second network element 1032 may determine the fifth information based on the received fourth information.
[0202] In some embodiments, the second network element 1032 may send the fifth information to the access network device 102 based on the received fourth information.
[0203] In some embodiments, the second network element 1032 may integrate the first data and / or second data corresponding to each target terminal based on the received fourth information.
[0204] Optionally, the second network element 1032 can integrate relevant information for different target terminals into different messages.
[0205] Optionally, the second network element 1032 can also integrate relevant information into the same message.
[0206] Optionally, the second network element 1032 can integrate the received information based on its own implementation.
[0207] In some embodiments, the fifth information may include at least one of the following: the first data; the second data; the second associated information; and a failure reason indication.
[0208] The aforementioned second association information is used to determine the first and second data associated with each target terminal.
[0209] In other words, the access network device 102 can associate the first data and the second data for each target terminal based on the aforementioned first association information. That is, the associated first data and second data can be used as data in a single dataset for model training.
[0210] Optionally, if the target terminal is served by the access network device 102, the aforementioned second associated information may include at least one of the following: the measurement ID corresponding to the first network element 1031, the RAN measurement ID, the air interface positioning protocol transaction ID, the identifier of the target terminal, the timestamp, etc.
[0211] Optionally, if the target terminal is not served by the access network device 102 (e.g., served by a neighboring gNB, rather than a gNB participating in data collection), the aforementioned second association information may include at least one of the following: measurement ID corresponding to the first network element 1031, RAN measurement ID, air interface positioning protocol transaction ID, timestamp, etc.
[0212] Optionally, the second association information may be the same as or different from the first association information.
[0213] In some embodiments, the second network element 1032 may determine the second association information based on the first association information in the fourth information.
[0214] Optionally, the second network element 1032 may modify the first association information based on some content stored locally to obtain the second association information (for example, the first association information only includes a timestamp, while the second association information adds the identifier of the target terminal and related measurement identifiers, etc.), and send it to the access network device 102 in the fifth information.
[0215] Optionally, the second network element 1032 may also directly send the first association information as the aforementioned second association information, including it in the aforementioned fifth information, to the access network device 102.
[0216] In some embodiments, if the above process fails for some terminals, the fifth message sent to these unsuccessful terminals may include the above failure reason indication, which is used to indicate the reason why the above process failed.
[0217] Optionally, messages indicating process failure and messages indicating process success can be contained in separate messages or in a single merged message.
[0218] In some embodiments, the name of the fifth information is not limited, and may be, for example, "data collection response", "data collection response message", "business data collection response", "data collection report", "business data collection report", "data report", "model training data collection", etc.
[0219] In some embodiments, the access network device 102 may obtain the first data and / or second data of the target terminal based on the received fifth information.
[0220] Furthermore, the access network device 102 can perform the operations required to achieve the corresponding purpose (such as model training, etc.) based on the collected data.
[0221] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.
[0222] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.
[0223] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0224] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".
[0225] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.
[0226] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".
[0227] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.
[0228] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.
[0229] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”
[0230] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.
[0231] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.
[0232] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.
[0233] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0234] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0235] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0236] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.
[0237] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.
[0238] The data collection method involved in the embodiments of this application may include at least one of steps S2101 to S2108. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, step S2101+S2102 can be implemented as an independent embodiment, step S2102+S2103 can be implemented as an independent embodiment, step S2101+S2102+S2104 can be implemented as an independent embodiment, step S2102+S2103+S2104 can be implemented as an independent embodiment, and so on, but not limited thereto.
[0239] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2A.
[0240] Figure 2B is an interactive schematic diagram of a data collection method according to an embodiment of this application. As shown in Figure 2B, the embodiment of this application relates to a data collection method, which includes:
[0241] Step S2201: Access network device 102 sends the second information.
[0242] In some embodiments, the second network element 1032 receives the aforementioned second information sent by the access network device 102.
[0243] In some embodiments, step S2201 can refer to the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, which will not be repeated here.
[0244] In step S2202, the second network element 1032 sends the first information.
[0245] In some embodiments, after receiving the second information, the second network element 1032 may send first information to the first network element 1031. The first information is used to request the first network element 1031 to collect the first data and / or the second data of the terminal.
[0246] In some embodiments, the first network element 1031 receives the first information sent by the second network element 1032.
[0247] In some embodiments, the first information is determined by the second network element 1032 based on the second information sent by the access network device 102.
[0248] In some embodiments, the first information and the second information may be the same, and the second network element 1032 may directly forward the second information as the first information to the first network element 1031.
[0249] In some embodiments, the above steps S2201 and S2202 can be replaced by a step S2201', where step S2201' is: the access network device 102 sends the above second information to the first network element 1031.
[0250] In some embodiments, the first network element 1031 may configure the access network device 102 to perform related operations to obtain the second data based on the first information described above.
[0251] In some embodiments, the first information described above includes at least one of the following:
[0252] Type information, wherein the type information is used to indicate the type of data collection requested in the first information request;
[0253] Identification of access network device 102;
[0254] The aforementioned users agree to the inspection results.
[0255] Optionally, the above-mentioned data collection types include at least one of the following:
[0256] Access network device 102 collects the aforementioned second data, wherein the aforementioned second data is used for a specified purpose;
[0257] Access network device 102 collects the aforementioned second data, wherein the aforementioned second data is not used for model training;
[0258] Access network device 102 collects the aforementioned second data, and the aforementioned second data is used by first network element 1031 to determine the true measurement value of the terminal.
[0259] As an example, if the type of data collection described above is: the access network device 102 collects the second data, which can be used to request relevant measurements for the access network device 102 so that the access network device 102 can obtain and use the second data based on its own needs.
[0260] As an example, if the type of data collection described above is: access network device 102 collects the second data, wherein the second data is not used for model training, but can be used to request the configuration of relevant measurements for access network device 102 to obtain the second data, but cannot be used for model training.
[0261] As an example, if the type of data collection is: access network device 102 collects the second data, and the second data is used by the first network element 1031 to determine the measurement truth value of the terminal, it can be used to request the access network device 102 to configure relevant measurements to obtain the second data, and return the second data to the first network element 1031 to determine the corresponding measurement truth value.
[0262] In some embodiments, the purpose for which the access network device 102 collects the first data and / or the second data can be indicated by the data collection type or by a separate parameter (such as the purpose information mentioned in the foregoing embodiments).
[0263] In some embodiments, the first information may also include the results of relevant user consent checks (e.g., whether the relevant terminal agrees to the access network device 102 using the terminal's data for model training, etc.).
[0264] In some embodiments, the name of the first information is not limited, and may be, for example, "measurement request", "measurement request message", "data collection request", "data collection request message", "business data collection request", "service operation request", etc.
[0265] In step S2203, the first network element 1031 determines at least one target terminal.
[0266] In some embodiments, the first network element 1031 determines at least one target terminal based on the received first information.
[0267] In some embodiments, the first network element 1031 determines at least one target terminal from at least one candidate terminal based on the first information described above.
[0268] In some embodiments, the first network element 1031 performs a user consent check for each candidate terminal.
[0269] That is, the first network element 1031 can perform a user consent check on the terminal that is requested to collect data to determine whether the UE agrees to the collection of UE-related data or its use for the corresponding purpose.
[0270] In some embodiments, a user consent check may include: a user consent check, a user privacy check, a user authorization check, etc. A user consent check can also be a user privacy check. A user consent check can be included within a user consent privacy check, and vice versa; that is, a user privacy check can be included within a user consent check.
[0271] In some embodiments, the first network element 1031 may determine the purpose information for the access network device 102 to collect the first data and / or the second data based on the first information described above. Further, the first network element 1031 may perform a user consent check on the terminal 101 based on the purpose information to obtain the user consent check result corresponding to the purpose information.
[0272] It is understood that the aforementioned purpose information can be used to instruct the access network device 102 on the purpose of requesting the collection of the first and / or second data. For example, the purpose for the access network device 102 to request the collection of data may be, for example, for model training on the access network device side, for determining relevant information of the terminal, etc., but is not limited to these.
[0273] In some embodiments, the first information may include the aforementioned purpose information.
[0274] In some embodiments, the first network element 1031 stores user consent check results for some candidate terminals (for example, the first network element 1031 may have previously performed user consent checks on the candidate terminal for other reasons, etc.). The first network element 1031 can directly obtain the user consent check results of the terminal 101 corresponding to the above-mentioned purpose information.
[0275] In some embodiments, if the first network element 1031 does not store the user consent check result for the terminal 101, the first network element 1031 can obtain the user consent check result of the terminal 101 corresponding to the aforementioned purpose information from the third network element 1033 based on the aforementioned purpose information. The first network element 1031 can perform the user consent check and obtain the user consent check result corresponding to the purpose information by retrieving the user consent-related information of the terminal 101 stored in the third network element 1033 based on the purpose information.
[0276] Optionally, the first network element 1031 can store the obtained results.
[0277] Optionally, the first network element 1031 may also store all the information related to user consent of the terminal 101 (for example, the first network element 1031 may obtain and store user consent-related information for other purposes from the third network element 1033).
[0278] In some embodiments, the first network element 1031 may also subscribe to the third network element 1033 for notifications of changes to the user consent check result for the terminal 101. When the user consent check result of a terminal changes, the third network element 1033 may send a notification of the change to the first network element 1031.
[0279] Further, optionally, after receiving the above-mentioned change notification, the first network element 1031 can obtain the changed user consent check result of the terminal 101 from the third network element 1033.
[0280] Further, optionally, the second network element 1032 may send information to the access network device 102 to indicate to the access network device 102 that the user of the terminal agrees to the change of the inspection result.
[0281] Furthermore, the access network device 102 can also perform corresponding operations based on the information indicating the change, such as triggering the execution of the above-mentioned step S2201.
[0282] In some embodiments, the user consent check result of terminal 101 may also be a default value. The first network element 1031 may determine, based on an agreement, that the user consent check result corresponding to the aforementioned purpose information of terminal 101 is the default value. Optionally, the default value may be consent or disagreement.
[0283] For example, if terminal 101 is a PRU, the user's consent check result can be considered as default consent.
[0284] In some embodiments, if the data of the first information request has already been stored locally as context information of the terminal at the first network element 1031 and is available, step S2208 can be executed directly.
[0285] In step S2204, the first network element 1031 sends the third information.
[0286] In some embodiments, the first network element 1031 can send the aforementioned third information to the access network device 102 through the second network element 1032.
[0287] In some embodiments, the third information described above is used to configure the access network device 102 to perform related operations to obtain the second data described above.
[0288] In some embodiments, the third information includes indication information, which is used to indicate that the first network element 1031 is configured with the data collection type of the access network device 102.
[0289] As an example, if the type of data collection indicated by the instruction information is: access network device 102 collects the second data, after receiving the third information, access network device 102 can perform related operations to obtain the second data, and does not need to send the second data to the first network element 1031.
[0290] As an example, if the type of data collection indicated by the instruction information is: access network device 102 collects the second data, wherein the second data is not used for model training, after receiving the third information, access network device 102 can perform relevant operations to obtain the second data, but cannot use it for model training, or cannot collect the second data for model training. However, access network device 102 can send the second data to the first network element 1031 to obtain relevant service information of the terminal (such as location information, etc.).
[0291] As an example, if the type of data collection described above is: access network device 102 collects the second data, and the second data is used by the first network element 1031 to determine the true value of the terminal's measurement, after receiving the third information, access network device 102 can perform relevant operations to obtain the second data. The second data can be used for model training. At the same time, access network device 102 can also collect the second data and report it to the first network element 1031 to obtain relevant service information of the terminal (such as location information, etc.).
[0292] In some embodiments, the name of the aforementioned third information is not limited, and may be, for example, "measurement response", "measurement response message", "data collection response", "data collection response message", "business data collection response", "data collection report", "business data collection report", "data collection instruction", "business data collection instruction", etc.
[0293] In step S2205, the first network element 1031 and / or access network device 102 collect the second data.
[0294] In step S2206, the first network element 1031 determines the first data.
[0295] In some embodiments, steps S2205-S2206 can refer to the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, which will not be repeated here.
[0296] In step S2207, the first network element 1031 sends the fourth message.
[0297] In some embodiments, the first network element 1031 may send the aforementioned fourth information to the access network device 102 based on the acquired data.
[0298] In some embodiments, the access network device 102 receives the aforementioned fourth information.
[0299] In some embodiments, the first network element 1031 sends the aforementioned fourth information to the access network device 102 through the second network element 1032.
[0300] In some embodiments, the first network element 1031 may integrate the first data and / or second data corresponding to each target terminal based on the acquired relevant data.
[0301] Optionally, the first network element 1031 can integrate relevant information for different target terminals into different messages.
[0302] Optionally, the first network element 1031 can also integrate relevant information into the same message.
[0303] Optionally, the first network element 1031 can integrate the acquired data based on its own implementation.
[0304] In some embodiments, the fourth information may include at least one of the following: the first data; the second data; first correlation information (or association information); and a failure reason indication.
[0305] The aforementioned first association information is used to determine the first and second data associated with each target terminal.
[0306] In other words, the access network device 102 can associate the first data and the second data for each target terminal based on the aforementioned first association information. That is, the associated first data and second data can be used as data in a single dataset for model training.
[0307] Optionally, if the target terminal is served by the access network device 102, the aforementioned first association information may include at least one of the following: the measurement ID corresponding to the first network element 1031, the Radio Access Network (RAN) measurement ID, the air interface positioning protocol transaction ID, the identifier of the target terminal, the timestamp, etc.
[0308] Optionally, if the target terminal is not served by the access network device 102 (e.g., served by a neighboring gNB, rather than a gNB participating in data collection), the aforementioned first association information may include at least one of the following: measurement ID corresponding to the first network element 1031, RAN measurement ID, air interface positioning protocol transaction ID, timestamp, etc.
[0309] In some embodiments, if the above process fails for some terminals, the fifth message sent to these unsuccessful terminals may include the above failure reason indication, which is used to indicate the reason why the above process failed.
[0310] Optionally, messages indicating process failure and messages indicating process success can be contained in separate messages or in a single merged message.
[0311] In some embodiments, the name of the fourth information is not limited, and may be, for example, "data collection response", "data collection response message", "business data collection response", "data collection report", "business data collection report", "data report", "model training data collection", etc.
[0312] In some embodiments, the access network device 102 may obtain the first data and / or second data of the target terminal based on the received fourth information.
[0313] Furthermore, the access network device 102 can perform the operations required to achieve the corresponding purpose (such as model training, etc.) based on the collected data.
[0314] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.
[0315] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.
[0316] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0317] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".
[0318] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.
[0319] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".
[0320] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.
[0321] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.
[0322] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”
[0323] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.
[0324] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.
[0325] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.
[0326] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0327] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0328] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0329] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.
[0330] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.
[0331] The data collection method involved in the embodiments of this application may include at least one of steps S2201 to S2207. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, step S2203 can be implemented as an independent embodiment, step S2204 can be implemented as an independent embodiment, step S2201+S2202 can be implemented as an independent embodiment, step S2202+S2203 can be implemented as an independent embodiment, step S2201+S2202+S2204 can be implemented as an independent embodiment, step S2202+S2203+S2204 can be implemented as an independent embodiment, etc., but not limited thereto.
[0332] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2B.
[0333] The following is an exemplary description of the methods described in the above embodiments.
[0334] In some embodiments, to support location information collection for UEs served by NG-RAN and / or for UEs not served by NG-RAN (e.g., UEs served by neighboring NG-RANs), location information collection using the gNB-side model is triggered by each RAN node. The RAN node may or may not include a list of candidate UEs participating in the location information collection. The UEs participating in the location information collection are determined by the AMF. As shown in Figure 3A, a flow example for location information collection of a UE (where the UE is served by the NG-RAN, or the NG-RAN is a neighboring NG-RAN of the NG-RAN served by the UE, and the UE can be determined by the AMF or directly use the list of UEs participating in the location information collection that the RAN node may include) can be provided.
[0335] In some embodiments, the data collection method may include at least one of the following steps:
[0336] 1. The gNB expects to receive location information, which consists of tags (e.g., UE location information, Part B) and / or measurement data (Part A) to form a dataset for training. Depending on the gNB's implementation, the gNB decides when and whether to trigger location information collection.
[0337] 2. A POSITIONING INFORMATION REQUEST message can be a Next Generation Application Protocol (NGAP) non-UE associated message, which may contain, for example, the NGAP UE ID of the UE for which it is seeking location information, a list of NGAP UE IDs corresponding to the list of candidate UEs participating in the location information collection, and various other conditional parameters or collection standard parameters for data collection.
[0338] Optionally, the RAN node may not include the candidate UE list that participates in location information collection.
[0339] Optionally, the information indicating what data type to collect can also be included in the location information request. For example, it may include an indication to request first data, and may specifically include the data type of the first data, such as a data type related to the UE's location. This could be a measurement type representing time information, and LOS (Line of Sight) and NLOS (Non-Line of Sight) indicators. The first data can be the truth value of location measurement information, tag information, UE location-related information, or B-part data.
[0340] Optionally, the location information request may also include an indication to request second data. The second data may be measurement information, location measurement information, gNB self-measurement data, or A-part data.
[0341] The first data and the second data are related; the first data is the true value of the second data. For location services, the first data can be the measurement truth value obtained based on the UE's location truth value, and may include, for example, the corresponding time information and LOS / NLOS indicators.
[0342] Optionally, the RAN node may include conditions required by the collected positioning information, such as valid time and valid area. For example, when the gNB requests the first data from the LMF, but the gNB itself determines the measurement data, i.e., the second data, it should indicate the valid time for synchronizing parts A and B, i.e., the first and second data.
[0343] 3. The AMF receives a request message from the RAN node. Based on the information received in step 2, the AMF selects UEs to participate in location information collection. The AMF needs to perform UE privacy checks. For example, it performs a user consent check and / or a Location Service (LCS) privacy file check for each selected UE. The user consent check can also be a user privacy check. The user consent check can be included in the user consent privacy check, and vice versa; that is, the user privacy check can be included in the user consent check. If step 2 includes a list of candidate UEs to participate in location information collection, the AMF can select UEs from the corresponding list or use this information as a reference only, or select UEs outside the list to participate in information collection. If step 2 does not include a list of candidate UEs to participate in location information collection, the AMF selects a list of UEs to participate in data collection based on the implementation or the condition information in step 2.
[0344] Understandably, if the requested information is already available at the AMF as part of the UE location context for all selected UEs, then the AMF can respond directly with the message in step 10. Otherwise, in steps 4 through 9, the AMF will select an LMF to request location for each UE for location information collection purposes.
[0345] If the RAN node can directly use the list of UEs that participate in the location information collection, step 3 can be ignored.
[0346] 4. The AMF triggers a location information request to the LMF (which may consist of a conventional Nlmf_Location_DetermineLocation service operation) to request that, based on the required conditions for location information collection received in step 2, the UE be provided with first and / or second data to form a training dataset. Optionally, the gNB identifier and / or TRP identifier may be included in the request, where the TRP (Transmission and Reception Point) is an important reference point for location measurements, used to describe the physical transmission and reception functions of the base station (such as the gNB), and can be an antenna array of a base station or multiple antenna elements within a base station.
[0347] Optionally, the AMF may request the LMF to collect at least one of the following measurement data:
[0348] a) Perform measurement data collection (Part A), i.e., the second data collection, according to the specified method. The specified method can be differentiated by whether the data is stored in the gNB and / or reported to the LMF. For example, the relevant gNB can be configured to collect measurement data according to the normal positioning process. The measurement data is collected in the gNB and reported to the LMF; whether the gNB stores the data depends on the implementation. Alternatively, the gNB can be configured to only collect measurement data, collecting and storing it in the gNB without reporting it to the LMF. Alternatively, the gNB can be configured to collect data in the gNB and store it, then report it to the LMF; or the gNB can be configured to collect data in the gNB but not store it in the gNB, only reporting it to the LMF.
[0349] b) Retrieve the truth of the measurement information, i.e., the first data, such as the tag (e.g., UE location-related information, Part B).
[0350] Optionally, if the first data and the second data are not acquired in the same measurement trigger—for example, if the true UE location value for acquiring the first data is not obtained through the second data in the same measurement process, but through other means such as another positioning process, configuration information, or information stored locally by the LMF—then the LMF can configure only the corresponding gNB to perform measurement data collection and store the data in the gNB. The gNB does not need to report the measurement data to the LMF, thus completing the gNB's collection of the second data. For example, the location information of the Positioning Reference Unit (PRU) is known, or the true UE location value can be obtained using a positioning method that does not require the measurement data requested in a).
[0351] Optionally, the purpose of location information collection can be specified by the type of measurement requested, or by a separate parameter received from the gNB indicating the purpose of location information collection. It may also include relevant user privacy check results (e.g., whether the user consents to the gNB using the UE's data for training).
[0352] 4a. If a privacy check is not performed in step 3, then LMF performs a user consent check or a privacy check for the collection of location information.
[0353] 5. LMF can perform positioning procedures. Among them,
[0354] Optionally, if the LMF determines that the configured gNB performs measurement data collection (Part A) solely for the gNB's own collection needs (e.g., for model training), then appropriate instructions should be included. In this way, the gNB does not need to report the measurement data to the LMF.
[0355] Optionally, if the LMF determines that the appropriate gNB is configured to perform measurement data collection only for UE positioning (Part A), but does not allow the gNB to collect this data for training, then a corresponding instruction should be included. In this case, the gNB must not collect measurement data for positioning data collection for model training (e.g., Part A), but the gNB can collect measurement data and report it to the LMF for UE positioning.
[0356] Optionally, if the LMF determines that the corresponding gNB is configured to perform measurement data collection (Part A) both for UE localization and for collecting data for its own training, then it should include the corresponding instructions. In this case, the gNB should collect measurement data (e.g., Part A) for localization data collection for model training, and the gNB may also collect measurement data and report it to the LMF for UE localization.
[0357] 6a. Measurement data (e.g., part A) is collected and stored in the gNB for localization data collection (e.g., part A) used in model training. Alternatively, an alternative approach is to reuse an existing process where the gNB can report measurement data (e.g., part A) to the LMF, which is then collected by the core network and sent back to the gNB. This approach requires modification to add a part where the core network collects and sends the data back to the gNB. This alternative approach requires that measurement data (e.g., part A) be included in steps 6b, 9, and 10.
[0358] 6b. The LMF collects second data for UE positioning and / or for model training positioning data collection.
[0359] 7. The LMF performs a positioning process to obtain the true location of the UE. The measurement data collected in step 5 can also be used to obtain the UE's location. Alternatively, the measurement data collected in step 5 can be used to obtain the UE's location, for example, if the location of the Positioning Reference Unit (PRU) is known, or another positioning procedure that does not require the measurement data requested in step 5 can be used to obtain the UE's location as the true location.
[0360] 8. The LMF determines the first data for model training on the gNB side, namely the labels of the UE location measurement information (e.g., the measurement information truth value derived from the UE's location truth value, i.e., part B data). These labels can be the UE's location or information derived from the UE's location. For example, the first data can be the measurement truth value obtained from the UE's location truth value, which may include the corresponding time information and LOS / NLOS indicators.
[0361] 9. The LMF returns the location information requested by the AMF to the AMF, including first data and / or second data. Optionally, the association information between the first and second data is also included.
[0362] Optionally, if the association information (also known as correlation information) for the second data of each UE enables the gNB to associate the first data and the second data, for the UE served by the gNB, the association information can be at least one of the following: LMF measurement identifier, Radio Access Network (RAN) measurement identifier, Air Interface Positioning Protocol (AIP) transaction identifier, UE identifier, and timestamp; while for the UE not served by the gNB (the UE served by a neighboring gNB but not a related gNB), the association information can be at least one of the following: LMF measurement identifier, RAN measurement identifier, AIP transaction identifier, and timestamp.
[0363] 10. The AMF will integrate the data collected from all UEs. In the AMF, the location information of all UEs may be integrated into different messages.
[0364] Optionally, the AMF returns the requested location information to the NG-RAN node, for example, via a Positioning Information Response message. If the process fails for some UEs, the AMF may return a failure message with an appropriate reason value instead. Information about failed and successful UEs may be included in separate messages or in a combined message.
[0365] Optionally, if the association information from Part A is included, the AMF can modify the received association information from the LMF and then send the modified association information to the gNB. For example, if the LMF only sends a timestamp, the AMF can add a UE identifier to the relevant information. In some cases, the AMF may also directly use the association information from the LMF.
[0366] 11. gNB uses the first and second data (part A and part B) of UE location information for AI / ML model management, such as model training.
[0367] It should be noted that the first data and the second data are related; the first data is the truth value of the second data. For location services, the first data can be the measurement truth value obtained based on the UE's location truth value, which may include, for example, the corresponding time information and LOS / NLOS indicators. For other services, the first data can be based on the measurement truth value of the corresponding service, such as the measurement truth value of a sensing service, and the second data is the sensing service measurement data. The service function network participating in the service can be the network function that processes the sensing service. The method of this embodiment is also applicable to the collection of measurement data for other services.
[0368] In some embodiments, to support location information collection for UEs served by NG-RAN and / or for UEs not served by NG-RAN (e.g., UEs served by neighboring NG-RANs), location data collection for the gNB end model is triggered node-by-node by the Radio Access Network (RAN) nodes. RAN nodes may or may not contain a list of candidate UEs participating in location information collection. The UEs participating in location information collection are determined by the LMF. The following figure illustrates an example of a process for location information collection for UEs served by NG-RAN, determined by the LMF. The difference in the above embodiments is that the LMF performs UE selection and merges the collected information, which has less impact on the AMF supporting location information collection. As shown in Figure 3B, Figure 3B illustrates an example of a process for collecting location information for a UE (where the UE is served by the NG-RAN or the NG-RAN is a neighboring NG-RAN of the NG-RAN served by the UE, and the UE can be determined by the LMF or directly use a list of UEs participating in the location information collection that the RAN node may include).
[0369] In some embodiments, the data collection method may include at least one of the following steps:
[0370] 1. The gNB expects to receive location information, which consists of tags (e.g., UE location information, Part B) and / or measurement data (Part A) to form a dataset for training. Depending on the gNB's implementation, the gNB decides when and whether to trigger location information collection.
[0371] 2. A Positioning Information Request (POSITIONING INFORMATION REQUEST) message can be an NRPPa or NGAP message not associated with a UE. Optional parameters may include, for example, the UE ID of the UE requesting its location information, a list of candidate UEs participating in the location information collection, and various conditional parameters or collection standard parameters for data collection. The AMF does not need to understand the message content and can simply forward it.
[0372] Optionally, the information indicating what data type to collect can also be included in the location information request. For example, it may include an indication to request first data, and may specifically include the data type of the first data, such as a data type related to the UE's location. This could be a measurement type representing time information, and LOS (Line of Sight) and NLOS (Non-Line of Sight) indicators. The first data can be the truth value of location measurement information, tag information, UE location-related information, or B-part data.
[0373] Optionally, the location information request may also include an indication to request second data. The second data may be measurement information, location measurement information, gNB self-measurement data, or A-part data.
[0374] The first data and the second data are related; the first data is the true value of the second data. For location services, the first data can be the measurement truth value obtained based on the UE's location truth value, and may include, for example, the corresponding time information and LOS / NLOS indicators.
[0375] Optionally, the RAN node may include conditions required by the collected positioning information, such as valid time and valid area. For example, when the gNB requests the first data from the LMF, but the gNB itself determines the measurement data, i.e., the second data, it should indicate the valid time for synchronizing parts A and B, i.e., the first and second data.
[0376] 3. The AMF forwards the information received in step 2 to the selected LMF. Optionally, this may include the gNB identifier or TRP identifier received in step 2.
[0377] 4. The LMF selects UEs to participate in location information collection based on the information received in step 3. The LMF needs to perform UE privacy checks. For example, it performs user consent checks and / or Location Service (LCS) privacy file checks for each selected UE. The user consent check can also be a user privacy check. The user consent check can be included in the user consent privacy check, or vice versa; that is, the user privacy check can be included in the user consent check. If step 2 includes a list of candidate UEs to participate in location information collection, the LMF can select UEs from the corresponding list or use this information as a reference only, or select UEs outside the list to participate in information collection. If step 2 does not include a list of candidate UEs to participate in location information collection, the LMF selects a list of UEs to participate in data collection based on the implementation or the condition information in step 2.
[0378] If the RAN node can be used directly to include the list of UEs participating in the location information collection, step 4 can be ignored.
[0379] Understandably, if the requested information is already available at the LMF as part of the UE location context for all selected UEs, the LMF will respond directly with the message in step 9. Otherwise, the LMF will collect location information for each UE in steps 5 through 8.
[0380] 5. The LMF determines to collect first and / or second data for the UE to form a training dataset. Optionally, the gNB identifier and / or TRP identifier may be included in the request, where the TRP (Transmission and Reception Point) is an important reference point for positioning measurements, used to describe the physical transmission and reception functions of the base station side (such as the gNB), and it can be an antenna array of a base station or multiple antenna elements in a base station.
[0381] Specifically, LMF performs at least one of the following measurement data collection:
[0382] a) Perform measurement data collection (Part A), i.e., the second data collection, according to the specified method. The specified method can be differentiated by whether the data is stored in the gNB and / or reported to the LMF. For example, the relevant gNB can be configured to collect measurement data according to the normal positioning process. The measurement data is collected in the gNB and reported to the LMF; whether the gNB stores the data depends on the implementation. Alternatively, the gNB can be configured to only collect measurement data, collecting and storing it in the gNB without reporting it to the LMF. Alternatively, the gNB can be configured to collect data in the gNB and store it, then report it to the LMF; or the gNB can be configured to collect data in the gNB but not store it in the gNB, only reporting it to the LMF.
[0383] b) Retrieve the truth of the measurement information, i.e., the first data, such as the tag (e.g., UE location-related information, Part B).
[0384] Optionally, if the first data and the second data are not acquired in the same measurement trigger—for example, if the true UE location value for acquiring the first data is not obtained through the second data in the same measurement process, but through other means such as another positioning process, configuration information, or information stored locally by the LMF—then the LMF can configure only the corresponding gNB to perform measurement data collection and store the data in the gNB. The gNB does not need to report the measurement data to the LMF, thus completing the gNB's collection of the second data. For example, the location information of the Positioning Reference Unit (PRU) is known, or the true UE location value can be obtained using a positioning method that does not require the measurement data requested in a).
[0385] Optionally, the purpose of location information collection can be specified by the type of measurement requested, or by a separate parameter received from the gNB indicating the purpose of location information collection. It may also include relevant user privacy check results (e.g., whether the user consents to the gNB using the UE's data for training).
[0386] LMF can perform a location procedure. Among these,
[0387] Optionally, if the LMF determines that the configured gNB performs measurement data collection (Part A) solely for the gNB's own collection needs (e.g., for model training), then appropriate instructions should be included. In this way, the gNB does not need to report the measurement data to the LMF.
[0388] Optionally, if the LMF determines that the appropriate gNB is configured to perform measurement data collection only for UE positioning (Part A), but does not allow the gNB to collect this data for training, then a corresponding instruction should be included. In this case, the gNB must not collect measurement data for positioning data collection for model training (e.g., Part A), but the gNB can collect measurement data and report it to the LMF for UE positioning.
[0389] Optionally, if the LMF determines that the corresponding gNB is configured to perform measurement data collection (Part A) both for UE localization and for collecting data for its own training, then it should include the corresponding instructions. In this case, the gNB should collect measurement data (e.g., Part A) for localization data collection for model training, and the gNB may also collect measurement data and report it to the LMF for UE localization.
[0390] 6a. Measurement data (e.g., part A) is collected and stored in the gNB for localization data collection (e.g., part A) used in model training. Alternatively, an alternative approach is to reuse an existing process where the gNB can report measurement data (e.g., part A) to the LMF, which is then collected by the core network and sent back to the gNB. This approach requires modification to add a part where the core network collects and sends the data back to the gNB. This alternative approach requires that measurement data (e.g., part A) be included in steps 6b, 9, and 10.
[0391] 6b. The LMF collects second data for UE positioning and / or for model training positioning data collection.
[0392] 7. The LMF performs a positioning process to obtain the true location of the UE. The measurement data collected in step 5 can also be used to obtain the UE's location. Alternatively, the measurement data collected in step 5 can be used to obtain the UE's location, for example, if the location of the Positioning Reference Unit (PRU) is known, or another positioning procedure that does not require the measurement data requested in step 5 can be used to obtain the UE's location as the true location.
[0393] 8. The LMF determines the first data for model training on the gNB side, namely the labels of the UE location measurement information (e.g., the measurement information truth value derived from the UE's location truth value, i.e., part B data). These labels can be the UE's location or information derived from the UE's location. For example, the first data can be the measurement truth value obtained from the UE's location truth value, which may include the corresponding time information and LOS / NLOS indicators.
[0394] 9. The LMF will integrate the data collected from all UEs. In the LMF, the location information of all UEs may be integrated into different messages.
[0395] The LMF can return the requested location information to the AMF. If the procedure fails for some UEs, the LMF can return a failure message with an appropriate reason value instead. Information about the failed and successful UEs may be contained in separate messages or in a combined message.
[0396] Optionally, if the association information (also known as correlation information) of the second data for each UE enables the gNB to associate the second data with the first data information, then for the UE being served (the UE served by the gNB), the association information can be at least one of the following: LMF measurement identifier, Radio Access Network (RAN) measurement identifier, New Radio Positioning Protocol (NRIP) transaction identifier, UE identifier, and timestamp; while for the UE not being served (the UE served by a neighboring gNB, but not a related gNB), the association information can be at least one of the following: LMF measurement identifier, RAN measurement identifier, NRIP transaction identifier, and timestamp.
[0397] 10. The AMF forwards the location information to the RAN node accordingly.
[0398] 11. gNB uses the first and second data (part A and part B) of UE location information for AI / ML model management, such as model training.
[0399] It should be noted that the first data and the second data are related; the first data is the truth value of the second data. For location services, the first data can be the measurement truth value obtained based on the UE's location truth value, which may include, for example, the corresponding time information and LOS / NLOS indicators. For other services, the first data can be based on the measurement truth value of the corresponding service, such as the measurement truth value of a sensing service, and the second data is the sensing service measurement data. The service function network participating in the service can be the network function that processes the sensing service. The method of this embodiment is also applicable to the collection of measurement data for other services.
[0400] In some embodiments, unless contradictory, the optional implementations in this embodiment can be implemented as independent embodiments, and the optional implementations in this embodiment can also be combined arbitrarily. The technical features of different feasible implementations in this embodiment can be combined to form new optional implementations based on their inherent logical relationships.
[0401] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0402] This application also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed, which includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.
[0403] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0404] In this application embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0405] Figure 4A is a schematic diagram of the structure of a first network element according to an embodiment of this application. The first network element 4100 is used to perform any of the above methods. In some embodiments, as shown in Figure 4A, the first network element 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module 4101 is used to receive first information sent by a second network element, the first information being used to request the collection of first data and / or second data of at least one target terminal; wherein, the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal; the first data and the second data are associated data of a specified service or a specified data type of the target terminal. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the first network element 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the first network element 101 in any of the above methods, which will not be elaborated here.
[0406] Figure 4B is a schematic diagram of the structure of the second network element proposed in an embodiment of this application. The second network element 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the second network element 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to send first information to the first network element, the first information being used to request the collection of first data and / or second data of at least one target terminal; wherein, the at least one target terminal is determined by the first network element or the second network element from at least one candidate terminal; the first data and the second data are associated data of a specified service or a specified data type of the target terminal. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the access network device 1021 in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform at least one of the other steps performed by the access network device 102 in any of the above methods, which will not be described in detail here.
[0407] Figure 4C is a schematic diagram of the structure of an access network device according to an embodiment of this application. The access network device 4300 is used to perform any of the above methods. In some embodiments, as shown in Figure 4C, the access network device 4300 may include at least one of a transceiver module 4301, a processing module 4302, etc. In some embodiments, the transceiver module 4301 is used to send second information to a second network element, the second information being used to instruct the access network device to request the collection of the first data and / or the second data. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the access network device 1021 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the access network device 102 in any of the above methods, which will not be elaborated here.
[0408] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0409] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0410] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.
[0411] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this application. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0412] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.
[0413] In some embodiments, the communication device 5100 further includes one or more transceivers 5103. When the communication device 5100 includes one or more transceivers 5103, the transceiver 5103 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0414] In some embodiments, the communication device 5100 further includes one or more memories 5102 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5102 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5102 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.
[0415] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this application is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0416] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this application. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.
[0417] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.
[0418] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.
[0419] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.
[0420] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0421] This application also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0422] This application also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0423] This application also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
Claims
1. A data collection method, characterized in that, The method is executed by an access network device, and the method includes: Receive third information, wherein the third information is sent by the first network element through the second network element, and the third information is used to configure the second data of the target terminal to be collected, and the data collection type.
2. The method as described in claim 1, characterized in that, The data collection type is used to indicate at least one of the following: The access network device stores the second data; The second data is used for model training; The second set of data is not used for model training; The access network device does not store the second data; The access network device sends the second data to the first network element; The access network device does not need to send the second data to the first network element.
3. The method as described in claim 1 or 2, characterized in that, The method further includes: Send a second message to the second network element, wherein the second message is used to instruct the collection of first data and / or second data, and the first data and the second data are associated data of a specified service or a specified data type; The second information includes condition information and / or a candidate terminal list. The condition information is used to indicate the conditions that the collected data needs to meet as the first data and / or the second data. The candidate terminal list is used to indicate the identifiers of the candidate terminals participating in the information collection. The condition information includes at least one of the following: time information and region information.
4. The method as described in claim 3, characterized in that, The target terminal is any one of the following: The terminals in the candidate terminal list included in the second information; The first network element determines the terminal after performing terminal selection and / or user privacy checks; The second network element determines the terminal by performing terminal selection and / or user privacy checks.
5. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive first data from at least one of the target terminals, wherein the first data from the target terminal is sent by the first network element through fourth information, or by the second network element through fifth information.
6. The method as described in claim 5, characterized in that, The fourth or fifth information may also include at least one of the following: At least one second data of the target terminal; The association information corresponding to each target terminal is used to associate the first data and the second data of each target terminal; Failure reason indication, which is used to indicate the reason why the data collection process for any target terminal was unsuccessful.
7. The method as described in claim 6, characterized in that, The target terminal is a terminal provided by the access network equipment, and the associated information corresponding to the target terminal includes at least one of the following: a measurement identifier corresponding to the first network element, a radio access network (RAN) measurement identifier, an air interface positioning protocol (AIP) transaction identifier, the identifier of the target terminal, and a timestamp; or, The target terminal is not a terminal provided by the access network equipment, and the associated information corresponding to the target terminal includes at least one of the following: the measurement identifier corresponding to the first network element, the RAN measurement identifier, the air interface positioning protocol transaction identifier, and the timestamp.
8. A data collection method, characterized in that, The method is executed by a first network element, and the method includes at least one of the following: The third information is sent to the access network device through the second network element, wherein the third information is used to configure the second data of the target terminal to be collected, and the data collection type.
9. The method as described in claim 8, characterized in that, The data collection type is used to indicate at least one of the following: The access network device stores the second data; The second data is used for model training; The second set of data is not used for model training; The access network device does not store the second data; The access network device sends the second data to the first network element; The access network device does not need to send the second data to the first network element.
10. The method as described in claim 8 or 9, characterized in that, The method further includes: Receive first information sent by the second network element, wherein the first information is used to request the collection of first data and / or second data of the terminal; The first information includes condition information, which is used to indicate the conditions that the collected data needs to meet as the first data and / or the second data; The condition information includes at least one of the following: time information and region information.
11. The method as described in claim 10, characterized in that, The first information also includes at least one of the following: A candidate terminal list, wherein the candidate terminal list is used to indicate the identifiers of candidate terminals participating in information collection; The identifier of the access network device; The consent check result of the target terminal.
12. The method as described in claim 11, characterized in that, The method further includes any one of the following: Perform a privacy check on the terminals in the candidate terminal list to determine at least one target terminal; The first information does not contain a list of candidate terminals. Terminal selection and / or user privacy checks are performed to determine at least one of the target terminals.
13. The method as described in claim 11 or 12, characterized in that, The target terminal is any one of the following: The terminals in the candidate terminal list; The first network element determines the terminal after performing terminal selection and / or user privacy checks; The second network element determines the terminal by performing terminal selection and / or user privacy checks.
14. The method according to any one of claims 8-13, characterized in that, The method further includes: Send fourth information to the second network element or the access network device, wherein the fourth information contains at least one first data of the target terminal.
15. The method as described in claim 14, characterized in that, The first data is determined based on at least one of the following: The second data of the target terminal; The location information of the target terminal is determined based on any of the following: measurements by the access network device, Global Navigation Satellite System (GNSS), and positioning procedures; Location and environmental information of the physical transmission and reception functions on the access network side; The target terminal's historical location measurement data.
16. The method as described in claim 15, characterized in that, The fourth information also includes at least one of the following: At least one second data of the target terminal; The first association information corresponding to each target terminal is used to associate the first data and the second data of each target terminal; A failure reason indication for any target terminal, wherein the failure reason indication is used to indicate the reason why the data collection process for the target terminal was unsuccessful.
17. The method as described in claim 16, characterized in that, The target terminal is a terminal provided by the access network device, and the first associated information corresponding to the target terminal includes at least one of the following: a measurement identifier corresponding to the first network element, a radio access network measurement identifier, an air interface positioning protocol transaction identifier, the identifier of the target terminal, and a timestamp; or, The target terminal is not a terminal provided by the access network device, and the first associated information corresponding to the target terminal includes at least one of the following: the measurement identifier corresponding to the first network element, the RAN measurement identifier, the air interface positioning protocol transaction identifier, and the timestamp.
18. A data collection method, characterized in that, The method is executed by a second network element, and the method includes: Send third information to the access network device, wherein the third information is received from the first network element and is used to configure the collection of second data of the target terminal and the data collection type.
19. The method as described in claim 18, characterized in that, The data collection type is used to indicate at least one of the following: The access network device stores the second data; The second data is used for model training; The second set of data is not used for model training; The access network device does not store the second data; The access network device sends the second data to the first network element; The access network device does not need to send the second data to the first network element.
20. The method as described in claim 18 or 19, characterized in that, The method further includes: The system receives second information sent by the access network device, wherein the second information is used to instruct the collection of first data and / or second data, and the first data and the second data are associated data of a target specified service or a specified data type; Send a first message to the first network element, wherein the first message is used to request the collection of the terminal's first data and / or second data; The first information and the second information include condition information, which is used to indicate the conditions that the collected data needs to meet as the first data and / or the second data; The condition information includes at least one of the following: time information and region information.
21. The method as described in claim 20, characterized in that, The first information or the second information also includes at least one of the following: A candidate terminal list, wherein the candidate terminal list is used to indicate the identifiers of candidate terminals participating in information collection; The identifier of the access network device.
22. The method as described in claim 21, characterized in that, The candidate terminal list includes the identifier of at least one candidate terminal; The identifier of the candidate terminal included in the first information may be different from or the same as the identifier of the candidate terminal included in the second information.
23. The method as described in claim 22 or 23, characterized in that, The method further includes any one of the following: Perform a privacy check on the terminals in the candidate terminal list to determine at least one target terminal; The second information does not contain a list of candidate terminals. Terminal selection and / or user privacy checks are performed to determine at least one of the target terminals.
24. The method as described in claim 23, characterized in that, The target terminal is any one of the following: The terminals in the candidate terminal list; The first network element determines the terminal after performing terminal selection and / or user privacy checks; The second network element determines the terminal by performing terminal selection and / or user privacy checks.
25. The method as described in any one of claims 18-24, characterized in that, The method further includes: Receive fourth information sent by the first network element, wherein the fourth information contains at least one first data of the target terminal; Send fifth information to the access network device, wherein the fifth information contains the first data of the at least one target terminal.
26. The method as described in claim 25, characterized in that, The fourth or fifth information may also include at least one of the following: At least one second data of the target terminal; The association information corresponding to each target terminal is used to associate the first data and the second data of each target terminal; A failure reason indication for any target terminal, wherein the failure reason indication is used to indicate the reason why the data collection process for the target terminal was unsuccessful.
27. The method as described in claim 26, characterized in that, The target terminal is a terminal provided by the access network device, and the associated information corresponding to the target terminal includes at least one of the following: a measurement identifier corresponding to the first network element, a radio access network measurement identifier, an air interface positioning protocol transaction identifier, the identifier of the target terminal, and a timestamp; or, The target terminal is not a terminal provided by the access network equipment, and the associated information corresponding to the target terminal includes at least one of the following: the measurement identifier corresponding to the first network element, the RAN measurement identifier, the air interface positioning protocol transaction identifier, and the timestamp.
28. An access network device, characterized in that, include: The transceiver module is used to receive third information, wherein the third information is sent by the first network element through the second network element, and the third information is used to configure the second data of the target terminal to be collected, and the data collection type.
29. A first network element, characterized in that, include: The transceiver module is used to send third information to the access network device through the second network element, wherein the third information is used to configure the second data of the target terminal to be collected, and the data collection type.
30. A second network element, characterized in that, include: The transceiver module is used to send third information to the access network device, wherein the third information is sent by the first network element and is used to configure the second data of the target terminal to be collected, and the data collection type.
31. An access network device, characterized in that, include: One or more processors; The access network device is used to perform the data collection method according to any one of claims 1-7.
32. A first network element, characterized in that, include: One or more processors; The first network element is used to perform the data collection method according to any one of claims 8-17.
33. A second network element, characterized in that, include: One or more processors; The second network element is used to perform the data collection method according to any one of claims 18-27.
34. A communication device, characterized in that, The communication device is used to perform the data collection method according to any one of claims 1-7, 8-17, or 18-27.
35. A communication system, characterized in that, The system includes an access network device, a first network element, and a second network element, wherein the access network device is configured to implement the data collection method of any one of claims 1-7, the first network element is configured to implement the data collection method of any one of claims 8-17, and the second network element is configured to implement the data collection method of any one of claims 18-27.
36. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the data collection method as described in any one of claims 1-7, 8-17, or 18-27.
37. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the data collection method according to any one of claims 1-7, 8-17, or 18-27.
