Routing information processing method and system, electronic equipment and storage medium

Abstract

The invention provides a routing information processing method and system, an electronic device and a storage medium, and the method comprises the steps: receiving a target service request, extracting request label information corresponding to the target service request, the request label information being used for representing business information associated with the target service request, matching the request label information with each route, and sending the matching result to the target service request; each route comprises at least one first-level route and at least one second-level route, each first-level route is an entrance route of the at least one second-level route, and if a target route matched with the request label information exists, the target service request is forwarded to a service node corresponding to the target route through the target route. By adopting the method, the service request processing capability of different service units under the same function module is improved, and the fine control capability of cluster nodes is also improved.

Description

Technical Field

[0001] This application relates to the field of routing technology, and in particular, to a method, system, electronic device, and storage medium for processing routing information. Background Art

[0002] Currently, the gateway framework corresponding to the remote online loan accounting service of the banking system is relatively flat, and there are problems such as the inability to effectively distinguish different service units under the same functional module and the lack of refined control ability for cluster nodes. Summary of the Invention

[0003] This application provides a method, system, electronic device, and storage medium for processing routing information.

[0004] In a first aspect of this application, a method for processing routing information is provided, and the method includes: Receiving a target service request; Extracting request tag information corresponding to the target service request, where the request tag information is used to characterize service information associated with the target service request; Matching the request tag information with each routing, where each routing includes at least one first-level routing and at least one second-level routing, and each first-level routing is an entry routing for at least one of the second-level routings; If there is a target routing that matches the request tag information, forwarding the target service request to a service node corresponding to the target routing through the target routing.

[0005] In an implementable manner, each second-level routing includes: at least one service routing and at least one virtual partition routing; different service routings correspond to different service nodes, and the service routing is used to forward a service request to the corresponding service node; the virtual partition routing corresponds to a child node of at least one service node, and the virtual partition routing is used to forward a service request to one of the corresponding child nodes.

[0006] In an implementable manner, each second-level routing is configured with a service identifier of a corresponding service node; The matching of the request tag information with each routing includes: For each first-level routing, determining the matching degree between the request tag information and service identifiers of each of the second-level routings corresponding to the first-level routing; If there is a second-level routing with a matching degree greater than a preset matching threshold, using the second-level routing as the target routing that matches the request tag information; If there is no secondary route with a matching degree greater than the preset matching threshold among the secondary routes corresponding to each primary route, any one of the primary routes is determined as the target route that matches the request tag information; Add the route identifier of the target route to the information of the target service request.

[0007] In an implementable manner, determining the matching degree between the request tag information and the service identifiers of the secondary routes corresponding to the primary route includes: Determine the first matching degree between the request tag information and the service identifiers of the secondary routes corresponding to the primary route; If there is a secondary route with a first matching degree greater than the preset matching threshold, the secondary route is used as the target route that matches the request tag information; If there is no secondary route with a matching degree greater than the preset matching threshold among the secondary routes corresponding to each primary route, determine the second matching degree between the request tag information and the service identifiers of the virtual partition routes; In response to a virtual partition route with a second matching degree greater than the preset matching threshold, the virtual partition route is used as the target route that matches the request tag information.

[0008] In an implementable manner, when the target route is a virtual partition route, the method further includes: If the target child node that matches the target service request is included in the child nodes corresponding to the virtual partition route, forward the target service request to the target child node through the virtual partition route; If the target child node that matches the target service request is not included in the child nodes corresponding to the virtual partition route, forward the target service request to each child node of the service node in sequence through the virtual partition route.

[0009] In an implementable manner, before extracting the request tag information corresponding to the target service request, it further includes: Verify the request permission corresponding to the target service request.

[0010] In a second aspect of the present application, a routing information processing system is provided, including: A request receiving module, configured to receive a target service request; At least one first-level route, which is used to extract the request label information corresponding to the target service request, and the request label information is used to characterize the service information associated with the target service request; match the request label information with each route, where each route includes at least one first-level route and at least one second-level route, and each first-level route is the entry route of at least one second-level route; if there is a first-level route that matches the request label information as the target route, forward the target service request to the service node corresponding to the target route through the target route; At least one second-level route, which is used to forward the target service request to the corresponding service node.

[0011] In an implementable manner, each second-level route includes: at least one service route and at least one virtual partition route; different service routes correspond to different service nodes, and the service route is used to forward the service request to the corresponding service node; the virtual partition route corresponds to the child nodes of at least one service node, and the virtual partition route is used to forward the service request to one of the corresponding child nodes.

[0012] By using the routing information processing method provided in the embodiments of the present application, by receiving the target service request, extracting the request label information corresponding to the target service request, where the request label information is used to characterize the service information associated with the target service request, matching the request label information with each route, where each route includes at least one first-level route and at least one second-level route, and each first-level route is the entry route of at least one second-level route, if there is a target route that matches the request label information, forward the target service request to the service node corresponding to the target route through the target route. That is, by using a multi-level routing framework, the control granularity of the service interface is refined, complex service requests can be effectively distinguished through multi-level routing, the service request processing capabilities of different service units under the same functional module are improved, and the refined control capabilities for cluster nodes are also improved.

[0013] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present application, nor is it used to limit the scope of the present application. Other features of the present application will become easily understandable through the following description. Description of the Drawings

[0014] By reading the following detailed description with reference to the drawings, the above and other objects, features, and advantages of the exemplary embodiments of the present application will become easily understandable. In the drawings, several embodiments of the present application are shown in an exemplary rather than restrictive manner, where: In the drawings, the same or corresponding reference numerals represent the same or corresponding parts.

[0015] Figure 1Shows a schematic implementation process diagram of the routing information processing method provided by an embodiment of the present application; Figure 2 Shows a schematic information matching process diagram provided by an embodiment of the present application; Figure 3 Shows a schematic composition structure diagram of an electronic device according to an embodiment of the present application. Detailed implementation manners

[0016] To make the objectives, features, and advantages of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts fall within the protection scope of the present application.

[0017] Since there are problems in the gateway framework corresponding to the remote online loan accounting service of the current banking system, such as the inability to effectively distinguish different business units under the same functional module and the lack of refined control ability for cluster nodes, therefore, to solve this problem, the present application provides a routing information processing method, system, electronic device, and storage medium. The electronic device provided by the present application can be devices such as mobile phones, computers, tablets, and servers.

[0018] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application.

[0019] Figure 1 Shows a schematic implementation process diagram of the routing information processing method provided by an embodiment of the present application. As Figure 1 shown, the routing information processing method includes: S101, receiving a target service request.

[0020] In the present application, the target service request includes application access requests, data acquisition requests, data accounting requests, etc. sent by the user side. The user side can include individual users and enterprise users, etc. The application access request can include access requests for microservices and access requests for services. Microservices can include various service products of the financial system, such as user services, transaction services, and risk control services. Services can include various services of the financial system, such as loan services, repayment services, and financial data query services. The data acquisition request can include loan service data acquisition requests and repayment service data acquisition requests. The data accounting request can include loan accounting requests and repayment accounting requests.

[0021] The target service request may include information such as request type information, user identification, and request target. The request type information may include the service identification of the requested service or the application identification of the requested application, etc. The user identification may be an identity identification representing the user's unique identity information. For example, a user account identification. The request target includes information such as the requested data or service, etc. The service identification, application identification, user identification, etc. may be strings and / or numbers, etc.

[0022] For example, if the target service request is a request related to a loan service, the target service request may include information such as request type, user identity identification, loan type, loan amount, and loan term, etc. The request type may be a loan application. The user identity identification may be the user's phone number or user ID number obtained by legal means or after user authorization. The loan type may be personal loan or mortgage loan, etc., and the loan term may be one-year or three-year, etc.

[0023] S102. Extract the request label information corresponding to the target service request, where the request label information is used to characterize the service information associated with the target service request.

[0024] In this application, the request label information corresponding to the target service request may include request type information, user identification, and request target, etc.

[0025] S103. Match the request label information with each route. Each of the routes includes at least one first-level route and at least one second-level route, and each of the first-level routes is the entry route of at least one of the second-level routes.

[0026] In this application, the first-level route may be a gateway route. The second-level route may include at least one service route. The second-level route may also include at least one virtual partition route. Each gateway route may serve as the entry route of at least one service route. The service route and the virtual partition route may be independent of each other, or the service route may serve as the entry route of at least one virtual partition route.

[0027] In this application, each gateway route may include its own route configuration information and the route configuration information of the corresponding second-level routes. Through the gateway route, the request label information may be respectively matched with the route configuration information of the gateway route itself and the corresponding second-level routes. Specifically, the edit distance or cosine similarity, etc. between the request label information and the route configuration information of the gateway route itself and the corresponding second-level routes may be calculated respectively as the matching degree of the request label information with each route. Determine whether the route matches the target service request according to the size of the matching degree. Or, it may be queried whether there is service information related to the service node included in the route configuration information in the request label information. If it exists, it indicates a match.

[0028] S104, if there is a target route that matches the request label information, forward the target service request to the service node corresponding to the target route through the target route.

[0029] In this application, the service node can be a microservice application of the financial system, such as an online banking application and a mobile payment platform, etc. The service node can also be a physical service node or a virtual service node such as a financial institution's back-end server, a data analysis platform, a customer service and support node, and a risk management and assessment node, etc.

[0030] By adopting the routing information processing method provided by the embodiment of this application, by receiving a target service request, extracting the request label information corresponding to the target service request, where the request label information is used to characterize the service information associated with the target service request, matching the request label information with each route, each route includes at least one first-level route and at least one second-level route, and each first-level route is an entry route for at least one second-level route. If there is a target route that matches the request label information, forward the target service request to the service node corresponding to the target route through the target route. That is, the business interface control granularity is refined through a multi-level routing framework, complex service requests can be effectively distinguished through multi-level routing, the service request processing ability of different business units under the same functional module is improved, and the refined control ability over cluster nodes is also improved.

[0031] In a possible implementation manner, each second-level route includes: at least one service route and at least one virtual partition route; different service routes correspond to different service nodes, and the service route is used to forward the service request to the corresponding service node; the virtual partition route corresponds to a child node of at least one service node, and the virtual partition route is used to forward the service request to one of the corresponding child nodes.

[0032] In this application, the sub-nodes corresponding to the virtual partition routing may include one or more sub-nodes of a service node, or may include sub-nodes in two or more service nodes. A service node may include one or more sub-nodes, and each sub-node may be used to process different business requirements. For example, a credit service node for processing credit service business in a financial system may include Node A1, Node A2, Node A3, and Node A4, where Node A1 and Node A2 may be used to process credit assessment business related to the user's monthly payment assets. An asset service node for processing asset management business may include Node B1, Node B2, Node B3, and Node B4, where Node B1 and Node B3 may be used to process monthly payment asset business. That is, Node A1 and Node A2 among the sub-nodes of the credit service node and Node B1 and Node B3 among the sub-nodes of the asset service node can both be used to process monthly payment asset business. Then, Node A1, Node A2, Node B1, and Node B3 can jointly form a virtual partition, and this virtual partition can correspond to a virtual partition routing. When the gateway routing receives a service request for this virtual partition, the virtual partition routing corresponding to this virtual partition can forward the service request to Node A1, Node A2, Node B1, and Node B3.

[0033] In this application, the first-level routing may include gateway routing, and the second-level routing may include service routing and virtual partition routing. The gateway routing, service routing, and virtual partition routing can form a three-level routing architecture. When the business complexity increases, developers of the financial system can configure the gateway routing, service routing, and virtual partition routing in the three-level routing architecture according to business requirements, so that the gateway routing, service routing, and virtual partition routing can undertake different service forwarding requirements, separate data access and application access in the financial system, and improve the business processing ability and granularity of the financial system.

[0034] In a possible implementation, for gateway routing, the api_interface_config node, api_route_config node, api_route_rule, etc. of the gateway routing can be configured. Among them, the api_interface_config node includes the main interface configuration information. The external request interface corresponding to the gateway routing, function switches, and default forwarding service node information, as well as the interfaces corresponding to the service nodes, can be configured in the api_interface_config node. The function switches can include routing switches and flow limiting switches, etc. The external request interface can be an API (Application Programming Interface) interface. The api_route_config node includes service forwarding configuration. The respective forwarding paths under the interface of the gateway routing and the set of matching rules for the service nodes corresponding to the gateway routing can be configured in the api_route_config node. The api_route_rule node includes a set of routing matching rules. The routing matching rules for service requests and the gateway routing can be configured in the api_route_rule node.

[0035] In this application, for business routing, developers can pre-configure the information of each business routing corresponding to the gateway routing in the api_interface_config node, api_route_rule node, api_unit_route node, and api_unit_service node of the gateway routing according to business requirements. For example, the switches of each business routing corresponding to the gateway routing, the default forwarding service nodes corresponding to each business routing, and the corresponding interfaces of the service nodes can continue to be configured in the api_interface_config. The routing matching rules of each business routing corresponding to the gateway routing can also be configured in the api_route_rule of the gateway routing. An api_unit_route node can be newly added to the gateway routing. The api_unit_route node includes business routing configuration. The business matching rules and enabling switches corresponding to each business routing corresponding to the gateway routing can be configured in the api_unit_route node. An api_unit_service node can also be newly added to the gateway routing. The api_unit_service node is used to configure the mapping relationship between business routing and service nodes. The enabling switches of the mapping relationship between each business routing and the corresponding service nodes can be configured in the api_unit_service node.

[0036] In this application, for virtual partition routing, developers can pre-configure the information of each virtual partition routing in the api_interface_config node, api_route_rule node, api_virtual_route node, and api_virtual_service node of the gateway routing according to business requirements. For example, the switches of each virtual partition routing, the default forwarding service nodes corresponding to each virtual partition routing, and the corresponding interfaces of the service nodes can continue to be configured in api_interface_config. The routing matching rules of each virtual route can also be continued to be configured in the api_route_rule of the gateway routing. The api_virtual_route node and api_virtual_service node can also be added to the gateway routing. The api_virtual_route node is used for virtual partition routing configuration, and the business matching rules and enabling switches corresponding to each virtual partition routing can be configured in the api_virtual_route node. The api_virtual_service node is used for configuring the mapping relationship between virtual partition routing and service nodes, and the enabling switch of the mapping relationship between each virtual partition routing and the corresponding service node can be configured in the api_virtual_service node.

[0037] In a possible implementation manner, each of the secondary routes is configured with the business identifier of the corresponding service node. The matching of the request tag information with each route may include steps A1 - A4: Step A1, for each primary route, determine the matching degree between the request tag information and the business identifiers of each of the secondary routes corresponding to the primary route.

[0038] In this application, the secondary routes may include business routes and virtual partition routes. The business identifier of the business route may include the business unit code or the identifier representing the address of the service node corresponding to the business route, etc. The business unit code may be the business code or node address identifier processed by the service node corresponding to the business route, etc. The business identifier of the virtual partition may include the virtual partition code or the identifier representing the address of the service node corresponding to the virtual partition routing, etc.

[0039] In this application, it can be queried whether the request tag information includes the business identifier of the secondary route. Or, in a possible implementation manner, Figure 2 The figure shows a schematic diagram of the information matching process provided by the embodiment of this application, as Figure 2 shown, the determining the matching degree between the request tag information and the business identifiers of each of the secondary routes corresponding to the primary route includes: S201, determine the first matching degree between the requested label information and the service identifiers of each of the service routes corresponding to this first-level route.

[0040] In this step, the edit distance or cosine similarity, etc. between the requested label information and the service identifiers of each of the second-level routes corresponding to the first-level route can be calculated as the first matching degree.

[0041] S202, if there is a service route with a first matching degree greater than the preset matching threshold, use this service route as the target route that matches the requested label information.

[0042] In this application, the preset matching threshold can be set according to application requirements. For example, it can be set to 90% or 95%, etc.

[0043] S203, if there is no service route among the second-level routes corresponding to each first-level route with a matching degree greater than the preset matching threshold, determine the second matching degree between the requested label information and the service identifiers of each of the virtual partition routes.

[0044] In this application, if there is no service route that matches the requested label information, the edit distance or cosine similarity, etc. between the requested label information and the service identifiers of each of the virtual partition routes can continue to be calculated as the second matching degree. In another implementation, if there is a service route that matches the requested label information, the edit distance or cosine similarity, etc. between the requested label information and the service identifiers of each of the virtual partition routes can also be further calculated as the second matching degree, and the virtual partition route that matches the requested label information can be further determined according to the second matching degree. Both the service route and the virtual partition route that match the requested label information are used as the target route.

[0045] S204, in response to a virtual partition route with a second matching degree greater than the preset matching threshold, use this virtual partition route as the target route that matches the requested label information.

[0046] For the case where there is no service route that matches the requested label information, the edit distance or cosine similarity, etc. between the requested label information and the service identifiers of each of the virtual partition routes can continue to be calculated as the second matching degree, and whether there is a virtual partition route that matches the requested label information can be determined according to the second matching degree and the preset matching threshold. If there is a virtual partition route that matches the requested label information, this virtual partition route can be used as the target route.

[0047] If there is no virtual partition route and service route that match the requested label information, any one of the first-level routes can be used as the target route.

[0048] Step A2, if there is a secondary route whose matching degree is greater than the preset matching threshold, use this secondary route as the target route that matches the request label information.

[0049] Step A3, if there is no secondary route whose matching degree is greater than the preset matching threshold among the secondary routes corresponding to each primary route, determine any one of the primary routes as the target route that matches the request label information.

[0050] Step A4, add the route identifier of the target route to the information of the target service request.

[0051] In this application, if it is determined that there is a service route that matches the request label information, the route identifier of the service route can be added to the information of the target service request. For example, the route identifier of the service route can be added to the request header information of the target service request. The route identifier of the service route can be used to identify the transfer of the target service request among the service nodes corresponding to the service route. For example, the route identifier of the service route can default to be empty or "DEFAULT", or the route identifier of the service route can be designed according to application requirements. For example, the route identifier of the service route for the monthly payment service in the financial system can be set to "YF". The route identifier of the service route can be set in the gateway route. It can be set that if the route identifier of the service route is empty, the route is not switched, and if the route identifier of the service route is not empty, the route identifier of the service route can be associated with the service identifier corresponding to the service route. For example, the route identifier is set to the service identifier of the service node corresponding to the service route.

[0052] In this application, if it is determined that there is a virtual partition route that matches the request label information, the route identifier of the virtual partition route can be added to the information of the target service request. For example, the route identifier of the virtual partition route can be added to the request header information of the target service request. The route identifier of the virtual partition route can be used to identify the transfer of the target service request among the service nodes corresponding to the virtual partition route. For example, the route identifier of the virtual partition route corresponding to the monthly payment virtual partition can be "DYYF". For the virtual partition route corresponding to the full partition, the route identifier of the virtual partition route can be empty. For interfaces that do not involve virtual partitions, the full partition is used for load balancing processing by default.

[0053] In this application, the route identifier of the virtual partition route can be set in the gateway route. For example, it can be set in the gateway route that if the route identifier of the virtual partition route is empty, it indicates no access node restriction, and if the route identifier of the virtual partition route is not empty, the route identifier of the virtual partition route can be associated with the service identifier corresponding to the virtual partition. For example, the route identifier is set to the service identifier of the service node corresponding to the virtual partition route.

[0054] In a possible implementation, the target route is a virtual partition route, and the method further includes steps B1 - B2: Step B1, if the target child node matching the target service request is included in the child nodes corresponding to the virtual partition route, forward the target service request to the target child node through the virtual partition route; Step B2, if the target child node matching the target service request is not included in the child nodes corresponding to the virtual partition route, forward the target service request to each child node of the service node in sequence through the virtual partition route.

[0055] In a possible implementation, before extracting the request tag information corresponding to the target service request, the routing information processing method further includes: verifying the request permission corresponding to the target service request.

[0056] In this application, in order to improve the security of the routing processing system, it is also necessary to verify the request permission corresponding to the target service request before forwarding the target service request. The request permission may be the permission for a user to access the service node corresponding to the target service request. The service node corresponding to the target service request and the required access permission can be parsed, and the permission information of the user corresponding to the target service request can be queried from the permission management system or database to determine whether the user has the request permission. If the user has the request permission, the request tag information corresponding to the target service request can be further extracted. If the user does not have the request permission, the target service request can be rejected or filtered. By verifying the request permission, the security and reliability of the routing information processing system are improved.

[0057] This application also provides a routing information processing system, including: A request receiving module, configured to receive a target service request; At least one primary route, configured to extract the request tag information corresponding to the target service request, where the request tag information is used to characterize the service information associated with the target service request; match the request tag information with each route, where each route includes at least one primary route and at least one secondary route, and each primary route is the entry route of at least one of the secondary routes; if there is a primary route matching the request tag information as the target route, forward the target service request to the service node corresponding to the target route through the target route; At least one secondary route, configured to forward the target service request to the corresponding service node.

