Moip control device and program

Abstract

The present invention enables control that utilizes the advantages of multicasting in an IP system for MoIP that transmits a media signal by using multicast on an IP network. The present invention is such that a virtual receiver performs the act of receiving reception control, and, on the basis of the received information, acts as a virtual sender and / or performs reception control with respect to another receiver. The sender information of a sender that is not SMPTE ST2022-7 compliant is altered to make the sender appear to be an SMPTE ST2022-7 compliant sender.

Description

MoIP control device and program

[0001] The present invention relates to a control device and a program in an MoIP (Media Over IP) environment that uses multicasting over an IP network.

[0002] The technology for transmitting media content (e.g., video, audio, auxiliary data; hereinafter referred to as media signals) using an IP network is called MoIP, and in relation to this, the SMPTE specifies in the SMPTE ST2022-10 standard (see Non-Patent Document 1), the SMPTE ST2110-6 standard (see Non-Patent Document 2), and their related standards that media signals be transmitted in RTP packets using unicast or multicast. When multicast is used, a sender sends a packet to a multicast address, which can be received by multiple receivers via a network switch.

[0003] Sender and receiver devices are called nodes, and AMWA NMOS IS-04 (see Non-Patent Document 4) has been published as a standard for discovering and registering nodes and obtaining node information on a network. AMWA NMOS IS-05 (see Non-Patent Document 5) has also been published as a standard for controlling transmissions to nodes.

[0004] The SMPTE ST2110-10 standard, the SMPTE ST2022-6 standard, and their related standards stipulate that parameters such as the format of a signal to be transmitted be described in the Session Description Protocol (SDP) (see Non-Patent Documents 6, 7, and 8). AMWA NMOS IS-05 provides a means for a receiver to obtain information described in the SDP.

[0005] The SMPTE ST2022-7 standard (see Non-Patent Document 3) specifies measures to deal with packet loss by multiplexing the network path from the sender to the receiver.

[0006] Patent 7401097

[0007] SMPTE ST2110-10SMPTE ST2022-6SMPTE ST2022-7AMWA NMOS IS-04 Discovery and Registration SpecificationAMWA NMOS IS-05 Connection ManagementRFC 4566RFC 5888RFC 7104

[0008] In conventional SDI (Serial Digital Interface), the signal sending and receiving sides are separate, and bidirectional communication is not possible. In broadcasting facilities using SDI, when sending and receiving video signals between multiple facilities, the sending side sends the appropriate signal. When selectively specifying a transmitter from multiple transmitters or switching video signals due to equipment failure or maintenance, the sending side does this, and the receiving side does not need to be aware of it. In addition, the video signal sent by the sending side can be distributed and used as desired on the receiving side, and the sending side does not need to be aware of this. The boundary between facilities is clearly defined by the output and input of the SDI signal.

[0009] MoIP, which transmits media signals using multicast over an IP network, requires receivers to control which senders they receive. In broadcasting equipment using MoIP (hereinafter referred to as IP systems), when media signals are transmitted and received between multiple IP systems, if the transmitting IP system wants to switch senders, it must cross-system boundaries to control the receivers in the receiving IP system. However, the transmitting IP system may not know which receivers are receiving which senders in the receiving IP system. Furthermore, each IP system node is registered in its own Registration & Discovery System (RDS) and controlled by its own system controller, making cross-system control difficult. Cross-system control also poses the problem of system independence being compromised.

[0010] Therefore, when a sending IP system needs to switch senders, measures such as interfacing with SDI, IP retransmission, multicast NAT (Network Address Translation), and information sharing among multiple RDSs are taken.

[0011] The SDI interfacing method converts the IP packets of the media signal into SDI in the sending IP system, and then converts the SDI back into IP packets in the receiving IP system. This method allows for operation in the same way as before, but it has significant disadvantages, such as not being able to take advantage of the advantages of IP networks and multicast, and increasing costs, delays, and points of failure.

[0012] The IP retransmission is a method of receiving IP packets of a media signal in one system and retransmitting them to another system as a media signal with a different fixed multicast address. Since the receiving side of the other system only needs to receive a fixed multicast address at all times, it can be operated in the same way as SDI described above. However, it has problems such as an increased load on the IP network, not being able to take advantage of the advantages of multicast, increased costs, and being unable to respond to breakdowns in the IP retransmission device itself.

[0013] The multicast NAT is a method that uses the network switch function to convert and fix the multicast address of media signals sent from one system to another. With this method, the receiving side only needs to always receive a fixed multicast address, so it is possible to take advantage of the benefits of multicast and operate in a similar manner to the SDI mentioned above. However, because the control method differs depending on the network switch product, it is necessary to control it individually depending on the network switch product used. In addition, there is a high possibility that shocks will occur in the video and audio when switching, which in the case of broadcasting stations, could cause damage to the broadcast.

[0014] The method for sharing information among multiple RDSs involves installing an RDS shared server that obtains sender information from the RDS of the sending IP system and registers that information in the RDS of the receiving IP system. This allows the sender of the sending IP system to appear as the sender of its own system on the receiving IP system, enabling it to receive media signals from senders of other systems. This method takes advantage of multicast and enables so-called resource sharing. However, in the event of an emergency switchover, such as when a sender in the sending IP system fails, even if the RDS information in the sending IP system is updated, the RDS shared server cannot immediately detect the information update in the RDS of the sending IP system. Furthermore, there is no guarantee that the controller of the receiving IP system will detect the information update in its own RDS and immediately switch the receiver's destination. Therefore, this method is not suitable for emergency switchover.

[0015] Furthermore, when multicast packets of a media signal transmitted from a sender that does not support SMPTE ST2022-7 are received by a receiver that supports SMPTE ST2022-7, even if the network paths along the way are multiplexed, the packets only pass through one of the networks, and the advantages of multicast are not fully utilized.

[0016] The present invention has been made in consideration of the above-mentioned problems, and while taking advantage of the advantages of multicast, clarifies the boundary of the interface between IP systems, allowing a sending IP system to switch senders at any timing, similar to the operation of SDI. A receiving IP system can arbitrarily distribute media signals received from the sending IP system, increasing or decreasing the number of receivers.

[0017] In addition, when a multicast packet transmitted from a sender that does not support SMPTE ST2022-7 is received by an SMPTE ST2022-7 compliant receiver, the packet can pass through each of the multiplexed network paths along the way.

[0018] In order to solve the above problem, one embodiment of the present invention is characterized in that, in a MoIP environment in which media signals are transmitted by multicast, the device has a memory unit and a receiving side control interface function that receives reception control based on information including a multicast address, a port number, and a source address, and stores the information in the memory unit, and has a first function that is a sending side control interface function that publishes the information held by the memory unit, and a second function that is a control controller function that has control destination information and controls reception so that a receiver set in the control destination information receives based on the information held by the memory unit, or has both the first function and the second function.

[0019] One embodiment of the present invention is characterized by having a plurality of functional assemblies in any combination of the following: a set of functional assemblies having the function of the receiving control interface, the first function, and the second function; a set of functional assemblies having the function of the receiving control interface and the first function; and a set of functional assemblies having the function of the receiving control interface and the second function.

[0020] One embodiment of the present invention is characterized in that the functions of two or more receiving control interfaces are linked, and when the function of one of the receiving control interfaces receives control based on the information, it compares the information in its own memory unit with the information in the other memory unit, and if the information is identical, it adds itself to the control destination information of the other interface, and if the information is not identical, it deletes itself from the control destination information of the other interface.

[0021] One embodiment of the present invention is characterized by having a function of modifying the information held in the storage unit so as to perform multiplexing of the SMPTE ST2022-7.

[0022] One embodiment of the present invention is characterized by having a virtual receiver that behaves as a receiver in terms of control in a MoIP environment in which media signals are transmitted by multicast, has a memory unit that stores parameters subject to reception control, and behaves as if it is receiving.

[0023] A general-purpose computer may be configured to have the above functions.

[0024] In the following, the function of the receiving side control interface will be referred to as a "virtual receiver," the first function as a "virtual sender," and the second function as a "control controller," and a set of functions comprising a virtual receiver and one or both of a virtual sender and a control controller will be referred to as a "virtual node."

[0025] According to the present invention, in MoIP, which transmits media signals using multicast over an IP network, it is possible to clearly define the boundaries of interfaces between IP systems while taking advantage of the benefits of multicast. That is, a sending IP system can switch senders at any time, and a receiving IP system can receive multicast packets sent from the sending IP system at any receiver. A single device can establish interfaces with multiple other systems, which also offers significant cost benefits.

[0026] Furthermore, by taking advantage of multicast, senders that do not support SMPTE ST2022-7 can be treated as if they were SMPTE ST2022-7 compatible senders, making it possible to configure an IP system while taking costs into consideration.

[0027] FIG. 1 is a block diagram showing the functional configuration of a virtual node according to an embodiment of the present invention. FIG. 1 is a configuration diagram of an example in which a virtual node according to an embodiment of the present invention is used as a virtual receiver and control controller. FIG. 1 is a configuration diagram of an example in which a virtual node according to an embodiment of the present invention is used as a virtual receiver and virtual sender. FIG. 2 is an example of a block diagram showing the functional configuration in which two or more virtual nodes according to an embodiment of the present invention are combined and control destination information is dynamically updated. FIG. 2 is a first diagram of an example of cooperation between two IP systems to which a virtual node according to an embodiment of the present invention is applied. FIG. 3 is a second diagram of an example of cooperation between two IP systems to which a virtual node according to an embodiment of the present invention is applied. FIG. 4 is a fourth diagram of an example of cooperation between two IP systems to which a virtual node according to an embodiment of the present invention is applied. FIG. 2 is a diagram of an example of cooperation between two IP systems to which a virtual node according to an embodiment of the present invention is applied. FIG. 3 is a diagram of an example of cooperation between two IP systems to which a virtual node according to an embodiment of the present invention is applied. 1 is an example diagram of a multicast packet passing from a non-SMPTE ST2110-7 compliant sender to an SMPTE ST2110-7 compliant receiver via both multiplexed networks in accordance with an embodiment of the present invention.

[0028] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that the same elements are given the same reference numerals, and duplicate explanations will be omitted. Furthermore, the following embodiments are merely examples for explaining the present invention, and are not intended to limit the present invention to only these embodiments. Furthermore, the present invention can be modified in various ways without departing from the gist of the invention.

[0029] 1 is a block diagram showing the functional configuration of a virtual node 1 to which an embodiment of the present invention can be applied. The virtual node 1 includes functional blocks of a virtual receiver 10, a virtual sender 20, and a controller 30.

[0030] The virtual receiver 10 includes a receiving control interface 11 that receives reception control and a storage unit 12 that stores the received reception control information. The virtual sender 20 includes a transmitting control interface 21. The receiving control interface 11 and the transmitting control interface 21 may be configured, for example, using AMWA NMOS IS-04 and IS-05 interfaces. The controller 30 includes a control interface 31 and control destination information 32. The control interface 31 may be configured, for example, using an AMWA NMOS IS-05 interface. The device according to the embodiment of the present invention may be configured as a dedicated device, or a general-purpose computer may be configured to have the functions of the device according to the embodiment of the present invention.

[0031] The receiver control interface 11 behaves as a normal receiver in terms of control. In other words, when configured with AMWA NMOS IS-04 and IS-05, it has a unique ID as a node and can optionally be discovered by DNS-SD (DNS-Based Service Discovery) or registered in RDS. When it receives reception control as a receiver, it stores that information in the memory unit 12 and behaves as if it has started receiving.

[0032] The information stored in the storage unit 12 includes a multicast address, a port number, and a source address, and may further include an SDP (hereinafter, this information will be referred to as sender information).

[0033] The sending control interface 21 behaves as a normal sender in terms of control. In other words, when configured with AMWA NMOS IS-04 and IS-05, it has a unique ID as a node and can be discovered by DNS-SD or registered in RDS. It then behaves as if it is transmitting multicast based on the information stored in the memory unit 12. However, while a normal sender can change the destination multicast address and receive control to stop or start transmission, if it receives such control, it returns an error or ignores the request.

[0034] When the information in the storage unit 12 changes, the control interface 31 quickly performs reception control on the receivers set in the control destination information 32 described below. A retry may be performed for receivers that could not be controlled at this time. When information in the control destination information 32 is added or changed, reception control may be performed on the added or changed receiver based on the information in the storage unit 12.

[0035] The control destination information 32 is assumed to be preset with information about the receiver that will perform reception control. That is, if the control controller 30 is configured with an AMWA NMOS IS-05, the information includes the receiver ID, the address of the NMOS API (Application Programming Interface), and port information. There may be zero or multiple pieces of control destination information. If there is zero control destination information, no control is performed.

[0036] The operation flow of one embodiment of the present invention will be specifically described with reference to the drawings. Figure 2 shows an example in which a virtual node 1 is used as a virtual receiver and controller.

[0037] In this example, the system is configured to include a control network 50 that controls the transmission and reception of media signals, a media network 51 that transmits and receives media signals by multicast, a control controller 60 that controls reception of receivers, a sender 70 that transmits media signals, a receiver 80 that receives media signals, and a virtual node 1. The control network 50 is connected to the control controller 60, the sender 70, the receiver 80, and the virtual node 1, while the media network 51 is connected to the sender 70 and the receiver 80.

[0038] The control network 50, media network 51, controller 60, sender 70, and receiver 80 are devices configured using existing technology. The control network 50 and media network 51 may be configured as a single network. There may be multiple senders 70 and receivers 80.

[0039] It is assumed that a media signal is being transmitted by multicast from the sender 70, but there is no receiver to receive it yet.

[0040] The control flow will be explained in alphabetical order in parentheses in the figure. In this example, the controller 60 acquires sender information from the sender 70 (A) and performs reception control for the virtual node 1 based on the sender information (B). As a result, the sender information for the sender 70 is registered in the storage unit 12. The receiver 80 is registered in advance in the control destination information 32 of the virtual node 1, and the virtual node 1 that has received reception control performs reception control for the receiver 80 based on the sender information in the storage unit 12 (C). The receiver 80 begins multicast reception of the media signal from the sender 70 (D).

[0041] As a result, the receiver 80 can receive a media signal from the sender 70 without being directly controlled by the controller 60 .

[0042] By applying the above, it is possible to quickly control reception of a sender selected arbitrarily from a plurality of senders in one IP system to a receiver in another IP system.

[0043] FIG. 3 shows an example in which virtual node 1 is used as both a virtual receiver and a virtual sender.

[0044] In this example, the system is configured with a control network 50 that controls the transmission and reception of media signals, a media network 51 that transmits and receives media signals by multicast, a control controller 60, another control controller 61, a sender 70 that transmits media signals, a receiver 80 that receives media signals, and a virtual node 1. The control network 50 is connected to the control controller 60, the control controller 61, the sender 70, the receiver 80, and the virtual node 1, while the media network 51 is connected to the sender 70 and the receiver 80.

[0045] The control network 50, the media network 51, the control controller 60, the control controller 61, the sender 70, and the receiver 80 are devices configured using existing technology. The control network 50 and the media network 51 may be configured as a single network. There may be multiple senders 70 and multiple receivers 80.

[0046] It is assumed that a media signal is being transmitted by multicast from the sender 70, but there is no receiver to receive it yet.

[0047] The flow of control will be explained in alphabetical order in parentheses in the figure. The control controller 61 performs reception control so that the virtual node 1 receives the sender 70 (A). As a result, sender information for the sender 70 is registered in the storage unit 12. Nothing is registered in the control destination information 32, so no particular control is performed. The control controller 60 acquires sender information from the virtual node 1 (B) and performs reception control on the receiver 80 based on the sender information (C). The receiver 80 starts multicast reception of the media signal from the sender 70 (D).

[0048] As a result of the above, the control controller 60 can control the receiver 80 to receive a media signal from the sender 70 without having any direct relationship with the sender 70, and the control controller 61 can control the receiver 80 to receive a media signal from the sender 70 without having any direct relationship with the receiver 80.

[0049] By applying the above, a sender selected from multiple senders in one IP system can be registered in a virtual node in the other IP system, and the other IP system can treat the virtual node as if it were a sender in its own IP system, making so-called resource sharing possible.

[0050] FIG. 4 is an example block diagram showing a functional configuration for combining two or more virtual nodes 1 and dynamically updating control destination information 32 according to an embodiment of the present invention. There may be multiple source virtual nodes 1 and multiple destination virtual nodes 1. Details within each virtual node 1 are omitted, and only the necessary parts are shown. The virtual nodes 1 may be in separate housings or in the same housing. If they are in the same housing, multiple virtual receivers and virtual senders may be configured as a single node. The device according to an embodiment of the present invention may be configured as a dedicated device, or a general-purpose computer may be configured to have the functions of the device according to an embodiment of the present invention.

[0051] When a control signal arrives from outside and the information in its own storage unit 12 changes, the source virtual node 1 compares the information in its own storage unit 12 with the information in the storage unit 12 of the destination virtual node 1. If they match, the source virtual node 1 is added to the control destination information 32 of the destination virtual node 1. However, if the source virtual node 1 already exists in the control destination information 32 of the destination virtual node 1, no action is taken. If they do not match, the source virtual node 1 is deleted from the control destination information 32 of the destination virtual node 1. However, if the source virtual node 1 does not exist in the control destination information 32 of the destination virtual node 1, no action is taken.

[0052] The flow of operation of one embodiment of the present invention will be specifically explained using the figures. Figures 5a, 5b, 5c, and 5d show an example of cooperation between a receiving IP system 100 and a sending IP system 101. Each is connected to a media network and a control network as necessary, but these are omitted from the figures.

[0053] The IP system 100 is an example configured to include a control controller 60, one or more senders 70, one or more receivers 80, and a plurality of virtual nodes 1. The IP system 101 is an example configured to include a control controller 61, a plurality of senders 70, and a virtual node 1.

[0054] The solid arrows in the figure represent the control destination information of each virtual node that has been set in advance. Receiver A80 is registered as the control destination information for virtual node A1. Receiver B80 is registered as the control destination information for virtual node B1. Receiver C80 is registered as the control destination information for virtual node C1. Virtual node X1 is registered as the control destination information for virtual node Y1.

[0055] The dotted arrows in the figure (white arrows) represent the pre-defined relationships between source and destination virtual nodes. Virtual node A1 is the source virtual node, and virtual node X1 is registered as its destination virtual node. Virtual node B1 is the source virtual node, and virtual node X1 is registered as its destination virtual node. Virtual node C1 is the source virtual node, and virtual node X1 is registered as its destination virtual node.

[0056] The flow of Figure 5a will be explained in alphabetical order in parentheses. Controller 61 acquires sender information from sender S70 and controls virtual node Y1 to receive sender S70 (A). Virtual node Y1, which has received this control, controls virtual node X1 to receive (B). As a result, sender information for sender S70 is registered in storage unit 12 of virtual node X1. At this point, there is no registration in control destination information 32 of virtual node X1, so no further control is performed.

[0057] Next, the flow of Figure 5b will be explained in alphabetical order in parentheses. Assume that controller 60 acquires sender information from virtual node X1 (C) and applies reception control to virtual nodes A1 and C1 (D). Virtual nodes A1 and C1, which have received reception control, then apply reception control to receivers A80 and C80, respectively (E). At this point, receivers A80 and C80 begin receiving media signals from sender S70. At the same time, virtual nodes A1 and C1 compare the information they received reception control from with the information in virtual node X1's memory unit 12. Since they match, virtual nodes A1 and C1 are added to virtual node X1's control destination information 32 (F).

[0058] Next, the flow of Figure 5c will be explained in alphabetical order in parentheses. Assume that the IP system 100 switches the media signal being received by receiver C80 to a media signal from sender U70 of its own system. Controller 60 acquires sender information from sender U70 and applies reception control to virtual node C1 based on the sender information (G). Virtual node C1, which has received reception control, then controls receiver C80 (H). At this point, receiver C80 switches to receiving the media signal from sender U70. At the same time, virtual node C1 compares the information it has received reception control with the information in storage unit 12 of virtual node X1. Since they do not match, virtual node C1 is deleted from the control destination information 32 of virtual node X1 (I).

[0059] Next, the flow of FIG. 5d will be explained in alphabetical order in parentheses. Assume that IP system 101 needs to switch the source of the media signal it is sending to IP system 100 from sender S70 to sender T70. Controller 61 acquires sender information from sender T70 and controls virtual node Y1 to receive from sender T70 (J). Virtual node Y1, which has received reception control, controls virtual node X1 (K). This registers sender information for sender T70 in storage unit 12 of virtual node X1. Because virtual node A1 was registered in the control destination information of virtual node X1 in step (I), virtual node X1 controls reception from virtual node A1 (L). Virtual node A1 then controls reception from receiver A80 (M). At this point, receiver A80 switches to receiving media signals from sender T70.

[0060] As a result, when the sender on the IP system 101 side is changed, the IP system 100 receiving the media signal from the IP system 101 can quickly switch the reception mode for each receiver 80 that is currently receiving the media signal from the IP system 101.

[0061] Each virtual node 1 is contained within its own IP system, and the control controller 60 and the control controller 61 do not need to perform control beyond their own system. This is because each virtual node 1 serves as an interface boundary, which clarifies the interface boundary between systems.

[0062] In one embodiment of the present invention, the present invention has a function of modifying sender information that does not support path multiplexing defined in the SMPTE ST2022-7 standard, thereby realizing path multiplexing.

[0063] FIG. 6 shows an example in which, when the sender information includes an SDP, a non-multiplexed SDP 200 is changed to an SDP 201 that supports multiplexing (duplexing in this example).

[0064] The specific processing contents will be explained.

[0065] The non-multiplexed SDP 200 is divided into character string group 1 and character string group 2 from the beginning, using the line beginning with "m=" as a delimiter.

[0066] An empty string variable is prepared. String group 1 is output to the string variable, and then "a=group:DUP identifier1 identifier2" is output, indicating that multiplexing is occurring. Identifier 1 and identifier 2 can be any unique alphanumeric string ("primary" and "secondary" in the example of Figure 6). If further multiplexing is to occur, the number of identifiers can be listed accordingly. String group 2 is output to the string variable, and "a=mid:identifier1" is output, indicating that this is the first media in a duplicated system. String group 2 is again output to the string variable, and "a=mid:identifier2" is output, indicating that this is the second media in a duplicated system.

[0067] The character string variable generated as described above is referred to as the modified SDP 201.

[0068] FIG. 7 shows an example of changing the non-multiplexed parameter 300 to a parameter 301 corresponding to multiplexing (duplication in this example) when the multicast address, port number, and source address included in the sender information are expressed in JSON (JavaScript Object Notation) of the staged API of AMWA NMOS IS-05.

[0069] The specific processing will be explained below. An empty JSON object variable is prepared. The first object in the array of the "transport_params" key value of the non-multiplexing parameters 300 is extracted, a "transport_params" key is generated in the JSON object variable, and two of its values ​​are placed as an array, identical to the object. All other keys and values ​​are copied as is.

[0070] The JSON object variables generated as described above are set as parameters 301 corresponding to the modified multiplexing.

[0071] The sender information modified as described above is recognized as sender information conforming to the SMPTE ST2110-7 standard. As a result, when combined with virtual node 1, it can be treated as a normal sender conforming to the SMPTE ST2110-7 standard. Similar operations may be achieved by incorporating this sender information modification function into a conventional controller.

[0072] As a result, a sender that does not support route multiplexing can be made to operate as if it does support route multiplexing. A receiver that supports the multiplexing of the SMPTE ST2022-7 standard and that has undergone reception control using the modified sender information performs IGMP (Internet Group Management Protocol) JOIN control so that the receiver receives the same multicast address from each network interface. Therefore, as shown in the example of Fig. 8, by setting up a network configuration in which non-multiplexed multicast packets output from a sender that does not support SMPTE ST2110-7 can be transferred to each multiplexed network via a network switch, it is possible to take advantage of multicast and actually multiplex routes after the network switch.

[0073] Although one embodiment of the present invention has been described above, the present invention is not limited to the above embodiment and can be embodied in various other forms without departing from the spirit and scope of the present invention. Therefore, the above embodiment is merely illustrative in all respects and should not be interpreted as limiting. For example, a control protocol other than NMOS may be used. Furthermore, with regard to multiplexing of SMPTE ST2022-7, sender information may be modified so that equipment compatible with duplexing becomes equipment compatible with triplexing.

[0074] 1 Virtual node 10 Virtual receiver function block 11 Receiving side control interface 12 Storage unit 20 Virtual sender function block 21 Sending side control interface 30 Control controller function block 31 Control interface 32 Control destination information 50 Control network 51 Media network 60 Control controller 61 Control controller 70 Sender 80 Receiver 100 Example of receiving side IP system 101 Example of sending side IP system 200 Example of non-multiplexed SDP 201 Example of SDP corresponding to modified multiplexing 300 Example of non-multiplexed NMOS staged API 301 Example of NMOS staged API corresponding to modified multiplexing

Claims

1. A MoIP control device in an MoIP environment that transmits media signals by multicast, comprising: a memory unit; and a receiving side control interface function that receives reception control based on information including a multicast address, port number, and source address, and stores the information in the memory unit; wherein the device has one of the following functions, or both the first and second functions: a first function that is a sending side control interface function that publishes information held by the memory unit; and a second function that is a control controller function that has control destination information and controls reception so that receivers set in the control destination information receive based on the information held by the memory unit.

2. The MoIP control device according to claim 1, characterized in that it comprises a plurality of functional groups in any combination of the following: a set of functional groups having the function of the receiving control interface, the first function, and the second function; a set of functional groups having the function of the receiving control interface and the first function; and a set of functional groups having the function of the receiving control interface and the second function.

3. The MoIP control device according to claim 1 or 2, characterized in that it links the functions of two or more receiving control interfaces, and when the function of one of the receiving control interfaces is subjected to receiving control to receive based on the information, it compares the information in its own memory unit with the information in the other memory unit, and if the information is identical, it adds itself to the control destination information of the other, and if the information is not identical, it deletes itself from the control destination information of the other.

4. The MoIP control device according to claim 1 or 2, characterized in that the information held in said storage unit is modified so as to be multiplexed in accordance with SMPTE ST2022-7.

5. A program that causes a computer to function as the MoIP control device according to claim 1 or 2.

6. A program that causes a computer to function as the MoIP control device according to claim 3.

7. A program that causes a computer to function as the MoIP control device according to claim 4.

8. In an MoIP environment where media signals are transmitted by multicast, a MoIP control device that behaves as a receiver in terms of control, has a memory unit that stores parameters subject to reception control, and has a virtual receiver that behaves as if it is receiving.

9. A program that causes a computer to function as the MoIP control device according to claim 8.

Images