CN114398631A - Business processing method and device, electronic equipment and storage medium - Google Patents
Business processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114398631A CN114398631A CN202111564288.1A CN202111564288A CN114398631A CN 114398631 A CN114398631 A CN 114398631A CN 202111564288 A CN202111564288 A CN 202111564288A CN 114398631 A CN114398631 A CN 114398631A
- Authority
- CN
- China
- Prior art keywords
- service request
- target service
- lock
- target
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/552—Detecting local intrusion or implementing counter-measures involving long-term monitoring or reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2336—Pessimistic concurrency control approaches, e.g. locking or multiple versions without time stamps
- G06F16/2343—Locking methods, e.g. distributed locking or locking implementation details
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a service processing method and device, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring a target service request; determining an idempotent function corresponding to the target service request, and judging whether to acquire a lock corresponding to the target service request according to the idempotent function; if yes, executing a service logic corresponding to the target service request; if not, returning abnormal information. The method and the device can prevent a large number of malicious and useless repeated requests and repeated submission of repeated form data caused by network jitter, so that the high availability, high expansibility, safety and the like of the system are efficiently improved, the clustered deployment of the service system is safer, simpler and more stable, and the service system is rapidly accessed without service intrusiveness based on configuration.
Description
Technical Field
The present application relates to the field of internet, and in particular, to a method and an apparatus for processing a service, an electronic device, and a storage medium.
Background
The hospital system single body is applied to the clustering deployment process, a timing task exists in the service, information such as medicine data, medicine inventory and inspection projects of an external system needs to be called, and the tasks are executed simultaneously at the same time under multiple nodes, so that repeated medicine catalog information of pharmacy data in a hospital can be caused; and under the weak network environment, form data repeated submission appears when a resident checks the medical advice, the medicines prescribed under the medical advice have repeated examination items, and a large amount of medical personnel cost is required to delete the repeated data, so that the efficiency of personnel is reduced, the time cost is increased, and the unreliability of the system is increased.
Existing service-based clustered deployment: the general scheme is that through a token mechanism, when a service interface is called, a back end is requested to generate a token, the token is stored in a cache redis-key and returned to a front end, a front end form is submitted and needs to carry the token on a headset to request the back end interface, and therefore a user may maliciously tamper with a large number of tokens and request the back end interface, system load is overlarge, a large number of useless keys exist in redis within a short time, and even the unavailability of the service end is caused. The existing annotation-based mode is to intercept a unique identifier before checking a calling method before a target method enters through a tangent plane thought, and is also a unique identifier which causes a large amount of invalidity in a short time, so that the customization and componentization modes cannot be realized, and the method cannot be quickly and efficiently integrated into engineering projects.
Disclosure of Invention
The embodiment of the application provides a service processing method, which is used for preventing a large number of malicious and useless repeated service requests, efficiently improving the high availability, high expansibility, safety and the like of a system, enabling the clustered deployment of a service system to be safer, simpler and more stable, and achieving the purpose of rapidly accessing the service system based on configuration and service non-invasiveness.
The embodiment of the application provides a service processing method, which comprises the following steps:
acquiring a target service request;
determining an idempotent function corresponding to the target service request, and judging whether to acquire a lock corresponding to the target service request according to the idempotent function;
if yes, executing a service logic corresponding to the target service request;
if not, returning abnormal information.
In one embodiment, the idempotent function is based on a Mysql optimistic lock;
the determining whether to obtain the lock corresponding to the target service request according to the idempotent function includes:
creating a table structure comprising a primary key id and a lock name;
performing md5 information abstract algorithm calculation on the designated service parameters in the target service request to obtain a target identifier;
searching whether a lock record table item corresponding to the target identifier exists in the created lock record table structure; if so, determining that the lock corresponding to the target service request is not obtained;
if not, determining to obtain the lock corresponding to the target service request, and creating a lock record table entry corresponding to the target identifier.
In an embodiment, the idempotent function is based on a Redission distributed lock;
the determining whether to obtain the lock corresponding to the target service request according to the idempotent function includes:
performing md5 information abstract algorithm calculation on the designated service parameters in the target service request to obtain a target identifier;
judging whether a lock corresponding to the target identifier exists according to an interface of a try lock in the Redission;
if yes, determining to obtain a lock corresponding to the target service request;
if not, determining that the lock corresponding to the target service request is not obtained.
In an embodiment, the idempotent function is based on a Zookeeper distributed lock;
the determining whether to obtain the lock corresponding to the target service request according to the idempotent function includes:
performing md5 information abstract algorithm calculation on the designated service parameters in the target service request to obtain a target identifier;
judging whether a lock corresponding to the target identifier exists according to an acquire interface in the Zookeeper;
if yes, determining to obtain a lock corresponding to the target service request;
if not, determining that the lock corresponding to the target service request is not obtained.
In one embodiment, the determining an idempotent function corresponding to the target service request includes:
and determining the idempotent function according to annotation configuration information corresponding to the target service request.
In an embodiment, the annotation configuration information comprises a switch of the extension component;
before the obtaining the target service request, the method further includes:
instantiating the extension component through a spring framework to obtain the extension component of the idempotent function annotation.
In an embodiment, before the instantiating the extension component through the spring framework, the method further includes:
loading a component resource package of the extension component from a specified resource path of the spring framework;
and injecting configuration class information corresponding to the extension component.
An embodiment of the present application further provides a service processing apparatus, including:
the request acquisition module is used for acquiring a target service request;
the judging module is used for determining an idempotent function corresponding to the target service request and judging whether to acquire a lock corresponding to the target service request according to the idempotent function;
the service logic execution module is used for executing the service logic corresponding to the target service request if the service logic is the target service request;
and the abnormal information returning module is used for returning the abnormal information if the abnormal information is not returned.
An embodiment of the present application further provides an electronic device, where the electronic device includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the service processing method.
An embodiment of the present application further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is executable by a processor to implement the service processing method.
According to the technical scheme provided by the embodiment of the application, the target service request is acquired; determining an idempotent function corresponding to the target service request, and judging whether to acquire a lock corresponding to the target service request according to the idempotent function; if yes, executing a service logic corresponding to the target service request; if not, returning abnormal information, thereby preventing a large number of malicious useless requests, efficiently improving the high availability, high expansibility, reusability and the like of the system, ensuring that the clustered deployment of the service system is safer, simpler and more stable, and realizing the rapid service access system without service intrusiveness based on configuration.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a service processing method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a service processing method according to an embodiment of the present application;
fig. 4 is a block diagram of a service processing apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
The method comprises the steps of determining an idempotent function corresponding to a target service request by acquiring the target service request, judging whether a lock corresponding to the target service request is acquired according to the idempotent function, and if so, executing a service logic corresponding to the target service request; if not, returning abnormal information.
Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device may be configured to execute the service processing method provided in the embodiment of the present application. As shown in fig. 1, the electronic device 100 includes: one or more processors 102, one or more memories 104 storing processor-executable instructions, wherein the processors 102 are configured to perform the business processing methods provided by the embodiments described below herein.
The processor 102 may be a gateway, or may be an intelligent terminal, or may be a device including a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or other form of processing unit having data processing capability and/or instruction execution capability, and may process data of other components in the electronic device 100, and may control other components in the electronic device 100 to perform desired functions.
The memory 104 may include one or more computer program products that may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, Random Access Memory (RAM), cache memory (cache), and/or the like. The non-volatile memory may include, for example, Read Only Memory (ROM), hard disk, flash memory, etc. On which one or more computer program instructions may be stored that may be executed by processor 102 to implement the business process methods described below. Various applications and various data, such as various data used and/or generated by the applications, may also be stored in the computer-readable storage medium.
In one embodiment, the electronic device 100 shown in FIG. 1 may also include an input device 106, an output device 108, and a data acquisition device 110, which are interconnected via a bus system 112 and/or other form of connection mechanism (not shown). It should be noted that the components and structure of the electronic device 100 shown in fig. 1 are exemplary only, and not limiting, and the electronic device may have other components and structures as desired.
The input device 106 may be a device used by a user to input instructions and may include one or more of a keyboard, a mouse, a microphone, a touch screen, and the like. The output device 108 may output various information (e.g., images or sounds) to the outside (e.g., a user), and may include one or more of a display, a speaker, and the like. The data acquisition device 110 may acquire an image of a subject and store the acquired image in the memory 104 for use by other components. Illustratively, the data acquisition device 110 may be a camera.
In an embodiment, the devices in the exemplary electronic device for implementing the business processing method of the embodiment of the present application may be integrally disposed, or may be disposed in a decentralized manner, such as integrally disposing the processor 102, the memory 104, the input device 106 and the output device 108, and disposing the data acquisition device 110 separately.
In an embodiment, an example electronic device for implementing the service processing method of the embodiment of the present application may be implemented as an intelligent terminal, such as a smart phone, a tablet computer, a smart watch, an in-vehicle device, and the like.
Fig. 2 is a schematic flow chart of a service processing method according to an embodiment of the present application. As shown in fig. 2, the method may include the following steps S210-S240.
Step S210: and acquiring a target service request.
And the server side acquires the target service request. The target business is, for example, a business for prescription in a hospitalization system, and is not limited herein.
Step S220: and determining an idempotent function corresponding to the target service request, and judging whether to acquire a lock corresponding to the target service request according to the idempotent function. If yes, go to step S230; if not, go to step S240.
After the server side obtains the target service request, determining an idempotent function corresponding to the target service request, wherein the idempotent function comprises the following steps: mysql, Redis, and Zookepper's corresponding idempotent implementation classes. And judging whether to acquire a lock corresponding to the target service request according to the idempotent function, wherein the lock corresponding to the target service request comprises the following steps: mysql optimistic locks, Redis distributed locks, and Zookeeper distributed locks. If yes, go to step S230; if not, go to step S240.
Step S230: and executing the service logic corresponding to the target service request.
And judging whether to obtain the lock corresponding to the target service request according to the idempotent function in the step S220, if so, obtaining the lock corresponding to the target service request, and executing the service logic corresponding to the target service request.
Step S240: and returning exception information.
And according to the above-mentioned step S220, determining whether to obtain the lock corresponding to the target service request according to the idempotent function, if not, not obtaining the lock corresponding to the target service request, and returning abnormal information indicating that there is repeatedly submitted abnormal information, which is not limited herein.
Fig. 3 is a schematic flow chart of a service processing method according to an embodiment of the present application. As shown in fig. 3, the method may include the following steps S310-S380.
Step S310: and loading the component resource package of the extension component from the specified resource path of the spring framework.
The method comprises the steps of firstly defining a Spring framework extension class, wherein the extension class is IdemConnectorBeanInject, then assembling an or. The component resource packet is a component jar packet, and the resource path is a storage address of the component jar packet, similar to addresses of an internal path, a relative path, and an absolute path, which is not limited herein.
Step S320: configuration class information corresponding to the extension component is injected.
Configuration class information corresponding to the extension component is injected. Wherein the configuration class information includes: the creation of the extension component is connected with entity class information, host information of the component, port number, account number, password and the like, and management-related api implementation classes injected into the corresponding extension component. Wherein the api is an application program interface.
Step S330: and instantiating the extension component through the spring framework to obtain the extension component annotated by the idempotent function.
The extension component with idempotent functions of Mysql, Redission and Zookeeper annotation is obtained by adding a component switch pre prefix field xw-idemponent and idemponent into a spring frame as prefixes and then instantiating the extension component. Wherein, the function of extension subassembly includes: is _ print: adding whether a log is printed or not, and identity-name: and adding the type of the idempotent lock, wherein the type of the idempotent lock is Mysql optimistic lock, Redis distributed lock, Zookeeper distributed lock and the like.
Step S340: and acquiring a target service request. For details, refer to the description of step S210 in the above embodiments, which is not repeated herein.
Step S350: and determining an idempotent function according to annotation configuration information corresponding to the target service request.
According to annotation configuration information corresponding to the target service request, wherein the annotation configuration information is @ interface idemponentlimit (functionintame, int second, string des), and the interface idemponentlimit is an annotation name; functionname is the method name; int second is the number of requests within a certain time, for example, if second is 5, it means that 5s requests can only be made once, and other requests are repeatedly filtered; string des is a quick response default value, which represents the exception information that is repeatedly submitted by the quick response. The annotation configuration information includes switches of the extension component. According to the annotation configuration information, determining an idempotent function, wherein the idempotent function comprises: mysql, Redis, and Zookepper's corresponding idempotent implementation classes.
Step S360: and judging whether to acquire the lock corresponding to the target service request according to the idempotent function.
And judging whether to obtain a lock corresponding to the target service request according to the idempotent function, wherein the lock corresponding to the target service request is a Mysql optimistic lock, a Redis distributed lock and a Zookeeper distributed lock. If the lock corresponding to the target service request is judged to be obtained according to the idempotent function, step S370 is executed; if it is determined according to the idempotent function that the lock corresponding to the target service request is not obtained, step S380 is executed.
Step S370: and executing the service logic corresponding to the target service request.
For details, refer to the description of step S230 in the above embodiments, which is not repeated herein.
Step S380: and returning exception information.
For details, refer to the description of step S240 in the above embodiments, which is not repeated herein.
In one embodiment, the idempotent function Mysql is based on Mysql optimistic locks; judging whether to obtain a Mysql optimistic lock corresponding to the target service request according to the idempotent function Mysql, which comprises the following steps: creating a table structure comprising a primary key id and a lock name; combining the specified service parameters and the service method in the target service request, and performing md5 information abstract algorithm calculation to obtain a target identification key; wherein, the specified service parameter may be a method name and a request parameter name, and in the created lock record table structure, by means of select from fu _ distribute _ lock _ name? for update to find out whether a lock record item corresponding to the target identification key exists, wherein the lock record item can be set with valid time; if yes, determining that the Mysql optimistic lock corresponding to the target service request is not obtained; if not, determining to obtain the Mysql optimistic lock corresponding to the target service request, and creating a lock record table entry corresponding to the target identifier.
In one embodiment, the idempotent function Redission is based on a Redission distributed lock; according to the idempotent function Redission, whether a Redission distributed lock corresponding to the target service request is obtained or not is judged, and the method comprises the following steps: performing md5 information abstract algorithm calculation on the designated service parameters in the target service request, wherein the designated service parameters can be a method name and a request parameter name to obtain a target identification key; judging whether a lock corresponding to the target identification key exists according to the interface redisclient of the try lock in the Redission; if so, determining to obtain a Redission distributed lock corresponding to the target service request; and if not, determining that the Redission distributed lock corresponding to the target service request is not obtained.
In one embodiment, the idempotent function Zookeeper is based on a Zookeeper distributed lock; according to the idempotent function, judging whether to obtain a lock corresponding to the target service request, comprising the following steps: performing md5 information abstract algorithm calculation on the designated service parameters in the target service request, wherein the designated service parameters can be a method name and a request parameter name to obtain a target identification key; judging whether a lock corresponding to the target identification key exists according to zkClient. If so, determining to obtain a Zookeeper distributed lock corresponding to the target service request; and if not, determining that the lock Zookeeper distributed lock corresponding to the target service request is not obtained.
The following is an embodiment of the apparatus, which may be used to execute the embodiment of the service processing method described in this application. For details that are not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the service processing method of the present application.
Fig. 4 is a block diagram of a service processing apparatus according to an embodiment of the present application. As shown in fig. 4, the apparatus includes a request obtaining module 410, a determining module 420, a business logic executing module 430, and an exception information returning module 440.
A request obtaining module 410, configured to obtain a target service request;
a determining module 420, configured to determine an idempotent function corresponding to the target service request, and determine whether to obtain a lock corresponding to the target service request according to the idempotent function;
a service logic executing module 430, configured to, if yes, execute a service logic corresponding to the target service request;
and an exception information returning module 440, configured to return exception information if the determination result is negative.
The implementation process of the functions and actions of each module in the device is specifically described in the implementation process of the corresponding step in the service processing method, and is not described herein again.
In the embodiments provided in the present application, the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules 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 application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 application. 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.
Claims (10)
1. A method for processing a service, the method comprising:
acquiring a target service request;
determining an idempotent function corresponding to the target service request, and judging whether to acquire a lock corresponding to the target service request according to the idempotent function;
if yes, executing a service logic corresponding to the target service request;
if not, returning abnormal information.
2. The method of claim 1, wherein the idempotent function is based on a Mysql optimistic lock;
the determining whether to obtain the lock corresponding to the target service request according to the idempotent function includes:
creating a table structure comprising a primary key id and a lock name;
performing md5 information abstract algorithm calculation on the designated service parameters in the target service request to obtain a target identifier;
searching whether a lock record table item corresponding to the target identifier exists in the created lock record table structure; if so, determining that the lock corresponding to the target service request is not obtained;
if not, determining to obtain the lock corresponding to the target service request, and creating a lock record table entry corresponding to the target identifier.
3. The method of claim 1, wherein the idempotent function is based on a Redission distributed lock;
the determining whether to obtain the lock corresponding to the target service request according to the idempotent function includes:
performing md5 information abstract algorithm calculation on the designated service parameters in the target service request to obtain a target identifier;
judging whether a lock corresponding to the target identifier exists according to an interface of a try lock in the Redission;
if yes, determining to obtain a lock corresponding to the target service request;
if not, determining that the lock corresponding to the target service request is not obtained.
4. The method of claim 1, wherein the idempotent function is based on a Zookeeper distributed lock;
the determining whether to obtain the lock corresponding to the target service request according to the idempotent function includes:
performing md5 information abstract algorithm calculation on the designated service parameters in the target service request to obtain a target identifier;
judging whether a lock corresponding to the target identifier exists according to an acquire interface in the Zookeeper;
if yes, determining to obtain a lock corresponding to the target service request;
if not, determining that the lock corresponding to the target service request is not obtained.
5. The method of claim 1, wherein determining the idempotent function corresponding to the target service request comprises:
and determining the idempotent function according to annotation configuration information corresponding to the target service request.
6. The method of claim 5, wherein the annotation configuration information comprises a switch of an extension component;
before the obtaining the target service request, the method further includes:
instantiating the extension component through a spring framework to obtain the extension component of the idempotent function annotation.
7. The method of claim 6, wherein prior to said instantiating the extension component via a spring framework, the method further comprises:
loading a component resource package of the extension component from a specified resource path of the spring framework;
and injecting configuration class information corresponding to the extension component.
8. A traffic processing apparatus, comprising:
the request acquisition module is used for acquiring a target service request;
the judging module is used for determining an idempotent function corresponding to the target service request and judging whether to acquire a lock corresponding to the target service request according to the idempotent function;
the service logic execution module is used for executing the service logic corresponding to the target service request if the service logic is the target service request;
and the abnormal information returning module is used for returning the abnormal information if the abnormal information is not returned.
9. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the traffic processing method of any of claims 1-7.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program executable by a processor to perform the service processing method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111564288.1A CN114398631A (en) | 2021-12-20 | 2021-12-20 | Business processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111564288.1A CN114398631A (en) | 2021-12-20 | 2021-12-20 | Business processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114398631A true CN114398631A (en) | 2022-04-26 |
Family
ID=81227336
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111564288.1A Pending CN114398631A (en) | 2021-12-20 | 2021-12-20 | Business processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114398631A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115098528A (en) * | 2022-06-24 | 2022-09-23 | 中电金信软件有限公司 | Service processing method and device, electronic equipment and computer readable storage medium |
| CN116594598A (en) * | 2023-06-30 | 2023-08-15 | 北京新里程叮铃科技有限公司 | Information interaction method and device of service system |
-
2021
- 2021-12-20 CN CN202111564288.1A patent/CN114398631A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115098528A (en) * | 2022-06-24 | 2022-09-23 | 中电金信软件有限公司 | Service processing method and device, electronic equipment and computer readable storage medium |
| CN116594598A (en) * | 2023-06-30 | 2023-08-15 | 北京新里程叮铃科技有限公司 | Information interaction method and device of service system |
| CN116594598B (en) * | 2023-06-30 | 2023-09-29 | 北京新里程叮铃科技有限公司 | Information interaction method and device of service system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108810006B (en) | Resource access method, device, equipment and storage medium | |
| US7930760B2 (en) | Centralized enforcement of name-based computer system security rules | |
| CN108427731B (en) | Page code processing method and device, terminal equipment and medium | |
| CN111143087B (en) | Interface calling method, device, storage medium and server | |
| CN114398631A (en) | Business processing method and device, electronic equipment and storage medium | |
| US9954880B2 (en) | Protection via webpage manipulation | |
| JP2017526253A (en) | Method and system for facilitating terminal identifiers | |
| CN112819617B (en) | Data uplink method and device, electronic equipment and storage medium | |
| CN113220717B (en) | Block chain-based data verification method and device and electronic equipment | |
| KR102242219B1 (en) | Method and device for preventing the server from being attacked | |
| CN108470126B (en) | Data processing method, device and storage medium | |
| CN111930363B (en) | Block interface code generation method and device | |
| CN112015563A (en) | Message queue switching method and device, electronic equipment and storage medium | |
| CN113569291B (en) | Log mask method and device | |
| CN109783156B (en) | Application starting control method and device | |
| US11349926B1 (en) | Protected smart contracts for managing internet of things devices | |
| CN109145220B (en) | Data processing method and device and electronic equipment | |
| CN110086637B (en) | Information personalized setting method, device, equipment and storage medium | |
| CN117828672B (en) | Fine-grained dynamic authorized access control and high concurrency processing method and device | |
| CN114978691B (en) | Camouflage method, device and medium for honeypot | |
| CN113934453B (en) | Risk detection method, risk detection device and storage medium | |
| CN112560112B (en) | Block chain based information shielding method, device, equipment and readable storage medium | |
| CN113296832A (en) | Data processing method and device and electronic equipment | |
| CN115567595A (en) | Information processing method, information processing device, computer equipment and storage medium | |
| CN115242625A (en) | Service deployment method and device, computer equipment and readable storage medium |
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 |