CN113377643B - SDK monitoring and tracking method and device and readable storage medium - Google Patents
SDK monitoring and tracking method and device and readable storage medium Download PDFInfo
- Publication number
- CN113377643B CN113377643B CN202110753021.0A CN202110753021A CN113377643B CN 113377643 B CN113377643 B CN 113377643B CN 202110753021 A CN202110753021 A CN 202110753021A CN 113377643 B CN113377643 B CN 113377643B
- Authority
- CN
- China
- Prior art keywords
- sdk
- monitoring
- sdks
- service system
- general
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a monitoring and tracking method and device of an SDK and a readable storage medium. The monitoring and tracking method of the SDK comprises the following steps: t1: defining a monitoring SDK; t2: defining one or more generic SDKs; each general SDK introduces a monitoring SDK when defined; t3: introducing a monitoring SDK and one or more universal SDKs in the development stage of the business system; the service system acquires key information of all general SDKs in the system by monitoring the SDKs and timing tracking; t4: and the service system reports the key information of all the universal SDKs to the server. Tracking statistics of version change conditions of the SDK is achieved through the introduction of the monitoring SDK, distribution conditions of the general SDK of the high-risk version in a business system can be timely and accurately found, timely repair is achieved before loopholes are triggered, production accidents are avoided, and losses of enterprises and clients are avoided.
Description
Technical Field
The application relates to an information system technology in the field of computers, in particular to a monitoring and tracking method and device of an SDK and a readable storage medium.
Background
In the development of business systems, engineering code typically needs to incorporate some generic SDKs, such as object store SDKs, cache SDKs, audio video SDKs, and so on. After the business system is on line, when a certain version of SDK is found to have a major defect causing production accidents, we cannot quickly and accurately grasp the influence range of the version of SDK (cannot know which business systems use the version with major defect), and the defect cannot be quickly repaired, so that the production accidents are finally caused, and the loss is caused to enterprises and clients.
Disclosure of Invention
In order to timely and accurately grasp the service condition of the SDK and grasp the distribution condition of the defect version SDK in real time, the scheme provides a technical means for regularly collecting the information such as the version, the name and the like of the general SDK used in the service system and reporting the information to the monitoring server.
In one aspect, the application provides a method for monitoring and tracking an SDK, which comprises the following steps:
t1: developer a defines a monitoring SDK;
t2: developer B defines one or more generic SDKs; each general SDK introduces a monitoring SDK when defined;
t3: developer C introduces one or more universal SDKs in the development stage of the service system; the service system acquires key information of all general SDKs in the system by monitoring the SDKs and timing tracking;
t4: and the monitoring SDK reports the key information of all the universal SDKs to the server.
Based on the scheme, the method further comprises the following steps:
in the step T1, defining a monitoring SDK specifically includes: an abstract interface is defined in the monitoring SDK, and an abstract method comprising acquiring the name of the current general SDK and defining the version number of the general SDK is defined in the abstract interface.
Based on the scheme, the method further comprises the following steps:
in the step T1, the introducing the monitoring SDK in the definition of the generic SDK specifically includes: and realizing an abstract interface in the universal SDK, and acquiring the name of the current universal SDK and the version number of the current universal SDK.
Based on the scheme, the method further comprises the following steps:
in the step T1, defining a monitoring SDK specifically includes: defining a timing task in the monitoring SDK, and searching the timing task to realize the general SDK of the abstract interface;
based on the scheme, the method further comprises the following steps:
in step T3, the service system tracks and obtains the names and version numbers of all the universal SDKs in the service system by indirectly introducing the monitoring SDKs.
Based on the scheme, the method further comprises the following steps:
in the step T4, the service system reports the service system ID and the name and version number of the generic SDK to the server.
Based on the scheme, the method further comprises the following steps:
the server side receives the report information from a plurality of service systems at the same time, and the method further comprises the steps of:
t5: the server receives the monitoring data reported by the monitoring SDK of each service system and stores the monitoring data in a database; and inquiring the name and version number of the target general SDK at the server side to obtain the corresponding service system ID.
Based on the scheme, the method further comprises the following steps:
the server side receives reporting information from a plurality of service systems in different terminals at the same time;
each service system reports the name and version number of the current terminal IP, the service system ID and the general SDK to a server;
in step T5, the name and version number of the target generic SDK are queried at the server, and the corresponding service system ID and terminal IP may be obtained.
In a second aspect, the present application provides a monitoring and tracking device for an SDK, including a memory and a processor;
the memory is used for storing a computer program;
the processor is used for executing the program to realize each step of the SDK monitoring and tracking method.
In a third aspect, the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of a method for monitoring and tracking an SDK as described above.
Compared with the prior art, the application has the following advantages and beneficial effects:
the tracking statistics of the version use condition of the SDK is realized by monitoring the introduction of the SDK, the distribution condition of the general SDK of the high-risk version in the service system can be timely and accurately found, the service system is timely repaired before the vulnerability is triggered, the production accident is avoided, and the loss of enterprises and clients is avoided.
Drawings
In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present application, the drawings that are needed in the examples will be briefly described below, it being understood that the following drawings only illustrate some examples of the present application and therefore should not be considered as limiting the scope, and that other related drawings may be obtained from these drawings without inventive effort for a person skilled in the art. In the drawings:
FIG. 1 is a schematic diagram of monitoring SDK functions;
FIG.2isaschematicdiagramofanSDKwithinabusinessSYSTEMBIZ-SYSTEM-A;
FIG. 3 is a schematic diagram of an SDK within a business SYSTEM BIZ-SYSTEM-B;
fig. 4 is a schematic diagram of a relationship among a terminal, a service system, and a server.
The achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
For the purpose of making apparent the objects, technical solutions and advantages of the present application, the present application will be further described in detail with reference to the following examples and the accompanying drawings, wherein the exemplary embodiments of the present application and the descriptions thereof are for illustrating the present application only and are not to be construed as limiting the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Those of ordinary skill in the art will appreciate that implementing all or part of the above facts and methods may be accomplished by a program to instruct related hardware, the program involved or the program may be stored in a computer readable storage medium, the program when executed comprising the steps of: the corresponding method steps are introduced at this time, and the storage medium may be a ROM/RAM, a magnetic disk, an optical disk, or the like.
Examples:
as shown in fig. 1, in the present embodiment, two general SDKs are provided inside the enterprise, the first is an object storage SDK, the name: "oss-sdk", current version number: 0.1; the second is an audio processing SDK, name: "alice-sdk", there are two versions: 1.1 and 1.2.
The development Role1 designs and develops the function of monitoring the SDK, as shown in fig. 1, mainly includes: the method comprises the steps of obtaining an abstract interface of general SDK key information and a timing searching and reporting function, wherein the interface comprises the abstract method: obtain a generic SDK name and obtain a generic SDK version number.
The development Role Role2 introduces a monitoring SDK in the development stage of the 0.1 version of the object storage SDK, and realizes two abstract methods in the monitoring SDK: acquiring the name of the object storage SDK: "oss-sdk" and the version number of the get object store sdk: 0.1;
the development Role Role2 introduces a monitoring SDK in the development stage of version 1.1 of the audio processing SDK, and realizes two abstract methods in the monitoring SDK: acquiring the name of the audio processing SDK: "alice-SDK" and get audio processing SDK version number: "1.1";
in the development stage of version 1.2 of the audio processing SDK, a monitoring SDK is introduced, and two methods in the monitoring SDK are realized: acquiring the name of the audio processing SDK: "alice-SDK" and get audio processing SDK version number: 1.2;
asshowninfig.2,thedevelopmentRolerow3introducesthefirstaudioprocessingsdk1.1versionandthefirstobjectstoragesdk0.1versioninthedevelopmentstageoftheserviceSYSTEMBIZ-SYSTEM-a,atthistime,themonitoringsdkisalsoindirectlyintroduced,andtheserviceSYSTEMisstartedonthefirstterminal192.168.0.1. When the monitoring SDK executes the search task at regular time, scanning the universal SDK used by the current service system: the first object storage SDK and the first audio processing SDK call two abstract methods respectively realized: the method for acquiring the SDK name by the first object storage SDK returns to the 'oss-SDK' version number, and the method for acquiring the version number returns to '0.1'; thefirstaudioprocessingSDKreturnsamethodforacquiringthenameoftheSDKto'voice-SDK',themethodforacquiringtheversionnumberreturnsto'1.1'tomonitortheSDK,andtheresults(BIZ-SYSTEM-A,terminalIP:192.168.0.1,voice-SDK,1.1)and(BIZ-SYSTEM-A,192.168.0.1,oss-SDK,0.1)arereportedtoamonitoringserver.
As shown in fig. 3, the development Role row 3 introduces the 1.2 version of the second audio processing SDK and the 0.1 version of the second object storage SDK in the development stage of the service SYSTEM BIZ-SYSTEM-B, and at this time, the monitoring SDK is also introduced, and as shown in fig. 4, the service SYSTEM is started on the second terminal 192.168.0.2 and the first terminal 192.168.0.1, respectively. When monitoring SDKs on two terminals execute search tasks at fixed time, scanning the universal SDKs used by the current service system: the second object stores SDK and second audio processing SDK, respectively calls two abstract methods respectively realized: the second object storage SDK calls the method for acquiring the name of the SDK to return to 'oss-SDK', and calls the method for acquiring the version number to return to '0.1'; the second audio processing SDK calls the get SDK name method back to "voice-SDK", and calls the get version number method back to "1.2". The monitoring SDK on 192.168.0.2 will result (BIZ-SYSTEM-B, terminal IP:192.168.0.2, oss-SDK, 0.1). The monitoring SDK on 192.168.0.1 reports the results (BIZ-SYSTEM-B, 192.168.0.1, oss-SDK, 0.1) and (BIZ-SYSTEM-B, 192.168.0.1, voice-SDK, 1.2) to the monitoring server.
The monitoring server receives the data reported by the monitoring SDK and persists to the database, and records as follows:
| BIZ-SYSTEM-A | 192.168.0.1 | oss-sdk | 0.1 |
| BIZ-SYSTEM-A | 192.168.0.1 | voice-sdk | 1.1 |
| BIZ-SYSTEM-B | 192.168.0.2 | oss-sdk | 0.1 |
| BIZ-SYSTEM-B | 192.168.0.2 | voice-sdk | 1.2 |
| BIZ-SYSTEM-B | 192.168.0.1 | oss-sdk | 0.1 |
| BIZ-SYSTEM-B | 192.168.0.1 | voice-sdk | 1.2 |
when the 0.1 version of oss-sdk is found to be defective, the server UI page searches for which business systems use oss-sdk of 0.1, subject to "oss-sdk" and "0.1".
| BIZ-SYSTEM-A | 192.168.0.1 | oss-sdk | 0.1 |
| BIZ-SYSTEM-B | 192.168.0.2 | oss-sdk | 0.1 |
| BIZ-SYSTEM-B | 192.168.0.1 | oss-sdk | 0.1 |
When the 1.2 version of alice-sdk is found to be defective, a server UI page searches for which business systems use 1.2 of alice-sdk, subject to "alice-sdk" and "1.2".
| BIZ-SYSTEM-B | 192.168.0.2 | voice-sdk | 1.2 |
| BIZ-SYSTEM-B | 192.168.0.1 | voice-sdk | 1.2 |
Notifying the system responsible person to correct in time. The foregoing embodiments have been provided for the purpose of illustrating the general principles of the present application, including by way of example only, and not by way of limitation, the application may be embodied in any form and method for practicing the application, including as follows, in any form and method for practicing the application.
Claims (7)
1. The monitoring and tracking method of the SDK is characterized by comprising the following steps of:
t1: defining a monitoring SDK, defining an abstract interface in the monitoring SDK, and defining an abstract method comprising obtaining the name of the current general SDK and defining the version number of the general SDK in the abstract interface; defining a timing task in the monitoring SDK, and searching the timing task to realize the general SDK of the abstract interface;
t2: defining one or more generic SDKs; each general SDK introduces a monitoring SDK when defined;
t3: the business system introduces one or more universal SDKs in the development stage; the service system acquires key information of all general SDKs in the system by monitoring the SDKs and timing tracking; the service system tracks and acquires the names and version numbers of all the universal SDKs in the service system through indirectly introduced monitoring SDKs;
t4: and the monitoring SDK reports the key information of all the universal SDKs to the server.
2. The method according to claim 1, wherein in the step T1, the step of introducing the monitoring SDK into the generic SDK during definition specifically comprises: and realizing an abstract interface in the universal SDK, and acquiring the name of the current universal SDK and the version number of the current universal SDK.
3. The method according to claim 1, wherein in the step T4, the service system reports the service system ID and the name and version number of the generic SDK to the server.
4. The method for monitoring and tracking an SDK according to claim 3, wherein the server side receives reporting information from a plurality of service systems at the same time, further comprising the steps of:
t5: the server receives the monitoring data reported by the monitoring SDK of each service system and stores the monitoring data in a database; and inquiring the name and version number of the target general SDK at the server side to obtain the corresponding service system ID.
5. The method for monitoring and tracking the SDK according to claim 4, wherein the server side receives reporting information from a plurality of service systems in different terminals at the same time;
each service system reports the name and version number of the current terminal IP, the service system ID and the general SDK to a server;
in step T5, the name and version number of the target generic SDK are queried at the server, and the corresponding service system ID and terminal IP may be obtained.
6. A monitoring and tracking device for an SDK, comprising a memory and a processor;
the memory is used for storing a computer program;
the processor is configured to execute the program to implement the steps of the monitoring and tracking method of the SDK according to any one of claims 1 to 5.
7. A computer-readable storage medium, characterized in that a computer program is stored, which, when being executed by a processor, implements the steps of a monitoring and tracking method of an SDK according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110753021.0A CN113377643B (en) | 2021-07-02 | 2021-07-02 | SDK monitoring and tracking method and device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110753021.0A CN113377643B (en) | 2021-07-02 | 2021-07-02 | SDK monitoring and tracking method and device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113377643A CN113377643A (en) | 2021-09-10 |
| CN113377643B true CN113377643B (en) | 2023-08-25 |
Family
ID=77580891
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110753021.0A Active CN113377643B (en) | 2021-07-02 | 2021-07-02 | SDK monitoring and tracking method and device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113377643B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017005037A1 (en) * | 2015-07-03 | 2017-01-12 | 中兴通讯股份有限公司 | Data usage control and control processing method, device and terminal |
| CN106557691A (en) * | 2016-10-12 | 2017-04-05 | 北京奇虎科技有限公司 | The device of third party's SDK methods, device and reinforcing installation kit in monitoring application |
| CN108235308A (en) * | 2017-12-27 | 2018-06-29 | 广东欧珀移动通信有限公司 | data reporting method, device, mobile terminal and computer-readable medium |
| CN108289118A (en) * | 2017-12-12 | 2018-07-17 | 北京奇艺世纪科技有限公司 | A kind of management method and device of distributed message stream |
| WO2018153207A1 (en) * | 2017-02-23 | 2018-08-30 | 腾讯科技（深圳）有限公司 | Data processing method, server, terminal, and system |
| CN110022307A (en) * | 2019-03-08 | 2019-07-16 | 视联动力信息技术股份有限公司 | A kind of control method of monitoring device and monitoring access server |
| CN111124891A (en) * | 2019-12-02 | 2020-05-08 | 腾讯科技（深圳）有限公司 | Access state detection method and device, storage medium and electronic device |
| CN112799925A (en) * | 2021-01-25 | 2021-05-14 | 北京嘀嘀无限科技发展有限公司 | Data acquisition method and device, electronic equipment and readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10025694B1 (en) * | 2016-12-22 | 2018-07-17 | SafeDK Mobile Ltd. | Monitoring activity of software development kits using stack trace analysis |
-
2021
- 2021-07-02 CN CN202110753021.0A patent/CN113377643B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017005037A1 (en) * | 2015-07-03 | 2017-01-12 | 中兴通讯股份有限公司 | Data usage control and control processing method, device and terminal |
| CN106557691A (en) * | 2016-10-12 | 2017-04-05 | 北京奇虎科技有限公司 | The device of third party's SDK methods, device and reinforcing installation kit in monitoring application |
| WO2018153207A1 (en) * | 2017-02-23 | 2018-08-30 | 腾讯科技（深圳）有限公司 | Data processing method, server, terminal, and system |
| CN108289118A (en) * | 2017-12-12 | 2018-07-17 | 北京奇艺世纪科技有限公司 | A kind of management method and device of distributed message stream |
| CN108235308A (en) * | 2017-12-27 | 2018-06-29 | 广东欧珀移动通信有限公司 | data reporting method, device, mobile terminal and computer-readable medium |
| CN110022307A (en) * | 2019-03-08 | 2019-07-16 | 视联动力信息技术股份有限公司 | A kind of control method of monitoring device and monitoring access server |
| CN111124891A (en) * | 2019-12-02 | 2020-05-08 | 腾讯科技（深圳）有限公司 | Access state detection method and device, storage medium and electronic device |
| CN112799925A (en) * | 2021-01-25 | 2021-05-14 | 北京嘀嘀无限科技发展有限公司 | Data acquisition method and device, electronic equipment and readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 袁博 ; 梁怡林 ; .STM32主控的GPS/GPRS移动终端定位跟踪系统.南阳理工学院学报.2018,(第02期),1-3节. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113377643A (en) | 2021-09-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110413634B (en) | Data query method, system, device and computer readable storage medium | |
| CN108063759B (en) | Web vulnerability scanning method | |
| CN109617745B (en) | Alarm prediction method, device, system and storage medium | |
| CN111355610A (en) | Exception handling method and device based on edge network | |
| US11809406B2 (en) | Event records in a log file | |
| CN110647562B (en) | Data query method and device, electronic equipment and storage medium | |
| CN106878038B (en) | Fault positioning method and device in communication network | |
| US9454561B2 (en) | Method and a consistency checker for finding data inconsistencies in a data repository | |
| CN108073611A (en) | The filter method and device of a kind of warning information | |
| CN111010318A (en) | Method and system for discovering loss of connection of terminal equipment of Internet of things and equipment shadow server | |
| CN112486640A (en) | Service processing method and device, electronic equipment and computer readable storage medium | |
| CN113377643B (en) | SDK monitoring and tracking method and device and readable storage medium | |
| CN106980617B (en) | Method and system for operating database based on JSON statement | |
| CN111427736A (en) | Log monitoring method, device, equipment and computer readable storage medium | |
| CN111061616A (en) | Alarm management method, device, communication equipment and storage medium | |
| CN113724074A (en) | Credit credit risk early warning method and device | |
| CN106095875B (en) | Method and device for improving ID of live broadcast terminal | |
| CN113656210A (en) | Processing method and device for error reporting information, server and readable storage medium | |
| US20060253426A1 (en) | Identifying duplicate entries in a historical database | |
| CN112328481A (en) | Automatic testing method, device and equipment for multi-task scene and storage medium | |
| CN108197147B (en) | Operation and maintenance method and device for number card database | |
| CN107688628B (en) | The common grouping construction method of relationship group data and device | |
| CN112905353A (en) | Service calling information generation method and device and storage medium | |
| CN112632281B (en) | Fusion delimitation method and device based on early warning complaint data | |
| US20230216727A1 (en) | Identification of root causes in data processing errors |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |