Service routing table management method and device

Abstract

The invention discloses a service routing table management method, device and equipment. The method comprises the following steps: constructing a service routing table based on a service table and a service template; and updating the service routing table based on the state of the service instance and the reckoning load of the service instance. According to the invention, the service requests of different levels are forwarded according to the next hops of the respective service routes, and the service requests of the same level realize the load balancing of the flow among a plurality of non-equivalent load sharing paths, so that the resource utilization rate is improved, the differentiated requirements of users are met, the response speed is higher, the deployment is simpler, and the user experience is improved. The technical problem that the utilization rate of network and computing power resources is low in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of routing technology, and in particular to a service routing table management method and device. Background Art

[0002] At present, the computing network is a new network architecture that deeply integrates computing power and network, which enables the network to dispatch computing resources in different locations on demand and on time, and improve the utilization rate of network and computing resources. Meeting the requirements of efficient connection, on-demand allocation and flexible scheduling of computing resources is an important direction for the development of computing network.

[0003] In related technologies, mathematical tools are usually used to model and solve the problems of efficient connection, on-demand allocation and flexible scheduling of computing resources. However, due to the differences in computing power measurement and network measurement, as well as the heterogeneous measurement of computing power, the method of mapping user needs is complicated, the premise and assumptions based on which the created model is based are different from the actual scenario, and the data involved in the model and the solution process are difficult to collect in the actual system.

[0004] The existence of these problems has resulted in low utilization of network and computing resources. Therefore, a solution to improve the utilization of network and computing resources is urgently needed. Summary of the invention

[0005] The present invention provides a service routing table management method and device, which can solve the technical problem of low utilization rate of network and computing power resources existing in the prior art.

[0006] To achieve the above object, the present invention provides the following technical solutions:

[0007] In a first aspect, an embodiment of the present invention provides a service routing table management method, the method comprising:

[0008] Build a service routing table based on the service table and service template;

[0009] The service routing table is updated based on the status of the service instance and the inferred load of the service instance.

[0010] In a second aspect, an embodiment of the present invention provides a service routing table management device, the device comprising:

[0011] A routing table building module, configured to build a service routing table based on the service table and the service template;

[0012] The information updating module is configured to update the service routing table based on the status of the service instance and the estimated load of the service instance.

[0013] In a third aspect, an embodiment of the present invention further provides an electronic device, comprising: a memory, a processor; the processor is used to read and execute a computer program stored in the memory to implement the aforementioned service routing table management method.

[0014] In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions, when executed, implement the aforementioned service routing table management method.

[0015] The beneficial effects brought by the technical solution provided by the embodiment of the present invention include:

[0016] The service routing table is built based on the service table and service template to map the service level Level of the server capability to the service level Color of the network side, so that the service capability and network capability are matched. The hierarchical service routing method is adopted, which is easy to operate and manage, avoids the huge table entry requirements of fine-grained traffic scheduling, meets the needs of users at different service levels, and provides differentiated services;

[0017] Based on the status of the service instance and the estimated load of the service instance, the service routing table is updated to balance the loads among different instances, thereby improving resource utilization.

[0018] Through the present invention, service requests of different levels are forwarded according to the next hop of their respective service routes, and service requests of the same level achieve load balancing of traffic among multiple non-equal load sharing paths, thereby improving resource utilization, meeting the differentiated needs of users, and having faster response speed and simpler deployment, thereby solving the technical problem of low utilization of network and computing resources existing in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0020] Figure 1 A schematic diagram of a flow chart of an embodiment of a service routing table management method of the present invention;

[0021] Figure 2 A schematic diagram of a service routing diagram according to an embodiment of the present invention;

[0022] Figure 3 A schematic diagram of a service routing network according to an embodiment of the present invention;

[0023] Figure 4 for Figure 1 Detailed flow chart of step S20;

[0024] Figure 5 A flow chart of another embodiment of the service routing table management method of the present invention;

[0025] Figure 6 A schematic diagram of functional modules of an embodiment of a service routing table management device of the present invention;

[0026] Figure 7 The figure is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0028] To make the objectives, technical solutions and advantages of the present invention more clear, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0029] In a first aspect, an embodiment of the present invention provides a service routing table management method.

[0030] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of an embodiment of the service routing table management method of the present invention. Figure 1 As shown, the service routing table management method includes:

[0031] Step S10, constructing a service routing table based on the service table and the service template;

[0032] In this embodiment, the service table is formed based on the service instance information of the configuration connection on the computing power routing egress node. The initial state of the service instance is available. The service instance information includes the computing power service identifier SID, computing power service level, computing power service instance IP, outbound interface, next hop information and computing power service type.

[0033] The service level in the service routing identifier represents the basic optimization goal of the service, including basic computing power service capabilities and network resource constraints. Different service instances of the same service function can provide different service capability levels, and the network capabilities required to match are also different. The routing node connected to the service colors the service route according to the mapping strategy and service level parameter value to indicate its requirements for network capabilities, that is, the network-side service level is represented by different colors, and the service-side capability service level is represented by different levels. Therefore, the corresponding service template should be deployed on the first router connected to the service instance to complete the mapping from Level to Color, and the service level capability is converted into the requirements for the network through Color to build an end-to-end hierarchical service capability. When the routing node calculates the service route, it iterates the forwarding path based on the service route Color to obtain the service routing table. The hierarchical service routing method is easy to operate and manage, avoids the huge table requirements for fine-grained traffic scheduling, meets the needs of users at different service levels, and provides differentiated services.

[0034] Reference Figure 2 , Figure 2 FIG. 1 is a schematic diagram of a service routing table according to an embodiment of the present invention. Figure 2 As shown in the figure, in the service routing table of the same service, each service level has its own corresponding routing next hop. There are one or more next hops for the same service level, and a UCMP (Unequal Cost Multiple Path) path is formed between multiple next hops. Service requests of different levels are forwarded according to the next hop of their respective service routes. For service requests of the same level, weighted load balancing of traffic is achieved between multiple UCMP paths.

[0035] It should be noted that when deploying a service instance, resources are allocated based on the service capabilities such as computing, communication, memory, and storage, and the initial resource level of the service instance is set. The service level division method is not limited here. Each computing service can have its own service level division method that can cover the needs of each user and has consistent semantics.

[0036] In some specific embodiments, step S10 includes:

[0037] Determine the service level of the server capability corresponding to each service instance based on the service table;

[0038] Determine the network-side service level corresponding to each server-side capability service level based on the service template;

[0039] The next hop is calculated by each network-side service level and the forwarding path is iterated to obtain the service routing table.

[0040] In this embodiment, refer to Figure 3 , Figure 3 FIG. 1 is a schematic diagram of a service routing network according to an embodiment of the present invention. Figure 3 As shown, computing power routing exit node 1 is connected to service 1: instance 1 and service 1: instance 2 on the computing power server; computing power routing exit node 2 is connected to service 1: instance 3 on the computing power server. Computing power routing exit node 1 and computing power routing exit node 2 obtain the following service table information through management and control configuration or protocol interaction with the server: computing power service (computing power service identifier SID, service level), service instance IP, outbound interface, next hop information, service type, etc. When the user needs to access service 1, it connects to computing power routing entry node 1 and computing power routing entry node 2 through CPE (Customer-premises equipment, user terminal equipment) dual homing.

[0041] Among them, the computing power routing entry node 1 and the computing power routing entry node 2 are both the second routers, and the computing power routing exit node 1 and the computing power routing exit node 2 are both the first routers. The computing power routing intermediate node 1 is a common node between the computing power routing entry node 1 and the computing power routing exit node 1, and the computing power routing intermediate node 2 is a common node between the computing power routing entry node 2 and the computing power routing exit node 2. The computing power routing intermediate node 1 and the computing power routing intermediate node 2 mainly play the role of information forwarding.

[0042] Hierarchical service routing identification uses SRv6 segment routing. SID includes Locator (network addressing, including service routing addressing), Function (service capability) and Level (service level). Function represents the service capability provided, and the parameter part of SRv6 SID represents the service level, which corresponds to the service capability level provided by the computing power service and the requirements for network carrying. For the SID of the same service, the Locator and Function are the same, but the Level can be different.

[0043] The service table formed based on the service instance information configured on the computing power routing exit node 1 is as follows:

[0044] Service 1, service instance 1, IP 1, SID 1 (Locator+Function)+Level 0, status (Green);

[0045] Service 1, service instance 2, IP 2, SID 1 (Locator+Function)+Level 1, status (Green).

[0046] The service table formed based on the service instance information configured on the computing power routing exit node 2 is as follows:

[0047] Service 1, service instance 3, IP 3, SID 1 (Locator+Function)+Level 1, status (Green).

[0048] The service templates configured on computing power routing exit nodes 1 and 2 are as follows:

[0049] Service 1, Level 0, color X;

[0050] Service 1, Level 1, color Y.

[0051] Based on the service table, it is determined that the server capability service level corresponding to service instance 1 is Level 0, the server capability service level corresponding to service instance 2 is Level 1, and the server capability service level corresponding to service instance 3 is Level 1.

[0052] Based on the service template, it is determined that the network-side service level corresponding to service 1Level 0 is color X, and the network-side service level corresponding to service 1Level 1 is color Y.

[0053] The computing power routing entry node 1 can learn the service tables advertised by the computing power routing exit nodes 1 and 2 through the extended BGP protocol, calculate the appropriate next-hop forwarding path based on the network-side service level color, and preferentially add all next-hops with a status of Green in each service table to the service routing table. Iterate the service instances with a service level of Level 0 on the server side according to color X to the SRv6-TE Policy that meets the requirements, and iterate the service instances with a service level of Level on the server side according to color Y to the SRv6-TE Policy that meets the requirements. The service routing table is as follows:

[0054] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0055] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2, weight w1;

[0056] SID 1 Level 1, next hop computing power routing exit node 2 IP, business SID_S2, instance IP3, weight w2.

[0057] The initial state weight w1=w2=1, and the service request message of the service level of Level 1 is load-balanced equally between the two instances IP2 and IP3.

[0058] Step S20: updating the service routing table based on the status of the service instance and the estimated load of the service instance.

[0059] In this embodiment, traffic forwarding is performed based on the service routing table constructed in step S10. After running for a period of time, if it is detected that the status of the service instance is unavailable, the service instance with the unavailable status is deleted from the service routing table; if the traffic of any service instance corresponding to the same service capability level increases significantly, if the new service request is still scheduled according to the original equivalent load sharing method, the load imbalance may be further aggravated. Therefore, the weight of each service instance in the service routing table needs to be updated to provide load balancing between the service instances.

[0060] In some specific embodiments, referring to Figure 4 , Figure 4 for Figure 1 Detailed flow chart of step S20 in FIG. Figure 4 As shown, step S20 includes:

[0061] Step S201: if it is determined that the status of the service instance is unavailable, the service instance with the unavailable status is deleted from the service routing table;

[0062] In this embodiment, traffic forwarding is performed based on the service routing table constructed in step S10, and the constructed initial service routing table is as follows:

[0063] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0064] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2, weight w1;

[0065] SID 1 Level 1, next hop computing power routing exit node 2 IP, business SID_S2, instance IP3, weight w2.

[0066] After running for a period of time, if the traffic of service instance 3 increases significantly and exceeds the computing processing capacity of service instance 3, service instance 3 will notify the real-time calculated λe and load threshold λmax to computing power routing exit node 2. If the actual load λe of service instance 3 is greater than or equal to λmax and lasts for the preset time T, the status of service instance 3 becomes unavailable (Red), and computing power routing exit node 2 notifies the current status of service instance 3 to computing power routing entry node 1 and computing power routing entry node 2. The service table maintained on computing power routing exit node 2 is currently updated from: service 1, service instance 3, IP3, SID 1 (Locator+Function)+Level 1, status (Green) to: service 1, service instance 3, IP3, SID 1 (Locator+Function)+Level 1, status (Red).

[0067] The computing power routing entry node 1 learns the service table update announced by the computing power routing exit node 2 through the extended BGP protocol, updates the routing next hop, and obtains the updated service routing table:

[0068] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0069] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2.

[0070] At this time, because service instance 3 is unavailable, it is deleted from the next hop table, and all new Level 1 service requests are dispatched to service instance 2. Service instance 3, which is in the unavailable state, is deleted from the service routing table to avoid dispatching new service requests to the unavailable service instance 3.

[0071] Step S202: If, among the service instances corresponding to the same service capability level, the absolute value of the difference between the estimated load of any service instance and the estimated load of the service instance at the last moment is greater than the product of the load of the service instance at the last moment multiplied by the change threshold, then the load average of the service instances corresponding to the same service capability level is calculated;

[0072] Step S203: Divide the load mean by the load of each service instance, and use the obtained quotient as the weight of each service instance corresponding to the same service capability level in the service routing table.

[0073] In this embodiment, traffic forwarding is performed based on the service routing table constructed in step S10, and the constructed initial service routing table is as follows:

[0074] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0075] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2, weight w1;

[0076] SID 1 Level 1, next hop computing power routing exit node 2 IP, business SID_S2, instance IP3, weight w2.

[0077] After running for a period of time, if the traffic dispatched to service instance 2 increases significantly, it is necessary to re-update the weights of each service instance in the service routing table for load balancing between the service instances. Specifically, if the traffic dispatched to service instance 2 increases significantly, that is, the current service instance 2 satisfies |Li_new-Li_old|>Li_old*X%, then update Li_old=Li_new, and notify the calculated load of the current service instance 2 to the computing power routing entry node 1, so that the computing power routing entry node 1 can perceive the significant increase in the traffic of service instance 2. The service-side capability service level corresponding to service instance 2 is Level 1, and the service instances corresponding to the service-side capability service level of Level 1 are service instance 2 and service instance 3. Therefore, it is also necessary to obtain the calculated load of the current service instance 3. Since the calculated load of service instance 3 has not been updated, the previous calculated load can be used.

[0078] The computing power routing entry node 1 learns the estimated load update of the service instances announced by the computing power routing exit nodes 1 and 2 through the extended BGP protocol, and records the estimated load of the current service instance 2 as L0, and the estimated load of the current service instance 3 as L1. The average load L of each service instance corresponding to the service level of the server capability Level 1 is calculated. Where n is the total number of service instances corresponding to the same service capability level, L i is the estimated load of the i-th service instance.

[0079] Divide the load average by the estimated load of the current service instance 2, and use the quotient as the weight w of service instance 2 in the service routing table. 1 ',Right now Divide the load average by the estimated load of the current service instance 3, and use the quotient as the weight w of service instance 3 in the service routing table. 2 ',Right now

[0080] The updated service routing table is as follows:

[0081] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0082] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2, weight w 1 ′;

[0083] SID 1 Level 1, next hop computing power routing exit node 2 IP, business SID_S2, instance IP3, weight w 2 ′.

[0084] The new weight w 1 ′ and w 2 ' is used as the weight for traffic load sharing. Traffic is shared according to the new weight during forwarding. New service requests are less likely to be dispatched to service instance 2, and more are dispatched to service instance 3. This balances the load between different instances and does not rely too much on status notifications of service instances.

[0085] In this embodiment, a service routing table is constructed based on the service table and service template, and the mapping of the service level Level of the service end capability to the service level Color of the network side is completed, so that the service capability and the network capability are matched. A hierarchical service routing method is adopted, which is easy to operate and manage, avoids the huge table item requirements of fine-grained traffic scheduling, meets the needs of users with different service levels, and provides differentiated services; based on the status of the service instance and the estimated load of the service instance, the service routing table is updated to balance the load between different instances and improve resource utilization. Through this embodiment, service requests of different levels are forwarded according to the next hop of their respective service routes, and service requests of the same level achieve load balancing of traffic between multiple non-equal load sharing paths, which improves resource utilization, meets the differentiated needs of users, and has a faster response speed and simpler deployment, solving the technical problem of low utilization of network and computing resources existing in related technologies.

[0086] Optionally, in one embodiment, the state of the service instance is determined based on the actual load of the service instance, and the estimated load of the service instance is obtained through a traffic statistics model.

[0087] In this embodiment, the processing capability of the service node for the request is calculated according to the status of the service instance, and there are two states: available and unavailable. The available state means that it can be used to process the service request, and the unavailable state means that it cannot be used to process the service request.

[0088] Select indicators λ1, λ2, λ3, ..., λn that can be used to represent the load level of the service instance, such as the number of supported service connections, available resources, CPU / GPU / NPU performance, and storage capacity. Set reasonable weight values ​​ω1, ω2, ω3, ..., ωn for each indicator, and comprehensively calculate the actual load λe of the service instance, which is defined as the system resource utilization. The quantization function of λe is expressed as: λe = ω1λ1 + ω2λ2 + ω3λ3 + ... ωnλn, where ω1 + ω2 + ω3 + ... + ωn = 1. For example, for a computing-intensive service, select CPU utilization and memory utilization to characterize the load level, with a weight of 0.5 for each, and the weighted sum of the two represents the system resource utilization of the service instance: λe = CPU utilization * 0.5 + memory utilization * 0.5.

[0089] The actual load of the service instance is calculated by using the indicators used to represent the load level of the service instance and the weights corresponding to each indicator. The actual load of the service instance is then compared with the load threshold of the service instance, and the status of the service instance can be determined based on the comparison result.

[0090] Multiple service instances of the same level of the same service can provide the service of the same level at the same time. Through the service routing table of UCMP, traffic can be scheduled according to the UCMP weight. According to the traffic sent to the service instance and the traffic received from the service instance, the traffic statistical model is used to obtain the statistical value of each preset parameter of the service instance and the weight corresponding to each preset parameter statistical value. Then, based on the statistical value of each preset parameter of the service instance and the weight corresponding to each preset parameter statistical value, the estimated load of the service instance can be calculated.

[0091] Optionally, in one embodiment, the step of determining the state of the service instance based on the actual load of the service instance includes:

[0092] In the initial state, the actual load of the service instance is compared with the load threshold value of the service instance to obtain a comparison result;

[0093] If the comparison result is that the actual load of the service instance is less than the load threshold of the service instance, determining that the status of the service instance is available;

[0094] If the comparison result is that the actual load of the service instance is greater than or equal to the load threshold of the service instance, the status of the service instance is determined to be unavailable.

[0095] In this embodiment, the actual load λe of the service instance when the performance is degraded is selected as the load threshold value of the service instance, for example, the λe value when the service delay of the service instance cannot meet the requirement, or a preset value is used as the load threshold value of the service instance. The load threshold value of the service instance is used to determine whether the service instance can continue to provide services.

[0096] Initial state: When the actual load λe of the service instance is less than the load threshold λmax of the service instance, the state of the service instance is determined to be available (Green).

[0097] When the actual load λe of the service instance is greater than or equal to λmax, the state of the service instance is determined to be unavailable (Red).

[0098] Optionally, in one embodiment, the step of obtaining the estimated load of the service instance through the traffic statistics model includes:

[0099] Obtain statistical values ​​of each preset parameter of the service instance through the traffic statistical model;

[0100] Multiply each preset parameter statistic of the service instance by the weight corresponding to each preset parameter statistic to obtain a product corresponding to each preset parameter statistic;

[0101] The products corresponding to the statistical values ​​of each preset parameter are accumulated to obtain the sum as the estimated load of the service instance.

[0102] In this embodiment, the traffic statistics method is adopted to count the total number of packets to the service instance (ToPackets), the total number of packets from the service instance (FromPackets), the number of bytes of packets to the service instance (ToBytes), and the number of bytes of packets from the service instance (FromBytes) through the traffic statistics model. The load Li inferred by the first router to a certain service instance can be calculated based on one of the above statistical values ​​or all four statistical values ​​(with different weights wi):

[0103] Li=(w1*ToPackets+w2*FromPackes+w3*ToBytes+w4*FromBytes);

[0104] In the formula, 0<=wi<=1 and w1+w2+w3+w4=1.

[0105] The weight of each statistical value can be configured or adjusted by self-learning. For example, for interactive applications, the outbound traffic and the return traffic can each account for half, and for non-interactive traffic, only the outbound traffic can be considered. Different applications can count the number of bytes, the number of packets, or a combination of the two. Therefore, the selection of the weight value is related to the application.

[0106] Specifically, taking service instance n as an example, service instance n:

[0107] Service A, Level i, {ToPackets,FromPackes,ToBytes,FromBytes}, {w1,w2,w3,w4}, sampling period: M1, change threshold: X%.

[0108] Specific calculation process:

[0109] Li is initialized to 0, Li_old = Li;

[0110] The first router collects parameters with non-zero weights in the traffic statistics model according to the sampling period M1, and calculates the estimated load Li_new of the service instance according to the formula Li=(w1*ToPackets+w2*FromPackes+w3*ToBytes+w4*FromBytes).

[0111] Further, when |Li_new-Li_old|<=Li_old*X%, the first router does not advertise Li_new to the second router;

[0112] When |Li_new-Li_old|>Li_old*X%, the first router notifies Li_new to the second router, and the first router updates Li_old=Li_new, where Li_old is the estimated load of the service instance at the last moment.

[0113] Optionally, in one embodiment, referring to Figure 5 , Figure 5 FIG. 2 is a flow chart of another embodiment of the service routing table management method of the present invention. Figure 5 As shown, after step S20, the following steps are included:

[0114] Step S30: If the actual load of the service instance in the available state is greater than or equal to the load threshold of the service instance and lasts for a preset time period, the available state of the service instance is changed to the unavailable state.

[0115] In this embodiment, the service routing table updated in step S20 is used as the current service routing table, and traffic forwarding is performed based on the current service routing. If the current service routing table is:

[0116] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0117] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2, weight w 1 ′;

[0118] SID 1 Level 1, next hop computing power routing exit node 2 IP, business SID_S2, instance IP3, weight w 2 ′.

[0119] If the actual load λe of the service instance 2 in the available state is greater than or equal to the load threshold λmax of the service instance and lasts for a preset time, the available state of the service instance 2 is changed to the unavailable state. Then, step S201 is executed again, and if it is determined that the state of the service instance is unavailable, the service instance in the unavailable state is deleted from the service routing table.

[0120] Optionally, in one embodiment, continue to refer to Figure 5 , after step S20, comprising:

[0121] Step S40: If the actual load of the service instance in the unavailable state is less than the load threshold of the service instance and lasts for a preset time, the unavailable state of the service instance is changed to the available state;

[0122] Step S50: Add the service instance in the available state to the service routing table, and reallocate the weight of each service instance corresponding to the service capability level to which the service instance belongs.

[0123] In this embodiment, the service routing table updated in step S20 is used as the current service routing table, and traffic forwarding is performed based on the current service routing. If the current service routing table is:

[0124] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0125] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2.

[0126] If the actual load λe of the service instance 3 in the unavailable state is less than the load threshold λmax of the service instance and lasts for a preset time period T, the unavailable state of the service instance 3 is changed to the available state;

[0127] The service instance 3 in the available state is added to the service routing table, and the weights of each service instance corresponding to the service capability level to which the service instance belongs are reallocated, that is, the weights of the service instance 2 and the service instance 3 corresponding to the server capability service level Level 1 to which the service instance 3 belongs are reallocated. Specifically, if the estimated loads of the service instance 2 and the service instance 3 both satisfy |Li_new-Li_old|<=Li_old*X%, the weights of the service instance 2 and the service instance 3 are equal. If the estimated load of the service instance 2 and / or the estimated load of the service instance 3 satisfies |Li_new-Li_old|>Li_old*X%, the load average of each service instance (service instance 2 and service instance 3) corresponding to the server capability service level Level 1 is calculated, and then the load average is divided by the load of the service instance 2, and the quotient obtained is used as the weight of the service instance 2, and the load average is divided by the load of the service instance 3, and the quotient obtained is used as the weight of the service instance 3.

[0128] Optionally, in one embodiment, after step S20, the following steps are included:

[0129] Service requests of different service capability levels are forwarded according to the next hop of their respective service routes based on the updated service routing table;

[0130] Service requests of the same service capability level are forwarded among multiple unequal-value load sharing paths based on the updated service routing table.

[0131] In this embodiment, the updated service routing table is:

[0132] SID 1 Level 0, next hop computing power routing exit node 1 IP, business SID_S1, instance IP1;

[0133] SID 1 Level 1, next hop computing power routing exit node 1 IP, business SID_S1, instance IP2, weight w 1 ′;

