A method and system for controlling routing within a trust domain

Abstract

The application relates to a method and system for controlling routing selection in a trust domain, and belongs to the technical field of communication. The method comprises the following steps: defining a target Large community attribute, the target Large community attribute comprising an identifier field, a first field and a second field; based on peer configuration, when a routing receiving end receives a target Large community attribute published by a routing publishing end, judging whether the routing receiving end and the routing publishing end are in the same trust domain; when the routing receiving end and the routing publishing end are in the same trust domain, obtaining a target route in the routing receiving end; when target Large community attribute transmission is carried out based on the target route, determining a routing priority of the target route, and selecting the route based on the routing priority. The method can select the route based on the routing priority, and ensures efficient transmission of network traffic.

Description

Technical Field

[0001] This invention belongs to the field of communication technology, and in particular relates to a method and system for controlling routing within a trust domain. Background Technology

[0002] In related technologies, different units within the same organization possess multiple Autonomous Systems (AS). During daily operation and maintenance, traffic between different AS systems constantly interacts. Considering geographical attributes, link bandwidth, latency, and service planning and deployment, network administrators do not want all cross-domain traffic to directly connect to the peer ASBR via their own ASBR. For some traffic, a route is designed to detour to the local PE node before reaching the peer ASBR. Different path planning requirements necessitate refined deployment by network administrators to achieve differentiated routing. Therefore, how to better implement routing within trusted domains has become a pressing issue. Summary of the Invention

[0003] In view of the shortcomings of the prior art, the purpose of this invention is to provide a method and system for controlling routing within a trust domain. This method can select routes based on routing priorities, ensuring efficient transmission of network traffic.

[0004] In a first aspect, the present invention proposes a method for controlling route selection within a trust domain, comprising: S1, defining a target Large community attribute, the target Large community attribute including an identifier field, a first field, and a second field; S2, based on peer configuration, when a route receiving end receives the target Large community attribute published by a route publishing end, determining whether the route receiving end and the route publishing end are in the same trust domain; S3, if the route receiving end and the route publishing end are in the same trust domain, obtaining a target route in the route receiving end; S4, if the target Large community attribute is passed based on the target route, determining the route priority of the target route, and selecting a route based on the route priority.

[0005] Further, obtaining the target route in the routing receiver includes: obtaining a first route carrying the target Large community attribute from multiple candidate routes in the routing receiver, wherein the first route includes multiple routes; obtaining the target byte value of the first field in the multiple first routes; and taking the first route corresponding to the smallest value of the target byte value of the first field in the multiple first routes as the target route.

[0006] Furthermore, it also includes: when the target Large community attribute carried in the plurality of candidate routes is the same, comparing other attributes carried in the plurality of candidate routes besides the target Large community attribute based on preset rules, and determining the target route based on the comparison results.

[0007] Further, obtaining the target route in the route receiving end includes: obtaining a first route carrying the target Large community attribute among multiple candidate routes in the route receiving end; and using the first route as the target route.

[0008] Furthermore, when the target Large community attribute is passed based on the target route, determining the route priority of the target route includes: determining the target source of the target route for passing the target Large community attribute; if the target source remains unchanged, the priority of the target route remains unchanged; if the target source changes, the priority of the target route is changed based on a preset configuration.

[0009] Further, determining the priority of the target route includes: determining the priority of the target route based on network performance parameters within the trust domain, wherein the network performance parameters include link bandwidth utilization, packet loss rate, and latency; or customizing the priority of the target route.

[0010] Furthermore, it also includes: obtaining a first route carrying the target Largecommunity attribute from multiple candidate routes in the route receiving end; obtaining routes carrying functional fields from the first route; and aggregating the routes.

[0011] A second aspect of the present invention provides a system for controlling routing selection within a trust domain, comprising: a definition module for defining a target Large community attribute, the target Large community attribute including an identifier field, a first field, and a second field; a judgment module for determining, based on peer configuration, whether a routing receiver and a routing publisher belong to the same trust domain when the routing receiver receives the target Large community attribute published by a routing publisher; an acquisition module for acquiring a target route in the routing receiver when the routing receiver and the routing publisher belong to the same trust domain; and a determination module for determining the route priority of the target route and selecting a route based on the route priority when the target Large community attribute is passed based on the target route.

[0012] A third aspect of the present invention provides an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method described in any one aspect of the present invention.

[0013] A fourth aspect of the present invention provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method described in any one of the first aspects of the present invention.

[0014] The beneficial effects of this invention are as follows:

[0015] The method and system for controlling routing within a trust domain as described in this invention define a target Large community attribute, which includes an identifier field, a first field, and a second field. Based on peer configuration, when a routing receiver receives the target Large community attribute published by a routing publisher, it determines whether the routing receiver and the routing publisher belong to the same trust domain. If the routing receiver and the routing publisher belong to the same trust domain, the target route is obtained from the routing receiver. When the target Large community attribute is passed based on the target route, the route priority of the target route is determined, and routing is selected based on the route priority. This method enables routing based on route priority, ensuring efficient transmission of network traffic. Attached Figure Description

[0016] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts. It is obvious that the drawings described below are merely some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings.

[0017] Figure 1 This is a flowchart of a method for control routing within a trust domain according to an embodiment of the present invention;

[0018] Figure 2 This is a flowchart of a method for control routing within a trust domain according to a specific embodiment of the present invention;

[0019] Figure 3 This is a schematic diagram of a first type of scenario control routing selection according to an embodiment of the present invention;

[0020] Figure 4 This is a schematic diagram of a second type of scenario control routing selection according to an embodiment of the present invention;

[0021] Figure 5 This is a schematic diagram of a system for controlling routing within a trust domain according to an embodiment of the present invention;

[0022] Figure 6 This is a structural block diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0023] To enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. It should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0024] Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts disclosed in this invention.

[0025] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance. The terms "installed," "connected," and "linked" should be interpreted broadly; for example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal communication of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0026] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of methods and systems consistent with some aspects of the invention as detailed in the appended claims.

[0027] This invention proposes a method, system, and related devices for control routing within a trust domain. Specifically, the method, system, and related devices for control routing within a trust domain according to embodiments of this invention are described below with reference to the accompanying drawings.

[0028] Figure 1 This is a flowchart of a method for intra-trust domain control routing selection according to an embodiment of the present invention. It should be noted that the intra-trust domain control routing selection method of the present invention can be applied to the intra-trust domain control routing selection system of the present invention. This intra-trust domain control routing selection system can be configured on an electronic device or in a server. This application does not limit the scope of the application.

[0029] like Figure 1 As shown, the method for controlling routing within a trust domain includes:

[0030] S110, define the target Large community attribute, which includes an identifier field, a first field, and a second field.

[0031] In an embodiment of the present invention, the target Large community attribute is divided into three parts: an identifier field, a first field, and a second field. The identifier field is the source AS when the route is generated. The first field is supplemented with a field that can identify the route priority. The second field is the router-id value of the router to which the route is introduced or the sequence number planned by the administrator.

[0032] S120, based on peer configuration, when the routing receiver receives the target Largecommunity attribute published by the routing publisher, it determines whether the routing receiver and the routing publisher are in the same trust domain.

[0033] The peer configuration can be pre-defined. For example, route publisher A can pre-define trust domain members including route receiver B and route receiver C. When route receiver B and route receiver C receive the target Large community attribute published by route publisher A, it can be determined that route publisher A and route receiver B and route receiver C are in the same trust domain.

[0034] Among them, peer configuration can ensure that the target Large community attribute is effective within the trusted domain and is not published outside the trusted domain, thus preventing other autonomous systems from knowing the internal implementation. At the same time, when peer neighbors in other non-trusted domains publish this attribute, they will not be processed according to the route carrying the route priority, thus preventing traffic from being hijacked.

[0035] S130: If the route receiver and the route publisher are in the same trust domain, obtain the target route from the route receiver.

[0036] In embodiments of the present invention, when the route receiving end and the route publishing end are in the same trust domain, the target route can be determined from multiple candidate routes in the route receiving end. Specific implementation details can be found in subsequent embodiments.

[0037] S140, when passing the target Large community attribute based on the target route, determine the route priority of the target route and select a route based on the route priority.

[0038] In embodiments of the present invention, when passing the target Large community attribute based on the target route, the target source of the target route for passing the target Large community attribute is determined, and the priority of the target route is determined based on the target source. Then, route selection is performed based on the priority of the target route. Specific implementation details can be found in subsequent embodiments.

[0039] According to an embodiment of the present invention, a method for controlling routing within a trust domain defines a target Large community attribute, which includes an identifier field, a first field, and a second field. Based on peer configuration, when a routing receiver receives a target Large community attribute published by a routing publisher, it determines whether the routing receiver and the routing publisher belong to the same trust domain. If the routing receiver and the routing publisher belong to the same trust domain, the target route is obtained from the routing receiver. When the target Large community attribute is passed based on the target route, the route priority of the target route is determined, and routing is selected based on the route priority. This method enables routing based on route priority, ensuring efficient transmission of network traffic.

[0040] To enable those skilled in the art to more readily understand the present invention, Figure 2 This is a method for controlling routing within a trust domain according to a specific embodiment of the present invention, such as... Figure 2 As shown, the method for controlling routing within this trust domain includes:

[0041] S210, define the target Large community attribute, which includes an identifier field, a first field, and a second field.

[0042] S220, based on peer configuration, when the routing receiver receives the Large community attribute published by the routing publisher, it determines whether the routing receiver and the routing publisher are in the same trust domain.

[0043] In the embodiments of the present invention, the implementation of steps S210-S220 can refer to the implementation of steps S110-S120 described above, and the present invention will not repeat the details.

[0044] S230: When the route receiver and the route advertiser are in the same trust domain, obtain the target route from the route receiver.

[0045] In an embodiment of the present invention, when the route receiving end and the route publishing end are in the same trust domain, the first route carrying the target Large community attribute among multiple candidate routes in the route receiving end is obtained, and the first route includes multiple routes; the target byte value of the first field in the multiple first routes is obtained; and the first route corresponding to the smallest value of the target byte value of the first field in the multiple first routes is taken as the target route.

[0046] In other words, when the route receiver and the route advertiser belong to the same trust domain, the multiple candidate routes participating in route selection at the route receiver all carry a target Large community attribute. This means that multiple candidate routes are treated as multiple first routes, and the target route is determined by comparing the target byte value of the first field in these multiple first routes. The target byte value of the first field ranges from 0 to 65535.

[0047] In an embodiment of the present invention, when multiple candidate routes carry the same target large community attribute, the other attributes carried by the multiple candidate routes besides the target large community attribute are compared based on a preset rule, and the target route is determined based on the comparison result.

[0048] The "other attributes" section refers to attributes used for routing in other BGP protocols. Preset rules include, but are not limited to, comparing numerical values ​​and comparison types. In other words, among multiple candidate routes, the other attributes of each candidate route are compared one by one based on the preset rules.

[0049] In one embodiment of the present invention, when the routing receiver and the routing publisher are in the same trust domain, the first route carrying the target Large community attribute is obtained from multiple candidate routes in the routing receiver; the first route is used as the target route.

[0050] In other words, when the route receiver and the route publisher are in the same trust domain, some of the candidate routes participating in route selection in the route receiver carry the target Large community attribute, and the route corresponding to the part carrying the target Large community attribute is taken as the first route, that is, the first route is taken as the target route.

[0051] S240, when passing the target Large community attribute based on the target route, determine the route priority of the target route.

[0052] In an embodiment of the present invention, the target source for the target route to pass the target Large community attribute is determined; if the target source remains unchanged, the priority of the target route remains unchanged; if the target source changes, the priority of the target route is changed based on a preset configuration.

[0053] The target source can be preset. For example, the target routes include routes A, B, and C. When routes A, B, and C pass the target Large community attribute, route A is passed to route B, meaning the target source of route B is route A. When route B is passed to route C, the target source of route C is either route A or route B. When the target source of route C is route A, the priority of the target route can be determined to remain unchanged, meaning the priority of route C is the priority carried by route A. When the target source of route C is route B, the priority of route C can be changed based on the preset configuration.

[0054] In one embodiment of the present invention, the priority of the target route is determined based on network performance parameters within the trust domain, including link bandwidth utilization, packet loss rate, and latency; or the priority of the target route can be customized.

[0055] S250 selects routes based on routing priority.

[0056] In one embodiment of the present invention, a first route carrying a target Largecommunity attribute is obtained from multiple candidate routes in the routing receiver; routes carrying functional fields are obtained from the first route, and the routes are aggregated. For example, if there are two routes carrying functional fields, these two routes can be merged into one route, wherein the attribute carrying the functional field is lost after aggregation, while other fields of the target Largecommunity attribute are unaffected.

[0057] In one specific embodiment of the present invention, a target Large community attribute with routing priority functionality is used to control route selection. This attribute can address scenarios that can be categorized into two main types.

[0058] In the first scenario, within the trusted domain, between two adjacent autonomous systems 65530 and 65531, for traffic entering autonomous system 65531, the network administrator plans to bypass the local router B to enter this autonomous system.

[0059] like Figure 3As shown: 1. Within Autonomous System 65531, Router A advertises a route. The route advertised to the reflector carries a priority of 50, and the route advertised to neighboring Autonomous System Router C carries a priority of 100. 2. Based on the directions of Router A, the reflector, and Router B, after the route reaches the reflector, it is advertised to Router B, carrying a local priority of 50 (unchanged after passing through the reflector). 3. Router B forwards this route to the neighboring Autonomous System. If this attribute is not modified, the priority of the route received by the router remains 50. 4. Based on the directions of Router A and Router C, the route advertised by Router A to the neighboring Autonomous System carries a priority of 100. 5. Router C and Router D receive routes with priorities of 100 and 50 respectively. After synchronizing the routes within the domain through the reflector, the routing results of Router C and Router D nodes are both route selections prioritizing routes with a priority of 50. Therefore, traffic destined for Autonomous System 65531 will ultimately exit through Router D, thus achieving the goal of controlling traffic entering 65531.

[0060] In summary, within a trusted domain, routing is controlled by the route priority carried by the control route, which ultimately determines the entry point for traffic into the target autonomous system.

[0061] In the second scenario, within the trust domain, network administrators can automatically or manually set the routing priority of each node based on factors such as link bandwidth, packet loss rate, latency, and geographical location, using a neighbor-based approach. Higher-quality paths have lower routing priorities. These priorities accumulate during routing, and the final path selection is based on the accumulated priorities.

[0062] like Figure 4As shown, 1. Router E initially advertises a route with a priority of 0. The route priority is then set in the outbound direction from neighboring systems. This priority is calculated based on factors such as link bandwidth, latency, and packet loss rate within the trust domain. Assuming the calculated priority is 10 for Router E to Router C and 5 for Router E to Router F, the routes advertised from Autonomous System 65532 to Autonomous System 65531 carry two paths with priorities of 10 and 15 respectively. 2. After the route reaches Autonomous System 65531, Router C has two routes: one learned from Router E with a priority of 10, and the other learned from Router E... Router D learns a route with a priority of 30 (the cumulative values ​​of E->F, F->D, and D->C are 5+10+15, which equals 30). It prioritizes the route advertised by router E. Similarly, router D prioritizes the route learned from router F. After this selection process, it continues to advertise routes to autonomous system 65530. 3. After the route reaches autonomous system 65530, router A has two routes: one learned from router C with a priority of 40, and the other learned from router B with a priority of 35. Therefore, it will prioritize the route learned from router B. This completes the accumulation of route priorities and route selection on the routing control plane for the entire path.

[0063] Based on the simulated routing priorities described above, when traffic enters autonomous system 65530 from routers in other untrusted domains, the traffic path calculated according to the routing priorities is: Router A -> Router B -> Router D -> Router F -> Router E.

[0064] Therefore, the target Large community attribute can remain unchanged during transmission to determine the path decision, or it can be accumulated by the administrator after comprehensively calculating factors such as existing link bandwidth, tunnel type, latency, packet loss rate and regional requirements, and finally achieve traffic forwarding on a low-consumption path that conforms to the network administrator's plan.

[0065] The method for controlling routing within a trust domain according to embodiments of the present invention, by defining a target Largecommunity attribute, including an identifier field, a first field (for identifying route priority), and a second field (for identifying the router-id or sequence number to which the route is introduced), achieves fine-grained control of traffic within the trust domain. Network administrators can set different priorities for different routes according to actual needs, thereby controlling the flow and path of traffic. This method allows network administrators to dynamically adjust route priorities based on network performance parameters (such as link bandwidth utilization, packet loss rate, latency, etc.) or custom rules. This flexibility helps network administrators respond quickly to network changes and optimize network performance. Through a routing mechanism based on route priority, the network can select a higher-quality path for data transmission, thereby reducing the risk of data transmission interruption due to network failures or performance degradation. Simultaneously, this method also supports route aggregation, further improving network reliability and stability. Furthermore, this method supports dynamic adjustment of route priorities based on preset rules and custom configurations, providing strong support for network automation. Network administrators can write scripts or utilize existing tools to automate route priority management, further improving the efficiency and accuracy of network management. This method is designed to consider various scenarios and needs within a trust domain, and through flexible configuration and adjustment of route priorities, it can adapt to network environments of different sizes and complexities. This makes the method more scalable and adaptable in large, complex network environments.

[0066] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0067] According to one aspect of the present invention, a system for controlling routing within a trust domain is also proposed. Figure 5 This is a schematic diagram of a system for controlling routing within a trust domain according to an embodiment of the present invention; as shown. Figure 5 As shown, it includes:

[0068] Definition module 510 is used to define a target Large community attribute, the target Large community attribute including an identifier field, a first field, and a second field;

[0069] The judgment module 520 is used to determine whether the route receiver and the route publisher are in the same trust domain based on the peer configuration and when the route receiver receives the target Large community attribute published by the route publisher.

[0070] The acquisition module 530 is used to acquire the target route in the route receiving end when the route receiving end and the route publishing end are in the same trust domain;

[0071] The determination module 540 is used to determine the route priority of the target route and select a route based on the route priority when the target Large community attribute is passed based on the target route.

[0072] According to an embodiment of the present invention, a system for controlling routing within a trust domain defines a target large community attribute, which includes an identifier field, a first field, and a second field. Based on peer configuration, when a routing receiver receives a target large community attribute published by a routing publisher, it determines whether the routing receiver and the routing publisher belong to the same trust domain. If the routing receiver and the routing publisher belong to the same trust domain, the system obtains the target route from the routing receiver. When the target large community attribute is passed based on the target route, the system determines the route priority of the target route and selects a route based on the route priority. This enables routing based on route priority, ensuring efficient transmission of network traffic.

[0073] Optionally, the acquisition module 530 is specifically used to acquire a first route carrying the target Large community attribute among multiple candidate routes in the routing receiver, wherein the first route includes multiple routes; acquire the target byte value of the first field in the multiple first routes; and take the first route corresponding to the smallest value of the target byte value of the first field in the multiple first routes as the target route.

[0074] Optionally, the acquisition module 530 is specifically used to compare other attributes carried in the multiple candidate routes besides the target Large community attribute based on preset rules when the target Large community attribute is the same, and to determine the target route based on the comparison result.

[0075] Optionally, the acquisition module 530 is specifically used to acquire the first route carrying the target Large community attribute among multiple candidate routes in the route receiving end; and to use the first route as the target route.

[0076] Optionally, the determining module 540 is specifically used to determine the target source for the target route to pass the target Largecommunity attribute; if the target source remains unchanged, the priority of the target route remains unchanged; if the target source changes, the priority of the target route is changed based on a preset configuration.

[0077] Optionally, the determining module 540 is specifically used to determine the priority of the target route based on network performance parameters within the trust domain, wherein the network performance parameters include link bandwidth utilization, packet loss rate, and latency; or to customize the priority of the target route.

[0078] Optionally, the system further includes an aggregation module, configured to obtain a first route carrying the target Large community attribute from multiple candidate routes in the route receiving end; obtain routes carrying functional fields from the first route; and aggregate the routes.

[0079] According to one aspect of the present invention, an electronic device is provided.

[0080] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Figure 6 As shown, an electronic device may include one or more ( Figure 6 Only one is shown in the image. A processor 102 (which may include, but is not limited to, a microprocessor unit (MPU) or a programmable logic device (PLD)) and a memory 104 for storing data are also shown. In one exemplary embodiment, the electronic device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 6 The structure shown is for illustrative purposes only and does not limit the structure of the terminal device described above. For example, the terminal device may also include components that are more... Figure 6 The more or fewer components shown, or having the same Figure 6 Equivalent functions or ratios shown Figure 6 The functions shown have more different configurations.

[0081] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the trust domain control routing method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to terminal devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0082] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the switching device. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0083] This invention proposes a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform a method for controlling routing within a trust domain.

[0084] The applicant of this invention has provided a detailed description of the embodiments of the invention in conjunction with the accompanying drawings. However, those skilled in the art should understand that the above embodiments are merely preferred embodiments of the invention. The detailed description is only intended to help readers better understand the spirit of the invention and is not intended to limit the scope of protection of the invention. On the contrary, any improvements or modifications made based on the inventive spirit of the invention should fall within the scope of protection of the invention.

[0085] Furthermore, the functional units in the various embodiments of the present invention can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0086] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.

[0087] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, and are not intended to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the protection scope of the present invention.

Claims

1. A method of controlling routing selection within a trust domain, characterized by, The method comprises the following steps: S1, defining a target Large community attribute, wherein the target Large community attribute comprises an identifier field, a first field and a second field; S2, based on peer configuration, if the receiving end receives the target Large community attribute published by the publishing end, determining whether the receiving end and the publishing end are in the same trust domain; S3, if the receiving end and the publishing end are in the same trust domain, obtaining a target route in the receiving end; S4, if the target Large community attribute is transmitted based on the target route, determining a route priority of the target route, and routing based on the route priority.

2. The method for controlling routing within a trust domain according to claim 1, wherein, The method for obtaining the target route in the receiving end comprises the following steps: Obtaining a first route carrying the target Large community attribute from a plurality of candidate routes in the receiving end, wherein the first route comprises a plurality of fields; Obtaining a target byte value of the first field from the plurality of first routes; Taking the first route corresponding to the minimum value of the target byte value of the first field in the plurality of first routes as the target route.

3. The method for controlling routing within a trust domain according to claim 2, wherein, The method further comprises the following steps: If the target Large community attribute carried in the plurality of candidate routes is the same, comparing other attributes carried in the plurality of candidate routes based on a preset rule, and determining the target route based on the comparison result.

4. The method for controlling routing within a trust domain according to claim 1, wherein, The method for obtaining the target route in the receiving end comprises the following steps: Obtaining a first route carrying the target Large community attribute from a plurality of candidate routes in the receiving end; Taking the first route as the target route.

5. The method for controlling routing within a trust domain according to claim 1, wherein, If the target Large community attribute is transmitted based on the target route, the method for determining the route priority of the target route comprises the following steps: Determining a target source of the target route for transmitting the target Large community attribute; If the target source is unchanged, the priority of the target route is unchanged; If the target source is changed, changing the priority of the target route based on a preset configuration.

6. The method for controlling routing within a trust domain according to claim 5, wherein, The method for determining the priority of the target route comprises the following steps: Determining the priority of the target route according to network performance parameters in the trust domain, wherein the network performance parameters comprise link bandwidth utilization, packet loss rate and time delay; or Customizing the priority of the target route.

7. The method for controlling routing within a trust domain according to claim 1, wherein, The method further comprises the following steps: Obtaining a first route carrying the target Large community attribute from a plurality of candidate routes in the receiving end; Obtaining a route carrying a function field from the first route, and aggregating the route.

8. A system for controlling routing within a trust domain, characterized in that, The method comprises the following steps: A defining module is configured to define a target Large community attribute, wherein the target Large community attribute comprises an identifier field, a first field and a second field; A judging module is configured to judge whether the route receiving end and the route publishing end are in the same trust domain based on peer configuration in a case where the route receiving end receives the target Large community attribute published by the route publishing end. An obtaining module is configured to obtain a target route in the route receiving end in a case where the route receiving end and the route publishing end are in the same trust domain. A determining module is configured to determine a route priority of the target route based on the target route in a case where the target Large community attribute is delivered based on the target route, and route selection based on the route priority.

9. An electronic device, comprising: Comprise: At least one processor; And The memory is in communication with the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having stored thereon computer instructions, wherein, The computer instructions are used to enable the computer to perform the method of any one of claims 1 to 7.

Images