Call request verification

Abstract

Disclosed in the embodiments of the present specification are a call request verification method and apparatus, and a storage medium and an electronic device. The method comprises: extracting identification information of a calling end from a call request by means of code injection, and verifying the identification information, so as to obtain a verification result; and if the verification result indicates that the identification information passes the verification, executing a call process on the basis of call information, so as to obtain a call result.

Description

Call request verification Technical Field

[0001] The present invention relates to computer technology, and in particular to a method, device, storage medium and electronic device for calling request verification. Background Art

[0002] RPC (Remote Procedure Call) is a remote procedure call protocol that allows applications to call functions or methods on another device over a network, just like a local call. During the RPC call process, malicious calls must be prevented to ensure system security. Related technologies typically use methods such as username and password-based authentication, digital certificates, and authorization protocols for identity authentication and authorization.

[0003] However, these methods rely on hard coding in the framework itself and are not suitable for large-scale transformation of existing systems. Summary of the Invention

[0004] An embodiment of the present specification provides a call request verification method, which includes: in response to receiving a call request sent by a calling end, decoding the call request to obtain call information corresponding to the call request; extracting identification information of the calling end from the call request by code injection, wherein the identification information is used to represent the identity information of the calling end; verifying the identification information to obtain a verification result, wherein the verification result represents whether the identification information has passed the verification; if the verification result represents that the identification information has passed the verification, executing a call process according to the call information to obtain a call result.

[0005] Furthermore, in some embodiments, the method further includes: if the verification result indicates that the identification information has failed verification, returning prompt information indicating that the verification has failed.

[0006] Furthermore, in some implementations, extracting the identification information of the calling end from the calling request by means of code injection includes: extracting the identification information of the calling end from a request header of the calling request by means of code injection.

[0007] Further, in some embodiments, the verification of the identification information to obtain a verification result includes: obtaining a pre-configured identification information blacklist, the identification information blacklist including multiple identification information; determining whether the identification information of the calling end is included in the identification information blacklist; if the identification information blacklist includes the identification information of the calling end, generating a verification result indicating that the identification information has failed the verification; if the identification information blacklist does not include the identification information of the calling end, generating a verification result indicating that the identification information has passed the verification.

[0008] Further, in some embodiments, the verification of the identification information to obtain a verification result includes: obtaining a pre-configured identification information whitelist, the identification information whitelist including multiple identification information; determining whether the identification information of the calling end is included in the identification information whitelist; if the identification information whitelist includes the identification information of the calling end, generating a verification result indicating that the identification information has passed the verification; if the identification information whitelist does not include the identification information of the calling end, generating a verification result indicating that the identification information has not passed the verification.

[0009] An embodiment of this specification also provides a remote calling method, which is applied to the calling end, and the method includes: encapsulating the calling information to obtain an initial calling request; inserting the identification information of the calling end into the initial calling request by code injection to obtain an updated calling request; encoding the updated calling request to obtain a calling request; and sending the calling request to the server.

[0010] Further, in some embodiments, the inserting the identification information of the calling end into the initial call request by code injection to obtain an updated call request includes: inserting the identification information of the calling end into the request header of the initial call request by code injection to obtain an updated call request.

[0011] An embodiment of this specification also provides a call request verification device, including: a request receiving module, which is used to decode the call request in response to receiving a call request sent by the calling end to obtain call information corresponding to the call request; an information extraction module, which is used to extract the identification information of the calling end from the call request by code injection, and the identification information is used to represent the identity information of the calling end; a verification module, which is used to verify the identification information and obtain a verification result, and the verification result represents whether the identification information has passed the verification; an execution module, which is used to execute the call process according to the call information to obtain a call result if the verification result represents that the identification information has passed the verification.

[0012] An embodiment of this specification also provides a remote calling device, including: an information encapsulation module, used to encapsulate the calling information to obtain an initial calling request; an information insertion module, used to insert the identification information of the calling end into the initial calling request by code injection, to obtain an updated calling request; an encoding module, used to encode the updated calling request to obtain a calling request; and a sending module, used to send the calling request to the server.

[0013] An embodiment of this specification further provides a storage medium, wherein the storage medium stores a computer program, and the computer program is suitable for being loaded by a processor and executing the steps of the above method.

[0014] An embodiment of this specification further provides an electronic device, comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the above method.

[0015] An embodiment of this specification also provides a computer program product, which stores at least one instruction, and the at least one instruction is suitable for being loaded by a processor and executing the above method steps.

