MoIP control device and program

Abstract

Using multicast on IP networks The media signal is transmitted The MoIP IP system enables control that takes advantage of the benefits of multicast. [Solution] No media signal reception The virtual receiver takes control of the reception and, based on the received information, No media signals are transmitted Virtual Sender discloses that information , and / or control other receivers. Also, modify the sender information of a sender that does not comply with SMPTE ST2022-7 to make it appear as a sender that complies with SMPTE ST2022-7.

Description

[Technical field]

[0001] The present invention relates to a MoIP (Media Over IP) environment using multicast in an IP network. Control device and regarding the program. [Background technology]

[0002] The technology of transmitting media contents (e.g., video, audio, auxiliary data, hereinafter referred to as media signals) using an IP network is called MoIP, and in relation to this, SMPTE specifies in the SMPTE ST2022-10 standard (see Non-Patent Document 1), SMPTE ST2110-6 standard (see Non-Patent Document 2), and related standards that media signals are transmitted in RTP packets using unicast or multicast. When multicast is used, when a sender sends a packet to a multicast address, multiple receivers can receive the packet 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 acquiring node information on a network. In addition, AMWA NMOS IS-05 (see Non-Patent Document 5) has been published as a standard for controlling transmission to nodes.

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

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

[0006] [Patent Document 1] Patent 7401097 [Non-patent literature]

[0007] [Non-Patent Document 1] SMPTE ST2110-10 [Non-Patent Document 2] SMPTE ST2022-6 [Non-Patent Document 3] SMPTE ST2022-7 [Non-Patent Document 4] AMWA NMOS IS-04 Discovery and Registration Specification [Non-Patent Document 5] AMWA NMOS IS-05 Connection Management [Non-Patent Document 6] RFC 4566 [Non-Patent Document 7] RFC 5888 [Non-Patent Document 8] RFC 7104 Summary of the Invention [Problem to be solved by the invention]

[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 when 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 by 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 IP networks, requires that receivers be controlled to receive from which sender. In broadcasting facilities using MoIP (hereafter referred to as IP systems), when media signals are sent and received between multiple IP systems, if the sending IP system wants to switch senders, it needs to cross-system borders to control the receiver in the receiving IP system. However, it may not be clear from the sending IP system which receiver is receiving which sender in the receiving IP system, and the nodes of each IP system are registered in the Registration & Discovery System (RDS) within that system and controlled by a controller within that system, making it difficult to control across systems. If control crosses system borders, there is also the problem that the independence of the systems cannot be maintained.

[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 between multiple RDSs are used.

[0011] The SDI interfacing method involves converting the IP packets of the media signal into SDI at the sending IP system, and then converting the SDI back into IP packets at the receiving IP system. Although this method allows for the same operation as before, it has significant disadvantages, such as not taking advantage of any 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's own system and retransmitting them as a media signal with a different fixed multicast address to another system. The receiving side of the other system only needs to receive a fixed multicast address at all times, so it can be operated in the same way as SDI mentioned above, but 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 handle 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 the media signal 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 advantages of multicast and operate in the same way as the above-mentioned SDI. 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, and there is a high possibility that shocks will occur in the video and audio when switching, which may cause damage to the broadcast in the case of a broadcasting station.

[0014] The method of sharing information between multiple RDSs is to obtain sender information from the RDS of the sending IP system and install an RDS shared server that registers that information in the RDS of the receiving IP system, so that the sender of the sending IP system appears to the receiving IP system as if it were the sender of its own system, and media signals can be received from senders of other systems. This method makes it possible to share resources while taking advantage of the advantages of multicast. However, when an emergency switchover is required, such as when the sender of the sending IP system breaks down, there are problems in that the RDS shared server cannot immediately detect the information update in the RDS of the sending IP system, even if the information in the RDS of the sending IP system is updated, and there is no guarantee that the controller of the receiving IP system will detect the information update in the RDS of its own system and immediately switch the receiver's destination, making this method unsuitable for use in emergency switchover.

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

[0016] The present invention has been made in consideration of the above problems, and while taking advantage of the advantages of multicast, it clarifies the boundaries of interfaces between IP systems and enables the sending IP system to switch senders at any timing, similar to SDI operation.The receiving IP system can arbitrarily distribute the 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 compatible receiver, the packet can pass through each of the multiplexed network paths along the way. [Means for solving the problem]

[0018] In order to solve the above problems, one embodiment of the present invention provides a method for transmitting media signals by multicast in an MoIP environment, comprising: storage section and, Multicast address, port number and source address of Information included The information transmission device is characterized in that it has one of the following functions: a first function which is a function of a transmitting side control interface that receives information based on the information received from the receiver and stores the information in the memory unit and discloses the information held by the memory unit; and a second function which is a function of a control controller that has control destination information and controls reception so that a receiver set in the control destination information receives information based on the information held by the memory unit, or both the first function and the second function.

[0019] One embodiment of the present invention comprises: The communication device is characterized by having a plurality of functional collections in any combination of a function of the receiving control interface, a set of functional collections having the first function and the second function, a function of the receiving control interface and a set of functional collections having the first function, a function of the receiving control interface and a set of functional collections having the second function.

[0020] One embodiment of the present invention comprises: Functions of two or more of said receiving control interfaces By coordinating Functions of the receiver control interface but Reception is performed based on the above information When receiving control, the device has a function of comparing the information in its own storage unit with that of the other storage unit, and if they are identical, adding itself to the control destination information of the other device, and if they are not identical, deleting itself from the control destination information of the other device. It is characterized by .

[0021] One embodiment of the present invention comprises: The storage unit The function to modify the information held by the above to multiplex the SMPTE ST2022-7 is provided. It is characterized by the following.

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

[0023] 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 including a virtual receiver and one or both of a virtual sender and a control controller will be referred to as a "virtual node". Effect of the Invention

[0024] According to the present invention, in MoIP, which transmits media signals using multicast over an IP network, it is possible to clarify the boundaries of interfaces between IP systems while taking advantage of the advantages of multicast. That is, a sending IP system can switch senders at any timing, 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, and this also has great cost benefits.

[0025] In addition, by taking advantage of the benefits 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. [Brief description of the drawings]

[0026] [Figure 1] FIG. 2 is a block diagram showing a functional configuration of a virtual node according to an embodiment of the present invention. [Diagram 2] FIG. 13 is a configuration diagram of an example of using a virtual node of an embodiment of the present invention as a virtual receiver and controller. [Diagram 3] FIG. 13 is a configuration diagram of an example of using a virtual node of an embodiment of the present invention as both a virtual receiver and a virtual sender. [Figure 4] FIG. 11 is a block diagram showing an example of a functional configuration for combining two or more virtual nodes according to an embodiment of the present invention and dynamically updating control destination information. [Figure 5a] FIG. 1 is a first diagram of an example of cooperation between two IP systems to which a virtual node according to one embodiment of the present invention is applied. [Figure 5b] FIG. 2 is a second diagram of an example of cooperation between two IP systems to which a virtual node according to one embodiment of the present invention is applied. [Figure 5c] FIG. 11 is a third diagram of an example of cooperation between two IP systems to which a virtual node of one embodiment of the present invention is applied. [Figure 5d]FIG. 4 is a fourth diagram of an example of cooperation between two IP systems to which a virtual node of one embodiment of the present invention is applied. [Figure 6] FIG. 13 is a diagram illustrating an example of modifying a non-multiplexed SDP into an SDP compatible with multiplexing according to one embodiment of the present invention. [Figure 7] FIG. 13 is a diagram illustrating an example of modifying parameters of a non-multiplexed NMOS staged API to parameters corresponding to multiplexing according to an embodiment of the present invention. [Figure 8] FIG. 2 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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0028] FIG. 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 the functional blocks of a virtual receiver 10, a virtual sender 20, and a controller 30.

[0029] The virtual receiver 10 includes a receiving side 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 sending side control interface 21 . The receiving control interface 11 and the transmitting control interface 21 may be implemented, for example, by 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 by, for example, an AMWA NMOS IS-05 interface. The apparatus 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 apparatus according to the embodiment of the present invention.

[0030] The receiving side control interface 11 behaves as a normal receiver in terms of control. That is, 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 (DNS-Based Service Discovery) or registered in RDS. When it receives reception control as a receiver, it stores the information in the memory unit 12 and behaves as if it has started receiving.

[0031] 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).

[0032] The sending side control interface 21 behaves as a normal sender in terms of control. That is, 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 as desired. It then behaves as if it is transmitting multicast based on the information stored in the memory unit 12. However, if it were a normal sender, it would be able to change the destination multicast address and receive control to stop / start transmission, but if it receives such control, it will return an error or ignore the request.

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

[0034] The control destination information 32 is set in advance as information about the receiver that performs reception control. That is, when the control controller 30 is configured with AMWA NMOS IS-05, it is configured to include information about the receiver ID, the address of the NMOS API (Application Programming Interface), and the port. There may be zero or more pieces of control destination information. When there is zero control destination information, no control is performed.

[0035] The flow of operations according to one embodiment of the present invention will be specifically described with reference to the drawings. FIG. 2 shows an example of using virtual node 1 as a virtual receiver and controller.

[0036] In this example, the network is composed of 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 the receiver, a sender 70 that transmits the media signals, a receiver 80 that receives the media signals, and a virtual node 1. A control controller 60, a sender 70, a receiver 80, and a virtual node 1 are connected to the control network 50, and the sender 70 and the receiver 80 are connected to the media network 51.

