CN110730092A - Method and device for debugging gateway - Google Patents
Method and device for debugging gateway Download PDFInfo
- Publication number
- CN110730092A CN110730092A CN201910854677.4A CN201910854677A CN110730092A CN 110730092 A CN110730092 A CN 110730092A CN 201910854677 A CN201910854677 A CN 201910854677A CN 110730092 A CN110730092 A CN 110730092A
- Authority
- CN
- China
- Prior art keywords
- gateway
- information
- push
- pushing
- simulated transaction
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
- H04L41/0869—Validating the configuration within one network element
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the specification provides a method and a device for debugging a gateway between a risk service providing server and a user server, wherein the method comprises the following steps: receiving a gateway debugging request input by a user through a front-end page, wherein the gateway debugging request comprises first simulated transaction information and risk type information; under a formal use environment, generating a simulated transaction based on the first simulated transaction information and the risk type information, wherein the simulated transaction has second simulated transaction information and a simulated transaction identifier; generating gateway debugging feedback information based on the second simulated transaction information and the risk type information; and pushing the gateway commissioning feedback information to the user server via a gateway between the risk service providing server and the user server for determining a configuration state of a gateway configuration of the user server.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a method and a device for debugging a gateway between a risk service providing server and a user server.
Background
The enterprise with the risk prediction technology can provide risk service for other enterprises to carry out risk prediction on transactions related to other enterprises, so that the business safety of other enterprises is guaranteed. An enterprise providing a risk service may be configured with a risk service providing server and an open platform for performing risk service related interactive operations with a user, and the risk service providing server may interact with the user via the open platform. The open platform may include a gateway, and information required to be transmitted to the user server via the gateway may be transmitted via the open platform. Typically, a user may perform a gateway configuration at a user server to establish a communication connection with a risk service providing server. The gateway configuration needs to be debugged after the gateway configuration is completed to ensure that the gateway configuration is accurate and error-free, so that the risk service can be obtained from the risk service providing server through the gateway when in formal use.
Disclosure of Invention
In view of the foregoing, embodiments of the present specification provide a method and an apparatus for performing gateway debugging between a risk service providing server and a user server.
According to an aspect of an embodiment of the present specification, there is provided a method for gateway debugging between a risk service providing server and a user server, including: receiving a gateway debugging request input by a user through a front-end page, wherein the gateway debugging request comprises first simulated transaction information and risk type information; under a formal use environment, generating a simulated transaction based on the first simulated transaction information and the risk type information, wherein the simulated transaction has second simulated transaction information and a simulated transaction identifier; generating gateway debugging feedback information based on the second simulated transaction information and the risk type information; and pushing the gateway commissioning feedback information to the user server via a gateway between the risk service providing server and the user server for determining a configuration state of a gateway configuration of the user server.
Optionally, in an example, after pushing the gateway debugging feedback information to the user server, the method further includes: acquiring push state information from a gateway log of the risk service providing server; generating a pushing state identifier based on the pushing state information, wherein the pushing state identifier indicates whether the risk service providing server successfully pushes the gateway debugging feedback information; and sending the pushing state identification to the front-end page through page communication.
Optionally, in an example, when the pushing status information indicates that the risk service providing server does not successfully push the gateway debugging feedback information, the pushing status identifier further includes a pushing failure reason identifier indicating a pushing failure reason.
Optionally, in an example, after sending the push status identifier to the front end page, the method further includes: receiving a solution suggestion acquisition request through the page communication, wherein the solution suggestion acquisition request comprises a pushing failure reason identifier; and responding to the solution suggestion acquisition request, sending solution suggestion information corresponding to the pushing failure reason identification to the front-end page through the page communication so as to display the solution suggestion information on the front-end page.
Optionally, in an example, the gateway is an API interface, and the gateway is configured as an API interface configuration.
According to another aspect of embodiments of the present specification, there is also provided an apparatus for performing gateway debugging between a risk service providing server and a user server, including: the gateway debugging request receiving unit is used for receiving a gateway debugging request input by a user through a front-end page, wherein the gateway debugging request comprises first simulated transaction information and risk type information; the simulated transaction generating unit is used for generating simulated transactions based on the first simulated transaction information and the risk type information under the formal use environment, and the simulated transactions are provided with second simulated transaction information and simulated transaction identifiers; the gateway debugging feedback information generating unit generates gateway debugging feedback information based on the second simulated transaction information and the risk type information; and a gateway debugging feedback information pushing unit for pushing the gateway debugging feedback information to the user server via the gateway between the risk service providing server and the user server, so as to determine the configuration state of the gateway configuration of the user server.
Optionally, in an example, the apparatus further comprises: a pushed state information acquisition unit which acquires pushed state information from a gateway log of the risk service providing server after pushing the gateway debugging feedback information to the user server; a pushing state identifier generating unit, configured to generate a pushing state identifier based on the pushing state information, where the pushing state identifier indicates whether the risk service providing server successfully pushes the gateway debugging feedback information; and the pushing state identification sending unit is used for sending the pushing state identification to the front-end page through page communication.
Optionally, in an example, when the pushing status information indicates that the risk service providing server does not successfully push the gateway debugging feedback information, the pushing status identifier generating unit generates a pushing failure reason identifier based on the pushing status information, where the pushing failure reason identifier indicates a pushing failure reason.
Optionally, in an example, the apparatus further comprises: a solution suggestion acquisition request receiving unit, configured to receive a solution suggestion acquisition request through the page communication after sending the push state identifier to the front-end page, where the solution suggestion acquisition request includes a push failure cause identifier; and a solution suggestion information sending unit, responding to a solution suggestion acquisition request, sending solution suggestion information corresponding to the push failure reason identifier to the front-end page through the page communication, so as to display the solution suggestion information on the front-end page.
According to another aspect of embodiments of the present specification, there is also provided a computing device including: at least one processor; and a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method as described above.
According to another aspect of embodiments herein, there is also provided a non-transitory machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the method as described above.
By using the method and the device in the embodiment of the specification, the simulated transaction with the simulated transaction identification is generated based on the simulated transaction information input by the user, then the gateway debugging feedback information is generated based on the generated second transaction information of the simulated transaction and the risk type information input by the user, and the gateway debugging feedback information is pushed to the user server through the gateway, so that whether the gateway configuration has a problem or not is confirmed by the user server based on the gateway debugging feedback information, the gateway debugging can be performed under the formal use environment, meanwhile, the simulated transaction information and the formal transaction information for gateway debugging can be distinguished based on the simulated transaction identification, and therefore, the influence of the simulated transaction in the gateway debugging process on the user analysis based on the transaction data can be avoided.
Drawings
A further understanding of the nature and advantages of contents of embodiments of the present specification may be realized by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. The accompanying drawings, which are included to provide a further understanding of the embodiments of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the detailed description below serve to explain the embodiments of the specification and not to limit the embodiments of the specification. In the drawings:
FIG. 1 is a flow diagram of a gateway debugging method according to one embodiment of the present description;
FIG. 2 is one example of a front end page for entering first simulated transaction information and risk type information in a gateway debugging method according to one embodiment of the present description;
fig. 3 is a flowchart of an example of a push status identifier generation procedure and a transmission procedure in a gateway debugging method according to an embodiment of the present specification;
fig. 4 is a flowchart of an example of a process of sending solution advice information in a gateway debugging method according to an embodiment of the present specification;
FIG. 5 is a diagram illustrating message paths in one application scenario of a gateway debugging method in accordance with one embodiment of the present description;
fig. 6 is a block diagram of a gateway debugging apparatus according to an embodiment of the present specification;
fig. 7 is a block diagram of a gateway debugging apparatus according to another embodiment of the present specification;
fig. 8 is a block diagram of a computing device for implementing a gateway debugging method according to one embodiment of the present specification.
Detailed Description
The subject matter described herein will be discussed with reference to example embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thereby implement the subject matter described herein, and are not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the embodiments of the disclosure. Various examples may omit, substitute, or add various procedures or components as needed. In addition, features described with respect to some examples may also be combined in other examples.
As used herein, the term "include" and its variants mean open-ended terms in the sense of "including, but not limited to. The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first," "second," and the like may refer to different or the same object. Other definitions, whether explicit or implicit, may be included below. The definition of a term is consistent throughout the specification unless the context clearly dictates otherwise.
The gateway debugging method and apparatus of the embodiments of the present specification will now be described with reference to the accompanying drawings. The gateway debugging method in the embodiment of the present specification is executed at a risk service providing server.
Fig. 1 is a flow diagram of a gateway debugging method according to one embodiment of the present description.
As shown in FIG. 1, at block 120, a gateway debug request input by a user via a front end page is received, the gateway debug request including first simulated transaction information and risk type information. The gateway may be, for example, an API interface, the API interface may be configured in a risk service providing system (for example, may be an open platform associated with a risk service providing server), and the user may perform gateway configuration in the user server according to the obtained API interface document to establish a communication connection with the risk service providing server by calling the API interface. The API interface document may include, for example, code examples, interface input parameters, output parameters, and the like. After completing the gateway configuration at the user server, the user may log in to a front-end page of the risk service providing system and then input the risk type information and the first simulated transaction information for generating the gateway debugging request.
Fig. 2 is an example of a front end page 200 for entering first simulated transaction information and risk type information in a gateway commissioning method according to one embodiment of the present description. As shown in fig. 2, the user may enter a risk type, such as a fraud class, a fake transaction class, etc., in a risk type information field. The various risk types may also be configured as a list for selection by the user. The user can select the transaction with the risk type which the user wants to debug according to the requirement of the user, for example, if the user wants to debug the transaction with the risk of fraud, the fraud can be input in the risk type input field. The simulated transaction information may include a user number identifying the identity of the user and a transaction serial number for simulating a corresponding simulated transaction. The user can input the transaction serial number according to the self transaction serial number numbering rule and can randomly input the transaction serial number capable of identifying corresponding simulated transaction. In another example, the transaction information input by the user may also include other information, such as identification information assigned to the user by the risk service providing system for identifying the user in the risk service providing system, and the like.
The front end page may also include a send control that the user may click to send after entering the risk type information and the first simulated transaction information. After the user clicks to send, the front-end page may send a gateway debugging request including risk type information and first simulated transaction information to the risk service providing server through page communication between the risk service providing server and the front-end page.
After receiving the gateway commissioning request, at block 140, a simulated transaction is generated based on the first simulated transaction information and the risk type information, the simulated transaction having the second simulated transaction information and the simulated transaction identification, under the formal use environment. The risk service system may include an offline debugging environment for gateway debugging in the offline environment before or after a period of formal use and a formal use environment. The formal use environment is an operation environment in which the user starts to formally send a transaction to the risk service providing server via the gateway to request the risk service providing server to predict the transaction, and then receives a risk prediction result from the risk service providing server.
The simulated transaction identification is used to identify that the generated transaction is a simulated transaction. The simulated transaction identifier can be used for eliminating the influence caused by simulated transaction for gateway debugging when a user is analyzed based on historical transaction data. For example, second simulated transaction information for the simulated transaction and transaction information for the official transaction may be stored in isolation based on the simulated transaction identification. Alternatively, the second simulated transaction information for the simulated transaction may be removed based on the simulated transaction identification when the user is analyzed. One example of analyzing a user is credit evaluation of the user based on historical transaction data. Since simulated transactions for gateway commissioning are often assigned some type of transaction risk, such simulated transaction information may degrade the user's credit assessment results at the time of credit assessment. And when the simulated transaction identifier is provided, the simulated transaction for gateway debugging can be removed during information evaluation, so that the influence of the simulated transaction information on the credit evaluation result can be avoided.
When the risk service providing server generates the simulated transaction, the received first simulated transaction information can be simply used as the second simulated transaction information, the first simulated transaction information can be reassembled according to the data format of the risk service providing server to generate the second simulated transaction information of the simulated transaction, and other information which may be needed can be added.
After generating the simulated transaction, gateway debug feedback information is generated based on the second simulated transaction information and the risk type information at block 160. The risk service providing server can assemble gateway debugging feedback information according to a message format for feeding back a transaction risk prediction result to the user under a formal use environment based on the second simulated transaction information and the risk type information.
After generating the gateway commissioning feedback information, at block 180, the gateway commissioning feedback information is pushed to the user server via the gateway between the risk service providing server and the user server for determining the configuration state of the gateway configuration of the user server.
The user may determine whether the gateway configuration of the user server is problematic based on whether the gateway debugging feedback information is received, for example, may determine that the gateway configuration is problematic when the gateway debugging feedback information is not received, and determine that the gateway configuration is not problematic when the gateway debugging feedback information is received. In another example, when the gateway debugging feedback information is received, the user may also determine whether there is a problem with the gateway configuration based on the first simulated transaction information input by the user and the second simulated transaction information and risk type information carried in the gateway debugging feedback information. For example, it may be determined that there is no problem with the gateway configuration when the second simulated transaction information and the risk type information in the gateway debugging feedback information are consistent with the second simulated transaction information and the risk type information input by the user, and it may be determined that there is a problem with the gateway configuration when there is inconsistent information. In addition, the specific existing problems of the gateway configuration can be analyzed based on inconsistent information.
By means of the embodiment, online gateway debugging can be performed in a formal use environment, and simulated transactions for gateway debugging are distinguished by means of simulated transaction identifiers, so that the simulated transactions for gateway debugging are prevented from being confused into formal transactions to influence data analysis based on transaction data (for example, influence on credit evaluation results of users) while offline gateway debugging is transferred to online gateway debugging.
In another example, after pushing the gateway debugging feedback information to the user server, whether the push result is successfully pushed may also be shown on the front-end page, for example, the process may be implemented with reference to the example shown in fig. 3. Fig. 3 is a flowchart of an example of a push status identifier generation procedure and a transmission procedure in a gateway debugging method according to an embodiment of the present specification.
As shown in fig. 3, after pushing gateway commissioning feedback information to the user server, at block 320, push status information is obtained from the gateway log of the risk service providing server. The gateway log comprises historical information of communication through the gateway, and the log information of whether the gateway debugging feedback information is successfully pushed to the user server or not can be obtained from the gateway log. In addition, if the gateway debugging feedback information is not successfully pushed to the user server, the gateway log may record the reason of the unsuccessful pushing, such as the reason of the gateway failure, the gateway parameter configuration error, and the like.
After obtaining the push status information, at block 340, a push status identifier is generated based on the push status information, where the push status identifier identifies whether the risk service providing server successfully pushes the gateway debug feedback information.
In one example, when the push status information indicates that the risk service providing server has not successfully pushed the simulated transaction information, the push status identifier may include a push failure reason identifier. A push failure reason identifier may be generated based on push failure reason information obtained from the gateway log to indicate a corresponding push failure reason.
The push status identifier is then sent to the front-end page via page communication at block 360. After receiving the push status identifier, the front-end page may display the push status identifier on the front-end page. Therefore, the user can intuitively see whether the gateway debugging feedback information is successfully received. When the push state identifier includes a push failure reason identifier, the user can also obtain the reason for failing to successfully receive the gateway debugging feedback information based on the push failure reason identifier.
The failure reason corresponding to the push failure reason identifier may be listed in the parameter information provided to the user, for example, so that the user may obtain the push failure reason through the push failure reason identifier. In addition, when the pushing failure reason identifier is sent to the front-end page, the pushing failure reason can also be sent to the front-end page so as to be displayed on the front-end page. In addition, the risk service providing server may be requested by the user to send a push failure reason corresponding to the push failure reason identification to the front-end page. For example, when the push failure reason identifier is displayed on the front-end page, a "view push failure reason" control may be displayed, and when the user clicks the control, the front-end page may send a push failure reason acquisition request including the push failure reason identifier to the risk service providing server. When receiving the push failure reason acquisition request, the risk service providing server can send the push failure reason corresponding to the push failure reason identification to the front-end page through page communication.
In one example, after receiving the push failure reason identification and displaying on the front-end page, the user may request to obtain a resolution suggestion for the corresponding push failure reason.
Fig. 4 is a flowchart of an example of a process of sending solution suggested cause information in a gateway debugging method according to an embodiment of the present specification.
As shown in FIG. 4, at block 420, after sending the push status identifier to the user server, a resolution suggestion acquisition request is received via page communication, the resolution suggestion acquisition request including a push failure cause identifier. For example, when the front-end page receives the push failure reason identifier, the push failure reason identifier (or the push failure reason) may be displayed on the front-end page, and the "view solution suggestion" may be displayed at the same time. When a user clicks 'view solution suggestion', a solution suggestion acquisition request is sent to the risk service providing server, and the solution suggestion acquisition request carries a pushing failure reason identifier.
Then, at block 440, in response to the failure cause obtaining request, the resolution suggestion cause information corresponding to the push failure cause identification is sent to the front-end page through page communication for displaying the resolution suggestion cause on the front-end page. The solution proposal can help the user to quickly determine the existing problem of the gateway configuration. For example, the reason for the push failure may be an IO interface exception, and the solution suggestion may include: certificate verification suggestions, certificate verification addresses, DNS resolution verification suggestions and DNS resolution verification code examples, network connection validity verification and network connection validity verification code examples and the like.
Fig. 5 is a schematic diagram for explaining a message path in one application scenario of the gateway debugging method according to one embodiment of the present specification.
As shown in fig. 5, in performing gateway debugging, at 502, a user may send a gateway debugging request to a risk service providing server through a front-end page. And after receiving the gateway debugging request, the risk service providing server generates a simulation transaction and generates gateway debugging feedback information. Then, at 504, the risk service providing server sends gateway commissioning feedback information to the open platform. After receiving the gateway debug feedback information, the open platform sends 506 the gateway debug feedback information to the user server via a gateway (e.g., an API interface) of the open platform based on the obtained user address.
After sending the gateway debug feedback information to the user server, the risk service providing server obtains gateway log information and push status information from the gateway log information, then generates a push status identifier based on the push status information, and then sends the generated push status identifier to the front-end page through page communication at 510. If the push status identifier includes a push failure cause identifier, then at 510, a resolution proposal get request is received from the front-end page via page communication. Corresponding resolution suggestion information is then sent to the front-end page at 512 in response to the resolution suggestion acquisition request.
As can be seen from fig. 5, other information than the gateway-mediated feedback information may be transmitted from the front-end page to the risk service providing server without passing through the gateway, so that it is possible to avoid that other information cannot be normally transmitted or received due to a problem in the configuration of the gateway.
Fig. 6 is a block diagram of a gateway debugging apparatus according to an embodiment of the present specification. As shown in fig. 6, the gateway debugging apparatus 600 includes a gateway debugging request receiving unit 610, a simulated transaction generating unit 620, a gateway debugging feedback information generating unit 630, and a gateway debugging feedback information pushing unit 640.
The gateway debugging request receiving unit 610 receives a gateway debugging request input by a user via a front-end page, wherein the gateway debugging request comprises first simulated transaction information and risk type information. The simulated transaction generating unit 620 generates a simulated transaction based on the first simulated transaction information and the risk type information under the formal use environment, wherein the simulated transaction has second simulated transaction information and a simulated transaction identifier. The gateway debugging feedback information generating unit 630 generates gateway debugging feedback information based on the second simulated transaction information and the risk type information. The gateway debugging feedback information pushing unit 640 pushes the gateway debugging feedback information to the user server via the gateway between the risk service providing server and the user server, so as to determine the configuration state of the gateway configuration of the user server.
Fig. 7 is a block diagram of a gateway debugging apparatus according to another embodiment of the present specification. As shown in fig. 7, the gateway debugging apparatus 700 includes a gateway debugging request receiving unit 710, a simulated transaction generating unit 720, a gateway debugging feedback information generating unit 730, a gateway debugging feedback information pushing unit 740, a pushing state information acquiring unit 750, a pushing state identifier generating unit 760, a pushing state identifier sending unit 770, a resolution suggestion acquisition request receiving unit 780, and a resolution suggestion information sending unit 790.
The gateway debugging request receiving unit 710 receives the gateway debugging request, and the simulated transaction generating unit 720 generates the simulated transaction based on the first simulated transaction information in the gateway debugging request. Then, after the gateway debug feedback information generation unit 730 generates the gateway debug feedback information, the gateway debug feedback information push unit 740 pushes the generated gateway debug feedback information to the user server via the gateway.
After pushing the gateway debug feedback information, the push status information obtaining unit 750 obtains the push status information from the gateway log of the risk service providing server. Then, the push status identifier generating unit 760 generates a push status identifier based on the push status information, where the push status identifier indicates whether the risk service providing server successfully pushes the gateway debugging feedback information. In an example, when the push status information indicates that the risk service providing server does not successfully push the gateway debugging feedback information, the push status identifier generating unit 760 may further generate a push failure reason identifier based on the push status information, where the push failure reason identifier indicates a push failure reason.
After generating the push status identifier, the push status identifier sending unit 770 sends the push status identifier to the front-end page through page communication.
After sending the push status identifier to the front-end page, the solution suggestion acquisition request receiving unit 780 receives a solution suggestion acquisition request through page communication, where the solution suggestion acquisition request includes a push failure cause identifier. Then, the resolution suggestion information sending unit 790 sends resolution suggestion reason information corresponding to the push failure reason identification to the front-end page through page communication in response to the failure reason acquisition request, for displaying the resolution suggestion information on the front-end page.
Embodiments of a gateway debugging method and apparatus according to embodiments of the present specification are described above with reference to fig. 1 to 7. The details mentioned in the above description of the method embodiments apply equally to the embodiments of the device of the embodiments of the present description.
The gateway debugging apparatus in the embodiments of the present specification may be implemented by hardware, or may be implemented by software, or a combination of hardware and software. The various embodiments in this specification are described in a progressive manner, with like reference to each other.
The gateway debugging apparatus in the embodiments of the present specification may be implemented by hardware, or may be implemented by software, or a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the storage into the memory for operation through the processor of the device where the software implementation is located as a logical means. In the embodiments of the present specification, the gateway debugging apparatus may be implemented by using a computing device, for example.
Fig. 8 is a block diagram of a computing device for implementing a gateway debugging method according to one embodiment of the present specification. As shown in fig. 8, computing device 800 includes a processor 810, a storage 820, a memory 830, a communication interface 840, and an internal bus 850, and processor 810, storage (e.g., non-volatile storage) 820, memory 830, communication interface 840 are connected together via bus 850. According to one embodiment, computing device 800 may include at least one processor 810, the at least one processor 810 executing at least one computer-readable instruction (i.e., an element described above as being implemented in software) stored or encoded in a computer-readable storage medium (i.e., memory 820).
In one embodiment, computer-executable instructions are stored in the memory 820 that, when executed, cause the at least one processor 810 to: receiving a gateway debugging request input by a user through a front-end page, wherein the gateway debugging request comprises first simulated transaction information and risk type information; under a formal use environment, generating a simulated transaction based on the first simulated transaction information and the risk type information, wherein the simulated transaction has second simulated transaction information and a simulated transaction identifier; generating gateway debugging feedback information based on the second simulated transaction information and the risk type information; and pushing gateway commissioning feedback information to the user server via a gateway between the risk service providing server and the user server for determining a configuration state of a gateway configuration of the user server.
It should be appreciated that the computer-executable instructions stored in the memory 820, when executed, cause the at least one processor 810 to perform the various operations and functions described above in connection with fig. 1-7 in the various embodiments of the present specification.
According to one embodiment, a program product, such as a non-transitory machine-readable medium, is provided. A non-transitory machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-7 in various ones of the embodiments of the present specification.
Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
In this case, the program code itself read from the readable medium can realize the functions of any of the above-described embodiments, and thus the machine-readable code and the readable storage medium storing the machine-readable code form part of the present invention.
Examples of the readable storage medium include floppy disks, hard disks, magneto-optical disks, optical disks (e.g., CD-ROMs, CD-R, CD-RWs, DVD-ROMs, DVD-RAMs, DVD-RWs), magnetic tapes, nonvolatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or from the cloud via a communications network.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Not all steps and elements in the above flows and system structure diagrams are necessary, and some steps or elements may be omitted according to actual needs. The execution order of the steps is not fixed, and can be determined as required. The apparatus structures described in the above embodiments may be physical structures or logical structures, that is, some units may be implemented by the same physical entity, or some units may be implemented by a plurality of physical entities, or some units may be implemented by some components in a plurality of independent devices.
The term "exemplary" used throughout this specification means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous" over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.
Although the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings, the embodiments of the present disclosure are not limited to the specific details of the embodiments, and various simple modifications may be made to the technical solutions of the embodiments of the present disclosure within the technical concept of the embodiments of the present disclosure, and all of them fall within the scope of the embodiments of the present disclosure.
The previous description of the contents of the embodiments of the present specification is provided to enable any person skilled in the art to make or use the contents of the embodiments of the present specification. Various modifications to the disclosure of the embodiments herein will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the embodiments herein. Thus, the present specification embodiments are not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (11)
1. A method for gateway debugging between a risk service providing server and a user server, comprising:
receiving a gateway debugging request input by a user through a front-end page, wherein the gateway debugging request comprises first simulated transaction information and risk type information;
under a formal use environment, generating a simulated transaction based on the first simulated transaction information and the risk type information, wherein the simulated transaction has second simulated transaction information and a simulated transaction identifier;
generating gateway debugging feedback information based on the second simulated transaction information and the risk type information; and
pushing, via a gateway between the risk service providing server and the user server, the gateway commissioning feedback information to the user server for determining a configuration state of a gateway configuration of the user server.
2. The method of claim 1, wherein after pushing the gateway commissioning feedback information to the user server, the method further comprises:
acquiring push state information from a gateway log of the risk service providing server;
generating a pushing state identifier based on the pushing state information, wherein the pushing state identifier indicates whether the risk service providing server successfully pushes the gateway debugging feedback information; and
and sending the pushing state identifier to the front-end page through page communication.
3. The method of claim 2, wherein when the push status information indicates that the risk service providing server did not successfully push the gateway debugging feedback information, the push status identifier further comprises a push failure reason identifier indicating a push failure reason.
4. The method of claim 3, wherein after sending the push status identification to the front-end page, the method further comprises:
receiving a solution suggestion acquisition request through the page communication, wherein the solution suggestion acquisition request comprises a pushing failure reason identifier; and
responding to the solution suggestion acquisition request, and sending solution suggestion information corresponding to the pushing failure reason identification to the front-end page through the page communication so as to display the solution suggestion information on the front-end page.
5. The method of claim 1, wherein the gateway is an API interface, the gateway configured as an API interface configuration.
6. An apparatus for gateway commissioning between a risk service providing server and a user server, comprising:
the gateway debugging request receiving unit is used for receiving a gateway debugging request input by a user through a front-end page, wherein the gateway debugging request comprises first simulated transaction information and risk type information;
the simulated transaction generating unit is used for generating simulated transactions based on the first simulated transaction information and the risk type information under the formal use environment, and the simulated transactions are provided with second simulated transaction information and simulated transaction identifiers;
the gateway debugging feedback information generating unit generates gateway debugging feedback information based on the second simulated transaction information and the risk type information; and
and the gateway debugging feedback information pushing unit is used for pushing the gateway debugging feedback information to the user server through a gateway between the risk service providing server and the user server so as to determine the configuration state of the gateway configuration of the user server.
7. The apparatus of claim 6, further comprising:
a pushed state information acquisition unit which acquires pushed state information from a gateway log of the risk service providing server after pushing the gateway debugging feedback information to the user server;
a pushing state identifier generating unit, configured to generate a pushing state identifier based on the pushing state information, where the pushing state identifier indicates whether the risk service providing server successfully pushes the gateway debugging feedback information; and
and the pushing state identifier sending unit is used for sending the pushing state identifier to the front-end page through page communication.
8. The apparatus of claim 7, wherein when the push status information indicates that the risk service providing server did not successfully push the gateway debugging feedback information, the push status identifier generating unit generates a push failure reason identifier indicating a push failure reason based on the push status information.
9. The apparatus of claim 8, further comprising:
a solution suggestion acquisition request receiving unit, configured to receive a solution suggestion acquisition request through the page communication after sending the push state identifier to the front-end page, where the failure cause acquisition request includes a push failure cause identifier; and
and the solution suggestion information sending unit responds to the failure reason acquisition request, and sends solution suggestion information corresponding to the pushing failure reason identification to the front-end page through the page communication so as to display the solution suggestion information on the front-end page.
10. A computing device, comprising:
at least one processor; and
a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 5.
11. A machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910854677.4A CN110730092B (en) | 2019-09-10 | 2019-09-10 | Method and device for debugging gateway |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910854677.4A CN110730092B (en) | 2019-09-10 | 2019-09-10 | Method and device for debugging gateway |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110730092A true CN110730092A (en) | 2020-01-24 |
| CN110730092B CN110730092B (en) | 2022-02-25 |
Family
ID=69217985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910854677.4A Active CN110730092B (en) | 2019-09-10 | 2019-09-10 | Method and device for debugging gateway |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110730092B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102164365A (en) * | 2011-03-14 | 2011-08-24 | 上海华腾软件系统有限公司 | Mobile through ticket simulation test system |
| CN102711070A (en) * | 2011-12-20 | 2012-10-03 | 中国移动（深圳）有限公司 | On-line charging simulation testing system and method |
| CN104090839A (en) * | 2014-07-02 | 2014-10-08 | 中国银行股份有限公司 | Simulation test method and device for abnormal scene |
| US20190034842A1 (en) * | 2017-07-31 | 2019-01-31 | Ncr Corporation | Discrete-event simulation for transaction service point device cash servicing |
| CN109586946A (en) * | 2018-09-29 | 2019-04-05 | 阿里巴巴集团控股有限公司 | Abnormality eliminating method, device and computer readable storage medium |
| CN109617731A (en) * | 2018-12-21 | 2019-04-12 | 青岛海信智慧家居系统股份有限公司 | Adaptive gateway role configuration method and device under a kind of multi-gateway environment |
| CN109670803A (en) * | 2018-10-25 | 2019-04-23 | 深圳壹账通智能科技有限公司 | Method, apparatus, medium and the electronic equipment tested before online trading |
| GB201904787D0 (en) * | 2018-10-11 | 2019-05-22 | Arm Ip Ltd | Method and apparatus for debugging devices |
-
2019
- 2019-09-10 CN CN201910854677.4A patent/CN110730092B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102164365A (en) * | 2011-03-14 | 2011-08-24 | 上海华腾软件系统有限公司 | Mobile through ticket simulation test system |
| CN102711070A (en) * | 2011-12-20 | 2012-10-03 | 中国移动（深圳）有限公司 | On-line charging simulation testing system and method |
| CN104090839A (en) * | 2014-07-02 | 2014-10-08 | 中国银行股份有限公司 | Simulation test method and device for abnormal scene |
| US20190034842A1 (en) * | 2017-07-31 | 2019-01-31 | Ncr Corporation | Discrete-event simulation for transaction service point device cash servicing |
| CN109586946A (en) * | 2018-09-29 | 2019-04-05 | 阿里巴巴集团控股有限公司 | Abnormality eliminating method, device and computer readable storage medium |
| GB201904787D0 (en) * | 2018-10-11 | 2019-05-22 | Arm Ip Ltd | Method and apparatus for debugging devices |
| CN109670803A (en) * | 2018-10-25 | 2019-04-23 | 深圳壹账通智能科技有限公司 | Method, apparatus, medium and the electronic equipment tested before online trading |
| CN109617731A (en) * | 2018-12-21 | 2019-04-12 | 青岛海信智慧家居系统股份有限公司 | Adaptive gateway role configuration method and device under a kind of multi-gateway environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110730092B (en) | 2022-02-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107402880B (en) | Test method and electronic equipment | |
| CN111177005B (en) | Service application testing method, device, server and storage medium | |
| US9372785B2 (en) | Identifying implicit assumptions associated with a software product | |
| KR102151326B1 (en) | Data processing method and device | |
| CN112241360B (en) | Test case generation method, device, equipment and storage medium | |
| CN108874654B (en) | Idempotent validity test method, device and equipment and readable medium | |
| US20150186195A1 (en) | Method of analysis application object which computer-executable, server performing the same and storage media storing the same | |
| CN110955409A (en) | Method and device for creating resources on cloud platform | |
| CN111858296A (en) | Interface test method, device, equipment and storage medium | |
| KR20130053027A (en) | Method and apparatus for providing data about abnormal termination of program | |
| CN108197914B (en) | Information acquisition method and device and server | |
| CN110730092B (en) | Method and device for debugging gateway | |
| CN117495544A (en) | Sandbox-based wind control evaluation method, sandbox-based wind control evaluation system, sandbox-based wind control evaluation terminal and storage medium | |
| CN110175915B (en) | Service execution result obtaining method and system based on block chain | |
| CN106570685B (en) | Service processing method and device | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN112990902A (en) | Service processing method, device, computer equipment and storage medium | |
| CN108108369B (en) | Method and device for processing calling error of common interface library | |
| CN111901299A (en) | Application authentication method and device, electronic equipment and storage medium | |
| CN113094281B (en) | Test method and device for hybrid App | |
| CN104348698B (en) | Message reminding method and device based on instant messaging service | |
| CN110738470A (en) | Electronic bill processing method and device, storage medium and equipment | |
| CN116501414B (en) | Resource control method, device, medium and computing equipment based on cloud platform | |
| CN117234949B (en) | Test data noise reduction method and device, storage medium and computer equipment | |
| CN110874228B (en) | Service integration method, device and equipment in application program |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201012 Address after: English genus Applicant after: Innovative advanced technology Co.,Ltd. Address before: English genus Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201012 Address after: English genus Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |