CN116016246A

CN116016246A - Equipment identifier acquisition method and device

Info

Publication number: CN116016246A
Application number: CN202111232300.9A
Authority: CN
Inventors: 石俊杰
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-10-22
Filing date: 2021-10-22
Publication date: 2023-04-25
Also published as: WO2023065901A1

Abstract

The application provides a device identifier acquisition method and device, wherein the device identifier acquisition method comprises the following steps: determining a target validity period; and acquiring a target equipment identifier corresponding to the target validity period, wherein the target equipment identifier is valid in the target validity period, the equipment identifiers corresponding to different validity periods are different, and the target equipment identifier is used for acquiring data in the target validity period. The method and the device can reduce the variety and the quantity of the data identified by the target device identifier, thereby improving the data security and the privacy of the device.

Description

Equipment identifier acquisition method and device

Technical Field

The embodiment of the application relates to the technical field of networks, in particular to a method and a device for acquiring a device identifier.

Background

In data analysis scenarios such as data collection and data processing of devices, the data of the devices (e.g., data based on applications, services, and systems of the devices) often includes more sensitive information such as user identification numbers, phones, addresses, credit card numbers, etc., which can cause unnecessary losses and hazards once compromised. In order to avoid leakage of sensitive information, data of the device is usually subjected to desensitization treatment so as to ensure the security of the data.

The device identifier is used for identifying the data of the device, through which the acquisition of the data of the device can be achieved and sensitive information in the data can be identified, so that the device identifier is particularly important for the security of the data. However, the security of the various device identifiers is low, which results in a high risk of data leakage.

There is therefore a need for a device identifier that ensures data security and reduces the risk of data leakage.

Disclosure of Invention

The application provides a device identifier acquisition method and device, which reduce the variety and quantity of data identified by a target device identifier, thereby improving the data security and privacy of the device.

In a first aspect, the present application provides a device identifier obtaining method, where the method includes: determining a target validity period; and acquiring a target equipment identifier corresponding to the target validity period, wherein the target equipment identifier is valid in the target validity period, the equipment identifiers corresponding to different validity periods are different, and the target equipment identifier is used for acquiring data in the target validity period.

In the method, the target equipment identifier is only valid in the target validity period, so that the equipment identifiers corresponding to different validity periods are different, so that the application can only collect the data of the equipment in the target validity period after acquiring the target equipment identifier, the variety and the quantity of the data identified by the target equipment identifier are reduced, and the data security and the privacy of the equipment are improved.

In one possible implementation, the target validity period includes at least one of the following characters: a start time field, an expiration time field, a valid time unit field, and a valid duration field.

In one possible implementation, the target validity period includes any one of the start time field and the expiration time field, and the valid time unit field, where a time unit of the any one time field and a time unit indicated by the valid time unit field are the same.

The start time field is used to indicate the start time of the target validity period, and the start time may be the receiving time of the acquisition request. The expiration time field is used for indicating the expiration time of the target validity period, and the expiration time can be obtained according to the reception time and the target range information by taking the reception time as the starting time. The valid time unit indicated by the valid time unit field may be obtained based on the first valid time unit in the target range information, and the valid time length field may be used to indicate a duration of the target valid period, which may be greater than or equal to the valid time length in the target range information.

In one possible implementation manner, the determining the target validity period includes: receiving an acquisition request of a device identifier, wherein the acquisition request is used for indicating target range information, and the target range information comprises effective duration or a first effective time unit; and determining the target validity period based on the receiving time of the acquisition request and the target range information, wherein a time period formed by the receiving time and the target range information belongs to the target validity period.

The acquisition request may be sent by the device on which any application is running, for example, by the device on which any application is running when a data acquisition event occurs. The device operated by any application may be the same as or different from the device receiving the acquisition request, i.e. the device operated by any application and the device receiving the acquisition request are two devices in the distributed device networking scenario.

There are various ways of acquiring the request indicating the target range information. In one implementation, the acquisition request may directly indicate the target range information. In another implementation, the acquisition request may directly indicate the purpose of use of the device identifier. The device determines the purpose of use from the acquisition request, and then determines the target range information based on the purpose of use. The device may determine a time period required for the data acquisition process according to the purpose of use, and determine the target range information according to the time period.

The device may store in advance correspondence between a plurality of usage destinations and a plurality of range information, and after receiving the acquisition request, determine, as target range information, range information corresponding to the usage destination indicated by the acquisition request based on the correspondence. Alternatively, the acquisition request may carry a destination character string, where the destination character string is used to indicate the purpose of use. The device may store correspondence between a plurality of destination strings and a plurality of range information.

The reception time may be an absolute time or a relative time. For example, when the reception time is an absolute time, it may be a time at which the acquisition request is received. When the reception time is a relative time, it may be a relative time of the time when the acquisition request is received and the reference time, that is, the interval between the time when the acquisition request is received and the reference time is determined first, and then, the reference time is used as the start, and the time after the interval is determined as the reception time.

In one possible implementation manner, the target range information includes the first valid time unit, and the determining the target validity period based on the receiving time of the acquisition request and the target range information includes: determining a first validity period and/or a second validity period as the target validity period based on the receiving time and the first validity time unit, wherein the first validity period and the second validity period comprise any one of the starting time field and the deadline time field and the validity time unit field; the arbitrary time field and the valid time unit field in the first validity period indicate the reception time and the first valid time unit, respectively; the arbitrary time field and the valid time unit field in the second validity indicate a neighbor time of the reception time and the first valid time unit, respectively, or indicate the reception time and the second valid time unit, respectively; the time interval between the neighbor time and the receiving time is at least one first effective time unit, the second effective time unit is longer than the first effective time unit, the time unit of the receiving time in the first effective period and the time unit of the neighbor time in the second effective period are the same as the first effective time unit, and the time unit of the receiving time in the second effective period is the same as the second effective time unit.

In one possible implementation manner, the determining, based on the receiving time and the first valid time unit, a first valid period and/or a second valid period as the target valid period includes: determining the first validity period based on the reception time and the first validity time unit; when the remaining effective time length of the first effective period is greater than a time length threshold, determining that the first effective period is the target effective period, wherein the remaining effective time length is the difference value between the expiration time of the first effective period and the receiving time; and when the remaining effective duration is less than or equal to the duration threshold, determining the second effective duration based on the receiving time and the first effective time unit, and determining the first effective duration and the second effective duration as the target effective duration.

When the remaining effective duration of the first effective period is less than or equal to the duration threshold, the duration of the data acquisition process is too short, the acquired data quantity and variety are small, and the situation that the use purpose cannot be achieved occurs. Therefore, when the remaining effective duration of the first effective period is longer, the second effective period can be determined, and the remaining effective duration of the target effective period is increased, so that data of sufficient quantity and variety can be obtained, and the realization of the using purpose is ensured.

In one possible implementation manner, the obtaining a target device identifier corresponding to the target validity period includes: and generating the target equipment identifier according to the target validity period.

The device may obtain target device identifier information based on the target validity period, the target device identifier information including a field for indicating a target device identifier and a field for indicating a target validity period. Optionally, the target device identifier information may further include a time zone field for indicating a time zone corresponding to a time indicated by any one of the time fields included in the target validity period.

The device may acquire the hardware information of the device, and then generate a target device identifier according to the hardware information and the target validity period, and regenerate the target device identifier information so that the target device identifier corresponds to the target validity period. Alternatively, the device may hash the hardware information with some or all of the fields in the target validity period using a hashing algorithm to obtain the target device identifier.

In one possible implementation manner, the obtaining a target device identifier corresponding to the target validity period includes: and determining the device identifier with the validity period including the target validity period from a plurality of device identifiers as the target device identifier, wherein the plurality of device identifiers respectively correspond to the validity periods, and the validity periods corresponding to any two device identifiers are different. The device may determine the target validity period itself, after which device identifiers corresponding to a plurality of validity periods are pre-generated.

In a second aspect, the present application provides a device identifier obtaining apparatus, the apparatus including: the processing module is used for determining the target validity period; the processing module is further configured to obtain a target device identifier corresponding to the target validity period, where the target device identifier is valid in the target validity period, device identifiers corresponding to different validity periods are different, and the target device identifier is used to collect data in the target validity period.

In one possible implementation, the apparatus further includes: the device comprises a receiving and transmitting module, a receiving and transmitting module and a receiving module, wherein the receiving and transmitting module is used for receiving an acquisition request of a device identifier, the acquisition request is used for indicating target range information, and the target range information comprises effective duration or a first effective time unit; the processing module is specifically configured to determine the target validity period based on a receiving time of the acquisition request and the target range information, where a time period formed by the receiving time and the target range information belongs to the target validity period.

In a possible implementation manner, the target range information includes the first valid time unit, and the processing module is specifically configured to determine, based on the receiving time and the first valid time unit, a first validity period and/or a second validity period as the target validity period, where each of the first validity period and the second validity period includes any one of the start time field and the deadline field and the valid time unit field; the arbitrary time field and the valid time unit field in the first validity period indicate the reception time and the first valid time unit, respectively; the arbitrary time field and the valid time unit field in the second validity indicate a neighbor time of the reception time and the first valid time unit, respectively, or indicate the reception time and the second valid time unit, respectively; the time interval between the neighbor time and the receiving time is at least one first effective time unit, the second effective time unit is longer than the first effective time unit, the time unit of the receiving time in the first effective period and the time unit of the neighbor time in the second effective period are the same as the first effective time unit, and the time unit of the receiving time in the second effective period is the same as the second effective time unit.

In a possible implementation manner, the processing module is specifically configured to determine the first validity period based on the receiving time and the first validity time unit; when the remaining effective time length of the first effective period is greater than a time length threshold, determining that the first effective period is the target effective period, wherein the remaining effective time length is the difference value between the expiration time of the first effective period and the receiving time; and when the remaining effective duration is less than or equal to the duration threshold, determining the second effective duration based on the receiving time and the first effective time unit, and determining the first effective duration and the second effective duration as the target effective duration.

In a possible implementation manner, the processing module is specifically configured to generate the target device identifier according to the target validity period.

In one possible implementation manner, the processing module is specifically configured to determine, as the target device identifier, a device identifier whose validity period includes the target validity period, where the validity periods correspond to a plurality of device identifiers, and the validity periods corresponding to any two device identifiers are different.

In a third aspect, the present application provides a device identifier obtaining apparatus, including: one or more processors; a memory for storing one or more computer programs or instructions; when executed by the one or more processors, causes the one or more processors to implement the method of any of the first aspects.

In a fourth aspect, the present application provides a device identifier obtaining apparatus, including: a processor for performing the method of any of the first aspects.

In a fifth aspect, the present application provides a computer readable storage medium comprising a computer program or instructions which, when executed on a computer, cause the computer to perform the method of any of the first aspects.

In a sixth aspect, the present application provides a computer program product comprising computer program code which, when run on a computer, causes the computer to perform the method of any one of the first aspects.

Drawings

Fig. 1 is a schematic diagram of a frame of an apparatus according to an embodiment of the present application;

Fig. 2 is a flow chart of a method for acquiring a device identifier according to an embodiment of the present application;

FIG. 3 is a schematic diagram of usage purpose and target range information according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a process for determining a target validity period according to an embodiment of the present application;

fig. 5 is a schematic diagram of a generation process of target device identifier information according to an embodiment of the present application;

fig. 6 is an interaction schematic diagram between a first device and a cloud end according to an embodiment of the present application;

fig. 7 is a schematic diagram of parameters used in a cloud data analysis process according to an embodiment of the present application;

fig. 8 is a block diagram of a device identifier obtaining apparatus provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of an apparatus identifier obtaining device according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of another device identifier obtaining apparatus according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The terms first and second and the like in the description and in the claims of embodiments of the present application are used for distinguishing between different objects and not necessarily for describing a particular sequential order of objects. For example, a first range and a second range, etc. are used to distinguish between different ranges, and are not used to describe a particular order of ranges.

In the embodiments of the present application, words such as "in one example," "illustratively," or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "in one example," "illustratively," or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "in one example," "illustratively," or "such as" is intended to present related concepts in a concrete fashion.

In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "at least one" means one or more, and the meaning of "a plurality" means two or more. For example, the plurality of processing units refers to two or more processing units; the plurality of systems means two or more systems.

In data analysis scenes such as user behavior analysis, fault analysis and big data statistics, the device identifier is used for identifying data of the device, the data of the device can be obtained through the device identifier, and sensitive information in the data can be identified.

In this embodiment of the present application, the device may be a terminal device. For example, it may include: an access terminal, a terminal unit, a terminal station, a mobile station, a remote terminal, a mobile device, a wireless communication device, a terminal agent, a terminal apparatus, and the like. The access terminal may include: cellular telephones, cordless telephones, session initiation protocol (Session Initiation Protocol, SIP) telephones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal Digital Assistant, PDA), handheld devices with wireless communication capabilities, computing devices, other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) networks or terminal devices in evolved public land mobile networks (Public Land Mobile Network, PLMN), etc.

Current device identifiers typically include: international mobile equipment identity (International Mobile Equipment Identity, IMEI), serial Number (SN), mobile equipment identity (Mobile Equipment Identifier, MEID), equipment unique identifier (Unique Device Identifier, UDID), anonymous equipment identifier (Open Anonymous Device Identifier, OAID), android identification Number (Android Identity document, android id), open equipment identifier (Open Device Identifier, ODID), and universal unique identity (Universally Unique Identifier, uuid).

The existing device identifier is usually fixed, and in order to ensure the data security of the device, the device is strict in management of the device identifier acquisition authority. The device identifier is fixed, so that the variety and the quantity of data identified by the device identifier are gradually increased, the possibility that the device is tracked is higher, the data security of the device is lower, and the risk of data leakage of the device is higher. The more strict management of the device identifier acquisition authority can increase the difficulty of acquiring the device identifier (such as the difficulty of acquiring the device identifier by a part of applications), thereby affecting the normal operation of a part of data analysis process.

Further, for a distributed device networking scenario in which a cross-device application experience can be implemented, device identifiers of a plurality of devices in the networking scenario need to be acquired, and data of the plurality of devices can be acquired according to the device identifiers of the plurality of devices, so that the acquired data volume is increased, and therefore the data security of the plurality of devices is low.

There is a need for a device identifier that ensures data security and reduces the risk of data leakage. In the related art, a device collects an identifiable device identifier and sends the device identifier to a server. The server side converts the received equipment identifier into an irreversible equipment identifier through a preset algorithm and sends the equipment identifier to equipment. The device stores the device identifier to a non-updatable storage area. In the process, the server side stores the original equipment identifier, so that the original equipment identifier can be acquired from the server side, and the data of the equipment are acquired, so that the data security of the equipment is lower. In addition, the process of generating the device identifier by the server needs to be performed in a networking environment, and when the server is in a non-networking environment, the server cannot generate the device identifier, so that the applicability of the related art is poor.

The embodiment of the application provides a device identifier acquisition method, which can be applied to the device, such as a first device. When the device identifier acquisition method is applied to the first device, the method may be performed by a different module in the first device. Referring to fig. 1, fig. 1 is a schematic frame diagram of a device provided in an embodiment of the present application, and fig. 1 shows a first device and a plurality of applications (including an application a, an application B, and an application C) running on the first device. The first device includes a data acquisition module 101, a device identifier generation module 102, and a device identifier management module 103. This method will be described below by taking fig. 1 as an example.

Referring to fig. 2, fig. 2 is a flowchart of a method for acquiring a device identifier according to an embodiment of the present application, where the method is applied to the first device (for example, the first device shown in fig. 1). The method may include the following process:

201. an acquisition request for a device identifier is received, the acquisition request indicating target range information, the target range information comprising a valid duration or a first valid time unit.

The acquisition request may be sent by the device on which any application is running, for example, by the device on which any application is running when a data acquisition event occurs. The device on which either application is running may be the same as or different from the device receiving the acquisition request, and may be, for example, the first device or the second device. When the equipment operated by any application is different from the equipment receiving the acquisition request, the two equipment are the two equipment in the distributed equipment networking scene.

There are various ways of acquiring the request indicating the target range information. In one implementation, the acquisition request may directly indicate the purpose of use of the device identifier, which may be determined by the device on which any application is running based on the data acquisition event. The device determines the purpose of use from the acquisition request, and then determines the target range information based on the purpose of use. The device may determine a time period required for the data acquisition process according to the purpose of use, and determine the target range information according to the time period. The longer the duration is, the longer the effective duration or the larger the effective time unit in the target range information is determined; the shorter the duration, the shorter the effective duration or the smaller the effective time unit in the determined target range information.

Wherein the effective time unit may include at least one of: year, quarter, month, day, time, minute, second, etc. The time unit of the effective duration may refer to an effective time unit, and the embodiments of the present application are not described herein.

The device may store in advance correspondence between a plurality of usage destinations and a plurality of range information, and after receiving the acquisition request, determine, as target range information, range information corresponding to the usage destination indicated by the acquisition request based on the correspondence. Alternatively, the acquisition request may carry a destination character string, where the destination character string is used to indicate the purpose of use. The device may store correspondence between a plurality of destination strings and a plurality of range information. The types of the destination strings may include text strings, symbol strings, binary number strings, and the like, for example, the destination strings may be multi-digit codes, which are not limited in the embodiment of the present application.

For example, the purpose of use may include at least one of: locating single-point faults, locating faults such as application performance jamming, frame loss, unsmooth and the like, counting application user behaviors (such as counting month, week or day activities of newly developed application pages), and carrying out loss analysis on part of devices (such as carrying out loss analysis on batteries). The single point failure may include an application unresponsiveness (Application Not Response, ANR), downtime (Crash), and Tombstone problem, which is a file for recording failure information of the single point failure, including basic information of the application, an occurrence address of Crash, stack call information when Crash occurs, and the like. The time length of the data acquisition process required for four purposes of locating single-point faults, locating faults such as application performance jamming, frame loss, unsmooth faults and the like, counting application user behaviors and carrying out loss analysis on part of devices is gradually increased.

For example, referring to fig. 3, fig. 3 is a schematic diagram of usage purpose and target range information provided in the embodiment of the present application, and fig. 3 is an illustration of the target range information including a first effective time unit. As shown in fig. 3, the data acquisition module sends an acquisition request when a data acquisition event occurs, and then determines a use purpose according to the acquisition request. Fig. 3 shows the four purposes of use, where the first effective time unit is determined to be days when the purpose of use is to locate single point failures, and the first effective time unit is determined to be days when the purpose of use is to locate failures such as application performance stuck, lost frames, and unsmooth, and the first effective time unit is determined to be months when the purpose of use is to count application user behaviors, and the first effective time unit is determined to be years when the purpose of use is to perform loss analysis on a part of devices.

The purpose of use and the corresponding target range information are merely exemplary, and are not limited to the purpose of use and the target range information. As long as the time length of the target range information determined based on the purpose of use is ensured, the absolute value of the difference in time length required for the data acquisition process corresponding to the purpose of use is smaller than the difference threshold. For example, the target range information includes a valid duration, and the valid duration corresponding to locating the single point of failure may be 50 minutes, 1 hour, 2 hours, 15 minutes, etc. The effective duration corresponding to faults such as blocking, frame loss, unsmooth positioning and the like of the application performance can be 22 hours, 1 day and 2 hours. The effective duration corresponding to the statistical application user behavior may be 29 days, 1 month, 2 months, 3 days, etc. The effective duration for loss analysis of a portion of the devices may be 300 days, 1 year, 18 days 2 years, etc.

In another implementation, the acquisition request may directly indicate the target range information. The device operated by any application may determine the purpose of use according to the data acquisition event, and further determine the target range information according to the purpose of use, where the process of determining the target range information may refer to the first implementation manner, and this embodiment of the present application is not described herein in detail.

This process 201 may be performed by the device identifier management module 103 in fig. 1. Fig. 1 also shows a second device and an application (including application D) running on the second device, where the first device and the second device are both two devices in the distributed device networking scenario, and the second device includes a distributed communication module 104, where the distributed communication module 104 establishes a communication connection with the data acquisition module 102 of the first device. The acquisition request may be sent to the device identifier management module 103 by a corresponding module in the device on which any of the applications a to D calls. For example, for any of applications a through C, the data acquisition module 101 may be invoked to send an acquisition request to the device identifier management module 103 when a data acquisition event occurs. For the application D, the distributed communication module 104 may be invoked to send indication information to the data acquisition module 101 when a data acquisition event occurs, where the data acquisition module 101 determines that the application D has occurred a data acquisition event according to the received indication information, and then sends an acquisition request to the device identifier management module 103 based on the data acquisition event.

202. And determining the target validity period based on the receiving time and the target range information of the acquisition request, wherein a time period formed by the receiving time and the target range information belongs to the target validity period.

This process may be performed by the device identifier management module 103 shown in fig. 1. The reception time may be an absolute time or a relative time. For example, when the reception time is an absolute time, it may be a time at which the acquisition request is received. When the reception time is a relative time, it may be a relative time of the time when the acquisition request is received and the reference time, that is, the interval between the time when the acquisition request is received and the reference time is determined first, and then, the reference time is used as the start, and the time after the interval is determined as the reception time. For example, the reference time may be 1971, 1, 00. The time zone corresponding to the time when the acquisition request is received may be any one of 24 time zones, for example, may be an eastern eight zone (i.e., beijing time).

The target expiration date may include at least one of the following characters: a start time field, an expiration time field, a valid time unit field, and a valid duration field. When the target validity period includes any one of the start time field and the expiration time field and a valid time unit field, the time unit of any one of the time fields and the time unit indicated by the valid time unit field are the same.

Alternatively, the target validity period may include a start time field and an expiration time field, or include any one of the start time field and the expiration time field, and any one of the valid time unit field and the valid duration field, so long as a time period can be obtained based on the included characters, which is not limited in the embodiment of the present application.

When the target range information includes the first valid time unit, the content indicated by the valid time unit field may be determined, and thus a target validity period including any one of the start time field and the expiration time field and the valid time unit field may be determined.

Alternatively, the first validity period and/or the second validity period may be determined as the target validity period based on the reception time and the first validity time unit. The first validity period and the second validity period each include any one of a start time field and an expiration time field and a validity time unit field. Any time field and valid time unit field in the first validity period indicate the reception time and the first valid time unit, respectively. Any one of the time field and the valid time unit field in the second validity period indicates a neighbor time of the reception time and the first valid time unit, respectively, or indicates the reception time and the second valid time unit, respectively. The time interval between the neighbor time and the receiving time is at least one first effective time unit, and the second effective time unit is longer than the first effective time unit. The time unit of the reception time in the first validity period and the time unit of the neighbor time in the second validity period are the same as the first validity time unit, and the time unit of the reception time in the second validity period is the same as the second validity time unit. In the embodiment of the present application, the number of the second validity periods may be one or more.

For example, assuming that the first validity time unit is day and the receiving time is 2021, 12, 18, 15, then the validity time unit field indicates day and any time field indicates 2021, 12, 18, i.e. 2021, 12, 18. In one example, any time field and valid time unit field in the second validity indicates a neighbor time and a first valid time unit of the reception time, respectively. The second validity period, the validity time unit field indicates day 16, and any time field indicates day 2021, day 12, month 17, day 2021, month 19, or day 2021, month 12, month 20, etc., i.e., the second validity period is day 2021, month 16, day 2021, month 17, day 2021, month 19, or day 2021, month 12, month 20. In another example, any time field and valid time unit field in the second validity period indicate a time of receipt and a second valid time unit, respectively. The second effective time unit is longer than the first effective time unit, and the second effective time unit can be week, month, quarter or year, and the like, accordingly, any time field in the second effective period indicates 2021 year 51 week, 2021 year 12 month, 2021 year 4 quarter or 2021 year, and the like, that is, the second effective period is 2021 year 51 week, 2021 year 12 month, 2021 year 4 quarter or 2021 year, and the like.

Alternatively, the first validity period may be determined based on the reception time and the first validity time unit. And then when the remaining effective time period in the first effective period is longer than a time period threshold value, determining the first effective period as a target effective period. And when the remaining effective duration is less than or equal to the duration threshold, determining a second effective duration based on the receiving time and the first effective time unit, and determining the first effective duration and the second effective duration as target effective durations. The remaining validity period is the difference between the expiration time of the first validity period and the reception time.

When the remaining effective duration of the first effective period is less than or equal to the duration threshold, the duration of the data acquisition process is too short, the acquired data quantity and variety are small, and the situation that the use purpose cannot be achieved occurs. Therefore, when the remaining effective duration of the first effective period is longer, the second effective period can be determined, and the remaining effective duration of the target effective period is increased, so that data of sufficient quantity and variety can be obtained, and the realization of the using purpose is ensured. The time unit of the duration threshold may be shorter than or equal to the time unit indicated by the valid time unit field in the first validity period.

For example, referring to fig. 4, fig. 4 is a schematic diagram illustrating a process for determining a target validity period according to an embodiment of the present application, fig. 4 illustrates a data acquisition module 101 and a device identifier management module 103, and fig. 4 illustrates an example in which a single point of failure is located for the purpose of use. The first effective time unit corresponding to the single point fault is day, when the time length threshold is 0.5, the data acquisition module 101 sends an acquisition request to the device identifier management module 103 when the data acquisition action occurs, and the receiving time of the acquisition request is 2021, 4 months, 5 days, 23 hours and 58 minutes. The first validity period determined at this time is 2021, 4 months and 5 days, the remaining validity period of the first validity period is 2 minutes, and when the remaining validity period is less than 0.5, the second validity period can be determined. Fig. 4 exemplifies the neighboring time and the first time unit of the reception time indicated by any one time field and the time unit field of the second validity period, respectively, and shows three second validity periods of 2021, 4, 6, 2021, 4, 7, and 2021, 4, 8, respectively.

It should be noted that, for the first validity period or the second validity period, since the time unit of any time field and the valid time unit field are the same, the content indicated by the start character and the deadline field are the same, that is, both indicate the reception time. For example, for the first validity period, assuming that the reception time is 2021, 12, 18, 15, and the first validity time unit is day, the contents indicated by the start time field string and the expiration time field string are 2021, 12, 15.

For the expiration time field of the target validity period, when the target range information includes the validity period, a time after the validity period has elapsed from the reception time may be determined as the expiration time indicated by the expiration time field. When the target range information includes a first effective time unit, the first effective time unit may be taken as a time unit of the reception time to determine the deadline. For example, assuming an effective duration of 20 days and a reception time of 2021,

month

4, and 1, then 2021, month 4, and 20 may be determined as the deadlines. The last day of the month where the reception time is located is determined as the deadline assuming that the first effective unit is month, for example, if the reception time is 2021, 4 months, 7 days, then 2021, 4 months, 30 days is determined as the deadline. The last day of the year in which the reception time is located is determined as the deadline assuming that the first effective unit is year, for example, the 2021 year 12 month 31 is determined as the deadline assuming that the reception time is 2021 year 4 month 7.

For the effective duration field of the target effective period, when the target range information includes the effective duration, a duration greater than or equal to the effective duration in the target range information may be determined as the content indicated by the effective duration field. When the target range information includes a first valid time unit, the first valid time unit may be taken as a time unit of the reception time to determine the content indicated by the valid duration field. For example, assuming that the effective duration is 20 days, 21 days, 22 days, or the like may be determined as the content indicated by the effective duration field. Assuming that the first effective unit is month and the reception time is 2021, 4 and 8 days, the time period from 2021, 4 and 8 days to 2021, 4 and 4 days in 2021 may be determined as the content indicated by the effective time period field, that is, 23 days as the content indicated by the effective time period field.

The formats of the respective fields in the target validity period are various, and, for example, taking any time field in which the target validity period includes a start time field or an expiration time field and a valid time unit field as an example, if the time indicated by any time field is 2021, 4 months, 1 days, 15 days, the valid time unit field is year, month, week, day, or time, and accordingly, the content indicated by any time field may be expressed as 2021, 202104, 202114, 20210401, or 2021040115.

203. And acquiring a target device identifier corresponding to the target validity period, wherein the target device identifier is valid in the target validity period, the device identifiers corresponding to different validity periods are different, and the target device identifier is used for acquiring data in the target validity period.

The device may obtain target device identifier information based on a target validity period, the target device identifier information including a field for indicating a target device identifier (also may be referred to as a target UDID) and a field for indicating a target validity period. Optionally, the target device identifier information may further include a time zone field for indicating a time zone corresponding to a time indicated by any one of the time fields included in the target validity period.

