WO2013056669A1 - 在组播接收端切换场景下建立优化路径的方法及系统 - Google Patents

在组播接收端切换场景下建立优化路径的方法及系统 Download PDF

Info

Publication number
WO2013056669A1
WO2013056669A1 PCT/CN2012/083194 CN2012083194W WO2013056669A1 WO 2013056669 A1 WO2013056669 A1 WO 2013056669A1 CN 2012083194 W CN2012083194 W CN 2012083194W WO 2013056669 A1 WO2013056669 A1 WO 2013056669A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
mag
source
tunnel
target
Prior art date
Application number
PCT/CN2012/083194
Other languages
English (en)
French (fr)
Inventor
刘娟
严为
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013056669A1 publication Critical patent/WO2013056669A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method and system for establishing an optimized path in a handover scenario of a multicast receiving end.
  • Multicast is to solve the efficiency problem that traditional unicast routing occurs when dealing with group communication.
  • IGMP Internet Group Management Protocol
  • MLD Multicast Listener Discovery Protocol
  • Mobility management protocols such as mobile IP.
  • IP multicast service models There are two types of IP multicast service models: Any Source Multicast ASM (full name Any-Source Multicast) and a specific source multicast SSM (full name Source-Specific Multicast).
  • ASM uses a multicast group address G to identify a multicast group. Each multicast group can have any number of multicast sources and receivers.
  • the aggregation point (RP, called Rendezvous Point) is used for the shared tree.
  • each channel can only have one specified source and any number of receivers. There is no need to select the aggregation point RP and the maintenance shared tree (RPT) in the SSM model.
  • the multicast source is registered, so that the SPT with the multicast source S as the root and the receiver as the leaf is directly constructed in the network, thereby eliminating the process of establishing the shared tree and then switching from the shared tree to the shortest path tree in the ASM model.
  • SSM is a simple and effective multicast model, which can overcome the shortcomings of ASM in access control, address allocation, source discovery, and vulnerability to DoS attacks. Therefore, SSM model is more scalable and can be used. Improve network performance in the future The Internet has a wider application prospect.
  • RPF reverse path forwarding
  • the RPF check process is as follows: The router that receives the multicast packet searches for the unicast routing table with the IP address of the multicast source as the destination address. The outbound interface in the corresponding entry is the RPF interface. The router considers that the RPF is configured by the RPF. The path that the multicast packet received by the interface is the shortest path from the multicast source to the local device. The RPF interface is compared with the interface where the multicast packet actually arrives.
  • the unicast routing information used as the basis for path judgment can be derived from any unicast routing protocol, multicast static route, or MBGP routing protocol.
  • the multicast receiver MN For mobile multicast, IETF is working on the PMIPv6-based mobile multicast mechanism in the MULTIMOB working group.
  • the multicast receiver MN The multicast source MN-S (MN-Source) is located in the same ⁇ domain, the multicast receiver is currently connected to the mobile access gateway P-MAG, and the MN-S is connected to the mobile access gateway MAG, MN and MN.
  • the top anchor of -S can be the same LMA or a different LMA.
  • the MN reports to the P-MAG through the MLDv2 report message that it needs to receive multicast data from the multicast source MN-S and sent to the multicast group G.
  • the P-MAG After receiving the MLDv2 report, the P-MAG sends the channel subscription hop-by-hop to the multicast source MN-S.
  • the subscription packet sent by the P-MAG to the LMA needs to be encapsulated in the tunnel.
  • the subscription message sent by the LMA to the MAG is subscribed. Tunnel encapsulation is also required. All routers along the way create (HoA, G) multicast routing entries, HoA represents the address of the multicast source MN-S, and G represents the multicast address, thus constructing the multicast source MN-S as the root.
  • the path from the MAG to the LMA to which the multicast source MN-S belongs is a PMIPv6 tunnel, and the path from the LMA to the P-MAG to which the MN belongs is a ⁇ tunnel, followed by a multicast source.
  • the multicast data sent by the MN-S arrives along the established SPT, and the multicast forwarding path is as shown in 100a of FIG.
  • the MN switches to the new mobile access gateway N-MAG a new SPT path is established through the above process.
  • the path from the MAG to the LMA to which the multicast source MN-S belongs is a PMIPv6 tunnel.
  • the path from the LMA to the N-MAG to which the MN belongs is a PMIPv6 tunnel.
  • the multicast packet sent by the MN-S to the MN must first be sent through the PMIPv6 tunnel between the MN-S mobile access gateway MAG and the local mobility anchor LMA, and the multicast packet arrives at the MN. After the LMA is anchored, it must be sent through the PMIPv6 tunnel between the mobile access gateways of the LMA and the MN. Therefore, the SPT paths 100a and 101a shown in FIG. 1A are not the shortest multicast forwarding paths, which reduces the efficiency of multicast routing.
  • the N-MAG When the MN is in the process of switching, the N-MAG needs to exchange the MLD query/report message with the MN to learn the current multicast listening state of the MN, and send the channel subscription hop by hop to the multicast source MN-S through the multicast routing protocol. In this case, the multicast forwarding tree is re-established. Because the multicast group member status and the multicast tree branch adjustment often take a long time, the MN has a large handover delay and the handover loss problem is also serious. Therefore, the mobile multicast solution proposed by ⁇ inevitably causes non-shortest SPT paths and multicast handover delays and packet loss, which reduces routing efficiency and performance of mobile multicast.
  • An embodiment of the present invention provides a method and system for establishing an optimized path in a handover scenario of a multicast receiving end, which solves the problem of low routing efficiency caused by a non-shortest SPT path in a handover scenario of a multicast receiving end in a related scheme.
  • the present invention provides a method for establishing an optimization path in a handover scenario of a multicast receiving end, including:
  • the target mobile access gateway (MAG) of the multicast receiving end ( ⁇ ) learns the multicast state information of the MN from the source MAG of the MN or the local mobility anchor (LMA) to which the source MAG of the MN belongs, according to The multicast status information of the MN is established with the MAG to which the multicast source (MN-S) of the MN belongs, and the MAG to which the MN-S belongs passes the multicast message of the MN-S.
  • the multicast tunnel is sent to the target MAG of the MN.
  • the multicast status information of the MN includes multicast listener discovery status information and multicast source information, and the multicast listener discovery status information includes a multicast address and a multicast source address list, where the multicast source information includes The address of the multicast source that allows multicast data to be sent to the MN in the multicast source address list and the address of the MAG to which the multicast source is connected.
  • the method further includes: after the multicast tunnel is established, the target MAG creates, according to the multicast listener discovery status information in the multicast status information of the MN, for each channel to which the MN belongs or The multicast routing entry is updated, and the multicast tunnel interface to the MAG to which the MN-S belongs is set as the inbound interface of each multicast routing entry.
  • the method further includes: after the multicast tunnel is established, the target MAG sends a protocol-independent multicast join message to the MAG to which the MN-S belongs by using the multicast tunnel to declare that the channel belongs to the MN to which the MN belongs.
  • the MAG to which the MN-S belongs creates or updates a multicast routing entry of the corresponding channel according to the channel information in the protocol-independent multicast join message, and adds a tunnel interface to the target MAG to the multicast routing entry. Out of the interface list.
  • the step of the MAG to which the MN-S belongs to send the multicast information of the MN-S to the target MAG of the MN through the multicast tunnel includes:
  • the MAG to which the MN-S belongs After receiving the multicast file sent by the MN-S, the MAG to which the MN-S belongs sends the multicast packet to all multicast tunnel interfaces in the outbound interface list of the maintained multicast routing entry.
  • the method further includes: after the target MAG receives the multicast message through the multicast tunnel, and determines that the multicast tunnel interface that receives the multicast packet is an inbound interface in the multicast routing entry, to the multicast All outbound interfaces in the outbound interface list of the routing entry forward the multicast packet.
  • the methods for establishing a multicast tunnel include:
  • the target MAG sends a multicast tunnel setup message to the MAG to which the MN-S belongs according to the multicast source information in the multicast state information, and the MAG to which the MN-S belongs sends a multicast tunnel to the target MAG.
  • Establishing a response message, and establishing a multicast tunnel end node to the target MAG the target MAG establishes a multicast tunnel end node of the MAG to which the MN-S belongs, and the multicast tunnel is established.
  • the target MAG learns the multicast status information of the MN from the source MAG by using an extended handover initiation message, and includes: the MN is connected to the source Transmitting the identifier of the MN and the target access network identifier on the network, the source access network sending, to the source MAG, handover indication information carrying the identifier of the MN and the identifier of the target access network, where the source MAG is according to the target
  • the access network identifier determines the address of the target MAG, and sends an extended handover initiation message to the target MAG, where the handover initiation message carries the multicast status information of the MN.
  • the target MAG Obtaining the multicast status information of the MN from the source MAG by using the extended handover confirmation message, the method includes: after the MN establishes a connection with the target MAG by using the target access network, the target MAG sends a handover initiation to the source MAG. The message, when the source MAG returns an extended handover confirmation message to the target MAG, carries the multicast status information of the MN in the handover confirmation message.
  • the target MAG obtains the multicast status information of the MN from the LMA to which the source MAG belongs by using the extended binding acknowledgement message, including:
  • the source MAG After the MN leaves the source MAG, the source MAG sends an extended ⁇ %m registration binding update message to the associated LMA, where the message carries the multicast status information of the MN, and the LMA saves the The multicast status information of the MN; after the MN switches to the target MAG, the target MAG sends a binding update message to the LMA, and the LMA returns an extended binding confirmation message to the target MAG, where The binding acknowledgement message carries the multicast status information of the MN.
  • the target MAG obtains the multicast status information of the MN from the LMA to which the source MAG belongs by using the extended binding acknowledgement message, including:
  • Each MAG under the control of the LMA receives a multicast listener discovery report message actively sent by the multicast receiving end of the jurisdiction, or triggers the multicast receiving end of the multicast receiver to send a multicast listener discovery report message, according to the multicast
  • the listener finds that the report message is informed of the multicast status information of the multicast receiver, and sends a registration message carrying the multicast status information of the multicast receiver to the LMA, where the LMA stores the multicast status information of each multicast receiver.
  • the target MAG After the MN switches to the target MAG, the target MAG sends a binding update message to the LMA, and the LMA returns an extended binding acknowledgement message to the target MAG, where the binding acknowledgement message carries the MN. Multicast status information.
  • the method further includes: when the MN is the last multicast listener on the source MAG that receives multicast data from the MN-S, after the MN switches into the target MAG, the source MAG direction
  • the MAG of the MN-S sends a prune message with the address of the multicast source as the destination address, and the multicast routing entry corresponding to the MN-S is deleted, and is deleted to the MAG of the MN-S.
  • the embodiment of the present invention further provides a system for establishing an optimized path in a handover scenario of a multicast receiving end, including a multicast receiving end (MN), a target mobile access gateway (MAG) of the MN, a source MAG of the MN, and a source of the MN.
  • MN multicast receiving end
  • MAG target mobile access gateway
  • LMA local mobility anchor
  • MN-S multicast source
  • the genus LMA learns the multicast status information of the MN, and establishes a multicast tunnel with the MAG to which the MN-S belongs according to the multicast status information of the MN;
  • the MAG to which the MN-S belongs is set to establish a multicast tunnel with the target MAG of the MN, and the multicast message of the MN-S is sent to the target MAG of the MN through the multicast tunnel.
  • the multicast status information of the MN includes multicast listener discovery status information and multicast source information, and the multicast listener discovery status information includes a multicast address and a multicast source address list, where the multicast source information includes The address of the multicast source that allows multicast data to be sent to the MN in the multicast source address list and the address of the MAG to which the multicast source is connected.
  • the target MAG is further configured to: after the multicast tunnel is established, create or update a multicast routing entry for each channel to which the MN belongs according to the multicast listener discovery status information of the MN, and then The multicast tunnel interface of the MAG to which the MN-S belongs is set as the inbound interface of each multicast routing entry.
  • the target MAG is further configured to: after the multicast tunnel is established, send a protocol-independent multicast join message to the MAG to which the MN-S belongs by using the multicast tunnel to declare to join each channel to which the MN belongs;
  • the MAG to which the MN-S belongs is further configured to create or update a multicast routing entry of the corresponding channel according to the channel information in the protocol-independent multicast join message, and add a tunnel interface to the target MAG to the multicast. In the outbound interface list of the routing entry.
  • the target MAG is configured to establish a multicast tunnel by: sending a multicast tunnel setup message to the MAG to which the MN-S belongs according to the multicast source information in the multicast state information, and receiving the multicast tunnel After the response message is established, the multicast tunnel end node of the MAG to which the MN-S belongs is established;
  • the MAG to which the MN-S belongs is set to establish a multicast tunnel by: after receiving the multicast tunnel setup message, sending a multicast tunnel setup response message to the target MAG, and establishing To the multicast tunnel end node of the target MAG.
  • the embodiment of the present invention further provides a mobile access gateway, including a multicast processing module, where the multicast processing module is configured to: use a mobile access gateway (MAG) as a local mobile anchor point (LMA) of a multicast receiving genus Obtaining the multicast status information of the MN, establishing a multicast tunnel with the MAG to which the multicast source (MN-S) of the MN belongs according to the multicast status information of the MN, and using the MAG as the MN When the multicast source (MN-S) belongs to the MAG, the multicast message of the MN-S is sent to the target MAG of the target through a multicast tunnel with the target MAG of the MN.
  • MAG mobile access gateway
  • LMA local mobile anchor point
  • the multicast status information of the MN includes multicast listener discovery status information and multicast source information, and the multicast listener discovery status information includes a multicast address and a multicast source address list, where the multicast source information includes The address of the multicast source that allows multicast data to be sent to the MN in the multicast source address list and the address of the MAG to which the multicast source is connected.
  • the multicast processing module is further configured to: when the associated MAG is the target MAG of the MN, after the multicast tunnel is established, the multicast listener discovers the status information according to the multicast status information of the MN as Each channel to which the MN belongs creates or updates a multicast routing entry, and sets the multicast tunnel interface of the target MAG to the MAG to which the MN-S belongs to an inbound interface of each multicast routing entry.
  • the multicast processing module is further configured to send, by the multicast tunnel, a protocol-independent group to the MAG to which the MN-S belongs after the multicast tunnel is established, when the primary MAG is the target MAG to which the MN belongs.
  • a multicast routing entry is added to the outbound interface list of the multicast routing entry.
  • the tunnel interface of the MAG to which the MN-S belongs is added to the outbound interface list of the multicast routing entry.
  • the method for establishing an SPT path provided by the solution can improve routing efficiency and performance of mobile multicast in the process of switching between multicast receiving ends.
  • FIG. 1 is a schematic diagram of a scenario in which a multicast handover is performed in a PMIPv6 domain in the related art
  • FIG. 2B is a schematic diagram of a scenario in which a multicast receiver MN switches in a PMIPv6 domain in the embodiment
  • FIG. 2 is a multicast receiver in the first embodiment.
  • FIG. 3 is a flowchart of a method for quickly establishing an optimized SPT path when a multicast receiver switches in a second embodiment
  • FIG. 4 is a flowchart of a method for quickly establishing an optimized SPT path when a multicast receiver switches in a third embodiment
  • 5a is a flow chart of a method for a multicast receiver to register multicast status information with an LMA according to Embodiment 4;
  • FIG. 5b is a flowchart of a method for quickly establishing an optimized SPT path when a multicast receiver is switched in the fourth embodiment
  • FIG. 6 is a flowchart of a method for performing a pruning process on a multicast forwarding path in an embodiment.
  • the method for establishing an optimized path in a multicast receiving end handover scenario includes: a target mobile access gateway (MAG) of a multicast receiving end (MN) from a source MAG of the MN or a local mobility anchor to which the source MAG of the MN belongs Point (LMA) knows the multicast status information of the MN, and establishes a multicast tunnel with the MAG to which the multicast source (MN-S) of the MN belongs according to the multicast status information of the MN, where the MN-S belongs.
  • the MAG sends the multicast message of the MN-S to the target MAG of the MN through the multicast tunnel.
  • the multicast status information of the MN includes multicast listener discovery status information and multicast source information, and the multicast listener discovery status information includes a multicast address and a multicast source address list, where the multicast source information includes The address of the multicast source that allows multicast data to be sent to the MN in the multicast source address list, and the MAG address, that is, the address of the MAG to which the multicast source is connected.
  • Figure lb is a scenario diagram of the multicast receiver MN switching in the PMIPv6 domain.
  • the P-MAG is the mobile access gateway before the MN handover
  • the N-MAG is the mobile access gateway after the MN handover. It is a mobile access gateway of the multicast source MN-S.
  • a set of multicast source MN-S and a set of mobile access gateways MAG are shown.
  • the MN Before the MN switches, the MN reports to the P-MAG that it needs to receive the multicast data from the multicast source MN-S and the multicast group G through the MLDv2 report message.
  • the P-MAG queries the LMA to query the MAG address information based on the multicast source address HoA, and establishes a tunnel between the P-MAG and the MAG.
  • the P-MAG sends the channel to the multicast source MN-S through the tunnel.
  • the routers along the way create a (HoA, G) multicast routing entry, HoA represents the address of the multicast source MN-S, and G represents the multicast address, thereby constructing the multicast source MN-S as the root.
  • the broadcast recipient MN is the optimized SPT path for the leaf, as shown at 100b of Figure lb.
  • the target MAG creates or updates a multicast routing entry for each channel to which the MN belongs according to the multicast listener discovery state information in the multicast state information of the MN. Setting the multicast tunnel interface of the target MAG to the MAG to which the MN-S belongs is set as the inbound interface of each multicast routing entry.
  • the target MAG After the multicast tunnel is established, the target MAG sends a protocol-independent multicast join message to the MAG to which the MN-S belongs by using the multicast tunnel to declare that the channel belongs to the MAG to which the MN-S belongs. Adding or updating a multicast routing entry of the corresponding channel according to the channel information in the protocol-independent multicast join message, and adding the tunnel interface of the MAG to which the MN-S belongs to the target MAG to the multicast routing entry In the list of interfaces.
  • the MAG to which the MN-S belongs After receiving the multicast file sent by the MN-S, the MAG to which the MN-S belongs sends the multicast packet to all multicast tunnel interfaces in the outbound interface list of the maintained multicast routing entry.
  • the target MAG After receiving the multicast message through the multicast tunnel, the target MAG determines the outbound interface list of the multicast routing entry when the multicast tunnel interface that receives the multicast message is the inbound interface of the multicast routing entry. All outgoing interfaces in the forwarding.
  • the method for establishing a multicast tunnel includes: the target MAG sends a multicast tunnel setup message to the MAG to which the MN-S belongs according to the multicast source information in the multicast state information, where the MAG direction to which the MN-S belongs Sending, by the target MAG, a multicast tunnel setup response message, and establishing the destination message to the destination.
  • the multicast tunnel end node of the standard MAG, the target MAG is established to the multicast tunnel end node of the MAG to which the MN-S belongs, and the multicast tunnel is established.
  • the target MAG obtains the multicast status information of the MN from the source MAG by using the extended handover initiation message, and specifically includes: the MN reporting the identity and target of the MN to the source access network.
  • An access network identifier the source access network sends, to the source MAG, handover indication information that carries an identifier of the MN and a target access network identifier, where the source MAG determines the target MAG according to the target access network identifier.
  • sending an extended handover initiation message to the target MAG where the handover initiation message carries the multicast status information of the MN.
  • the specific implementation method of Embodiment 1 includes the following steps:
  • Step 200 The multicast source sends a multicast packet to the MN by optimizing the SPT path. As shown in step 200b, the multicast data is sent through the tunnel between the MAG and the P-MAG.
  • Step 201 The MN detects that it needs to perform MAG handover, and reports its own ID and the new access point identifier AP-ID to the source access network P-AN (ie, the access network before the MN handover), the AP-ID Obtaining is related to specific access technologies, and this solution is not discussed.
  • P-AN the access network before the MN handover
  • Step 202 After receiving the advertisement message from the MN, the P-AN sends a handover indication message to the source mobile access gateway P-MAG, where the message also carries the MN-ID and the new access point identifier AP-ID.
  • Step 203 The P-MAG obtains the address information of the new mobile access gateway N-MAG according to the new access point identifier AP-ID in the handover indication message, and sends a handover initiation message HI to the N-MAG, where the message carries Multicast status information of the MN.
  • the scheme extends the handover initiation message HI so that it can carry the multicast state information of the MN.
  • the multicast status information of the MN includes the MLD status information of the MN and the multicast source information.
  • the multicast router running MLDv2 maintains the MLD status according to the multicast address on each directly connected link.
  • the MLD status includes the filtering mode, source list, and timer information. Therefore, the P-MAG maintains the interface connected to the MN.
  • the MLD state is the MLD state of the MN.
  • the MLD status information of the MN includes several records, and the content of each record includes (multicast address G, multicast source address list, filtering mode). If the filtering mode is INCLUDE mode, the multicast source address list includes an Include List. The MN receives the multicast data sent by all the multicast sources in the Include List.
  • the filtering mode is EXCLUDE mode
  • the multicast source address list includes the Exclude List and the Requested List
  • the MN receives the group sent by all the multicast sources in the Requested List. Broadcast data, the MN rejects multicast data sent from all multicast sources in the Exclude List.
  • the multicast source information includes a plurality of records, and the content of each record includes (multicast source address, MAG address), and the multicast source address is the multicast included in the Include List or the Request List in the multicast status information of the MN.
  • the source address and the MAG address are the mobile access gateway addresses connected to the multicast source.
  • the content included in the multicast status information is not limited to the above field, and other fields may be added as needed in the actual application.
  • Step 204 The N-MAG sends a handover confirmation message HAck to the P-MAG as an acknowledgement of the handover initiation message HI.
  • the scheme defines a pair of new mobile header messages, Proxy Multicast Tunnel (PMT) and Proxy Multicast Tunnel Reply (PMTR) as a pair of messages for establishing a multicast tunnel, and can also be extended.
  • the PBU/PBA message serves as a message for establishing a multicast tunnel.
  • Step 205 The N-MAG sends a PMT message to the MAG (that is, the mobile access gateway connected to the multicast source) to establish a multicast tunnel with the MAG according to the MAG address in the multicast status information of the MN.
  • the MAG that is, the mobile access gateway connected to the multicast source
  • Step 206 After receiving the PMT message, the MAG sends a proxy multicast tunnel establishment response message PMTR to the N-MAG, and establishes an end node of the bidirectional tunnel to the N-MAG.
  • Step 207 After receiving the PMTR message, the N-MAG establishes an end node of the bidirectional tunnel to the MAG, and the bidirectional multicast tunnel between the N-MAG and the MAG is established, and the bidirectional tunnel is used to carry the multicast control packet and the group. Broadcast data message.
  • Step 208 The N-MAG saves the MLD state information of the MN, and creates or updates a multicast routing entry for each channel to which the MN belongs according to the MLD state information of the MN. (When it can be determined that the multicast routing entry of the corresponding channel does not exist, the N-MAG creates and The new multicast routing entry corresponding to the corresponding channel determines the multicast routing entry of the corresponding channel, updates the multicast routing entry, and multicasts the N-MAG to the MAG. The interface is set to the inbound interface of the multicast routing entry. The MN is not connected to the N-MAG at this time. The outbound interface list is empty.
  • Step 209 The N-MAG sends a protocol independent multicast (PIM) message to the MAG according to the multicast source information of the MN, and the PIM Join message is encapsulated and sent through the multicast tunnel.
  • PIM protocol independent multicast
  • Step 210 After receiving the PIM Join message, the MAG creates or updates the corresponding multicast routing entry according to the channel information in the PIM Join message, and adds the tunnel interface that receives the PIM Join message to the outbound interface list of the multicast routing entry.
  • Step 211 The MN establishes a connection with the new access network N-AN.
  • Step 212 The new access network N-AN establishes a connection with the new mobile access gateway N-MAG.
  • Step 214 The multicast source sends a multicast message to the multicast group G.
  • Step 215 After receiving the multicast message, the MAG searches for a multicast routing entry and sends a multicast packet to all interfaces in the outbound interface list.
  • the new tunnel interface that arrives at the N-MAG is saved in the outbound interface list.
  • the MAG tunnels the multicast packets to the N-MAG.
  • Step 217 After decapsulating the packet, the N-MAG searches for the multicast routing entry and sends the multicast packet to all the interfaces in the outbound interface list. The MN then receives the multicast packet. Step 208 ensures that the interface that the N-MAG receives the multicast packet matches the inbound interface saved in the multicast routing entry.
  • an optimized SPT path is established in advance, and the routers that the path passes generate corresponding multicast routing entries in the forwarding table.
  • the MN can quickly receive multicast data by optimizing the SPT path after the handover occurs, reducing the multicast handover delay, optimizing the SPT path after the handover, and improving the multicast forwarding efficiency.
  • the FPMIPv6 protocol defined in RFC5949 is used to establish a bidirectional tunnel between the current P-MAG and the N-MAG to which the request is made, so that the MN establishes a multicast tunnel between the N-MAG and the MAG.
  • the target MAG learns the multicast status information of the MN from the source MAG by using an extended handover confirmation message, and specifically includes: the MN establishes a connection with the target MAG via a target access network. Then, the target MAG sends a handover initiation message to the source MAG, and when the source MAG returns an extended handover confirmation message to the target MAG, the handover confirmation message carries the multicast state information of the MN.
  • the specific implementation method of the second embodiment includes:
  • Step 300 The multicast source sends the multicast message to the MN by optimizing the SPT path. As shown in step 300b, the multicast data is sent through the tunnel between the MAG and the P-MAG.
  • Step 301 The MN initiates a handover, and the MN establishes a connection with the new access network N-AN.
  • Step 302 The new access network N-AN establishes a connection with the new mobile access gateway N-MAG, and the N-MAG obtains the address information of the P-MAG through the AP-ID of the P-AN.
  • Step 303 The N-MAG sends a handover initiation message to the P-MAG.
  • Step 304 The P-MAG sends a handover confirmation message HAck to the N-MAG, and the HAck message is extended.
  • the message carries the multicast status information of the MN, and the content of the multicast status information is the same as that of step 203.
  • Step 305 The N-MAG sends a PMT (Proxy Multicast Tunnel) message request to the MAG (that is, the mobile access gateway connected to the multicast source) according to the MAG address in the multicast status information of the MN.
  • PMT Proxy Multicast Tunnel
  • the MAG establishes a multicast tunnel.
  • Step 306 After receiving the PMT message, the MAG sends a Proxy Multicast Tunnel Reply (PMTR) message to the N-MAG, and establishes an end node of the bidirectional tunnel to the N-MAG.
  • PMTR Proxy Multicast Tunnel Reply
  • Step 307 After receiving the PMTR message, the N-MAG establishes an end node of the bidirectional tunnel to the MAG, and the bidirectional multicast tunnel between the N-MAG and the MAG is established, and the bidirectional tunnel is used to carry the multicast control packet and the group. Broadcast data message.
  • the multicast routing entry of the corresponding channel is determined, the multicast routing entry is updated, the multicast tunnel interface of the N-MAG to the MAG is set as the inbound interface of the multicast routing entry, and the interface connecting the MN is added to In the outbound interface list of multicast routing entries.
  • Step 309 The N-MAG sends a PIM Join message to the MAG according to the multicast status information of the MN, and the PIM Join message is encapsulated and sent through the multicast tunnel.
  • Step 310 After receiving the PIM Join message, the MAG creates or updates the corresponding multicast routing entry according to the channel information in the PIM Join message, and adds the tunnel interface that receives the PIM Join message to the outbound interface list of the multicast routing entry. in.
  • Step 311 The multicast source sends a multicast message to the multicast group G.
  • Step 312 After receiving the multicast message, the MAG searches for a multicast routing entry and sends a multicast packet to all interfaces in the outbound interface list. In step 310, the new tunnel interface that arrives at the N-MAG is saved in the outbound interface list. The MAG tunnels the multicast packets to the N-MAG.
  • Step 313 After decapsulating the packet, the N-MAG searches for the multicast routing entry, and sends the multicast packet to all the interfaces in the outbound interface list.
  • the MN receives the multicast packet.
  • Step 308 ensures that the interface that the N-MAG receives the multicast packet matches the inbound interface saved in the multicast routing entry.
  • the N-MAG pre-establishes an optimized SPT path by requesting the multicast status information of the MN from the P-MAG, and the routers through which the path passes are A multicast routing entry is generated in the forwarding table.
  • the MN can quickly receive multicast data by optimizing the SPT path after the handover occurs, reducing the multicast handover delay, and optimizing the SPT path after the handover. Improve the efficiency of multicast forwarding.
  • the FPMIPv6 protocol defined in RFC5949 is used to establish a bidirectional tunnel between the current P-MAG and the N-MAG to which the request is made, so that the MN establishes a multicast tunnel between the N-MAG and the MAG.
  • the multicast data can be continuously received through the bidirectional tunnel between the P-MAG and the N-MAG, so that the multicast switching packet loss can be reduced.
  • the target MAG obtains the multicast state information of the MN from the LMA to which the source MAG belongs by using the extended binding acknowledgement message
  • the method includes: after the MN leaves the source MAG, the The source MAG sends an extended 4th registration registration update message to the associated LMA, where the message carries the multicast status information of the MN, and the LMA saves the multicast status information of the MN; After the target MAG, the target MAG carries the multicast status information of the MN to the LMA in the binding acknowledgement message.
  • the specific method of Embodiment 3 includes the following steps:
  • Step 400 The multicast source sends the multicast message to the MN by optimizing the SPT path. As shown in step 400b, the multicast data is sent through the tunnel between the MAG and the P-MAG.
  • Step 401 The MN leaves the current mobile access gateway P-MAG, and the P-MAG sends a deregistration De-Reg (De-Registration) binding update message with a lifetime time of zero to the LMA.
  • the present invention increases the message by adding The new mobility option carries the multicast status information of the MN, and the content of the multicast status information is the same as step 203.
  • Step 402 After receiving the De-Reg message from the P-MAG, the LMA saves the multicast state information carried in the message to the corresponding binding cache entry BCE.
  • Step 403 The LMA sends a binding acknowledgement message to the P-MAG as a confirmation of the De-Reg message.
  • Step 404 The MN switches to the new mobile access gateway N-MAG, and the N-MAG sends a binding update message PBU to the LMA.
  • Step 405 The LMA updates the local binding cache entry BCE, and carries the multicast state information saved in the BCE in the PBA message and sends the information to the N-MAG, and deletes the information from the local BCE.
  • the processing flow of the steps 406 to 414 is the same as the processing flow of the steps 305 to 313, and details are not described herein again.
  • the multicast receiver MN when the multicast receiver MN switches to the new mobile access gateway N-MAG, the optimized SPT path is quickly established, and the path passes through the router.
  • the multicast routing entries are generated in the forwarding table.
  • the target MAG obtains the multicast status information of the MN from the LMA to which the source MAG belongs by using the extended binding acknowledgement message, and specifically includes: the group that is controlled by each MAG that is controlled by the LMA
  • the multicast listener that is sent by the receiving end actively discovers the report message or triggers the multicast receiving end of the multicast receiver to send the multicast listener discovery report message, and obtains the multicast receiver according to the multicast listener discovery report message.
  • the multicast status information is sent to the LMA to send a registration message carrying the multicast status information of the multicast receiving end, where the LMA stores the multicast status information of each multicast receiving end; after the MN switches to the target MAG, the The target MAG sends a binding acknowledgement message to the LMA to carry the multicast status information of the MN.
  • FIG. 5a shows the flow of the MN registering multicast status information with the LMA.
  • the MAG-MN refers to the mobile access gateway of the MN, and includes the following steps:
  • Step 500 The MAG-MN periodically sends an MLD query message to learn the multicast listening state of the neighboring interface.
  • the MN sends an MLD report message to the MAG-MN to report the current multicast listening state, or actively forwards the MAG to the MAG.
  • the MN sends an MLD report message to report the current multicast listening status.
  • Step 501 The MAG-MN obtains the multicast status information of the MN according to the MLD 4.
  • the content of the multicast status information is the same as that of step 203, and the MAG-MN sends a registration message to register the multicast of the MN with the LMA.
  • State information and define a new mobility option to carry the multicast status information and the multicast status registration flag of the MN, where the registration message carries the new mobility option, and the registration message may be a PBU message (carrying the multicast status information option) And the multicast status registration flag option), or a newly defined mobile header message (with multicast status information option).
  • Step 502 After receiving the registration message, the LMA sends a registration response message to the MAG-MN.
  • the book response message may be a PBA message (multicast status registration flag option, copied from the PBU message) or a newly defined mobile header message.
  • the LMA saves the multicast status information of the MN in the registration message.
  • the multicast status information of all multicast receivers in the PMIPv6 domain is saved on the LMA.
  • Step 500 The multicast source sends a multicast message to the MN by optimizing the SPT path, as shown in step 500b, the multicast data passes through the MAG and The tunnel between the P-MAGs is sent.
  • Step 501 The MN switches to the new mobile access gateway N-MAG, and the N-MAG sends a binding update message PBU to the LMA.
  • Step 502 The LMA updates the local binding cache entry BCE, and sends a PBA message to the N-MAG.
  • the extended PBA message carries the multicast status information option, and the multicast status information option carries the multicast of the MN saved in the BCE. status information.
  • the multicast state information of all multicast receivers MN in the domain is uniformly managed by the LMA.
  • the N-MAG quickly obtains the current multicast of the MN from the LMA. Status information, and then quickly establish an optimized SPT path.
  • the routers that the path passes through generate corresponding multicast routing entries in its forwarding table.
  • the MN can quickly receive multicast data by optimizing the SPT path after the handover occurs. The multicast handover delay and handover packet loss are reduced, and the multicast forwarding efficiency is improved.
  • the old SPT path must be pruned.
  • the P-MAG is the mobile access gateway before the MN handover
  • the MAG is the mobile access gateway of the multicast source.
  • Step 600 The P-MAG sends a PIM Prune prune message to the MAG through the multicast tunnel.
  • Step 602 After receiving the PIM Prune message, the MAG searches for a local multicast routing item, and updates the group.
  • the outbound interface list of the routing entry is deleted from the outbound interface list and removed from the P-MAG multicast tunnel.
  • the MN is the last multicast listener on the P-MAG that receives the multicast data from the multicast source MN-S, and the old multicast forwarding path (that is, the group between the P-MAG and the MAG) Broadcast tunneling) performs pruning processing to ensure efficient transmission of multicast data.
  • the above embodiment of the present invention is directed to the scenario of ⁇ , and uses MLDv2 to perform IPv6 multicast group member management.
  • the solution is also applicable to the scenario of proxying mobile IPv4, and can be implemented by a person skilled in the art according to the technical solution in the embodiment of the present invention and combined with the prior art solutions in the field.
  • the mobile node in the proxy mobile IPv6 joins the multicast group using MLDv2
  • the mobile node in the proxy mobile IPv4 joins the multicast group using IGMPv3.
  • the system for establishing an optimized path in the multicast receiving end handover scenario corresponding to the foregoing method includes a multicast receiving end (MN), a target mobile access gateway (MAG) of the MN, a source MAG of the MN, and a source MAG of the MN.
  • MN multicast receiving end
  • MAG target mobile access gateway
  • LMA Local Mobile Anchor Point
  • the target MAG is set as: a local mobile anchor from the source MAG of the MN or the source MAG of the MN.
  • Point (LMA) knows the multicast status information of the MN, and establishes a multicast tunnel with the MAG to which the multicast source (MN-S) of the MN belongs according to the multicast status information of the MN;
  • the MAG is set to establish a multicast tunnel with the target MAG of the MN, and send the multicast message of the MN-S to the target MAG of the MN through the multicast tunnel.
  • the multicast status information of the MN includes multicast listener discovery status information and multicast source information, and the multicast listener discovery status information includes a multicast address and a multicast source address list, where the multicast source information includes The address of the multicast source that allows multicast data to be sent to the MN in the multicast source address list, and the MAG address, that is, the address of the MAG to which the multicast source is connected.
  • the target MAG is further configured to: after the multicast tunnel is established, create or update a multicast routing entry for each channel to which the MN belongs according to the multicast listener discovery status information of the MN, and The multicast tunnel interface to the MAG to which the MN-S belongs is set as the inbound interface of each multicast routing entry.
  • the target MAG is further configured to: after the multicast tunnel is established, send, by using the multicast tunnel, a protocol-independent multicast join message to the MAG to which the MN-S belongs to declare to join each channel to which the MN belongs;
  • the MAG to which the MN-S belongs is further configured to create or update a multicast routing entry of the corresponding channel according to the channel information in the protocol-independent multicast join message, and add a tunnel interface to the target MAG to the multicast. In the outbound interface list of the routing entry.
  • the target MAG is configured to establish a multicast tunnel by: sending a multicast tunnel setup message to the MAG to which the MN-S belongs according to the multicast source information in the multicast state information, and receiving the multicast tunnel establishment After the response message, the multicast tunnel end node of the MAG to which the MN-S belongs is established;
  • the MAG to which the MN-S belongs is set to establish a multicast tunnel by: after receiving the multicast tunnel setup message, sending a multicast tunnel setup response message to the target MAG, and establishing a multicast to the target MAG. Tunnel end node.
  • the mobile access gateway in this solution includes a multicast processing module.
  • the function of this module is the same as that of the mobile access gateway described in the above method. E.g:
  • the multicast processing module is configured to: obtain, by the local mobile access gateway (MAG), the local mobile anchor point (LMA) of the multicast receiving genus, the multicast status information of the MN, according to the multicast status information of the MN. Establishing a multicast tunnel with the MAG to which the multicast source (MN-S) of the MN belongs, and when the associated MAG is the MAG to which the multicast source (MN-S) of the MN belongs, the MN-S The multicast message is sent to the target MAG of the target through a multicast tunnel with the target MAG of the MN.
  • MAG local mobile access gateway
  • LMA local mobile anchor point
  • the multicast status information of the MN includes multicast listener discovery status information and multicast source information, and the multicast listener discovery status information includes a multicast address and a multicast source address list, where the multicast source information includes The address of the multicast source in the multicast source address list that allows multicast data to be sent to the MN.
  • the MAG address is also the address of the MAG to which the multicast source is connected.
  • the multicast processing module is further configured to: when the associated MAG is the target MAG of the MN, after the multicast tunnel is established, the multicast listener discovers the status information according to the multicast status information of the MN as Each channel to which the MN belongs creates or updates a multicast routing entry, and sets the multicast tunnel interface of the target MAG to the MAG to which the MN-S belongs to an inbound interface of each multicast routing entry.
  • the multicast processing module is further configured to: when the associated MAG is the target MAG to which the MN belongs, after the multicast tunnel is established, the multicast tunnel is not related to the MAG transmission protocol to which the MN-S belongs.
  • Multicast join message to declare to join the respective channels; and, when the belonging MAG is the MAG to which the MN-S belongs, create or update the multicast of the corresponding channel according to the channel information in the received protocol-independent multicast join message.
  • the routing entry adds the tunnel interface of the MAG to which the MN-S belongs to the destination MAG to the outbound interface list of the multicast routing entry.
  • the execution mode of the multicast processing module is the same as that in the above method, and the description is not repeated here.
  • the method for establishing an SPT path provided by the embodiment of the present invention can improve routing efficiency and performance of mobile multicast in a handover process of a multicast receiving end.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种在组播接收端切换场景下建立优化路径的方法及系统，该方法包括：组播接收端（MN）的目标移动接入网关（MAG）从所述 MN的源MAG或所述MN的源MAG所属的本地移动锚点（LMA）获知所述MN的组播状态信息，根据所述MN的组播状态信息与所述MN的组播源（MN-S）所属的MAG建立组播隧道，所述MN-S所属的MAG将所述MN-S的组播报文通过所述组播隧道发送至所述MN的目标MAG。本方案提供的建立SPT路径的方法可以提高组播接收端切换过程中的路由效率和移动组播的性能。

Description

在组播接收端切换场景下建立优化路径的方法及系统
技术领域
本发明涉及移动通信领域， 尤其涉及在组播接收端切换场景下建立优化 路径的方法及系统。
背景技术
组播的出现是为了解决传统单播路由在处理组通信时出现的效率问题。 随着无线和移动技术的发展， 在移动过程中获取组播服务成为了一个研究热 点,移动组播由传统固定组播发展而来， 为移动用户提供诸如移动视频会议、 移动在线游戏等多种应用， 可有效提高数据传输效率。 移动组播需要解决两 个基本问题:一是组成员关系管理， 二是组成员位置管理。 当前组成员关系管 理一般釆用 Internet组管理协议 IGMP (全称为 Internet Group Management Protocol,简称）/组播监听者发现协议 MLD(全称为 Multicast Listener Discovery Protocol )等协议， 而组成员位置管理则釆用移动 IP等移动性管理协议。
IP 组播业务模型分为两种： 任意源组播 ASM (全称为 Any-Source Multicast )和特定源组播 SSM (全称为 Source-Specific Multicast ) 。 ASM模 型使用一个组播组地址 G来标识一个组播组， 每个组播组可以有任意多个组 播源和接收者， 需要利用汇集点（RP, 全称为 Rendezvous Point )进行共享树 ( RPT , 全称为 Rendezvous Point Tree )的建立， 并且通过组播源注册机制建 立最短路径树 SPT (全称为 Shortest Path Tree ) ； SSM和 MLDv2/IGMPv3相 结合， 使用组播组地址 G和组播源地址 S来标识一个组播会话， 也称为一个 频道， 每个频道只能有一个指定源和任意多个接收者， 在 SSM模型中不需要 选择汇集点 RP和维护共享树（RPT ) , 不需要进行组播源注册， 从而在网络 内直接构建以组播源 S为根、以接收者为叶子的 SPT,省去了 ASM模型中先 建立共享树再从共享树向最短路径树切换的过程， 从而能够从一开始就沿最 短路径树转发数据。 和 ASM比较， SSM是一种简单有效的组播模型， 它可 以克服 ASM在访问控制、 地址分配、 源发现、 易于遭受 DoS攻击等方面的 缺陷， 因此 SSM模型具有更强的可扩展性， 可以提高网络性能， 在未来的 Internet中具备更加广泛的应用前景。
为了处理同一路由器在不同接口上收到来自不同对端的相同组播信息， 需要对组播报文的入接口进行逆向路径转发 RPF (全称为 Reverse Path Forwarding )检查， 以决定转发还是丟弃该报文。 在 SSM模型中， RPF检查 的过程是： 接收组播报文的路由器以组播源的 IP地址为目的地址查找单播路 由表， 对应表项中的出接口为 RPF接口， 路由器认为由该 RPF接口接收到 的组播报文所经历的路径是从组播源到本地的最短路径， 将 RPF接口与组 播报文实际到达的接口相比较， 如果两接口相一致， 那么就认为这个组播包 是从正确路径而来， RPF检查成功； 如果两接口不一致， 将该组播报文丟弃。 作为路径判断依据的单播路由信息可以来源于任何一种单播路由协议、 组播 静态路由或者 MBGP路由协议。
对于移动组播， IETF在 MULTIMOB工作组致力于研究基于 PMIPv6的 移动组播机制， 目前提出了一种基本解决方案， 下面结合附图介绍该方案的 实现过程， 如图 la, 组播接收者 MN和组播源 MN-S(MN-Source)位于同一个 ΡΜΙΡνό域 , 组播接收者 ΜΝ当前连接在移动接入网关 P-MAG上 , MN-S连 接在移动接入网关 MAG上， MN和 MN-S的拓朴锚点可以是同一个 LMA也 可以是不同的 LMA。 在 SSM模型下， MN通过 MLDv2报告报文向 P-MAG 报告自己需要接收来自组播源 MN-S、 发往组播组 G的组播数据。 P-MAG 收到 MLDv2 Report 文后， 向组播源 MN-S 逐跳发送频道订阅 4艮文（由 P-MAG发往 LMA的订阅 文需要进行隧道封装，由 LMA发往 MAG的订阅 报文也需要进行隧道封装）， 沿途所有路由器都创建（HoA, G )组播路由项， HoA代表组播源 MN-S的地址， G代表组播地址， 从而构建以组播源 MN-S 为根， 以组播接收者 MN为叶子的 SPT路径， 从组播源 MN-S所属的 MAG 到 LMA的路径是 PMIPv6隧道， 从 LMA到 MN所属的 P-MAG的路径是 ΡΜΙΡνό隧道，随后组播源 MN-S发出的组播数据沿着已建好的 SPT到达 ΜΝ , 组播转发路径如图 la的 100a所示。当 MN切换到新的移动接入网关 N-MAG, 通过以上过程建立新的 SPT路径， 如图 la的 101a所示， 从组播源 MN-S所 属的 MAG到 LMA的路径是 PMIPv6隧道， 从 LMA到 MN所属的 N-MAG 的路径是 PMIPv6隧道。 以上解决方案， 由 MN-S发往 MN的组播报文必须先通过 MN-S的移动 接入网关 MAG和本地移动锚点 LMA之间的 PMIPv6隧道进行发送， 组播报 文到达 MN的移动锚点 LMA后，必须通过 LMA和 MN的移动接入网关之间 的 PMIPv6隧道进行发送， 所以图 la所示 SPT路径 100a和 101a都不是最短 的组播转发路径， 降低了组播路由的效率。 并且当 MN发生切换时， N-MAG 需要与 MN进行 MLD查询 /报告报文的交互过程获知 MN当前的组播监听状 态， 并通过组播路由协议向组播源 MN-S逐跳发送频道订阅 文来重建组播 转发树， 由于组播组成员状态和组播树分支的调整往往需要花费较长时间， 因此 MN的切换延时较大， 切换丟包问题也比较严重。 因此， 目 前基于 ΡΜΙΡνό所提出的移动组播解决方法不可避免的造成了非最短 SPT路径以及 组播切换延时和丟包， 降低了路由效率和移动组播的性能。
发明内容
本发明实施方式提供一种在组播接收端切换场景下建立优化路径的方法 及系统， 解决相关方案中组播接收端切换场景下非最短 SPT路径造成的路由 效率低的问题。
为了解决上述技术问题， 本发明提供了在组播接收端切换场景下建立优 化路径的方法， 包括：
组播接收端（ ΜΝ )的目标移动接入网关（ MAG )从所述 MN的源 MAG 或所述 MN的源 MAG所属的本地移动锚点 （ LMA )获知所述 MN的组播状 态信息， 根据所述 MN的组播状态信息与所述 MN的组播源 （MN-S )所属 的 MAG建立组播隧道，所述 MN-S所属的 MAG将所述 MN-S的组播 文通 过所述组播隧道发送至所述 MN的目标 MAG。
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址以 及该组播源连接的 MAG的地址。
该方法还包括： 所述组播隧道建立后， 所述目标 MAG根据所述 MN的 组播状态信息中的组播监听者发现状态信息为所述 MN所属的各频道创建或 更新组播路由项 , 并将至所述 MN-S所属的 MAG的组播隧道接口设置为各 组播路由项的入接口。
该方法还包括： 所述组播隧道建立后， 所述目标 MAG通过所述组播隧 道向所述 MN-S所属的 MAG发送协议无关组播加入消息以声明加入所述 MN 所属的各频道， 所述 MN-S所属的 MAG根据所述协议无关组播加入消息中 的频道信息创建或更新相应频道的组播路由项， 并将至所述目标 MAG的隧 道接口添加到此组播路由项的出接口列表中。
所述 MN-S所属的 MAG将所述 MN-S的组播 4艮文通过所述组播隧道发 送至所述 MN的目标 MAG的步骤包括：
所述 MN-S所属的 MAG收到所述 MN-S发送的组播 文后， 向所维护 的组播路由项的出接口列表中的所有组播隧道接口发送所述组播报文。
该方法还包括： 所述目标 MAG通过所述组播隧道收到组播 文后， 判 断收到组播报文的组播隧道接口是组播路由项中的入接口时， 向所述组播路 由项的出接口列表中的所有出接口转发该组播报文。
建立组播隧道的方法包括：
所述目标 MAG根据所述组播状态信息中的组播源信息向所述 MN-S所 属的 MAG发送组播隧道建立消息，所述 MN-S所属的 MAG向所述目标 MAG 发送组播隧道建立应答消息， 并建立到所述目标 MAG的组播隧道端节点， 所述目标 MAG建立到所述 MN-S所属的 MAG的组播隧道端节点 ,组播隧道 建立完成。
所述目标 MAG获知所述 MN的组播状态信息的步骤中， 所述目标 MAG 通过扩展的切换发起消息从所述源 MAG获知所述 MN的组播状态信息， 包 括： 所述 MN向源接入网上报所述 MN的标识以及目标接入网标识 , 所述源 接入网向所述源 MAG发送携带 MN的标识以及目标接入网标识的切换指示 信息，所述源 MAG根据所述目标接入网标识确定所述目标 MAG的地址， 向 所述目标 MAG发送扩展的切换发起消息，在此切换发起消息中携带所述 MN 的组播状态信息。
所述目标 MAG获知所述 MN的组播状态信息的步骤中， 所述目标 MAG 通过扩展的切换确认消息从所述源 MAG获知所述 MN的组播状态信息， 包 括： 所述 MN经由目标接入网与所述目标 MAG建立连接后， 所述目标 MAG 向源 MAG发送切换发起消息， 源 MAG向目标 MAG返回扩展的切换确认消 息时， 在此切换确认消息中携带所述 MN的组播状态信息。
所述目标 MAG获知所述 MN的组播状态信息的步骤中，所述目标 MAG 通过扩展的绑定确认消息从所述源 MAG所属的 LMA获知所述 MN的组播状 态信息， 包括：
所述 MN离开所述源 MAG后，所述源 MAG向所属的 LMA发送扩展的 \%m注册绑定更新消息，在此消息中携带所述 MN的组播状态信息，所述 LMA 保存所述 MN的组播状态信息； 所述 MN切换到所述目标 MAG后， 所述目 标 MAG向所述 LMA发送绑定更新消息， 所述 LMA向所述目标 MAG返回 扩展的绑定确认消息， 在此绑定确认消息中携带所述 MN的组播状态信息。
所述目标 MAG获知所述 MN的组播状态信息的步骤中，所述目标 MAG 通过扩展的绑定确认消息从所述源 MAG所属的 LMA获知所述 MN的组播状 态信息， 包括：
所述 LMA管辖的各 MAG接收所管辖的组播接收端主动发送的组播监听 者发现报告报文或者触发所管辖的组播接收端发送组播监听者发现报告报 文， 根据所述组播监听者发现报告报文获知组播接收端的组播状态信息， 向 所述 LMA发送携带组播接收端的组播状态信息的注册消息， 所述 LMA保存 各组播接收端的组播状态信息； 所述 MN切换到所述目标 MAG后， 所述目 标 MAG向所述 LMA发送绑定更新消息， 所述 LMA向所述目标 MAG返回 扩展的绑定确认消息， 在此绑定确认消息中携带所述 MN的组播状态信息。
该方法还包括：所述 MN是所述源 MAG上最后一个接收来自所述 MN-S 的组播数据的组播监听者时，所述 MN切换入所述目标 MAG后，所述源 MAG 向所述 MN-S所属 MAG发送声明退出以所述组播源的地址为目标地址的剪 枝消息， 并删除所述 MN-S对应的组播路由项， 拆除到所述 MN-S所属 MAG 的组播隧道， 所述 MN-S所属 MAG更新维护的组播路由项的出接口列表， 将接收剪枝消息的隧道接口从所述出接口列表中删除，并拆除到所述源 MAG 的组播隧道。 本发明实施方式还提供一种在组播接收端切换场景下建立优化路径的系 统， 包括组播接收端（ MN ) , MN的目标移动接入网关（ MAG ) , MN的源 MAG, MN的源 MAG所属的本地移动锚点（ LMA ) 以及所述 MN的组播源 ( MN-S )所属的 MAG; 其中
属的 LMA获知所述 MN的组播状态信息， 根据所述 MN的组播状态信息与 所述 MN-S所属的 MAG建立组播隧道；
所述 MN-S所属的 MAG设置为与所述 MN的目标 MAG建立组播隧道， 并将所述 MN-S的组播 ^艮文通过所述组播隧道发送至所述 MN的目标 MAG。
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址以 及该组播源连接的 MAG的地址。
所述目标 MAG还设置为： 在所述组播隧道建立后， 根据所述 MN的组 播监听者发现状态信息为所述 MN所属的各频道创建或更新组播路由项， 并 将至所述 MN-S所属的 MAG的组播隧道接口设置为各组播路由项的入接口。
所述目标 MAG还设置为在所述组播隧道建立后， 通过所述组播隧道向 所述 MN-S所属的 MAG发送协议无关组播加入消息以声明加入所述 MN所 属的各频道；
所述 MN-S所属的 MAG还设置为根据所述协议无关组播加入消息中的 频道信息创建或更新相应频道的组播路由项， 并将至所述目标 MAG的隧道 接口添加到此组播路由项的出接口列表中。 所述目标 MAG是设置为通过如下方式建立组播隧道： 根据所述组播状 态信息中的组播源信息向所述 MN-S所属的 MAG发送组播隧道建立消息， 在收到组播隧道建立应答消息后， 建立到所述 MN-S所属的 MAG的组播隧 道端节点；
所述 MN-S所属的 MAG是设置为通过如下方式建立组播隧道： 收到组 播隧道建立消息后， 向所述目标 MAG发送组播隧道建立应答消息， 并建立 到所述目标 MAG的组播隧道端节点。
本发明实施方式还提供一种移动接入网关， 包括组播处理模块， 所述组播处理模块设置为： 在所属移动接入网关（MAG )作为组播接收 属的本地移动锚点（LMA )获知所述 MN的组播状态信息， 根据所述 MN的 组播状态信息与所述 MN的组播源（ MN-S )所属的 MAG建立组播隧道， 以 及， 在所属 MAG作为所述 MN的组播源 （ MN-S )所属的 MAG时， 将所述 MN-S的组播 文通过与所述 MN的目标 MAG之间的组播隧道发送至所述 匪的目标 MAG„
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址以 及该组播源连接的 MAG的地址。
所述组播处理模块还设置为： 在所属 MAG作为所述 MN的目标 MAG 时， 在所述组播隧道建立后， 根据所述 MN的组播状态信息中的组播监听者 发现状态信息为所述 MN所属的各频道创建或更新组播路由项， 将所述目标 MAG至所述 MN-S所属的 MAG的组播隧道接口设置为各组播路由项的入接 口。 所述组播处理模块还设置为在所属 MAG作为所述 MN所属的目标 MAG 时， 在所述组播隧道建立后， 通过所述组播隧道向所述 MN-S所属的 MAG 发送协议无关组播加入消息以声明加入所述 MN所属的各频道； 以及， 在所 属 MAG作为所述 MN-S所属的 MAG时，根据收到的协议无关组播加入消息 中的频道信息创建或更新相应频道的组播路由项， 并将所述 MN-S 所属的 MAG至所述目标 MAG的隧道接口添加到此组播路由项的出接口列表中。
本方案提供的建立 SPT路径的方法可以提高组播接收端切换过程中的路 由效率和移动组播的性能。 附图概述
图 la为相关技术中在 PMIPv6域中进行组播切换的场景示意图； 图 lb为实施例中组播接收者 MN在 PMIPv6域内发生切换的场景示意图； 图 2为具体实施例一中组播接收者切换时快速建立优化 SPT路径的方法 流程图；
图 3为具体实施例二中组播接收者切换时快速建立优化 SPT路径的方法 流程图；
图 4为具体实施例三中组播接收者切换时快速建立优化 SPT路径的方法 流程图；
图 5a为具体实施例四的组播接收者向 LMA注册组播状态信息的方法流 程图；
图 5b为具体实施例四的组播接收者切换时快速建立优化 SPT路径的方 法流程图；
图 6是实施例中对组播转发路径进行剪枝处理的方法流程图。
本发明的较佳实施方式
在组播接收端切换场景下建立优化路径的方法包括： 组播接收端 （MN ) 的目标移动接入网关 （ MAG )从所述 MN的源 MAG或所述 MN的源 MAG 所属的本地移动锚点 （LMA )获知所述 MN的组播状态信息， 根据所述 MN 的组播状态信息与所述 MN的组播源 （ MN-S )所属的 MAG建立组播隧道， 所述 MN-S所属的 MAG将所述 MN-S的组播 文通过所述组播隧道发送至 所述 MN的目标 MAG。
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址， 还包括 MAG地址即所述组播源连接的 MAG的地址。
如图 lb为组播接收者 MN在 PMIPv6域内切换时的场景图， P-MAG是 MN切换前的移动接入网关， N-MAG是 MN切换后的移动接入网关， MAG 是组播源 MN-S的移动接入网关， 图中画出了一组组播源 MN-S和一组移动 接入网关 MAG。
MN切换前， MN通过 MLDv2报告报文向 P-MAG报告自己需要接收来 自组播源 MN-S、 发往组播组 G的组播数据。 P-MAG收到 MLDv2 Report报 文后 ,根据组播源地址 HoA向 LMA查询 MAG的地址信息 , 建立 P-MAG和 MAG之间的隧道， P-MAG通过隧道向组播源 MN-S发送频道订阅报文， 沿 途的路由器都创建（HoA, G )组播路由项， HoA代表组播源 MN-S的地址， G代表组播地址， 从而构建以组播源 MN-S为根， 以组播接收者 MN为叶子 的优化的 SPT路径， 如图 lb的 100b所示。
根据本方案， 当 MN发生切换时快速建立优化 SPT路径的方法流程， 优 化后的 SPT路径如图 lb的 101b所示。
上述方法中， 所述组播隧道建立后， 所述目标 MAG根据所述 MN的组 播状态信息中的组播监听者发现状态信息为所述 MN所属的各频道创建或更 新组播路由项，将所述目标 MAG至所述 MN-S所属的 MAG的组播隧道接口 设置为各组播路由项的入接口。
所述组播隧道建立后， 所述目标 MAG通过所述组播隧道向所述 MN-S 所属的 MAG发送协议无关组播加入消息以声明加入所述各频道，所述 MN-S 所属的 MAG根据所述协议无关组播加入消息中的频道信息创建或更新相应 频道的组播路由项，将所述 MN-S所属的 MAG至所述目标 MAG的隧道接口 添加到此组播路由项的出接口列表中。
所述 MN-S所属的 MAG收到所述 MN-S发送的组播 文后， 向所维护 的组播路由项的出接口列表中的所有组播隧道接口发送所述组播报文。
所述目标 MAG通过所述组播隧道收到组播 文后， 判断收到组播 "^文 的组播隧道接口是组播路由项中的入接口时， 向组播路由项的出接口列表中 的所有出接口转发。
建立组播隧道的方法包括： 所述目标 MAG根据所述组播状态信息中的 组播源信息向所述 MN-S所属的 MAG发送组播隧道建立消息， 所述 MN-S 所属的 MAG向所述目标 MAG发送组播隧道建立应答消息，并建立到所述目 标 MAG的组播隧道端节点， 所述目标 MAG建立到所述 MN-S所属的 MAG 的组播隧道端节点， 组播隧道建立完成。
下面通过多个实施例进行说明。
实施例一
本实施例一中， 所述目标 MAG通过扩展的切换发起消息从所述源 MAG 获知所述 MN 的组播状态信息， 具体包括： 所述 MN向源接入网上报所述 MN的标识以及目标接入网标识 ,所述源接入网向所述源 MAG发送携带 MN 的标识以及目标接入网标识的切换指示信息， 所述源 MAG根据所述目标接 入网标识确定所述目标 MAG的地址，向所述目标 MAG发送扩展的切换发起 消息， 在此切换发起消息中携带所述 MN的组播状态信息。
参考图 2, 实施例一的具体实现方法包括以下步骤：
步骤 200, 组播源通过优化 SPT路径向 MN发送组播报文， 如步骤 200b 所示组播数据通过 MAG和 P-MAG之间的隧道进行发送。
步骤 201 , MN检测到自己需要进行 MAG切换， 将自己的 ID和新的接 入点标识 AP-ID报告给源接入网络 P-AN (即 MN切换前的接入网络)， AP-ID 的获取与具体的接入技术相关， 本方案不讨论。
步骤 202, P-AN收到来自 MN的艮告消息后，向源移动接入网关 P-MAG 发送切换指示消息， 消息中也携带 MN-ID和新的接入点标识 AP-ID。
步骤 203 , P-MAG根据切换指示消息中新的接入点标识 AP-ID获得新的 移动接入网关 N-MAG的地址信息， 并向 N-MAG发出切换发起消息 HI, 在 此消息中携带 MN的组播状态信息。
本方案对切换发起消息 HI进行扩展,使其可以携带 MN的组播状态信息。
MN的组播状态信息包括 MN的 MLD状态信息以及组播源信息。
由于在 PMIPv6 中移动节点与移动接入网关之间是点对点链路， 根据
MLDv2协议， 运行 MLDv2 的组播路由器按每条直连链路上的组播地址来保 持 MLD状态，该 MLD状态包括过滤模式、源列表和定时器信息，所以 P-MAG 为连接 MN的接口维护的 MLD状态即 MN的 MLD状态。 所述 MN的 MLD状态信息包括若干条记录， 每条记录的内容包括（组 播地址 G, 组播源地址列表， 过滤模式） ， 如果过滤模式为 INCLUDE模式， 则组播源地址列表包含 Include List, 即 MN接收 Include List中所有组播源发 送的组播数据， 如果过滤模式为 EXCLUDE模式， 则组播源地址列表包含 Exclude List和 Requested List, MN接收来自 Requested List中所有组播源发 送的组播数据， MN拒绝来自 Exclude List中所有组播源发送的组播数据。
所述组播源信息包括若干条记录， 每条记录的内容包括（组播源地址， MAG地址 ) , 组播源地址即 MN的组播状态信息中 Include List或者 Request List中所包含的组播源地址， MAG地址即组播源连接的移动接入网关地址。
值得说明的是， 所述组播状态信息包含的内容不限于上述字段， 实际应 用中可以根据需要新增其他字段。
步骤 204, N-MAG向 P-MAG发送切换确认消息 HAck,作为对切换发起 消息 HI的确认。
本方案通过定义一对新的移动头消息即代理组播信道消息 PMT ( Proxy Multicast Tunnel )和代理组播信道响应消息 PMTR ( Proxy Multicast Tunnel Reply )作为一对建立组播隧道的消息， 也可以扩展 PBU/PBA消息作为建立 组播隧道的消息。
步骤 205, N-MAG根据 MN的组播状态信息中的 MAG地址向 MAG(即 组播源连接的移动接入网关）发送 PMT消息请求与 MAG建立组播隧道。
步骤 206, MAG收到 PMT消息后， 向 N-MAG发送代理组播隧道建立 应答消息 PMTR, 并建立到 N-MAG的双向隧道的端节点。
步骤 207 , N-MAG收到 PMTR消息后， 建立到 MAG的双向隧道的端节 点 , N-MAG和 MAG之间的双向组播隧道建立完成， 该双向隧道用于承载组 播控制报文和组播数据报文。
步骤 208, N-MAG保存 MN的 MLD状态信息 , 并根据 MN的 MLD状 态信息为 MN所属的各频道创建或更新组播路由项 （可判断不存在相应频道 的组播路由项时， 则创建与相应频道对应的新的组播路由项， 判断存在相应 频道的组播路由项时， 更新此组播路由项）， 并将 N-MAG到 MAG的组播隧 道接口设置为组播路由项的入接口， 由于此时 MN还没有与 N-MAG建立连 接， 出接口列表为空。
步骤 209,N-MAG根据 MN的组播源信息向 MAG发送协议无关组播 PIM ( Protocol Independent Multicast )力口入 ( Join ) 消息， PIM Join消息通过组播 隧道进行封装发送。
步骤 210, MAG收到 PIM Join消息后，根据 PIM Join消息中的频道信息 创建或更新相应组播路由项 , 将接收 PIM Join消息的隧道接口添加到此组播 路由项的出接口列表中。
步骤 211 , MN与新的接入网路 N-AN建立连接。
步骤 212, 新的接入网络 N-AN与新的移动接入网关 N-MAG建立连接。 步骤 213 , N-MAG根据 MN的 MLD状态信息为直连链路 (即 N-MAG 连接 MN的链路 )创建 MLD状态， 并将链路接口添加到相应的组播路由项 (即步骤 208所创建的组播路由项） 的出接口列表中。
步骤 214 , 组播源向组播组 G发送组播 4艮文。
步骤 215, MAG收到组播^艮文后， 查找组播路由项， 向出接口列表中的 所有接口发送组播报文。 由步骤 210可知， 出接口列表中保存了到达 N-MAG 的新的隧道接口， MAG对组播 ^艮文进行隧道封装后发往 N-MAG。
步骤 217, N-MAG对报文进行解封装后， 查找组播路由项， 向出接口列 表中的所有接口发送该组播报文， 最终 MN会收到该组播报文。 步骤 208保 证了 N-MAG接收组播报文的接口与组播路由项中保存的入接口匹配。
本实施例在组播接收者 MN切换到新的移动接入网关 N-MAG前， 预先 建立好优化的 SPT路径， 路径所经过的路由器都在其转发表中生成了相应的 组播路由项，运用本方法， MN能够在发生切换后通过优化 SPT路径快速接 收组播数据， 减小了组播切换时延， 优化了切换后的 SPT路径， 提高了组播 转发效率。 运用 RFC5949定义的 FPMIPv6协议， 针对发起切换的 MN, 预先 在当前所属的 P-MAG和请求切换到的 N-MAG之间建立一条双向隧道， 使 MN在 N-MAG和 MAG之间建立组播隧道之前仍然能够通过 P-MAG和 N-MAG之间的双向隧道持续接收组播数据，从而减小组播切换丟包，具体的 实现细节可以参见 RFC5949的预先式快速切换技术，本实施例不做详细介绍。
实施例二
在本实施例二中， 所述目标 MAG通过扩展的切换确认消息从所述源 MAG获知所述 MN的组播状态信息， 具体包括： 所述 MN经由目标接入网 与所述目标 MAG建立连接后，所述目标 MAG向源 MAG发送切换发起消息， 源 MAG向目标 MAG返回扩展的切换确认消息时，在此切换确认消息中携带 所述 MN的组播状态信息。
如图 3 , 实施例二的具体实现方法包括：
步骤 300, 组播源通过优化 SPT路径向 MN发送组播^艮文， 如步骤 300b 所示组播数据通过 MAG和 P-MAG之间的隧道进行发送。
步骤 301 , MN发生切换， MN与新的接入网路 N-AN建立连接。
步骤 302, 新的接入网络 N-AN与新的移动接入网关 N-MAG建立连接， N-MAG通过 P-AN的 AP-ID获得 P-MAG的地址信息。
步骤 303 , N-MAG向 P-MAG发出一个切换发起消息 ΗΙ。
步骤 304, P-MAG向 N-MAG发送切换确认消息 HAck,扩展 HAck消息， 在消息中携带 MN的组播状态信息， 组播状态信息所包含的内容与步骤 203 相同。
步骤 305, N-MAG根据 MN的组播状态信息中的 MAG地址向 MAG(即 组播源连接的移动接入网关）发送 PMT ( Proxy Multicast Tunnel )消息请求与
MAG建立组播隧道。
步骤 306, MAG收到 PMT消息后， 向 N-MAG发送代理组播隧道建立 应答消息 PMTR ( Proxy Multicast Tunnel Reply ) , 并建立到 N-MAG的双向 隧道的端节点。
步骤 307 , N-MAG收到 PMTR消息后， 建立到 MAG的双向隧道的端节 点 , N-MAG和 MAG之间的双向组播隧道建立完成， 该双向隧道用于承载组 播控制报文和组播数据报文。 步骤 308, N-MAG根据 MN的 MLD状态信息 MN所属的各频道创建或 更新组播路由项 （可判断不存在相应频道的组播路由项时， 则创建与相应频 道对应的新的组播路由项 , 判断存在相应频道的组播路由项时 , 更新此组播 路由项） ， 将 N-MAG到 MAG的组播隧道接口设置为组播路由项的入接口， 并将连接 MN的接口添加到组播路由项的出接口列表中。
步骤 309, N-MAG根据 MN的组播状态信息向 MAG发送 PIM Join消息， PIM Join消息通过组播隧道进行封装发送。
步骤 310, MAG收到 PIM Join消息后，根据所述 PIM Join消息中的频道 信息创建或者是更新相应组播路由项 , 将接收 PIM Join消息的隧道接口添加 到此组播路由项的出接口列表中。
步骤 311 , 组播源向组播组 G发送组播 4艮文。
步骤 312, MAG收到组播^艮文后， 查找组播路由项， 向出接口列表中的 所有接口发送组播报文。 由步骤 310可知， 出接口列表中保存了到达 N-MAG 的新的隧道接口， MAG对组播 ^艮文进行隧道封装后发往 N-MAG。
步骤 313 , N-MAG对报文进行解封装后， 查找组播路由项， 向出接口列 表中的所有接口发送该组播报文， 最终 MN会收到该组播报文。 步骤 308保 证了 N-MAG接收组播报文的接口与组播路由项中保存的入接口匹配。
本实施例在 MN切换到新的移动接入网关 N-MAG的过程中， N-MAG通 过向 P-MAG请求 MN的组播状态信息预先建立好优化的 SPT路径， 路径所 经过的路由器都在其转发表中生成了相应的组播路由项， 运用本方法， MN 能够在发生切换后通过优化 SPT路径快速接收组播数据， 减小了组播切换时 延， 优化了切换后的 SPT路径， 提高了组播转发效率。 运用 RFC5949定义的 FPMIPv6协议，针对发起切换的 MN,预先在当前所属的 P-MAG和请求切换 到的 N-MAG之间建立一条双向隧道，使 MN在 N-MAG和 MAG之间建立组 播隧道之前仍然能够通过 P-MAG和 N-MAG之间的双向隧道持续接收组播数 据， 从而减小组播切换丟包， 具体的实现细节可以参见 RFC5949的反应式快 速切换技术， 本实施例不做详细介绍。 实施例三
本实施例三中， 所述目标 MAG通过扩展的绑定确认消息从所述源 MAG 所属的 LMA获知所述 MN的组播状态信息， 具体包括： 所述 MN离开所述 源 MAG后，所述源 MAG向所属的 LMA发送扩展的 4敦销注册绑定更新消息， 在此消息中携带所述 MN的组播状态信息， 所述 LMA保存所述 MN的组播 状态信息； 所述 MN切换到所述目标 MAG后， 所述目标 MAG向所述 LMA 在此绑定确认消息中携带所述 MN的组播状态信息。
如图 4, 实施例三的具体方法包括以下步骤：
步骤 400, 组播源通过优化 SPT路径向 MN发送组播^艮文， 如步骤 400b 所示组播数据通过 MAG和 P-MAG之间的隧道进行发送。
步骤 401 , MN离开当前的移动接入网关 P-MAG, P-MAG向 LMA发送 生存时间 lifetime为零的撤销注册 De-Reg ( De-Registration )绑定更新消息， 本发明通过扩展此消息， 增加新的移动选项来携带 MN的组播状态信息， 组 播状态信息所包含的内容与步骤 203相同。
步骤 402 , LMA收到来自 P-MAG的 De-Reg消息后， 将消息中携带的组 播状态信息保存到相应的绑定緩存表项 BCE中。
步骤 403 , LMA向 P-MAG发送绑定确认消息， 作为对 De-Reg消息的确 认。
步骤 404 , MN切换到新的移动接入网关 N-MAG , N-MAG向 LMA发送 绑定更新消息 PBU。
步骤 405, LMA更新本地绑定緩存表项 BCE, 并将该 BCE中保存的组 播状态信息携带在 PBA消息中发送给 N-MAG,并将这些信息从本地 BCE删 除。
步骤 406〜步骤 414的处理流程与步骤 305〜步骤 313的处理流程相同，此 处不再赘述。
本实施例通过扩展绑定更新消息 De-Reg,在组播接收者 MN切换到新的 移动接入网关 N-MAG时， 快速建立优化的 SPT路径， 路径所经过的路由器 都在其转发表中生成了相应的组播路由项， 运用本方法， MN能够在发生切 换后通过优化 SPT路径快速接收组播数据，减小了组播切换时延和切换丟包， 提高了组播转发效率。
实施例四
本实施例四中， 所述目标 MAG通过扩展的绑定确认消息从所述源 MAG 所属的 LMA获知所述 MN的组播状态信息， 具体包括： 所述 LMA管辖的各 MAG接收所管辖的组播接收端主动发送的组播监听者发现报告报文或者触 发所管辖的组播接收端发送组播监听者发现报告报文， 并根据所述组播监听 者发现报告报文获知组播接收端的组播状态信息 ,向所述 LMA发送携带组播 接收端的组播状态信息的注册消息 ,所述 LMA保存各组播接收端的组播状态 信息； 所述 MN切换到所述目标 MAG后， 所述目标 MAG向所述 LMA发送 绑定确认消息中携带所述 MN的组播状态信息。
如图 5a和图 5b, 为实施例四提供的当 MN发生切换时， 快速建立优化
SPT路径的一种方法流程图。
图 5a为 MN向 LMA注册组播状态信息的流程， MAG-MN指 MN的移 动接入网关， 包括以下步骤：
步骤 500 , MAG-MN周期性的发送 MLD查询 4艮文来了解相邻接口的组 播侦听状态， MN向 MAG-MN发送 MLD报告报文来汇报当前的组播监听状 态， 或者主动向 MAG-MN发送 MLD报告报文来汇报当前的组播监听状态。
步骤 501 , MAG-MN根据 MLD 4艮告才艮文， 得到 MN的组播状态信息， 所述组播状态信息包含的内容与步骤 203相同， MAG-MN发送注册消息向 LMA注册 MN的组播状态信息，并定义新的移动选项来携带 MN的组播状态 信息和组播状态注册标志， 注册消息中携带所述新的移动选项， 所述注册消 息可以是 PBU消息（携带组播状态信息选项和组播状态注册标志选项）， 也 可以是新定义的移动头消息 （携带组播状态信息选项） 。
步骤 502, LMA收到注册消息后， 向 MAG-MN发送注册应答消息， 注 册应答消息可以是 PBA消息（组播状态注册标志选项，从 PBU消息中拷贝）， 也可以是新定义的移动头消息。 LMA保存注册消息中的 MN的组播状态信息。
通过以上步骤， LMA上保存了 PMIPv6域内所有组播接收者的组播状态 信息。
图 5b结合图 5a中保存的信息快速建立优化的 SPT路径，包括以下步骤： 步骤 500, 组播源通过优化 SPT路径向 MN发送组播^艮文， 如步骤 500b 所示组播数据通过 MAG和 P-MAG之间的隧道进行发送。
步骤 501 , MN切换到新的移动接入网关 N-MAG, N-MAG向 LMA发送 绑定更新消息 PBU。
步骤 502 , LMA更新本地绑定緩存表项 BCE , 并向 N-MAG发送 PBA消 息， 通过扩展 PBA消息， 携带组播状态信息选项， 组播状态信息选项中携带 该 BCE中保存的 MN的组播状态信息。
步骤 503〜步骤 511的处理流程与步骤 305〜步骤 313相同，此处不再赘述。 本实施例通过 LMA对域内所有组播接收者 MN的组播状态信息进行统 一管理， 当 MN切换到新的移动接入网关 N-MAG时， 由 N-MAG从 LMA快 速获取 MN当前的组播状态信息， 然后快速建立起优化的 SPT路径， 路径所 经过的路由器都在其转发表中生成了相应的组播路由项， 运用本方法 MN能 够在发生切换后通过优化 SPT路径快速接收组播数据， 减小了组播切换时延 和切换丟包， 提高了组播转发效率。
对于实施例一〜实施例四， 当发生切换的 MN是 P-MAG上最后一个接收 来自组播源 MN-S的组播数据的组播监听者时， 必须对老的 SPT路径进行剪 枝， 如图 6所示， P-MAG是 MN切换前的移动接入网关， MAG是组播源的 移动接入网关， 具体步骤如下：
步骤 600 , P-MAG通过组播隧道向 MAG发送 PIM Prune剪枝消息。 步骤 601 , P-MAG删除 MN-S对应的组播路由项， 并拆除到 MAG的组 播隧道。
步骤 602, MAG收到 PIM Prune消息后， 查找本地组播路由项， 更新组 播路由项的出接口列表， 将接收 PIM Prune消息的隧道接口从出接口列表中 删除， 并拆除到 P-MAG的组播隧道。
本实施例针对 MN是 P-MAG上最后一个接收来自组播源 MN-S的组播 数据的组播监听者的情况， 对老的组播转发路径 (即 P-MAG和 MAG之间的 组播隧道）进行剪枝处理， 保证了组播数据的有效传输。
本发明上述实施例针对 ΡΜΙΡνό的场景， 并且运用 MLDv2进行 IPv6组 播组成员管理。 本方案同样适用于代理移动 IPv4的场景， 本领域的技术人员 可以根据本发明实施例中的技术方案， 并结合本领域的现有技术方案即可实 现。 在代理移动 IPv6中的移动节点使用 MLDv2加入组播组， 而在代理移动 IPv4中的移动节点使用 IGMPv3加入组播组。
与上述方法相对应的在组播接收端切换场景下建立优化路径的系统包括 组播接收端 （ MN ) , MN的目标移动接入网关 （ MAG ) , MN的源 MAG, MN的源 MAG所属的本地移动锚点 （LMA ) 以及所述 MN的组播源所属的 MAG„
本系统中 MN所属 MAG和 MN-S所属 MAG的执行方式与上述方法中 相应相同， 例如， 所述目标 MAG设置为： 从所述 MN的源 MAG或所述 MN 的源 MAG所属的本地移动锚点 （LMA )获知所述 MN的组播状态信息， 根 据所述 MN的组播状态信息与所述 MN的组播源（ MN-S )所属的 MAG建立 组播隧道； 所述 MN-S所属的 MAG设置为与所述 MN的目标 MAG建立组播 隧道， 并将所述 MN-S的组播 ^艮文通过所述组播隧道发送至所述 MN的目标 MAG„
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址， 还包括 MAG地址即所述组播源连接的 MAG的地址。
所述目标 MAG还设置为： 在所述组播隧道建立后， 根据所述 MN的组 播监听者发现状态信息为所述 MN所属的各频道创建或更新组播路由项， 并 将至所述 MN-S所属的 MAG的组播隧道接口设置为各组播路由项的入接口。 所述目标 MAG还设置为在所述组播隧道建立后， 通过所述组播隧道向 所述 MN-S所属的 MAG发送协议无关组播加入消息以声明加入所述 MN所 属的各频道；
所述 MN-S所属的 MAG还设置为根据所述协议无关组播加入消息中的 频道信息创建或更新相应频道的组播路由项， 并将至所述目标 MAG的隧道 接口添加到此组播路由项的出接口列表中。 所述目标 MAG设置为通过如下方式建立组播隧道： 根据所述组播状态 信息中的组播源信息向所述 MN-S所属的 MAG发送组播隧道建立消息， 在 收到组播隧道建立应答消息后， 建立到所述 MN-S所属的 MAG的组播隧道 端节点；
所述 MN-S所属的 MAG设置为通过如下方式建立组播隧道： 收到组播 隧道建立消息后， 向所述目标 MAG发送组播隧道建立应答消息， 并建立到 所述目标 MAG的组播隧道端节点。
述。
本方案中移动接入网关， 包括组播处理模块。 此模块的功能与上述方法 中描述的移动接入网关的功能相同。 例如：
所述组播处理模块设置为： 在所属移动接入网关（MAG )作为组播接收 属的本地移动锚点（LMA )获知所述 MN的组播状态信息， 根据所述 MN的 组播状态信息与所述 MN的组播源（ MN-S )所属的 MAG建立组播隧道， 以 及， 在所属 MAG作为所述 MN的组播源 （ MN-S )所属的 MAG时， 将所述 MN-S的组播报文通过与所述 MN的目标 MAG之间的组播隧道发送至所述 匪的目标 MAG„
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址， 还包括 MAG地址即所述组播源连接的 MAG的地址。
所述组播处理模块还设置为： 在所属 MAG作为所述 MN的目标 MAG 时， 在所述组播隧道建立后， 根据所述 MN的组播状态信息中的组播监听者 发现状态信息为所述 MN所属的各频道创建或更新组播路由项， 将所述目标 MAG至所述 MN-S所属的 MAG的组播隧道接口设置为各组播路由项的入接 口。 所述组播处理模块还设置为： 在所属 MAG作为所述 MN所属的目标 MAG时， 在所述组播隧道建立后， 通过所述组播隧道向所述 MN-S 所属的 MAG发送协议无关组播加入消息以声明加入所述各频道；以及，在所属 MAG 作为所述 MN-S所属的 MAG时， 根据收到的协议无关组播加入消息中的频 道信息创建或更新相应频道的组播路由项， 并将所述 MN-S所属的 MAG至 所述目标 MAG的隧道接口添加到此组播路由项的出接口列表中。
组播处理模块的执行方式与上述方法中相应相同， 此处不再重复描述。
需要说明的是， 在不冲突的情况下， 本申请中的实施例及实施例中的特 征可以相互任意组合。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成， 所述程序可以存储于计算机可读存储介质中， 如只读 存储器、 磁盘或光盘等。 可选地， 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地， 上述实施例中的各模块 /单元可以釆用 硬件的形式实现， 也可以釆用软件功能模块的形式实现。 本发明不限制于任 何特定形式的硬件和软件的结合。
工业实用性
与现有技术相比， 本发明实施方式提供的建立 SPT路径的方法可以提高 组播接收端切换过程中的路由效率和移动组播的性能。

Claims

权 利 要 求 书
1、 一种在组播接收端切换场景下建立优化路径的方法， 包括：
组播接收端（ MN )的目标移动接入网关（ MAG )从所述 MN的源 MAG 或所述 MN的源 MAG所属的本地移动锚点 （ LMA )获知所述 MN的组播状 态信息， 根据所述 MN的组播状态信息与所述 MN的组播源 （MN-S )所属 的 MAG建立组播隧道，所述 MN-S所属的 MAG将所述 MN-S的组播 文通 过所述组播隧道发送至所述 MN的目标 MAG。
2、 如权利要求 1所述的方法， 其中，
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址以 及该组播源连接的 MAG的地址。
3、 如权利要求 1所述的方法， 还包括：
所述组播隧道建立后， 所述目标 MAG根据所述 MN的组播状态信息中 的组播监听者发现状态信息为所述 MN所属的各频道创建或更新组播路由 项， 并将至所述 MN-S所属的 MAG的组播隧道接口设置为各组播路由项的 入接口。
4、 如权利要求 1所述的方法， 还包括：
所述组播隧道建立后， 所述目标 MAG通过所述组播隧道向所述 MN-S 所属的 MAG发送协议无关组播加入消息以声明加入所述 MN所属的各频道， 所述 MN-S所属的 MAG根据所述协议无关组播加入消息中的频道信息创建 或更新相应频道的组播路由项， 并将至所述目标 MAG的隧道接口添加到此 组播路由项的出接口列表中。
5、 如权利要求 4 所述的方法， 其中， 所述 MN-S所属的 MAG将所述 MN-S的组播 ^艮文通过所述组播隧道发送至所述 MN的目标 MAG的步骤包 括：
所述 MN-S所属的 MAG收到所述 MN-S发送的组播 文后， 向所维护 的组播路由项的出接口列表中的所有组播隧道接口发送所述组播报文。
6、 如权利要求 3所述的方法， 还包括：
所述目标 MAG通过所述组播隧道收到组播 文后， 判断收到组播 "^文 的组播隧道接口是组播路由项中的入接口时， 向所述组播路由项的出接口列 表中的所有出接口转发该组播报文。
7、 如权利要求 1中所述的方法， 其中， 建立组播隧道的方法包括： 所述目标 MAG根据所述组播状态信息中的组播源信息向所述 MN-S所 属的 MAG发送组播隧道建立消息，所述 MN-S所属的 MAG向所述目标 MAG 发送组播隧道建立应答消息， 并建立到所述目标 MAG的组播隧道端节点， 所述目标 MAG建立到所述 MN-S所属的 MAG的组播隧道端节点 ,组播隧道 建立完成。
8、如权利要求 1至 7中任一权利要求所述的方法，其中，所述目标 MAG 获知所述 MN的组播状态信息的步骤中， 所述目标 MAG通过扩展的切换发 起消息从所述源 MAG获知所述 MN的组播状态信息， 包括： 所述 MN向源 接入网上报所述 MN 的标识以及目标接入网标识 , 所述源接入网向所述源 MAG发送携带 MN 的标识以及目标接入网标识的切换指示信息， 所述源 MAG根据所述目标接入网标识确定所述目标 MAG的地址，向所述目标 MAG 发送扩展的切换发起消息， 在此切换发起消息中携带所述 MN的组播状态信 息。
9、如权利要求 1至 7中任一权利要求所述的方法，其中，所述目标 MAG 获知所述 MN的组播状态信息的步骤中， 所述目标 MAG通过扩展的切换确 认消息从所述源 MAG获知所述 MN的组播状态信息， 包括： 所述 MN经由 目标接入网与所述目标 MAG建立连接后，所述目标 MAG向源 MAG发送切 换发起消息， 源 MAG向目标 MAG返回扩展的切换确认消息时，在此切换确 认消息中携带所述 MN的组播状态信息。
10、如权利要求 1至 7中任一权利要求所述的方法，其中，所述目标 MAG 获知所述 MN的组播状态信息的步骤中， 所述目标 MAG通过扩展的绑定确 认消息从所述源 MAG所属的 LMA获知所述 MN的组播状态信息， 包括： 所述 MN离开所述源 MAG后，所述源 MAG向所属的 LMA发送扩展的 •ί敦销注册绑定更新消息 ,在此消息中携带所述 ΜΝ的组播状态信息 ,所述 LMA 保存所述 ΜΝ的组播状态信息； 所述 ΜΝ切换到所述目标 MAG后， 所述目 标 MAG向所述 LMA发送绑定更新消息， 所述 LMA向所述目标 MAG返回 扩展的绑定确认消息， 在此绑定确认消息中携带所述 MN的组播状态信息。
11、如权利要求 1至 7中任一权利要求所述的方法，其中，所述目标 MAG 获知所述 MN的组播状态信息的步骤中， 所述目标 MAG通过扩展的绑定确 认消息从所述源 MAG所属的 LMA获知所述 MN的组播状态信息， 包括： 所述 LMA管辖的各 MAG接收所管辖的组播接收端主动发送的组播监听 者发现报告报文或者触发所管辖的组播接收端发送组播监听者发现报告报 文， 根据所述组播监听者发现报告报文获知组播接收端的组播状态信息， 向 所述 LMA发送携带组播接收端的组播状态信息的注册消息， 所述 LMA保存 各组播接收端的组播状态信息； 所述 MN切换到所述目标 MAG后， 所述目 标 MAG向所述 LMA发送绑定更新消息， 所述 LMA向所述目标 MAG返回 扩展的绑定确认消息， 在此绑定确认消息中携带所述 MN的组播状态信息。
12、 如权利要求 1至 7中任一权利要求所述的方法， 还包括：
所述 MN是所述源 MAG上最后一个接收来自所述 MN-S的组播数据的 组播监听者时，所述 MN切换入所述目标 MAG后，所述源 MAG向所述 MN-S 所属 MAG发送声明退出以所述组播源的地址为目标地址的剪枝消息， 并删 除所述 MN-S对应的组播路由项， 拆除到所述 MN-S所属 MAG的组播隧道 , 所述 MN-S所属 MAG更新维护的组播路由项的出接口列表， 将接收剪枝消 息的隧道接口从所述出接口列表中删除， 并拆除到所述源 MAG的组播隧道。
13、 一种在组播接收端切换场景下建立优化路径的系统， 包括组播接收 端 （ MN ) , MN的目标移动接入网关 （ MAG ) , MN的源 MAG, MN的源 MAG所属的本地移动锚点（LMA )以及所述 MN的组播源 （MN-S )所属的 MAG; 其中 属的 LMA获知所述 MN的组播状态信息， 根据所述 MN的组播状态信息与 所述 MN-S所属的 MAG建立组播隧道； 所述 MN-S所属的 MAG设置为与所述 MN的目标 MAG建立组播隧道， 并将所述 MN-S的组播 ^艮文通过所述组播隧道发送至所述 MN的目标 MAG。
14、 如权利要求 13所述的系统， 其中，
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址以 及该组播源连接的 MAG的地址。
15、 如权利要求 13所述的系统， 其中，
所述目标 MAG还设置为： 在所述组播隧道建立后， 根据所述 MN的组 播监听者发现状态信息为所述 MN所属的各频道创建或更新组播路由项， 并 将至所述 MN-S所属的 MAG的组播隧道接口设置为各组播路由项的入接口。
16、 如权利要求 14所述的系统， 其中，
所述目标 MAG还设置为在所述组播隧道建立后， 通过所述组播隧道向 所述 MN-S所属的 MAG发送协议无关组播加入消息以声明加入所述 MN所 属的各频道；
所述 MN-S所属的 MAG还设置为根据所述协议无关组播加入消息中的 频道信息创建或更新相应频道的组播路由项， 并将至所述目标 MAG的隧道 接口添加到此组播路由项的出接口列表中。
17、 如权利要求 13至 16中任一权利要求所述的系统， 其中，
所述目标 MAG是设置为通过如下方式建立组播隧道： 根据所述组播状 态信息中的组播源信息向所述 MN-S所属的 MAG发送组播隧道建立消息， 在收到组播隧道建立应答消息后， 建立到所述 MN-S所属的 MAG的组播隧 道端节点；
所述 MN-S所属的 MAG是设置为通过如下方式建立组播隧道： 收到组 播隧道建立消息后， 向所述目标 MAG发送组播隧道建立应答消息， 并建立 到所述目标 MAG的组播隧道端节点。
18、 一种移动接入网关， 包括组播处理模块，
所述组播处理模块设置为： 在所属移动接入网关（MAG )作为组播接收 属的本地移动锚点（LMA )获知所述 MN的组播状态信息， 根据所述 MN的 组播状态信息与所述 MN的组播源（ MN-S )所属的 MAG建立组播隧道， 以 及， 在所属 MAG作为所述 MN的组播源 （ MN-S )所属的 MAG时， 将所述 MN-S的组播 ^艮文通过与所述 MN的目标 MAG之间的组播隧道发送至所述 匪的目标 MAG„
19、 如权利要求 18所述的移动接入网关， 其中，
所述 MN的组播状态信息包括组播监听者发现状态信息和组播源信息， 所述组播监听者发现状态信息包括组播地址和组播源地址列表， 所述组播源 信息包括所述组播源地址列表中允许向 MN发送组播数据的组播源的地址以 及该组播源连接的 MAG的地址。
20、 如权利要求 18所述的移动接入网关， 其中，
所述组播处理模块还设置为： 在所属 MAG作为所述 MN的目标 MAG 时， 在所述组播隧道建立后， 根据所述 MN的组播状态信息中的组播监听者 发现状态信息为所述 MN所属的各频道创建或更新组播路由项， 将所述目标 MAG至所述 MN-S所属的 MAG的组播隧道接口设置为各组播路由项的入接 口。
21、 如权利要求 18所述的移动接入网关， 其中，
所述组播处理模块还设置为在所属 MAG作为所述 MN所属的目标 MAG 时， 在所述组播隧道建立后， 通过所述组播隧道向所述 MN-S所属的 MAG 发送协议无关组播加入消息以声明加入所述 MN所属的各频道； 以及， 在所 属 MAG作为所述 MN-S所属的 MAG时，根据收到的协议无关组播加入消息 中的频道信息创建或更新相应频道的组播路由项， 并将所述 MN-S 所属的 MAG至所述目标 MAG的隧道接口添加到此组播路由项的出接口列表中。
PCT/CN2012/083194 2011-10-19 2012-10-19 在组播接收端切换场景下建立优化路径的方法及系统 WO2013056669A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110318845.1 2011-10-19
CN201110318845.1A CN103067865B (zh) 2011-10-19 2011-10-19 在组播接收端切换场景下建立优化路径的方法及系统

Publications (1)

Publication Number Publication Date
WO2013056669A1 true WO2013056669A1 (zh) 2013-04-25

Family

ID=48110295

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/083194 WO2013056669A1 (zh) 2011-10-19 2012-10-19 在组播接收端切换场景下建立优化路径的方法及系统

Country Status (2)

Country Link
CN (1) CN103067865B (zh)
WO (1) WO2013056669A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111541579A (zh) * 2020-06-19 2020-08-14 深圳市乙辰科技股份有限公司 工业网关控制方法、装置、计算机设备和存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103945452B (zh) * 2014-04-30 2017-07-14 中国科学技术大学 一种分布式移动管理架构下数据传输的方法
CN110351194B (zh) 2018-04-04 2021-03-30 华为技术有限公司 一种组播组创建、组播组加入方法及装置
CN111510964B (zh) * 2019-01-31 2021-09-07 华为技术有限公司 一种通信方法及装置
CN112134776B (zh) * 2019-06-25 2022-08-26 华为技术有限公司 生成组播转发表项的方法和接入网关
CN113938840A (zh) * 2020-07-13 2022-01-14 华为技术有限公司 通信方法和通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179457A (zh) * 2006-11-09 2008-05-14 华为技术有限公司 一种基于本地移动管理域中路由优化的切换方法
WO2010118698A1 (en) * 2009-04-17 2010-10-21 Huawei Technologies Co., Ltd. Apparatus and method for basic multicast support for proxy mobile internet protocol version six (ipv6)
WO2011038635A1 (en) * 2009-10-02 2011-04-07 Huawei Technologies Co.,Ltd. Mobility route optimization in a network having distributed local mobility anchors

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009008464A1 (ja) * 2007-07-12 2009-01-15 Sharp Kabushiki Kaisha 移動ノード、アクセスゲートウェイ、位置管理装置および移動パケット通信システム
CN101940014B (zh) * 2008-02-04 2013-10-23 爱立信电话股份有限公司 用于提供路由优化的方法和设备
CN101594609B (zh) * 2008-05-27 2012-08-08 华为技术有限公司 在不同域间切换时保持会话连续的方法、系统及节点
CN101909276B (zh) * 2009-06-04 2013-01-23 中国移动通信集团公司 一种移动组播切换方法、系统及相关设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179457A (zh) * 2006-11-09 2008-05-14 华为技术有限公司 一种基于本地移动管理域中路由优化的切换方法
WO2010118698A1 (en) * 2009-04-17 2010-10-21 Huawei Technologies Co., Ltd. Apparatus and method for basic multicast support for proxy mobile internet protocol version six (ipv6)
WO2011038635A1 (en) * 2009-10-02 2011-04-07 Huawei Technologies Co.,Ltd. Mobility route optimization in a network having distributed local mobility anchors

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111541579A (zh) * 2020-06-19 2020-08-14 深圳市乙辰科技股份有限公司 工业网关控制方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
CN103067865B (zh) 2017-05-17
CN103067865A (zh) 2013-04-24

Similar Documents

Publication Publication Date Title
US8102792B2 (en) Enabling foreign network multicasting for a roaming mobile node, in a foreign network, using a persistent address
JP3942033B2 (ja) ポイントツーポイントパケット交換向きのネットワークにおけるマルチキャスト方法
US9871718B2 (en) Method and device for registering multicast source and establishing multicast path
KR101216757B1 (ko) 하이브리드 멀티캐스팅 가능하고 비-멀티캐스팅 가능한 ｒａｎｓ를 통한 멀티캐스트 트래픽 흐름을 가능하게 하기 위한 방법
US8385249B2 (en) Apparatus and method for basic multicast support for proxy mobile internet protocol version six (IPv6)
CN101518122A (zh) 组播快速切换
WO2013056669A1 (zh) 在组播接收端切换场景下建立优化路径的方法及系统
EP1400060A2 (en) Multicast in a point-to-point oriented packet-switched telecommunication network
CA2547946C (en) Route-optimised multicast traffic for a mobile network node
WO2012083844A1 (zh) 传输组播数据的方法、组播树的更新方法以及系统和装置
KR20110114662A (ko) 모바일 멀티캐스트 서비스를 위한 고정 네트워크에서 멀티캐스트 백홀 채널들의 셋 업을 보조하기 위한 방법 및 장치
Schmidt et al. Mobile multicast sender support in proxy mobile IPv6 (PMIPv6) domains
Bettstetter et al. Interoperation of Mobile IPv6 and protocol independent multicast dense mode
WO2008154796A1 (fr) Procédé et équipement permettant de commander la transmission de paquets de données de multidiffusion dans la station de base et la passerelle du système wimax
KR20120011803A (ko) 이동 통신 시스템에서 이동 노드에 대한 멀티캐스트 서비스 제공 방법 및 장치
WO2013053334A1 (zh) 一种为组播数据建立优化路径的方法及系统
JP2009017545A (ja) 移動エンティティ通信におけるシームレスなハンドオーバ方法および装置
WO2013056633A1 (zh) 在组播源切换场景下建立优化路径的方法及系统
KR20100047433A (ko) 프록시 모바일 아이피 프로토콜 기반의 멀티캐스트 데이터 전송 방법
Kim et al. Proxy mobile IP extension for mobile multimedia multicast services
Ponnusamy A survey on wired and mobile multicast group membership management protocol
Singh et al. Core based tree multicast (M-CBT) approach in supporting mobility
WO2009026783A1 (fr) Procédé et équipement pour commander un nœud mobile dans un réseau de communication communiquant avec un réseau hétérogène
Namee et al. Designing a Protocol to Support Multicast Mobility in IPv6 Network
Gao et al. RFC 7287: Mobile Multicast Sender Support in Proxy Mobile IPv6 (PMIPv6) Domains

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

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

Country of ref document: EP

Kind code of ref document: A1