US12395572B2 - Packet processing method - Google Patents

Packet processing method

Info

Publication number
US12395572B2
US12395572B2 US17/533,216 US202117533216A US12395572B2 US 12395572 B2 US12395572 B2 US 12395572B2 US 202117533216 A US202117533216 A US 202117533216A US 12395572 B2 US12395572 B2 US 12395572B2
Authority
US
United States
Prior art keywords
packet
identifier
packet header
header
sff
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, expires
Application number
US17/533,216
Other languages
English (en)
Other versions
US20220109745A1 (en
Inventor
Yongkang Zhang
Zhongzhen Wang
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of US20220109745A1 publication Critical patent/US20220109745A1/en
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WANG, Zhongzhen, Zhang, Yongkang
Application granted granted Critical
Publication of US12395572B2 publication Critical patent/US12395572B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • 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
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • the target packet header is a segment routing (SR) packet header.
  • SR segment routing
  • a form of the first packet header is merely used as an example for description, to improve applicability of the solution.
  • the first packet also includes a second identifier.
  • the method further includes: the SF obtains the first identifier according to indication of the second identifier, and adds the first identifier to the third packet.
  • the second packet may further carry the second identifier, so that the SF can determine, based on the second identifier, whether the second packet includes the first identifier. This avoids an unnecessary read operation of the SF when the second packet does not carry the first identifier, and reduces operation pressure of the SF.
  • the method further includes: the SF adds a third identifier to the third packet.
  • the third identifier is used to indicate that the third packet includes the first identifier.
  • the SF may further add the third identifier to the third packet, so that the SFF may determine, based on the third identifier, whether the third packet includes the first identifier. This avoids an unnecessary read operation that may exist, and reduces operation pressure of the SFF.
  • a third aspect of an embodiment provides a service function forwarder (SFF).
  • the service function forwarder (SFF) may include:
  • the transceiver unit is further configured to: send the second packet to a service function (SF) device; and receive a third packet from the SF.
  • the third packet is obtained after the SF processes the second packet based on the second packet header.
  • the third packet includes the first identifier.
  • the processing unit is further configured to: determine, based on a mapping relationship between the first identifier and the first packet header, the first packet header corresponding to the first identifier; and replace a third packet header of the third packet with the first packet header to obtain a fourth packet.
  • the transceiver unit is further configured to send the fourth packet to a next-hop node.
  • the first packet header is a segment routing (SR) packet header.
  • SR segment routing
  • the first packet header is a packet header that cannot be parsed by the SF.
  • the processing unit is further configured to: if the first packet header exists locally, determine the first identifier based on the preset mapping relationship between the first packet header and the first identifier; or if the first packet header does not exist locally, allocate the first identifier to the first packet header, and store the mapping relationship between the first identifier and the first packet header.
  • the second packet further includes a second identifier.
  • the second identifier is used to indicate that the second packet includes the first identifier and instruct to add the first identifier to the third packet.
  • the target packet header is a segment routing (SR) packet header.
  • SR segment routing
  • a sixth aspect of an embodiment provides a service function (SF) device.
  • the service function (SF) device may include:
  • the transceiver is configured to receive a first packet from a service function forwarder (SFF) and store the first packet in the memory.
  • the first packet includes a first identifier.
  • the first packet also includes a second identifier.
  • the processor is further configured to read the second identifier, obtain the first identifier according to indication of the second identifier, and add the first identifier to the third packet.
  • a seventh aspect of an embodiment provides a message processing system.
  • the system may include:
  • the service function device includes the service function forwarder according to any one of the fourth aspect, the sixth aspect, or a specific embodiment of the fourth aspect and the sixth aspect.
  • An eighth aspect of an embodiment provides a computer storage medium including instructions. When the instructions are run on a computer, the computer is enabled to perform the method according to any one of the first aspect, the second aspect, or a specific embodiment of the first aspect and the second aspect.
  • a ninth aspect of an embodiment provides a computer program product including instructions.
  • the computer program product runs on a computer, the computer is enabled to perform the method according to any one of the first aspect, the second aspect, or a specific embodiment of the first aspect and the second aspect.
  • the SFF After the SFF obtains the first packet, if the SF connected to the SFF cannot parse the first packet or in another case, the SFF replaces the first packet header of the first packet with the second packet header that can be parsed by the SF, to obtain the second packet. Then, the SFF sends the second packet to the SF.
  • the second packet includes the first identifier corresponding to the first packet header.
  • the third packet further includes the first identifier. Therefore, the SFF can parse the third packet to obtain the first identifier.
  • FIG. 4 is a schematic diagram of an embodiment of a packet processing method according to an embodiment
  • the embodiments are applicable to the computer field, and may be applicable to a plurality of types of packet forwarding and processing processes.
  • the embodiments are not limited to packet forwarding and processing when an SR technology is used to forward a packet.
  • Segment routing is a tunneling technology based on a source route forwarding mode.
  • a head node is used to specify a path for a packet, so that the packet is forwarded and processed on a routing node according to the specified path.
  • the packet forwarded by using an SR technology includes an SR packet header and a payload part.
  • the SR packet header includes indication information about a forwarding path.
  • the payload part is used to carry service data.
  • an SR technology may be used to forward a packet between nodes on the service chain.
  • the SR technology is a tunneling technology based on a source route forwarding mode.
  • a head node of a traffic flow is used to specify a path for the packet.
  • the SR technology may be divided into two data planes: multi-protocol label switching (MPLS) and internet protocol version 6 (IPv6), which are respectively referred to as SR-MPLS and an SRv6.
  • MPLS multi-protocol label switching
  • IPv6 internet protocol version 6
  • the nodes on the service chain may forward the SR packet according to the path indicated by the SID list in the SR packet header and process the SR packet.
  • SID is the same as a conventional MPLS label or a conventional IPv6 address in a form, the SID is essentially an instruction.
  • the SID may be further used to instruct to perform a predefined association operation on the packet on the specified device.
  • FIG. 2 is a schematic diagram of a general architecture of an SR proxy defined in the conventional technology.
  • SR segment routing
  • SF service function
  • the SFF converts the SR packet into a non-segment routing (non-SR) packet that can be parsed by the SF, and sends the non-segment routing (non-SR) packet to the SF. Then, the SFF restores a non-SR packet that is returned and that is processed by the SF to an SR packet and forwards the packet on a service chain.
  • non-SR non-segment routing
  • SR proxy technologies may be further classified into a plurality of types of proxies, such as a static proxy, a dynamic proxy, a shared-memory proxy, and a masquerading proxy.
  • a static proxy such as a static proxy, a dynamic proxy, a shared-memory proxy, and a masquerading proxy.
  • SR proxy technology is an SR dynamic proxy technology.
  • An SFF stores an SR packet header of a first SR packet received from a previous node and replaces the SR packet header of the first SR packet with a non-SR packet header that can be parsed by an SF, to obtain a first non-SR packet. Then, the SFF sends the first non-SR packet to the SF. After the SF processes the first non-SR packet, the SFF receives, from the SF, a processed second non-SR packet.
  • the SFF After receiving the second non-SR packet that is returned and processed by the SF, the SFF finds a locally pre-stored SR packet header based on 5-tuple and based on virtual private network identification (VPN ID), replaces a non-SR packet header of the second non-SR packet with the found SR packet header to obtain a second SR packet, and forwards the second SR packet to a next hop.
  • VPN ID virtual private network identification
  • the SR dynamic proxy technology is used, so that a device that does not support the SR technology is more compatible.
  • the SR packet is forwarded along a path specified by a head node. If a segment of the path fails in a forwarding process, the SR packet may fail to be forwarded.
  • a path optimization technology is defined in the SR technology to allow the SR packet to change the forwarding path and bypass the faulty path during forwarding, so as to implement normal forwarding.
  • SR path optimization may include proactive optimization and passive optimization. In the passive optimization, if a link/node/shared risk link group (SRLG) fails during forwarding of the SR packet, a head node of the faulty segment calculates a repair tunnel corresponding to a post-convergence path.
  • SRLG link/node/shared risk link group
  • a controller can adjust a forwarding path of a traffic flow at any time according to a user instruction or a specified policy triggered in a link running status.
  • the node R 2 enables a path optimization function and calculates a repair tunnel R 4 -R 5 , splices an SID list ( 2004 - 2005 ) corresponding to the repair tunnel to the SID list recorded in the source SR packet header, to obtain a new SR packet header. Therefore, the R 2 may send the received packet to the node R 6 through the repair tunnel indicated in a new SR packet header.
  • a repair tunnel R 4 -R 5 calculates a repair tunnel R 4 -R 5 , splices an SID list ( 2004 - 2005 ) corresponding to the repair tunnel to the SID list recorded in the source SR packet header, to obtain a new SR packet header. Therefore, the R 2 may send the received packet to the node R 6 through the repair tunnel indicated in a new SR packet header.
  • a path between R 2 -R 6 is in a normal state when the node R 6 receives a first SR packet, and the path is in an abnormal state (faulty or adjusted) when the node R 6 receives a second SR packet of a same traffic flow, it can be understood according to the foregoing description that: a packet header of the first SR packet received by the SFF is different from a packet header of the second SR packet.
  • the SFF when the SFF performs a dynamic proxy on the first SR packet, if the SFF receives the second SR packet before receiving a non-SR packet that corresponds to the first SR packet and that is returned by the SF, the SFF replaces the originally stored first SR packet header of the first SR packet with the second SR packet header of the second SR packet. In this way, after the SFF receives the non-SR packet that corresponds to the first SR packet and that is returned by the SF, the found SR packet header is not the pre-stored first SR packet header. As a result, in a subsequent process of encapsulating an SR packet by using the non-SR packet and the found SR packet header, an encapsulation error may occur, and forwarding of a subsequent packet is affected.
  • the SR packet is used as an example for description.
  • the pre-stored SR packet header is incorrectly replaced.
  • the packet encapsulation error may be caused.
  • a packet header of a first packet is incorrectly replaced during buffering. Consequently, a subsequent encapsulation error is caused, and normal packet forwarding is affected.
  • the embodiments provide a packet processing method, to improve a success rate of packet forwarding, and reduce a probability of a case in which the packet forwarding is affected due to an encapsulation error in a packet forwarding process.
  • the SFF parses the packet 1 to obtain the corresponding packet header 1.
  • the packet header 1 is an SR packet header is used for description.
  • the network device determines whether the packet header 1 meets the preset rule. For example, whether the packet header 1 is a packet header that can be parsed by an SF may be determined. For example, it may be determined by judging whether a specific field of the packet header 1 is a preset specific field.
  • the SFF strips the packet header 1 of the packet 1 and encapsulates service data of the packet 1 and the packet header 2 to obtain the packet 2.
  • the packet 2 includes the first identifier.
  • the first identifier may be written into a reserved field of the packet header 2 based on different types of the packet header 2.
  • the SF processes the packet 2 to obtain a packet 3, where the packet 3 includes the first identifier.
  • the packet 3 also includes a third identifier.
  • the SF adds the third identifier to the packet 3.
  • the third identifier is used to indicate the SFF to read the first identifier according to indication of the third identifier.
  • the third identifier may be a preset value, and is used to indicate the SFF to read, when the third identifier is the preset value, the first identifier carried in the packet 3.
  • a manner of carrying the third identifier is similar to the manner of carrying the first identifier in the packet 2 in the step S 405 . Details are not described herein again.
  • the SF after generating the packet 3, the SF sends the packet 3 to the SFF.
  • the SFF determines, based on a mapping relationship between the first identifier and the packet header 1, the packet header 1 corresponding to the first identifier.
  • the packet 3 also includes the third identifier, and the third identifier is the preset value. Therefore, when determining that the third identifier is the preset value, the SFF reads the first identifier carried in the packet 3.
  • S 410 The SFF replaces a packet header 3 of the packet 3 with the packet header 1 to obtain a packet 4.
  • the SFF encapsulates the processed service data carried in the packet 3 and the packet header 1 obtained through query to obtain the packet 4.
  • the SFF determines the next hop based on a destination address in the packet header 1 and sends the packet 4 to the next hop.
  • the SFF After receiving the packet 1 sent by the previous hop, the SFF replaces the packet header 1 of the packet 1 with the packet header 2 that can be identified by the SF, to obtain the packet 2.
  • the packet 2 includes the first identifier corresponding to the packet header 1.
  • the SFF sends the packet 2 to the SF.
  • the packet 2 may be parsed and processed by the SF.
  • the SFF receives the packet 3 obtained after the SF processes the packet header 2, the packet 3 further includes the first identifier. Therefore, the SFF may obtain the prestored packet header 1 through query based on the first identifier to generate the packet 4, and then forward the packet 4 to the next hop.
  • the foregoing manner implements processing performed by the SF on the packet 1 and avoids a case in the conventional technology in which a packet 4 encapsulation error is caused by an error in querying the packet header 1.
  • FIG. 5 is a schematic diagram of another embodiment of a packet processing method.
  • the method may include the following steps.
  • S 506 The SFF sends the second packet to an SF.
  • the SF receives the first packet from the SFF, and locally stores the first packet.
  • the first packet includes the first identifier.
  • the first packet header is a packet header that cannot be parsed by the SF.
  • the first packet also includes a second identifier.
  • the processing unit S 801 is further configured to add a third identifier to the third packet.
  • the third identifier is used to indicate that the first packet includes the first identifier.
  • the processor S 901 is further configured to: if the first packet header exists locally, determine the first identifier based on the preset mapping relationship between the first packet header and the first identifier; or if the first packet header does not exist locally, allocate the first identifier to the first packet header, and store the mapping relationship between the first identifier and the first packet header.
  • the second packet further includes a second identifier.
  • the second identifier is used to indicate that the second packet includes the first identifier and instruct to add the first identifier to the third packet.
  • the first packet header is a packet header that cannot be parsed by the SF.
  • FIG. 10 is a schematic diagram of an embodiment of a service function device 1000 according to an embodiment.
  • the service function device 1000 may include:
  • the processor S 1001 is configured to: read the first packet from the memory S 1002 and process the first packet to obtain a second packet.
  • the transceiver S 1003 is further configured to: obtain the second packet from the memory S 1002 and send the second packet to the SFF.
  • the second packet includes the first identifier.
  • the first identifier is used to instruct that the SFF obtains a prestored target packet header through query based on the first identifier.
  • the target packet header is a segment routing (SR) packet header.
  • SR segment routing
  • the processor S 1001 is further configured to add a third identifier to the third packet.
  • the third identifier is used to indicate that the third packet includes the first identifier.
  • An embodiment further provides a packet processing system.
  • the system may include:
  • the service function device includes the service function device described in any step in the embodiment shown in FIG. 4 or FIG. 6 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US17/533,216 2019-05-24 2021-11-23 Packet processing method Active 2042-02-04 US12395572B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201910441426.3A CN111988266B (zh) 2019-05-24 2019-05-24 一种处理报文的方法
CN201910441426.3 2019-05-24
PCT/CN2020/091935 WO2020238809A1 (fr) 2019-05-24 2020-05-22 Procédé de traitement de message

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/091935 Continuation WO2020238809A1 (fr) 2019-05-24 2020-05-22 Procédé de traitement de message

Publications (2)

Publication Number Publication Date
US20220109745A1 US20220109745A1 (en) 2022-04-07
US12395572B2 true US12395572B2 (en) 2025-08-19

Family

ID=73437123

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/533,216 Active 2042-02-04 US12395572B2 (en) 2019-05-24 2021-11-23 Packet processing method

Country Status (4)

Country Link
US (1) US12395572B2 (fr)
EP (1) EP3955541B1 (fr)
CN (1) CN111988266B (fr)
WO (1) WO2020238809A1 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11520615B1 (en) * 2020-03-31 2022-12-06 Equinix, Inc. Virtual network function virtual domain isolation
CN112751826B (zh) * 2020-12-07 2024-04-30 中兴通讯股份有限公司 算力应用流量转发方法及装置
CN113014485B (zh) * 2021-02-25 2022-04-26 烽火通信科技股份有限公司 一种基于SRv6-TE路径的报文转发方法和报文转发装置
CN115426305B (zh) * 2021-05-31 2024-06-11 华为技术有限公司 报文处理方法、装置、系统及存储介质
US11706121B2 (en) 2021-09-20 2023-07-18 Juniper Networks, Inc. Segment identifiers that support end-to-end segment routing with color extended community and border gateway protocol virtual private network option b
EP4507269A4 (fr) * 2022-04-29 2025-06-18 Huawei Technologies Co., Ltd. Procédé, appareil et système de traitement de message
US12095642B2 (en) * 2022-07-25 2024-09-17 Hewlett Packard Enterprise Development Lp Remote reachability checks in a distributed tunnel fabric
US11831548B1 (en) * 2022-11-29 2023-11-28 Ciena Corporation Distinguishing SRv6 micro-SID destination address from IPv6 destination address

Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150043328A1 (en) * 1999-07-15 2015-02-12 Juniper Networks, Inc. Method and apparatus for fast reroute in a connection-oriented network
US20150092551A1 (en) * 2013-09-30 2015-04-02 Juniper Networks, Inc. Session-aware service chaining within computer networks
CN104579973A (zh) 2014-12-24 2015-04-29 北京华为数字技术有限公司 一种虚拟集群中的报文转发方法和装置
CN105743822A (zh) 2014-12-11 2016-07-06 华为技术有限公司 一种处理报文的方法及装置
WO2016165492A1 (fr) 2015-07-02 2016-10-20 中兴通讯股份有限公司 Procédé et appareil permettant la mise en œuvre de chaîne de fonction de service
US20170005920A1 (en) * 2015-07-01 2017-01-05 Cisco Technology, Inc. Forwarding packets with encapsulated service chain headers
US20170085477A1 (en) * 2014-05-30 2017-03-23 Huawei Technologies Co., Ltd. Packet Edit Processing Method and Related Device
US20170134538A1 (en) * 2015-11-10 2017-05-11 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods of an enhanced state-aware proxy device
US20170180824A1 (en) * 2015-12-21 2017-06-22 Centurylink Intellectual Property Llc Video File Universal Identifier for Metadata Resolution
US20170237656A1 (en) * 2016-02-12 2017-08-17 Huawei Technologies Co., Ltd. Method and apparatus for service function forwarding in a service domain
US20170244631A1 (en) * 2016-02-22 2017-08-24 Cisco Technology, Inc. Sr app-segment integration with service function chaining (sfc) header metadata
WO2018006675A1 (fr) * 2016-07-05 2018-01-11 中兴通讯股份有限公司 Procédé et appareil de traitement de données
CN107911258A (zh) 2017-12-29 2018-04-13 深信服科技股份有限公司 一种基于sdn网络的安全资源池的实现方法及系统
EP3322135A1 (fr) 2015-07-06 2018-05-16 ZTE Corporation Procédé et dispositif de transmission de paquets
US20180152374A1 (en) * 2016-11-30 2018-05-31 Futurewei Technologies, Inc. Service Function Chaining and Overlay Transport Loop Prevention
CN108173694A (zh) 2017-12-29 2018-06-15 深信服科技股份有限公司 一种数据中心的安全资源池接入方法及系统
CN108199958A (zh) 2017-12-29 2018-06-22 深信服科技股份有限公司 一种通用的安全资源池服务链实现方法及系统
EP3355519A1 (fr) 2017-01-30 2018-08-01 Thomson Licensing Procédé de gestion de chaînage de services à un équipement de réseau, équipement de réseau correspondant
US20180375968A1 (en) * 2017-06-27 2018-12-27 Cisco Technology, Inc., A California Corporation Providing Efficiencies in Processing and Communicating Internet Protocol Packets in a Network Using Segment Routing
CN109728962A (zh) 2017-10-27 2019-05-07 华为技术有限公司 一种发送报文的方法和设备
CN109756521A (zh) 2019-03-21 2019-05-14 山东浪潮云信息技术有限公司 一种nsh报文处理方法、装置及系统
US20190394211A1 (en) * 2018-06-26 2019-12-26 Cisco Technology, Inc. Providing Processing and Network Efficiencies in Protecting Internet Protocol Version 6 Segment Routing Packets and Functions Using Security Segment Identifiers
US20200145331A1 (en) * 2018-11-02 2020-05-07 Cisco Technology, Inc., A California Corporation Using In-Band Operations Data to Signal Packet Processing Departures in a Network
WO2020182085A1 (fr) 2019-03-08 2020-09-17 华为技术有限公司 Procédé et dispositif de transmission pour un message
WO2020220987A1 (fr) * 2019-04-30 2020-11-05 中兴通讯股份有限公司 Procédé et appareil de transmission de paquets de données, procédé et appareil de gestion de transmission de paquets de données, dispositif de transfert de paquets de données, et support d'informations

Patent Citations (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150043328A1 (en) * 1999-07-15 2015-02-12 Juniper Networks, Inc. Method and apparatus for fast reroute in a connection-oriented network
US20150092551A1 (en) * 2013-09-30 2015-04-02 Juniper Networks, Inc. Session-aware service chaining within computer networks
US20170085477A1 (en) * 2014-05-30 2017-03-23 Huawei Technologies Co., Ltd. Packet Edit Processing Method and Related Device
CN105743822A (zh) 2014-12-11 2016-07-06 华为技术有限公司 一种处理报文的方法及装置
CN104579973A (zh) 2014-12-24 2015-04-29 北京华为数字技术有限公司 一种虚拟集群中的报文转发方法和装置
US20170005920A1 (en) * 2015-07-01 2017-01-05 Cisco Technology, Inc. Forwarding packets with encapsulated service chain headers
WO2016165492A1 (fr) 2015-07-02 2016-10-20 中兴通讯股份有限公司 Procédé et appareil permettant la mise en œuvre de chaîne de fonction de service
CN106330714A (zh) 2015-07-02 2017-01-11 中兴通讯股份有限公司 一种实现业务功能链的方法和装置
US20180198705A1 (en) * 2015-07-02 2018-07-12 Zte Corporation Method and apparatus for implementing service function chain
EP3322135A1 (fr) 2015-07-06 2018-05-16 ZTE Corporation Procédé et dispositif de transmission de paquets
US10461958B2 (en) * 2015-07-06 2019-10-29 Zte Corporation Packet transmission method and apparatus
US20170134538A1 (en) * 2015-11-10 2017-05-11 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods of an enhanced state-aware proxy device
US20170180824A1 (en) * 2015-12-21 2017-06-22 Centurylink Intellectual Property Llc Video File Universal Identifier for Metadata Resolution
US20170237656A1 (en) * 2016-02-12 2017-08-17 Huawei Technologies Co., Ltd. Method and apparatus for service function forwarding in a service domain
US20170244631A1 (en) * 2016-02-22 2017-08-24 Cisco Technology, Inc. Sr app-segment integration with service function chaining (sfc) header metadata
CN108702331A (zh) 2016-02-22 2018-10-23 思科技术公司 Sr应用段与服务功能链(sfc)报头元数据的集成
WO2018006675A1 (fr) * 2016-07-05 2018-01-11 中兴通讯股份有限公司 Procédé et appareil de traitement de données
US20180152374A1 (en) * 2016-11-30 2018-05-31 Futurewei Technologies, Inc. Service Function Chaining and Overlay Transport Loop Prevention
EP3355519A1 (fr) 2017-01-30 2018-08-01 Thomson Licensing Procédé de gestion de chaînage de services à un équipement de réseau, équipement de réseau correspondant
US20180375968A1 (en) * 2017-06-27 2018-12-27 Cisco Technology, Inc., A California Corporation Providing Efficiencies in Processing and Communicating Internet Protocol Packets in a Network Using Segment Routing
CN109728962A (zh) 2017-10-27 2019-05-07 华为技术有限公司 一种发送报文的方法和设备
CN108199958A (zh) 2017-12-29 2018-06-22 深信服科技股份有限公司 一种通用的安全资源池服务链实现方法及系统
CN107911258A (zh) 2017-12-29 2018-04-13 深信服科技股份有限公司 一种基于sdn网络的安全资源池的实现方法及系统
CN108173694A (zh) 2017-12-29 2018-06-15 深信服科技股份有限公司 一种数据中心的安全资源池接入方法及系统
US20190394211A1 (en) * 2018-06-26 2019-12-26 Cisco Technology, Inc. Providing Processing and Network Efficiencies in Protecting Internet Protocol Version 6 Segment Routing Packets and Functions Using Security Segment Identifiers
US20200145331A1 (en) * 2018-11-02 2020-05-07 Cisco Technology, Inc., A California Corporation Using In-Band Operations Data to Signal Packet Processing Departures in a Network
WO2020182085A1 (fr) 2019-03-08 2020-09-17 华为技术有限公司 Procédé et dispositif de transmission pour un message
CN109756521A (zh) 2019-03-21 2019-05-14 山东浪潮云信息技术有限公司 一种nsh报文处理方法、装置及系统
WO2020220987A1 (fr) * 2019-04-30 2020-11-05 中兴通讯股份有限公司 Procédé et appareil de transmission de paquets de données, procédé et appareil de gestion de transmission de paquets de données, dispositif de transfert de paquets de données, et support d'informations

Non-Patent Citations (16)

* Cited by examiner, † Cited by third party
Title
Bashandy et al., "Topology Independent Fast Reroute using Segment Routing; draft-bashandy-rtgwg-segment-routing-ti-lfa-05", Network Working Group, Oct. 4, 2018; 19 Pages.
Clad et al., "Service Programming with Segment Routing; draft-xuclad-spring-sr-service-programming-00", Spring, Jul. 2, 2018; 30 Pages.
Clad et al., "Service Programming with Segment Routing; draft-xuclad-spring-sr-service-programming-01", Spring, Oct. 22, 2018; 31 Pages.
Conta et al., "Generic Packet Tunneling in IPV6 Specification", Network Working Group , RFC 2473, Dec. 1998; 36 Pages.
Deering et al., "Internet Protocol, Version 6 (IPv6) Specification", Internet Engineering Task Force (IETF) , RFC 8200 , Jul. 2017; 42 Pages.
Farinacci et al, "Generic Routing Encapsulation (GRE)", Network Working Group, RFC 2784 , Mar. 2000, 9 Pages.
Filsfils et al., "IPv6 Segment Routing Header (SRH); draft-ietf-6man-segment-routing-header-14", Network Working Group, Jun. 28, 2018; 29 Pages.
Filsfils et al., "Segment Routing Architecture", Internet Engineering Task Force (IETF) , RFC 8402 , Jul. 2018; 32 Pages.
Filsfils et al., "Segment Routing Policy Architecture; draft-ietf-spring-segment-routing-policy-02.txt", Spring Working Group, Oct. 22, 2018; 33 Pages.
Filsfils et al., "SRv6 Network Programming; draft-filsfils-spring-srv6-network-programming-05", Spring, Jul. 2, 2018, 53 Pages.
Gross et al., "Geneve: Generic Network Virtualization Encapsulation; draft-ietf-nvo3-geneve-08", Network Working Group, Oct. 7, 2018; 29 Pages.
Halpern et al., "Service Function Chaining (SFC) Architecture", Internet Engineering Task Force (IETF) , RFC 7665, Oct. 2015; 32 Pages.
Mahalingam et al., "Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks", Independent Submission , RFC 7348, Aug. 2014; 22 Pages.
Maino et al., "Generic Protocol Extension for VXLAN; draft-ietf-nvo3-vxlan-gpe-06", Network Working Group, Apr. 30, 2018; 17 Pages.
Pignataro et al., "IPv6 Support for Generic Routing Encapsulation (GRE)", Internet Engineering Task Force (IETF), RFC 7676 , Oct. 2015; 11 Pages.
Quinn et al., "Network Service Header (NSH)", Internet Engineering Task Force (IETF), RFC 8300, Jan. 2018; 40 Pages.

Also Published As

Publication number Publication date
CN111988266A (zh) 2020-11-24
EP3955541A4 (fr) 2022-05-18
EP3955541A1 (fr) 2022-02-16
CN111988266B (zh) 2022-05-17
EP3955541B1 (fr) 2023-06-21
WO2020238809A1 (fr) 2020-12-03
US20220109745A1 (en) 2022-04-07

Similar Documents

Publication Publication Date Title
US12395572B2 (en) Packet processing method
US12309064B2 (en) Method for forwarding packet in SRv6 service function chain, SFF, and SF device
US12267230B2 (en) Packet processing method and apparatus, network device, and storage medium
US11979322B2 (en) Method and apparatus for providing service for traffic flow
US20220360525A1 (en) Packet Processing Method, Apparatus, and System
KR102555671B1 (ko) 패킷 처리 방법, 관련 기기 및 컴퓨터 저장 매체
EP3742683B1 (fr) Procédé et dispositif de traitement de paquet à l'aide d'une pile d'étiquettes sr unifiée
US10516610B2 (en) Segment routing packet policies and functions providing processing signaling and packet forwarding efficiencies in a network
US20230137778A1 (en) Packet Sending Method and Apparatus, Network Device, System, and Storage Medium
US20210203586A1 (en) Communication Method, Device, and System
US20240106748A1 (en) Packet processing method, apparatus, and system
WO2018000443A1 (fr) Procédé, dispositif et système de réacheminement de paquets basés sur le chaînage de fonctions de service (sfc)
US20220109627A1 (en) Method and Apparatus for Implementing Service Function Processing
US20240275722A1 (en) Packet forwarding method and apparatus, device, and storage medium
US11343173B2 (en) Systems and methods to implement path aware networking
US12531803B2 (en) Method and apparatus for sending multicast packet and method and apparatus for obtaining forwarding entry
WO2020114083A1 (fr) Procédé et appareil de traitement d'informations ioam
US20240283738A1 (en) Packet Processing Method, Apparatus, and System
US12615208B2 (en) Method for generating routing information, method for sending location information, method for forwarding packet, and device
US11082540B2 (en) Network operations including protocol processing of a packet updating an operations data field of a different protocol

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHANG, YONGKANG;WANG, ZHONGZHEN;SIGNING DATES FROM 20200119 TO 20250512;REEL/FRAME:071310/0034

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE