A link log association method and a link log association device

Abstract

This application discloses a link log association method and apparatus, relating to the field of smart home technology. The method includes: obtaining an initial link identifier from an application; sending the initial link identifier to a cloud server and sending the initial link identifier and link tracking data to a log service system; generating business data based on the initial link identifier and generating cloud server tracking data based on the business data; sending the business data to a software development tool on the device side and sending the cloud server tracking data to the log service system; generating device tracking data based on the business data and sending the device tracking data to the log service system; and performing association processing on the link tracking data, cloud server tracking data, and device tracking data based on the initial link identifier to generate target log data. The embodiments provided in this application enable the generation of complete target log data through link log association even when the software development tool cannot be updated.

Description

Technical Field

[0001] This application relates to the field of smart home technology, and in particular to a link log association method and a link log association device. Background Technology

[0002] With the development of technology, data interaction between cloud servers and devices is becoming increasingly close. App applications often need to integrate more and more external data communication SDKs and cloud services for data interaction. Due to reasons such as server upgrades, the bankruptcy of external companies, and the cessation of procurement, the data communication SDK cannot be updated, resulting in the inability to upgrade and update communication data content. After the data communication SDK stops iterative updates, the multi-point link logs between the cloud server and the device cannot be correlated, making it impossible to perform data statistics and troubleshooting through complete link logs. Summary of the Invention

[0003] In view of this, this application provides a link log association method and a link log association device to solve the defect in the prior art that complete link logs cannot be obtained when the SDK cannot be updated, and realizes the association of link logs to generate complete target log data when the SDK cannot be updated.

[0004] In a first aspect, this application provides a link log association method applied to a server, wherein the server is connected to an application, a cloud server, a device, and a log service system via a network.

[0005] The link log association method includes:

[0006] Obtain the initial link identifier from the application.

[0007] The initial link identifier is sent to the cloud server, and the initial link identifier and the link tracking data corresponding to the initial link identifier are sent to the log service system;

[0008] Upon receiving the initial link identifier, the cloud server generates business data based on the initial link identifier and generates cloud server data points based on the business data.

[0009] The business data is sent to the software development tool on the device, and the cloud server data is sent to the log service system.

[0010] When the software development tool on the device receives the business data, it generates device tracking data based on the business data and sends the device tracking data to the log service system.

[0011] Upon receiving the link tracking data, cloud server tracking data, and device tracking data, the log service system performs association processing on the link tracking data, cloud server tracking data, and device tracking data based on the initial link identifier to generate target log data.

[0012] Preferably, according to the link log association method provided in this application,

[0013] The generation of service data based on the initial link identifier includes:

[0014] The initial link identifier is processed to obtain the target link identifier;

[0015] The service data is generated based on the target link identifier.

[0016] Preferably, according to the link log association method provided in this application,

[0017] The step of generating cloud server event tracking data based on the business data includes:

[0018] Based on the target link identifier, obtain the device identifier of the target device from the device end;

[0019] Calculate the device identifier and the service data to obtain a first service identifier corresponding to the target link identifier;

[0020] Based on the first service identifier, the device identifier, and the service data, cloud server embedding data corresponding to the first service identifier is generated.

[0021] Preferably, according to the link log association method provided in this application,

[0022] The process of generating device tracking data based on the business data includes:

[0023] The business data is processed to obtain the target business data;

[0024] Based on the target business data, obtain the device identifier of the target device;

[0025] A second service identifier is obtained by calculating the device identifier and the target service data.

[0026] Based on the second service identifier, the device identifier, and the target service data, device embedding data corresponding to the second service identifier is generated.

[0027] Preferably, according to the link log association method provided in this application,

[0028] After the step of generating the cloud server embedding data corresponding to the first service identifier based on the first service identifier, the device identifier, and the service data, the method includes:

[0029] The target link identifier and the first service identifier corresponding to the target link identifier are sent to the log service system.

[0030] Preferably, according to the link log association method provided in this application,

[0031] After the step of generating device tracking data corresponding to the second service identifier based on the second service identifier, the device identifier, and the target service data, the method includes:

[0032] The second service identifier is sent to the log service system.

[0033] Preferably, according to the link log association method provided in this application,

[0034] Upon receiving the link tracking data, cloud server tracking data, and device tracking data from the log service system, the system performs association processing on the link tracking data, cloud server tracking data, and device tracking data based on the initial link identifier to generate target log data, including:

[0035] When the log service system receives the link tracking data, the cloud server tracking data, the initial link identifier, and the target link identifier, it determines the link relationship between the link tracking data corresponding to the initial link identifier and the cloud server tracking data corresponding to the target link identifier based on the initial link identifier and the target link identifier.

[0036] When the log service system receives the cloud server data, the device data, the first service identifier, and the second service identifier, it determines the log relationship between the cloud server data corresponding to the first service identifier and the device data corresponding to the second service identifier based on the first service identifier and the second service identifier.

[0037] Based on the link relationship and the log relationship, the link tracking data, the cloud server tracking data, and the device tracking data are correlated to generate the target log data.

[0038] Preferably, according to the link log association method provided in this application,

[0039] The link relationship includes at least: a first association relationship and a second association relationship;

[0040] The step of determining the link relationship between the link tracking data corresponding to the initial link identifier and the cloud server tracking data corresponding to the target link identifier based on the initial link identifier and the target link identifier includes:

[0041] The initial link identifier and the target link identifier are compared and processed.

[0042] If the initial link identifier and the target link identifier are the same, a first comparison result is obtained, and based on the first comparison result, the first association relationship between the link tracking data and the cloud server tracking data is determined.

[0043] If the initial link identifier and the target link identifier are different, a second comparison result is obtained, and based on the second comparison result, the second association relationship between the link tracking data and the cloud server tracking data is determined.

[0044] Preferably, according to the link log association method provided in this application,

[0045] The log relationships include at least: a third association relationship and a fourth association relationship;

[0046] The step of determining the log relationship between the cloud server embedding data corresponding to the first service identifier and the device embedding data corresponding to the second service identifier based on the first service identifier and the second service identifier includes:

[0047] The first service identifier and the second service identifier are compared and processed.

[0048] If the first service identifier and the second service identifier are the same, a third comparison result is obtained, and based on the third comparison result, the third association relationship between the cloud server embedding data and the device embedding data is determined;

[0049] If the first service identifier and the second service identifier are different, a fourth comparison result is obtained, and based on the fourth comparison result, the fourth association relationship between the cloud server embedding data and the device embedding data is determined.

[0050] Preferably, according to the link log association method provided in this application,

[0051] The process of associating the link tracking data, the cloud server tracking data, and the device tracking data based on the link relationship and the log relationship to generate the target log data includes:

[0052] Based on the first association relationship and the third association relationship, the link tracking data, the cloud server tracking data, and the device tracking data are associated to generate the target log data.

[0053] Secondly, this application also provides a link log association device, applied to a server, wherein the server is connected to the application end, cloud server, device end and log service system via a network respectively;

[0054] The link log association device includes:

[0055] The module for obtaining the initial link identifier is used to obtain the initial link identifier from the application.

[0056] The first sending module is used to send the initial link identifier to the cloud server, and to send the initial link identifier and the link tracking data corresponding to the initial link identifier to the log service system;

[0057] A cloud server event tracking data generation module is used to generate business data based on the initial link identifier when the cloud server receives the initial link identifier, and generate cloud server event tracking data based on the business data.

[0058] The second sending module is used to send the business data to the software development tool on the device side and send the cloud server data to the log service system.

[0059] A device tracking data generation module is used to generate device tracking data based on the business data received by the software development tool on the device side, and send the device tracking data to the log service system.

[0060] The target log data generation module is used to generate target log data based on the initial link identifier when the log service system receives the link tracking data, the cloud server tracking data, and the device tracking data, and performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data.

[0061] Thirdly, this application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the link log association method as described above through the computer program.

[0062] Fourthly, this application also provides a computer-readable storage medium comprising a stored program, wherein the program, when executed, implements any of the link log association methods described above.

[0063] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the link log association method as described above.

[0064] This application provides a link log association method and a link log association device. The link log association method is applied to a server, which is connected to an application, a cloud server, a device, and a log service system via a network. The link log association method involves obtaining an initial link identifier from the application; sending the initial link identifier to the cloud server; and sending the initial link identifier and corresponding link tracking data to the log service system. Upon receiving the initial link identifier, the cloud server generates business data based on the initial link identifier and generates cloud server tracking data based on the business data. The process involves several steps: First, the system sends the business data to the software development tool on the device side and sends the cloud server's data to the log service system. Second, upon receiving the business data, the software development tool on the device side generates device-level data based on the business data and sends this data to the log service system. Third, upon receiving the link-level data, the cloud server's data, and the device-level data, the log service system performs association processing based on the initial link identifier to generate target log data. This addresses the deficiency in existing technologies where complete link logs cannot be obtained when the SDK cannot be updated, enabling the association of link logs to generate complete target log data even when the SDK cannot be updated. Attached Figure Description

[0065] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0066] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0067] Figure 1 This is a schematic diagram of the hardware environment for a link log association method provided in this application;

[0068] Figure 2 This is one of the flowcharts illustrating a link log association method provided in this application;

[0069] Figure 3 This is the second flowchart of a link log association method provided in this application;

[0070] Figure 4 This is a schematic diagram of the structure of a link log association device provided in this application;

[0071] Figure 5 This is a schematic diagram of the electronic device provided in this application. Detailed Implementation

[0072] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0073] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0074] First, let's analyze some of the terms used in this application:

[0075] Servers: A server is a type of computer that runs faster, handles higher loads, and is more expensive than a regular computer. Servers provide computing or application services to other client machines (such as PCs, smartphones, ATMs, and even large equipment like train systems) on a network. Servers feature high-speed CPU processing power, long-term reliable operation, powerful I / O external data throughput, and better scalability. Traditional servers typically integrate a Central Processing Unit (CPU), Hard Disk Drive (HDD), Solid State Drive (SSD), GPU (General Processing Unit), and other peripherals into a single physical chassis. They often use different server designs to meet different application needs, lacking the flexibility to expand and change to accommodate diverse requirements.