[0134] SID 1 Level 1, next hop computing power routing exit node 2 IP, business SID_S2, instance IP3, weight w 2 ′.

[0135] For service requests with service capability levels of Level 0 and Level 1, service requests with service capability level 0 are forwarded according to instance IP1 corresponding to service capability level 0; service requests with service capability level 1 are forwarded according to instance IP2 and instance IP3 corresponding to service capability level 1.

[0136] For a service request with a service capability level of Level 1, the instance IP2 and instance IP3 corresponding to the service capability level of Level 1 form a UCMP (Unequal Cost Multiple Path, non-equal load sharing) path. 1 ′ and the weight w corresponding to instance IP3 2 'Forward traffic and achieve weighted load balancing of traffic.

[0137] In a second aspect, an embodiment of the present invention further provides a service routing table management device.

[0138] In one embodiment, referring to Figure 6 , Figure 6 This is a functional module diagram of an embodiment of a service routing table management device of the present invention. Figure 6 As shown, the service routing table management device includes:

[0139] A routing table building module 10 is configured to build a service routing table based on the service table and the service template;

[0140] The information updating module 20 is configured to update the service routing table based on the status of the service instance and the estimated load of the service instance.

[0141] Optionally, in one embodiment, the routing table construction module 10 is configured to:

[0142] Determine the service level of the server capability corresponding to each service instance based on the service table;

[0143] Determine the network-side service level corresponding to each server-side capability service level based on the service template;

[0144] The next hop is calculated by each network-side service level and the forwarding path is iterated to obtain the service routing table.

[0145] Optionally, in one embodiment, the state of the service instance is determined based on the actual load of the service instance, and the estimated load of the service instance is obtained through a traffic statistics model.

[0146] Optionally, in one embodiment, the service routing table management device further includes an information determination module configured to:

[0147] In the initial state, the actual load of the service instance is compared with the load threshold value of the service instance to obtain a comparison result;

[0148] If the comparison result is that the actual load of the service instance is less than the load threshold of the service instance, determining that the status of the service instance is available;

[0149] If the comparison result is that the actual load of the service instance is greater than or equal to the load threshold of the service instance, the status of the service instance is determined to be unavailable.

[0150] Optionally, in one embodiment, the information determination module is further configured to:

[0151] Obtain statistical values ​​of each preset parameter of the service instance through the traffic statistical model;

[0152] Multiply each preset parameter statistic of the service instance by the weight corresponding to each preset parameter statistic to obtain a product corresponding to each preset parameter statistic;

[0153] The products corresponding to the statistical values ​​of each preset parameter are accumulated to obtain the sum as the estimated load of the service instance.

[0154] Optionally, in one embodiment, the information updating module 20 is configured to:

[0155] If it is determined that the status of the service instance is unavailable, the service instance with the unavailable status is deleted from the service routing table;

[0156] If, among the service instances corresponding to the same service capability level, the absolute value of the difference between the estimated load of any service instance and the estimated load of the service instance at the previous moment is greater than the product of the load of the service instance at the previous moment multiplied by the change threshold, then the load average of the service instances corresponding to the same service capability level is calculated;

[0157] The load mean is divided by the load of each service instance, and the obtained quotient is used as the weight of each service instance corresponding to the same service capability level in the service routing table.

[0158] Optionally, in one embodiment, the information updating module 20 is further configured to:

[0159] If the actual load of a service instance in the available state is greater than or equal to the load threshold of the service instance and lasts for a preset period of time, the available state of the service instance is changed to the unavailable state.

[0160] Optionally, in one embodiment, the information updating module 20 is further configured to:

[0161] If the actual load of the service instance in the unavailable state is less than the load threshold of the service instance and lasts for a preset period of time, the unavailable state of the service instance is changed to the available state;

[0162] The service instances with the available status are added to the service routing table, and the weights of the service instances corresponding to the service capability level to which the service instances belong are reallocated.

[0163] Among them, the functional implementation of each module in the above-mentioned service routing table management device corresponds to each step in the above-mentioned service routing table management method embodiment, and its functions and implementation processes are no longer repeated here one by one.

