A signal agile replacement method for IP system boundaries
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- 中央广播电视总台
- Filing Date
- 2022-11-17
- Publication Date
- 2026-06-23
Smart Images
Figure CN115776437B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of broadcasting and television, and in particular to a method for agile signal replacement at the boundaries of IP systems. Background Technology
[0002] In IP (Internet Protocol) transmission within the broadcasting industry, differences in the source address, destination address, source port number, and destination port number carried in the IP / UDP (User Datagram Protocol) packet header can affect the reception of downstream devices. Rapid recovery of the upstream system's final-level broadcast signal requires NAT (Network Address Translation) to ensure that the emergency signal maintains fixed source address, destination address, source port number, and destination port number even after a handover, guaranteeing correct reception downstream without requiring adjustments to receiving parameters.
[0003] When IP-based audio and video multicast signals are transmitted between systems, if the core switching matrix has NAT functionality, it acts as the final-level signal processing device in the upstream system to send signals to the downstream system. If the core switching matrix does not have NAT functionality, an audio and video processing device can be configured as the signal processing boundary of the IP system, and the multicast stream can be pulled based on the terminal switching to IGMP (Internet Group Management Protocol) to complete the NAT operation.
[0004] However, current solutions for core switching matrices lacking NAT functionality only handle abnormal signals via terminal switching, assuming the signal switching equipment for the final-level signal, the switch ports and fiber optic cables transmitting the signal to it are all functioning normally at the signal layer, ensuring the normal output of the final-level signal. This approach cannot guarantee effective handling of the following abnormal broadcast signal conditions:
[0005] 1. A failure in the final-level signal switching equipment results in an abnormal final-level IP multicast signal, at which point the system is in single-channel signal broadcast mode. The final-level gateway device is the last signal processing unit on the broadcast link.
[0006] 2. If a primary and backup dual-link transmission based on SMPTE2022-7 is used, a port or fiber optic cable failure between a core switching matrix and the final-level signal switching device will cause one of the final-level -7 signals to be abnormal. Based on the SMPTE2022-7 protocol and secure broadcast requirements, the system should ensure that both -7 signals are normal. Summary of the Invention
[0007] To address one of the aforementioned technical shortcomings, this application provides a signal agile replacement method for IP system boundaries.
[0008] The method includes:
[0009] When the multicast control system determines that the primary final-level signal processing equipment is abnormal, it will synchronize the configuration of the primary final-level signal processing equipment to the backup final-level signal processing equipment.
[0010] The multicast control system's core IP switching matrix shuts down the interface connecting to the primary final-stage signal processing equipment.
[0011] The multicast control system changes the upstream interface to the interface connecting to the backup final-stage signal processing equipment; the upstream interface is located in the multicast routing table of the core IP switching matrix.
[0012] Optionally, the core IP switching matrix establishes audio and video service communication connections with the primary final-stage signal processing equipment and the backup final-stage signal processing equipment, respectively.
[0013] Optionally, the multicast control system establishes control communication connections with the primary final-stage signal processing equipment, the backup final-stage signal processing equipment, and the IP switching matrix, respectively.
[0014] Optionally, both the primary and backup final-stage signal processing devices have multi-channel audio and video signal processing capabilities and are accurately located through internal IDs; they also report to the multicast control system via a Restful API, thereby controlling the corresponding channels.
[0015] Optionally, both the primary final-stage signal processing equipment and the backup final-stage signal processing equipment are based on the IGMPv3 protocol, and the final-stage signal is switched by joining different multicast groups;
[0016] Both the primary and backup final-stage signal processing equipment support MAB mode.
[0017] Both the primary and backup final-stage signal processing devices have at least two independently configured WAN channels with IP addresses. One channel ensures that the corresponding connected switch port address is matched to achieve Layer 3 routing switching, while the other channel ensures that the backup signal is distributed under the same physical port using the multicast source address of the backed-up signal. Both the primary and backup final-stage signal processing devices encapsulate the switched signal into IP addresses based on the SMPTE ST.2110 standard. Each audio / video processing channel is independently configured with a multicast destination address and port number, and the WAN channel matching the multicast source address of the backed-up signal is selected as the source address.
[0018] Optionally, at least one backup final-stage signal processing device may be provided.
[0019] Optionally, when the multicast control system determines that the primary final-level signal processing equipment is malfunctioning, it synchronizes the configuration of the primary final-level signal processing equipment to the backup final-level signal processing equipment, including:
[0020] When the multicast control system determines that the primary final-level signal processing device is abnormal, it selects a target backup final-level signal processing device from all backup final-level signal processing devices.
[0021] The multicast control system will synchronize the configuration of the primary final-stage signal processing equipment to the target backup final-stage signal processing equipment;
[0022] The multicast control system changes the upstream interface to connect to the backup final-stage signal processing equipment, including:
[0023] The multicast control system changes the upstream interface to the interface that connects to the target backup final-stage signal processing equipment.
[0024] Optionally, both the primary final-stage signal processing equipment and the backup final-stage signal processing equipment are configured with a Layer 3 interconnect address that interconnects with the core IP switching matrix.
[0025] Optionally, both the primary final-stage signal processing device and the backup final-stage signal processing device provide API interfaces to external systems.
[0026] When the multicast control system determines that the primary final-level signal processing equipment is malfunctioning, it will synchronize the configuration of the primary final-level signal processing equipment to the backup final-level signal processing equipment, including:
[0027] When the multicast control system determines that the primary final-level signal processing device is abnormal, it copies the signal configuration in the primary final-level signal processing device through the API interface of the primary final-level signal processing device.
[0028] The multicast control system sends signal configurations to the backup final-level signal processing equipment via the API interface of the backup final-level signal processing equipment.
[0029] Optionally, the multicast control system's core IP switching matrix disables the interface connecting to the primary final-stage signal processing equipment, including:
[0030] The multicast control system sends configuration commands to the core IP switching matrix via command line. The configuration commands are used to close the interface connecting to the primary final-level signal processing device.
[0031] The core IP switching matrix receives and executes configuration commands.
[0032] This application provides a method for agile signal replacement at the IP system boundary. The method includes: when a multicast control system determines that the primary final-level signal processing device is malfunctioning, synchronizing the configuration of the primary final-level signal processing device to a backup final-level signal processing device; the multicast control system controlling the core IP switching matrix to close the interface connected to the primary final-level signal processing device; and the multicast control system changing the upstream interface to the interface connected to the backup final-level signal processing device; the upstream interface is located in the multicast routing table of the core IP switching matrix. The method provided in this application, by changing the upstream interface of the core IP switching matrix to the interface connected to the backup final-level signal processing device when the primary final-level signal processing device malfunctions, achieves rapid multicast replacement and improves emergency response efficiency. Attached Figure Description
[0033] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:
[0034] Figure 1 A schematic diagram illustrating the implementation process of a signal agile replacement method for IP system boundaries provided in this application embodiment;
[0035] Figure 2 A schematic diagram illustrating the implementation architecture of a signal agile replacement method for IP system boundaries provided in this application embodiment;
[0036] Figure 3 This application provides a schematic diagram of the configuration of a final-stage signal processing device.
[0037] Figure 4 This application provides a schematic diagram of normal service forwarding traffic as an embodiment of the present application.
[0038] Figure 5 This is a schematic diagram of service forwarding traffic under abnormal conditions provided in an embodiment of this application. Detailed Implementation
[0039] To make the technical solutions and advantages of the embodiments of this application clearer, the exemplary embodiments of this application will be described in further detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not an exhaustive list of all embodiments. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.
[0040] In developing this application, the inventors discovered that current solutions for core switching matrices lacking NAT functionality only handle abnormal signals via terminal switching when the signal switching equipment for the final-level signal, the switch ports and fiber optic cables transmitting the signal with it are all functioning normally, ensuring the normal output of the final-level signal. However, they cannot guarantee effective handling of the following abnormal broadcast signal conditions:
[0041] 1. A failure in the final-level signal switching equipment results in an abnormal final-level IP multicast signal, at which point the system is in single-channel signal broadcast mode. The final-level gateway device is the last signal processing unit on the broadcast link.
[0042] 2. If a primary and backup dual-link transmission based on SMPTE2022-7 is used, a port or fiber optic cable failure between a core switching matrix and the final-level signal switching device will cause one of the final-level -7 signals to be abnormal. Based on the SMPTE2022-7 protocol and secure broadcast requirements, the system should ensure that both -7 signals are normal.
[0043] To address the aforementioned issues, this application provides a method for agile signal replacement at IP system boundaries. This method includes: when the multicast control system determines that the primary final-level signal processing device is malfunctioning, synchronizing the configuration of the primary final-level signal processing device to a backup final-level signal processing device; the multicast control system controlling the core IP switching matrix to close the interface connected to the primary final-level signal processing device; and the multicast control system changing the upstream interface to the interface connected to the backup final-level signal processing device. The upstream interface is located in the multicast routing table of the core IP switching matrix. The method provided in this application, by changing the upstream interface of the core IP switching matrix to the interface connected to the backup final-level signal processing device when the primary final-level signal processing device malfunctions, achieves rapid multicast replacement and improves emergency response efficiency.
[0044] See Figure 1 The signal agile replacement method for IP system boundaries provided in this embodiment is implemented as follows:
[0045] 101. When the multicast control system determines that the primary final-level signal processing equipment is abnormal, it will synchronize the configuration of the primary final-level signal processing equipment to the backup final-level signal processing equipment.
[0046] If both the primary and backup final-level signal processing devices provide API interfaces, then when the multicast control system determines that the primary final-level signal processing device is malfunctioning, it copies the signal configuration from the primary final-level signal processing device through its API interface. The multicast control system then distributes the signal configuration to the backup final-level signal processing device through its API interface.
[0047] In practical implementation, a failure of the primary signal processing equipment will directly affect the signal reception of downstream systems, posing a significant security risk to broadcast safety. An N+1 backup approach can be adopted to enhance security and high availability, ensuring broadcast safety. This means there is at least one backup primary signal processing device. When the multicast control system determines that the primary primary signal processing device is malfunctioning, it selects a target backup primary signal processing device from all backup devices. The multicast control system then synchronizes the configuration of the primary primary signal processing device to the target backup device.
[0048] There are many methods for determining the target backup final stage signal processing device, such as randomly selecting one or selecting one according to a preset standard. This embodiment does not limit the scheme for determining the target backup final stage signal processing device.
[0049] 102. The interface connecting the IP switching matrix of the multicast control system control core to the primary final-stage signal processing device is closed.
[0050] This step can be implemented via command line. The multicast control system sends a configuration command to the core IP switching matrix via command line. The configuration command is used to close the interface connecting the primary final-level signal processing device. The core IP switching matrix receives and executes the configuration command.
[0051] 103. The multicast control system changes the upstream interface to the interface for connecting to the backup final-stage signal processing equipment.
[0052] The upstream interface is located in the multicast routing table of the core IP switching matrix.
[0053] Multicast routing table: Deploying multicast routing protocols on multicast routers, its main function is to determine the upstream and downstream interfaces for establishing and maintaining multicast routing table entries. It includes (S, G) entries, the upstream interface, and the downstream list interfaces. Here, S is the multicast source address, and G is the multicast group address.
[0054] If there is at least one backup final-stage signal processing device, the multicast control system will change the upstream interface to the interface connected to the target backup final-stage signal processing device.
[0055] The signal agile replacement method for IP system boundaries provided in this embodiment is implemented by an architecture consisting of a core IP switching matrix, a primary final-level signal processing device, a backup final-level signal processing device, and a multicast control system.
[0056] In this architecture, the core IP switching matrix establishes audio and video service communication connections with both the primary and backup final-level signal processing devices. The multicast control system establishes control communication connections with the primary, backup, and IP switching devices, respectively.
[0057] In implementation, the core IP switching matrix in this structure is also connected to other receiving devices such as video servers and video splitters (used to receive multicast traffic from end-level devices), such as... Figure 2 As shown ( Figure 2 This example uses only one backup final-stage signal processing device; in actual implementation, there can be multiple backup final-stage signal processing devices.
[0058] The switch housing the core IP switching matrix serves as the core switching device, transmitting signals with the video server and the final-level signal processing device (unless otherwise specified, in this embodiment, the primary final-level signal processing device and all backup final-level signal processing devices are collectively referred to as final-level signal processing devices).
[0059] 1. Core IP Switching Matrix
[0060] The core IP switching matrix receives multicast packets from server group devices and the master controller based on the ACL (Access Control List) policy defined by the control terminal (matching multicast source / destination addresses and port numbers). It can also protect bandwidth based on committed information rates and committed burst rates, and finally achieve non-blocking forwarding based on terminal requests.
[0061] 2. Final stage signal processing equipment
[0062] The final-stage signal processing equipment has three main functions. First, it receives multicast streams from upstream video server groups, such as video servers and pad players, on demand. Second, it ensures that the picture is clean and the audio is free of noise during the quiet switching process of the multicast streams from the video playback devices that serve as signal sources. Finally, it processes the selected multicast streams and sends them to the lower-level video receiver as video sources. The processing includes, but is not limited to, address conversion and generating low-bitrate video.
[0063] 1) The final-stage signal processing equipment is based on the IGMPv3 protocol and achieves final-stage signal switching by joining different multicast groups. It also supports the MAB (Make After Break) method to ensure clean video and noise-free audio during audio / video switching. Furthermore, the switched signal can be encapsulated in IP format according to the SMPTE ST.2110 standard, enabling downstream receiving units to achieve rapid signal recovery without adjusting receiving parameters.
[0064] 2) The final stage signal processing equipment itself may have multi-channel audio and video signal processing capabilities. It can accurately locate the internal processing channel by internal ID (i.e., the internal processing channel can be accurately located according to the internal ID) and report it to the multicast control system through the Restful API, thereby controlling the corresponding channel.
[0065] 3) Both the primary and backup final-level signal processing devices are configured with Layer 3 interconnect addresses that connect to the core IP switching matrix. Simultaneously, a route for the primary final-level gateway device's interconnect address segment is configured on the core IP switching matrix, with the next hop pointing to the backup final-level gateway device. Both the primary and backup final-level signal processing devices receive multicast streams from the video server, but only the primary final-level signal processing device provides multicast services to lower-level devices.
[0066] Unlike baseband systems, the source address, destination address, source port number, and destination port number carried in the IP / UDP packet header of IP-encapsulated signals can all affect the reception of downstream devices. Furthermore, because the system uses the PIM-SSM multicast service model and a Layer 3 routing and switching mode, the terminal's WAN address needs to match both the corresponding switch port address and the multicast source address of the backed-up signal. Figure 3 As shown.
[0067] 4) The final-stage signal processing equipment has one pair of 100GE network interfaces for connecting to the IP matrix equipment (i.e., both the primary and backup final-stage signal processing equipment have one pair of 100GE network interfaces, which are used to establish communication connections with the core IP switching matrix). It supports the transmission and reception of signals conforming to the ST.2022-7 standard. Both the primary and backup final-stage signal processing equipment have at least two independently configurable WAN channels. One is used to ensure matching the corresponding connected switch port address for Layer 3 routing switching, and the other is used to ensure that the backup signal is distributed under the same physical port using the multicast source address of the backed-up signal. Both the primary and backup final-stage signal processing equipment encapsulate the switched signals using the SMPTE ST.2110 standard. Each audio / video processing channel can be independently configured with a multicast destination address and port number, and can select the WAN channel matching the multicast source address of the backed-up signal as the source address. For example, by pre-configuring four different WAN channels, while ensuring that Layer 3 routing switching is achieved by matching the corresponding switch port addresses, it also ensures that the backup signal is distributed under the same physical port using the multicast source address of the backup signal.
[0068] 5) The last-level gateway device itself has the ability to provide API interfaces to the outside world. By using the HTTP protocol to access its provided API interfaces, the last-level gateway device can be controlled.
[0069] 3. Multicast Control System
[0070] The multicast control system is used to control the final-level gateway devices and IP matrix devices.
[0071] The agile signal replacement method for IP system boundaries provided in this embodiment can be used for emergency handling when the final-level signal processing equipment fails or when the final-level IP multicast signal is abnormal, or for emergency handling when a port, board, or fiber optic cable failure between the core switch and the final-level signal processing equipment causes an abnormal -7 signal. Two links are formed by a primary final-level signal processing device and a backup final-level signal processing device. The status and configuration information of the on-premises final-level gateway are obtained through two methods: manual acquisition and automatic acquisition via the upstream comparison system sending interface information, and stored in the multicast control system database. When one link experiences a failure as described above, the configuration information of the fault-switching gateway device is sent to the backup device via an API interface. Simultaneously, the switch port of the faulty device is closed, the switch port corresponding to the backup gateway is opened, and the backup device outputs the final-level signal stream, thereby achieving the function of emergency replacement at the signal level.
[0072] The following section uses a multicast scenario as an example to further explain the implementation process of the signal agile replacement method for IP system boundaries provided in this embodiment.
[0073] Multicast is a one-to-many communication mode between hosts. It's a technology that allows one or more multicast sources to send the same message to multiple receivers. A multicast source sends a message to a specific multicast address. Unlike unicast addresses, multicast addresses don't belong to a specific host but to a group of hosts. A multicast address represents a group, and receivers that need to receive multicast messages join this group.
[0074] A multicast message uses a single multicast address as its destination address. The source sends one and only one copy of the message to that multicast address. The multicast protocol deployed in the network establishes a tree-like route for this multicast message, with the source at the root and all multicast group members as leaves. Multicast technology effectively solves the problem of single-point sending and multi-point receiving, enabling efficient point-to-multipoint data transmission in IP networks.
[0075] Multicast Group: A multicast group is identified by an IP multicast address. Any user host (or other receiving device) that joins a multicast group becomes a member of that group and can recognize and receive IP packets destined for that IP multicast address.
[0076] Multicast source: A source of information that sends IP packets to a multicast group address as the destination address. A single multicast source can send data to multiple multicast groups simultaneously; multiple multicast sources can send data to a single multicast group simultaneously.
[0077] Multicast routing table: Deploying multicast routing protocols on multicast routers, its main function is to determine the upstream and downstream interfaces for establishing multicast routing table entries and to maintain these entries. The multicast routing table is shown below:
[0078] MulticastroutingtableofVPN-Instance: publicnet
[0079] Total 1 entry
[0080] 00001.(192.168.0.2, 227.0.0.1)
[0081] Uptime: 00:00:28
[0082] UpstreamInterface: GigabitEthernet2 / 0 / 0
[0083] List of 2 downstream interfaces
[0084] 1: GigabitEthernet3 / 0 / 0
[0085] 2: GigabitEthernet1 / 0 / 0
[0086] Among them, the main areas of focus are (192.168.0.2, 227.0.0.1), upstream interface, and downstream interface.
[0087] (192.168.0.2, 227.0.0.1): The (S, G) entry in the multicast routing table. S is the multicast source address, and G is the multicast group address.
[0088] upstreaminterface: The upstream interface of the (S, G) table entry or multicast VPN Extranet entry.
[0089] downstreaminterface: A list of downstream interfaces for (S, G) entries or multicast VPN Extranet entries.
[0090] Both the primary and backup final-level signal processing devices are connected to the core IP switching matrix. Each device is configured with a Layer 3 interconnect address that connects to the core IP switching matrix. Simultaneously, the core IP switching matrix is configured with a route for the primary final-level gateway device's interconnect address segment, with the next hop pointing to the backup final-level gateway device. Both devices receive multicast streams from the video server, but only the primary final-level signal processing device provides multicast services to lower-level devices. For example, as shown below:
[0091] <huawei>dismulticastrouting-table
[0092] MulticastroutingtableofVPN-Instance: publicnet
[0093] Total 3 entries
[0094] 00001.(12.12.12.2,224.1.1.1)
[0095] Uptime: 00:01:39
[0096] UpstreamInterface: GigabitEthernet0 / 0 / 0
[0097] List of 1 downstream interfaces
[0098] 1: GigabitEthernet0 / 0 / 2
[0099] [huawei]disiprou 12.12.12.2
[0100] Route Flags: R-relay, D-download to fib
[0101] Routing Table: Public
[0102] SummaryCount: 1
[0103] Destination / Mask Proto Pre Cost Flags NextHop Interface
[0104] 12.12.12.0 / 30 Direct 0 0D 12.12.12.1 GigabitEthernet 0 / 0 / 0
[0105] Under normal circumstances, the interface (e.g., port) connecting to the primary final-level signal processing device is functioning correctly. On the core IP switching matrix, by querying the multicast routing table record (S, G) for S, where S is the address of the primary final-level signal processing device, and the multicast routing table shows that address S is forwarded from the primary final-level gateway device, the multicast stream will be pulled from the port of the primary final-level gateway device. The service forwarding traffic diagram is as follows: Figure 4 As shown in the figure, the dashed line represents the direction of multicast stream flow.
[0106] When the primary final-level signal processing device fails, the signal agile replacement method for IP system boundaries provided in this embodiment synchronizes the configuration of the primary final-level signal processing device to the backup final-level gateway device and closes the port to achieve traffic switching. The service forwarding traffic diagram is as follows: Figure 5 As shown in the figure, the dashed line represents the direction of multicast stream flow.
[0107] The solution is as follows:
[0108] In step 101, the multicast control system synchronizes the configuration of the primary final-stage signal processing equipment to the backup final-stage signal processing equipment.
[0109] That is, the multicast control system backs up the configuration of the primary final-level signal processing device through the API interface of the primary final-level signal processing device, and sends the configuration to the backup final-level signal processing device.
[0110] In the event of a failure in the primary final-level signal processing equipment, multicast traffic will be abnormal. An emergency switchover is required. This involves backing up the configuration of the primary final-level signal processing equipment and then distributing the backup configuration to the standby final-level signal processing equipment. After this operation is completed, the standby final-level signal processing equipment can send multicast service streams normally.
[0111] In addition, the last-level gateway device itself has the ability to provide an API interface. By using the HTTP protocol to access its provided API interface, the last-level gateway device can be controlled.
[0112] In step 102, the multicast control system controls the core IP switching matrix to close the interface connecting to the primary final-stage signal processing device.
[0113] After executing step 101, since the S address of the (S, G) entry recorded in the multicast routing table of the core IP switching matrix still points to the interface (such as port) connecting the primary final-level signal processing device, the service has not yet been switched to the backup final-level signal processing device for forwarding. It is still necessary to close the interface through step 102 and perform the routing switch operation through step 103.
[0114] In step 102, the ports connecting to the primary last-level gateway devices in the core IP switching matrix will be closed. For example, network devices can be managed via CLI (Command Line Interface). Users only need to issue relevant configurations through the graphical interface, and the multicast control system can analyze the content and convert it into corresponding configuration commands for issuance.
[0115] In step 103, the multicast control system changes the upstream interface to the interface that connects to the backup final-stage signal processing equipment.
[0116] After executing step 102, the port connected to the primary last-level gateway device on the IP switching matrix of the multicast control system control core is closed, and the original direct-connected routes in the multicast routing table become invalid. At this time, step 103 is needed to change the configured backup route entry to the optimal one.
[0117] That is, by querying the S address of the (S, G) record in the multicast routing table, the route is switched to the interface query of the backup final-level signal processing device. Then, the core IP switching matrix will select the multicast stream received by the backup final-level signal processing device port for forwarding.
[0118] At this point, the multicast routing table lookup is as follows:
[0119] <huawei>dismulticastrouting-table
[0120] MulticastroutingtableofVPN-Instance: publicnet
[0121] Total 3 entries
[0122] 00001.(12.12.12.2,224.1.1.1)
[0123] Uptime: 00:01:39
[0124] UpstreamInterface: GigabitEthernet0 / 0 / 1
[0125] List of 1 downstream interfaces
[0126] 1: GigabitEthernet0 / 0 / 2
[0127] [huawei]disiprou 12.12.12.2
[0128] Route Flags: R-relay, D-download to fib
[0129] Routing Table: Public
[0130] SummaryCount: 1
[0131] Destination / Mask Proto Pre Cost Flags NextHop Interface
[0132] 12.12.12.0 / 30 Static60 0RD 13.13.13.2 GigabitEthernet 0 / 0 / 1
[0133] After shutting down the interface, the S address in the multicast routing table (S, G) record is looked up according to the routing table. The address is changed from the original G0 / 0 / 0 interface to point to the G0 / 0 / 1 interface, thus completing the emergency switchover of the last-level device.
[0134] In practical implementation, steps 101, 102, and 103 can be implemented by configuring the internal ID of the primary and secondary gateway devices to determine the processing channel of the received signals within these devices. The latest data stream information of the configured signal sources can be periodically retrieved from the API interface provided by the primary and secondary gateway devices using the HTTP protocol, and categorized and viewed according to the signal numbers. Simultaneously, the configuration information of the primary and secondary gateway devices can be obtained through these numbers, allowing for editing and saving of the configuration information to a database.
[0135] When the primary final-level signal processing device fails, the multicast control system copies the signal configuration stored on the primary final-level signal processing device and sends it to the backup final-level signal processing device via HTTP protocol through the API provided by the backup final-level signal processing device. This ensures that the backup final-level signal processing device has all the signal configurations and information of the failed primary device. Simultaneously, the system uses CLI configuration commands to shut down the interface of the switching device connected to the failed primary final-level signal processing device and uses CLI configuration commands to open the interface of the switching device connected to the backup final-level signal processing device. This transfers the network connection between the failed primary final-level signal processing device and the switching device (the device housing the core IP switching matrix) to the backup final-level signal processing device. Ultimately, all services and network traffic from the failed primary final-level signal processing device are transferred to the emergency backup final-level signal processing device, enabling an emergency replacement of the IP primary / backup flow.
[0136] Once the primary final-level signal processing equipment recovers from a failure, the saved configuration is distributed, and the network ports of the switching equipment and the emergency backup final-level signal processing equipment are closed. The ports of the primary final-level gateway equipment are then opened, completing the restoration of services and network for the primary final-level signal processing equipment. The backup final-level signal processing equipment is then restored to its original configuration to complete the recovery.
[0137] Furthermore, this can be achieved through the following interface commands.
[0138] 1. Access the API interfaces related to the final stage signal processing device using the HTTP protocol's POST or GET methods.
[0139]
[0140]
[0141] 2. Exchange device-related commands and send them to the device using CLI.
[0142]
[0143] This embodiment provides a method for agile signal replacement at IP system boundaries. When the multicast control system determines that the primary final-level signal processing device is malfunctioning, it synchronizes the configuration of the primary final-level signal processing device to the backup final-level signal processing device. The multicast control system controls the core IP switching matrix to close the interface connected to the primary final-level signal processing device. The multicast control system then changes the upstream interface to the interface connected to the backup final-level signal processing device. The upstream interface is located in the multicast routing table of the core IP switching matrix. This method, when the primary final-level signal processing device malfunctions, achieves rapid multicast replacement by changing the upstream interface of the core IP switching matrix to the interface connected to the backup final-level signal processing device, thus improving emergency response efficiency.
[0144] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely software embodiment or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The solutions in the embodiments of this application can be implemented in various computer languages, such as the object-oriented programming language Java and the interpreted scripting language JavaScript.
[0145] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0146] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0147] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0148] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.
[0149] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.< / huawei> < / huawei>
Claims
1. A signal agile replacement method for IP system boundaries, characterized in that, The method includes: When the multicast control system determines that the primary final-level signal processing device is abnormal, it will configure and synchronize the primary final-level signal processing device to the backup final-level signal processing device. The multicast control system controls the core IP switching matrix to shut down the interface connected to the primary final-stage signal processing device. The multicast control system changes the upstream interface to the interface connecting the backup final-stage signal processing device; the upstream interface is located in the multicast routing table of the core IP switching matrix; The core IP switching matrix establishes audio and video service communication connections with the primary final-stage signal processing device and the backup final-stage signal processing device, respectively. The multicast control system establishes control communication connections with the primary final-stage signal processing device, the backup final-stage signal processing device, and the IP switching matrix, respectively.
2. The method according to claim 1, characterized in that, Both the primary final-stage signal processing device and the backup final-stage signal processing device have multi-channel audio and video signal processing capabilities and are accurately located through internal IDs; they also report to the multicast control system through a Restful API, thereby controlling the corresponding channels.
3. The method according to claim 1, characterized in that, Both the primary final-stage signal processing device and the backup final-stage signal processing device are based on the IGMPv3 protocol and switch final-stage signals by joining different multicast groups. Both the primary final-stage signal processing device and the backup final-stage signal processing device support MAB mode. Both the primary final-stage signal processing device and the backup final-stage signal processing device have at least two independently configured WAN channels. One WAN channel is used to ensure that the corresponding connected switch port address is matched to achieve Layer 3 routing switching. The other WAN channel is used to ensure that the backup final-stage signal is distributed under the same physical port using the multicast source address of the backup final-stage signal. Both the primary final-stage signal processing device and the backup final-stage signal processing device encapsulate the switched signal into IP based on the SMPTE ST.2110 standard. Each audio / video processing channel is independently configured with a multicast destination address and port number, and selects the WAN channel that matches the multicast source address of the backup final-stage signal as the source address.
4. The method according to claim 1, characterized in that, The backup final-stage signal processing device is at least one.
5. The method according to claim 4, characterized in that, When the multicast control system determines that the primary final-level signal processing device is malfunctioning, it synchronizes the configuration of the primary final-level signal processing device to the backup final-level signal processing device, including: When the multicast control system determines that the primary final-level signal processing device is abnormal, it determines a target backup final-level signal processing device from all backup final-level signal processing devices. The multicast control system will configure and synchronize the primary final-stage signal processing device to the target backup final-stage signal processing device. The multicast control system changes the upstream interface to the interface connecting the backup final-stage signal processing device, including: The multicast control system changes the upstream interface to the interface connecting to the target backup final-stage signal processing device.
6. The method according to claim 1, characterized in that, Both the primary final-stage signal processing device and the backup final-stage signal processing device are configured with a Layer 3 interconnect address that interconnects with the core IP switching matrix.
7. The method according to claim 1, characterized in that, Both the primary final-stage signal processing device and the backup final-stage signal processing device provide API interfaces to external devices. When the multicast control system determines that the primary final-level signal processing device is malfunctioning, it synchronizes the configuration of the primary final-level signal processing device to the backup final-level signal processing device, including: When the multicast control system determines that the primary final-level signal processing device is abnormal, it copies the signal configuration in the primary final-level signal processing device through the API interface of the primary final-level signal processing device. The multicast control system sends the signal configuration to the backup final-level signal processing device through the API interface of the backup final-level signal processing device.
8. The method according to claim 1, characterized in that, The multicast control system controls the core IP switching matrix to close the interface connected to the primary final-stage signal processing device, including: The multicast control system sends a configuration command to the core IP switching matrix via a command line. The configuration command is used to close the interface connected to the primary final-stage signal processing device. The core IP switching matrix receives and executes the configuration command.