WO2015196923A1 - Procédé d'envoi d'informations et dispositif de réseau - Google Patents

Procédé d'envoi d'informations et dispositif de réseau Download PDF

Info

Publication number
WO2015196923A1
WO2015196923A1 PCT/CN2015/080992 CN2015080992W WO2015196923A1 WO 2015196923 A1 WO2015196923 A1 WO 2015196923A1 CN 2015080992 W CN2015080992 W CN 2015080992W WO 2015196923 A1 WO2015196923 A1 WO 2015196923A1
Authority
WO
WIPO (PCT)
Prior art keywords
attribute information
identifier
configuration information
topology configuration
network device
Prior art date
Application number
PCT/CN2015/080992
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 WO2015196923A1 publication Critical patent/WO2015196923A1/fr

Links

Images

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and a network device for transmitting information.
  • the service chain network includes a service chain control system (English service chain orchestrator), one or more SRs (Service Routers), and one or more SN (Service Node) service chain control systems attached to the SR. Maintain and manage the SN and SR included in the service chain network.
  • the service chain control system needs to rely on the service chain network topology to maintain and manage the service chain network. Therefore, before maintaining and managing the service chain network, the service chain control system needs to be a service chain network topology.
  • a scheme for generating a service chain network topology which may be: a technician manually configures an SN and SR attachment relationship table corresponding to each SR in the service chain network, and the SN and SR attachment relationship table corresponding to the SR includes the The identifier of the SR and the identity of the SN bound to the SR. The technician then records the SN and SR attachment relationship table corresponding to each SR into the service chain control system.
  • the technician can also input the SR attribute information of each SR into the service chain control system, and the SR attribute information of the SR includes the management IP (Internet Protocol) address of the SR, The UUID (Universally Unique Identifier) of the SR, the interface type of the SR, the interface number of the SR, the number of flow tables supported by the SR, and/or the number of SNs supported by the SR.
  • the service chain control system generates a service chain network topology according to the SN and SR attachment relationship table corresponding to each SR and/or the SR attribute information of each SR.
  • the efficiency of generating the service chain network topology is generated because the technician manually enters the SN and SR attachment relationship table corresponding to each SR and/or the SR attribute information of each SR. Lower.
  • an embodiment of the present invention provides a method and a network device for transmitting information.
  • the technical solution is as follows:
  • a network device the network device includes:
  • a receiving module configured to receive SR attribute information sent by the service router SR, where the SR attribute information includes at least an identifier of the SR;
  • An acquiring module configured to acquire topology configuration information, where the topology configuration information includes the SR attribute information and an identifier of an SN included in the network device;
  • a sending module configured to send the topology configuration information to the service chain control system.
  • the receiving module is configured to receive, by the service router SR, a link layer discovery protocol LLDP packet that carries the SR attribute information, from the LLDP.
  • the SR attribute information is extracted from the data unit of the message.
  • the receiving module is configured to receive a link layer discovery protocol LLDP packet sent by the service router SR, If the reserved bit in the system capability field of the LLDP packet is set, the LLDP packet is determined to carry the SR attribute information, and the SR attribute information is extracted from the data unit of the LLDP packet.
  • the topology configuration information includes at least an SN and an SR attachment relationship
  • the obtaining module includes:
  • Selecting a submodule configured to select an identifier of the SN from the SN list, where the SN list is used to store an identifier of the SN attached to the SR;
  • Establishing a sub-module configured to establish, according to the identifier of the selected SN and the SR attribute information, an SN-SR attachment relationship, where the SN-SR attachment relationship includes an identifier of the SR and an identifier of the selected SN.
  • the selecting submodule is configured to select an identifier of all SNs included in the SN list; or if the SR attribute information includes Referring to the number of SNs supported by the SR, the identifier of the SN is selected from the SN list according to the number of SNs supported by the SR.
  • the sending module is specifically configured to: call a function for reading information from a preset function library;
  • the topology configuration information is stored in a management component on the network device, wherein the management component includes an open interface, and the open interface is configured to store the storage in the management component after being invoked by the service chain control system Topology configuration information is transmitted to the service chain control system.
  • the SR attribute information further includes an interface type of the SR, Any one or more of an interface number of the SR, a number of flow tables supported by the SR, and a number of SNs supported by the SR.
  • a second aspect is a method of transmitting information, the method comprising:
  • SR attribute information sent by the service router SR, where the SR attribute information includes at least an identifier of the SR;
  • topology configuration information includes the SR attribute information and an identifier of a service node SN included in the network device;
  • the information about the SR attribute sent by the receiving service router SR includes:
  • Extracting SR attribute information from the data unit of the LLDP message Extracting SR attribute information from the data unit of the LLDP message.
  • the link layer discovery protocol LLDP packet that is sent by the receiving service router SR that carries the SR attribute information includes :
  • the topology configuration information includes at least an SN and an SR attachment relationship
  • the acquiring topology configuration information includes:
  • the selecting the identifier of the SN from the SN list includes:
  • the identifier of the SN is selected from the SN list according to the number of SNs supported by the SR.
  • the sending the topology configuration information to the service chain control system includes:
  • the function And storing, by the function, the topology configuration information in a management component on the network device, wherein the management component includes an open interface, where the open interface is used after being invoked by the service chain control system
  • the topology configuration information stored in the management component is transmitted to the service chain control system.
  • the SR attribute information further includes an interface class of the SR Any one or more of a type, an interface number of the SR, a number of flow tables supported by the SR, and a number of SNs supported by the SR.
  • a network device includes a memory, a processor, and one or more programs, wherein the one or more programs are stored in the memory and configured to be processed by the Executing the one or more programs includes instructions for performing the following operations:
  • SR attribute information sent by the service router SR, where the SR attribute information includes at least an identifier of the SR;
  • topology configuration information includes the SR attribute information and an identifier of a service node SN included in the network device;
  • the SR attribute information sent by the SR is received, and the topology configuration information is obtained, where the topology configuration information includes the SR attribute information and the identifier of the SN attached to the SR; and the topology configuration information is sent to the service chain control system,
  • the service chain control system generates a service chain network topology according to the topology configuration information.
  • the service chain control system can automatically obtain topology configuration information, and generate a service chain network topology according to the topology configuration information. Thereby, the efficiency of generating a service chain network topology is improved.
  • FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for transmitting information according to an embodiment of the present invention.
  • FIG. 4-1 is a flowchart of another method for sending information according to an embodiment of the present invention.
  • LLDP Link Layer Discovery Protocol
  • FIG. 4 is a schematic structural diagram of a system capability TLV (Type-length-value) according to an embodiment of the present invention.
  • 4-4 is a schematic structural diagram of a system attribute TLV according to an embodiment of the present invention.
  • FIGS. 4-5 are schematic diagrams showing a topology structure of a service chain network according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • a service chain network needs to be deployed in the network.
  • the service chain network includes a service control system, one or more SRs, and a server connected to the SR, and one or more SNs are deployed in the server.
  • the service chain control system is used for the SN created in the server, maintains the service chain network topology, and configures a forwarding table for each SR according to the service chain network topology.
  • the SR is configured to receive the packet and forward the packet to the SN attached to it or to the SR connected thereto according to the forwarding table stored by itself.
  • SRs can be deployed on physical switches.
  • the SN is configured to receive the packet forwarded by the SR, and process the packet.
  • the SN can be implemented as a VM (Virtual Machine). For example, if the SN is a firewall, the SN can enhance the received message.
  • the service chain control system needs to configure each SR according to the service chain network topology.
  • the forwarding table so the service chain network topology is very important to implement the function of the service chain network. Therefore, in the invention, the service chain network topology can be generated by the following embodiments.
  • an embodiment of the present invention provides a network device, including:
  • the receiving module 201 is configured to receive SR attribute information sent by the SR, where the SR attribute information includes at least an identifier of the SR;
  • the obtaining module 202 is configured to acquire topology configuration information, where the topology configuration information includes the SR attribute information and an identifier of the SN included in the network device;
  • the sending module 203 is configured to send the topology configuration information to the service chain control system.
  • the service chain control system receives topology configuration information sent by each network device in the Servie chain network, and generates a Servie chain network topology according to each topology configuration information received.
  • the receiving module 201 is configured to receive an LLDP packet that carries the SR attribute information sent by the SR, and extract the SR attribute information from the data unit of the LLDP packet.
  • the receiving module 201 is configured to receive the LLDP packet sent by the SR, and if the reserved bit in the system capability field of the LLDP packet is set, determine that the LLDP packet carries the SR attribute information, from the LLDP.
  • the SR attribute information is extracted from the data unit of the message.
  • the SR may select one bit from the reserved bits of the system capability field of the LLDP message, and select the selected bit position, and the set bit is used to represent the LLDP.
  • the data unit of the packet carries the SR attribute information, and then the data unit of the LLDP packet carries the SR attribute information, and the LLDP packet is sent.
  • the topology configuration information includes at least an SN and an SR attachment relationship
  • the obtaining module 202 includes:
  • Selecting a submodule configured to select an identifier of the SN from the SN list, where the SN list is used to store an identifier of the SN included in the network device;
  • a sub-module is configured to establish an SN-SR attachment relationship according to the identifier of the selected SN and the SR attribute information, where the SN-SR attachment relationship includes the identifier of the SR and the identifier of the selected SN.
  • the topology configuration information may further include any one or more of an interface type of the SR, an interface number of the SR, a number of flow tables supported by the SR, and a number of SNs supported by the SR.
  • the selection sub-module is specifically used to select an identifier of all SNs included in the SN list; or, if the SR attribute information includes the number of SNs supported by the SR, select from the SN list according to the number of SNs supported by the SR.
  • the logo of the SN is specifically used to select an identifier of all SNs included in the SN list; or, if the SR attribute information includes the number of SNs supported by the SR, select from the SN list according to the number of SNs supported by the SR.
  • the logo of the SN is specifically used to select an identifier of all SNs included in the SN list.
  • the sending module 203 is specifically configured to: call a function for reading information from a preset function library; and store the topology configuration information in a management component on the network device, where the management component includes an open interface.
  • the open interface is configured to transmit topology configuration information stored in the management component to the service chain control system after being invoked by the service chain control system.
  • the network device may be a server.
  • the SR attribute information sent by the SR is received, and the topology configuration information is obtained, where the topology configuration information includes the SR attribute information and the identifier of the SN attached to the SR; and the topology configuration information is sent to the service chain control system,
  • the service chain control system generates a service chain network topology according to the topology configuration information.
  • the service chain control system can automatically obtain topology configuration information, and generate a service chain network topology according to the topology configuration information. Thereby, the efficiency of generating a service chain network topology is improved.
  • the LLDP packet can be extended to the LLDP packet to carry the SR attribute information, so that the SR can report the SR attribute information to the network device through the LLDP packet.
  • an embodiment of the present invention provides a method for sending information, where the processing procedure of the method may include the following steps:
  • Step 301 Receive SR attribute information sent by the SR, where the SR attribute information includes at least an identifier of the SR.
  • Step 302 Acquire topology configuration information, where the topology configuration information includes the SR attribute information and an identifier of the SN included in the network device.
  • Step 303 Send the topology configuration information to the service chain control system.
  • the network device may be a server.
  • the various steps shown in FIG. 3 may be performed by the network device shown in FIG. 2.
  • the SR attribute information that is sent by the SR is received, where the SR attribute information includes at least the identifier of the SR, and the topology configuration information is obtained, where the topology configuration information includes the SR attribute information and
  • the identifier of the SN included in the network device is sent to the service chain control system, and the service chain control system generates a Service chain network topology according to the topology configuration information.
  • the service chain control system can automatically acquire topology configuration information, and generate a Service chain network topology according to the topology configuration information. Thereby, the efficiency of generating a service chain network topology is improved.
  • an embodiment of the present invention provides a method for sending information, including:
  • Step 401 The SR sends the SR attribute information to the server connected thereto, where the SR attribute information includes at least the identifier of the SR.
  • the SR can be directly connected to the server. That is, there is no other device on the link between the SR and the server.
  • the SR can also be connected to the server through other devices.
  • the SR can be connected to the server through a router.
  • the identifier of the SR may include the ID of the SR, the UUID of the SR, and/or the management IP address of the SR, and the like.
  • the SR attribute information may also include an interface type of the SR, an interface number of the SR, a number of flow tables supported by the SR, and/or a number of SNs supported by the SR, and the like.
  • the SR can send the SR attribute information to the server through the LLDP packet, specifically:
  • the SR selects a bit from the reserved bits in the system capability field of the LLDP packet, and sets the bit bit to set the data unit of the LLDP packet to carry the SR attribute information, where the set bit is used to represent the LLDP.
  • the data unit of the packet carries the SR attribute information, and sends the LLDP message to the server directly connected thereto.
  • LLDP messages include DA, SA, Type, FCS, and data units.
  • the DA is used to carry the destination MAC address.
  • the destination MAC address is 01-80-C2-00-00-0E.
  • the SA is used to carry the source MAC address.
  • Type is used to carry the packet type.
  • the type of the packet carried by the Type is 0x88CC.
  • the FCS is used to carry a frame check sequence.
  • the data unit is an information exchange body of the LLDP packet and can carry different information. In the embodiment of the present invention, the data unit carries the SR attribute information.
  • the data unit includes a system capability TLV and at least one system attribute TLV.
  • the system capability TLV is located before the system attribute TLV in the data unit.
  • the system capability TLV includes a system capability field, the bits in the system capability field represent a system capability, and the system attribute TLV is used to carry information.
  • the system capability TLV includes a TLV Type field (TLV Type), a Capabilities/Status String Length field, a System Capabilities, and an Enable Capability field. (Enable Capabilities).
  • TLV Type TLV Type
  • Capabilities/Status String Length field a System Capabilities
  • Enable Capability field a TLV Type field
  • the System Capability field consists of two bytes, 16 bits. Each system capability of the data unit corresponds to a bit in the System Capability field. If a certain ratio feature is set, the System Capability TLV is used to indicate that the data unit has the system capability corresponding to that bit.
  • the eighth to sixteenth bits of the System Capability field are still reserved. Therefore, in the embodiment of the present invention, one bit can be selected from the reserved bits, and the system function corresponding to the bit is defined as an SR function. If the selected bit position is bit, it indicates that the data unit has the SR function, and the data unit having the SR function is defined to be able to carry the SR attribute information.
  • the system attribute TLV includes a TLV header and a payload part
  • the TLV header is used to carry the information type
  • each value formed by the TLV field represents an information type.
  • Table 2 a type of information represented by each value formed by a TLV field, such as a TLV field.
  • the value of the constructed value 5 represents the device name.
  • the payload portion is used to carry information corresponding to the type of information.
  • the data unit that sets the LLDP packet carries the SR attribute information, which may be:
  • the system attribute TLV of the LLDP packet is configured to carry the information type corresponding to the SR attribute information, and the payload part of the system attribute TLV of the LLDP packet carries the SR attribute information to implement setting the data of the LLDP packet.
  • the unit carries SR attribute information.
  • Step 402 The server receives the SR attribute information sent by the SR.
  • the server receives the LLDP packet sent by the SR, and determines whether the reserved bit in the system capability field in the LLDP packet is set. If the LLDP packet is set, the LLDP packet carries the SR attribute information. The SR attribute information is extracted from the data unit of the LLDP message.
  • Step 403 The server acquires topology configuration information, where the topology configuration information includes the SR attribute information and an identifier of the SN included by itself.
  • the server includes at least one SN.
  • the identity of the SN may uniquely identify the SN in the service chain network, and the SN identity may be, but is not limited to, the ID of the SN, the UUID of the SN, and/or the SN. IP address.
  • the server selects the identifier of the SN from the SN list, and establishes an attachment relationship between the SN and the SR according to the received SR attribute information and the selected SN identifier.
  • the SN and SR attachment relationship includes the identifier and selection of the SR.
  • the identifier of the SN and the attachment relationship table of the SN and the SR are used as topology configuration information.
  • the topology configuration information may further include any one or more of an interface type of the SR in the SR attribute information, an interface number of the SR, a number of flow tables supported by the SR, and a number of SNs supported by the SR.
  • the identifier of the SN is selected from the SN list according to the number of SNs supported by the SR.
  • the server has a virtual machine management module, and the virtual machine management module can receive the SR attribute information sent by the SR, and acquire and store the topology configuration information.
  • Step 404 The server sends topology configuration information to the service chain control system.
  • the server includes a function library.
  • a function for reading information is extended in the function library.
  • a management component is also provided in the server, the management component having an open interface and opening the open interface to the service chain control system.
  • This library can be libvirt.
  • This step may be: the server calls a function for reading information from the preset function library; the topology configuration information is stored in its own management component by the called function, and the management component includes an open interface.
  • the service chain control system invokes an open interface of the management component and invokes the topology configuration information from the management component through the open interface.
  • the server invokes the topology configuration information from the virtual machine management module by using the called function, and then stores the called topology configuration information in the management component.
  • Step 405 The service chain control system receives the topology configuration information, and generates a service chain network topology according to the topology configuration information.
  • the service chain control system determines each SR and attaches to each SR according to the topology configuration information.
  • the SN generates a service chain network topology based on each SR and the SN attached to each SR. For example, the generated service chain network topology is shown in Figure 4-5.
  • the SR attribute information sent by the SR is sent to the server, the server obtains the topology configuration information, and then sends the topology configuration information to the service chain control system, and the service chain control system generates the service chain network topology according to the topology configuration information.
  • the service chain control system can automatically obtain topology configuration information, and generate a service chain network topology according to the topology configuration information. Thereby, the efficiency of generating a service chain network topology is improved.
  • an embodiment of the present invention provides a network device, where the network device includes a memory 501, a processor 502, and one or more programs, where the one or more programs are stored in the memory 501. And configured to execute, by the processor 502, the one or more programs include instructions for:
  • SR attribute information sent by the service router SR, where the SR attribute information includes at least an identifier of the SR;
  • topology configuration information includes the SR attribute information and an identifier of a service node SN included in the network device;
  • the SR attribute information sent by the receiving service router SR includes:
  • Extracting SR attribute information from the data unit of the LLDP message Extracting SR attribute information from the data unit of the LLDP message.
  • the memory 501 is permanent (non-transitory in English).
  • the link layer discovery protocol LLDP packet that carries the SR attribute information sent by the receiving service router SR includes:
  • the topology configuration information includes at least an SN and an SR attachment relationship
  • the acquiring topology configuration information includes:
  • the selecting an identifier of the SN from the SN list includes:
  • the identifier of the SN is selected from the SN list according to the number of SNs supported by the SR.
  • the sending the topology configuration information to the service chain control system includes:
  • the function And storing, by the function, the topology configuration information in a management component on the network device, wherein the management component includes an open interface, where the open interface is used after being invoked by the service chain control system
  • the topology configuration information stored in the management component is transmitted to the service chain control system.
  • the SR attribute information further includes any one or more of an interface type of the SR, an interface number of the SR, a number of flow tables supported by the SR, and a number of SNs supported by the SR.
  • the network device shown in FIG. 5 can perform all operations performed by the server in the embodiment corresponding to the five figures of FIGS. 4-1 to 4-5 in accordance with one or more programs.
  • the SR attribute information that is sent by the SR is received, where the SR attribute information includes at least the identifier of the SR, and the topology configuration information is obtained, where the topology configuration information includes the SR attribute information and an identifier of the SN attached to the SR;
  • the topology configuration information is sent to the service chain control system, so that the service chain control system generates the service chain network topology according to the topology configuration information.
  • the service chain control system can automatically obtain topology configuration information, and generate a service chain network topology according to the topology configuration information. Thereby, the efficiency of generating a service chain network topology is improved.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé pour envoyer des informations et un dispositif de réseau, appartenant au domaine des communications. Le procédé consiste : à recevoir des informations d'attribut de SR envoyées par un routeur de service SR, les informations d'attribut SR comprenant au moins l'identification du SR ; à obtenir des informations de configuration de topologie, les informations de configuration de topologie comprenant les informations d'attribut de SR, et l'identification des nœuds de service SN compris dans le dispositif de réseau ; et à envoyer les informations de configuration de topologie à un système de commande de chaîne de service. L'appareil comporte un module de réception, un module d'obtention et un module d'envoi. L'utilisation de la présente invention permet une amélioration de l'efficacité d'une topologie de réseau de chaîne de service.
PCT/CN2015/080992 2014-06-24 2015-06-08 Procédé d'envoi d'informations et dispositif de réseau WO2015196923A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410287382.0A CN105207909B (zh) 2014-06-24 2014-06-24 一种发送信息的方法和网络装置
CN201410287382.0 2014-06-24

Publications (1)

Publication Number Publication Date
WO2015196923A1 true WO2015196923A1 (fr) 2015-12-30

Family

ID=54936742

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/080992 WO2015196923A1 (fr) 2014-06-24 2015-06-08 Procédé d'envoi d'informations et dispositif de réseau

Country Status (2)

Country Link
CN (1) CN105207909B (fr)
WO (1) WO2015196923A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113746658A (zh) * 2020-05-30 2021-12-03 华为技术有限公司 确定网络切片拓扑的方法、设备和系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017113346A1 (fr) * 2015-12-31 2017-07-06 华为技术有限公司 Procédé de partage de charge et commutateur de service
CN107360011A (zh) * 2016-05-10 2017-11-17 中兴通讯股份有限公司 一种业务链生成方法及系统
CN108243106B (zh) 2016-12-23 2020-09-04 华为技术有限公司 控制网络切片的方法、转发设备、控制设备和通信系统
CN107786462B (zh) * 2017-10-30 2020-05-12 新华三技术有限公司 报文转发方法和装置
CN112600689A (zh) * 2020-12-01 2021-04-02 曙光信息产业(北京)有限公司 网络拓扑生成方法、装置和计算机设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621414A (zh) * 2009-08-21 2010-01-06 杭州华三通信技术有限公司 一种网络资源及拓扑的发现方法及装置
CN102137007A (zh) * 2011-01-17 2011-07-27 华为技术有限公司 网络拓扑生成方法、系统、协调者
WO2012109855A1 (fr) * 2011-07-29 2012-08-23 华为技术有限公司 Procédé et système pour obtenir des informations sur une connexion réseau en utilisant le protocole lldp

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101345655A (zh) * 2008-08-15 2009-01-14 中兴通讯股份有限公司 一种利用链路层发现协议获取网络连接信息的方法
CN102025590B (zh) * 2009-09-18 2012-07-18 中兴通讯股份有限公司 新网与互联网互通的实现方法和系统
CN101834745B (zh) * 2010-05-17 2014-08-13 中兴通讯股份有限公司 一种自动生成onu网元拓扑的方法、服务器及系统
CN106170024B (zh) * 2012-12-24 2019-12-24 华为技术有限公司 一种基于软件定义网络中数据处理的系统、方法和节点
CN103095495B (zh) * 2013-01-06 2016-05-25 华为技术有限公司 网络开局配置方法及装置、系统
CN103491129B (zh) * 2013-07-05 2017-07-14 华为技术有限公司 一种业务节点配置方法、业务节点池注册器及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621414A (zh) * 2009-08-21 2010-01-06 杭州华三通信技术有限公司 一种网络资源及拓扑的发现方法及装置
CN102137007A (zh) * 2011-01-17 2011-07-27 华为技术有限公司 网络拓扑生成方法、系统、协调者
WO2012109855A1 (fr) * 2011-07-29 2012-08-23 华为技术有限公司 Procédé et système pour obtenir des informations sur une connexion réseau en utilisant le protocole lldp

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113746658A (zh) * 2020-05-30 2021-12-03 华为技术有限公司 确定网络切片拓扑的方法、设备和系统
US11588701B2 (en) 2020-05-30 2023-02-21 Huawei Technologies Co., Ltd. Method and system for determining network slice topology, and device
CN113746658B (zh) * 2020-05-30 2023-07-11 华为技术有限公司 确定网络切片拓扑的方法、设备和系统

Also Published As

Publication number Publication date
CN105207909A (zh) 2015-12-30
CN105207909B (zh) 2019-02-12

Similar Documents

Publication Publication Date Title
US11463353B2 (en) Methods and apparatus for use in providing transport and data center segmentation in a mobile network
US20220060416A1 (en) Routing Rule Management Method and Communications Apparatus
WO2015196923A1 (fr) Procédé d'envoi d'informations et dispositif de réseau
US10791053B2 (en) Service function chain SFC-based communication method, and apparatus
US11621926B2 (en) Network device and method for sending BGP information
EP3140964B1 (fr) Implémentation d'un coeur de paquet 3g dans un ordinateur en nuage comportant des données openflow et des plans de commande
US10263808B2 (en) Deployment of virtual extensible local area network
US20210091994A1 (en) Network slicing with smart contracts
US20140241247A1 (en) Implementing a 3g packet core in a cloud computer with openflow data and control planes
US10361954B2 (en) Method and apparatus for processing modified packet
WO2018153221A1 (fr) Procédé, dispositif et système de commande de qualité de service d'entreprise dans un réseau de transmission
US11233724B2 (en) Multicast data packet processing method, and apparatus
US10581735B2 (en) Packet processing method and apparatus
WO2021174958A1 (fr) Procédé de transfert de message, dispositif, système, dispositif de réseau et support de stockage
US20190215191A1 (en) Deployment Of Virtual Extensible Local Area Network
WO2022160665A1 (fr) Procédé de transfert de paquets, procédé de traitement de paquets et dispositif
WO2021244356A1 (fr) Procédé et appareil de transmission de données
JP2016012909A (ja) 通信装置、通信方法および通信システム
WO2015070763A1 (fr) Procédé et appareil d'auto-établissement d'interface x2
WO2015180560A1 (fr) Procédé de traitement de paquets de routeur de services et nœud de services
WO2015096734A1 (fr) Procédé de transmission en liaison descendante pour des données de service, et passerelle de données de paquet
JP2022120845A5 (fr)
CN107995113B (zh) 路径建立方法及装置
CN114079583A (zh) 发送组播报文的方法、获取转发表项的方法及装置
WO2023088145A1 (fr) Procédé, appareil et dispositif de traitement de paquets

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: 15811467

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: 15811467

Country of ref document: EP

Kind code of ref document: A1