CN120321176B - Routing information processing method, system, electronic device and storage medium - Google Patents
Routing information processing method, system, electronic device and storage mediumInfo
- Publication number
- CN120321176B CN120321176B CN202510819535.XA CN202510819535A CN120321176B CN 120321176 B CN120321176 B CN 120321176B CN 202510819535 A CN202510819535 A CN 202510819535A CN 120321176 B CN120321176 B CN 120321176B
- Authority
- CN
- China
- Prior art keywords
- route
- service
- request
- target
- node
- 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
Classifications
-
- 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L45/507—Label distribution
-
- 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/02—Topology update or discovery
- H04L45/06—Deflection routing, e.g. hot-potato routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本申请提供了一种路由信息处理方法、系统、电子设备及存储介质，所述方法包括：接收目标服务请求，提取目标服务请求对应的请求标签信息，请求标签信息用于表征目标服务请求关联的业务信息，将请求标签信息与各个路由进行匹配，各个路由包括至少一个一级路由和至少一个二级路由，每个一级路由为至少一个二级路由的入口路由，如果存在与请求标签信息匹配的目标路由，通过目标路由将目标服务请求转发至目标路由对应的服务节点。采用该方法提升了同一功能模块下的不同业务单元的业务请求处理能力，也提升了对集群节点的精细化控制能力。
The present application provides a routing information processing method, system, electronic device and storage medium, the method comprising: receiving a target service request, extracting request tag information corresponding to the target service request, the request tag information being used to characterize the business information associated with the target service request, matching the request tag information with each route, each route comprising at least one first-level route and at least one second-level route, each first-level route being the entry route of at least one second-level route, and if there is a target route that matches the request tag information, forwarding the target service request to the service node corresponding to the target route through the target route. This method improves the business request processing capabilities of different business units under the same functional module, and also improves the refined control capabilities of cluster nodes.
Description
Technical Field
The present application relates to the field of routing technologies, and in particular, to a routing information processing method, a system, an electronic device, and a storage medium.
Background
At present, a gateway framework corresponding to remote network credit accounting business of a banking system is relatively flat, and the problems that different business units under the same functional module cannot be effectively distinguished and the fine control capability of cluster nodes is lacking exist.
Disclosure of Invention
The application provides a routing information processing method, a system, electronic equipment and a storage medium.
In a first aspect of the present application, there is provided a routing information processing method, the method comprising:
receiving a target service request;
extracting request tag information corresponding to the target service request, wherein the request tag information is used for representing service information associated with the target service request;
Matching the request label information with each route, wherein each route comprises at least one primary route and at least one secondary route, and each primary route is an inlet route of at least one secondary route;
And if the target route matched with the request label information exists, forwarding the target service request to a service node corresponding to the target route through the target route.
In one embodiment, each secondary route comprises at least one service route and at least one virtual partition route, wherein different service routes correspond to different service nodes, the service routes are used for forwarding service requests to the corresponding service nodes, the virtual partition route corresponds to a child node of the at least one service node, and the virtual partition route is used for forwarding the service requests to one of the corresponding child nodes.
In an implementation manner, each secondary route is configured with a service identifier of a corresponding service node;
the matching the request label information with each route comprises the following steps:
determining the matching degree between the request label information and the service identifiers of the secondary routes corresponding to the primary routes according to each primary route;
If a secondary route with the matching degree larger than a preset matching threshold exists, the secondary route is used as a target route matched with the request label information;
if the secondary routes with the matching degree larger than a preset matching threshold value do not exist in the secondary routes corresponding to the primary routes, determining any one primary route as a target route matched with the request label information;
and adding the route identification of the target route to the information of the target service request.
In an embodiment, the determining the matching degree between the request tag information and the service identifier of each secondary route corresponding to the primary route includes:
determining a first matching degree between the request label information and the service identifiers of the service routes corresponding to the primary routes;
If a business route with the first matching degree being larger than the preset matching threshold exists, the business route is used as a target route matched with the request label information;
if no service route with the matching degree larger than the preset matching threshold exists in the corresponding secondary routes of each primary route, determining a second matching degree between the request label information and the service identifier of each virtual partition route;
And responding to the virtual partition route with the second matching degree larger than the preset matching threshold value, and taking the virtual partition route as a target route matched with the request label information.
In an embodiment, the target route is a virtual partition route, and the method further includes:
if the sub-node corresponding to the virtual partition route comprises a target sub-node matched with the target service request, forwarding the target service request to the target sub-node through the virtual partition route;
And if the sub-node corresponding to the virtual partition route does not comprise the target sub-node matched with the target service request, forwarding the target service request to each sub-node of the service node in sequence through the virtual partition route.
In an embodiment, before the extracting the request tag information corresponding to the target service request, the method further includes:
and verifying the request authority corresponding to the target service request.
In a second aspect of the present application, there is provided a routing information processing system including:
The request receiving module is used for receiving the target service request;
The system comprises at least one first-level route, at least one second-level route, a service node and a service node, wherein the first-level route is used for extracting request label information corresponding to the target service request, the request label information is used for representing service information related to the target service request, the request label information is matched with each route, and each route comprises at least one first-level route and at least one second-level route;
And at least one secondary route for forwarding the target service request to a corresponding service node.
In one embodiment, each secondary route comprises at least one service route and at least one virtual partition route, wherein different service routes correspond to different service nodes, the service routes are used for forwarding service requests to the corresponding service nodes, the virtual partition route corresponds to a child node of the at least one service node, and the virtual partition route is used for forwarding the service requests to one of the corresponding child nodes.
By adopting the route information processing method provided by the embodiment of the application, the request label information corresponding to the target service request is extracted by receiving the target service request, the request label information is used for representing the service information related to the target service request, the request label information is matched with each route, each route comprises at least one primary route and at least one secondary route, each primary route is an entry route of at least one secondary route, and if the target route matched with the request label information exists, the target service request is forwarded to the service node corresponding to the target route through the target route. The service interface management and control granularity is thinned through the multi-level routing framework, complex service requests can be effectively distinguished through multi-level routing, the service request processing capacity of different service units under the same functional module is improved, and the fine control capacity of cluster nodes is also improved.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the application or to delineate the scope of the application. Other features of the present application will become apparent from the description that follows.
Drawings
The above, as well as additional purposes, features, and advantages of exemplary embodiments of the present application will become readily apparent from the following detailed description when read in conjunction with the accompanying drawings. Several embodiments of the present application are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:
in the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Fig. 1 is a schematic flow chart of an implementation of a routing information processing method according to an embodiment of the present application;
fig. 2 shows a schematic diagram of an information matching flow provided by an embodiment of the present application;
fig. 3 is a schematic diagram showing a composition structure of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, features and advantages of the present application more comprehensible, the technical solutions according to the embodiments of the present application will be clearly described in the following with reference to the accompanying drawings, and it is obvious that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Because the gateway framework corresponding to the remote network credit accounting service of the bank system at present has the problems that different service units under the same functional module cannot be effectively distinguished and the fine control capability of cluster nodes is lacking, the application provides a routing information processing method, a system, electronic equipment and a storage medium for solving the problems. The electronic equipment provided by the application can be mobile phones, computers, tablet computers, servers and other equipment.
The technical solutions of the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.
Fig. 1 is a schematic flow chart of an implementation of a routing information processing method according to an embodiment of the present application. As shown in fig. 1, the routing information processing method includes:
s101, receiving a target service request.
In the application, the target service request comprises an application access request, a data acquisition request, a data accounting request and the like sent by a user side. The user side can comprise an individual user, an enterprise user and the like. The application access request may include an access request for a micro service, an access request for a service, and the like. Micro services may include various types of service products of financial systems, such as user services, transaction services, and risk control services. The businesses may include businesses of financial systems, such as loan businesses, repayment businesses, and financial data query businesses, among others. The data acquisition requests may include loan service data acquisition requests, repayment service data acquisition requests, and the like. The data accounting requests may include loan accounting requests, repayment accounting requests, and the like.
The request for the target service may include information such as request type information, user identification, and request target. The request type information may include a service identification of the requested service or an application identification of the requested service, etc. The user identification may be an identification characterizing unique identity information of the user, e.g. a user account identification. The request target includes information such as the requested data or service. The service identifier, the application identifier, the user identifier and the like can be character strings and/or numbers and the like.
For example, if the target service request is a loan business related request, the target service request may include information such as request type, user identification, loan type, loan amount, and loan duration. The request type may be a loan application. The user identification can be a user telephone or a user identification card number obtained by legal means or after authorization of the user. The loan type may be a personal loan or mortgage loan, etc., and the loan period may be one or three years, etc.
S102, extracting request tag information corresponding to the target service request, wherein the request tag information is used for representing service information associated with the target service request.
In the application, the request label information corresponding to the target service request can comprise request type information, user identification, a request target and the like.
S103, the request label information is matched with each route, wherein each route comprises at least one primary route and at least one secondary route, and each primary route is an inlet route of at least one secondary route.
In the present application, the primary route may be a gateway route. The secondary routes may include at least one traffic route. The secondary routes may also include at least one virtual partition route. Each gateway route may serve as an ingress route for at least one traffic route. The traffic route and the virtual partition route may be independent of each other, or the traffic route may serve as an ingress route for at least one virtual partition route.
In the present application, each gateway route may include own route configuration information and route configuration information of each corresponding secondary route. The request label information can be respectively matched with the route configuration information of the gateway route and the route configuration information of each corresponding secondary route through the gateway route. Specifically, the matching degree of the request label information and each route can be obtained by respectively calculating the edit distance or cosine similarity between the request label information and the route configuration information of the gateway route itself and the route configuration information of each corresponding secondary route. And determining whether the route is matched with the target service request according to the matching degree. Or it may query whether service information related to the service node included in the route configuration information exists in the request tag information, and if so, the tokens match.
S104, if the target route matched with the request label information exists, forwarding the target service request to a service node corresponding to the target route through the target route.
In the application, the service node can be a micro service application of a financial system, such as an online banking application, a mobile payment platform and the like. The service nodes may also be physical service nodes or virtual service nodes such as financial institution background servers, data analysis platforms, customer service and support nodes, and risk management and assessment nodes.
By adopting the route information processing method provided by the embodiment of the application, the request label information corresponding to the target service request is extracted by receiving the target service request, the request label information is used for representing the service information related to the target service request, the request label information is matched with each route, each route comprises at least one primary route and at least one secondary route, each primary route is an entry route of at least one secondary route, and if the target route matched with the request label information exists, the target service request is forwarded to the service node corresponding to the target route through the target route. The service interface management and control granularity is thinned through the multi-level routing framework, complex service requests can be effectively distinguished through multi-level routing, the service request processing capacity of different service units under the same functional module is improved, and the fine control capacity of cluster nodes is also improved.
In one possible implementation, each secondary route includes at least one traffic route and at least one virtual partition route, different ones of the traffic routes corresponding to different ones of the service nodes for forwarding service requests to the corresponding service nodes, the virtual partition route corresponding to a child of the at least one service node, the virtual partition route for forwarding service requests to one of the corresponding respective child nodes.
In the application, the sub-node corresponding to the virtual partition route can comprise one or more sub-nodes of one service node, and also can comprise sub-nodes of two or more service nodes. The service node may include one or more sub-nodes, each of which may be used to handle different traffic demands. For example, credit service nodes for processing credit service traffic for a financial system may include an A1 node, an A2 node, an A3 node, and an A4 node, wherein the A1 node and the A2 node may be used to process credit assessment traffic related to a user's monthly payment of assets. The asset service nodes for handling asset management traffic may include a B1 node, a B2 node, a B3 node, and a B4 node, wherein the B1 node and the B3 node may be used for handling monthly asset traffic. Namely, the node A1 and the node A2 in the child nodes of the credit service node and the node B1 and the node B3 in the child nodes of the asset service node can be used for processing the monthly asset service, the node A1, the node A2, the node B1 and the node B3 can jointly form a virtual partition, and the virtual partition can correspond to a virtual partition route. When the gateway route receives the service request for the virtual partition, the virtual partition route corresponding to the virtual partition can forward the service request to the A1 node, the A2 node, the B1 node and the B3 node.
In the present application, the primary route may include a gateway route, and the secondary route may include a traffic route and a virtual partition route. Gateway routing, traffic routing, and virtual partition routing may constitute a three-level routing architecture. When the business complexity becomes high, a developer of the financial system can configure gateway routing, business routing and virtual partition routing in the three-level routing architecture according to business requirements, so that the gateway routing, the business routing and the virtual partition routing can bear different business forwarding requirements, separate data access and application access of the financial system, and improve business processing capacity and granularity of the financial system.
In one possible implementation, the api_interface_config node, api_route_config node, api_route_rule, etc. of the gateway route may be configured for the gateway route. The api_interface_config node includes interface configuration main information, and an external request interface, a function switch, service node information forwarded by default, an interface corresponding to a service node, and the like corresponding to a gateway route can be configured at the api_interface_config node. The function switch may include a route switch, a current limit switch, etc., and the external request interface may be an API (application program interface) interface. The api_route_config node includes a service forwarding configuration, and each forwarding path under an interface of the gateway route and a matching rule set of a service node corresponding to the gateway route may be configured at the api_route_config node. The api_route_rule node comprises a route matching rule set, and a route matching rule of a service request and a gateway route can be configured in the api_route_rule node.
In the application, aiming at the service route, a developer can configure the information of each service route corresponding to the gateway route in the api_interface_config node, the api_route_rule node, the api_unit_route node and the api_unit_service node of the gateway route in advance according to the service requirement. For example, the switch of each service route corresponding to the gateway route, the default forwarding service node corresponding to each service route, the corresponding interface of the service node, and the like may be continuously configured at the api_interface_config. And the route matching rule of each service route corresponding to the gateway route can be continuously configured in the api_route_rule of the gateway route. The api_unit_route node can be added in the gateway route, the api_unit_route node comprises service route configuration, and service matching rules, enabling switches and the like corresponding to each service route corresponding to the gateway route can be configured in the api_unit_route node. The mapping relation configuration of the service route and the service node can be carried out by adding an api_unit_service node in the gateway route, and the enabling switch of the mapping relation between each service route and the corresponding service node can be configured in the api_unit_service node.
In the application, aiming at the virtual partition route, a developer can configure the information of each virtual partition route in the api_interface_config node, the api_route_rule node, the api_virtual_route node and the api_virtual_service node of the gateway route in advance according to the service requirement. For example, the switch of each virtual partition route, the default forwarding service node corresponding to each virtual partition route, the corresponding interface of the service node, and the like may be continuously configured at the api_interface_config. The route matching rules of each virtual route can also be continuously configured in the api_route_rule of the gateway route. An api_virtual_route node and an api_virtual_service node may also be added at the gateway. The api_virtual_route node is used for performing virtual partition route configuration, and a service matching rule, an enabling switch and the like corresponding to each virtual partition route can be configured at the api_virtual_route node. The api_virtual_service node is configured to perform mapping relationship configuration between the virtual partition route and the service node, and may configure an enabling switch of the mapping relationship between each virtual partition route and the corresponding service node at the api_virtual_service node.
In a possible implementation manner, each secondary route is configured with a service identifier of a corresponding service node. The matching the request label information with each route may include steps A1-A4:
and A1, determining the matching degree between the request label information and the service identifiers of the secondary routes corresponding to each primary route aiming at each primary route.
In the present application, the secondary routes may include traffic routes and virtual partition routes. The service identifier of the service route may include an identifier of the service unit code or an address characterizing the service node to which the service route corresponds, etc. The service unit code may be a service code processed by a service node corresponding to the service route, or a node address identifier, etc. The service identification of the virtual partition may include a virtual partition code or an identification characterizing an address of a service node to which the virtual partition route corresponds, etc.
In the application, whether the request label information comprises the service identifier of the secondary route can be inquired. Or in a possible implementation manner, fig. 2 shows a schematic information matching flow provided by the embodiment of the present application, as shown in fig. 2, where the determining a matching degree between the request tag information and service identifiers of the secondary routes corresponding to the primary route includes:
s201, determining a first matching degree between the request label information and the service identifiers of the service routes corresponding to the primary route.
In this step, an edit distance or cosine similarity between the request label information and the service identifier of each secondary route corresponding to the primary route may be calculated as the first matching degree.
S202, if a service route with the first matching degree being larger than the preset matching threshold exists, the service route is used as a target route matched with the request label information.
In the present application, the preset matching threshold may be set according to the application requirement, for example, set to 90% or 95% or the like.
And S203, if no service route with the matching degree larger than the preset matching threshold exists in the secondary routes corresponding to the primary routes, determining a second matching degree between the request label information and the service identifier of each virtual partition route.
In the application, if no service route is matched with the request label information, the editing distance or cosine similarity between the request label information and the service identifications of the virtual partition routes can be continuously calculated to be used as the second matching degree. In another embodiment, if there is a service route matching with the request label information, the editing distance or cosine similarity between the request label information and the service identifier of each virtual partition route may be further calculated as the second matching degree, and the virtual partition route matching with the request label information may be further determined according to the second matching degree. And taking the service route and the virtual partition route matched with the request label information as target routes.
S204, responding to the virtual partition route with the second matching degree larger than the preset matching threshold value, and taking the virtual partition route as a target route matched with the request label information.
For the case that no service route is matched with the request label information, the editing distance or cosine similarity between the request label information and the service identifications of each virtual partition route can be continuously calculated to serve as a second matching degree, whether the virtual partition route matched with the request label information exists or not is determined according to the second matching degree and a preset matching threshold, and if the virtual partition route matched with the request label information exists, the virtual partition route can be used as a target route.
If there is no virtual partition route and no traffic route matching the request label information, any one of the primary routes can be used as the target route.
And step A2, if a secondary route with the matching degree larger than a preset matching threshold exists, the secondary route is used as a target route matched with the request label information.
And step A3, if no secondary route with the matching degree larger than a preset matching threshold exists in the secondary routes corresponding to the primary routes, determining any one primary route as a target route matched with the request label information.
And step A4, adding the route identification of the target route to the information of the target service request.
In the present application, if it is determined that there is a traffic route matching the request tag information, the route identification of the traffic route may be added to the information of the target service request, for example, the route identification of the traffic route may be added to the request header information of the target service request. The route identifier of the service route may be used to identify that the target service request is to be transferred between service nodes corresponding to the service route. For example, the route identification of the traffic route may DEFAULT to null or "DEFAULT", or the route identification of the traffic route may be designed according to the application requirements, e.g., the route identification of the traffic route of the monthly payment traffic of the financial system may be set to "YF". The route identifier of the service route may be set in the gateway route, and may be set such that the route is not switched when the route identifier of the service route is null, and the route identifier of the service route may be associated with the service identifier corresponding to the service route when the route identifier of the service route is not null, for example, the route identifier is set as the service identifier of the service node corresponding to the service route.
In the present application, if it is determined that there is a virtual partition route matching the request tag information, the route identification of the virtual partition route may be added to the information of the target service request, for example, the route identification of the virtual partition route may be added to the request header information of the target service request. The route identification of the virtual partition route may be used to identify that the target service request is to be communicated between service nodes corresponding to the virtual partition route. For example, the route identification of the virtual partition route corresponding to the monthly virtual partition may be "DYYF". The route identifier of the virtual partition route can be null corresponding to the virtual partition of the full partition. For interfaces that do not involve virtual partitions, load balancing is performed by default using full partitions.
In the application, the route identification of the virtual partition route can be set in the gateway route. For example, the gateway route may be set such that the route identifier of the virtual partition route is null and indicates no access node limitation, and the route identifier of the virtual partition route may be associated with the service identifier corresponding to the virtual partition if the route identifier of the virtual partition route is not null, for example, the route identifier is set as the service identifier of the service node corresponding to the virtual partition route.
In one possible implementation, the target route is a virtual partition route, and the method further includes steps B1-B2:
Step B1, if the sub-node corresponding to the virtual partition route comprises a target sub-node matched with the target service request, forwarding the target service request to the target sub-node through the virtual partition route;
And B2, if the sub-node corresponding to the virtual partition route does not comprise the target sub-node matched with the target service request, forwarding the target service request to each sub-node of the service node in sequence through the virtual partition route.
In one possible implementation manner, before the request tag information corresponding to the target service request is extracted, the routing information processing method further comprises verifying the request authority corresponding to the target service request.
In the application, in order to improve the security of the routing processing system, the request authority corresponding to the target service request needs to be verified before the target service request is forwarded. The request authority may be authority of a user to access a service node corresponding to the target service request. The service node corresponding to the target service request and the required access authority can be analyzed, the authority information of the user corresponding to the target service request is queried from the authority management system or the database, and whether the user has the request authority is judged. If the user has the request authority, the request label information corresponding to the target service request can be further extracted. If the user does not have the request rights, the target service request may be rejected or filtered. By verifying the request authority, the security and reliability of the routing information processing system are improved.
The application also provides a routing information processing system, which comprises:
The request receiving module is used for receiving the target service request;
The system comprises at least one first-level route, at least one second-level route, a service node and a service node, wherein the first-level route is used for extracting request label information corresponding to the target service request, the request label information is used for representing service information related to the target service request, the request label information is matched with each route, and each route comprises at least one first-level route and at least one second-level route;
And at least one secondary route for forwarding the target service request to a corresponding service node.
By adopting the route information processing system provided by the embodiment of the application, the request label information corresponding to the target service request is extracted by receiving the target service request, the request label information is used for representing the service information related to the target service request, the request label information is matched with each route, each route comprises at least one primary route and at least one secondary route, each primary route is an entrance route of at least one secondary route, and if the target route matched with the request label information exists, the target service request is forwarded to the service node corresponding to the target route through the target route. The service interface management and control granularity is thinned through the multi-level routing framework, complex service requests can be effectively distinguished through multi-level routing, the service request processing capacity of different service units under the same functional module is improved, and the fine control capacity of cluster nodes is also improved.
In one embodiment, each secondary route comprises at least one service route and at least one virtual partition route, wherein different service routes correspond to different service nodes, the service routes are used for forwarding service requests to the corresponding service nodes, the virtual partition route corresponds to a child node of the at least one service node, and the virtual partition route is used for forwarding the service requests to one of the corresponding child nodes.
In an implementation manner, each secondary route is configured with a service identifier of a corresponding service node;
The first-level routes are also used for determining the matching degree between the request label information and the service identifications of the second-level routes corresponding to the first-level routes according to each first-level route, if the second-level routes with the matching degree larger than a preset matching threshold exist, the second-level routes are used as target routes matched with the request label information, if the second-level routes with the matching degree larger than the preset matching threshold do not exist in the second-level routes corresponding to the first-level routes, any one first-level route is determined to be the target route matched with the request label information, and the route identifications of the target routes are added into the information of the target service requests.
In an implementation manner, the primary route is further used for determining a first matching degree between the request label information and service identifications of the service routes corresponding to the primary routes, if a service route with the first matching degree being larger than the preset matching threshold exists, the service route is used as a target route matched with the request label information, if a service route with the matching degree being larger than the preset matching threshold does not exist in the secondary routes corresponding to the primary routes, a second matching degree between the request label information and the service identifications of the virtual partition routes is determined, and the virtual partition route is used as the target route matched with the request label information in response to the virtual partition route with the second matching degree being larger than the preset matching threshold.
In an implementation manner, the target route is a virtual partition route, the primary route is further used for forwarding the target service request to the target sub-node through the virtual partition route if the sub-node corresponding to the virtual partition route includes the target sub-node matched with the target service request, and forwarding the target service request to each sub-node of the service node through the virtual partition route if the sub-node corresponding to the virtual partition route does not include the target sub-node matched with the target service request.
In an embodiment, the routing information processing system further includes a verification module, configured to verify a request authority corresponding to the target service request.
The application also provides an electronic device and a readable storage medium. The application provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing one or more steps of the routing information processing method described above when the program is executed by the processor. The present application provides a readable storage medium containing computer executable instructions which, when executed by a computer processor, are for performing one or more steps of the routing information processing method described above.
FIG. 3 illustrates a schematic block diagram of an example electronic device 300 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 3, the apparatus 300 includes a computing unit 301 that may perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM) 302 or a computer program loaded from a storage unit 308 into a Random Access Memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the device 300 may also be stored. The computing unit 301, the ROM 302, and the RAM 303 are connected to each other by a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.
Various components in the device 300 are connected to the I/O interface 305, including an input unit 306, such as a keyboard, mouse, etc., an output unit 307, such as various types of displays, speakers, etc., a storage unit 308, such as a magnetic disk, optical disk, etc., and a communication unit 309, such as a network card, modem, wireless communication transceiver, etc. The communication unit 309 allows the device 300 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 301 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 301 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 301 performs the respective methods and processes described above, such as a route information processing method. For example, in some embodiments, the routing information processing method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 308. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 300 via the ROM 302 and/or the communication unit 309. When the computer program is loaded into the RAM 303 and executed by the computing unit 301, one or more steps of the routing information processing method described above may be performed. Alternatively, in other embodiments, the computing unit 301 may be configured to perform the routing information processing method by any other suitable means (e.g. by means of firmware).
Various implementations of the techniques described above herein may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), integrated Systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. In the context of the present disclosure, a machine-readable medium may be a tangible medium. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The 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. The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain. Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. In the description of the present disclosure, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
The foregoing is merely a specific embodiment of the disclosure, but the protection scope of the disclosure is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the disclosure, and it should be covered in the protection scope of the disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.
Claims (7)
1. A method of processing routing information, the method comprising:
receiving a target service request;
extracting request tag information corresponding to the target service request, wherein the request tag information is used for representing service information associated with the target service request;
the request label information is matched with each route, each route comprises at least one primary route and at least one secondary route, each primary route is an inlet route of at least one secondary route, each secondary route comprises at least one service route and at least one virtual partition route, different service nodes are corresponding to different service routes, the service routes are used for forwarding service requests to the corresponding service nodes, the virtual partition route corresponds to a child node of the at least one service node, the virtual partition route is used for forwarding the service requests to one child node of the corresponding child nodes, and each secondary route is configured with a service identifier of the corresponding service node;
If a target route matched with the request label information exists, forwarding the target service request to a service node corresponding to the target route through the target route;
wherein said matching the request tag information with each route includes:
determining the matching degree between the request label information and the service identifiers of the secondary routes corresponding to the primary routes according to each primary route;
If a secondary route with the matching degree larger than a preset matching threshold exists, the secondary route is used as a target route matched with the request label information;
if the secondary routes with the matching degree larger than a preset matching threshold value do not exist in the secondary routes corresponding to the primary routes, determining any one primary route as a target route matched with the request label information;
and adding the route identification of the target route to the information of the target service request.
2. The method of claim 1, wherein said determining a degree of matching between said request label information and traffic identifications of respective ones of said secondary routes corresponding to said primary route comprises:
determining a first matching degree between the request label information and the service identifiers of the service routes corresponding to the primary routes;
If a business route with the first matching degree being larger than the preset matching threshold exists, the business route is used as a target route matched with the request label information;
if no service route with the matching degree larger than the preset matching threshold exists in the corresponding secondary routes of each primary route, determining a second matching degree between the request label information and the service identifier of each virtual partition route;
And responding to the virtual partition route with the second matching degree larger than the preset matching threshold value, and taking the virtual partition route as a target route matched with the request label information.
3. The method of claim 1, wherein the target route is a virtual partition route, the method further comprising:
if the sub-node corresponding to the virtual partition route comprises a target sub-node matched with the target service request, forwarding the target service request to the target sub-node through the virtual partition route;
And if the sub-node corresponding to the virtual partition route does not comprise the target sub-node matched with the target service request, forwarding the target service request to each sub-node of the service node in sequence through the virtual partition route.
4. The method of claim 1, further comprising, prior to said extracting the request tag information corresponding to the target service request:
and verifying the request authority corresponding to the target service request.
5. A routing information processing system, comprising:
The request receiving module is used for receiving the target service request;
The system comprises at least one first-level route, at least one second-level route, a service node and a service node, wherein the first-level route is used for extracting request label information corresponding to the target service request, the request label information is used for representing service information related to the target service request, the request label information is matched with each route, and each route comprises at least one first-level route and at least one second-level route;
At least one secondary route for forwarding the target service request to a corresponding service node; each secondary route comprises at least one traffic route and at least one virtual partition route; different service routes correspond to different service nodes, and the service routes are used for forwarding service requests to the corresponding service nodes; the virtual partition route is used for forwarding a service request to one of the corresponding sub-nodes, and each secondary route is configured with a service identifier of the corresponding service node;
The first-level routes are also used for determining the matching degree between the request label information and the service identifications of the second-level routes corresponding to the first-level routes according to each first-level route, if the second-level routes with the matching degree larger than a preset matching threshold exist, the second-level routes are used as target routes matched with the request label information, if the second-level routes with the matching degree larger than the preset matching threshold do not exist in the second-level routes corresponding to the first-level routes, any one first-level route is determined to be the target route matched with the request label information, and the route identifications of the target routes are added into the information of the target service requests.
6. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of claims 1-4 when the program is executed.
7. A storage medium containing computer executable instructions which, when executed by a computer processor, are for performing the method of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510819535.XA CN120321176B (en) | 2025-06-19 | 2025-06-19 | Routing information processing method, system, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510819535.XA CN120321176B (en) | 2025-06-19 | 2025-06-19 | Routing information processing method, system, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN120321176A CN120321176A (en) | 2025-07-15 |
| CN120321176B true CN120321176B (en) | 2025-09-05 |
Family
ID=96331780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202510819535.XA Active CN120321176B (en) | 2025-06-19 | 2025-06-19 | Routing information processing method, system, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN120321176B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120711010A (en) * | 2025-08-22 | 2025-09-26 | 新立讯科技集团股份有限公司 | Elastic load balancing method and system for processing tens of millions of concurrent accesses |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114338397A (en) * | 2021-12-27 | 2022-04-12 | 中国联合网络通信集团有限公司 | Cloud platform network configuration method, device, server, storage medium and system |
| CN116527583A (en) * | 2023-06-20 | 2023-08-01 | 平安科技（深圳）有限公司 | Gateway route matching method, device, computer equipment and storage medium |
| CN117997970A (en) * | 2024-01-11 | 2024-05-07 | 百望股份有限公司 | Method and system for processing api request |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8266266B2 (en) * | 1998-12-08 | 2012-09-11 | Nomadix, Inc. | Systems and methods for providing dynamic network authorization, authentication and accounting |
| CN105141512B (en) * | 2015-06-29 | 2018-01-16 | 清华大学 | Support the Unified Network framework and control method of packet/circuit hybrid switching network |
| US10171353B2 (en) * | 2016-03-04 | 2019-01-01 | Oracle International Corporation | System and method for supporting dual-port virtual router in a high performance computing environment |
| US11153194B2 (en) * | 2019-04-26 | 2021-10-19 | Juniper Networks, Inc. | Control plane isolation for software defined network routing services |
| CN116886601A (en) * | 2019-09-12 | 2023-10-13 | 华为技术有限公司 | Computing power routing method and device |
| CN114827282B (en) * | 2022-03-30 | 2024-12-31 | 阿里云计算有限公司 | Service routing method, device, equipment and storage medium |
| CN116633852B (en) * | 2023-06-14 | 2026-01-13 | 阿里巴巴（中国）有限公司 | Data transmission method, system and electronic equipment |
| CN116896531A (en) * | 2023-06-16 | 2023-10-17 | 度小满科技(北京)有限公司 | Route forwarding method and device |
| CN119276861A (en) * | 2023-07-07 | 2025-01-07 | 中兴通讯股份有限公司 | Computing network scheduling method, network domain, cloud side node, computing power gateway, system and medium |
-
2025
- 2025-06-19 CN CN202510819535.XA patent/CN120321176B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114338397A (en) * | 2021-12-27 | 2022-04-12 | 中国联合网络通信集团有限公司 | Cloud platform network configuration method, device, server, storage medium and system |
| CN116527583A (en) * | 2023-06-20 | 2023-08-01 | 平安科技（深圳）有限公司 | Gateway route matching method, device, computer equipment and storage medium |
| CN117997970A (en) * | 2024-01-11 | 2024-05-07 | 百望股份有限公司 | Method and system for processing api request |
Also Published As
| Publication number | Publication date |
|---|---|
| CN120321176A (en) | 2025-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10942918B2 (en) | Self-cleaning token vault | |
| US11849051B2 (en) | System and method for off-chain cryptographic transaction verification | |
| US12026723B2 (en) | Electronic payment network security | |
| WO2020192184A1 (en) | Gang fraud detection based on graph model | |
| JP2019004463A (en) | Method, apparatus and non-transitory computer readable storage medium for transaction execution and validation in blockchain (transaction execution and validation in blockchain) | |
| US10609087B2 (en) | Systems and methods for generation and selection of access rules | |
| CN111404887A (en) | Service processing method and device | |
| CN103443800A (en) | Network rating | |
| CN120321176B (en) | Routing information processing method, system, electronic device and storage medium | |
| CN108549965A (en) | Data processing method and data processing platform (DPP), server | |
| CN112637222A (en) | Request processing method and device | |
| US11568416B2 (en) | Cryptocurrency transaction pattern based threat intelligence | |
| US20200167791A1 (en) | Crypto taint tracking | |
| CN110197426B (en) | Credit scoring model building method, device and readable storage medium | |
| CN116702159B (en) | Host protection method, device, computer equipment and storage medium | |
| TWI668657B (en) | Business processing method and device | |
| CN116703595A (en) | A metaverse money laundering identification method, device and storage medium | |
| Tunzina et al. | CBDC: Implementation of central bank digital currency using blockchain | |
| CN117765650B (en) | Hot ticket card blacklist generation method, device and medium | |
| CN118522026B (en) | Risk identification methods and devices | |
| US20250181891A1 (en) | Leveraging graph neural networks, community detection, and tree-based models for transaction classifications | |
| CN111291335B (en) | Bill data processing method and device, computer equipment and storage medium | |
| HK40032973A (en) | Service processing method and device | |
| CN115631027A (en) | Information processing method, device and computer-readable storage medium for service contract | |
| CN117453824A (en) | Data synchronization method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |