CN114389996A - SRv6SID distribution method and device under resource-based multi-topology environment - Google Patents
SRv6SID distribution method and device under resource-based multi-topology environment Download PDFInfo
- Publication number
- CN114389996A CN114389996A CN202210005948.0A CN202210005948A CN114389996A CN 114389996 A CN114389996 A CN 114389996A CN 202210005948 A CN202210005948 A CN 202210005948A CN 114389996 A CN114389996 A CN 114389996A
- Authority
- CN
- China
- Prior art keywords
- topology
- resource
- sid
- vtn
- srv6sid
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/741—Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/34—Source routing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a method and a device for allocating SRv6SID in a resource-based multi-topology environment. The method mainly comprises the following steps: dividing the SID into topology ID + resource ID; searching corresponding service resources according to the received SID allocation request and allocating resource IDs; setting a requested VTN topology bitmap; the assigned SID is returned using the combination of Locator + topology ID + resource ID. The invention can greatly reduce the memory occupation and improve the distribution and release efficiency when the VTN corresponding to the multiple network slices distributes SID in the VPN + application deployment. On the other hand, the invention also solves the problem troubled by the industry at present, namely the problem of carrying the VTN ID.
Description
[ technical field ] A method for producing a semiconductor device
The present invention relates to the field of data communication SRv6, and in particular, to a method and an apparatus for SRv6SID assignment in a resource-based multi-topology environment.
[ background of the invention ]
With SRv6(Segment-Routing IPv6, IPv6 Segment Routing) Network slice and VPN (Virtual Private Network) + service deployment in a Network environment, a multiple VTN (Virtual Terminal Network, Network Virtual Terminal) Network will be introduced, each VTN Network has its own independent topology, and route calculation is performed according to a specific algorithm (constraints such as delay, packet loss, etc.). Each topology on a device node plans an independent Locator (location identity). This results in the assignment of SIDs (Segment identifiers) based on multiple locators for each topology on the device.
As shown in fig. 1, is an exemplary diagram of an SRv6 multi-topology network: there are two topologies in this network exemplified in the figure, respectively the top ( nodes 1, 2, 3, 4) network topology applying the flex-algo 128 algorithm and the bottom ( nodes 5, 6, 7, 8) network topology applying the flex-algo 129 algorithm. Nodes 0 and 9 exist in two network topologies at the same time, and the corresponding device nodes have the requirement of allocating SID for two different Locator segments where the two network topologies exist at the same time.
Both the traditional MPLS (Multi-Protocol Label Switching) Label allocation and the existing SRv6SID allocation are methods for resource allocation based on a Locator space, and the allocation algorithm is based on a segment + bitmap index allocation release algorithm. When the method is applied to the distribution of SIDs by multiple locators, more SIDs to be distributed are needed, and the problems of low distribution efficiency and high resource occupation are highlighted.
As shown in fig. 2, a diagram of conventional SRv6SID assignment is shown. First, it is necessary to explain: when the SID (in the format of IPv 6-like address format) is allocated from a Locator segment, the area of the whole Locator segment is divided into the allocated area and the unallocated area, the SID in the allocated area is occupied by other applicant, and the new SID can be allocated only in the unallocated area. In the figure, two Locator segments are shown as 100:: 64 and 200:: 64 respectively, and for the same resource, for example, vpn1,100:: 64 this Locator segment allocates 100::1 this SID of END.DT4 type to it, and 200:: 64 this Locator segment allocates 200::2 this SID of END.DT4 type to it. Thus, 100:/64 the SID to service resource allocation relationship maintained by this Locator segment is: 100: 1end.DT4 to vpn 1; 200: 64 the distribution relationship between SID maintained by this Locator segment and service resource is: 200: 2end.DT4 to vpn 1. It can be seen that, for different Locator segments, the existing allocation methods need to maintain allocation relationships (SID < - > service resources) respectively, and occupy huge memory. This has the following consequences: each time of allocation and release, management resources of a plurality of Locator segments are needed, and the efficiency is low.
In view of this, how to overcome the defects in the prior art, and solve the problems of low allocation efficiency and high resource occupation of the existing SRv6SID allocation technology in a multi-topology multi-Locator network environment are the problems to be solved in the technical field.
[ summary of the invention ]
In view of the above drawbacks and needs of the prior art, the present invention provides a method and an apparatus for allocating SRv6SID in a resource-based multi-topology environment, wherein the method and apparatus divide the variable Function + definitions during SRv6SID allocation into two parts: and the topology ID + the resource ID performs resource abstraction on the binary formula to obtain the advantage that the resource ID can be applied to a plurality of network topologies only by being allocated once, thereby greatly improving the allocation and release efficiency of SRv6 SID.
The embodiment of the invention adopts the following technical scheme:
in a first aspect, the present invention provides a method for SRv6SID assignment in a resource-based multi-topology environment, including:
dividing the SID into topology ID + resource ID;
searching corresponding service resources according to the received SID allocation request and allocating resource IDs;
setting a requested VTN topology bitmap;
the assigned SID is returned using the combination of Locator + topology ID + resource ID.
Further, the searching for the corresponding service resource according to the received SID allocation request and performing the allocation of the resource ID specifically includes:
receiving a SID distribution request of a VTN topology;
searching an allocation relation table according to the service resource key in the received SID allocation request, and judging whether the service resource corresponding to the VTN topology has allocated a resource ID;
if the resource ID is not allocated, a resource ID is allocated to the resource ID, and if the resource ID is allocated, the resource ID does not need to be reallocated.
Further, the setting of the VTN topology bitmap of the request specifically includes:
and modifying the original topology bitmap according to the SID allocation request of the newly added VTN topology so as to record that the service resources corresponding to the newly added VTN topology are referred by the new VTN topology allocation.
Further, the method also comprises a SID release process:
and resetting the corresponding VTN topology bitmap, if the topology bitmap in the distribution relation is 0, releasing the SID, otherwise, not releasing the SID.
Further, the SID release procedure specifically includes:
receiving a SID release request of a VTN topology;
searching an allocation relation table according to the service resource key, and judging whether the service resource corresponding to the VTN topology has allocated a resource ID;
if so, resetting the corresponding VTN topology bitmap, and checking whether the topology bitmap in the distribution relation is 0;
and if the topology bitmap is 0, releasing the SID.
Further, in the SID release process, if the service resource corresponding to the VTN topology is not allocated with the resource ID, the process is directly ended; if the topology bitmap is not 0, the process is directly ended.
Further, the Locator segment of the SID remains fixed as a prefix.
Further, for the same service resource, under different topologies, the resource ID is the same, and the topology ID is different.
Further, the topology ID is a VTN ID in the network slice, and the resource ID is an ID allocated based on sub-interface, next hop, VPN instance, and EVPN instance resources.
On the other hand, the invention provides a device for allocating SRv6 SIDs in a resource-based multi-topology environment, which specifically comprises: comprising at least one processor and a memory, the at least one processor and the memory being connected by a data bus, the memory storing instructions executable by the at least one processor, the instructions, after execution by the processor, performing the method of SRv6SID allocation in a resource-based multi-topology environment of the first aspect.
Compared with the prior art, the embodiment of the invention has the beneficial effects that: in the VPN + application deployment, when the VTN corresponding to the multiple network slices allocates SIDs, the memory occupation is greatly reduced, and the allocation and release efficiency is improved. On the other hand, the invention also solves the problem troubled by the industry at present, namely the problem of carrying the VTN ID.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
FIG. 1 is a diagram illustrating an SRv6 multi-topology network in the background art of the present invention;
FIG. 2 is a diagram illustrating a conventional SRv6SID assignment in the background of the invention;
fig. 3 is a flowchart of a method for SRv6SID assignment in a resource-based multi-topology environment according to embodiment 1 of the present invention;
fig. 4 is a schematic diagram of SID value division provided in embodiment 1 of the present invention;
fig. 5 is a schematic diagram comparing the SRv6SID distribution method provided in embodiment 1 of the present invention;
FIG. 6 is a flowchart of step 200 provided in embodiment 1 of the present invention;
fig. 7 is a flowchart of SID release provided in embodiment 1 of the present invention;
fig. 8 is a block diagram of system modules for SRv6SID allocation in a resource-based multi-topology environment according to embodiment 2 of the present invention;
fig. 9 is a schematic structural diagram of an apparatus for allocating SRv6SID in a resource-based multi-topology environment according to embodiment 3 of the present invention.
[ detailed description ] embodiments
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The present invention is a system structure of a specific function system, so the functional logic relationship of each structural module is mainly explained in the specific embodiment, and the specific software and hardware implementation is not limited.
In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other. The invention will be described in detail below with reference to the figures and examples.
Example 1:
as shown in fig. 3, an embodiment of the present invention provides a method for allocating SRv6SID in a resource-based multi-topology environment, which includes the following specific steps.
Step 100: the Function + attributes, which are variable when SID is assigned, are divided into topology ID + resource ID. That is, this step divides the SID into topology ID + resource ID.
Step 200: and searching corresponding service resources according to the received SID allocation request and allocating the resource IDs.
Step 300: the requested VTN topology bitmap is set.
Step 400: the assigned SID is returned using the combination of Locator + topology ID + resource ID.
In this embodiment, through the above steps, the Function + constraints replanning, which is variable when SRv6SID is allocated in a multi-topology environment, is divided into two parts: the topology ID + the resource ID abstract the service resource, so that under the condition of the same service resource, the resource ID is only required to be allocated once to be applied to a plurality of different network topologies, and the SRv6SID allocation efficiency is greatly improved.
Specifically, each step in this example will be described in detail below.
First, it should be noted that in SRv6 networks, the common SID is of the following type:
1) node-dependent: END.
2) Egress interface and next hop related: X/end.DX4/end.DX6/end.DX2/end.DX2L.
3) Service instance related: end.DT4/end.DT6/end.DT2U/end.DT2M.
When SID is allocated to Locator segments corresponding to different VTNs, if the SID corresponds to the same service resource: for example, for the same sub-interface resource allocation end.x or for the same vpn resource allocation end.dt4, the corresponding service resource is one when allocated, and is allocated only in different Locator segments.
As shown in fig. 4, the present patent divides the Function + definitions that is variable when SID is assigned into two parts: topology ID (Topology ID in the figure) + Resource ID (Resource ID in the figure), and Locator as a prefix is fixed with respect to subsequent fields.
Topology ID: in network slicing, this is typically the VTN ID. Through the design of the topology ID, the invention solves the problem of carrying VTN ID in the prior art.
Resource ID: ID based on resource allocation like subinterface, next hop, VPN instance, EVPN instance, etc.
In the prior art, originally, when SID is allocated, it is implemented by variable functions + definitions, so that when different Locator segments are allocated, the existing allocation method needs to maintain allocation relations (SID < - > service resources in the background art) respectively, thereby occupying more resources and memories, and having lower efficiency.
For the technical scheme, the resource IDs of the same service resource are the same under different topologies, and only the topology IDs are different. Therefore, the field behind the Locator segment is divided into the topology ID and the resource ID when the SID is allocated, so that the purpose that the resource ID is allocated to the same service resource only once and can be quickly applied to another VTN topology is achieved.
After the SRv6SID assignment method is adopted, as shown in fig. 5, the left two SIDs in fig. 5 are assigned as the assignment method in the prior art, and the right SID assignment method is the assignment method in this embodiment. In the present embodiment, each line of text in the block of fig. 5 represents a resource allocated in the allocated area, and for the allocation method in the prior art, as in the background art, it is required to maintain respective allocation relationships (SID < - > service resources), but in the allocation method in this embodiment, only one allocation relationship needs to be maintained for SIDs of multiple Locator segments: resource ID (resource ID) + topology bitmap + service resources.
The topology bitmap in the above allocation relationship means that if the same service resource is allocated and used by a plurality of topologies, the topology bitmap records all managed topologies. For example, topology 1 and topology 2 have the same service resource vpn1, then the topology bitmap uses binary 11 to express this information. For example, topology 1 does not have traffic resource vpn2, and topology 2 does have traffic resource vpn2, then this information can be expressed as 01. Similarly, if there is a traffic resource in topology 1 but not in topology 2, it can be represented by 10. It should be further noted that the number of bits of the bitmap in this embodiment is variable, and generally, when the implementation is performed, an integer has 32 bits, which can represent 32 topology IDs, and how many bits are needed, and according to the number of topologies, for example, only two topologies are used, which is represented by two-bit 0 and 1(0 represents that the topology has no corresponding service resource, and 1 represents that the topology has corresponding service resource), and how many topologies are represented by how many bits of 0 and 1, and in addition, when the number of topologies exceeds 32, variable length expansion similar to an array can be performed.
Based on the above description, it is apparent that, in the new SRv6SID allocation method, under a multi-topology environment, on one hand, SRv6SID allocation efficiency can be greatly improved, and on the other hand, occupation of allocated resources can be reduced.
Based on the topology ID and resource ID division in step 100, the corresponding SID assignment process can be represented as step 200-step 400, which is as follows.
As shown in fig. 6, in the preferred embodiment, the step 200 (searching for the corresponding service resource according to the received SID allocation request and performing resource ID allocation) specifically includes:
step 201: a SID assignment request is received for a certain VTN topology.
Step 202: and searching an allocation relation table according to the service resource key in the received SID allocation request, and judging whether the service resource corresponding to the VTN topology has the allocated resource ID. With the above allocation relationship: for example, resource ID (resource ID) + topology bitmap + service resource, in this step, the corresponding allocation relationship is found out according to the key value of the service resource, and then it is determined whether the service resource corresponding to the VTN topology that receives the SID allocation request has already allocated the resource ID.
Step 203: if the resource ID is not allocated, a resource ID is allocated to the resource ID, and if the resource ID is allocated, the resource ID does not need to be reallocated.
In the preferred embodiment, step 300 (setting the VTN topology bitmap of the request) specifically includes: and modifying the original topology bitmap according to the SID allocation request of the newly added VTN topology so as to record that the service resources corresponding to the newly added VTN topology are referred by the new VTN topology allocation. The topology bitmap records the corresponding relation between one service resource and a plurality of topologies, which indicates that the service resource is quoted by all VTN topologies represented by the bitmap, and setting the VTN topology bitmap means that the new VTN which is added and recorded to the topology bitmap corresponding to the service resource also quotes the service resource.
Specifically, for example, three topologies 1, 2, and 3 are provided, at first, only topologies 1 and 2 have corresponding resource allocation SIDs, at this time, topology bitmap expresses that topology bitmap is binary 011, SID needs to be configured in topology 3, after setting, corresponding topology bitmap expresses that topology bitmap is binary 111, and the binary expression records that the service resource is allocated and referred by a new VTN topology.
Finally, step 400 is performed: the assigned SID is returned using the combination of Locator + topology ID + resource ID. It should be noted that the final returned SID is also in a standard SID format, which is in an IPv6 address format, and the SID of this IPv 6-like address is formed by combining Locator + topology ID + resource ID.
In the preferred embodiment, in addition to the above SID assignment procedure, the method further includes a SID release procedure: and resetting the corresponding VTN topology bitmap, if the topology bitmap in the distribution relation is 0, releasing the SID, otherwise, not releasing the SID.
Specifically, as shown in fig. 7, the SID release process specifically includes:
step 501: a SID release request is received for a certain VTN topology.
Step 502: and searching an allocation relation table according to the service resource key, and judging whether the service resource corresponding to the VTN topology has the allocated resource ID. The step is an optional step, and in general, even if only one topology is used, the resource ID is allocated first, so that the topology can be known to be allocated with the resource ID without judgment.
Step 503: if so, resetting the corresponding VTN topology bitmap, and checking whether the topology bitmap in the distribution relation is 0; if not, the releasing process is directly ended. It should be noted that resetting the VTN topology bitmap herein means to release the reference relationship between the VTN topology and the service resource for the topology bitmap corresponding to the service resource.
Step 504: under the condition that the resource ID is distributed, if the topology bitmap is 0, releasing the SID; if the topology bitmap is not 0, the release process is directly ended. The assignment and release of SIDs is embodied as topology increase and decrease, respectively.
Obviously, in the above design, the release process of the SID in this embodiment has the beneficial effects of reducing the memory usage and improving the release efficiency compared with the prior art.
As can be seen from the above description of this embodiment, in the VPN + application deployment, when the VTNs corresponding to multiple network slices allocate the SID, the embodiment of the present invention greatly reduces the memory usage and improves the allocation and release efficiency. On the other hand, the invention also solves the problem troubled by the industry at present, namely the problem of carrying the VTN ID.
Example 2:
based on the SRv6SID distribution method in the resource-based multi-topology environment provided in embodiment 1, this embodiment 2 provides a system for SRv6SID distribution in the resource-based multi-topology environment corresponding to embodiment 1, and as shown in fig. 8, the system includes a SID value division module, a resource ID distribution module, a set topology bitmap module, a SID distribution module, and a SID release module. The SID value dividing module is used for dividing variable Function + attributes during SID allocation into topology ID + resource ID; the resource ID distribution module is used for searching corresponding service resources according to the received SID distribution request and distributing the resource ID; the setting topology bitmap module is used for setting the requested VTN topology bitmap; the SID distribution module is used for returning the distributed SID by using the combination of Locator, topology ID and resource ID; and the SID release module is used for executing the SID release request of the VTN topology.
Corresponding to embodiment 1, the function of the SID value dividing module in this embodiment 2 corresponds to step 100 in embodiment 1; the function of the resource ID allocation module corresponds to step 200 in embodiment 1; the function responsible for setting the topology bitmap module corresponds to the step 300 in the embodiment 1; the function for which the SID assignment module is responsible corresponds to step 400 in embodiment 1; the function of the SID release module corresponds to the SID release procedure in embodiment 1.
Specifically, the resource ID allocation module may be further subdivided into: the device comprises an allocation request acquisition module, a resource ID judgment module and a resource ID allocation module. The distribution request acquisition module is used for receiving an SID distribution request of VTN topology; the resource ID judging module is used for searching the distribution relation table according to the service resource key and judging whether the service resource corresponding to the VTN topology is distributed with the resource ID; the resource ID allocation module is used for allocating a resource ID to the service resource when the service resource is not allocated with the resource ID.
The SID release module may be further subdivided to include: the system comprises a release request acquisition module, a resource ID judgment module, a topology bitmap checking module and a release SID module. The release request acquisition module is used for acquiring an SID release request of the VTN topology; the resource ID judging module is used for searching the distribution relation table according to the service resource key and judging whether the service resource corresponding to the VTN topology is distributed with the resource ID; the topology bitmap checking module is used for resetting the corresponding VTN topology bitmap under the condition of the allocated resource ID and checking whether the topology bitmap in the allocation relation is 0 or not; and the release SID module is used for releasing SID under the condition that the topology bitmap is 0.
In this embodiment, the modules perform cooperative processing to implement allocation and release of SRv6SID in a multi-topology environment, so as to achieve the technical effects of greatly reducing memory usage and improving allocation and release efficiency. The flow and steps of the cooperative processing among the modules in this embodiment are detailed in embodiment 1, and are not described herein again.
Example 3:
based on the SRv6SID allocation method and system in the resource-based multi-topology environment provided in embodiments 1 to 2, the present invention further provides a device for implementing SRv6SID allocation in the resource-based multi-topology environment of the above method and system, as shown in fig. 9, which is a schematic diagram of a device architecture in an embodiment of the present invention. The apparatus for SRv6SID assignment in resource-based multi-topology environment of the present embodiment includes one or more processors 21 and a memory 22. In fig. 9, one processor 21 is taken as an example.
The processor 21 and the memory 22 may be connected by a bus or other means, and fig. 9 illustrates the connection by a bus as an example.
The memory 22, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the SRv6SID assignment method and system in the resource-based multi-topology environment of embodiments 1-2. The processor 21 executes various functional applications and data processing of the apparatus for SRv6SID assignment in resource-based multi-topology environment, namely, implements the method and system for SRv6SID assignment in resource-based multi-topology environment of embodiments 1 to 2, by running non-volatile software programs, instructions and modules stored in the memory 22.
The memory 22 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory 22 may optionally include memory located remotely from the processor 21, and these remote memories may be connected to the processor 21 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Program instructions/modules are stored in the memory 22 and when executed by the one or more processors 21, perform the method and system for SRv6SID allocation in a resource-based multi-topology environment in embodiments 1-2, for example, perform the functions of the above-described steps/modules shown in fig. 1-8.
Those of ordinary skill in the art will appreciate that all or part of the steps of the various methods of the embodiments may be implemented by associated hardware as instructed by a program, which may be stored on a computer-readable storage medium, which may include: a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.
Claims (10)
1. A method for SRv6SID assignment in a resource-based multi-topology environment, comprising:
dividing the SID into topology ID + resource ID;
searching corresponding service resources according to the received SID allocation request and allocating resource IDs;
setting a requested VTN topology bitmap;
the assigned SID is returned using the combination of Locator + topology ID + resource ID.
2. The method for SRv6SID assignment in multi-topology environment based on resources as claimed in claim 1, wherein the searching for corresponding service resources and performing resource ID assignment according to the received SID assignment request specifically comprises:
receiving a SID distribution request of a VTN topology;
searching an allocation relation table according to the service resource key in the received SID allocation request, and judging whether the service resource corresponding to the VTN topology has allocated a resource ID;
if the resource ID is not allocated, a resource ID is allocated to the resource ID, and if the resource ID is allocated, the resource ID does not need to be reallocated.
3. The method for SRv6SID allocation in resource-based multi-topology environment according to claim 2, wherein the VTN topology bitmap of the set request specifically includes:
and modifying the original topology bitmap according to the SID allocation request of the newly added VTN topology so as to record that the service resources corresponding to the newly added VTN topology are referred by the new VTN topology allocation.
4. The method for SRv6SID assignment in resource-based multi-topology environment according to claim 1, further comprising SID release procedure:
and resetting the corresponding VTN topology bitmap, if the topology bitmap in the distribution relation is 0, releasing the SID, otherwise, not releasing the SID.
5. The method for SRv6SID assignment in resource-based multi-topology environment according to claim 4, wherein the SID release procedure specifically includes:
receiving a SID release request of a VTN topology;
searching an allocation relation table according to the service resource key, and judging whether the service resource corresponding to the VTN topology has allocated a resource ID;
if so, resetting the corresponding VTN topology bitmap, and checking whether the topology bitmap in the distribution relation is 0;
and if the topology bitmap is 0, releasing the SID.
6. The method for SRv6SID assignment under the multi-topology environment based on resources as claimed in claim 5, wherein in the SID release procedure, if the service resources corresponding to VTN topology do not assign resource ID, then directly ending the procedure; if the topology bitmap is not 0, the process is directly ended.
7. The method for SRv6SID assignment in resource-based multi-topology environment according to any of claims 1-6, wherein the Locator segment of the SID is kept fixed as a prefix.
8. The method for SRv6SID assignment in resource-based multi-topology environment according to any of claims 1-6, wherein the resource IDs are the same and the topology IDs are different in different topologies for the same traffic resource.
9. The method for SRv6SID assignment in resource-based multi-topology environment according to any of claims 1-6, wherein the topology ID is VTNID in network slice, and the resource ID is ID based on sub-interface, next hop, VPN instance, EVPN instance resource assignment.
10. An apparatus for SRv6SID assignment in a resource-based multi-topology environment, comprising:
comprising at least one processor and a memory, said at least one processor and memory being connected by a data bus, said memory storing instructions executable by said at least one processor, said instructions upon execution by said processor performing the method of SRv6SID allocation in a resource based multi-topology environment according to any of claims 1-9.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210005948.0A CN114389996B (en) | 2022-01-04 | 2022-01-04 | Method and device for SRv SID distribution in multi-topology environment based on resources |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210005948.0A CN114389996B (en) | 2022-01-04 | 2022-01-04 | Method and device for SRv SID distribution in multi-topology environment based on resources |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114389996A true CN114389996A (en) | 2022-04-22 |
CN114389996B CN114389996B (en) | 2023-06-09 |
Family
ID=81199759
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210005948.0A Active CN114389996B (en) | 2022-01-04 | 2022-01-04 | Method and device for SRv SID distribution in multi-topology environment based on resources |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114389996B (en) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019105066A1 (en) * | 2017-12-01 | 2019-06-06 | 华为技术有限公司 | Route processing method and apparatus, and data transmission method and apparatus |
CN110830352A (en) * | 2018-08-07 | 2020-02-21 | 中兴通讯股份有限公司 | Method and device for realizing VPN cross-domain and boundary node |
CN111935007A (en) * | 2019-05-13 | 2020-11-13 | 瞻博网络公司 | Compressed routing header information for networks |
CN112087387A (en) * | 2020-08-14 | 2020-12-15 | 烽火通信科技股份有限公司 | Network processor and data packet forwarding method |
CN113055202A (en) * | 2019-12-26 | 2021-06-29 | 华为技术有限公司 | Method, device and system for transmitting data message |
WO2021135468A1 (en) * | 2019-12-30 | 2021-07-08 | 华为技术有限公司 | Segment identifier determining method and device |
CN113535399A (en) * | 2021-07-15 | 2021-10-22 | 电子科技大学 | NFV resource scheduling method, device and system |
-
2022
- 2022-01-04 CN CN202210005948.0A patent/CN114389996B/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019105066A1 (en) * | 2017-12-01 | 2019-06-06 | 华为技术有限公司 | Route processing method and apparatus, and data transmission method and apparatus |
CN110830352A (en) * | 2018-08-07 | 2020-02-21 | 中兴通讯股份有限公司 | Method and device for realizing VPN cross-domain and boundary node |
CN111935007A (en) * | 2019-05-13 | 2020-11-13 | 瞻博网络公司 | Compressed routing header information for networks |
CN113055202A (en) * | 2019-12-26 | 2021-06-29 | 华为技术有限公司 | Method, device and system for transmitting data message |
WO2021129014A1 (en) * | 2019-12-26 | 2021-07-01 | 华为技术有限公司 | Method for transmitting data message, apparatus, and system |
WO2021135468A1 (en) * | 2019-12-30 | 2021-07-08 | 华为技术有限公司 | Segment identifier determining method and device |
CN112087387A (en) * | 2020-08-14 | 2020-12-15 | 烽火通信科技股份有限公司 | Network processor and data packet forwarding method |
CN113535399A (en) * | 2021-07-15 | 2021-10-22 | 电子科技大学 | NFV resource scheduling method, device and system |
Also Published As
Publication number | Publication date |
---|---|
CN114389996B (en) | 2023-06-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2987314C (en) | Method, device and system for forwarding message | |
WO2020052605A1 (en) | Network slice selection method and device | |
CN113259238B (en) | Method and device for processing segment identifiers | |
US20230145093A1 (en) | Packet processing method and device, advertisement method and device, bridge node, source apparatus, storage medium, and packet processing system | |
WO2017124709A1 (en) | Method of establishing traffic engineering tunnel and device | |
CN115004656A (en) | Message sending method, equipment and system | |
WO2022110535A1 (en) | Packet sending method, device, and system | |
CN113037527B (en) | Network slice creation method, message forwarding method and device thereof | |
WO2023103506A1 (en) | Memory management method for device, and memory management device and computing system | |
CN113676412A (en) | Network control method and equipment | |
CN114285787A (en) | Cross-user-plane forwarding method, system and computer-readable storage medium | |
WO2022037609A1 (en) | Data transmission method and device, communication node, and storage medium | |
CN113206787A (en) | Method and device for processing segment identifiers | |
US20230083406A1 (en) | Port resource reservation method, electronic device, and storage medium | |
EP3879767B1 (en) | Distributed label assignment for labeled routing protocol routes | |
CN110875886B (en) | Data transmission method, device and system for transmission network | |
CN114389996A (en) | SRv6SID distribution method and device under resource-based multi-topology environment | |
WO2012126435A2 (en) | Method and apparatus for allocating bandwidth resources | |
CN111464443B (en) | Message forwarding method, device, equipment and storage medium based on service function chain | |
CN113727394A (en) | Method and device for realizing shared bandwidth | |
US7082128B1 (en) | Method and apparatus for non-stop forwarding with labels | |
CN117278885A (en) | Passive optical network traffic flow configuration | |
CN112532520B (en) | PCE-based TE-LSP implementation method and device | |
CN106161166B (en) | Coordination approach and device between a kind of multiple power line networks | |
CN109639600B (en) | Tunnel speed limiting method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |