WO2023050313A1 - 一种报文处理方法、装置、网络设备及介质 - Google Patents

一种报文处理方法、装置、网络设备及介质 Download PDF

Info

Publication number
WO2023050313A1
WO2023050313A1 PCT/CN2021/122183 CN2021122183W WO2023050313A1 WO 2023050313 A1 WO2023050313 A1 WO 2023050313A1 CN 2021122183 W CN2021122183 W CN 2021122183W WO 2023050313 A1 WO2023050313 A1 WO 2023050313A1
Authority
WO
WIPO (PCT)
Prior art keywords
segment
srv6
slice
address
oam message
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.)
Ceased
Application number
PCT/CN2021/122183
Other languages
English (en)
French (fr)
Inventor
李�昊
林长望
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to JP2023572012A priority Critical patent/JP7685076B2/ja
Priority to US18/563,785 priority patent/US20240283733A1/en
Priority to CN202180002802.4A priority patent/CN117280671A/zh
Priority to EP21958885.2A priority patent/EP4412181A4/en
Priority to KR1020237038000A priority patent/KR102912343B1/ko
Priority to PCT/CN2021/122183 priority patent/WO2023050313A1/zh
Publication of WO2023050313A1 publication Critical patent/WO2023050313A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/34—Source routing
    • 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
    • H04L45/026—Details of "hello" or keep-alive messages
    • 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/72—Routing based on the source address
    • 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
    • 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/76—Routing in software-defined topologies, e.g. routing between virtual machines
    • 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/80—Ingress point selection by the source endpoint, e.g. selection of ISP or POP

Definitions

  • the present application relates to the technical field of communications, and in particular to a message processing method, device, network equipment and media.
  • Network slicing is an on-demand networking method that can separate multiple virtual end-to-end networks on the same network.
  • the network topology can be divided into multiple topologies, and the resources in the topology can be further sliced through the controller to reserve bandwidth resources for each slice.
  • Different service level agreement (service level agreement, SLA) guarantees can be provided for different services through network slicing.
  • slices can be associated with pre-allocated hardware queues to reserve specified bandwidth resources for the slices.
  • IPv6 Segment Routing Segment Routing IPv6, SRv6
  • the head node in the bearer network performs IPv6 encapsulation on the original packet to obtain the encapsulated packet.
  • Protocol version 6, IPv6 IPv6
  • the lower N bits of the address carry the slice ID.
  • the intermediate node in the bearer network can associate with the pre-allocated hardware queue based on the slice ID carried in the encapsulated message, and use the bandwidth resources corresponding to the hardware queue to forward the encapsulated message.
  • the slice network segment of the slice domain is 2001:2002:2003:2004::/64
  • the slice network segment configured for the head node in the slice domain is 2001:2002:2003:2004:nodeid::/96
  • the nodeid is The node ID of the head node.
  • the slice ID can be carried by the host bit of the slice network segment.
  • OAM Operations, Administration, and Maintenance
  • the node receiving the OAM message will exchange the source IPv6 address and the destination IPv6 address of the OAM message to generate a response message of the OAM message, and send the response message to the head node. That is to say, the destination IPv6 address in the response message is the address carrying the slice ID: 2001:2002:2003:2004:0000:0002::1, which is inconsistent with the host address of the head node. In the case of a large number of slices, there will be a large number of destination addresses for response messages. After the head node receives these response messages, how to make these response messages be correctly sent to the control plane is an urgent problem to be solved. question.
  • the purpose of the embodiment of the present application is to provide a message processing method, device, network device and medium, so as to solve the problem that the response message of the OAM message cannot be sent to the control plane.
  • the specific technical scheme is as follows:
  • the embodiment of the present application provides a message processing method, the method is applied to the head node in the SRv6 network, and the method includes:
  • the source address of the first SRv6 OAM message includes a network segment, a host segment, and a slice segment, and the slice segment includes a slice identifier;
  • the loopback address of the head node includes a network segment, a host segment, and a slice segment with a slice bit of 0, and the host segment included in the loopback address includes the node identifier of the master node;
  • Generate the first SRv6 OAM message including:
  • the method before generating the first SRv6 OAM message, the method further includes:
  • the route advertisement message includes the loopback address
  • the embodiment of the present application provides a message processing method, the method is applied to a destination node in an SRv6 network, and the method includes:
  • the source address of the first SRv6 OAM message includes a network segment, a host segment and a slice segment, and the slice segment includes a slice identifier;
  • the slice segment in the source address is cleared, and the slice segment is cleared
  • the source address after is used as the destination address of the second SRv6 OAM message
  • the clearing the segment in the source address includes:
  • the slice segment of the source address is cleared.
  • the method before receiving the first SRv6 OAM message from the head node, the method further includes:
  • the route notification report includes the loopback address of the head node, the loopback address includes a network segment, a host segment, and a slice segment with a slice bit of 0, and the loopback address includes The host segment includes the node identifier of the master node;
  • a forwarding entry is generated according to the loopback address.
  • an embodiment of the present application provides a message processing device, the device is applied to a head node in an SRv6 network, and the device includes:
  • the source address of the first SRv6 OAM message includes a network segment, a host segment and a slice segment, and the slice segment includes a slice identifier;
  • a sending module configured to send the first SRv6 OAM message to a destination node, so that after the destination node receives the first SRv6 OAM message, if it is determined according to the network segment and the host segment
  • the source address in the first SRv6 OAM message belongs to the specified slice network segment, then the slice segment in the source address is cleared, and the source address whose slice segment is cleared is used as the destination address of the second SRv6 OAM message, and sending the second SRv6 OAM message to the head node;
  • a receiving module configured to receive the second SRv6 OAM message, where the second SRv6 OAM message includes a destination address
  • a sending module configured to send the second SRv6 OAM message to the control plane if the destination address is the same as the host address of the head node.
  • the loopback address of the head node includes a network segment, a host segment, and a slice segment with a slice bit of 0, and the host segment included in the loopback address includes the node identifier of the master node;
  • the generating module is further configured to generate a route advertisement message, where the route advertisement message includes the loopback address;
  • the sending module is further configured to send the route advertisement message to other nodes in the SRv6 network except the head node, so that the node that receives the route advertisement message generates an address based on the loopback address. Forward entry.
  • an embodiment of the present application provides a message processing device, the device is applied to a destination node in an SRv6 network, and the device includes:
  • a receiving module configured to receive the first SRv6 OAM message from the head node, the source address of the first SRv6 OAM message includes a network segment, a host segment and a slice segment, and the slice segment includes a slice identifier;
  • a matching module configured to match the source address of the first SRv6 OAM message with the specified slice network segment according to the network segment and the host segment;
  • An encapsulation module configured to, if it is determined according to the network segment and the host segment that the source address of the first SRv6 OAM message belongs to the specified segment network segment, clear the segment in the source address, and set The source address after the segment is cleared is used as the destination address of the second SRv6 OAM message;
  • a sending module configured to send the second SRv6 OAM message to the head node.
  • the encapsulation module is specifically configured to clear the slice segment of the source address to zero based on the pre-configured slice bit length information.
  • the device further includes a generating module
  • the receiving module is further configured to receive a route notification message sent by the head node, the route notification report includes the loopback address of the head node, and the loopback address includes a network segment, a host segment, and a slice bit of 0 Slicing segment, the host segment included in the loopback address includes the node identifier of the master node;
  • the generating module is configured to generate a forwarding entry according to the loopback address.
  • the embodiment of the present application further provides a network device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete mutual communication through the communication bus;
  • the processor is configured to implement the steps of the message processing method described in the first aspect or the second aspect when executing the program stored in the memory.
  • the embodiment of the present application also provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the computer program in the first aspect or the second aspect is implemented.
  • a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the computer program in the first aspect or the second aspect is implemented.
  • the embodiment of the present application further provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute the message processing method described in the first aspect or the second aspect.
  • the source address of the first SRv6 OAM message generated by the head node includes the network segment, the host segment and the slice segment, after the destination node receives the first SRv6 OAM message, if according to the network segment and the host segment It is determined that the source address belongs to the specified slice network segment, then the slice segment of the source address can be cleared, and the source address whose slice segment is cleared is used as the destination address of the second SRv6 OAM message.
  • the host address of the head node is usually composed of the network segment and the host segment, after clearing the segments in the above source address, the host address of the head node is obtained, that is to say, the second SRv6 OAM received by the head node
  • the destination address of the message is its own host address, and then the forwarding plane of the head node can correctly send the second SRv6 OAM message to the control plane.
  • FIG. 1 is an architecture diagram of an SRv6 network provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a segmented structure of a source address in the related art
  • FIG. 3 is a schematic diagram of a segmented structure of a source address provided by an embodiment of the present application.
  • FIG. 4 is a flow chart of a message processing method provided in an embodiment of the present application.
  • FIG. 5 is a flow chart of another message processing method provided by the embodiment of the present application.
  • FIG. 6 is a flowchart of another message processing method provided by the embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a message processing device provided in an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another message processing device provided in an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • the embodiment of the present application can be applied in the SRv6 network.
  • the SRv6 network is a sliced network.
  • the SRv6 network includes four nodes, respectively P1 , P2, P3 and P4, where P1 is the head node and P4 is the tail node.
  • the P1 node can perform IPv6 encapsulation for the original message.
  • it can carry the slice ID (Slice ID) in the source address of the IPv6 header.
  • the encapsulated original message includes a destination address (Destination Address, DA), a source address (Source Address, SA) carrying a slice ID, a segment routing extension header (Segment Routing Header, SRH) and the original message.
  • the packet carrying the slice identifier is transmitted between P1 and P2, and the packet carrying the slice identifier is also transmitted between P2 and P3.
  • the P4 node will receive the encapsulated packet Perform decapsulation to restore the original message, and forward the original message according to the destination address of the original message.
  • the slice prefix is 32 bits
  • the node ID (node id) is 16 bits
  • the slice ID is 32 bits.
  • the source address includes a network segment and a host segment.
  • the host segment carries the slice identifier.
  • Table 1 shows two source addresses carrying slice identifiers.
  • the source address A slice segment is added to the address, that is, the source address can be divided into 3 segments, namely the network segment, the host segment and the segment segment, and the segment identifier is carried by the segment segment.
  • the source address has a total of 128 bits
  • the network segment can be 80 bits
  • the host segment can be 16 bits
  • the slice segment can be 32 bits
  • the network segment is 64 bits
  • both the host segment and the slice segment are 32 bits.
  • the lengths of the network segment, the host segment and the slice segment can be configured according to actual requirements, which is not limited in this embodiment of the present application.
  • the network segment is 64 bits, and the slice segment and host segment are both 32 bits. Still using the network segment 2001:2002:2003:2004::/64 as an example, the final presentation of the source address is still as shown in Table 1 above. source address form, but the segmentation method has changed.
  • nodes in the embodiments of the present application may also be referred to as node devices, and the node devices may be routers, switches, and the like.
  • the embodiment of the present application provides a message processing method, the method is applied to the head node in the SRv6 network, as shown in Figure 4, the method includes:
  • S401 Generate a first SRv6 OAM message, where the source address of the first SRv6 OAM message includes a network segment, a host segment, and a slice segment, and the slice segment includes a slice identifier.
  • the first SRv6 OAM message is used to detect the connectivity of the SRv6 path and locate the faulty node in the SRv6 path.
  • the first SRv6 OAM message may be a ping message, a traceroute message, Bidirectional Forwarding Detection (Bidirectional Forwarding Detection, BFD), etc.
  • the ping message is used to detect whether the nodes in the slice are reachable in the slice domain
  • the traceroute message is used to detect whether the nodes in the slice are reachable, and can also be used to analyze which node fails.
  • the destination node is other nodes belonging to the same SRv6 network as the head node.
  • the destination node can be the P2 node, P3 node or P4 node in FIG. 1 .
  • the specified slice network segment can be "2001:2002:2003:2004:nodeid::", the nodeid is the node ID of the head node .
  • the source address in the first SRv6 OAM message is 2001:2002:2003:2004:0000:0002::1, and the source address "2001:2002:2003:2004:” belongs to the network segment, "0000:0002:” belongs to the host segment, and "0000:0001” belongs to the slice segment.
  • the source address belongs to the specified slice network segment 2001:2002:2003:2004:0000:0002::, so the destination node can clear the slices included in the source address to get 2001:2002:2003:2004:0000: 0002::, and then use 2001:2002:2003:2004:0000:0002:: as the destination address of the second SRv6 OAM message, and use the destination address included in the first SRv6 OAM message as the destination address of the second SRv6 OAM message source address.
  • the second SRv6 OAM message is a response message of the ping message.
  • the second SRv6 OAM message is an Internet Control Message Protocol (Internet Control Message Protocol, ICMP) timeout message.
  • Internet Control Message Protocol Internet Control Message Protocol, ICMP
  • the second SRv6 OAM packet is a BFD response packet.
  • the second SRv6 OAM message includes a destination address, and the destination address is 2001:2002:2003:2004:0000:0002::.
  • the forwarding plane of the head node can obtain the destination address 2001:2002:2003:2004:0000:0002:: of the second SRv6 OAM message, because the purpose The address does not carry the slice ID, and is the same as the host address of the head node, so the second SRv6 OAM message can be sent to the control plane.
  • the source address of the first SRv6 OAM message generated by the head node includes a network segment, a host segment, and a slice segment
  • the destination node receives the first SRv6 OAM message
  • the slice segment of the source address can be cleared, and the source address whose slice segment is cleared can be used as the destination address of the second SRv6 OAM message.
  • the host address of the head node is usually composed of the network segment and the host segment, after clearing the segments in the above source address, the host address of the head node is obtained, that is to say, the second SRv6 OAM received by the head node
  • the destination address of the message is its own host address, and then the forwarding plane of the head node can correctly send the second SRv6 OAM message to the control plane.
  • a loopback (loopback) address may be pre-configured for the head node, and the loopback address may be configured as the source address of the slice.
  • the loopback address includes a network segment, a host segment, and a slice segment whose slice bit is 0, and the host segment included in the loopback address includes a node identifier of the head node.
  • the head node uses the loopback address as its own host address.
  • the loopback address is 2001:2002:2003:2004:nodeid::/128.
  • the process that the head node generates the first SRv6 OAM message includes:
  • the slice bits in the segment of the loopback address are all 0, and when the segment identifier needs to be carried in the message, the slice identifier to be carried can be directly filled in the segment of the loopback address, so that the obtained address can be used as The source address of the packet.
  • the slice identifiers of the slices to which the head node and the destination node belong can be directly filled in the slice segment of the loopback address, thereby using the obtained address as the source address of the first SRv6 OAM message.
  • the loopback address is 2001:2002:2003:2004:0000:0005::/128, and if the slice ID of the slice to which the head node and the destination node belong is 3, the slice The identifier 3 is filled into the slice segment of the loopback address, and the source address 2001:2002:2003:2004:0000:0005::3 is obtained.
  • the source address when generating the first SRv6 OAM message, the source address can be generated simply by filling the required slice identifier into the slice segment of the loopback address of the head node.
  • the host segment of the source address and the slice segment are set independently in the embodiment of the present application, after the destination node receives the first SRv6 OAM message, if it is determined that the first SRv6 OAM belongs to the specified slice segment, the segment segment In this way, the host address of the outgoing node can be restored, and then the host address can be used as the destination address of the second SRv6 OAM message.
  • the master node does not need additional matching operations, and can naturally support the sending of the second SRv6 OAM message. control surface.
  • the slice identifier is carried in the host segment, and the destination node cannot delete the slice identifier in the host segment.
  • the control plane of the master node can send all addresses with slice identifiers as host addresses to the forwarding plane. In this way, if the purpose of the message received by the forwarding plane is The address carries the slice identifier, and the forwarding plane can also send the packet to the control plane.
  • the network segment of the slice is very large, and correspondingly there are many addresses carrying the slice identifier, and the control plane will take up a lot of resources to deliver the addresses carrying the slice identifier to the forwarding plane one by one.
  • the destination node can restore the host address of the head node that does not carry the slice identifier, and the destination address of the second SRv6 OAM message returned by the destination node to the head node does not carry the slice identifier, so in the embodiment of the application, the host The control plane of the node only needs to send the local address to the forwarding plane, and then the second SRv6 OAM message can be sent to the control plane. There is no need to issue addresses carrying slice identifiers one by one, which can reduce the occupation of resources.
  • the method before the process shown in FIG. 4, the method further includes:
  • Generate a route advertisement message which includes a loopback address, and send a route advertisement message to other nodes in the SRv6 network except the head node, so that the node that receives the route advertisement message generates a forwarding table based on the loopback address item.
  • the head node sends a route advertisement message to the above destination node, and after the destination node receives the route advertisement message, the next hop of the generated forwarding entry is the loopback address carried in the route advertisement message.
  • the next hop is the address of the physical interface of the device connected to the destination node among the devices included in the path from the destination node to the head node.
  • the next hop of the forwarding entry generated by the destination node is: the physical address of the interface connected to the destination node on the head node.
  • the head node is node 1
  • physical interface A of node 1 is connected to node 2
  • physical interface B of node 2 is connected to node 3
  • the next hop in the forwarding entry generated by node 2 is the physical interface of physical interface A.
  • the next hop in the forwarding entry generated by node 3 is the physical address of physical interface B.
  • node that receives the route advertisement message can also generate forwarding entries in the same way.
  • the head node advertises the loopback address as a common host address.
  • other nodes can generate a forwarding entry based on the loopback address, so that the head node can send The second SRv6 OAM packet identified.
  • the network segment that needs special maintenance for the head node is simplified to the host address of the head node, so that there is no need for special maintenance of the network segment. It is closer to the processing of the head node itself, which simplifies the processing of the head node.
  • the embodiment of the present application also provides a message processing device, the device is applied to the destination node in the SRv6 network, as shown in Figure 6, the method includes:
  • the host segment includes the node identifier of the head node.
  • the source address in the first SRv6 OAM message is 2001:2002:2003:2004:0000:0002::1, the "2001:2002:2003:2004:” belongs to the network segment, and "0000:0002:” It belongs to the host segment. It can be seen that the source address belongs to the specified slice network segment 2001:2002:2003:2004:0000:0002::.
  • each node in the SRv6 network is configured with the specified slice network segment and slice bit length information.
  • the destination node receives the first SRv6 OAM message, if it is determined that the source address of the first SRv6 OAM message belongs to the specified slice network segment, it can be determined that the source address carries the slice identifier, and then it can be based on the pre-configured slice bit length information , to clear the slices included in the source address to obtain the host address of the head node.
  • the destination node may clear the lower 16 bits of the source address to zero.
  • the destination node may clear the lower 32 bits of the source address to zero.
  • the source address of the first SRv6 OAM packet received by the destination node includes the network segment, the host segment and the slice segment, so the destination node can directly send The segment segment of the source address is cleared, and the source address whose segment segment is cleared is used as the destination address of the second SRv6 OAM message. Because the host address of the head node is usually composed of the network segment and the host segment, after clearing the segments in the above source address, the host address of the head node is obtained, that is to say, the second SRv6 OAM received by the head node The destination address of the message is its own host address, and then the forwarding plane of the head node can correctly send the second SRv6 OAM message to the control plane.
  • the method further includes:
  • the routing notification report includes the loopback address of the head node.
  • the loopback address includes the network segment, the host segment, and the slice segment with a slice bit of 0.
  • the host segment included in the loopback address includes the node identifier of the master node.
  • the next hop of the generated forwarding entry is the loopback address carried in the route advertisement message.
  • the next hop is the address of the physical interface of the device connected to the destination node among the devices included in the path from the destination node to the head node.
  • the destination node may send the second SRv6 OAM message to the head node based on the above forwarding entry.
  • each node in the SRv6 network generates a forwarding entry according to the loopback entry, and then sends a second SRv6 OAM message that does not carry a slice identifier to the head node according to the forwarding entry, so that the forwarding plane of the head node can use the
  • the second SRv6 OAM message is sent to the control plane without configuring a complex matching mechanism for the head node, which can avoid the situation that the second SRv6 OAM message cannot be sent to the control plane.
  • the embodiment of the present application also provides a packet processing device, which is applied to the head node in the SRv6 network, as shown in Figure 7, the device includes:
  • Generating module 701 for generating the first SRv6 OAM message, the source address of the first SRv6 OAM message includes network segment, host segment and slice segment, and slice segment includes slice identifier;
  • the sending module 702 is configured to send the first SRv6 OAM message to the destination node, so that after the destination node receives the first SRv6 OAM message, if it is determined according to the network segment and the host segment that the source address in the first SRv6 OAM message belongs to Specify the slice network segment, then clear the slice segment in the source address, use the cleared source address of the slice segment as the destination address of the second SRv6 OAM message, and send the second SRv6 OAM message to the head node;
  • a receiving module 703, configured to receive a second SRv6 OAM message, where the second SRv6 OAM message includes a destination address;
  • the sending module 704 is configured to send the second SRv6 OAM message to the control plane if the destination address is the same as the host address of the head node.
  • the loopback address of the head node includes a network segment, a host segment, and a slice segment whose slice bit is 0, and the host segment included in the loopback address includes a node identifier of the master node.
  • the generation module 701 is specifically used for:
  • the source address is obtained by filling the slice identifier in the segment of the loopback address, and generating the first SRv6 OAM message.
  • the generation module 701 is further configured to generate a route notification message, where the route notification message includes a loopback address;
  • the sending module 702 is further configured to send a route advertisement message to other nodes in the SRv6 network except the head node, so that the node receiving the route advertisement message generates a forwarding entry based on the loopback address.
  • the embodiment of the present application also provides another packet processing device, the device is applied to the destination node in the SRv6 network, as shown in Figure 8, the device includes:
  • the receiving module 801 is configured to receive the first SRv6 OAM message from the head node, the source address of the first SRv6 OAM message includes a network segment, a host segment and a slice segment, and the slice segment includes a slice identifier;
  • the matching module 802 is used to match the source address of the first SRv6 OAM message with the specified slice network segment according to the network segment and the host segment;
  • the encapsulation module 803 is used to determine the source address of the first SRv6 OAM message according to the network segment and the host segment to belong to the specified slice network segment, then clear the slice segment in the source address, and the source address after the slice segment is cleared As the destination address of the second SRv6 OAM message;
  • a sending module 804 configured to send the second SRv6 OAM message to the head node.
  • the encapsulation module 803 is specifically configured to clear the slice segment of the source address to zero based on the pre-configured slice bit length information.
  • the device further includes a generating module
  • the receiving module 801 is also used to receive the routing notification message sent by the head node.
  • the routing notification report includes the loopback address of the head node.
  • the loopback address includes a network segment, a host segment, and a segment with a slice bit of 0.
  • the loopback address includes a host segment Including the node identification of the master node;
  • the generation module is used to generate forwarding entries according to the loopback address.
  • the embodiment of the present application also provides a network device.
  • the network device can be the head node in the above embodiment or the destination node, as shown in FIG. 9 , including a processor 901, a communication interface 902, a memory 903 and a communication A bus 904, wherein, the processor 901, the communication interface 902, and the memory 903 complete mutual communication through the communication bus 904,
  • Memory 903 used to store computer programs
  • the processor 901 is configured to implement the method steps in the foregoing method embodiments when executing the program stored in the memory 903 .
  • the communication bus mentioned in the aforementioned network device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus or the like.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the communication bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.
  • the communication interface is used for communication between the above-mentioned network device and other devices.
  • the memory may include a random access memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk memory.
  • RAM Random Access Memory
  • NVM non-Volatile Memory
  • the memory may also be at least one storage device located far away from the aforementioned processor.
  • the above-mentioned processor can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (Digital Signal Processor, DSP), a dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any message processing described above is implemented. method steps.
  • a computer program product including instructions is also provided, which, when run on a computer, causes the computer to execute any packet processing method in the foregoing embodiments.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • each embodiment in this specification is described in a related manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments.
  • the description is relatively simple, and for relevant parts, please refer to part of the description of the method embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种报文处理方法、装置、网络设备及介质，涉及通信技术领域。该方法应用于SRv6网络内的头节点，该方法包括：生成第一SRv6 OAM报文，第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，切片段包括切片标识，然后向目的节点发送第一SRv6 OAM报文，以使得目的节点接收到第一SRv6 OAM报文后，若根据网络段和主机段确定第一SRv6 OAM报文中的源地址属于指定切片网段，则将源地址中的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址，并向头节点发送第二SRv6 OAM报文。接收第二SRv6 OAM报文，若目的地址与头节点的主机地址相同，则向控制面上送第二SRv6 OAM报文。可以使得第二SRv6 OAM报文被正确上送控制面。

Description

一种报文处理方法、装置、网络设备及介质 技术领域
本申请涉及通信技术领域，特别是涉及一种报文处理方法、装置、网络设备及介质。
背景技术
网络切片是一种按需组网的方式，可以在同一网络上分离出多个虚拟的端到端网络。在控制面上，可以将网络拓扑切分为多个拓扑，再通过控制器将拓扑内的资源进行进一步切片，为每个切片预留带宽资源。通过网络切片可以为不同的业务提供不同的服务等级协议(service level agreement，SLA)保证。
在转发面处理报文时，可以将切片与预先分配的硬件队列关联，从而为该切片预留指定的带宽资源。以IPv6段路由(Segment Routing IPv6，SRv6)场景为例，当原始报文进入承载网后，承载网中的头节点对原始报文进行IPv6封装得到封装报文，通过源互联网协议版本6(internet protocol version 6，IPv6)地址的低N位携带切片ID。承载网络中的中间节点接收到该封装报文后，能够基于该封装报文中携带的切片ID，关联到预先分配的硬件队列，使用该硬件队列对应的带宽资源来转发该封装报文。
为了使得中间节点能够识别封装报文的源IPv6地址中是否携带切片ID，需要提前规划专属于切片域的切片网段，并需要为切片域内的每个节点配置一个网段。例如，切片域的切片网段为2001:2002:2003:2004::/64，为切片域内的头节点配置的切片网段为2001:2002:2003:2004:nodeid::/96，该nodeid为头节点的节点标识。
目前，可以使用切片网段的主机位携带切片ID，例如，在该主节点向切片域内的其他节点发送操作、管理和维护(Operations,Administration,and Maintenance，OAM)报文时，假设若切片ID为1，头节点的节点标识为2，则该OAM报文的源IPv6地址为2001:2002:2003:2004:0000：0002::1，其中，“2001:2002:2003:2004:0000:0002”为该源IPv6地址的网络段，“0000:0001”为该 源IPv6地址的主机段。
接收到该OAM报文的节点会将该OAM报文的源IPv6地址和目的IPv6地址调换，以生成OAM报文的应答报文，并向头节点发送该应答报文。也就是说，应答报文中的目的IPv6地址为携带切片ID的地址：2001:2002:2003:2004:0000：0002::1，该目的IPv6地址与头节点的主机地址不一致。在有海量切片的情况下，作为应答报文的目的地址的数量会很多，在头节点接收到这些应答报文后，如何使得这些应答报文被正确上送至控制面是一个亟需解决的问题。
发明内容
本申请实施例的目的在于提供一种报文处理方法、装置、网络设备及介质，以解决OAM报文的应答报文无法上送控制面的问题。具体技术方案如下：
第一方面，本申请实施例提供一种报文处理方法，所述方法应用于SRv6网络内的头节点，所述方法包括：
生成第一SRv6 OAM报文，所述第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
向目的节点发送所述第一SRv6 OAM报文，以使得所述目的节点接收到所述第一SRv6 OAM报文后，若根据所述网络段和所述主机段确定所述第一SRv6 OAM报文中的源地址属于指定切片网段，则将所述源地址中的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址，并向所述头节点发送所述第二SRv6 OAM报文；
接收所述第二SRv6 OAM报文，所述第二SRv6 OAM报文包括目的地址；
若所述目的地址与所述头节点的主机地址相同，则向控制面上送所述第二SRv6 OAM报文。
在一种可能的实现方式中，所述头节点的回环地址包括网络段、主机段和切片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；所述生成第一SRv6 OAM报文，包括：
获取所述头节点与所述目的节点所属切片的切片标识，所述切片标识属 于所述指定切片网段；
在所述回环地址的切片段填充所述切片标识得到源地址，生成所述第一SRv6 OAM报文。
在一种可能的实现方式中，在所述生成第一SRv6 OAM报文之前，所述方法还包括：
生成路由通告报文，所述路由通告报文包括所述回环地址；
向所述SRv6网络内除所述头节点之外的其他节点发送所述路由通告报文，以使得接收到所述路由通告报文的节点基于所述回环地址生成转发表项。
第二方面，本申请实施例提供一种报文处理方法，所述方法应用于SRv6网络内的目的节点，所述方法包括：
接收来自头节点的第一SRv6 OAM报文，所述第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
根据所述网络段和所述主机段将所述第一SRv6 OAM报文的源地址与指定切片网段进行匹配；
若根据所述网络段和所述主机段确定所述第一SRv6 OAM报文的源地址属于所述指定切片网段，则将所述源地址中的切片段清零，将切片段被清零后的所述源地址作为第二SRv6 OAM报文的目的地址；
向所述头节点发送所述第二SRv6 OAM报文。
在一种可能的实现方式中，所述将所述源地址中的切片段清零，包括：
基于预先配置的切片位长度信息，将所述源地址的切片段清零。
在一种可能的实现方式中，在所述接收来自头节点的第一SRv6 OAM报文之前，所述方法还包括：
接收所述头节点发送的路由通告报文，所述路由通告报包括所述头节点的回环地址，所述回环地址包括网络段、主机段和切片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；
根据所述回环地址生成转发表项。
第三方面，本申请实施例提供一种报文处理装置，所述装置应用于SRv6网络内的头节点，所述装置包括：
生成模块，用于生成第一SRv6 OAM报文，所述第一SRv6 OAM报文的 源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
发送模块，用于向目的节点发送所述第一SRv6 OAM报文，以使得所述目的节点接收到所述第一SRv6 OAM报文后，若根据所述网络段和所述主机段确定所述第一SRv6 OAM报文中的源地址属于指定切片网段，则将所述源地址中的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址，并向所述头节点发送所述第二SRv6 OAM报文；
接收模块，用于接收所述第二SRv6 OAM报文，所述第二SRv6 OAM报文包括目的地址；
上送模块，用于若所述目的地址与所述头节点的主机地址相同，则向控制面上送所述第二SRv6 OAM报文。
在一种可能的实现方式中，所述头节点的回环地址包括网络段、主机段和切片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；所述生成模块，具体用于：
获取所述头节点与所述目的节点所属切片的切片标识，所述切片标识属于所述指定切片网段；
在所述回环地址的切片段填充所述切片标识得到源地址，生成所述第一SRv6 OAM报文。
在一种可能的实现方式中，所述生成模块，还用于生成路由通告报文，所述路由通告报文包括所述回环地址；
所述发送模块，还用于向所述SRv6网络内除所述头节点之外的其他节点发送所述路由通告报文，以使得接收到所述路由通告报文的节点基于所述回环地址生成转发表项。
第四方面，本申请实施例提供一种报文处理装置，所述装置应用于SRv6网络内的目的节点，所述装置包括：
接收模块，用于接收来自头节点的第一SRv6 OAM报文，所述第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
匹配模块，用于根据所述网络段和所述主机段将所述第一SRv6 OAM报文的源地址与指定切片网段进行匹配；
封装模块，用于若根据所述网络段和所述主机段确定所述第一SRv6 OAM 报文的源地址属于所述指定切片网段，则将所述源地址中的切片段清零，将切片段被清零后的所述源地址作为第二SRv6 OAM报文的目的地址；
发送模块，用于向所述头节点发送所述第二SRv6 OAM报文。
在一种可能的实现方式中，所述封装模块，具体用于基于预先配置的切片位长度信息，将所述源地址的切片段清零。
在一种可能的实现方式中，所述装置还包括生成模块；
所述接收模块，还用于接收所述头节点发送的路由通告报文，所述路由通告报包括所述头节点的回环地址，所述回环地址包括网络段、主机段和切片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；
所述生成模块，用于根据所述回环地址生成转发表项。
第五方面，本申请实施例还提供一种网络设备，包括处理器、通信接口、存储器和通信总线，其中，处理器，通信接口，存储器通过通信总线完成相互间的通信；
存储器，用于存放计算机程序；
处理器，用于执行存储器上所存放的程序时，实现上述第一方面或第二方面所述的报文处理方法步骤。
第六方面，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现第一方面或第二方面中所述的报文处理方法。
第七方面，本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面中所述的报文处理方法。
采用上述技术方案，因头节点生成的第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所以目的节点接收到该第一SRv6 OAM报文后，如果根据网络段和主机段确定源地址属于指定切片网段，则可将源地址的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址。因头节点的主机地址通常是由网络段和主机段组成，所以将上述源地址中的切片段清零后，得到的就是头节点的主机地址，也就是说头节点接收到的第二SRv6 OAM报文的目的地址就是自身的主机地址，进而头节点的转发面可 以将该第二SRv6 OAM报文正确上送控制面。
当然，实施本申请的任一产品或方法并不一定需要同时达到以上所述的所有优点。
附图说明
为了更清楚地说明本申请实施例和现有技术的技术方案，下面对实施例和现有技术中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的实施例。
图1为本申请实施例提供的一种SRv6网络的架构图；
图2为本相关技术中的源地址的分段结构示意图；
图3为本申请实施例提供的一种源地址的分段结构示意图；
图4为本申请实施例提供的一种报文处理方法的流程图；
图5为本申请实施例提供的另一种报文处理方法的流程图；
图6为本申请实施例提供的另一种报文处理方法的流程图；
图7为本申请实施例提供的一种报文处理装置的结构示意图；
图8为本申请实施例提供的另一种报文处理装置的结构示意图；
图9为本申请实施例提供的一种网络设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案、及优点更加清楚明白，以下参照附图并举实施例，对本申请进一步详细说明。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
首先对本申请实施例的应用场景进行介绍，本申请实施例可以应用在SRv6网络中，该SRv6网络是一个切片网络，例如，如图1所示，该SRv6网络中包括四个节点，分别为P1、P2、P3和P4，其中P1为头节点，P4为尾节点。
以图1所示的SRv6网络为例，P1节点接收到原始报文后，可以为原始报文进行IPv6封装，在进行IPv6封装时，可在IPv6头的源地址中携带切片 标识(Slice ID)，封装后的原始报文包括目的地址(Destination Address，DA)、携带切片ID的源地址(Source Address，SA)、分段路由扩展头(Segment Routing Header，SRH)和原始报文。
从图1中可以看出，P1与P2之间传输的是携带切片标识的报文，P2与P3之间传输的也是携带切片标识的报文，P4节点会对接收到的封装后的报文进行解封装，从而恢复出原始报文，根据原始报文的目的地址转发该原始报文。
在相关技术中，需要为切片域内的每个节点配置一个网段，例如，切片前缀为32位，节点标识(node id)为16位，切片ID为32位。假设用于部署切片的网段为2001:2002:2003:2004::/64，则需要为切片网络内的头节点配置的切片网段为2001:2002:2003:2004:nodeid::/96。如图2所示，源地址包括网络段和主机段，相关技术中通过主机段携带切片标识。
例如，表1中示出了两个携带切片标识的源地址。
表1
切片标识 节点标识 源地址
1 2 2001:2002:2003:2004:0000:0002::1
5 8 2001:2002:2003:2004:0000:0008::5
其中，源地址2001:2002:2003:2004:0000:0002::1中，“2001:2002:2003:2004:0000:0002”属于网络段，“0000:0001”属于主机段，即主机段中包括切片标识1。
源地址2001:2002:2003:2004:0008::5中，“2001:2002:2003:2004:0000:0008”属于网络段，“0000:0005”属于主机段，即主机段中包括切片标识5。
本申请实施例中，为了使得第二SRv6 OAM报文被正确上送控制面，对携带切片标识的源地址进行了另一种分段处理，如图3所示，本申请实施例中在源地址中新增了一个切片段，即将源地址可以分为3段，分别为网络段、 主机段和切片段，通过切片段携带切片标识。其中，源地址一共128位，网络段可以为80位，主机段可以为16位，切片段可以为32位；或者，网络段为64位，主机段和切片段均为32位。网络段、主机段和切片段的长度可根据实际需求进行配置，本申请实施例对此不作限制。
作为一个例子，网络段为64位，切片段和主机段均为32位，仍以使用网段2001:2002:2003:2004::/64为例，源地址的最终呈现仍为上述表1中的源地址形式，但是分段方式发生了变化。
例如，源地址2001:2002:2003:2004:0000:0002::1中，“2001:2002:2003:2004:”属于网络段，“0000:0002:”属于主机段，“0000:0001”属于切片段。
源地址2001:2002:2003:2004:0000:0008::5中，“2001:2002:2003:2004:”属于网络段，“0000:0008:”属于主机段，“0000:0005”属于切片段。
需要说明的是，本申请实施例中的节点也可称为节点设备，节点设备可以为路由器、交换机等。
以下结合上述报文分段方式，对本申请实施例提供的报文处理方法进行详细描述。
本申请实施例提供一种报文处理方法，该方法应用于SRv6网络内的头节点，如图4所示，该方法包括：
S401、生成第一SRv6 OAM报文，该第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，切片段包括切片标识。
其中，第一SRv6 OAM报文用于检测SRv6路径的连通性并定位SRv6路径中的故障节点。
第一SRv6 OAM报文具体可以为ping报文、traceroute报文、双向转发检测(Bidirectional Forwarding Detection，BFD)等。ping报文用于在切片域内探测切片内的节点是否可达，traceroute报文用于探测切片内的节点是否可达，还可以用于分析哪个节点发生故障。
S402、向目的节点发送第一SRv6 OAM报文，以使得目的节点接收到第一SRv6 OAM报文后，若根据网络段和主机段确定第一SRv6 OAM报文中的源地址属于指定切片网段，则将源地址中的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址，并向头节点发送第二SRv6  OAM报文。
其中，目的节点为与头节点属于同一SRv6网络的其他节点，例如，若头节点为图1中的P1节点，则目的节点可以为图1中的P2节点、P3节点或P4节点。
如果头节点使用的网段为使用2001:2002:2003:2004::/64，则指定切片网段可以为“2001:2002:2003:2004:nodeid::”，该nodeid为头节点的节点标识。
假设头节点的节点标识为2，第一SRv6 OAM报文中的源地址为2001:2002:2003:2004:0000:0002::1，该源地址“2001:2002:2003:2004:”属于网络段，“0000:0002:”属于主机段，“0000:0001”属于切片段。
可见，该源地址属于指定切片网段2001:2002:2003:2004:0000:0002::，所以目的节点可以将该源地址包括的切片段清零，得到2001:2002:2003:2004:0000:0002::，进而将2001:2002:2003:2004:0000:0002::作为第二SRv6 OAM报文的目的地址，并将第一SRv6 OAM报文包括的目的地址作为第二SRv6 OAM报文的源地址。
本申请实施例中，若第一SRv6 OAM报文为ping报文，则第二SRv6 OAM报文为ping报文的应答报文。
若第一SRv6 OAM报文为traceroute报文，则第二SRv6 OAM报文为因特网控制报文协议(Internet Control Message Protocol，ICMP)超时报文。
若第一SRv6 OAM报文为BFD报文，则第二SRv6 OAM报文为BFD应答报文。
S403、接收第二SRv6 OAM报文。
其中，该第二SRv6 OAM报文包括目的地址，该目的地址为2001:2002:2003:2004:0000:0002::。
S404、若目的地址与头节点的主机地址相同，则向控制面上送第二SRv6 OAM报文。
基于节点转发面的工作原理，如果节点的转发面接收到的报文的目的地址是自身的主机地址，则会将接收到的报文上送控制面。在本申请实施例中，头节点的转发面接收到第二SRv6 OAM报文后，可获取第二SRv6 OAM报文的目的地址2001:2002:2003:2004:0000:0002::，因该目的地址中不携带切片ID， 与头节点的主机地址相同，所以可以向控制面上送该第二SRv6 OAM报文。
采用该方法，因头节点生成的第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所以目的节点接收到该第一SRv6 OAM报文后，如果根据源地址的网络段和主机段确定源地址属于指定切片网段，则可将源地址的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址。因头节点的主机地址通常是由网络段和主机段组成，所以将上述源地址中的切片段清零后，得到的就是头节点的主机地址，也就是说头节点接收到的第二SRv6 OAM报文的目的地址就是自身的主机地址，进而头节点的转发面可以将该第二SRv6 OAM报文正确上送控制面。
在本申请实施例中，可以预先为头节点配置回环(loopback)地址，并将该回环地址配置为切片的源地址。该回环地址包括网络段、主机段和切片位为0的切片段，回环地址包括的主机段包括头节点的节点标识。在本申请实施例中，头节点将该回环地址作为自身的主机地址。
例如，该回环地址为2001:2002:2003:2004:nodeid::/128。
在上述实施例的基础上，如图5所示，上述S401、头节点生成第一SRv6 OAM报文的过程包括：
S4011、获取头节点与目的节点所属切片的切片标识，该切片标识属于指定切片网段。
S4012、在回环地址的切片段填充切片标识，得到源地址，生成第一SRv6 OAM报文。
其中，上述回环地址的切片段中的切片位全为0，当需要在报文中携带切片标识时，可以直接将需要携带的切片标识填充在回环地址的切片段中，从而将得到的地址作为报文的源地址。
在生成第一SRv6 OAM报文时，则可直接将头节点与目的节点所属切片的切片标识，填充在回环地址的切片段，从而将得到的地址作为第一SRv6 OAM报文的源地址。
例如，若头节点的节点标识为5，则该回环地址为2001:2002:2003:2004:0000:0005::/128，若头节点与目的节点所属切片的切片标识为3，则可将切片标识3填充到回环地址的切片段，得到源地址2001:2002:2003:2004:0000:0005:: 3。
采用该方法，在生成第一SRv6 OAM报文时，只需将所需携带的切片标识填充到头节点的回环地址的切片段，即可生成源地址，实现简单。另外，因本申请实施例中将源地址的主机段与切片段独立设置，使得目的节点在接收到第一SRv6 OAM报文后，如果确定第一SRv6 OAM属于指定切片网段，则将切片段清零，如此，就可以恢复出头节点的主机地址，进而将该主机地址作为第二SRv6 OAM报文的目的地址，主节点无需额外的匹配操作，可以自然支持将第二SRv6 OAM报文上送控制面。
在相关技术中，切片标识被携带在主机段中，目的节点无法将主机段中的切片标识删除。为了使得第二SRv6 OAM报文能够上送控制面，主节点的控制面可以将所有带有切片标识的地址都作为主机地址下发给转发面，如此，如果转发面接收到的报文的目的地址携带切片标识，转发面也可以将该报文上送控制面。但是，切片网段很大，相应地携带切片标识的地址也很多，控制面逐条向转发面下发携带切片标识的地址会占用大量的资源。
而本申请实施例中，目的节点可以恢复出头节点的不携带切片标识的主机地址，目的节点向头节点返回的第二SRv6 OAM报文的目的地址不携带切片标识，所以本申请实施例中主节点的控制面只需将本机地址下发给转发面，即可实现第二SRv6 OAM报文上送控制面。无需逐条下发携带切片标识的地址，可以减少对资源的占用。
在本申请另一实施例中，在图4所示的流程之前，该方法还包括：
生成路由通告报文，该路由通告报文包括回环地址，向SRv6网络内除头节点之外的其他节点发送路由通告报文，以使得接收到路由通告报文的节点基于该回环地址生成转发表项。
例如，头节点向上述目的节点发送路由通告报文，目的节点接收到路由通告报文后，生成的转发表项的下一跳为路由通告报文中携带的回环地址。
例如，若该回环地址为：2001:2002:2003:2004:nodeid::/128，则目的节点生成的转发表项的前缀为2001:2002:2003:2004:nodeid:，出接口为目的节点上连接于头节点的接口，下一跳为从目的节点至头节点的路径中包括的设备中，与目的节点相连的设备的物理接口的地址。
在头节点与目的节点之间直接相连的情况下，目的节点生成的转发表项的下一跳为：头节点上连接于目的节点的接口的物理地址。
例如，若头节点为节点1，节点1的物理接口A与节点2相连，节点2的物理接口B与节点3相连，则节点2生成的转发表项中的下一跳为物理接口A的物理地址，节点3生成的转发表项中的下一跳为物理接口B的物理地址。
可以理解的是，接收到路由通告报文的节点也可按照相同方法生成转发表项。
本申请实施例中，头节点将回环地址作为普通的主机地址向外通告，相应地，其他节点可以根据该回环地址生成转发表项，从而可以根据生成的转发表项向头节点发送不携带切片标识的第二SRv6 OAM报文。并且相比于现有技术，本申请实施例中将头节点需要特殊维护的网段(为每个节点配置的网段)简化为头节点的主机地址，如此就无需特殊维护网段，在逻辑上更接近于头节点本身的处理，简化了头节点的处理。
与上述实施例相对应，本申请实施例还提供一种报文处理装置，该装置应用于SRv6网络内的目的节点，如图6所示，该方法包括：
S601、接收来自头节点的第一SRv6 OAM报文，第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，切片段包括切片标识。
其中，该主机段包括头节点的节点标识。
S602、根据网络段和主机段将第一SRv6 OAM报文的源地址与指定切片网段进行匹配。
例如，若第一SRv6 OAM报文中的源地址为2001:2002:2003:2004:0000:0002::1，该“2001:2002:2003:2004:”属于网络段，“0000:0002:”属于主机段，可见，该源地址属于指定切片网段2001:2002:2003:2004:0000:0002::。
S603、若根据网络段和主机段确定第一SRv6 OAM报文的源地址属于指定切片网段，则将源地址中的切片段清零，将切片段被清零后的源地址作为第二SRv6 OAM报文的目的地址。
其中，SRv6网络内的每个节点都被配置了指定切片网段和切片位长度信 息。目的节点接收到第一SRv6 OAM报文后，如果确定第一SRv6 OAM报文的源地址属于指定切片网段，则可确定该源地址中携带切片标识，进而可基于预先配置的切片位长度信息，将该源地址包括的切片段清零，以得到头节点的主机地址。
例如，若切片位长度信息为低16位，则目的节点可将该源地址的低16位清零。或者，若切片为长度信息为低32位，则目的节点可将该源地址的低32位清零。
S604、向头节点发送第二SRv6 OAM报文。
采用该方法，目的节点接收到的第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所以目的节点在确定第一SRv6 OAM与指定切片网段匹配的情况下，可以直接将源地址的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址。因头节点的主机地址通常是由网络段和主机段组成，所以将上述源地址中的切片段清零后，得到的就是头节点的主机地址，也就是说头节点接收到的第二SRv6 OAM报文的目的地址就是自身的主机地址，进而头节点的转发面可以将该第二SRv6 OAM报文正确上送控制面。
在本申请另一实施例中，在图6所示的实施例之前，该方法还包括：
接收头节点发送的路由通告报文，路由通告报包括头节点的回环地址，回环地址包括网络段、主机段和切片位为0的切片段，回环地址包括的主机段包括主节点的节点标识，根据回环地址生成转发表项。
例如，目的节点接收到路由通告报文后，生成的转发表项的下一跳为路由通告报文中携带的回环地址。
例如，若该回环地址为：2001:2002:2003:2004:nodeid::/128，则目的节点生成的转发表项的前缀为2001:2002:2003:2004:nodeid:，出接口为目的节点上连接于头节点的接口，下一跳为从目的节点至头节点的路径中包括的设备中，与目的节点相连的设备的物理接口的地址。
基于此，在上述S604中，目的节点可以基于上述转发表项向头节点发送第二SRv6 OAM报文。
采用该方法，使得SRv6网络中的各节点根据回环表项生成转发表项，从 而根据转发表项向头节点发送不携带切片标识的第二SRv6 OAM报文，使得头节点的转发面可以将该第二SRv6 OAM报文上送控制面，无需为头节点配置复杂的匹配机制，可以避免第二SRv6 OAM报文无法被上送控制面的情况发生。
对应于上述方法实施例，本申请实施例还提供一种报文处理装置，该装置应用于SRv6网络内的头节点，如图7所示，该装置包括：
生成模块701，用于生成第一SRv6 OAM报文，第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，切片段包括切片标识；
发送模块702，用于向目的节点发送第一SRv6 OAM报文，以使得目的节点接收到第一SRv6 OAM报文后，若根据网络段和主机段确定第一SRv6 OAM报文中的源地址属于指定切片网段，则将源地址中的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址，并向头节点发送第二SRv6 OAM报文；
接收模块703，用于接收第二SRv6 OAM报文，所述第二SRv6 OAM报文包括目的地址；
上送模块704，用于若该目的地址与头节点的主机地址相同，则向控制面上送第二SRv6 OAM报文。
在本申请另一实施例中，头节点的回环地址包括网络段、主机段和切片位为0的切片段，回环地址包括的主机段包括主节点的节点标识。
生成模块701，具体用于：
获取头节点与目的节点所属切片的切片标识，切片标识属于指定切片网段；
在回环地址的切片段填充切片标识得到源地址，生成第一SRv6 OAM报文。
在本申请另一实施例中，生成模块701，还用于生成路由通告报文，路由通告报文包括回环地址；
发送模块702，还用于向SRv6网络内除头节点之外的其他节点发送路由通告报文，以使得接收到路由通告报文的节点基于回环地址生成转发表项。
对应于上述方法实施例，本申请实施例还提供另一种报文处理装置，该装置应用于SRv6网络内的目的节点，如图8所示，该装置包括：
接收模块801，用于接收来自头节点的第一SRv6 OAM报文，第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，切片段包括切片标识；
匹配模块802，用于将根据网络段和主机段将第一SRv6 OAM报文的源地址与指定切片网段进行匹配；
封装模块803，用于若根据网络段和主机段确定第一SRv6 OAM报文的源地址属于指定切片网段，则将源地址中的切片段清零，将切片段被清零后的源地址作为第二SRv6 OAM报文的目的地址；
发送模块804，用于向头节点发送第二SRv6 OAM报文。
在本申请另一实施例中，封装模块803，具体用于基于预先配置的切片位长度信息，将源地址的切片段清零。
在本申请另一实施例中，该装置还包括生成模块；
接收模块801，还用于接收头节点发送的路由通告报文，路由通告报包括头节点的回环地址，回环地址包括网络段、主机段和切片位为0的切片段，回环地址包括的主机段包括主节点的节点标识；
生成模块，用于根据回环地址生成转发表项。
本申请实施例还提供了一种网络设备，该网络设备可以为上述实施例中的头节点，也可以为目的节点，如图9所示，包括处理器901、通信接口902、存储器903和通信总线904，其中，处理器901，通信接口902，存储器903通过通信总线904完成相互间的通信，
存储器903，用于存放计算机程序；
处理器901，用于执行存储器903上所存放的程序时，实现上述方法实施例中的方法步骤。
上述网络设备提到的通信总线可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。该通信总线可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信接口用于上述网络设备与其他设备之间的通信。
存储器可以包括随机存取存储器(Random Access Memory，RAM)，也可以包括非易失性存储器(Non-Volatile Memory，NVM)，例如至少一个磁盘存储器。可选的，存储器还可以是至少一个位于远离前述处理器的存储装置。
上述的处理器可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
在本申请提供的又一实施例中，还提供了一种计算机可读存储介质，该计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现上述任一报文处理方法的步骤。
在本申请提供的又一实施例中，还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述实施例中任一报文处理方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质 (例如固态硬盘Solid State Disk(SSD))等。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用相关的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本申请的较佳实施例，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内所作的任何修改、等同替换、改进等，均包含在本申请的保护范围内。

Claims (14)

  1. 一种报文处理方法，其特征在于，所述方法应用于SRv6网络内的头节点，所述方法包括：
    生成第一SRv6 OAM报文，所述第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
    向目的节点发送所述第一SRv6 OAM报文，以使得所述目的节点接收到所述第一SRv6 OAM报文后，若根据所述网络段和所述主机段确定所述第一SRv6 OAM报文中的源地址属于指定切片网段，则将所述源地址中的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址，并向所述头节点发送所述第二SRv6 OAM报文；
    接收所述第二SRv6 OAM报文，所述第二SRv6 OAM报文包括目的地址；
    若所述目的地址与所述头节点的主机地址相同，则向控制面上送所述第二SRv6 OAM报文。
  2. 根据权利要求1所述的方法，其特征在于，所述头节点的回环地址包括网络段、主机段和切片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；所述生成第一SRv6 OAM报文，包括：
    获取所述头节点与所述目的节点所属切片的切片标识，所述切片标识属于所述指定切片网段；
    在所述回环地址的切片段填充所述切片标识得到源地址，生成所述第一SRv6 OAM报文。
  3. 根据权利要求2所述的方法，其特征在于，在所述生成第一SRv6 OAM报文之前，所述方法还包括：
    生成路由通告报文，所述路由通告报文包括所述回环地址；
    向所述SRv6网络内除所述头节点之外的其他节点发送所述路由通告报文，以使得接收到所述路由通告报文的节点基于所述回环地址生成转发表项。
  4. 一种报文处理方法，其特征在于，所述方法应用于SRv6网络内的目的节点，所述方法包括：
    接收来自头节点的第一SRv6 OAM报文，所述第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
    根据所述网络段和所述主机段将所述第一SRv6 OAM报文的源地址与指定切片网段进行匹配；
    若根据所述网络段和所述主机段确定所述第一SRv6 OAM报文的源地址属于所述指定切片网段，则将所述源地址中的切片段清零，将切片段被清零后的所述源地址作为第二SRv6 OAM报文的目的地址；
    向所述头节点发送所述第二SRv6 OAM报文。
  5. 根据权利要求4所述的方法，其特征在于，所述将所述源地址中的切片段清零，包括：
    基于预先配置的切片位长度信息，将所述源地址的切片段清零。
  6. 根据权利要求4或5所述的方法，其特征在于，在所述接收来自头节点的第一SRv6 OAM报文之前，所述方法还包括：
    接收所述头节点发送的路由通告报文，所述路由通告报包括所述头节点的回环地址，所述回环地址包括网络段、主机段和切片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；
    根据所述回环地址生成转发表项。
  7. 一种报文处理装置，其特征在于，所述装置应用于SRv6网络内的头节点，所述装置包括：
    生成模块，用于生成第一SRv6 OAM报文，所述第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
    发送模块，用于向目的节点发送所述第一SRv6 OAM报文，以使得所述目的节点接收到所述第一SRv6 OAM报文后，若根据所述网络段和所述主机段确定所述第一SRv6 OAM报文中的源地址属于指定切片网段，则将所述源地址中的切片段清零，将切片段被清零的源地址作为第二SRv6 OAM报文的目的地址，并向所述头节点发送所述第二SRv6 OAM报文；
    接收模块，用于接收所述第二SRv6 OAM报文，所述第二SRv6 OAM报文包括目的地址；
    上送模块，用于若所述目的地址与所述头节点的主机地址相同，则向控制面上送所述第二SRv6 OAM报文。
  8. 根据权利要求7所述的装置，其特征在于，所述头节点的回环地址包 括网络段、主机段和切片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；所述生成模块，具体用于：
    获取所述头节点与所述目的节点所属切片的切片标识，所述切片标识属于所述指定切片网段；
    在所述回环地址的切片段填充所述切片标识得到源地址，生成所述第一SRv6 OAM报文。
  9. 根据权利要求8所述的装置，其特征在于，
    所述生成模块，还用于生成路由通告报文，所述路由通告报文包括所述回环地址；
    所述发送模块，还用于向所述SRv6网络内除所述头节点之外的其他节点发送所述路由通告报文，以使得接收到所述路由通告报文的节点基于所述回环地址生成转发表项。
  10. 一种报文处理装置，其特征在于，所述装置应用于SRv6网络内的目的节点，所述装置包括：
    接收模块，用于接收来自头节点的第一SRv6 OAM报文，所述第一SRv6 OAM报文的源地址包括网络段、主机段和切片段，所述切片段包括切片标识；
    匹配模块，用于根据所述网络段和所述主机段将所述第一SRv6 OAM报文的源地址与指定切片网段进行匹配；
    封装模块，用于若根据所述网络段和所述主机段确定所述第一SRv6 OAM报文的源地址属于所述指定切片网段，则将所述源地址中的切片段清零，将切片段被清零后的所述源地址作为第二SRv6 OAM报文的目的地址；
    发送模块，用于向所述头节点发送所述第二SRv6 OAM报文。
  11. 根据权利要求10所述的装置，其特征在于，
    所述封装模块，具体用于基于预先配置的切片位长度信息，将所述源地址的切片段清零。
  12. 根据权利要求10或11所述的装置，其特征在于，所述装置还包括生成模块；
    所述接收模块，还用于接收所述头节点发送的路由通告报文，所述路由通告报包括所述头节点的回环地址，所述回环地址包括网络段、主机段和切 片位为0的切片段，所述回环地址包括的主机段包括所述主节点的节点标识；
    所述生成模块，用于根据所述回环地址生成转发表项。
  13. 一种网络设备，其特征在于，包括处理器、通信接口、存储器和通信总线，其中，处理器，通信接口，存储器通过通信总线完成相互间的通信；
    存储器，用于存放计算机程序；
    处理器，用于执行存储器上所存放的程序时，实现权利要求1-3或4-6任一所述的方法步骤。
  14. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-3或4-6任一所述的方法步骤。
PCT/CN2021/122183 2021-09-30 2021-09-30 一种报文处理方法、装置、网络设备及介质 Ceased WO2023050313A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2023572012A JP7685076B2 (ja) 2021-09-30 2021-09-30 メッセージ処理方法、装置、ネットワークデバイス及び媒体
US18/563,785 US20240283733A1 (en) 2021-09-30 2021-09-30 Packet processing method and apparatus, and network device and medium
CN202180002802.4A CN117280671A (zh) 2021-09-30 2021-09-30 一种报文处理方法、装置、网络设备及介质
EP21958885.2A EP4412181A4 (en) 2021-09-30 2021-09-30 MESSAGE PROCESSING METHOD AND APPARATUS, AND NETWORK DEVICE AND MEDIUM
KR1020237038000A KR102912343B1 (ko) 2021-09-30 2021-09-30 메시지 처리 방법, 디바이스, 네트워크 기기 및 매체
PCT/CN2021/122183 WO2023050313A1 (zh) 2021-09-30 2021-09-30 一种报文处理方法、装置、网络设备及介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/122183 WO2023050313A1 (zh) 2021-09-30 2021-09-30 一种报文处理方法、装置、网络设备及介质

Publications (1)

Publication Number Publication Date
WO2023050313A1 true WO2023050313A1 (zh) 2023-04-06

Family

ID=85781142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/122183 Ceased WO2023050313A1 (zh) 2021-09-30 2021-09-30 一种报文处理方法、装置、网络设备及介质

Country Status (6)

Country Link
US (1) US20240283733A1 (zh)
EP (1) EP4412181A4 (zh)
JP (1) JP7685076B2 (zh)
KR (1) KR102912343B1 (zh)
CN (1) CN117280671A (zh)
WO (1) WO2023050313A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116633873A (zh) * 2023-05-24 2023-08-22 阿里云计算有限公司 硬件卸载虚拟交换机装置和相关设备及报文转发方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117097633A (zh) * 2022-05-12 2023-11-21 华为技术有限公司 报文传输方法、传输控制方法、装置及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110266594A (zh) * 2019-06-28 2019-09-20 Ut斯达康通讯有限公司 跨网络切片的分段路由转发方法及装置
WO2021008515A1 (zh) * 2019-07-18 2021-01-21 华为技术有限公司 网络切片架构下的数据传输的方法和装置
US20210075697A1 (en) * 2018-05-28 2021-03-11 Greenwave Systems Pte. Ltd. Self-balancing network
CN112770196A (zh) * 2019-10-21 2021-05-07 中兴通讯股份有限公司 一种虚拟化方法及装置
CN112817688A (zh) * 2019-11-15 2021-05-18 大唐移动通信设备有限公司 一种网络切片模板生成方法及装置
CN112910773A (zh) * 2019-11-19 2021-06-04 华为技术有限公司 下发oam配置信息的方法及控制节点

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101442442B (zh) * 2008-12-17 2011-01-19 华为技术有限公司 管理装置、控制装置、管理控制装置及路由器系统
CN107231384B (zh) * 2017-08-10 2020-11-17 北京科技大学 一种面向5g网络切片的DDoS攻击检测防御方法及系统
US10469367B2 (en) * 2017-10-04 2019-11-05 Cisco Technology, Inc. Segment routing network processing of packets including operations signaling and processing of packets in manners providing processing and/or memory efficiencies
CN110535766B (zh) * 2018-05-25 2021-10-22 华为技术有限公司 一种生成路由的方法和设备
US10904152B2 (en) * 2018-12-17 2021-01-26 Cisco Technology, Inc. Hardware-friendly mechanisms for in-band OAM processing
CN110324681B (zh) * 2019-07-08 2021-05-25 广州酷狗计算机科技有限公司 多媒体数据的切片方法、装置、存储介质及传输系统
CN113300949B (zh) * 2020-02-24 2022-12-06 华为技术有限公司 转发报文的方法、发布路由信息的方法、装置及系统
CN113315697B (zh) * 2020-02-26 2022-11-11 华为技术有限公司 报文处理方法、装置、网络设备及存储介质
CN116684920A (zh) 2020-03-17 2023-09-01 华为技术有限公司 报文处理方法、装置、设备及存储介质
CN111865785B (zh) * 2020-06-28 2022-04-29 烽火通信科技股份有限公司 Sr-tp隧道信号传递方法、装置、服务器及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210075697A1 (en) * 2018-05-28 2021-03-11 Greenwave Systems Pte. Ltd. Self-balancing network
CN110266594A (zh) * 2019-06-28 2019-09-20 Ut斯达康通讯有限公司 跨网络切片的分段路由转发方法及装置
WO2021008515A1 (zh) * 2019-07-18 2021-01-21 华为技术有限公司 网络切片架构下的数据传输的方法和装置
CN112770196A (zh) * 2019-10-21 2021-05-07 中兴通讯股份有限公司 一种虚拟化方法及装置
CN112817688A (zh) * 2019-11-15 2021-05-18 大唐移动通信设备有限公司 一种网络切片模板生成方法及装置
CN112910773A (zh) * 2019-11-19 2021-06-04 华为技术有限公司 下发oam配置信息的方法及控制节点

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4412181A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116633873A (zh) * 2023-05-24 2023-08-22 阿里云计算有限公司 硬件卸载虚拟交换机装置和相关设备及报文转发方法

Also Published As

Publication number Publication date
JP7685076B2 (ja) 2025-05-28
KR102912343B1 (ko) 2026-01-14
EP4412181A4 (en) 2024-10-30
US20240283733A1 (en) 2024-08-22
CN117280671A (zh) 2023-12-22
JP2024524833A (ja) 2024-07-09
KR20240022456A (ko) 2024-02-20
EP4412181A1 (en) 2024-08-07

Similar Documents

Publication Publication Date Title
CN102823205B (zh) 聚合来自接入域的数据业务
CN108574639B (zh) Evpn报文处理方法、设备及系统
CN108574630B (zh) Evpn报文处理方法、设备及系统
US20210014158A1 (en) Network Device Management Method and Apparatus, and System
CN108964940B (zh) 消息发送方法及装置、存储介质
US9641420B1 (en) Methods and apparatus for assessing the quality of a data path including both layer-2 and layer-3 devices
CN109218456B (zh) Mac地址表的老化时间的处理方法及装置
CN111614505B (zh) 报文处理的方法和网关设备
WO2023116457A1 (zh) 报文处理方法及装置、通信系统
WO2022121638A1 (zh) 一种报文处理方法及装置
CN108512755A (zh) 一种路由信息的学习方法及装置
WO2023050313A1 (zh) 一种报文处理方法、装置、网络设备及介质
US10531168B2 (en) Low-latency data switching device and method
CN109951371B (zh) 数据转发方法及装置
CN115242699A (zh) 报文传输方法、切片生成方法、装置及系统
CN111600798A (zh) 一种发送和获取断言报文的方法和网络节点
JP2019117972A (ja) ネットワーク管理装置、ネットワークシステム、方法、及びプログラム
CN103873339A (zh) 一种虚拟网关路由器的分配方法和装置
CN101102231B (zh) 一种ppp链路路由设备的自动发现方法和装置
CN111404816B (zh) 一种跨网络发送组播报文的方法、装置、系统及存储介质
WO2015024523A1 (zh) 确定ip承载网故障的方法和系统
CN114765589A (zh) 网络测试方法、装置及存储介质
US12526211B2 (en) Message processing method for in-situ flow detection, and network device
CN104660446B (zh) N:1保护场景下dhcp中继实现系统及方法
CN102904776B (zh) 一种虚拟局域网中的探测方法、装置和设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21958885

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023572012

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202327079095

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 11202308851P

Country of ref document: SG

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021958885

Country of ref document: EP

Effective date: 20240430