[0037] The control network 50, the media network 51, the controller 60, the sender 70, and the receiver 80 are devices configured using existing technology. A single network may be used as both the control network 50 and the media network 51. A plurality of senders 70 and receivers 80 may be provided.

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

[0039] The flow of control will be explained in alphabetical order in parentheses in the figure. The controller 60 in this example 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 of 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 on the receiver 80 based on the sender information in the storage unit 12 (C). Receiver 80 begins multicast reception of the media signal from sender 70 (D).

[0040] As a result of the above, the receiver 80 is able to receive a media signal from the sender 70 without being directly controlled by the controller 60 .

[0041] By applying the above, it is possible to quickly control reception of a sender selected from multiple senders in one IP system at a receiver in the other IP system.

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

[0043] In this example, it is composed of 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. A control controller 60, a control controller 61, a sender 70, a receiver 80 and a virtual node 1 are connected to the control network 50, and the sender 70 and the receiver 80 are connected to the media network 51.

[0044] 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. A single network may be used as both the control network 50 and the media network 51. A plurality of senders 70 and receivers 80 may be provided.

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

[0046] 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 of the sender 70 is registered in the storage unit 12. Nothing is registered in the control destination information 32, and no particular control is performed. The 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). Receiver 80 begins multicast reception of the media signal from sender 70 (D).

[0047] 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.

[0048] 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.

[0049] 4 is an example of a 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. Each virtual node 1 may be in a separate housing or in the same housing. In the case of the same housing, a plurality of virtual receivers and virtual senders may be configured as one node. 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.

[0050] When a control signal arrives from outside and the information in its own memory unit 12 changes, the source virtual node 1 compares the information in its own memory unit 12 with the information in memory 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, nothing is done. 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, nothing is done.

[0051] The flow of operations according to one embodiment of the present invention will be specifically described with reference to the drawings. 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 in the drawings.

[0052] The IP system 100 is an example that includes a 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 that includes a controller 61, a plurality of senders 70, and a virtual node 1.

[0053] The solid arrows in the figure represent preset control destination information of each virtual node. In the virtual node A1, the receiver A80 is registered as control destination information. In the virtual node B1, the receiver B80 is registered as control destination information. In the virtual node C1, a receiver C80 is registered as control destination information. In virtual node Y1, virtual node X1 is registered as control destination information.

[0054] The dotted arrows in the figure (arrows painted white) represent the relationship between the addition source virtual node and the addition destination virtual node that has been set in advance. Virtual node A1 is the source virtual node, and virtual node X1 is registered as the 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.

[0055] The flow of FIG. 5a will be explained in alphabetical order in parentheses. The control controller 61 acquires sender information from sender S70 and controls virtual node Y1 to receive sender S70 (A). The controlled virtual node Y1 controls reception on virtual node X1 (B). As a result, the sender information of sender S70 is registered in the storage unit 12 of virtual node X1. At this point, there is no registration in the control destination information 32 of virtual node X1, so no further control is performed.

[0056] Next, the flow of FIG. 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 node A1 and virtual node C1 (D). Virtual node A1 and virtual node C1 that have received reception control then apply reception control to receiver A80 and receiver C80, respectively (E). At this point, receiver A80 and receiver C80 start receiving media signals from sender S70. At the same time, virtual node A1 and virtual node C1 compare the information that has received reception control with the information in storage unit 12 of virtual node X1, and since they match, virtual node A1 and virtual node C1 are added to control destination information 32 of virtual node X1 (F).

[0057] Next, the flow of FIG. 5c will be explained in alphabetical order in parentheses. Assume that the IP system 100 switches the media signal being received by the receiver C80 to the media signal from the sender U70 of its own system. The control controller 60 acquires sender information from the sender U70 and applies reception control to the virtual node C1 based on the sender information (G). The virtual node C1 that has received reception control performs reception control on the receiver C80 (H). At this point, the receiver C80 switches to receiving a media signal from the sender U70. At the same time, the virtual node C1 compares the information that has received reception control with the information in the memory unit 12 of the virtual node X1, and since they do not match, deletes the virtual node C1 from the control destination information 32 of the virtual node X1 (I).

[0058] Next, the flow of FIG. 5d will be explained in alphabetical order in parentheses. Assume that the IP system 101 needs to switch the source of the media signal being transmitted to the IP system 100 from sender S70 to sender T70. The control controller 61 acquires sender information from sender T70 and controls virtual node Y1 to receive from sender T70 (J). Having received the reception control, virtual node Y1 applies reception control to virtual node X1 (K). As a result, the sender information of sender T70 is registered in the storage unit 12 of virtual node X1. Since virtual node A1 was registered in the control destination information of virtual node X1 in the above step (I), virtual node X1 applies reception control to virtual node A1 (L). Virtual node A1 exercises reception control on receiver A80 (M). At this point, receiver A80 switches to receiving the media signal from sender T70.

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

[0060] 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 makes the interface boundary between systems clear.

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

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

[0063] The specific processing contents will be explained.

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

[0065] Prepare an empty string variable. The string group 1 is output to the string variable, and then "a=group:DUP identifier 1 identifier 2" is output to indicate that duplication is occurring. Identifier 1 and identifier 2 can be any unique alphanumeric string ("primary" and "secondary" in the example of FIG. 6). If further duplication is occurring, the number of identifiers can be listed accordingly. The character string group 2 is output to the character string variable, and "a=mid:identifier 1" is output to indicate that this is the first media of a duplicated system. Again, the character string group 2 is output to the character string variable, and "a=mid:identifier 2" is output, indicating that this is the second media of the duplicated system.

[0066] The character string variable generated as described above is regarded as the modified SDP 201.

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

[0068] A specific process will now be described. Prepare an empty JSON object variable. The first object in the array of the value of the "transport_params" key of the non-multiplexing parameters 300 is extracted, a "transport_params" key is generated in the JSON object variable, and the value is placed as an array, with two objects identical to the object. All other keys and values ​​are copied as is.

[0069] The JSON object variable generated as described above is set as a parameter 301 corresponding to the modified multiplexing.

[0070] The sender information modified as described above is recognized as sender information conforming to the SMPTE ST2110-7 standard. This makes it possible to treat it as a normal sender conforming to the SMPTE ST2110-7 standard when combined with virtual node 1. The same operation may be achieved by incorporating this sender information modification function into a conventional controller.

[0071] As a result, a sender that does not support route multiplexing can be made to operate as if it supports route multiplexing. Receivers that support SMPTE ST2022-7 standard multiplexing and have been subjected to reception control using modified sender information will apply IGMP (Internet Group Management Protocol) JOIN control so that they receive the same multicast address from their respective network interfaces. Therefore, as shown in the example in Figure 8, by configuring a network configuration in which non-multiplexed multicast packets output from senders that do not support SMPTE ST2110-7 can be forwarded via a network switch to each of the multiplexed networks, it is possible to take advantage of the benefits of multicast and actually multiplex the routes after the network switch.

[0072] 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 scope of the present invention. Therefore, the above embodiment is merely an example in every respect and should not be interpreted as being restrictive. For example, a control protocol other than NMOS may be used. In addition, for multiplexing of SMPTE ST2022-7, sender information may be modified so that a device compatible with duplexing is compatible with triplexing. [Explanation of symbols]

[0073] 1 Virtual Node 10 Virtual Receiver Functional Block 11 Receiver Control Interface 12 Storage section 20 Virtual sender function block 21 Sender Control Interface 30 Controller Function Block 31 Control Interface 32 Control information 50 Control Network 51 Media Network 60 Controller 61 Controller 70 Sender 80 Receiver 100 Example of a receiving IP system 101 Example of a sending IP system 200 Non-multiplexed SDP example 201 An example of a modified SDP for multiplexing 300 An example of a non-multiplexed NMOS staged API 301 An example of modified NMOS staged API for multiplexing

Claims

1. In an MoIP environment where media signals are transmitted by multicast, A storage unit; A function of a receiving side control interface that receives a receiving control based on information including a multicast address, a port number, and a source address and stores the information in the storage unit; having A first function which is a function of a transmission side control interface that publishes information held by the storage unit; A second function is a function of a controller that includes control destination information and controls reception so that a receiver set in the control destination information receives based on the information stored in the storage unit; or both the first function and the second function; 13. A MoIP control device comprising:

2. A set of function aggregates having a function of the receiving side control interface, the first function, and the second function; a set of function collections having the functions of the receiving control interface and the first function; a set of function aggregates having the function of the receiving control interface and the second function; The present invention has a plurality of functional assemblies in any combination of the above.

2. The MoIP control device according to claim 1.

3. The functions of two or more receiving control interfaces are linked, and when the function of one of the receiving control interfaces is subjected to receiving control to receive information based on the information, the function compares the information in the memory unit of the receiving interface with the information in the memory unit of the other interface, and if the information is identical, adds the receiving interface to the control destination information of the other interface, and if the information is not identical, deletes the receiving interface from the control destination information of the other interface.

3. The MoIP control device according to claim 1 or 2.

4. 3. The MoIP control device according to claim 1, wherein the information stored in said storage unit is modified so as to conform to SMPTE ST2022-7 multiplexing.

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

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

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

Images