Supplier-specific data collection

Abstract

This disclosure relates to methods, apparatus, devices, and computer-readable storage media for supplier-specific data collection. The method includes: receiving information from a management entity regarding at least one supplier-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one supplier-specific configuration; receiving at least one user device identifier from at least one user device for associating the at least one user device with the data collection; determining whether the received at least one user device identifier is among the at least one data collection device identifier; if it is determined that the received at least one user device identifier is among the at least one data collection device identifier, selecting at least one user device for data collection; and sending at least one supplier-specific configuration to the at least one user device for performing data collection according to the at least one supplier-specific configuration.

Description

Technical Field

[0001] This disclosure relates generally to the telecommunications field, and more particularly to methods, apparatus, devices, and computer-readable storage media for supplier-specific data collection. Background Technology

[0002] During research into data collection for artificial intelligence (AI) / machine learning (ML), the question of whether existing data collection frameworks should be modified was explored. Based on this research, Minimum Drive Testing (MDT) was deemed suitable for enhancement and was investigated. Summary of the Invention

[0003] In a first aspect of this disclosure, a network node is provided. The network node includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network node to at least: receive information from a management entity regarding at least one provider-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; receive from at least one user device identifier for associating the at least one user device with the data collection; determine whether the received at least one user device identifier is among the at least one data collection device identifier; if it is determined that the received at least one user device identifier is among the at least one data collection device identifier, select the at least one user device for data collection; and send at least one provider-specific configuration to the at least one user device for performing data collection according to the at least one provider-specific configuration.

[0004] In a second aspect of this disclosure, a management entity is provided. The management entity includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the management entity to at least: configure at least one provider-specific configuration for data collection from a data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration for a network node; and send information to the network node regarding the at least one provider-specific configuration for data collection and the at least one data collection device identifier associated with the at least one provider-specific configuration.

[0005] In a third aspect of this disclosure, a user equipment is provided. The user equipment includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to at least: send at least one user equipment identifier to a network node for associating the user equipment with data collection; receive from the network node one or more provider-specific configurations allocated for the user equipment for performing data collection according to the one or more provider-specific configurations; and perform data collection according to at least one provider-specific configuration.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving information from a management entity by a network node regarding at least one provider-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; receiving from at least one user device (User Device) identifier for associating the at least one User Device with the data collection; determining whether the received at least one User Device identifier is among the at least one Data Collection Device identifier; if it is determined that the received at least one User Device identifier is among the at least one Data Collection Device identifier, selecting the at least one User Device for data collection; and sending at least one provider-specific configuration to the at least one User Device for performing data collection according to the at least one provider-specific configuration.

[0007] In a fifth aspect of this disclosure, a method is provided. The method includes: configuring a network node with at least one provider-specific configuration for data collection from a data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; and sending information to the network node regarding the at least one provider-specific configuration for data collection and the at least one data collection device identifier associated with the at least one provider-specific configuration.

[0008] In a sixth aspect of this disclosure, a method is provided. The method includes: sending at least one user equipment identifier from a user equipment to a network node for associating the user equipment with data collection; receiving from the network node one or more provider-specific configurations allocated for the user equipment for performing data collection according to the one or more provider-specific configurations; and performing data collection according to at least one provider-specific configuration.

[0009] In a seventh aspect of this disclosure, a network node is provided. The network node includes: components for receiving information from a management entity regarding at least one provider-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; components for receiving at least one user device identifier from at least one user device for associating the at least one user device with the data collection; components for determining whether the received at least one user device identifier is among the at least one data collection device identifier; components for selecting at least one user device for data collection if it is determined that the received at least one user device identifier is among the at least one data collection device identifier; and components for sending at least one provider-specific configuration to the at least one user device for performing data collection according to the at least one provider-specific configuration.

[0010] In an eighth aspect of this disclosure, a management entity is provided. The management entity includes: components for configuring at least one provider-specific configuration for data collection from a data collection device for a network node and at least one data collection device identifier associated with the at least one provider-specific configuration; and components for sending information to the network node regarding the at least one provider-specific configuration for data collection and the at least one data collection device identifier associated with the at least one provider-specific configuration.

[0011] In a ninth aspect of this disclosure, a user equipment is provided. The user equipment includes: components for transmitting at least one user equipment identifier to a network node for associating the user equipment with data collection; components for receiving one or more provider-specific configurations allocated to the user equipment from the network node for performing data collection according to one or more provider-specific configurations; and components for performing data collection according to at least one provider-specific configuration.

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

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

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

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

[0016] Some examples will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which the examples of this disclosure can be performed is shown; Figure 2 A signaling diagram illustrating an example process of a supplier server subscription management entity according to some examples of this disclosure is shown; Figure 3 Signaling diagrams are shown for example processes of data collection based on supplier-specific configurations, according to some examples of this disclosure; Figure 4 A signaling diagram illustrating an example process for a network node to retrieve a UE identifier, according to some examples of this disclosure, is shown. Figure 5 A signaling diagram is shown for another example process of a network node retrieving a UE identifier, according to some examples of this disclosure; Figure 6 A diagram illustrating an example process for collecting supplier-specific data through forwarding, according to some examples of this disclosure; Figure 7 A flowchart is shown illustrating a method performed at a first device according to some examples of this disclosure; Figure 8 A flowchart is shown illustrating a method performed at a second device according to some examples of this disclosure; Figure 9 A flowchart illustrating a method performed at a third device according to some examples of this disclosure is shown; Figure 10 A simplified block diagram of a device suitable for performing examples of this disclosure is shown; and Figure 11 A block diagram of an example computer-readable medium according to some examples of this disclosure is shown.

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

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

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

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

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

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

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

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the examples. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms “comprising,” “including,” “having,” “possessing,” “including,” and / or “containing” as used herein specify the presence of the stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0025] As used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or (multiple) digital hardware circuits and software / firmware, and (ii) Any part of a device (such as a mobile phone or server) that has software (including multiple digital signal processors), software, and multiple memories working together to enable the device to perform various functions, and (c) Multiple hardware circuits and / or multiple processors, such as multiple microprocessors or a portion thereof, that require software (e.g., firmware) to operate (but such software may not exist when it is not required to operate).

[0026] This definition of circuit system applies to all uses of the term in this application, including in any claim. As an example, as used herein, the term circuit system also covers implementations of only hardware circuitry or processors (or processors in general) or portions thereof and their accompanying software and / or firmware. For instance, if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

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

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

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

[0030] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination of time-domain, frequency-domain, spatial-domain, and / or code-domain resources that allow communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources used to describe some examples of this disclosure. Note that the examples of this disclosure also apply to other resources in other domains.

[0031] Figure 1 An example communication environment 100 in which examples of this disclosure can be performed is shown. Communication environment 100 includes network nodes 110 and management entity 120 that can communicate with each other. Network node 110 may also be referred to hereinafter as, for example, a RAN node, gNB, or base station. Management entity 120 may also be referred to hereinafter as, for example, a management function or management system. Specifically, management entity 120 may be referred to as Operation, Administration and Maintenance (OAM).

[0032] Communication environment 100 includes UEs 130-1, 130-2, and 130-3, each of which can communicate with network node 110. In the following text, each of UEs 130-1, 130-2, and 130-3 may also be referred to as a terminal device, user terminal, or user equipment. UEs 130-1, 130-2, and 130-3 may also be collectively referred to as UE 130.

[0033] As an example, the link from network node 110 to UE 130 is referred to as the downlink (DL), and the link from UE 130 to network node 110 is referred to as the uplink (UL). In the DL, network node 110 is the transmitting (TX) device (or transmitter), and UE 130 is the receiving (RX) device (or receiver). In the UL, UE 130 is the TX device (or transmitter), and network node 110 is the RX device (or receiver).

[0034] Additionally, the communication environment 100 may include a provider server 140, which can communicate with the management entity 120.

[0035] It should be understood that Figure 1 The numbers of network nodes, UEs, management entities, and / or provider servers shown are given for illustrative purposes and do not imply any limitation. The communication network 100 may include any suitable number of network nodes, UEs, management entities, and / or provider servers.

[0036] Communication in communication environment 100 may be performed according to any suitable communication protocol(s), including but not limited to: cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G); wireless local network communication protocols such as IEEE 802.11; and / or any other currently known or future-developed protocols. Furthermore, communication may utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple-input multiple-output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0037] Based on the discussion of non-standardized measurement data collection, two requirements were proposed: the ability to collect data at servers that may not belong to the operator's network; and the ability to collect supplier-specific data and direct configurations to specific types of UEs.

[0038] The term "non-standardized measurement data collection" as used in this article can refer to a collection of one or more specific data sets. For the purpose of performing measurements to obtain vendor- or user-equipment-specific data, it is necessary to be able to collect such data, which may not be obtained through standardized measurements but rather using vendor-specific measurements and measurement configurations. This data can then be used to train or execute AI / ML models on the UE side or on the vendor's server.

[0039] “Non-standardized measurement data collection” can be performed by one or more UEs. “Non-standardized measurement data collection” may also be referred to below as vendor-proprietary data collection or vendor-specific data collection. In this context, the one or more UEs performing “non-standardized measurement data collection” may also be referred to as one or more data collection devices. The data collected by non-standardized measurement data collection may also be referred to as “non-standardized measurement data,” “vendor-proprietary data,” “proprietary data,” or “proprietary measurement data.”

[0040] As used in this article, “standardized measurement data collection” can refer to at least one of radio measurement data collection, sensor data collection, or device status data collection, such as battery power or temperature.

[0041] "Non-standardized measurement data collection" may be required by a data collection entity from one or more data collection devices. For example, the data collection entity may be located at a provider server and / or management entity.

[0042] As mentioned above, based on the discussion of data collection for AI / ML, MDT is qualified to be studied for enhancement. Currently, MDT features are widely used by operators who want feedback on coverage in specific areas of their network (managed MDT), or feedback on the radio conditions experienced by some (or more) specific UEs in a given coverage area of ​​a Public Land Mobile Network (PLMN) (signaling-based MDT).

[0043] There are two types of MDTs: Recorded MDTs and Immediate MDTs. Recorded MDTs are applicable to idle or inactive modes (i.e., RRC_IDLE or RRC_INACTIVE modes). For recorded MDTs, when the UE is in connected mode (i.e., RRC_CONNECTED), the UE receives the recorded MDT configuration from the network. The recorded MDT configuration can be stored in the UE. When the UE is in RRC_IDLE / RRC_INACTIVE mode for the configured recording duration (maximum 2 hours in the current specification), the configured recorded measurements associated with the MDT configuration are performed, and the measurement results are cached in the UE. When the UE reconnects, the availability of the cached measurements is signaled to the network, which can retrieve the logs and forward them to the OAM (e.g., to the Trace Collection Entity (TCE)). In RRC_CONNECTED (RRC connected) mode, the recorded MDT configuration is simply retained, but no measurements are performed; however, the network can be configured with an immediate MDT configuration. The latter may result in the UE being configured to perform RRC measurements, but the UE does not know whether the purpose of these RRC measurements is RRM (Radio Resource Management) or MDT.

[0044] For managed MDT data collection, UE selection can be made in the gNB's radio network based on input information received from the management system and user consent information stored in the gNB.

[0045] However, current management-based data collection methods do not allow for the configuration of measurements for specific UEs or UE types (e.g., UE hardware model, UE chipset model, or UE firmware version) in a vendor-specific manner.

[0046] RAN nodes cannot configure proprietary or non-proprietary measurements for specific UEs or UE types using provider-specific configurations. The network cannot configure provider-specific proprietary measurements for UEs transparently to the network.

[0047] Based on some examples of this disclosure, a UE-centric solution is provided that enables network nodes (e.g., RAN nodes) to configure measurements that can be associated with non-standardized or standardized measurement data collection for a specific UE or UE type using provider-specific configurations.

[0048] Examples of this disclosure will now be described in detail with reference to the accompanying drawings.

[0049] Now for reference Figure 2 The diagram 200 illustrates a signaling diagram of an example process for a supplier server subscription management entity according to some examples of this disclosure. Figure 2As shown, signaling diagram 200 involves supplier server 140 and management entity 120 (e.g., OAM).

[0050] When provider server 140 subscribes to an operator's network, provider server 140 may initiate a subscription (205) to management entity 120 associated with the operator's network. Management entity 120 may be provided with a data collection device identifier corresponding to non-standardized measurement data collection from provider server 140 requesting data collection. When provider server 140 subscribes to an operator's network, it may be assumed that the set of permitted data collection device identifiers for non-standardized measurement data collection is known to management entity 120. Upon subscription, provider server 140 may initiate (210) at least one provider-specific configuration to management entity 120 by including at least one data collection device identifier associated with at least one provider-specific configuration.

[0051] It should be understood that multiple provider servers can simultaneously subscribe to the management entity 120. Figure 2 The examples shown are for illustrative purposes only. Upon receiving at least one provider-specific configuration and at least one data collection device identifier, a network node can enable the device associated with the at least one data collection device identifier to perform data collection according to at least one provider-specific configuration. References will follow below. Figure 3 Describe in detail the data collection process based on supplier-specific configurations.

[0052] Now for reference Figure 3 Signaling diagram 300 illustrates an example process for data collection based on a supplier-specific configuration, according to some examples of this disclosure. Figure 3 As shown, signaling diagram 300 involves network node 110 (e.g., gNB), management entity 120 (e.g., OAM), and user equipment 130. (Reference) Figure 1 To describe signaling diagram 300.

[0053] The process may also involve a data collection entity 301, which may be considered to be co-located with management entity 120 or with provider server 140.

[0054] like Figure 3 As shown, management entity 120 may send (305) to network node 110 at least one provider-specific configuration for data collection from at least one data collection device, and at least one data collection device identifier associated with at least one provider-specific configuration.

[0055] For example, data collection from at least one data collection device, depending on at least one supplier-specific configuration, can be referred to as collection of proprietary data (e.g., supplier-specific data required for the UE-side model) from at least one data collection device. In the following, at least one data collection device may be referred to as at least one UE. At least one supplier-specific configuration may include at least one supplier-specific measurement configuration.

[0056] By configuring at least one supplier-specific configuration and associated data collection device(s) identifiers, a supplier sensor can request non-standardized measurement data collection, which can be used to enhance specific performance at the data collection devices(s). For example, proprietary data can be used to train a UE-side model that requests data from the non-standardized measurement data collection as training data.

[0057] At least one data collection device identifier associated with at least one supplier-specific configuration may refer to the identifier of one or more devices to which at least one supplier-specific configuration will be applied. That is, one or more devices configured with at least one supplier-specific configuration can collect data according to at least one supplier-specific configuration.

[0058] At least one data collection device identifier may refer to one or more identifier types.

[0059] In some embodiments, at least one data collection device identifier may be an identifier type with a permanent identifier. As an example, the permanent identifier may be an International Mobile Equipment Identity (IMEI) associated with one or more data collection devices and / or an IMEI Type Assignment Code (IMEI-TAC) associated with one or more data collection devices. An IMEI with 14 or 15 digits can be used as a distinctive device-specific identifier to ensure global uniqueness. The first eight digits of the IMEI constitute the Type Assignment Code (TAC), which can indicate the manufacturer and model of a specific device. Therefore, device models from a specific manufacturer can have the same TAC.

[0060] It should be understood that at least one data collection device identifier provided by management entity 120 may correspond to one or more UEs. For example, an IMEI-TAC provided by management entity 120 may correspond to one or more UEs whose IMEI-TAC field matches the provided IMEI-TAC. This means that the provider-specific configuration provided by management entity 120 may not require knowledge of the UE's IMEI.

[0061] Additionally, a permanent identifier can also be a hashed IMEI associated with one or more data collection devices.

[0062] As another example, a permanent identifier can also be a chipset hardware model associated with one or more data collection devices, and / or a data collection type identifier associated with one or more data collection devices. That is, one or more data collection devices having the same chipset hardware model and / or whose data collections have the same type identifier can have the same data collection device identifier.

[0063] In some embodiments, at least one data collection device identifier may be an identifier type having a semi-permanent identifier. The semi-permanent identifier used herein may be firmware and / or firmware version associated with the data collection device.

[0064] In some embodiments, at least one data collection device identifier may have an identifier type of temporary identifier. For example, the temporary identifier may be assigned by a provider server based on one or more of the following: the hardware model associated with the data collection device, one or more chipset hardware models associated with the data collection device, and / or the data collection requirements associated with the data collection device. Additionally, the temporary identifier may also be assigned based on machine learning-based data collection and may be provided by an entity that owns the data collection process (e.g., a data collection entity) based on the identifier of the machine learning model and / or machine learning capabilities.

[0065] In some embodiments, at least one data collection device identifier provided by the management entity 120 may refer to one of the identifiers described above. In some embodiments, at least one data collection device identifier may also refer to a range of one of the identifiers described above. For example, at least one data collection device identifier may be IMEI-TAC 0-10.

[0066] It is also possible that at least one data collection device identifier provided by the management entity 120 may refer to a list of one or more identifiers as described above, or at least one data collection device identifier may refer to a list of more than one identifier ranges as described above. At least one data collection device identifier may include a combination of a list of more than one identifier ranges as described above and a list of one or more identifiers as described above.

[0067] As described, at least one data collection may include one or more identifiers of the same or different identifier types, which is beneficial for the supplier server to request data collection from a group of devices of the same type. For example, the supplier server may request data collection from devices with the same hardware model or the same firmware version. In this case, the supplier server may not provide a data collection device identifier for each device. Therefore, signaling overhead can also be reduced.

[0068] like Figure 3 As shown, management entity 120 can send (305) a trace activation message to network node 110 containing at least one provider-specific configuration for data collection from at least one data collection device, and at least one data collection device identifier associated with the at least one provider-specific configuration. For example, the trace activation message can be associated with a new trace job type for data collection based on the provider-specific configuration.

[0069] Management entity 120 may send (310) MDT configuration to network node 110, which configures network node 110 to have a configuration that requests radio measurements from (multiple) devices (e.g., (multiple) UEs). In this case, at least one provider-specific configuration and at least one data collection device identifier associated with at least one provider-specific configuration may be sent from management entity 120 to network node 110 along with the MDT configuration.

[0070] For example, management entity 120 may send at least one provider-specific configuration and at least one data collection device identifier associated with at least one provider-specific configuration, as well as MDT configuration, through two separate tracking activation messages or the same tracking activation message.

[0071] Alternatively, a new tracking job type can be introduced to request both non-standardized measurement data collection and standardized measurement data collection (e.g., measurements associated with an MDT configuration) from network node 110. That is, management entity 120 can send at least one provider-specific configuration and at least one data collection device identifier associated with the at least one provider-specific configuration, along with the MDT configuration, via the same tracking activation message associated with this introduced new tracking job type.

[0072] Upon receiving at least one vendor-specific configuration for data collection and at least one data collection device identifier associated with the at least one vendor-specific configuration, network node 110 may store (315) them. If the MDT configuration has also been provided by management entity 120, network node 110 may also store (320) the MDT configuration.

[0073] User equipment 130 sends (325) at least one UE identifier to network node 110 for associating user equipment 130 with data collection. For illustrative purposes, signaling diagram 300 only involves one user equipment 130. It should be understood that the operations performed by user equipment 130 can also be performed by (multiple) other user equipments.

[0074] In some embodiments, user equipment 130 may send at least one UE identifier to network node 110 without any request from network node 110.

[0075] For example, user equipment 130 may provide at least one UE identifier without being requested, via an RRC establishment completion message or an RRC reconfiguration completion message, for example, whenever user equipment 130 enters the RRC connection state. It should be understood that user equipment 130 may provide at least one UE identifier not only whenever user equipment 130 enters the RRC connection state, but also whenever the identifier changes from a previous identifier.

[0076] As an alternative, user equipment 130 may send at least one UE identifier to network node 110 via a new introduction message associated with the UE identifier without request.

[0077] In some other embodiments, user equipment 130 may send at least one UE identifier to network node 110 upon request from network node 110. Figure 4 Signaling diagram 400 illustrates an example process for a network node to retrieve a UE identifier according to some examples of this disclosure.

[0078] Signaling diagram 400 involves network node 110 and user equipment 130. (Reference) Figure 1 The signaling diagram 400 is described below. Although the signaling diagram 400 only involves one user equipment 130, it should be understood that the operations performed by user equipment 130 can also be performed by (multiple) other user equipments.

[0079] like Figure 4 As shown, network node 110 can send (405) a request to user equipment 130 for retrieving at least one UE identifier. Such a request can be sent by network node 110 to user equipment 130 via an RRC message (i.e., via an RRC establishment message or an RRC reconfiguration message) during the RRC connection establishment process.

[0080] If user equipment 130 determines that at least one UE identifier is available, that is, at least one UE identifier for associating user equipment 130 with data collection has been obtained, then user equipment 130 sends (410) at least one UE identifier to network node 110 in response to the request.

[0081] Accordingly, if network node 110 requests at least one UE identifier through the RRC connection establishment procedure, user equipment 130 may send at least one UE identifier to network node 110 through an RRC establishment complete message or an RRC reconfiguration complete message.

[0082] Network node 110 can also request at least one UE identifier from user equipment 130 after the RRC connection is established. For example, a new message / procedure can be introduced to network node 110 for identifier retrieval from user equipment 130.

[0083] In some other embodiments, at least one UE identifier may be unavailable at user equipment 130. Figure 5 Signaling diagram 500 illustrates another example process by which a network node retrieves a UE identifier, according to some examples of this disclosure.

[0084] Signaling diagram 500 involves network node 110, user equipment 130, and supplier server 140. (Reference) Figure 1 The signaling diagram 500 is described below. Although the signaling diagram 500 only involves one user equipment 130, it should be understood that the operations performed by user equipment 130 can also be performed by (multiple) other user equipments.

[0085] For example, if user equipment 130 determines (510) that at least one UE identifier is not available at user equipment 130, user equipment 130 may send (515) a request to provider server 140 to retrieve at least one UE identifier.

[0086] Alternatively, user equipment 130 may request at least one UE identifier from provider server 140 when it receives (505) a request from network node 110 for retrieving at least one UE identifier.

[0087] Then, the supplier server 140 may provide (520) at least one UE identifier to the user equipment 130. The user equipment 130 sends (525) at least one UE identifier to the network node 110 in response to a request to retrieve at least one UE identifier from the network node 110. Alternatively, the user equipment 130 may send (525) at least one UE identifier to the network node 110 without a request to retrieve at least one UE identifier from the network node 110.

[0088] The provider server 140 may also provide at least one UE identifier to the user equipment 130 without request. For example, when the provider server 140 updates its data collection policy, the provider server 140 may provide at least one UE identifier to the user equipment 130 (520).

[0089] The “at least one UE identifier that associates user equipment 130 with data collection” used herein may be associated with at least one data collection identifier as described above.

[0090] Similarly, at least one UE identifier can refer to one or more identifier types.

[0091] In some embodiments, at least one UE identifier may have an identifier type with a permanent identifier. As an example, the permanent identifier may be an International Mobile Equipment Identity (IMEI) associated with one or more data collection devices and / or an IMEI Type Assignment Code (IMEI-TAC) associated with one or more data collection devices. An IMEI with 14 or 15 digits can be used as a distinctive device-specific identifier to ensure global uniqueness. The first eight digits of the IMEI constitute the Type Assignment Code (TAC), which can indicate the manufacturer and model of a specific device. Therefore, device models from a specific manufacturer can have the same TAC. It should be understood that an IMEI-TAC provided by user equipment 130 can correspond to one or more UEs whose IMEI-TAC field matches the provided IMEI-TAC.

[0092] Additionally, a permanent identifier can also be a hashed IMEI associated with one or more data collection devices.

[0093] As another example, a permanent identifier can also be a chipset hardware model associated with one or more data collection devices and / or a data collection type identifier associated with one or more data collection devices. That is, one or more data collection devices having the same chipset hardware model and / or whose data collections have the same type identifier can have the same data collection device identifier.

[0094] In some other embodiments, at least one UE identifier may have an identifier type of semi-permanent identifier. The semi-permanent identifier used herein may be firmware and / or firmware version associated with the data collection device.

[0095] In other embodiments, at least one UE identifier may also have an identifier type of temporary identifier. For example, a temporary identifier may be assigned by a provider server based on one or more of the following: the hardware model associated with the data collection device, one or more chipset hardware models associated with the data collection device, and / or the data collection requirements associated with the data collection device. Additionally, the temporary identifier may also be assigned based on machine learning-based data collection and may be provided by an entity that owns the data collection process (e.g., a data collection entity) based on identifiers of machine learning models and / or machine learning capabilities.

[0096] Return to reference Figure 3 When receiving at least one UE identifier from user equipment 130, network node 110 may store (330) at least one UE identifier in the UE context.

[0097] Then, at network node 110, selection of a device for data collection based on at least one provider-specific configuration can be performed. Network node 110 can determine whether at least one UE identifier received by user equipment 130 is among, associated with, or mapped to at least one data collection device identifier provided by management entity 120.

[0098] As described above, at least one data collection device identifier may include a single data collection device identifier of identifier type (such as IMEI), or may include multiple data collection device identifiers of identifier type (such as a range of IMEI-TAC (e.g., taking values ​​in the range 0-10)).

[0099] Alternatively, at least one data collection device identifier may include multiple data collection device identifiers of more than one identifier type. That is, one set of data collection device identifiers may be permanent identifiers, and another set of data collection device identifiers may be temporary identifiers.

[0100] For example, in the case where at least one data collection device identifier includes multiple data collection device identifiers of the identifier type, if the received UE identifier of the identifier type is among, associated with, or mapped to multiple data collection device identifiers of the identifier type, then at least one UE associated with the received UE identifier can be selected as a device for data collection according to at least one provider-specific configuration.

[0101] As another example, where at least one data collection device identifier includes multiple data collection device identifiers of more than one identifier type, if the received UE identifier of identifier type is among, associated with, or mapped to multiple data collection device identifiers of more than one identifier type, then at least one UE associated with the received UE identifier can be selected as a device for data collection according to at least one provider-specific configuration. For example, the received UE identifier may be an IMEI, and the multiple data collection device identifiers may include an IMEI-TAC range and a hashed IMEI set. If the received IMEI is among, associated with, or mapped to an IMEI-TAC range and / or a hashed IMEI set, then the UE associated with the IMEI can be selected as a device for data collection according to at least one provider-specific configuration.

[0102] Alternatively, at least one data collection device identifier may include a single data collection device identifier of the same identifier type. In this case, as an option, if a received UE identifier of the same identifier type is in / associated with / mapped to a single data collection device identifier, then at least one UE associated with the received UE identifier may be selected as a device for data collection according to at least one provider-specific configuration.

[0103] As an alternative, the received UE identifier can have a different identifier type than the individual data collection device identifier. For example, the received UE identifier can be an IMEI, and the individual data collection device identifier can be an IMEI-TAC. As mentioned above, the IMEI TAC can be the first 8 bits of the IMEI. That is, even if the received UE identifier can have a different identifier type than the individual data collection device identifier, if the received IMEI has the same first 8 bits as the IMEI TAC (which is provided as the data collection device identifier), the received UE identifier (i.e., IMEI) can still be considered to match the individual data collection device identifier.

[0104] In this way, by matching identifiers from the UE and the management entity with the same or different identifier types, the selection of the UE can be made more flexible.

[0105] In addition to the mapping of at least one UE identifier to at least one data collection device identifier received, network node 110 may also consider user capabilities and user consent to select a device for data collection based on at least one provider-specific configuration.

[0106] Based on the determination of mapping, user capabilities and user consent, network node 110 may select (335) user equipment 130 as a device for data collection according to provider-specific configuration.

[0107] If network node 110 has received the MDT configuration, network node 110 may also determine (340) that user equipment 130 should be configured with one or more measurements associated with the MDT configuration, for example, based on considerations of user consent or UE capability information.

[0108] After selecting user equipment 130 as the device for data collection based on a provider-specific configuration, network node 110 may send (345) at least one provider-specific configuration to user equipment 130 for performing data collection based on at least one provider-specific configuration.

[0109] If network node 110 has already received the MDT configuration, network node 110 can also send the (350) MDT configuration to user equipment 130.

[0110] User equipment 130 can then perform data collection based on the at least one provider-specific configuration. Specifically, user equipment 130 can perform one or more provider-specific measurements associated with the at least one provider-specific configuration. User equipment 130 can generate (355) a report on the data collection performed according to the at least one provider-specific configuration and send it to network node 110. The report on the data collection performed according to the at least one provider-specific configuration may be undecodeable by network node 110 because the data collected based on the at least one provider-specific configuration will be used by the data collection entity or the provider server.

[0111] If at least one UE 130 is configured with an MDT configuration, then at least one UE 140 can also perform one or more measurements associated with the standardized measurement data collection according to the MDT configuration. At least one UE 130 generates (365) a report of one or more measurements associated with the standardized measurement data collection and sends it to network node 110. The report of one or more measurements associated with the standardized measurement data collection is decodable by network node 110.

[0112] User equipment 130 may send reports of one or more measurements associated with standardized measurement data collection, as well as data collected according to at least one supplier-specific configuration. Alternatively, user equipment 130 may send reports of one or more measurements associated with standardized measurement data collection, as well as data collected according to at least one supplier-specific configuration.

[0113] Network node 110 may store (375) reports of data collection performed according to at least one supplier-specific configuration and reports of one or more measurements associated with standardized measurement data collection (if present) at network node 110.

[0114] Network node 110 can then send a report to management entity 120 on data collection based on at least one vendor-specific configuration. If applicable, reports on one or more measurements associated with standardized measurement data collection can also be sent from network node 110 to management entity 120. If the same tracking job type is used for at least one vendor-specific configuration and MDT configuration, they can be sent in a public MDT report.

[0115] As shown in the figure, network node 110 can send (380) reports of data collection performed according to at least one supplier-specific configuration and reports of one or more measurements associated with standardized measurement data collection (if any) to the TCE in data collection entity 301 within management entity 120.

[0116] In some scenarios, provider-specific data collection (UEvsDC) between TCE and UE may not be co-located. Figure 6 A diagram illustrating an example process for collecting supplier-specific data through forwarding, according to some examples of this disclosure.

[0117] In this scenario, reports of data collection based on at least one provider-specific configuration can be forwarded from data collection entity 601 within management entity 120 (e.g., management entity) to UEvsDC at data collection entity 602 located within provider server 140 (e.g., provider server) that is subscribing to management entity 120.

[0118] Based on this solution, it is possible to configure measurements for specific UEs or UE types (e.g., UE hardware model, UE chipset model, or UE firmware version) in a vendor-specific manner. In this way, it is possible to collect both non-standardized and standardized measurement data associated with a specific UE or UE type based on vendor-specific configurations, thereby enhancing the performance of the UE-side model.

[0119] Figure 7 A flowchart of an example method 700 for network node 110 is shown, which can be based on the above... Figures 1 to 6 The examples and embodiments described will be used to perform this. It will be from... Figure 1 Method 700 is described from the perspective of network node 110.

[0120] At box 710, network node 110 receives information from a management entity regarding at least one provider-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration.

[0121] At box 720, network node 110 receives from at least one user equipment (UE) at least one UE at least one UE identifier for associating at least one UE with data collection.

[0122] At box 730, network node 110 determines whether the received at least one user equipment identifier is among at least one data collection device identifier.

[0123] At box 740, if it is determined that at least one received user equipment identifier is among at least one data collection device identifier, then network node 110 selects at least one user equipment for data collection.

[0124] At box 750, network node 110 sends at least one provider-specific configuration to at least one user equipment for performing data collection based on at least one provider-specific configuration.

[0125] As an example, method 700 includes sending a request to a user equipment for retrieving at least one user equipment identifier from at least one user equipment.

[0126] As an example, the request can be sent to the user equipment via an RRC process and / or a dedicated process associated with the retrieval of at least one user equipment identifier.

[0127] As an example, method 700 includes: receiving at least one user equipment identifier from at least one user equipment via an RRC message and / or a dedicated message for providing at least one user equipment identifier, either upon a request from a network node or without a request.

[0128] As an example, method 700 includes: receiving at least one data collection device identifier associated with at least one identifier type, the at least one identifier type including permanent identifiers, semi-permanent identifiers, and / or temporary identifiers.

[0129] As an example, at least one data collection device identifier includes a plurality of data collection device identifiers associated with an identifier type, and method 700 includes: if it is determined that a received user device identifier of a certain identifier type is among a plurality of data collection device identifiers of that identifier type, or a received user device identifier of another identifier type is associated with a plurality of data collection device identifiers of the identifier type, then at least one user device associated with the received user device identifier is selected for data collection.

[0130] As an example, at least one data collection device identifier includes multiple data collection device identifiers associated with multiple identifier types, and method 700 includes: if it is determined that a user device identifier of a received identifier type is among multiple data collection device identifiers of one of multiple identifier types, then at least one user device associated with the received user device identifier is selected for data collection.

[0131] As an example, at least one data collection device identifier includes a data collection device identifier of a certain identifier type, and method 700 includes: if it is determined that a received user device identifier of an identifier type is equal to a data collection device identifier of an identifier type, or a received user device identifier of another identifier type is associated with a data collection device identifier of an identifier type, then at least one user device associated with the received user device identifier is selected for data collection.

[0132] As an example, permanent identifiers include IMEI associated with one or more data collection devices, IMEI type assignment code associated with one or more data collection devices, IMEI-TAC associated with one or more data collection devices, hash IMEI associated with one or more data collection devices, identifier of chipset hardware model associated with one or more data collection devices, and / or data collection type identifier associated with one or more data collection devices.

[0133] As an example, semi-permanent identifiers are based on the firmware and / or firmware version associated with the data collection device.

[0134] As an example, the temporary identifier is assigned by the provider server based on: one or more hardware models associated with the data collection device; one or more chipset hardware models associated with the data collection device; data collection requirements associated with the data collection device; and / or machine learning-based data collection, which is provided by the entity that owns the data collection process based on the identifier of the machine learning model and / or machine learning capabilities.

[0135] Figure 8A flowchart of an example method 800 for managing entity 120 is shown, which can be based on the above... Figures 1 to 6 The examples and embodiments described will be used to perform this. It will be from... Figure 1 Method 800 is described from the perspective of the management entity 120 in the middle.

[0136] At box 810, management entity 120 configures network nodes with at least one provider-specific configuration for data collection from data collection devices and at least one data collection device identifier associated with the at least one provider-specific configuration.

[0137] At box 820, management entity 120 sends information to network nodes about at least one provider-specific configuration for data collection and at least one data collection device identifier associated with the at least one provider-specific configuration.

[0138] Figure 9 A flowchart of an example method 900 for user equipment 130 is shown, which can be based on the above-mentioned method using... Figures 1 to 6 The examples and embodiments described will be used to perform this. It will be from... Figure 1 Method 900 is described from the perspective of user equipment 130.

[0139] At box 910, user equipment 130 sends at least one user equipment identifier to the network node for associating the user equipment with data collection.

[0140] At box 920, user equipment 130 receives one or more provider-specific configurations assigned to the user equipment from a network node for performing data collection based on one or more provider-specific configurations.

[0141] As an example, method 900 includes: receiving a request from a network node for retrieving at least one user equipment identifier.

[0142] As an example, the request is received from the network node via the Radio Resource Control (RRC) process and / or via a dedicated process associated with the retrieval of at least one user equipment identifier.

[0143] As an example, method 900 includes: sending at least one user equipment identifier to the network node via an RRC message and / or a dedicated message for providing at least one user equipment identifier, either upon request from the network node or without a request.

[0144] As an example, method 900 includes: requesting at least one user equipment identifier from a supplier server.

[0145] As an example, method 900 includes performing data collection based on one or more target supplier-specific configurations associated with at least one user equipment identifier.

[0146] As an example, at least one user equipment identifier has an identifier type of permanent identifier, which includes an IMEI associated with one or more data collection devices, an IMEI type assignment code associated with one or more data collection devices, an IMEI-TAC associated with one or more data collection devices, a hash IMEI associated with one or more data collection devices, an identifier of the chipset hardware model associated with one or more data collection devices, and / or a data collection type identifier associated with one or more data collection devices.

[0147] As an example, at least one user equipment identifier is associated with a semi-permanent identifier based on the firmware and / or firmware version associated with the data collection device.

[0148] As an example, at least one user equipment identifier has an identifier type of temporary identifier, which is assigned by the provider server based on one or more of the following: the hardware model associated with the data collection device; one or more chipset hardware models associated with the data collection device; the data collection requirements associated with the data collection device; and / or machine learning-based data collection, which is provided by an entity that owns the data collection process based on the identifier of the machine learning model and / or machine learning capabilities.

[0149] As an example, a device capable of performing any of the methods in 700 (e.g., Figure 1 The network node 110 in the process may include a component for performing the corresponding operation of method 700. This component can be implemented in any suitable form. For example, the component can be implemented in a circuit or software module. The device can serve as... Figure 1 Network node 110 is used to execute or is included in it.

[0150] As an example, the apparatus includes: components for receiving information from a management entity regarding at least one provider-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; components for receiving at least one user device identifier for associating the at least one user device with data collection from at least one user device; components for determining whether the received at least one user device identifier is among the at least one data collection device identifier; components for selecting at least one user device for data collection if it is determined that the received at least one user device identifier is among the at least one data collection device identifier; and components for sending at least one provider-specific configuration to at least one user device for performing data collection according to the at least one provider-specific configuration.

[0151] As an example, the apparatus includes: a component for sending a request to a user equipment for retrieving at least one user equipment identifier from at least one user equipment.

[0152] As an example, the request is sent to the user equipment via a Radio Resource Control (RRC) procedure and / or a dedicated procedure associated with the retrieval of at least one user equipment identifier.

[0153] As an example, the apparatus includes: a component for receiving at least one user equipment identifier from at least one user equipment via an RRC message and / or a dedicated message for providing at least one user equipment identifier, either upon a request from a network node or without a request.

[0154] As an example, the apparatus includes: a component for receiving at least one data collection device identifier associated with at least one identifier type, the at least one identifier type including permanent identifiers, semi-permanent identifiers, and / or temporary identifiers.

[0155] As an example, at least one data collection device identifier includes a plurality of data collection device identifiers associated with an identifier type, and the apparatus includes a component for selecting at least one user device associated with a received user device identifier for data collection if it is determined that a received user device identifier of a certain identifier type is among a plurality of data collection device identifiers of the identifier type or a received user device identifier of another identifier type is associated with a plurality of data collection device identifiers of the identifier type.

[0156] As an example, at least one data collection device identifier includes a plurality of data collection device identifiers associated with a plurality of identifier types, and the apparatus includes: a component for selecting at least one user device associated with the received user device identifier for data collection if it is determined that the user device identifier of the received identifier type is among a plurality of data collection device identifiers of one of a plurality of identifier types.

[0157] As an example, at least one data collection device identifier includes a data collection device identifier of a certain identifier type, and the apparatus includes: a component for selecting at least one user device associated with the received user device identifier for data collection if it is determined that a received user device identifier of the identifier type is equal to the data collection device identifier of the identifier type or a received user device identifier of another identifier type is associated with the data collection device identifier of the identifier type.

[0158] As an example, permanent identifiers include IMEI associated with one or more data collection devices, IMEI type assignment code, IMEI-TAC associated with one or more data collection devices, hash IMEI associated with one or more data collection devices, identifier of chipset hardware model associated with one or more data collection devices, and / or data collection type identifier associated with one or more data collection devices.

[0159] As an example, semi-permanent identifiers are based on the firmware and / or firmware version associated with the data collection device.

[0160] As an example, a temporary identifier is assigned by the provider server based on one or more of the following: the hardware model associated with the data collection device; one or more chipset hardware models associated with the data collection device; the data collection requirements associated with the data collection device; and / or machine learning-based data collection, which is provided by the entity that owns the data collection process based on the identifier of the machine learning model and / or machine learning capabilities.

[0161] As an example, the device includes components for performing other operations, such as method 700 or network node 110. As an example, the components include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to execute.

[0162] As an example, a component capable of executing any method 800 (e.g., Figure 1The management entity 120 in the document may include a component for performing the corresponding operation of method 800. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. This component may serve as... Figure 1 The management entity 120 is used to execute or is included in it.

[0163] As an example, the apparatus includes: components for configuring a network node with at least one provider-specific configuration for data collection from a data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; and components for sending information to the network node regarding the at least one provider-specific configuration for data collection and at least one data collection device identifier associated with the at least one provider-specific configuration.

[0164] As an example, the device includes components for performing other operations, such as method 800 or management entity 120. As an example, the components include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to execute.

[0165] As an example, it can execute any method 900 (e.g., Figure 1 The user equipment 130 in the system may include components for performing the corresponding operations of method 900. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The components may serve as... Figure 1 User equipment 130 is used to perform or is included therein.

[0166] As an example, the apparatus includes: a component for sending at least one user equipment identifier of a user equipment to a network node for associating the user equipment with data collection; and a component for receiving one or more provider-specific configurations assigned to the user equipment from the network node for performing data collection according to one or more provider-specific configurations.

[0167] As an example, the apparatus includes a component for receiving from a network node a request to retrieve at least one user equipment identifier.

[0168] As an example, the request is received from the network node via an RRC process and / or a dedicated process associated with the retrieval of at least one user equipment identifier.

[0169] As an example, the apparatus includes: a component for sending at least one user equipment identifier to a network node in response to a request from a network node or, without a request, via an RRC message and / or a dedicated message for providing at least one user equipment identifier.

[0170] As an example, the apparatus includes a component for requesting at least one user equipment identifier from a supplier server.

[0171] As an example, the apparatus includes a component for performing data collection based on one or more target supplier-specific configurations associated with at least one user equipment identifier.

[0172] As an example, at least one user equipment identifier has an identifier type of permanent identifier, which includes an IMEI associated with one or more data collection devices, an IMEI type assignment code, an IMEI-TAC associated with one or more data collection devices, a hash IMEI associated with one or more data collection devices, an identifier of the chipset hardware model associated with one or more data collection devices, and / or a data collection type identifier associated with one or more data collection devices.

[0173] As an example, at least one user equipment identifier is associated with a semi-permanent identifier, which is based on the firmware and / or firmware version associated with the data collection device.

[0174] As an example, at least one user equipment identifier has an identifier type of temporary identifier, which is assigned by the supplier server based on one or more of the following: the hardware model associated with the data collection device; one or more chipset hardware models associated with the data collection device; data collection requirements associated with the data collection device; and / or machine learning-based data collection, which is provided by the entity that owns the data collection process based on the identifier of the machine learning model and / or machine learning capabilities.

[0175] As an example, the device includes components for performing other operations, as exemplified by method 900 or user equipment 130. As an example, the components include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the device.

[0176] Figure 10 It is suitable for performing the above by means of Figures 1 to 6 A simplified block diagram of the device 1000 described in the examples and embodiments. Device 1000 can be configured to implement a communication device, for example, as... Figure 1 The network node 110, management entity 120, or user equipment 130 shown are illustrated. As shown, device 1000 includes one or more processors 1010, one or more memories 1020 connected to processor 1010, and one or more communication modules 1040 connected to processor 1010.

[0177] Communication module 1040 is used for bidirectional communication. Communication module 1040 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. As an example, communication module 1040 may include at least one antenna.

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

[0179] Memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1022 and other volatile memories that will not persist during power outages.

[0180] Computer program 1030 includes computer-executable instructions that are executed by an associated processor 1010. The instructions of program 1030 may include instructions for performing some of the operations / actions of this disclosure. Program 1030 may be stored in memory (e.g., ROM 1024). Processor 1010 can perform any suitable actions and processes by loading program 1030 into RAM 1022.

[0181] The examples disclosed herein can be implemented by program 1030, enabling device 1000 to execute as referenced. Figures 2 to 9 Any process discussed in this disclosure. Examples of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0182] As an example, program 1030 may be tangibly contained in a computer-readable medium, which may be included in device 1000 (such as in memory 1020) or in other storage devices accessible by device 1000. Device 1000 may load program 1030 from the computer-readable medium into RAM 1022 for execution. As an example, computer-readable media may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein refers to a limitation of the medium itself (i.e., tangible, not tactile), rather than a limitation of the persistence of data storage (e.g., RAM vs. ROM).

[0183] Figure 11 An example of a computer-readable medium 1100 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1100 has a program 1030 stored thereon.

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

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

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

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

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

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

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

Claims

1. A network node, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the network node to at least: Receive at least one user equipment identifier for associating the at least one user equipment with the data collection from at least one user equipment; Receive from the management entity at least one supplier-specific configuration for data collection and at least one data collection device identifier associated with the at least one supplier-specific configuration for data collection; Determine whether the received at least one user equipment identifier is associated with the at least one data collection device identifier; If it is determined that the received at least one user equipment identifier is associated with the at least one data collection device identifier, then the user equipment is selected for the data collection; as well as Send the at least one provider-specific configuration for data collection to the at least one user equipment.

2. The network node according to claim 1, wherein the network node is configured to: Send a request to the at least one user equipment for retrieving the at least one user equipment identifier from the at least one user equipment.

3. The network node of claim 2, wherein the request is sent to the at least one user equipment by: Radio Resource Control (RRC) procedures, and / or A dedicated process associated with the retrieval of the at least one user equipment identifier.

4. The network node according to claim 1, wherein the network node is configured to: The at least one user equipment identifier is received from the at least one user equipment via the following: Based on a request from the network node or an RRC message performed without the request, and / or A dedicated message used to provide the at least one user equipment identifier.

5. The network node according to claim 1, wherein the network node is configured to: Receive the at least one data collection device identifier associated with at least one identifier type, the at least one identifier type including permanent identifiers, semi-permanent identifiers and / or temporary identifiers.

6. The network node of claim 5, wherein the at least one data collection device identifier comprises a plurality of data collection device identifiers associated with one or more identifier types, and wherein the network node is such that: If it is determined that the received user equipment identifier maps to the plurality of data collection device identifiers of at least one of the one or more identifier types, then at least one user equipment associated with the received user equipment identifier is selected for the data collection.

7. The network node of claim 5, wherein the at least one data collection device identifier includes a data collection device identifier of identifier type, and wherein the network node is configured such that: If it is determined that the received user equipment identifier maps to the data collection device identifier of the identifier type, then at least one user equipment associated with the received user equipment identifier is selected for the data collection.

8. The network node according to claim 5, wherein the permanent identifier includes: International Mobile Equipment Identity (IMEI) associated with one or more data collection devices The IMEI type assignment code IMEI-TAC associated with one or more data collection devices. A hashed IMEI associated with one or more data collection devices. The identifier of the chipset hardware model associated with one or more data collection devices, and / or A type identifier for data collection associated with one or more data collection devices.

9. The network node of claim 5, wherein the semi-permanent identifier is based on firmware and / or firmware version associated with the data collection device.

10. The network node of claim 5, wherein the temporary identifier is assigned by the supplier server based on: One or more hardware models associated with the data collection device; One or more chipset hardware models associated with the data collection device; Data collection requirements associated with data collection devices, and / or Machine learning-based data collection, provided by an entity with a data collection process based on the identifier of a machine learning model and / or machine learning capabilities.

11. A management entity, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the management entity to at least: Configure a network node with at least one provider-specific configuration for data collection from a data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; as well as Send information to the network node, the information being about the at least one provider-specific configuration for the data collection and the at least one data collection device identifier associated with the at least one provider-specific configuration.

12. A user equipment, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to at least: Send at least one user equipment identifier of the user equipment to the network node for associating the user equipment with data collection; Receive at least one provider-specific configuration assigned to the user equipment from the network node for performing the data collection based on the at least one provider-specific configuration; as well as The data collection is performed according to at least one supplier-specific configuration.

13. The user equipment of claim 12, wherein the user equipment is configured to: Receive a request from the network node for retrieving the at least one user equipment identifier.

14. The user equipment of claim 13, wherein the request is received from the network node by: Radio Resource Control (RRC) procedures, and / or A dedicated process associated with the retrieval of the at least one user equipment identifier.

15. The user equipment of claim 12, wherein the user equipment is configured to: The at least one user equipment identifier is sent to the network node via the following: Based on a request from the network node or an RRC message performed without the request, and / or A dedicated message used to provide the at least one user equipment identifier.

16. The user equipment of claim 12, wherein the user equipment is configured to: Request the at least one user equipment identifier from the supplier's server.

17. The user equipment of claim 12, wherein the user equipment is configured to: The data collection is performed based on one or more target supplier-specific configurations associated with the at least one user equipment identifier.

18. The user equipment of claim 12, wherein the at least one user equipment identifier has an identifier type of permanent identifier, the permanent identifier comprising: International Mobile Equipment Identity (IMEI) associated with one or more data collection devices The IMEI type assignment code IMEI-TAC associated with one or more data collection devices. A hashed IMEI associated with one or more data collection devices. The identifier of the chipset hardware model associated with one or more data collection devices, and / or A type identifier for data collection associated with one or more data collection devices.

19. The user equipment of claim 12, wherein the at least one user equipment identifier is associated with a semi-permanent identifier, the semi-permanent identifier being based on firmware and / or firmware version associated with the data collection device.

20. The user equipment of claim 12, wherein the at least one user equipment identifier has an identifier type of temporary identifier, the temporary identifier being assigned by a provider server based on: One or more hardware models associated with the data collection device; One or more chipset hardware models associated with the data collection device; Data collection requirements associated with data collection devices, and / or Machine learning-based data collection, provided by an entity with a data collection process based on the identifier of a machine learning model and / or machine learning capabilities.

21. A method comprising: The network node receives information from the management entity regarding at least one provider-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration. Receive at least one user equipment identifier for associating the at least one user equipment with the data collection from at least one user equipment; Determine whether the received at least one user equipment identifier is among the at least one data collection device identifier; If it is determined that the received at least one user equipment identifier is among the at least one data collection device identifier, then the at least one user equipment is selected for the data collection; as well as Send the at least one provider-specific configuration to the at least one user equipment for performing the data collection according to the at least one provider-specific configuration.

22. A method comprising: The management entity configures at least one provider-specific configuration for data collection from data collection devices for network nodes, and at least one data collection device identifier associated with the at least one provider-specific configuration; as well as Send information to the network node, the information being about the at least one provider-specific configuration for the data collection and the at least one data collection device identifier associated with the at least one provider-specific configuration.

23. A method comprising: Send at least one user equipment identifier of the user equipment to the network node for associating the user equipment with data collection; Receive one or more provider-specific configurations assigned to the user equipment from the network node for performing the data collection based on the one or more provider-specific configurations; as well as The data collection is performed according to at least one supplier-specific configuration.

24. A network node, comprising: Components for receiving information from a management entity, the information being about at least one provider-specific configuration for data collection from at least one data collection device and at least one data collection device identifier associated with the at least one provider-specific configuration; A component for receiving from at least one user equipment at least one user equipment identifier for associating the at least one user equipment with the data collection; A component for determining whether the received at least one user equipment identifier is among the at least one data collection device identifier; A component for selecting at least one user equipment for data collection if it is determined that the received at least one user equipment identifier is among the at least one data collection device identifier; as well as A component for sending the at least one provider-specific configuration to the at least one user equipment for performing the data collection according to the at least one provider-specific configuration.

25. A management entity, comprising: Components for configuring at least one provider-specific configuration for data collection from a data collection device for a network node and at least one data collection device identifier associated with the at least one provider-specific configuration; as well as Components for sending information to the network node, the information being about at least one provider-specific configuration for the data collection and at least one data collection device identifier associated with the at least one provider-specific configuration.

26. A user equipment, comprising: Components for sending at least one user equipment identifier of the user equipment to network nodes to associate the user equipment with data collection; Components for receiving one or more provider-specific configurations allocated for the user equipment from the network node for performing the data collection according to the one or more provider-specific configurations; as well as A component for performing the data collection according to the at least one supplier-specific configuration.

27. A computer-readable medium comprising instructions stored thereon, the instructions being configured to cause a device to perform at least the method of claim 22, the method of claim 23, or the method of claim 24.

Images