Code issuance method and system

Abstract

The present application provides a code sending method, the method comprising: in response to a program initialization operation, obtaining target device information of a target user device; generating a local identification code according to the target device information; generating a code sending request, the code sending request including the target device information and the local identification code; sending the code sending request to a server so that the server returns a target identification code to the target user device according to the target device information, wherein the target identification code is the local identification code or the remote identification code; and upon receiving the target identification code, determining the target identification code as the identification code of the target user device. The technical solution provided by the present application can avoid multiple code sending, thereby ensuring the stability of user information, realizing effective management of the service background, and operations such as content push can also be inherited, thereby improving push accuracy.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a code issuing method, system, device and computer readable storage medium. Background Art

[0002] With the development of the Internet and computer technology, there are more and more users. For the convenience of management, the network platform needs to configure an identification code for each user for identification, such as through various encryption algorithms.

[0003] However, in the prior art, the same user may be configured with multiple identification codes at the same time, which makes it impossible to ensure the stability of user information, resulting in an inability to effectively manage it, and operations such as push based on the identification code will also be negatively affected. Summary of the invention

[0004] The purpose of this application is to provide a code issuance method, system, computer device and computer readable storage medium to solve the above problems.

[0005] A first aspect of an embodiment of the present application provides a code issuing method, including:

[0006] In response to the program initialization operation, obtaining target device information of the target user device;

[0007] Generate a local identification code according to the target device information;

[0008] Generate a code sending request, wherein the code sending request includes the target device information and the local identification code;

[0009] Sending the code sending request to a server so that the server returns a target identification code to the target user device according to the target device information, wherein the target identification code is the local identification code or the remote identification code, the local identification code is the identification code provided to the server by the target user device through the code sending request, and the remote identification code is the identification code stored in the server and associated with the target device information; and

[0010] In case of receiving the target identification code, the target identification code is determined as the identification code of the target user equipment.

[0011] Optionally, it also includes:

[0012] In response to the program initialization operation, querying the stored identification code in the target user device;

[0013] In the case where the stored identification code is found, the stored identification code is determined as the identification code of the target user equipment.

[0014] Optionally, the target device information includes sub-device information, and different sub-device information has different priorities; and generating a local identification code according to the target device information includes:

[0015] When a plurality of sub-device information is obtained, selecting the sub-device information with the highest priority from the plurality of sub-device information; and

[0016] The local identification code is generated according to the sub-device information with the highest priority.

[0017] Optionally, it also includes:

[0018] In response to the target identification code being the local identification code, sending the operation log carrying the local identification code to the service gateway;

[0019] In response to the target identification code being the remote identification code, the local identification code in the operation log is updated to the remote identification code to obtain an updated operation log, and the updated operation log is sent to the service gateway.

[0020] Optionally, it also includes:

[0021] Before receiving the target identification code returned by the server, sending the local identification code to the service gateway; and

[0022] After receiving the target identification code, in response to the target identification code being the remote identification code, a mapping relationship between the remote identification code and the local identification code is established, and the mapping relationship is notified to the service gateway so that the service gateway updates the identification code of the target user device stored therein according to the mapping relationship.

[0023] One aspect of an embodiment of the present application further provides a code issuing system, the system comprising:

[0024] An acquisition module, used for acquiring target device information of a target user device in response to a program initialization operation;

[0025] A first generating module, used to generate a local identification code according to the target device information;

[0026] A second generating module, configured to generate a code sending request, wherein the code sending request includes the target device information and the local identification code;

[0027] a sending module, configured to send the code sending request to a server, so that the server returns a target identification code to the target user device according to the target device information, wherein the target identification code is the local identification code or the remote identification code, the local identification code is the identification code provided to the server by the target user device through the code sending request, and the remote identification code is the identification code stored in the server and associated with the target device information; and

[0028] The determination module is configured to, upon receiving the target identification code, determine the target identification code as the identification code of the target user equipment.

[0029] One aspect of an embodiment of the present application further provides a code issuing method, the method comprising:

[0030] receiving a code sending request sent by a target user equipment, wherein the code sending request includes target equipment information and a local identification code, wherein the local identification code is generated by the target user equipment according to the target equipment information;

[0031] According to the target device information, querying a target remote identification code from an identification code mapping library, wherein the identification code mapping library is used to store mapping relationships between remote identification codes and device information, and the target remote identification code is a remote identification code associated with the target device information;

[0032] When the target remote identification code is found, returning the target remote identification code to the target user equipment; and

[0033] In the case that the target remote identification code is not found, the local identification code is returned to the target user equipment, and the local identification code and the target equipment information are updated in the identification code mapping library.

[0034] Optionally, the target device information includes sub-device information, and different sub-device information corresponds to different priorities; the querying of the target remote identification code from the identification code mapping library includes:

[0035] In the case where the target device information includes a plurality of sub-device information, a plurality of query conditions are determined according to the system version number of the target user device, each query condition being one of the plurality of sub-device information;

[0036] Querying the remote identification code matching each query condition from the identification code mapping library; and

[0037] When several query conditions among the multiple query conditions are matched to respective remote identification codes, the remote identification code matching the target query condition is determined as the target remote identification code; wherein the target query condition is the query condition with the highest priority among the several query conditions.

[0038] Optionally, in the case where the target remote identification code is queried, returning the target remote identification code to the target user equipment includes:

[0039] When the target remote identification code is different from the local identification code, obtaining a device model associated with the target remote identification code;

[0040] In a case where the device model associated with the target remote identification code is different from the device model of the target user device, the target remote identification code is returned to the target user device.

[0041] Optionally, it also includes:

[0042] The identification code mapping library is pre-established, the identification code mapping library includes a plurality of data, each data includes a remote identification code and device information mapped to the remote identification code, the device information includes attribute information and location information;

[0043] The identification code mapping library is updated according to each remote identification code, attribute information and / or location information of each remote identification code mapping.

[0044] Optionally, it also includes:

[0045] Storing incremental data in the identification code mapping library at preset time intervals;

[0046] If an abnormal identification code is detected in the incremental data, an abnormal identification is performed on the data corresponding to the abnormal identification code; wherein the abnormal identification is used to indicate that the abnormal identification code is logically deleted or cannot be returned to the user device.

[0047] Optionally, it also includes:

[0048] At preset time intervals, monitoring data of the multiple code rate is obtained, where the multiple code rate is the ratio of the number of newly added multiple code devices to the number of newly added devices.

[0049] One aspect of an embodiment of the present application further provides a code issuing system, including:

[0050] A receiving module, configured to receive a code sending request sent by a target user equipment, wherein the code sending request includes target equipment information and a local identification code, wherein the local identification code is generated by the target user equipment according to the target equipment information;

[0051] A query module, used to query a target remote identification code from an identification code mapping library according to the target device information, wherein the identification code mapping library is used to store mapping relationships between remote identification codes and device information, and the target remote identification code is a remote identification code associated with the target device information;

[0052] A first returning module, configured to return the target remote identification code to the target user equipment when the target remote identification code is found; and

[0053] The second returning module is used to return the local identification code to the target user equipment when the target remote identification code is not found, and to update the local identification code and the target equipment information into the identification code mapping library.

[0054] One aspect of an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is used to implement the steps of the above-mentioned code sending method when executing the computer program.

[0055] One aspect of an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. The computer program can be executed by at least one processor to enable the at least one processor to perform the steps of the above-mentioned code sending method.

[0056] The code issuance method, system, device, and computer-readable storage medium provided in the embodiments of the present application include the following advantages:

[0057] After the target user device generates a local identification code, it sends a code request to the server. The server determines whether the local identification code is a multiple-send code to determine whether to return a local identification code or a remote identification code. The target user device determines / updates its own identification code based on the returned local identification code or remote identification code to avoid multiple-send codes.

[0058] In view of the above, multiple codes are avoided, and there will not be multiple identification codes for the same user device, thereby ensuring the stability of user information and realizing effective management of the service background. Operations such as content push can also be inherited to improve push accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] Figure 1 The following schematically shows an environment architecture diagram according to an embodiment of the present application;

[0060] Figure 2 The flowchart of the code issuing method according to the first embodiment of the present application is schematically shown;

[0061] Figure 3 for Figure 2 Flow chart of sub-steps of step S202;

[0062] Figure 4 The following is a flow chart of the operation of the server after receiving a code sending request;

[0063] Figures 5 to 7 The newly added flow chart of the code issuing method according to the first embodiment of the present application is schematically shown;

[0064] Figure 8 The following is a schematic diagram showing an operation flow chart of an exemplary application of the code issuing method according to the first embodiment of the present application;

[0065] Fig. 9 The flowchart of the code issuing method according to the second embodiment of the present application is schematically shown;

[0066] Fig.10 A block diagram schematically shows a method for sending codes according to Embodiment 3 of the present application;

[0067] Fig.11 A block diagram schematically shows a method for sending codes according to a fourth embodiment of the present application; and

[0068] Fig.12 The following schematically shows a hardware architecture diagram of a computer device suitable for implementing a code issuing method according to Embodiment 5 of the present application. DETAILED DESCRIPTION

[0069] In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0070] It should be noted that the descriptions of "first", "second", "third", etc. in this application are only for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in this field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0071] In the description of the present application, it should be understood that the numerical labels before the steps do not indicate the order in which the steps are executed, but are only used to facilitate the description of the present application and to distinguish each step, and therefore should not be understood as a limitation on the present application.

[0072] The following is an explanation of the terms used in this application:

[0073] Code issuance: providing an identification code, such as generating a unique identification code for a user device through an encryption algorithm that combines various physical device numbers to identify the user device.

[0074] Multiple codes: The same user device corresponds to multiple identification codes, which can be used as an important indicator to measure the uniqueness of the code issuance service.

[0075] Multi-send code rate: the number of newly added multi-send code devices / the number of newly added devices.

[0076] ID: identification code.

[0077] Local Identifier: A unique identifier generated locally on the user device using a client-side algorithm.

[0078] Remote ID: A unique ID obtained remotely through the IDM service.

[0079] IDM (ID Mapping) service: provides services for mapping and matching various IDs (identification codes, Identifiers).

[0080] In order to facilitate those skilled in the art to understand the technical solutions provided by the embodiments of the present application, the relevant technologies are described below:

[0081] The network platform needs to configure an identification code for each user for identification.

[0082] However, the problem of multiple codes has long existed on various network platforms. It not only affects data statistics, but also affects the recovery of promotional content (such as advertising). Taking the number of monthly active users as an example, more than 10% of new activations are caused by multiple codes; in addition, it also affects the display of artificial intelligence recommendation results, that is, the same user uses two identification codes to generate recommendation results. Since the data features of the two identification codes cannot be associated, the recommendation results cannot be inherited.

[0083] In addition, as device information such as IMEI (International Mobile Equipment Identity) becomes increasingly difficult to obtain, or fake physical device numbers are directly issued as interference, and the current code issuance algorithms are mostly directly generated by encryption algorithms composed of physical device numbers, the multiple code issuance rate will become higher and higher, and any functional changes on the client that affect the acquisition of the physical device number will affect the code issuance results.

[0084] In view of the above-mentioned defects of the related technologies, this application will provide a new code issuance solution that can eliminate the multiple code issuance service based on IDM.

[0085] An exemplary application environment of the present application is provided below.

[0086] like Figure 1 As shown, the exemplary application environment may include a server 2, a service gateway 4, and a user device 6 connected via a network.

[0087] The network may include various network devices, such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and / or the like. The network may include physical links, such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and / or the like. The network may include wireless links, such as cellular links, satellite links, Wi-Fi links, and / or the like.

[0088] The server 2 is configured with an identification code mapping library for providing identification code mapping (IDM) services.

[0089] The server 2 may be composed of a single or multiple computing devices, such as a rack server, a blade server, a tower server or a cabinet server (including an independent server, or a server cluster composed of multiple servers), etc. The one or more computer devices may include a virtualized computing instance. The computer device may load a virtual machine based on a virtual image and / or other data defining a specific software (e.g., an operating system, a dedicated application, a server) for simulation. As the demand for different types of processing services changes, different virtual machines may be loaded and / or terminated on the one or more computer devices.

[0090] The service gateway 4 is used to provide various specific service, such as advertisement push, video push, etc. Taking video push as an example, the service gateway 4 can push different video contents to different user devices to achieve differentiated push.

[0091] User devices 6 can interact with server 2 / service gateway 4. For example, smart phones, tablet devices, laptop computers, smart devices (e.g., smart watches, smart glasses), virtual reality, gaming devices, set-top boxes, digital streaming devices, vehicle terminals, smart TVs, TV boxes, MP4 (Moving Picture Experts Group Audio Layer IV) players, etc.

[0092] The user device 6 can run an operating system such as Windows, Android™, or iOS. Based on the above systems, various application programs such as video player programs, game interactive programs, etc. can be run.

[0093] The user device 6 may interact with the server 2 to determine its own identification code.

[0094] The user equipment 6 can interact with the service gateway 4 to obtain various contents sent by the service gateway 4, such as advertisements.

[0095] It should be noted that Figure 1 The server 2, service gateway 4 and user equipment 6 are only illustrative and are not used to limit the present application. According to actual needs, there may be any number of servers, service gateways and user equipment.

[0096] Hereinafter, the present application will provide a code issuing method, system, computer device and computer readable storage medium.

[0097] Embodiment 1

[0098] It should be noted that the execution subject of this embodiment is the user equipment 6 (hereinafter referred to as the target user equipment).

[0099] Figure 2 The flowchart of the code issuing method according to the first embodiment of the present application is schematically shown.

[0100] like Figure 2 As shown, the code sending method may include steps S200 to S208, wherein:

[0101] Step S200, in response to the program initialization operation, obtaining target device information of the target user device.

[0102] As the number of user devices increases, the service backend has a need to manage each user device.

[0103] For example, for personalized content push, it is necessary to bind an identification code to each user device. The service backend (such as the service gateway 4) can distinguish different user devices according to different identification codes, so as to perform personalized push.

[0104] For another example, for security reasons, an identification code needs to be bound to each user device. When a user device (such as a target user device) is installed, the service backend can obtain the identification code of the target user device. If the target user device is turned on or logged in, the identification code can be used to determine whether the target device is trustworthy.

[0105] Therefore, when the program is initialized, an identification code is generated for the target device information for the above purpose.

[0106] The initialization of a program corresponds to the stage when the program is first installed or when it is opened after being uninstalled and then installed again.

[0107] The identification code can be generated according to the software and hardware information of the target user device, so it is necessary to obtain the target device information.

[0108] The target device information may be obtained under user authorization or by default, and may include:

[0109] (1) DRMID (Digital Rights Management Identity);

[0110] (2) IMEI (International Mobile Equipment Identity);

[0111] (3) MAC (Media Access Control Address);

[0112] (4) Android ID (Android device unique identifier);

[0113] (5) OAID (Open Anonymous ID, open anonymous device identifier).

[0114] It should be noted that the above target device information is only exemplary, and other information may be obtained according to actual needs.

[0115] Step S202: Generate a local identification code according to the target device information.

[0116] The local identification code may be generated by using various coding algorithms, such as MD5 (Message Digest Algorithm 5) to encrypt device information (eg, device number).

[0117] As mentioned above, the target device information may include multiple sub-device information, such as: DRMID, IMEI, MAC, Android ID, OAID, etc. In order to improve the effectiveness and stability of the local identification code, different sub-device information has different priorities. Figure 3 As shown, step S202 may include: step S300, when obtaining several sub-device information, selecting the sub-device information with the highest priority from the several sub-device information; and step S302, generating the local identification code according to the sub-device information with the highest priority.

[0118] Different sub-device information has different stability and validity, and therefore has different priorities.

[0119] For example, the priority of each sub-device information is set as follows: DRMID>IMEI>MAC>Android ID>OAID.

[0120] Some sub-device information may not be available. To improve the effectiveness of the local identification code, you can do the following:

[0121] For example, when the multiple sub-information obtained is DRMID, MAC, and OAID, a local identification code is generated based on the DRMID;

[0122] For example, when the multiple sub-information obtained are IMEI, Android ID, and OAID, a local identification code is generated based on IMEI.

[0123] The above describes the generation operation of the local identification code, but the local identification code may have a multiple code problem, that is, the target user device may be bound to other identification codes in addition to the local identification code. This multiple code problem will cause confusion in the management of the service background. For example, when the service background (such as the service gateway 4) has two identification codes of the target user device, the data features of the two identification codes cannot be associated, and the data cannot be inherited.

[0124] Therefore, after the local identification code is generated, it is necessary to further determine whether the local identification code can be used as the identification code of the target user equipment to ensure that the local identification code does not cause the occurrence of multiple codes. See below for details.

[0125] Step S204: Generate a code sending request, wherein the code sending request includes the target device information and the local identification code.

[0126] The target device information in the code sending request is used to provide query conditions for the server 2.

[0127] The local identification code in the code sending request is used by the server 2 to determine whether it will cause the problem of multiple code sending.

[0128] Step S206: Send the code sending request to the server so that the server returns a target identification code to the target user device according to the target device information, wherein the target identification code is the local identification code or the remote identification code, the local identification code is the identification code provided to the server by the target user device through the code sending request, and the remote identification code is the identification code stored in the server and associated with the target device information.

[0129] When the server 2 determines that the target user device has multiple identification codes, it returns one of the identification codes (the target identification code) to the target user device 6, so that the target user device 6 uses the returned identification code as a true and unique identification code.

[0130] The following is an introduction to Server 2:

[0131] The server 2 is configured with an identification code mapping library for storing the mapping relationship between each remote identification code and each device information.

[0132] like Figure 4 As shown, after receiving the code sending request, server 2 can perform the following operations:

[0133] Step S400: querying a remote identification code from an identification code mapping library according to the target device information.

[0134] The target device information may include DRMID, IMEI, MAC, Android ID, OAID, etc.

[0135] In an exemplary application, a single sub-device information may be used as a query condition, or multiple sub-device information may be used as query conditions. The stability and validity of different sub-device information may be different, and the query results may also be different.

[0136] Step S402, determining whether the query result is returned within a preset time.

[0137] If the query result is returned, the process goes to step S404, otherwise the local identification code or confirmation information that the local identification code can be used is returned.

[0138] Step S404, determining a remote identification code (stable remote identification code) according to the query result.

[0139] By querying a single device information, or querying multiple sub-device information separately, the query results of different sub-device information may be different.

[0140] If only the same remote identification code is found, this remote identification code is determined as the final query result.

[0141] If multiple remote identification codes are found, server 2 performs the following operations:

[0142] ① Determine whether each remote identification code queried is associated with an abnormal identification.

[0143] It should be noted that the server 2 will periodically detect the data stored therein (each piece of data includes an identification code and device information associated with the identification code). If an abnormal identification code is detected, an abnormal identification code is marked as abnormal.

[0144] ② Delete the remote identification code associated with the abnormal identification to obtain the remaining remote identification codes.

[0145] ③ According to the query conditions, select the final remote identification code from the remaining remote identification codes.

[0146] For example, use the system version number to determine the query condition:

[0147] OS=6, query condition: IMEI;

[0148] 6≤OS<10, query condition: MAC;

[0149] OS≥10, query conditions are: MAC, OAID, DRMLD, Android ID;

[0150] OS>11, query conditions: OAID, DRMID, Android ID;

[0151] OS represents the system version number. Taking OS=10 as an example, if the above four query conditions query the remote identification code respectively, and there is no abnormal mark, the query result corresponding to the query condition with the highest priority is selected to determine as the final remote identification code.

[0152] The above is only an example of determining the remote identification code. If necessary, it can also be determined according to the activity of each remote identification code.

[0153] Step S406, determining whether the remote identification code determined in step S404 is the same as the local identification code.

[0154] If they are different, the process proceeds to step S408, otherwise the local identification code or confirmation information that the local identification code can be used is returned.

[0155] Step S408 , determining whether the device model associated with the determined remote identification code is the same as the device model of the target user device.

[0156] If they are the same, the process proceeds to step S410 , otherwise the local identification code or confirmation information that the local identification code can be used is returned.

[0157] Step S410: determine that it is a multiple-code, and return the remote identification code as the target identification code to the target user equipment. The process ends.

[0158] Through the parallel judgment of multiple independent features such as multiple sub-device information and device models, each sub-device information is given a corresponding priority according to the acquisition accuracy and coverage, which can ensure that the returned query results are accurate and reliable.

[0159] Step S208: upon receiving the target identification code, determining the target identification code as the identification code of the target user equipment.

[0160] The target user equipment determines / updates its own identification code according to the target identification code.

[0161] The code issuance method provided in the embodiment of the present application has the following advantages:

[0162] (1) After the target user device generates a local identification code, it sends a code request to server 2. Server 2 determines whether the local identification code is a multiple-send code and returns a local identification code or a remote identification code. The target user device determines / updates its own identification code based on the returned local identification code or remote identification code to avoid multiple-send codes.

[0163] In view of the above, multiple codes are avoided, and there will not be multiple identification codes for the same user device, thereby ensuring the stability of user information and realizing effective management of the service background. Operations such as content push can also be inherited to improve push accuracy.

[0164] (2) In some existing technologies, such as unified processing at the data layer or processing at the data gateway layer, the processing cost is very high on the one hand, and it also causes a lot of data inconsistency and lack of explanation on the other hand. In addition, the original coding algorithm cannot be changed, otherwise the coexistence of the new and old algorithms will lead to large-scale multiple coding problems.

[0165] Compared with the prior art that cannot update the code sending algorithm to reduce multiple code sending, in this embodiment, the code sending algorithm can be iterated. If multiple code sending occurs after iteration, the local identification code can be replaced by the remote identification code to solve the problem.

[0166] Moreover, the problem of multiple code transmission is handled from the source (target user equipment), ensuring that the processing cost is minimized without affecting data consistency. The service response can be achieved within 10ms and the multiple code rate can be reduced by more than 80%.

[0167] (3) Without major changes to the downstream, the multiple code rate can be reduced by quickly updating and iterating the identification code mapping library. Practice shows that the multiple code rate can be reduced from 16% to less than 3% using the coding method of this embodiment.

[0168] Some optional embodiments of the present application are provided below.

[0169] As an optional embodiment, Figure 5 As shown, the method may also include: step S500, in response to the target identification code being the local identification code, sending the operation log carrying the local identification code to the service gateway; step S502, in response to the target identification code being the remote identification code, updating the local identification code in the operation log to the remote identification code to obtain an updated operation log, and sending the updated operation log to the service gateway. In this optional embodiment, an inheritable operation log may be provided to the service gateway 4, so that the service gateway 4 can jointly determine the differentiated and accurate services provided to the target user device based on the current operation log provided above and the previous operation log, such as personalized content recommendation.

[0170] As an optional embodiment, Figure 6 As shown, the method may further include: step S600, in which, in response to a program initialization operation, a stored identification code in the target user device is queried; and step S602, in which, when the stored identification code is queried, the stored identification code is determined as the identification code of the target user device. In this optional embodiment, the stored identification code is used again as the identification code of the target user device. Since no new identification code is generated, the problem of multiple codes will not occur, and inheritance is maintained.

[0171] As an optional embodiment, Figure 7 As shown, the method may also include: step S700, before receiving the target identification code returned by the server, sending the local identification code to the service gateway; and step S700, after receiving the target identification code, in response to the target identification code being the remote identification code, establishing a mapping relationship between the remote identification code and the local identification code, and notifying the service gateway of the mapping relationship, so that the service gateway updates the identification code of the target user device stored therein according to the mapping relationship. In this optional embodiment, the problem of multiple codes is handled from the target user device, and the local identification code is first returned for services with strong timeliness requirements. After receiving the remote identification code, the mapping relationship between the local identification code and the remote identification code is used to let the service gateway 4 know the association between the two, so that the service gateway 4 can: according to the mapping relationship between the local identification code and the remote identification code, perform a senseless replacement and seamless connection between the local identification code and the remote identification code, and ensure that the operation based on the remote identification code can inherit the operation based on the local identification code. Timeliness is ensured under the premise of no perception and modification cost downstream.

[0172] In order to make the present invention easier to understand, Figure 8 As shown, an application example is provided below.

[0173] After the program is installed:

[0174] S800, the target user equipment 6 queries whether there is a stored identification code.

[0175] If yes, go to step S802, otherwise go to step S804.

[0176] S802 , the target user equipment 6 uses the stored identification code as the identification code of the target user equipment, and provides the operation log carrying the identification code to the service gateway 4 .

[0177] S804, the target user device 6 obtains target device information.

[0178] S806, the target user device 6 generates a local identification code according to the target device information.

[0179] S808 , the target user device 6 sends a code sending request carrying the target device information and the local identification code to the server 2 .

[0180] S810, server 2 returns the target identification code according to the code sending request.

[0181] The target identifier may be the local identifier or a remote identifier in the identifier mapping library.

[0182] If the target identification code is a remote identification code, it means that the local identification code causes the multiple code problem. Before the local identification code is sent to the server 2, the identification code mapping library already has a stable identification code of the target user device 6.

[0183] If the target identification code is a remote identification code, the process proceeds to S812 , otherwise the process proceeds to S816 .

[0184] S812: Update the local identification code in the operation log to the remote identification code to obtain an updated operation log.

[0185] S814, sending the updated operation log to the service gateway 4. The process ends.

[0186] S816: Send the operation log carrying the local identification code to the service gateway 4. The process ends.

[0187] Embodiment 2

[0188] It should be noted that the execution subject of this embodiment is the server 2. For specific technical details, please refer to the first embodiment.

[0189] Fig. 9 The flowchart of the code issuing method according to the second embodiment of the present application is schematically shown.

[0190] like Fig. 9 As shown, the code sending method may include steps S900 to S906, wherein:

[0191] Step S900: receiving a code sending request sent by a target user equipment, wherein the code sending request includes target equipment information and a local identification code, wherein the local identification code is generated by the target user equipment according to the target equipment information.

[0192] Step S902: query a target remote identification code from an identification code mapping library according to the target device information. The identification code mapping library is used to store mapping relationships between remote identification codes and device information. The target remote identification code is a remote identification code associated with the target device information.

[0193] Step S904: when the target remote identification code is found, the target remote identification code is returned to the target user equipment.

[0194] Step S906: if the target remote identification code is not found, the local identification code is returned to the target user device, and the local identification code and the target device information are updated in the identification code mapping library.

[0195] As an optional embodiment, the target device information includes sub-device information, and different sub-device information corresponds to different priorities; the querying of the target remote identification code from the identification code mapping library includes:

[0196] In the case where the target device information includes a plurality of sub-device information, a plurality of query conditions are determined according to the system version number of the target user device, each query condition being one of the plurality of sub-device information;

[0197] Querying the remote identification code matching each query condition from the identification code mapping library; and

[0198] When several query conditions among the multiple query conditions are matched to respective remote identification codes, the remote identification code matching the target query condition is determined as the target remote identification code; wherein the target query condition is the query condition with the highest priority among the several query conditions.

[0199] As an optional embodiment, in the case where the target remote identification code is queried, returning the target remote identification code to the target user equipment includes:

[0200] When the target remote identification code is different from the local identification code, obtaining a device model associated with the target remote identification code;

[0201] In a case where the device model associated with the target remote identification code is different from the device model of the target user device, the target remote identification code is returned to the target user device.

[0202] As an optional embodiment, the method further includes:

[0203] The identification code mapping library is pre-established, the identification code mapping library includes a plurality of data, each data includes a remote identification code and device information mapped to the remote identification code, the device information includes attribute information and location information;

[0204] The identification code mapping library is updated according to each remote identification code, attribute information and / or location information of each remote identification code mapping.

[0205] Each piece of data may include an identification code mapping pair, attributes, etc. to ensure effective management.

[0206] The identification code mapping pair may include: IMEI, OAID, DRMID, MAC, Android ID, etc.

[0207] Attributes may include platform, activation time, active days, brand, model, system version number, IP region, program version, etc.

[0208] As an optional embodiment, the method further includes:

[0209] Storing incremental data in the identification code mapping library at preset time intervals;

[0210] If an abnormal identification code is detected in the incremental data, an abnormal identification is performed on the data corresponding to the abnormal identification code; wherein the abnormal identification is used to indicate that the abnormal identification code is logically deleted or cannot be returned to the user device.

[0211] In the initial stage, the full amount of data is provided in the identification code mapping library, and then incremental data is stored every day. If anomalies are found in the data to be stored, the format field is_valid=0 (abnormal flag) of the corresponding data will be set, thereby logically deleting it.

[0212] Among them, the step of detecting abnormal identification codes may include: anti-cheating, kicking out low-quality remote identification codes, specifically:

[0213] (1) Threshold anti-cheating: the corresponding value of a certain type of device information should be within a reasonable range.

[0214] (2) Attribute anti-cheating: For example, two logs appearing on the same day may have completely different machine models and device information.

[0215] (3) Positioning anti-cheating: At the same time, the identification codes of two different cities correspond to different device information.

[0216] By using the above method, unstable abnormal identification codes are detected and identified, thereby improving the data reliability of the identification code mapping library.

[0217] As an optional embodiment, the method further includes:

[0218] At preset time intervals, monitoring data of the multiple code rate is obtained, where the multiple code rate is the ratio of the number of newly added multiple code devices to the number of newly added devices.

[0219] In an exemplary application, the multiple bitrate can be monitored on a daily basis, the number of correctable numbers for each version can be monitored, the accuracy of the corrected part can be compared with that of third-party data, and service coverage monitoring and timeout monitoring can also be provided. In this optional embodiment, the data interpretability can be enhanced through the above-mentioned complete monitoring log.

[0220] Embodiment 3

[0221] Fig.10 The block diagram of the coding method according to the third embodiment of the present application is schematically shown. The coding method can be divided into one or more program modules, and one or more program modules are stored in a storage medium and executed by one or more processors to complete the embodiment of the present application. The program module referred to in the embodiment of the present application refers to a series of computer program instruction segments that can complete specific functions. The following description will specifically introduce the functions of each program module in this embodiment. Fig.10 As shown, the code issuing system 1000 may include an acquisition module 1010, a first generation module 1020, a second generation module 1030, a sending module 1040 and a determination module 1050, wherein:

[0222] An acquisition module 1010 is used to acquire target device information of a target user device in response to a program initialization operation;

[0223] A first generating module 1020, configured to generate a local identification code according to the target device information;

[0224] A second generating module 1030 is used to generate a code sending request, wherein the code sending request includes the target device information and the local identification code;

[0225] a sending module 1040, configured to send the code sending request to a server, so that the server returns a target identification code to the target user device according to the target device information, wherein the target identification code is the local identification code or the remote identification code, the local identification code is the identification code provided to the server by the target user device through the code sending request, and the remote identification code is the identification code stored in the server and associated with the target device information; and

[0226] The determination module 1050 is configured to, upon receiving the target identification code, determine the target identification code as the identification code of the target user equipment.

[0227] As an optional embodiment, the system may further include a first response module (not shown) configured to:

[0228] In response to the program initialization operation, querying the stored identification code in the target user device;

[0229] In the case where the stored identification code is found, the stored identification code is determined as the identification code of the target user equipment.

[0230] As an optional embodiment, the target device information includes sub-device information, and different sub-device information has different priorities; the first generating module 1020 is further used to:

[0231] When a plurality of sub-device information is obtained, selecting the sub-device information with the highest priority from the plurality of sub-device information; and

[0232] The local identification code is generated according to the sub-device information with the highest priority.

[0233] As an optional embodiment, the system may further include a second response module (not identified) for:

[0234] In response to the target identification code being the local identification code, sending the operation log carrying the local identification code to the service gateway;

[0235] In response to the target identification code being the remote identification code, the local identification code in the operation log is updated to the remote identification code to obtain an updated operation log, and the updated operation log is sent to the service gateway.

[0236] As an optional embodiment, the system may further include an identification code sending module (not marked) for:

[0237] Before receiving the target identification code returned by the server, sending the local identification code to the service gateway; and

[0238] After receiving the target identification code, in response to the target identification code being the remote identification code, a mapping relationship between the remote identification code and the local identification code is established, and the mapping relationship is notified to the service gateway so that the service gateway updates the identification code of the target user device stored therein according to the mapping relationship.

[0239] Embodiment 4

[0240] Fig.11 The block diagram of the coding method according to the fourth embodiment of the present application is schematically shown. The coding method can be divided into one or more program modules, and one or more program modules are stored in a storage medium and executed by one or more processors to complete the embodiment of the present application. The program module referred to in the embodiment of the present application refers to a series of computer program instruction segments that can complete specific functions. The following description will specifically introduce the functions of each program module in this embodiment. Fig.11As shown, the code issuing system 1100 may include a receiving module 1110, a query module 1120, a first returning module 1130 and a second returning module 1140, wherein:

[0241] The receiving module 1110 is configured to receive a code sending request sent by a target user equipment, wherein the code sending request includes target equipment information and a local identification code, wherein the local identification code is generated by the target user equipment according to the target equipment information;

[0242] A query module 1120, configured to query a target remote identification code from an identification code mapping library according to the target device information, wherein the identification code mapping library is configured to store mapping relationships between remote identification codes and device information, and the target remote identification code is a remote identification code associated with the target device information;

[0243] A first returning module 1130 is configured to return the target remote identification code to the target user equipment when the target remote identification code is found; and

[0244] The second returning module 1140 is configured to return the local identification code to the target user device and update the local identification code and the target device information into the identification code mapping library when the target remote identification code is not found.

[0245] As an optional embodiment, the target device information includes sub-device information, and different sub-device information corresponds to different priorities; the query module 1120 is further used to:

[0246] In the case where the target device information includes a plurality of sub-device information, a plurality of query conditions are determined according to the system version number of the target user device, each query condition being one of the plurality of sub-device information;

[0247] Querying the remote identification code matching each query condition from the identification code mapping library; and

[0248] When several query conditions among the multiple query conditions are matched to respective remote identification codes, the remote identification code matching the target query condition is determined as the target remote identification code; wherein the target query condition is the query condition with the highest priority among the several query conditions.

[0249] As an optional embodiment, the first returning module 1130 is further configured to:

[0250] When the target remote identification code is different from the local identification code, obtaining a device model associated with the target remote identification code;

[0251] In a case where the device model associated with the target remote identification code is different from the device model of the target user device, the target remote identification code is returned to the target user device.

[0252] As an optional embodiment, the system may further include a building module (not shown) for:

[0253] The identification code mapping library is pre-established, the identification code mapping library includes a plurality of data, each data includes a remote identification code and device information mapped to the remote identification code, the device information includes attribute information and location information;

[0254] The identification code mapping library is updated according to each remote identification code, attribute information and / or location information of each remote identification code mapping.

[0255] As an optional embodiment, the system may further include an abnormality identification module (not identified) for:

[0256] Storing incremental data in the identification code mapping library at preset time intervals;

[0257] If an abnormal identification code is detected in the incremental data, an abnormal identification is performed on the data corresponding to the abnormal identification code; wherein the abnormal identification is used to indicate that the abnormal identification code is logically deleted or cannot be returned to the user device.

[0258] As an optional embodiment, the system may further include a monitoring module (not shown) for:

[0259] At preset time intervals, monitoring data of the multiple code rate is obtained, where the multiple code rate is the ratio of the number of newly added multiple code devices to the number of newly added devices.

[0260] Embodiment 5

[0261] Fig.12 The schematic diagram of the hardware architecture of a computer device suitable for implementing the code issuance method according to the fifth embodiment of the present application is shown schematically. The computer device 10000 can be a distributed server 2 or a part of the server 2, or a target user device 6 or a part of the target user device 6. In this embodiment, the computer device 10000 is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions. For example, it can be a rack server, a blade server, a tower server or a cabinet server (including an independent server, or a server cluster composed of multiple servers), etc., or it can be a smart phone, a tablet device, a laptop computer, a smart device (for example, a smart watch, smart glasses), virtual reality, a gaming device, a set-top box, a digital streaming device, a vehicle-mounted terminal, a smart TV, an MP4 (Moving Picture Experts Group Audio Layer IV) player, etc. Fig.12As shown, the computer device 10000 includes at least but is not limited to: a memory 10010, a processor 10020, and a network interface 10030 that can communicate with each other through a system bus. Among them:

[0262] The memory 10010 includes at least one type of computer-readable storage medium, and the readable storage medium includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 10010 may be an internal storage module of the computer device 10000, such as a hard disk or a memory of the computer device 10000. In other embodiments, the memory 10010 may also be an external storage device of the computer device 10000, such as a plug-in hard disk equipped on the computer device 10000, a smart memory card (Smart Media Card, referred to as SMC), a secure digital (Secure Digital, referred to as SD) card, a flash card, etc. Of course, the memory 10010 may also include both the internal storage module of the computer device 10000 and its external storage device. In the embodiment of the present application, the memory 10010 is generally used to store the operating system and various application software installed in the computer device 10000, such as the program code of the code sending method, etc. In addition, the memory 10010 can also be used to temporarily store various data that have been output or will be output.

[0263] In some embodiments, the processor 10020 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 10020 is generally used to control the overall operation of the computer device 10000, such as performing control and processing related to data interaction or communication with the computer device 10000. In this embodiment, the processor 10020 is used to run the program code stored in the memory 10010 or process data.

[0264] The network interface 10030 may include a wireless network interface or a wired network interface, and the network interface 10030 is generally used to establish a communication link between the computer device 10000 and other computer devices. For example, the network interface 10030 is used to connect the computer device 10000 to an external terminal through a network, and to establish a data transmission channel and a communication link between the computer device 10000 and the external terminal. The network may be a wireless or wired network such as an intranet, the Internet, the Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth, Wi-Fi, etc.

[0265] It should be pointed out that Fig.12 Only a computer device having components 10010 - 10030 is shown, but it should be understood that implementation of all of the components shown is not a requirement, and more or fewer components may be implemented instead.

[0266] In this embodiment, the code sending method stored in the memory 10010 may also be divided into one or more program modules and executed by one or more processors (processor 10020 in this embodiment) to complete the present application.

[0267] Embodiment 6

[0268] This embodiment further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the code sending method in the embodiment are implemented.

[0269] In this embodiment, the computer-readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the computer-readable storage medium can be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the computer-readable storage medium can also be an external storage device of a computer device, such as a plug-in hard disk equipped on the computer device, a smart memory card (Smart Media Card, referred to as SMC), a secure digital (Secure Digital, referred to as SD) card, a flash card, etc. Of course, the computer-readable storage medium can also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the computer-readable storage medium is generally used to store an operating system and various application software installed on the computer device, such as the program code of the code sending method in the embodiment, etc. In addition, the computer-readable storage medium can also be used to temporarily store various types of data that have been output or are to be output.

[0270] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual assembled circuit modules, or multiple modules or steps therein can be made into a single assembled circuit module for implementation. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0271] It should be noted that the above are only preferred embodiments of the present application, and the patent protection scope of the present application is not limited thereto. Any equivalent structure or equivalent process transformation made using the contents of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A code issuing method based on IDM service, characterized in that: The method comprises: In response to the program initialization operation, obtaining target device information of the target user device; Generate a local identification code according to the target device information; Generate a code sending request, wherein the code sending request includes the target device information and the local identification code; Sending the code sending request to a server so that the server returns a target identification code to the target user device according to the target device information, wherein the target identification code is the local identification code or the remote identification code, the local identification code is a unique identification code generated locally in the target user device by a client algorithm, the target user device provides the local identification code to the server through the code sending request, the remote identification code is an identification code stored in the server and associated with the target device information, and the remote identification code is a unique identification code obtained through a remote service; and In case of receiving the target identification code, determining the target identification code as the identification code of the target user equipment; The target device information includes sub-device information, and different sub-device information has different priorities; and generating a local identification code according to the target device information includes: When a plurality of sub-device information is obtained, selecting the sub-device information with the highest priority from the plurality of sub-device information; and The local identification code is generated according to the sub-device information with the highest priority.

2. The code issuing method based on IDM service according to claim 1, characterized in that: Also includes: In response to the program initialization operation, querying the stored identification code in the target user device; In the case where the stored identification code is found, the stored identification code is determined as the identification code of the target user equipment.

3. The method for issuing codes based on IDM service according to any one of claims 1 to 2, characterized in that: Also includes: In response to the target identification code being the local identification code, sending the operation log carrying the local identification code to the service gateway; In response to the target identification code being the remote identification code, the local identification code in the operation log is updated to the remote identification code to obtain an updated operation log, and the updated operation log is sent to the service gateway.

4. The method for issuing codes based on IDM service according to any one of claims 1 to 2, characterized in that: Also includes: Before receiving the target identification code returned by the server, sending the local identification code to the service gateway; and After receiving the target identification code, in response to the target identification code being the remote identification code, a mapping relationship between the remote identification code and the local identification code is established, and the mapping relationship is notified to the service gateway so that the service gateway updates the identification code of the target user device stored therein according to the mapping relationship.

5. A code issuing system based on IDM service, characterized in that: The system comprises: An acquisition module, used for acquiring target device information of a target user device in response to a program initialization operation; A first generating module, used to generate a local identification code according to the target device information; A second generating module, configured to generate a code sending request, wherein the code sending request includes the target device information and the local identification code; a sending module, configured to send the code sending request to a server, so that the server returns a target identification code to the target user device according to the target device information, wherein the target identification code is the local identification code or the remote identification code, the local identification code is a unique identification code generated locally in the target user device by a client algorithm, the target user device provides the local identification code to the server through the code sending request, the remote identification code is an identification code stored in the server and associated with the target device information, and the remote identification code is a unique identification code obtained through a remote service; and a determination module, configured to, upon receiving the target identification code, determine the target identification code as an identification code of the target user equipment; The target device information includes sub-device information, and different sub-device information has different priorities; the first generating module is used to: When a plurality of sub-device information is obtained, selecting the sub-device information with the highest priority from the plurality of sub-device information; and The local identification code is generated according to the sub-device information with the highest priority.

6. A code issuing method based on IDM service, characterized in that: The method comprises: Receiving a code sending request sent by a target user device, the code sending request including target device information and a local identification code, wherein the local identification code is a unique identification code generated locally by the target user device through a client algorithm according to the target device information; the target device information includes sub-device information, and different sub-device information has different priorities; the target user device generates a local identification code according to the target device information, including: The target user equipment selects the sub-device information with the highest priority from the sub-device information when the target user equipment obtains the sub-device information with the highest priority; and the target user equipment generates the local identification code according to the sub-device information with the highest priority; According to the target device information, query a target remote identification code from an identification code mapping library, wherein the identification code mapping library is used to store mapping relationships between remote identification codes and device information, wherein the target remote identification code is a remote identification code associated with the target device information, and wherein the remote identification code is a unique identification code obtained through a remote service; When the target remote identification code is found, returning the target remote identification code to the target user equipment; and In the case that the target remote identification code is not found, the local identification code is returned to the target user equipment, and the local identification code and the target equipment information are updated in the identification code mapping library.

7. The code issuing method based on IDM service according to claim 6, characterized in that: The target device information includes sub-device information, and different sub-device information corresponds to different priorities; The querying of the target remote identification code from the identification code mapping library includes: In the case where the target device information includes a plurality of sub-device information, a plurality of query conditions are determined according to the system version number of the target user device, each query condition being one of the plurality of sub-device information; Querying the remote identification code matching each query condition from the identification code mapping library; and When several query conditions among the multiple query conditions are matched to respective remote identification codes, the remote identification code matching the target query condition is determined as the target remote identification code; wherein the target query condition is the query condition with the highest priority among the several query conditions.

8. The code issuing method based on IDM service according to claim 7, characterized in that: When the target remote identification code is found, returning the target remote identification code to the target user equipment includes: When the target remote identification code is different from the local identification code, obtaining a device model associated with the target remote identification code; In a case where the device model associated with the target remote identification code is different from the device model of the target user device, the target remote identification code is returned to the target user device.

9. The method for issuing codes based on IDM service according to any one of claims 6 to 8, characterized in that: Also includes: The identification code mapping library is pre-established, the identification code mapping library includes a plurality of data, each data includes a remote identification code and device information mapped to the remote identification code, the device information includes attribute information and location information; The identification code mapping library is updated according to each remote identification code and the attribute information and / or location information of each remote identification code mapping.

10. The code issuing method based on IDM service according to claim 9, characterized in that: Also includes: Storing incremental data in the identification code mapping library at preset time intervals; If an abnormal identification code is detected in the incremental data, an abnormal identification is performed on the data corresponding to the abnormal identification code; wherein the abnormal identification is used to indicate that the abnormal identification code is logically deleted or cannot be returned to the user device.

11. The method for issuing codes based on IDM service according to any one of claims 6 to 8, characterized in that: Also includes: At preset time intervals, monitoring data of the multiple code rate is obtained, where the multiple code rate is the ratio of the number of newly added multiple code target user devices to the number of newly added target user devices.

12. A code issuing system based on IDM service, characterized in that: include: A receiving module, configured to receive a code sending request sent by a target user device, wherein the code sending request includes target device information and a local identification code, wherein the local identification code is a unique identification code generated locally by the target user device through a client algorithm according to the target device information; wherein the target device information includes sub-device information, and different sub-device information has different priorities; the target user device generates a local identification code according to the target device information, including: When a plurality of sub-device information is obtained, selecting the sub-device information with the highest priority from the plurality of sub-device information; and generating the local identification code according to the sub-device information with the highest priority; A query module, configured to query a target remote identification code from an identification code mapping library according to the target device information, wherein the identification code mapping library is used to store a mapping relationship between each remote identification code and each device information, wherein the target remote identification code is a remote identification code associated with the target device information, and wherein the remote identification code is a unique identification code obtained through a remote service; A first returning module, configured to return the target remote identification code to the target user equipment when the target remote identification code is found; and The second returning module is used to return the local identification code to the target user equipment when the target remote identification code is not found, and to update the local identification code and the target equipment information into the identification code mapping library.

13. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, it is used to implement the steps of the code issuance method based on the IDM service as described in any one of claims 1 to 4 or 6 to 11.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program can be executed by at least one processor to enable the at least one processor to perform the steps of the code issuance method based on the IDM service as described in any one of claims 1 to 4 or 6 to 11.

Images