WO2019134361A1

WO2019134361A1 - Method and device for calling an interface and responding to an interface call, electronic device, and medium

Info

Publication number: WO2019134361A1
Application number: PCT/CN2018/097311
Authority: WO
Inventors: 丁晶晶; 徐国诚
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2018-01-02
Filing date: 2018-07-27
Publication date: 2019-07-11
Also published as: CN108365961A; CN108365961B

Abstract

The present invention is applicable to the technical field of the Internet, and provides a method and device for calling an interface and responding to an interface call, an electronic device, and a medium. The method for calling an interface comprises: receiving a device identifier of a mobile device, interface parameters, and an interface verification SMS message; extracting an interface verification code from the interface verification SMS message; performing a signing operation on a digest of the interface verification code and respectively encrypting the interface parameters on the basis of an algorithm corresponding to the device identifier, to obtain an interface encryption field and a verification code signature field; assembling the device identifier, the interface encryption field, and the verification code signature field into an interface call request, and sending the interface call request to a server, so as to improve the automation level and security of interface calls.

Description

Interface call and interface call response method, device, electronic device and medium

This application claims the priority of the Chinese patent application filed on January 2, 2018, the Chinese Patent Office, the application number is 201810001742.4, and the invention name is "interface calling method and terminal device, response method and server called interface", all contents thereof This is incorporated herein by reference.

Technical field

The present application belongs to the field of Internet technologies, and in particular, to an interface calling method and a terminal device, a response method for an interface call, and a server.

Background technique

At present, many terminal devices need to call related interfaces from the server when implementing certain functions. Generally, after inputting the parameters of the interface to be called, the user of the terminal device needs to manually perform subsequent operations to implement the interface call, which gives The user has brought great inconvenience. In order to make the terminal device more convenient for users, there are some methods for automatically calling the interface in the prior art, but when the server needs the terminal device to provide the verification code, the existing interface automatic calling method cannot be implemented.

In addition, the existing automatic call method of the interface also has a problem of low security, which may cause user data or server interface data to be stolen during the automatic call process.

In summary, the prior art has a problem of low automation and poor security when making interface calls.

technical problem

The prior art has a problem of poor security in the interface call and save process.

Technical solution

A first aspect of the embodiment of the present application provides an interface calling method, including:

Receiving a device identifier of the mobile device, an interface parameter, and an interface verification message sent by the server to the mobile device; extracting an interface verification code from the interface verification short message; determining an encryption algorithm according to the device identifier, and using the encryption algorithm Encrypting the interface parameter to generate an interface encryption field; calculating a summary of the interface verification code as a verification code digest; determining a signature key according to the device identifier, and performing the verification code digest by using the signature key The signature operation generates a verification code signature field; assembles the device identifier, the interface encryption field, and the verification code signature field into an interface call request, and sends the interface call request to the server.

A second aspect of the embodiment of the present application provides a response method for an interface call, including:

Receiving an interface call request sent by the terminal; parsing the device identifier, the interface encryption field, and the verification code signature field of the mobile device from the interface call request; determining a signature key according to the device identifier, and using the signature key pair The verification code signature field performs a decoding operation to obtain a verification code digest; and the interface verification code is restored according to the verification code digest; if the interface verification code is the same as the interface verification code sent by the server to the mobile device, Determining a decryption algorithm by using the decryption algorithm, and performing decryption calculation on the interface encryption field by using the decryption algorithm to generate an interface parameter; if the server has a parameter consistent with the interface parameter, corresponding to the interface parameter The interface logic processes the to-be-processed data sent by the terminal.

A third aspect of the embodiments of the present application provides an interface calling apparatus, where the interface calling apparatus includes a module for executing the interface calling method described in the above first aspect.

A fourth aspect of the embodiments of the present application provides a response device for an interface call, the interface calling device comprising a module for executing the interface calling method described in the second aspect above.

A fifth aspect of the embodiments of the present application provides an electronic device including a memory and a processor, wherein the memory stores computer readable instructions executable on the processor, the processor executing the computer The steps of the interface invocation method as described in the first aspect are implemented when the instruction is read.

A sixth aspect of the embodiments of the present application provides an electronic device including a memory and a processor, wherein the memory stores computer readable instructions executable on the processor, the processor executing the computer The step of implementing the response method of the interface call as described in the second aspect when the instruction is read.

A seventh aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions, the computer readable instructions being executed by a processor to implement the first aspect as described in the first aspect The steps of the interface call method.

An eighth aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions, the computer readable instructions being executed by a processor to implement the second aspect The steps of the response method.

Beneficial effect

In the embodiment of the present application, by receiving the device identifier, the interface parameter, and the interface verification short message of the mobile device, the interface verification code is extracted from the interface verification short message, and the abstract of the interface verification code is respectively performed according to the algorithm corresponding to the device identifier. And encrypting the interface parameters, obtaining the interface encryption field and the verification code signature field, and assembling the device identification, the interface encryption field, and the verification code signature field into an interface call request, and sending the interface call request to the server to improve the interface call. The level of automation and safety.

DRAWINGS

1 is a flowchart of an implementation of an interface calling method provided by an embodiment of the present application;

2 is a specific implementation flowchart of an interface calling method S102 provided by an embodiment of the present application;

3 is a flowchart of additional extraction of a verification code provided by an embodiment of the present application;

4 is a flowchart of an implementation of a response method of an interface call provided by an embodiment of the present application;

FIG. 5 is a structural block diagram of an interface calling apparatus according to an embodiment of the present application;

6 is a structural block diagram of a response device for an interface call provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a terminal device according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a server provided by an embodiment of the present application.

Embodiments of the invention

In order to explain the technical solutions described in the present application, the following description will be made by way of specific embodiments.

FIG. 1 shows an implementation flow of an interface calling method provided by an embodiment of the present application, where the method flow includes steps S101 to S106. The specific implementation principle of each step is as follows.

S101: Receive a device identifier of the mobile device, an interface parameter, and an interface verification short message sent by the server to the mobile device.

In the embodiment of the present application, there is a terminal device, a mobile device, and a server, where the terminal device is configured to invoke an interface of the server to implement a function that the user needs to invoke, and the mobile device is configured to receive an interface verification short message sent by the server, and the server is configured to respond to the terminal device. The interface calls the request to provide the corresponding service for the terminal device.

Illustratively, in our daily life, sometimes when we want to use a certain function of a webpage through a computer, the webpage often sends a text message containing a verification code to our mobile phone. When we input the verification code in the short message through the computer, the computer You can use some feature of the web page. In this example, the computer is used as the terminal device in the embodiment of the present application, and the mobile phone is used as the mobile device, and the server of the web page is used as the server in the embodiment of the present application.

It can be understood that the execution entity of the embodiment of the present application is not necessarily a terminal device different from the mobile device, and the mobile device and the terminal device may also be the same device. For example, the mobile phone can be used as a mobile device that receives a short message including a verification code, or as a terminal device that invokes an interface of the server.

Optionally, in the embodiment of the present application, the device identifier of the mobile device may be a physical address of the mobile device, a CPU identifier, or a model of the mobile phone, so the device identifier of the mobile device may be a unique identifier or may be The same as other mobile devices is just an identifier for distinguishing categories.

Specifically, the interface parameter is input by the user, and is used to indicate to the server which parameter the interface needs to be invoked. It can be understood that after receiving the interface parameter, the server can provide the corresponding service to the terminal device according to the interface parameter.

Specifically, as described above, the interface verification short message includes a verification code, and only after the correct verification code is input through the terminal device, the server may respond to the terminal device's interface call request. It can be understood that if the terminal device and the mobile device are different devices, the mobile device needs to forward the interface verification short message to the terminal device; if the terminal device and the mobile device are the same device, the terminal device can directly analyze the interface verification short message.

S102. Extract an interface verification code from the interface verification short message.

In the embodiment of the present application, after the terminal device interface interface verifies the short message, the interface verification code in the interface verification short message needs to be automatically extracted.

As an embodiment of the present application, as shown in FIG. 2, the foregoing S102 includes:

S1021: Identify, according to a preset keyword database, a keyword included in the interface verification short message and a key degree corresponding to the keyword, where the keyword database includes a correspondence between a keyword and a criticality.

Understandably, the interface verification message received in our daily life will include one or more keywords, according to which the location of the verification code can be locked, thereby extracting the verification code.

Exemplarily, an interface verification message is: "[Software A] 581458 (software A mobile phone verification code, please complete verification), if not, please ignore this message." Another interface verification message is: "[Software B] 934047 (Device Lock Verification Code), used for device verification with QQ number 12345678 login, please do not forward. If you do not want to receive such SMS, please reply T", in these two In the interface verification message, words such as "verification code" and "verification" can be used as keywords.

Understandably, not all interface verification messages have such obvious keywords as "verification code". For example, an interface verification message is: "[Software C] You are requesting to call the X function, please call 29834918", There is no "verification code" or "verification" as a keyword in this interface verification message.

As described in the above example, in order to respond to various interfaces to verify the diversity of keywords in a short message, the embodiment of the present application verifies a short message through a massive interface, and summarizes a keyword database, which contains multiple keys. word. In addition, since it is considered that an interface verification message may contain a plurality of keywords, and the probability of occurrence of a verification code in the periphery of different keywords in the interface verification message is different, each keyword is given a critical degree, so The keyword database also includes the correspondence between keywords and criticality. It can be understood that the higher the criticality of a keyword, the greater the probability that a verification code appears around the keyword.

Specifically, based on the keyword database, the keyword included in the interface verification short message can be identified by the text recognition algorithm.

S1022: Determine the number of keywords included in the interface verification short message.

As described above, an interface verification short message may include one or more keywords. In the embodiment of the present application, a method for verifying a short message by processing an interface containing only one keyword and an interface verifying a short message with multiple keywords are processed. The method is different, so it is necessary to first judge the number of keywords identified by the above-described text recognition algorithm.

S1023: If the interface verification message includes only one keyword, the number existing between the preset blocking flag before the keyword and the preset blocking flag after the keyword is used as the Interface verification code.

In the embodiment of the present application, in order to identify the verification code in the interface verification short message, in addition to identifying the keyword, it is necessary to identify the preset isolation flag. Alternatively, a partial punctuation mark can be used as a preset cutoff mark.

Exemplarily, as described in the above example: an interface verification message is: "[Software A] 581458 (software A mobile phone verification code, please complete verification), if not, please ignore this message." The punctuation mark "]" and the punctuation mark "," can be used as two preset cutoff marks. It can be understood that, since the verification code appears in the context of the keyword in the interface verification short message, and the number of characters is relatively small, the interval in which the verification code is located can be determined by identifying the preset blocking flag. Further, a number existing between the preset cutoff flag before the keyword and the preset cutoff flag after the keyword is used as the interface verification code. It can be understood that the reason why the embodiment of the present application does not directly detect the number in the short message verification is because the excuses verify that there are often multiple numbers in the short message, such as a verification code, a time, a mobile phone number, a qq number, or other login account. Therefore, it is necessary to determine the interval in which the verification code may exist, and then perform digital extraction. Notably, in the embodiment of the present application, not all the punctuation marks are directly used as the preset blocking flag, but the preset blocking flag is determined according to the massive interface verification code short message.

Exemplarily, if the word "verification code" is a keyword, the punctuation mark "]" and the punctuation mark "," are preset partition marks, still the above example is taken as an example: an interface verification message is: "[Software A] 581458 (Software A mobile phone verification code, please complete the verification), if you are not operating, please ignore this SMS. The preset partition mark before the keyword is "]", and the preset cutoff flag after the keyword is ",", so the "] 581458 can be intercepted from the interface verification message by two preset cutoff flags (software A mobile phone verification) Code, please complete the verification),", by identifying the number in the section, get "581458" as the verification code in the interface verification SMS.

Optionally, the method for setting a preset blocking flag includes: selecting a punctuation mark whose appearance frequency is greater than or equal to the first frequency threshold from the plurality of interface verification short messages, to obtain a first symbol group; and calculating each of the first symbols The punctuation marks in the group appear in the frequency between the verification code and the keyword as the second frequency of each punctuation mark; the punctuation symbol in the first symbol group whose second frequency is greater than the second frequency threshold is deleted to obtain the second a symbol group; the punctuation marks in the second symbol group are used as a preset blocking flag. It can be understood that the preset cutoff flag should be a punctuation symbol with a higher frequency appearing in the interface verification code short message but appearing between the verification code and the keyword, that is, the preset cutoff flag should not be verified. The code is separated from the keyword, and the part where the verification code and the keyword are co-located should be separated from the other parts.

S1024: If the interface verification message includes multiple keywords, determine a special keyword, where the special keyword is a key position among the plurality of keywords included in the interface verification short message. The highest degree keyword, and the number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword is used as the interface verification code.

Specifically, if an interface verification code may have multiple keywords, the keyword with the highest degree of criticality is selected as a special keyword from among these keywords. If there are multiple keywords with the highest degree of juxtaposition, the one with the highest position among the key points is selected as the special keyword in the interface verification short message.

In the embodiment of the present application, by extracting keywords and preset partition marks, the interval of the verification code in the interface verification short message is divided, and the number of the interval is extracted as a verification code, thereby realizing automatic analysis of the interface verification short message. Extract the verification code without human intervention to improve the automation of the entire interface call process.

If an interface is verified to have multiple keywords in a short message, there may be cases where the special keyword is not accurately located, so that the verification code may be incorrectly extracted. On the other hand, some short messages may not have clear keywords, or the location relationship between the verification code and the keyword in the interface verification message is special, which may also lead to error in the verification code extraction. It can be understood that, if the verification code is incorrectly extracted, after the interface call request is sent to the server, the verification code that is fed back by the server does not match the response. In order to better cope with the above situation, FIG. 3 shows the embodiment of the present application. The verification code additional extraction process is provided, and the specific implementation principles of each step are as follows.

S301. If the verification code fed back by the server does not match the response, determine, according to the preset keyword database, whether the interface verifies that there is a legacy keyword in the short message.

The legacy keyword is a keyword that is not used to extract the interface verification code, and the keyword database includes a correspondence between a keyword and a criticality. The embodiment of the present application is configured to cope with a process of receiving a verification code that does not match the feedback of the server, and the method for extracting the keyword in the short message according to the keyword database is introduced in other embodiments of the invention. I will not repeat them here. It can be understood that, since the verification code that is fed back by the server does not match the response, it is proved that the interface verification code has been extracted by a keyword. Therefore, in the embodiment of the present application, it is required to determine whether the interface verification message is still not used. The keyword that extracts the interface verification code is the legacy keyword. It can be understood that the judgment result is divided into three kinds of cases, namely: 1, there is one legacy keyword; 2, there are multiple legacy keywords; 3, there is no legacy keyword. In the embodiment of the present application, there are three different processing methods for the above three cases.

S302. If one of the legacy keywords exists in the interface verification short message, the number existing between the preset cutoff flag before the legacy keyword and the preset cutoff flag after the legacy keyword is used as a number. The interface verification code.

It can be understood that if there is only one legacy keyword, the method for extracting the interface verification code according to the keyword and the preset partition flag introduced in the above embodiment is extracted in this step by the legacy keyword and the preset partition flag. Interface verification code.

S303. If the interface verification short message includes a plurality of the legacy keywords, determining a special keyword, where the special keyword is the most located among the plurality of the legacy keywords included in the interface verification short message. a previous keyword with the highest degree of criticality, and a number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the Interface verification code.

It can be understood that if there are multiple legacy keywords, one special keyword is selected from these legacy keywords again, and the interface verification code is extracted again based on the special keyword and the preset partition flag.

S304. If the legacy keyword is not present in the interface verification short message, notify the user to view the verification short message or notify the server to resend the new verification short message.

In the embodiment of the present application, if there is no legacy keyword in the interface verification short message, the method for extracting the verification code from the interface verification short message introduced in the above embodiment is not applicable to the current interface verification short message. Alternatively, since an unexpected situation may occur, the server may be notified in this case to resend an interface verification short message to the mobile device to re-analyze and extract the verification code based on the new interface verification message. Optionally, since the method introduced in the foregoing embodiment may not be applicable to the phrase arrangement rule of the current interface verification code short message, the verification code cannot be automatically identified, so the user needs to be notified to check the verification code received by the mobile device, and manually input the verification code. Code to get the interface. Optionally, although the method introduced in the foregoing embodiment may not be applicable to the phrase arrangement rule of the current interface verification code short message, other methods for automatically identifying the verification code in the interface verification code short message may be automatically switched. For example, instead of keywords, the number in the short message is directly recognized as a verification code. In the embodiment of the present application, by determining whether the interface has a legacy keyword in the short message, different processing methods are respectively performed on the three situations, thereby improving the ability to respond to different interfaces for verifying the short message.

S103. Determine an encryption algorithm according to the device identifier, and encrypt the interface parameter by using the encryption algorithm to generate an interface encryption field.

In the embodiment of the present application, in order to ensure that others cannot steal interface parameters during the interface call, the interface parameters need to be encrypted. Notably, in the embodiment of the present application, the device identifiers of different mobile devices may correspond to different encryption algorithms, so that others cannot know which algorithm to encrypt the interface parameters, and thus cannot be based on the known corresponding algorithm. The interface encryption field is decrypted.

S104. Calculate a summary of the interface verification code as a verification code digest.

In the embodiment of the present application, if the verification code is stolen by others during the process of the interface call, the other person may invoke the relevant interface based on the verification code, so that the verification code loses the original meaning, in order to ensure the verification code is in the interface. For security in the transmission process of the call, the embodiment of the present application encrypts the verification code by using a signature algorithm. In order to encrypt the verification code by the signature algorithm, it is necessary to first calculate a summary of the verification code. Alternatively, the digest of the verification code can be calculated by the existing MD5 algorithm.

S105. Determine a signature key according to the device identifier, and perform a signature operation on the verification code digest by using the signature key to generate a verification code signature field.

In the embodiment of the present application, different mobile device identifiers correspond to different signature keys to prevent others from decoding the verification code signature field after intercepting the signature key, and obtaining a verification code. Specifically, in the embodiment of the present application, one signature key includes two parameters. Assume that the signature key corresponding to a device identifier includes d and n according to a preset device identifier and a signature key mapping table. Then, the verification code signature field is calculated by a formula: S=(h(m)^d) mod n, where S is the verification code signature field, h(m) is a verification code digest, and the symbol ^ is a power operator And the symbol mod is the remainder operator. In the embodiment of the present application, the interface parameters and the verification code are separately encrypted by different algorithms, and the selected algorithm is related to the device identifier, and different device identifiers may correspond to different algorithms, which greatly improves some important functions in the interface calling process. The data security of the data.

S106. Assemble the device identifier, the interface encryption field, and the verification code signature field into an interface call request, and send the interface call request to the server.

FIG. 4 shows an implementation flow of a response method for an interface call provided by an embodiment of the present application, where the method flow includes steps S401 to S407. The specific implementation principle of each step is as follows.

S401. Receive an interface call request sent by the terminal device.

In the embodiment of the present application, there are a terminal device, a mobile device, and a server, where the terminal device is configured to invoke an interface of the server to implement a function that the user needs to invoke, and the mobile device is configured to receive an interface verification short message sent by the server, and the server is configured to respond to the terminal. The interface of the device invokes the request to provide the corresponding service for the terminal device.

In the embodiment of the present application, the interface call request is sent by the terminal device, and the server needs to verify the related data in the interface call request, and determine whether to use the relevant interface logic to process the data for the terminal device.

S402. Parse the device identifier, the interface encryption field, and the verification code signature field of the mobile device from the interface call request.

Since the terminal device assembles the device identification, the interface encryption field, and the verification code signature field into an interface call request on the terminal device side, the server side needs to separate the three types of data from the interface call request.

S403. Determine a signature key according to the device identifier, and perform a decoding operation on the verification code signature field by using the signature key to obtain a verification code digest.

Exemplarily, it is assumed that on the terminal device side, the signature keys corresponding to one device identifier include parameters d and n, respectively. Moreover, the verification code signature field is calculated by a formula: S=(h(m)^d) mod n, where S is the verification code signature field, h(m) is a verification code digest, and the symbol ^ is a power calculation. The character and the symbol mod are the remainder operators.

On the server side, the signature key is also determined by the device identifier, and the verification code summary field is calculated by the inverse process of the signature calculation. For example, in this example, by the formula S=(h(m)^d) the inverse of mod n The process calculates the verification code signature field S on the premise that the verification code signature field S and the parameters d and n of the signature key are known.

S404. Restore an interface verification code according to the verification code digest.

It can be understood that, according to the inverse process of the digest algorithm on the terminal device side, the verification code digest can be restored to the interface verification code, notably, the algorithm for calculating the verification code digest of the verification code or the algorithm for restoring the verification code from the verification code digest and There is no need to distinguish between different mobile devices or terminal devices. In the embodiment of the present invention, the MD5 algorithm or other algorithm for calculating the digest can be used to calculate the verification code received by each mobile device. Therefore, in the embodiment of the present application, the MD5 algorithm or other calculation digest can also be uniformly used. The algorithm restores the verification code digest.

S405. Determine whether the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device.

In the embodiment of the present application, the server stores a verification code sent to each mobile device in a preset unit time period, and the server may find an interface verification code sent to the mobile device by using the device identifier of the mobile device, so that the server can determine The interface verification code parsed in the port invocation request is the same as the interface verification code sent by the server to the mobile device.

S406. If the interface verification code restored from the verification code digest is different from the interface verification code sent by the server to the mobile device, send a verification code mismatch notification to the mobile device.

In the embodiment of the present application, the server sends a verification code mismatch notification to the mobile device, which is convenient for prompting the user to request the verification code again, or reminding the user that the related data may be being stolen by others.

S407, if the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device, determining a decryption algorithm according to the device identifier, and using the decryption algorithm to the interface The encrypted field is decrypted and calculated to generate interface parameters.

It can be understood that, in the embodiment of the present application, the server can also determine the corresponding decryption algorithm according to the device identifier, and the decryption algorithm is The interface encryption field performs decryption calculation and generates interface parameters.

S408. If a parameter that is consistent with the interface parameter exists in the server, process the to-be-processed data sent by the terminal according to the interface logic corresponding to the interface parameter.

It is to be understood that the purpose of the interface parameter input by the user in the terminal device is to invoke the relevant interface of the server. Therefore, in the embodiment of the present application, the server needs to determine whether the interface parameter of the interface exists in the interface and the interface call request sent by the terminal device. The interface parameters are the same. If they are consistent, the data to be processed sent by the terminal is processed according to the interface logic corresponding to the interface parameter.

In the embodiment of the present application, the interface is invoked by the interface that is sent by the terminal device; the device identifier, the interface encryption field, and the verification code signature field of the mobile device are parsed from the interface call request; the signature key is determined according to the device identifier, and the signature is obtained. The key is decoded by the verification code signature field to obtain a verification code digest; the interface verification code is restored according to the verification code digest; if the interface verification code is the same as the interface verification code sent by the server to the mobile device, the decryption algorithm is determined according to the device identifier. And decrypting the interface encryption field by using a decryption algorithm to generate an interface parameter; if the server has a parameter consistent with the interface parameter, processing the to-be-processed data sent by the terminal according to the interface logic corresponding to the interface parameter, to automatically verify the terminal device The sent interface calls the request to increase the automation of the entire system.

It should be understood that the size of the sequence of the steps in the above embodiments does not mean that the order of execution is performed. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Corresponding to the interface calling method described in the foregoing embodiment, FIG. 5 is a structural block diagram of the interface calling device provided by the embodiment of the present application. For the convenience of description, only the parts related to the embodiment of the present application are shown.

Referring to Figure 5, the apparatus includes:

The receiving unit 51 is configured to receive a device identifier of the mobile device, an interface parameter, and an interface verification short message sent by the server to the mobile device, and an extracting unit 52, configured to extract an interface verification code from the interface verification short message, and the generating unit 53 And determining, by the device identifier, an encryption algorithm, and encrypting the interface parameter by using the encryption algorithm to generate an interface encryption field; and the calculating unit 54 is configured to calculate a summary of the interface verification code, as a verification code summary. a signature unit 55, configured to determine a signature key according to the device identifier, and perform a signature operation on the verification code digest by using the signature key to generate a verification code signature field; and an assembly unit 56, configured to: use the device The identification, the interface encryption field, and the verification code signature field are assembled into an interface call request, and the interface call request is sent to the server.

Optionally, the signature unit 55 includes:

a parameter determining subunit, configured to determine the signature key according to a preset correspondence between a device identifier and a signature key, where the signature key includes a parameter d and a parameter n; and the digest calculation subunit is used to pass the formula S =(h(m)^d) mod n calculates the verification code signature field, where S is the verification code signature field, h(m) is the verification code digest, the symbol ^ is the power operator, and the symbol mod is taken Remainder operator.

Corresponding to the response method of the interface call described in the above embodiment, FIG. 6 is a structural block diagram of the response device of the interface call provided by the embodiment of the present application. For the convenience of description, only the related to the embodiment of the present application is shown. section.

The receiving unit 61 is configured to receive an interface call request sent by the terminal device. The parsing unit 62 is configured to parse out the device identifier, the interface encryption field, and the verification code signature field of the mobile device from the interface call request. The decoding unit 63 is configured to determine a signature key according to the device identifier, and perform a decoding operation on the verification code signature field by using the signature key to obtain a verification code digest. The restoring unit 64 is configured to restore the interface verification code according to the verification code digest. The determining unit 65 is configured to determine whether the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device. The first execution unit 66 is configured to: if the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device, determine a decryption algorithm according to the device identifier, and pass the The decryption algorithm performs decryption calculation on the interface encryption field to generate an interface parameter. The second execution unit 67 is configured to process the to-be-processed data sent by the terminal according to the interface logic corresponding to the interface parameter, if a parameter that is consistent with the interface parameter exists in the server.

FIG. 7 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 7, the terminal device 7 of this embodiment includes a processor 70, a memory 71, and computer readable instructions 72 stored in the memory 71 and operable on the processor 70, such as an interface caller. . The processor 70, when executing the computer readable instructions 72, implements the steps in the various interface invocation method embodiments described above, such as steps 101 through 106 shown in FIG. Alternatively, the processor 70, when executing the computer readable instructions 72, implements the functions of the various modules/units in the various apparatus embodiments described above, such as the functions of the units 51-56 shown in FIG.

Illustratively, the computer readable instructions 72 may be partitioned into one or more modules/units that are stored in the memory 71 and executed by the processor 70, To complete this application. The terminal device 7 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The processor 70 can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits (Application). Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, the memory 71 may be an internal storage unit of the terminal device 7, such as a hard disk of the terminal device 7. Or memory.

FIG. 8 is a schematic diagram of a server according to an embodiment of the present application. As shown in FIG. 8, the server 8 of this embodiment includes a processor 80, a memory 81, and computer readable instructions 82 stored in the memory 81 and executable on the processor 80, such as an interface call response. program. The processor 80 executes the computer readable instructions 82 to implement the steps in the response method embodiments of the various interface calls described above, such as steps 401 through 407 shown in FIG. Alternatively, when the processor 80 executes the computer readable instructions 82, the functions of the various modules/units in the various apparatus embodiments described above are implemented, such as the functions of the units 66 through 67 shown in FIG.

Illustratively, the computer readable instructions 82 may be partitioned into one or more modules/units that are stored in the memory 81 and executed by the processor 80, To complete this application. The server 8 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The server may include, but is not limited to, a processor 80, a memory 81. It will be understood by those skilled in the art that FIG. 8 is merely an example of the server 8, does not constitute a limitation of the server 8, may include more or less components than those illustrated, or combine some components, or different components, such as The server may also include an input and output device, a network access device, a bus, and the like.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims

An interface calling method, comprising:

Receiving a device identifier of the mobile device, an interface parameter, and an interface verification message sent by the server to the mobile device;

Extracting an interface verification code from the interface verification short message;

Determining an encryption algorithm according to the device identifier, and encrypting the interface parameter by using the encryption algorithm to generate an interface encryption field;

Calculating a summary of the interface verification code as a verification code summary;

Determining a signature key according to the device identifier, and performing a signature operation on the verification code digest by using the signature key to generate a verification code signature field;

The device identifier, the interface encryption field, and the verification code signature field are assembled into an interface call request, and the interface call request is sent to the server.
The method for invoking an interface according to claim 1, wherein the extracting the interface verification code from the interface verification short message comprises:

Determining, according to a preset keyword database, a keyword included in the interface verification short message and a key degree corresponding to the keyword, where the keyword database includes a correspondence between a keyword and a criticality;

If the interface verification message includes only one of the keywords, the number existing between the preset blocking flag before the keyword and the preset blocking flag after the keyword is used as the interface verification. code;

If the interface verification message includes a plurality of the keywords, determining a special keyword, where the special keyword is the highest priority among the plurality of keywords included in the interface verification message And a number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code.
The interface calling method according to claim 1, wherein the determining a signature key according to the device identifier, and performing a signature operation on the verification code digest by using the signature key to generate a verification code signature field, include:

Determining, according to a preset correspondence between the device identifier and the signature key, the signature key, where the signature key includes a parameter d and a parameter n;

The verification code signature field is calculated by the formula S=(h(m)^d) mod n, where S is the verification code signature field, h(m) is the verification code digest, the symbol ^ is the power operator, and the symbol Mod is the remainder operator.
The interface calling method according to claim 1, further comprising:

If the verification code received by the server does not match the response, determining, according to the preset keyword database, whether the interface verifies that there is a legacy keyword in the short message, and the legacy keyword is not used to extract the interface verification code. Keywords, the keyword database includes a correspondence between keywords and critical degrees;

If there is one of the legacy keywords in the interface verification short message, the number existing between the preset cutoff flag before the legacy keyword and the preset cutoff flag after the legacy keyword is used as the Interface verification code;

If the interface verification message includes a plurality of the legacy keywords, determining a special keyword, where the special keyword is the top position among the plurality of the legacy keywords included in the interface verification short message a legacy keyword having the highest degree of criticality, and verifying the number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code;

If the legacy keyword is not present in the interface verification message, the user is notified to view the verification message or the notification server resends the new verification message.
A response method for an interface call, comprising:

Receiving an interface call request sent by the terminal device;

Parsing out a device identifier, an interface encryption field, and a verification code signature field of the mobile device from the interface call request;

Determining a signature key according to the device identifier, and performing a decoding operation on the verification code signature field by using the signature key to obtain a verification code digest;

Restore an interface verification code according to the verification code digest;

And if the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device, determining a decryption algorithm according to the device identifier, and encrypting the field by using the decryption algorithm Perform decryption calculation to generate interface parameters;

And if the parameter is consistent with the interface parameter, the to-be-processed data sent by the terminal is processed according to the interface logic corresponding to the interface parameter.
An interface calling device, comprising:

a receiving unit, configured to receive a device identifier of the mobile device, an interface parameter, and an interface verification short message sent by the server to the mobile device;

An extracting unit, configured to extract an interface verification code from the interface verification short message;

a generating unit, configured to determine an encryption algorithm according to the device identifier, and encrypt the interface parameter by using the encryption algorithm to generate an interface encryption field;

a calculation unit, configured to calculate a summary of the interface verification code, as a verification code summary;

a signature unit, configured to determine a signature key according to the device identifier, and perform a signature operation on the verification code digest by using the signature key to generate a verification code signature field;

And an assembly unit, configured to assemble the device identifier, the interface encryption field, and the verification code signature field into an interface call request, and send the interface call request to the server.
The interface calling device according to claim 6, wherein the extracting the interface verification code from the interface verification short message comprises:

Determining, according to a preset keyword database, a keyword included in the interface verification short message and a key degree corresponding to the keyword, where the keyword database includes a correspondence between a keyword and a criticality;

If the interface verification message includes only one of the keywords, the number existing between the preset blocking flag before the keyword and the preset blocking flag after the keyword is used as the interface verification. code;

If the interface verification message includes a plurality of the keywords, determining a special keyword, where the special keyword is the highest priority among the plurality of keywords included in the interface verification message And a number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code.
The interface calling device according to claim 6, wherein the determining a signature key according to the device identifier, and performing a signature operation on the verification code digest by using the signature key to generate a verification code signature field, include:

Determining, according to a preset correspondence between the device identifier and the signature key, the signature key, where the signature key includes a parameter d and a parameter n;

The verification code signature field is calculated by the formula S=(h(m)^d) mod n, where S is the verification code signature field, h(m) is the verification code digest, the symbol ^ is the power operator, and the symbol Mod is the remainder operator.
The interface calling device according to claim 6, further comprising:

If the verification code received by the server does not match the response, determining, according to the preset keyword database, whether the interface verifies that there is a legacy keyword in the short message, and the legacy keyword is not used to extract the interface verification code. Keywords, the keyword database includes a correspondence between keywords and critical degrees;

If there is one of the legacy keywords in the interface verification short message, the number existing between the preset cutoff flag before the legacy keyword and the preset cutoff flag after the legacy keyword is used as the Interface verification code;

If the interface verification message includes a plurality of the legacy keywords, determining a special keyword, where the special keyword is the top position among the plurality of the legacy keywords included in the interface verification short message a legacy keyword having the highest degree of criticality, and verifying the number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code;

If the legacy keyword is not present in the interface verification message, the user is notified to view the verification message or the notification server resends the new verification message.
A response device called by an interface, comprising:

The receiving unit is configured to receive an interface call request sent by the terminal device.

And a parsing unit, configured to parse out a device identifier, an interface encryption field, and a verification code signature field of the mobile device from the interface call request.

And a decoding unit, configured to determine a signature key according to the device identifier, and perform a decoding operation on the verification code signature field by using the signature key to obtain a verification code digest.

And a restoring unit, configured to restore the interface verification code according to the verification code digest.

The determining unit 65 is configured to determine whether the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device.

a first execution unit, configured to: if an interface verification code restored from the verification code digest is the same as an interface verification code sent by the server to the mobile device, determine a decryption algorithm according to the device identifier, and perform the decryption by using the The algorithm performs decryption calculation on the interface encryption field to generate an interface parameter.

The second execution unit is configured to process the to-be-processed data sent by the terminal according to the interface logic corresponding to the interface parameter, if a parameter that is consistent with the interface parameter exists in the server.
An electronic device, comprising: a memory and a processor, wherein the memory stores computer readable instructions executable on the processor, and the processor implements the following steps when the computer readable instructions are executed :

Receiving a device identifier of the mobile device, an interface parameter, and an interface verification message sent by the server to the mobile device;

Extracting an interface verification code from the interface verification short message;

Determining an encryption algorithm according to the device identifier, and encrypting the interface parameter by using the encryption algorithm to generate an interface encryption field;

Calculating a summary of the interface verification code as a verification code summary;

Determining a signature key according to the device identifier, and performing a signature operation on the verification code digest by using the signature key to generate a verification code signature field;

The device identifier, the interface encryption field, and the verification code signature field are assembled into an interface call request, and the interface call request is sent to the server.
The electronic device according to claim 11, wherein the extracting the interface verification code from the interface verification short message comprises:

Determining, according to a preset keyword database, a keyword included in the interface verification short message and a key degree corresponding to the keyword, where the keyword database includes a correspondence between a keyword and a criticality;

If the interface verification message includes only one of the keywords, the number existing between the preset blocking flag before the keyword and the preset blocking flag after the keyword is used as the interface verification. code;

If the interface verification message includes a plurality of the keywords, determining a special keyword, where the special keyword is the highest priority among the plurality of keywords included in the interface verification message And a number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code.
The electronic device according to claim 11, wherein the determining a signature key according to the device identifier, and performing a signature operation on the verification code digest by using the signature key to generate a verification code signature field, including :

Determining, according to a preset correspondence between the device identifier and the signature key, the signature key, where the signature key includes a parameter d and a parameter n;

The verification code signature field is calculated by the formula S=(h(m)^d) mod n, where S is the verification code signature field, h(m) is the verification code digest, the symbol ^ is the power operator, and the symbol Mod is the remainder operator.
The electronic device according to claim 11, further comprising:

If the verification code received by the server does not match the response, determining, according to the preset keyword database, whether the interface verifies that there is a legacy keyword in the short message, and the legacy keyword is not used to extract the interface verification code. Keywords, the keyword database includes a correspondence between keywords and critical degrees;

If there is one of the legacy keywords in the interface verification short message, the number existing between the preset cutoff flag before the legacy keyword and the preset cutoff flag after the legacy keyword is used as the Interface verification code;

If the interface verification message includes a plurality of the legacy keywords, determining a special keyword, where the special keyword is the top position among the plurality of the legacy keywords included in the interface verification short message a legacy keyword having the highest degree of criticality, and verifying the number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code;

If the legacy keyword is not present in the interface verification message, the user is notified to view the verification message or the notification server resends the new verification message.
An electronic device, comprising: a memory and a processor, wherein the memory stores computer readable instructions executable on the processor, and the processor implements the following steps when the computer readable instructions are executed :

Receiving an interface call request sent by the terminal device;

Parsing out a device identifier, an interface encryption field, and a verification code signature field of the mobile device from the interface call request;

Determining a signature key according to the device identifier, and performing a decoding operation on the verification code signature field by using the signature key to obtain a verification code digest;

Restore an interface verification code according to the verification code digest;

And if the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device, determining a decryption algorithm according to the device identifier, and encrypting the field by using the decryption algorithm Perform decryption calculation to generate interface parameters;

And if the parameter is consistent with the interface parameter, the to-be-processed data sent by the terminal is processed according to the interface logic corresponding to the interface parameter.
A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by at least one processor, implement the following steps:

Receiving a device identifier of the mobile device, an interface parameter, and an interface verification message sent by the server to the mobile device;

Extracting an interface verification code from the interface verification short message;

Determining an encryption algorithm according to the device identifier, and encrypting the interface parameter by using the encryption algorithm to generate an interface encryption field;

Calculating a summary of the interface verification code as a verification code summary;

Determining a signature key according to the device identifier, and performing a signature operation on the verification code digest by using the signature key to generate a verification code signature field;

The device identifier, the interface encryption field, and the verification code signature field are assembled into an interface call request, and the interface call request is sent to the server.
The computer readable storage medium according to claim 16, wherein the extracting the interface verification code from the interface verification short message comprises:

Determining, according to a preset keyword database, a keyword included in the interface verification short message and a key degree corresponding to the keyword, where the keyword database includes a correspondence between a keyword and a criticality;

If the interface verification message includes only one of the keywords, the number existing between the preset blocking flag before the keyword and the preset blocking flag after the keyword is used as the interface verification. code;

If the interface verification message includes a plurality of the keywords, determining a special keyword, where the special keyword is the highest priority among the plurality of keywords included in the interface verification message And a number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code.
The computer readable storage medium according to claim 16, wherein the determining a signature key according to the device identifier, and performing a signature operation on the verification code digest by the signature key to generate a verification code signature Fields, including:

Determining, according to a preset correspondence between the device identifier and the signature key, the signature key, where the signature key includes a parameter d and a parameter n;

The verification code signature field is calculated by the formula S=(h(m)^d) mod n, where S is the verification code signature field, h(m) is the verification code digest, the symbol ^ is the power operator, and the symbol Mod is the remainder operator.
The computer readable storage medium of claim 16 further comprising:

If the verification code received by the server does not match the response, determining, according to the preset keyword database, whether the interface verifies that there is a legacy keyword in the short message, and the legacy keyword is not used to extract the interface verification code. Keywords, the keyword database includes a correspondence between keywords and critical degrees;

If there is one of the legacy keywords in the interface verification short message, the number existing between the preset cutoff flag before the legacy keyword and the preset cutoff flag after the legacy keyword is used as the Interface verification code;

If the interface verification message includes a plurality of the legacy keywords, determining a special keyword, where the special keyword is the top position among the plurality of the legacy keywords included in the interface verification short message a legacy keyword having the highest degree of criticality, and verifying the number existing between the preset cutoff flag before the special keyword and the preset cutoff flag after the special keyword as the interface verification code;

If the legacy keyword is not present in the interface verification message, the user is notified to view the verification message or the notification server resends the new verification message.
A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by at least one processor, implement the following steps:

Receiving an interface call request sent by the terminal device;

Parsing out a device identifier, an interface encryption field, and a verification code signature field of the mobile device from the interface call request;

Determining a signature key according to the device identifier, and performing a decoding operation on the verification code signature field by using the signature key to obtain a verification code digest;

Restore an interface verification code according to the verification code digest;

And if the interface verification code restored from the verification code digest is the same as the interface verification code sent by the server to the mobile device, determining a decryption algorithm according to the device identifier, and encrypting the field by using the decryption algorithm Perform decryption calculation to generate interface parameters;

And if the parameter is consistent with the interface parameter, the to-be-processed data sent by the terminal is processed according to the interface logic corresponding to the interface parameter.