[0076] Application side: The application side where apps such as mobile apps and computer apps are located.

[0077] Cloud servers: Elastic Compute Service (ECS) is a simple, efficient, secure, reliable computing service with elastically scalable processing power. Its management is simpler and more efficient than that of physical servers. Users can quickly create or release any number of cloud servers without having to purchase hardware in advance.

[0078] Devices include: smart air conditioners, mobile phones, tablets, smart range hoods, smart refrigerators, smart ovens, smart stoves, smart washing machines, smart water heaters, smart washing equipment, smart dishwashers, smart projectors, smart TVs, smart clothes racks, smart curtains, smart audio-visual systems, smart sockets, smart speakers, smart speakers, smart fresh air systems, smart kitchen and bathroom equipment, smart bathroom fixtures, smart robot vacuum cleaners, smart window cleaning robots, smart mopping robots, smart air purifiers, smart steam ovens, smart microwave ovens, smart water heaters, smart air purifiers, smart water dispensers, smart door locks, etc.

[0079] Log service system: Also known as system log, the system log records information about hardware, software, and system problems, and can also monitor events occurring in the system. Users can use it to check the cause of errors or look for traces left by attackers during attacks. System logs include system logs, application logs, and security logs.

[0080] Software Development Kit (SDK) is generally a collection of development tools used by software engineers to create application software for specific software packages, software frameworks, hardware platforms, operating systems, etc. It is a toolkit provided by a third-party service provider to implement a certain function of a software product. It usually appears in the form of a collection of KPIs, documents, examples, and tools, that is, a collection of many types of files.

[0081] Tracking data: The traces left by instructions in different systems or terminals. It can be understood as log data automatically generated by the server based on the operation of the executed instructions.

[0082] The following is combined with Figures 1-5 This application describes a link log association method and apparatus, which, through the embodiments provided in this application, solve the defect in the prior art that complete link logs cannot be obtained when the SDK cannot be updated, and realize the association of link logs to generate complete target log data when the SDK cannot be updated.

[0083] According to one aspect of the embodiments of this application, a link log association method is provided. This link log association method is widely used in whole-house intelligent digital control application scenarios such as smart homes, smart home ecosystems, and intelligence house ecosystems. Optionally, in this embodiment, the above-mentioned link log association method can be applied to, for example... Figure 1 The hardware environment shown consists of terminal device 102 and server 104. For example... Figure 1 As shown, server 104 is connected to terminal device 102 via a network and can be used to provide services (such as application services) to the terminal or clients installed on the terminal. A database can be set up on the server or independently of the server to provide data storage services for server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data processing services for server 104.

[0084] The aforementioned network may include, but is not limited to, at least one of the following: wired network, wireless network. The aforementioned wired network may include, but is not limited to, at least one of the following: wide area network, metropolitan area network, local area network. The aforementioned wireless network may include, but is not limited to, at least one of the following: Wi-Fi (Wireless Fidelity), Bluetooth. The terminal device 102 may not be limited to PC, mobile phone, tablet computer, smart air conditioner, smart range hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing equipment, smart dishwasher, smart projector, smart TV, smart clothes rack, smart curtains, smart audio-visual equipment, smart socket, smart speaker, smart speaker box, smart fresh air equipment, smart kitchen and bathroom equipment, smart bathroom equipment, smart robot vacuum cleaner, smart window cleaning robot, smart mopping robot, smart air purifier, smart steam oven, smart microwave oven, smart water heater, smart air purifier, smart water dispenser, smart door lock, etc.

[0085] like Figure 2 As shown, it is one of the implementation flow diagrams of a link log association method provided in the embodiments of this application. A link log association method may include, but is not limited to, steps S100 to S600.

[0086] S100, obtain the initial link identifier from the application;

[0087] S200, the initial link identifier is sent to the cloud server, and the initial link identifier and the link tracking data corresponding to the initial link identifier are sent to the log service system;

[0088] S300, when the cloud server receives the initial link identifier, it generates business data based on the initial link identifier and generates cloud server embedding data based on the business data;

[0089] S400, the business data is sent to the software development tool on the device side, and the cloud server data points are sent to the log service system;

[0090] S500, when the software development tool on the device receives the business data, it generates device tracking data based on the business data and sends the device tracking data to the log service system;

[0091] S600, when the log service system receives the link tracking data, the cloud server tracking data, and the device tracking data, it performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data based on the initial link identifier to generate target log data.

[0092] First, it should be noted that the link log association method provided in this application embodiment is applied to a server, which is connected to the application end, cloud server, device end and log service system through a network.

[0093] In the embodiments of this application, the application is an APP, and the device is a smart air conditioner as an example.

[0094] In step S100 of some embodiments, the initial link identifier of the application is obtained.

[0095] It is understandable that the application (APP) automatically generates an initial link identifier A according to a preset link identifier generation algorithm, and the server obtains the initial link identifier A generated by the application.

[0096] It should be noted that the initial link identifier A is the starting identifier for identifying the link.

[0097] In step S200 of some embodiments, the initial link identifier is sent to the cloud server, and the initial link identifier and the link tracking data corresponding to the initial link identifier are sent to the log service system.

[0098] It is understandable that after completing step S100 to obtain the initial link identifier of the application, the server sends the initial link identifier to the cloud server and sends the initial link identifier and the link tracking data corresponding to the initial link identifier to the log service system.

[0099] It should be noted that the server records the time when the application generates the initial link identifier A and the time when the server obtains the initial link identifier A, and generates link tracking data D.

[0100] It should be further noted that the initial link identifier A and the link tracking data D are associated together.

[0101] In step S300 of some embodiments, when the cloud server receives the initial link identifier, business data is generated based on the initial link identifier, and cloud server embedding data is generated based on the business data.

[0102] It is understandable that after completing step S200, which sends the initial link identifier to the cloud server and sends the initial link identifier and the link tracking data corresponding to the initial link identifier to the log service system, the specific execution steps can be as follows: when the cloud server receives the initial link identifier, the server first processes the initial link identifier to obtain the target link identifier, and then generates the business data based on the target link identifier.

[0103] The server then obtains the device identifier of the target device from the device based on the target link identifier, and calculates the device identifier and the service data to obtain the first service identifier corresponding to the target link identifier. Based on the first service identifier, the device identifier and the service data, the server generates the cloud server embedding data corresponding to the first service identifier.

[0104] It should be noted that the target link identifier and the first service identifier correspond to each other, and the first service identifier corresponds to the cloud server data points. Therefore, the target link identifier, the first service identifier, and the cloud service data points are all in a corresponding relationship.

[0105] In step S400 of some embodiments, the business data is sent to the software development tool on the device side, and the cloud server data points are sent to the log service system.

[0106] It is understandable that after step S300 is completed, in which the cloud server receives the initial link identifier, generates business data based on the initial link identifier, and generates cloud server embedding data based on the business data, the specific execution steps can be: the server sends the business data to the software development tool on the device side.

[0107] More specifically, the server also sends the cloud server embedding data, the first business identifier, and the target link identifier to the log service system.

[0108] It should be noted that the software development tool is only responsible for data forwarding and does not have data parsing capabilities. Therefore, the software development tool forwards the received business data to the processing program on the device side, so as to parse and process the business data.

[0109] In step S500 of some embodiments, when the software development tool on the device receives the business data, it generates device tracking data based on the business data and sends the device tracking data to the log service system.

[0110] It is understandable that after completing step S400, which sends the business data to the software development tool on the device and sends the cloud server data to the log service system, the specific execution steps can be as follows: when the server receives the business data from the software development tool on the device, the server forwards the business data from the software development tool to the processing program on the device, thereby processing the business data to obtain target business data. Based on the target business data, the server obtains the device identifier of the target device. The server calculates the device identifier and the target business data to obtain a second business identifier. Based on the second business identifier, the device identifier, and the target business data, the server generates device data corresponding to the second business identifier.

[0111] It should be noted that after generating the device tracking data, the device tracking data and the second business identifier are sent to the log service system.

[0112] It should be further noted that the device embedding data corresponds to the second business identifier.

[0113] In step S600 of some embodiments, when the log service system receives the link tracking data, the cloud server tracking data, and the device tracking data, it performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data based on the initial link identifier to generate target log data.

[0114] It is understandable that after step S500, where the software development tool on the device receives the business data, generates device tracking data based on the business data, and sends the device tracking data to the log service system, the specific execution steps can be as follows: when the log service system receives the link tracking data, the cloud server tracking data, the initial link identifier, and the target link identifier, the server determines the link relationship between the link tracking data corresponding to the initial link identifier and the cloud server tracking data corresponding to the target link identifier based on the initial link identifier and the target link identifier.

[0115] When the log service system receives the cloud server data, the device data, the first service identifier, and the second service identifier, the server determines the log relationship between the cloud server data corresponding to the first service identifier and the device data corresponding to the second service identifier based on the first service identifier and the second service identifier.

[0116] Based on the link relationship and the log relationship, the server performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data to generate the target log data.

[0117] It should be noted that the complete target log data is obtained by associating the link logs when the SDK cannot be updated, and it is used for data statistics or troubleshooting.

[0118] In some embodiments of this application, generating service data based on the initial link identifier includes:

[0119] The initial link identifier is processed to obtain the target link identifier;

[0120] The service data is generated based on the target link identifier.

[0121] It is understandable that the server stores the initial link identifier A to obtain the target link identifier A1. Specifically, the initial link identifier A is stored in the cloud database of the cloud server to obtain the target link identifier A1, and business data is generated based on the target link identifier A1.

[0122] Business data includes request headers and business data body. An example of business data is: The target device, a smart air conditioner, is set to heating mode at 25 degrees Celsius.

[0123] In some embodiments of this application, generating cloud server tracking data based on the business data includes:

[0124] Based on the target link identifier, obtain the device identifier of the target device from the device end;

[0125] Calculate the device identifier and the service data to obtain a first service identifier corresponding to the target link identifier;

[0126] Based on the first service identifier, the device identifier, and the service data, cloud server embedding data corresponding to the first service identifier is generated.

[0127] Understandably, the server obtains the device identifier of the target device from the target device on the device side based on the target link identifier A1.

[0128] It should be noted that the device identifier is either the device ID or the client ID.

[0129] After obtaining the device identifier of the target device, the server uses a preset algorithm to calculate the device identifier and business data to generate a first business identifier M. Then, based on the first business identifier, the device identifier, and the business data, the server generates cloud server embedding data E corresponding to the first business identifier.

[0130] It should be further noted that this preset algorithm is a pre-built algorithm for generating business identifiers within the cloud server, and no further limitations are imposed here.

[0131] The cloud service data E includes at least the first business identifier data, device identifier data, and business data, as well as the time data for receiving and sending the first business identifier data, device identifier data, and business data.

[0132] In some embodiments of this application, generating device tracking data based on the business data includes:

[0133] The business data is processed to obtain the target business data;

[0134] Based on the target business data, obtain the device identifier of the target device;

[0135] A second service identifier is obtained by calculating the device identifier and the target service data.

[0136] Based on the second service identifier, the device identifier, and the target service data, device embedding data corresponding to the second service identifier is generated.

[0137] Understandably, the server first sends business data from the cloud server to the device. After receiving the business data, the software development tools on the device forward the data to the processing program on the device, so that the processing program can parse and process the business data to obtain the target business data.

[0138] Based on the target business data, the server obtains the device identifier of the target device from the target device on the device side, and calculates the second business identifier N using the device identifier and the target business data using the device's preset algorithm. The server then automatically generates device tracking data F based on the second business identifier N, the device identifier, and the target business data.

[0139] It should be noted that the device embedding data F includes at least the second service identification data, the device identification data, and the target service data, as well as the time data for receiving, sending, and processing the second service identification data, the device identification data, and the target service data.

[0140] It should be further noted that the second business identifier N and the device embedding data F are corresponding.

[0141] In some embodiments of this application, after the step of generating the cloud server embedding data corresponding to the first service identifier based on the first service identifier, the device identifier, and the service data, the method includes:

[0142] The target link identifier and the first service identifier corresponding to the target link identifier are sent to the log service system.

[0143] It is understood that after the server generates the cloud server tracking data corresponding to the first service identifier based on the first service identifier, the device identifier, and the service data, the server sends the target link identifier A1 and the first service identifier M corresponding to the target link identifier to the log service system for associating the link tracking data D and the cloud server tracking data E in the log service system.

[0144] In some embodiments of this application, after the step of generating device embedding data corresponding to the second service identifier based on the second service identifier, the device identifier, and the target service data, the method includes:

[0145] The second service identifier is sent to the log service system.

[0146] It is understandable that after the server generates device tracking data corresponding to the second service identifier based on the second service identifier, the device identifier, and the target service data, the server will also send the second service identifier N to the log service system for associating the corresponding cloud server tracking data E and device tracking data F according to the first service identifier M and the second service identifier N.

[0147] In some embodiments of this application, when the log service system receives the link tracking data, the cloud server tracking data, and the device tracking data, based on the initial link identifier, performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data to generate target log data, including:

[0148] When the log service system receives the link tracking data, the cloud server tracking data, the initial link identifier, and the target link identifier, it determines the link relationship between the link tracking data corresponding to the initial link identifier and the cloud server tracking data corresponding to the target link identifier based on the initial link identifier and the target link identifier.

[0149] When the log service system receives the cloud server data, the device data, the first service identifier, and the second service identifier, it determines the log relationship between the cloud server data corresponding to the first service identifier and the device data corresponding to the second service identifier based on the first service identifier and the second service identifier.

[0150] Based on the link relationship and the log relationship, the link tracking data, the cloud server tracking data, and the device tracking data are correlated to generate the target log data.

[0151] Understandably, the specific execution steps can be as follows: when the log service system receives the link tracking data, the cloud server tracking data, the initial link identifier, and the target link identifier, the server first compares the initial link identifier and the target link identifier. If the initial link identifier and the target link identifier are the same, a first comparison result is obtained, and the first association relationship between the link tracking data and the cloud server tracking data is determined based on the first comparison result. If the initial link identifier and the target link identifier are different, a second comparison result is obtained, and the second association relationship between the link tracking data and the cloud server tracking data is determined based on the second comparison result.

[0152] When the server receives the cloud server tracking data, the device tracking data, the first service identifier, and the second service identifier from the log service system, it will also compare the first service identifier and the second service identifier. If the first service identifier and the second service identifier are the same, a third comparison result is obtained, and the third association relationship between the cloud server tracking data and the device tracking data is determined based on the third comparison result. If the first service identifier and the second service identifier are different, a fourth comparison result is obtained, and the fourth association relationship between the cloud server tracking data and the device tracking data is determined based on the fourth comparison result.

[0153] Based on the first association relationship and the third association relationship, the server performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data to generate the target log data.