There are two ways to obtain the target device identifier, the first way to obtain is to directly generate the target device identifier according to the target validity period. The second obtaining manner is to obtain the target device identifier from the existing device identifiers, and for example, the device identifier whose validity period includes the target validity period among the plurality of device identifiers may be determined as the target device identifier, the plurality of device identifiers respectively correspond to the validity periods, and validity periods corresponding to any two device identifiers are different.

The device may determine whether there is a corresponding device identifier whose validity period includes the target validity period based on the target validity period, and the process may be performed by the device identifier management module 103. When there is a device identifier including the target validity period, the corresponding device identifier whose validity period includes the target validity period may be acquired as the target device identifier, and this process may be performed by the device identifier management module 103. The target device identifier may also be regenerated, and the device identifier management module 103 may invoke the device identifier generation module 102 to regenerate the target device identifier. When there is no device identifier including the target validity period, the target device identifier may be directly generated. The device identifier management module 103 may invoke the device identifier generation module 102 to directly generate the target device identifier.

For the process of generating the target device identifier by the device, the device may acquire the hardware information of the device, and then generate the target device identifier according to the hardware information and the target validity period, and regenerate the target device identifier information so that the target device identifier corresponds to the target validity period. Alternatively, the device may hash the hardware information with some or all of the fields in the target validity period using a hashing algorithm to obtain the target device identifier. The hash algorithm may include a hash secure hash algorithm (Secure Hash Algorithm, sha), such as hash sha256. The hardware information includes at least one of: SN, embedded multimedia card ID (Embedded Multi Media Card ID, emmcid), wireless fidelity media access control address (Wireless Fidelity Media Access Control Address, wifiMac), bluetooth Mac (BluetoothMac).

For example, please refer to fig. 5, fig. 5 is a schematic diagram illustrating a process of generating the target device identifier information according to an embodiment of the present application. Fig. 5 illustrates that the target validity period includes a start time field and a valid time unit field, and the start time field indicates 20210401 as an example. The device passes SN, emmcid, wifiMac, bluetoothMac and 20210401 through hash sha256 to obtain the target device identifier. And then splicing the target equipment identifier, the time zone field, the starting time field (20210401) and the valid time unit field to obtain the target equipment identifier information.

For the process that the device obtains the target device identifier from the existing device identifiers, the device may generate the device identifiers corresponding to a plurality of validity periods in advance, and the process may refer to the foregoing description, which is not repeated herein in the embodiments of the present application. The device may determine the target validity period itself when the device generates device identifiers corresponding to a plurality of validity periods in advance. Assuming that the target validity period includes a valid time unit field, the device may determine a plurality of start times and a plurality of valid time units corresponding to each start time, and then determine a plurality of target validity periods, each target validity period including one of the plurality of start times and one valid time unit corresponding to the one start time.

It should be noted that, when the target validity period includes at least one of the following fields: when the start time field, the expiration time field, and the validity duration field are used, if the validity period corresponding to the existing device identifier only includes a period of time in the target validity period, the device may regenerate the target device identifier corresponding to the target validity period, or may generate the target device identifier corresponding to a time other than a period of time in the target validity period.

After acquiring the target device identifier, the device may send target device identifier information to the application that sent the acquisition request. The device running the application that sends the acquisition request may be the first device or the second device, that is, the application running by the second device in the embodiment of the present application may also request the target device identifier of the first device.

When the target validity period includes a valid time unit field, the target device identifier may include a time-of-day valid device identifier, a month valid device identifier, a year valid device identifier, and the like. As described in the foregoing process 202, the target device identifier is transmitted differently for different purposes of use. As shown in the foregoing fig. 3, fig. 3 also shows the target device identifiers corresponding to different usage purposes. And locating the effective target equipment identifier corresponding to the single-point fault, locating the effective target equipment identifier corresponding to the faults such as the application performance is stuck, the frame is lost, the fault is not smooth, and the like, counting the effective target equipment identifier corresponding to the month of the application user behavior, and carrying out loss analysis on part of devices to obtain the effective target equipment identifier corresponding to the year.

In addition, when the target validity period includes a valid time unit field and the number of target validity periods is plural, for example, the aforementioned first validity period and second validity period, the number of corresponding target device identifiers is plural. As shown in the foregoing fig. 4, fig. 4 also shows the target device identifiers UDID0 to UDID3 respectively corresponding to the first validity period and the three second validity periods. UDID0 to UDID3 are 2021, 4, 5, 2021, 4, 6, 2021, 4, 7, and 2021, 4, 8, respectively. Therefore, in the embodiment of the present application, if the remaining validity period of the target device identifier corresponding to the current first validity period is too short, the device identifier corresponding to the second validity period may be obtained, so as to ensure that the use purpose can be achieved.

When the target validity period includes a valid time unit field, the device identifier management module 103 may perform classification management on the generated device identifiers according to various time units, so as to quickly determine whether there is a device identifier whose corresponding validity period includes the target validity period, thereby improving the acquisition efficiency of the target device identifier.

In this embodiment of the present invention, the first device may further report the obtained target device identifier information to the cloud, where the cloud parses the target device identifier information to obtain contents indicated by each field in the target device identifier information, and stores the parsed contents. The cloud end can acquire the data of the device according to the content indicated by each field in the stored target device identifier information, and analyze the data of the device.

For example, please refer to fig. 6, fig. 6 is a schematic diagram illustrating interaction between a first device and a cloud terminal according to an embodiment of the present application. Fig. 6 shows a first device and a cloud comprising a server, a storage module and a data analysis module. The first device sends target device identifier information to the cloud, the server analyzes the target device identifier information to obtain contents indicated by each field in the target device identifier information, and the contents indicated by each field are stored in the storage module. The data analysis module may then perform data analysis using the content indicated by each field in the target device identifier information stored in the storage module. For example, the data analysis may include: battery aging analysis, reliability analysis, user behavior analysis, and the like.

The following describes a data analysis process of the cloud by taking a data analysis scenario as an example, where the data analysis scenario is a time delay from a first device (e.g. a mobile phone) to a second device (e.g. a television) in the cloud analysis 2021 month 4. The first device may obtain and send to the cloud a target device identifier corresponding to month 2021 of the first device and month 2021 of the second device, and the second device may obtain and send to the cloud a target device identifier corresponding to month 2021 of the second device. The cloud end associates the target device identifiers corresponding to the first device and the second device 2021 month 4 based on the target device identifiers corresponding to the first device and the second device 2021 month 4 sent by the first device, so as to determine a screen projection object of the first device. In the screen projection process carried out in 4 months of 2021, the first device sends a screen projection request to the second device and simultaneously sends a screen projection event to the cloud. And the second equipment receives the screen throwing request and simultaneously sends and receives a screen throwing event to the cloud. And then the first equipment sends the screen-throwing data stream to the second equipment, and the second equipment reads the screen-throwing data stream and simultaneously sends a data stream reading event to the cloud.

It should be noted that, the second device may also send the target device identifier corresponding to other times and the event occurring at other times to the cloud. For example, the second device may obtain and send to the cloud a target device identifier corresponding to month 2021 of the second device. And when receiving an instruction to open a certain application (for example, a video application) at the month 5 of 2021, opens the certain application and simultaneously sends an event of opening the certain application to the cloud.

Thus, when the cloud analyzes the time delay from the first device of 2021 to the second device in month 4 of 2021 according to the target device identifiers of the first device and the second device in month 4 of 2021, the target device identifier of the first device of 2021 in month 4 only identifies the data corresponding to the screen-in process of 2021 in month 4, the data of the other time devices cannot be identified (for example, the data corresponding to a certain application event is opened in month 5 of 2021), and the cloud cannot analyze the data of the first device and the second device in the time beyond month 4 of 2021. Therefore, the data safety and privacy of the device are improved while the quantity and the variety of data in the data analysis process are reduced.

For example, referring to fig. 7, fig. 7 is a schematic diagram of parameters used in a cloud data analysis process according to an embodiment of the present application, where, as shown in fig. 7, the parameters include related parameters of a first device and related parameters of a second device. The relevant parameters include: device type, target device identifier, target expiration start time, target expiration time, time zone, unit of expiration time for the target expiration, event name for various events, event occurrence time, and event parameters. Fig. 7 shows the target device identifiers corresponding to month 2021 and 4 of the two devices, and the event name, event occurrence time, and event parameters of the screen-casting process that occurred at month 2021 and 4. And figure 7 also shows the target device identifier for the second device at 2021, month 5 and the name of the open application event, the time of occurrence of the event and the event parameters that occurred at 2021, month 5.

In summary, according to the method for acquiring the device identifier provided by the embodiment of the present application, the target validity period may be determined, then the target device identifier corresponding to the target validity period may be acquired, the target device identifier is valid in the target validity period, the device identifiers corresponding to different validity periods are different, and the target device identifier is used for acquiring data in the target validity period. The target device identifier is only valid in the target validity period, so that the device identifiers corresponding to different validity periods are different, the application can only collect the data of the device in the target validity period after acquiring the target device identifier, the variety and the quantity of the data identified by the target device identifier are reduced, and the data security and the privacy of the device are improved.

Further, the validity period may be determined based on the received acquisition request sent by the application. The acquisition request may directly indicate the purpose of use of the device identifier or indicate target range information including a valid duration or a first valid time unit. In this way, the application running on the device needs to determine the purpose or target range information of the data of the device before collecting the data of the device, so as to obtain the target device identifier corresponding to the corresponding target validity period. Thereby avoiding the occurrence of the situation that malicious applications collect and leak the data of the device.

The sequence of the method provided by the embodiment of the application can be properly adjusted, and the process can be correspondingly increased or decreased according to the situation. For example, the

aforementioned processes

101 and 102 may not be performed, but the target validity period may be directly determined. Any person skilled in the art will readily recognize that the modified method is within the scope of the present disclosure, and the embodiments of the present disclosure should not be limited thereto.

The above description is mainly given to the device identifier obtaining method provided in the embodiment of the present application from the perspective of the device. It will be appreciated that the apparatus, in order to achieve the above-described functions, comprises hardware structures and/or software modules corresponding to the execution of the respective functions. Those of skill in the art will readily appreciate that the algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application may divide the functional modules of the device according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.

Fig. 8 is a block diagram of a device identifier obtaining apparatus provided in the embodiment of the present application, where the device identifier obtaining apparatus 300 may include a transceiver module 301 and a processing module 302 in a case where respective functional modules are divided by corresponding respective functions. The device identifier obtaining means may be, for example, a device (e.g., a terminal device), a chip or other combination device, component, etc. having the function of the device identifier obtaining means described above. When the device identifier acquiring means is a device, the transceiver module 301 may be a transceiver, which may include an antenna, a radio frequency circuit, and the like; the processing module 302 may be a processor (or processing circuitry), such as a baseband processor, which may include one or more central processing units (central processing unit, CPU) therein. When the device identifier acquiring apparatus is a device or part having the above-described function, the transceiver module 301 may be a radio frequency unit; the processing module 302 may be a processor (or processing circuit), such as a baseband processor. When the device identifier acquiring apparatus 300 is a chip system, the transceiver module 301 may be an input/output interface of a chip (e.g., a baseband chip); the processing module 302 may be a processor (or processing circuit) of a system-on-chip and may include one or more central processing units. It should be appreciated that the transceiver module 301 in the embodiments of the present application may be implemented by a transceiver or transceiver related circuit components; the processing module 302 may be implemented by a processor or processor-related circuit component (alternatively referred to as a processing circuit).

For example, when the device identifier obtaining apparatus 300 is a device or a chip or a functional unit of a device, the transceiver module 301 may be configured to perform all of the transceiver operations performed by the device in the embodiment illustrated in fig. 2, and/or to support other processes of the techniques described herein; the processing module 302 may be used to perform all but the transceiving operations performed by the device in the embodiment illustrated in fig. 2, and/or other processes for supporting the techniques described herein.

The transceiver module 301 may include a transmitting module and/or a receiving module, configured to perform the operations of transmitting and receiving performed by the device in the embodiment shown in fig. 2, and in one example, the device identifier obtaining apparatus includes:

the processing module is used for determining the target validity period;

the processing module is further configured to obtain a target device identifier corresponding to the target validity period, where the target device identifier is valid in the target validity period, device identifiers corresponding to different validity periods are different, and the target device identifier is used to collect data in the target validity period.

In combination with the above scheme, the target validity period includes at least one of the following characters: a start time field, an expiration time field, a valid time unit field, and a valid duration field.

In combination with the above solution, the target validity period includes any one of the start time field and the expiration time field and the valid time unit field, and a time unit of the any one of the time fields is the same as a time unit indicated by the valid time unit field.

In combination with the above solution, the apparatus further includes: the device comprises a receiving and transmitting module, a receiving and transmitting module and a receiving module, wherein the receiving and transmitting module is used for receiving an acquisition request of a device identifier, the acquisition request is used for indicating target range information, and the target range information comprises effective duration or a first effective time unit; the processing module is specifically configured to determine the target validity period based on a receiving time of the acquisition request and the target range information, where a time period formed by the receiving time and the target range information belongs to the target validity period.

In combination with the above solution, the target range information includes the first valid time unit, and the processing module is specifically configured to determine, based on the receiving time and the first valid time unit, a first validity period and/or a second validity period as the target validity period, where each of the first validity period and the second validity period includes any one of the start time field and the deadline field, and the valid time unit field; the arbitrary time field and the valid time unit field in the first validity period indicate the reception time and the first valid time unit, respectively; the arbitrary time field and the valid time unit field in the second validity indicate a neighbor time of the reception time and the first valid time unit, respectively, or indicate the reception time and the second valid time unit, respectively; the time interval between the neighbor time and the receiving time is at least one first effective time unit, the second effective time unit is longer than the first effective time unit, the time unit of the receiving time in the first effective period and the time unit of the neighbor time in the second effective period are the same as the first effective time unit, and the time unit of the receiving time in the second effective period is the same as the second effective time unit.

In combination with the above solution, the processing module is specifically configured to determine the first validity period based on the receiving time and the first validity time unit; when the remaining effective time length of the first effective period is greater than a time length threshold, determining that the first effective period is the target effective period, wherein the remaining effective time length is the difference value between the expiration time of the first effective period and the receiving time; and when the remaining effective duration is less than or equal to the duration threshold, determining the second effective duration based on the receiving time and the first effective time unit, and determining the first effective duration and the second effective duration as the target effective duration.

In combination with the above solution, the processing module is specifically configured to generate the target device identifier according to the target validity period.

In combination with the above solution, the processing module is specifically configured to determine, as the target device identifier, a device identifier whose validity period includes the target validity period, where the device identifiers correspond to validity periods respectively, and validity periods corresponding to any two device identifiers are different.

Fig. 9 is a schematic structural diagram of an apparatus identifier obtaining device provided in the embodiment of the present application, where the apparatus identifier obtaining device 400 may be a chip or a functional module in an apparatus. As shown in fig. 9, the device identifier acquisition apparatus 400 includes a processor 401, a transceiver 402, and a communication line 403.

Wherein the processor 401 is adapted to perform any of the steps performed by the device in the method embodiment shown in fig. 2, and when performing signal/data transmission such as acquisition, the transceiver 402 and the communication line 403 may be selectively invoked to complete the corresponding operations.

Further, the device identifier acquisition means 400 may further comprise a memory 404. The processor 401, the memory 404, and the transceiver 402 may be connected by a communication line 403.

Processor 401 is, among other things, a CPU, general purpose processor network processor (network processor, NP), digital signal processor (digital signal processing, DSP), microprocessor, microcontroller, programmable logic device (programmable logic device, PLD), or any combination thereof. The processor 401 may also be any other device having a processing function, such as a circuit, a device, or a software module, without limitation.

A transceiver 402 for communicating with other devices or other communication networks, which may be ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), etc. The transceiver 402 may be a module, circuitry, transceiver, or any device capable of enabling communications.

The transceiver 402 is mainly used for receiving and transmitting signals/data, and may include a transmitter and a receiver for respectively transmitting and receiving signals/data; operations other than signal/data transceiving are implemented by a processor, such as information processing, computation, and the like.

A communication line 403 for transmitting information between the respective components included in the device identifier acquisition apparatus 400.

In one design, the processor may be considered logic circuitry and the transceiver may be considered interface circuitry.

Memory 404 for storing instructions. Wherein the instructions may be computer programs.

The memory 404 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM). The memory 404 may also be a compact disk (compact disc read-only memory) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media, or other magnetic storage device, etc. It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It is noted that the memory 404 may exist separately from the processor 401 or may be integrated with the processor 401. Memory 404 may be used to store instructions or program code or some data, etc. The memory 404 may be located in the device identifier acquiring apparatus 400 or may be located outside the device identifier acquiring apparatus 400, without limitation. The processor 401 is configured to execute instructions stored in the memory 404, so as to implement the method provided in the foregoing embodiments of the present application.

In one example, processor 401 may include one or more CPUs, such as CPU0 and CPU1 in fig. 9.

As an alternative implementation, the device identifier obtaining apparatus 400 includes a plurality of processors, for example, may include a processor 407 in addition to the processor 401 in fig. 9.

As an alternative implementation, the device identifier obtaining apparatus 400 further comprises an output device 405 and an input device 406. Illustratively, the input device 406 is a keyboard, mouse, microphone, or joystick device, and the output device 405 is a display screen, speaker (spaker), or the like.

It should be noted that the device identifier acquiring apparatus 400 may be a terminal device, a network device, a relay device, an embedded device, a chip system, or a device having a similar structure as in fig. 9. Further, the constituent structure shown in fig. 9 does not constitute a limitation of the device identifier acquiring apparatus 400, and the device identifier acquiring apparatus 400 may include more or less components than those shown in fig. 9, or may combine some components, or may be arranged differently, in addition to those shown in fig. 9.

The processors and transceivers described herein may be implemented on integrated circuits (integrated circuit, ICs), analog ICs, radio frequency ICs, mixed signal ICs, application specific integrated circuits (application specific integrated circuit, ASIC), printed circuit boards (printed circuit board, PCB), electronic devices, and the like. The processor and transceiver may also be fabricated using a variety of IC process technologies such as complementary metal oxide semiconductor (complementary metal oxide semiconductor, CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (Bipolar Junction Transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

It is noted that the device identifier obtaining apparatus 400 may be any type of handheld device or stationary device, such as a notebook or laptop, a mobile phone, a smart phone, a tablet or tablet, a camera, a desktop computer, a set-top box, a television, a display device, a digital media player, a video game console, a video streaming device (e.g., a content service server or a content distribution server), a broadcast receiving device, a broadcast transmitting device, a monitoring device, etc., and may not use or use any type of operating system. The device identifier obtaining apparatus 400 may be a device in a cloud computing scenario, such as a virtual machine in the cloud computing scenario. In some cases, the device identifier acquisition apparatus 400 may be equipped with components for wireless communication. Thus, the device identifier obtaining means 400 may be a wireless communication device. Or a device having a similar structure to that of fig. 9. Further, the constituent structure shown in fig. 9 does not constitute a limitation of the device identifier acquiring apparatus 400, and the device identifier acquiring apparatus 400 may include more or less components than those shown in fig. 9, or may combine some components, or may be arranged differently, in addition to those shown in fig. 9.

The device identifier obtaining apparatus 400 may also be a chip system, which may be formed by a chip, or may include a chip and other discrete devices. Further, actions, terms, etc. referred to between embodiments of the present application may be referred to each other without limitation. In the embodiment of the present application, the name of the message or the name of the parameter in the message, etc. interacted between the devices are only an example, and other names may also be adopted in the specific implementation, and are not limited.

As yet another implementation, the transceiver module 301 in fig. 8 may be replaced by the transceiver 402 in fig. 9, and the transceiver 402 may integrate the functions of the transceiver module 301; the processing module 302 may be replaced by a processor 407, which processor 407 may integrate the functions of the processing module 302. Further, the device identifier obtaining apparatus 300 shown in fig. 8 may further include a memory (not shown in the figure). When the transceiver module 301 is replaced by the transceiver 402 and the processing module 302 is replaced by the processor 407, the device identifier acquiring apparatus 300 shown in fig. 8 may be the device identifier acquiring apparatus 400 shown in fig. 9.

Fig. 10 is a schematic structural diagram of another device identifier obtaining apparatus according to an embodiment of the present application. The device identifier obtaining apparatus may be adapted to the scenario shown in the above-described method embodiment. For ease of illustration, fig. 10 shows only the main components of the device identifier acquisition apparatus, including a processor, a memory, a control circuit, and an input-output apparatus. The processor is mainly used for processing the communication protocol and the communication data, executing the software program and processing the data of the software program. The memory is mainly used for storing software programs and data. The control circuit is mainly used for supplying power and transmitting various electric signals. The input/output device is mainly used for receiving data input by a user and outputting the data to the user.

When the device identifier obtaining apparatus is a device, the control circuit is a main board, the memory includes a hard disk, a RAM, a ROM and other media with storage functions, the processor may include a baseband processor and a central processor, the baseband processor is mainly used for processing communication protocols and communication data, the central processor is mainly used for controlling the whole network device, executing a software program, processing data of the software program, and the input/output apparatus includes a display screen, a keyboard, a mouse and the like; the control circuit may further include or be connected to a transceiver circuit or transceiver, for example: network interfaces, etc., for transmitting or receiving data or signals, such as data transmissions and communications with other devices. Further, the wireless communication device can also comprise an antenna for receiving and transmitting wireless signals and transmitting data/signals with other devices.

According to the method provided by the embodiment of the application, the application further provides a computer program product, which comprises computer program code, which when run on a computer causes the computer to perform the method according to any of the embodiments of the application.

Embodiments of the present application also provide a computer-readable storage medium. All or part of the above-described method embodiments may be implemented by a computer or an apparatus having information processing capabilities to control the implementation of relevant hardware, and the computer program or the set of instructions may be stored in the above-described computer-readable storage medium, and the computer program or the set of instructions may include the above-described method embodiments when executed. The computer readable storage medium may be an internal storage unit of the device of any of the foregoing embodiments, such as a hard disk or a memory of the device. The computer readable storage medium may be an external storage device of the device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash card (flash card), or the like. Further, the computer-readable storage medium may include both an internal storage unit and an external storage device of the above device. The computer-readable storage medium is used to store the computer program or instructions and other programs and data required by the apparatus. The above-described computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (personal computer, server, network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for obtaining a device identifier, the method comprising:

determining a target validity period;

and acquiring a target equipment identifier corresponding to the target validity period, wherein the target equipment identifier is valid in the target validity period, the equipment identifiers corresponding to different validity periods are different, and the target equipment identifier is used for acquiring data in the target validity period.

2. The method of claim 1, wherein the target expiration date comprises at least one of the following characters: a start time field, an expiration time field, a valid time unit field, and a valid duration field.

3. The method of claim 2, wherein the target validity period comprises any one of the start time field and the expiration time field and the valid time unit field, wherein a time unit of the any one of the time fields and a time unit indicated by the valid time unit field are the same.

4. A method according to claim 2 or 3, characterized in that the method further comprises:

receiving an acquisition request of a device identifier, wherein the acquisition request is used for indicating target range information, and the target range information comprises effective duration or a first effective time unit;

the determining the target validity period includes:

and determining the target validity period based on the receiving time of the acquisition request and the target range information, wherein a time period formed by the receiving time and the target range information belongs to the target validity period.

5. The method of claim 4, wherein the target range information comprises the first unit of validity, wherein the determining the target validity period based on the time of receipt of the acquisition request and the target range information comprises:

determining a first validity period and/or a second validity period as the target validity period based on the receiving time and the first validity time unit, wherein the first validity period and the second validity period comprise any one of the starting time field and the deadline time field and the validity time unit field;

the arbitrary time field and the valid time unit field in the first validity period indicate the reception time and the first valid time unit, respectively;

The arbitrary time field and the valid time unit field in the second validity indicate a neighbor time of the reception time and the first valid time unit, respectively, or indicate the reception time and the second valid time unit, respectively;

the time interval between the neighbor time and the receiving time is at least one first effective time unit, the second effective time unit is longer than the first effective time unit, the time unit of the receiving time in the first effective period and the time unit of the neighbor time in the second effective period are the same as the first effective time unit, and the time unit of the receiving time in the second effective period is the same as the second effective time unit.

6. The method of claim 5, wherein the determining a first validity period and/or a second validity period as the target validity period based on the reception time and the first validity time unit comprises:

determining the first validity period based on the reception time and the first validity time unit;

when the remaining effective time length of the first effective period is greater than a time length threshold, determining that the first effective period is the target effective period, wherein the remaining effective time length is the difference value between the expiration time of the first effective period and the receiving time;

And when the remaining effective duration is less than or equal to the duration threshold, determining the second effective duration based on the receiving time and the first effective time unit, and determining the first effective duration and the second effective duration as the target effective duration.

7. The method according to any one of claims 1 to 6, wherein the obtaining a target device identifier corresponding to the target validity period comprises:

and generating the target equipment identifier according to the target validity period.

8. The method according to any one of claims 1 to 6, wherein the obtaining a target device identifier corresponding to the target validity period comprises:

and determining the device identifier with the validity period including the target validity period from a plurality of device identifiers as the target device identifier, wherein the plurality of device identifiers respectively correspond to the validity periods, and the validity periods corresponding to any two device identifiers are different.

9. A device identifier acquisition apparatus, the apparatus comprising:

the processing module is used for determining the target validity period;

10. The apparatus of claim 9, wherein the target expiration date comprises at least one of the following characters: a start time field, an expiration time field, a valid time unit field, and a valid duration field.

11. The apparatus of claim 10, wherein the target validity period comprises any one of the start time field and the expiration time field and the valid time unit field, wherein a time unit of the any one of the time field and a time unit indicated by the valid time unit field are the same.

12. The apparatus according to claim 10 or 11, characterized in that the apparatus further comprises: the device comprises a receiving and transmitting module, a receiving and transmitting module and a receiving module, wherein the receiving and transmitting module is used for receiving an acquisition request of a device identifier, the acquisition request is used for indicating target range information, and the target range information comprises effective duration or a first effective time unit; the processing module is specifically configured to determine the target validity period based on a receiving time of the acquisition request and the target range information, where a time period formed by the receiving time and the target range information belongs to the target validity period.

13. The apparatus according to claim 12, wherein the target range information comprises the first time unit of validity, wherein the processing module is configured to determine, based on the time of receipt and the first time unit of validity, a first validity period and/or a second validity period as the target validity period, each of the first validity period and the second validity period comprising either one of the start time field and the deadline time field and the time unit of validity field; the arbitrary time field and the valid time unit field in the first validity period indicate the reception time and the first valid time unit, respectively; the arbitrary time field and the valid time unit field in the second validity indicate a neighbor time of the reception time and the first valid time unit, respectively, or indicate the reception time and the second valid time unit, respectively; the time interval between the neighbor time and the receiving time is at least one first effective time unit, the second effective time unit is longer than the first effective time unit, the time unit of the receiving time in the first effective period and the time unit of the neighbor time in the second effective period are the same as the first effective time unit, and the time unit of the receiving time in the second effective period is the same as the second effective time unit.

14. The apparatus according to claim 13, wherein the processing module is configured to determine the first validity period based in particular on the reception time and the first validity time unit; when the remaining effective time length of the first effective period is greater than a time length threshold, determining that the first effective period is the target effective period, wherein the remaining effective time length is the difference value between the expiration time of the first effective period and the receiving time; and when the remaining effective duration is less than or equal to the duration threshold, determining the second effective duration based on the receiving time and the first effective time unit, and determining the first effective duration and the second effective duration as the target effective duration.

15. The apparatus according to any one of claims 9 to 14, wherein the processing module is configured to generate the target device identifier in particular according to the target validity period.

16. The apparatus according to any one of claims 9 to 14, wherein the processing module is specifically configured to determine, as the target device identifier, a device identifier whose validity period includes the target validity period, which corresponds to a plurality of device identifiers, respectively, and the validity periods corresponding to any two device identifiers are different.

17. A device identifier acquisition apparatus, comprising:

one or more processors;

a memory for storing one or more computer programs or instructions;

when executed by the one or more processors, causes the one or more processors to implement the method of any one of claims 1 to 8.

18. A computer readable storage medium comprising a computer program or instructions which, when executed on a computer, cause the computer to perform the method of any of claims 1 to 8.