CN114339729A

CN114339729A - Method and device for generating equipment identifier, electronic equipment and storage medium

Info

Publication number: CN114339729A
Application number: CN202011066133.0A
Authority: CN
Inventors: 祝聪; 马旭涛; 李成亮; 张文; 邱爽
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2022-04-12

Abstract

One or more embodiments of the present specification provide a method and an apparatus for generating a device identifier, an electronic device, and a storage medium; the method can comprise the following steps: acquiring attribute data pairs of a plurality of devices, wherein each attribute data pair is related to at least one application client program on corresponding device, and the attribute data pair related to any client program comprises a client identification corresponding to any client program on the device to which the client program belongs and device state information of the device to which the client program belongs; establishing an association relation between attribute data pairs meeting association relation establishment conditions so as to divide client identifications contained in the attribute data pairs with the association relation into the same set; and respectively generating corresponding equipment identifications aiming at each set obtained by division.

Description

Method and device for generating equipment identifier, electronic equipment and storage medium

Technical Field

One or more embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a method and an apparatus for generating a device identifier, an electronic device, and a storage medium.

Background

The device id (identity document) serves as a unique identifier of the device, and is used for indicating the identity of the device and thus distinguishing the device from other devices. In the related art, hardware information of a device can be generally employed as a device id; such as the MAC address, serial number, etc. of the device.

However, for privacy protection, there may be situations where hardware information cannot be obtained, making it difficult to accurately distinguish between different devices.

Disclosure of Invention

In view of this, one or more embodiments of the present specification provide a method and an apparatus for generating a device identifier, an electronic device, and a storage medium.

To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

according to a first aspect of one or more embodiments of the present specification, there is provided a method for generating a device identifier, including:

acquiring attribute data pairs of a plurality of devices, wherein each attribute data pair is related to at least one application client program on corresponding device, and the attribute data pair related to any client program comprises a client identification corresponding to any client program on the device to which the client program belongs and device state information of the device to which the client program belongs;

establishing an association relation between attribute data pairs meeting association relation establishment conditions so as to divide client identifications contained in the attribute data pairs with the association relation into the same set;

and respectively generating corresponding equipment identifications aiming at each set obtained by division.

According to a second aspect of one or more embodiments of the present specification, there is provided a method for generating a device identifier, including:

acquiring attribute data pairs related to at least one client program of application on equipment, wherein the attribute data pairs related to any client program comprise a client identifier corresponding to any client program on the equipment and equipment state information of the equipment;

sending the obtained attribute data pairs to a server, so that after the server obtains the attribute data pairs respectively uploaded by the equipment and other equipment, an association relation is established between the attribute data pairs meeting association relation establishment conditions, and client identifiers contained in the attribute data pairs with the association relation are divided into the same set;

and receiving the device identification generated by the server aiming at the set to which the client identification of the client program on the device belongs, and distributing the received device identification to the client program on the device.

According to a third aspect of one or more embodiments of the present specification, a data sharing method is provided, which is applied to a first service end corresponding to a first application; the method comprises the following steps:

receiving target data uploaded by a first client program of a first application, wherein the target data comprises a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server through establishing an association relation between attribute data pairs meeting an association relation establishment condition, the attribute data pairs are related to the device to which the first client program belongs and at least one client program of application on other devices, the attribute data pairs related to any client program comprise a client identifier corresponding to the client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers contained in the attribute data pairs with the association relation are divided into the same set, and each set obtained through division respectively has a corresponding device identifier;

and sharing the target data to a second server corresponding to a second application, so that the second server obtains associated data corresponding to the target data, and sends the associated data to a second client program, wherein the second client program is the client program corresponding to the client identifier in the set to which the device identifier contained in the target data belongs.

According to a fourth aspect of one or more embodiments of the present specification, a data sharing method is provided, which is applied to a second server corresponding to a second application; the method comprises the following steps:

receiving target data uploaded by a first client program of a first application and shared by a first server corresponding to the first application, wherein the target data comprises a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server through establishing an association relation between attribute data pairs meeting an association relation establishment condition, the attribute data pairs are related to the device to which the first client program belongs and at least one client program of an application on other devices, the attribute data pairs related to any client program comprise the client identifier corresponding to any client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers contained in the attribute data pairs with the association relation are divided into the same set, and each set obtained through division respectively has a corresponding device identifier;

and acquiring associated data corresponding to the target data, and sending the associated data to a second client program, wherein the second client program is a client program corresponding to the client identifier in the set to which the device identifier contained in the target data belongs.

According to a fifth aspect of one or more embodiments of the present specification, there is provided an apparatus for generating a device identifier, including:

the attribute data acquisition unit is used for acquiring attribute data pairs uploaded by a plurality of devices, each attribute data pair is related to at least one application client program on corresponding device, and the attribute data pair related to any client program comprises a client identification corresponding to any client program on the device to which the client program belongs and device state information of the device to which the client program belongs;

the dividing unit is used for establishing an association relationship between the attribute data pairs meeting the association relationship establishing condition so as to divide the client identifications contained in the attribute data pairs with the association relationship into the same set;

and the identifier generation unit is used for respectively generating corresponding equipment identifiers for each set obtained by division.

According to a sixth aspect of one or more embodiments of the present specification, there is provided an apparatus for generating a device identifier, including:

the attribute data acquisition unit is used for acquiring an attribute data pair related to at least one client program applied to the equipment, wherein the attribute data pair related to any client program comprises a client identifier corresponding to any client program on the equipment and equipment state information of the equipment;

the attribute data sending unit is used for sending the obtained attribute data pairs to the server, so that after the server obtains the attribute data pairs respectively uploaded by the equipment and other equipment, an association relationship is established between the attribute data pairs meeting association relationship establishment conditions, and client identifiers contained in the attribute data pairs with the association relationship are divided into the same set;

and the receiving unit is used for receiving the device identification generated by the server aiming at the set to which the client identification of the client program on the device belongs, and distributing the received device identification to the client program on the device.

According to a seventh aspect of one or more embodiments of the present specification, a data sharing apparatus is provided, which is applied to a first service end corresponding to a first application; the device comprises:

the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving target data uploaded by a first client program of a first application, the target data comprises a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server through establishing an association relation between attribute data pairs meeting an association relation establishment condition, the attribute data pairs are related to the device to which the first client program belongs and client programs of at least one application on other devices, the attribute data pairs related to any client program comprise the client identifier corresponding to the any client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers contained in the attribute data pairs with the association relation are divided into the same set, and each set obtained through division respectively has a corresponding device identifier;

and the sharing unit is used for sharing the target data to a second server corresponding to a second application so that the second server acquires associated data corresponding to the target data and sends the associated data to a second client program, wherein the second client program is the client program corresponding to the client identifier in the set to which the device identifier contained in the target data belongs.

According to an eighth aspect of one or more embodiments of the present specification, a data sharing apparatus is provided, which is applied to a second server corresponding to a second application; the device comprises:

the device comprises a receiving unit, a first application and a second application, wherein the receiving unit is used for receiving target data which is shared by a first server corresponding to the first application and is uploaded by a first client program of the first application, the target data comprises a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server through establishing an association relation between an attribute data pair meeting an association relation establishment condition, the attribute data pair is related to the device to which the first client program belongs and at least one client program of an application on other devices, the attribute data pair related to any client program comprises the client identifier corresponding to the client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers contained in the attribute data pair with the association relation are divided into the same set, and each set obtained through division respectively has a corresponding device identifier;

and the acquisition unit is used for acquiring the associated data corresponding to the target data and sending the associated data to a second client program, wherein the second client program is a client program corresponding to the client identifier in the set to which the equipment identifier contained in the target data belongs.

According to a ninth aspect of one or more embodiments herein, there is provided an electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method as in any of the above embodiments by executing the executable instructions.

According to a tenth aspect of one or more embodiments of the present description, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method as described in any of the above embodiments.

Drawings

Fig. 1 is an architecture diagram of a system for generating a device identifier according to an exemplary embodiment.

Fig. 2 is a flowchart of a method for generating a device identifier according to an exemplary embodiment.

FIG. 3 is a flow chart of a set partitioning method provided by an exemplary embodiment.

FIG. 4 is a flow chart of another set partitioning method provided by an exemplary embodiment.

Fig. 5A-5B are diagrams of a partition set provided by an exemplary embodiment.

Fig. 6 is a flowchart of another method for generating a device identifier according to an exemplary embodiment.

Fig. 7 is an architecture diagram of a data sharing system according to an exemplary embodiment.

Fig. 8 is a flowchart of a data sharing method according to an exemplary embodiment.

FIG. 9 is an interaction diagram of a method for data sharing in accordance with an illustrative embodiment.

FIG. 10 is a flow chart of another method for sharing data provided by an exemplary embodiment.

Fig. 11 is a schematic diagram of an apparatus according to an exemplary embodiment.

Fig. 12 is a block diagram of an apparatus for generating a device identifier according to an exemplary embodiment.

Fig. 13 is a block diagram of another apparatus for generating a device identifier according to an exemplary embodiment.

Fig. 14 is a schematic structural diagram of another apparatus provided in an exemplary embodiment.

Fig. 15 is a block diagram of a data sharing apparatus according to an example embodiment.

Fig. 16 is a block diagram of another data sharing apparatus provided in an example embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.

Fig. 1 is an architecture diagram of a system for generating a device identifier according to an exemplary embodiment. As shown in fig. 1, the system may include a number of electronic devices, such as a server 11, handsets 12-14, and a network 15.

The server 11 may be a physical server comprising a separate host, or the server 11 may be a virtual server carried by a cluster of hosts. In one or more embodiments of the present disclosure, the server 11 may cooperate with the client programs running on the mobile phones 12 to 14 to generate corresponding device identifiers for the mobile phones 12 to 14, respectively.

Handsets 12-14 are just one type of electronic device that a user may use. In fact, it is obvious that the user can also use electronic devices of the type such as: tablet devices, notebook computers, Personal Digital Assistants (PDAs), wearable devices (e.g., smart glasses, smart watches, etc.), etc., which are not limited by one or more embodiments of the present disclosure. In the operation process, the electronic equipment can operate one or more client programs of the application to realize the related service functions of the application; that is, at least one client program is installed on the electronic devices such as the handsets 12-14.

And the network 15 for interaction between the handsets 12-14 and the server 11 may comprise various types of wired or wireless networks. In one embodiment, the Network 15 may include the Public Switched Telephone Network (PSTN) and the Internet. A long connection may be established between the server 11 and the handsets 12-14 over the network 15 so that data may be transmitted between the server 11 and the handsets 12-14 over the long connection.

The service provider of the application develops a corresponding client program for its own application, and the device can use the corresponding function by installing and running the client program. Wherein the device has installed thereon a client program of at least one application.

The device id serves as a unique identification of the device, indicating the identity of the device and thus being distinguishable from other devices. Taking a smart phone as an example, for a Mobile phone with an android system, a unique hardware address such as an MAC address and an IMEI (International Mobile Equipment Identity, i.e., a Mobile phone serial number) can be used as a device id; for a handset with an IOS system, IDFA (Identifier For advertisement Identifier) can be used as the device id.

However, due to the permission control of the operating system on the device privacy, the client program on the device may not have the permission to read the device hardware address, or requires the authorization of the operating system, so that the client program cannot add the device id to the generated data, and the receiver of the data cannot identify the device source of the data. Moreover, a plurality of client programs of different applications can be installed on the device, and data generated by the client programs are actually associated with the device, and since the device id cannot be acquired, data generated by each client program on the device cannot be associated, so that the management efficiency of data is low, and the data utilization rate is low.

Accordingly, the present specification provides a device identifier generation scheme that, when at least one client program of an application is installed on each device, generates a corresponding device identifier for each device, and can assign the device identifier to the client program on the corresponding device.

Referring to fig. 2, fig. 2 is a flowchart illustrating a method for generating a device identifier according to an exemplary embodiment. As shown in fig. 2, the method applied to the server may include the following steps:

step 202, obtaining attribute data pairs of multiple devices, where each attribute data pair is related to at least one application client program on a corresponding device, and the attribute data pair related to any client program includes a client identifier corresponding to the client program on the device to which the client program belongs and device state information of the device to which the client program belongs.

In this embodiment, the client programs on the devices may generate attribute data pairs and send the attribute data pairs to the server through the devices to which the client programs belong, so that the server groups the client programs based on the attribute data pairs to obtain sets, and the sets and the devices are in a one-to-one correspondence relationship, so that a device id may be generated for each set, and then the client programs in each set (installed on the same device) may share the device id.

For any client program, the attribute data pair generated by the client program contains the client identifier corresponding to the client program on the belonging device and the device state information of the belonging device. In other words, for the client identifier and the device status information in the same attribute data pair, an association exists between the client identifier and the device status information. Based on the characteristic of uniqueness of the identification, the client identifications of the client programs of the same application on different devices are different, and the client identifications of the client programs of different applications on the same device are also different.

For example, the client identifications of the client programs of the respective applications on the devices 00-03 are shown in table 1:

device	Client identification
		Device 00	Application a: APP 1; application b: APP2
Device 01	Application a: APP 3; application b: APP 4; application c: APP5
		Device 02	Application a: APP 6; application b: APP7
Device 03	Application a: APP8
		……	……

TABLE 1

It should be noted that, when actually selecting a parameter as a client identifier, the parameter may be flexibly selected according to an operating system installed on the device, as long as the requirement for the client identifier is met, which is not limited in this specification.

The device state information indicates the device state of the device, and all client programs on each device share the same device state information, while the device state information of different devices at the same time is different from each other.

By way of example, the device status information may include a network address of the device and/or location information of the device. For example, the network address may be a logical address of the device, i.e., an IP address. In one case, an IPv6(Internet Protocol Version 6, Version 6 of the Internet Protocol) address of the device may be employed as the device status information. The number of network address resources of IPv6 is huge, and in a network environment adopting IPv6, each device can be assigned IPv6 addresses that are different from each other, and a client program on each device communicates using the IPv6 address of the device to which it belongs. In another case, location information of the device may be employed as the device status information. For example, GPS (Global Positioning System) data of the device, data of the beidou satellite navigation System, data of the galileo Positioning System, and the like are used. Since different devices are usually located at different spatial locations, the location information of each device is distinguished from each other at the same time, and all client programs on each device share the location information of the device. In yet another case, device status information may also be generated based on both the network address and location information of the device. For example, the network address and the location information are spliced, and then hash calculation is performed on the spliced data, so that the calculated hash value is used as the device state information. Of course, any other device parameters meeting the above requirement for the device status information may also be used, and this specification does not limit this.

And step 204, establishing an association relationship between the attribute data pairs meeting the association relationship establishing condition so as to divide the client identifications contained in the attribute data pairs with the association relationship into the same set.

In this embodiment, based on the above-mentioned characteristics of the device status information, the client programs may be grouped according to whether the attribute data pairs have the same device status information, that is, the association relationship establishing condition may include having the same device status information. Specifically, the attribute data pairs satisfying the association relationship establishment condition may establish an association relationship, so that the client identifiers included in the attribute data pairs having an association relationship are divided into the same set. By the above-mentioned manner of dividing the sets based on the device state information, the client programs having the same device state can be divided into the same set, and the client programs having the same device state are all installed on the same device, so that the one-to-one correspondence relationship between the sets and the devices can be realized. Then, corresponding device identifiers may be generated for the respective sets, and the generated device identifiers may be configured to the client programs in the respective sets, respectively.

And step 206, respectively generating corresponding device identifiers for each set obtained by division.

In one case, all attribute data pairs uploaded by each device contain the same device status information for the corresponding device. In other words, the client program generates only one pair of attribute data pairs that contains the client identification and unique device state information. In this case, the association relationship establishment conditions may include having the same device state information. In another case, the attribute data uploaded by the portion of the device may relate to multiple device state information for the device based on the "transient" nature of the device state information. For "transient" understanding, for example, all client programs on a device share the same network address, but the network address is exclusively owned by the device for a certain period of time, and other periods of time are switched to other devices; as another example, a device is at location a for a certain period of time, and when the device is carried by a user to another area, location a may be monopolized by other devices. In other words, "transient" can mean that the state is shared by all client programs on the device, and only one device monopolizes the state for a certain period of time.

Further, in order to further improve the accuracy of the partition set in the case that the attribute data uploaded by the at least one device is paired with the plurality of device state information related to the at least one device, the association relationship establishing condition may further include a client identifier having the same value, that is, the client identifier is also used as a basis for partitioning the client program; in other words, the association relationship establishment conditions include having the same device state information or having the same client identification.

Based on the originally existing association relationship between the client identifier and the device status information included in the attribute data pair, the association relationship is further established for the attribute data pair according to a relationship establishment condition (having the same device status information or having the same client identifier). The process of partitioning the collection is described in detail below in conjunction with fig. 3-4.

Referring to fig. 3, fig. 3 is a flowchart illustrating a set partitioning method according to an exemplary embodiment. As shown in fig. 3, the method applied to the server may include the following steps:

step 302, reading each attribute data pair in sequence.

In this embodiment, after acquiring attribute data pairs uploaded by multiple devices, the server may sequentially read each attribute data pair to group client identifiers included in all attribute data pairs.

Step 304, if there is an association relationship between the currently read attribute data pair and any attribute data pair read previously, then go to step 306; otherwise, go to step 308.

Step 306, the client identifier in the current attribute data pair is divided into a set to which the client identifier in any attribute data pair belongs.

And step 308, dividing into a new set.

Step 310, if the division is finished, the step 312 is executed; otherwise, return to step 302.

Step 312, the division is ended.

For example, the client id is denoted by a1... an and the device status information is denoted by t1.. tn. Assume that the server receives the attribute data pairs as shown in table 2:

client program	Attribute data pair
		Client program 1	<a1，t1>
Client program 2	<a2，t1、t2>
		Client program 3	<a3，t2>
Client program 4	<a4，t3>
		Client program 5	<a5，t3>

TABLE 2

The server first reads the attribute data pair < a1, t1> generated by the client program 1, and can divide a1 into a set x. Then, the reading of the attribute data pair < a1, t1, t2> generated by the client program 2 is continued, and it can be seen that the attribute data pair < a1, t1, t2> relates to the device state t1 and the device state t2 (i.e., the device states at different times). Since t1 in the attribute data pair is the same as the device state information t1 in the attribute data pair < a1, t1>, it can be determined that the attribute data pair < a1, t1, t2> has an association relationship with the attribute data pair < a1, t1>, that is, the association relationship is established between the attribute data pair and the attribute data pair < a1, t1 >. At this time, there is an association relationship among a1, a2, t1 and t2, and a2 can be divided into sets x.

Further, the attribute data pair < a3, t2> generated by the client program 3 is continuously read, and since t2 in the attribute data pair is the same as the device state information t2 in the attribute data pair < a2, t1, t2>, it can be determined that the attribute data pair < a3, t2> has an association relationship with the attribute data pair < a2, t1, t2 >. At this time, there is an association relationship among a1, a2, a3, t1 and t2, and a3 can be divided into a set x.

Similarly, it can be determined that the attribute data pair < a4, t3> has an association relationship with the attribute data pair < a5, t3 >. At this time, there is an association relationship among a4, a5 and t3, and a set y can be newly created, so that a4 and a5 are divided into the set y.

In summary, a1-a3 is divided into set x and a4-a5 is divided into set y. Then, device id-d 1 may be generated for set x and device id-d 2 may be generated for set y. When generating the device id, the uniqueness of the device id needs to be ensured, and the algorithm for generating the device id may refer to the records in the related art, which is not described herein again.

Referring to fig. 4, fig. 4 is a flowchart illustrating another set partitioning method according to an exemplary embodiment. As shown in fig. 4, the method applied to the server may include the following steps:

and step 402, aggregating the attribute data pairs to obtain an undirected graph.

In this embodiment, the specific process of polymerization may be: and taking the client identifier and the equipment state information as the vertex of the undirected graph, and taking the incidence relation between the client identifier and the equipment state information as the edge of the undirected graph. That is, the association between the client identity and the device state information is embodied by the edges of the undirected graph (embodying the connectivity between the vertices).

Step 404, determining a maximal connected subgraph of the undirected graph.

At step 406, a device id is assigned to each maximal connected subgraph.

In this embodiment, the client identifiers belonging to the same maximal connected subgraph are divided into the same set.

Taking the example shown in table 2 above, the following describes a process of assigning device ids based on undirected graphs with reference to fig. 5A to 5B.

As shown in fig. 5A, based on the acquired attribute data pair, the following relationship pair is obtained: a 1-t 1, a 2-t 1, a 2-t 2, a 3-t 2, a 4-t 3 and a 5-t 3. Further, in the above aggregation manner, an undirected graph as shown in fig. 5B can be obtained. In this undirected graph, a very large connected subgraph 51 and a very large connected subgraph 52 are included. Therefore, a1-a3 contained in the maximum connectivity subgraph 51 can be divided into the set x, and a4-a5 contained in the maximum connectivity subgraph 52 can be divided into the set y. Similarly, a device id-d 1 may be generated for set x and a device id-d 2 may be generated for set y. It should be noted that, the algorithm for solving the maximally connected subgraph of the undirected graph can be flexibly selected according to actual requirements, and the description does not limit this. For example, depth-first traversal, breadth-first traversal, and cross-reference algorithms may be used.

In the device identifier generation scheme of the present specification, in addition to the above-mentioned attribute data pair, a device id may be generated in a compatible manner, for example, some client programs on the device have a right to acquire the hardware identifier information of the device to which the client programs belong. Specifically, the server may obtain hardware data pairs uploaded by multiple devices, and similarly, each hardware data pair is generated by at least one client program of an application on a corresponding device, and a hardware data pair generated by any client program includes a corresponding client identifier and hardware identification information of the device to which the client program belongs. Based on the hardware identification information of the device acquired by the client program, the server can divide the client identifications with the same corresponding hardware identification information into the same set.

For example, the server acquires the hardware data pairs < a6, h1>, < a7, h1>, < a8, and h2 >; wherein h1.. Then the server may partition a6 into the same set and a8 into another set.

The server can send the generated device identifier to the client program corresponding to the client identifier in the corresponding set, so that the target data sent by the client program to the receiver contains the device identifier of the client program. Based on the device identifier included in the target data, the receiving side can determine from which device the target data comes from according to the device identifier included in the target data. Therefore, under the condition that the equipment is provided with a plurality of client programs with different applications, the client programs can associate the data generated by all the client programs on the same equipment with the equipment by adding the equipment identifiers in the generated data, so that the management efficiency and the data utilization rate of the data are improved.

Corresponding to the above-mentioned server-side embodiment, this specification also proposes an apparatus-side embodiment, and the description related to the server-side embodiment may also be applied to the apparatus-side embodiment, which is not described again in the following.

Accordingly, referring to fig. 6, fig. 6 is a flowchart of another method for generating a device identifier according to an exemplary embodiment. As shown in fig. 6, the method applied to the device may include the following steps:

step 602, obtaining an attribute data pair related to a client program of at least one application on a device, where the attribute data pair related to any client program includes a client identifier corresponding to the client program on the device and device state information of the device.

Step 604, sending the obtained attribute data pairs to a server, so that after obtaining the attribute data pairs respectively uploaded by the device and other devices, the server establishes an association relationship between the attribute data pairs meeting the association relationship establishment condition, so that the client identifiers included in the attribute data pairs having an association relationship are divided into the same set.

Step 606, receiving the device identifier generated by the server for the set to which the client identifier of the client program on the device belongs, and allocating the received device identifier to the client program on the device.

As described above, target data generated by a client program on the device may be obtained, where the target data includes a device identifier assigned to the client program on the device; and then, sending the target data to a receiver so that the receiver judges that the target data come from the equipment according to the equipment identification contained in the target data.

In the technical solution of this specification, a server allocates a device identifier of a device to which a client program belongs, and when the client program sends target data to a data receiving side, the client program can add the device identifier to the target data, so that the receiving side can determine from which device the target data comes according to the device identifier included in the target data, and further can associate and share data generated by all client programs on the same device with the device. This is explained below with reference to fig. 7-10.

Fig. 7 is an architecture diagram of a data sharing system according to an exemplary embodiment. As shown in fig. 7, the system may include several servers (e.g., server 71, server 72, etc.), devices 73, and a network 74. The device 73 is respectively installed with client programs of a first application and a second application, the server 71 serves as a first server of the first application, and the server 72 serves as a second server of the second application.

Based on the above system architecture, please refer to fig. 8, fig. 8 is a flowchart of a data sharing method according to an exemplary embodiment. As shown in fig. 8, the method applied to the first service end corresponding to the first application may include the following steps:

step 802, receiving target data uploaded by a first client program of a first application, where the target data includes a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server by establishing an association relationship between attribute data pairs satisfying an association relationship establishment condition, the attribute data pairs are related to the device to which the first client program belongs and a client program of at least one application on another device, an attribute data pair related to any client program includes a client identifier corresponding to the any client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers included in the attribute data pairs having the association relationship are divided into the same set, and each set obtained by the division has a corresponding device identifier.

In this embodiment, the process of generating the device identifier may refer to the embodiments corresponding to fig. 1 to 6, which are not described herein again.

Step 804, the target data is shared to a second server corresponding to a second application, so that the second server obtains associated data corresponding to the target data, and sends the associated data to a second client program, where the second client program is a client program corresponding to a client identifier in a set to which the device identifier included in the target data belongs.

In this embodiment, when a first client program corresponding to a first application and a second client program corresponding to a second application are installed on a device at the same time, a user of the device generates data when using both the first client program and the second client program, and since the user is associated with the device, the data generated by both the first client program and the second client program is associated with the user. Thus, data generated by the first client program and the second client program may be associated by the device identification. For example, after the user generates the target data by using the first client program, the target data is shared to the second server. Then, when the user uses the second client program, the second server may return data to the second client program in combination with the target data, that is, obtain associated data corresponding to the target data, and further send the associated data to the second client program, so as to provide a better service to the user.

For example, the target data is a retrieval record of a user when using a first client program, through the data sharing process, the first server shares the retrieval record to a second server, and the second server can obtain a corresponding retrieval result based on the retrieval record, and then send the retrieval result to the second client program for the same user to view. For another example, the target data is a user purchase record, and the associated data is a commodity which is interested by the user; the target data is a dialogue record of the user and the customer service, and the associated data is potential business handling requirements of the user. As another example, the associated data may also be the target data itself, thereby enabling synchronization of data between different client programs on the same device. It should be noted that, when determining the associated data corresponding to the target data, the second server may determine the associated data together according to the data generated by the second client program, in addition to the target data itself. In other words, the specific implementation process for determining the associated data may be flexibly changed according to the application scenario, and this specification does not limit this.

For ease of understanding, the following detailed description is made in conjunction with application scenarios and interaction diagrams.

Referring to fig. 9, fig. 9 is an interaction diagram of a data sharing method according to an exemplary embodiment. As shown in fig. 9, the interactive process may include the following steps:

at step 902, APP1 generates user data.

In the present embodiment, the apparatus 73 is described by taking as an example the APP1 of the application a and the APP2 of the application b. The server of the application a is a server 1, and the server of the application b is a server 2. APP1 of application a provides search services to the user and APP2 of application b provides shopping services to the user. Then, when the user searches using APP1 on device 73, APP1 may generate user data, which may be the user's retrieved records, browsing records, and so forth. Meanwhile, the APP1 adds the device id of the device 73 to the user data.

In step 904, APP1 uploads user data to corresponding server 1.

Step 906, the server 1 shares the user data with the pre-accessed server 2.

In this embodiment, the server 1 and the server 2 complete access in advance, so that the server 1 and the server 2 can share data therebetween.

Step 908, the server 2 reads the device id.

Step 910, the server 2 determines the corresponding APP in the set to which it belongs.

As can be seen from the above process of generating device id, since APP1 and APP2 are both installed on device 73, the client program identifications of APP1 and APP2 are necessarily divided into the same set. Then, the server can determine the set corresponding to the device id included in the user data (the server that generates the device id can synchronize the divided set and the corresponding device id to each server), thereby determining other client programs installed on the device 73. Taking APP2 as an example in the present embodiment, the server 2 can determine the client identifier of the client program installed on the device 73 corresponding to application b, that is, the client identifier of APP 2.

In step 912, the server 2 generates user recommendation information.

The server 2 may generate the user recommendation information according to data such as a search record and a browsing record in the user data. For example, if the application b is used for providing shopping services for the user, a corresponding purchase recommendation list can be generated according to the retrieval record and the browsing record of the user on the APP1, and is issued to the APP2 to be displayed to the user, so that the operation of purchasing articles by the user on the APP2 is simplified.

In step 914, the server 2 sends the user recommendation information to the APP 2.

At step 916, the APP2 presents the user recommendation information.

Corresponding to the above embodiment of the first service end side, the present specification also proposes an embodiment of the second service end side, and the description related to the embodiment of the first service end side may also be applied to the embodiment of the second service end side, which is not described again in the following.

Accordingly, referring to fig. 10, fig. 10 is a flowchart of another data sharing method according to an exemplary embodiment. As shown in fig. 10, the method applied to a second server corresponding to a second application may include the following steps:

step 1002, receiving target data uploaded by a first client program of a first application, shared by a first server corresponding to the first application, where the target data includes a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server by establishing an association relationship between attribute data pairs satisfying an association relationship establishment condition, the attribute data pairs are related to the device to which the first client program belongs and a client program of at least one application on another device, the attribute data pairs related to any client program include a client identifier corresponding to the any client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers included in the attribute data pairs having an association relationship are divided into the same set, and each set obtained by the division has a corresponding device identifier.

Step 1004, obtaining the associated data corresponding to the target data, and sending the associated data to a second client program, where the second client program is a client program corresponding to the client identifier in the set to which the device identifier included in the target data belongs.

Corresponding to the above method embodiments, the present specification further provides an embodiment of an apparatus for generating a device identifier.

FIG. 11 is a schematic block diagram of an apparatus provided in an exemplary embodiment. Referring to fig. 11, at the hardware level, the apparatus includes a processor 1102, an internal bus 1104, a network interface 1106, a memory 1108, and a non-volatile storage 1110, although other hardware required for services may be included. The processor 1102 reads the corresponding computer program from the non-volatile memory 1110 into the memory 1108 and then runs the computer program, thereby forming a device identifier generating apparatus on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 12, in a software implementation, the apparatus for generating the device identifier may include:

an attribute data acquisition unit 1201 for acquiring attribute data pairs uploaded by a plurality of devices, each attribute data pair being related to at least one client program applied to a corresponding device, the attribute data pair related to any client program including a client identifier corresponding to the client program on the device to which the client program belongs and device status information of the device to which the client program belongs;

a dividing unit 1202, configured to establish an association relationship between attribute data pairs that satisfy an association relationship establishment condition, so as to divide client identifiers included in attribute data pairs having an association relationship into a same set;

the identifier generating unit 1203 generates corresponding device identifiers for each of the sets obtained by the division.

Alternatively to this, the first and second parts may,

under the condition that all attribute data pairs of each device contain the same device state information of the corresponding device, the association relationship establishment condition comprises the same device state information; alternatively, the first and second electrodes may be,

in the case where the attribute data pair of at least one device relates to a plurality of device status information of the at least one device, the association establishment condition includes having the same device status information or having the same client identification.

Optionally, the dividing unit 1202 is specifically configured to:

reading each attribute data pair in sequence;

if the incidence relation exists between the currently read attribute data pair and any previously read attribute data pair, dividing the client identifier in the current attribute data pair into a set to which the client identifier in any attribute data pair belongs.

Optionally, the dividing unit 1202 is specifically configured to:

aggregating all attribute data pairs to obtain an undirected graph; the client identification and the equipment state information are vertexes of the undirected graph, and the incidence relation between the client identification and the equipment state information is an edge of the undirected graph;

and determining the maximum connected subgraphs of the undirected graph, and dividing the client identifications belonging to the same maximum connected subgraph into the same set.

Optionally, all the client programs on each device share the same device state information, and the device state information of different devices at the same time is different from each other.

Optionally, the device status information includes:

network address of the device and/or location information of the device.

Optionally, the method further includes:

a hardware data obtaining unit 1204, configured to obtain hardware data pairs uploaded by multiple devices, where each hardware data pair is generated by at least one application client program on a corresponding device, and a hardware data pair generated by any client program includes a corresponding client identifier and hardware identifier information of the device to which the client program belongs;

the dividing unit 1202 is further configured to divide the client identifiers having the same hardware identification information into the same set.

Optionally, the method further includes:

sending unit 1205, sending the generated device identifier to the client program corresponding to the client identifier in the corresponding set, so that the target data sent by the client program to the receiving party includes the device identifier of the client program.

Referring to fig. 13, in another software implementation, the apparatus for generating a device identifier may include:

an attribute data obtaining unit 1301, configured to obtain an attribute data pair related to at least one client program applied to a device, where the attribute data pair related to any client program includes a client identifier corresponding to the client program on the device and device state information of the device;

an attribute data sending unit 1302, configured to send the obtained attribute data pairs to a server, so that after obtaining the attribute data pairs respectively uploaded by the device and other devices, the server establishes an association relationship between the attribute data pairs meeting an association relationship establishment condition, so that client identifiers included in the attribute data pairs having an association relationship are divided into a same set;

the receiving unit 1303 receives the device identifier generated by the server for the set to which the client identifier of the client program on the device belongs, and allocates the received device identifier to the client program on the device.

Optionally, the method further includes:

a target data obtaining unit 1304 configured to obtain target data generated by the client program on the device, where the target data includes a device identifier of the client program allocated to the device;

the target data sending unit 1305 sends the target data to the receiving side, so that the receiving side determines that the target data is from the device according to the device identifier included in the target data.

Fig. 14 is a schematic block diagram of another apparatus provided in an exemplary embodiment. Referring to FIG. 14, at the hardware level, the device includes a processor 1402, an internal bus 1404, a network interface 1406, a memory 1408, and a non-volatile storage 1410, although other hardware required for service may be included. The processor 1402 reads the corresponding computer program from the non-volatile memory 1410 into the memory 1408 and then runs, forming a data sharing device on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 15, in a software implementation, the data sharing apparatus applied to a first service end corresponding to a first application may include:

a receiving unit 1501, configured to receive target data uploaded by a first client program of a first application, where the target data includes a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server by establishing an association relationship between attribute data pairs that satisfy an association relationship establishment condition, the attribute data pairs are related to client programs of at least one application on the device to which the first client program belongs and other devices, an attribute data pair related to any client program includes a client identifier corresponding to the client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers included in the attribute data pairs having the association relationship are divided into the same set, and each set obtained by the division has a corresponding device identifier;

the sharing unit 1502 shares the target data with a second server corresponding to a second application, so that the second server obtains associated data corresponding to the target data, and sends the associated data to a second client program, where the second client program is a client program corresponding to a client identifier in a set to which the device identifier included in the target data belongs.

Referring to fig. 16, in another software implementation, the data sharing apparatus applied to a second server corresponding to a second application may include:

a receiving unit 1601, configured to receive target data uploaded by a first client program of a first application, where the target data is shared by a first server corresponding to the first application, where the target data includes a device identifier of a device to which the first client program belongs, the device identifier is obtained by a server through establishing an association relationship between an attribute data pair that satisfies an association relationship establishment condition, the attribute data pair is related to a device to which the first client program belongs and a client program of at least one application on another device, the attribute data pair related to any client program includes a client identifier corresponding to the client program on the device to which the client program belongs and device state information of the device to which the client program belongs, the client identifiers included in the attribute data pairs having an association relationship are divided into a same set, and each set obtained through division has a corresponding device identifier;

an obtaining unit 1602, obtaining associated data corresponding to the target data, and sending the associated data to a second client program, where the second client program is a client program corresponding to a client identifier in a set to which the device identifier included in the target data belongs.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims

1. A method for generating a device identifier, comprising:

2. The method of claim 1,

3. The method according to claim 1 or 2, wherein the dividing the client identifiers included in the attribute data pairs with association relationships into the same set comprises:

reading each attribute data pair in sequence;

4. The method according to claim 1 or 2, wherein the dividing the client identifiers included in the attribute data pairs with association relationships into the same set comprises:

5. The method of claim 1, wherein all client programs on each device share the same device state information, and wherein the device state information for different devices at the same time is distinguished from each other.

6. The method of claim 1, wherein the device state information comprises:

network address of the device and/or location information of the device.

7. The method of claim 1, further comprising:

acquiring hardware data pairs uploaded by a plurality of devices, wherein each hardware data pair is generated by at least one application client program on corresponding device, and the hardware data pair generated by any client program comprises corresponding client identification and hardware identification information of the device;

and dividing the client identifications with the same corresponding hardware identification information into the same set.

8. The method of claim 1, further comprising:

and sending the generated equipment identifier to the client program corresponding to the client identifier in the corresponding set, so that the target data sent to the receiver by the client program contains the equipment identifier of the client program.

9. A method for generating a device identifier, comprising:

10. The method of claim 9, further comprising:

acquiring target data generated by a client program on the equipment, wherein the target data comprises an equipment identifier of the client program distributed to the equipment;

and sending the target data to a receiver so that the receiver judges that the target data come from the equipment according to the equipment identification contained in the target data.

11. A data sharing method is characterized in that the method is applied to a first service end corresponding to a first application; the method comprises the following steps:

12. The data sharing method is characterized by being applied to a second server corresponding to a second application; the method comprises the following steps:

13. An apparatus for generating a device identifier, comprising:

14. An apparatus for generating a device identifier, comprising:

15. The data sharing device is applied to a first service end corresponding to a first application; the device comprises:

16. The data sharing device is applied to a second server corresponding to a second application; the device comprises:

17. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 1-12 by executing the executable instructions.

18. A computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 12.