CN115103026A - Service processing method, device, equipment and storage medium - Google Patents
Service processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115103026A CN115103026A CN202210582474.6A CN202210582474A CN115103026A CN 115103026 A CN115103026 A CN 115103026A CN 202210582474 A CN202210582474 A CN 202210582474A CN 115103026 A CN115103026 A CN 115103026A
- Authority
- CN
- China
- Prior art keywords
- request
- service
- rule
- parameters
- determining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/313—Logic programming, e.g. PROLOG programming language
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to a data processing technology, and discloses a service processing method, a device, equipment and a storage medium, wherein the method comprises the following steps: determining a request type of an intercepted service request; determining a corresponding request parameter acquisition rule according to the request type, analyzing and screening all request parameters in the service request, and splicing and sequencing the analyzed and screened request parameters to obtain multi-dimensional request parameters; releasing the intercepted service request; when detecting that the service request triggers service logic processing, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameter to a rule engine for service rule logic calculation; and sending the calculation result to a service server to carry out corresponding service logic. According to the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a method, an apparatus, a device, and a storage medium for processing a service.
Background
The rule engine mainly performs logic operation according to different input parameters of a service scene and outputs an operation result aiming at the input parameters. For example, the identity card number is input, the rule engine judges whether the client is male, if so, the jump link A is output, and if not, the jump link B is output.
The rule engine originally abstracts the service decision rules and conditions into a common module so as to reuse all service scenes and avoid repeated development and improve efficiency, but along with the increase of service scene access, the service judgment latitude supported by the rule engine can be enriched, such as the rule judgment of client latitude, the rule judgment of geographic position, the rule judgment of equipment latitude, the rule judgment of operating system latitude and the like.
At present, the judgment of various latitudes in the industry is determined based on business scene input parameters, namely, if the judgment of the latitudes of customers is needed, identification numbers or customer or other identification marks must be input into the business scene, if the judgment is based on address positions, relevant latitude and longitude information must be input into the business scene, but a problem is brought about, namely, with the support of more business rule latitudes by a rule engine, the business scene also needs to continuously increase the input parameters, the new business rule latitude characteristics of the rule engine can be used, and therefore the change of each business scene is brought about, the flexibility of the rule engine is reduced, and the modification workload of the business scene is increased.
Disclosure of Invention
The invention mainly aims to solve the technical problem that the existing business processing process needs to input request parameters according to the specified dimension of a rule engine.
A first aspect of the present invention provides a service processing method, including: intercepting a service request received by a service server and determining the request type of the service request; determining a corresponding request parameter acquisition rule according to the request type of the service request; analyzing and screening all request parameters in the service request according to the request parameter acquisition rule, and splicing and sequencing the analyzed and screened request parameters according to a preset splicing sequence to obtain multi-dimensional request parameters; storing the multidimensional request parameters in a local cache of a current thread of the service server, and releasing the intercepted service request; detecting whether the service request triggers service logic processing in real time; if yes, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameters in the local cache to a rule engine for service rule logic calculation; and acquiring a calculation result obtained by the rule engine for service logic calculation, and sending the calculation result to a service server for corresponding service logic.
Optionally, in a first implementation manner of the first aspect of the present invention, the determining, according to the request type of the service request, a corresponding request parameter acquisition rule includes: acquiring a corresponding first acquisition rule from a preset memory space according to the request type of the service request; judging whether the first acquisition rule is valid or not according to the storage time of the first acquisition rule in the memory space; if so, taking the first acquisition rule as a request parameter acquisition rule corresponding to the service request; if not, sending a rule acquisition request to a rule engine, and taking a second acquisition rule issued by the rule engine as a request parameter acquisition rule corresponding to the service request.
Optionally, in a second implementation manner of the first aspect of the present invention, the request type includes an http request, the service request includes a request line and a request header, and when the request type is an http request, the analyzing and screening all request parameters in the service request according to the request parameter acquisition rule, and performing splicing and ordering on the analyzed and screened request parameters according to a preset splicing order to obtain the multidimensional request parameters includes: extracting request parameters in a request header of the service request according to the request parameter acquisition rule; determining a request method in the request line, wherein the request method comprises a get request and a post request; if the request method is a get request, extracting request parameters of the URL in the request line; if the request method is a post request, determining that the service request carries a form, and extracting request parameters from the form; determining whether the service request carries cookie or not, and if so, extracting request parameters in the cookie; and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
Optionally, in a third implementation manner of the first aspect of the present invention, the request type further includes an RCP request, the service request includes a request header, and when the request type is an RPC request, the analyzing and screening are performed on all request parameters in the service request according to the request parameter acquisition rule, and the request parameters analyzed and screened are spliced and sorted according to a preset splicing order, so as to obtain multidimensional request parameters, where the obtaining includes: extracting request parameters in a request header of the service request according to the request parameter acquisition rule; judging whether the service request carries a JSON object or not; if yes, extracting a request parameter in the JSON object; and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
Optionally, in a fourth implementation manner of the first aspect of the present invention, the determining a service scenario identifier that triggers the service logic processing, and sending the service scenario identifier and the multidimensional request parameter in the local cache to a rule engine for performing service rule logic calculation includes: determining a service scene identifier triggering the service logic processing, and calling a preset rule engine judgment interface; sending the service request and the service scene identifier to the rule engine through the rule engine judgment interface; and when receiving the authentication valid information sent by the rule engine after the service request and the service scene identification are authenticated, sending the multidimensional request parameters in the local cache to the rule engine for service logic calculation.
Optionally, in a fifth implementation manner of the first aspect of the present invention, when receiving authentication valid information sent by the rule engine after authenticating the service request and the service scene identifier, sending the multidimensional request parameter in the local cache to the rule engine for service logic calculation includes: when receiving authentication valid information sent by the rule engine after authenticating the service request and the service scene identifier, judging a local cache corresponding to the service request; sending a parameter query request to the local cache, and receiving a multi-dimensional request parameter returned by the local cache; and sending the multidimensional request parameters in the local cache to the rule engine for business logic calculation.
Optionally, in a sixth implementation manner of the first aspect of the present invention, before intercepting a service request received by a service server and determining a request type of the service request, the method further includes: acquiring a rule updating request and determining an updating type of the rule updating request, wherein the updating type comprises acquisition rule updating and service rule updating; if the update type is acquisition rule update, acquiring a corresponding first rule code according to the rule update request; updating the request parameter acquisition rule in the rule engine according to the first rule code; if the update type is service rule update, acquiring a corresponding second rule code according to the rule update request; and updating the business rules in the rule engine according to the first rule code.
A second aspect of the present invention provides a service processing apparatus, including: the intercepting module is used for intercepting a service request received by a service server and determining the request type of the service request; the rule determining module is used for determining a corresponding request parameter acquisition rule according to the request type of the service request; the splicing module is used for analyzing and screening all request parameters in the service request according to the request parameter acquisition rule and splicing and sequencing the analyzed and screened request parameters according to a preset splicing sequence to obtain multi-dimensional request parameters; the release module is used for storing the multidimensional request parameters in a local cache of a current thread of the service server and releasing the intercepted service request; the detection module is used for detecting whether the service request triggers service logic processing in real time; the calculation module is used for determining a service scene identifier for triggering the service logic processing when the service request triggers the service logic processing, and sending the service scene identifier and the multidimensional request parameters in the local cache to a rule engine for service rule logic calculation; and the forwarding module is used for acquiring a calculation result obtained by the rule engine through service logic calculation and sending the calculation result to a service server for carrying out corresponding service logic.
Optionally, in a first implementation manner of the second aspect of the present invention, the rule determining module is specifically configured to: acquiring a corresponding first acquisition rule from a preset memory space according to the request type of the service request; judging whether the first acquisition rule is valid or not according to the storage time of the first acquisition rule in the memory space; if so, taking the first acquisition rule as a request parameter acquisition rule corresponding to the service request; if not, sending a rule acquisition request to a rule engine, and taking a second acquisition rule issued by the rule engine as a request parameter acquisition rule corresponding to the service request.
Optionally, in a second implementation manner of the second aspect of the present invention, the request type includes an http request, the service request includes a request line and a request header, and when the request type is an http request, the splicing module is specifically configured to: extracting request parameters in a request head of the service request according to the request parameter acquisition rule; determining a request method in the request line, wherein the request method comprises a get request and a post request; if the request method is a get request, extracting request parameters of the URL in the request line; if the request method is a post request, determining that the service request carries a form, and extracting request parameters from the form; determining whether the service request carries cookie or not, and if so, extracting request parameters in the cookie; and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
Optionally, in a third implementation manner of the second aspect of the present invention, the request type further includes an RCP request, the service request includes a request header, and when the request type is an RPC request, the splicing module is specifically configured to: extracting request parameters in a request header of the service request according to the request parameter acquisition rule; judging whether the service request carries a JSON object or not; if yes, extracting a request parameter in the JSON object; and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
Optionally, in a fourth implementation manner of the second aspect of the present invention, the calculation module specifically includes: the interface calling unit is used for determining a service scene identifier triggering the service logic processing and calling a preset rule engine to judge an interface; a sending unit, configured to send the service request and the service scene identifier to the rule engine through the rule engine determination interface; and the authentication unit is used for sending the multidimensional request parameters in the local cache to the rule engine for service logic calculation when receiving the authentication valid information sent by the rule engine after the service request and the service scene identification are authenticated.
Optionally, in a fifth implementation manner of the second aspect of the present invention, the authentication unit is specifically configured to: when receiving authentication valid information sent by the rule engine after authenticating the service request and the service scene identifier, judging a local cache corresponding to the service request; sending a parameter query request to the local cache, and receiving a multi-dimensional request parameter returned by the local cache; and sending the multidimensional request parameters in the local cache to the rule engine for business logic calculation.
Optionally, in a sixth implementation manner of the second aspect of the present invention, the service processing apparatus further includes an update module, where the update module is specifically configured to: acquiring a rule updating request and determining an updating type of the rule updating request, wherein the updating type comprises acquisition rule updating and service rule updating; if the update type is acquisition rule update, acquiring a corresponding first rule code according to the rule update request; updating a request parameter acquisition rule in the rule engine according to the first rule code; if the update type is service rule update, acquiring a corresponding second rule code according to the rule update request; and updating the business rules in the rule engine according to the first rule code.
A third aspect of the present invention provides a service processing device, including: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line; the at least one processor invokes the instructions in the memory to cause the business processing apparatus to perform the steps of the business processing method described above.
A fourth aspect of the present invention provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the steps of the above-described service processing method.
In the technical scheme of the invention, the corresponding request parameter acquisition rule is determined according to the request type, all request parameters in the service request are analyzed and screened, and the analyzed and screened request parameters are spliced and sequenced to obtain multi-dimensional request parameters; releasing the intercepted service request; when detecting that the service request triggers service logic processing, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameter to a rule engine for service rule logic calculation; and sending the calculation result to a service server to carry out corresponding service logic. According to the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
Drawings
Fig. 1 is a schematic diagram of a first embodiment of a service processing method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a second embodiment of a service processing method according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a third embodiment of a service processing method in the embodiment of the present invention;
FIG. 4 is a schematic diagram of an embodiment of a service processing apparatus according to an embodiment of the present invention;
fig. 5 is a schematic diagram of another embodiment of a service processing apparatus according to an embodiment of the present invention;
fig. 6 is a schematic diagram of an embodiment of a service processing device in the embodiment of the present invention.
Detailed Description
In the technical scheme of the invention, the corresponding request parameter acquisition rule is determined according to the request type, all request parameters in the service request are analyzed and screened, and the analyzed and screened request parameters are spliced and sequenced to obtain multi-dimensional request parameters; releasing the intercepted service request; when detecting that the service request triggers service logic processing, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameter to a rule engine for service rule logic calculation; and sending the calculation result to a service server to carry out corresponding service logic. According to the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be implemented in other sequences than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For convenience of understanding, a specific flow of the embodiment of the present invention is described below, and referring to fig. 1, a first embodiment of a service processing method in the embodiment of the present invention includes:
101. intercepting a service request received by a service server and determining the request type of the service request;
it is to be understood that the execution subject of the present invention may be a service processing apparatus, and may also be a terminal or a server, and is not limited herein. The embodiment of the present invention is described by taking a server as an execution subject. The server may be an independent server, or may be a cloud server that provides basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a web service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), and a big data and artificial intelligence platform.
In this embodiment, the interceptor embedded in the service server is used mainly as an interceptor that performs interception analysis on a request when the service server has the request to enter, analyzes request information according to different request types, such as a PRC request and an http request, and performs subsequent processing on the service request only after all the interceptors have the result, and returns the result to the front end of the service server through the interceptor after the processing is completed.
In this embodiment, the interceptor is mainly provided in the form of java jar package, and adds a configuration file to a specified directory of the service server, and obtains configuration information carried in the jar package of the interceptor and adds the configuration information to the configuration file, thereby implementing embedding of the interceptor in the service server.
102. Determining a corresponding request parameter acquisition rule according to the request type of the service request;
in this embodiment, the request types of the service request include a PRC request and an http request, and a corresponding request parameter acquisition rule is determined according to different request types, where the request parameter acquisition rule is as follows: if the request type is an http request, acquiring specified parameters in a request header, specified parameters in cookies, specified parameters in a form in a post request, and specified parameters on a get request URL, and if the request type is an RPC request, acquiring the specified parameters in the request or the specified parameters of a JSON object in request data.
103. Analyzing and screening all request parameters in the service request according to a request parameter acquisition rule, and splicing and sequencing the analyzed and screened request parameters according to a preset splicing sequence to obtain multi-dimensional request parameters;
in this embodiment, the request parameter collection rule may analyze and filter all request parameters in the service request, and filter out the request parameters that meet the condition, where the service request may be an http request or an RPC request.
In practical application, a service request is an HTTP request, an HTTP request message is composed of 4 parts of a request line (request line), a request header (header), a null line and request data, wherein the request line is composed of 3 fields of a request method field, a URL field and an HTTP protocol version field, according to the HTTP standard, the HTTP request can use various request methods including GET, post and head methods, and the like, and if the request method of the HTTP request is the GET method, the GET method requires a server to place a resource located by a URL in a data part of a response message and return the resource to a client. When the GET method is used, the request parameters and the corresponding values are attached behind the URL, and the request parameter acquisition rule acquires the specified parameters on the URL in the request line of the GET request. The request data is not used in the get method but in the post method. The post method is suitable for occasions requiring clients to fill in forms, and if the request method is the post method, the specified parameters in the form in the request are collected. The request header consists of key/value pairs, one pair per row, with the key and value separated by the english colon ": to.
In this embodiment, the analyzed and screened request parameters are spliced and sequenced according to a preset splicing sequence, for example, if the service request is an http request, the extracted specified parameters are spliced in sequence according to the sequence of the request line, the request header, the idle line and the request data, and are separated by a blank space.
104. Storing the multidimensional request parameters in a local cache of a current thread of a service server, and releasing an intercepted service request;
in this embodiment, a multithreading technique is used, which refers to a technique for implementing concurrent execution of multiple threads on software or hardware, where different threads are allocated to different service servers in advance and correspond to different threads, each thread corresponds to a local cache, and the local cache is used for storing multidimensional request parameters of a corresponding service server.
In this embodiment, the thread cache is actually a transient cache located inside a thread storage, the storage is a mapping between a key value and an object, a specific multidimensional request parameter determines a key value of a unique identifier, the key value corresponds to a unique object, that is, the key value can be used to identify the uniqueness of the multidimensional request parameter, the key value and the multidimensional request parameter are stored in a local cache, and when a service request triggers service logic processing, the corresponding multidimensional request parameter is obtained from the local cache according to the key value to perform service processing.
105. Detecting whether the service request triggers service logic processing in real time;
in this embodiment, since there is a time interval between the triggering of the service logic processing and the sending time of the service request, and the service logic has a high requirement on the timeliness of the parameter, if data acquisition is performed after the triggering of the service logic processing, different service processing results may occur, so that after a user sends a service request, the service request is directly intercepted, the parameter of the intercepted service request is acquired, and after the multidimensional request parameter is stored in a local cache, whether the service request triggers the service logic processing is detected in real time, thereby avoiding the influence of timeliness.
106. If yes, determining a service scene identifier for triggering service logic processing, and sending the service scene identifier and the multidimensional request parameters in the local cache to a rule engine for service rule logic calculation;
in this embodiment, when it is detected whether the service request triggers service logic processing, a service scene identifier and multidimensional request parameters in the local cache are sent to a rule engine, when the service request needs to request the rule engine to make a service logic decision, an API applied by the original remote call rule engine is changed into a locally called rule engine judgment interface for calling an interceptor, an input parameter of the interface only needs the identifier of the service scene, the rule engine loads a configured rule table in advance, determines a target service rule from the rule table according to the service scene identifier, and performs service logic calculation on the multidimensional request parameters according to the target service rule, thereby obtaining a calculation result finally.
107. And acquiring a calculation result obtained by the rule engine performing service logic calculation, and sending the calculation result to a service server to perform corresponding service logic.
In this embodiment, the calculation result may be a numerical value, for example, the gender of the user is queried, an identity card number is input, the rule engine determines whether the client is male, if the client is male, the output is 0, if the client is female, the output is 1, the calculation result may also be a decision policy or the input is an identity card number, the rule engine determines whether the client is male, for example, if the client is male, the jump link a is output, if the client is female, the jump link B is output, and the user clicks the jump link to perform corresponding service processing.
In the embodiment, a multi-dimensional request parameter is obtained by determining a corresponding request parameter acquisition rule according to a request type, analyzing and screening all request parameters in a service request, and splicing and sequencing the analyzed and screened request parameters; releasing the intercepted service request; when detecting that the service request triggers service logic processing, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameter to a rule engine for service rule logic calculation; and sending the calculation result to a service server to carry out corresponding service logic. According to the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
Referring to fig. 2, a second embodiment of the service processing method according to the embodiment of the present invention includes:
201. intercepting a service request received by a service server and determining the request type of the service request;
specifically, before intercepting a service request received by a service server and determining a request type of the service request, the method may further include acquiring a rule update request and determining an update type of the rule update request, where the update type includes acquisition rule update and service rule update; if the update type is the update of the acquisition rule, acquiring a corresponding first rule code according to the rule update request; updating a request parameter acquisition rule in the rule engine according to the first rule code; if the update type is service rule update, acquiring a corresponding second rule code according to the rule update request; and updating the business rules in the rule engine according to the first rule code.
In this embodiment, the service server monitors the data change of the server that issues the rule. And when the rule updating message is monitored, acquiring the scene identification and the rule identification in the rule updating message, and updating the rule version corresponding to the rule identification in the corresponding service scene into the rule version corresponding to the rule identification in the rule updating message according to the scene identification.
In this embodiment, the rule update includes updating the parameter acquisition rule and updating the service rule, and the update of the rule code in the service server may be implemented by calling a message queue and an http interface. Entering a terminal, selecting a corresponding rule code needing to be modified and updated in a rule scene, editing the rule code into a required rule code through a page online code editor, storing the updated rule code into a database, and generating a new rule version and storing the new rule version into the database. And setting the rule version corresponding to the updated rule code as the current use version.
202. Acquiring a corresponding first acquisition rule from a preset memory space according to the request type of the service request;
203. judging whether the first acquisition rule is valid according to the storage time of the first acquisition rule in the memory space;
204. if so, taking the first acquisition rule as a request parameter acquisition rule corresponding to the service request;
205. if not, sending a rule acquisition request to the rule engine, and taking a second acquisition rule issued by the rule engine as a request parameter acquisition rule corresponding to the service request;
in this embodiment, the business dimension of the rule engine may increase with time, and when the business dimension of the rule engine increases, it is only necessary to issue a new request parameter acquisition rule to the interceptor in the business server. When the storage time of the new memory space exceeds the preset storage time, the request parameter acquisition rule fails, and the service request needs to acquire the request parameter acquisition rule again from the rule engine.
In this embodiment, in order to simplify the logic of issuing the request parameter acquisition rule, the rule engine is requested to acquire the latest acquisition rule every preset time, and the latest acquisition rule is cached in the memory of the application server, for example, the acquisition rule is requested to be updated once every 10 minutes.
206. Extracting request parameters in a request header of a service request;
in this embodiment, the service request is an http request, and is composed of 4 parts, namely, a request line (request line), a request header (header), a null line and request data, wherein the http request is composed of a key/value pair, each line is a pair, and the key and the value are separated by an english colon. The request header informs the server of information about the client request, and typical request headers are: User-Agent: generating a browser type of the request; accept: a content type list that the client can identify; host: the requested host name, allows multiple domain names to be collocated with one IP address, i.e., a virtual host.
207. Determining a request method in a request line, wherein the request method comprises a get request and a post request;
in practical applications, the http request may use various request methods according to the http standard, including get, post, and head methods.
208. If the request method is a get request, extracting request parameters of a URL in a request header;
in this embodiment, if the request method of the http request is the GET method, the GET method requires the server to place the resource located by the URL in the data portion of the response packet, and send the resource back to the client. When the GET method is used, the request parameters and the corresponding values are attached behind the URL, and the request parameter acquisition rule acquires the specified parameters on the URL in the request line of the GET request.
209. If the request method is a post request, determining that the service request carries a form, and extracting request parameters from the form;
in this embodiment, if the request method is a post request, the request data is not used in the get method, but is used in the post method. The post method is suitable for occasions requiring clients to fill in forms, if the request method is the post method, designated parameters in forms in requests are collected, in practical application, the forms are used for receiving input of users, the input of the users is submitted to a server in a mode of a set of 'name value pair', the forms are defined by < form > </form >, various controls for receiving input of the users are placed in the forms, the forms submitted by post are used, data are submitted to the server in a data block mode, form data cannot appear in URLs, and therefore the form data submitted in the mode are safe.
210. Determining whether the service request carries the cookie or not, and if so, extracting request parameters in the cookie;
in practical applications, the Cookie is used for maintaining a session state of the server, and is usually written by the server and is read by the server in a subsequent request. Generally, both the HTTP response message and the HTTP request message include Cookie information, which respectively exist in the Set-Cookie field and the Cookie field, and the Cookie information may include a plurality of Cookie name/value pairs.
211. Splicing and sequencing all the request parameters according to a preset splicing sequence to obtain multi-dimensional request parameters;
in this embodiment, the analyzed and screened request parameters are subjected to splicing sequencing according to a preset splicing sequence, for example, if the service request is an http request, the extracted specified parameters are spliced in sequence and separated by spaces according to the sequence of the request line, the request header, the blank line and the request data.
212. Storing the multidimensional request parameters in a local cache of a current thread of a service server, and releasing the intercepted service request;
213. detecting whether the service request triggers service logic processing in real time;
214. if yes, determining a service scene identifier for triggering service logic processing, and sending the service scene identifier and the multidimensional request parameters in the local cache to a rule engine for service rule logic calculation;
215. and acquiring a calculation result obtained by the rule engine performing service logic calculation, and sending the calculation result to a service server to perform corresponding service logic.
On the basis of the previous embodiment, the process of determining the corresponding request parameter acquisition rule according to the request type of the service request is described in detail, and the corresponding first acquisition rule is acquired from the preset memory space according to the request type of the service request; judging whether the first acquisition rule is valid or not according to the storage time of the first acquisition rule in the memory space; if so, taking the first acquisition rule as a request parameter acquisition rule corresponding to the service request; if not, sending a rule acquisition request to the rule engine, and taking a second acquisition rule issued by the rule engine as a request parameter acquisition rule corresponding to the service request. By the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
Referring to fig. 3, a third embodiment of the service processing method according to the embodiment of the present invention includes:
301. intercepting a service request received by a service server and determining the request type of the service request;
302. determining a corresponding request parameter acquisition rule according to the request type of the service request;
303. extracting request parameters in a request header of a service request according to a request parameter acquisition rule;
304. judging whether the service request carries a JSON object or not;
305. if so, extracting a request parameter in the JSON object;
306. splicing and sequencing all the request parameters according to a preset splicing sequence to obtain multi-dimensional request parameters;
in practical application, RPC refers to remote procedure call, that is, two servers a and B, one application is deployed on the server a, and it is desired to call a function/method provided by the application on the server B, because it is not in a memory space, it cannot be called directly, and it is necessary to express the semantics of the call and to convey the data of the call through a network, that is, the request parameter.
In practical application, JSON (JavaScript object notation) is a compact text file format, and can be used for storing and transmitting data, and when an RPC request carries a JSON object, a data parameter in the JSON object needs to be read as a request parameter.
307. Storing the multidimensional request parameters in a local cache of a current thread of a service server, and releasing an intercepted service request;
308. detecting whether the service request triggers service logic processing in real time;
309. if yes, determining a service scene identifier triggering service logic processing, and calling a preset rule engine to judge an interface;
310. sending the service request and the service scene identifier to a rule engine through a rule engine judgment interface;
in this embodiment, a service scene identifier of a service request triggering the service logic processing is determined, and when a preset rule engine judgment interface is called, validity authentication is performed on received request information, when the result of the validity authentication is valid, authentication valid information is sent to a service server, and after the service server receives the authentication valid information, the step of sending a request operation rule can be continuously executed; and when the validity authentication result is invalid, the invalid authentication information can be sent, or no information can be sent, at this time, a timer can be set in the service server, and when the validity authentication information is not received within the preset time period, the validity authentication which does not pass through the rule engine is represented, and the request information can be sent again.
311. When receiving authentication valid information sent by a rule engine after authenticating the service request and the service scene identifier, judging and determining a local cache corresponding to the service request;
312. sending a parameter query request to a local cache, and receiving a multi-dimensional request parameter returned by the local cache;
313. sending the multidimensional request parameters in the local cache to a rule engine for business logic calculation;
in this embodiment, a multithreading technique is used, which refers to a technique for implementing concurrent execution of multiple threads on software or hardware, where different threads are allocated to different service servers in advance and correspond to different threads, each thread corresponds to a local cache, and the local cache is used for storing multidimensional request parameters of a corresponding service server. Due to the adoption of the multithreading technology, after the service request and the service scene identifier are determined to be effective, a corresponding local cache needs to be determined according to the current thread, and the multidimensional request parameter is acquired from the local cache.
314. And acquiring a calculation result obtained by the rule engine through business logic calculation, and sending the calculation result to a business server for corresponding business logic.
The present embodiment describes in detail a process of determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameter in the local cache to a rule engine for performing service rule logic calculation, on the basis of the previous embodiment, by determining the service scene identifier triggering the service logic processing, and calling a preset rule engine judgment interface; sending the service request and the service scene identifier to the rule engine through the rule engine judgment interface; and when receiving the authentication valid information sent by the rule engine after the service request and the service scene identification are authenticated, sending the multidimensional request parameters in the local cache to the rule engine for service logic calculation. According to the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
With reference to fig. 4, the service processing method in the embodiment of the present invention is described above, and the service processing apparatus in the embodiment of the present invention is described below, where an embodiment of the service processing apparatus in the embodiment of the present invention includes:
the intercepting module 401 is configured to intercept a service request received by a service server, and determine a request type of the service request;
a rule determining module 402, configured to determine, according to a request type of the service request, a corresponding request parameter acquisition rule;
the splicing module 403 is configured to analyze and screen all request parameters in the service request according to the request parameter acquisition rule, and splice and sort the analyzed and screened request parameters according to a preset splicing order to obtain multidimensional request parameters;
a releasing module 404, configured to store the multidimensional request parameter in a local cache of a current thread of the service server, and release an intercepted service request;
a detection module 405, configured to detect whether the service request triggers service logic processing in real time;
a calculation module 406, configured to determine a service scene identifier for triggering service logic processing when the service request triggers service logic processing, and send the service scene identifier and the multidimensional request parameter in the local cache to a rule engine for performing service rule logic calculation;
and the forwarding module 407 is configured to obtain a calculation result obtained by performing service logic calculation by the rule engine, and send the calculation result to a service server for performing corresponding service logic.
In the embodiment of the invention, the service processing device runs the service processing method, and the service processing device determines a corresponding request parameter acquisition rule according to the request type, analyzes and screens all request parameters in the service request, and splices and sorts the analyzed and screened request parameters to obtain multi-dimensional request parameters; releasing the intercepted service request; when detecting that the service request triggers service logic processing, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameter to a rule engine for service rule logic calculation; and sending the calculation result to a service server to carry out corresponding service logic. According to the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
Referring to fig. 5, a second embodiment of the service processing apparatus according to the embodiment of the present invention includes:
the intercepting module 401 is configured to intercept a service request received by a service server, and determine a request type of the service request;
a rule determining module 402, configured to determine, according to a request type of the service request, a corresponding request parameter acquisition rule;
the splicing module 403 is configured to analyze and screen all request parameters in the service request according to the request parameter acquisition rule, and splice and sort the analyzed and screened request parameters according to a preset splicing order to obtain multidimensional request parameters;
a releasing module 404, configured to store the multidimensional request parameter in a local cache of a current thread of the service server, and release an intercepted service request;
a detection module 405, configured to detect whether the service request triggers service logic processing in real time;
a calculation module 406, configured to determine a service scene identifier for triggering service logic processing when the service request triggers service logic processing, and send the service scene identifier and the multidimensional request parameter in the local cache to a rule engine for performing service rule logic calculation;
and the forwarding module 407 is configured to obtain a calculation result obtained by performing service logic calculation by the rule engine, and send the calculation result to a service server for performing corresponding service logic.
In this embodiment, the rule determining module 402 is specifically configured to: acquiring a corresponding first acquisition rule from a preset memory space according to the request type of the service request; judging whether the first acquisition rule is valid or not according to the storage time of the first acquisition rule in the memory space; if so, taking the first acquisition rule as a request parameter acquisition rule corresponding to the service request; if not, sending a rule acquisition request to a rule engine, and taking a second acquisition rule issued by the rule engine as a request parameter acquisition rule corresponding to the service request.
In this embodiment, the request type includes an http request, the service request includes a request line and a request header, and when the request type is an http request, the splicing module 403 is specifically configured to: extracting request parameters in a request header of the service request according to the request parameter acquisition rule; determining a request method in the request line, wherein the request method comprises a get request and a post request; if the request method is a get request, extracting request parameters of the URL in the request line; if the request method is a post request, determining that the service request carries a form, and extracting request parameters from the form; determining whether the service request carries cookie or not, and if so, extracting request parameters in the cookie; and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
In this embodiment, the request type further includes an RCP request, the service request includes a request header, and when the request type is an RPC request, the splicing module 403 is specifically configured to: extracting request parameters in a request header of the service request according to the request parameter acquisition rule; judging whether the service request carries a JSON object or not; if yes, extracting a request parameter in the JSON object; and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
In this embodiment, the calculating module 406 specifically includes: an interface calling unit 4061, configured to determine a service scene identifier triggering the service logic processing, and call a preset rule engine to determine an interface; a sending unit 4062, configured to send the service request and the service scenario identifier to the rule engine through the rule engine determination interface; the authentication unit 4063, configured to send the multidimensional request parameter in the local cache to the rule engine for performing service logic calculation when receiving authentication valid information sent by the rule engine after authenticating the service request and the service scene identifier.
In this embodiment, the authentication unit 4063 is specifically configured to: when receiving authentication valid information sent by the rule engine after authenticating the service request and the service scene identifier, judging a local cache corresponding to the service request; sending a parameter query request to the local cache, and receiving a multi-dimensional request parameter returned by the local cache; and sending the multidimensional request parameters in the local cache to the rule engine for business logic calculation.
In this embodiment, the service processing apparatus further includes an update module 408, where the update module 408 is specifically configured to: acquiring a rule updating request and determining an updating type of the rule updating request, wherein the updating type comprises acquisition rule updating and business rule updating; if the update type is acquisition rule update, acquiring a corresponding first rule code according to the rule update request; updating a request parameter acquisition rule in the rule engine according to the first rule code; if the update type is service rule update, acquiring a corresponding second rule code according to the rule update request; and updating the business rules in the rule engine according to the first rule code.
On the basis of the previous embodiment, the specific functions of each module and the unit composition of part of the modules are described in detail, and through the module units, the corresponding request parameter acquisition rules can be determined according to the request types, all request parameters in the service request are analyzed and screened, and the analyzed and screened request parameters are spliced and sequenced to obtain multi-dimensional request parameters; releasing the intercepted service request; when detecting that the service request triggers service logic processing, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameters to a rule engine for service rule logic calculation; and sending the calculation result to a service server to carry out corresponding service logic. According to the method, the business scene does not need to pay attention to all latitude parameters input into the rule engine, and even if more latitude condition parameters are newly added to the rule engine, the business scene can immediately carry out business operation on newly added dimension conditions without modification.
Fig. 4 and fig. 5 describe the middle service processing apparatus in the embodiment of the present invention in detail from the perspective of the modular functional entity, and the service processing apparatus in the embodiment of the present invention is described in detail from the perspective of hardware processing.
Fig. 6 is a schematic structural diagram of a business processing apparatus 600 according to an embodiment of the present invention, where the business processing apparatus 600 may generate relatively large differences due to different configurations or performances, and may include one or more processors (CPUs) 610 (e.g., one or more processors) and a memory 620, and one or more storage media 630 (e.g., one or more mass storage devices) for storing applications 633 or data 632. Memory 620 and storage medium 630 may be, among other things, transient or persistent storage. The program stored on the storage medium 630 may include one or more modules (not shown), each of which may include a sequence of instructions for operating on the business processing apparatus 600. Further, the processor 610 may be configured to communicate with the storage medium 630, and execute a series of instruction operations in the storage medium 630 on the service processing device 600 to implement the steps of the service processing method.
The business processing device 600 may also include one or more power supplies 640, one or more wired or wireless network interfaces 650, one or more input-output interfaces 660, and/or one or more operating systems 631, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, and so forth. Those skilled in the art will appreciate that the service processing device configuration illustrated in fig. 6 is not intended to be limiting of the service processing devices provided herein and may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components.
The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, and which may also be a volatile computer-readable storage medium, having stored therein instructions, which, when run on a computer, cause the computer to perform the steps of the business process method.
It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working process of the system, the apparatus, and the unit described above may refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; although the present invention has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A service processing method is characterized in that the service processing method comprises the following steps:
intercepting a service request received by a service server and determining the request type of the service request;
determining a corresponding request parameter acquisition rule according to the request type of the service request;
analyzing and screening all request parameters in the service request according to the request parameter acquisition rule, and splicing and sequencing the analyzed and screened request parameters according to a preset splicing sequence to obtain multi-dimensional request parameters;
storing the multidimensional request parameters in a local cache of a current thread of the service server, and releasing the intercepted service request;
detecting whether the service request triggers service logic processing in real time;
if yes, determining a service scene identifier triggering the service logic processing, and sending the service scene identifier and the multidimensional request parameters in the local cache to a rule engine for service rule logic calculation;
and acquiring a calculation result obtained by the rule engine through business logic calculation, and sending the calculation result to a business server for corresponding business logic.
2. The service processing method according to claim 1, wherein determining the corresponding request parameter acquisition rule according to the request type of the service request comprises:
acquiring a corresponding first acquisition rule from a preset memory space according to the request type of the service request;
judging whether the first acquisition rule is valid or not according to the storage time of the first acquisition rule in the memory space;
if so, taking the first acquisition rule as a request parameter acquisition rule corresponding to the service request;
if not, sending a rule acquisition request to a rule engine, and taking a second acquisition rule issued by the rule engine as a request parameter acquisition rule corresponding to the service request.
3. The service processing method according to claim 1, wherein the request type includes an http request, the service request includes a request line and a request header, and when the request type is an http request, the analyzing and screening are performed on all request parameters in the service request according to the request parameter acquisition rule, and the splicing and ordering are performed on the request parameters analyzed and screened according to a preset splicing order, so as to obtain multidimensional request parameters, including:
extracting request parameters in a request header of the service request according to the request parameter acquisition rule;
determining a request method in the request line, wherein the request method comprises a get request and a post request;
if the request method is a get request, extracting request parameters of the URL in the request line;
if the request method is a post request, determining that the service request carries a form, and extracting request parameters from the form;
determining whether the service request carries a cookie or not, and if so, extracting request parameters in the cookie;
and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
4. The service processing method of claim 1, wherein the request types further include RCP requests, the service requests include request headers, and when the request types are RPC requests, the service requests are analyzed and screened according to the request parameter acquisition rules, and the analyzed and screened request parameters are spliced and sorted according to a preset splicing order to obtain multidimensional request parameters, including:
extracting request parameters in a request header of the service request according to the request parameter acquisition rule;
judging whether the service request carries a JSON object or not;
if yes, extracting a request parameter in the JSON object;
and splicing and sequencing all the request parameters according to a preset splicing sequence to obtain the multi-dimensional request parameters.
5. The business processing method of claim 1, wherein the determining the business scenario identifier triggering the business logic processing, and sending the business scenario identifier and the multidimensional request parameter in the local cache to a rule engine for business rule logic calculation comprises:
determining a service scene identifier triggering the service logic processing, and calling a preset rule engine judgment interface;
sending the service request and the service scene identifier to the rule engine through the rule engine judgment interface;
and when receiving the authentication valid information sent by the rule engine after the service request and the service scene identification are authenticated, sending the multidimensional request parameters in the local cache to the rule engine for service logic calculation.
6. The service processing method according to claim 5, wherein the sending the multidimensional request parameter in the local cache to the rule engine for service logic calculation when receiving authentication valid information sent by the rule engine after the service request and the service scene identifier are authenticated comprises:
when receiving authentication valid information sent by the rule engine after authenticating the service request and the service scene identifier, judging that the local cache corresponding to the service request is determined;
sending a parameter query request to the local cache, and receiving a multi-dimensional request parameter returned by the local cache;
and sending the multidimensional request parameters in the local cache to the rule engine for business logic calculation.
7. The method according to any of claims 1-6, further comprising, before intercepting the service request received by the service server and determining a request type of the service request:
acquiring a rule updating request and determining an updating type of the rule updating request, wherein the updating type comprises acquisition rule updating and service rule updating;
if the update type is acquisition rule update, acquiring a corresponding first rule code according to the rule update request;
updating a request parameter acquisition rule in the rule engine according to the first rule code;
if the update type is service rule update, acquiring a corresponding second rule code according to the rule update request;
and updating the business rules in the rule engine according to the first rule code.
8. A service processing apparatus, characterized in that the service processing apparatus comprises:
the intercepting module is used for intercepting a service request received by a service server and determining the request type of the service request;
the rule determining module is used for determining a corresponding request parameter acquisition rule according to the request type of the service request;
the splicing module is used for analyzing and screening all request parameters in the service request according to the request parameter acquisition rule, and splicing and sequencing the analyzed and screened request parameters according to a preset splicing sequence to obtain multi-dimensional request parameters;
the release module is used for storing the multidimensional request parameters in a local cache of a current thread of the service server and releasing the intercepted service request;
the detection module is used for detecting whether the service request triggers service logic processing in real time;
the calculation module is used for determining a service scene identifier for triggering the service logic processing when the service request triggers the service logic processing, and sending the service scene identifier and the multidimensional request parameters in the local cache to a rule engine for service rule logic calculation;
and the forwarding module is used for acquiring a calculation result obtained by the rule engine through service logic calculation and sending the calculation result to a service server for carrying out corresponding service logic.
9. A service processing device, characterized in that the service processing device comprises: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line;
the at least one processor invoking the instructions in the memory to cause the business processing apparatus to perform the steps of the business processing method of any of claims 1-7.
10. A computer-readable storage medium, having a computer program stored thereon, which, when being executed by a processor, carries out the steps of the traffic processing method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210582474.6A CN115103026B (en) | 2022-05-26 | 2022-05-26 | Service processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210582474.6A CN115103026B (en) | 2022-05-26 | 2022-05-26 | Service processing method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115103026A true CN115103026A (en) | 2022-09-23 |
| CN115103026B CN115103026B (en) | 2023-06-16 |
Family
ID=83288766
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210582474.6A Active CN115103026B (en) | 2022-05-26 | 2022-05-26 | Service processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115103026B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101017540A (en) * | 2007-01-24 | 2007-08-15 | 华为技术有限公司 | Intelligent questionnaire system, questionnaire development method and device thereof |
| WO2010011528A1 (en) * | 2008-07-24 | 2010-01-28 | Abb Research Ltd. | System and method of business rule integration with engineering applications |
| CN108399176A (en) * | 2017-02-07 | 2018-08-14 | 阿里巴巴集团控股有限公司 | A kind of rule-based data processing method and regulation engine device |
| CN110782169A (en) * | 2019-10-29 | 2020-02-11 | 中国联合网络通信集团有限公司 | Method and device for updating business process |
| CN113377372A (en) * | 2021-06-29 | 2021-09-10 | 平安普惠企业管理有限公司 | Business rule analysis method and device, computer equipment and storage medium |
| CN114416026A (en) * | 2021-11-19 | 2022-04-29 | 中国建设银行股份有限公司 | Business demand analysis system, method, computer device and storage medium |
-
2022
- 2022-05-26 CN CN202210582474.6A patent/CN115103026B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101017540A (en) * | 2007-01-24 | 2007-08-15 | 华为技术有限公司 | Intelligent questionnaire system, questionnaire development method and device thereof |
| WO2010011528A1 (en) * | 2008-07-24 | 2010-01-28 | Abb Research Ltd. | System and method of business rule integration with engineering applications |
| CN108399176A (en) * | 2017-02-07 | 2018-08-14 | 阿里巴巴集团控股有限公司 | A kind of rule-based data processing method and regulation engine device |
| CN110782169A (en) * | 2019-10-29 | 2020-02-11 | 中国联合网络通信集团有限公司 | Method and device for updating business process |
| CN113377372A (en) * | 2021-06-29 | 2021-09-10 | 平安普惠企业管理有限公司 | Business rule analysis method and device, computer equipment and storage medium |
| CN114416026A (en) * | 2021-11-19 | 2022-04-29 | 中国建设银行股份有限公司 | Business demand analysis system, method, computer device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115103026B (en) | 2023-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8051207B2 (en) | Inferring server state in s stateless communication protocol | |
| US8825849B2 (en) | Distributed data collection and aggregation | |
| CN112035317B (en) | Micro-service link monitoring method, device, equipment and medium | |
| JP2002507308A (en) | Method and apparatus for redirecting a hyperlink query to an external server | |
| WO2008130946A2 (en) | Unobtrusive methods and systems for collecting information transmitted over a network | |
| CN113676563B (en) | Scheduling method, device, equipment and storage medium of content distribution network service | |
| US11372937B1 (en) | Throttling client requests for web scraping | |
| US11178160B2 (en) | Detecting and mitigating leaked cloud authorization keys | |
| CN114465741B (en) | Abnormality detection method, abnormality detection device, computer equipment and storage medium | |
| EP3579526B1 (en) | Resource file feedback method and apparatus | |
| US10419351B1 (en) | System and method for extracting signatures from controlled execution of applications and application codes retrieved from an application source | |
| CN111600929B (en) | Transmission line detection method, routing strategy generation method and proxy server | |
| CN115103026B (en) | Service processing method, device, equipment and storage medium | |
| CN113778709B (en) | Interface calling method, device, server and storage medium | |
| EP4227829A1 (en) | Web scraping through use of proxies, and applications thereof | |
| CN113965385B (en) | Monitoring processing method, device, equipment and medium for abnormal website | |
| US20230018983A1 (en) | Traffic counting for proxy web scraping | |
| US10810302B2 (en) | Database access monitoring with selective session information retrieval | |
| JPH0950422A (en) | Interaction succession type access control method on computer network and server computer therefor | |
| US20050204403A1 (en) | Method and system for monitoring the operation of networked computing system | |
| KR102654479B1 (en) | A system that detects and monitors the risk of tampering with request parameters by generating and executing verification queries through analysis of large amounts of user behavior data | |
| CN113987317A (en) | Front-end request processing method, device, equipment and storage medium | |
| CN117336215A (en) | Network data auditing method and device, electronic equipment and storage medium | |
| CN116260750A (en) | Flow mirroring method, device, electronic equipment, storage medium and product | |
| WO2009128820A1 (en) | Unobtrusive methods and systems for collecting information transmitted over a network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |