Multicast service design method, server and storage medium

Directly configuring the router through the SDN controller solves the problem of complex MP-BGP configuration in the BIER network, simplifies network deployment and architecture, and improves management efficiency.

CN114531392BActive Publication Date: 2024-12-03NANJING ZHONGXING SOFTWARE
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
CN202011210579.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-11-03
Publication Date
2024-12-03
Estimated Expiration
2040-11-03

AI Technical Summary

Technical Problem

In large BIER networks, the prior art requires MP-BGP to be configured on each bit forwarding router, resulting in complex network deployment and architecture, and forming a full-mesh MP-BGP neighbor, increasing the difficulty of network management.

Method used

The multicast service update event is obtained through the software-defined network (SDN) controller, the router to be configured and its configuration information are determined, and directly configured to the router, avoiding dependence on MP-BGP and simplifying network deployment and architecture.

Benefits of technology

Eliminate MP-BGP on each router node, simplifying network deployment and architecture, avoiding full mesh BGP neighbors between BFIR and BFER, and improving network management flexibility and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114531392B_ABST
    Figure CN114531392B_ABST
Patent Text Reader

Abstract

The embodiment of the present application relates to the field of communications, and discloses a multicast service design method, a server, and a storage medium. In the embodiment of the present application, the SDN controller obtains a multicast service update event; determines the router to be configured corresponding to the multicast service update event, and the configuration information corresponding to the router to be configured; the SDN controller can directly configure the configuration information to the router to be configured, and does not need to rely on MP-BGP, so there is no need to configure MP-BGP on each router node, simplifying network deployment, and there is no need to establish MP-BGP neighbors between BFIR and BFER, which can avoid the full mesh BGP neighbors between BFIR and BFER, simplifying the network architecture.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a multicast service design method, a server, and a storage medium. Background Art

[0002] Bit Index Explicit Replication (BIER) is a new type of multicast technology, in which a router with BIER capability is a Bit-Forward Router (BFR), and the domain composed of BFRs is called a BIER domain. The BFRs where multicast services enter and leave the BIER domain are called Bit-Forward Ingress Router (BFIR) and Bit-Forward Egress Router (BFER), respectively. When a multicast service enters the BIER domain, the BFIR determines the BFER set for the multicast service, and then encapsulates the multicast message into a BIER message for forwarding. When the BIER message arrives at the BFER, the BIER message header is unsealed and the multicast message is forwarded by multicast routing.

[0003] In a large BIER network, a router can be both a BFIR for one multicast service and a BFER for another multicast service. By configuring the Multi-Protocol Border Gateway Protocol (MP-BGP) on the BFIR and BFER, a fully meshed MP-BGP neighbor is formed between the BFIR and BFER, so that the BFIR and BFER of each multicast service can be determined through MP-BGP, and when the BFER joins or leaves the multicast service, the message of joining or leaving the multicast service is sent to the corresponding BFIR through MP-BGP, so that the BFER joins or leaves the multicast service. However, configuring MP-BGP on each BFIR and BFER makes the network deployment more complicated, and forming a fully meshed MP-BGP neighbor makes the network architecture more complicated. Summary of the invention

[0004] The embodiments of the present application provide a multicast service design method, a server, and a storage medium, which eliminates the need to configure MP-BGP on router nodes in order to implement a multicast forwarding mechanism, thereby simplifying network deployment and network architecture.

[0005] To achieve the above-mentioned purpose, an embodiment of the present application provides a multicast service design method, which is applied to a software-defined network (SDN) controller. The method includes: obtaining a multicast service update event; determining a router to be configured corresponding to the multicast service update event, and configuration information corresponding to the router to be configured; and configuring the configuration information to the router to be configured.

[0006] To achieve the above-mentioned purpose, an embodiment of the present application also provides a server, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the multicast service design method described above.

[0007] To achieve the above objectives, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned multicast service design method when executed by a processor.

[0008] The multicast service design method, server and storage medium proposed in the present application obtain multicast service update events; determine the router to be configured corresponding to the multicast service update event, and the configuration information corresponding to the router to be configured; the SDN controller can directly configure the configuration information to the router to be configured, and does not need to rely on MP-BGP, so there is no need to configure MP-BGP on each router node, simplifying network deployment, and there is no need to establish MP-BGP neighbors between BFIR and BFER, which can avoid the full mesh BGP neighbors between BFIR and BFER and simplify the network architecture. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a flowchart of a multicast service design method according to the first embodiment of the present application;

[0010] Figure 2 is a flowchart of a multicast service design method according to the second embodiment of the present application;

[0011] Figure 3 is a flow chart of a multicast service design method according to the third embodiment of the present application;

[0012] Figure 4 is a flowchart of a multicast service design method according to a fourth embodiment of the present application;

[0013] Figure 5 It is a schematic diagram of the structure of the server in the fifth embodiment of the present application. DETAILED DESCRIPTION

[0014] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. However, it will be appreciated by those skilled in the art that in the present application, many technical details are proposed in order to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical scheme claimed in the present application can also be implemented. The division of the following embodiments is for the convenience of description, and the specific implementation of the present application should not be construed as any limitation, and the various embodiments can be combined and referenced with each other under the premise of no contradiction.

[0015] The first embodiment of the present application relates to a multicast service design method, which is applied to a software defined network (SDN) controller. The specific process is as follows Figure 1 As shown, including:

[0016] Step 101: Acquire a multicast service update event.

[0017] Specifically, in a multicast network, multicast services may increase or decrease, and routers used to transmit multicast services, i.e., routers corresponding to multicast services, may also increase or decrease; for example, in Internet Protocol Television (IPTV), some customers may choose to add a channel service. If the channel is an existing channel, a Bit-Forward Egress Router (BFER) corresponding to the multicast service needs to be added to the multicast network. When a multicast service update event occurs, the router or customer management system will perceive it, and at this time the router or customer management system will send an instruction containing the multicast service update event to the SDN controller, and the SDN controller can obtain the multicast service update event from the instruction received by the router or from the instruction received by the customer management system; wherein, the customer management system is a system for managing customers receiving multicast services.

[0018] Step 102: Determine the router to be configured corresponding to the multicast service update event and the configuration information corresponding to the router to be configured.

[0019] Step 103: configure the configuration information to the router to be configured.

[0020] Specifically, the SDN controller determines the corresponding router to be configured and the configuration information corresponding to the router to be configured according to the type of event in the multicast service update event and the relationship between the multicast service and the router, wherein the type of event includes adding a new multicast service, increasing or reducing the router corresponding to the original multicast service, wherein reducing the original multicast service is equivalent to removing all the routers corresponding to the original multicast service; and, when the router to be configured is different, the configuration information corresponding to the router to be configured is also different, so the SDN controller needs to determine the configuration information corresponding to the router to be configured, for example: if the router to be configured is a bit forwarding ingress router (Bit-Forward Ingress Router, BFIR), the configuration information corresponding to the BFIR at least includes the correspondence between the multicast service and the BFER, and if the router to be configured is a BFER, the configuration information corresponding to the BFER at least includes the decapsulation method. The SDN controller then sends the configuration information to the router to be configured, and the router to be configured configures the configuration information.

[0021] In an example, if the multicast service update event includes a newly added multicast service, the router to be configured is the BFIR and BFER corresponding to the newly added multicast service; if the multicast service update event includes increasing or decreasing the BFIR corresponding to the original multicast service, or increasing or decreasing the BFER corresponding to the original multicast service, the router to be configured is the BFIR corresponding to the original multicast service.

[0022] Specifically, if the multicast service update event includes a newly added multicast service, that is, the type of the event is a newly added multicast service, then the SDN controller needs to determine at least the encapsulation method and decapsulation method of the message of the newly added multicast service in addition to determining the router corresponding to the newly added multicast service. The encapsulation method needs to be configured to the BFIR, and the decapsulation method needs to be configured to the BFER. Therefore, if the multicast service update event includes a newly added multicast service, the router to be configured at this time is the BFIR and BFER corresponding to the newly added multicast service. If the multicast service update event includes increasing or decreasing the BFIR corresponding to the original multicast service, or increasing or decreasing the BFER corresponding to the original multicast service, that is, the type of the event is increasing or decreasing the router corresponding to the original multicast service, since the encapsulation method and other information have been determined, only the BFIR or BFER has changed, at this time, it is only necessary to notify the BFIR corresponding to the original multicast service, so that the BFIR knows the increase or decrease of the BFIR corresponding to the original multicast service, or the BFIR knows the increase or decrease of the BFER corresponding to the original multicast service. Therefore, if the multicast service update event includes increasing or decreasing the BFIR corresponding to the original multicast service, or increasing or decreasing the BFER corresponding to the original multicast service, the router to be configured at this time is the BFIR corresponding to the original multicast service. Through this method, the corresponding router to be configured can be accurately determined for different multicast service update information, and corresponding processing can be performed, so as to achieve the flexibility of multicast service design.

[0023] In one example, if the multicast service update event includes a newly added multicast service, the router to be configured is the BFIR and BFER corresponding to the newly added multicast service; if the multicast service update event includes increasing or decreasing the BFIR corresponding to the original multicast service, or increasing or decreasing the BFER corresponding to the original multicast service, the router to be configured is the BFIR corresponding to the original multicast service. The configuration information corresponding to the BFIR includes the correspondence between the multicast service and the BFER; wherein, if the multicast service is the original multicast service, the BFER is determined according to one of the following instructions: determined according to an instruction received from the BFER added to the original multicast service, determined according to an instruction received from the BFER leaving the original multicast service, determined according to an instruction received from the customer management system; if the multicast service is a newly added multicast service, the BFER is determined according to the following instructions: determined according to an instruction received from the customer management system; the customer management system is a system for managing customers receiving multicast services.

[0024] Specifically, the SDN controller acts as the RR reflector, and both the BFIR and the BFER only establish neighbor relationships with the SDN controller, and the SDN controller communicates with the BFIR and the BFER. If the multicast service is an existing multicast service, the BFER added to the existing multicast service can sense the increase in customers, where customers refer to customers receiving multicast services. The BFER added to the existing multicast service will send instructions to the SDN controller. The SDN controller determines the BFER corresponding to the existing multicast service from the instructions received by the BFER added to the existing multicast service, and sends configuration information including the correspondence between the existing multicast service and the BFER to the BFIR corresponding to the existing multicast service. For example, the BFER corresponding to the existing multicast service 1 is A, B, and C, and the BFER added to the existing multicast service is D. Then D will send instructions to the SDN controller. The SDN controller can determine that the BFER corresponding to the multicast service is A, B, C, and D according to the instructions received from D. Then the SDN controller sends configuration information including the correspondence between the multicast service 1 and A, B, C, and D to the BFIR corresponding to the existing multicast service 1. If the multicast service is the original multicast service, the BFER that leaves the original multicast service can sense the departure of the customer, and the BFER that leaves the original multicast service will send an instruction to the SDN controller. The SDN controller determines the BFER corresponding to the original multicast service from the instruction received from the BFER that leaves the original multicast service, and sends the configuration information including the BFER corresponding to the original multicast service to the BFIR corresponding to the original multicast service. For example, the BFERs corresponding to the original multicast service 1 are A, B, and C, and the BFER that leaves the original multicast service is C. Then C will send an instruction to the SDN controller. The SDN controller can determine that the BFERs corresponding to the original multicast service are A and B according to the instruction received from C, and the SDN controller sends the configuration information including the correspondence between multicast service 1 and A and B to the BFIR corresponding to the original multicast service 1. If the multicast service is an existing multicast service, and the customer management system can also sense the BFER added to the existing multicast service and / or the BFER leaving the existing multicast service, the customer management system will send instructions to the SDN controller, and the instructions received by the SDN controller from the customer management system can determine the BFER corresponding to the existing multicast service, and send the configuration information including the BFER corresponding to the existing multicast service to the BFIR corresponding to the existing multicast service. If the multicast service is a newly added multicast service, and the customer management system can sense the addition to the newly added multicast service, the customer management system will send instructions to the SDN controller, and the instructions received by the SDN controller from the customer management system can determine the BFER corresponding to the newly added multicast service, and send the configuration information including the BFER corresponding to the newly added multicast service to the BFIR corresponding to the newly added multicast service.In one example, the configuration information sent to the BFIR corresponding to the newly added multicast service may also include the encapsulation method of the message, and the SDN controller also needs to send the configuration information including the decapsulation method of the message to the BFER corresponding to the newly added multicast service. In this way, the SDN controller can play the role of an RR reflector, and realize the correspondence between the multicast service and the BFER specified by the SDN controller.

[0025] In one example, the SDN controller includes a southbound interface and a northbound interface. The SDN controller interacts with a router in a multicast network through the southbound interface and interacts with external devices through the northbound interface, wherein the external devices include but are not limited to orchestrators, upper layer applications, third-party applications, etc. In this way, the SDN controller can interact using different interfaces according to different requirements.

[0026] In this embodiment, the SDN controller obtains a multicast service update event; determines the router to be configured corresponding to the multicast service update event, and the configuration information corresponding to the router to be configured; the SDN controller can directly configure the configuration information to the router to be configured, and does not need to rely on MP-BGP, so there is no need to configure MP-BGP on each router node, which simplifies network deployment, and there is no need to establish an MP-BGP neighbor between the BFIR and the BFER, which can avoid the full mesh BGP neighbor between the BFIR and the BFER, and simplify the network architecture.

[0027] The second embodiment of the present invention relates to a multicast service design method. The second embodiment is substantially the same as the first embodiment, with the main difference being that the updated attribute information of the BFIR is sent to the BFER corresponding to the target multicast service, thereby influencing the BFER's selection of the BFIR. The specific flow chart is as follows Figure 2 As shown, including:

[0028] Step 201: Acquire a multicast service update event.

[0029] Step 202: Determine the router to be configured corresponding to the multicast service update event and the configuration information corresponding to the router to be configured.

[0030] Step 203: configure the configuration information to the router to be configured.

[0031] Steps 201 - 203 are similar to steps 101 - 103 in the first embodiment and are not described in detail herein.

[0032] Step 204: If the attribute information of the BFIR corresponding to the target multicast service is updated, the updated attribute information of the BFIR is sent to the BFER corresponding to the target multicast service, so that the BFER corresponding to the target multicast service can determine the selection strategy for the BFIR corresponding to the target multicast service according to the updated attribute information of the BFIR.

[0033] Specifically, the SDN controller can also play an additional function as an RR reflector, that is, the SDN controller monitors the attribute information of the BFIR corresponding to the multicast service. If the attribute information of the BFIR corresponding to the target multicast service is updated, the SDN controller sends the updated attribute information of the BFIR to the BFER corresponding to the target multicast service, and the BFER determines the selection strategy for the BFIR corresponding to the target multicast service according to the updated attribute information of the BFIR. For example, if the BFIR corresponding to the target multicast service is M and N, and if the M corresponding to the target multicast service will be updated after 2 hours, M will update its own attribute information, then the SDN controller can monitor that the attribute information of M is updated, and send the updated attribute information of M to the BFER corresponding to the target multicast service, and the BFER determines whether to select M according to the updated attribute information of M. In an example, the BFER determines the priority ranking of all BFIRs corresponding to the target multicast service according to the updated attribute information of the BFIR, and determines the selection strategy for all BFIRs corresponding to the target multicast service according to the priority ranking.

[0034] In one example, the execution order of step 204 is not limited, and step 204 can be executed at any time.

[0035] In this embodiment, the SDN controller also sends the updated attribute information of the BFIR to the BFER corresponding to the target multicast service, that is, the SDN controller can play an additional function as an RR reflector to influence the BFER's selection of the BFIR.

[0036] The third embodiment of the present invention relates to a multicast service design method. The third embodiment is substantially the same as the first embodiment, with the main difference being that: the SDN controller also collects the link status information of the entire network, and generates a network node topology based on the link status information of the entire network; collects the link status information of the bit index display replication BIER, and generates a BIER node topology based on the link status information of BIER; collects the traffic information of BIER, and generates a BIER traffic topology based on the traffic information of BIER. The specific flow chart is as follows: Figure 3 As shown, including:

[0037] Step 301: Acquire a multicast service update event.

[0038] Step 302: Determine the router to be configured corresponding to the multicast service update event and the configuration information corresponding to the router to be configured.

[0039] Step 303: configure the configuration information to the router to be configured.

[0040] Steps 301 - 303 are similar to steps 101 - 103 in the first embodiment and are not described in detail here.

[0041] Step 304: collect link status information of the entire network, and generate a network node topology based on the link status information of the entire network.

[0042] Step 305, collect the bit index display to replicate the link status information of BIER, and generate the BIER node topology based on the link status information of BIER.

[0043] Specifically, the Bit Index Explict Replication (BIER) node extends the BIER information in the multicast network through the Interior Gateway Protocol (IGP) extension protocol, wherein the BIER information is carried in the BIER prefix, and the BIER information includes at least one of the following or any combination thereof: Bit-Forward Router Identify (BFR-ID), Bit String Length (BSL), Sub Domain (SD). The SDN controller collects the link status information of the entire network and the link status information of BIER through the southbound interface based on the Border Gateway Protocol link state (BGP-LS) and the IGP extension protocol, and generates the network node topology based on the link status information of the entire network, and generates the BIER node topology based on the link status information of the BIER. In this way, the network nodes that do not support BIER and the network nodes that support BIER in the entire network can be distinguished, and when the message passes through the network node that does not support BIER, the tunnel is transparently transmitted.

[0044] In one example, after generating the network node topology according to the link status information of the whole network and generating the BIER node topology according to the link status information of the BIER, it also includes: obtaining the BIER forwarding tables corresponding to each BIER node according to the network node topology and the BIER node topology; sending each BIER forwarding table to the corresponding BIER nodes. Specifically, the SDN controller calculates the BIER forwarding table of each BIER node according to the network node topology and the BIER node topology using the locally configured algorithm, and sends each BIER forwarding table to the corresponding BIER nodes. Each BIER can determine the forwarding path according to the BIER forwarding table, and transmit the multicast service message to the corresponding BFER according to the forwarding path. Through this method, since each BIER forwarding table is sent to each BIER node, the BIER node can directly determine the forwarding path according to the BIER forwarding table more quickly. In one example, the SDN controller uses a unified algorithm to calculate the BIER forwarding table of each BIER node, which can shield the differences in algorithm support from different manufacturers, and can also shield the differences in the implementation of the same algorithm by different manufacturers.

[0045] Step 306, collect BIER traffic information and generate BIER traffic topology based on the BIER traffic information.

[0046] In one example, the SDN controller can collect BIER traffic information by itself, and generate a BIER traffic topology based on the BIER traffic information. In one example, collecting BIER traffic information includes: receiving multicast service messages reported by each BIER node, and obtaining BIER traffic information from the multicast service messages; wherein, a multicast service message is collected from every N multicast service messages passing through the BIER node, and N is a positive integer. Specifically, the BIER node supports the NetFlow function, which is a network monitoring function that can collect the number and information of packets entering and leaving the network interface. The port of the BIER node collects one multicast service message from every N multicast service messages passing through the BIER node, and N is a positive integer, and reports the collected multicast service messages to the SDN controller. For example: N is 10, and the port of BIER node L collects one multicast service message from every 10 multicast service messages passing through BIER node L. When the SDN controller receives the multicast service messages reported by each BIER node, it can obtain the BIER traffic information from the multicast service messages. For example, BIER nodes may use different identification fields to represent different types of multicast service messages. The NextHead field of Internet Protocol Version 6 (IPv6) is used to represent Bierin6's multicast service messages, the field of the label value range is used to represent Multi-Protocol Label Switching (MPLS), and the type field is used to represent Ethernet protocol multicast service messages. Therefore, the SDN controller can obtain the BIER traffic type based on the field. Through this method, there may be a situation where the BIER node does not need to collect and report all multicast service messages, which can reduce the workload.

[0047] In one example, the execution order of steps 304 - 306 is not limited, and steps 304 - 306 can be executed at any time.

[0048] In one example, the multicast service design method may include steps 301-303, and any one of steps 304-306 or a combination of any two of steps 304-306. Through such a method, at least one of the following may be generated: network node topology, BIER traffic topology, BIER traffic topology, to facilitate the development of multicast services.

[0049] In one example, the method also includes: if the attribute information of the BFIR corresponding to the target multicast service is updated, the updated attribute information of the BFIR is sent to the BFER corresponding to the target multicast service, so that the BFER corresponding to the target multicast service determines the selection strategy for the BFIR corresponding to the target multicast service according to the updated attribute information of the BFIR.

[0050] In this embodiment, the SDN controller also collects link status information of the entire network, and generates a network node topology based on the link status information of the entire network; collects link status information of the bit index display replication BIER, and generates a BIER node topology based on the link status information of BIER; collects BIER traffic information, and generates a BIER traffic topology based on the BIER traffic information. In this way, the SDN controller can generate network node topology, BIER traffic topology, and BIER traffic topology to facilitate the development of multicast services.

[0051] The fourth embodiment of the present invention relates to a multicast service design method. The fourth embodiment is substantially the same as the first embodiment, with the main difference being that the status information of the BIER node is collected, and a diagnostic service is provided to the BIER node when the status information indicates that the BIER node is in an abnormal state. The specific flow chart is as follows Figure 4 As shown, including:

[0052] Step 401: Acquire a multicast service update event.

[0053] Step 402: Determine the router to be configured corresponding to the multicast service update event and the configuration information corresponding to the router to be configured.

[0054] Step 403: configure the configuration information to the router to be configured.

[0055] Steps 401-403 are similar to steps 101-103 in the first embodiment and are not described in detail here.

[0056] Step 404, collect status information of the BIER node, and provide diagnostic services to the BIER node when the status information indicates that the BIER node is in an abnormal state.

[0057] Specifically, the status information includes but is not limited to one of the following or any combination thereof: memory usage, central processing unit CPU usage, queues, etc. The SDN controller can provide network element management services, monitor the status information of the BIER node by itself, and determine whether the status of the BIER node is in an abnormal state; or the BIER node can actively report the status information to the SDN controller using an interface, and the SDN controller determines whether the status of the BIER node is in an abnormal state based on the reported status information; wherein, the BIER node can actively report the status information according to a preset period, and the preset period can be pre-set according to actual needs, and this implementation does not make specific restrictions, for example: reporting status information every 30 seconds; or it can actively report status information when an event trigger occurs, and the event triggering conditions can be pre-set according to actual needs, and this implementation does not make specific restrictions, for example: reporting status information when the average usage of the central processing unit CPU is greater than a preset threshold. When the status information indicates that the BIER node is in an abnormal state, the SDN controller can send an alarm to the BIER node and / or provide diagnostic services such as solutions.

[0058] In one example, the execution order of step 404 is not limited, and step 404 can be executed at any time.

[0059] In one example, after collecting the status information of the BIER node, the SDN controller also generates relevant data reports and views to display the status of the BIER node in real time.

[0060] In one example, the SDN controller also saves the hardware version information and software version information of each BIER node. The SDN controller monitors the hardware version information and software version information of each BIER node, compares them with the saved hardware version information and software version information, and gives suggestions for version upgrades.

[0061] In one example, the SDN controller receives configuration data from an orchestrator or an upper-layer application or a third-party application, converts the configuration data into configuration data of a YANG model, and sends the configuration data of the YANG model to a BIER node, which then performs automatic configuration based on the configuration data of the YANG model.

[0062] In one example, the method also includes: if the attribute information of the BFIR corresponding to the target multicast service is updated, the updated attribute information of the BFIR is sent to the BFER corresponding to the target multicast service, so that the BFER corresponding to the target multicast service determines the selection strategy for the BFIR corresponding to the target multicast service according to the updated attribute information of the BFIR.

[0063] In one example, the method also includes one of the following steps or any combination thereof: collecting link status information of the entire network, and generating a network node topology based on the link status information of the entire network; collecting link status information of the bit index display replication BIER, and generating a BIER node topology based on the link status information of BIER; collecting BIER traffic information, and generating a BIER traffic topology based on the BIER traffic information.

[0064] In one example, the method further includes: if the attribute information of the BFIR corresponding to the target multicast service is updated, the updated attribute information of the BFIR is sent to the BFER corresponding to the target multicast service, so that the BFER corresponding to the target multicast service can determine the selection strategy for the BFIR corresponding to the target multicast service according to the updated attribute information of the BFIR. And the method further includes one of the following steps or any combination thereof: collecting the link status information of the entire network, and generating the network node topology according to the link status information of the entire network; collecting the link status information of the bit index display copy BIER, and generating the BIER node topology according to the link status information of the BIER; collecting the traffic information of the BIER, and generating the BIER traffic topology according to the traffic information of the BIER.

[0065] In this embodiment, the SDN controller also collects status information of the BIER node, and provides diagnostic services to the BIER node when the status information indicates that the BIER node is in an abnormal state, that is, SDN control can provide network element management services for the BIER node.

[0066] A fifth embodiment of the present invention relates to a server, such as Figure 5 As shown, it includes at least one processor 502; and a memory 501 that is communicatively connected to the at least one processor; wherein the memory 501 stores instructions that can be executed by the at least one processor 502, and the instructions are executed by the at least one processor 502 so that the at least one processor 502 can execute an embodiment of the above-mentioned multicast service design method.

[0067] The memory 501 and the processor 502 are connected in a bus manner, and the bus may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors 502 and the memory 501 together. The bus can also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. The data processed by the processor 502 is transmitted on a wireless medium via an antenna, and further, the antenna also receives data and transmits the data to the processor 502.

[0068] The processor 502 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management and other control functions. The memory 501 can be used to store data used by the processor 502 when performing operations.

[0069] A sixth embodiment of the present invention relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0070] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0071] Those skilled in the art will appreciate that the above embodiments are specific embodiments for implementing the present invention, and that in actual applications, various changes may be made in form and detail without departing from the spirit and scope of the present invention.

Claims

1. A multicast service design method, characterized in that: Applied to a software defined network (SDN) controller, the method comprises: Get multicast service update events; Determine the router to be configured corresponding to the multicast service update event, and configuration information corresponding to the router to be configured; Configuring the configuration information to the router to be configured; Wherein, if the multicast service update event includes a newly added multicast service, the router to be configured is a bit forwarding ingress router BFIR and a bit forwarding egress router BFER corresponding to the newly added multicast service; If the multicast service update event includes increasing or decreasing the BFIR corresponding to the original multicast service, or increasing or decreasing the BFER corresponding to the original multicast service, the router to be configured is the BFIR corresponding to the original multicast service.

2. The multicast service design method according to claim 1, characterized in that: The configuration information corresponding to the BFIR includes the correspondence between the multicast service and the BFER; Among them, if the multicast service is the original multicast service, the BFER is determined according to one of the following instructions: determined according to an instruction received from a BFER added to the original multicast service, determined according to an instruction received from a BFER leaving the original multicast service, and determined according to an instruction received from a customer management system; if the multicast service is the newly added multicast service, the BFER is determined according to the following instructions: determined according to an instruction received from the customer management system; the customer management system is a system for managing customers receiving multicast services.

3. The multicast service design method according to claim 1, characterized in that: The method further comprises: If the attribute information of the BFIR corresponding to the target multicast service is updated, the updated attribute information of the BFIR is sent to the BFER corresponding to the target multicast service, so that the BFER corresponding to the target multicast service can determine the selection strategy for the BFIR corresponding to the target multicast service according to the updated attribute information of the BFIR.

4. The multicast service design method according to claim 1, characterized in that: The method further comprises at least one of the following: Collecting link status information of the entire network, and generating a network node topology based on the link status information of the entire network; The collection bit index displays the link status information of the replicated BIER, and generates the BIER node topology based on the link status information of the BIER; Collect BIER traffic information and generate BIER traffic topology based on the BIER traffic information.

5. The multicast service design method according to claim 4, characterized in that: After generating the network node topology according to the link status information of the whole network and generating the BIER node topology according to the link status information of the BIER, the method further includes: According to the network node topology and the BIER node topology, obtain the BIER forwarding tables corresponding to the BIER nodes respectively; Each of the BIER forwarding tables is sent to the corresponding BIER nodes respectively.

6. The multicast service design method according to claim 4, characterized in that: The collected BIER traffic information includes: Receive the multicast service messages reported by each BIER node, and obtain the BIER traffic information from the multicast service messages; wherein, the multicast service message is collected from every N multicast service messages passing through the BIER node, and N is a positive integer.

7. The multicast service design method according to claim 1, characterized in that: The method further comprises: Collect status information of the BIER node, and provide diagnostic services to the BIER node when the status information indicates that the BIER node is in an abnormal state.

8. A server, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the multicast service design method according to any one of claims 1 to 7.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the multicast service design method according to any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • Method for providing multicast service and software defined network controller

    CN106357542A

  • Transmission method, apparatus and system of BIER control information

    CN106656524A

  • Method, device and system for fast rerouting processing

    CN107204920A

  • Address configuration method and device in software-defined network system

    CN108206783A

  • Data transmission method, device and system

    CN108632678A