Data acquisition methods, apparatus, electronic devices, computer-readable media and products

Abstract

This application discloses a data acquisition method, apparatus, electronic device, computer-readable medium, and product, relating to the field of data processing technology. The method includes: identifying a first terminal device from a plurality of terminal devices to be processed based on a first identifier, wherein the first identifier is used to characterize the identity information of the terminal device to be processed, and the first identifier corresponding to the first terminal device is denoted as a target identifier; acquiring update data corresponding to each first terminal device and sending the corresponding update data to the first terminal device; acquiring a first identifier and status information reported by a second terminal device; if the first identifier of the second terminal device matches the target identifier, determining the update status of the second terminal device based on the status information, wherein the update status includes updated or not updated. This application can confirm whether the terminal device that reported the status information has updated through update data, improving the ability to acquire reported status information.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more specifically, to a data acquisition method, apparatus, electronic device, computer-readable medium, and product. Background Technology

[0002] Currently, with the development of electronic information technology, people have increasingly higher requirements for the user experience of terminal devices. Methods to improve the user experience can be found by analyzing the status information of terminal devices. However, the current ability to obtain the status information reported by terminal devices is insufficient. Summary of the Invention

[0003] This application proposes a data acquisition method, apparatus, electronic device, computer-readable medium, and product to improve the above-mentioned deficiencies.

[0004] In a first aspect, embodiments of this application provide a data acquisition method, the method comprising: identifying a first terminal device from a plurality of terminal devices to be processed based on a first identifier, wherein the first identifier is used to characterize the identity information of the terminal device to be processed, and the first identifier corresponding to the first terminal device is denoted as a target identifier; acquiring update data corresponding to each of the first terminal devices, and sending the corresponding update data to the first terminal device; acquiring a first identifier and status information reported by a second terminal device; if the first identifier of the second terminal device matches the target identifier, determining the update status of the second terminal device according to the status information, wherein the update status includes updated or not updated.

[0005] Secondly, embodiments of this application also provide a data acquisition device, the device comprising: a confirmation unit, a first processing unit, an acquisition unit, and a second processing unit. The confirmation unit is configured to confirm a first terminal device from a plurality of terminal devices to be processed based on a first identifier, the first identifier being used to characterize the identity information of the terminal device to be processed, and the first identifier corresponding to the first terminal device being denoted as a target identifier; the first processing unit is configured to acquire update data corresponding to each of the first terminal devices and send the corresponding update data to the first terminal device; the acquisition unit is configured to acquire a first identifier and status information reported by a second terminal device; the second processing unit is configured to, if the first identifier of the second terminal device matches the target identifier, determine the update status of the second terminal device based on the status information, the update status including updated or not updated.

[0006] Thirdly, embodiments of this application also provide an electronic device, including: one or more processors; a memory; and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, and the one or more application programs are configured to perform the methods described above.

[0007] Fourthly, embodiments of this application also provide a computer-readable medium storing processor-executable program code, which, when executed by the processor, causes the processor to perform the above-described method.

[0008] Fifthly, embodiments of this application also provide a computer program product, including a computer program / instructions that, when executed by a processor, implement the above-described method.

[0009] The data acquisition method, apparatus, electronic device, computer-readable medium, and product provided in this application first identify a first terminal device from a plurality of terminal devices to be processed based on a first identifier. Then, update data corresponding to each of the first terminal devices is acquired and sent to the first terminal device. Based on the first identifier and status information reported by the acquired second terminal device, the update status of the second terminal device is confirmed. Since it is impossible to determine whether a terminal device has updated using update data when acquiring the status information reported by the terminal device, the correspondence between status information and update data cannot be known. This application confirms that the second terminal device is the terminal device that received the update data by matching the first identifier with the target identifier. Then, based on the reported status information, the update status of the second terminal device is determined, i.e., it can know whether the second terminal device that reported the status information has updated using update data. Therefore, the correspondence between status information and update data can be known, improving the ability to acquire reported status information.

[0010] Other features and advantages of the embodiments of this application will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the embodiments of this application. The objects and other advantages of the embodiments of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1An application scenario diagram of the data acquisition method provided in the embodiments of this application is shown;

[0013] Figure 2 A flowchart of a data acquisition method provided in an embodiment of this application is shown;

[0014] Figure 3 A flowchart of a data acquisition method according to another embodiment of this application is shown;

[0015] Figure 4 It shows Figure 3 A diagram illustrating one embodiment of step S210;

[0016] Figure 5 It shows Figure 3 A diagram illustrating one embodiment of step S220;

[0017] Figure 6 It shows Figure 5 A diagram illustrating one embodiment of step S222;

[0018] Figure 7 It shows Figure 3 A diagram illustrating one embodiment of step S260;

[0019] Figure 8 It shows Figure 7 A diagram illustrating one embodiment of step S261;

[0020] Figure 9 A schematic diagram of a data acquisition method provided in another embodiment of this application is shown;

[0021] Figure 10 A unit block diagram of the data acquisition apparatus provided in an embodiment of this application is shown;

[0022] Figure 11 A schematic diagram of an electronic device provided in an embodiment of this application is shown;

[0023] Figure 12 A structural block diagram of a computer-readable storage medium provided in an embodiment of this application is shown;

[0024] Figure 13 A structural block diagram of a computer program product provided in an embodiment of this application is shown. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, and not all of them. The components of the embodiments of the present application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without inventive effort are within the scope of protection of the present application.

[0026] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0027] Currently, with the development of electronic information technology, people have increasingly higher requirements for the user experience of terminal devices. Methods to improve the user experience can be found by analyzing the status information of terminal devices. However, the current ability to obtain the status information reported by terminal devices is insufficient.

[0028] It is easy to understand that the ability to obtain status information reported by terminal devices can include the ability to match the obtained status information with terminal devices, that is, the ability to know the identity information of the terminal device corresponding to the reported status information, where the identity information can be used to determine which specific terminal device it is. It can also include the ability to know whether the terminal device has been updated via update data, that is, the ability to know whether the status information was reported by a terminal device that has been updated via update data or has not been updated.

[0029] In existing technologies, terminal devices can generally be managed to improve the user experience by controlling hardware scheduling and application resource usage. For example, limiting the display frame rate can control power consumption, thereby reducing heat generation and improving user experience. Similarly, limiting the processor's operating frequency can also control power consumption, reducing heat generation and improving user experience. Specifically, terminal device management can be achieved by providing updated data to the user's device. Different updated data can include different management measures. For example, updated data A might limit the processor frequency to 2GHz, and updated data B might limit it to 2.1GHz. The updated data can be changes to configuration parameters, such as the processor frequencies of 2GHz and 2.1GHz mentioned above, which can be configured through processor-related settings. In this case, the updated data can be pushed to the user's device through an update platform. Update data can also be system installation packages, such as system software upgrades, which the user can download and install.

[0030] Furthermore, after a user's terminal device receives the updated data, it's necessary to assess the impact of this update on the device. Existing methods could involve pushing different versions of the update data to the user's terminal device on different dates within a specific region. For example, update data A could be pushed to the terminal device on the first date in a specific region, and update data B could be pushed to the terminal device on the second date. Then, by obtaining the status information of all users' terminal devices within that specific region, the differences in status information obtained on different dates can be compared. This status information can include data such as the terminal device's operating temperature, operating current, processor operating frequency, processor load rate, and memory usage. Another approach could be to randomly select users within a specific region and within the same time period, pushing different versions of the update data to the selected users' terminal devices.

[0031] However, the inventors discovered in their research that for methods that push different update data to users' terminal devices on different dates, some data in the terminal device's status information may be affected by environmental changes on different dates. For example, the terminal device's operating temperature may change with the date. Therefore, it is impossible to determine whether the difference in the terminal device's status information on different dates is caused by different update data or by environmental changes brought about by different dates. Furthermore, it is also impossible to know whether the terminal device that reported the status information successfully updated using the pushed update data. For methods that randomly select users within a specific area and the same time period to push different update data, it is not easy to distinguish the terminal devices that received different update data, and the status information reported by those terminal devices; that is, it is impossible to determine which version of update data the terminal device that reported the status information received. Furthermore, it is also impossible to know whether the terminal device that reported the status information successfully updated using the pushed update data. Therefore, the existing methods are insufficient in their ability to obtain the status information reported by terminal devices.

[0032] Therefore, in order to overcome the above-mentioned defects, this application provides a data acquisition method, apparatus, electronic device, computer-readable medium, and product. It can confirm that the second terminal device is the terminal device that has received the updated data by matching the first identifier with the target identifier. Then, based on the reported status information, the update status of the second terminal device is determined. That is, it can be known whether the second terminal that reported the status information has been updated with updated data. Therefore, the correspondence between the status information and the updated data can be known, which improves the ability to acquire the reported status information.

[0033] Please see Figure 1 , Figure 1 This diagram illustrates an application scenario of a data acquisition method provided in an embodiment of this application, namely data acquisition scenario 100. This data acquisition scenario includes a terminal device 110 and a server 130. The terminal device 110 is connected to the server 130.

[0034] Specifically, server 130 can generate different versions of update data and select the corresponding terminal device 110 based on certain conditions, pushing the generated update data to the terminal device 110 so that the terminal device 110 can update itself using the update data. Server 130 then obtains the identifier and status data reported by the terminal device 110, and matches each terminal device 110 with the reported status data based on the identifier and status data, confirming whether the terminal device 110 has updated based on the obtained update data. This allows server 130 to know the status data reported by the terminal device 110 after updating to different versions of update data, thus revealing the correspondence between status information and update data for subsequent data analysis to obtain the optimal update data for the status information. The identifier can be used to represent the identity information of the terminal device.

[0035] In some implementations, the terminal device 110 can update itself based on the acquired update data. The terminal device 110 can also report identifiers and status data, enabling the server to obtain the identifiers and status information reported by the terminal device 110. Specifically, the server 130 can access the Internet through network devices such as access gateways or routers, and the terminal device 110 can access the Internet through cellular data or wireless routers, meaning that the terminal device 110 and the server 130 can communicate via the Internet. The terminal device 110 can be an electronic device, such as a smartphone, tablet, laptop, or desktop computer.

[0036] Furthermore, the method for obtaining the status information reported by the terminal device 110 can be found in subsequent embodiments.

[0037] Please see Figure 2 , Figure 2 This application illustrates a data acquisition method provided by an embodiment of the present application, which can be applied to the data acquisition scenario 100 in the foregoing embodiments. Specifically, the method includes steps S110 to S140.

[0038] Step S110: Identify a first terminal device from a plurality of terminal devices to be processed based on a first identifier. The first identifier is used to characterize the identity information of the terminal device to be processed. The first identifier corresponding to the first terminal device is denoted as the target identifier.

[0039] In some implementation methods, due to the large number and wide distribution of terminal devices, different terminal devices may be located in different external environments. These different external environments may affect the status data reported by the terminal devices, thereby reducing the confidence level of the acquired status data. For example, if terminal devices a and b, which have acquired the same updated data, are located at locations a and b respectively, where the ambient temperature at location a is 20 degrees Celsius and the ambient temperature at location b is 30 degrees Celsius, the temperature-related information in the status information reported by terminal device a will deviate significantly from that reported by terminal device b. This reduces the confidence level of the acquired status data and interferes with subsequent analysis of the collected status data reported by the terminal devices. Therefore, by setting certain conditions, only terminal devices that meet these conditions can be selected as the terminal devices to be processed, thereby avoiding large deviations in status information caused by the external environment. For a method to determine the terminal devices to be processed based on multiple terminal devices, please refer to the following embodiments.

[0040] In some implementations, a first terminal device can be identified from the list of terminal devices to be processed, and then update data can be sent to the first terminal device. For example, all terminal devices to be processed can be considered as the first terminal device, in which case update data can be sent to all terminal devices to be processed.

[0041] In other implementations, a first terminal device can be identified from multiple terminal devices to be processed based on a first identifier. The first identifier is used to characterize the identity information of the terminal devices to be processed; that is, each terminal device to be processed can be uniquely associated with the first identifier. For example, terminal device A can be associated with first identifier A, terminal device B can be associated with first identifier B, and terminal device C can be associated with first identifier C. The first identifier can be a string consisting of multiple characters, such as a string consisting of 128 binary characters. Therefore, the first terminal device can be identified based on one or more characters in the first identifier. For a specific method of identifying a first terminal device from multiple terminal devices to be processed based on the first identifier, please refer to the following embodiments.

[0042] Furthermore, after obtaining the first terminal device, the first identifier corresponding to the first terminal device can be recorded as the target identifier. That is, the first terminal device corresponding to the target identifier can obtain the sent update data.

[0043] Step S120: Obtain update data corresponding to each of the first terminal devices, and send the corresponding update data to the first terminal device.

[0044] It's easy to understand that by controlling the relevant parameters of the first terminal device, the device can be adjusted and controlled, thereby improving the user experience. Therefore, control of the first terminal device and adjustment of its relevant parameters can be achieved by sending update data to it.

[0045] Specifically, the update data can have different versions. Each version of the update data can adjust or restrict the same parameters in the first terminal device, but the specific values ​​of adjustment or restriction differ. For example, update data A and update data B both restrict the operating frequency of the processor in the first terminal device. Update data A restricts the operating frequency of the processor in the first terminal device to 2GHz, while update data B restricts the operating frequency of the processor in the first terminal device to 2.1GHz. In other implementations, each version of the update data can also adjust or restrict different parameters in the first terminal device. For example, update data A restricts the frequency of the processor in the first terminal device, while update data B restricts the power of the processor in the first terminal device.

[0046] In some implementations, the updated data may also have the same business metrics, which may include power consumption, current, temperature, screen brightness, etc. Different business metrics can generate corresponding updated data to obtain the status data corresponding to that business metric, thereby enabling correlation analysis between the updated data and status information. For example, both updated data A and updated data B include the power consumption business metric, where updated data A limits the power consumption of the processor in the first terminal device, and updated data B limits the power consumption of the display screen in the first terminal device. Update data may also have different business metrics. For example, updated data A includes the power consumption business metric, and updated data B includes the temperature business metric, where updated data A limits the power of the processor in the first terminal device, and updated data B limits the power of the processor in the first terminal device. It is easy to understand that the same parameter may have multiple effects, that is, the same parameter may correspond to multiple different business metrics. For example, the processor's power can affect not only the power consumption business metric, but also the current business metric and the temperature business metric. Therefore, even if the updated data have different business metrics, they may still have the same parameter.

[0047] Furthermore, corresponding update data can be generated for each first terminal device. Specifically, the same update data can be generated for each first terminal device; alternatively, different versions of update data can be generated for each first terminal device. For example, a first version of update data can be generated for a certain proportion of the first terminal devices, and a second version of update data can be generated for the remaining first terminal devices. It is easy to understand that the update data can be determined based on the required business metrics. For example, to obtain status information related to the temperature business metric, update data related to the temperature business metric can be obtained.

[0048] Furthermore, after obtaining the update data corresponding to each first terminal device, each update data is sent to the first terminal device. Specifically, the update data can be pushed to the first terminal device through the update platform, enabling the terminal device to update itself using the update data.

[0049] Step S130: Obtain the first identifier and status information reported by the second terminal device.

[0050] In some implementations, information reported by the second terminal device can be obtained, including a first identifier and status information. Before obtaining the first identifier and status information, a request to obtain them can be sent to the second terminal device. This request indicates that the relevant content needs to be reported. The user can confirm this request through the second terminal device, enabling it to report the first identifier and status information.

[0051] Specifically, the first identifier can be used to represent the identity information of the second terminal device reporting the reported information; the status information can include relevant parameters of the corresponding business indicator. For example, if the business indicator is a temperature business indicator, the status information can include the temperature of the second terminal device. Furthermore, the status information can also include the temperature of specific components in the second terminal device, such as the temperature of the processor, the temperature of the memory, and the temperature of the display screen. The status information can also include version information representing the system version of the second terminal device reporting the status information. That is, based on the status information and the corresponding update data of the second terminal device, it can be confirmed whether the second terminal device has been updated, thereby knowing whether the status information was reported by the updated second terminal device, improving the confidence of the status information. In other implementations, after receiving the corresponding update data, the first terminal device can update itself and add an updated identifier to the status information, so that the reported status information can also include an identifier indicating whether an update has been performed. If the identifier is detected in the reported status information, it indicates that the second terminal device has been successfully updated; if the identifier is not detected in the reported status information, it indicates that the second terminal device has not been updated.

[0052] Step S140: If the first identifier of the second terminal device matches the target identifier, determine the update status of the second terminal device according to the status information, wherein the update status includes updated or not updated.

[0053] In some implementations, the first identifier and status information reported by the second terminal device can be matched, meaning it can be known that the status information was reported by the second terminal device corresponding to the first identifier. It can be checked whether the first identifier reported by the second terminal device matches the target identifier. If they match, it indicates that the second terminal device belongs to the first terminal device, meaning the second terminal device is the first terminal device that received update data. At this point, the update status of the second terminal device can be confirmed, which includes updated or not updated. An updated status indicates that the second terminal device has received update data and updated itself using that data. An not updated status indicates that the second terminal device is a terminal device other than the first terminal device, meaning it has not received update data, or it has received update data but has not updated itself.

[0054] Furthermore, through the above steps, the updated status of the second terminal device can be associated with the reported status information, thereby improving the ability to obtain the reported status information.

[0055] Optionally, by associating the updated status of the second terminal device with the reported status information, the impact of the updated data on the status information can be obtained. For example, if there is only one type of updated data, the differences in status information reported by terminal devices that received the updated data and those that did not can be compared; if there are multiple types of updated data, the differences in status information reported by the corresponding impact-damaging device can be compared. It is easy to understand that the status data reported by the terminal devices contains a large amount of data, therefore, automatic analysis can be achieved using automated analysis tools.

[0056] The data acquisition method, apparatus, electronic device, computer-readable medium, and product provided in this application first identify a first terminal device from a plurality of terminal devices to be processed based on a first identifier. Then, update data corresponding to each of the first terminal devices is acquired and sent to the first terminal device. Based on the first identifier and status information reported by the acquired second terminal device, the update status of the second terminal device is confirmed. Since it is impossible to determine whether a terminal device has updated using update data when acquiring the status information reported by the terminal device, the correspondence between status information and update data cannot be known. This application confirms that the second terminal device is the terminal device that received the update data by matching the first identifier with the target identifier. Then, based on the reported status information, the update status of the second terminal device is determined, i.e., it can know whether the second terminal device that reported the status information has updated using update data. Therefore, the correspondence between status information and update data can be known, improving the ability to acquire reported status information.

[0057] Please see Figure 3 , Figure 3 This application illustrates a data acquisition method provided by an embodiment of the present application, which can be applied to the data acquisition scenario 100 in the foregoing embodiments. Specifically, the method includes steps S210 to S260.

[0058] Step S210: Select multiple candidate terminal devices that meet the first update requirements as terminal devices to be processed.

[0059] Due to the large number and wide geographical distribution of terminal devices, external environmental factors may affect the status data reported by these devices, thus reducing the accuracy of the acquired status data. For example, if terminal devices a and b, which have acquired the same updated data, are located in regions a and b respectively, with ambient temperatures of 20 degrees Celsius in region a and 30 degrees Celsius in region b, the temperature-related information reported by terminal device a will deviate significantly from that reported by terminal device b, interfering with subsequent analysis of the collected status data. Therefore, a first update requirement can be used to filter candidate terminal devices, thereby reducing the interference of external environmental factors on the reported status data. Optionally, the first update requirement can include location requirements or time requirements; it can also include both. Sending update data only to candidate terminal devices that meet the first update requirement can minimize interference from external environments caused by different location or time requirements. For example, if the first update requirement is determined based on location requirements, then candidate terminal devices located in a specified region can be selected to meet the first update requirement. For instance, a terminal device located in region A can be considered to meet the first update requirement. If the first update requirement is determined based on time requirements, then candidate terminal devices within a specified time period can be selected to meet the first update requirement. For instance, candidate terminal devices within the time range t1 to t2 can be considered to meet the first update requirement. Specifically, the location requirements of the candidate terminal devices can be obtained through a pre-set tracking table. Specific methods can be found in the following embodiments.

[0060] Please see Figure 4 , Figure 4 A diagram illustrating one embodiment of step S210 is shown, specifically... Figure 4 This includes steps S211 and S212.

[0061] Step S211: Obtain the first information of each of the candidate terminal devices.

[0062] Step S212: Select the candidate terminal device whose first information satisfies the first update requirement as the terminal device to be processed.

[0063] In some implementations, before obtaining the first information from the terminal device, a request for obtaining the first information can be sent to a backup terminal device. This request for obtaining the first information indicates that the first information needs to be obtained. The user can confirm the request for obtaining the first information through the backup terminal device, thereby enabling the backup terminal device to report the first information.

[0064] As described above, in some implementation methods, the first update requirement may include a time requirement or a location requirement. Therefore, by obtaining the first information of each candidate terminal device, it can be determined whether the corresponding candidate terminal device meets the first update requirement. Since the determination of whether the first update requirement is met needs to be based on the first information, the first information may include location information or time information.

[0065] For example, when the first update requirement is a time requirement, the first information may include time information. In this case, the time information of each candidate terminal device can be obtained, and then it can be determined whether the time information meets the time requirement. Candidate terminal devices whose time information meets the time requirement are designated as pending terminal devices. Specifically, the time requirement may include a time range; if the time information falls within the time range, the first update requirement is met. For example, if the time range includes t1 to t2, and the time information of a candidate terminal device is t3, where t3 lies between t1 and t2, then the candidate terminal device corresponding to the time information t3 meets the first update requirement and can be designated as a pending terminal device.

[0066] When the first update requirement is a location requirement, the first information can include location information. In this case, the location information of each candidate terminal device can be obtained, and then it can be determined whether the location information meets the location requirement. Candidate terminal devices whose location information meets the location requirement are designated as pending terminal devices. Specifically, the location requirement can include a specified area; if the location information is located within the specified area, the first update requirement is met. For example, if the specified area is area A, and the location information of the candidate terminal device is area A, then the candidate terminal device whose location information is area A meets the first update requirement and can be designated as a pending terminal device. It is easy to understand that the first information can also include both time information and location information simultaneously; in this case, the first information can also be used to determine whether the first requirement is met.

[0067] In other implementations, the first update requirement may also include a time requirement and a location requirement. In this case, the first information includes time information and location information, i.e., the time information and location information of each terminal device are obtained, and the candidate terminal devices whose location information meets the location requirement and whose time information meets the time requirement are selected as the terminal devices to be processed. Specifically, the time requirement may include a time range, and the location requirement may include a specified area. Therefore, if the location information is located in the specified area and the time information is within the time range, the first update requirement is met, and the candidate terminal devices that meet the first update requirement are selected as the terminal devices to be processed.

[0068] Step S220: Obtain the first identifier for each of the terminal devices to be processed.

[0069] In some implementations, before obtaining the first identifier, second identifier, or third identifier, a request for obtaining the identifier may be sent to the terminal device to be processed. The request for obtaining the identifier is used to indicate that the first identifier, second identifier, or third identifier needs to be obtained. The user can confirm the request for obtaining the identifier through the terminal device to be processed, so that the terminal device to be processed can report the first identifier, second identifier, or third identifier.

[0070] In some implementations, before confirming the first terminal device from among multiple terminal devices to be processed based on the first identifier, the first identifier of each of the terminal devices to be processed can also be obtained, wherein the first identifier is used to characterize the identity information of the terminal device to be processed. For example, the identity information of the terminal device to be processed can be obtained through a data tracking table.

[0071] For details, please refer to Figure 5 , Figure 5 A diagram illustrating one embodiment of step S220 is shown, specifically including steps S221 and S222.

[0072] Step S221: Obtain a second identifier for each of the terminal devices to be processed, wherein the second identifier is used to characterize the identity information of the terminal device to be processed.

[0073] Step S222: Encrypt each of the second identifiers to obtain the first identifier of each of the terminal devices to be processed.

[0074] In some implementations, since the first identifier is used to characterize the identity information of the terminal device, directly transmitting it in plaintext would compromise the security of the terminal device. Therefore, the first identifier can also be an encrypted identifier. Specifically, a second identifier can be obtained for each of the terminal devices to be processed, which characterizes the identity information of the terminal device. Then, each of the second identifiers is encrypted to obtain the first identifier for each of the terminal devices to be processed. Different types of encryption algorithms can be used, such as symmetric encryption or asymmetric encryption.

[0075] It's easy to understand that, generally, different plaintext data, after being encrypted using an encryption algorithm, will result in different encrypted data. However, it's possible for different plaintext data to produce the same encrypted data after being encrypted using an algorithm. In this case, the same encrypted data can correspond to multiple plaintext data. For example, encrypting a second identifier might result in the same first identifier, and the first identifier could correspond to multiple second identifiers; that is, the first identifier and the second identifier are not in a one-to-one correspondence. For instance, second identifier A, after being encrypted using an algorithm, yields first identifier A; second identifier B, after being encrypted using an algorithm, yields first identifier B; and second identifier C, after being encrypted using an algorithm, yields first identifier A. In this case, second identifier A can correspond to either second identifier A or second identifier C, resulting in a non-unique correspondence; that is, it's impossible to confirm the second identifier corresponding to first identifier A. In this situation, identical first and second identifiers can be excluded. Specific methods can be found in the following embodiments.

[0076] For details, please refer to Figure 6 , Figure 6 The diagram shows one embodiment of step S222, which specifically includes steps S223 to S225.

[0077] Step S223: Encrypt each of the second identifiers to obtain the first alternative identifier.

[0078] Step S224: Select the first candidate identifiers that are the same among the multiple first candidate identifiers as the second candidate identifiers.

[0079] Step S225: Select the first candidate identifier (excluding the second candidate identifier) ​​from the plurality of first candidate identifiers as the first identifier of the terminal device to be processed.

[0080] In some implementations, the second identifier can be encrypted to obtain the first candidate identifier. Then, identical first candidate identifiers are used as the second candidate identifier. Finally, the first candidate identifiers other than the second candidate identifier among multiple first candidate identifiers are used as the first identifier of the terminal device to be processed. For example, as in the aforementioned steps, the second identifier A is encrypted to obtain the first candidate identifier A1, the second identifier B is encrypted to obtain the first candidate identifier B1, and the second identifier C is encrypted to obtain the first candidate identifier A1. Since two first candidate identifiers are identical, i.e., the first candidate identifier A1 is used as the second candidate identifier A1, the second candidate identifier A1 can be excluded, and the remaining first candidate identifier B1 is used as the first identifier B1.

[0081] In some implementation methods, it may be inconvenient to directly obtain the second identifier of the terminal device to be processed. In such cases, the third identifier of the terminal device to be processed can be obtained first, and then the corresponding second identifier can be found based on the third identifier. The third identifier and the second identifier can have a one-to-one correspondence. For example, the third identifier can be the International Mobile Equipment Identity (IMEI), and the second identifier can be a Globally Unique Identifier (GUID).

[0082] Step S230: Identify a first terminal device from a plurality of terminal devices to be processed based on a first identifier. The first identifier is used to characterize the identity information of the terminal device to be processed. The first identifier corresponding to the first terminal device is denoted as the target identifier.

[0083] In some implementations, the first identifier can be a string consisting of at least one character. Therefore, identifying a first terminal device from multiple terminal devices to be processed based on the first identifier can be done by identifying the first terminal device based on at least one character in the first identifier. For example, the first terminal device can be identified based on the last character of the first identifier. For instance, a first identifier whose last character is even can be used to identify the terminal device to be processed. Alternatively, a first identifier whose last character is odd can be used to identify the terminal device to be processed.

[0084] Optionally, after confirming the first terminal device from multiple pending terminal devices based on the first identifier, the number of the first terminal devices can also be obtained. If the number is small, it may result in less status information being obtained in the subsequent process, thus reducing the confidence of the obtained status information. In this case, the conditions for confirming the first terminal device based on the first identifier can be adjusted, and the first terminal device can be reconfirmed from multiple pending terminal devices based on the first identifier, so that the number of the first terminal devices is larger, thereby improving the confidence of the obtained status information.

[0085] Step S240: Obtain update data corresponding to each of the first terminal devices, and send the corresponding update data to the first terminal device.

[0086] Step S250: Obtain the first identifier and status information reported by the second terminal device.

[0087] Steps S240 and S250 have been described in detail in the foregoing embodiments and will not be repeated here.

[0088] Step S260: If the first identifier of the second terminal device matches the target identifier, determine the update status of the second terminal device according to the status information, wherein the update status includes updated or not updated.

[0089] Please see Figure 7 , Figure 7 A diagram illustrating one embodiment of step S260 is shown, specifically including steps S261 to S263.

[0090] Step S261: Obtain the matching relationship between the status information and the target update data.

[0091] Step S262: If the matching relationship is already matched, determine that the update status is already updated.

[0092] Step S263: If the matching relationship is not matched, determine that the update status is not updated.

[0093] In some implementations, since the first terminal device corresponding to the target identifier has received updated data, if the first identifier reported by the second terminal device matches the target identifier, it means that the second terminal device has received updated data. The updated data corresponding to the target identifier that matches the first identifier of the second terminal device is considered the target updated data. At this time, the matching relationship between the status information and the target updated data can be obtained. Specifically, the matching relationship can be determined based on the obtained status information reported by the second terminal device and the target updated data. If the matching relationship is matched, the update status is determined to be updated; if the matching relationship is not matched, the update status is determined to be not updated.

[0094] For details, please refer to Figure 8 , Figure 8 A diagram illustrating one embodiment of step S261 is shown, specifically... Figure 8 This includes steps S264 and S265.

[0095] Step S264: If the first version information is the same as the second version information, then it is determined that the matching relationship is matched.

[0096] Step S265: If the first version information is different from the second version information, then the matching relationship is determined to be unmatched.

[0097] In some implementations, the status information includes the current first version information of the second terminal device's system, and the target update data includes second version information. The first version information can be used to characterize the version of the system currently running on the second terminal device, and the target update data also corresponds to a system version. If the second terminal device updates using the received update data, the version of the system running on the second terminal device should be the same as the version in the target update data. Therefore, the matching relationship can be determined by judging whether the current first version information of the second terminal device's system is the same as the second version information included in the target update data. A match indicates that the first version information and the second version information are identical.

[0098] If the first version information and the second version information are the same, the matching relationship is determined to be matched, indicating that the second terminal device has updated using the target update data. If the version of the system running on the second terminal device is different from the version of the update data, that is, if the first version information and the second version information are different, the matching relationship is determined to be unmatched, and the second terminal device has received the update data but has not updated.

[0099] The data acquisition method, apparatus, electronic device, computer-readable medium, and product provided in this application, by determining the terminal device to be processed from multiple candidate terminal devices based on a first update requirement before confirming the first terminal device from multiple candidate terminal devices based on a first identifier, and then obtaining the first identifier of the terminal device to be processed, achieves the filtering of candidate terminal devices using the first update requirement, thereby reducing the interference of external environmental factors on the reported status data. By determining the update status of the second terminal device by obtaining the matching relationship between the status information and the target update data, the updated status of the second terminal device is correlated with the acquired status information, improving the ability to acquire status information.

[0100] Please see Figure 9 , Figure 9 This application illustrates a data acquisition method provided by an embodiment of the present application, which can be applied to the data acquisition scenario 100 in the foregoing embodiments. Specifically, the method includes steps S301 to S311.

[0101] Step S301: Select multiple candidate terminal devices that meet the first update requirements as terminal devices to be processed.

[0102] Due to the large number and wide geographical distribution of terminal devices, external environmental factors may affect the status data reported by these devices, thereby reducing the accuracy of the acquired status data. Therefore, a first update request can be used to filter candidate terminal devices, thus reducing the interference of external environmental factors on the reported status data. The specific method for determining the terminal devices to be processed using the first update request can be found in the aforementioned embodiments, and will not be repeated here.

[0103] Step S302: Obtain the third identifier of the terminal device to be processed.

[0104] In some implementation methods, it may be inconvenient to directly obtain the second identifier of the terminal device to be processed. In such cases, the third identifier of the terminal device to be processed can be obtained first, and then the corresponding second identifier can be found based on the third identifier. The third identifier and the second identifier can be in a one-to-one correspondence. A pre-set tracking table can contain the third identifier used to represent the identity information of the terminal device to be processed, so the third identifier can be obtained through the tracking table. Furthermore, the model code of the terminal device can also be determined based on the third identifier. The model code can be used to represent the type of the terminal device, such as a smartphone, smart tablet, or laptop.

[0105] Optionally, the location of the terminal device satisfying the third condition, the third identifier, and the device model code can be stored in a table. For example, see Table 1.

[0106] Table 1

[0107] Field meaning Field type Model Code String Third identifier String area String

[0108] It's easy to understand that all fields in Table 1 are of string type. The model code and third identifier can be strings consisting of multiple English or numeric characters, while the region is generally represented by Chinese characters. Therefore, a pre-set lookup table can be used to map Chinese characters to numeric or alphanumeric strings. For example, region A can correspond to the string "dyA", and region B can correspond to the string "dyB".

[0109] Step S303: Obtain the second identifier of the terminal device to be processed.

[0110] In some implementations, the corresponding second identifier can also be found based on the third identifier. A one-to-one correspondence can be established between the third and second identifiers. Specifically, when setting the tracking table, the design can simultaneously report both the third and second identifiers. In this case, the corresponding second identifier can be found in the tracking table based on the obtained third identifier. In other implementations, the third and second identifiers can be entered and stored when the terminal device leaves the factory. In this case, the second identifier corresponding to the third identifier can be directly retrieved.

[0111] Optionally, after obtaining the second identifier corresponding to the third identifier, a second identifier can be added to Table 1 above to generate Table 2.

[0112] Table 2

[0113] Field meaning Field type Model Code String Third identifier String area String Second identifier String

[0114] The second identifier can be a string consisting of multiple English or numeric characters, such as a 128-bit binary string. In this case, a one-to-one correspondence is established between the third identifier, the second identifier, and the terminal device.

[0115] Step S304: Obtain the first alternative identifier of the terminal device to be processed.

[0116] Step S305: Does the same first alternative identifier exist?

[0117] In some implementations, the second identifier can be encrypted to obtain the first alternative identifier, and it can be determined whether there is a first alternative identifier with the same identifier. If there is, the process jumps to step S306; if not, the process jumps to step S307.

[0118] Step S306: Obtain the second alternative identifier.

[0119] Step S307: Obtain the first identifier.

[0120] The same first candidate identifier is used as the second candidate identifier, and then the first candidate identifier other than the second candidate identifier among the multiple first candidate identifiers is used as the first identifier of the terminal device to be processed.

[0121] Step S308: Does the first identifier meet the specified conditions?

[0122] In some implementations, the specified condition can be determined based on at least one character in the first identifier. For example, the specified condition can be that the last character in the first identifier is an even number. The terminal device to be processed corresponding to the first identifier that satisfies the specified condition can be designated as the first terminal device. When the specified condition is met, the process jumps to step S309; ​​when the specified condition is not met, the process jumps to step S312.

[0123] Furthermore, to quickly determine whether the first identifier meets the specified conditions, a fourth identifier can be generated based on the specified conditions and the first identifier. This process then transforms the identification of the first terminal device into determining whether the fourth identifier meets the specified conditions. For example, if the specified condition is that the last two characters of the first identifier are in the range of 00 to 50, a fourth identifier can be generated based on the specified conditions and the first identifier, where the fourth identifier can be the last two characters of the first identifier. Then, it can be directly determined whether the fourth identifier meets the specified conditions. If it does, then the first identifier corresponding to the fourth identifier also meets the specified conditions, and the terminal device to be processed corresponding to the first identifier is the first terminal device.

[0124] Therefore, after obtaining the first identifier, a fourth identifier can be added to Table 2 to generate Table 3.

[0125] Table 3

[0126] Field meaning Field type Model Code String Third identifier String area String Second identifier String First identifier String Fourth identifier String

[0127] The fourth identifier in Table 3 is obtained based on the first identifier.

[0128] Step S309: Is the update status of the second terminal device "updated"?

[0129] In some implementations, the second terminal device can report status information and a first identifier. If the first identifier of the second terminal device matches the target identifier, the update status of the second terminal device is determined according to the status information. If the update status is updated, the process jumps to step S310. If the update status is not updated, the process jumps to step S311.

[0130] Step S310: Updated data received and updated.

[0131] The second terminal device corresponding to step S310 has received the update data and updated it using the update data.

[0132] Step S311: Updated data received but not updated.

[0133] The second terminal device corresponding to step S311 received the update data, but did not update using the update data.

[0134] Step S312: No updated data received.

[0135] If the second terminal device corresponding to step S312 has not received update data, it cannot update using update data.

[0136] Please see Figure 10 The diagram shows a structural block diagram of a data acquisition device 1000 provided in an embodiment of this application. The device includes: a confirmation unit 1010, a first processing unit 1020, an acquisition unit 1030, and a second processing unit 1040.

[0137] The confirmation unit 1010 is used to confirm a first terminal device from a plurality of terminal devices to be processed based on a first identifier. The first identifier is used to characterize the identity information of the terminal device to be processed, and the first identifier corresponding to the first terminal device is denoted as the target identifier.

[0138] Furthermore, the confirmation unit 1010 is also used to confirm the first terminal device from among a plurality of terminal devices to be processed based on at least one character in the first identifier.

[0139] Furthermore, the confirmation unit 1010 is also used to identify the terminal device to be processed corresponding to the first identifier whose last character is an even number as the first terminal device.

[0140] The first processing unit 1020 is used to acquire update data corresponding to each of the first terminal devices and send the corresponding update data to the first terminal devices.

[0141] The acquisition unit 1030 is used to acquire the first identifier and status information reported by the second terminal device.

[0142] The second processing unit 1040 is configured to determine the update status of the second terminal device based on status information if the first identifier of the second terminal device matches the target identifier, wherein the update status includes being updated or not being updated.

[0143] Furthermore, the second processing unit 1040 is also used to obtain the matching relationship between the status information and the target update data; if the matching relationship is matched, the update status is determined to be updated; if the matching relationship is not matched, the update status is determined to be not updated.

[0144] Furthermore, the second processing unit 1040 is also configured to determine that the matching relationship is matched if the first version information is the same as the second version information; and to determine that the matching relationship is not matched if the first version information is different from the second version information.

[0145] Furthermore, the data acquisition device 1000 is also used to acquire the first identifier of each of the terminal devices to be processed.

[0146] Furthermore, the data acquisition device 1000 is also used to acquire a second identifier for each of the terminal devices to be processed, the second identifier being used to characterize the identity information of the terminal device to be processed; and to encrypt each of the second identifiers to acquire a first identifier for each of the terminal devices to be processed.

[0147] Furthermore, the data acquisition device 1000 is also configured to encrypt each of the second identifiers to obtain a first alternative identifier; to use the same first alternative identifier among a plurality of first alternative identifiers as a second alternative identifier; and to use the first alternative identifiers other than the second alternative identifier among a plurality of first alternative identifiers as the first identifier of the terminal device to be processed.

[0148] Furthermore, the data acquisition device 1000 is also used to select multiple alternative terminal devices that meet the first update requirements as terminal devices to be processed.

[0149] Furthermore, the data acquisition device 1000 is also used to acquire first information of each of the candidate terminal devices; and to designate the candidate terminal devices whose first information satisfies the first update requirement as the terminal devices to be processed.

[0150] Furthermore, the data acquisition device 1000 is also used to acquire the location information or time information of each of the candidate terminal devices; the step of using the candidate terminal device whose first information satisfies the first update requirement as the terminal device to be processed includes: using the candidate terminal device whose location information satisfies the location requirement or the candidate terminal device whose time information satisfies the time requirement as the terminal device to be processed.

[0151] Furthermore, the data acquisition device 1000 is also used to acquire the location information and time information of each of the candidate terminal devices; the step of using the candidate terminal device whose first information satisfies the first update requirement as the terminal device to be processed includes: using the candidate terminal device whose location information satisfies the location requirement and whose time information satisfies the time requirement as the terminal device to be processed.

[0152] Wherein, the time requirement includes a time range, the location requirement includes a specified area, the location information satisfying the location requirement includes the location information being the specified area, and the time information satisfying the time requirement includes the time information being within the time range.

[0153] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the above-described apparatus and unit can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0154] In the several embodiments provided in this application, the coupling between the units can be electrical, mechanical or other forms of coupling.

[0155] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0156] Please see Figure 11 This diagram illustrates a structural block diagram of an electronic device provided in an embodiment of this application. The electronic device 1100 can be a smartphone, tablet computer, e-reader, etc. The electronic device 1100 in this application may include one or more of the following components: a processor 1110, a memory 1120, and one or more applications, wherein the one or more applications can be stored in the memory 1120 and configured to be executed by one or more processors 1110, and the one or more applications are configured to perform the methods described in the foregoing method embodiments.

[0157] Processor 1110 may include one or more processing cores. Processor 1110 connects to various parts within the electronic device 1100 using various interfaces and lines, and performs various functions and processes data of the electronic device 1100 by running or executing instructions, programs, code sets, or instruction sets stored in memory 1120, and by calling data stored in memory 1120. Optionally, processor 1110 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 1110 may integrate one or more of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into processor 1110 and may be implemented separately using a communication chip.

[0158] The memory 1120 may include random access memory (RAM) or read-only memory (ROM). The memory 1120 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 1120 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch functionality, sound playback functionality, image playback functionality, etc.), and instructions for implementing the various method embodiments described below. The data storage area may also store data created by the terminal 1100 during use (such as phonebook data, audio and video data, chat log data, etc.).

[0159] Please refer to Figure 12 This diagram illustrates a structural block diagram of a computer-readable storage medium provided in an embodiment of this application. The computer-readable medium 1200 stores program code that can be called by a processor to execute the methods described in the above method embodiments.

[0160] Computer-readable storage medium 1200 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. Optionally, computer-readable storage medium 1100 includes a non-transitory computer-readable storage medium. Computer-readable storage medium 1200 has storage space for program code 1210 that performs any of the method steps described above. This program code can be read from or written to one or more computer program products. The program code 1210 may be compressed, for example, in a suitable form.

[0161] Please refer to Figure 13 The diagram illustrates a structural block diagram 1300 of a computer program product provided in an embodiment of this application. The computer program product 1300 includes a computer program / instructions 1310, which, when executed by a processor, implements the steps of the aforementioned method.

[0162] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A data acquisition method, characterized in that, include: Obtain the initial information for each candidate terminal device; The candidate terminal devices whose first information satisfies the first update requirement are designated as terminal devices to be processed. Obtain the first identifier of each of the terminal devices to be processed; A first terminal device is identified from a plurality of terminal devices to be processed based on a first identifier. The first identifier is used to characterize the identity information of the terminal device to be processed. The first identifier corresponding to the first terminal device is denoted as the target identifier. Obtain update data corresponding to each of the first terminal devices, and send the corresponding update data to the first terminal devices; Obtain the first identifier and status information reported by the second terminal device; If the first identifier of the second terminal device matches the target identifier, the update status of the second terminal device is determined according to the status information, and the update status includes updated or not updated.

2. The method according to claim 1, characterized in that, The update data corresponding to the target identifier that matches the first identifier of the second terminal device is used as the target update data. Determining the update status of the second terminal device based on the status information includes: Obtain the matching relationship between the status information and the target updated data; If the matching relationship is already matched, the update status is determined to be updated; If the matching relationship is not matched, the update status is determined to be not updated.

3. The method according to claim 2, characterized in that, The status information includes the current first version information of the system of the second terminal device, and the target update data includes second version information. Obtaining the matching relationship between the status information and the target update data includes: If the first version information is the same as the second version information, then the matching relationship is determined to be matched; If the first version information is different from the second version information, then the matching relationship is determined to be unmatched.

4. The method according to claim 1, characterized in that, The step of obtaining the first identifier of each of the terminal devices to be processed includes: Obtain a second identifier for each of the terminal devices to be processed, the second identifier being used to characterize the identity information of the terminal device to be processed; Each of the second identifiers is encrypted to obtain the first identifier of each of the terminal devices to be processed.

5. The method according to claim 4, characterized in that, The step of encrypting each of the second identifiers to obtain the first identifier of each of the terminal devices to be processed includes: Each of the second identifiers is encrypted to obtain the first alternative identifier; The first candidate identifiers that are the same among multiple first candidate identifiers are used as the second candidate identifiers; The first candidate identifier, excluding the second candidate identifier, among the multiple first candidate identifiers, is used as the first identifier of the terminal device to be processed.

6. The method according to claim 1, characterized in that, The first information includes location information or time information, the first update request includes location request or time request, and obtaining the first information of each of the candidate terminal devices includes: Obtain the location or time information of each of the candidate terminal devices; The step of selecting the candidate terminal device whose first information satisfies the first update requirement as the terminal device to be processed includes: The candidate terminal device whose location information meets the location requirement or whose time information meets the time requirement is selected as the terminal device to be processed.

7. The method according to claim 6, characterized in that, The first information includes location information and time information; the first update request includes location request and time request; obtaining the first information of each of the candidate terminal devices includes: Obtain the location and time information of each of the candidate terminal devices; The step of selecting the candidate terminal device whose first information satisfies the first update requirement as the terminal device to be processed includes: The candidate terminal devices whose location information meets the location requirement and whose time information meets the time requirement are selected as the terminal devices to be processed.

8. The method according to claim 6 or 7, characterized in that, The time requirement includes a time range, the location requirement includes a specified area, the location information satisfies the location requirement by the location information being the specified area, and the time information satisfies the time requirement by the time information being within the time range.

9. The method according to claim 1, characterized in that, The first identifier includes at least one character, and the step of identifying the first terminal device from a plurality of terminal devices to be processed based on the first identifier includes: The first terminal device is identified from a plurality of terminal devices to be processed based on at least one character in the first identifier.

10. The method according to claim 9, characterized in that, The step of identifying the first terminal device from multiple terminal devices based on at least one character in the first identifier includes: The terminal device to be processed corresponding to the first identifier whose last character is an even number is designated as the first terminal device.

11. A data acquisition device, characterized in that, The device includes: The confirmation unit is used to obtain first information of each candidate terminal device; to designate the candidate terminal devices whose first information meets the first update requirement as terminal devices to be processed; to obtain a first identifier of each terminal device to be processed; and to confirm a first terminal device from multiple terminal devices to be processed based on the first identifier, wherein the first identifier is used to characterize the identity information of the terminal device to be processed, and the first identifier corresponding to the first terminal device is denoted as the target identifier. The first processing unit is configured to acquire update data corresponding to each of the first terminal devices and send the corresponding update data to the first terminal devices. The acquisition unit is used to acquire the first identifier and status information reported by the second terminal device; The second processing unit is configured to determine the update status of the second terminal device based on status information if the first identifier of the second terminal device matches the target identifier, wherein the update status includes being updated or not being updated.

12. An electronic device, characterized in that, include: One or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications being configured to perform the method as described in any one of claims 1-10.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium contains program code that can be invoked by a processor to execute the method as described in any one of claims 1-10.

14. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the method described in any one of claims 1-10.

Images