[0016] In the embodiments of this specification, code injection is used to extract the caller's identification information from the call request, and the identification information is verified. Finally, based on the verification result, a decision is made whether to approve the call request, ensuring that only authorized users can make calls. The call request verification method proposed in the embodiments of this specification does not require the business party to participate in coding reform. Code injection is used to complete call request verification non-invasively and efficiently, making it suitable for large-scale transformation of existing online systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a flow chart of a method for verifying a call request provided in an embodiment of this specification.

[0018] FIG2 is a flow chart of a remote calling method provided in an embodiment of this specification.

[0019] FIG3 is a schematic diagram of the structure of a call request verification device provided in an embodiment of this specification.

[0020] FIG4 is a schematic structural diagram of a remote calling device provided in an embodiment of this specification.

[0021] FIG5 is a schematic diagram of the structure of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0022] To make the objectives, technical solutions, and advantages of this specification more clear, the following will clearly and completely describe the technical solutions of this specification in conjunction with the specific embodiments of this specification and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of this specification.

[0023] Please refer to Figure 1, which is a schematic diagram of a process flow of a call request verification method provided in an embodiment of this specification. In this embodiment of this specification, the call request verification method is applied to a call request verification device or an electronic device (server) equipped with a call request verification device. The process shown in Figure 1 will be described in detail below. The call request verification method may specifically include the following steps.

[0024] S102 : In response to receiving a call request sent by the call end, decoding the call request to obtain call information corresponding to the call request.

[0025] In one or more embodiments of this specification, in response to receiving a call request sent by a caller, a server may decode the call request to obtain call information corresponding to the call request. In practice, the call request is encoded according to an agreed protocol, so that the server can decode it according to the agreed protocol to obtain the call information. The call information may include the identifier of the object to be called, input parameter values, parameter types, etc.

[0026] S104: extract identification information of the calling end from the calling request by means of code injection, where the identification information is used to represent the identity information of the calling end.

[0027] In one or more embodiments of this specification, as an example, the identification information may be an application name (App Name) or an Internet Protocol (IP) address. As another example, the identification information may also include application version information, etc.

[0028] Optionally, extracting the caller's identification information from the call request through code injection includes extracting the caller's identification information from the request header of the call request through code injection. It is understood that during the encoding phase, the caller can insert the caller's identification information into different locations in the call request, so that during the decoding phase, the server can extract the caller's identification information from the corresponding location. In practice, the caller and server can agree on the location where the identification information is to be inserted, thereby accurately extracting the caller's identification information.

[0029] S106: Verify the identification information to obtain a verification result, which indicates whether the identification information passes the verification.

[0030] In one or more embodiments of this specification, the server may verify the identification information in various ways to obtain a verification result. For example, a regular expression may be used to verify the identification information to obtain a verification result.

[0031] Optionally, the identification information is verified to obtain a verification result, including: obtaining a pre-configured identification information blacklist, the identification information blacklist including multiple identification information; determining whether the identification information of the calling end is included in the identification information blacklist; if the identification information blacklist includes the identification information of the calling end, generating a verification result indicating that the identification information has failed the verification; if the identification information blacklist does not include the identification information of the calling end, generating a verification result indicating that the identification information has passed the verification.

[0032] Optionally, the identification information is verified to obtain a verification result, including: obtaining a pre-configured identification information whitelist, the identification information whitelist including multiple identification information; determining whether the identification information whitelist includes the identification information of the calling end; if the identification information whitelist includes the identification information of the calling end, generating a verification result indicating that the identification information has passed the verification; if the identification information whitelist does not include the identification information of the calling end, generating a verification result indicating that the identification information has not passed the verification.

[0033] S108: If the verification result indicates that the identification information has passed the verification, a calling process is executed according to the calling information to obtain a calling result.

[0034] In one or more embodiments of the present specification, if the verification result indicates that the identification information has passed the verification, the call information can be passed to the call control process (RpcProcessor) to control the processing of the call process, and entrust the proxy process (RpcInvoker) provided by the RPC framework to execute the call process and return the call result.

[0035] Optionally, if the verification result indicates that the identification information fails the verification, a preset parameter value may be returned.

[0036] In one or more embodiments of this specification, code injection is used to extract the calling end's identification information from the call request, verify the identification information, and finally, based on the verification result, determine whether to release the call request, ensuring that only authorized users can make calls. The call request verification method proposed in the embodiments of this specification does not require the business side to participate in coding modifications. Code injection is used to complete call request verification non-invasively and efficiently, making it suitable for large-scale modifications to existing online systems.

[0037] Please refer to Figure 2, which is a flowchart of a remote calling method provided in an embodiment of this specification. As shown in Figure 2, the method includes the following steps.

[0038] S202: Encapsulate the call information to obtain an initial call request.

[0039] In one or more embodiments of this specification, the calling end may encapsulate the call information to obtain an initial call request. The call information may include the identifier of the object to be called, input parameter values, parameter types, etc. Based on this, the initial call request may be encapsulated according to a preset format.

[0040] S204: insert the identification information of the calling end into the initial calling request by code injection to obtain an updated calling request.

[0041] In one or more embodiments of the present specification, the identification information of the calling end may be inserted into the initial calling request to obtain an updated calling request.

[0042] S206: Encode the update call request to obtain a call request.

[0043] In one or more embodiments of the present specification, the update call request may be encoded according to a pre-agreed protocol to obtain a call request.

[0044] S208: Send the call request to the server.

[0045] In one or more embodiments of the present specification, a call request may be sent to a server.

[0046] Optionally, the identification information of the calling end is inserted into the initial calling request by code injection to obtain an updated calling request, including: inserting the identification information of the calling end into the request header of the initial calling request by code injection to obtain an updated calling request.

[0047] In one or more embodiments of this specification, code injection is used to insert the caller's identification information into a call request. This allows the server to verify the identification information and, based on the verification result, decide whether to approve the call request, ensuring that only authorized users can make calls. Furthermore, code injection allows for non-invasive identification information insertion, making it suitable for large-scale modifications to existing online systems.

[0048] Please refer to Figure 3, which is a structural diagram of a call request verification device provided in an embodiment of this specification. As shown in Figure 3, the call request verification device 1 can be implemented as all or part of an electronic device through software, hardware, or a combination of both. According to some embodiments, the call request verification device 1 includes a request receiving module 11, an information extraction module 12, a verification module 13, and an execution module 14. Among them, the request receiving module 11 is used to decode the call request in response to receiving a call request sent by the calling end to obtain call information corresponding to the call request; the information extraction module 12 is used to extract the identification information of the calling end from the call request by code injection, and the identification information is used to represent the identity information of the calling end; the verification module 13 is used to verify the identification information and obtain a verification result, and the verification result represents whether the identification information has passed the verification; the execution module 14 is used to execute the call process according to the call information to obtain a call result if the verification result represents that the identification information has passed the verification.

[0049] Optionally, the call request verification device 1 further includes a return module, which is configured to return prompt information indicating that the verification has failed if the verification result indicates that the identification information has failed the verification.

[0050] Optionally, the information extraction module 12 is specifically configured to extract identification information of the calling end from the request header of the calling request by means of code injection.

[0051] Optionally, the verification module 13 is specifically used to: obtain a pre-configured identification information blacklist, the identification information blacklist including multiple identification information; determine whether the identification information of the calling end is included in the identification information blacklist; if the identification information blacklist includes the identification information of the calling end, generate a verification result indicating that the identification information has failed the verification; if the identification information blacklist does not include the identification information of the calling end, generate a verification result indicating that the identification information has passed the verification.

[0052] Optionally, the verification module 13 is specifically used to: obtain a pre-configured identification information whitelist, the identification information whitelist includes multiple identification information; determine whether the identification information of the calling end is included in the identification information whitelist; if the identification information whitelist includes the identification information of the calling end, generate a verification result indicating that the identification information has passed the verification; if the identification information whitelist does not include the identification information of the calling end, generate a verification result indicating that the identification information has not passed the verification.

[0053] The above-mentioned device embodiments correspond to the method embodiments. For detailed descriptions, please refer to the description of the method embodiments, which will not be repeated here. The device embodiments are obtained based on the corresponding method embodiments and have the same technical effects as the corresponding method embodiments. For detailed descriptions, please refer to the corresponding method embodiments.

[0054] Please refer to Figure 4, which is a structural diagram of a remote calling device provided in an embodiment of this specification. As shown in Figure 4, the remote calling device 2 can be implemented as all or part of an electronic device through software, hardware, or a combination of both. According to some embodiments, the remote calling device 2 includes an information encapsulation module 21, an information insertion module 22, an encoding module 23, and a sending module 24. Among them, the information encapsulation module 21 is used to encapsulate the call information to obtain an initial call request; the information insertion module 22 is used to insert the identification information of the calling end into the initial call request by code injection to obtain an updated call request; the encoding module 23 is used to encode the updated call request to obtain a call request; and the sending module 24 is used to send the call request to the server.

[0055] Optionally, the information insertion module 22 is specifically configured to insert the identification information of the calling end into the request header of the initial calling request by means of code injection to obtain an updated calling request.

[0056] The above-mentioned device embodiments correspond to the method embodiments. For detailed descriptions, please refer to the description of the method embodiments, which will not be repeated here. The device embodiments are obtained based on the corresponding method embodiments and have the same technical effects as the corresponding method embodiments. For detailed descriptions, please refer to the corresponding method embodiments.

[0057] The embodiments of this specification also provide a computer storage medium, which can store multiple instructions. The instructions are suitable for being loaded by a processor and executing the method of the embodiments shown in Figures 1 to 2 above. The specific execution process can be found in the specific description of the embodiments shown in Figures 1 to 2, and will not be repeated here.

[0058] This specification also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded by the processor and executes the method of the embodiment shown in Figures 1 to 2 above. The specific execution process can be found in the specific description of the embodiment shown in Figures 1 to 2, and will not be repeated here.

[0059] The embodiments of this specification also provide a schematic diagram of the structure of an electronic device, as shown in Figure 5. As shown in Figure 5, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, memory, and non-volatile storage, and may also include other hardware required for services. The processor reads the corresponding computer program from the non-volatile storage into the memory and then runs it to implement the above-mentioned call request verification method.

[0060] Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0061] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0062] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

[0063] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0064] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0065] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0066] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0067] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0068] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0069] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0070] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0071] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0072] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0073] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Thus, this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0074] This specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.

[0075] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0076] The foregoing is merely an example of the present invention and is not intended to limit the present invention. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be included within the scope of the claims of the present invention.

Claims

1. A call request verification method, applied to a server, comprising: In response to receiving a call request sent by a calling end, decoding the call request to obtain call information corresponding to the call request; Extracting identification information of the calling end from the calling request by means of code injection, wherein the identification information is used to represent identity information of the calling end; Verifying the identification information to obtain a verification result, wherein the verification result indicates whether the identification information passes the verification; If the verification result indicates that the identification information passes the verification, a calling process is executed according to the calling information to obtain a calling result.

2. The method according to claim 1, further comprising: If the verification result indicates that the identification information has failed the verification, a prompt message indicating that the verification has failed is returned.

3. The method according to claim 1, wherein extracting the identification information of the calling end from the calling request by code injection comprises: The identification information of the calling end is extracted from the request header of the calling request by means of code injection.

4. The method according to claim 1, wherein verifying the identification information to obtain a verification result comprises: Obtaining a pre-configured identification information blacklist, wherein the identification information blacklist includes a plurality of identification information; Determining whether the identification information blacklist includes the identification information of the calling end; If the identification information blacklist includes the identification information of the calling end, generating a verification result indicating that the identification information has failed verification; If the identification information blacklist does not include the identification information of the calling end, a verification result indicating that the identification information has passed the verification is generated.

5. The method according to claim 1, wherein verifying the identification information to obtain a verification result comprises: Obtaining a pre-configured identification information whitelist, wherein the identification information whitelist includes multiple identification information; Determining whether the identification information whitelist includes the identification information of the calling end; If the identification information whitelist includes the identification information of the calling end, generating a verification result indicating that the identification information has passed the verification; If the identification information whitelist does not include the identification information of the calling end, a verification result indicating that the identification information has failed the verification is generated.

6. A remote calling method, applied to a calling end, comprising: Encapsulate the call information to obtain the initial call request; Inserting the identification information of the calling end into the initial calling request by code injection to obtain an updated calling request; Encoding the update call request to obtain a call request; Send the call request to the server.

7. The method according to claim 6, wherein the step of inserting the identification information of the calling end into the initial calling request by code injection to obtain the updated calling request comprises: The identification information of the calling end is inserted into the request header of the initial calling request by means of code injection to obtain an updated calling request.

8. A call request verification device, comprising: a request receiving module, configured to, in response to receiving a call request sent by a calling end, decode the call request to obtain call information corresponding to the call request; An information extraction module, configured to extract identification information of the calling end from the calling request by means of code injection, wherein the identification information is used to represent the identity information of the calling end; A verification module, configured to verify the identification information and obtain a verification result, wherein the verification result indicates whether the identification information passes the verification; An execution module is configured to execute a calling process according to the calling information to obtain a calling result if the verification result indicates that the identification information has passed the verification.

9. A remote calling device, comprising: An information encapsulation module is used to encapsulate the call information to obtain an initial call request; An information insertion module, configured to insert the identification information of the calling end into the initial calling request by means of code injection, to obtain an updated calling request; An encoding module, configured to encode the update call request to obtain a call request; The sending module is used to send the call request to the server.

10. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 or 6 to 7 are implemented.

11. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the method according to any one of claims 1 to 5 or 6 to 7.

12. A computer program product having at least one instruction stored thereon, characterized in that: When the at least one instruction is executed by the processor, the steps of the method described in any one of claims 1 to 5 or 6 to 7 are implemented.

Images