[0058] By using the routing information processing system provided in the embodiments of the present application, by receiving a target service request, extracting request tag information corresponding to the target service request, where the request tag information is used to characterize the service information associated with the target service request, and matching the request tag information with each route, each route includes at least one first-level route and at least one second-level route, and each first-level route is the entry route of at least one second-level route. If there is a target route that matches the request tag information, the target service request is forwarded to the service node corresponding to the target route through the target route. That is, by using a multi-level routing framework, the control granularity of the service interface is refined, complex service requests can be effectively distinguished through multi-level routing, the service request processing capabilities of different service units under the same functional module are improved, and the refined control capabilities for cluster nodes are also improved.

[0059] In an implementable manner, each second-level route includes: at least one service route and at least one virtual partition route; different service routes correspond to different service nodes, and the service route is used to forward a service request to the corresponding service node; the virtual partition route corresponds to a child node of at least one service node, and the virtual partition route is used to forward a service request to one of the corresponding child nodes.

[0060] In an implementable manner, each second-level route is configured with a service identifier of the corresponding service node; The first-level route is further configured to, for each first-level route, determine the matching degree between the request tag information and the service identifiers of the respective second-level routes corresponding to the first-level route; if there is a second-level route with a matching degree greater than a preset matching threshold, use the second-level route as the target route that matches the request tag information; if there is no second-level route with a matching degree greater than the preset matching threshold among the second-level routes corresponding to each first-level route, determine any one of the first-level routes as the target route that matches the request tag information; and add the route identifier of the target route to the information of the target service request.

[0061] In an implementable manner, the first-level route is further configured to determine a first matching degree between the request tag information and the service identifiers of the respective service routes corresponding to the first-level route; if there is a service route with a first matching degree greater than the preset matching threshold, use the service route as the target route that matches the request tag information; if there is no service route with a matching degree greater than the preset matching threshold among the second-level routes corresponding to each first-level route, determine a second matching degree between the request tag information and the service identifiers of the respective virtual partition routes; in response to a virtual partition route with a second matching degree greater than the preset matching threshold, use the virtual partition route as the target route that matches the request tag information.

[0062] In an implementable embodiment, the target route is a virtual partition route, and the first-level route is further configured to, if a target child node matching the target service request is included in the child nodes corresponding to the virtual partition route, forward the target service request to the target child node through the virtual partition route; if a target child node matching the target service request is not included in the child nodes corresponding to the virtual partition route, forward the target service request to each child node of the service node in sequence through the virtual partition route.

[0063] In an implementable embodiment, the route information processing system further includes a verification module configured to verify the request permission corresponding to the target service request.

[0064] This application also provides an electronic device and a readable storage medium. The electronic device provided by this application includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, one or more steps of the route information processing method described above are implemented. The readable storage medium provided by this application contains computer-executable instructions that are used to execute one or more steps of the route information processing method described above when executed by a computer processor.

[0065] Figure 3 FIG. shows a schematic block diagram of an exemplary electronic device 300 that can be used to implement the embodiments of the present disclosure. The electronic device is intended to represent various forms of digital computers, such as, for example, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, for example, a personal digital processor, a cellular phone, a smartphone, a wearable device, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely exemplary and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0066] As Figure 3 shown, the device 300 includes a computing unit 301 that can perform various appropriate 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 can also be stored. The computing unit 301, the ROM 302, and the RAM 303 are connected to each other through a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0067] Multiple components in device 300 are connected to I / O interface 305, including: an input unit 306, such as a keyboard, a mouse, etc.; an output unit 307, such as various types of displays, speakers, etc.; a storage unit 308, such as a disk, an optical disc, etc.; and a communication unit 309, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 309 allows device 300 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0068] The computing unit 301 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated 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 executes the various methods and processes described above, such as the routing information processing method. For example, in some embodiments, the routing information processing method can be implemented as a computer software program that is tangibly contained in a machine-readable medium, such as the storage unit 308. In some embodiments, part or all of the computer program can be loaded and / or installed onto 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 can be executed. Alternatively, in other embodiments, the computing unit 301 can be configured to execute the routing information processing method in any other suitable manner (e.g., by means of firmware).

[0069] Various embodiments of the technologies described above in this document may be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system on a chip (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. Program code for implementing the 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. A 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, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. A computer system may include a client and a server. The client and the server are generally far apart from each other and typically interact through a communication network. The server may be a cloud server, or a server of a distributed system, or a server incorporating a blockchain. Additionally, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. In the description of the present disclosure, "a plurality of" means two or more unless otherwise specifically defined.

[0070] The above are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art can easily conceive of changes or substitutions within the technical scope disclosed by the present disclosure, and all such changes or substitutions should be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A method for processing routing information, characterized in that The method includes: Receiving a target service request; Extracting request tag information corresponding to the target service request, where the request tag information is used to characterize service information associated with the target service request; Matching the request tag information with each route, where each route includes at least one first-level route and at least one second-level route, and each first-level route is an entry route for at least one of the second-level routes; If there is a target route that matches the request tag information, forwarding the target service request to a service node corresponding to the target route through the target route.

2. The method according to claim 1, wherein Each second-level route includes: at least one service route and at least one virtual partition route; different service routes correspond to different service nodes, and the service route is used to forward a service request to the corresponding service node; the virtual partition route corresponds to a child node of at least one service node, and the virtual partition route is used to forward a service request to one of the corresponding child nodes.

3. The method according to claim 2, characterized in that, Each second-level route is configured with a service identifier of a corresponding service node; The matching of the request tag information with each route includes: For each first-level route, determining a matching degree between the request tag information and service identifiers of each of the second-level routes corresponding to the first-level route; If there is a second-level route with a matching degree greater than a preset matching threshold, taking the second-level route as a target route that matches the request tag information; If there is no second-level route with a matching degree greater than the preset matching threshold among the second-level routes corresponding to each first-level route, determining any one of the first-level routes as a target route that matches the request tag information; Adding a route identifier of the target route to information of the target service request.

4. The method according to claim 3, wherein The determining the matching degree between the request tag information and service identifiers of each of the second-level routes corresponding to the first-level route includes: Determining a first matching degree between the request tag information and service identifiers of each of the service routes corresponding to the first-level route; If there is a service route with a first matching degree greater than the preset matching threshold, taking the service route as a target route that matches the request tag information; If there is no service route with a matching degree greater than the preset matching threshold among the second-level routes corresponding to each first-level route, determining a second matching degree between the request tag information and service identifiers of each of the virtual partition routes; In response to a virtual partition route with a second matching degree greater than the preset matching threshold, taking the virtual partition route as a target route that matches the request tag information.

5. The method according to claim 2, wherein When the target route is a virtual partition route, the method further includes: If a target child node that matches the target service request is included in child nodes corresponding to the virtual partition route, forwarding the target service request to the target child node through the virtual partition route; If a target child node that matches the target service request is not included in child nodes corresponding to the virtual partition route, forwarding the target service request to each of the child nodes of the service node in sequence through the virtual partition route.

6. The method according to claim 1, characterized in that, Before extracting the request tag information corresponding to the target service request, it further includes: Verifying the request permission corresponding to the target service request.

7. A routing information processing system, characterized in that, It includes: A request receiving module, configured to receive a target service request; At least one first-level route, configured to extract the request tag information corresponding to the target service request, where the request tag information is used to characterize the service information associated with the target service request; matching the request tag information with each route, where each route includes at least one first-level route and at least one second-level route, and each first-level route is the entry route of at least one of the second-level routes; if there is a first-level route that matches the request tag information as the target route, forwarding the target service request to the service node corresponding to the target route through the target route; At least one second-level route, configured to forward the target service request to the corresponding service node.

8. The system according to claim 7, wherein Each second-level route includes: at least one service route and at least one virtual partition route; different service routes correspond to different service nodes, and the service route is configured to forward the service request to the corresponding service node; the virtual partition route corresponds to a child node of at least one service node, and the virtual partition route is configured to forward the service request to one of the corresponding child nodes.

9. An electronic device, characterized in that, It includes: A memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the program, it implements the method according to any one of claims 1-6.

10. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to execute the method according to any one of claims 1-6.

Images