WO2015161736A1 - 一种指示组播转发表项的方法及设备 - Google Patents
一种指示组播转发表项的方法及设备 Download PDFInfo
- Publication number
- WO2015161736A1 WO2015161736A1 PCT/CN2015/075786 CN2015075786W WO2015161736A1 WO 2015161736 A1 WO2015161736 A1 WO 2015161736A1 CN 2015075786 W CN2015075786 W CN 2015075786W WO 2015161736 A1 WO2015161736 A1 WO 2015161736A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- multicast
- identifier
- port
- access
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1854—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with non-centralised forwarding system, e.g. chaincast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
-
- 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/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
Definitions
- the present invention relates to the field of computer network technologies, and in particular, to a method and a device for indicating a multicast forwarding entry.
- FIG. 1 is a schematic diagram of a typical scenario of an access network in the prior art.
- each network node (Node) on the multicast path must support an Internet Group Management Protocol (IGMP)/
- IGMP Internet Group Management Protocol
- MLD multicast listener discovery
- Node2 parses the IGMP/MLD message to obtain the multicast IP address, and obtains the multicast MAC address.
- the mapping between the port that receives the IGMP/MLD message and the multicast MAC address is set up to generate a multicast forwarding entry consisting of the port and the multicast MAC address. Only after each node generates its own multicast forwarding entry in the process of transmitting IGMP/MLD messages, each node can identify its own multicast data packet and continue to use the port recorded by the multicast forwarding entry. The next node sends a multicast packet to complete data multicast.
- the nodes in the multicast path may not be able to correctly parse the IGMP/MLD messages and generate multicast forwarding entries.
- engineers and technicians usually need to introduce network nodes (such as Digital Subscriber Line Multiplexer (DSLAM), Optical Network Unit (ONU), Optical Line Termination (OLT). ), Ethernet switch, Broadband Network Gateway (BNG) / Broadband Access Server (Broadband Remote Access Server, BRAS, etc.)
- DSLAM Digital Subscriber Line Multiplexer
- ONU Optical Network Unit
- OLT Optical Line Termination
- Ethernet switch such as Ethernet switch, Broadband Network Gateway (BNG) / Broadband Access Server (Broadband Remote Access Server, BRAS, etc.)
- BNG Broadband Network Gateway
- BRAS Broadband Remote Access Server
- each network node can obtain a multicast forwarding entry when the IGMP/MLD protocol versions of the network nodes are different.
- the embodiment of the invention provides a method and a device for indicating a multicast forwarding entry, which are used to solve the problem that the network node does not obtain the multicast forwarding entry in the network.
- an embodiment of the present invention provides a method for indicating a multicast forwarding entry, including:
- the access loop identifier is an access loop identifier of the first node
- Determining an identifier of the first port of the second node and a identifier of the second port of the third node on the multicast path corresponding to the access loop identifier including:
- the access loop of the first node that is sent by the server identifies the identifier of the first port of the second node and the identifier of the second port of the third node in the corresponding multicast path.
- the access loop identifier includes an access loop identifier of the first node, an access loop identifier of the second node, and an access ring of the third node. a path identifier, where the second node and the third node are both on a multicast path corresponding to an access loop identifier of the first node;
- Determining an identifier of the first port of the second node and a identifier of the second port of the third node on the multicast path corresponding to the access loop identifier including:
- determining, according to the multicast internet protocol IP address in the multicast control message, the multicast media access control MAC address corresponding to the multicast path including:
- the multicast MAC address corresponding to the multicast path is determined according to the multicast IP address in the multicast control message and the mapping relationship between the predetermined multicast IP address and the multicast MAC address.
- the multicast control message is an Internet Group Management Protocol (IGMP) message or a multicast listener discovery protocol (MLD) message.
- IGMP Internet Group Management Protocol
- MLD multicast listener discovery protocol
- the method further includes:
- the protocol packet is sent to the fourth node.
- any one of the first to the fourth possible implementation manners of the first aspect in a sixth possible implementation manner, the receiving, by the first node, the multicast control message Into the loop logo, including:
- the second aspect is a device for indicating a multicast forwarding entry, including:
- a first receiving unit configured to receive a multicast control message sent by the first node and an access loop identifier
- a first determining unit configured to determine an identifier of a first port of the second node and a second port of the third node on the multicast path corresponding to the access loop identifier, the first port and the The second port is an egress port on the multicast path;
- a second determining unit configured to determine, according to the multicast internet protocol IP address in the multicast control message, a multicast media access control MAC address corresponding to the multicast path;
- a first sending unit configured to send a first forwarding entry to the second node, where a destination address of the first forwarding entry is the multicast MAC address, and an outbound port information of the first forwarding entry is The identifier of the first port;
- a second sending unit configured to send a second forwarding entry to the third node, where a destination address of the second forwarding entry is the multicast MAC address, and an outbound port information of the second forwarding entry is The identifier of the second port.
- the access loop identifier received by the first receiving unit is an access loop identifier of the first node
- the first determining unit is specifically configured to:
- the multicast path corresponding to the loop identifier determines the access loop of the first node Identifying an identifier of the first port of the second node on the corresponding multicast path and an identifier of the second port of the third node; or
- the access loop of the first node that is sent by the server identifies the identifier of the first port of the second node and the identifier of the second port of the third node in the corresponding multicast path.
- the access loop identifier received by the first receiving unit includes an access loop identifier of the first node, an access loop identifier of the second node, and a An access loop identifier of the three nodes, where the second node and the third node are both on the multicast path corresponding to the access loop identifier of the first node;
- the first determining unit is specifically configured to:
- the second determining unit is specifically configured to:
- the multicast MAC address corresponding to the multicast path is determined according to the multicast IP address in the multicast control message and the mapping relationship between the predetermined multicast IP address and the multicast MAC address.
- the multicast control message received by the first receiving unit is an Internet Group Management Protocol (IGMP) message or a multicast listener discovery protocol (MLD) message.
- IGMP Internet Group Management Protocol
- MLD multicast listener discovery protocol
- the device further includes:
- a third sending unit configured to send the IGMP message or the MLD message to the fourth node;
- the first receiving unit is specifically configured to:
- the multicast control message sent by the first node and the access loop identifier are received; the identifier of the first port of the second node on the multicast path corresponding to the access loop identifier is determined, and the third An identifier of the second port of the node, where the first port and the second port are both egress ports on the multicast path; and determining, according to the multicast internet protocol IP address in the multicast control message, a multicast media access control MAC address corresponding to the multicast path; sending a first forwarding entry to the second node, where the destination address of the first forwarding entry is the multicast MAC address, the first forwarding The outbound port information of the published item is the identifier of the first port, and the second forwarding entry is sent to the third node, where the destination address of the second forwarding entry is the multicast MAC address, and the second The outbound port information of the forwarding entry is the identifier of the second port.
- the multicast forwarding entry is generated for each network node
- FIG. 1 is a schematic diagram of a typical scenario of an access network in the prior art
- FIG. 2 is a schematic diagram of an access network scenario according to an embodiment of the present invention.
- FIG. 3 is a schematic flowchart of a method for indicating a multicast forwarding entry according to an embodiment of the present invention
- FIG. 4 is a schematic flowchart of a method for indicating a multicast forwarding entry according to another embodiment of the present invention.
- FIG. 5 is a message flow diagram provided by an embodiment of the present invention.
- FIG. 6 is a schematic flow chart of a specific embodiment 1 of the present invention.
- FIG. 7 is a schematic flow chart of a second embodiment of the present invention.
- FIG. 8 is a schematic structural diagram of a device according to an embodiment of the present invention.
- FIG. 9 is another schematic structural diagram of an apparatus according to an embodiment of the present invention.
- the embodiment of the invention provides a method and a device for indicating a multicast forwarding entry, which can be used to obtain a multicast forwarding entry for each network node without parsing the IGMP message or the MLD message.
- FIG. 2 is a schematic diagram of a novel access network scenario according to an embodiment of the present invention.
- the control plane functions of the network node including IGMP/MLD listening/proxy are centralized to the Access Controller.
- Each network node passes the Openflow protocol, access management or control (such as the Optical Network Unit Management and Control Interface (OMCI) or Ethernet Operation, Administration, and Maintenance (Eth OAM).
- OMCI Optical Network Unit Management and Control Interface
- Eth OAM Ethernet Operation, Administration, and Maintenance
- the protocol, or tunneling protocol is connected to the access controller.
- the access controller can be a standalone device or embedded in an OLT, a sink node, or a router (such as BNG/BRAS) as a functional module.
- a method for indicating a multicast forwarding entry includes:
- S310 Receive a multicast control message sent by the first node and an access loop identifier.
- S320 Determine an identifier of a first port of the second node and a second port of the third node on the multicast path corresponding to the access loop identifier, where the first port and the second port are both An outbound port on the multicast path;
- S330 Determine the group according to the multicast internet protocol IP address in the multicast control message. Multicast media access control MAC address corresponding to the broadcast path;
- S340 Send a first forwarding entry to the second node, where the destination address of the first forwarding entry is the multicast MAC address, and the outbound port information of the first forwarding entry is the first port Identification
- S350 Send a second forwarding entry to the third node, where a destination address of the second forwarding entry is the multicast MAC address, and an outbound port information of the second forwarding entry is the second port Logo.
- a multicast forwarding entry is generated by using a separate controller device to generate a multicast forwarding entry for the second node and the third node on the multicast path according to the message from the first node, so that the second node and the third node do not need to receive the local forwarding entry.
- the IGMP message or the MLD message of the previous node of the node is parsed, and the multicast forwarding entry of the node is also obtained.
- the IGMP or MLD version of the first node, the second node, and the third node are not.
- the second node and the third node cannot parse the IGMP or MLD messages to establish the respective multicast forwarding entries.
- the method for indicating a multicast forwarding entry is a scenario in which a plurality of network nodes exist in a network, and even a scenario in which a multicast path spans a network management domain of a controller device exists. As shown in Figure 4, it includes:
- S410 Receive a multicast control message and an access loop identifier sent by an edge node of the network management domain, where the multicast control message is an Internet Group Management Protocol (IGMP) message or a multicast listener discovery protocol (MLD) message;
- IGMP Internet Group Management Protocol
- MLD multicast listener discovery protocol
- S420 Determine, according to the access loop identifier, the port information of each network node in the multicast path corresponding to the access loop identifier, and the multicast internet protocol according to the IGMP message or the MLD message. (Internet Protocol, IP) address, determining a multicast media access control (MAC) address corresponding to the multicast path;
- IP Internet Protocol
- S430 Send, to each network node on the multicast path, the port information of the network node and the multicast MAC address to a multicast forwarding entry corresponding to the network node.
- the edge node is an ingress network node or an egress network node in the current network management domain.
- the ingress network node or the outbound multicast path in the network management domain is usually a network node; the network node may be a Customer Premises Equipment (CPE), an AN (such as an ONU/DSLAM/OLT), or a sink node, or a router (such as a BNG/BRAS), the multicast Control messages include IGMP/MLD and access line identification (Line ID).
- CPE Customer Premises Equipment
- AN such as an ONU/DSLAM/OLT
- a sink node such as a BNG/BRAS
- the multicast Control messages include IGMP/MLD and access line identification (Line ID).
- the access loop identifier is an access loop identifier of the edge node, and in step S420, determining, according to the access loop identifier, a multicast path corresponding to the access loop identifier Port information of each network node, including:
- mapping relationship between the pre-stored access ring identifier and the port information of each network node according to the access loop identifier of the edge node, and the access loop of the edge node determined according to the pre-stored network topology relationship Identifying a corresponding multicast path, and determining port information of each network node on the multicast path corresponding to the access loop identifier of the edge node; or
- the access loop of the edge node that is fed back identifies the port information of each network node on the corresponding multicast path.
- a separate server can be set, and the access controller can query the server for the port information of each network node on the multicast path corresponding to the access loop identifier, or the access controller can preset the access loop.
- the mapping relationship between the ports of each network node and the network topology relationship is identified, and the access controller queries the mapping relationship and the network topology relationship to obtain the port information of each network node.
- the access loop identifier is an identifier widely used in various network systems.
- DSL Digital Subscriber Line
- ETH Ethernet
- the format of the access loop identifier is as follows: :
- the access loop identifier is Access-Node-Identifier atm slot/port:vpi.vci; when the AN accesses the ETH-based DSL/ETH
- the format of the access loop identifier is Access-Node-Identifier eth slot/port[:vlan-id].
- the access-Node-Identifier is the identifier of the AN; the slot/port is the chassis number, the rack number, the frame number, the slot number, and the sub-slot on the AN. One of -slot), port number, etc. Or a combination of multiple, the specific content is related to the site layout of the device; vpi.vci is the virtual path identifier and virtual channel identifier on the DSL line; "[]" in the format indicates optional.
- the access loop identifier For a Passive Optical Network (PON) system, the access loop identifier has two format options, as follows:
- Option 1 is the access loop identifier that contains only the ONU port information.
- the format is as follows: when the ONU accesses the ATM-based DSL line, it is ONUID atm slot2/port2:vpi.vci; when the ONU accesses the ETH-based DSL line, For ONUID eth slot2/port2[:vlan-id].
- the vlan-id is a C-VLAN ID (Customer VLAN ID), which is used to identify a user or an access line, and is usually added or deleted by the ONU.
- Option 2 is the access loop identifier that contains both the ONU port information and the OLT port information.
- the format is as follows: When the ONU accesses the ATM-based DSL line, the access-Node-Identifier atm slot1/port1/ONUID/slot2/port2 :vpi.vci; When the ONU accesses the ETH-based DSL/ETH line, it is Access-Node-Identifier eth slot1/port1/ONUID/slot2/port2[:vlan-id].
- the access-Node-Identifier is the identifier of the OLT; the slot1/port1 is the chassis number, the rack number, the frame number, the slot number, and the sub-slot of the OLT.
- slot2/port2 is the chassis number, rack number, and frame on the ONU.
- the access loop identifier reported by the network node includes port information, and according to the access loop identifier reported by the network node, the nodes of the multicast path and their port information can also be determined.
- the access loop identifier is an access loop identifier of each network node on the multicast path; and in step S420, determining, according to the access loop identifier, the access loop identifier Port information of each network node on the corresponding multicast path, including:
- IGMP/MLD IGMP/MLD
- the message is still transmitted on the multicast path.
- the network nodes on the multicast path do not resolve the IGMP/MLD message. Instead, the ICMP/MLD message is inserted into the message before the IGMP/MLD message is forwarded.
- the edge node reports the IGMP/MLD message and the access loop identifier of each node to the access controller.
- the access controller parses the IGMP/MLD message, and obtains the port information in the access loop identifier, and indicates the multicast forwarding entry corresponding to the network node of each network node.
- step S420 determining, according to the multicast internet protocol IP address in the multicast control message, the multicast media access control MAC address corresponding to the multicast path, including:
- the multicast MAC address corresponding to the multicast path is determined according to the multicast IP address in the multicast control message and the mapping relationship between the predetermined multicast IP address and the multicast MAC address.
- the method further includes: sending the IGMP message or the MLD message to other edge nodes other than the edge node; or
- the access controller passes the IGMP/MLD message through Openflow, access management or control protocol (such as OMCI). Or ETH OAM) or tunnel to the other edge nodes; when the other edge node is a router (such as BNG/BRAS), the access controller will generate a multicast routing protocol (such as protocol independent multicast (Protocol Independent) Multicast, PIM)/Source-Specific Multicast (SSM) messages are forwarded to the other edge nodes that are routers through the Openflow protocol, access management or control protocol or tunneling protocol.
- the other edge node continues to transmit the message.
- the message flow diagram of the foregoing embodiment is shown in FIG. 5.
- the access controller receives an IGMP/MLD message sent by an edge node that is an ingress network node, and sends a multicast forwarding entry to each network node, and serves as an egress network node.
- the edge node sends an IGMP/MLD message.
- a specific embodiment 1 of the present invention includes the following steps:
- S620 The Remote AN sends the IGMP/MLD packet and the Line ID to the access controller by extending the openflow message.
- the access controller sends an AAA message to the AAA (Authentication, Authorisation, Accounting, abbreviated) server, where the message carries a Line ID, which is used to query port information.
- AAA Authentication, Authorisation, Accounting, abbreviated
- the AAA server obtains port information corresponding to each network node according to the Line ID.
- the AAA server sends an AAA message to the access controller, where the message carries the line ID corresponding to the port information of each network node.
- the access controller obtains a multicast IP address according to the IGMP/MLD, and forms a membership entry of each group according to the port information and the multicast IP address, and maps the multicast IP address to the multicast MAC address, further forming corresponding Level multicast forwarding entry;
- S680 Send, by using an openflow message, a corresponding multicast forwarding entry to each network node.
- the line ID carried in the openflow message in the step S620 can be Option1
- Port information is
- a specific embodiment 2 of the present invention includes the following steps:
- S710 The user sends an IGMP/MLD message to the ONU.
- S720 The ONU sends the IGMP/MLD packet and the line ID 1 (port information of the ONU) to the OLT by extending the openflow message.
- the OLT sends the IGMP/MLD packet, the line ID 2 (the port information of the ONU, and the port information of the OLT) to the access controller by extending the openflow message.
- the access controller obtains a multicast IP address according to the IGMP/MLD, and forms a membership entry of each group according to the port information and the multicast IP address, and maps the multicast IP address to the multicast MAC address to further form corresponding Level multicast forwarding entry;
- S750 Configure a corresponding multicast forwarding entry on each network node by using the openflow protocol.
- S760 Send, by using an openflow message, a corresponding multicast forwarding entry to each network node.
- the device 80 for indicating a multicast forwarding entry provided by the embodiment of the present invention includes:
- the first receiving unit 810 is configured to receive a multicast control message sent by the first node and an access loop identifier.
- the first determining unit 820 is configured to determine an identifier of the first port of the second node and a second port of the third node on the multicast path corresponding to the access loop identifier, where the first port and the The second port is an outgoing port on the multicast path;
- a second determining unit 830 configured to determine, according to the multicast internet protocol IP address in the multicast control message, a multicast media access control MAC address corresponding to the multicast path;
- the first sending unit 840 is configured to send a first forwarding entry to the second node, where the destination address of the first forwarding entry is the multicast MAC address, and the outbound port information of the first forwarding entry The identifier of the first port;
- a second sending unit 850 configured to send a second forwarding entry to the third node, where a destination address of the second forwarding entry is the multicast MAC address, and an outbound port information of the second forwarding entry Is the identifier of the second port.
- the access loop identifier received by the first receiving unit 810 is an access loop identifier of the first node
- the first determining unit 820 is specifically configured to:
- the access loop of the first node that is sent by the server identifies the identifier of the first port of the second node and the identifier of the second port of the third node in the corresponding multicast path.
- the access loop identifier received by the first receiving unit 810 includes an access loop identifier of the first node, an access loop identifier of the second node, and an access loop identifier of the third node, where The second node and the third node are both on the multicast path corresponding to the access loop identifier of the first node;
- the first determining unit 820 is specifically configured to:
- the second determining unit 830 is specifically configured to:
- the multicast MAC address corresponding to the multicast path is determined according to the multicast IP address in the multicast control message and the mapping relationship between the predetermined multicast IP address and the multicast MAC address.
- the multicast control message received by the first receiving unit 810 is an Internet Group Management Protocol (IGMP) message or a Multicast Listener Discovery Protocol (MLD) message.
- IGMP Internet Group Management Protocol
- MLD Multicast Listener Discovery Protocol
- the device 80 further includes:
- a third sending unit configured to send the IGMP message or the MLD message to the fourth node;
- first receiving unit 810 is specifically configured to:
- the device 90 for indicating a multicast forwarding entry provided by the embodiment of the present invention includes:
- the processor 910, the memory 920 and the communication interface 930; the processor 910, the memory 920 and the communication interface 930 are connected to each other by a bus or the like.
- the memory 920 is configured to store a program.
- the program can include program code, the program code including computer operating instructions.
- the memory may include a high speed random access memory (RAM) memory, and may also include a non-volatile memory such as at least one disk memory.
- the communication interface 930 is for communicating with various nodes.
- the processor 910 executes the program stored in the memory 920, and may execute S310-S350 in the embodiment corresponding to FIG. 3.
- the S410-S430 in the embodiment corresponding to FIG. 4 may be executed, and the corresponding to FIG. 5-7 may be performed. All operations of the access controller in the embodiment may display all functions of the device 80 of the multicast forwarding entry.
- the above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP for short), and the like; or a digital signal processor (DSP) or an application specific integrated circuit ( ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
- CPU central processing unit
- NP Network Processor
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA off-the-shelf programmable gate array
- control plane function of the network node is centralized on the access controller side, and the network node is simplified as a programmable forwarding device, and the network node does not need to support the IGMP/MLD listening/proxy. Decoupling the network node from the multicast service, the network node does not need to consider the compatibility matching problem with the terminal and the multicast router, which greatly reduces the operation and maintenance complexity and management cost.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
- the present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It should be understood that the flow chart can be implemented by computer program instructions And/or a combination of the processes and/or blocks in the block diagrams, and the flowcharts and/or blocks in the flowcharts. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明实施例提供了一种指示组播转发表项的方法及设备,用于避免统一网络节点的IGMP/MLD协议版本,降低运维复杂度。该方法包括:接收第一节点发送的组播控制消息以及接入环路标识;确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识;根据所述组播控制消息中的组播IP地址,确定组播MAC地址;向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识。
Description
本申请要求于2014年4月24日提交中国专利局、申请号为CN 201410169740.8、发明名称为“一种指示组播转发表项的方法及设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本发明涉及计算机网络技术领域,尤其涉及一种指示组播转发表项的方法及设备。
图1为现有技术中接入网典型场景示意图,如图1中箭头所示,组播路径上的每个网络节点(Node)都必须支持因特网组管理协议(Internet Group Management Protocol,IGMP)/组播监听者发现协议(multicast listener discovery,MLD)的侦听/代理功能,才能完成IGMP/MLD消息在组播路径上的传输,并各自生成对应的组播转发表项。
例如,图1中Node1和Node2的IGMP/MLD版本相同时,Node2接收到Node1转发的IGMP/MLD消息后,解析IGMP/MLD消息获取组播IP地址,也就获取到组播MAC地址,进而,建立接收IGMP/MLD消息的端口与组播MAC地址的对应关系,即生成由端口与组播MAC地址组成的组播转发表项。仅仅当各个节点在传输IGMP/MLD消息的过程中生成各自的组播转发表项后,各个节点才能够在后续识别出自己的组播数据包,并通过组播转发表项记录的端口继续向下一节点发送组播数据包,完成数据组播。而如果IGMP/MLD版本不同,组播路径的各个节点不一定都能正确解析IGMP/MLD消息,生成组播转发表项,组播也就无法实现。为此,工程技术人员通常需要在引入网络节点(如数字用户线接入复用器(DSL Access Multiplexer,DSLAM),光网络单元(Optical Network Unit,ONU),光路终结点(Optical Line Termination,OLT),以太网交换机,宽带网络网关(Broadband Network Gateway,BNG)/宽带接入服务器
(Broadband Remote Access Server,BRAS)等)时考虑各个网络节点的IGMP/MLD版本问题,对接入网进行大量的兼容匹配工作,显然,这种方式增加了运维复杂度。
现有技术还没有提出一种简便的解决方案,能够实现在各个网络节点的IGMP/MLD协议版本不同时,各个网络节点能够获取组播转发表项。
发明内容
本发明实施例提供了一种指示组播转发表项的方法及设备,用于解决现有技术中网络节点的IGMP/MLD协议版本不同,导致各个网络节点无法获取组播转发表项的问题。
第一方面,本发明实施例提供了一种指示组播转发表项的方法,包括:
接收第一节点发送的组播控制消息以及接入环路标识;
确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,所述第一端口和所述第二端口均为所述组播路径上的出端口;
根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址;
向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;
向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识。
结合第一方面,在第一种可能的实现方式中,所述接入环路标识为所述第一节点的接入环路标识;
确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,包括:
根据所述第一节点的接入环路标识,预先存储的接入环路标识与各个网络节点的端口信息的映射关系,以及根据预先存储的网络拓扑关系确定的所
述第一节点的接入环路标识对应的组播路径,确定所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识;或者,
将所述第一节点的接入环路标识发送给服务器,所述服务器中预先存储了接入环路标识与各个网络节点的端口信息的映射关系,以及预先存储了网络拓扑关系;接收所述服务器反馈的所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
结合第一方面,在第二种可能的实现方式中,所述接入环路标识包括第一节点的接入环路标识、第二节点的接入环路标识和第三节点的接入环路标识,所述第二节点和所述第三节点均在所述第一节点的接入环路标识对应的组播路径上;
确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,包括:
根据所述组播路径上的第二节点的接入环路标识和第三节点的接入环路标识,分别获取所述组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
结合第一方面,在第三种可能的实现方式中,根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址,包括:
根据所述组播控制消息中的组播IP地址,以及预先确定的组播IP地址与组播MAC地址的映射关系,确定所述组播路径对应的组播MAC地址。
结合第一方面,在第四种可能的实现方式中,所述组播控制消息为因特网组管理协议IGMP报文或组播监听者发现协议MLD报文。
结合第一方面,第一方面的第一种至第四种可能的实现方式中的任一种,在第五种可能的实现方式中,所述方法还包括:
将所述IGMP报文或MLD报文发送给第四节点;或者,
根据所述IGMP报文或MLD报文生成组播路由协议报文,将所述组播路由
协议报文发送给第四节点。
结合第一方面,第一方面的第一种至第四种可能的实现方式中的任一种,在第六种可能的实现方式中,所述接收第一节点发送的组播控制消息以及接入环路标识,包括:
接收第一节点根据openflow协议,或者接入管理或控制协议,或者以太网操作、管理和维护协议,或者隧道协议发送的组播控制消息以及接入环路标识。
第二方面,一种指示组播转发表项的设备,包括:
第一接收单元,用于接收第一节点发送的组播控制消息以及接入环路标识;
第一确定单元,用于确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,所述第一端口和所述第二端口均为所述组播路径上的出端口;
第二确定单元,用于根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址;
第一发送单元,用于向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;
第二发送单元,用于向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识。
结合第二方面,在第一种可能的实现方式中,所述第一接收单元接收的接入环路标识为所述第一节点的接入环路标识;
所述第一确定单元,具体用于:
根据所述第一节点的接入环路标识,预先存储的接入环路标识与各个网络节点的端口信息的映射关系,以及根据预先存储的网络拓扑关系确定的所述第一节点的接入环路标识对应的组播路径,确定所述第一节点的接入环路
标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识;或者,
将所述第一节点的接入环路标识发送给服务器,所述服务器中预先存储了接入环路标识与各个网络节点的端口信息的映射关系,以及预先存储了网络拓扑关系;接收所述服务器反馈的所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
结合第二方面,在第二种可能的实现方式中,所述第一接收单元接收的接入环路标识包括第一节点的接入环路标识、第二节点的接入环路标识和第三节点的接入环路标识,所述第二节点和所述第三节点均在所述第一节点的接入环路标识对应的组播路径上;
所述第一确定单元,具体用于:
根据所述组播路径上的第二节点的接入环路标识和第三节点的接入环路标识,分别获取所述组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
结合第二方面,在第三种可能的实现方式中,所述第二确定单元,具体用于:
根据所述组播控制消息中的组播IP地址,以及预先确定的组播IP地址与组播MAC地址的映射关系,确定所述组播路径对应的组播MAC地址。
结合第二方面,在第四种可能的实现方式中,所述第一接收单元接收的组播控制消息为因特网组管理协议IGMP报文或组播监听者发现协议MLD报文。
结合第二方面,第二方面的第一种至第四种可能的实现方式中的任一种,在第五种可能的实现方式中,所述设备还包括:
第三发送单元,用于将所述IGMP报文或MLD报文发送给第四节点;或者,
根据所述IGMP报文或MLD报文生成组播路由协议报文,将所述组播路由协议报文发送给第四节点。
结合第二方面,第二方面的第一种至第四种可能的实现方式中的任一种,
在第六种可能的实现方式中,所述第一接收单元具体用于:
接收第一节点根据openflow协议,或者接入管理或控制协议,或者以太网操作、管理和维护协议,或者隧道协议发送的组播控制消息以及接入环路标识。
本发明实施例中,接收第一节点发送的组播控制消息以及接入环路标识;确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,所述第一端口和所述第二端口均为所述组播路径上的出端口;根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址;向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识;通过使用一个单独的设备为组播路径上各个网络节点生成组播转发表项,使得各个网络节点无需对IGMP报文或MLD报文进行解析,也能够获取到组播转发表项。
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作一简单地介绍,显而易见地,下面描述中的附图是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1是现有技术中接入网典型场景示意图;
图2是本发明实施例提供的接入网场景示意图;
图3是本发明实施例提供的指示组播转发表项的方法的流程示意图;
图4是本发明另一实施例提供的指示组播转发表项的方法的流程示意图;
图5是本发明实施例提供的消息流图;
图6是本发明具体实施例一的流程示意图;
图7是本发明具体实施例二的流程示意图;
图8是本发明实施例提供的设备的结构示意图;
图9是本发明实施例提供的设备的另一结构示意图。
为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本发明保护的范围。
本发明实施例提供了一种指示组播转发表项的方法及设备,用于使得各个网络节点无需对IGMP报文或MLD报文进行解析,也能够获取到组播转发表项。
参见图2,是本发明实施例提供的新型接入网场景示意图。网络节点的包括IGMP/MLD的侦听/代理在内的控制面功能集中到接入控制器(Access Controller)实现。各个网络节点通过Openflow协议、接入管理或控制(如光网络单元管理和控制接口(ONU Management and Control Interface,OMCI)或以太网操作、管理和维护(Ethernet Operation,Administration,and Maintenance,Eth OAM))协议、或隧道协议连接到接入控制器。接入控制器可以为独立设备,也可以内嵌于OLT、汇聚节点、或路由器(如BNG/BRAS)等设备中作为一个功能模块。
参见图3,本发明实施例提供的指示组播转发表项的方法包括:
S310:接收第一节点发送的组播控制消息以及接入环路标识;
S320:确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,所述第一端口和所述第二端口均为所述组播路径上的出端口;
S330:根据所述组播控制消息中的组播互联网协议IP地址,确定所述组
播路径对应的组播媒体接入控制MAC地址;
S340:向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;
S350:向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识。
本发明实施例,通过使用单独的控制器设备根据来自第一节点的消息为组播路径上第二节点、第三节点生成组播转发表项,使得第二节点、第三节点无需接收来自本节点的上一节点的IGMP报文或MLD报文并进行解析,也能够获取到本节点的组播转发表项,避免了第一节点、第二节点、第三节点的IGMP或MLD协议版本不同时,第二节点、第三节点无法解析IGMP或MLD消息以建立各自的组播转发表项的问题。
进一步地,结合图3所示流程,对于网络中存在多个网络节点,甚至存在组播路径跨越了控制器设备的网络管理域的场景,本发明实施例提供的指示组播转发表项的方法如图4所示,包括:
S410:接收网络管理域的边缘节点发送的组播控制消息以及接入环路标识,所述组播控制消息为因特网组管理协议IGMP报文或组播监听者发现协议MLD报文;
S420:根据所述接入环路标识,分别确定所述接入环路标识对应的组播路径上各个网络节点的端口信息,以及根据所述IGMP报文或MLD报文中的组播互联网协议(Internet Protocol,IP)地址,确定所述组播路径对应的组播媒体接入控制(Media Access Control,MAC)地址;
S430:针对组播路径上的每个网络节点,将该网络节点的端口信息和所述组播MAC地址组成对应该网络节点的组播转发表项发送给该网络节点。
所述边缘节点是在当前网络管理域中的入口网络节点或出口网络节点,对于组播业务来说,通常为在网络管理域内组播路径上的入口网络节点或出
口网络节点;所述网络节点可以为用户端设备(Customer Premises Equipment,CPE),AN(如ONU/DSLAM/OLT),或汇聚节点,或路由器(如BNG/BRAS)等设备,所述组播控制消息包括IGMP/MLD,以及接入环路标识(Line ID)。
可选的,所述接入环路标识为所述边缘节点的接入环路标识;步骤S420中,根据所述接入环路标识,分别确定所述接入环路标识对应的组播路径上各个网络节点的端口信息,包括:
根据所述边缘节点的接入环路标识,预先存储的接入环路标识与各个网络节点的端口信息的映射关系,以及根据预先存储的网络拓扑关系确定的所述边缘节点的接入环路标识对应的组播路径,确定所述边缘节点的接入环路标识对应的组播路径上各个网络节点的端口信息;或者,
将所述边缘节点的接入环路标识发送给服务器,所述服务器中预先存储了接入环路标识与各个网络节点的端口信息的映射关系,以及预先存储了网络拓扑关系;接收所述服务器反馈的所述边缘节点的接入环路标识对应的组播路径上各个网络节点的端口信息。
也就是说,既可以设置单独的服务器,接入控制器向服务器查询接入环路标识对应的组播路径上各个网路节点的端口信息,也可以由接入控制器预先设置接入环路标识与各个网络节点的端口的映射关系以及网络拓扑关系,接入控制器查询映射关系以及网络拓扑关系得到各个网络节点的端口信息。
其中,接入环路标识为广泛应用于各类网络***中的一种标识,对于数字用户线(Digital Subscriber Line,DSL)或以太网(ETH)接入***,接入环路标识的格式如下:
当AN接入基于异步传输模式(Asynchronous Transfer Mode,ATM)的DSL线路时,接入环路标识为Access-Node-Identifier atm slot/port:vpi.vci;当AN接入基于ETH的DSL/ETH线路时,接入环路标识的格式为Access-Node-Identifier eth slot/port[:vlan-id]。其中,Access-Node-Identifier为AN的标识;slot/port为AN上的机柜(chassis)号、机架(rack)号、框(frame)号、槽位(slot)号、子槽位(sub-slot)号、端口(port)号等信息中的一种
或多种的组合,具体内容与设备的现场布置状况相关;vpi.vci为DSL线路上的虚路径标识符和虚通道标识符;格式中的“[]”表示可选。
对于无源光网络(Passive Optical Network,PON)***,接入环路标识有两种格式选项(option),如下所示:
Option 1为接入环路标识只包含ONU端口信息,格式如下:当ONU接入基于ATM的DSL线路时,为ONUID atm slot2/port2:vpi.vci;当ONU接入基于ETH的DSL线路时,为ONUID eth slot2/port2[:vlan-id]。通常,对于ONU端口,vlan-id为C-VLAN ID(Customer VLAN ID,用户虚拟局域网标识),用于标识用户或接入线路,一般由ONU添加或删除。
Option 2为接入环路标识既包含ONU端口信息,又包含OLT端口信息,格式如下:当ONU接入基于ATM的DSL线路时,为Access-Node-Identifier atm slot1/port1/ONUID/slot2/port2:vpi.vci;当ONU接入基于ETH的DSL/ETH线路时,为Access-Node-Identifier eth slot1/port1/ONUID/slot2/port2[:vlan-id]。其中,Access-Node-Identifier为OLT的标识;slot1/port1为OLT上的机柜(chassis)号、机架(rack)号、框(frame)号、槽位(slot)号、子槽位(sub-slot)号、端口(port)号的一种或多种的组合,具体内容与设备的现场布置状况相关;slot2/port2为ONU上的机柜(chassis)号、机架(rack)号、框(frame)号、槽位(slot)号、子槽位(sub-slot)号、端口(port)号的一种或多种的组合。
总之,网络节点上报的接入环路标识包括端口信息,根据网络节点上报的接入环路标识,还能够确定组播路径各节点及其端口信息。
可选地,所述接入环路标识为所述组播路径上各个网络节点的接入环路标识;步骤S420中,根据所述接入环路标识,分别确定所述接入环路标识对应的组播路径上各个网络节点的端口信息,包括:
根据所述组播路径上各个网络节点的接入环路标识,分别获取组播路径上各个网络节点的接入环路标识中包括的端口信息。
也就是说,在图2所示场景下,还存在另一种实施方式,即IGMP/MLD
消息仍然在组播路径上传输,组播路径上各个网络节点不解析IGMP/MLD消息,而是在转发IGMP/MLD消息之前在消息中***本节点的接入环路标识,再由网络管理域的边缘节点向接入控制器上报IGMP/MLD消息和各个节点的接入环路标识。最后,再由接入控制器解析IGMP/MLD消息,以及获取接入环路标识中的端口信息,并指示每一网络节点与该网络节点对应的组播转发表项。
具体地,步骤S420中,根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址,包括:
根据所述组播控制消息中的组播IP地址,以及预先确定的组播IP地址与组播MAC地址的映射关系,确定所述组播路径对应的组播MAC地址。
具体的,步骤S410之后,还包括:将所述IGMP报文或MLD报文发送给所述边缘节点以外的其它边缘节点;或者,
根据所述IGMP报文或MLD报文生成组播路由协议报文,将所述组播路由协议报文发送给所述边缘节点以外的其它边缘节点。
当所述其它边缘节点(如图2的Node n)为接入节点(如OLT、DSLAM)或汇聚节点时,接入控制器将IGMP/MLD消息通过Openflow、接入管理或控制协议(如OMCI或ETH OAM)或隧道转送到所述其它边缘节点;当所述其它边缘节点节点为路由器(如BNG/BRAS)时,接入控制器将生成组播路由协议(如协议无关组播(Protocol Independent Multicast,PIM)/指定源组播(Source-Specific Multicast,SSM))消息通过Openflow协议、接入管理或控制协议或隧道协议转送到作为路由器的所述其它边缘节点。所述其它边缘节点在接收到所述IGMP报文或MLD报文或组播路由协议报文后,将报文继续传输下去。
上述实施例的消息流图如图5所示,接入控制器接收作为入口网络节点的边缘节点发送的IGMP/MLD消息,向各个网络节点下发组播转发表项,以及向作为出口网络节点的边缘节点发送IGMP/MLD消息。
下面给出几个本发明的具体实施例。
参见图6,本发明具体实施例一包括如下步骤:
S610:用户向远端接入节点(Remote AN)发送IGMP/MLD报文;
S620:Remote AN通过扩展openflow消息,将IGMP/MLD报文和Line ID送往接入控制器;
S630:接入控制器向AAA(Authentication、Authorisation、Accounting简称)服务器发送AAA消息,消息中携带Line ID,用于查询端口信息;
S640:AAA服务器根据Line ID,得到各级网络节点对应的端口信息;
S650:AAA服务器向接入控制器发送AAA消息,消息中携带Line ID与各级网络节点对应的端口信息;
S660:接入控制器根据IGMP/MLD获取组播IP地址,根据端口信息和组播IP地址形成各级组成员关系表项,将组播IP地址映射到组播MAC地址,进一步形成相应的各级组播转发表项;
S670:通过openflow协议配置各级网络节点上相应的组播转发表项;
S680:通过openflow消息向各个网络节点发送对应的组播转发表项;
S690:各个网络节点完成组播转发表项配置。
具体实施例一中,当Remote AN为ONU,AN 1为OLT,AN 2为DSLAM时,步骤S620中openflow消息携带的Line ID可以为Option1,此时接入控制器根据Line ID信息,查询AAA服务器得到OLT和DSLAM的端口信息;或者,步骤S620中openflow消息携带的Line ID为Option2,ONU需要事先得到或设置OLT的端口信息,此时接入控制器根据Line ID信息,查询AAA服务器得到DSLAM的端口信息。
参见图7,本发明具体实施例二包括如下步骤:
S710:用户向ONU发送IGMP/MLD报文;
S720:ONU通过扩展openflow消息,将IGMP/MLD报文和Line ID 1(ONU的端口信息)送往OLT;
S730:OLT通过扩展openflow消息,将IGMP/MLD报文、Line ID 2(ONU的端口信息和OLT的端口信息)送往接入控制器;
S740:接入控制器根据IGMP/MLD获取组播IP地址,根据端口信息和组播IP地址形成各级组成员关系表项,将组播IP地址映射到组播MAC地址,进一步形成相应的各级组播转发表项;
S750:通过openflow协议配置各级网络节点上相应的组播转发表项;
S760:通过openflow消息向各个网络节点发送对应的组播转发表项;
S770:各个网络节点完成组播转发表项配置。
参见图8,本发明实施例提供的指示组播转发表项的设备80包括:
第一接收单元810,用于接收第一节点发送的组播控制消息以及接入环路标识;
第一确定单元820,用于确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,所述第一端口和所述第二端口均为所述组播路径上的出端口;
第二确定单元830,用于根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址;
第一发送单元840,用于向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;
第二发送单元850,用于向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识。
可选地,所述第一接收单元810接收的接入环路标识为所述第一节点的接入环路标识;
所述第一确定单元820,具体用于:
根据所述第一节点的接入环路标识,预先存储的接入环路标识与各个网络节点的端口信息的映射关系,以及根据预先存储的网络拓扑关系确定的所述第一节点的接入环路标识对应的组播路径,确定所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口
的标识;或者,
将所述第一节点的接入环路标识发送给服务器,所述服务器中预先存储了接入环路标识与各个网络节点的端口信息的映射关系,以及预先存储了网络拓扑关系;接收所述服务器反馈的所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
可选地,所述第一接收单元810接收的接入环路标识包括第一节点的接入环路标识、第二节点的接入环路标识和第三节点的接入环路标识,所述第二节点和所述第三节点均在所述第一节点的接入环路标识对应的组播路径上;
所述第一确定单元820,具体用于:
根据所述组播路径上的第二节点的接入环路标识和第三节点的接入环路标识,分别获取所述组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
可选地,所述第二确定单元830,具体用于:
根据所述组播控制消息中的组播IP地址,以及预先确定的组播IP地址与组播MAC地址的映射关系,确定所述组播路径对应的组播MAC地址。
可选地,所述第一接收单元810接收的组播控制消息为因特网组管理协议IGMP报文或组播监听者发现协议MLD报文。
进一步地,设备80还包括:
第三发送单元,用于将所述IGMP报文或MLD报文发送给第四节点;或者,
根据所述IGMP报文或MLD报文生成组播路由协议报文,将所述组播路由协议报文发送给第四节点。
进一步地,所述第一接收单元810,具体用于:
接收第一节点根据openflow协议,或者接入管理或控制协议,或者以太网操作、管理和维护协议,或者隧道协议发送的组播控制消息以及接入环路标识。
参见图9,本发明实施例提供的指示组播转发表项的设备90包括:
处理器910,存储器920和通信接口930;处理器910,存储器920和通信接口930通过总线或其他方式相互连接。
存储器920,用于存放程序。具体地,程序可以包括程序代码,所述程序代码包括计算机操作指令。存储器可能包含高速随机存取存储器(random access memory,简称RAM)存储器,也可能还包括非易失性存储器(non-volatile memory),例如至少一个磁盘存储器。
所述通信接口930用于与各个节点通信。
处理器910执行存储器920所存放的程序,可以执行与图3对应的实施例中的S310-S350,可以执行与图4对应的实施例中的S410-S430,可以执行与图5-7对应的实施例中的接入控制器的全部操作,可以显示组播转发表项的设备80的全部功能。
上述的处理器可以是通用处理器,包括中央处理器(Central Processing Unit,简称CPU)、网络处理器(Network Processor,简称NP)等;还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
终上所述,本发明实施例中,将网络节点的控制面功能集中在接入控制器侧,将网络节点简化为可编程转发设备,网络节点不用再支持IGMP/MLD的侦听/代理,实现网络节点与组播业务解耦,网络节点不需考虑与终端和组播路由器的兼容匹配问题,极大降低了运维复杂度和管理成本。
本领域内的技术人员应明白,本发明的实施例可提供为方法、***、或计算机程序产品。因此,本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图
和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。
Claims (14)
- 一种指示组播转发表项的方法,其特征在于,包括:接收第一节点发送的组播控制消息以及接入环路标识;确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,所述第一端口和所述第二端口均为所述组播路径上的出端口;根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址;向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识。
- 如权利要求1所述的方法,其特征在于,所述接入环路标识为所述第一节点的接入环路标识;确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,包括:根据所述第一节点的接入环路标识,预先存储的接入环路标识与各个网络节点的端口信息的映射关系,以及根据预先存储的网络拓扑关系确定的所述第一节点的接入环路标识对应的组播路径,确定所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识;或者,将所述第一节点的接入环路标识发送给服务器,所述服务器中预先存储了接入环路标识与各个网络节点的端口信息的映射关系,以及预先存储了网络拓扑关系;接收所述服务器反馈的所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
- 如权利要求1所述的方法,其特征在于,所述接入环路标识包括第一 节点的接入环路标识、第二节点的接入环路标识和第三节点的接入环路标识,所述第二节点和所述第三节点均在所述第一节点的接入环路标识对应的组播路径上;确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,包括:根据所述组播路径上的第二节点的接入环路标识和第三节点的接入环路标识,分别获取所述组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
- 如权利要求1所述的方法,其特征在于,根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址,包括:根据所述组播控制消息中的组播IP地址,以及预先确定的组播IP地址与组播MAC地址的映射关系,确定所述组播路径对应的组播MAC地址。
- 如权利要求1所述的方法,其特征在于,所述组播控制消息为因特网组管理协议IGMP报文或组播监听者发现协议MLD报文。
- 如权利要求1至5任一权项所述的方法,其特征在于,还包括:将所述IGMP报文或MLD报文发送给第四节点;或者,根据所述IGMP报文或MLD报文生成组播路由协议报文,将所述组播路由协议报文发送给第四节点。
- 如权利要求1至5任一权项所述的方法,其特征在于,所述接收第一节点发送的组播控制消息以及接入环路标识,包括:接收第一节点根据openflow协议,或者接入管理或控制协议,或者以太网操作、管理和维护协议,或者隧道协议发送的组播控制消息以及接入环路标识。
- 一种指示组播转发表项的设备,其特征在于,包括:第一接收单元,用于接收第一节点发送的组播控制消息以及接入环路标识;第一确定单元,用于确定所述接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识,所述第一端口和所述第二端口均为所述组播路径上的出端口;第二确定单元,用于根据所述组播控制消息中的组播互联网协议IP地址,确定所述组播路径对应的组播媒体接入控制MAC地址;第一发送单元,用于向所述第二节点发送第一转发表项,所述第一转发表项的目的地址为所述组播MAC地址,所述第一转发表项的出端口信息为所述第一端口的标识;第二发送单元,用于向所述第三节点发送第二转发表项,所述第二转发表项的目的地址为所述组播MAC地址,所述第二转发表项的出端口信息为所述第二端口的标识。
- 如权利要求8所述的设备,其特征在于,所述第一接收单元接收的接入环路标识为所述第一节点的接入环路标识;所述第一确定单元,具体用于:根据所述第一节点的接入环路标识,预先存储的接入环路标识与各个网络节点的端口信息的映射关系,以及根据预先存储的网络拓扑关系确定的所述第一节点的接入环路标识对应的组播路径,确定所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识;或者,将所述第一节点的接入环路标识发送给服务器,所述服务器中预先存储了接入环路标识与各个网络节点的端口信息的映射关系,以及预先存储了网络拓扑关系;接收所述服务器反馈的所述第一节点的接入环路标识对应的组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
- 如权利要求8所述的设备,其特征在于,所述第一接收单元接收的接入环路标识包括第一节点的接入环路标识、第二节点的接入环路标识和第三节点的接入环路标识,所述第二节点和所述第三节点均在所述第一节点的接入环路标识对应的组播路径上;所述第一确定单元,具体用于:根据所述组播路径上的第二节点的接入环路标识和第三节点的接入环路标识,分别获取所述组播路径上的第二节点的第一端口的标识和第三节点的第二端口的标识。
- 如权利要求8所述的设备,其特征在于,所述第二确定单元,具体用于:根据所述组播控制消息中的组播IP地址,以及预先确定的组播IP地址与组播MAC地址的映射关系,确定所述组播路径对应的组播MAC地址。
- 如权利要求8所述的设备,其特征在于,所述第一接收单元接收的组播控制消息为因特网组管理协议IGMP报文或组播监听者发现协议MLD报文。
- 如权利要求8至12任一权项所述的设备,其特征在于,还包括:第三发送单元,用于将所述IGMP报文或MLD报文发送给第四节点;或者,根据所述IGMP报文或MLD报文生成组播路由协议报文,将所述组播路由协议报文发送给第四节点。
- 如权利要求8至12任一权项所述的设备,其特征在于,所述第一接收单元,具体用于:接收第一节点根据openflow协议,或者接入管理或控制协议,或者以太网操作、管理和维护协议,或者隧道协议发送的组播控制消息以及接入环路标识。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15783491.2A EP3128697B1 (en) | 2014-04-24 | 2015-04-02 | Method and device for instructing multicast forwarding entry |
US15/332,867 US11196576B2 (en) | 2014-04-24 | 2016-10-24 | Method for indicating multicast forwarding entry and device |
US17/518,338 US20220060344A1 (en) | 2014-04-24 | 2021-11-03 | Method for indicating multicast forwarding entry and device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410169740.8 | 2014-04-24 | ||
CN201410169740.8A CN105099914B (zh) | 2014-04-24 | 2014-04-24 | 一种指示组播转发表项的方法及设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/332,867 Continuation US11196576B2 (en) | 2014-04-24 | 2016-10-24 | Method for indicating multicast forwarding entry and device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015161736A1 true WO2015161736A1 (zh) | 2015-10-29 |
Family
ID=54331726
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/075786 WO2015161736A1 (zh) | 2014-04-24 | 2015-04-02 | 一种指示组播转发表项的方法及设备 |
Country Status (4)
Country | Link |
---|---|
US (2) | US11196576B2 (zh) |
EP (1) | EP3128697B1 (zh) |
CN (1) | CN105099914B (zh) |
WO (1) | WO2015161736A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106357542B (zh) * | 2016-10-12 | 2019-10-18 | 华为技术有限公司 | 提供组播业务的方法和软件定义网络控制器 |
US10862807B2 (en) * | 2018-09-19 | 2020-12-08 | Cisco Technology, Inc. | Packet telemetry data via first hop node configuration |
CN109862437B (zh) * | 2019-03-20 | 2020-11-27 | 新华三技术有限公司 | 一种转发表项创建方法及bras |
CN112073317B (zh) * | 2019-06-10 | 2022-01-07 | 华为技术有限公司 | 一种发送报文流量的方法和装置 |
CN111585854B (zh) * | 2020-05-12 | 2022-08-23 | ***通信集团内蒙古有限公司 | 数据网承载调度的网络***、保护方法、设备及存储介质 |
US20210149812A1 (en) * | 2020-11-18 | 2021-05-20 | Intel Corporation | Network interface controller with eviction cache |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101150425A (zh) * | 2007-11-15 | 2008-03-26 | 中国电信股份有限公司 | 组播业务权限控制方法及其光网络单元和光线路终端 |
US20090059935A1 (en) * | 2007-08-27 | 2009-03-05 | Cisco Technology, Inc. | Colored access control lists for multicast forwarding using layer 2 control protocol |
CN102946357A (zh) * | 2012-11-28 | 2013-02-27 | 杭州华三通信技术有限公司 | 组播转发表项的下发方法及设备 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6707796B1 (en) * | 1999-05-07 | 2004-03-16 | Nortel Networks Limited | System device and method for reducing forwarding states in a communication system |
US7765300B2 (en) * | 2003-10-06 | 2010-07-27 | Ericsson Ab | Protocol for messaging between a centralized broadband remote aggregation server and other devices |
CN100461732C (zh) * | 2006-06-16 | 2009-02-11 | 华为技术有限公司 | 一种以太技术交换和转发的方法、***和设备 |
CN100433665C (zh) * | 2006-11-07 | 2008-11-12 | 华为技术有限公司 | 一种因特网组管理协议监听方法及交换机 |
US8619797B2 (en) * | 2009-05-12 | 2013-12-31 | Futurewei Technologies, Inc. | Using internet protocol version six (IPv6) tunnel for access identifier transport |
CN102088391B (zh) * | 2009-12-07 | 2013-09-11 | 华为技术有限公司 | 一种IPv6报文的处理方法、设备和*** |
CN101924701B (zh) * | 2010-08-26 | 2013-04-17 | 北京星网锐捷网络技术有限公司 | 组播转发路径的建立方法及路由设备 |
JP5678678B2 (ja) * | 2011-01-18 | 2015-03-04 | 富士通株式会社 | プロバイダ網及びプロバイダエッジ装置 |
JP6102214B2 (ja) * | 2012-11-22 | 2017-03-29 | 富士通株式会社 | 転送プログラム、設定プログラム、送信プログラム、転送装置、設定装置、送信装置、転送方法、設定方法および送信方法 |
EP2932661A4 (en) * | 2012-12-17 | 2016-06-01 | Qualcomm Inc | MULTICAST TRAFFIC BRIDGE |
WO2014121468A1 (zh) | 2013-02-06 | 2014-08-14 | 华为技术有限公司 | 在网络虚拟化***中组播数据通道建立的方法及设备 |
WO2014147483A2 (en) * | 2013-03-20 | 2014-09-25 | Marvell World Trade Ltd. | Cut-through processing for slow and fast ports |
CN103414644B (zh) * | 2013-07-31 | 2016-12-07 | 华为技术有限公司 | 表项下发的方法及控制器 |
-
2014
- 2014-04-24 CN CN201410169740.8A patent/CN105099914B/zh active Active
-
2015
- 2015-04-02 WO PCT/CN2015/075786 patent/WO2015161736A1/zh active Application Filing
- 2015-04-02 EP EP15783491.2A patent/EP3128697B1/en active Active
-
2016
- 2016-10-24 US US15/332,867 patent/US11196576B2/en active Active
-
2021
- 2021-11-03 US US17/518,338 patent/US20220060344A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090059935A1 (en) * | 2007-08-27 | 2009-03-05 | Cisco Technology, Inc. | Colored access control lists for multicast forwarding using layer 2 control protocol |
CN101150425A (zh) * | 2007-11-15 | 2008-03-26 | 中国电信股份有限公司 | 组播业务权限控制方法及其光网络单元和光线路终端 |
CN102946357A (zh) * | 2012-11-28 | 2013-02-27 | 杭州华三通信技术有限公司 | 组播转发表项的下发方法及设备 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3128697A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN105099914B (zh) | 2018-12-25 |
CN105099914A (zh) | 2015-11-25 |
US20170041157A1 (en) | 2017-02-09 |
EP3128697B1 (en) | 2019-12-04 |
EP3128697A1 (en) | 2017-02-08 |
US11196576B2 (en) | 2021-12-07 |
EP3128697A4 (en) | 2017-05-03 |
US20220060344A1 (en) | 2022-02-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015161736A1 (zh) | 一种指示组播转发表项的方法及设备 | |
US8619788B1 (en) | Performing scalable L2 wholesale services in computer networks | |
Mahalingam et al. | Virtual extensible local area network (VXLAN): A framework for overlaying virtualized layer 2 networks over layer 3 networks | |
US11374857B2 (en) | Network device management method and apparatus, and system for indicating a network device to perform management operation | |
EP2154821B1 (en) | Method and apparatus for sending and receiving multicast packets | |
US12021561B1 (en) | Data provisioning | |
EP3328004A1 (en) | Broadband access | |
CN104917849B (zh) | 一种消息处理方法、接入控制器及网络节点 | |
US8730979B2 (en) | Method and system for increasing forwarding efficiency of virtual private LAN service network | |
CN108964940B (zh) | 消息发送方法及装置、存储介质 | |
WO2012139453A1 (zh) | 一种dpoe***及基于该***业务自动配置方法和网络 | |
US9270480B1 (en) | Systems and methods for Ethernet-based management of optical networks using OMCI | |
WO2016041379A1 (zh) | Nni ping的实现方法及装置 | |
WO2009021371A1 (fr) | Procédé et dispositif permettant de réaliser une émulation pseudo-filaire de bout en bout | |
US8964749B2 (en) | Method, device and system for establishing a pseudo wire | |
WO2015180120A1 (zh) | 报文转发方法、转发表项下发方法及网络设备 | |
US8531974B2 (en) | Technique for testing peers in multicast network domain | |
US11870681B2 (en) | Bier multicast traffic statistics collection method, device, and system | |
JP6332544B1 (ja) | ネットワーク管理装置、ネットワークシステム、方法、及びプログラム | |
WO2014101185A1 (zh) | 组播通道的性能检测方法、装置和*** | |
WO2019085809A1 (zh) | 获得目标传输路径的方法、相关设备及*** | |
US20140112659A1 (en) | Olt and frame transfer control method | |
US20230318974A1 (en) | BIER Packet Forwarding Method, Device, and System | |
JP2019195139A (ja) | ネットワーク管理装置、ネットワークシステム、方法、及びプログラム | |
JP2013078087A (ja) | Vpn終端装置、通信システム、パケット転送方法、及びプログラム |
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: 15783491 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2015783491 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015783491 Country of ref document: EP |