CN113448993A - Service request routing method and device, electronic equipment and computer storage medium - Google Patents
Service request routing method and device, electronic equipment and computer storage medium Download PDFInfo
- Publication number
- CN113448993A CN113448993A CN202110796583.3A CN202110796583A CN113448993A CN 113448993 A CN113448993 A CN 113448993A CN 202110796583 A CN202110796583 A CN 202110796583A CN 113448993 A CN113448993 A CN 113448993A
- Authority
- CN
- China
- Prior art keywords
- service request
- background system
- key domain
- routing
- name
- 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
- 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/24—Querying
- G06F16/245—Query processing
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Computing Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a service request routing method, a service request routing device, electronic equipment and a computer storage medium, wherein the service request routing method comprises the following steps: firstly, receiving a service request sent by a front-end system; then, analyzing the service request to obtain key domain information of the service request; wherein the key domain information includes a key domain value; then, inquiring the key domain value in a global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user; after receiving the name of a target background system, sending the service request to the target background system; and the name of the target background system is the name of the background system selected by the user. The method avoids the operation that the data of the new system and the old system need to be synchronized in two directions in the prior art, thereby achieving the purpose of efficiently processing the service.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for routing a service request, an electronic device, and a computer storage medium.
Background
With the development of business, more and more enterprises adopt a micro-service architecture to develop application systems, and when a complex legacy system is modified, a parallel transition period of a new system and an old system exists for ensuring reliability, and meanwhile, services are provided for the outside, so that the old system can be switched to in time when a fault occurs.
In the existing implementation scheme, a database synchronization mode is usually adopted, data of a new system and an old system need to be synchronized in two directions, and a request of associated services can be randomly forwarded to any system. However, data synchronization is required, and data consistency between two sides of the new system and the old system is required, so the response of service processing is slow.
Disclosure of Invention
In view of the above, the present application provides a method, an apparatus, an electronic device, and a computer storage medium for routing a service request, which are used to perform service processing efficiently.
A first aspect of the present application provides a method for routing a service request, including:
receiving a service request sent by a front-end system;
analyzing the service request to obtain key domain information of the service request; wherein the key domain information includes a key domain value;
querying the key domain value in a global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user;
receiving the name of a target background system; the name of the target background system is the name of the background system selected by the user;
and sending the service request to the target background system.
Optionally, the analyzing the service request to obtain the key domain information of the service request includes:
inquiring the transaction code of the service request in an inquiry message parameter table to obtain the message parameter of the service request;
and analyzing the service request by using the message parameter of the service request to obtain the key domain information of the service request.
Optionally, the method for routing a service request further includes:
and if the key domain value is inquired in the global routing mapping table and the background system corresponding to the key domain value cannot be obtained, selecting one background system as a target background system according to the routing proportion parameter of each background system.
Optionally, the method for routing a service request further includes:
receiving a return message of the target background system aiming at the service request;
analyzing the return message to obtain key domain information of the return message; the key domain information of the return message comprises a key domain field name and a key domain value;
and maintaining the corresponding relation between the key field name, the key field value and the target background system to the global routing mapping table.
Optionally, the analyzing the return packet to obtain the key domain information of the return packet includes:
inquiring the transaction code of the return message in an inquiry message parameter table to obtain the message parameter of the return message;
inquiring the transaction code of the return message in a routing rule table to obtain the key field name of the return message;
and analyzing the return message by using the message parameter of the service request to obtain the key domain information of the return message.
A second aspect of the present application provides a service request routing apparatus, including:
the first receiving unit is used for receiving a service request sent by a front-end system;
the first analysis unit is used for analyzing the service request to obtain key domain information of the service request; wherein the key domain information includes a key domain value;
the first query unit is used for querying the key domain value in a global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user;
the second receiving unit is used for receiving the name of the target background system; the name of the target background system is the name of the background system selected by the user;
and the sending unit is used for sending the service request to the target background system.
Optionally, the first parsing unit includes:
the second query unit is used for querying the transaction code of the service request in a query message parameter table to obtain the message parameter of the service request;
and the first analysis subunit is used for analyzing the service request by using the message parameter of the service request to obtain the key domain information of the service request.
Optionally, the routing apparatus for the service request further includes:
and the selecting unit is used for selecting one background system as a target background system according to the routing proportion parameter of each background system if the background system corresponding to the key domain value cannot be obtained by inquiring the key domain value in the global routing mapping table.
Optionally, the routing apparatus for the service request further includes:
a third receiving unit, configured to receive a return packet of the target background system for the service request;
the second analysis unit is used for analyzing the return message to obtain the key domain information of the return message; the key domain information of the return message comprises a key domain field name and a key domain value;
and the maintenance unit is used for maintaining the corresponding relation between the key field name, the key field value and the target background system to the global routing mapping table.
Optionally, the second parsing unit includes:
the third query unit is used for querying the transaction code of the return message in a query message parameter table to obtain the message parameter of the return message;
a fourth query unit, configured to query, in a routing rule table, a transaction code of the return packet to obtain a key field name of the return packet;
and the second analysis subunit is used for analyzing the return message by using the message parameter of the service request to obtain the key domain information of the return message.
A third aspect of the present application provides an electronic device comprising:
one or more processors;
a storage device having one or more programs stored thereon;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement a method of routing service requests as recited in any of the first aspects.
A fourth aspect of the present application provides a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method for routing a service request according to any one of the first aspects.
In view of the foregoing, the present application provides a service request routing method, device, electronic device, and computer storage medium, where the service request routing method includes: firstly, receiving a service request sent by a front-end system; then, analyzing the service request to obtain key domain information of the service request; wherein the key domain information includes a key domain value; then, inquiring the key domain value in a global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user; after receiving the name of a target background system, sending the service request to the target background system; and the name of the target background system is the name of the background system selected by the user. The method avoids the operation that the data of the new system and the old system need to be synchronized in two directions in the prior art, thereby achieving the purpose of efficiently processing the service.
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 detailed flowchart of a service request routing method according to an embodiment of the present application;
fig. 2 is a detailed flowchart of a method for parsing a service request according to another embodiment of the present application;
fig. 3 is a detailed flowchart of a method for routing a service request according to another embodiment of the present application;
fig. 4 is a specific flowchart of a method for parsing a return packet according to another embodiment of the present application;
fig. 5 is a schematic diagram of a service request routing apparatus according to another embodiment of the present application;
fig. 6 is a schematic view of an electronic device implementing a service request routing method according to another embodiment of the present application.
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.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present application are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this application are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that reference to "one or more" unless the context clearly dictates otherwise.
An embodiment of the present application provides a method for routing a service request, as shown in fig. 1, which specifically includes the following steps:
s101, receiving a service request sent by a front-end system.
It should be noted that, in the implementation process in the present application, when the global gateway service is started, a corresponding Transmission Control Protocol (TCP) connection needs to be established according to the connection configuration table. The method comprises the steps of establishing a TCP long connection with a front-end system, starting a global gateway TCP short connection server to monitor, and establishing a TCP long connection with a new background system and an old background system. And meanwhile, the successfully established background system connection list is put into a local memory.
S102, analyzing the service request to obtain key domain information of the service request.
Wherein the key domain information includes a key domain value.
It should be noted that the key domain information of different service requests may be different, and is not limited herein.
Specifically, after receiving a TCP service request from the front-end system, the global gateway service parses the service request to obtain key domain information of the service request.
Optionally, in another embodiment of the present application, an implementation manner of step S102, as shown in fig. 2, includes:
s201, inquiring the transaction code of the service request in the inquiry message parameter table to obtain the message parameter of the service request.
It should be noted that different front-end systems may have different message formats, such as xml, json, 8583, fixed-length message, and so on. Therefore, message parameter configuration needs to be acquired according to different transaction codes.
S202, analyzing the service request by using the message parameter of the service request to obtain the key domain information of the service request.
S103, inquiring the key domain value in the global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user.
And S104, receiving the name of the target background system.
The name of the target background system is the name of the background system selected by the user.
It can be understood that, in the practical application process of the present application, there may also be a case where the key domain value is queried in the global routing mapping table and a background system corresponding to the key domain value cannot be obtained, so the embodiment of the present application further includes:
and if the key domain value is inquired in the global routing mapping table, and the background system corresponding to the key domain value cannot be obtained, selecting one background system as a target background system according to the routing proportion parameter of each background system.
It should be noted that, but not limited to, one background system may be selected as a target background system according to the routing proportion parameter of each background system; and routing to an optional background system by using a load balancing algorithm according to the routing proportion parameter of each background system, wherein the optional background system is used as a target background system and the like, and the routing is not limited herein.
And S105, sending the service request to a target background system.
Optionally, in another embodiment of the present application, an implementation manner of the service request routing method, as shown in fig. 3, further includes:
s301, receiving a return message of the target background system for the service request.
S302, the return message is analyzed, and key domain information of the return message is obtained.
The key domain information of the return message comprises a key domain field name and a key domain value.
Optionally, in another embodiment of the present application, an implementation manner of step S302, as shown in fig. 4, includes:
s401, in the inquiry message parameter table, inquiring the transaction code of the return message to obtain the message parameter of the return message.
S402, in the routing rule table, inquiring the transaction code of the return message to obtain the key domain field name of the return message.
It should be noted that, in the routing rule table, for multiple associated transaction codes in the same scene, the request key field of the first service may be null, which indicates a random routing of the first transaction; the request key domain name of the subsequent associated transaction needs to be the same as the return key domain name of the last transaction code, so that multiple associated transactions are routed to the same background system in the same payment scene.
And S403, analyzing the return message by using the message parameter of the service request to obtain the key domain information of the return message.
S303, maintaining the corresponding relation between the key field name, the key field value and the target background system to the global routing mapping table.
According to the above scheme, the present application provides a service request routing method: firstly, receiving a service request sent by a front-end system; then, analyzing the service request to obtain key domain information of the service request; wherein the key domain information comprises a key domain value; then, inquiring a key domain value in the global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user; after receiving the name of the target background system, sending the service request to the target background system; the name of the target background system is the name of the background system selected by the user. The method avoids the operation that the data of the new system and the old system need to be synchronized in two directions in the prior art, thereby achieving the purpose of efficiently processing the service.
Another embodiment of the present application provides a routing apparatus for a service request, as shown in fig. 5, specifically including:
a first receiving unit 501, configured to receive a service request sent by a front-end system.
A first parsing unit 502, configured to parse the service request to obtain key domain information of the service request.
Wherein the key domain information includes a key domain value.
Optionally, in another embodiment of the present application, an implementation manner of the first parsing unit 502 includes:
and the second query unit is used for querying the transaction code of the service request in the query message parameter table to obtain the message parameters of the service request.
And the first analysis subunit is used for analyzing the service request by using the message parameter of the service request to obtain the key domain information of the service request.
For a specific working process of the unit disclosed in the above embodiment of the present application, reference may be made to the content of the corresponding method embodiment, as shown in fig. 2, which is not described herein again.
The first querying unit 503 is configured to query the global routing mapping table for the key domain value, obtain at least one background system corresponding to the key domain value, and display each background system to the user.
A second receiving unit 504, configured to receive a name of the target backend system.
The name of the target background system is the name of the background system selected by the user.
A sending unit 505, configured to send the service request to the target background system.
For a specific working process of the unit disclosed in the above embodiment of the present application, reference may be made to the content of the corresponding method embodiment, as shown in fig. 1, which is not described herein again.
Optionally, in another embodiment of the present application, an implementation manner of the routing apparatus for a service request further includes:
and the selecting unit is used for selecting one background system as a target background system according to the routing proportion parameter of each background system if the background system corresponding to the key domain value cannot be obtained by inquiring the key domain value in the global routing mapping table.
For specific working processes of the units disclosed in the above embodiments of the present application, reference may be made to the contents of the corresponding method embodiments, which are not described herein again.
Optionally, in another embodiment of the present application, an implementation manner of the routing apparatus for a service request further includes:
and the third receiving unit is used for receiving a return message of the target background system aiming at the service request.
And the second analysis unit is used for analyzing the return message to obtain the key domain information of the return message.
The key domain information of the return message comprises a key domain field name and a key domain value.
And the maintenance unit is used for maintaining the corresponding relation between the key field name, the key field value and the target background system to the global routing mapping table.
For a specific working process of the unit disclosed in the above embodiment of the present application, reference may be made to the content of the corresponding method embodiment, as shown in fig. 3, which is not described herein again.
Optionally, in another embodiment of the present application, an implementation manner of the second parsing unit includes:
and the third query unit is used for querying the transaction code of the return message in the query message parameter table to obtain the message parameter of the return message.
And the fourth query unit is used for querying the transaction code of the return message in the routing rule table to obtain the key domain field name of the return message.
And the second analysis subunit is used for analyzing the return message by using the message parameter of the service request to obtain the key domain information of the return message.
For a specific working process of the unit disclosed in the above embodiment of the present application, reference may be made to the content of the corresponding method embodiment, as shown in fig. 4, which is not described herein again.
According to the above scheme, the present application provides a service request routing apparatus: first, a first receiving unit 501 receives a service request sent by a front-end system; then, the first parsing unit 502 parses the service request to obtain key domain information of the service request; wherein the key domain information comprises a key domain value; then, the first querying unit 503 queries the key domain value in the global routing mapping table to obtain at least one background system corresponding to the key domain value, and displays each background system to the user; after the second receiving unit 504 receives the name of the target background system, the sending unit 505 sends the service request to the target background system; the name of the target background system is the name of the background system selected by the user. The method avoids the operation that the data of the new system and the old system need to be synchronized in two directions in the prior art, thereby achieving the purpose of efficiently processing the service.
Another embodiment of the present application provides an electronic device, as shown in fig. 6, including:
one or more processors 601.
A storage device 602 having one or more programs stored thereon.
The one or more programs, when executed by the one or more processors 601, cause the one or more processors 601 to implement a method of routing service requests as described in any of the above embodiments.
Another embodiment of the present application provides a computer storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the method for routing a service request as described in any one of the above embodiments.
In the context of this application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be noted that the computer readable medium mentioned above in the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
Another embodiment of the present application provides a computer program product for performing the method for routing a service request according to any one of the above when the computer program product is executed.
In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means, or installed from a storage means, or installed from a ROM. The computer program, when executed by a processing device, performs the above-described functions defined in the method of the embodiments of the present application.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
While several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the application. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the application referred to in the present application is not limited to the embodiments with a particular combination of the above-mentioned features, but also encompasses other embodiments with any combination of the above-mentioned features or their equivalents without departing from the scope of the application. For example, the above features may be replaced with (but not limited to) features having similar functions as those described in this application.
Claims (10)
1. A method for routing a service request, comprising:
receiving a service request sent by a front-end system;
analyzing the service request to obtain key domain information of the service request; wherein the key domain information includes a key domain value;
querying the key domain value in a global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user;
receiving the name of a target background system; the name of the target background system is the name of the background system selected by the user;
and sending the service request to the target background system.
2. The routing method according to claim 1, wherein the parsing the service request to obtain the key domain information of the service request includes:
inquiring the transaction code of the service request in an inquiry message parameter table to obtain the message parameter of the service request;
and analyzing the service request by using the message parameter of the service request to obtain the key domain information of the service request.
3. The routing method according to claim 1, further comprising:
and if the key domain value is inquired in the global routing mapping table and the background system corresponding to the key domain value cannot be obtained, selecting one background system as a target background system according to the routing proportion parameter of each background system.
4. The routing method according to claim 3, further comprising:
receiving a return message of the target background system aiming at the service request;
analyzing the return message to obtain key domain information of the return message; the key domain information of the return message comprises a key domain field name and a key domain value;
and maintaining the corresponding relation between the key field name, the key field value and the target background system to the global routing mapping table.
5. The routing method according to claim 4, wherein the analyzing the return packet to obtain the key domain information of the return packet comprises:
inquiring the transaction code of the return message in an inquiry message parameter table to obtain the message parameter of the return message;
inquiring the transaction code of the return message in a routing rule table to obtain the key field name of the return message;
and analyzing the return message by using the message parameter of the service request to obtain the key domain information of the return message.
6. A device for routing service requests, comprising:
the first receiving unit is used for receiving a service request sent by a front-end system;
the first analysis unit is used for analyzing the service request to obtain key domain information of the service request; wherein the key domain information includes a key domain value;
the first query unit is used for querying the key domain value in a global routing mapping table to obtain at least one background system corresponding to the key domain value, and displaying each background system to a user;
the second receiving unit is used for receiving the name of the target background system; the name of the target background system is the name of the background system selected by the user;
and the sending unit is used for sending the service request to the target background system.
7. The routing device according to claim 6, wherein the first parsing unit comprises:
the second query unit is used for querying the transaction code of the service request in a query message parameter table to obtain the message parameter of the service request;
and the first analysis subunit is used for analyzing the service request by using the message parameter of the service request to obtain the key domain information of the service request.
8. The routing device of claim 6, further comprising:
and the selecting unit is used for selecting one background system as a target background system according to the routing proportion parameter of each background system if the background system corresponding to the key domain value cannot be obtained by inquiring the key domain value in the global routing mapping table.
9. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement a method of routing a service request as recited in any of claims 1 to 5.
10. A computer storage medium, having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a method of routing a service request according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110796583.3A CN113448993A (en) | 2021-07-14 | 2021-07-14 | Service request routing method and device, electronic equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110796583.3A CN113448993A (en) | 2021-07-14 | 2021-07-14 | Service request routing method and device, electronic equipment and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113448993A true CN113448993A (en) | 2021-09-28 |
Family
ID=77816364
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110796583.3A Pending CN113448993A (en) | 2021-07-14 | 2021-07-14 | Service request routing method and device, electronic equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113448993A (en) |
-
2021
- 2021-07-14 CN CN202110796583.3A patent/CN113448993A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109871224A (en) | A kind of gray scale dissemination method, system, medium and equipment based on user identifier | |
| US7194529B2 (en) | Method and apparatus for the delivery and integration of an asset management system into an existing enterprise network | |
| CN112600926A (en) | Message pushing method and device and computer readable storage medium | |
| CN111460129B (en) | Method, device, electronic equipment and storage medium for generating identification | |
| CN108093015B (en) | File transmission system | |
| CN111917838B (en) | Micro-service-based processing method and device, storage medium and electronic device | |
| CN115114044A (en) | Message pushing method, device, equipment and medium | |
| CN105227736A (en) | A kind of update method, Apparatus and system of reserved phone number | |
| KR101857020B1 (en) | Apparatas and method for managing service of providing server in a terminal | |
| CN109471713B (en) | Method and device for inquiring information | |
| CN110798495A (en) | Method and server for end-to-end message push in cluster architecture mode | |
| CN115951923B (en) | Subscription event management method, display system, device and storage medium | |
| CN113448993A (en) | Service request routing method and device, electronic equipment and computer storage medium | |
| CN108259576B (en) | Software and hardware real-time information transmission system and method | |
| CN112948138A (en) | Method and device for processing message | |
| CN113746851B (en) | Proxy system and method supporting real-time analysis of GRPC request | |
| CN115496544A (en) | Data processing method and device | |
| CN115665274A (en) | Data transmission method and system of heterogeneous protocol, electronic device and storage medium | |
| CN113079055B (en) | AGV operation data dynamic acquisition method and device | |
| CN113542424A (en) | Data processing method, device, equipment and computer program product | |
| CN113141236A (en) | Message processing method and device | |
| US20030056004A1 (en) | Method and apparatus for the routing of messages in an asset management system | |
| CN109688432B (en) | Information transmission method, device and system | |
| CN105281976A (en) | Method and apparatus for monitoring transmission of proxy service data | |
| US11799982B2 (en) | Message push method, apparatus, device and 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 |