RU2750642C2 - System and method for registering a unique mobile device identifier - Google Patents

Abstract

FIELD: information security.

SUBSTANCE: method is proposed containing stages in which: at the request of the application, at least two mobile device identifiers are selected based on a rule from the list of rules for selecting mobile device identifiers; a unique identifier is formed based on the requested local identifiers; the unique identifier generated for the specified application is synchronized with the unique identifiers generated earlier for related applications, where during synchronization a single unique identifier is determined, which is provided to all related applications; the unique identifier obtained as a result of synchronization is registered in the database of unique identifiers.

EFFECT: technical result is ensuring the registration of the unique mobile device identifier.

12 cl, 3 dwg

Description

Technology area

The invention relates to the field of information security, and more specifically to systems and methods for working with unique identifiers of mobile devices.

State of the art

The rapid development of computer technologies in the last decade, as well as the widespread use of various computing devices (personal computers, laptops, tablets, smartphones, etc.) have become a powerful incentive for the use of these devices in various fields of activity and for a huge number of tasks (from the Internet surfing to bank transfers and electronic document management).

In connection with the above, tasks (and applications that implement them) have come to the fore, providing a single information environment for the user, when, working in one application, the user can use the results of his work in another application, using one device (for example, a mobile phone), the user can continue to work on another device (for example, a tablet). For the effective implementation of the specified functionality, knowledge about all user's devices (including mobile devices), applications running on these devices and data exchanged by these applications is required. In a particular case, the described approach is used to implement an ecosystem of user information security, in order to provide full support for which it is necessary to know exactly which applications are installed on one device and which ones are installed on different ones.

Often there are problems with the collection of such information, for example, the Android operating system with each new version toughens the rules for accessing standard device identifiers: IMEI, Serial ID, Android ID, WiFi Mac, Advertising ID. Starting with Android 8, most of them require ReadPhoneState permission, which is very negative for the user experience when requested. Other parameters (for example Advertising ID) can be locked by the user or even reset.

Only applications with a single signature can use the equivalent of a shared data store. Often, if there are several applications that create a security ecosystem on Android devices, this is difficult to implement and it is impossible to change the situation without re-releasing the application (which means the loss of all users). Therefore, to ensure the quality of applications and services, you have to sacrifice user experience and request ReadPhoneState permission.

The present invention solves the problem of determining a unique identifier for a mobile device.

Disclosure of invention

The invention is intended to determine the unique identifier of a mobile device.

The technical result of the present invention is to implement the purpose.

The system for registering a unique identifier of a mobile device (hereinafter referred to as a unique identifier) at the request of at least two applications that exchange data with each other (hereinafter referred to as related applications) running on the specified mobile device comprises: a selection tool designed to select an application at least measure of two identifiers of a mobile device (hereinafter, local identifiers) based on a rule from the list of rules for selecting identifiers of a mobile device; generating means for generating a unique identifier based on the local identifiers received from the fetching means; synchronization means for synchronizing the unique identifier received from the generating means with the unique identifiers generated earlier for related applications; registration means for registering a unique identifier received from the synchronization means.

A method for registering a unique identifier of a mobile device (hereinafter referred to as a unique identifier) at the request of at least two applications that communicate with each other (hereinafter referred to as related applications) running on a specified mobile device, the method comprising the steps that are implemented using the means of the described system where: upon application request, at least two identifiers of a mobile device (hereinafter, local identifiers) are selected based on a rule from a list of rules for selecting identifiers of a mobile device; generate a unique identifier based on the requested local identifiers; synchronize the unique identifier generated for the specified application with the unique identifiers generated earlier for related applications; register a unique identifier obtained as a result of synchronization.

The local identifier can be at least:

• IMEI;

• Serial ID;

• Android ID;

• WiFi Mac;

• Advertising ID.

In this case, the generated identifier is considered unique if the probability of coincidence of the generated identifiers on different mobile devices is below a predetermined threshold value. In a particular case, the unique identifier is generated based on the weighting factors predefined for each local identifier and characterizing the probability that the specified identifier will be the same on different mobile devices.

Fetching the local identifier can be performed after requesting access permission from the user. In a particular case, when synchronizing unique identifiers, a unique identifier is selected that was generated earlier than others. When you uninstall one of the applications, they can synchronize unique identifiers. If the unique identifier generated at the request of the application is the only one, the specified identifier is provided to all associated applications.

Brief Description of Drawings

FIG. 1 is a block diagram of a system for registering a unique identifier of a mobile device.

FIG. 2 is a block diagram of a method for registering a unique identifier of a mobile device.

FIG. 3 is an example of a general purpose computer system, personal computer or server.

Although the invention may take various modifications and alternative forms, the characteristic features shown by way of example in the drawings will be described in detail. It should be understood, however, that the purpose of the description is not to limit the invention to a specific embodiment. On the contrary, the purpose of the description is to cover all changes, modifications falling within the scope of this invention, as defined by the appended claims.

Description of embodiments of the invention

The objects and features of the present invention, methods for achieving these objects and features will become apparent by reference to exemplary embodiments. However, the present invention is not limited to the exemplary embodiments disclosed below, but may be embodied in various forms. The essence recited in the description is nothing more than the specific details necessary to assist a person skilled in the art in a thorough understanding of the invention, and the present invention is defined within the scope of the appended claims.

FIG. 1 is a block diagram of a system for registering a unique identifier of a mobile device.

The block diagram of the registration system of a unique identifier of a mobile device consists of applications 101, a selection tool 110, a list of identifier selection rules 111, a generating tool 120, a synchronization tool 130, a registration tool 140, a database of unique identifiers 141.

Registration of a unique identifier of a mobile device (hereinafter referred to as a unique identifier) in the database of unique identifiers 141 is performed at the request of at least two applications 101 that exchange data with each other (hereinafter referred to as related applications) running on the specified mobile device.

The selector 110 is designed to select, upon request of the application 101, at least two identifiers of the mobile device (hereinafter, local identifiers) based on a rule from the list of rules for identifying identifiers of the mobile device 111.

In one embodiment of the system, at least the following acts as a local identifier (depending on the mobile device and the operating system installed on it):

• IMEI;

• Serial ID;

• Android ID;

• WiFi Mac;

• Advertising ID.

For example, for a mobile device running Android 3, 4 and 5, the first local identifier available from IMEI, Serial ID, Android ID and WiFi Mac is selected, which is not a stub.

In another example, for a mobile device running Android 6 and 7, the first local identifier available from Serial ID, Android ID, and WiFi Mac is selected, which is not a stub.

In another example, for a mobile device running Android 8 and older, the Advertising ID is selected if this identifier is available on the mobile device, otherwise:

• if this is the first run of the picker 110, the picker 110 requests the Read_Phone_State permission and picks the first available ID from IMEI, Serial ID, Android ID, and WiFi Mac that is not a stub;

• if the finder 110 is restarted, the finder 110 selects an Android ID that will be unique for each application 101.

The generating means 120 is designed to generate a unique identifier based on the local identifiers received from the fetching means 110.

In one embodiment of the system, the generated identifier is considered unique if the probability of coincidence of the generated identifiers on different mobile devices is below a predetermined threshold value.

In yet another embodiment of the system, a unique identifier is generated based on weights predetermined for each local identifier and characterizing the likelihood that the specified identifier will be the same on different mobile devices.

In another embodiment of the system, the local identifier is retrieved after requesting access permission from the user.

For example, a convolution from a local identifier, for example, SHA256, is selected as a unique identifier.

In yet another example, the method for generating the unique identifier depends on the conditions under which the unique identifier is generated. Therefore, each application 101 regularly checks the relevance of the unique identifier. If during the check it is found that the unique identifier has lost its relevance, then the application 101 must re-submit a request to the selector 110, which will be used to generate a unique identifier and then register it in the database of unique identifiers 141.

The synchronization means 130 is designed to synchronize the unique identifier received from the generating means 120 with the unique identifiers generated earlier for related applications 101.

In one embodiment of the system, when synchronizing unique identifiers, a unique identifier generated earlier than others is selected.

In yet another embodiment of the system, when one of the applications 101 is removed, the unique identifiers are synchronized.

In another embodiment of the system, if the unique identifier generated at the request of the application 101 is the only one, the specified identifier is provided to all associated applications.

In another embodiment of the system, unique identifiers are synchronized if the generated unique identifier is deemed irrelevant, while the unique identifier is deemed irrelevant at least if:

• the unique identifier was generated based on the non-highest priority local identifier due to the unavailability of the specified local identifier, but the selector 110 determined during operation that the local identifier became available;

For example, this situation will occur if the Serial ID was used to form a unique identifier on a mobile device running Android 4, and not IMEI, because the mobile device was switched to an offline mode (English Airplane mode);

• Application 101 was updated from the version on which the identifier was generated according to the outdated algorithm;

• Application 101 determines that the value of the local identifier has changed, on the basis of which the unique identifier was generated.

The registration tool 140 is designed to register in the database of unique identifiers 141 the unique identifier received from the synchronization tool 130.

FIG. 2 is a block diagram of a method for registering a unique identifier of a mobile device.

The block diagram of a method for registering a unique identifier of a mobile device comprises step 210, in which local identifiers of the mobile device are selected, step 220, in which a unique identifier is generated, step 230, in which unique identifiers are synchronized, step 240, in which a unique identifier is registered.

At step 210, at the request of the application 101 using the selector 110, at least two identifiers of the mobile device (hereinafter, local identifiers) are selected based on a rule from the list of rules for selecting identifiers of the mobile device 111.

At step 220, using the generating means 120, a unique identifier is generated based on the local identifiers requested at step 210.

At step 230, using the synchronization tool 130, the unique identifier generated at step 220 for the specified application 101 is synchronized with the unique identifiers generated earlier for related applications.

At step 240, the registration means 140 registers in the unique identifier database 141 the unique identifier obtained as a result of synchronization at step 230.

3 shows an example of a general-purpose computer system, a personal computer or server 20, comprising a central processing unit 21, a system memory 22, and a system bus 23 that contains various system components, including memory associated with the central processing unit 21. The system bus 23 is implemented as any bus structure known from the prior art, containing in turn a bus memory or a bus memory controller, a peripheral bus and a local bus that is capable of interfacing with any other bus architecture. System memory contains read-only memory (ROM) 24, random access memory (RAM) 25. The main input / output system (BIOS) 26 contains basic procedures that transfer information between the elements of the personal computer 20, for example, at the time of loading the operating room. systems using ROM 24.

The personal computer 20, in turn, contains a hard disk 27 for reading and writing data, a magnetic disk drive 28 for reading and writing to removable magnetic disks 29 and an optical drive 30 for reading and writing to removable optical disks 31, such as CD-ROM, DVD -ROM and other optical media. The hard disk 27, the magnetic disk drive 28, and the optical drive 30 are connected to the system bus 23 through the hard disk interface 32, the magnetic disk interface 33, and the optical drive interface 34, respectively. Drives and corresponding computer storage media are non-volatile storage media for computer instructions, data structures, program modules and other data of a personal computer 20.

The present description discloses an implementation of a system that uses a hard disk 27, a removable magnetic disk 29 and a removable optical disk 31, but it should be understood that other types of computer storage media 56 are possible that are capable of storing data in a computer readable form (solid state drives, flash memory cards, digital disks, random access memory (RAM), etc.), which are connected to the system bus 23 through the controller 55.

Computer 20 has a file system 36, where the recorded operating system 35 is stored, as well as additional software applications 37, other program modules 38 and program data 39. The user has the ability to enter commands and information into the personal computer 20 through input devices (keyboard 40, manipulator " mouse "42). Other input devices may be used (not shown): microphone, joystick, game console, scanner, etc. Such input devices are conventionally connected to the computer system 20 through a serial port 46, which in turn is connected to the system bus, but can be connected in another way, for example, using a parallel port, a game port, or a universal serial bus (USB). A monitor 47 or other type of display device is also connected to the system bus 23 via an interface such as a video adapter 48. In addition to the monitor 47, the personal computer may be equipped with other peripheral output devices (not displayed), such as speakers, a printer, etc. ...

The personal computer 20 is capable of operating in a networked environment using a network connection with other or more remote computers 49. The remote computer (or computers) 49 are the same personal computers or servers that have most or all of the elements mentioned earlier in the description of the entity. the personal computer 20 shown in FIG. 3. In a computer network, there may also be other devices, such as routers, network stations, peer-to-peer devices, or other network nodes.

Network connections can form a local area network (LAN) 50 and a wide area network (WAN). Such networks are used in corporate computer networks, internal networks of companies and, as a rule, have access to the Internet. In LAN or WAN networks, personal computer 20 is connected to local network 50 via a network adapter or network interface 51. When using networks, personal computer 20 may use a modem 54 or other means of providing communication with a wide area network, such as the Internet. Modem 54, which is an internal or external device, is connected to the system bus 23 via a serial port 46. It should be noted that the network connections are only exemplary and are not required to reflect the exact configuration of the network, i. E. in fact, there are other ways of establishing a connection by technical means of communication of one computer with another.

In conclusion, it should be noted that the information given in the description are examples, which do not limit the scope of the present invention defined by the claims.

Claims (30)

1. A system for registering a unique identifier of a mobile device (hereinafter referred to as a unique identifier) at the request of at least two applications that exchange data with each other (hereinafter referred to as related applications) running on the specified mobile device, which contains: a) selection means for selecting at least two identifiers of a mobile device (hereinafter, local identifiers) on the basis of a rule from a list of rules for selecting identifiers of a mobile device; b) generating means for generating a unique identifier based on the local identifiers received from the fetching means, where the unique identifier is represented in the form of a convolution from the priority local identifier; c) synchronization means for synchronizing the unique identifier received from the generating means with unique identifiers generated earlier for related applications, where during synchronization a single unique identifier is determined that is provided to all related applications; d) registration tool designed to register the unique identifier received from the synchronization tool in the unique identifier database. 2. The system according to claim 1, according to which at least: • IMEI; • Serial ID; • Android ID; • WiFi Mac; • Advertising ID. 3. The system according to claim 1, in which the generated identifier is considered to be unique if the probability of coincidence of the generated identifiers on different mobile devices is below a predetermined threshold value. 4. The system according to PP. 2 and 3, in which the unique identifier is generated based on weights predetermined for each local identifier and characterizing the likelihood that the identifier will be the same on different mobile devices. 5. The system of claim. 1, in which the selection of the local identifier is carried out after requesting access permission from the user. 6. The system of claim. 1, in which when synchronizing unique identifiers select a unique identifier generated earlier than others. 7. A method for registering a unique identifier of a mobile device (hereinafter referred to as a unique identifier) at the request of at least two applications that communicate with each other (hereinafter referred to as related applications) running on the specified mobile device, the method comprising the steps that are implemented using the means from the system according to claim 1 and on which: a) at the request of the application, at least two identifiers of the mobile device (hereinafter, local identifiers) are selected based on a rule from the list of rules for selecting identifiers of a mobile device; b) based on the requested local identifiers, a unique identifier is formed, where the unique identifier is presented in the form of a convolution from the priority local identifier; c) synchronize the unique identifier generated for the specified application with the unique identifiers generated earlier for related applications, where during synchronization a single unique identifier is determined that is provided to all related applications; d) register a unique identifier obtained as a result of synchronization in the database of unique identifiers. 8. The method according to claim 7, according to which at least: • IMEI; • Serial ID; • Android ID; • WiFi Mac; • Advertising ID. 9. The method according to claim 7, according to which the generated identifier is considered unique if the probability of coincidence of the generated identifiers on different mobile devices is below a predetermined threshold value. 10. The method according to PP. 8 and 9, according to which the unique identifier is generated based on the weights predetermined for each local identifier and characterizing the likelihood that the specified identifier will be the same on different mobile devices. 11. The method according to claim 7, wherein the fetching of the local identifier is performed upon requesting the access permission from the user. 12. The method according to claim 7, according to which, when synchronizing unique identifiers, a unique identifier generated earlier than others is selected.

Images