WO2012106935A1 - Procédé de configuration de réseau de communication de données, élément de passerelle, et système de communication de données - Google Patents

Procédé de configuration de réseau de communication de données, élément de passerelle, et système de communication de données Download PDF

Info

Publication number
WO2012106935A1
WO2012106935A1 PCT/CN2011/077665 CN2011077665W WO2012106935A1 WO 2012106935 A1 WO2012106935 A1 WO 2012106935A1 CN 2011077665 W CN2011077665 W CN 2011077665W WO 2012106935 A1 WO2012106935 A1 WO 2012106935A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
gateway
address
network
gateway network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2011/077665
Other languages
English (en)
Chinese (zh)
Inventor
李洪广
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
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
Priority to CN201180001453.0A priority Critical patent/CN102308523B/zh
Priority to PCT/CN2011/077665 priority patent/WO2012106935A1/fr
Publication of WO2012106935A1 publication Critical patent/WO2012106935A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses

Definitions

  • the present invention relates to the field of communication technologies, and more particularly to a data communication network configuration method, a gateway network element, and a data communication system. Background technique
  • the backhaul bearer between the mobile base station and the wireless core device is carried by the fixed network device.
  • DCN Data Communication Network
  • a DCN system network is composed of a network management server, a gateway network element and a non-gateway network element and a connection line or network between them; wherein the network management server and the gateway network element are connected and directly accessible to each other; the gateway network element A plurality of non-gateway network elements directly or indirectly connected to each other form an administrative domain, and the gateway network element and the plurality of non-gateway network elements in the management domain can directly access each other.
  • the PPP protocol is used to establish a point-to-point logical link channel, and the private network IP addresses of the same network segment are allocated on the directly connected ports, and then The point link channel obtains the routing information of the management plane through the routing protocol, and the routing information is a host route formed by the PPP link and the private network address allocated in the PPP process.
  • the routing information between the gateway NE and the non-gateway NE in the DCN management domain is used to implement DCN packet transmission.
  • the specific workflow of the DCN system includes:
  • the IP packet In the downlink direction, when the network management server sends an IP packet to the network element in the management domain, the IP packet includes the destination IP address. Because the network management server only directly contacts the gateway network element in the management domain, these purposes are The IP address is the IP address of the gateway NE. After receiving the IP packet, the gateway NE needs to determine the NE ID in the IP packet. If the NE ID in the IP packet is the NE ID of the gateway NE, the IP packet is forwarded to the upper layer. The protocol/application continues to process. If the network element ID in the IP packet is not the network element ID of the gateway network element, the IP address of the destination network element is converted according to the network element ID, and then forwarded through the management plane route.
  • the destination network element is a non-gateway network element; the non-gateway network
  • the device determines whether the IP address of the destination network element is the IP address of the network element. If yes, the non-gateway network element delivers the IP packet to the upper layer for further processing. If not, the management plane is based on the management plane. The routing information forwards the IP packet.
  • the non-gateway network element in the management domain sends an IP packet to the network management server
  • the IP packet is sent to the gateway network element according to the routing information of the management plane, and the gateway network element is configured according to the non-gateway network element.
  • the IP address information is obtained by the network element ID of the non-gateway network element, and the gateway network element adds the network element ID to the IP address information of the gateway network element, and finally adds the IP address information of the non-gateway network element to the IP address information of the gateway network element.
  • the gateway network element sends an IP packet including the network element ID of the non-gateway network element and the IP address information of the gateway network element to the network management server.
  • the inventor has found that at least the following defects exist in the prior art: Since all management messages must be analyzed by the application layer through the gateway network element, the CPU load of the gateway network element is too large, so the network element of the management domain is The number of packets is limited. The forwarding of IP packets in the management domain is not efficient. Summary of the invention
  • the embodiment of the present invention provides a DCN configuration method, a gateway network element, and a data communication network DCN to reduce the CPU load of the gateway network element.
  • An embodiment of the present invention provides a data communication network DCN configuration method, including: sending a broadcast packet carrying an IP address of a network management server to a non-gateway network element in a management domain in which it is located;
  • the network element identifier registration information Acquiring the network element identifier registration information that is sent by the non-gateway network element after receiving the broadcast packet, where the network element identifier registration information includes the network element identifier of the non-gateway network element;
  • a non-gateway network element including a public network IP address and a private network IP address for device management, generating and storing a network identifier including the non-gateway network element, a public network IP address, and a private device for device management NAT mapping table of the network IP address;
  • gateway network element including:
  • a transmitter configured to send, to the non-gateway network element in the management domain to which the gateway network element belongs, a broadcast packet carrying an IP address of the network management server;
  • the acquiring unit is configured to obtain the network element identifier registration information that is sent by the non-gateway network element after the broadcast message is received, where the network element identifier registration information includes the network element identifier of the non-gateway network element; a generating unit, configured to allocate a public network IP address and a private network IP address for device management, and generate a network element identifier including the non-gateway network element, a public network IP address, and a device management NAT mapping table of the private network IP address;
  • a memory configured to store a NAT mapping table generated by the generating unit
  • a further aspect of the present invention provides a data communication system, including a network management server, the foregoing gateway network element, and at least one non-gateway network element; the gateway network element and the at least one non-gateway network element belong to the same An administrative domain, the at least one non-gateway network element communicating with the network management server by the gateway network element.
  • the non-gateway network element when receiving the network element identifier registration information sent by the non-gateway network element, the non-gateway network element is allocated a public network IP address and a private network for device management.
  • the IP address is generated and stored in the NAT mapping table, and then the gateway network element registers the NAT mapping table in the network management server, so that when the network management server interacts with the non-gateway network element, the gateway network element only needs to be
  • the packet can be NAT-transformed, so the load of the gateway network element CPU is reduced, so that the gateway network element is no longer the performance bottleneck of the entire DCN, effectively increasing the number of network elements in the management domain, and improving management. Forwarding efficiency of packets in the domain.
  • FIG. 1 is a schematic diagram of steps of a DCN configuration method according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a NAT mapping table according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a data communication system according to an embodiment of the present invention. detailed description
  • the inventor has found through research that in the prior art, the CPU load of the gateway network element is too large because the gateway network element needs to function as an application layer gateway for managing maintenance messages, that is, the gateway network element receives management and maintenance ⁇ After the essay, the load part of the suffix must be parsed, the network element identifier is identified, and then the packet is encapsulated. In this manner, all management and maintenance messages must be sent to the CPU of the gateway network element for processing.
  • the CPU of the gateway network element needs to process the management and maintenance packets sent by the non-gateway NEs in the management domain.
  • the CPU of the gateway network element increases the load, which makes the gateway network element become the performance bottleneck of the entire DCN, resulting in the management domain.
  • the number of NEs is limited, and the forwarding efficiency of packets in the management domain is not high.
  • this embodiment provides a DCN configuration method, as shown in FIG. 1 . As shown, including the steps:
  • the gateway network element sends a broadcast packet carrying the IP address of the network management server to the non-gateway network element in the management domain.
  • the broadcast packet is used to enable the non-gateway network element in the management domain to register the network element identifier with the gateway network element.
  • the public network IP address of the gateway network element is first configured, the address of the network management server, and the routing path of the gateway network element to the network management server are obtained.
  • the gateway network element sends a broadcast packet to all non-gateway network elements in the management domain, and broadcasts the IP address information of the packet packet network management server. If the IP address information of the gateway NE is not configured in the non-gateway NE, the broadcast text should also include the IP address information of the gateway NE.
  • the gateway network element sends a broadcast packet to all the non-gateway network elements directly connected to the gateway through the PPP link; after receiving the broadcast packet, the non-gateway network element directly connected to the gateway network element sends the broadcast packet to the other The directly connected non-gateway network element forwards the broadcast message. And so on, until the broadcast arrives at all non-gateway network elements in the entire management domain.
  • the gateway network element can send the broadcast packet, so that the non-gateway network element in the management domain can obtain the IP address information of the gateway network element and the IP address information of the network management server, and then the non-gateway network element can implement the gateway network element or the network. Manage data transfer between servers.
  • the broadcast and the text can be sent through a newly defined protocol.
  • the broadcast message can also be sent by extending the standard protocol, for example, by extending the routing protocol. Send the broadcast message.
  • the information carried in the broadcast packet includes an IP address of the network management server, and may also include an IP address of the gateway network element, and a virtual local area network (VLAN) to which the gateway network element belongs.
  • logo an IP address of the network management server, and may also include an IP address of the gateway network element, and a virtual local area network (VLAN) to which the gateway network element belongs.
  • VLAN virtual local area network
  • the network element identifier registration information includes the network element identifier of the non-gateway network element.
  • the network element identifier registration information may further include a management protocol supported by the non-gateway network element (hereinafter referred to as a communication protocol) and a port for the non-gateway network element to send the network element identifier registration information (hereinafter referred to as the first port).
  • the communication protocol can be an IP based management protocol such as SNMP, NETCONF or HTTP.
  • IP based management protocol such as SNMP, NETCONF or HTTP.
  • Non-gateway network elements in the same management domain use the same communication protocol.
  • the non-gateway network element In order to enable the gateway network element to directly forward the management and maintenance messages between the non-gateway network element and the network management server, the non-gateway network element needs to send its own network element identification information to the gateway network element.
  • the network element identifier may be a character, a string, a digit, a digit string, or a numeric string stored in the device memory when the non-gateway network element device is shipped from the factory.
  • the network element identifier is a numeric string, Specifically, it may be the MAC address of the non-gateway network element device.
  • the non-gateway network element that sends the network element identifier registration information is assigned a public network IP address and a private network IP address used for device management, and generates and stores a network element identifier including the non-gateway network element, and a public network IP address. And a NAT mapping table for the private network IP address used for device management.
  • the network element identification information includes a communication protocol and/or a first port
  • the NAT mapping table may further include the communication protocol and/or the first port.
  • the gateway network element After the gateway network element receives the registration information of the network element identifier sent by the non-gateway network element, in order to enable the non-gateway network element to communicate with the network management server outside the management domain, the gateway network element first needs to assign a public network IP address to the non-gateway network element. And a private network IP address used for device management, and then, a public network address including a non-gateway network element, a private network IP address, and a NAT mapping table of the network element identifier are generated.
  • the NAT mapping table may further include a port number (hereinafter referred to as a second port number) of a port on which the gateway network element receives the network element registration information sent by the non-gateway network element.
  • a port number hereinafter referred to as a second port number
  • FIG. 2 shows a NAT mapping table composed of related information of four non-gateway network elements, and the network element identifiers of the four non-gateway network elements are NE10 and NE11, respectively.
  • the network element identifier of each non-gateway network element also corresponds to the private network of the non-gateway network element.
  • the gateway network element registers a NAT mapping table with the network management server.
  • the gateway network element After establishing the NAT mapping table of the non-gateway network element, the public network IP address, and the private network IP address, the gateway network element registers the NAT mapping table with the network management server.
  • the network management server may send a management and maintenance message of the non-gateway network element to the gateway network element according to the NAT mapping table, and the gateway network element sends the management and maintenance message to the non-gateway network element according to the NAT mapping table.
  • the network management server may obtain the public network IP address or IP address of the non-gateway network element and the first port, so that the non-gateway network element and the network management server pass the IP-based management.
  • a protocol communication protocol such as SNMP or HTTP protocol, performs packet exchange
  • the gateway network element receives a packet whose destination address is a public network IP address of a non-gateway network element, the gateway network element stores the packet according to the storage in the memory.
  • the NAT mapping table is configured to modify the destination IP address of the packet to be the private network IP address allocated by the non-gateway network element for device management, and send the modified packet to the non-gateway network element; or, the gateway network element When receiving the packet whose non-gateway network element is the private network IP address of the non-gateway network element for the device management and the destination address is the IP address of the network management server, according to the NAT mapping table stored in the memory
  • the source IP address of the packet is modified to be the public IP address of the non-gateway network element, and the modified packet is sent to the network management server.
  • the network management server When the communication protocol is included in the network element registration information, the network management server encapsulates the message sent to the non-gateway network element according to a protocol supported by the non-gateway network element.
  • the destination address of the network management server sent to the non-gateway network element is the public network IP address of the non-gateway network element, and the destination port is the first port, and the gateway is the gateway.
  • the network element modifies the destination address of the packet to the private network for device management of the non-gateway network element.
  • the modified packet is sent to the first port.
  • the gateway network element first allocates a public network address and a private network IP address for management to the non-gateway network element, and then uses the network element identification information of the non-gateway network element to manage the private network IP.
  • the NAT information mapping table is established between the address information and the public network address information, and then the gateway network element registers the NAT mapping table in the network management server, so that when the network management server exchanges packets with the non-gateway network element, the gateway network element only The NAT of the packet needs to be converted, so that the load of the gateway network element CPU is reduced, so that the gateway network element is no longer the performance bottleneck of the entire DCN, and the number of network elements in the management domain can be increased, and the management domain is improved.
  • the broadcast VLAN identifier may also include the management VLAN identifier. Specifically, if a broadcast packet carries a management The VLAN is identified. The non-gateway NE that receives the broadcast packet re-establishes a PPP connection according to the management VLAN, and performs route refresh according to the newly established PPP connection. In this embodiment, the default VLAN is replaced by the method of actively broadcasting the management VLAN. Therefore, the scenario can be used to reduce the flexibility of the system.
  • the data communication network includes a gateway network element, at least one non-gateway network element (three are shown in the figure), and a network management server, and the gateway network element and the at least one non-gateway network element belong to The same management domain, the at least one non-gateway network element communicates with the network management server by the gateway network element.
  • the gateway network element includes: a transmitter 1, an obtaining unit 2, a generating unit 3, a memory 4, and a registration unit 5.
  • a PPP connection is established on all directly connected physical links in the management domain to which the gateway network element belongs, and after each network element starts the IGP routing protocol, the sender 1 sends the management domain to which the gateway network element belongs.
  • the non-gateway network element sends a broadcast message carrying the IP address of the network management server.
  • the transmitter 1 sends the broadcast packet to all non-gateway network elements directly connected to the gateway network element in the management domain to which the gateway network element belongs.
  • the broadcast message includes the IP address of the network management server.
  • the broadcast message may further include an IP address of the gateway network element.
  • the broadcast network message is sent by the gateway network element, so that the non-gateway network element in the management domain can obtain the IP address of the gateway network element and the IP address of the network management server, thereby implementing communication with the gateway network element or the network management server.
  • the broadcast may be sent through a newly defined protocol.
  • the broadcast message may also be sent by extending the standard protocol.
  • the broadcast message may be sent by using an extended routing protocol.
  • the non-gateway network element In order to enable the packet to be forwarded between the non-gateway network element and the network management server through the gateway network element, the non-gateway network element needs to send its own network element identification information to the gateway network element.
  • the obtaining unit 2 obtains the network element identifier registration information that is sent by the non-gateway network element after receiving the broadcast message, and the network element identifier registration information includes the network element identifier of the non-gateway network element, and the network element identifier registration letter
  • the information may further include a communication protocol and a first port that the non-gateway network element communicates with the network management server.
  • the generating unit 3 is configured to allocate a public network IP address and a private network IP address for device management, and generate a network element identifier including the non-gateway network element, and a public network IP address, for the non-gateway network element that sends the network element identification information. And a NAT mapping table for the private network IP address used for device management.
  • the NAT mapping table may further include a communication protocol and/or a first port.
  • the gateway network element After the gateway network element receives the registration information of the network element identifier from the non-gateway network element, in order to enable the non-gateway network element to communicate with the network management server outside the management domain, the gateway network element first needs to assign a public network IP address to the non-gateway network element. And the private network IP address used for device management. Next, a NAT mapping table including a public network IP address of the non-gateway network element, a private network IP address for device management, and a network element identifier is established.
  • the NAT mapping table may further include a port number (ie, a second port number) of the port on which the gateway network element receives the network element registration information sent by the non-gateway network element.
  • the network element identifier registration information may be a character, a string, a digit, a digit string, or a numeric string stored in the device memory when the non-gateway network element device is shipped from the factory.
  • the specific It may be the MAC address of the non-gateway network element device.
  • the network element registration information may also be the IP address of the non-gateway network element, or the IP address plus the port number of the communication protocol; wherein the IP address of the non-gateway network element may be the private address of the non-gateway network element in the management domain.
  • the IP address of the network Specifically, the IP address of the private network can be generated when a PPP connection is established.
  • the memory 4 is configured to store a NAT mapping table generated by the generating unit.
  • the registration unit 5 is configured to register a NAT mapping table generated by the generating unit with the network management server.
  • the gateway network element establishes a NAT mapping table including the network element identifier of the non-gateway network element, the public network IP address, and the private network IP address allocated for the non-gateway network element
  • the network element registers the NAT with the network management server.
  • the mapping table in this way, after the network management server obtains the NAT mapping table, the network management server sends the IP packet header of the management maintenance message to the non-gateway network element, and the destination address is the public network IP address of the non-gateway network element.
  • the gateway network element After receiving the message, the gateway network element performs NAT translation, and replaces the public network IP address of the non-gateway network element in the IP header with the private network IP address used for non-gateway network element management, and then performs normal operation in the management domain. IP routing forwarding process.
  • the gateway network element may further include a NAT converting unit 6 configured to: when receiving the packet sent by the network management server to the non-gateway network element, according to the NAT mapping table stored in the memory, the destination IP address of the packet Modify to become the private network IP address for device management assigned by the non-gateway network element.
  • a NAT converting unit 6 configured to: when receiving the packet sent by the network management server to the non-gateway network element, according to the NAT mapping table stored in the memory, the destination IP address of the packet Modify to become the private network IP address for device management assigned by the non-gateway network element.
  • the packet is sent
  • the source IP address is modified to become the public network IP address allocated by the non-gateway network element, and the modified packet is sent to the network management server; and/or, when the non-gateway network element sends the network element identifier registration information, including the first port.
  • the destination address of the packet sent by the network management server is a non-gateway network element and the destination port number is the packet of the first port, and the destination address of the packet is modified to be the non-gateway network element.
  • the private network IP address used for device management, and the modified packet is sent to the first port.
  • the network management server in the data communication system receives and stores the NAT mapping table sent by the gateway network element, and encapsulates the packet according to the NAT mapping table, and sends the encapsulated packet to the gateway network element.
  • the packet is forwarded by the gateway network element to the corresponding non-gateway network element.
  • the non-gateway network element in the data communication system receives the broadcast packet sent by the gateway network element, and sends its own network element identifier registration information to the gateway network element, so that the gateway network element generates a NAT mapping table according to the network element identifier registration information. Receiving the packet after the gateway network element performs NAT conversion.
  • the gateway network element first allocates public network address information and a private network IP address for device management, a NAT mapping table for the non-gateway network element, and then the gateway network element registers the NAT mapping table in the network management server. Since the network management server can obtain the public network IP address of the non-gateway network element after obtaining the NAT mapping table, the non-gateway network element and the network management server pass a communication protocol such as an IP-based management protocol, such as SNMP or HTTP. When the protocol is used for packet exchange, the gateway network element only needs to perform NAT translation on the packet, thereby avoiding the need for the gateway network element to perform application layer parsing in the prior art. For example, the payload part of the packet needs to be parsed, and the packet is identified.
  • IP-based management protocol such as SNMP or HTTP

Landscapes

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

Abstract

Selon les modes de réalisation, la présente invention concerne un procédé de configuration de réseau de communication de données (DCN), un élément de passerelle, et un système de communication de données. L'élément de passerelle transmet à l'élément non passerelle dans le domaine de gestion un message de diffusion portant l'adresse IP d'un serveur de gestion de réseau; l'élément de passerelle obtient l'information de registre d'identifiants d'éléments, qui est transmis par l'élément non passerelle après la réception du message de diffusion par l'élément de non passerelle; l'élément de passerelle alloue pour l'élément non passerelle une adresse IP de réseau public et une adresse IP de réseau privé qui est utilisée pour la gestion de dispositif, génère et stocke une table de mappage de traduction d'adresses de réseau (NAT); l'élément de passerelle enregistre la table de mappage NAT sur le serveur de gestion de réseau; l'élément de passerelle permet l'échange de messages entre l'élément non passerelle et le serveur de gestion de réseau selon la table de mappage NAT. Lors de la réalisation d'une interaction de messages entre le serveur de gestion de réseau et l'élément non passerelle, l'élément de passerelle n'a qu'à effectuer une traduction d'adresses de réseau sur le message, et allège donc la charge de l'unité centrale de traitement de l'élément de passerelle, accroît efficacement le nombre d'éléments dans le domaine de gestion et améliore l'efficacité de réacheminement du message dans le domaine de gestion.
PCT/CN2011/077665 2011-07-27 2011-07-27 Procédé de configuration de réseau de communication de données, élément de passerelle, et système de communication de données Ceased WO2012106935A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180001453.0A CN102308523B (zh) 2011-07-27 2011-07-27 数据通信网络配置方法、网关网元及数据通信系统
PCT/CN2011/077665 WO2012106935A1 (fr) 2011-07-27 2011-07-27 Procédé de configuration de réseau de communication de données, élément de passerelle, et système de communication de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/077665 WO2012106935A1 (fr) 2011-07-27 2011-07-27 Procédé de configuration de réseau de communication de données, élément de passerelle, et système de communication de données

Publications (1)

Publication Number Publication Date
WO2012106935A1 true WO2012106935A1 (fr) 2012-08-16

Family

ID=45381267

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077665 Ceased WO2012106935A1 (fr) 2011-07-27 2011-07-27 Procédé de configuration de réseau de communication de données, élément de passerelle, et système de communication de données

Country Status (2)

Country Link
CN (1) CN102308523B (fr)
WO (1) WO2012106935A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190094463A (ko) * 2016-12-26 2019-08-13 후아웨이 테크놀러지 컴퍼니 리미티드 Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
CN114024939A (zh) * 2021-11-24 2022-02-08 深圳市共进电子股份有限公司 网络地址分配方法、装置及路由器

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102790811B (zh) * 2012-07-25 2015-10-14 浙江宇视科技有限公司 一种在监控网络中穿越nat设备的方法和装置
CN102857382B (zh) * 2012-09-28 2015-02-18 瑞斯康达科技发展股份有限公司 网管设备、接入汇聚设备、接入终端设备及其管理方法和系统
CN105812166B (zh) * 2014-12-30 2020-06-12 中兴通讯股份有限公司 连接实现方法及系统、网络服务器和网关网元、管理方法
CN105610619B (zh) * 2015-12-31 2019-04-16 北京格林伟迪科技股份有限公司 一种网元设备管理方法和装置
CN106936615A (zh) * 2015-12-31 2017-07-07 中兴通讯股份有限公司 一种报文处理方法及装置
CN105933142A (zh) * 2016-04-08 2016-09-07 邦彦技术股份有限公司 网元管理的方法及装置
CN107769939B (zh) * 2016-08-17 2020-03-20 华为技术有限公司 数据通信网中网元管理方法、网管、网关网元及系统
CN106656721A (zh) * 2016-11-16 2017-05-10 广州视源电子科技股份有限公司 跨vlan的服务连接方法、设备及系统
CN109787900B (zh) * 2017-11-15 2022-04-19 阿里巴巴集团控股有限公司 传输方法、装置、设备和机器可读介质
CN111917621B (zh) * 2019-05-10 2021-09-07 烽火通信科技股份有限公司 通信设备的网管服务器与网元的通信方法及系统
CN114301877B (zh) * 2021-12-28 2024-03-22 中国电信股份有限公司 自动化管理dcn的ip的方法和系统
CN115941498A (zh) * 2022-11-17 2023-04-07 华信塞姆（成都）科技有限公司 一种自动发现及访问dcn网络中网元的方法及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1741536A (zh) * 2005-09-21 2006-03-01 烽火通信科技股份有限公司 一种基于corba的浮动接口的组网方法
CN1893394A (zh) * 2005-07-05 2007-01-10 华为技术有限公司 一种穿越网络地址转换的方法
CN1918863A (zh) * 2004-02-17 2007-02-21 银河网路股份有限公司 地址解析装置、地址解析方法及采用它们的通信系统
US20070118594A1 (en) * 2005-10-20 2007-05-24 Kabushiki Kaisha Toshiba Communication system
CN101083594A (zh) * 2006-05-31 2007-12-05 西门子通信技术（北京）有限公司 一种网络设备的管理方法及装置
CN102035661A (zh) * 2009-09-24 2011-04-27 中兴通讯股份有限公司 光网络单元的管理方法、装置、和系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1918863A (zh) * 2004-02-17 2007-02-21 银河网路股份有限公司 地址解析装置、地址解析方法及采用它们的通信系统
CN1893394A (zh) * 2005-07-05 2007-01-10 华为技术有限公司 一种穿越网络地址转换的方法
CN1741536A (zh) * 2005-09-21 2006-03-01 烽火通信科技股份有限公司 一种基于corba的浮动接口的组网方法
US20070118594A1 (en) * 2005-10-20 2007-05-24 Kabushiki Kaisha Toshiba Communication system
CN101083594A (zh) * 2006-05-31 2007-12-05 西门子通信技术（北京）有限公司 一种网络设备的管理方法及装置
CN102035661A (zh) * 2009-09-24 2011-04-27 中兴通讯股份有限公司 光网络单元的管理方法、装置、和系统

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190094463A (ko) * 2016-12-26 2019-08-13 후아웨이 테크놀러지 컴퍼니 리미티드 Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
US20190319829A1 (en) * 2016-12-26 2019-10-17 Huawei Technologies Co., Ltd. Dcn packet processing method, network device, and network system
KR102342286B1 (ko) 2016-12-26 2021-12-22 후아웨이 테크놀러지 컴퍼니 리미티드 Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
US11894970B2 (en) * 2016-12-26 2024-02-06 Huawei Technologies Co., Ltd. DCN packet processing method, network device, and network system
CN114024939A (zh) * 2021-11-24 2022-02-08 深圳市共进电子股份有限公司 网络地址分配方法、装置及路由器

Also Published As

Publication number Publication date
CN102308523B (zh) 2014-07-16
CN102308523A (zh) 2012-01-04

Similar Documents

Publication Publication Date Title
WO2012106935A1 (fr) Procédé de configuration de réseau de communication de données, élément de passerelle, et système de communication de données
EP2489172B1 (fr) Couche virtuelle 2 et mécanisme pour la rendre évolutive
CN102882699B (zh) 边缘节点的分配方法和装置及边缘节点控制器
CN102577255B (zh) 云计算中企业的第2层无缝站点扩展
WO2011032472A1 (fr) Procédé et système d'implémentation de réseau privé virtuel
US9705706B2 (en) Multiple prefix connections with translated virtual local area network
WO2011032473A1 (fr) Procédé et système d'implémentation de réseau privé virtuel
WO2012106919A1 (fr) Procédé de commande de routage, appareil et système de réseau privé virtuel de couche 3
WO2011069399A1 (fr) Procédé de mappage d'adresse et nœud de service d'accès
CN104365066B (zh) 用于以太虚拟专用网的方法和设备
US9641433B2 (en) Method, routing bridge, and system for sending packet
KR101381701B1 (ko) 데이터 메시지 처리 방법, 시스템 및 접속 서비스 노드
WO2012155867A1 (fr) Procédé d'envoi de paquet et contrôleur d'accès
CN102025600B (zh) 一种数据传输、接收的方法及系统及路由器
CN102959906B (zh) 多归属站点内主机的路由选择方法和装置
WO2011032447A1 (fr) Procédé, système et terminal de communication permettant d'implémenter une intercommunication entre un nouveau réseau et internet
EP4383656A1 (fr) Procédé et dispositif de transmission de réseau
CN101499951A (zh) 隧道配置方法、虚拟接入节点、虚拟边缘节点以及系统
CN108206783A (zh) 一种软件定义网络系统中地址配置方法及其装置
CN118202623A (zh) 网络中的云边缘转发
CN102291305A (zh) 实现6to4中继路由的方法和设备以及报文转发方法
WO2011044807A1 (fr) Procédé de communication et d'enregistrement de communication anonyme et système émetteur-récepteur de message de données
WO2014063606A1 (fr) Procédé de transmission de paquets, et dispositif correspondant
CN100479457C (zh) 一种实现虚拟私有网络中数据传输的方法
CN101841481B (zh) 虚拟专用网络路由转发实例的实现方法及装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001453.0

Country of ref document: CN

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

Ref document number: 11858421

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

Country of ref document: EP

Kind code of ref document: A1