[0154] In some embodiments of this application, the link relationship includes at least: a first association relationship and a second association relationship;

[0155] The step of determining the link relationship between the link tracking data corresponding to the initial link identifier and the cloud server tracking data corresponding to the target link identifier based on the initial link identifier and the target link identifier includes:

[0156] The initial link identifier and the target link identifier are compared and processed.

[0157] If the initial link identifier and the target link identifier are the same, a first comparison result is obtained, and based on the first comparison result, the first association relationship between the link tracking data and the cloud server tracking data is determined.

[0158] If the initial link identifier and the target link identifier are different, a second comparison result is obtained, and based on the second comparison result, the second association relationship between the link tracking data and the cloud server tracking data is determined.

[0159] When the server receives the link tracking data D, the cloud server tracking data E, the initial link identifier A, and the target link identifier A1 from the log service system, it compares the initial link identifier A and the target link identifier A1. If the initial link identifier A and the target link identifier A1 are the same, a first comparison result is obtained. Based on the first comparison result, the first association relationship between the link tracking data D and the cloud server tracking data E is determined, and the link tracking data D and the cloud server tracking data E are associated together according to the first association relationship.

[0160] It should be noted that if the initial link identifier A and the target link identifier A1 are different, a second comparison result is obtained, and based on the second comparison result, the second association relationship between the link tracking data and the cloud server tracking data is determined. According to the second association relationship, the link tracking data D and the cloud server tracking data E cannot be associated together.

[0161] In some embodiments of this application, the log relationship includes at least: a third association relationship and a fourth association relationship;

[0162] The step of determining the log relationship between the cloud server embedding data corresponding to the first service identifier and the device embedding data corresponding to the second service identifier based on the first service identifier and the second service identifier includes:

[0163] The first service identifier and the second service identifier are compared and processed.

[0164] If the first service identifier and the second service identifier are the same, a third comparison result is obtained, and based on the third comparison result, the third association relationship between the cloud server embedding data and the device embedding data is determined;

[0165] If the first service identifier and the second service identifier are different, a fourth comparison result is obtained, and based on the fourth comparison result, the fourth association relationship between the cloud server embedding data and the device embedding data is determined.

[0166] It is understandable that when the server log service system receives the cloud server tracking data, the device tracking data, the first service identifier, and the second service identifier, it compares the first service identifier M and the second service identifier N. If the first service identifier M and the second service identifier N are the same, a third comparison result is obtained. Based on the third comparison result, the third association relationship between the cloud server tracking data E and the device tracking data F is determined, and the cloud server tracking data E and the device tracking data F are associated together based on the third association relationship.

[0167] It should be noted that if the first service identifier M and the second service identifier N are different, a fourth comparison result is obtained, and based on the fourth comparison result, the fourth association relationship between the cloud server tracking data E and the device tracking data F is determined. According to the fourth association relationship, the cloud server tracking data E and the device tracking data F cannot be associated together.

[0168] In some embodiments of this application, the step of associating the link tracking data, the cloud server tracking data, and the device tracking data based on the link relationship and the log relationship to generate the target log data includes:

[0169] Based on the first association relationship and the third association relationship, the link tracking data, the cloud server tracking data, and the device tracking data are associated to generate the target log data.

[0170] Understandably, the server first associates the link tracking data D and the cloud server tracking data E together based on the first association relationship, and then associates the cloud server tracking data E and the device tracking data F together based on the third association relationship, thereby linking the link tracking data D, the cloud server tracking data E, and the device tracking data F together to generate target log data.

[0171] like Figure 3The diagram shown is a second flowchart of a link log association method provided in this application. The specific execution steps are as follows: the server first obtains the initial link identifier A from the APP application, then generates the corresponding link tracking data D based on the initial link identifier A, and then sends the initial link identifier A to the cloud server, and sends the initial link identifier A and the link tracking data D to the log service system.

[0172] Upon receiving the initial link identifier A from the cloud server, the server processes the initial link identifier A to obtain a target link identifier A1. Based on the target link identifier A1, it generates service data and obtains the device identifier of the target device from the device terminal based on the target link identifier A1. Then, it performs calculations on the device identifier and the service data to obtain a first service identifier M. Based on the first service identifier M, the device identifier, and the service data, it generates cloud server embedding data E. The server sends the service data to the data communication SDK on the device terminal and sends the target link identifier A1, the first service identifier M, and the cloud server embedding data E to the log service system.

[0173] When the server receives the service data via the data communication SDK on the device side, it forwards the service data to the processing program on the device side. Upon receiving the service data, the processing program on the device side processes the service data to obtain target service data, and based on the target service data, obtains the device identifier of the target device. It then calculates a second service identifier N based on the device identifier N, the device identifier, and the target service data. Finally, the server sends the second service identifier N and the device tracking data F to the log service system.

[0174] Upon receiving the initial link identifier A and the target link identifier A1 from the log service system, the server performs a first comparison process on the initial link identifier A and the target link identifier A1, resulting in a first comparison result where the initial link identifier A and the target link identifier A1 are identical. Based on the first comparison result, a first association relationship is generated between the link tracking data D corresponding to the initial link identifier A and the cloud server tracking data E corresponding to the target link identifier A1.

[0175] When the server receives the first service identifier M and the second service identifier N from the log service system, it compares the first service identifier M and the second service identifier N to obtain a third comparison result where the first service identifier M and the second service identifier N are the same. Based on the third comparison result, a third association relationship is generated between the cloud server embedded data E corresponding to the first service identifier M and the device embedded data F corresponding to the second service identifier N.

[0176] The server first associates the link tracking data D and the cloud server tracking data E together according to the first association relationship, and then associates the cloud server tracking data E and the device tracking data F together according to the third association relationship, thereby linking the link tracking data D, the cloud server tracking data E, and the device tracking data F together to generate target log data.

[0177] It should be noted that after generating the second service identifier N, the server will also send the service data and the second service identifier N to the display screen to display the corresponding data.

[0178] This application provides a link log association method and a link log association device. The link log association method is applied to a server, which is connected to an application, a cloud server, a device, and a log service system via a network. The link log association method involves obtaining an initial link identifier from the application; sending the initial link identifier to the cloud server; and sending the initial link identifier and corresponding link tracking data to the log service system. Upon receiving the initial link identifier, the cloud server generates business data based on the initial link identifier and generates cloud server tracking data based on the business data. The process involves several steps: First, the system sends the business data to the software development tool on the device side and sends the cloud server's data to the log service system. Second, upon receiving the business data, the software development tool on the device side generates device-level data based on the business data and sends this data to the log service system. Third, upon receiving the link-level data, the cloud server's data, and the device-level data, the log service system performs association processing based on the initial link identifier to generate target log data. This addresses the deficiency in existing technologies where complete link logs cannot be obtained when the SDK cannot be updated, enabling the association of link logs to generate complete target log data even when the SDK cannot be updated.

[0179] The following describes a link log association device provided in this application. The link log association device described below can be referred to in correspondence with the link log association method described above, and will not be repeated here.

[0180] like Figure 4 The diagram shown is a structural schematic of a link log association device provided in this application. The link log association device is applied to a server, which is connected to an application terminal, a cloud server, a device terminal, and a log service system via a network.

[0181] The link log association device includes:

[0182] The initial link identifier acquisition module 410 is used to acquire the initial link identifier of the application.

[0183] The first sending module 420 is used to send the initial link identifier to the cloud server, and send the initial link identifier and the link embedding data corresponding to the initial link identifier to the log service system;

[0184] The cloud server data generation module 430 is used to generate business data based on the initial link identifier when the cloud server receives the initial link identifier, and generate cloud server data based on the business data.

[0185] The second sending module 440 is used to send the business data to the software development tool on the device side and send the cloud server data to the log service system.

[0186] The device data generation module 450 is used to generate device data based on the business data when the software development tool on the device receives the business data, and send the device data to the log service system.

[0187] The target log data generation module 460 is used to generate target log data based on the initial link identifier when the log service system receives the link tracking data, the cloud server tracking data, and the device tracking data, and performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data.

[0188] This application provides a link log association method and a link log association device to solve the defect in the prior art that complete link logs cannot be obtained when the SDK cannot be updated, and realizes the association of link logs to generate complete target log data when the SDK cannot be updated.

[0189] Figure 5An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 5 As shown, the electronic device may include: a processor 510, a communication interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other through the communication bus 540. The processor 510 can call logical instructions in the memory 530 to execute a link log association method provided by the above methods. This method includes: obtaining an initial link identifier from the application; sending the initial link identifier to the cloud server and sending the initial link identifier and corresponding link tracking data to the log service system; when the cloud server receives the initial link identifier, generating business data based on the initial link identifier and generating cloud server tracking data based on the business data; sending the business data to the software development tool on the device side and sending the cloud server tracking data to the log service system; when the software development tool on the device side receives the business data, generating device tracking data based on the business data and sending the device tracking data to the log service system; when the log service system receives the link tracking data, the cloud server tracking data, and the device tracking data, performing association processing on the link tracking data, the cloud server tracking data, and the device tracking data based on the initial link identifier to generate target log data.

[0190] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0191] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a computer-readable storage medium. When the computer program is executed by a processor, the computer is able to execute a link log association method provided by the above methods.

[0192] In another aspect, this application also provides a computer-readable storage medium comprising a stored program, wherein the program executes a link log association method provided by the methods described above when it runs.

[0193] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0194] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

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

Claims

1. A link log association method, characterized in that, It is applied to servers, which are connected to the application client, cloud server, device client and log service system via network respectively; The link log association method includes: Obtain the initial link identifier from the application. The initial link identifier is sent to the cloud server, and the initial link identifier and the link tracking data corresponding to the initial link identifier are sent to the log service system; Upon receiving the initial link identifier, the cloud server generates business data based on the initial link identifier and generates cloud server data points based on the business data. The business data is sent to the software development tool on the device, and the cloud server data is sent to the log service system. When the software development tool on the device receives the business data, it generates device tracking data based on the business data and sends the device tracking data to the log service system. Upon receiving the link tracking data, cloud server tracking data, and device tracking data, the log service system performs association processing on the link tracking data, cloud server tracking data, and device tracking data based on the initial link identifier to generate target log data.

2. The link log association method according to claim 1, characterized in that, The generation of service data based on the initial link identifier includes: The initial link identifier is processed to obtain the target link identifier; The service data is generated based on the target link identifier.

3. The link log association method according to claim 2, characterized in that, The step of generating cloud server event tracking data based on the business data includes: Based on the target link identifier, obtain the device identifier of the target device from the device end; Calculate the device identifier and the service data to obtain a first service identifier corresponding to the target link identifier; Based on the first service identifier, the device identifier, and the service data, cloud server embedding data corresponding to the first service identifier is generated.

4. The link log association method according to claim 3, characterized in that, The process of generating device tracking data based on the business data includes: The business data is processed to obtain the target business data; Based on the target business data, obtain the device identifier of the target device; A second service identifier is obtained by calculating the device identifier and the target service data; Based on the second service identifier, the device identifier, and the target service data, device embedding data corresponding to the second service identifier is generated.

5. The link log association method according to claim 3, characterized in that, After the step of generating the cloud server embedding data corresponding to the first service identifier based on the first service identifier, the device identifier, and the service data, the method includes: The target link identifier and the first service identifier corresponding to the target link identifier are sent to the log service system.

6. The link log association method according to claim 4, characterized in that, After the step of generating device tracking data corresponding to the second service identifier based on the second service identifier, the device identifier, and the target service data, the method includes: The second service identifier is sent to the log service system.

7. The link log association method according to claim 4, characterized in that, Upon receiving the link tracking data, cloud server tracking data, and device tracking data from the log service system, the system performs association processing on the link tracking data, cloud server tracking data, and device tracking data based on the initial link identifier to generate target log data, including: When the log service system receives the link tracking data, the cloud server tracking data, the initial link identifier, and the target link identifier, it determines the link relationship between the link tracking data corresponding to the initial link identifier and the cloud server tracking data corresponding to the target link identifier based on the initial link identifier and the target link identifier. When the log service system receives the cloud server data, the device data, the first service identifier, and the second service identifier, it determines the log relationship between the cloud server data corresponding to the first service identifier and the device data corresponding to the second service identifier based on the first service identifier and the second service identifier. Based on the link relationship and the log relationship, the link tracking data, the cloud server tracking data, and the device tracking data are correlated to generate the target log data.

8. The link log association method according to claim 7, characterized in that, The link relationship includes at least: a first association relationship and a second association relationship; The step of determining the link relationship between the link tracking data corresponding to the initial link identifier and the cloud server tracking data corresponding to the target link identifier based on the initial link identifier and the target link identifier includes: The initial link identifier and the target link identifier are compared and processed. If the initial link identifier and the target link identifier are the same, a first comparison result is obtained, and based on the first comparison result, the first association relationship between the link tracking data and the cloud server tracking data is determined. If the initial link identifier and the target link identifier are different, a second comparison result is obtained, and based on the second comparison result, the second association relationship between the link tracking data and the cloud server tracking data is determined.

9. The link log association method according to claim 8, characterized in that, The log relationships include at least: a third association relationship and a fourth association relationship; The step of determining the log relationship between the cloud server embedding data corresponding to the first service identifier and the device embedding data corresponding to the second service identifier based on the first service identifier and the second service identifier includes: The first service identifier and the second service identifier are compared and processed. If the first service identifier and the second service identifier are the same, a third comparison result is obtained, and based on the third comparison result, the third association relationship between the cloud server embedding data and the device embedding data is determined; If the first service identifier and the second service identifier are different, a fourth comparison result is obtained, and based on the fourth comparison result, the fourth association relationship between the cloud server embedding data and the device embedding data is determined.

10. The link log association method according to claim 9, characterized in that, The process of associating the link tracking data, the cloud server tracking data, and the device tracking data based on the link relationship and the log relationship to generate the target log data includes: Based on the first association relationship and the third association relationship, the link tracking data, the cloud server tracking data, and the device tracking data are associated to generate the target log data.

11. A link log association device, characterized in that, It is applied to servers, which are connected to the application client, cloud server, device client and log service system via network respectively; The link log association device includes: The module for obtaining the initial link identifier is used to obtain the initial link identifier from the application. The first sending module is used to send the initial link identifier to the cloud server, and to send the initial link identifier and the link tracking data corresponding to the initial link identifier to the log service system; A cloud server event tracking data generation module is used to generate business data based on the initial link identifier when the cloud server receives the initial link identifier, and generate cloud server event tracking data based on the business data. The second sending module is used to send the business data to the software development tool on the device side and send the cloud server data to the log service system. A device tracking data generation module is used to generate device tracking data based on the business data received by the software development tool on the device side, and send the device tracking data to the log service system. The target log data generation module is used to generate target log data based on the initial link identifier when the log service system receives the link tracking data, the cloud server tracking data, and the device tracking data, and performs association processing on the link tracking data, the cloud server tracking data, and the device tracking data.

Images