Link state detection method, multicast device and link state detection system

Technical field of link state detection method, multicast equipment and link state detection system

[0001] The present application relates to the field of communication technology, and specifically to a link state detection method, a multicast device, and a link state detection system.

Background technique

[0002] In a multicast transmission network such as a PTN (Packet Transport Network, packet transport network) application network, the application of the multicast service is extremely wide. With the continuous improvement of network quality requirements, it is necessary to increase protection mechanisms for multicast services. However, in the existing protected multicast service application scenario, when the access point monitors or diagnoses the network link status, usually only the link status from the access point to the source node can be diagnosed. Due to the inherent service characteristics of the multicast service, there is only a mechanism from the source node to the access point for message forwarding, and the forwarding mechanism from the access point to the source node is missing. Therefore, the access point cannot monitor or diagnose the status of the network link. Unable to identify network failures in time.

Summary of the invention

[0003] This application provides a link state detection method, a multicast device, and a link state detection system to improve the link state detection mechanism and realize the link state monitoring from the access point to the source node.

[0004] In the first aspect, an embodiment of the present application provides a link state detection method, including:

[0005] In the multicast device of the multicast transmission network, a reverse unknown multicast group is configured; wherein, the multicast transmission network includes a client, a multicast device, and a target multicast source;

[0006] The multicast device forwards the link state detection message sent by the client to the target multicast source through the reverse unknown multicast group; wherein, the link state detection message is used To detect the working link status;

[0007] The target multicast source sends a link state response message to the client according to the link state detection message;

[0008] Upon receiving the link state response message, the client determines that the working link state is normal.

[0009] In the second aspect, an embodiment of the present application provides a link state detection system, including a client, a multicast device, and a target multicast source; the client is in communication connection with the multicast device, and the multicast The device is in communication connection with the target multicast source; wherein,

[0010] The client is used to send a link state detection message, and in the case of receiving a link state response message sent by the target multicast source, determine that the working link state is normal;

[0011] The multicast device is configured with a reverse unknown multicast group for forwarding the link state detection message sent by the client to the target multicast source through the reverse unknown multicast group; wherein , The link state detection message is used to detect the working link state;

[0012] The target multicast source is configured to send the link state response message to the client according to the link state detection message.

[0013] In the third aspect, an embodiment of the present application provides a link state detection method, which is applied to a multicast device of a multicast transmission network, and includes:

[0014] receiving the link state detection message sent by the client, and forwarding the link state detection message to the target multicast source through the configured reverse unknown multicast group;

[0015] Wherein, the link state detection message is used to detect the working link state;

[0016] The client is used to send a link state detection message, and in the case of receiving a link state response message sent by the target multicast source, determine that the working link state is normal;

[0017] The target multicast source is used to send the link state response message to the client according to the link state detection message.

[0018] In a fourth aspect, an embodiment of the present application provides a link state detection device, which is configured in a multicast device of a multicast transmission network, and is characterized by including:

[0019] The detection message processing module is configured to receive the link state detection message sent by the client, and forward the link state detection message to the target multicast source through the configured reverse unknown multicast group;

[0020] Wherein, the link state detection message is used to detect the working link state;

[0021] The client is used to send a link state detection message, and in the case of receiving a link state response message sent by the target multicast source, determine that the working link state is normal;

[0022] The target multicast source is configured to send the link state response message to the client according to the link state detection message.

[0023] In a fifth aspect, an embodiment of the present application provides a multicast device, including:

[0024] one or more processors;

[0025] A storage device for storing one or more programs;

[0026] When the one or more programs are executed by the one or more processors, the one or more processors implement the link state detection method as described in the third aspect.

[0027] In a sixth aspect, an embodiment of the present application provides a computer storage medium on which a computer program is stored, and when the program is executed by a processor, the link state detection method as described in the third aspect is implemented.

[0028] In the embodiment of the present application, a reverse unknown multicast group is configured in the multicast device of the multicast transmission network to forward the link state detection message sent by the client to the target group through the reverse unknown multicast group. Broadcast source. After the target multicast source receives the link state detection message, it can send a link state response message to the client. When the client receives the link status response message, it can determine that the working link status is normal, and solve the problem that the existing multicast transmission network cannot monitor the link status from the access point to the source node to improve the link The state detection mechanism realizes the link state monitoring from the access point to the source node.

[0029] Regarding the above embodiments and other aspects of the present application and their implementation, more descriptions are provided in the description of the drawings, the specific implementation and the claims.

Description of the drawings

[0030] FIG. 1a is a schematic flowchart of a link state detection method provided by an embodiment of the application;

[0031] FIG. 1b is a thumbnail of a protected P2MP L2 multicast transmission network without switching request according to an embodiment of the present application;

[0032] FIG. 1c is a thumbnail of a network state with protection scenario, provided by an embodiment of the present application, with a request for switching;

[0033] FIG. 1d is a schematic diagram of a service implementation provided by an embodiment of the present application;

[0034] FIG. 1e is a logic operation diagram of a normal state unicast service provided by an embodiment of the present application

[0035] FIG. 1f is a logic operation diagram of a switched state unicast service provided by an embodiment of the present application;

[0036] FIG. 2 is a schematic structural diagram of a link state detection system provided by an embodiment of the application;

[0037] FIG. 3 is a schematic flowchart of a link state detection method provided by an embodiment of the application;

[0038] FIG. 4 is a schematic structural diagram of a link state detection device provided by an embodiment of the application;

[0039] FIG. 5 is a schematic structural diagram of a multicast device provided by an embodiment of the application.

Detailed ways

[0040] In order to make the objectives, technical solutions, and advantages of the application more clear, the embodiments of the application will be described in detail below in conjunction with the accompanying drawings. It should be noted that the embodiments in this application and the features in the embodiments can be combined with each other arbitrarily if there is no conflict.

[0041] In an exemplary embodiment, FIG. 1a is a schematic flowchart of a link state detection method provided by an embodiment of the application. This method can be suitable for monitoring the status of the link from the access point to the source node. Correspondingly, as shown in FIG. 1a, the road state detection method provided by the embodiment of the present application includes S110, S120, S130, and S140.

[0042] S110. Configure a reverse unknown multicast group in the multicast device of the multicast transmission network; wherein, the multicast transmission network includes a client, a multicast device, and a target multicast source.

[0043] Wherein, the multicast transmission network may be an application network that supports a multicast transmission function. For example, a PTN application network and EPON (Ethernet Passive Optical Network, Ethernet Passive Optical Network) can all be used as a multicast transmission network. The client is the source node in the multicast transmission network configured with the reverse unknown multicast group, and can send messages to the access point. Exemplarily, a PC (Personal Computer, personal computer) terminal may serve as a client. A multicast device is a network device that completes a multicast transmission function. Illustratively, a PTN device can be used as a multicast device. The reverse unknown multicast group can be used to forward packets sent by the client to the multicast source. That is, the message sent by the client is sent to the multicast source. The target multicast source is the multicast source in the multicast transmission network, a kind of hardware device. Exemplarily, a wireless router with a multicast function can be used as a target multicast source. The target multicast source may include only the working multicast source, or may include both the working multicast source and the protection multicast source. Wherein, the working multicast source may be a multicast source on the working path in the multicast network; the protected multicast source may be a multicast source on the protection path in the multicast network, and the embodiment of the present application does not apply to the group of the target multicast source. The source type is restricted.

[0044] It should be noted that in the prior art, the source node is a leaf node in the multicast transmission network, and the access node is a client in the multicast transmission network. In the embodiment of the present application, in order to monitor the status of the working link from the access point to the source node in the multicast transmission network, after configuring the reverse unknown multicast group for the multicast device, in the logical relationship, the client It becomes a source node, and the leaf node becomes an access node.

[0045] S120. The multicast device forwards the link state detection message sent by the client to the target multicast source through the reverse unknown multicast group; wherein, the link state detection message This document is used to detect the working link status.

[0046] Wherein, the working link state is the state of the path link in the network, and the working link may be the working path link or the protection path link. Correspondingly, the working link state may be the working source link state for the working path link, or the protection source link state for the protection path link. The embodiment of the present application does not monitor the working link and the working link state. The specific type is limited.

[0047] Correspondingly, after the multicast device is configured with a reverse unknown multicast group, the multicast device can forward the link state detection message sent by the client to the target multicast source through the reverse unknown multicast group . Optionally, the client can use the ping technology to initiate a link state detection message (ie, send a packet), and the link state detection message can be used to detect the working link state.

[0048] S130. The target multicast source sends a link state response message to the client according to the link state detection message.

[0049] The link state response message may be a response packet generated by the target multicast source according to the link state detection message.

[0050] In the embodiment of the present application, after the target multicast source receives the link state detection message, it may send a link state response message to the client according to the link state detection message.

[0051] S140: The client determines that the working link status is normal when receiving the link status response message.

[0052] It can be understood that if the working link status is abnormal, the client cannot normally receive the link status response message sent by the target multicast source. Therefore, in the embodiment of the present application, if the client receives the link status response message, it can be determined that the working link status in the multicast transmission network is normal. That is, the monitoring of the working link status from the access node to the source node in the prior art is realized.

[0053] In this embodiment of the application, a reverse unknown multicast group is configured in the multicast device of the multicast transmission network to forward the link state detection message sent by the client to the target group through the reverse unknown multicast group. Broadcast source. After the target multicast source receives the link state detection message, it can send a link state response message to the client. When the client receives the link status response message, it can determine that the working link status is normal, and solve the problem that the existing multicast transmission network cannot monitor the working link status from the access point to the source node to improve the chain. The path status detection mechanism realizes the status monitoring of the working link from the access point to the source node.

[0054] On the basis of the above-mentioned embodiment, a modified embodiment of the above-mentioned embodiment is proposed. It should be noted here that, in order to make the description concise, only the differences from the above-mentioned embodiment are described in the modified embodiment.

[0055] In an example, configuring the reverse unknown multicast group may include: configuring the original reverse unknown multicast group according to the target service of the multicast transmission network; combining the client and the target multicast source The multicast information of is added to the original reverse unknown multicast group to configure the reverse unknown multicast group.

[0056] Among them, the target service can be determined according to the type of the multicast source in the multicast transmission network. Exemplarily, if the type of the multicast source in the multicast transmission network only includes the working multicast source, the target service may be an unprotected service. If the type of the multicast source in the multicast transmission network includes both the working multicast source and the protected multicast source, the target service may be a protected service. The original reverse unknown multicast group may be a reverse unknown multicast group with empty information to be configured. The multicast information of the client and the target multicast source may be service member information of the client and the target multicast source in the multicast device.

[0057] Specifically, when configuring the reverse unknown multicast group for the multicast device, the original reverse unknown multicast group can be created according to the target service of the multicast transmission network. Then, the multicast information of the client and the target multicast source can be added to the original reverse unknown multicast group to complete the configuration of the original reverse unknown multicast group.

[0058] In an example, adding the multicast information of the client and the target multicast source to the original reverse unknown multicast group may include: in the original reverse unknown multicast group Add service members of the multicast device.

[0059] Wherein, the service members may be nodes in each role of the client and the target multicast source in the multicast device. Exemplarily, the working root (W_Root), the protection root (P_Root), and the common leaf (C_Leaf) may all be service members of the multicast device.

[0060] Specifically, when the multicast information of the client and the target multicast source is added to the original reverse unknown multicast group, service members of the multicast device may be added to the original reverse unknown multicast group.

[0061] In an example, the target multicast source may include a working multicast source and a protection multicast source; the target service may include a protected service; and the service members may include a working root, a protection root, and a general leaf. At least one of.

[0062] Wherein, the working root may be a working path root node, the protection root may be a protection path root node, and the general leaf may be a client leaf node.

[0063] Optionally, in this embodiment of the application, the target multicast source may include both a working multicast source and a protected multicast source. Correspondingly, the target service may be a protected service, and the service members may include at least one of working root, protection root, and general leaf.

[0064] In an example, adding service members of the multicast device to the original reverse unknown multicast group may include: configuring the general leaf, and adding the next hop of the general leaf to the The original reverse unknown multicast group; configure the working root, and add the next hop of the working root to the original reverse unknown multicast group; and/or, configure the protection root, and set the protection The next hop of the root joins the original reverse unknown multicast group.

[0065] Specifically, when adding service members of the multicast device to the original reverse unknown multicast group, a general leaf can be configured, and the next hop of the general leaf can be added to the original reverse unknown multicast group. If you need to configure the protective root and working root at the same time, you can configure the working root first, and add the next hop of the working root to the original reverse unknown multicast group, and then configure the protective root to add the next hop of the protective root to the original reverse Unknown multicast group. In addition, this application may also configure only the working root or only the protection root. It should be noted that the embodiment of the present application does not limit the configuration sequence of the general leaf, the working root, and the protection root.

[0066] In an example, after adding the service members of the multicast device to the original reverse unknown multicast group, it may further include: forming a protection group according to the working root and the protection root; wherein, The protection group is used to protect the link detection operation of the client.

[0067] Correspondingly, after adding service members of the multicast device to the original reverse unknown multicast group to complete the configuration of the original reverse unknown multicast group and form the reverse unknown multicast group, it can also be based on the reverse The information of service members in the unknown multicast group is protected. Specifically, a protection group can be formed according to the working root and the protection root, and the protection group enablement is interrupted, which can be used to protect the client's link detection operation, specifically for the protection switching response switching client to detect the target multicast source (including the working group). The detection operation of the link where the broadcast source and protected multicast source are located.

[0068] In an example, the multicast device forwarding the link state detection message sent by the client to the target multicast source through the reverse unknown multicast group may include: the group The broadcast device searches for the target service members included in the reverse unknown multicast group to forward the link state detection message sent by the client to the target multicast source according to the target service members; wherein, the The target business member includes the working root and the protection root.

[0069] Specifically, when the multicast device forwards the link state detection message to the target multicast source through the reverse unknown multicast group, it can search for the working root and/or protection root of the target service member included in the reverse unknown multicast group. , To forward the link state detection message sent by the client to the target multicast source according to the working root and/or the protection root. If the client receives the return packet of the link where the target multicast source is located, that is, receives the link status response message sent by the target multicast source, it can be determined that the working link is normal.

[0070] In an example, the link state response message includes a working source link state response message; the working link state includes a working source link state; the client is receiving the link In the case of a status response message, determining that the working link status is normal may include: there is no switching request status in the network status of the multicast transmission network, and the client receives the working source link status In the case of a response message, it is determined that the working source link status is normal.

[0071] Wherein, the working source link state response message may be a response packet sent by the working multicast source to the client when the network state is in a state without a switching request.

[0072] Optionally, the link state response message may include a working source link state response message. The working link state may include the working source link state. Correspondingly, if the switching request state does not exist in the network state of the multicast transmission network, and the client receives the working source link state response message, it can be determined that the working source link state is normal.

[0073] In an example, the link state response message includes a protection source link state response message, and the working link state includes a protection source link state; the client receives the link state In the case of a response message, determining that the working link status is normal may include: a switching request status exists in the network status of the multicast transmission network, and the client receives the protection source link status response report In the case of the document, it is determined that the protection source link status is normal.

[0074] Wherein, the protection source link state response message may be a response packet sent by the protection multicast source to the client when the network state is in the switching request state.

[0075] Optionally, the link state response message may include a protection source link state response message. The working link status may include the protection source link status. Correspondingly, if the switching request state exists in the network state of the multicast transmission network, and the client receives the protection source link state response message, it can be determined that the protection source link state is normal.

[0076] P2MP (Point-to-Multipoint, Point-to-Multipoint) is a transmission technology in a PTN network that transmits multicast services from a single sender device in the network to multiple receiver devices. The multicast service has only one data stream for the same multicast service in the established forwarding channel, and the multicast data stream is transmitted to the multicast service branch. At the bifurcation point on the multicast path, the replication of the multicast data stream to different directions is completed to ensure that there is only one multicast data stream in the same downstream direction, thereby avoiding backbone network congestion.

[0077] FIG. 1b is a thumbnail of a protected P2MP L2 multicast transmission network without switching request provided by an embodiment of the present application. Fig. 1c is a thumbnail image of a network state switching request in a protected scenario provided by an embodiment of the present application. As shown in Figure 1b and Figure 1c. The access PTN1 device is deployed between the client and the working multicast source, and the PTN2 device is deployed between the client and the protected multicast source. The solid line represents the working path, and the dotted line represents the protection path. PTN1 and PTN2 deploy business members with multiple roles, such as: W_Root (working root), P_Root (protection root), and C_Leaf (common leaf).

[0078] In a summary of a specific example, P2MP L2 multicast is taken as an example to illustrate:

[0079] Mtree (a type of multicast transmission network) includes member clients and multicast sources, creates an original reverse unknown multicast group, and adds the client and multicast source to the original reverse unknown multicast group to complete Reverse unknown multicast group configuration. The client can use the ping technology to detect the multicast source in C_Leaf. At this time, the detection packet can be forwarded to the multicast source in the same network. Specifically, in the initial state of Mtree, Mtree can add clients and working multicast sources to join the reverse unknown multicast group. In the protected state of Mtree, Mtree can add clients, working multicast sources, and protected multicast sources to join the reverse unknown multicast group. Correspondingly, in the initial state of Mtree, the client and the working multicast source are in the same reverse unknown multicast group, and the client service forwards the packet to the working multicast source interface in the same reverse unknown multicast. In the protected scenario of Mtree, when the client detects in the normal scenario, the link state detection message is concurrently sent to the working multicast source and the protection multicast source, and the working multicast source and the protection multicast source are returned and sent to the client. Link status response message. The client can detect the working source link status when the network status does not have any request. In the network status request switching scenario, the client can detect the protection source link status to ensure the working link regardless of whether the network status has a switching request. The status can be detected.

[0080] FIG. 1d is a schematic diagram of a service implementation provided by an embodiment of the present application, FIG. 1e is a logic operation diagram of a normal state unicast service provided by an embodiment of the present application, and FIG. 1f is a switching provided by an embodiment of the present application State unicast business logic operation diagram. As shown in Figure 1d, when configuring a reverse unknown multicast group for a multicast device, you can configure the protection service P2MP L2 service implementation level to create the original reverse unknown multicast group for the P2MP L2 service. Then, for the original reverse unknown group created

Add business members such as C_Leaf, W_Root and W_Root to the broadcast group. Specifically, the next hop of the general leaf is added to the original reverse unknown multicast group, the next hop of the working root is added to the original reverse unknown multicast group, and the next hop of the protection root is added to the original reverse unknown. In the multicast group. Correspondingly, after the reverse unknown multicast group is configured, a protection group can be formed according to W_Root and P_Root, and the protection group enable interruption is used to protect the link detection operation of the client, and it is specifically used to switch the client detection target in response to protection switching Multicast source (including working multicast source and protection multicast source) link detection operation.

[0081] Exemplarily, a multicast device configured with a reverse unknown multicast group may be used to detect the working link status. As shown in Figure 1e, when there is no switching request in the network state, the client uses the ping technology to initiate a link state detection message. After the service is connected to the PTN device, it uses the reverse unknown multicast group to find service members including W_Root, P_Root, forwards the link state detection message to the working multicast source and the protection multicast source. The working multicast source and the protection multicast source receive the link state detection message, and the working multicast source can send the link state response message to the client according to the link state detection message, that is, send the working source chain to the client Road status response message. The protection of the multicast source can do packet loss operations. At this time, if the client receives the working source link status response message sent by the working multicast source, it can determine that the working source link status is normal.

[0082] As shown in FIG. 1f, when there is a switching request state in the network state, the client uses the ping technology to initiate a link state detection message. After the service is accessed by the PTN device, it uses the reverse unknown multicast group to find the service members including W_Root and P_Root, then forward the link state detection message to the working multicast source and the protection multicast source. The working multicast source and the protection multicast source receive the link state detection message, and the working multicast source can perform packet loss operations. The protection multicast source may send a link state response message to the client according to the link state detection message, that is, send a protection source link state response message to the client. At this time, if the client receives the protection source link status response message sent by the protection multicast source, it can determine that the protection source link status is normal.

[0083] In an exemplary embodiment, an embodiment of the present application also provides a link state detection system, and FIG. 2 is a schematic structural diagram of a link state detection system provided by an embodiment of the application. For the content that is not yet exhaustive in this embodiment, reference may be made to the above-mentioned embodiment, which will not be repeated here.

[0084] As shown in FIG. 2, the link state detection system provided by the embodiment of the present application may include a client 10, a multicast device 20, and a target multicast source 30; the client 10 is in communication connection with the multicast device 20, and multicast The device 20 is in communication connection with the target multicast source 30; wherein, the client 10 is used to send a link state detection message, and in the case of receiving a link state response message sent by the target multicast source 30, determine the working chain The path status is normal; the multicast device 20 is configured with a reverse unknown multicast group for forwarding the link status detection message sent by the client 10 to the target multicast source 30 through the reverse unknown multicast group; wherein, the chain The link state detection message is used to detect the working link state; the target multicast source 30 is used to send the link state response message to the client 10 according to the link state detection message.

[0085] Wherein, the multicast transmission network may be an application network that supports a multicast transmission function. For example, a PTN application network and EPON may be used as a multicast transmission network. The client 10 is the source node in the multicast transmission network configured with the reverse unknown multicast group, and can send messages to the access point. The multicast device 20 is a network device that completes the multicast transmission function. Illustratively, the PTN device may be used as a kind of multicast device 20. The reverse unknown multicast group can be used to forward the message sent by the client 10 to the multicast source. That is, the message sent by the client 10 is sent to the multicast source. The target multicast source 30 is the multicast source in the multicast transmission network, and may include only the working multicast source, or may include both the working multicast source and the protection multicast source. Wherein, the working multicast source may be a multicast source on the working path in the multicast network; the protected multicast source may be a multicast source on the protection path in the multicast network. The embodiment of the present application does not affect the target multicast source 30. The type of multicast source is restricted.

[0086] It should be noted that in the prior art, the source node is a leaf node in the multicast transmission network, and the access node is a client in the multicast transmission network. In the embodiment of the present application, in order to realize the access point to the source in the multicast transmission network

For monitoring the working link status of a node, after configuring a reverse unknown multicast group for the multicast device, in terms of a logical relationship, the client 10 becomes a source node, and the leaf node becomes an access node.

[0087] Wherein, the working link state is the state of the path link in the network, and the working link may be the working path link or the protection path link. Correspondingly, the working link state may be the working source link state for the working path link, or the protection source link state for the protection path link. The embodiment of the present application does not monitor the working link and the working link state. The specific type is limited.

[0088] Correspondingly, after the multicast device 20 is configured with a reverse unknown multicast group, the multicast device 20 can forward the link state detection message sent by the client 10 to the target multicast through the reverse unknown multicast group. Source 30. Optionally, the client 10 may use the ping technology to initiate a link state detection message (ie, send a packet), and the link state detection message may be used to detect the working link state.

[0089] The link state response message may be a response packet generated by the target multicast source 30 according to the link state detection message.

[0090] In the embodiment of the present application, after the target multicast source 30 receives the link state detection message, it may send a link state response message to the client 10 according to the link state detection message.

[0091] It can be understood that if the working link status is abnormal, the client 10 cannot normally receive the link status response message sent by the target multicast source 30. Therefore, in the embodiment of the present application, if the client 10 receives the link status response message, it can be determined that the working link status in the multicast transmission network is normal. That is, the monitoring of the working link status from the access node to the source node in the prior art is realized.

[0092] The link state detection system provided by the embodiment of the present application includes a client, a multicast device, and a target multicast source. Among them, the multicast device may configure a reverse unknown multicast group to forward the link state detection message sent by the client to the target multicast source through the reverse unknown multicast group. When the client receives the link status response message sent by the target multicast source, it can determine that the working link status is normal, which solves the problem that the existing multicast transmission network cannot monitor the link status from the access point to the source node , In order to improve the link state detection mechanism, realize the link state monitoring from the access point to the source node.

[0093] On the basis of the above-mentioned embodiment, a modified embodiment of the above-mentioned embodiment is proposed. It should be noted here that, in order to make the description concise, only the differences from the above-mentioned embodiment are described in the modified embodiment.

[0094] In an example, the multicast device 20 is used to configure the original reverse unknown multicast group according to the target service of the multicast transmission network; add the client 10 and the target multicast source 30 to the original reverse To the unknown multicast group to configure the reverse unknown multicast group.

[0095] Wherein, the target service can be determined according to the type of the multicast source in the multicast transmission network. Exemplarily, if the type of the multicast source in the multicast transmission network only includes the working multicast source, the target service may be an unprotected service. If the type of the multicast source in the multicast transmission network includes both the working multicast source and the protected multicast source, the target service may be a protected service. The original reverse unknown multicast group may be a reverse unknown multicast group with empty information to be configured. The multicast information of the client 10 and the target multicast source 30 may be service member information of the client 10 and the target multicast source 30 in the multicast device.

[0096] Specifically, when configuring the reverse unknown multicast group for the multicast device 20, the original reverse unknown multicast group may be created according to the target service of the multicast transmission network. Then, the multicast information of the client 10 and the target multicast source 30 can be added to the original reverse unknown multicast group to complete the configuration of the original reverse unknown multicast group.

[0097] In an example, the multicast device 20 is used to add service members of the multicast device 20 to the original reverse unknown multicast group.

[0098] Among them, the service members may be the nodes of the various roles of the client 10 and the target multicast source 30 in the multicast device.

point. Exemplarily, the working root, protection root, general leaf, etc. may all be service members of the multicast device 20.

[0099] Specifically, when the multicast information of the client 10 and the target multicast source 30 is added to the original reverse unknown multicast group, the service members of the multicast device 20 may be added to the original reverse unknown multicast group.

[0100] In an example, the target multicast source 30 includes a working multicast source and a protection multicast source; the target service includes a protected service; the service member includes a general leaf, and at least one of the working root and the protection root One kind.

[0101] Wherein, the working root may be a working path root node, the protection root may be a protection path root node, and the general leaf may be a client leaf node.

[0102] Optionally, in this embodiment of the application, the target multicast source may include both a working multicast source and a protected multicast source. Correspondingly, the target service may be a protected service, and the service members must include general leaves, and may include at least one of a working root and a protection root.

[0103] In an example, the multicast device 20 is configured to: configure the general leaf, add the next hop of the general leaf to the original reverse unknown multicast group; configure the working root, and add all The next hop of the working root is added to the original reverse unknown multicast group; and/or, the protection root is configured, and the next hop of the protection root is added to the original reverse unknown multicast group.

[0104] Specifically, when adding service members of the multicast device to the original reverse unknown multicast group, a general leaf can be configured, and the next hop of the general leaf can be added to the original reverse unknown multicast group, and then it can be configured Working root, the next hop of the working root is added to the original reverse unknown multicast group, and finally the protection root can be configured to add the next hop of the protection root to the original reverse unknown multicast group. It should be noted that the embodiment of the present application does not limit the configuration sequence of the general leaf, the working root, and the protection root.

[0105] In an example, the multicast device 20 is used to form a protection group according to the working root and the protection root; wherein, the protection group is used to protect the link detection operation of the client 10.

[0106] Correspondingly, after adding service members of the multicast device to the original reverse unknown multicast group to complete the configuration of the original reverse unknown multicast group and form the reverse unknown multicast group, it can also be based on the reverse The information of service members in the unknown multicast group is protected. Specifically, a protection group can be formed according to the working root and the protection root, and the protection group enablement is interrupted, which can be used to protect the client's link detection operation, specifically for the protection switching response switching client to detect the target multicast source (including the working group). The detection operation of the link where the broadcast source and protected multicast source are located.

[0107] In an example, the multicast device 20 is configured to search for target service members included in the reverse unknown multicast group, so as to forward the link state detection message sent by the client 10 according to the target service member To the target multicast source 30; wherein, the target service member includes the working root and the protection root.

[0108] Specifically, when the multicast device 20 forwards the link state detection message to the target multicast source 30 through the reverse unknown multicast group, it can search for the working roots and/or the target service members included in the reverse unknown multicast group. The protection root is used to forward the link state detection message sent by the client 10 to the target multicast source 30 according to the working root and/or the protection root. If the client 10 receives the return packet of the link where the target multicast source 30 is located, that is, receives the link status response message sent by the target multicast source 30, it can be determined that the working link status is normal.

[0109] In an example, the link state response message includes a working source link state response message; the working link state includes a working source link state; the client 10 is used to: In the case that the network state of the transmission network does not have a switching request state, and the working source link state response message is received, it is determined that the working source link state is normal.

[0110] Wherein, the working source link state response message may be the working multicast when the network state is in the state of no switching request.

The return packet sent by the source to the client 10.

[0111] Optionally, the link state response message may include a working source link state response message. The working link state may include the working source link state. Correspondingly, if there is no switching request state in the network state of the multicast transmission network, and the client 10 receives the working source link state response message, it can be determined that the working source link state is normal.

[0112] In an example, the link state response message includes a protection source link state response message; the working link state includes a protection source link state; the client 10 is used to: In the case that the network status of the transmission network has a switching request status, and the protection source link status response message is received, it is determined that the protection source link status is normal.

[0113] The protection source link state response message may be a response packet sent by the protection multicast source to the client 10 when the network state is in the switching request state.

[0114] Optionally, the link state response message may include a protection source link state response message. The working link status may include the protection source link status. Correspondingly, if the switching request state exists in the network state of the multicast transmission network, and the client 10 receives the protection source link state response message, it can be determined that the protection source link state is normal.

[0115] In an exemplary embodiment, FIG. 3 is a schematic flowchart of a link state detection method provided by an embodiment of the application. This method can be applied to the situation where the multicast device forwards the message for detecting the link state to the multicast source. Correspondingly, as shown in FIG. 3, the road state detection method provided by the embodiment of the present application includes S210.

[0116] S210. Receive the link state detection message sent by the client, and forward the link state detection message to the target multicast source through the configured reverse unknown multicast group.

[0117] Wherein, the link state detection message is used to detect the working link state;

[0118] The client is used to send a link state detection message, and in the case of receiving a link state response message sent by the target multicast source, determine that the working link state is normal;

[0119] The target multicast source is used to send the link state response message to the client according to the link state detection message.

[0120] In this embodiment of the application, the link state detection message sent by the client is received by the multicast device, and the link state detection message is forwarded to the target multicast source through the reverse unknown multicast group configured by the multicast device. So that the target multicast source sends a link state response message to the client according to the link state detection message, and the client determines the working chain after receiving the link state response message sent by the target multicast source The path status is normal, which solves the problem that the existing multicast transmission network cannot monitor the link status from the access point to the source node, so as to improve the link status detection mechanism and realize the link status monitoring from the access point to the source node.

[0121] In an example, before receiving the link state detection message sent by the client, it further includes: configuring the original reverse unknown multicast group according to the target service of the multicast transmission network; combining the client with The multicast information of the target multicast source is added to the original reverse unknown multicast group to configure the reverse unknown multicast group.

[0122] In an example, adding the multicast information of the client and the target multicast source to the original reverse unknown multicast group may include: in the original reverse unknown multicast group Add service members of the multicast device.

[0123] In an example, the target multicast source includes a working multicast source and a protected multicast source; the target service includes a protected service; the service member includes a general leaf, and the working root and the protected root At least one.

[0124] In an example, adding service members of the multicast device to the original reverse unknown multicast group may include: configuring the general leaf, and adding the next hop of the general leaf to the The original reverse unknown multicast group; configure the working root, and add the next hop of the working root to the original reverse unknown multicast group; and/or configure the

A protection root, adding the next hop of the protection root to the original reverse unknown multicast group.

[0125] In an example, the service members include general leaves, working roots, and protection roots; after adding the service members of the multicast device to the original reverse unknown multicast group, it may also include: The working root and the protection root form a protection group; wherein, the protection group is used to protect the link detection operation of the client.

[0126] In an example, forwarding the link state detection message to the target multicast source through the configured reverse unknown multicast group may include: searching for target service members included in the reverse unknown multicast group To forward the link state detection message sent by the client to the target multicast source according to the target service member; wherein the target service member includes the working root and the protection root.

[0127] In an example, the link state response message includes a working source link state response message; the working link state includes a working source link state; and the client is used for: in the multicast transmission In the case that there is no switching request state in the network state of the network and the working source link state response message is received, it is determined that the working source link state is normal.

[0128] In an example, the link state response message includes a protection source link state response message; the working link state includes a protection source link state; the client is used for: in the multicast transmission If the network status of the network has a switching request status, and the protection source link status response message is received, it is determined that the protection source link status is normal.

[0129] In an exemplary embodiment, an embodiment of the present application provides a link state detection device, and the link state detection device is configured in a multicast device of a multicast transmission network. FIG. 4 is a schematic structural diagram of a link state detection device provided by an embodiment of the application. As shown in FIG. 4, the link state detection device in the embodiment of the present application may include: [0130] A detection message processing module 310, configured to receive a link state detection message sent by a client, and pass the configured reverse The unknown multicast group forwards the link state detection message to the target multicast source;

[0131] Wherein, the link state detection message is used to detect the working link state;

[0132] The client is used to send a link state detection message, and in the case of receiving a link state response message sent by the target multicast source, determine that the working link state is normal;

[0133] The target multicast source is configured to send the link state response message to the client according to the link state detection message.

[0134] In this embodiment of the application, the link state detection message sent by the client is received by the multicast device, and the link state detection message is forwarded to the target multicast source through the reverse unknown multicast group configured by the multicast device. So that the target multicast source sends a link state response message to the client according to the link state detection message, and the client determines the working chain after receiving the link state response message sent by the target multicast source The path status is normal, which solves the problem that the existing multicast transmission network cannot monitor the link status from the access point to the source node, so as to improve the link status detection mechanism and realize the link status monitoring from the access point to the source node.

[0135] In an example, the device further includes: a reverse unknown multicast group configuration module, configured to configure an original reverse unknown multicast group according to the target service of the multicast transmission network; The multicast information of the target multicast source is added to the original reverse unknown multicast group to configure the reverse unknown multicast group.

[0136] In an example, the reverse unknown multicast group configuration module is specifically configured to: add service members of the multicast device to the original reverse unknown multicast group.

[0137] In an example, the target multicast source includes a working multicast source and a protected multicast source; the target service includes a protected service; the service member includes a general leaf, and the working root and the protected root At least one.

[0138] In an example, the reverse unknown multicast group configuration module is specifically configured to: configure the general leaf, and set the

The next hop of the general leaf joins the original reverse unknown multicast group; configures the working root, and adds the next hop of the working root to the original reverse unknown multicast group; and/or, configure The protection root adds the next hop of the protection root to the original reverse unknown multicast group.

[0139] In an example, the business member includes a general leaf, a working root, and a protection root; the device may also include: a protection group forming module for forming a protection group according to the working root and the protection root; Wherein, the protection group is used to protect the link detection operation of the client.

[0140] In an example, the detection message processing module 310 is specifically configured to: search for the target service member included in the reverse unknown multicast group, so as to send the client according to the link sent by the target service member. The status detection message is forwarded to the target multicast source; wherein, the target service member includes the working root and the protection root.

[0141] In an example, the link state response message includes a working source link state response message; the working link state includes a working source link state; the client is used for: transmitting in the multicast In the case that there is no switching request state in the network state of the network, and the working source link state response message is received, it is determined that the working source link state is normal.

[0142] In an example, the link state response message includes a protection source link state response message; the working link state includes a protection source link state; the client is used for: in the multicast transmission When the network status of the network has a switching request status, and the protection source link status response message is received, it is determined that the protection source link status is normal. [0143] The above-mentioned link state detection device can execute the link state detection method provided by any embodiment of the present application, and has the functional modules and beneficial effects corresponding to the execution method. For technical details that are not described in detail in this embodiment, please refer to the link state detection method provided in any embodiment of this application.

[0144] Since the link state detection device introduced above is a device that can execute the link state detection method in the embodiment of the present application, based on the link state detection method introduced in the embodiment of the present application, the technology in the art Personnel can understand the specific implementation of the link state detection device of this embodiment and its various variations, so how the link state detection device implements the link state detection method in the embodiment of this application will not be described in detail here. . As long as those skilled in the art implement the link state detection method in the embodiment of the present application, the device shall fall within the scope of the protection of the present application.

[0145] In an exemplary embodiment, an embodiment of the present application provides a multicast device, and FIG. 5 is a schematic structural diagram of a multicast device provided by an embodiment of the application. As shown in FIG. 5, the multicast device in the embodiment of the present application may include: [0146] One or more processors 21 and a storage device 22; the multicast device may have one or more processors 21, as shown in FIG. 5 One processor 21 is taken as an example; the storage device 22 is used to store one or more programs; the one or more programs are executed by the one or more processors 21.

[0147] The processor 21 and the storage device 22 in the multicast device may be connected by a bus or in other ways. In FIG. 5, the connection by a bus is taken as an example.

[0148] As a computer-readable storage medium, the storage device 22 can be configured to store software programs, computer-executable programs, and modules. The storage device 22 may include a storage program area and a storage data area. The storage program area may store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the device, and the like. In addition, the storage device 22 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the storage device 22 may further include memories remotely provided with respect to the processor 21, and these remote memories may be connected to the main board through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0149] The multicast device provided in the embodiments of the present application can be configured with a reverse unknown multicast group, which is used to multicast the link state detection message sent by the client in the network through the reverse unknown multicast group. Forward to the target multicast source, so that the target multicast source sends a link state response message to the client according to the link state detection message, and causes the client to receive the link In the case of a status response message, it is determined that the working link status is normal.

[0150] In an exemplary embodiment, an embodiment of the present application provides a computer storage medium storing a computer program, which is used to execute any of the foregoing embodiments of the present invention when the computer program is executed by a computer processor. The link state detection method: receiving the link state detection message sent by the client, and forwarding the link state detection message to the target multicast source through the configured reverse unknown multicast group; wherein, the chain The path state detection message is used to detect the working link state; the client is used to send a link state detection message, and in the case of receiving a link state response message sent by the target multicast source, determine The working link status is normal; the target multicast source is used to send the link status response message to the client according to the link status detection message.

[0151] The computer storage medium of the embodiment of the present invention may adopt any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (Read Only Memory) , ROM), Erasable Programmable Read Only Memory ((Erasable Programmable Read Only Memory, EPROM) or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or the above Any suitable combination. In this document, the computer-readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, apparatus, or device.

[0152] A computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device .

[0153] The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the above.

[0154] The computer program code used to perform the operations of the present invention can be written in one or more programming languages or a combination thereof, the programming languages including object-oriented programming languages such as Java, Smalltalk, C++, and Including conventional procedural programming languages-such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any kind of network-including a local area network (LAN) or a wide area network (WAN)-or, it can be connected to an external computer (for example, using an Internet service provider to pass Internet connection).

[0155] The above are only exemplary embodiments of the present application, and are not used to limit the protection scope of the present application.

[0156] Those skilled in the art should understand that the term user terminal encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser, or a vehicle-mounted mobile station.

[0157] In general, the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.

In the realization. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0158] The embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code written in any combination of one or more programming languages or Object code.

[0159] The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function discs) DVD or CD) etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), programmable logic devices (FGPA) And processors based on multi-core processor architecture.

[0160] Through exemplary and non-limiting examples, a detailed description of the exemplary embodiments of the present application has been provided above. However, considering the accompanying drawings and claims, various modifications and adjustments to the above embodiments are obvious to those skilled in the art, but they do not deviate from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.