WO2018188663A1 - Procédé et dispositif de notification d'informations - Google Patents

Procédé et dispositif de notification d'informations Download PDF

Info

Publication number
WO2018188663A1
WO2018188663A1 PCT/CN2018/083101 CN2018083101W WO2018188663A1 WO 2018188663 A1 WO2018188663 A1 WO 2018188663A1 CN 2018083101 W CN2018083101 W CN 2018083101W WO 2018188663 A1 WO2018188663 A1 WO 2018188663A1
Authority
WO
WIPO (PCT)
Prior art keywords
ioam
node
pcep
message
capability information
Prior art date
Application number
PCT/CN2018/083101
Other languages
English (en)
Chinese (zh)
Inventor
陈然
肖敏
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018188663A1 publication Critical patent/WO2018188663A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling

Definitions

  • the present disclosure relates to the field of communication technologies, for example, to an information notification method and apparatus.
  • IOAM In-situ Operation Administration and Maintenance
  • IOAM is also called in-band OAM.
  • In-band OAM is sent along with data packets, and no additional control plane messages are required to send OAM data.
  • In-band OAM is generally deployed in a specific domain.
  • IOAM can implement complex OAM functions such as multiple path tracking, path verification, and Service-Level Agreement (SLA) authentication.
  • SLA Service-Level Agreement
  • in-band OAM can be used in different scenarios, such as Internet Protocol Version 6, IPV6, and Virtual Extensible LAN-Generic Protocol Extension (VXLAN-GPE).
  • IPV6 Internet Protocol Version 6
  • VXLAN-GPE Virtual Extensible LAN-Generic Protocol Extension
  • SFC service function chain
  • SR segment routing
  • the IOAM function cannot be implemented through a node outside the IOAM domain.
  • the embodiment of the present application provides an information notification method and apparatus, so as to implement node information collected by a predetermined node to support an IOAM function in an IOAM domain.
  • An embodiment of the present application provides an information notification method, including:
  • the IOAM node encapsulates IOAM capability information using one of the following protocols: Extended Path Computation Unit Communication Protocol (PCEP), Extended PCEP-Link State (LS), or OpenFlow OpenFlow Protocol;
  • PCEP Extended Path Computation Unit Communication Protocol
  • LS Extended PCEP-Link State
  • OpenFlow OpenFlow Protocol OpenFlow OpenFlow Protocol
  • the IOAM node sends a PCEP message, a PCEP-LS message, or an OpenFlow protocol message carrying the IOAM capability information to a predetermined node.
  • An embodiment of the present application provides an information notification method, including:
  • the predetermined node receives the PCEP message, the PCEP-LS message, or the OpenFlow protocol message sent by the IOAM node;
  • the predetermined node parses the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, and includes:
  • the processing module is configured to encapsulate the IOAM capability information by using one of the following protocols: an extended PCEP, an extended PCEP-LS, or an OpenFlow protocol;
  • the sending module is configured to: send the PCEP message, the PCEP-LS message, or the OpenFlow protocol message that carries the IOAM capability information to the predetermined node.
  • the embodiment of the present application provides an information notification apparatus, which is applied to a predetermined node, and includes:
  • the receiving module is configured to: receive a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node;
  • the parsing module is configured to parse the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed Any one of the above information notification methods is implemented when the reader reads execution.
  • An embodiment of the present application provides an information notification apparatus, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is read and executed by the processor , to implement any of the above information notification methods.
  • the embodiment of the present application further provides a machine readable medium, where a computer program is stored thereon, and when the computer program is executed by the processor, any one of the foregoing information notification methods is implemented.
  • the embodiment of the present application further provides a machine readable medium storing a computer program, where the computer program is executed by a processor to implement any of the above information notification methods.
  • the node information supporting the IOAM function in the IOAM domain is collected by extending the PCEP, the PCEP-LS, or the OpenFlow protocol, so that the node that collects the IOAM function in the IOAM domain is collected by the predetermined node.
  • FIG. 1 is a flowchart of an information notification method according to an embodiment of the present application
  • FIG. 2 is a flowchart of an information notification method according to another embodiment of the present application.
  • FIG. 3 is a network connection diagram according to an embodiment of the present application.
  • FIG. 5 is a network connection diagram according to another embodiment of the present application.
  • FIG. 6 is a flowchart of an information notification method according to another embodiment of the present application.
  • FIG. 7 is a network connection diagram according to another embodiment of the present application.
  • FIG. 8 is a flowchart of an information notification method according to another embodiment of the present application.
  • FIG. 9 is a schematic diagram of a format of an IOAM capability type length value according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of a format of a path tracking subtype length value according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of a format of a path verification subtype length value according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of an information notification apparatus according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an information notification apparatus according to another embodiment of the present application.
  • the edge node that embeds the OAM data packet in the data packet is also called the IOAM encapsulation node.
  • the edge node that leaves the IOAM domain removes the OAM data packet.
  • the path verification method of the IOAM is: embedding the OAM data packet in the data packet in the IOAM encapsulation node, and the IOAM forwarding node fills the relevant OAM information into the OAM data packet according to a certain algorithm.
  • the IOAM decapsulation node replaces the OAM information in the OAM data packet with the IOAM forwarding node to check whether the path is consistent with the configured path and removes the OAM data packet.
  • the node that implements the path check may be completed by a predetermined node set outside the IOAM domain, for example, the external predetermined node completes the path check based on the complete in-band OAM data message.
  • an embodiment of the present application provides an information notification method, including:
  • Step 101 The IOAM node encapsulates the IOAM capability information by using an extended Path Computation Element Protocol (PCEP), or encapsulates the IOAM capability by using an extended PCEP-link-state (PCEP-LS). Information, or, encapsulates IOAM capability information using the OpenFlow protocol.
  • PCEP Path Computation Element Protocol
  • PCEP-LS extended PCEP-link-state
  • Step 102 The IOAM node sends a PCEP message, a PCEP-LS message, or an OpenFlow protocol message that carries the IOAM capability information to the predetermined node.
  • the IOAM node may use the extended PCEP to encapsulate the IOAM capability information, and send the PCEP message carrying the IOAM capability information to the predetermined node; or the IOAM node may encapsulate the IOAM capability information by using the extended PCEP-LS, and will carry The PCEP-LS packet of the IOAM capability information is sent to the predetermined node.
  • the IOAM node may encapsulate the IOAM capability information by using the OpenFlow protocol, and send an OpenFlow protocol message carrying the IOAM capability information to the predetermined node.
  • the predetermined node may be a Path Computation Element (PCE) or a controller or a network management system in the network management system.
  • PCE Path Computation Element
  • the PCE is an entity capable of computing and knowing the path between any nodes in an autonomous system (AS). It can be integrated inside the router or exist as a separate entity in the network. Can be integrated with the network management system. PCE is more aware of network traffic and path selection within the AS and can therefore be used for better path computation.
  • the nodes in the IOAM domain can work as a Path Computation Client (PCC), so the PCEP can be extended to notify the PCE of its own supported IOAM capabilities.
  • PCC Path Computation Client
  • the OpenFlow protocol is used to describe the criteria used for the interaction between the controller and the switch, as well as the interface standards for the controller and switch.
  • the core part of the protocol is a collection of information structures for the OpenFlow protocol.
  • the OpenFlow protocol can be run between the nodes and controllers in the IOAM domain. In some scenarios using the OpenFlow protocol, the OpenFlow protocol can be extended to perform IOAM capability advertisement in the IOAM domain.
  • the IOAM node encapsulates the IOAM capability information by using the extended PCEP, and may include:
  • the IOAM node extends the Open message in the PCEP to carry IOAM capability information.
  • the IOAM node encapsulates the IOAM capability information by using the extended PCEP-LS, and may include:
  • the IOAM node adds a PCEP-LS object (Object); the IOAM capability information is encapsulated by the added PCEP-LS object.
  • Object PCEP-LS object
  • the added PCEP-LS object may include at least one of: Node Descriptors Type Length Value (TLV), Prefix Descriptors TLV, and Link Description Link Descriptors TLV.
  • TLV Type Length Value
  • Prefix Descriptors TLV Prefix Descriptors TLV
  • Link Description Link Descriptors TLV Link Description Link Descriptors
  • the IOAM capability information may be carried by at least one of a Node Descriptor TLV, a Prefix Descriptor TLV, and a Link Descriptor TLV.
  • the IOAM node encapsulates the IOAM capability information by using the OpenFlow protocol, and may include: the IOAM node encapsulates the IOAM capability information in a flow table function response (table feature reply) message.
  • the IOAM node encapsulating the IOAM capability information in the table feature reply message may include: adding one or more IOAM matching fields in the table feature reply message, and specifying to match the one or more IOAM matching fields. Subsequent operations, such as modifying or adding new entries, may be used to modify or add IOAM data.
  • the IOAM capability information may include the following information: a type of IOAM.
  • the types of IOAM include: path tracking, path verification, and end-to-end verification.
  • the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
  • the embodiment of the present application provides an information notification method, including:
  • Step 201 The predetermined node receives a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node.
  • Step 202 The predetermined node parses the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • the predetermined node may be a controller or a network manager in the PCE or network management system.
  • the predetermined node may receive the PCEP message sent by the IOAM node, and parse the IOAM capability information advertised by the IOAM node from the PCEP message; or, the predetermined node receives the PCEP-LS message sent by the IOAM node, and from the PCEP - The LSAM capability information advertised by the IOAM node is parsed in the LS packet; or the predetermined node receives the OpenFlow protocol message sent by the IOAM node, and parses the IOAM capability information advertised by the IOAM node from the OpenFlow protocol message.
  • the IOAM capability information may be carried by an Open message in the PCEP, or encapsulated in an added PCEP-LS object, or carried by a table feature reply message of the OpenFlow protocol.
  • the added PCEP-LS object may include at least one of the following: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV.
  • the IOAM capability information may be carried by at least one of a Node Descriptor TLV, a Prefix Descriptor TLV, and a Link Descriptor TLV.
  • the IOAM capability information may include: a type of IOAM; in an exemplary embodiment, the types of the IOAM include: path tracking, path verification, and end-to-end verification.
  • the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
  • the Bit Indexed Explicit Replication (BIER) domain is an IOAM domain, and all BIER nodes in FIG. 3 are also nodes supporting IOAM technology at the same time.
  • a BIER-Forwarding Ingress Router (BFIR) is also called an IOAM encapsulation node
  • BFER BIER egress router
  • BFR BIER forwarding node
  • the data message is sent from the BIER ingress node to the BIER egress node.
  • BIER BIER Ingress Node
  • IOAM encapsulation node interacts with the PCE.
  • FIG. 4 is a flowchart of an information notification method according to the embodiment. Referring to FIG. 4, the method provided in this embodiment includes:
  • step 301 the BIER ingress node carries the IOAM capability TLV through the extended PCEP-LS object, and notifies the PCE that it supports the IOAM capability.
  • the IOAM capability information may be carried by an extension node descriptor TLV (NODE Descriptors TLV), a link descriptor TLV (Link Descriptors TLV), and a prefix descriptor TLV (Prefix Descriptors TLV).
  • NODE Descriptors TLV extension node descriptors TLV
  • Link Descriptors TLV Link Descriptors TLV
  • Prefix Descriptors TLV prefix Descriptors TLV
  • the Type field identifies the TLV as the IOAM capability type length value (IOAM-capability TLV); the Length field is the total length of the TLV; and the Option type field is the type of the IOAM.
  • the IETF defines three types of IOAM types: in-suit OAM Tracing Option, in-suit OAM Proof of Transit Option, and In-situ OAM Edge-to-Edge Option.
  • the Reserved field is a reserved field to be expanded.
  • the one or more option sub-TLVs may include an in-suit OAM Tracing Option Sub-TLV, an in-suit OAM Proof of Transit Option Sub-TLV, and an end-to-end In-situ OAM Edge-to-Edge Option Sub-TLV.
  • FIG. 10 is a schematic diagram of a format of a path tracking subtype length value. As shown in FIG. 10, the F byte is used to indicate the type of path tracking, and currently includes the following two types: Pre-allocated Trace Option and Incremental Trace Option.
  • FIG. 11 is a schematic diagram of the format of the path verification subtype length value.
  • the path verification subtype length value is defined as the following three types: universal proof of Transit (universal POT), network service header metadata (NSH metadata) path verification, and Proof of Transit of Segment Routing (SR POT).
  • universal POT universal proof of Transit
  • NSH metadata network service header metadata
  • SR POT Proof of Transit of Segment Routing
  • the IOAM encapsulation node/BIER ingress node interacts with the PCE.
  • the nodes supporting the IOAM and BIER technologies in the IOAM and BIER domains may interact with the PCE, or the designated IOAM node may interact with the PCE. This application is not limited to this, and which nodes the PCE interacts with depends on the actual deployment.
  • the BIER ingress node/IOAM encapsulation node collects the supported IOAM of the relevant node in the IOAM domain through the Interior Gateway Protocol (IGP).
  • IGP Interior Gateway Protocol
  • Step 302 After receiving the PCEP-LS packet, the PCE analyzes which nodes support the IOAM capability.
  • the segment routing (SR) domain is an IOAM domain
  • all the SR nodes in FIG. 5 are also nodes supporting the IOAM technology at the same time. All of the SR nodes in Figure 5 interact with the PCE.
  • the SR ingress node is also called an IOAM encapsulation node
  • the SR egress node is also called an IOAM decapsulation node
  • the SR forwarding node is also called an intermediate IOAM forwarding node; as shown in FIG. 5, the data packet is sent from the SR ingress node. Go to the SR exit node.
  • FIG. 6 is a flowchart of an information notification method provided by this embodiment. As shown in FIG. 6, the process of this embodiment includes:
  • the IOAM-related node (such as the node supporting both the SR technology and the IOAM technology in FIG. 5) sends an Open message carrying the IOAM Capability TLV to the PCE, indicating that the IOAM node supports the IOAM.
  • Step 402 After receiving the extended Open message, the PCE parses to know which nodes support the IOAM capability.
  • the VXLAN domain is an IOAM domain, and all nodes supporting the VXLAN technology in FIG. 7 also support IOAM.
  • the VXLAN domain and the nodes in the IOAM domain that support VXLAN and IOAM technologies interact with the controller.
  • Network Virtual Edge (NVE) is also called IOAM encapsulation node.
  • NVE is also called IOAM decapsulation node.
  • VXLAN forwarding node is also called intermediate IOAM forwarding node.
  • data packet From the IOAM encapsulation node to the IOAM decapsulation node.
  • FIG. 8 is a flowchart of an information notification method provided by this embodiment. As shown in FIG. 8, the process of this embodiment includes:
  • Step 501 The IOAM node sends a table feature reply message carrying the IOAM capability information to the controller, indicating that the IOAM node supports the IOAM function.
  • one or more IOAM matching fields may be added in the table feature reply message, and at the same time, an operation performed after matching the IOAM matching field may be specified, and may be an operation of modifying or adding a new item.
  • the controller After receiving the table feature reply message, the controller calculates the forwarding path of the IOAM node according to the IOAM capability information carried in the table feature reply message, and processes the IOAM capability information, and obtains the IOAM node forwarding path and the processed IOAM capability information. Send to the IOAM node.
  • the IOAM node After receiving the data packet carrying the IOAM packet, the IOAM node matches the IOAM header according to the IOAM node forwarding path and the IOAM capability information received from the controller, and then performs operations on the IOAM data, such as modifying or adding a new entry. And forward the data packet after the operation.
  • Step 502 After receiving the extended flow table function response message, the controller parses to know which nodes support the IOAM capability.
  • an embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, and includes:
  • the processing module 901 is configured to: encapsulate the IOAM capability information by using the extended PCEP, or encapsulate the IOAM capability information by using the extended PCEP-LS, or encapsulate the IOAM capability information by using the OpenFlow protocol;
  • the sending module 902 is configured to: send a PCEP message, a PCEP-LS message, or an OpenFlow protocol message that carries the IOAM capability information to the predetermined node.
  • the processing module 901 may be configured to encapsulate the IOAM capability information with the extended PCEP by:
  • the Open message in the PCEP is extended to carry IOAM capability information.
  • the processing module 901 may be configured to encapsulate the IOAM capability information with the extended PCEP-LS by:
  • the added PCEP-LS object may include at least one of the following: a node descriptor TLV, a prefix descriptor TLV, and a link descriptor TLV.
  • the processing module 901 may be configured to encapsulate the IOAM capability information by using the OpenFlow protocol in the following manner:
  • the IOAM capability information is encapsulated in a flow table function reply (table feature reply) message.
  • the IOAM capability information may include the following information: a type of IOAM; in an exemplary embodiment, the types of the IOAM include: path tracking, path verification, and end-to-end verification.
  • the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
  • the embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node, and includes:
  • the receiving module 1001 is configured to: receive a PCEP message, a PCEP-LS message, or an OpenFlow protocol message sent by the IOAM node;
  • the parsing module 1002 is configured to parse the IOAM capability information advertised by the IOAM node from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • the IOAM capability information may be carried by an Open message in the PCEP, or encapsulated in an added PCEP-LS object, or carried by a table feature reply message of the OpenFlow protocol.
  • the IOAM capability information may include: a type of IOAM.
  • the types of the IOAM include: path tracking, path verification, and end-to-end verification.
  • the IOAM capability information may further include at least one of the following: a subtype of path tracking, a subtype of path verification, and an end-to-end verification subtype.
  • An embodiment of the present application provides an information notification apparatus, which is applied to an IOAM node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed
  • the information notification method of the above IOAM node side is implemented when the reader reads and executes.
  • the embodiment of the present application further provides an information notification apparatus, which is applied to an IOAM node, including: a transmission module, a memory, and one or more processors; wherein the memory is configured to store a program for information notification; the information is used for information notification.
  • an information notification apparatus which is applied to an IOAM node, including: a transmission module, a memory, and one or more processors; wherein the memory is configured to store a program for information notification; the information is used for information notification.
  • the IOAM node encapsulates the IOAM capability information by using the extended PCEP, or encapsulates the IOAM capability information by using the extended PCEP-LS, or encapsulates the IOAM capability information by using the OpenFlow protocol; and transmits the PCEP message carrying the IOAM capability information and the PCEP-LS packet through the transmission module.
  • the text or OpenFlow protocol message is sent to the predetermined node.
  • the processor may include, but is not limited to, a processing device such as a Microcontroller Unit (MCU) or a Field-Programmable Gate Array (FPGA).
  • MCU Microcontroller Unit
  • FPGA Field-Programmable Gate Array
  • the memory may be set as a software program and a module for storing application software, such as a program instruction/module corresponding to the information notification method of the present application, and the processor executes various function applications and data processing by running a software program and a module stored in the memory. That is, the above method is implemented.
  • the memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • the memory can further include memory remotely located relative to the processor, which can be connected to the IOAM node over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission module can be arranged to receive or transmit data via a network.
  • the transmission module can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
  • RF Radio Frequency
  • An embodiment of the present application provides an information notification apparatus, which is applied to a predetermined node, including: a memory and one or more processors; wherein the memory is configured to store a program for information notification; the program for information notification is processed When the device reads and executes, the information notification method on the predetermined node side described above is implemented.
  • the embodiment of the present application further provides an information notification apparatus, which is applied to a predetermined node, including: a transmission module, a memory, and one or more processors; wherein the memory is configured to store a program for information notification; the information notification is used When the program is read and executed by the processor, the following operations are performed:
  • the IOAM capability information advertised by the IOAM node is parsed from the PCEP message, the PCEP-LS message, or the OpenFlow protocol message.
  • the processor may include, but is not limited to, a processing device such as an MCU or an FPGA.
  • the predetermined nodes described above may also include more or fewer components or have different configurations.
  • the memory may be configured as a software program and a module for storing application software, such as a program instruction/module corresponding to the information notification method in the embodiment of the present application, and the processor executes various functional applications by running a software program and a module stored in the memory. And data processing, that is, to achieve the above method.
  • the memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • the memory can further include memory remotely located relative to the processor, the remote memory being connectable to the predetermined node over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission module can be arranged to receive or transmit data via a network.
  • the transmission module can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
  • RF Radio Frequency
  • the embodiment of the present application further provides a machine readable medium storing a computer program, where the computer program is executed by the processor to implement the above information notification method on the IOAM node side or the predetermined node side.
  • a program to instruct related hardware e.g., a processor
  • a machine readable medium such as a read only memory, disk or optical disk.
  • Computer readable storage medium e.g., a hard disk drive
  • all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.
  • This application is not limited to any specific combination of hardware and software.
  • the present disclosure collects node information that supports the IOAM function in the IOAM domain by extending the PCEP, PCEP-LS, or OpenFlow protocol, thereby implementing node information that the predetermined node collects to support the IOAM function in the IOAM domain.

Landscapes

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

Abstract

La présente invention concerne un procédé et un dispositif de notification d'informations. Le procédé de notification d'informations consiste à : utiliser, par un nœud d'administration et de maintenance d'opérations intra-bandes (IOAM), un protocole de communication d'élément de calcul de chemin (PCEP) étendu pour intégrer des informations de capacité d'IOAM, ou utiliser un état de liaison (LS) de PCEP étendu pour intégrer des informations de capacité d'IOAM, ou utiliser le protocole OpenFlow pour intégrer des informations de capacité d'IOAM ; et transmettre un message de PCEP, un paquet de LS de PCEP, ou un message de protocole OpenFlow véhiculant les informations de capacité d'IOAM vers un nœud prédéfini.
PCT/CN2018/083101 2017-04-13 2018-04-13 Procédé et dispositif de notification d'informations WO2018188663A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710241351.5 2017-04-13
CN201710241351.5A CN108737127B (zh) 2017-04-13 2017-04-13 一种信息通告方法及装置

Publications (1)

Publication Number Publication Date
WO2018188663A1 true WO2018188663A1 (fr) 2018-10-18

Family

ID=63792271

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083101 WO2018188663A1 (fr) 2017-04-13 2018-04-13 Procédé et dispositif de notification d'informations

Country Status (2)

Country Link
CN (1) CN108737127B (fr)
WO (1) WO2018188663A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112868214A (zh) * 2018-11-02 2021-05-28 思科技术公司 分组内的协调负载转移oam记录
CN113810229A (zh) * 2021-09-16 2021-12-17 烽火通信科技股份有限公司 一种基于时序调度的ioam质量性能数据分析方法和装置
EP4047888A4 (fr) * 2019-11-19 2022-12-21 Huawei Technologies Co., Ltd. Procédé d'émission d'informations de configuration oam et noeud de commande

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109743340B (zh) 2019-04-04 2019-07-30 华为技术有限公司 报文处理的方法和网络装置
CN113783745A (zh) * 2020-06-10 2021-12-10 中国电信股份有限公司 网络遥测信息采集方法和系统、bier域入口节点
CN114301839B (zh) * 2020-09-22 2023-05-12 华为技术有限公司 一种组播报文传输方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1848775A (zh) * 2005-09-30 2006-10-18 华为技术有限公司 多跳伪线故障检测、上报和维护协商控制方法
CN101335692A (zh) * 2007-06-27 2008-12-31 华为技术有限公司 协商pcc和pce之间安全能力的方法及其网络系统
CN101945048A (zh) * 2010-09-20 2011-01-12 中兴通讯股份有限公司 一种标签交换路径的建立方法、系统及装置
CN101986622A (zh) * 2010-11-08 2011-03-16 中兴通讯股份有限公司 一种pce状态属性的自动识别方法及系统
CN104579946A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 确定路径计算单元的方法及通信设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3091705B1 (fr) * 2014-01-23 2018-09-05 Huawei Technologies Co., Ltd. Procédé de traitement de tunnel pour paquet, dispositif de commutation et dispositif de commande
CN105516015A (zh) * 2014-09-25 2016-04-20 中兴通讯股份有限公司 通知消息的获取、上报方法、装置及通知消息的交互系统
CN105306276B (zh) * 2015-11-13 2019-07-09 上海斐讯数据通信技术有限公司 基于软件定义网络的oam协议封装方法、系统及epon接入网

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1848775A (zh) * 2005-09-30 2006-10-18 华为技术有限公司 多跳伪线故障检测、上报和维护协商控制方法
CN101335692A (zh) * 2007-06-27 2008-12-31 华为技术有限公司 协商pcc和pce之间安全能力的方法及其网络系统
CN101945048A (zh) * 2010-09-20 2011-01-12 中兴通讯股份有限公司 一种标签交换路径的建立方法、系统及装置
CN101986622A (zh) * 2010-11-08 2011-03-16 中兴通讯股份有限公司 一种pce状态属性的自动识别方法及系统
CN104579946A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 确定路径计算单元的方法及通信设备

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112868214A (zh) * 2018-11-02 2021-05-28 思科技术公司 分组内的协调负载转移oam记录
CN112868214B (zh) * 2018-11-02 2024-01-19 思科技术公司 分组内的协调负载转移oam记录
EP4047888A4 (fr) * 2019-11-19 2022-12-21 Huawei Technologies Co., Ltd. Procédé d'émission d'informations de configuration oam et noeud de commande
CN113810229A (zh) * 2021-09-16 2021-12-17 烽火通信科技股份有限公司 一种基于时序调度的ioam质量性能数据分析方法和装置
CN113810229B (zh) * 2021-09-16 2023-12-05 烽火通信科技股份有限公司 一种基于时序调度的ioam质量性能数据分析方法和装置

Also Published As

Publication number Publication date
CN108737127B (zh) 2022-07-22
CN108737127A (zh) 2018-11-02

Similar Documents

Publication Publication Date Title
WO2018188663A1 (fr) Procédé et dispositif de notification d'informations
WO2018188662A1 (fr) Procédé et dispositif de notification d'informations
US11979322B2 (en) Method and apparatus for providing service for traffic flow
US10243827B2 (en) Techniques to use a network service header to monitor quality of service
US10439931B2 (en) Data packet processing method, service node, and delivery node
EP3787243B1 (fr) Procédé et appareil de traitement de paquets de données, support de données et dispositif électronique
WO2018210213A1 (fr) Procédé et dispositif de mise en œuvre d'un conditionnement ioam et support de stockage
WO2018210225A1 (fr) Procédé et dispositif de mise en œuvre automatique d'encapsulation ioam, et support d'informations
WO2016045098A1 (fr) Commutateur,dispositif de commande, système et procédé de détection de qualité de liaison
WO2016089575A1 (fr) Chaînage de fonctions de service inter-domaines
WO2015184771A1 (fr) Procédé et dispositif de nœud pour l'exploitation, l'administration et la maintenance d'un chaînage de fonctions de service
US10693777B2 (en) In-situ operations, administration, and maintenance (iOAM) for software defined architectures (SDAs)
WO2018121257A1 (fr) Procédé, appareil et système d'émission de message, et support de stockage
CN108712338B (zh) 报文处理方法及装置
WO2015035616A1 (fr) Procédé et dispositif permettant des communications multiréseaux
WO2017193732A1 (fr) Procédé d'encapsulation et de décapsulation d'un message de données à pseudo-fil, et appareil associé
CN112350934A (zh) 数据传输方法、网络节点和数据传输系统
CN112672363B (zh) 随流信息遥测能力的确认方法和设备
US11489768B2 (en) Method for creating inter-domain bidirectional tunnel, communication method and device, and storage medium
CN107231309B (zh) 获取sdn全网视图的方法、控制器及目的交换节点
WO2020114083A1 (fr) Procédé et appareil de traitement d'informations ioam
CN110784402B (zh) 路径标识传输方法、装置和计算机可读存储介质
WO2015154393A1 (fr) Procédé et appareil de traitement de capacité de nœud de service, classificateur de service et contrôleur de service
US10397059B2 (en) Router controlling
CN110011820B (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: 18783976

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18783976

Country of ref document: EP

Kind code of ref document: A1