CN113709177B - Method for processing message and external call gateway - Google Patents
Method for processing message and external call gateway Download PDFInfo
- Publication number
- CN113709177B CN113709177B CN202111039350.5A CN202111039350A CN113709177B CN 113709177 B CN113709177 B CN 113709177B CN 202111039350 A CN202111039350 A CN 202111039350A CN 113709177 B CN113709177 B CN 113709177B
- Authority
- CN
- China
- Prior art keywords
- message
- request
- processed
- format
- callout
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Abstract
The invention discloses a method for processing a message and an external call gateway, which can be applied to the field of mobile interconnection. Receiving a first calling request which is sent by an internal system and used for calling an external system, wherein the request type of the first calling request is any one of a plurality of preset request types, and the message format of a message to be processed is any one of a plurality of preset message formats; analyzing the message to be processed into a map object according to the message format of the message to be processed; acquiring a request parameter corresponding to a message to be processed from a map object; determining the message format of the callout message according to the request parameters; generating an external call message by using the request parameters, the message format of the external call message and the message to be processed; and sending the second calling request carrying the calling message to an external system according to a preset request routing rule. When the external system changes, the related content of the business service of the internal system does not need to be changed, so that the cost is reduced and the operation stability of the business service is ensured.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method for processing a message and an external call gateway.
Background
Currently, when a business service of an internal system calls an external system, the business service defines a relevant calling rule by itself to complete the calling of the external system. However, when the external system changes, each business service related to the changed external system needs to be modified at the same time, which consumes large manpower and material resources, is high in cost, and the external system cannot be called due to the fact that the calling rule of the business service cannot be adjusted in real time, so that the operation stability of the business service is affected.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method for processing a packet and an callout gateway, so as to solve the problems that the current manner in which an internal system calls an external system is high in cost and easy to affect the operation stability of a service.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
a first aspect of an embodiment of the present invention discloses a method for processing a packet, where the method includes:
receiving a first calling request which is sent by an internal system and used for calling an external system, wherein the first calling request at least carries a message to be processed, the request type of the first calling request is any one of a plurality of preset request types, and the message format of the message to be processed is any one of a plurality of preset message formats;
analyzing the message to be processed into a map object according to the message format of the message to be processed;
acquiring a request parameter corresponding to the message to be processed from the map object;
determining the message format of the callout message according to the request parameters;
generating the callout message by using the request parameter, the message format of the callout message and the message to be processed;
and sending a second calling request carrying the calling message to the external system according to a preset request routing rule, wherein the request routing rule at least configures the request type of the calling request which can be received by the external system.
Preferably, the generating the callout message by using the request parameter, the message format of the callout message, and the message to be processed includes:
acquiring target information from the message to be processed and acquiring a target field from the request parameter;
determining a preset message template matched with the target field;
and generating the callout message according to the message template and the message format of the callout message, and writing the target information into the callout message.
Preferably, the parsing the message to be processed into a map object according to the message format of the message to be processed includes:
and analyzing the message to be processed by utilizing a message analyzer corresponding to the message format of the message to be processed to obtain a map object.
Preferably, the plurality of preset request types at least include: http requests, dubbo requests and socket requests.
Preferably, the plurality of preset message formats at least include: json format, xml format, and fixed length format.
A second aspect of the embodiments of the present invention discloses an outbound gateway, including:
an access module to: receiving a first calling request which is sent by an internal system and used for calling an external system, wherein the first calling request at least carries a message to be processed; analyzing the message to be processed into a map object according to the message format of the message to be processed; acquiring a request parameter corresponding to the message to be processed from the map object; the request type of the first call request is any one of a plurality of preset request types, and the message format of the message to be processed is any one of a plurality of preset message formats;
the parameter analysis module is used for determining the message format of the callout message according to the request parameter;
the message generating module is used for generating the callout message by utilizing the request parameter, the message format of the callout message and the message to be processed;
and the request routing module is used for sending a second calling request carrying the callout message to the external system according to a preset request routing rule, wherein the request routing rule at least configures the request type of the calling request which can be received by the external system.
Preferably, the message generating module includes:
an obtaining unit, configured to obtain target information from the to-be-processed packet, and obtain a target field from the request parameter;
the determining unit is used for determining a preset message template matched with the target field;
and the generating unit is used for generating the callout message according to the message template and the message format of the callout message and writing the target information into the callout message.
Preferably, the access module, configured to parse the message to be processed into a map object, is specifically configured to: and analyzing the message to be processed by utilizing a message analyzer corresponding to the message format of the message to be processed to obtain a map object.
Preferably, the plurality of preset request types at least include: http requests, dubbo requests and socket requests.
Preferably, the plurality of preset message formats at least include: json format, xml format, and fixed length format.
Based on the method for processing a message and the callout gateway provided by the embodiment of the present invention, a first call request sent by an internal system for calling an external system is received, where a request type of the first call request is any one of a plurality of preset request types, and a message format of a message to be processed is any one of the plurality of preset message formats; analyzing the message to be processed into a map object according to the message format of the message to be processed; acquiring a request parameter corresponding to a message to be processed from a map object; determining the message format of the callout message according to the request parameters; generating an external call message by using the request parameters, the message format of the external call message and the message to be processed; and sending the second calling request carrying the calling message to an external system according to a preset request routing rule. According to the scheme, the calling requests of different request types from the internal system can be received, the message format of the callout message is determined according to the to-be-processed message carried in the calling request of the internal system, the callout message is generated by combining the to-be-processed message, the calling request carrying the callout message is sent to the external system according to the request routing rule, when the external system changes, the related content of the business service of the internal system does not need to be changed, the cost is reduced, and the operation stability of the business service is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for processing a packet according to an embodiment of the present invention;
fig. 2 is a flowchart of generating an callout message according to an embodiment of the present invention;
fig. 3 is a schematic diagram of an execution logic of a method for processing a packet according to an embodiment of the present invention;
fig. 4 is a block diagram of an outbound gateway according to an embodiment of the present invention;
fig. 5 is another structural block diagram of an outbound gateway according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
It should be noted that the method for processing a packet and the callout gateway provided by the present invention can be used in the field of mobile internet. The foregoing is only an example, and does not limit the application fields of the method for processing a packet and the callout gateway provided in the present invention.
As known in the background art, currently, the business service of the internal system mainly completes the call of the external system through a customized call rule. However, when the external system changes, each business service related to the changed external system needs to be modified at the same time, which is relatively high in cost, and the external system cannot be called due to the fact that the calling rule of the business service cannot be adjusted in real time, and the operation stability of the business service is affected.
Therefore, the embodiment of the present invention provides a method for processing a message and an callout gateway, which can receive call requests of different request types from an internal system, determine a message format of the callout message according to a to-be-processed message carried in the call request of the internal system, generate the callout message according to the to-be-processed message, and send the call request carrying the callout message to an external system according to a request routing rule.
Referring to fig. 1, a flowchart of a method for processing a packet according to an embodiment of the present invention is shown, where the method is applied to an outbound gateway, and the method includes:
step S101: receiving a first calling request sent by an internal system and used for calling an external system.
It should be noted that the first invocation request at least carries a to-be-processed message, the request type of the first invocation request is any one of a plurality of preset request types, and the message format of the to-be-processed message is any one of a plurality of preset message formats.
In some embodiments, the plurality of predetermined request types includes at least: http requests, dubbo requests, and socket requests.
In some embodiments, the plurality of predetermined message formats includes at least: json format, xml format, and fixed length format.
In the process of implementing step S101 specifically, a first call request sent by a service of an internal system is received, where the first call request is used to call an external system, and the first call request carries a to-be-processed packet.
It is understood that the first invocation request is an http request, a dubbo request, or a socket request, and specifically, the first invocation request sent by the business service of the internal system may be received through different types of request interfaces, such as: if the first calling request is an http request, receiving the first calling request through an http request interface, if the first calling request is a dubbo request, receiving the first calling request through a dubbo request interface, and if the first calling request is a socket request, receiving the first calling request through a socket request interface; the request interfaces do not interfere with each other.
That is, the service of the internal system may call the external system in an http manner (sending an http request), a dubbo manner (sending a dubbo request), or a socket manner (sending a socket request).
It can be understood that the first invocation request may carry a to-be-processed packet in a plurality of preset packet formats, that is, the packet format of the to-be-processed packet carried by the first invocation request is a json format, an xml format, or a fixed-length format. That is, each of the above-mentioned request interfaces can receive messages in json format, xml format and fixed length format.
Step S102: and analyzing the message to be processed into a map object according to the message format of the message to be processed.
In the process of implementing step S102, the message to be processed is parsed by using the message parser corresponding to the message format of the message to be processed, so as to obtain a map object (also referred to as an internal object). For example: and if the message to be processed is a json message, analyzing the message to be processed by a json message analyzer to obtain a corresponding map object.
It should be noted that the map object is a general program object for the callout gateway, and assuming that the message to be processed is a json message, the form of the map object obtained by analyzing the message to be processed is as follows: { "key1": value1"," key2": value2" }, at this time, the value (value) corresponding to each key may be acquired by means of get.
Step S103: and acquiring a request parameter corresponding to the message to be processed from the map object.
In the process of implementing step S103, a preset parameter parsing rule is used to obtain a request parameter corresponding to the message to be processed from the map object corresponding to the message to be processed. For example: suppose the map object of the message to be processed is: the key1 and the key2 are request parameters, and the values corresponding to the key1 and the key2 can be obtained through a get mode.
Step S104: and determining the message format of the callout message according to the request parameters.
In the process of implementing step S104 specifically, the request parameter is analyzed, and the message format of the callout message is determined according to the analysis result (the value of the request parameter), where the message format of the callout message is json format, xml format, or fixed-length format.
It should be noted that the request parameters corresponding to the message to be processed include information for determining the message format of the callout message, and the message format of the callout message can be determined by analyzing the request parameters. For example: suppose the map object of the message to be processed is: the value of the request parameter is xml which can be obtained by analyzing the request parameter outputFormat, and the message format of the callout message can be determined to be xml format (that is to say, the callout message is xml message).
It should be further noted that, in the foregoing example, the manner of determining the message format of the outgoing message by analyzing the request parameter outputFormat is only one manner of determining the message format of the outgoing message, and in practical applications, the message format of the outgoing message needs to be determined by combining values of multiple request parameters (such as external system identifiers and other information), which is not illustrated here.
Step S105: and generating the callout message by using the request parameters, the message format of the callout message and the message to be processed.
It can be understood that the pending message includes target information to be written into the callout message, for example: the data field (i.e., the target information) exists in the message to be processed, and at this time, the data field needs to be written into the generated callout message.
In the process of implementing step S105 specifically, after the message format of the callout message is determined, the callout message (the message format of which is determined before) is generated by combining the request parameter, the message format of the callout message, and the message to be processed.
For example: and after the message format of the callout message is assumed to be the xml format, generating the callout message (including the target information in the message to be processed) in the xml format by combining the request parameter and the message to be processed.
By the method, the callout message in the xml format, the json format or the fixed length format can be generated, namely the callout message is the xml message, the json message or the fixed length message.
Step S106: and sending the second calling request carrying the calling message to an external system according to a preset request routing rule.
It should be noted that, at least the request type of the invocation request that can be received by the external system is configured in the request routing rule, that is, the request type of the invocation request that can be received by each external system is defined by configuring the content in the request routing rule. When the request type of the call request which can be received by the external system changes, only the request routing rule needs to be modified.
For example: assuming that the invocation request that the external system a can receive is an http request in the request routing rule, after the invocation request that the external system a can receive is switched to a dubbo request, only the relevant content in the request routing rule needs to be modified.
In the process of implementing step S106 specifically, according to a preset request routing rule, a second invocation request carrying an callout message is routed to the external system to invoke the external system, where a request type of the second invocation request is a request type of an invocation request that can be received by the external system.
For example: assuming that the call request that the external system a can receive is an http request, the http request (i.e., the second call request) carrying the outbound message is routed to the external system a.
It should be noted that the second call request is an http request, a dubbo request, or a socket request, where the dubbo request is a generalized call request.
In the embodiment of the invention, the calling requests of different request types from the internal system can be received, the message format of the callout message is determined according to the message to be processed carried in the calling request of the internal system, the callout message is generated by combining the message to be processed according to the message format, the calling request carrying the callout message is sent to the external system according to the request routing rule, when the external system changes, the related content of the business service of the internal system does not need to be changed, the cost is reduced, and the operation stability of the business service is ensured.
Referring to fig. 2, the process of generating an callout message in step S105 in the embodiment of the present invention described above is a flowchart of generating a callout message according to the embodiment of the present invention, and includes the following steps:
step S201: and acquiring target information from the message to be processed and acquiring a target field from the request parameter.
It should be noted that a message generation rule is preset, and the message generation rule includes a message template corresponding to each field.
In the process of implementing step S201 specifically, target information is obtained from the message to be processed, where the target information is information to be written into the callout message, and a target field is obtained from the request parameter corresponding to the message to be processed, where the target field is any one of fields preset in the message generation rule.
Step S202: and determining a preset message template matched with the target field segment.
In the process of implementing step S202 specifically, a preset message template matching the target field is determined according to the message generation rule.
For example: assuming that an external system to be called supports two different transactions, the two different transaction codes are x and y, respectively, a target field of the transaction code is carried in a request parameter corresponding to a message to be processed, and at this time, a message template corresponding to the transaction code x and y can be determined by using a message generation rule.
By the above mode, diversified calling messages can be generated,
step S203: and generating the callout message according to the message template and the message format of the callout message, and writing the target information into the callout message.
In the process of implementing step S203, an callout message is generated according to the determined message template and the message format of the callout message, and the target information is written into the callout message, thereby finally completing the generation of the callout message.
In the embodiment of the invention, the message template can be determined and obtained according to the message generation rule and the request parameter of the message to be processed, the callout message is finally generated according to the message template and the message format of the callout message, and the calling request carrying the callout message is sent to the external system according to the request routing rule. Diversified callouts can be generated through the message generation rule, different requirements are met, related contents of business services of the internal system do not need to be changed when the external system changes, cost is reduced, and operation stability of the business services is guaranteed.
To better explain the contents of the steps in fig. 1 and fig. 2 in the above embodiment of the present invention, an execution logic diagram of a method for processing a packet shown in fig. 3 is used for explanation, and it should be noted that fig. 3 is only used for illustration.
In fig. 3, the callout gateway provides an http request interface, a dubbo request interface, and a socket request interface to the internal system, and can support receiving an http request, a dubbo request, and a socket request sent by the internal system. Through rule configuration, parameter analysis rules, message generation rules and request routing rules are configured in advance. And analyzing the message to be processed into a map object through parameter analysis and determining the message format of the callout message. And generating the callout message in a json format, an xml format or a fixed length format through the message generation rule. According to the request routing rule, when the external system A is called, an http request carrying an callout message is sent to the external system A, when the external system B is called, a dubbo request carrying the callout message is sent to the external system B, and when the external system C is called, a socket request carrying the callout message is sent to the external system C.
Corresponding to the method for processing a packet provided in the foregoing embodiment of the present invention, referring to fig. 4, an embodiment of the present invention further provides a structural block diagram of an outbound gateway, where the outbound gateway includes: an access module 401, a parameter analysis module 402, a message generation module 403 and a request routing module 404;
an access module 401 configured to: receiving a first calling request which is sent by an internal system and used for calling an external system, wherein the first calling request at least carries a message to be processed; analyzing the message to be processed into a map object according to the message format of the message to be processed; acquiring a request parameter corresponding to a message to be processed from a map object; the request type of the first call request is any one of a plurality of preset request types, and the message format of the message to be processed is any one of a plurality of preset message formats.
In a specific implementation, the access module 401 configured to parse a message to be processed into a map object is specifically configured to: and analyzing the message to be processed by using a message analyzer corresponding to the message format of the message to be processed to obtain a map object.
In some embodiments, the plurality of predetermined request types includes at least: http requests, dubbo requests and socket requests.
In some embodiments, the plurality of predetermined message formats includes at least: json format, xml format, and fixed length format.
And a parameter analyzing module 402, configured to determine a message format of the callout message according to the request parameter.
The message generating module 403 is configured to generate an callout message by using the request parameter, the message format of the callout message, and the message to be processed.
The request routing module 404 is configured to send a second invocation request carrying the callout message to the external system according to a preset request routing rule, where the request routing rule at least configures a request type of the invocation request that can be received by the external system.
In the embodiment of the invention, the calling requests of different request types from the internal system can be received, the message format of the callout message is determined according to the message to be processed carried in the calling request of the internal system, the callout message is generated by combining the message to be processed according to the message format, the calling request carrying the callout message is sent to the external system according to the request routing rule, when the external system changes, the related content of the business service of the internal system does not need to be changed, the cost is reduced, and the operation stability of the business service is ensured.
Preferably, referring to fig. 5 in combination with fig. 4, another structural block diagram of an outbound gateway provided in the embodiment of the present invention is shown, where the message generating module 403 includes: an acquisition unit 4031, a determination unit 4032, and a generation unit 4033;
an obtaining unit 4031, configured to obtain target information from the to-be-processed packet and obtain a target field from the request parameter.
A determining unit 4032, configured to determine a preset message template matching the target field.
A generating unit 4033, configured to generate the callout message according to the message template and the message format of the callout message, and write the target information into the callout message.
In the embodiment of the invention, the message template can be determined and obtained according to the message generation rule and the request parameter of the message to be processed, the callout message is finally generated according to the message template and the message format of the callout message, and the calling request carrying the callout message is sent to the external system according to the request routing rule. Diversified callout messages can be generated through the message generation rule, different requirements are met, when an external system changes, the related content of the business service of the internal system does not need to be changed, the cost is reduced, and the operation stability of the business service is ensured.
In summary, embodiments of the present invention provide a method for processing a message and an callout gateway, which can receive call requests of different request types from an internal system, determine a message format of the callout message according to a to-be-processed message carried in the call request of the internal system, generate the callout message according to the to-be-processed message, and send the call request carrying the callout message to an external system according to a request routing rule.
All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, the system or system embodiments, which are substantially similar to the method embodiments, are described in a relatively simple manner, and reference may be made to some descriptions of the method embodiments for relevant points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. A method for processing a packet, the method comprising:
receiving a first calling request which is sent by an internal system and used for calling an external system, wherein the first calling request at least carries a message to be processed, the request type of the first calling request is any one of a plurality of preset request types, and the message format of the message to be processed is any one of a plurality of preset message formats;
analyzing the message to be processed into a map object according to the message format of the message to be processed;
acquiring a request parameter corresponding to the message to be processed from the map object;
determining the message format of the callout message according to the request parameters;
generating the callout message by using the request parameter, the message format of the callout message and the message to be processed;
sending a second calling request carrying the calling message to the external system according to a preset request routing rule, wherein the request routing rule at least configures the request type of the calling request which can be received by the external system;
wherein the generating the callout message by using the request parameter, the message format of the callout message, and the message to be processed includes:
acquiring target information from the message to be processed and acquiring a target field from the request parameter, wherein the target field is a field preset in a message generation rule;
determining a preset message template matched with the target field;
and generating the callout message according to the message template and the message format of the callout message, and writing the target information into the callout message.
2. The method according to claim 1, wherein the parsing the packet to be processed into a map object according to the packet format of the packet to be processed comprises:
and analyzing the message to be processed by utilizing a message analyzer corresponding to the message format of the message to be processed to obtain a map object.
3. The method of claim 1, wherein the plurality of predetermined request types comprises at least: http requests, dubbo requests and socket requests.
4. The method according to claim 1, wherein the plurality of predetermined message formats comprises at least: json format, xml format, and fixed length format.
5. An callout gateway, comprising:
an access module to: receiving a first calling request which is sent by an internal system and used for calling an external system, wherein the first calling request at least carries a message to be processed; analyzing the message to be processed into a map object according to the message format of the message to be processed; acquiring a request parameter corresponding to the message to be processed from the map object; the request type of the first call request is any one of a plurality of preset request types, and the message format of the message to be processed is any one of a plurality of preset message formats;
the parameter analysis module is used for determining the message format of the callout message according to the request parameter;
the message generating module is used for generating the callout message by utilizing the request parameter, the message format of the callout message and the message to be processed;
the request routing module is used for sending a second calling request carrying the callout message to the external system according to a preset request routing rule, wherein the request routing rule at least configures the request type of the calling request which can be received by the external system;
wherein, the message generating module comprises:
an obtaining unit, configured to obtain target information from the to-be-processed packet, and obtain a target field from the request parameter, where the target field is a field preset in a packet generation rule;
the determining unit is used for determining a preset message template matched with the target field;
and the generating unit is used for generating the calling message and writing the target information into the calling message according to the message template and the message format of the calling message.
6. The callout gateway of claim 5, wherein the access module configured to parse the packet to be processed into a map object is specifically configured to: and analyzing the message to be processed by utilizing a message analyzer corresponding to the message format of the message to be processed to obtain a map object.
7. The callout gateway of claim 5, wherein the plurality of predetermined request types includes at least: http requests, dubbo requests and socket requests.
8. The callout gateway of claim 5, wherein the plurality of predefined message formats includes at least: json format, xml format, and fixed length format.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111039350.5A CN113709177B (en) | 2021-09-06 | 2021-09-06 | Method for processing message and external call gateway |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111039350.5A CN113709177B (en) | 2021-09-06 | 2021-09-06 | Method for processing message and external call gateway |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113709177A CN113709177A (en) | 2021-11-26 |
| CN113709177B true CN113709177B (en) | 2022-10-18 |
Family
ID=78660576
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111039350.5A Active CN113709177B (en) | 2021-09-06 | 2021-09-06 | Method for processing message and external call gateway |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113709177B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114567557A (en) * | 2022-03-07 | 2022-05-31 | 上海数禾信息科技有限公司 | Message processing method and device, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106020963A (en) * | 2016-06-07 | 2016-10-12 | 中国建设银行股份有限公司 | Cross-system internal service calling method and device |
| CN111182025A (en) * | 2019-11-26 | 2020-05-19 | 腾讯科技（深圳）有限公司 | Message processing method, device, server and storage medium |
| CN112134900A (en) * | 2020-09-28 | 2020-12-25 | 中国银行股份有限公司 | Data message processing method and device |
| CN112383533A (en) * | 2020-11-10 | 2021-02-19 | 中国农业银行股份有限公司 | Message format conversion method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103095479A (en) * | 2011-11-04 | 2013-05-08 | 华为技术有限公司 | Method and device of business configuration |
-
2021
- 2021-09-06 CN CN202111039350.5A patent/CN113709177B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106020963A (en) * | 2016-06-07 | 2016-10-12 | 中国建设银行股份有限公司 | Cross-system internal service calling method and device |
| CN111182025A (en) * | 2019-11-26 | 2020-05-19 | 腾讯科技（深圳）有限公司 | Message processing method, device, server and storage medium |
| CN112134900A (en) * | 2020-09-28 | 2020-12-25 | 中国银行股份有限公司 | Data message processing method and device |
| CN112383533A (en) * | 2020-11-10 | 2021-02-19 | 中国农业银行股份有限公司 | Message format conversion method and device |
Non-Patent Citations (1)
| Title |
|---|
| 恒丰银行分布式核心系统-API网关技术原型落地实践;赵毅等;《中国金融电脑》;20170407(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113709177A (en) | 2021-11-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111290865A (en) | Service calling method and device, electronic equipment and storage medium | |
| CN108574604A (en) | test method and device | |
| CN110933095A (en) | Message parsing method and device | |
| CN113360301B (en) | Message transmission system and method | |
| CN112511591A (en) | Method, device, equipment and medium for realizing hospital interface data interaction | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN112788128A (en) | Business information pushing method and device, storage medium and electronic device | |
| CN113709177B (en) | Method for processing message and external call gateway | |
| CN111200523B (en) | Method, device, equipment and storage medium for configuring middle platform system | |
| CN107368334B (en) | Business plug-in interaction system and method | |
| CN111367690A (en) | Method and device for supporting combined API service calling | |
| CN104954363A (en) | Method and device for generating interface document | |
| CN112019596B (en) | Message pushing method and device based on message routing configuration and electronic equipment | |
| CN114285793A (en) | Distribution method, distribution device, distribution equipment and storage medium | |
| CN112416739B (en) | Test method and device and electronic equipment | |
| CN112948306A (en) | Method and device for expanding system interface | |
| CN111988398A (en) | Data acquisition method, API gateway and medium | |
| CN116668520A (en) | Gateway-based service arrangement method, system, equipment and storage medium | |
| CN116346660A (en) | Data processing method, device, equipment and medium based on dependent replacement service | |
| CN114095365B (en) | Processing method and device of Internet of things service based on 5G message | |
| CN113691618A (en) | Message notification method, device, message center and storage medium | |
| CN113271300A (en) | Authentication system and method | |
| CN112714148A (en) | Interface configuration method, device, equipment and medium | |
| CN114428723A (en) | Test system, system test method, related device and storage medium | |
| CN111949472A (en) | Method and device for recording application logs |
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 |