CN114928663A - Method and device for recognizing callback message - Google Patents
Method and device for recognizing callback message Download PDFInfo
- Publication number
- CN114928663A CN114928663A CN202210629307.2A CN202210629307A CN114928663A CN 114928663 A CN114928663 A CN 114928663A CN 202210629307 A CN202210629307 A CN 202210629307A CN 114928663 A CN114928663 A CN 114928663A
- Authority
- CN
- China
- Prior art keywords
- callback
- message
- upstream
- message information
- queue
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method for identifying callback messages, which comprises the following steps: when the target program is detected to be triggered, receiving an upstream callback message; after the successful receiving of the upstream callback message is confirmed, analyzing the upstream callback message by using an analysis algorithm to obtain message information; if the message information is successfully acquired, adding the message information into an upstream callback queue; if the message information can not be acquired, acquiring the message information by adopting a corresponding processing class and adding the message information into the upstream callback queue; and after the message information is added into the upstream callback queue, obtaining the message information from the upstream callback queue and writing the message information into a database or performing callback on downstream. The invention aims to provide a callback message identification method and device with the advantages of simplified codes, convenience and flexibility in development, high fault tolerance rate and low maintenance cost.
Description
Technical Field
The invention belongs to the field of data analysis, and particularly relates to a method and a device for recognizing callback messages.
Background
Generally, as an intermediary, when processing a callback message of an upstream API, a developer is required to write a corresponding Handler processing class for each upstream message to process, as shown in fig. 1, so as to extract information in the message from the callback message. Generally, there are many upstream messages, so that developers are required to write many processing classes correspondingly and frequently to process callback messages. This causes the following problems:
1. the code repetition degree is high: although a plurality of processing classes are written, the processing methods for each upstream callback message are not very different, and the redundancy condition of the code is serious;
2. the development cycle of the analysis message is long: different upstream callback message formats are different, and developers are required to perform coding analysis according to different upstream message formats;
3. if the callback message is changed, the code needs to be modified again: if the structure of the upstream callback message is changed, the corresponding processing class needs to be restarted and modified, so that the timely synchronization of the transaction result is influenced;
4. the fault tolerance rate is low: in the process of analyzing the upstream callback message, as long as the position analysis of the parameter is not correct or the encryption mode is mistakenly identified, the analysis of the callback message is mistaken;
5. the maintenance cost is high: whenever the structure of the upstream callback packet changes, the code needs to be modified and each node issues a restart, resulting in increased maintenance costs.
Disclosure of Invention
In view of the above disadvantages of the prior art, an object of the present invention is to provide a method and an apparatus for identifying a callback packet, which are simplified in code, convenient and flexible to develop, high in fault tolerance rate, and low in maintenance cost.
The patent scheme provides a method for identifying callback messages, which comprises the following steps:
when the target program is detected to be triggered, receiving an upstream callback message;
after the upstream callback message is confirmed to be successfully received, analyzing the upstream callback message by using an analysis algorithm to acquire message information;
if the message information is successfully acquired, adding the message information into an upstream callback queue;
if the message information can not be acquired, acquiring the message information by adopting a corresponding processing class and adding the message information into the upstream callback queue;
and after the message information is added into the upstream callback queue, obtaining the message information from the upstream callback queue and writing the message information into a database or performing callback on downstream.
Further, after the upstream callback packet is successfully received, analyzing the upstream callback packet by using an analysis algorithm to obtain packet information, including:
after the successful receiving of the upstream callback message is confirmed, judging the message type of the upstream callback message;
after the message type is obtained, selecting the corresponding analysis algorithm according to the message type;
and after the corresponding analysis algorithm is selected, analyzing the upstream callback message by using the analysis algorithm to acquire message information.
Further, the packet type includes JSON and XML.
Further, the determining the message type of the upstream callback message includes: and judging the message type of the upstream callback message by identifying keywords at the head and the tail of the upstream callback message.
Further, the parsing algorithm includes: and acquiring message information in the upstream callback message according to a preset key field.
Further, the key fields can be preset through a graphical interface.
Further, the upstream callback queue is a message queue.
Also provided is a device for identifying callback messages, comprising:
the receiving unit is used for receiving an upstream callback message when the target program is detected to be triggered;
the analysis unit is used for analyzing the upstream callback message by using an analysis algorithm to acquire message information after confirming that the upstream callback message is successfully received;
the access queue unit is used for adding the message information into an upstream callback queue if the message information is successfully acquired;
the exception handling unit is used for acquiring the message information by adopting a corresponding processing class and adding the message information into the upstream callback queue if the message information cannot be acquired;
and the message processing unit is used for acquiring the message information from the upstream callback queue and writing the message information into a database or performing callback downstream after the message information is added into the upstream callback queue.
Further, the parsing algorithm includes: and acquiring message information in the upstream callback message according to a preset key field.
Further, the key fields can be preset through a graphical interface.
The improvement of this patent brings the following advantage:
(1) compared with the codes for identifying the callback message in the prior art, the codes compiled by the method are simpler, the redundancy rate of the codes is low, the development period is short, and the message analysis speed is high.
(2) The code written by the method can be immediately used after being configured, a server does not need to be restarted, and the maintenance cost is low.
(3) The what you see is what you get configuration mode, greatly reduce the probability of making mistakes.
(4) The coupling degree of the code written by the method and the system is low, hard coding is carried out without depending on a third party callback message format, and the extension is easy.
Drawings
Fig. 1 is a schematic diagram of an optional system architecture capable of implementing dynamic recognition of a callback packet according to the embodiment of the present application.
Fig. 2 is a flowchart illustrating a method for identifying a callback packet according to an embodiment of the present application.
Fig. 3 is a schematic structural diagram of a device for identifying a callback packet according to an embodiment of the present application.
Fig. 4 and fig. 5 are schematic diagrams of two key field configuration windows, respectively.
Detailed Description
The following embodiments of the present invention are provided by way of specific examples, and other advantages and effects of the present invention will be readily apparent to those skilled in the art from the disclosure herein. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention.
Fig. 1 is an alternative system architecture that may implement dynamic callback message identification according to an embodiment of the present disclosure, where the system architecture includes an upstream API, a target program, and a downstream or database.
Wherein, the upstream API provides an upstream callback message; the target program is used for dynamically identifying the upstream callback message, extracting message information from the upstream callback message and providing the message information to a downstream or database; the downstream can call back the downstream, continue to utilize the message information, the database can record the message information.
What this application will realize is: the message structure of the upstream callback message is uniform, and most of the upstream callback message consists of a request parameter, a request header, an encryption mode and a request response. The application finds out the butt joint rules of most upstream API callback messages, and can realize the rapid analysis of the upstream callback messages by analyzing and matching the upstream callback messages through the internal processing program, thereby realizing the rapid analysis of the upstream callback messages.
Next, from the perspective of the target program, the method for identifying a callback packet of the present application is described in detail, as shown in fig. 2, where fig. 2 shows a flowchart of the method, and includes the following steps:
s100, when the target program is detected to be triggered, receiving an upstream callback message;
s200, after the successful receiving of the upstream callback message is confirmed, analyzing the upstream callback message by using an analysis algorithm to obtain message information;
s300, if the message information is successfully acquired, adding the message information into an upstream callback queue;
s400, if the message information can not be acquired, acquiring the message information by adopting a corresponding processing class and adding the message information into an upstream callback queue;
specifically, if the upstream callback packet cannot be processed by the parsing algorithm, the upstream callback packet is parsed by writing a processing class corresponding to the upstream callback packet.
And S500, after the message information is added into the upstream callback queue, obtaining the message information from the upstream callback queue and writing the message information into a database or performing callback on a downstream.
Specifically, the upstream callback queue is a message queue.
By adopting the method to process the upstream callback messages, the method does not need to compile a Handler processing class for each upstream as the prior art, and can process the callback messages of a plurality of upstream by only analyzing the format and the structure of the upstream callback messages and selecting a proper analysis algorithm. The code is simple, the redundancy is low, and the message analysis speed is favorably improved. And the code written by the method can be immediately used after being configured, a server does not need to be restarted, and the maintenance cost is low. The coupling degree of the code and the system is low, the stability of the system is improved, hard coding is carried out without depending on a third-party callback message format, and the expansion is easy and efficient.
As an embodiment, step S200 includes the following substeps:
s201, after confirming that the upstream callback message is successfully received, judging the message type of the upstream callback message.
Specifically, the packet type may include JSON, XML, or other packet types, and the packet type of the upstream callback packet is determined by identifying keywords at the head and the tail of the upstream callback packet.
S202, after the message type is obtained, a corresponding analysis algorithm is selected according to the message type.
S203, after selecting the corresponding analysis algorithm, analyzing the upstream callback message by using the analysis algorithm to acquire message information.
The type of the upstream callback message is identified first, and then the corresponding analysis algorithm is selected, so that the identification speed can be improved, and the error probability can be reduced.
As one embodiment, the parsing algorithm includes: and acquiring message information in the upstream callback message according to a preset key field. According to the implementation, the upstream callback message is identified by presetting the key field and then identifying the key words corresponding to the key field from the message, so that the risk that the message cannot be identified once the message structure is changed in the prior art can be avoided. As long as the corresponding keywords are still called back in the message upstream, the message information in the message is identified one by one according to the preset key fields, and the identification of the message information is basically not influenced by the change of the message structure. Even if the keywords in the upstream callback message are changed, the embodiment only needs to correspondingly adjust the changed keywords, does not need to change codes, and does not need to issue a restart. And the analysis speed of the upstream callback message is high, and the upstream callback message can be analyzed only by simply learning semantics. For example, it takes 4 hours to write and process multiple processing classes of multiple upstream callback messages before, and by using the method, the target program can be written and completed only in about 30min, and multiple upstream callback messages can be processed.
As a further improvement, the key fields may be preset through a graphical interface, as shown in fig. 4 and 5. The key field is set into a key field configuration window which can be edited and set through a visual mode (a graphical interface), and the key field configuration window is presented to a user. Therefore, even if some keywords corresponding to the key fields on the upstream callback message are changed, the user can conveniently and quickly input the changed keywords into the key field configuration window according to the change to be used as the preset key fields, so that the corresponding keywords in the upstream callback message can be identified, the message information can be extracted, and the probability of identification errors can be reduced.
As an embodiment, as shown in fig. 3, an apparatus for identifying a callback message includes:
a receiving unit 100, configured to receive an upstream callback packet when it is detected that a target program is triggered;
the parsing unit 200 is configured to parse the upstream callback packet by using a parsing algorithm to obtain packet information after the upstream callback packet is determined to be successfully received;
an access queue unit 300, configured to add the message information to an upstream callback queue if it is determined that the message information is successfully obtained;
an exception handling unit 400, configured to, if the message information cannot be obtained, obtain the message information by using the corresponding processing class and add the message information to the upstream callback queue;
the message processing unit 500 is configured to obtain the message information from the upstream callback queue and write the message information into the database or perform callback on the downstream after the message information is added to the upstream callback queue.
As a specific example, the following further details the method with reference to the apparatus for identifying a callback packet, including:
1. the upstream API sends an upstream callback message to trigger a target program, and the receiving unit receives the upstream callback message.
2. And the analysis unit analyzes the JSON, XML or other types of messages according to the upstream callback message. Specifically, the keywords, such as serial number, upstream order status description, upstream order return status value, etc., are analyzed by an analysis algorithm. The following respectively describes the parsing methods of two message types, JSON and XML.
2.1 upstream callback packet example of JSON type:
specifically, the parsing unit identifies that the head and the tail of the current upstream callback message contain { } characters, and then can judge that the message is of the Json message type. Then according to the configured key fields, such as: message, orderState, orderNo and the like, analyzes the message content by using a java placeholder or a content function, and then acquires the value information of corresponding keywords such as state description, success state value, serial number and the like in the upstream callback message. For example, the keyword in the upstream callback packet corresponding to the key field "message" is "message". After finding out the corresponding keyword according to the key field, extracting the value of the keyword, for example, the value of the keyword "message" is "recharging success". Wherein the key field configuration window is shown in fig. 4 and includes a stream number (orderNo), a status (orderState), a status description (message), and a success status value (0000).
2.2 example of an upstream callback message of XML type:
specifically, the parsing unit identifies that the header of the currently returned message contains? XML character can be judged as XML message type. And then analyzing the message content by using a java content function according to the configured key fields, such as sp _ order _ id, sp _ deal _ status, msg and the like, and then acquiring the value information of the corresponding keywords, such as serial numbers, states, state descriptions and the like. For example, the key in the upstream callback message corresponding to the key field "msg" is "msg". After finding the corresponding keyword according to the keyword field, extracting the value of the keyword, for example, the value of the keyword "msg" is "success". The key field configuration window is shown in fig. 5, and the serial number: sp _ order _ id, status: sp _ deal _ status, status description: msg.
3. And after keywords and keyword values such as the serial number, the upstream order state description, the upstream order return state value and the like are obtained, the information is packaged into message information and provided for the next operation.
4. And updating the order state in the system according to the message information, and adding the corresponding order state description into the order information. And further checking the real order state according to the returned state value of the upstream order, and responding to the upstream callback.
5. Because part of the upstream needs batch order-raising operation, order information can be returned in large batch, and therefore the upstream callback message needs to be plugged into the callback queue for peak clipping after being processed, the IO pressure of the database is relieved, and upstream callback entries are convenient to unify.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.
Claims (10)
1. A method for identifying a callback message is characterized by comprising the following steps:
when the target program is detected to be triggered, receiving an upstream callback message;
after the successful receiving of the upstream callback message is confirmed, analyzing the upstream callback message by using an analysis algorithm to obtain message information;
if the message information is successfully acquired, adding the message information into an upstream callback queue;
if the message information can not be acquired, acquiring the message information by adopting a corresponding processing class and adding the message information into the upstream callback queue;
and after the message information is added into the upstream callback queue, obtaining the message information from the upstream callback queue and writing the message information into a database or performing callback on downstream.
2. The method of claim 1, wherein after the acknowledging successful receipt of the upstream callback packet, parsing the upstream callback packet using a parsing algorithm to obtain packet information comprises:
after the successful receiving of the upstream callback message is confirmed, judging the message type of the upstream callback message;
after the message type is obtained, selecting the corresponding analysis algorithm according to the message type;
and after the corresponding analysis algorithm is selected, analyzing the upstream callback message by using the analysis algorithm to acquire message information.
3. The method of claim 2, wherein the packet types comprise JSON, XML.
4. The method according to claim 2, wherein said determining the packet type of the upstream callback packet comprises: and judging the message type of the upstream callback message by identifying keywords at the head and the tail of the upstream callback message.
5. The method of claim 1, wherein the parsing algorithm comprises: and acquiring message information in the upstream callback message according to a preset key field.
6. The method of claim 5, wherein the key fields are presettable via a graphical interface.
7. The method of claim 1, wherein the upstream callback queue is a message queue.
8. An apparatus for recognizing a callback packet, comprising:
the receiving unit is used for receiving an upstream callback message when the target program is detected to be triggered;
the analysis unit is used for analyzing the upstream callback message by using an analysis algorithm to acquire message information after the upstream callback message is confirmed to be successfully received;
the access queue unit is used for adding the message information into an upstream callback queue if the message information is successfully acquired;
the exception handling unit is used for acquiring the message information by adopting a corresponding processing class and adding the message information into the upstream callback queue if the message information cannot be acquired;
and the message processing unit is used for acquiring the message information from the upstream callback queue and writing the message information into a database or performing callback downstream after the message information is added into the upstream callback queue.
9. The apparatus of claim 8, wherein the parsing algorithm comprises: and acquiring message information in the upstream callback message according to a preset key field.
10. The apparatus of claim 9, wherein the key field is capable of being preset via a graphical interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210629307.2A CN114928663A (en) | 2022-06-02 | 2022-06-02 | Method and device for recognizing callback message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210629307.2A CN114928663A (en) | 2022-06-02 | 2022-06-02 | Method and device for recognizing callback message |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114928663A true CN114928663A (en) | 2022-08-19 |
Family
ID=82813506
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210629307.2A Pending CN114928663A (en) | 2022-06-02 | 2022-06-02 | Method and device for recognizing callback message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114928663A (en) |
Citations (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070189159A1 (en) * | 2003-12-17 | 2007-08-16 | Telefonaktiebolaget Lm Ericsson | System and method for dynamically optimized message processing |
| US20090158242A1 (en) * | 2007-12-18 | 2009-06-18 | Kabira Technologies, Inc., | Library of services to guarantee transaction processing application is fully transactional |
| CN105227667A (en) * | 2015-10-14 | 2016-01-06 | 深圳市金证科技股份有限公司 | Message forwarding method and platform |
| CN109067911A (en) * | 2018-09-14 | 2018-12-21 | 国云科技股份有限公司 | A kind of message transmission implementation method sending condition based on cloudy platform |
| CN109194617A (en) * | 2018-08-01 | 2019-01-11 | 杭州电子科技大学 | The automatically parsing of XML message, packaging method and device |
| CN110036609A (en) * | 2016-12-30 | 2019-07-19 | 英特尔公司 | Intelligent packet polymerization |
| CN110209377A (en) * | 2019-04-26 | 2019-09-06 | 平安科技（深圳）有限公司 | Interface packet processing method, device, equipment and storage medium based on factory class |
| CN110677427A (en) * | 2019-10-08 | 2020-01-10 | 山东浪潮商用系统有限公司 | Multi-message analysis method |
| CN110769009A (en) * | 2019-12-29 | 2020-02-07 | 深圳竹云科技有限公司 | User identity authentication method and system |
| CN111061696A (en) * | 2019-12-17 | 2020-04-24 | 中国银行股份有限公司 | Method and device for analyzing transaction message log |
| US20200186445A1 (en) * | 2018-12-11 | 2020-06-11 | Vmware, Inc. | Methods and systems that provision distributed applications that invoke functions provided by a distributed-function-as-a-service feature |
| CN111314485A (en) * | 2020-03-11 | 2020-06-19 | 山东超越数控电子股份有限公司 | Method for customizing networked expandability of key module |
| CN111614647A (en) * | 2020-05-14 | 2020-09-01 | 中国银行股份有限公司 | Message detection and analysis method and device |
| CN111694797A (en) * | 2020-06-04 | 2020-09-22 | 中国建设银行股份有限公司 | File uploading and analyzing method, device, server and medium |
| CN111752720A (en) * | 2020-06-27 | 2020-10-09 | 武汉众邦银行股份有限公司 | Asynchronous request disguising synchronous request method |
| CN112232881A (en) * | 2020-10-22 | 2021-01-15 | 腾讯科技（深圳）有限公司 | Data detection method and device, electronic equipment and storage medium |
| CN112256954A (en) * | 2020-09-08 | 2021-01-22 | 国网宁夏电力有限公司经济技术研究院 | Message pushing processing method and related system |
| CN112272218A (en) * | 2020-10-16 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Cloud platform instance resource operation method and device, computer equipment and storage medium |
| CN112445868A (en) * | 2019-08-30 | 2021-03-05 | 北京京东振世信息技术有限公司 | Service message processing method and device |
| CN113676437A (en) * | 2020-05-14 | 2021-11-19 | 中国移动通信集团云南有限公司 | Parameter analysis method, parameter acquisition method, parameter setting method and device |
| CN113918357A (en) * | 2020-09-15 | 2022-01-11 | 京东科技控股股份有限公司 | Service processing method and device, storage medium and electronic equipment |
| CN114024821A (en) * | 2018-06-28 | 2022-02-08 | 中兴通讯股份有限公司 | Northbound interface management method and device |
| CN114205167A (en) * | 2021-12-17 | 2022-03-18 | 深圳市健成云视科技有限公司 | Application layer registration keep-alive method, system, electronic equipment and storage medium |
| CN114363412A (en) * | 2022-01-07 | 2022-04-15 | 中国工商银行股份有限公司 | Message data processing method and device, computer equipment and storage medium |
| CN114553978A (en) * | 2022-04-24 | 2022-05-27 | 深圳市城市交通规划设计研究中心股份有限公司 | Sensor message data processing method, electronic equipment and storage medium |
-
2022
- 2022-06-02 CN CN202210629307.2A patent/CN114928663A/en active Pending
Patent Citations (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070189159A1 (en) * | 2003-12-17 | 2007-08-16 | Telefonaktiebolaget Lm Ericsson | System and method for dynamically optimized message processing |
| US20090158242A1 (en) * | 2007-12-18 | 2009-06-18 | Kabira Technologies, Inc., | Library of services to guarantee transaction processing application is fully transactional |
| CN105227667A (en) * | 2015-10-14 | 2016-01-06 | 深圳市金证科技股份有限公司 | Message forwarding method and platform |
| CN110036609A (en) * | 2016-12-30 | 2019-07-19 | 英特尔公司 | Intelligent packet polymerization |
| CN114024821A (en) * | 2018-06-28 | 2022-02-08 | 中兴通讯股份有限公司 | Northbound interface management method and device |
| CN109194617A (en) * | 2018-08-01 | 2019-01-11 | 杭州电子科技大学 | The automatically parsing of XML message, packaging method and device |
| CN109067911A (en) * | 2018-09-14 | 2018-12-21 | 国云科技股份有限公司 | A kind of message transmission implementation method sending condition based on cloudy platform |
| US20200186445A1 (en) * | 2018-12-11 | 2020-06-11 | Vmware, Inc. | Methods and systems that provision distributed applications that invoke functions provided by a distributed-function-as-a-service feature |
| CN110209377A (en) * | 2019-04-26 | 2019-09-06 | 平安科技（深圳）有限公司 | Interface packet processing method, device, equipment and storage medium based on factory class |
| CN112445868A (en) * | 2019-08-30 | 2021-03-05 | 北京京东振世信息技术有限公司 | Service message processing method and device |
| CN110677427A (en) * | 2019-10-08 | 2020-01-10 | 山东浪潮商用系统有限公司 | Multi-message analysis method |
| CN111061696A (en) * | 2019-12-17 | 2020-04-24 | 中国银行股份有限公司 | Method and device for analyzing transaction message log |
| CN110769009A (en) * | 2019-12-29 | 2020-02-07 | 深圳竹云科技有限公司 | User identity authentication method and system |
| CN111314485A (en) * | 2020-03-11 | 2020-06-19 | 山东超越数控电子股份有限公司 | Method for customizing networked expandability of key module |
| CN111614647A (en) * | 2020-05-14 | 2020-09-01 | 中国银行股份有限公司 | Message detection and analysis method and device |
| CN113676437A (en) * | 2020-05-14 | 2021-11-19 | 中国移动通信集团云南有限公司 | Parameter analysis method, parameter acquisition method, parameter setting method and device |
| CN111694797A (en) * | 2020-06-04 | 2020-09-22 | 中国建设银行股份有限公司 | File uploading and analyzing method, device, server and medium |
| CN111752720A (en) * | 2020-06-27 | 2020-10-09 | 武汉众邦银行股份有限公司 | Asynchronous request disguising synchronous request method |
| CN112256954A (en) * | 2020-09-08 | 2021-01-22 | 国网宁夏电力有限公司经济技术研究院 | Message pushing processing method and related system |
| CN113918357A (en) * | 2020-09-15 | 2022-01-11 | 京东科技控股股份有限公司 | Service processing method and device, storage medium and electronic equipment |
| CN112272218A (en) * | 2020-10-16 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Cloud platform instance resource operation method and device, computer equipment and storage medium |
| CN112232881A (en) * | 2020-10-22 | 2021-01-15 | 腾讯科技（深圳）有限公司 | Data detection method and device, electronic equipment and storage medium |
| CN114205167A (en) * | 2021-12-17 | 2022-03-18 | 深圳市健成云视科技有限公司 | Application layer registration keep-alive method, system, electronic equipment and storage medium |
| CN114363412A (en) * | 2022-01-07 | 2022-04-15 | 中国工商银行股份有限公司 | Message data processing method and device, computer equipment and storage medium |
| CN114553978A (en) * | 2022-04-24 | 2022-05-27 | 深圳市城市交通规划设计研究中心股份有限公司 | Sensor message data processing method, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11822919B2 (en) | Auto-generation of API documentation via implementation-neutral analysis of API traffic | |
| US10572370B2 (en) | Test-assisted application programming interface (API) learning | |
| US11775414B2 (en) | Automated bug fixing using deep learning | |
| US20060242145A1 (en) | Method and Apparatus for Extraction | |
| CN110688307B (en) | JavaScript code detection method, device, equipment and storage medium | |
| CN111447227A (en) | Protocol analysis method and device of Internet of things equipment | |
| CN110837393A (en) | Method and device for manufacturing firmware differential upgrade package and readable storage medium | |
| CN108664471B (en) | Character recognition error correction method, device, equipment and computer readable storage medium | |
| WO2021175053A1 (en) | Method and apparatus for executing functional module in virtual machine | |
| CN111667923B (en) | Data matching method and device, computer readable medium and electronic equipment | |
| CN113381963A (en) | Domain name detection method, device and storage medium | |
| CN113094625B (en) | Page element positioning method and device, electronic equipment and storage medium | |
| CN111581057B (en) | General log analysis method, terminal device and storage medium | |
| CN114928663A (en) | Method and device for recognizing callback message | |
| US20050289525A1 (en) | Extensible command line parsing | |
| CN111026604A (en) | Log file analysis method and device | |
| US20160253374A1 (en) | Data file writing method and system, and data file reading method and system | |
| CN116186223A (en) | Financial text processing method, device, equipment and storage medium | |
| CN114510717A (en) | ELF file detection method and device and storage medium | |
| WO2022111209A1 (en) | Data acquisition method and apparatus, data acquisition device and readable storage medium | |
| CN114385918A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN110806896B (en) | Method for realizing internationalized information extraction in software development based on maven extension plug-in | |
| CN113672512A (en) | Code inspection rule generating method, code inspection method, device and medium | |
| CN115587364B (en) | Firmware vulnerability input point positioning method and device based on front-end and back-end correlation analysis | |
| CN114519357B (en) | Natural language processing method and system based on machine learning |
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 |