CN113765794B - Data transmission method and device, electronic equipment and medium - Google Patents
Data transmission method and device, electronic equipment and medium Download PDFInfo
- Publication number
- CN113765794B CN113765794B CN202111162888.5A CN202111162888A CN113765794B CN 113765794 B CN113765794 B CN 113765794B CN 202111162888 A CN202111162888 A CN 202111162888A CN 113765794 B CN113765794 B CN 113765794B
- Authority
- CN
- China
- Prior art keywords
- private network
- public private
- routing information
- aggregation
- network label
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000005540 biological transmission Effects 0.000 title claims description 22
- 230000002776 aggregation Effects 0.000 claims abstract description 143
- 238000004220 aggregation Methods 0.000 claims abstract description 143
- 230000006855 networking Effects 0.000 claims abstract description 39
- 238000004806 packaging method and process Methods 0.000 claims description 8
- 238000005538 encapsulation Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 6
- 230000007547 defect Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000013459 approach Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 239000004148 curcumin Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
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/14—Routing performance; Theoretical aspects
-
- 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/20—Hop count for routing purposes, e.g. TTL
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a data sending method, a data sending device, electronic equipment and a medium. The first aggregation routing device applied to the SRv6 networking scene can receive first routing information which is issued by first access equipment and points to second access equipment, and encapsulate a target public private network label into the first routing information, wherein the target public private network label is used for indicating a next hop address table item of receiving equipment, the receiving equipment comprises the second access equipment and second aggregation equipment which is associated with the second access equipment, and then the first routing information encapsulated with the target public private network label is issued to the second aggregation equipment.
Description
Technical Field
The present application relates to data communication technologies, and in particular, to a method, an apparatus, an electronic device, and a medium for data transmission.
Background
With the development of communication technology, SRv6 (Segment Routing Internet Protocol Version 6, segment Routing based on the sixth Version Internet Protocol) network is widely used.
Further, in the service deployment process of the existing SRv6, when a route is released between access devices, a large amount of access devices exist in networking. It is therefore generally necessary to implement the distribution of routes by the aggregation device for both access devices. For example, when the access device 1 issues a route to the access device 2, the access device 1 needs to send the route to the aggregation device 1 associated therewith, so that the aggregation device 1 issues the route to the aggregation device 2 associated with the access device 2, and finally the aggregation device 2 sends the route to the access device 2.
However, since the aggregation device 1 is associated with a plurality of access device addresses, a problem may be caused in the mechanism of the SRv6 networking scenario, that is, when the aggregation device 2 or the access device 2 receives a route, a large number of next-hop table entries may be issued to the aggregation device 2 or the access device, so that the table entry resources of the receiving device are greatly affected.
Disclosure of Invention
Embodiments of the present application provide a method, an apparatus, an electronic device, and a medium for data transmission, which are used to solve the problem that, in an SRv6 VPN networking scenario in the related art, a device receiving a route may greatly consume entry resources.
According to an aspect of the embodiments of the present application, a method for sending data is provided, where the method is applied to a first aggregation routing device in an SRv6 networking scenario, and includes:
receiving first routing information which is issued by first access equipment and points to second access equipment;
encapsulating a target public private network label into the first routing information, the target public private network label being used to indicate a next hop address table entry of a receiving device, the receiving device including the second access device and a second aggregation device associated with the second access device;
and issuing the first routing information encapsulated with the target public private network label to the second convergence equipment.
Optionally, in another embodiment of the present application, the target public private network tag includes:
a first public private network tag for indicating a next hop address table entry of the receiving device as the address of the first aggregation routing device; or the like, or, alternatively,
and the second public private network label is used for indicating that the next hop address table entry of the receiving equipment is the target node address.
Optionally, in another embodiment of the present application, before the encapsulating the target public private network label into the first routing information, the method further includes:
detecting the current SRv6 networking scene environment, and selecting the first public private network label or the second public private network label as the target public private network label
Optionally, in another embodiment of the present application, after the issuing the first routing information encapsulated with the target public and private network label to the second aggregation device, the method further includes:
receiving second routing information which is sent by the second aggregation equipment and points to the first access equipment, and encapsulating a target public private network label into the second routing information;
and issuing the second routing information encapsulated with the target public private network label to the first access device.
Optionally, in another embodiment of the present application, before receiving the first routing information, which is issued by the first access device and is directed to the second access device, the method further includes:
and acquiring the target public private network label of an IPv6 address field with a preset digit.
According to an aspect of the embodiments of the present application, a method for sending data is provided, where the method is applied to a second aggregation routing device in an SRv6 networking scenario, and includes:
receiving first routing information which is sent by a first aggregation device and points to a second access device, wherein the first routing information carries a public private network label used for indicating a next hop address table item of the second aggregation device;
analyzing the public private network label to obtain a table entry containing a next hop address as the address of the first aggregation routing equipment or the next hop address as the address of a target node;
and packaging the target public private network label into the first routing information, and issuing the first routing information packaged with the target public private network label to the second access equipment.
Optionally, in another embodiment of the present application, after the issuing the first routing information encapsulated with the target public private network label to the second access device, the method further includes:
receiving second routing information which is issued by the second access equipment and points to the first access equipment;
and encapsulating the target public private network label into the second routing information, and issuing the second routing information encapsulated with the target public private network label to the first convergence device.
According to an aspect of the embodiments of the present application, an apparatus for sending data, which is applied to a first aggregation routing device in an SRv6 networking scenario, includes:
the first receiving module is configured to receive first routing information which is issued by first access equipment and points to second access equipment;
a first encapsulation module configured to encapsulate a target public private network tag into the first routing information, the target public private network tag indicating a next hop address table entry for a receiving device, the receiving device including the second access device and a second aggregation device associated with the second access device;
and the issuing module is configured to issue the first routing information encapsulated with the target public private network label to the second aggregation equipment.
According to an aspect of the embodiments of the present application, an apparatus for sending data, which is applied to a second aggregation routing device in an SRv6 networking scenario, includes:
a second receiving module, configured to receive first routing information, which is sent by a first aggregation device and points to a second access device, where the first routing information carries a public private network tag used for indicating a next hop address table entry of the second aggregation routing device;
the decapsulation module is configured to resolve the public private network label to obtain an entry containing a next hop address as the first aggregation routing device address or a destination node address;
and the second packaging module is configured to package the target public private network label into the first routing information and issue the first routing information packaged with the target public private network label to the second access equipment.
According to another aspect of the embodiments of the present application, there is provided an electronic device including:
a memory for storing executable instructions; and
a display for displaying with the memory to execute the executable instructions to perform the operations of any of the above methods of data transmission.
According to still another aspect of the embodiments of the present application, a computer-readable storage medium is provided, which stores computer-readable instructions that, when executed, perform the operations of any one of the above-described data transmission methods.
The first aggregation routing device applied to the SRv6 networking scene can receive first routing information which is issued by first access equipment and points to second access equipment, and encapsulate a target public private network label into the first routing information, wherein the target public private network label is used for indicating a next hop address table item of receiving equipment, the receiving equipment comprises the second access equipment and second aggregation equipment which is associated with the second access equipment, and then the first routing information encapsulated with the target public private network label is issued to the second aggregation equipment. By applying the technical scheme of the application, a public private network label used for indicating the next hop address table entry of the receiving equipment can be added before the convergence equipment sends the route in an SRv6 networking scene. Therefore, after receiving the route, the receiving device only needs to receive the issued list item containing the specified next-hop address, and further avoids the defect of device resource consumption caused by the need of receiving the next-hop list items of all the access device addresses associated with the convergence device in the related technology.
The technical solution of the present application is further described in detail by the accompanying drawings and examples.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description, serve to explain the principles of the application.
The present application may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:
fig. 1 is a schematic diagram of a data transmission method proposed in the present application;
fig. 2 is a schematic diagram of a data transmission architecture proposed in the present application;
FIG. 3 is a block diagram of a data transmission architecture according to the present application;
fig. 4 is a schematic diagram of another data transmission method proposed in the present application;
fig. 5 is a schematic flow chart of another data transmission proposed in the present application;
fig. 6-7 are schematic structural diagrams of an electronic device for data transmission according to the present application;
fig. 8 is a schematic structural diagram of an electronic device for data transmission according to the present application.
Detailed Description
Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present application unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the application, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
In addition, technical solutions between the various embodiments of the present application may be combined with each other, but it must be based on the realization of the technical solutions by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination of technical solutions should be considered to be absent and not within the protection scope of the present application.
It should be noted that all directional indicators (such as up, down, left, right, front, back, 8230; \8230;) in the embodiments of the present application are only used to explain the relative positional relationship between the components, the motion situation, etc. in a specific posture (as shown in the drawings), and if the specific posture is changed, the directional indicator is changed accordingly.
A method for data transmission according to an exemplary embodiment of the present application is described below in conjunction with fig. 1-5. It should be noted that the following application scenarios are merely illustrated for the convenience of understanding the spirit and principles of the present application, and the embodiments of the present application are not limited in this respect. Rather, embodiments of the present application may be applied to any scenario where applicable.
Furthermore, the application also provides a method, a device, an electronic device and a medium for data transmission.
Fig. 1 schematically shows a flow chart of a method for data transmission according to an embodiment of the present application. As shown in fig. 1, the method is applied to a first aggregation routing device in an SRv6 networking scenario, and includes:
s101, receiving first routing information which is issued by first access equipment and points to second access equipment.
In the related art, the SRv6 networking scenario includes many devices, and the coverage area is wide, which results in a complex network architecture. For management convenience, an SRv6 networking scenario is generally divided into three levels, i.e., a core device, an aggregation device and an access device. As shown in fig. 2, the networking architecture design is typically employed. That is, a core device may be associated with a plurality of aggregation devices, and each aggregation device may be associated with a plurality of access devices. It should be noted that, because the number of the access devices is huge, the aggregation device may be responsible for the corresponding access device, so that the aggregation device aggregates the access routes, ports, and sessions of the associated access devices and sends the aggregated access routes, ports, and sessions to the core device.
Further, as shown in fig. 3, when Srv6 service is deployed, since the aggregation device 1 cannot reallocate a private network label to send to the access 1, when transmitting a route issued by the access device 1, the aggregation device 1 directly encapsulates the private network address (i.e., vpnsid A5:1:: B100) of the access device 1 to issue to an opposite end. Then the next hop waiting for access 1 to this private network route is the address of access 3 at this time. This also leads to a problem that when the number of access devices 1, and/or aggregation devices is large, the receiving device at the opposite end of the route directly issues a large number of next hop representations to the receiving device. It can be understood that the next hop of the access device is directly a massive remote access device, and therefore, the table entry resource of the receiving device is greatly consumed. Moreover, when the network fails, the device receiving the route also needs to refresh the table entry frequently, and the pressure on the device is also high.
S102, packaging a target public private network label into the first routing information, wherein the target public private network label is used for indicating a next hop address table item of a receiving device, and the receiving device comprises a second access device and a second aggregation device associated with the second access device.
Further, in order to avoid the above mentioned problem, the present application may assign a public private network tag to the aggregation device in the SRv6 networking scenario. Its role is to indicate the next hop address table entry of the device (e.g. peer aggregation device, peer access device) receiving the route. Therefore, the next hop address table entry of the opposite terminal equipment only comprises a limited number of address nodes. Compared with the prior art, the next-hop address table entry of the peer device contains a large number of access device address nodes. The table resource of the equipment can be greatly saved.
Specifically, after the first aggregation device encapsulates the target public private network label into the first routing information, the aggregation device itself in the SRv6 networking scenario can forward the target public private network label without looking up a private network route (because the device does not have an AC port locally, the target public private network label does not need to look up a table for forwarding after decapsulation because the device does not have an AC port locally). That is, it does not need to go through the next hop table entry in the process of forwarding the peer device. This also ensures that although the public private network label is added, the forwarding path of the device is not changed, but only the next hop table entry of the receiving device is affected.
It should be noted that, in the present application, the number of the access devices and the aggregation devices is not specifically limited, and may be, for example, one or a plurality of.
In one approach, the public private network tag may be an end. Which can be mapped to each other with all end-like tags. And it may be a tag of the Ipv6 address field of a 16-field bit or a 32-field bit.
S103, the first routing information encapsulated with the target public private network label is issued to the second convergence device.
For example, it shows a process of issuing, at a first aggregation routing device, first routing information encapsulated with a target public private network label to a second aggregation device:
the first access device may encapsulate the public type E100 via the private network label of the first aggregation device, and then forward the routing information to the first aggregation device. After the first aggregation device encapsulates the target public private network label to the first routing information, the routing is encapsulated again according to the private network label of the aggregation 3, and the routing information is forwarded to the second aggregation device, and after the second aggregation device encapsulates the first routing information with the private network label, the second aggregation device encapsulates again according to the private network label of the second access device, and then forwards the first routing information to the second access device.
The first aggregation routing device is applied to an SRv6 networking scene, and can receive first routing information which is issued by a first access device and points to a second access device, and encapsulate a target public private network label into the first routing information, wherein the target public private network label is used for indicating a next hop address table item of a receiving device, the receiving device comprises the second access device and a second aggregation device which is associated with the second access device, and then issues the first routing information encapsulated with the target public private network label to the second aggregation device. By applying the technical scheme of the application, a public private network label used for indicating the next hop address table entry of the receiving equipment can be added before the convergence equipment sends the route in an SRv6 networking scene. Therefore, after receiving the route, the receiving device only needs to receive the sent table item containing the designated next hop address, and the defect that the device resource is consumed due to the fact that the next hop table items of all the access device addresses associated with the aggregation device need to be received in the related technology is avoided.
Optionally, in a possible implementation manner of the present application, the target public private network tag includes:
a first public private network label used for indicating the next hop address table entry of the receiving device as the address of the first aggregation routing device; or the like, or, alternatively,
and the second public private network label is used for indicating that the next hop address table entry of the receiving equipment is the target node address.
Further, in order to avoid the problem that the device receiving the route may issue a large number of next hop entries as in the related art. The method and the device can allocate a public private network tag for the convergence device in the SRv6 networking scene. Its role is to indicate the next hop address table entry of the device (e.g. peer aggregation device, peer access device) receiving the route.
Alternatively, the public private network label may indicate that the next hop address table entry of the device receiving the route is the first public private network label of the first aggregation routing device address.
For example, 100 first access devices are associated under a first aggregation device, and after a second aggregation device receives routing information sent by the first aggregation device, it needs to receive next hop address table entries of 100 first access devices corresponding to the first aggregation device after decapsulating a route. When the first aggregation device adds a first public private network label into the routing information (i.e. the next hop address of the routing information is changed into the first aggregation device itself), the second aggregation device can only obtain a next hop table item which is the node address of the first aggregation device by analyzing the first public private network label in the process of de-encapsulating the route.
It can be understood that, compared with the prior art, the next-hop address table entry of the peer device includes 100 access device address nodes. Only one next-hop table entry (the table entry address is the first aggregation) is obtained, so that the table entry resource of the equipment can be greatly saved.
In an optional another manner, the public private network tag may also be a second public private network tag used to indicate that the next-hop address table entry of the receiving device is a certain target node address.
For example, 100 first access devices are associated under a first aggregation device, and after a second aggregation device receives routing information sent by the first aggregation device, it needs to receive next hop address entries of the 100 first access devices corresponding to the first aggregation device after decapsulating a route. When the first aggregation device adds a first public private network label into the routing information (i.e. the next hop address of the routing information is changed into a destination node address), the second aggregation device can only obtain a next hop table item which is a destination node address by analyzing the first public private network label in the process of de-encapsulating the route.
It can be understood that, compared with the prior art, the next hop address table entry of the peer device includes 100 access device address nodes. Only one next-hop table entry (the table entry address is a target node address) is obtained, so that the table entry resource of the equipment can be greatly saved.
It should be noted that the destination node address is not specifically limited in this application, and may be, for example, a unidirectional lsp node address. The unidirectional node may include an ingress node, that is, an initial node of an lsp, where an lsp has only one ingress, and a new label is pressed and encapsulated into an mpls packet for forwarding. For an intermediate node, i.e. an intermediate node of an lsp, an lsp may have multiple transitions, and look up a label forwarding information table to complete mpls forwarding through label switching. An egress node may also be present.
Specifically, after the first aggregation device encapsulates the target public private network label into the first routing information, the aggregation device itself in the SRv6 networking scenario can forward the target public private network label without looking up a private network route (because the device does not have an AC port locally, the target public private network label does not need to look up a table for forwarding after decapsulation because the device does not have an AC port locally). That is, it does not need to go through the next hop table entry in the process of forwarding the peer device. This also ensures that although the public private network tag is added, the forwarding path of the device is not changed, but only the next hop table entry of the receiving device is affected.
Optionally, in a possible implementation manner of the present application, before the encapsulating the target public private network label into the first routing information, the method further includes:
and detecting the current SRv6 networking scene environment, and selecting the first public private network tag or the second public private network tag as a target public private network tag.
Specifically, the method and the device for encapsulating the routing information by the aggregation device can specifically select to encapsulate a first public private network label or a second public private network label on the routing information by the aggregation device according to the current SRv6 networking scene environment. The first public-private network tag may be selected, for example, when the number of deployed devices of the SRv6 networking scenario environment is detected to be greater than a threshold. And when detecting that the number of deployed devices of the SRv6 networking scenario environment is greater than a threshold, a second public private network tag may be selected. Thereby ensuring that the pressure on the list items of the equipment is not large.
Optionally, in a possible implementation manner of the present application, after the issuing the first routing information encapsulated with the target public and private network label to the second aggregation device, the method further includes:
receiving second routing information which is sent by the second aggregation equipment and points to the first access equipment, and encapsulating a target public private network label into the second routing information;
and issuing the second routing information encapsulated with the target public private network label to the first access device.
Optionally, in a possible implementation manner of the present application, before the receiving the first routing information that is issued by the first access device and is directed to the second access device, the method further includes:
assigning a preset number of bits of the target public private network tag of the Ipv6 address field.
In one approach, the public private network tag may be an end. Which can be mapped to each other with all end-like tags. And it may be a tag of the Ipv6 address field of a 16-field bit or a 32-field bit.
Fig. 4 schematically shows a flow chart of a method for data transmission according to an embodiment of the present application. As shown in fig. 4, the method is applied to a second aggregation routing device in an SRv6 networking scenario, and includes:
s201, receiving first routing information which is sent by a first aggregation device and points to a second access device, wherein the first routing information carries a public private network label which is used for indicating a next hop address table item of the second aggregation device.
Similarly, when Srv6 service is deployed, because the aggregation device 1 cannot reallocate the private network label to send to the access 1, when transmitting the route issued by the access device 1, the aggregation device 1 directly encapsulates the private network address (i.e., vpnsid A5:1:: B100) of the access device 1 to issue to the opposite end. Then the next hop waiting for access 1 to this private network route is the address of access 3 at this time. This also leads to a problem that when the number of access devices 1, and/or aggregation devices is large, the receiving device at the opposite end of the route directly issues a large number of next hop representations to the receiving device. It can be understood that the next hop of the access device is directly a massive remote access device, and therefore, the table entry resource of the receiving device is greatly consumed. Moreover, when the network fails, the device receiving the route also needs to refresh the table entries frequently, and the pressure on the device is also large.
S202, resolving the public private network label to obtain a table entry containing a next hop address as a first aggregation routing device address or a target node address.
S203, packaging the target public private network label into the first routing information, and issuing the first routing information packaged with the target public private network label to the second access device.
Further, in order to avoid the problem that the device receiving the route may issue a large number of next hop entries as in the related art. The method and the device can allocate a public private network label for the convergence device in the SRv6 networking scene. Its role is to indicate the next hop address table entry of the device (e.g. peer aggregation device, peer access device) receiving the route.
Alternatively, the public private network label may indicate that the next hop address table entry of the device receiving the route is the first public private network label of the first aggregation routing device address.
For example, 100 first access devices are associated under a first aggregation device, and after a second aggregation device receives routing information sent by the first aggregation device, it needs to receive next hop address table entries of 100 first access devices corresponding to the first aggregation device after decapsulating a route. When the first aggregation device adds a first public private network label into the routing information (i.e. the next hop address of the routing information is changed into the first aggregation device itself), the second aggregation device can only obtain a next hop table item which is the node address of the first aggregation device by analyzing the first public private network label in the process of de-encapsulating the route.
It can be understood that, compared with the prior art, the next-hop address table entry of the peer device includes 100 access device address nodes. Only one next-hop table entry (the table entry address is the first aggregation) is obtained, so that the table entry resource of the equipment can be greatly saved.
Optionally, in another manner, the public private network tag may also be a second public private network tag used to indicate that the next-hop address table entry of the receiving device is a certain destination node address.
For example, 100 first access devices are associated under a first aggregation device, and after a second aggregation device receives routing information sent by the first aggregation device, it needs to receive next-hop address table entries of the 100 first access devices corresponding to the first aggregation device after decapsulating a route. When the first aggregation device adds a first public private network label into the routing information (i.e. the next hop address of the routing information is changed into a destination node address), the second aggregation device can only obtain a next hop table item which is a destination node address by analyzing the first public private network label in the process of de-encapsulating the route.
Optionally, in a possible implementation manner of the present application, after the issuing the first routing information encapsulated with the target public private network label to the second access device, the method further includes:
receiving second routing information which is issued by the second access equipment and points to the first access equipment;
and packaging the target public private network label into second routing information, and issuing the second routing information packaged with the target public private network label to the first convergence equipment.
Further, as shown in fig. 5, a schematic flow diagram of a data sending method provided in the present application is shown, where the schematic flow diagram includes a first aggregation routing device in an SRv6 networking scenario and a second aggregation routing device in the SRv6 networking scenario.
According to the method and the device, a first aggregation routing device receives first routing information which is issued by a first access device and points to a second access device, and encapsulates a target public private network label into the first routing information, wherein the target public private network label is used for indicating a next hop address table item of the receiving device, the receiving device comprises the second access device and a second aggregation device which is associated with the second access device, and then issues the first routing information which is encapsulated with the target public private network label to the second aggregation device.
And further, the second aggregation router receives first routing information which is sent by the first aggregation router and points to the second access device, wherein the first routing information carries a public private network label used for indicating a next-hop address table item of the second aggregation router, and analyzes the public private network label to obtain a table item containing a next-hop address as the address of the first aggregation router or a target node address. And finally, packaging the target public private network label into the first routing information, and issuing the first routing information packaged with the target public private network label to the second access equipment.
By applying the technical scheme of the application, a public private network label used for indicating the next hop address table entry of the receiving equipment can be added before the convergence equipment sends the route in an SRv6 networking scene. Therefore, after receiving the route, the receiving device only needs to receive the issued list item containing the specified next-hop address, and further avoids the defect of device resource consumption caused by the need of receiving the next-hop list items of all the access device addresses associated with the convergence device in the related technology.
In another embodiment of the present application, as shown in fig. 6, the present application further provides a data transmission apparatus. The device is applied to a first aggregation routing device in an SRv6 networking scene, and comprises the following steps:
a first receiving module 301, configured to receive first routing information, which is issued by a first access device and is directed to a second access device;
a first encapsulation module 302 configured to encapsulate a target public private network tag into the first routing information, the target public private network tag indicating a next hop address entry for a receiving device, the receiving device including the second access device and a second aggregation device associated with the second access device;
a publishing module 303 configured to publish the first routing information encapsulated with the target public private network label to the second aggregation device.
By applying the technical scheme of the application, a public private network label used for indicating the next hop address table entry of the receiving equipment can be added before the convergence equipment sends the route in an SRv6 networking scene. Therefore, after receiving the route, the receiving device only needs to receive the issued list item containing the specified next-hop address, and further avoids the defect of device resource consumption caused by the need of receiving the next-hop list items of all the access device addresses associated with the convergence device in the related technology.
In another embodiment of the present application, the first receiving module 301 further includes:
a first receiving module 301, configured to indicate that a next hop address table entry of the receiving device is a first public private network tag of the first aggregation routing device address; or the like, or a combination thereof,
a first receiving module 301 configured to indicate that the next hop address table entry of the receiving device is a second public private network label of the destination node address.
In another embodiment of the present application, the first receiving module 301 further includes:
a first receiving module 301 configured to detect a current SRv6 networking scenario environment, and select the first public private network tag or the second public private network tag as the target public private network tag
In another embodiment of the present application, the first receiving module 301 further includes:
a first receiving module 301, configured to receive second routing information, which is sent by the second aggregation device and is directed to the first access device, and encapsulate a target public private network tag into the second routing information;
a first receiving module 301, configured to issue the second routing information encapsulated with the target public private network tag to the first access device.
In another embodiment of the present application, the first receiving module 301 further includes:
a first receiving module 301 configured to assign a preset number of bits of the target public private network tag of the Ipv6 address field.
In another embodiment of the present application, as shown in fig. 7, the present application further provides a data transmission apparatus. The device is applied to a second aggregation routing device in an SRv6 networking scene, and comprises the following steps:
a second receiving module 304, configured to receive first routing information, which is sent by a first aggregation device and is directed to the second access device, where the first routing information carries a public private network tag used for indicating a next hop address table entry of the second aggregation device;
a decapsulation module 305, configured to parse the public private network label to obtain an entry containing a next hop address as the first aggregation routing device address or a destination node address;
a second encapsulating module 306 configured to encapsulate the target public and private network label into the first routing information, and issue the first routing information encapsulated with the target public and private network label to the second access device.
In another embodiment of the present application, the second receiving module 304 further includes:
a second receiving module 304, configured to receive second routing information, which is issued by the second access device and is directed to the first access device;
a second receiving module 304, configured to encapsulate the target public private network tag into the second routing information, and issue the second routing information encapsulated with the target public private network tag to the first aggregation device.
FIG. 8 is a block diagram illustrating a logical configuration of an electronic device in accordance with an exemplary embodiment. For example, the electronic device 300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium, such as a memory, including instructions executable by an electronic device processor to perform the method of network monitoring described above, the method comprising: receiving first routing information which is issued by first access equipment and points to second access equipment; encapsulating a target public private network label into the first routing information, the target public private network label being used to indicate a next hop address table entry of a receiving device, the receiving device including the second access device and a second aggregation device associated with the second access device; and issuing the first routing information encapsulated with the target public private network label to the second convergence device. Optionally, the instructions may also be executable by a processor of the electronic device to perform other steps involved in the exemplary embodiments described above. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, there is also provided an application/computer program product including one or more instructions executable by a processor of an electronic device to perform the above-described method of network monitoring, the method comprising: receiving first routing information which is issued by first access equipment and points to second access equipment; encapsulating a target public private network label into the first routing information, the target public private network label being used to indicate a next hop address table entry of a receiving device, the receiving device including the second access device and a second aggregation device associated with the second access device; and issuing the first routing information encapsulated with the target public private network label to the second convergence equipment. Optionally, the instructions may also be executable by a processor of the electronic device to perform other steps involved in the exemplary embodiments described above.
Fig. 8 is an exemplary diagram of the computer device 40. Those skilled in the art will appreciate that the schematic diagram 8 is merely an example of the computer device 40 and does not constitute a limitation of the computer device 40, and may include more or fewer components than shown, or some of the components may be combined, or different components, e.g., the computer device 40 may also include input output devices, network access devices, buses, etc.
The Processor 402 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor 402 may be any conventional processor or the like, the processor 402 being the control center for the computer device 40 and connecting the various parts of the overall computer device 40 using various interfaces and lines.
The modules integrated by the computer device 40 may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by hardware related to computer readable instructions, which may be stored in a computer readable storage medium, and when the computer readable instructions are executed by a processor, the steps of the method embodiments may be implemented.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (10)
1. A method for sending data, which is applied to a first aggregation routing device in an SRv6 networking scenario, includes:
receiving first routing information which is issued by first access equipment and points to second access equipment;
encapsulating a target public private network label into the first routing information, the target public private network label being used to indicate a next hop address table entry of a receiving device, the receiving device including the second access device and a second aggregation device associated with the second access device;
and issuing the first routing information encapsulated with the target public private network label to the second convergence equipment.
2. The method of claim 1, wherein the target public private network tag comprises:
a first public private network tag for indicating a next hop address table entry of the receiving device as the address of the first aggregation routing device; or the like, or a combination thereof,
and the second public private network label is used for indicating that the next hop address table entry of the receiving equipment is the target node address.
3. The method of claim 2, prior to said encapsulating a target public private network label into said first routing information, further comprising:
and detecting the current SRv6 networking scene environment, and selecting the first public private network label or the second public private network label as the target public private network label.
4. The method of claim 1, wherein after said publishing the first routing information encapsulated with the target public private network label to the second aggregation device, further comprising:
receiving second routing information which is sent by the second aggregation equipment and points to the first access equipment, and encapsulating a target public private network label into the second routing information;
and issuing the second routing information encapsulated with the target public private network label to the first access device.
5. The method of claim 1, wherein prior to said receiving the first routing information issued by the first access device directed to the second access device, further comprising:
assigning the target public private network tag of an Ipv6 address field of a preset number of bits.
6. A method for sending data, which is applied to a second aggregation routing device in an SRv6 networking scenario, includes:
receiving first routing information which is sent by a first aggregation routing device and points to a second access device, wherein the first routing information carries a public private network label used for indicating a next hop address table item of the second aggregation routing device;
analyzing the public private network label to obtain a table entry which contains a next hop address as the address of the first aggregation routing equipment or the next hop address as the address of a target node;
and packaging the target public private network label into the first routing information, and issuing the first routing information packaged with the target public private network label to the second access equipment.
7. The method of claim 6, wherein after said publishing the first routing information encapsulated with the target public private network label to the second access device, further comprising:
receiving second routing information which is issued by the second access equipment and points to the first access equipment;
and encapsulating the target public private network label into the second routing information, and issuing the second routing information encapsulated with the target public private network label to the first convergence routing device.
8. An apparatus for data transmission, wherein the apparatus is applied to a first aggregation routing device in an SRv6 networking scenario, and the apparatus comprises:
the first receiving module is configured to receive first routing information which is issued by first access equipment and points to second access equipment;
a first encapsulation module configured to encapsulate a target public private network tag into the first routing information, the target public private network tag indicating a next hop address entry for a receiving device, the receiving device including the second access device and a second aggregation device associated with the second access device;
and the issuing module is configured to issue the first routing information encapsulated with the target public and private network label to the second aggregation equipment.
9. An apparatus for data transmission, wherein the second aggregation routing device applied in SRv6 networking scenario includes:
a second receiving module, configured to receive first routing information which is sent by a first aggregation routing device and points to a second access device, where the first routing information carries a public private network tag used for indicating a next hop address table entry of the second aggregation routing device;
the decapsulation module is configured to resolve the public private network label to obtain an entry containing a next hop address as the first aggregation routing device address or a destination node address;
and the second packaging module is configured to package the target public private network label into the first routing information and issue the first routing information packaged with the target public private network label to the second access equipment.
10. An electronic device, comprising:
a memory for storing executable instructions; and the number of the first and second groups,
a processor for display with the memory to execute the executable instructions to perform the operations of the method of data transmission of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111162888.5A CN113765794B (en) | 2021-09-30 | 2021-09-30 | Data transmission method and device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111162888.5A CN113765794B (en) | 2021-09-30 | 2021-09-30 | Data transmission method and device, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113765794A CN113765794A (en) | 2021-12-07 |
| CN113765794B true CN113765794B (en) | 2022-11-25 |
Family
ID=78798632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111162888.5A Active CN113765794B (en) | 2021-09-30 | 2021-09-30 | Data transmission method and device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113765794B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1725731A (en) * | 2005-05-19 | 2006-01-25 | 杭州华为三康技术有限公司 | Method for controlling number of Layer2 Ethernet ring equipment MAC address learning |
| CN102638413A (en) * | 2012-05-14 | 2012-08-15 | 杭州华三通信技术有限公司 | Route issuing method and provider edge device |
| CN102724118A (en) * | 2012-06-06 | 2012-10-10 | 华为技术有限公司 | Label distribution method and device |
| CN103001872A (en) * | 2011-09-13 | 2013-03-27 | 华为技术有限公司 | A label distribution method and aggregation device |
| CN110572326A (en) * | 2019-09-27 | 2019-12-13 | 新华三信息安全技术有限公司 | Method, device, network equipment and system for establishing forwarding path |
| CN110896379A (en) * | 2018-09-13 | 2020-03-20 | 中兴通讯股份有限公司 | Message sending method, binding relationship notification method, device and storage medium |
| CN111385206A (en) * | 2018-12-29 | 2020-07-07 | 北京华为数字技术有限公司 | Message forwarding method, network system, related equipment and computer storage medium |
| CN113206787A (en) * | 2020-01-31 | 2021-08-03 | 中国移动通信有限公司研究院 | Method and device for processing segment identifiers |
-
2021
- 2021-09-30 CN CN202111162888.5A patent/CN113765794B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1725731A (en) * | 2005-05-19 | 2006-01-25 | 杭州华为三康技术有限公司 | Method for controlling number of Layer2 Ethernet ring equipment MAC address learning |
| CN103001872A (en) * | 2011-09-13 | 2013-03-27 | 华为技术有限公司 | A label distribution method and aggregation device |
| CN102638413A (en) * | 2012-05-14 | 2012-08-15 | 杭州华三通信技术有限公司 | Route issuing method and provider edge device |
| CN102724118A (en) * | 2012-06-06 | 2012-10-10 | 华为技术有限公司 | Label distribution method and device |
| CN110896379A (en) * | 2018-09-13 | 2020-03-20 | 中兴通讯股份有限公司 | Message sending method, binding relationship notification method, device and storage medium |
| CN111385206A (en) * | 2018-12-29 | 2020-07-07 | 北京华为数字技术有限公司 | Message forwarding method, network system, related equipment and computer storage medium |
| CN110572326A (en) * | 2019-09-27 | 2019-12-13 | 新华三信息安全技术有限公司 | Method, device, network equipment and system for establishing forwarding path |
| CN113206787A (en) * | 2020-01-31 | 2021-08-03 | 中国移动通信有限公司研究院 | Method and device for processing segment identifiers |
Non-Patent Citations (1)
| Title |
|---|
| MPLS L3VPN组网中BGP协议路由汇聚的标签分配策略;于俊锋等;《铁路计算机应用》;20120728(第07期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113765794A (en) | 2021-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7481436B2 (en) | Method, device and system for forwarding packets in a SR network | |
| CN104350714B (en) | A kind of message forwarding method and VxLAN gateways | |
| TWI744359B (en) | Method for data transmission and network equipment | |
| CN113326228B (en) | Message forwarding method, device and equipment based on remote direct data storage | |
| US12355666B2 (en) | Method for forwarding packet in hybrid network, device, and system | |
| CN106254256B (en) | Data message forwarding method and equipment based on three layers of VXLAN gateway | |
| EP4160950B1 (en) | Method and apparatus for sending a message, and network device, system and storage medium | |
| CN109617995B (en) | Management system and method for VPC (virtual private network) internal container of tenant cluster and electronic equipment | |
| CN111510386B (en) | Method and device for processing message | |
| CN110311860B (en) | Multilink load balancing method and device under VXLAN | |
| CN113132202A (en) | Message transmission method and related equipment | |
| US20230336478A1 (en) | Packet transmission method, apparatus, device, and system, and storage medium | |
| CN113630316B (en) | Data transmission method and communication device | |
| JP7448597B2 (en) | Message generation method and device and message processing method and device | |
| EP4236245A1 (en) | Route advertisement method, apparatus, and system | |
| CN109286564B (en) | Message forwarding method and device | |
| CN113765794B (en) | Data transmission method and device, electronic equipment and medium | |
| CN109218258B (en) | Data packet transmission method and gateway equipment | |
| CN111464443A (en) | Message forwarding method, device, equipment and storage medium based on service function chain | |
| CN114900458B (en) | Message forwarding method, device, medium and product | |
| CN113596038B (en) | Data packet parsing method and server | |
| CN108259350A (en) | A kind of message transmitting method, device and machine readable storage medium | |
| CN113992558B (en) | Method, device, electronic equipment and medium for route publishing | |
| US20230018873A1 (en) | Method and system for processing encapsulated wireless traffic | |
| CN116455810A (en) | Message forwarding method, device, readable storage medium and electronic equipment |
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 |