Data processing method and apparatus

Abstract

Embodiments of the present specification provide a data processing method and device, wherein the data processing method is applied to a client security verification component constructed in a client, and includes: obtaining an initial service call request, wherein the initial service call request includes initial service call information; determining to-be-transmitted information in the initial service call information; in a case where it is determined that the client starts a transmission function, marking the initial service call request based on the to-be-transmitted information to generate a target service call request; and sending the target service call request to a server. By introducing the client security verification component, the to-be-transmitted information in the initial service call information is extracted, and the initial service call request is marked based on the to-be-transmitted information, so that the initial service call request marked by the to-be-transmitted information is sent to the server, and the to-be-transmitted information is used for marking without changing the initial service call request, thereby realizing call tracking of the initial service call request.

Description

TECHNICAL FIELD

[0001] Embodiments of the present specification relate to the technical field of data processing, and in particular to a data processing method. BACKGROUND

[0002] With the continuous development and wide application of microservices, the calling relationship between different types of applications in various project systems is complex, and in many scenarios, we need to determine which service requests belong to the same full-process request link in a large number of service requests, so as to facilitate the positioning of a certain service request.

[0003] A common way to track the link of a service request is to perform point embedding in the log corresponding to the service request in advance, find the target log with the same request identifier through the embedded point, determine the service request corresponding to the target log, and restore the request calling link corresponding to the target log by adding the position identifier and the sequence identifier corresponding to each service request. However, the point embedding in advance needs to change the service request code of the application, and therefore, a link tracking method without changing the service request is needed. SUMMARY

[0004] Therefore, the embodiments of the present specification provide a data processing method applied to a client-side security verification component constructed in a client. One or more embodiments of the present specification also provide a data processing method applied to a server-side security verification component constructed in a server, a data processing device applied to a client-side security verification component constructed in a client, a data processing device applied to a server-side security verification component constructed in a server, a computing device, a computer-readable storage medium, and a computer program to solve the technical defects in the prior art.

[0005] According to a first aspect of the embodiments of the present specification, a data processing method applied to a client-side security verification component constructed in a client is provided, including:

[0006] obtaining an initial service calling request, wherein the initial service calling request includes initial service calling information;

[0007] determining the to-be-transmitted information in the initial service calling information;

[0008] in a case where it is determined that the client-side security verification component is enabled, marking the initial service calling request based on the to-be-transmitted information, and generating a target service calling request;

[0009] sending the target service calling request to a server.

[0010] According to a second aspect of the embodiments of the present specification, a data processing method applied to a server-side security verification component constructed in a server is provided, including:

[0011] receive a target service call request sent by the client, wherein the target service call request comprises to-be-pass-through information;

[0012] send the target service call request to a target project application corresponding to the target service call request;

[0013] acquire the to-be-pass-through information in a case where it is determined that the server starts the pass-through function;

[0014] generate a target to-be-processed service call request based on the to-be-pass-through information in a case where the to-be-processed service call request is acquired;

[0015] send the target to-be-processed service call request to a target to-be-processed project application corresponding to the to-be-processed service call request.

[0016] According to a third aspect of the embodiments of the present specification, a data processing apparatus is provided, which is applied to a client-side security verification component constructed in a client, and comprises:

[0017] a request acquisition module configured to acquire an initial service call request, wherein the initial service call request comprises initial service call information;

[0018] a determination module configured to determine to-be-pass-through information in the initial service call information;

[0019] a marking module configured to mark the initial service call request based on the to-be-pass-through information in a case where it is determined that the client starts a pass-through function, and generate a target service call request;

[0020] a first sending module configured to send the target service call request to the server.

[0021] According to a fourth aspect of the embodiments of the present specification, a data processing apparatus is provided, which is applied to a server-side security verification component constructed in a server, and comprises:

[0022] a receiving module configured to receive a target service call request sent by the client, wherein the target service call request comprises to-be-pass-through information;

[0023] a second sending module configured to send the target service call request to a target project application corresponding to the target service call request;

[0024] an information acquisition module configured to acquire the to-be-pass-through information in a case where it is determined that the server starts the pass-through function;

[0025] a generation module configured to generate a target to-be-processed service call request based on the to-be-pass-through information in a case where the to-be-processed service call request is acquired;

[0026] The third sending module is configured to send the target to-be-processed service call request to a target to-be-processed project application corresponding to the to-be-processed service call request.

[0027] According to a fifth aspect of an embodiment of the present specification, a computing device is provided, comprising:

[0028] a memory and a processor;

[0029] The memory is configured to store computer executable instructions, and the processor is configured to execute the computer executable instructions, and the computer executable instructions, when executed by the processor, implement the steps of the data processing method.

[0030] According to a sixth aspect of an embodiment of the present specification, a computer readable storage medium is provided, which stores computer executable instructions, and the instructions, when executed by a processor, implement the steps of the data processing method.

[0031] According to a seventh aspect of an embodiment of the present specification, a computer program is provided, wherein when the computer program is executed in a computer, the computer program causes the computer to execute the steps of the data processing method.

[0032] One embodiment of the present specification provides a data processing method applied to a client-side security verification component constructed in a client, comprising: obtaining an initial service call request, wherein the initial service call request comprises initial service call information; determining to-be-transmitted information in the initial service call information; in a case where it is determined that the client-side opens a transmission function, marking the initial service call request based on the to-be-transmitted information to generate a target service call request; and sending the target service call request to a server. By introducing the client-side security verification component, the to-be-transmitted information in the initial service call information is extracted, and the initial service call request is marked based on the to-be-transmitted information, so that the initial service call request marked by the to-be-transmitted information is sent to the server, so that the to-be-transmitted information is used for marking without changing the initial service call request, and the calling tracking of the initial service call request is implemented. BRIEF DESCRIPTION OF DRAWINGS

[0033] Figure 1 is an interaction flow diagram under a data processing system architecture provided by one embodiment of the present specification;

[0034] Figure 2 is a flowchart of a data processing method provided by one embodiment of the present specification;

[0035] Figure 3 is a flowchart of another data processing method provided by one embodiment of the present specification;

[0036] Figure 4is a process flow diagram of a data processing method provided by an embodiment of the present specification;

[0037] Figure 5a is a process flow diagram of a data processing method applied to a client security verification component provided by an embodiment of the present specification;

[0038] Figure 5b is a process flow diagram of a data processing method applied to a server security verification component provided by an embodiment of the present specification;

[0039] Figure 6 is a structure diagram of a data processing method provided by an embodiment of the present specification;

[0040] Figure 7 is a structure diagram of a data processing device provided by an embodiment of the present specification;

[0041] Figure 8 is a structure diagram of another data processing device provided by an embodiment of the present specification;

[0042] Figure 9 is a structure block diagram of a computing device provided by an embodiment of the present specification. DETAILED DESCRIPTION

[0043] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present specification. However, the present specification can be practiced without the specific details, other than in the examples, set forth in this description. Those skilled in the art, in light of the description, can implement the present specification without limiting the scope of the present specification.

[0044] The terminology used in one or more embodiments of the present specification is for the purpose of describing particular embodiments only and is not intended to be limiting of one or more embodiments of the present specification. As used in one or more embodiments of the present specification and the accompanying claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in one or more embodiments of the present specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0045] It should be understood that, although the terms first, second, etc. can be employed in describing various information in one or more embodiments of the present specification, the information should not be limited to such terms. These terms are only used to distinguish one piece of information from another piece of information of the same type. For example, without departing from the scope of one or more embodiments of the present specification, first can also be referred to as second, and similarly, second can also be referred to as first. Depending on the context, the word "if" as used herein can be interpreted as "when" or "upon" or "in response to determining".

[0046] In addition, it should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in one or more embodiments of the present specification are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0047] First, the terms involved in one or more embodiments of the present specification are explained.

[0048] Security Aspect: Aspect-oriented Programming (AOP), which is a programming paradigm that dynamically adds functions to programs without modifying the source code through pre-compilation, runtime dynamic proxy or injection.

[0049] Full-link message transparent transmission: link data transparent transmission, which stores data in the context of HTTP request, so that the data can be operated by all applications on the whole link. Full-link refers to the process of data transmission, calculation and storage.

[0050] HTTP request: refers to the request message from the client to the server. HTTP request includes: request line, request header and request data. The request line includes method, uniform resource identifier (URL) and HTTP version. The request header includes the type of browser generating the request, the list of content types recognizable by the client, and the host address. The request data includes key value form data. Key value form is a key that determines the position of data in the table and the value carried by the key in the hash table.

[0051] HTTP: is a communication protocol that can obtain network resources such as HyperText Markup Language (HTML, HyperText Markup Language). It is the basis for data exchange on the global wide area network (Web), and is a client-server protocol.

[0052] Hook technology: a technology widely used in computer attack and defense confrontation, which can monitor various event messages in the system or process, intercept messages sent to the target window for processing, and Hook technology is generally directional.

[0053] Programming paradigm: the method used in computer programming, the design style adopted in designing program structure, refers to the writing mode of the program.

[0054] With the continuous development and wide application of microservices, the calling relationship between different types of applications in various project systems is complex, and in many scenarios we need to determine which service requests belong to the same full-process request link in the massive service requests, so as to locate a service request and further locate the corresponding abnormal vulnerabilities and vulnerability points of the service request.

[0055] Local thread variable (ThreadLocal): refers to the variable that stores the current thread, which is closed and isolated to other threads, ThreadLocal creates a copy of the variable in each thread, so that each thread can access its own internal copy variable, and the variable can be the information to be transmitted.

[0056] The common way to track the link of the service request is to embed points in the log corresponding to the service request in advance, find the target log with the same request identifier through the embedded points, determine the service request corresponding to the target log, and restore the request calling link corresponding to the target log by adding the position identifier and sequence identifier of each service request. However, the pre-embedding method needs to change the service request code of the application, so a link tracking method without changing the application code is needed.

[0057] To solve the above technical problems, the present specification provides a data processing method applied to a client-side security verification component constructed in a client, comprising: obtaining an initial service call request, wherein the initial service call request includes initial service call information; determining to-be-transmitted information in the initial service call information; in a case where it is determined that the client opens a transmission function, marking the initial service call request based on the to-be-transmitted information to generate a target service call request; and sending the target service call request to a server. By introducing the client-side security verification component, the to-be-transmitted information in the initial service call information is extracted, and the initial service call request is marked based on the to-be-transmitted information. When the initial service call request marked by the to-be-transmitted information is sent to the server, the to-be-transmitted information is used for marking without changing the initial service call request, so that the calling tracking of the initial service call request is realized.

[0058] In the present specification, a data processing method applied to a client-side security verification component constructed in a client is provided. One or more embodiments of the present specification simultaneously relate to a data processing method applied to a server-side security verification component constructed in a server, a data processing device applied to a client-side security verification component constructed in a client, a data processing device applied to a server-side security verification component constructed in a server, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

[0059] Referring to Figure 1 , Figure 1 An interaction flow diagram under a data processing system architecture provided by one embodiment of the present specification is shown, as shown in Figure 1 The system includes a client 101 and a server 102, wherein the client 101 includes a client-side security verification component 1011, and the server 102 includes a server-side security verification component 1021.

[0060] The client-side security verification component 1011 is configured to obtain an initial service call request, wherein the initial service call request includes initial service call information; determine to-be-transmitted information in the initial service call information; in a case where it is determined that the client opens a transmission function, mark the initial service call request based on the to-be-transmitted information to generate a target service call request; and send the target service call request to the server 102.

[0061] The service end security verification component 1021 is configured to receive a target service call request sent by the client 101, wherein the target service call request comprises to-be-transmitted information; send the target service call request to a target project application corresponding to the target service call request; in a case where it is determined that the service end starts the transmission function, acquire the to-be-transmitted information; in a case where the to-be-processed service call request corresponding to the target service call request is acquired, mark the to-be-processed service call request based on the to-be-transmitted information, to generate a target to-be-processed service call request; and send the target to-be-processed service call request to a target to-be-processed project application corresponding to the to-be-processed service call request.

[0062] The scheme of the embodiment of the present specification is applied to acquire an initial service call request, wherein the initial service call request comprises initial service call information; determine to-be-transmitted information in the initial service call information; in a case where it is determined that the client starts the transmission function, mark the initial service call request based on the to-be-transmitted information, to generate a target service call request; and send the target service call request to the service end. By introducing a client security verification component, to-be-transmitted information in initial service call information is extracted, and the initial service call request is marked based on the to-be-transmitted information, so that the initial service call request marked by the to-be-transmitted information is sent to the service end, so that the initial service call request is tracked by using the to-be-transmitted information without changing the initial service call request.

[0063] Referring to Figure 2 , Figure 2 A flowchart of a data processing method provided by one embodiment of the present specification is shown, which is applied to a client security verification component constructed in a client, and specifically includes the following steps:

[0064] Step 202: Acquire an initial service call request, wherein the initial service call request comprises initial service call information.

[0065] The embodiment of the present specification is applied to a client security verification component constructed in a client (Client) with a data processing function.

[0066] Specifically, the initial service call request refers to a starting point call request of a full-link flow, for example, a user initiates a login request to the client backend by clicking the starting point application front end, the client generates an initial service call request based on the login request, the initial service call request comprises initial service call information, and the initial service call request can be an HTTP request, and the starting point application can be a browser. The initial service call information refers to information needed to process the initial service call request, which is used to process the initial service call request, for example, the initial service call information comprises an Internet Protocol (IP) of the client, an account and a password for login, etc.

[0067] The initial service call request is usually triggered by an operation of a client to generate the initial service call request when a user has a call demand.

[0068] In an optional embodiment of the present specification, to reduce the code modification cost of the client and the server and further improve the efficiency of processing the service call request, a client security verification component can be constructed in the client before processing the service call request. In actual application, there are various ways to construct the client security verification component, which are selected according to actual conditions, and the embodiments of the present specification do not make any limitation on this. In a possible implementation manner of the present specification, the security verification component can be developed by using the java agent bytecode instrumentation technology. In another possible implementation manner of the present specification, the client can be modified in an embedded manner to construct the security verification component.

[0069] The security verification component can also be called an aspect-oriented security (AOS) toolkit, which can systematically integrate security capabilities into the technical infrastructure and the internal application service, while maintaining the decoupling of security response capabilities and complex project logic to form an independent functional aspect.

[0070] Through the initial service call request, the subsequent client can identify the to-be-transmitted information based on the initial service call request, and process based on the to-be-transmitted information and the initial service call request, which lays a foundation for subsequent processing.

[0071] Optionally, the client security verification component includes a hook unit; and the step 202 includes the following specific steps.

[0072] The initial service call request initiated by the initial project application in the client is obtained through the hook unit.

[0073] Specifically, the hook unit is used to obtain the initial service call request, and the hook unit includes Hook technology. The initial project application can be an application in the client, such as a browser, an application (App), and the like.

[0074] Optionally, the hook unit in the client security verification component can be generated by writing the Hook technology into the client security verification component in a programming paradigm manner.

[0075] The initial service call request initiated by the initial project application in the client is acquired through the hook unit. Specifically, when the initial service call request is executed to the client security verification component, the initial service call request initiated by the initial project application in the client is acquired through the hook unit. For example, the initial service call request needs to perform 5 steps in the client, and when the second step is executed and transferred to the third step, since the client security verification component is between the second step and the third step, the initial service call request will be acquired by the hook unit and acquired into the client security verification component.

[0076] The acquisition through the hook unit is specifically extracting the initial service call request by using the Hook technology in the hook unit, so that the initial service call request executes the code logic in the client security verification component.

[0077] By applying the scheme in the embodiments of the present specification, the hook unit is included in the client security verification component, and the initial service call request initiated by the initial project application in the client is acquired through the hook unit, so that the initial service call request can be acquired to the client security verification component, and the running of the initial service call request in the client will not be affected, that is, by not changing the basis of the original initial service call request running, the initial service call request executes the logic of the client security verification component, and the effect of subsequent link tracking is guaranteed.

[0078] Step 204: determining the to-be-transmitted information in the initial service call information.

[0079] Specifically, the to-be-transmitted information refers to information that needs to be transmitted, which is used to track the initial service call request in the link. For example, the to-be-transmitted information can be a client IP address, a user identifier initiating the initial service call request, etc., which can be determined through the code logic in the client security verification component.

[0080] The to-be-transmitted information in the initial service call information is determined, which is specifically extracting the to-be-transmitted information from the initial service call information based on the client security verification component. The based on the client security verification component can be determined based on the functional unit included in the client security verification component.

[0081] Optionally, the to-be-transmitted information in the initial service call information can be information directly included in the to-be-transmitted information, which can be directly extracted; or the to-be-transmitted information can be semantic information including the to-be-transmitted information in the initial service call information, and the to-be-transmitted information can be obtained by data analysis on the semantic information in the initial service call information.

[0082] The to-be-transmitted information in the initial service call information is determined, so that subsequent processing is performed based on the determined to-be-transmitted information, to track the initial service call request in the link.

[0083] Optionally, the client security verification component comprises a determination unit, wherein the determination unit is configured to determine the to-be-transmitted information from the initial service call information; the step 204 comprises the following specific steps:

[0084] inputting the initial service call information into the determination unit;

[0085] obtaining the to-be-transmitted information determined based on the determination unit.

[0086] Specifically, the determination unit is configured to obtain the to-be-transmitted information, and the determination unit can comprise a keyword recognition technology, a matching technology, etc. The to-be-transmitted information is determined from the initial service call information by using the keyword recognition technology and the matching technology.

[0087] Optionally, the determination unit can comprise a keyword recognition technology. By using the keyword recognition technology, information corresponding to a keyword recognized in the initial service call information is determined as the to-be-transmitted information. For example, the preset information is "user identifier", the character "xx" in "user identifier information: xx" contained in the initial service call information is recognized, it is determined that the character in the preset information is included in the information, and then it is determined that "user identifier information: xx" is the to-be-transmitted information.

[0088] Optionally, the determination unit can comprise a matching technology. By using the matching technology, the initial service call information is matched with the preset information, and information corresponding to a high matching degree is determined as the to-be-transmitted information. For example, the preset information is "user identifier", and the information contained in the initial service call information includes "user identifier information: xx". By matching the preset information "user identifier" with "user identifier information: xx", it is determined that the matching degree of "user identifier" in the preset information and "user identifier" in "user identifier information: xx" is 100%, and then it is determined that "user identifier information: xx" corresponding to "user identifier" is the to-be-transmitted information.

[0089] The initial service call information is input into the determination unit, and the to-be-transmitted information determined based on the determination unit is obtained. Specifically, the initial service call information is input into the determination unit, the to-be-transmitted information is determined, and the to-be-transmitted information is obtained. The specific implementation manner can be that the initial service call information is input into the determination unit, the initial service call information is processed by using the technology contained in the determination unit and the preset information corresponding to the technology, the to-be-transmitted information is determined, and the to-be-transmitted information is obtained.

[0090] According to the scheme of the embodiment of the present specification, the client security verification component includes a determination unit configured to determine the to-be-transmitted information from the initial service call information. The initial service call request is input to the determination unit, and the to-be-transmitted information determined based on the determination unit is obtained. The to-be-transmitted information determined is information meeting the requirements of the client security verification component, and the logic in the client security verification component can be customized by the user, thereby improving the flexibility of the to-be-transmitted information and improving the use rate of the to-be-transmitted information in the future.

[0091] Optionally, after the step 204, the method further includes the following specific steps:

[0092] The to-be-transmitted information is stored in the client to-be-transmitted information storage thread. The client to-be-transmitted information storage thread is configured to store the to-be-transmitted information.

[0093] Specifically, the client to-be-transmitted information storage thread is located in the client and is configured to store the to-be-transmitted information in the client. For example, the client to-be-transmitted information storage thread can be a ThreadLocal in the client.

[0094] Optionally, the storage manner of the to-be-transmitted information in the client to-be-transmitted information storage thread is different based on the structure of the client to-be-transmitted information storage thread. In one possible implementation, the client to-be-transmitted information storage thread includes a plurality of storage areas, and the to-be-transmitted information is stored in one of the storage areas in the client to-be-transmitted information storage thread. In another possible implementation, the client to-be-transmitted information storage thread is a single storage area, and the to-be-transmitted information is stored in the client to-be-transmitted information storage thread, that is, the to-be-transmitted information is directly stored in the thread.

[0095] According to the scheme of the embodiment of the present specification, by storing the to-be-transmitted information in the client to-be-transmitted information storage thread, the client security verification component can store the to-be-transmitted information in the client to-be-transmitted information storage thread after obtaining the to-be-transmitted information, and save the to-be-transmitted information. Therefore, when it is determined to send the to-be-transmitted information to the server, the to-be-transmitted information can be obtained from the client to-be-transmitted information storage thread, thereby improving the speed of obtaining the to-be-transmitted information.

[0096] Step 206: In the case where the client starts the transmission function, the initial service call request is marked based on the to-be-transmitted information, and a target service call request is generated.

[0097] In one or more embodiments of the specification, an initial service call request and initial service call information included in the initial service call request are acquired, to-be-transmitted information in the initial service call request information is determined, and it is determined whether the client has enabled a transparent transmission function. In a case where it is determined that the client has enabled the transparent transmission function, the initial service call request is marked based on the to-be-transmitted information, and a target service call request is generated, so that the client security verification component initiates a request to a server based on the target service call request, and the request flow of two applications in a link is realized.

[0098] Specifically, the transparent transmission function refers to a transparent transmission function for transmitting data, and does not change any form of the transmitted data in the transmission process, that is, the transmission process is transparent, and the function ensures the quality of the transmission, where the form in any form can be data content, data representation form, etc. Enabling the transparent transmission function means that the to-be-transmitted information can be received or sent.

[0099] Optionally, when the client transparent transmission function is used, it can be determined whether the client has enabled the transparent transmission function, and corresponding processing is performed based on the determination result. In a case where the transparent transmission function is enabled, the to-be-transmitted information is sent based on the to-be-transmitted information, and in a case where the transparent transmission function is not enabled, the to-be-transmitted information is stopped.

[0100] In a case where it is determined that the client has enabled the transparent transmission function, the initial service call request is marked based on the to-be-transmitted information, and a target service call request is generated. Specifically, in a case where it is determined that the client has enabled the transparent transmission function, the to-be-transmitted information is added to the initial service call request to generate the target service call request.

[0101] Optionally, the to-be-transmitted information is added to the initial service call request. Specifically, the to-be-transmitted information is added to the initial service call request without changing the request content corresponding to the initial service call request. The initial service call request includes a request header line, a request header, a blank line, and a request content. Specifically, the to-be-transmitted information is added to the request header in the initial service call request to mark the initial service call request with the to-be-transmitted information.

[0102] Optionally, the initial service call request further includes an initial request header.

[0103] The initial service call request is marked based on the to-be-transmitted information, and a target service call request is generated, including:

[0104] The to-be-transmitted information is extracted from the client transparent transmission information storage thread;

[0105] The to-be-transmitted information is added to the initial request header to generate a target request header;

[0106] The target service call request is generated based on the target request header and the initial service call information.

[0107] Specifically, the initial request header refers to a request header in the initial service call request, and is located at a next structure of a request line in the initial service call request. For example, the initial request header can be an x-message header.

[0108] The to-be-transmitted information is extracted from the client-to-be-transmitted information storage thread, and the to-be-transmitted information is added to the initial request header to generate a target request header. Specifically, the to-be-transmitted information determined and stored in the client-to-be-transmitted information storage thread is taken out, the taken-out to-be-transmitted information is placed in the initial request header in the initial service call request, a target request header is generated, and the request content in the initial service call request is not changed. Only the initial service call request is marked by the to-be-transmitted information, so as to be tracked in the subsequent initial service call request.

[0109] Optionally, after the target request header is generated, the target request header can replace the initial request header in the initial service call request to generate a target service call request.

[0110] Based on the target request header and the initial service call information, a target service call request is generated. Specifically, the target request header and the initial service call information are combined with a request line and a blank line in the initial service call request to generate the target service call request, that is, the target request header and the initial service call information are determined as the request header and the call information in the target service call request; the request header and the call information are combined with the request line and the blank line in the initial service call request to generate the target service call request.

[0111] By applying the scheme of the embodiments of the present specification, the initial service call request further includes an initial request header, the to-be-transmitted information is extracted from the client-to-be-transmitted information storage thread, the to-be-transmitted information is added to the initial request header to generate a target request header, and based on the target request header and the initial service call information, a target service call request is generated. Therefore, the to-be-transmitted information is contained in the generated target service call request, that is, the target service call request is the initial service call request marked by the to-be-transmitted information, so that the initial service call request can be tracked by using the to-be-transmitted information in the subsequent process. Moreover, the to-be-transmitted information is added in the initial request header, and the initial service call information in the initial service call request is not changed, and the request content in the initial service call request is not changed specifically, so that the response of the request content corresponding to the initial service call request in the subsequent process is ensured.

[0112] Optionally, before the step 206, the method further includes the following specific steps:

[0113] Obtaining the transmission configuration information of the client, wherein the transmission configuration information is configured with information of the client transmission function;

[0114] Based on the transparent transmission configuration information, it is judged whether the client opens the transparent transmission function.

[0115] Specifically, the transparent transmission configuration information refers to information for limiting the transparent transmission function of the client. For example, the transparent transmission configuration information can include "transparent transmission function: on" and "transparent transmission function: off".

[0116] Optionally, the transparent transmission configuration information of the client can be pre-stored in the client security verification component, and can be read; or the client security verification component can search from the client, and identify the transparent transmission configuration information from multiple configuration information of the client according to the identification keyword.

[0117] Optionally, the transparent transmission configuration information can be pre-configured by the user. Specifically, the transparent transmission function of the system default client is opened, and the user can customize the configuration.

[0118] In one or more embodiments of the present specification, there are many ways to judge whether the client opens the transparent transmission function based on the transparent transmission configuration information. The specific selection is based on the actual situation, and the present specification does not make any limitation.

[0119] In a possible implementation manner of the present specification, the keyword in the transparent transmission configuration information can be identified, and based on the identification result, it is judged whether the client opens the transparent transmission function.

[0120] In another possible implementation manner of the present specification, the information content in the transparent transmission configuration information can be matched with the preset character, and based on the matching result, it is judged whether the client opens the transparent transmission function.

[0121] By applying the scheme of the present specification, the transparent transmission configuration information of the client is obtained, and based on the transparent transmission configuration information, it is judged whether the client opens the transparent transmission function. The transparent transmission function of the client is judged by the transparent transmission configuration information of the client, so that the result obtained is the actual configuration of the client.

[0122] Optionally, based on the transparent transmission configuration information, it is judged whether the client opens the transparent transmission function, including:

[0123] The transparent transmission configuration information is parsed to obtain a transparent transmission configuration keyword;

[0124] Based on the transparent transmission configuration keyword, it is judged whether the client opens the transparent transmission function.

[0125] Specifically, the transparent transmission configuration keyword refers to a keyword for limiting the transparent transmission function of the client. For example, the transparent transmission configuration keyword can be "on", "off", "default", etc.

[0126] The transparent transmission configuration information is parsed to obtain a transparent transmission configuration keyword. Specifically, information content in the transparent transmission configuration information is identified, and the transparent transmission configuration keyword is obtained.

[0127] Based on the transparent transmission configuration keyword, it is determined whether the client has enabled the transparent transmission function. Specifically, semantic information of the transparent transmission configuration keyword is determined, and based on the semantic information, it is determined whether the client has enabled the transparent transmission function. For example, if the transparent transmission configuration keyword is "on", the semantic information is identified as: the transparent transmission function is enabled.

[0128] By applying the scheme of the embodiments of the present specification, the transparent transmission configuration information is parsed to obtain a transparent transmission configuration keyword, and based on the transparent transmission configuration keyword, it is determined whether the client has enabled the transparent transmission function. By identifying the keyword, information extraction is performed on the transparent transmission configuration information, the client is quickly determined whether the transparent transmission function is enabled based on the transparent transmission configuration information, and the efficiency of link tracking is improved.

[0129] Optionally, the data processing method further includes the following specific steps:

[0130] In a case where it is determined that the client has not enabled the transparent transmission function, an exception prompt information is returned to an initial project application in the client.

[0131] Specifically, the exception prompt information is used to prompt the front-end user that the client has not enabled the transparent transmission function.

[0132] Optionally, in a case where it is determined that the client has not enabled the transparent transmission function, an exception prompt information is returned to an initial project application in the client. The initial project application displays the exception prompt information on the front end.

[0133] By applying the scheme of the embodiments of the present specification, in a case where it is determined that the client has not enabled the transparent transmission function, an exception prompt information is returned to an initial project application in the client, so that the initial project application displays the exception prompt information on the front end and processes the exception prompt information based on the exception prompt information.

[0134] Step 208: sending the target service call request to the server.

[0135] In one or more embodiments of the present specification, the initial service call request and the initial service call information included in the initial service call request are obtained, the to-be-transmitted information in the initial service call request information is determined, and it is determined whether the client has enabled the transparent transmission function. In a case where it is determined that the client has enabled the transparent transmission function, the target service call request is generated based on the to-be-transmitted information marked in the initial service call request. After that, the client security verification component sends the target service call request to the server.

[0136] sending the target service call request to the server, specifically, sending the target service call request to other item application of the client, and sending the target service call request from the other item application to the server.

[0137] The target service call request is sent to the server, so that the server performs corresponding processing based on the target service call request.

[0138] Optionally, after the step 208, the method further includes the following specific steps:

[0139] The to-be-transmitted information is deleted from the client-transmitted information storage thread.

[0140] Optionally, the implementation manner of deleting the to-be-transmitted information from the client-transmitted information storage thread is related to the function and storage manner of the client-transmitted information storage thread. For example, if the client-transmitted information storage thread is independent and in one-to-one correspondence with the to-be-transmitted information, the client-transmitted information storage thread is emptied; if the client-transmitted information storage thread includes multiple partitions, and each partition can store to-be-transmitted information, the to-be-transmitted information that needs to be deleted is deleted from the client-transmitted information storage thread.

[0141] According to the scheme of the embodiment of the present specification, the to-be-transmitted information is deleted from the client-transmitted information storage thread, so that subsequent other information can be stored in the storage space emptied after deletion, and the utilization rate of the client-transmitted information storage thread is improved.

[0142] Referring to Figure 3 , Figure 3 A flowchart of another data processing method provided by an embodiment of the present specification is shown, which is applied to a server security verification component constructed in a server, and specifically includes the following steps:

[0143] Step 302: receiving a target service call request sent by a client, wherein the target service call request includes to-be-transmitted information.

[0144] The embodiment of the present specification is applied to a server security verification component constructed in a server with data processing, wherein the server security verification component refers to a security aspect.

[0145] Optionally, the target service call request sent by the client can be received by other item application in the front row of the server, and the server security verification component receives the target service call request when the target service call request is executed to the server security verification component.

[0146] The target service call request sent by the client is usually sent to the server by the user when the client has a call demand and the client opens the transparent function. The server receives the target service call request, that is, the server security verification component can receive the target service call request.

[0147] The target service call request sent by the client is usually sent to the server by the user when the client has a call demand and the client opens the transparent function. The server receives the target service call request, that is, the server security verification component can receive the target service call request.

[0148] Step 304: Send the target service call request to the target project application corresponding to the target service call request.

[0149] Specifically, the target project application refers to the project application corresponding to the initial project application, which is used to process the target service call request and generate response information to return the response information to the client by the server. The corresponding relationship between the initial project application and the target project application is specifically embodied in the corresponding relationship between the request content corresponding to the target service call request and the processing function of the target project application.

[0150] The target service call request is sent to the target project application corresponding to the target service call request, and specifically the request content in the target service call request is sent to the target project application, so that the target project application processes the request content and generates response information.

[0151] Optionally, the target service call request includes the to-be-transmitted information, and after receiving the target service call request, the to-be-transmitted information in the target service call request can be processed, such as acquisition, sending or rejection, based on the opening or closing of the transparent function of the server.

[0152] The target service call request is sent to the target project application corresponding to the target service call request, and specifically the request content in the target service call request is sent to the target project application, so that the target project application processes the request content and generates response information.

[0153] Step 306: In the case where it is determined that the server opens the transparent function, the to-be-transmitted information is acquired.

[0154] Optionally, in the case where it is determined that the server opens the transparent function, the to-be-transmitted information is acquired, that is, in the case where it is determined that the server opens the transparent function, the server can receive the to-be-transmitted information and acquire the to-be-transmitted information, so as to be used subsequently.

[0155] Optionally, after the to-be-transmitted information is acquired, the to-be-transmitted information can be stored in the storage space of the server, so that the server can acquire the to-be-transmitted information from the storage space when initiating a corresponding request based on the target service call request, and mark the corresponding request.

[0156] In the case that the service end starts the transparent transmission function, the information to be transparently transmitted is acquired, so that the service end subsequently performs processing based on the acquired information to be transparently transmitted, and the target service call request is tracked in the link.

[0157] Optionally, after the information to be transparently transmitted is acquired, the following specific steps are further included:

[0158] The information to be transparently transmitted is stored in a service end transparent transmission information storage thread, wherein the service end transparent transmission information storage thread is used to store the information to be transparently transmitted.

[0159] Specifically, the service end transparent transmission information storage thread is located in the service end and is used to store the information to be transparently transmitted in the service end. For example, the service end transparent transmission information storage thread can be a ThreadLocal in the service end.

[0160] Optionally, the storage mode of the information to be transparently transmitted to the service end transparent transmission information storage thread is different based on the structure of the service end transparent transmission information storage thread. In one possible implementation, the service end transparent transmission information storage thread includes multiple storage areas, and the information to be transparently transmitted is stored in one storage area in the service end transparent transmission information storage thread. In another possible implementation, the service end transparent transmission information storage thread is a single storage area, and the information to be transparently transmitted is stored in the service end transparent transmission information storage thread, that is, the information to be transparently transmitted is directly stored in the thread.

[0161] By storing the information to be transparently transmitted in the service end transparent transmission information storage thread, the service end security verification component can store the information to be transparently transmitted in the service end transparent transmission information storage thread after acquiring the information to be transparently transmitted, and save the information to be transparently transmitted, so that the information to be transparently transmitted can be acquired from the service end transparent transmission information storage thread when the information to be transparently transmitted is used for transmission, thereby improving the acquisition speed of the information to be transparently transmitted.

[0162] Step 308: In the case that the information to be processed service call request is acquired, the information to be transparently transmitted is marked based on the information to be processed service call request, and a target information to be processed service call request is generated.

[0163] Specifically, the information to be processed service call request refers to a call request received by the service end to process the target service call request, and specifically refers to a call request used by the service end to send a call request to a next level service end to receive response information returned by the next level service end. The target information to be processed service call request refers to a call request sent to a next project application, which is generated by marking the information to be processed service call request with the information to be transparently transmitted, wherein the next project application refers to a next level service end relative to the service end.

[0164] The obtained to-be-processed service call request can be request information corresponding to the to-be-processed service call request sent to the next service end, and therefore the service end obtains the to-be-processed service call request.

[0165] In the case of obtaining the to-be-processed service call request corresponding to the target service call request, the to-be-processed service call request is marked based on the to-be-transmitted information, and a target to-be-processed service call request is generated. Specifically, in the case of obtaining the to-be-processed service call request, the to-be-transmitted information is added to the to-be-processed service call request to generate the target to-be-processed service call request.

[0166] Optionally, the to-be-transmitted information is added to the to-be-processed service call request. Specifically, the to-be-transmitted information is added to the request header in the to-be-processed service call request without changing the request content corresponding to the to-be-processed service call request, so as to realize that the to-be-transmitted information marks the to-be-processed service call request. The initial service call request includes a request header line, a request header, a blank line, and request content. Specifically, the to-be-transmitted information is added to the request header in the to-be-processed service call request.

[0167] Optionally, the to-be-processed service call request includes to-be-processed request header and to-be-processed service call information.

[0168] The to-be-processed service call request is marked based on the to-be-transmitted information, and a target to-be-processed service call request is generated, including:

[0169] The to-be-transmitted information is extracted from the service end transmission information storage thread.

[0170] The to-be-transmitted information is added to the to-be-processed request header to generate a target to-be-processed request header.

[0171] The target to-be-processed request header and the to-be-processed service call information are used to generate a target to-be-processed service call request.

[0172] Specifically, the to-be-processed request header refers to a request header in the to-be-processed service call request, which is located in the next structure of a request line in the to-be-processed service call request. The to-be-processed service call information refers to information needed for processing the to-be-processed service call request, which is used for corresponding processing of the to-be-processed service call request. For example, the to-be-processed service call information can include an Internet Protocol (IP) of the service end and request content in the to-be-processed service call request.

[0173] The to-be-transmitted information is extracted from the service end transmission information storage thread, and the to-be-transmitted information is added to the to-be-processed request header to generate a target to-be-processed request header. Specifically, the to-be-transmitted information determined and stored in the service end transmission information storage thread is taken out, and the taken-out to-be-transmitted information is placed in the to-be-processed request header in the to-be-processed service call request to generate a target to-be-processed request header. No change is made to the request content in the to-be-processed service call request. Only the to-be-processed service call request is marked by using the to-be-transmitted information, so as to be tracked in the subsequent to-be-processed service call request.

[0174] Optionally, after the target to-be-processed request header is generated, the target to-be-processed request header can replace the to-be-processed request header in the to-be-processed service call request to generate a target to-be-processed service call request.

[0175] Based on the target to-be-processed request header and the to-be-processed service call information, a target to-be-processed service call request is generated. Specifically, the target to-be-processed request header and the to-be-processed service call information are combined with the request line and the blank line in the to-be-processed service call request to generate the target to-be-processed service call request. That is, the target to-be-processed request header and the to-be-processed service call information are determined as the request header and the call information in the target to-be-processed service call request. The request header, the call information, the request line, and the blank line in the to-be-processed service call request are combined to generate the target to-be-processed service call request.

[0176] By applying the scheme of the embodiments of the present specification, the to-be-processed service call request includes a to-be-processed request header and to-be-processed service call information. The to-be-transmitted information is extracted from the service end transmission information storage thread, and the to-be-transmitted information is added to the to-be-processed request header to generate a target to-be-processed request header. Based on the target to-be-processed request header and the to-be-processed service call information, a target to-be-processed service call request is generated. The to-be-transmitted information is contained in the generated target to-be-processed service call request, that is, the target to-be-processed service call request is a to-be-processed service call request marked by the to-be-transmitted information. The to-be-transmitted information can be used to track the to-be-processed service call request in the subsequent process. By adding the to-be-transmitted information in the to-be-processed request header, no change is made to the to-be-processed service call information in the to-be-processed service call request, and no specific change is made to the request content in the to-be-processed service call request. The response of the subsequent to-be-processed service call request corresponding to the request content is ensured.

[0177] Step 310: The target to-be-processed service call request is sent to a target to-be-processed project application corresponding to the to-be-processed service call request.

[0178] The target to-be-processed service call request is sent to the target to-be-processed project application. Specifically, the target to-be-processed service call request is sent from the service end to the target to-be-processed project application.

[0179] The target to-be-processed service call request is sent to the target to-be-processed item application, so that the target to-be-processed item application performs corresponding processing based on the target to-be-processed service call request.

[0180] According to the scheme of the embodiments of the present specification, a target service call request sent by a client is received, wherein the target service call request includes to-be-pass-through information; the target service call request is sent to a target item application corresponding to the target service call request; in a case where it is determined that the server starts a pass-through function, the to-be-pass-through information is acquired; in a case where a to-be-processed service call request is acquired, the to-be-processed service call request is marked based on the to-be-pass-through information, a target to-be-processed service call request is generated; and the target to-be-processed service call request is sent to a target to-be-processed item application corresponding to the to-be-processed service call request. By sending the received target service call request to the corresponding target item application, the target item application processes the target service call request, in a case where it is determined that the server starts the pass-through function, the to-be-pass-through information is acquired, and in a case where a to-be-processed service call request corresponding to the target service call request is acquired, the to-be-pass-through information and the to-be-processed service call request are processed, a target to-be-processed service call request is generated, and the target to-be-processed service call request is sent to the corresponding target to-be-processed item application, so that the target to-be-processed item application processes the target to-be-processed service call request, and the to-be-pass-through information is used to further mark and track the to-be-processed service call request.

[0181] In one or more embodiments of the present specification, the cut points of the client security verification component and the server security verification component in the client and the server can be any one of the following:

[0182] When the encapsulated component is “Tomcat”, the cut points can be “org”, “apache”, “catalina”, “connector”, “CoyoteAdapter#service”, and the like, and the encapsulated component can also be “Apache-HttpClient-V3”, “Apache-HttpClient-V4”, “OK-HttpClient-V2”, “OK-HttpClient-V3”, and “JDK-HttpClient”.

[0183] When the client initiates a call request to the server, the request is specifically initiated by a component, and there is a corresponding cut point corresponding to different components. The cut point is the location of the security verification component. The component and the cut point corresponding to the component are selected according to actual conditions, and the embodiments of the present specification do not make any limitation in this regard.

[0184] The following is described in combination with the drawingsFigure 4 With the application of the data processing method provided in the specification in the login of the browser page as an example, the data processing method is further described. Among them, Figure 4 A flow chart of the processing process of a data processing method provided by an embodiment of the specification is shown, which specifically includes the following steps.

[0185] The following steps 402 to 414 are executed in the client security verification component:

[0186] Step 402: Obtain the initial service call request initiated by the initial project application in the client through the hook unit.

[0187] The user initiates a login request to the client by clicking the login button in the browser, and the client generates an initial service call request based on the login request. The initial service call request executes 5 steps in the client, wherein the client security verification component is located between step 2 and step 3. When the initial service call request is executed between step 2 and step 3, the client security verification component obtains the initial service call request through the hook unit.

[0188] Step 404: Input the initial service call information to the determination unit; obtain the to-be-transmitted information determined based on the determination unit.

[0189] After the client security verification component obtains the initial service call request through the hook unit, the initial service call request is input to the determination unit, and the to-be-transmitted information output by the determination unit is the user identifier.

[0190] Step 406: Store the to-be-transmitted information to the client transmission information storage thread, wherein the client transmission information storage thread is used to store the to-be-transmitted information.

[0191] The determined user identifier is stored in the client ThreadLocal.

[0192] Step 408: Obtain the transmission configuration information of the client, wherein the transmission configuration information is configured with the information of the client transmission function; based on the transmission configuration information, determine whether the client opens the transmission function.

[0193] Obtain the transmission configuration information previously set in the client.

[0194] Step 410: In the case where it is determined that the client opens the transmission function, mark the initial service call request based on the to-be-transmitted information, and generate a target service call request.

[0195] According to the identification of the characters in the transparent transmission configuration information, when the keywords "open" or "default" and the like are identified, it is determined that the client opens the transparent transmission function, and the initial service call request is marked with a user identifier to generate a target service call request.

[0196] Step 412: In the case where it is determined that the client does not open the transparent transmission function, an exception prompt information is returned to the initial project application in the client.

[0197] In the case where it is determined that the client does not open the transparent transmission function, an exception prompt information "Hook Catalina exception" is returned to the browser in the client.

[0198] Step 414: The to-be-transmitted information is deleted from the client transparent transmission information storage thread.

[0199] Referring to Figure 5a , Figure 5a The processing flowchart of the data processing method applied to the client security verification component provided by one embodiment of the present specification is shown in the following figure:

[0200] The flow executed in the client security verification component is as follows: 1, start; 2, the client security verification component: the initial service call request reaches the client security verification component; 3, judge whether the client opens the transparent transmission function, if yes, execute steps 4, 5, 6, 7; if not, execute step 7; 4, store the to-be-transmitted information in the client transparent transmission information storage thread; 5, Hook Catalina return / exception: in the case where the client opens the transparent transmission function, Hook Catalina returns, wherein the return is prompt information; 6, store the to-be-transmitted information in the initial request header; 7, delete the to-be-transmitted information from the client transparent transmission information storage thread; 8, end.

[0201] The following steps 416 to 426 are executed in the server security verification component:

[0202] Step 416: receiving the target service call request sent by the client, wherein the target service call request includes to-be-transmitted information.

[0203] Step 418: sending the target service call request to the target project application corresponding to the target service call request.

[0204] The target service call request is sent to the target project application A corresponding to the target service call request.

[0205] Step 420: obtaining the server transparent transmission configuration information of the server, wherein the server transparent transmission configuration information is configured with the information of the server transparent transmission function; based on the server transparent transmission configuration information, judging whether the server opens the transparent transmission function.

[0206] Obtaining pre-set transparent transmission configuration information in the service end, identifying characters in the transparent transmission configuration information, and judging whether the service end starts the transparent transmission function according to the identification result.

[0207] Step 422: obtaining the information to be transparently transmitted in the case of determining that the service end starts the transparent transmission function.

[0208] In the case of identifying the keyword “on” or “default” or other characters, it is determined that the service end starts the transparent transmission function, and the information to be transparently transmitted “user identifier” is obtained.

[0209] Step 424: storing the information to be transparently transmitted to the service end transparent transmission information storage thread, wherein the service end transparent transmission information storage thread is used to store the information to be transparently transmitted.

[0210] Storing “user identifier” in the service end ThreadLocal.

[0211] Step 426: in the case of obtaining the service call request to be processed, marking the service call request to be processed based on the information to be transparently transmitted, and generating the target service call request to be processed.

[0212] Specifically, extracting “user identifier” from the service end ThreadLocal, adding “user identifier” to the request header to be processed, generating the target request header to be processed, and generating the target service call request to be processed based on the target request header to be processed and the service call information to be processed.

[0213] Referring to Figure 5b , Figure 5b The processing flow chart of the data processing method applied to the service end security verification component provided by one embodiment of the present specification is shown in the following figure:

[0214] The flow executed in the service end security verification component is as follows: 1, start; 2, receive the target service call request; 3, judge whether the service end starts the transparent transmission, if yes, execute step 4; if no, execute step 5; 4, judge whether the target request header exists the information to be transparently transmitted, if yes, execute step 6; if no, execute step 5; 5, end; 6, extract the information to be transparently transmitted from the service end transparent transmission information storage thread; 7, Hook Catalina return / exception, when the information to be transparently transmitted is extracted, Hook Catalina returns, and executes step 8; 8, delete the information to be transparently transmitted from the service end transparent transmission information storage thread, and execute step 5.

[0215] Wherein, Catalina is the service end container.

[0216] Referring to Figure 6 , Figure 6 The structure diagram of the data processing method provided by one embodiment of the present specification is shown in the following figure:

[0217] The structure comprises: a client and a server, wherein the client comprises: a client security verification component; the server comprises: a server security verification component, an abstract collection component (interface), and an information management component;

[0218] 1. Calling, the server receives an HTTP request, calls the abstract collection component (interface) to process the HTTP request, and generates response information;

[0219] 2. Returning, the server returns the response information to the client;

[0220] 3. Storing, the server stores the to-be-transmitted information to a server transparent transmission information storage thread: in the case that the server starts a transparent transmission function, the to-be-transmitted information is obtained from a target request header, and the to-be-transmitted information is stored to the server transparent transmission information storage thread.

[0221] 4. Deleting, the server deletes the to-be-transmitted information from the server transparent transmission information storage thread: in the case that the server does not send an HTTP request to a next server or has sent the HTTP request completely, the to-be-transmitted information is deleted from the server transparent transmission information storage thread.

[0222] Corresponding to the method embodiments, the present specification also provides data processing device embodiments, Figure 7 A structural schematic diagram of a data processing device provided by one embodiment of the present specification is shown, which is applied to a client security verification component constructed in a client. As shown in the figure, Figure 7 The device comprises:

[0223] The request obtaining module 702 is configured to obtain an initial service call request, wherein the initial service call request comprises initial service call information;

[0224] The determination module 704 is configured to determine to-be-transmitted information in the initial service call information;

[0225] The marking module 706 is configured to, in the case that the client starts a transparent transmission function, mark the initial service call request based on the to-be-transmitted information, and generate a target service call request;

[0226] The first sending module 708 is configured to send the target service call request to the server.

[0227] Optionally, the client security verification component comprises a hook unit; and the request obtaining module 702 is further configured to obtain, through the hook unit, an initial service call request initiated by an initial project application in the client.

[0228] Optionally, the client security verification component includes a determination unit, wherein the determination unit is configured to determine the to-be-transmitted information from the initial service call information; the determination module 704 is further configured to input the initial service call information to the determination unit; and the to-be-transmitted information determined by the determination unit is acquired.

[0229] Optionally, the apparatus further includes a first storage module configured to store the to-be-transmitted information to a client-transmitted information storage thread, wherein the client-transmitted information storage thread is configured to store the to-be-transmitted information.

[0230] Optionally, the initial service call request further includes an initial request header; the marking module 706 is further configured to extract the to-be-transmitted information from the client-transmitted information storage thread; add the to-be-transmitted information to the initial request header to generate a target request header; and generate a target service call request based on the target request header and the initial service call information.

[0231] Optionally, the apparatus further includes a deletion module configured to delete the to-be-transmitted information from the client-transmitted information storage thread.

[0232] Optionally, the apparatus further includes an information acquisition module configured to acquire transmitted configuration information of the client, wherein the transmitted configuration information is configured with information of a client-transmitted function; and a judgment module configured to judge whether the client starts the transmitted function based on the transmitted configuration information.

[0233] Optionally, the judgment module is further configured to parse the transmitted configuration information to obtain a transmitted configuration keyword; and judge whether the client starts the transmitted function based on the transmitted configuration keyword.

[0234] Optionally, the apparatus further includes a return module configured to return an abnormal reminder information to the initial project application in the client in a case where it is determined that the client does not start the transmitted function.

[0235] The application of the scheme of the present specification includes the following steps: acquiring an initial service call request, wherein the initial service call request includes initial service call information; determining to-be-transmitted information in the initial service call information; in a case where it is determined that the client starts a transmitted function, marking the initial service call request based on the to-be-transmitted information to generate a target service call request; and sending the target service call request to a server. By introducing a client security verification component, to-be-transmitted information in the initial service call information is extracted, and the initial service call request is marked based on the to-be-transmitted information, so that the initial service call request marked by the to-be-transmitted information is sent to the server, which realizes the call tracking of the initial service call request without changing the initial service call request.

[0236] Each of the embodiments in the specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other. Each embodiment focuses on the difference from other embodiments. In particular, for the data processing apparatus, since it is basically similar to the data processing method embodiment shown above Figure 3 , the description is relatively simple, and the relevant parts can be referred to the part of the data processing method embodiment shown above Figure 3 .

[0237] Corresponding to the above method embodiment, the specification also provides a data processing apparatus embodiment, Figure 8 which shows the structure schematic diagram of another data processing apparatus provided by an embodiment of the specification, applied to the service end security verification component constructed in the service end. As Figure 8 shown, the apparatus includes:

[0238] The receiving module 802 is configured to receive the target service call request sent by the client, wherein the target service call request includes the to-be-transmitted information;

[0239] The second sending module 804 is configured to send the target service call request to the target project application corresponding to the target service call request;

[0240] The information acquisition module 806 is configured to acquire the to-be-transmitted information in the case of determining that the service end opens the transmission function;

[0241] The generation module 808 is configured to mark the to-be-processed service call request based on the to-be-transmitted information in the case of acquiring the to-be-processed service call request, and generate a target to-be-processed service call request;

[0242] The third sending module 810 is configured to send the target to-be-processed service call request to the target to-be-processed project application corresponding to the to-be-processed service call request.

[0243] Optionally, the apparatus further includes a second storage module configured to store the to-be-transmitted information to the service end transmission information storage thread, wherein the service end transmission information storage thread is used to store the to-be-transmitted information.

[0244] Optionally, the to-be-processed service call request includes a to-be-processed request header and to-be-processed service call information; the generation module 808 is further configured to extract the to-be-transmitted information from the service end transmission information storage thread; add the to-be-transmitted information to the to-be-processed request header to generate a target to-be-processed request header; and generate a target to-be-processed service call request based on the target to-be-processed request header and the to-be-processed service call information.

[0245] The application discloses a method for processing a service call request. The method comprises the following steps: receiving a target service call request sent by a client, wherein the target service call request comprises to-be-transmitted information; sending the target service call request to a target project application corresponding to the target service call request; obtaining the to-be-transmitted information in the case that a server starts a transmission function; marking a to-be-processed service call request based on the to-be-transmitted information, generating a target to-be-processed service call request in the case that the to-be-processed service call request is obtained; and sending the target to-be-processed service call request to a target to-be-processed project application corresponding to the to-be-processed service call request. The target service call request is sent to the corresponding target project application, and the target service call request is processed by the target project application. In the case that the server starts the transmission function, the to-be-transmitted information is obtained, and the target to-be-processed service call request is generated based on the to-be-transmitted information and the to-be-processed service call request in the case that the target service call request corresponding to the to-be-processed service call request is obtained. The target to-be-processed service call request is sent to the corresponding target to-be-processed project application, so that the target to-be-processed project application processes the target to-be-processed service call request, and the to-be-transmitted information is used to further mark and track the to-be-processed service call request.

[0246] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts of each of the embodiments can be referred to each other. Each of the embodiments mainly describes the difference from other embodiments. In particular, for the data processing device, since it is basically similar to the above-described data processing method embodiment, the description is relatively simple, and the related parts can be referred to the above-described data processing method embodiment. Figure 4 Figure 4

[0247] Figure 9 A structural block diagram of a computing device provided by one embodiment of the specification is shown. The components of the computing device 900 include but are not limited to a memory 910 and a processor 920. The processor 920 is connected with the memory 910 through a bus 930, and a database 950 is used to save data.

[0248] ​​The computing device 900 also includes an access device 940 that enables the computing device 900 to communicate via one or more networks 960. Examples of such networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or combinations of such networks, such as the Internet. The access device 940 can include one or more of any type of network interface (for example, a network interface card (NIC)) such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, Near Field Communication (NFC).

[0249] In one embodiment of the present specification, the above-mentioned components of the computing device 900 and other components not shown in the Figure 9 may be connected to each other, such as through a bus. It should be understood that Figure 9 The computing device structure diagram shown is only for the purpose of example, and is not a limitation on the scope of the present specification. Those skilled in the art can add or replace other components as needed.

[0250] The computing device 900 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (for example, a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, and the like), a mobile phone (for example, a smartphone), a wearable computing device (for example, a smart watch, smart glasses, and the like), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 900 can also be a mobile or stationary server.

[0251] The processor 920 is configured to execute computer-executable instructions, which, when executed by the processor, implement the steps of the above-mentioned data processing method.

[0252] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts among the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, the computing device embodiment is described simply because it is basically similar to the data processing method embodiment, and the relevant part can be referred to the part of the data processing method embodiment.

[0253] An embodiment of the specification further provides a computer readable storage medium storing computer executable instructions, which, when executed by a processor, implement the steps of the above data processing method.

[0254] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts among the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, the computer readable storage medium embodiment is described simply because it is basically similar to the data processing method embodiment, and the relevant part can be referred to the part of the data processing method embodiment.

[0255] An embodiment of the specification further provides a computer program, which, when executed in a computer, causes the computer to execute the steps of the above data processing method.

[0256] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts among the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, the computer program embodiment is described simply because it is basically similar to the data processing method embodiment, and the relevant part can be referred to the part of the data processing method embodiment.

[0257] The above describes specific embodiments of the specification. Other embodiments are within the scope of the appended claims. In some cases, the acts or steps recited in the claims can be performed in a different order than the order in which they are recited and still accomplish desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0258] The computer readable medium can include any entity or apparatus capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable medium can include appropriate additions or subtractions according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

[0259] It should be noted that the above describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different than the order in the embodiments and still achieve the desired result. In addition, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous. Secondly, those skilled in the art should know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments of the specification.

[0260] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0261] The preferred embodiments of the present specification disclosed above are only used to help explain the present specification. The alternative embodiments do not describe all the details and do not limit the invention to the specific embodiments described. Obviously, according to the content of the embodiments of the present specification, many modifications and changes can be made. The present specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of the present specification, so that those skilled in the art can well understand and utilize the present specification. The present specification is limited only by the claims and their full scope and equivalents.

Claims

1. A data processing method applied to a client security verification component constructed in a client, wherein, The client security verification component includes a hook unit, and the client security verification component is a security aspect toolkit and is an independent functional aspect, and includes: An initial service call request is acquired, wherein the initial service call request includes initial service call information, and the acquiring the initial service call request includes: acquiring, by the hook unit, an initial service call request initiated by an initial project application in the client; Determination of to-be-transmitted information in the initial service call information is performed; In a case where it is determined that the client opens a transmission function, the initial service call request is marked based on the to-be-transmitted information, and a target service call request is generated; The target service call request is sent to a server.

2. The method of claim 1, the client security verification component comprising a determination unit, wherein, The determination unit is configured to determine to-be-transmitted information from initial service call information; The determination of the to-be-transmitted information in the initial service call information includes: The initial service call information is input to the determination unit; The to-be-transmitted information determined based on the determination unit is acquired.

3. The method of claim 1, after determining the to-be-transmitted information in the initial service call information, further comprising: storing the to-be-transmitted information to a client transmission information storage thread, wherein the client transmission information storage thread is configured to store to-be-transmitted information.

4. The method of claim 3, wherein the initial service call request further includes an initial request header; marking the initial service call request based on the to-be-transmitted information to generate a target service call request includes: extracting the to-be-transmitted information from the client transmission information storage thread; adding the to-be-transmitted information to the initial request header to generate a target request header; generating a target service call request based on the target request header and the initial service call information.

5. The method of claim 4, after sending the target service call request to the server, further comprising: deleting the to-be-transmitted information from the client transmission information storage thread.

6. The method of claim 1, before determining whether the client opens a transmission function, further comprising: acquiring transmission configuration information of the client, wherein the transmission configuration information is configured with information of the client transmission function; determining whether the client opens a transmission function based on the transmission configuration information.

7. The method of claim 6, determining whether the client opens a transmission function based on the transmission configuration information includes: parsing the transmission configuration information to obtain a transmission configuration keyword; determining whether the client opens a transmission function based on the transmission configuration keyword.

8. The method of claim 1, further comprising: in a case where it is determined that the client does not open a transmission function, returning abnormal prompt information to an initial project application in the client.

9. A data processing method applied to a server-side security verification component constructed in a server, wherein, The server security verification component is a security aspect toolkit and is an independent functional aspect, and includes: receive a target service call request sent by a client, wherein the target service call request includes to-be-transmitted information determined from initial service call information included in an initial service request initiated by an initial project application in the client and obtained by a hook unit in a client security verification component; send the target service call request to a target project application corresponding to the target service call request; in a case where it is determined that the server starts a transmission function, obtain the to-be-transmitted information; in a case where a to-be-processed service call request is obtained, mark the to-be-processed service call request based on the to-be-transmitted information, and generate a target to-be-processed service call request; send the target to-be-processed service call request to a target to-be-processed project application corresponding to the to-be-processed service call request.

10. The method of claim 9, after obtaining the to-be-transmitted information, further comprising: store the to-be-transmitted information to a server transmission information storage thread, wherein the server transmission information storage thread is configured to store to-be-transmitted information.

11. The method of claim 10, wherein the to-be-processed service call request includes a to-be-processed request header and to-be-processed service call information; marking the to-be-processed service call request based on the to-be-transmitted information to generate a target to-be-processed service call request, comprises: extracting the to-be-transmitted information from the server transmission information storage thread; adding the to-be-transmitted information to the to-be-processed request header to generate a target to-be-processed request header; generating a target to-be-processed service call request based on the target to-be-processed request header and the to-be-processed service call information.

12. A data processing apparatus for use in a client-side constructed client-side security verification component, wherein, The client security verification component includes a hook unit, and the client security verification component is a security aspect toolkit, which is an independent functional aspect, and includes: a request obtaining module configured to obtain an initial service call request, wherein the initial service call request includes initial service call information, and the request obtaining module is further configured to obtain the initial service call request initiated by an initial project application in the client through the hook unit; a determination module configured to determine to-be-transmitted information in the initial service call information; a marking module configured to, in a case where it is determined that the client starts a transmission function, mark the initial service call request based on the to-be-transmitted information to generate a target service call request; a first sending module configured to send the target service call request to a server.

13. The apparatus of claim 12, the client security verification component comprising a determination unit, wherein, The determination unit is configured to determine to-be-transmitted information from initial service call information; and the determination module is further configured to: input the initial service call information to the determination unit; obtain to-be-transmitted information determined based on the determination unit.

14. The apparatus of claim 12, further comprising: a first storage module configured to store the to-be-transmitted information to a client transmission information storage thread, wherein the client transmission information storage thread is configured to store to-be-transmitted information.

15. The apparatus of claim 14, wherein the initial service call request further comprises an initial request header; and the marking module is further configured to: extract the to-be-pass-through information from the client to-be-pass-through information storage thread; add the to-be-pass-through information to the initial request header to generate a target request header; and generate a target service call request based on the target request header and the initial service call information.

16. The apparatus of claim 15, further comprising: a deletion module configured to delete the to-be-pass-through information from the client to-be-pass-through information storage thread.

17. The apparatus of claim 12, further comprising: an information acquisition module configured to acquire to-be-pass-through configuration information of the client, wherein the to-be-pass-through configuration information is configured with information of the client pass-through function; and a judgment module configured to judge whether the client has enabled the pass-through function based on the to-be-pass-through configuration information.

18. The apparatus of claim 17, wherein the judgment module is further configured to: parse the to-be-pass-through configuration information to obtain a pass-through configuration keyword; and judge whether the client has enabled the pass-through function based on the pass-through configuration keyword. The server-side security verification component is a security aspect toolkit, which is an independent functional aspect, and comprises: a receiving module configured to receive a target service call request sent by a client, wherein the target service call request comprises to-be-pass-through information, the to-be-pass-through information is determined from initial service call information, the initial service call information is contained in an initial service request, and the initial service request is initiated by an initial project application in the client and acquired through a hook unit in the client-side security verification component; a second sending module configured to send the target service call request to a target project application corresponding to the target service call request; an information acquisition module configured to acquire the to-be-pass-through information in a case where it is determined that the server has enabled the pass-through function; a generation module configured to, in a case where a to-be-processed service call request is acquired, mark the to-be-processed service call request based on the to-be-pass-through information to generate a target to-be-processed service call request; and a third sending module configured to send the target to-be-processed service call request to a target to-be-processed project application corresponding to the to-be-processed service call request.

20. The apparatus of claim 19, further comprising: a second storage module configured to store the to-be-pass-through information to a server-side to-be-pass-through information storage thread, wherein the server-side to-be-pass-through information storage thread is used to store to-be-pass-through information.

21. The apparatus of claim 20, wherein the to-be-processed service call request comprises a to-be-processed request header and to-be-processed service call information; and the generation module is further configured to: extract the to-be-pass-through information from the server-side to-be-pass-through information storage thread; add the to-be-pass-through information to the to-be-processed request header to generate a target to-be-processed request header; and generate a target to-be-processed service call request based on the target to-be-processed request header and the to-be-processed service call information. ​ ​ ​ ​ 19. A data processing apparatus applied to a server security verification component constructed in a server, wherein, ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 22. A computing device comprising: a memory and a processor; the memory for storing computer-executable instructions, the processor for executing the computer-executable instructions, the computer-executable instructions, when executed by the processor, implementing the steps of the method of any one of claims 1 to 11.

23. A computer-readable storage medium storing computer-executable instructions, the computer-executable instructions, when executed by a processor, implementing the steps of the method of any one of claims 1 to 11.

Images