WO2022095769A1

WO2022095769A1 - Multicast service design method, server and storage medium

Info

Publication number: WO2022095769A1
Application number: PCT/CN2021/126782
Authority: WO
Inventors: 马汝胜
Original assignee: 中兴通讯股份有限公司
Priority date: 2020-11-03
Filing date: 2021-10-27
Publication date: 2022-05-12
Also published as: CN114531392A

Abstract

The embodiments of the present application relate to the field of communications, and disclose a multicast service design method, a server and a storage medium. In the embodiments of the present application, an SDN controller acquires a multicast service update event, determines a router to be configured, corresponding to the multicast service update event, and configuration information corresponding to said router, and the SDN controller can directly configure said router with the configuration information.

Description

Multicast service design method, server and storage medium

cross reference

This application is based on the Chinese patent application with the application number "202011210579.6" and the application date is November 03, 2020, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference. Apply.

technical field

The embodiments of the present application relate to the field of communications, and in particular, to a method for designing a multicast service, a server, and a storage medium.

Background technique

Bit Index Explicit Replication (BIER) is a new type of multicast technology, in which the router with BIER capability is the Bit-Forward Router (BFR), and the domain composed of BFR is called the BIER domain. The BFRs entering and leaving the BIER domain for multicast services are called Bit-Forward Ingress Router (BFIR) and Bit-Forward Egress Router (BFER) respectively. When a multicast service enters the BIER domain, BFIR determines the BFER set of the multicast service, and then encapsulates the multicast packet into a BIER packet for forwarding. When the BIER packet reaches the BFER, it decapsulates the BIER packet header and sends a multicast report. multicast routing forwarding.

In a large-scale BIER network, a router can be either a BFIR of a multicast service or a BFER of another multicast service. By configuring Multi-Protocol Border Gateway Protocol (MP-BGP) on BFIR and BFER, a full-mesh MP-BGP neighbor can be formed between BFIR and BFER, so that MP-BGP can determine each BFIR and BFER of a multicast service, and when 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 can join or leave the multicast service. However, configuring MP-BGP on each BFIR and BFER leads to complicated network deployment, and forming a full mesh of MP-BGP neighbors leads to complicated network architecture.

SUMMARY OF THE INVENTION

An embodiment of the present application provides a method for designing a multicast service, which is applied to a software-defined network SDN controller. The method includes: acquiring 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; configure the configuration information to the router to be configured.

An embodiment of the present application further provides a server, including: 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 , the instruction is executed by the at least one processor, so that the at least one processor can execute the above-mentioned method for designing a multicast service.

Embodiments of the present application further provide a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the above-mentioned method for designing a multicast service is implemented.

Description of drawings

1 is a flowchart of a method for designing a multicast service according to a first embodiment of the present application;

2 is a flowchart of a method for designing a multicast service according to a second embodiment of the present application;

3 is a flowchart of a method for designing a multicast service according to a third embodiment of the present application;

4 is a flowchart of a method for designing a multicast service according to a fourth embodiment of the present application;

FIG. 5 is a schematic structural diagram of a server according to a fifth embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the embodiments of the present application more clear, each embodiment of the present application will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can understand that, in each embodiment of the present application, many technical details are provided for 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 solutions claimed in the present application can be realized. The following divisions of the various embodiments are for the convenience of description, and should not constitute any limitation on the specific implementation of the present application, and the various embodiments may be combined with each other and referred to each other on the premise of not contradicting each other.

The embodiments of the present application provide a multicast service design method, server and 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.

The first embodiment of the present application relates to a method for designing a multicast service, which is applied to a software defined network (Software Defined Network, SDN) controller. The specific process is shown in Figure 1, including:

Step 101: Obtain a multicast service update event.

Specifically, in a multicast network, multicast services may increase or decrease, and routers used to transmit multicast services, that is, routers corresponding to multicast services, may also increase or decrease; In Internet Protocol Television, IPTV), some customers may choose to add a channel service. If the channel is the original channel, the multicast network needs to add a bit-forwarding egress router (Bit-Forward Egress router) corresponding to the multicast service. Router, BFER). When a multicast service update event occurs, the router or customer management system will perceive it, and the router or customer management system will send an instruction containing the multicast service update event to the SDN controller. The SDN controller can receive the instruction from the router or The multicast service update event is obtained from the instruction received by the client management system; wherein, the client management system is a system for managing clients receiving multicast services.

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.

Step 103, configure the configuration information to the router to be configured.

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 the event in the multicast service update event and the relationship between the multicast service and the router, where the type of the event includes the newly added router. Multicast service, adding or reducing the routers corresponding to the original multicast service, among which, reducing the original multicast service is equivalent to reducing all the routers corresponding to the original multicast service; moreover, the routers to be configured are not the same as the routers to be configured The corresponding configuration information 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-Forward Ingress Router (BFIR), the configuration information corresponding to BFIR at least includes the group The corresponding relationship between broadcast services and BFER. If the router to be configured is BFER, the configuration information corresponding to BFER at least includes the decapsulation mode. The SDN controller then sends the configuration information to the router to be configured, and the router to be configured configures the configuration information.

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 adding or reducing the original multicast service The corresponding BFIR, or, increase or decrease the BFER corresponding to the original multicast service, and the router to be configured is the BFIR corresponding to the original multicast service.

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, in this case, the SDN controller needs to determine at least the router corresponding to the newly added multicast service. It is also necessary to determine the encapsulation mode and decapsulation mode of the newly added multicast service packets. The encapsulation mode needs to be set to BFIR, and the decapsulation mode needs to be set to BFER. Therefore, if the multicast service update event includes the 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 adding or reducing the BFIR corresponding to the original multicast service, or adding or reducing the BFER corresponding to the original multicast service, that is, the event type is adding or reducing 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 can know the increase or decrease of the BFIR corresponding to the original multicast service, or make the BFIR Knowing the increase or decrease of the BFER corresponding to the original multicast service, if the multicast service update event includes the increase or decrease of the BFIR corresponding to the original multicast service, or the increase or decrease of the BFER corresponding to the original multicast service, then The router to be configured is the BFIR corresponding to the original multicast service. Through such a method, the corresponding routers to be configured can be accurately determined for different multicast service update information, and corresponding processing is performed, thereby realizing the flexibility of multicast service design.

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 adding or reducing the original multicast service The corresponding BFIR, or, increase or decrease the BFER corresponding to the original multicast service, and 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: According to the instruction received from the BFER added to the original multicast service Determined, determined according to the instruction received from the BFER that left the original multicast service, determined according to the instruction received from the client management system; if the multicast service is a newly added multicast service, the BFER is determined according to the following instructions: According to the client management system The received instruction is determined; the client management system is a system for managing clients receiving multicast services.

Specifically, the SDN controller acts as an RR reflector. Both BFIR and BFER only establish neighbor relationships with the SDN controller, and the SDN controller communicates with BFIR and BFER. If the multicast service is the original multicast service, the BFER added to the original multicast service can perceive the increase of customers. The customer refers to the customer who receives the multicast service, and the BFER added to 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 added to the original multicast service, and sends the configuration information including the correspondence between the original multicast service and the BFER. For the BFIR corresponding to the original multicast service, for example: the BFER corresponding to the original multicast service 1 is A, B, and C, and the BFER added to the original multicast service is D, then D will send an instruction to the SDN controller, The SDN controller can determine that the BFERs corresponding to the multicast service are A, B, C, and D according to the instruction received from D, and the SDN controller will include the configuration information of the correspondence between the multicast service 1 and A, B, C, and D. It is sent to the BFIR corresponding to the original multicast service 1. If the multicast service is the original multicast service, the BFER leaving the original multicast service can sense the departure of the customer, and the BFER leaving the original multicast service will send an instruction to the SDN controller. The instruction received by the BFER with the multicast service determines the BFER corresponding to 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 original group The BFER corresponding to the multicast service 1 is 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, and the SDN controller can determine the original multicast service according to the instruction received from C. The corresponding BFERs are A and B, 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 the original multicast service, and the customer management system can also perceive the BFER added to the original multicast service and/or the BFER that leaves the original multicast service, the customer management system will send an instruction to the SDN controller , the instruction received by the SDN controller from the customer management system can determine the BFER corresponding to the original multicast service, and send the configuration information including the BFER corresponding to the original multicast service to the BFIR corresponding to the original multicast service. If the multicast service is a newly added multicast service, and the client management system can perceive the addition of the newly added multicast service, the client management system will send an instruction to the SDN controller, and the instruction received by the SDN controller from the client management system can be The BFER corresponding to the newly added multicast service is determined, and the configuration information including the BFER corresponding to the newly added multicast service is sent 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 packet encapsulation mode, and the SDN controller also needs to send the configuration information including the packet decapsulation mode to the newly added multicast service. The corresponding BFER of the multicast service. Through such a method, the SDN controller can function as an RR reflector to realize the corresponding relationship between multicast services and BFER specified by the SDN controller.

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

In this embodiment, the SDN controller acquires the 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, There is no need to rely on MP-BGP, so there is no need to configure MP-BGP on each router node, which simplifies network deployment, and does not need to establish MP-BGP neighbors between BFIR and BFER, which can avoid the complete conflict between BFIR and BFER. Mesh BGP neighbors to simplify network architecture.

The second embodiment of the present application relates to a method for designing a multicast service. The second embodiment is roughly the same as the first embodiment, and the main difference is that the updated attribute information of the BFIR is sent to the BFER corresponding to the target multicast service. , thereby affecting the choice of BFER over BFIR. The specific flow chart is shown in Figure 2, including:

Step 201, acquiring a multicast service update event.

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.

Step 203, configure the configuration information to the router to be configured.

Steps 201-203 are similar to steps 101-103 in the first embodiment, and are not repeated here.

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 use the updated attribute of the BFIR according to the updated attribute information of the BFIR. The information determines the selection strategy of the BFIR corresponding to the target multicast service.

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 control The 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 of the BFIR corresponding to the target multicast service according to the updated attribute information of the BFIR. For example, the BFIRs corresponding to the target multicast service are M and N. If M corresponding to the target multicast service will be updated after 2 hours, and M will update its own attribute information, the SDN controller can monitor the attributes of M. When the information is updated, the updated attribute information of M is sent 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 one example, the BFER determines the priority ordering of all BFIRs corresponding to the target multicast service according to the updated attribute information of the BFIRs, and determines the selection strategy for all the BFIRs corresponding to the target multicast service according to the priority ordering.

In one example, the order in which step 204 is performed is not limited, and step 204 may be performed at any time.

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, affecting the selection of the BFIR by the BFER.

The third embodiment of the present application relates to a method for designing a multicast service. The third embodiment is roughly the same as the first embodiment. The main difference is that the SDN controller also collects link status information of the entire network, and performs a The link status information of the BIER is collected to generate the network node topology; the collection bit index displays the link status information of the copied BIER, and the BIER node topology is generated according to the link status information of the BIER; the flow information of the BIER is collected, and the BIER traffic is generated according to the flow information of the BIER topology. The specific flowchart is shown in Figure 3, including:

Step 301, acquiring a multicast service update event.

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.

Step 303, configure the configuration information to the router to be configured.

Steps 301-303 are similar to steps 101-103 in the first embodiment, and are not repeated here.

Step 304: Collect link status information of the entire network, and generate a network node topology according to the link status information of the entire network.

Step 305 , collect the bit index to display the link state information of the duplicate BIER, and generate the BIER node topology according to the link state information of the BIER.

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 is carried in the BIER prefix. The information includes at least one of the following or any combination thereof: bit-forward router identification (Bit-Forward Router Identify, BFR-ID), bit string length (BitString Length, BSL), sub domain (Sub Domain, SD). The SDN controller collects the link state information of the whole network and the link state information of BIER through the southbound interface based on the Border Gateway Protocol link state (Border Gateway Protocol link state, BGP-LS) and the IGP extension protocol. The link state information generates the network node topology, and the BIER node topology is generated according to the link state information of the BIER. In this way, network nodes that do not support BIER and network nodes that support BIER can be distinguished in the entire network, and when packets pass through the network nodes that do not support BIER, tunnel transparent transmission is performed.

In one example, after generating the network node topology according to the link state information of the entire network and generating the BIER node topology according to the link state information of the BIER, the method further includes: obtaining the corresponding corresponding BIER nodes according to the network node topology and the BIER node topology. Each BIER forwarding table is sent; each BIER forwarding table is sent to each corresponding BIER node. Specifically, the SDN controller calculates the BIER forwarding table of each BIER node according to the network node topology and the BIER node topology, and uses a locally configured algorithm, and sends each BIER forwarding table to the corresponding BIER nodes. The BIER forwarding table determines the forwarding path, and transmits the multicast service packets 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 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 by different manufacturers, as well as differences in implementation of the same algorithm by different manufacturers.

In step 306, the traffic information of the BIER is collected, and a BIER traffic topology is generated according to the traffic information of the BIER.

In one example, the SDN controller can collect the BIER traffic information by itself, and generate the BIER traffic topology according to the BIER traffic information. In an example, collecting BIER traffic information includes: receiving multicast service packets reported by each BIER node, and obtaining BIER traffic information from the multicast service packets; wherein, the multicast service packets are sent from the BIER node through the BIER node. Collect one out of every N multicast service packets, where 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 a multicast service packet from every N multicast service packets passing through the BIER node, where N is a positive integer, and reports the collected multicast service packets to the SDN controller, for example: N is 10. The port of the BIER node L collects one multicast service packet from every 10 multicast service packets passing through the BIER node L. When the SDN controller receives the multicast service packets reported by each BIER node, the SDN controller can obtain the BIER traffic information from the multicast service packets. For example, BIER nodes may use different identification fields to represent different multicast services. The type of the packet. For Bierin6 multicast service packets, the NextHead field of Internet Protocol Version 6 (IPv6) is used to indicate, and for Multi-Protocol Label Switching (MPLS) multicast services The message is represented by the field of the value range of the label, and the multicast service message of the Ethernet protocol is represented by the type field, so the SDN controller can obtain the BIER traffic type according to the field. With this method, there may be situations where the BIER node does not need to collect and report all multicast service packets, which can reduce the workload.

In one example, the order in which steps 304-306 are performed is not limited, and steps 304-306 may be performed at any time.

In one example, the method for designing a multicast service 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 can be generated: network node topology, BIER traffic topology, and BIER traffic topology, which facilitates the development of multicast services.

In one example, the method further includes: if the attribute information of the BFIR corresponding to the target multicast service is updated, sending the updated attribute information of the BFIR to the BFER corresponding to the target multicast service for the BFER corresponding to the target multicast service to The updated attribute information of the BFIR determines the selection strategy of the BFIR corresponding to the target multicast service.

In this embodiment, the SDN controller also collects link status information of the entire network, and generates a network node topology according to the link status information of the entire network; Status information generates BIER node topology; BIER traffic information is collected, and BIER traffic topology is generated according to BIER traffic information, so that the SDN controller can generate network node topology, BIER traffic topology, and BIER traffic topology to facilitate the development of multicast services.

The fourth embodiment of the present application relates to a method for designing a multicast service. The fourth embodiment is roughly the same as the first embodiment, and the main difference is that the state information of the BIER node is collected, and when the state information indicates that the BIER node is in an abnormal state Provide diagnostic services to BIER nodes. The specific flowchart is shown in Figure 4, including:

Step 401, acquiring a multicast service update event.

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.

Step 403, configure the configuration information to the router to be configured.

Steps 401-403 are similar to steps 101-103 in the first embodiment, and are not repeated here.

Step 404: Collect state information of the BIER node, and provide a diagnosis service to the BIER node when the state information indicates that the BIER node is in an abnormal state.

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, and the like. 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 use the interface to actively report the status information to the SDN controller, and the SDN controller can report the status information according to the report. The state information of the BIER node determines whether the state of the BIER node is in an abnormal state; wherein, the BIER node can actively report the state information according to a preset period, and the preset period can be preset according to actual needs, which is not specifically limited in this implementation, for example: every Status information is reported once every 30 seconds; it can also actively report status information when an event is triggered. The conditions for event triggering can be preset according to actual needs, which are not specifically limited in this implementation, for example: the average utilization rate of the central processing unit (CPU) Report status information when it is greater than the preset threshold. When the status information indicates that the BIER node is in an abnormal state, the SDN controller may issue an alarm to the BIER node and/or provide diagnostic services such as solutions.

In one example, the order in which step 404 is performed is not limited, and step 404 may be performed at any time.

In one example, after collecting the status information of BIER nodes, the SDN controller also generates related data reports and views, so as to display the status of BIER nodes in real time.

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, and compares them with the saved hardware version information and software version information. The software version information is compared, and suggestions for version upgrade are given.

In one example, the SDN controller receives the configuration data of the orchestrator or the upper-layer application or the third-party application, the SDN controller converts the configuration data into the configuration data of the YANG model, and sends the configuration data of the YANG model to the BIER node, Automatic configuration by the BIER node based on the configuration data of the YANG model.

In one example, the method further includes one or any combination of the following steps: collecting link status information of the entire network, and generating a network node topology according to the link status information of the entire network; collecting the bit index to display the link status of the replicated BIER information, and generate BIER node topology according to BIER link state information; collect BIER traffic information, and generate BIER traffic topology according to BIER traffic information.

In one example, the method further includes: if the attribute information of the BFIR corresponding to the target multicast service is updated, sending the updated attribute information of the BFIR to the BFER corresponding to the target multicast service for the BFER corresponding to the target multicast service to The updated attribute information of the BFIR determines the selection strategy of the BFIR corresponding to the target multicast service. And 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 according to the link status information of the entire network; BIER link state information generates BIER node topology; BIER traffic information is collected, and BIER traffic topology is generated according to BIER traffic information.

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

The fifth embodiment of the present application relates to a server, as shown in FIG. 5 , comprising at least one processor 502 ; and a memory 501 communicatively connected to the at least one processor; wherein, the memory 501 stores data that can be used by the at least one processor 502 The executed instructions are executed by the at least one processor 502, so that the at least one processor 502 can execute the above-mentioned embodiments of the multicast service design method.

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

Processor 502 is responsible for managing the bus and general processing, and may also provide various functions including timing, peripheral interface, voltage regulation, power management, and other control functions. The memory 501 may be used to store data used by the processor 502 in performing operations.

The sixth embodiment of the present application relates to a computer-readable storage medium storing a computer program. The above method embodiments are implemented when the computer program is executed by the processor.

That is, those skilled in the art can understand that all or part of the steps in the method for implementing the above embodiments can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments 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), magnetic disk or optical disk and other media that can store program codes .

Those of ordinary skill in the art can understand that the above-mentioned embodiments are specific embodiments for realizing the present application, and in practical applications, various changes in form and details can be made without departing from the spirit and the spirit of the present application. scope.

Claims

A multicast service design method, applied to a software-defined network SDN controller, the method includes:

Get multicast service update events;

determining the router to be configured corresponding to the multicast service update event, and the configuration information corresponding to the router to be configured;

Configure the configuration information to the router to be configured.
The method for designing a multicast service according to claim 1, wherein if the multicast service update event includes a newly added multicast service, the router to be configured is a bit forwarding entry corresponding to the newly added multicast service router BFIR and bit forwarding egress router BFER;

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. BFIR.
The multicast service design method according to claim 2, wherein the configuration information corresponding to the BFIR comprises 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 added to the original multicast service, The instruction received by the BFER of the original multicast service is determined according to the instruction received from the client management system; if the multicast service is the newly added multicast service, the BFER is determined according to the following instructions: The instruction received by the client management system is determined; the client management system is a system for managing clients receiving multicast services.
The multicast service design method according to any one of claims 1 to 3, wherein 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 for the BFER corresponding to the target multicast service according to the BFIR The updated attribute information of the target multicast service determines the selection strategy of the BFIR corresponding to the target multicast service.
The multicast service design method according to any one of claims 1 to 4, wherein the method further comprises at least one of the following:

collecting link status information of the entire network, and generating a network node topology according to the link status information of the entire network;

Collecting the bit index to display the link state information of the copy BIER, and generate the BIER node topology according to the link state information of the BIER;

The flow information of the BIER is collected, and a BIER flow topology is generated according to the flow information of the BIER.
The multicast service design method according to claim 5, wherein, after the generating of the network node topology according to the link state information of the whole network and the generating of the BIER node topology according to the link state information of the BIER, The method also includes:

Obtain each BIER forwarding table corresponding to each BIER node according to the network node topology and the BIER node topology;

Each of the BIER forwarding tables is sent to the corresponding BIER nodes respectively.
The method for designing a multicast service according to claim 5 or 6, wherein the collecting the traffic information of BIER comprises:

Receive the multicast service message reported by each BIER node, and obtain the BIER traffic information from the multicast service message; wherein, the multicast service message is sent from every N multicast service message passing through the BIER node. One is collected in the text, and N is a positive integer.
The multicast service design method according to any one of claims 1 to 7, wherein the method further comprises:

The state information of the BIER node is collected, and a diagnosis service is provided to the BIER node when the state information indicates that the BIER node is in an abnormal state.
A server that includes:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the multicasting of claims 1 to 8 business design methodology.
A computer-readable storage medium storing a computer program, when the computer program is executed by a processor, the method for designing a multicast service described in claims 1 to 8 is implemented.