[0164] In a third aspect, an embodiment of the present invention further provides an electronic device, whose structure is as follows: Figure 7 As shown, it includes: a memory and a processor, wherein the processor is used to read and execute a computer program stored in the memory to implement the aforementioned service routing table management method.

[0165] In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions, when executed, implement the aforementioned service routing table management method.

[0166] In a fifth aspect, an embodiment of the present invention provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned service routing table management method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0167] Finally, it should be noted that: in some processes described in the embodiments of the present invention, multiple operations or steps appearing in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present invention or may be executed in parallel, and the sequence number of the operation is only used to distinguish between different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0168] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments, or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A service routing table management method, characterized in that: The method comprises: Build a service routing table based on the service table and service template; The service routing table is updated based on the status of the service instance and the inferred load of the service instance.

2. The service routing table management method according to claim 1, characterized in that: The step of constructing a service routing table based on the service table and the service template includes: Determine the service level of the server capability corresponding to each service instance based on the service table; Determine the network-side service level corresponding to each server-side capability service level based on the service template; The next hop is calculated by each network-side service level and the forwarding path is iterated to obtain the service routing table.

3. The service routing table management method according to claim 1, characterized in that: The state of the service instance is determined based on the actual load of the service instance, and the estimated load of the service instance is obtained through a traffic statistics model.

4. The service routing table management method according to claim 3, characterized in that: The steps of determining the status of the service instance based on the actual load of the service instance include: In the initial state, the actual load of the service instance is compared with the load threshold value of the service instance to obtain a comparison result; If the comparison result is that the actual load of the service instance is less than the load threshold of the service instance, determining that the status of the service instance is available; If the comparison result is that the actual load of the service instance is greater than or equal to the load threshold of the service instance, the status of the service instance is determined to be unavailable.

5. The service routing table management method according to claim 3, characterized in that: The steps of obtaining the estimated load of the service instance through the traffic statistics model include: Obtain statistical values ​​of each preset parameter of the service instance through the traffic statistical model; Multiply each preset parameter statistic of the service instance by the weight corresponding to each preset parameter statistic to obtain a product corresponding to each preset parameter statistic; The products corresponding to the statistical values ​​of each preset parameter are accumulated to obtain the sum as the estimated load of the service instance.

6. The service routing table management method according to claim 1, characterized in that: The step of updating the service routing table based on the status of the service instance and the estimated load of the service instance comprises: If it is determined that the status of the service instance is unavailable, the service instance with the unavailable status is deleted from the service routing table; If, among the service instances corresponding to the same service capability level, the absolute value of the difference between the estimated load of any service instance and the estimated load of the service instance at the previous moment is greater than the product of the load of the service instance at the previous moment multiplied by the change threshold, then the load average of the service instances corresponding to the same service capability level is calculated; The load mean is divided by the load of each service instance, and the obtained quotient is used as the weight of each service instance corresponding to the same service capability level in the service routing table.

7. The service routing table management method according to any one of claims 1 to 6, characterized in that: After the step of updating the service routing table based on the state of the service instance and the estimated load of the service instance, the following steps are included: If the actual load of a service instance in the available state is greater than or equal to the load threshold of the service instance and lasts for a preset period of time, the available state of the service instance is changed to the unavailable state.

8. The service routing table management method according to any one of claims 1 to 6, characterized in that: After the step of updating the service routing table based on the state of the service instance and the estimated load of the service instance, the following steps are included: If the actual load of the service instance in the unavailable state is less than the load threshold of the service instance and lasts for a preset period of time, the unavailable state of the service instance is changed to the available state; The service instances with the available status are added to the service routing table, and the weights of the service instances corresponding to the service capability level to which the service instances belong are reallocated.

9. The service routing table management method according to claim 1, characterized in that: After the step of updating the service routing table based on the state of the service instance and the estimated load of the service instance, the following steps are included: Service requests of different service capability levels are forwarded according to the next hop of their respective service routes based on the updated service routing table; Service requests of the same service capability level are forwarded among multiple unequal-value load sharing paths based on the updated service routing table.

10. A service routing table management device, characterized in that: The device comprises: A routing table building module, configured to build a service routing table based on the service table and the service template; The information updating module is configured to update the service routing table based on the status of the service instance and the estimated load of the service instance.

Images