CN106059925B - Multicast processing method and equipment - Google Patents
Multicast processing method and equipment Download PDFInfo
- Publication number
- CN106059925B CN106059925B CN201610310493.8A CN201610310493A CN106059925B CN 106059925 B CN106059925 B CN 106059925B CN 201610310493 A CN201610310493 A CN 201610310493A CN 106059925 B CN106059925 B CN 106059925B
- Authority
- CN
- China
- Prior art keywords
- multicast address
- main link
- multicast
- message
- link
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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
-
- 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/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
Abstract
The embodiment of the application provides a multicast processing method and equipment. The method is applied to the access stratum equipment and comprises the following steps: receiving a report message from a base station; the report message carries a multicast address; according to the multicast address, inquiring in a mapping relation between a pre-established multicast address and a main link to obtain a target main link corresponding to the multicast address; and sending the report message through the target main link. The embodiment of the application can realize the sharing of the uplink load of the main link.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a multicast processing method and device.
Background
Multicast is a transmission technology for realizing point-to-multipoint, and has the capability of sending the same data to a plurality of sites at a time in an IP (Internet Protocol, Protocol for interconnecting networks), so that the network bandwidth of a backbone network can be saved, and the network load can be reduced. Therefore, the multicast technology has been widely applied to value-added services such as video on demand, IPTV, video conference, distance education, internet radio, internet games, and the like.
An IP Radio Access Network (IP-based Radio Access Network) is an overall solution for a router/switch that is optimized and customized for an IP-based base station backhaul application scenario. Generally, an ip ran networking is divided into three layers, a core layer, a convergence layer, and an access layer. Wherein, the core layer is directly connected with a Base Station Controller (BSC) or an IP backbone network, generally constructed by a large-capacity router, and has a high-density port and a high-flow convergence capability; the convergence layer consists of B-type equipment (IPRAN convergence router) and is used for accessing convergence A-type equipment (IPRAN access router); the access layer consists of class a devices connected to the base station. As the application of the multicast service in the ip ran network becomes wider and wider, the requirements on the stability and reliability of the multicast service also become higher and higher.
In order to improve the quality of multicast services, in an existing ip ran networking structure, a main link and a standby link are generally deployed, where the main link connects a class a device and a main class B device, and the standby link connects a class a backup device and a backup class B device. Since multicast has the characteristic of data duplication, if class a device sends IGMP (internet group Management Protocol) membership report messages to main class B device and backup class B device at the same time, the situation of data duplication may occur. Therefore, the class a device usually forwards an IGMP membership report packet from the base station to the main class B device through the main chain, and the main class B device forwards the IGMP membership report packet to the gateway; and, the class a device can only receive the multicast data from the gateway forwarded by the main class B device through the main link.
It can be seen that, in the existing process of implementing multicast service in ip ran networking, all IGMP membership report packets and multicast data need to be forwarded through the main link, and when there are many multicast groups, the network load of the main link is large, thereby affecting the quality of multicast service.
Disclosure of Invention
In view of the above problems, embodiments of the present application are proposed to provide a multicast processing method and apparatus that overcome or at least partially solve the above problems, and can reduce uplink load of a main link.
In order to solve the above problem, an embodiment of the present application discloses a multicast processing method, which is applied to an access stratum device, and includes:
receiving a report message from a base station; the report message carries a multicast address;
according to the multicast address, inquiring in a mapping relation between a pre-established multicast address and a main link to obtain a target main link corresponding to the multicast address;
and sending the report message through the target main link.
On the other hand, the embodiment of the present application discloses an access stratum device, including:
a receiving module, configured to receive a report packet from a base station; the report message carries a multicast address;
the query module is used for querying in a mapping relation between a pre-established multicast address and a main link according to the multicast address so as to obtain a target main link corresponding to the multicast address;
and the sending module is used for sending the report message through the target main link.
The embodiment of the application has the following advantages:
when receiving a report message from a base station, the embodiment of the application obtains a target main link corresponding to a multicast address by inquiring the established mapping relation between the multicast address and the main link, and sends the report message through the target main link. Because the embodiment of the present application can establish the mapping relationship between the multicast address and the main link in advance, that is, different multicast addresses may correspond to different main links, but not all multicast addresses correspond to a fixed main link, for the report messages corresponding to different multicast addresses, different main links may be selected to transmit, and compared with the prior art, the report messages corresponding to all multicast addresses need to be forwarded through a fixed main link, the embodiment of the present application can share the uplink load of the main link.
Drawings
Fig. 1 is a flowchart illustrating steps of a multicast processing method according to an embodiment of the present application;
fig. 2 is a schematic diagram of a network structure for implementing a multicast service in an IPRAN networking according to an embodiment of the present application;
fig. 3 is a flowchart illustrating steps of a multicast processing method according to another embodiment of the present application;
fig. 4 is a block diagram of an access stratum device according to an embodiment of the present application; and
fig. 5 is a block diagram of a multicast processing system according to an embodiment of the present application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
Referring to fig. 1, a flowchart illustrating steps of a multicast processing method according to an embodiment of the present application is shown, and specifically may include the following steps:
102, inquiring in a mapping relation between a pre-established multicast address and a main link according to the multicast address to obtain a target main link corresponding to the multicast address;
and 103, sending the report message through the target main link.
The embodiment of the application can be applied to the access layer A type equipment in the IPRAN network and is used for realizing load sharing of multicast data flow on a main link. Referring to fig. 2, a schematic diagram of a network structure for implementing a multicast service in an IPRAN networking according to an embodiment of the present application is shown. The class-A devices correspond to the base stations one by one, that is, one class-A device can be accessed to one base station, and the class-A devices can be accessed to a pair of class-B devices in a ring shape or dual homing mode. A PW (Pseudowire) shown in fig. 2 is a virtual, directly connected link from a class a device to a class B device, and transparent transmission of data in a layer two of a user can be completed through the PW. The class-A device can receive an IGMP query message from a gateway forwarded by the class-B device, and send the IGMP query message to a corresponding base station through a downlink port AC (access Circuit) of the class-A device, and the base station sends the IGMP query message to a corresponding host; the class a device may further receive an IGMP membership report packet from the host for the IGMP query packet forwarded by the base station, and send the IGMP membership report packet to the main class B device through the main PW, and the main class B device forwards the IGMP membership report packet to a CE (Customer Edge, Customer-side Edge device), and finally reaches the gateway. The primary link described in the embodiments of the present application is the primary PW shown in fig. 2. It can be understood that the embodiment of the present application is not limited to a specific network structure, and for example, the embodiment of the present application may also be used in a networking structure in which an enterprise network MPLS (Multiprotocol Label Switching) L2VPN (two-layer VPN service of a network) accesses an MPLS L3VPN (three-layer VPN service of a network).
In practical application, the report message may specifically be an IGMP membership report message, which may be used to report a multicast group to which a host belongs, and after receiving an IGMP query message, a membership report message of the multicast group may be responded to indicate the multicast group to which the membership report message belongs; or, if the host wants to join a multicast group, it can actively send an IGMP membership report message to declare joining the multicast group.
When receiving an IGMP membership report message from a host responding to an IGMP query message forwarded by a base station, the embodiments of the present application may query a mapping relationship between a pre-established multicast address and a main link according to the multicast address to obtain a target main link corresponding to the multicast address, and send the IGMP membership report message through the target main link. Because the mapping relationship between the multicast address and the main link can be pre-established in the embodiment of the present application, that is, different multicast addresses can correspond to different main links, but not all multicast addresses correspond to a fixed main link, different main links can be selected to transmit IGMP membership report messages corresponding to different multicast addresses, and compared with the prior art in which IGMP membership report messages corresponding to all multicast addresses need to be forwarded by a fixed main link, the embodiment of the present application can share the uplink load of the main link.
In an optional embodiment of the present application, the method may further comprise: and receiving the multicast data corresponding to the multicast address through the target main link.
Therefore, the embodiment of the application enables the multicast data corresponding to different multicast addresses to be sent through different main links, thereby realizing the sharing of the downlink load of the main links. Therefore, the embodiment of the application can share the load of the IGMP membership report message and the multicast data on the main link, reduce the network load of the main link and further improve the quality of the multicast service.
In an optional embodiment of the present application, the mapping relationship between the multicast address and the main link may be established by:
step S11, when receiving the inquiry message from the gateway, establishing the corresponding relation between the multicast address and the uplink in the inquiry message;
step S12, when receiving a report message from the base station for the response of the query message, querying the corresponding relation according to the multicast address in the report message, and acquiring the uplink corresponding to the multicast address;
step S13, selecting one of the uplinks as a main link corresponding to the multicast address, and establishing a mapping relationship between the multicast address and the main link.
In a specific application, when the class a device receives an IGMP query packet of a gateway forwarded by the class B device for the first time, a corresponding relationship between a multicast address and an uplink in the query packet may be established. Optionally, an uplink list may be established for storing the correspondence. For example, when a class a device receives IGMP query packets from two class B devices from two uplink ports, respectively, a corresponding relationship between a multicast address ADDR1 in the IGMP query packet and an uplink may be established, see table 1, which shows an uplink list of one embodiment of the present application.
TABLE 1
| Multicast address | Uplink link |
| ADDR1 | PW1、PW2 |
As shown in table 1, PW1 and PW2 are uplinks corresponding to two uplink ports, ADDR1 is a multicast address carried in an IGMP query packet, and it can be known from table 1 that ADDR1 corresponds to two uplinks, PW1 and PW 2. In the embodiment of the present application, the main and standby attributes are not distinguished for the uplink in the uplink list, but the main link corresponding to the IGMP membership report message is determined only when the class-a device receives the IGMP membership report message forwarded from the base station and responding to the IGMP query message, specifically, the corresponding relationship in the uplink list is queried according to the multicast address ADDR1 in the IGMP membership report message, the uplink corresponding to the multicast address ADDR1 is obtained, one of the uplink is selected as the main link corresponding to the multicast address ADDR1, and a mapping relationship between the multicast address and the main link is established.
It can be understood that, in a specific application, the mapping relationship between the multicast address and the main link may be established in a list manner, or the mapping relationship may also be stored in a database, and the like. For convenience of description, in the embodiment of the present application, the mapping relationship is established by a list as an example, specifically, a forwarding list may be established in advance, and the mapping relationship between the multicast address and the main link is stored in the forwarding list. Optionally, in this embodiment of the present application, if an uplink that is not selected as the main link is also used as the backup link, the forwarding list includes a mapping relationship between the multicast address and the main link and a mapping relationship between the multicast address and the backup link. In a specific application, when receiving a report message from a base station, a primary link corresponding to a multicast address carried in the report message is searched in a forwarding list, if the primary link corresponding to the multicast address exists in the forwarding list, the report message is sent through the primary link, and if the primary link corresponding to the multicast address does not exist, the report message is sent through a backup link corresponding to the multicast address. In addition, when the main link fails, the multicast data flow on the main link can be immediately switched to the backup link, so that the interruption of the multicast data flow is avoided.
Referring to table 2, an illustration of a forwarding list for one embodiment of the present application is shown.
TABLE 2
| Multicast address | Main link | Backup link | Downstream port |
| 225.1.1.1 | PW1 | PW2 | AC1 |
| 225.1.1.2 | PW2 | PW1 | AC1 |
In table 2, the first entry indicates that the main link corresponding to the multicast group with multicast address 225.1.1.1 is PW1, and the backup link is PW 2; the second entry indicates that the main link corresponding to the multicast group with the multicast address 225.1.1.2 is PW2, and the backup link is PW 1. Therefore, the class-A equipment can send the IGMP membership report messages of different multicast addresses through different main links, so that the IGMP membership report messages of all the multicast addresses can be prevented from being sent through the same main link, and the load of the main link can be further reduced.
In an optional embodiment of the present application, the step of selecting an uplink from the uplink list as the main link corresponding to the multicast address may specifically include:
and selecting the uplink with the minimum current multicast data flow as the main link corresponding to the multicast address.
In a specific application, the uplink with the minimum current multicast data traffic in the uplink list is selected as the main link corresponding to the multicast address, so that the multicast data traffic can be evenly distributed on a plurality of main links, and the load on the main links can be greatly reduced.
In one application example of the present application, it is assumed that a class a device has established an uplink list as shown in table 3.
TABLE 3
| Multicast address | Uplink link |
| ADDR1 | PW1、PW2 |
| ADDR2 | PW1、PW2 |
| ADDR3 | PW3、PW4 |
The uplinks corresponding to the multicast addresses ADDR1 and ADDR2 include PW1 and PW 2. The uplink corresponding to the multicast address ADDR3 includes PW3 and PW 4. In a specific application, it is assumed that a class a device receives an IGMP membership report packet corresponding to a multicast group G1, may obtain a multicast address ADDR1 corresponding to the multicast group G1 from the IGMP membership report packet, may obtain an uplink including PW1 and PW2 corresponding to ADDR1 by querying an uplink list shown in table 3, and both of the two uplinks are currently in an idle state, may arbitrarily select one of the uplinks as a main link corresponding to a multicast address ADDR1, and may establish a mapping relationship between the multicast address ADDR1 and a main link PW1 by assuming that PW1 is selected, and send the IGMP membership report packet corresponding to the multicast address ADDR1 through PW1, and receive multicast data corresponding to ADDR1 through PW 1; at this time, the class a device receives an IGMP membership report packet corresponding to the multicast group G2 again, acquires the multicast address ADDR2 corresponding to the multicast group G2 from the IGMP membership report packet, and by querying the uplink list, it can be known that the uplink corresponding to ADDR2 includes PW1 and PW2, and at this time, the traffic on PW2 is smaller than the traffic on PW1, so that PW2 can be selected as the main link corresponding to multicast address ADDR2, a mapping relationship between the multicast address ADDR2 and the main link PW2 is established, an IGMP membership report packet corresponding to the multicast address ADDR2 is sent through PW2, and multicast data corresponding to ADDR2 is received through PW2, thereby enabling multicast data traffic to be distributed on multiple main links in a balanced manner, and greatly reducing the load on the main links.
In an optional embodiment of the present application, the method may further comprise the steps of:
and according to the mapping relation between the multicast address and the main link, the gateway is replaced to periodically send a query message to the base station.
The access layer device may specifically be an access layer a-type device, the query message may specifically be an IGMP query message, and the IGMP query message may specifically include an IGMP general group query message or an IGMP specific group query message. In a specific application, after the mapping relationship between the multicast address and the main link is established, the class a device can replace the class B device to periodically send an IGMP universal group query message to the base station, so that the host can trigger and respond to an IGMP membership report message in time, thereby accelerating the speed of the host joining the multicast group.
In an optional embodiment of the present application, the method may further include the steps of:
and when receiving the query message from the gateway, replacing the base station to respond to the query message by a report message according to the mapping relation between the multicast address and the main link.
In a specific application, after the mapping relationship between the multicast address and the main link is established, when the class a device receives an IGMP query message forwarded by the class B device, the class a device may directly respond to the IGMP membership report message instead of the base station, so as to reduce the interaction time between the class a device and the base station and between the base station and the host, thereby increasing the response speed and further improving the transmission efficiency of multicast data. Further, by querying the mapping relationship between the multicast address and the main link, if the target main link corresponding to the multicast address exists, the target main link replaces the base station to respond and send an IGMP membership report message, and if the target main link does not exist or fails, the backup link replaces the base station to respond and send the IGMP membership report message, so as to avoid interruption of multicast traffic.
In summary, in the embodiment of the present application, when receiving a report packet from a base station, a target main link corresponding to a multicast address is obtained by querying a mapping relationship between the established multicast address and the main link, and the report packet is sent through the target main link. Because the embodiment of the present application can establish the mapping relationship between the multicast address and the main link in advance, that is, different multicast addresses may correspond to different main links, but not all multicast addresses correspond to a fixed main link, for the report messages corresponding to different multicast addresses, different main links may be selected to transmit, and compared with the prior art, the report messages corresponding to all multicast addresses need to be forwarded through a fixed main link, the embodiment of the present application can share the uplink load of the main link.
In addition, the embodiment of the application can also receive the multicast data corresponding to the multicast address through the main link, so that the multicast data corresponding to different multicast addresses can be sent through different main links, and the downlink load of the main links can be shared.
Furthermore, in the embodiment of the present application, the gateway may be replaced to periodically send the query packet to the base station according to a mapping relationship between a pre-established multicast address and a main link, or the base station may be replaced to respond to the query packet to send a report packet, so as to accelerate the speed of the host joining the multicast group and improve the transmission efficiency of multicast data.
In another embodiment of the present application, fast convergence of a failure may also be implemented, and referring to fig. 3, a flowchart of steps of a multicast processing method according to another embodiment of the present application is shown, which specifically includes the following steps:
and 304, when detecting that the target main link fails, sending a report message corresponding to the multicast address through the backup link.
In this embodiment of the present application, a class a device may detect occurrence of a failure of a target main link in time through a BFD (Bidirectional forwarding detection), and may send an IGMP membership report message immediately through a backup link instead of a base station, and a class B device may continue to forward the IGMP membership report message to a gateway direction after receiving the IGMP membership report message, so as to accelerate recovery of a multicast service.
In an optional embodiment of the present application, the method may further comprise the steps of:
and when the recovery of the failed target main link is detected, after waiting for preset delay time, sending a report message corresponding to the multicast address through the recovered target main link.
In a specific application, after the failure of the target main link is recovered, the IGMP membership report packet may be continuously sent from the target main link, and optionally, in order to avoid a situation that the failure is not completely recovered and the failure repeatedly occurs in a short period, the IGMP membership report packet may be sent through the recovered target main link after waiting for a preset delay time, so as to prevent a situation that the main and standby links are frequently switched due to the occurrence of the failure again.
In the embodiment of the application, after the target main link is recovered, the state after the fault is kept unchanged, and only the IGMP membership report message is sent to the newly added group from the recovered main link, so that the back-and-forth switching between the main link and the standby link is avoided. In an application example of the present application, an IGMP membership report packet corresponding to a multicast address ADDR1 is sent through PW1, after PW1 fails, the IGMP membership report packet corresponding to the multicast address ADDR1 is switched to PW2 for sending, and after a period of time, PW1 is recovered, at this time, the state of the IGMP membership report packet corresponding to the multicast address ADDR1 sent through PW2 may be kept unchanged, and the IGMP membership report PW message corresponding to the newly added multicast address ADDR3 may be selected to be sent from 1.
In an optional embodiment of the present application, the method may further comprise:
and sending a group leaving message to the backup link after detecting that the restored target main link receives multicast data from the gateway.
After the target main link with the fault is detected to be recovered, an IGMP membership report message can be sent to the recovered target main link, and after multicast data is received from the target main link, a group leaving message can be sent to the backup link, so that the condition that the multicast data is lost during switching due to incomplete recovery of the target main link can be avoided, and the integrity of the multicast data can be ensured.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.
Referring to fig. 4, a block diagram of an access stratum device according to an embodiment of the present application is shown. In this embodiment, the access stratum device may specifically include:
a receiving module 401, configured to receive a report packet from a base station; the report message carries a multicast address;
a query module 402, configured to query, according to the multicast address, a mapping relationship between a pre-established multicast address and a main link to obtain a target main link corresponding to the multicast address;
a sending module 403, configured to send the report packet through the target main link.
In an optional embodiment of the present application, the apparatus may further comprise: a mapping relation establishing module, configured to establish a mapping relation between the multicast address and a main link; the mapping relationship establishing module comprises:
the list establishing submodule is used for establishing the corresponding relation between the multicast address and the uplink in the query message when receiving the query message from the gateway;
the address acquisition submodule is used for inquiring the corresponding relation according to the multicast address in the report message and acquiring the uplink corresponding to the multicast address when receiving the report message from the base station and responding to the inquiry message;
and the main link selection submodule is used for selecting one of the uplink links as a main link corresponding to the multicast address and establishing a mapping relation between the multicast address and the main link.
In another optional embodiment of the present application, the apparatus may further include:
and the backup link setting module is used for taking the uplink which is not selected as the main link as the backup link corresponding to the multicast address.
In yet another optional embodiment of the present application, the apparatus may further comprise:
and the fault processing module is used for sending a report message corresponding to the multicast address through the backup link when the target main link is detected to be in fault.
In yet another optional embodiment of the present application, the apparatus may further comprise:
and the failure recovery module is used for sending the report message corresponding to the multicast address through the recovered target main link after waiting for the preset delay time when the recovery of the target main link with the failure is detected.
In yet another optional embodiment of the present application, the apparatus may further comprise:
and the leaving message sending module is used for sending a group leaving message to the backup link after detecting that the restored target main link receives the multicast data from the gateway.
In yet another optional embodiment of the present application, the apparatus may further comprise:
and the multicast data receiving module is used for receiving the multicast data corresponding to the multicast address through the target main link.
In yet another optional embodiment of the present application, the apparatus may further comprise:
and the first response module is used for replacing the gateway to periodically send the query message to the base station according to the mapping relation between the multicast address and the main link.
In yet another optional embodiment of the present application, the apparatus may further comprise:
and the second generation answering module is used for substituting the base station for responding to the query message and reporting the message according to the mapping relation between the multicast address and the main link when receiving the query message from the gateway.
Referring to fig. 5, a block diagram of a multicast processing system according to an embodiment of the present application is shown, which may specifically include: a base station 501, an access stratum device 502, a convergence layer device 503, and a gateway 504. The access stratum equipment may include the access stratum equipment described in one of the above embodiments.
The multicast processing system according to the embodiment of the present application has all the features of the access stratum device according to one of the above embodiments, and therefore, the multicast processing system according to the embodiment of the present application has all the advantageous effects of one of the above embodiments, and details of the embodiment of the present application are not repeated herein.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the attached claims
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.
The foregoing detailed description is directed to a multicast processing method, an access stratum device, and a multicast processing system provided in the present application, and specific examples are applied in the present application to explain the principles and embodiments of the present application, and the descriptions of the foregoing examples are only used to help understand the method and core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (14)
1. A multicast processing method is applied to an access stratum device, and the method comprises the following steps:
receiving a report message from a base station; the report message carries a multicast address;
according to the multicast address, inquiring in a mapping relation between a pre-established multicast address and a main link to obtain a target main link corresponding to the multicast address; in the mapping relation, different multicast addresses correspond to different main links;
sending the report message through the target main link;
establishing a mapping relation between the multicast address and a main link by the following steps:
when receiving a query message from a gateway, establishing a corresponding relation between a multicast address and an uplink in the query message;
when receiving a report message from a base station for responding to the query message, querying the corresponding relation according to a multicast address in the report message, and acquiring an uplink corresponding to the multicast address;
and selecting one of the uplinks as a main link corresponding to the multicast address, and establishing a mapping relation between the multicast address and the main link.
2. The method of claim 1, further comprising:
and taking the uplink which is not selected as the main link as a backup link corresponding to the multicast address.
3. The method of claim 2, further comprising:
and when the target main link is detected to be in fault, sending a report message corresponding to the multicast address through the backup link.
4. The method of claim 3, further comprising:
and when the recovery of the failed target main link is detected, after waiting for preset delay time, sending a report message corresponding to the multicast address through the recovered target main link.
5. The method of claim 4, further comprising:
and sending a group leaving message to the backup link after detecting that the restored target main link receives multicast data from the gateway.
6. The method of claim 1, further comprising:
and according to the mapping relation between the multicast address and the main link, the gateway is replaced to periodically send a query message to the base station.
7. The method of claim 1, further comprising:
and when receiving the query message from the gateway, replacing the base station to respond to the query message by a report message according to the mapping relation between the multicast address and the main link.
8. An access stratum device, comprising:
a receiving module, configured to receive a report packet from a base station; the report message carries a multicast address;
the query module is used for querying in a mapping relation between a pre-established multicast address and a main link according to the multicast address so as to obtain a target main link corresponding to the multicast address; in the mapping relation, different multicast addresses correspond to different main links;
a sending module, configured to send the report packet through the target main link;
the apparatus further comprises: a mapping relation establishing module, configured to establish a mapping relation between the multicast address and a main link; the mapping relationship establishing module comprises:
the list establishing submodule is used for establishing the corresponding relation between the multicast address and the uplink in the query message when receiving the query message from the gateway;
the address acquisition submodule is used for inquiring the corresponding relation according to the multicast address in the report message and acquiring the uplink corresponding to the multicast address when receiving the report message from the base station and responding to the inquiry message;
and the main link selection submodule is used for selecting one of the uplink links as a main link corresponding to the multicast address and establishing a mapping relation between the multicast address and the main link.
9. The apparatus of claim 8, further comprising:
and the backup link setting module is used for taking the uplink which is not selected as the main link as the backup link corresponding to the multicast address.
10. The apparatus of claim 9, further comprising:
and the fault processing module is used for sending a report message corresponding to the multicast address through the backup link when the target main link is detected to be in fault.
11. The apparatus of claim 10, further comprising:
and the failure recovery module is used for sending the report message corresponding to the multicast address through the recovered target main link after waiting for the preset delay time when the recovery of the target main link with the failure is detected.
12. The apparatus of claim 11, further comprising:
and the leaving message sending module is used for sending a group leaving message to the backup link after detecting that the restored target main link receives the multicast data from the gateway.
13. The apparatus of claim 8, further comprising:
and the first response module is used for replacing the gateway to periodically send the query message to the base station according to the mapping relation between the multicast address and the main link.
14. The apparatus of claim 8, further comprising:
and the second generation answering module is used for substituting the base station for responding to the query message and reporting the message according to the mapping relation between the multicast address and the main link when receiving the query message from the gateway.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610310493.8A CN106059925B (en) | 2016-05-11 | 2016-05-11 | Multicast processing method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610310493.8A CN106059925B (en) | 2016-05-11 | 2016-05-11 | Multicast processing method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106059925A CN106059925A (en) | 2016-10-26 |
| CN106059925B true CN106059925B (en) | 2020-04-10 |
Family
ID=57177724
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610310493.8A Active CN106059925B (en) | 2016-05-11 | 2016-05-11 | Multicast processing method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106059925B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111372144B (en) * | 2020-03-23 | 2021-09-28 | 北京小鸟科技股份有限公司 | Link backup system and method for multicast video code stream |
| CN116033365B (en) * | 2023-03-22 | 2023-06-20 | 新华三技术有限公司 | Communication method, device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852249A (en) * | 2005-12-01 | 2006-10-25 | 华为技术有限公司 | Multi-cast broadcasting business realizing method |
| CN101051920A (en) * | 2006-04-07 | 2007-10-10 | 华为技术有限公司 | Method for realizing multicast business and network equipment |
| CN101170432A (en) * | 2006-10-27 | 2008-04-30 | 中兴通讯股份有限公司 | A method for realizing multi-cast service protection switching and load balance |
| CN102201999A (en) * | 2011-06-13 | 2011-09-28 | 中兴通讯股份有限公司 | Multicast service load sharing method and system |
| US8948023B2 (en) * | 2010-08-31 | 2015-02-03 | Cisco Technology, Inc. | Enhancing mtrace to detect failure in multicast diverse paths |
-
2016
- 2016-05-11 CN CN201610310493.8A patent/CN106059925B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852249A (en) * | 2005-12-01 | 2006-10-25 | 华为技术有限公司 | Multi-cast broadcasting business realizing method |
| CN101051920A (en) * | 2006-04-07 | 2007-10-10 | 华为技术有限公司 | Method for realizing multicast business and network equipment |
| CN101170432A (en) * | 2006-10-27 | 2008-04-30 | 中兴通讯股份有限公司 | A method for realizing multi-cast service protection switching and load balance |
| US8948023B2 (en) * | 2010-08-31 | 2015-02-03 | Cisco Technology, Inc. | Enhancing mtrace to detect failure in multicast diverse paths |
| CN102201999A (en) * | 2011-06-13 | 2011-09-28 | 中兴通讯股份有限公司 | Multicast service load sharing method and system |
Non-Patent Citations (1)
| Title |
|---|
| 《IGMP V3协议研究与实现》;李卫平 等;《飞行器测控学报》;20120630;第31卷(第3期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106059925A (en) | 2016-10-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6654371B1 (en) | Method and apparatus for forwarding multicast data by relaying IGMP group membership | |
| US8218429B2 (en) | Method and device for multicast traffic redundancy protection | |
| US7817542B2 (en) | Method and network device for fast service convergence | |
| JP6165850B2 (en) | Enhanced protocol independent multicast (PIM) fast rerouting methodology using downstream notification packets | |
| US9059902B2 (en) | Procedures, apparatuses, systems, and computer-readable media for operating primary and backup network elements | |
| US8804486B2 (en) | Base stations routing traffic over a packet backhaul network to multiple routing elements | |
| US20130021896A1 (en) | Method, system, and device for protecting multicast in communication network | |
| EP3422632B1 (en) | Pim join entropy | |
| US9160616B2 (en) | Multicast packet transmission method, related device and system | |
| US20150254149A1 (en) | Dual Adjacency Between Edge Devices at a Network Site | |
| US11611509B2 (en) | Communication method, communications device, and communications system | |
| CN103117935B (en) | Be applied to multicast data forwarding method and the device of multi-home networking | |
| CN104255002A (en) | Redundant network connections | |
| WO2012106915A1 (en) | Failure notification method, detection apparatus, forwarding apparatus, system and data structure | |
| CN103067286A (en) | Multicast data transmission method and equipment | |
| US10225091B2 (en) | Method for implementing point-to-multipoint multicast, network node, and system | |
| WO2022253087A1 (en) | Data transmission method, node, network manager, and system | |
| JP2008103864A (en) | Ip multicast service system, switch device, and method of selecting and transmitting group used for them | |
| WO2022017432A1 (en) | Multicast packet sending method, apparatus, and system | |
| CN106059925B (en) | Multicast processing method and equipment | |
| US9313037B2 (en) | Method, apparatus and system for forwarding data under protocol independent multicast dual join | |
| WO2020001602A1 (en) | Method for implementing data multicast, apparatus, and system | |
| US20150043329A1 (en) | Proactive Creation of Multicast State in an Overlay Transport Network to Achieve Fast Convergence on Failover | |
| EP4131868A1 (en) | Information submitting method, information processing method, apparatus, and device | |
| KR101308088B1 (en) | Method and apparatus for blocking the search for the website |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou science and Technology Development Zone, Zhejiang high tech park, No. six and road, No. 310 Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |