CN115277047A - Message desensitization method, system and storage medium based on Spring Cloud Gateway - Google Patents
Message desensitization method, system and storage medium based on Spring Cloud Gateway Download PDFInfo
- Publication number
- CN115277047A CN115277047A CN202210606737.2A CN202210606737A CN115277047A CN 115277047 A CN115277047 A CN 115277047A CN 202210606737 A CN202210606737 A CN 202210606737A CN 115277047 A CN115277047 A CN 115277047A
- Authority
- CN
- China
- Prior art keywords
- message
- desensitization
- request
- cloud gateway
- client
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a message desensitization method, a system and a storage medium based on Spring Cloud Gateway, comprising the following steps: s1, receiving a request sent by a client through a Spring Cloud Gateway; s2, identifying the received request, and judging whether desensitization processing needs to be carried out on the message; if yes, executing the next step, otherwise, ending the process; and S3, desensitizing the message according to pre-stored desensitization configuration to obtain the desensitized message. Compared with the prior art, the technical scheme has the beneficial effects that: after receiving the request through the Spring Cloud Gateway, judging whether desensitization processing needs to be carried out on the message or not by identifying the received request, desensitizing the message according to pre-stored desensitization configuration, and realizing efficient and ordered desensitization by uniformly processing and uniformly configuring.
Description
Technical Field
The invention relates to the field of service Gateway data processing, relates to a message desensitization technology, and particularly relates to a message desensitization method, a system and a storage medium based on Spring Cloud Gateway.
Background
The Spring Cloud framework can convert a single system framework into a distributed micro-service framework, an original heavy single system is split into a plurality of micro-services according to the service field or the service direction, and each micro-service is only responsible for a specific service field and provides an access interface for the outside. The split micro-services are generally more, and a gateway is required to provide a uniform external access entrance from the perspective of security and service management. The Spring Cloud Gateway is taken as a member in the Spring Cloud system, and provides an efficient service access entry and route management mode for the micro-service architecture.
In some actual service scenarios, the writing and reading of the client may include some sensitive data, such as a mobile phone number, an identification card number, a bank card number, and the like, and in order to ensure information security, desensitization processing needs to be performed when relevant information is accessed. Under the micro-service architecture, the interface design of each micro-service is different, the field names which need desensitization are also different, and differentiation requirements can be met for whether different operation roles are desensitized or not. Therefore, the problem of non-uniformity of desensitization process, standard and rule can occur in a micro-service system, each micro-service needing desensitization additionally introduces roles and authorities, and even carries out additional desensitization processing according to interface design, so that the implementation process is relatively disordered. There is a need in the art to provide a desensitization scheme that enables uniform processing and uniform configuration based on Spring Cloud Gateway.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method, a system and a storage medium for desensitizing messages based on a Spring Cloud Gateway, which can perform unified processing and unified configuration on related messages based on the Spring Cloud Gateway, thereby achieving efficient and orderly desensitization.
The technical scheme adopted by the invention for solving the technical problem is as follows:
a message desensitization method based on Spring Cloud Gateway comprises the following steps:
s1, receiving a request sent by a client through a Spring Cloud Gateway;
s2, identifying the received request, and judging whether desensitization processing needs to be carried out on the message or not; if yes, executing the next step, otherwise, ending the process;
and S3, desensitizing the message according to pre-stored desensitization configuration to obtain the desensitized message.
Compared with the prior art, the technical scheme has the beneficial effects that: after receiving the request through the Spring Cloud Gateway, judging whether desensitization processing needs to be carried out on the message or not by identifying the received request, desensitizing the message according to pre-stored desensitization configuration, and realizing efficient and ordered desensitization by uniformly processing and uniformly configuring.
Further, in step S2, identifying the received request specifically includes: acquiring login information of a client, a request address and a message body; the step of judging whether the desensitization treatment is required to be carried out specifically comprises the following steps: judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration;
the step S2 specifically comprises the following steps: acquiring client login information, a request address and a message body, and judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration by combining the client login information, the request address and the message body; if yes, executing the next step, otherwise, ending the process.
The beneficial effect who adopts above-mentioned scheme is: the client login information, the request address, the message body and other information recorded in the request are combined with the pre-stored desensitization configuration for judgment, and the differentiation requirement is met.
Further, in step S2, if it is determined that desensitization processing is required to be performed on the packet, the type of the packet requiring desensitization is further determined according to the client login information, the request address, and the packet body, where the packet type includes a request data packet and a response data packet.
The beneficial effect who adopts above-mentioned scheme is: and judging the message type needing desensitization as a request data message or a response data message according to the client login information, the request address and the message body, so that the message is convenient to store or output.
Further, when the type of the message requiring desensitization is a request data message, the method specifically includes:
receiving a request sent by a client through a Spring Cloud Gateway;
acquiring client login information, a request address and a message body;
and reconstructing the request data message according to the prestored desensitization configuration, and storing the reconstructed request data message into the microserver after the Spring Cloud Gateway.
The beneficial effect who adopts above-mentioned scheme is: the stored message can be desensitized according to the information such as the client login information, the request address, the message body and the like in the request, and the reconstructed request data message is stored in the micro-service side after the Spring Cloud Gateway.
Further, when the type of the message requiring desensitization is a response data message, the method specifically includes:
receiving a request sent by a client through a Spring Cloud Gateway;
acquiring client login information, a request address and a message body;
and reconstructing the response data message according to the pre-stored desensitization configuration, and returning the reconstructed response data message to the client sending the request to the Spring Cloud Gateway.
The beneficial effect who adopts above-mentioned scheme is: the output message can be desensitized according to the information such as the client login information, the request address, the message body and the like in the request, and the reconstructed response data message is returned to the client sending the request to the Spring Cloud Gateway.
A Spring Cloud Gateway based message desensitization system, comprising:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for identifying the received request and judging whether desensitization processing needs to be carried out on the message or not; if yes, executing the next step, otherwise, ending the process;
and the desensitization execution module is used for desensitizing the message according to the pre-stored desensitization configuration to obtain the desensitized message.
Compared with the prior art, the technical scheme has the beneficial effects that: after receiving the request through the Spring Cloud Gateway, judging whether desensitization processing needs to be carried out on the message or not by identifying the received request, desensitizing the message according to pre-stored desensitization configuration, and realizing efficient and ordered desensitization by uniformly processing and uniformly configuring.
Further, in the request identification module, identifying the received request specifically includes: acquiring client login information, a request address and a message body; the step of judging whether desensitization treatment is needed specifically comprises the following steps: judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration;
the request identification module is specifically configured to: acquiring client login information, a request address and a message body, and judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration by combining the client login information, the request address and the message body; if yes, executing the next step, otherwise, ending the process.
The beneficial effect who adopts above-mentioned scheme is: and judging by combining the pre-stored desensitization configuration through the client login information, the request address, the message body and other information recorded in the request, so that the differentiation requirement is met.
Further, when the request identification module judges that desensitization processing needs to be performed on the message, the type of the message needing desensitization is further judged according to the client login information, the request address and the message body, wherein the message type comprises a request data message and a response data message.
The beneficial effect who adopts above-mentioned scheme is: and judging the message type needing desensitization as a request data message or a response data message according to the client login information, the request address and the message body, so that the message is convenient to store or output.
Further, when the request identification module judges that the message type needing desensitization is a request data message:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for acquiring login information of a client, a request address and a message body;
the desensitization execution module is used for reconstructing the request data message according to pre-stored desensitization configuration and storing the reconstructed request data message into the micro-service end behind the Spring Cloud Gateway;
when the request identification module judges that the message type needing desensitization is a response data message:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for acquiring the login information of the client, the request address and the message body;
the desensitization execution module is used for reconstructing the response data message according to the pre-stored desensitization configuration and returning the reconstructed response data message to the client side which sends the request to the Spring Cloud Gateway.
The beneficial effect who adopts above-mentioned scheme is: the method can desensitize the stored or output message according to the client login information, request address, message body and other information in the request, store the reconstructed request data message into the micro-service terminal after the Spring Cloud Gateway, or return the reconstructed response data message to the client sending the request to the Spring Cloud Gateway.
A storage medium containing computer executable instructions which, when executed by a computer processor, are configured to perform any of the above-described Spring Cloud Gateway based message desensitization methods.
Drawings
FIG. 1 is a flow chart of the message desensitization method based on the Spring Cloud Gateway of the present invention.
FIG. 2 is a schematic block diagram of a message desensitization system based on Spring Cloud Gateway according to the present invention.
FIG. 3 is an architecture diagram of the Spring Cloud Gateway based message desensitization system of the present invention.
In the figures, the list of components represented by the various reference numbers is as follows:
the system comprises a request receiving module 1, a request identification module 2, a desensitization execution module 3, a Spring Cloud Gateway4, a client 5 and a micro server 6.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the description of the present invention, it is to be understood that the terms "center", "upper", "lower", "front", "rear", "left", "right", and the like, indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience in describing the present invention and simplifying the description, but do not indicate or imply that the device or assembly referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; the two components can be directly connected or indirectly connected through an intermediate medium, and the two components can be communicated with each other. When an element is referred to as being "secured to" or "disposed on" another element, it can be directly on the other element or intervening elements may also be present. When a component is referred to as being "connected" to another element, it can be directly connected to the other element or intervening elements may also be present. The specific meaning of the above terms in the present invention can be understood in specific cases to those skilled in the art.
The Spring Cloud framework can convert a single system framework into a distributed micro-service framework, an original heavy single system is split into a plurality of micro-services according to the service field or the service direction, and each micro-service is only responsible for a specific service field and provides an access interface for the outside. The split micro-services are generally more, and a gateway is required to provide a uniform external access entrance from the perspective of security and service management. The Spring Cloud Gateway is used as a member in the Spring Cloud system, and provides an efficient service access entry and route management mode for the micro-service architecture.
In some actual service scenarios, the writing and reading of the client may include some sensitive data, such as a mobile phone number, an identification card number, a bank card number, and the like, and in order to ensure information security, desensitization processing needs to be performed when relevant information is accessed. Under the micro-service architecture, the interface design of each micro-service is different, the field names which need desensitization are also different, and differentiation requirements can be met for whether different operation roles are desensitized or not. Therefore, the problem of non-uniform desensitization process, standard and rule can occur under a micro-service system, each micro-service needing desensitization additionally introduces roles and authorities, and even carries out additional desensitization processing according to interface design, so that the implementation process is disordered. There is a need in the art to provide a desensitization scheme that enables uniform processing and uniform configuration based on Spring Cloud Gateway.
In order to provide a new solution, facilitate the unified processing and the unified configuration of the related messages based on the Spring Cloud Gateway, and realize the efficient and orderly desensitization, the invention provides a message desensitization method, a system and a storage medium based on the Spring Cloud Gateway.
As shown in fig. 1, a message desensitization method based on Spring Cloud Gateway includes the following steps:
s1, receiving a request sent by a client through a Spring Cloud Gateway. When a client makes a request, the system receives the request through the Spring Cloud Gateway.
S2, identifying the received request, and judging whether desensitization processing needs to be carried out on the message or not; if yes, executing the next step, otherwise, ending the process. The request sent by the client contains specific data, and after the system identifies the data, the system further judges whether desensitization processing needs to be carried out on the message. If the message needs to be desensitized, the step S3 is continuously executed, otherwise, the message is directly stored or output. Different clients and different requests correspond to different security authorities. Some need desensitization, some do not need, and this technical scheme realizes unified differentiation processing through step S3.
And S3, desensitizing the message according to the pre-stored desensitization configuration to obtain the desensitized message. Desensitization configuration is stored in the system in advance, the desensitization configuration defines desensitization modes, desensitization logics and the like corresponding to different requests, the corresponding desensitization modes and desensitization logics can be determined only by combining the desensitization configuration for analysis according to the requests, and desensitization can be performed on the messages on the basis of the desensitization modes and the desensitization logics to obtain the desensitized messages.
Based on the technical scheme, after the request is received through the Spring Cloud Gateway, whether the desensitization processing needs to be carried out on the message is judged through identifying the received request, the message is desensitized according to the pre-stored desensitization configuration, and the efficient and ordered desensitization is realized through unified configuration processing.
Preferably, in step S2, identifying the received request specifically includes: acquiring client login information, a request address and a message body; the step of judging whether desensitization treatment is needed specifically comprises the following steps: and judging whether desensitization processing needs to be carried out on the message according to the prestored desensitization configuration. Correspondingly, step S2 specifically includes: acquiring client login information, a request address and a message body, and judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration by combining the client login information, the request address and the message body; if yes, executing the next step, otherwise, ending the process.
Based on the technical scheme, the client login information, the request address, the message body and other information recorded in the request are combined with the pre-stored desensitization configuration for judgment, and the differentiation requirement is met.
Preferably, in step S2, if it is determined that desensitization processing is required to be performed on the packet, the type of the packet requiring desensitization is further determined according to the client login information, the request address, and the packet body, where the packet type includes a request data packet and a response data packet.
Referring to fig. 3, in the network consisting of the Spring Cloud Gateway4, the request data packet corresponds to the packet stored in the micro server 6 from the client 5, and the response data packet corresponds to the packet output from the micro server 6 from the client 5. The system carries out information interaction through the Spring Cloud Gateway4, judges the type of the message needing desensitization according to the login information of the client, the request address and the message body, and is convenient for storing or outputting the message.
Specifically, a message desensitization method based on Spring Cloud Gateway, when a message type requiring desensitization is a request data message, the method specifically includes:
receiving a request sent by a client through a Spring Cloud Gateway;
acquiring client login information, a request address and a message body;
and reconstructing the request data message according to the pre-stored desensitization configuration, and storing the reconstructed request data message into the micro-service terminal behind the Spring Cloud Gateway.
Based on the scheme, the stored message can be desensitized according to the client login information, the request address, the message body and other information in the request, and the reconstructed request data message is stored in the microserver after Spring Cloud Gateway.
Specifically, when the type of the message requiring desensitization is a response data message, the method specifically includes:
receiving a request sent by a client through a Spring Cloud Gateway;
acquiring client login information, a request address and a message body;
and reconstructing the response data message according to the pre-stored desensitization configuration, and returning the reconstructed response data message to the client sending the request to the Spring Cloud Gateway.
Based on the scheme, the output message can be desensitized according to the information such as the client login information, the request address, the message body and the like in the request, and the reconstructed response data message is returned to the client sending the request to the Spring Cloud Gateway.
As shown in fig. 2, correspondingly, a message desensitization system based on Spring Cloud Gateway includes a request receiving module, a request identifying module and a desensitization executing module.
The request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway; the request identification module is used for identifying the received request and judging whether desensitization processing needs to be carried out on the message or not; if yes, executing the next step, otherwise, ending the process; the desensitization execution module is used for desensitizing the message according to the pre-stored desensitization configuration to obtain the desensitized message.
Preferably, in the request identifying module, identifying the received request specifically includes: acquiring login information of a client, a request address and a message body; the step of judging whether the desensitization treatment is required to be carried out specifically comprises the following steps: and judging whether desensitization processing needs to be carried out on the message according to the prestored desensitization configuration. Specifically, the request identification module is specifically configured to: acquiring client login information, a request address and a message body, and judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration by combining the client login information, the request address and the message body; if yes, executing the next step, otherwise, ending the process.
Preferably, when the request identification module determines that desensitization processing needs to be performed on the message, the type of the message needing desensitization is further determined according to the client login information, the request address and the message body, where the message type includes a request data message and a response data message.
Specifically, when the request identification module determines that the message type requiring desensitization is a request data message:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for acquiring the login information of the client, the request address and the message body;
the desensitization execution module is used for reconstructing the request data message according to the pre-stored desensitization configuration and storing the reconstructed request data message into the micro service end behind the Spring Cloud Gateway.
Specifically, when the request identification module determines that the message type requiring desensitization is a response data message:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for acquiring login information of a client, a request address and a message body;
the desensitization execution module is used for reconstructing the response data message according to the pre-stored desensitization configuration and returning the reconstructed response data message to the client side which sends the request to the Spring Cloud Gateway.
Correspondingly, the technical solution also includes a storage medium, where the storage medium contains computer-executable instructions, and the computer-executable instructions are used for executing the method for desensitizing the message based on the Spring Cloud Gateway as described above when executed by a computer processor.
It will be understood that the invention is not limited to the examples described above, but that modifications and variations will occur to those skilled in the art in light of the above teachings, and that all such modifications and variations are considered to be within the scope of the invention as defined by the appended claims.
Claims (10)
1. A message desensitization method based on Spring Cloud Gateway is characterized by comprising the following steps:
s1, receiving a request sent by a client through a Spring Cloud Gateway;
s2, identifying the received request, and judging whether desensitization processing needs to be carried out on the message or not; if yes, executing the next step, otherwise, ending the process;
and S3, desensitizing the message according to the pre-stored desensitization configuration to obtain the desensitized message.
2. The message desensitization method based on Spring Cloud Gateway according to claim 1, wherein in step S2, the identifying the received request specifically includes: acquiring login information of a client, a request address and a message body; the step of judging whether the desensitization treatment is required to be carried out specifically comprises the following steps: judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration;
the step S2 specifically comprises the following steps: acquiring client login information, a request address and a message body, and judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration by combining the client login information, the request address and the message body; if yes, executing the next step, otherwise, ending the process.
3. The message desensitization method based on the Spring Cloud Gateway of claim 2, wherein in step S2, if it is determined that the message needs to be desensitized, the message type needing to be desensitized is further determined according to the client login information, the request address and the message body, where the message type includes a request data message and a response data message.
4. The message desensitization method based on the Spring Cloud Gateway according to claim 3, wherein when the message type requiring desensitization is a request data message, the method specifically comprises:
receiving a request sent by a client through a Spring Cloud Gateway;
acquiring client login information, a request address and a message body;
and reconstructing the request data message according to the prestored desensitization configuration, and storing the reconstructed request data message into the microserver after the Spring Cloud Gateway.
5. The message desensitization method based on the Spring Cloud Gateway according to claim 3, wherein when the message type requiring desensitization is a response data message, the method specifically comprises:
receiving a request sent by a client through a Spring Cloud Gateway;
acquiring login information of a client, a request address and a message body;
and reconstructing the response data message according to the pre-stored desensitization configuration, and returning the reconstructed response data message to the client sending the request to the Spring Cloud Gateway.
6. A message desensitization system based on Spring Cloud Gateway, comprising:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for identifying the received request and judging whether desensitization processing needs to be carried out on the message or not; if yes, executing the next step, otherwise, ending the process;
and the desensitization execution module is used for desensitizing the message according to the pre-stored desensitization configuration to obtain the desensitized message.
7. The message desensitization system based on Spring Cloud Gateway of claim 6, wherein in the request identification module, identifying the received request specifically comprises: acquiring client login information, a request address and a message body; the step of judging whether the desensitization treatment is required to be carried out specifically comprises the following steps: judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration;
the request identification module is specifically configured to: acquiring client login information, a request address and a message body, and judging whether desensitization processing needs to be carried out on the message according to pre-stored desensitization configuration by combining the client login information, the request address and the message body; if yes, executing the next step, otherwise, ending the process.
8. The message desensitization system based on the Spring Cloud Gateway of claim 7, wherein when the request identification module determines that the message needs to be desensitized, the message type that needs to be desensitized is further determined according to the client login information, the request address and the message body, and the message type includes a request data message and a response data message.
9. The message desensitization system based on Spring Cloud Gateway of claim 8, wherein when the request identification module determines that the message type requiring desensitization is a request data message:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for acquiring login information of a client, a request address and a message body;
the desensitization execution module is used for reconstructing the request data message according to the pre-stored desensitization configuration and storing the reconstructed request data message into the micro service end behind the Spring Cloud Gateway;
when the request identification module judges that the message type needing desensitization is a response data message:
the request receiving module is used for receiving a request sent by a client through a Spring Cloud Gateway;
the request identification module is used for acquiring the login information of the client, the request address and the message body;
the desensitization execution module is used for reconstructing the response data message according to the pre-stored desensitization configuration and returning the reconstructed response data message to the client side which sends the request to the Spring Cloud Gateway.
10. A storage medium containing computer-executable instructions for performing the Spring Cloud Gateway based message desensitization method of any of claims 1-5 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210606737.2A CN115277047A (en) | 2022-05-31 | 2022-05-31 | Message desensitization method, system and storage medium based on Spring Cloud Gateway |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210606737.2A CN115277047A (en) | 2022-05-31 | 2022-05-31 | Message desensitization method, system and storage medium based on Spring Cloud Gateway |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115277047A true CN115277047A (en) | 2022-11-01 |
Family
ID=83758988
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210606737.2A Pending CN115277047A (en) | 2022-05-31 | 2022-05-31 | Message desensitization method, system and storage medium based on Spring Cloud Gateway |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115277047A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106611129A (en) * | 2016-12-27 | 2017-05-03 | 东华互联宜家数据服务有限公司 | Data desensitization method, device and system |
| CN109981619A (en) * | 2019-03-13 | 2019-07-05 | 泰康保险集团股份有限公司 | Data capture method, device, medium and electronic equipment |
| CN111488604A (en) * | 2020-04-07 | 2020-08-04 | 杭州迪普科技股份有限公司 | Data desensitization system and data desensitization method |
| WO2020211222A1 (en) * | 2019-04-15 | 2020-10-22 | 厦门市美亚柏科信息股份有限公司 | Method and device for providing micro-service based on data service platform, and storage medium |
| CN113360947A (en) * | 2021-06-30 | 2021-09-07 | 杭州网易再顾科技有限公司 | Data desensitization method and device, computer readable storage medium and electronic equipment |
| CN113407421A (en) * | 2021-08-19 | 2021-09-17 | 北京江融信科技有限公司 | Dynamic log record management method and system for micro-service gateway |
| CN113407997A (en) * | 2021-06-30 | 2021-09-17 | 平安国际智慧城市科技股份有限公司 | Data desensitization method and device, computer equipment and storage medium |
| CN114254389A (en) * | 2021-12-20 | 2022-03-29 | 中国工商银行股份有限公司 | Message desensitization method, device, electronic equipment and medium |
-
2022
- 2022-05-31 CN CN202210606737.2A patent/CN115277047A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106611129A (en) * | 2016-12-27 | 2017-05-03 | 东华互联宜家数据服务有限公司 | Data desensitization method, device and system |
| CN109981619A (en) * | 2019-03-13 | 2019-07-05 | 泰康保险集团股份有限公司 | Data capture method, device, medium and electronic equipment |
| WO2020211222A1 (en) * | 2019-04-15 | 2020-10-22 | 厦门市美亚柏科信息股份有限公司 | Method and device for providing micro-service based on data service platform, and storage medium |
| CN111488604A (en) * | 2020-04-07 | 2020-08-04 | 杭州迪普科技股份有限公司 | Data desensitization system and data desensitization method |
| CN113360947A (en) * | 2021-06-30 | 2021-09-07 | 杭州网易再顾科技有限公司 | Data desensitization method and device, computer readable storage medium and electronic equipment |
| CN113407997A (en) * | 2021-06-30 | 2021-09-17 | 平安国际智慧城市科技股份有限公司 | Data desensitization method and device, computer equipment and storage medium |
| CN113407421A (en) * | 2021-08-19 | 2021-09-17 | 北京江融信科技有限公司 | Dynamic log record management method and system for micro-service gateway |
| CN114254389A (en) * | 2021-12-20 | 2022-03-29 | 中国工商银行股份有限公司 | Message desensitization method, device, electronic equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111371892A (en) | High-concurrency distributed message pushing system and method | |
| CN109639782B (en) | Message sending platform and method | |
| CN102377617A (en) | Systems, methods, and apparatus to monitor and authenticate mobile internet activity | |
| US20200344352A1 (en) | Communication methods | |
| US8467815B2 (en) | Mobile address book population using SMS polling | |
| CN112543431A (en) | Account synchronization method, medium and server | |
| EP2442487A1 (en) | Location processing method address duplication processing method and device | |
| CN106357654B (en) | Remote procedure calling method, device and communication system | |
| CN110336592A (en) | It is applicable in the data transmission method and electronic equipment of Bluetooth card reader | |
| CN115277047A (en) | Message desensitization method, system and storage medium based on Spring Cloud Gateway | |
| CN112181337A (en) | Customer service consultation method, system and storage medium | |
| CN111698287A (en) | Cloud mobile phone active application acquisition method, system and storage medium | |
| CN113114642B (en) | Interface integrated driver identity authentication method and device | |
| CN112104747B (en) | Request response system based on chain processing | |
| CN112866268B (en) | Message processing method and system | |
| CN111935316B (en) | Method and device for acquiring front-end equipment catalog | |
| CN113452793A (en) | Diagnostic service processing method and device, vehicle-mounted terminal and medium | |
| CN111523872A (en) | Transaction processing method and device, mobile terminal and computer readable storage medium | |
| CN108965431B (en) | Method and device for realizing event-driven architecture by IBM (International Business machines corporation) host | |
| CN111552907A (en) | Message processing method, device, equipment and storage medium | |
| CN112003867A (en) | Communication method of vehicle-mounted T-BOX and cloud server and related equipment | |
| CN111752625A (en) | Method and device for interface mock | |
| CN114265557B (en) | Pollutant emission data processing method and device | |
| CN116760852A (en) | Information processing method, device and system and electronic equipment | |
| FR3057085A1 (en) | CONTROL OF DELEGATION OF RIGHTS |
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 |