Controller, DNS list acquisition device and DNS list server, and their programs

Abstract

To make it possible to facilitate the connection and operation of a plurality of NMOS-compliant program production systems that are capable of stand-alone operation.SOLUTION: A consolidated program production system Sjoin includes a plurality of program production systems for each domain and a DNS list server 70. The plurality of program production systems for each domain includes an NMOS-compliant controller 10, an authorization server 20, an RDS 30 and equipment 40, a DNS server 50, and a DNS list acquisition device 60 that acquires a DNS list for each domain from the DNS list server 70. The DNS list server 70 provides the DNS lists.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a controller, a DNS list retrieval device, a DNS list server, and programs for them. [Background technology]

[0002] Television program production systems are increasingly using IP (Internet Protocol) networks, rather than SDI (Serial Digital Interface), to transmit video, audio, and control signals between devices. Because IP networks allow for device control over the network, there is a growing need for a single control application to control devices from various vendors using a vendor-standard control method.

[0003] Therefore, in recent years, the implementation of NMOS (Networked Media Open Specification), a vendor-common control method developed by AMWA (Advanced Media Workflow Association) that utilizes IP networks, has been progressing in each piece of equipment used in program production systems. AMWA NMOS's IS-04 (see Non-Patent Document 1) defines the APIs (Application Programming Interfaces) provided by the Registration and Discovery System (RDS) that registers and discovers devices (nodes) within the system. For example, IS-04 defines a Registration API for registering devices within the system with the RDS, and a Query API for obtaining information about devices existing within the system.

[0004] Furthermore, AMWA NMOS's IS-05 (see Non-Patent Document 2) defines a Connection API for performing switching control to manage connections between devices on a network. Furthermore, AMWA NMOS's IS-10 (see Non-Patent Document 3) defines an authorization method that restricts API usage using JWT (JSON [JavaScript Object Notation] Web Token) access tokens (see Non-Patent Document 4) to enhance API security.

[0005] Here, referring to Figure 15, we will explain the configuration and control flow of a conventional NMOS-compatible program production system SX. The program production system SX comprises a controller 10X, an authorization server 20, an RDS (Registration and Discovery System) 30, multiple devices 40, and a DNS (Domain Name System) server 50, all connected via an IP network (not shown).

[0006] Controller 10X is a control device that uses the Connection API to control the connection of equipment 40 within the program production system SX. Authorization server 20 is a server that issues authorizations compliant with IS-10. RDS30 is a device that registers and detects equipment 40 within the program production system SX, and provides a Registration API and a Query API. Equipment 40(401,…,40 M :M is an integer greater than or equal to 1) These are program production devices such as cameras and microphones that accept connection control via the Connection API. DNS server 50 is a server that stores and provides the address of authorization server 20 and endpoints for various APIs.

[0007] First, when device 40 is connected to the network, it queries the DNS server 50 to obtain the endpoint of the Registration API and the address of the authorization server 20 for obtaining authorization to use the Registration API (S10). Then, device 40 obtains authorization (authorization token) from authorization server 20 in an IS-10 compliant manner to use the Registration API (S11). Next, device 40 registers its device information with RDS30 using the Registration API (S12). At this time, the registration request using the Registration API includes the authorization obtained in S11.

[0008] Controller 10X queries DNS server 50 to obtain the endpoint of the Query API and the address of authorization server 20 for obtaining authorization to use the Query API (S13). Then, the controller 10X obtains authorization from the authorization server 20 to use the Query API in a manner compliant with IS-10 (S14). Next, the controller 10X uses the Query API to obtain device information for the devices 40 present in the program production system SX from the RDS30 (S15). At this time, the information acquisition request using the Query API includes the authorization obtained in S14. The Query API returns device information for all registered devices 40 (including the Connection API endpoints) as a response.

[0009] The controller 10X then obtains authorization from the authorization server 20 to use the Connection API in an IS-10 compliant manner (S16). The controller 10X sends a control request to the device 40's Connection API to control the device 40 (S17). At this time, the control request includes the authorization obtained in S16. This allows the program production system SX to control various program production equipment (equipment 40) via an IP network.

[0010] Note that the program production system SX may be configured by omitting the authorization server 20. In this case, the device 40 omits the acquisition of authorization (authorization token) in S11 and registers device information in the RDS 30 (S12). Further, the controller 10X omits the acquisition of authorization in S14 and acquires device information from the RDS 30 (S15). Furthermore, the controller 10X omits the acquisition of authorization in S16 and transmits a control request to the device 40 (S17).

Prior Art Documents

Non-Patent Documents

[0011]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0012] In a conventional program production system compatible with AMWA NMOS, it is premised that all information is collected in the RDS, and only one RDS exists in the program production system. Therefore, in order to operate a conventional program production system independently in a broadcast relay vehicle or in connection with a broadcast station system, an RDS must exist in both the relay vehicle and the broadcast station.

[0013] Conventional program production systems, when connected to the broadcasting station's system via a network and not utilizing the RDS (Radio Digital System) of the outside broadcast vehicle, have the problem that the outside broadcast vehicle cannot be operated until it is connected to the broadcasting station. Furthermore, if the system uses the outside broadcast vehicle's RDS when it is not connected to the broadcasting station, and then uses the broadcasting station's RDS after connection, it becomes necessary to change the registration and contact information for each device depending on the connection status, resulting in modification work and downtime.

[0014] This invention has been made in view of the above problems, and aims to provide a program production system controller, a DNS list acquisition device, and a DNS list server, as well as programs thereof, that enable easy connection and operation of multiple NMOS-compatible program production systems that can be operated independently. [Means for solving the problem]

[0015] To solve the aforementioned problems, the controller according to the present invention is a controller in a linked program production system that connects multiple program production systems for each domain, each equipped with an NMOS-compatible controller, an equipment information registration device and program production equipment, a DNS server and a DNS list acquisition device that obtains a DNS list for each domain from a DNS list server, and a DNS list server that provides a DNS list, via a network, and comprises a DNS list receiving unit, an NMOS interface control unit and a user interface control unit (see Figures 3 and 14).

[0016] In this configuration, the controller receives a domain-specific DNS list from the DNS list acquisition device via the DNS list receiving unit. This allows the controller to recognize the addresses of DNS servers belonging to multiple domains without requiring any special modifications. The controller, via its NMOS interface control unit, obtains the Query API endpoint for the device information registration device for each domain from the DNS server listed in the DNS list. Using the Query API, it obtains device information for program production equipment for each domain and controls the program production equipment.

[0017] Furthermore, the controller displays device information via the user interface control unit and instructs the NMOS interface control unit to control the program production equipment based on user commands. This allows the controller to acquire device information from NMOS-compatible program production equipment belonging to different domains and control program production equipment belonging to multiple domains. Furthermore, the controller can be operated using a program that causes the computer to function as one of the aforementioned components.

[0018] Furthermore, in order to solve the aforementioned problems, the DNS list acquisition device according to the present invention is a DNS list acquisition device in a linked program production system that connects multiple program production systems for each domain, each equipped with an NMOS-compatible controller, an equipment information registration device and program production equipment, a DNS server and a DNS list acquisition device that acquires a DNS list for each domain from the DNS list server, and a DNS list server that provides the DNS list, via a network, and comprises a DNS list storage unit, a DNS list exchange unit and a DNS list distribution unit (see Figure 5).

[0019] In this configuration, the DNS list acquisition device pre-stores the addresses of DNS servers belonging to its own domain in the DNS list storage unit, associating them with domain names, as a DNS list for its own domain. The DNS list acquisition device then connects to the DNS list server via the DNS list exchange unit, distributes its own domain's DNS list to the DNS list server, and acquires available domain-specific DNS lists from the DNS list server and stores them in the DNS list storage unit. The DNS list acquisition device then distributes the updated DNS list to the controller whenever the DNS list stored in the DNS list storage unit is updated by the DNS list distribution unit. This allows the DNS list acquisition device to provide the DNS server's DNS list to the controller without requiring any special modifications, and without needing to be aware of whether the system is operating independently (within a single domain) or in multiple domains. Furthermore, the DNS list acquisition device can be operated using a program that causes the computer to function as each of the aforementioned components.

[0020] Furthermore, in order to solve the above problems, the DNS list server according to the present invention is a DNS list server in a linked program production system in which a plurality of program production systems for each domain, each equipped with an NMOS-compatible controller, an equipment information registration device and program production equipment, a DNS server and a DNS list acquisition device that acquires a DNS list for each domain from the DNS list server, and a DNS list server that provides a DNS list are connected by a network, and the DNS list server is configured to include a DNS list storage unit and a DNS list distribution unit (see Figure 7).

[0021] In this configuration, the DNS list server accepts connections from DNS list acquisition devices via the DNS list distribution unit, receives DNS lists for the domain to which the DNS list acquisition device belongs from the connected DNS list acquisition device, stores them in the DNS list storage unit, and distributes all DNS lists stored in the DNS list storage unit to the currently connected DNS list acquisition device. This allows the DNS list server to distribute the DNS lists of DNS servers belonging to each domain of the program production system to the DNS list acquisition devices of all program production systems. Furthermore, a DNS list server can be operated using a program that causes a computer to function as one of the aforementioned components. [Effects of the Invention]

[0022] According to the present invention, multiple NMOS-compatible program production systems can be connected and operated. Furthermore, according to the present invention, the operation of multiple NMOS-compatible program production systems or a single system can be easily switched by connecting or disconnecting the network. This allows the present invention to flexibly construct a program production system. [Brief explanation of the drawing]

[0023] [Figure 1] This is a diagram showing the overall configuration of a program production system according to an embodiment of the present invention. [Figure 2] This is a configuration diagram showing the configuration of a linked program production system in which multiple program production systems according to the embodiment of the present invention are connected. [Figure 3] This is a block diagram showing the configuration of a controller according to an embodiment of the present invention. [Figure 4] This table shows examples of what the Domain Management Department manages. [Figure 5] This is a block diagram showing the configuration of a DNS list acquisition device according to an embodiment of the present invention. [Figure 6] This table shows examples of DNS lists stored by a DNS list retrieval device. [Figure 7] This is a block diagram showing the configuration of a DNS list server according to an embodiment of the present invention. [Figure 8] This table shows examples of DNS lists stored by a DNS list server. [Figure 9] This is an explanatory diagram for illustrating the control flow of multiple program production systems (linked program production systems) according to an embodiment of the present invention, in comparison with conventional systems. [Figure 10] This is a sequence diagram (1 / 3) showing the control flow of multiple program production systems according to an embodiment of the present invention. [Figure 11] This is a sequence diagram (2 / 3) showing the control flow of multiple program production systems according to an embodiment of the present invention. [Figure 12]This is a sequence diagram (3 / 3) showing the control flow of multiple program production systems according to an embodiment of the present invention. [Figure 13] This is a diagram showing the overall configuration of a modified example of a program production system according to an embodiment of the present invention. [Figure 14] This is a block diagram showing a modified configuration of the controller according to an embodiment of the present invention. [Figure 15] This is an explanatory diagram illustrating the configuration and control flow of a conventional program production system. [Modes for carrying out the invention]

[0024] Embodiments of the present invention will be described below with reference to the drawings. ≪Program Production System Configuration≫ First, with reference to Figures 1 and 2, the configuration of the program production system S according to an embodiment of the present invention will be described. Figure 1 shows an example configuration of a program production system S configured independently, while Figure 2 shows an example configuration of a linked program production system Sjoin, which consists of multiple program production systems S connected together.

[0025] The program production system S allows multiple program productions to share equipment within an NMOS-compatible system and control each piece of equipment individually. The program production system S comprises an NMOS-compatible controller 10, an authorization server 20, an RDS (Registration and Discovery System: device information registration device) 30 and equipment (program production equipment) 40, a DNS (Domain Name System) server 50, and a DNS list acquisition device 60, all connected via an IP network N.

[0026] The program production system S constitutes one domain in the IP network N. When multiple program production systems S are connected, as shown in Figure 2, a linked program production system Sjoin is configured by connecting a DNS list server 70 to the IP network N which contains multiple program production systems S. Here, the connected program production system Sjoin will be described by taking an example of connecting program production systems S A ,S B . However, three or more program production systems S may be connected.

[0027] The program production system S A uses the equipment 40B within the program production system S<9>to carry out program production together with the equipment 40A within the program production system S B . That is, the program production system S A functions as the side that uses the equipment 40, and the program production system S B functions as the side that provides the equipment 40. Note that in FIG. 1, only the NMOS APIs related to the present invention are described for the NMOS APIs, and the descriptions of other APIs are omitted.

[0028] The controller 10 is a broadcast controller that collectively controls the NMOS-compatible program production equipment 40 in the program production system S. The controller 10 performs connection control of the equipment 40 using the Connection API (connection API) for the equipment 40 in a single or multiple program production systems S. For example, the controller 10A obtains the address lists (DNS lists) of the DNS servers 50A and 50B of the multiple program production systems S A ,S B from the DNS list acquisition device 60A, and obtains the addresses of the authorization servers 20A and 20B and the endpoints (addresses) of the Query APIs of the RDSs 30A and 30B from the DNS servers 50A and 50B. Thereby, in addition to the authorization server 20A and the RDS 30A, the controller having access to the authorization server 20B and the RDS 30B, and being able to control the equipment 40A and 40B of the program production systems S A ,S B . Note that the controller 10 will be described in detail later with reference to FIG. 3.

[0029] Authorization server 20 is a server that issues authorizations (authorization tokens) compliant with AMWA NMOS IS-10. Here, the authorization server 20 has the function of granting registration authorization to the device 40 in accordance with IS-10, and granting the controller 10 authorization to acquire device information of the device 40 and authorization to control the device 40.

[0030] The RDS (Device Information Registration Device) 30 is a device that registers and detects devices 40 within the program production system S, which conforms to AMWA NMOS IS-04. RDS30 has a function to accept registration requests to register device information for equipment 40 within the device via its Registration API. RDS30 also has a function to accept query requests to provide device information for registered equipment 40 via its Query API. The device information includes various types of information for identifying the operation of the device 40, such as the name of the device 40, the endpoint (address) of the API it provides, the parameters of the signals to be transmitted, and the types of signals that can be received.

[0031] Equipment (Program production equipment) 40 (401, ..., 40 M :M is an integer greater than or equal to 1) refers to various program production equipment such as cameras, microphones, video mixers, and monitors for producing programs compliant with AMWA NMOS IS-04 / 05. Device 40 obtains authorization from the authorization server 20 to use the Registration API in accordance with AMWA NMOS IS-10, and registers the device by sending a registration request containing authorization and device information to RDS30. Device 40 accepts control instructions as connection requests via the Connection API. The Connection API defines various connection controls, such as transmitting video output from a camera to a monitor.

[0032] DNS server 50 is a server that provides the address (IP address) of the authorization server 20 of the program production system S, as well as the endpoints (IP addresses) of various APIs (Registration API, Query API, etc.). Note that there may be more than one DNS server 50 deployed in the program production system S.

[0033] The DNS list acquisition device 60 obtains a list of available DNS server addresses (DNS list) from the DNS list server 70. The DNS list acquisition device 60 notifies the DNS list server 70 of the DNS list of the domain of the program production system S to which it is connected, and in doing so, obtains the DNS list of all connected program production systems S (linked program production system Sjoin) from the DNS list server 70. The DNS list acquisition device 60 will be explained in detail later, referring to Figure 5.

[0034] The DNS list server 70 stores the address lists (DNS lists) of the DNS servers 50 of multiple program production systems S (linked program production system Sjoin) and provides them to each program production system S. The DNS list server 70 obtains the domain name of each program production system S and the addresses of DNS servers 50 available within each program production system S from the DNS list acquisition device 60 of each program production system S, and provides the DNS list available for use by multiple program production systems S to the respective DNS list acquisition device 60. The DNS list server 70 will be explained in detail later, referring to Figure 7. The controller 10, DNS list acquisition device 60, and DNS list server 70 will be described in detail below.

[0035] <Controller> The configuration of the controller 10 will be described with reference to Figure 3. As shown in Figure 3, the controller 10 comprises a DNS list receiving unit 11, an NMOS interface control unit 12, and a user interface control unit 13.

[0036] The DNS list receiving unit 11 receives the DNS list from the DNS list acquisition device 60. The DNS list receiving unit 11 connects to the DNS list acquisition device 60 and receives a DNS list from the DNS list acquisition device 60 containing the addresses of currently available DNS servers. The DNS list includes a predetermined domain name for each domain that constitutes the program production system S, and the addresses of DNS servers available within that domain. In this case, the DNS list receiving unit 11 simply obtains the available DNS list, regardless of whether the program production system S is operating independently or with multiple connections; no changes are required depending on the operating configuration. The DNS list receiving unit 11 outputs the received DNS list to the domain management unit 120 of the NMOS interface control unit 12.

[0037] The NMOS interface control unit 12 obtains the addresses of the authorization servers 20 for each domain and the RDS 30 Query API endpoints from the DNS servers 50 listed in the DNS list. Using authorization from the authorization servers 20, it obtains device information for each device 40 for each domain via the Query API and controls the devices 40. In other words, the NMOS interface control unit 12 controls the interface with various NMOS-compatible devices within all domains included in the DNS list received by the DNS list receiving unit 11. In this configuration, the NMOS interface control unit 12 comprises a domain management unit 120, a DNS-SD processing unit 121, an authorization acquisition unit 122, a device information acquisition unit 123, and a device control unit 124.

[0038] The domain management unit 120 maintains input / output information for each domain with various NMOS-compatible devices within that domain and controls those devices. When the domain management unit 120 receives a DNS list for each domain from the DNS list receiving unit 11, it stores the addresses of the DNS servers included in the DNS list in a storage unit (not shown in the diagram). For example, as shown in Figure 4, the domain management unit 120 stores the DNS server address "192.0.2.1" associated with the domain name "sub1.example.com". Note that multiple DNS server addresses may be stored for the same domain name. Similarly, the domain management unit 120 stores DNS server addresses for other domains, associating them with their domain names. The domain management unit 120 then outputs the DNS server addresses for each domain to the DNS-SD processing unit 121.

[0039] When the DNS-SD processing unit 121 inputs the address of the authorization server 20 and the Query API endpoint (address) for each domain, the domain management unit 120 stores the address of the authorization server 20 and the Query API endpoint in a storage unit (not shown in the diagram). For example, as shown in Figure 4, the domain management unit 120 stores the authorization server address "192.0.2.2" and the Query API endpoint (address) "192.0.2.3" associated with the domain name "sub1.example.com". Similarly, the domain management unit 120 stores the authorization server address and Query API endpoint for other domains, associated with their domain names. The domain management unit 120 then outputs the authorization server address for each domain to the authorization acquisition unit 122.

[0040] When the domain management unit 120 receives a domain-specific authorization (authorization token) from the authorization acquisition unit 122, it stores the domain-specific authorization token in a storage unit (not shown in the diagram). For example, as shown in Figure 4, the domain management unit 120 stores the authorization token obtained from the authorization server 20, associating it with the domain name "sub1.example.com". Similarly, the domain management unit 120 stores authorization tokens for other domains, associating them with their domain names. The domain management unit 120 then outputs the authorization token for each domain and the Query API endpoint (address) to the device information acquisition unit 123.

[0041] When the domain management unit 120 receives device information for each domain from the device information acquisition unit 123, it stores the device information in a storage unit (not shown in the diagram). For example, as shown in Figure 4, the domain management unit 120 stores the device information of device 40 belonging to the domain, associating it with the domain name "sub1.example.com". In the example in Figure 4, the first device information (device 1) is stored as "label:"cam1", connection_api: "https: / / 192.0.2.5:8080 / x-nmos / connection / v1.1 / "". This device information indicates that device 40 is a camera labeled "cam1" and that the Connection API endpoint is "https: / / 192.0.2.5:8080 / ...". The domain management unit 120 then outputs device information for each domain to the user interface control unit 13.

[0042] When the domain management unit 120 receives the control result of the device 40 from the device control unit 124, it outputs the control result to the user interface control unit 13. When the domain management unit 120 receives control information from the user interface control unit 13, which includes device information (including the Connection API endpoint) and control details for the device 40 to be controlled, it outputs a control instruction to the device control unit 124 that includes the Connection API endpoint, the authorization token for the domain to which the device 40 to be controlled belongs, and the control details.

[0043] The DNS-SD (DNS Service Discovery) processing unit 121 retrieves the addresses of the domain-specific authorization servers 20 and the Query API endpoints (addresses) from the domain-specific DNS servers 50. The DNS-SD processing unit 121 receives the DNS server addresses for each domain from the domain management unit 120 and obtains the address of the authorization server 20 and the Query API endpoint from each DNS server 50. The DNS-SD processing unit 121 outputs the addresses of the authorization servers 20 for each domain and the Query API endpoints obtained to the domain management unit 120.

[0044] The authorization acquisition unit 122 acquires domain-specific authorization (authorization token) from the domain-specific authorization server 20. The authorization acquisition unit 122 receives the authorization server address for each domain from the domain management unit 120 and obtains an authorization token from the respective authorization server 20. The authorization acquisition unit 122 outputs the acquired authorization token for each domain to the domain management unit 120.

[0045] The device information acquisition unit 123 acquires device information for each domain's devices 40 from the RDS 30 for each domain. The device information acquisition unit 123 receives the authorization token for each domain and the Query API endpoint from the domain management unit 120, and acquires the device information held by the RDS30 by sending the authorization token corresponding to the domain to the Query API of the RDS30 for each domain. The device information acquisition unit 123 outputs the acquired device information to the domain management unit 120.

[0046] The device control unit 124 controls the operation of the device 40 to be controlled. The device control unit 124 receives a control instruction from the domain management unit 120, which includes the Connection API endpoint, the authorization token for the domain to which the device 40 to be controlled belongs, and the control content. The device control unit 124 then outputs the authorization token and the control content to the Connection API of the device 40. The device control unit 124 receives the control results in response to control instructions from the device 40 and outputs them to the domain management unit 120.

[0047] The user interface control unit 13 displays device information of the device 40 input from the domain management unit 120 and instructs the NMOS interface control unit to control the device 40 based on instructions from the user. Here, the control content refers to information that defines the control operation of the device 40, such as the start time of operation, stop time of operation, video and audio parameters, input and output destinations for video and audio, and mixing ratio.

[0048] The user interface control unit 13 displays device information of the device 40 input from the domain management unit 120 on a display device such as a monitor (not shown), and accepts control content via an input device such as a keyboard or mouse (not shown). The user interface control unit 13 outputs control information, including the device information (including the Connection API endpoint) and the control details of the controlled device 40, to the domain management unit 120. The user interface control unit 13 also displays the control results of the device 40, which are input from the domain management unit 120, on a display device (not shown).

[0049] With the configuration described above, the controller 10 can acquire and control the device information of the device 40 in the manner defined by AMWA NMOS for a plurality of program production systems S. Further, since the controller 10 can grasp the connection status based on the DNS list, it can easily switch between the single operation and the multiple operation of the program production system S. Note that the controller 10 can be operated by a program for causing a computer (not shown) to function as each of the above-described units.

[0050] <DNS List Acquisition Device> Next, referring to FIG. 5, the configuration of the DNS list acquisition device 60 will be described. As shown in FIG. 5, the DNS list acquisition device 60 includes a DNS list storage unit 61, a DNS list exchange unit 62, and a DNS list distribution unit 63.

[0051] The DNS list storage unit 61 stores the domain name and the address of the domain to which the DNS server 50 belongs. The DNS list storage unit 61 can be configured by a general storage medium such as a semiconductor memory. The DNS list storage unit 61 stores in advance the name of its own domain and the address of the DNS server belonging to its own domain by means of an external setting file or the like. The DNS list storage unit 61 stores the DNS lists of all domains registered in the DNS list server 70 by the DNS list exchange unit 62. Also, the DNS list storage unit 61 reads out the DNS list by the DNS list distribution unit 63.

[0052] The DNS list exchange unit 62 connects to the DNS list server 70, distributes the DNS list of its own domain to the DNS list server 70, and acquires the DNS list for each available domain from the DNS list server 70. The DNS list exchange unit 62 connects to the DNS list server 70 via the network and sends the domain name of its own domain, stored in the DNS list storage unit 61, and the addresses of the DNS servers 50 belonging to its own domain as a DNS list to the DNS list server 70. The address of the DNS list server 70 is set in advance using an external configuration file or the like. The DNS list exchange unit 62 then retrieves a DNS list from the DNS list server 70 for all domains currently connected to and available to the DNS list server 70, and stores the DNS list in the DNS list storage unit 61, associating it with the domain names.

[0053] As a result, the DNS list storage unit 61 stores a DNS list 600 in which domain names 601 and DNS server addresses 602 are associated, as shown in Figure 6. In the example in Figure 6, two DNS server addresses, 602 "203.0.113.1" and "203.0.113.2", are listed as a third domain not shown in Figure 2, corresponding to the domain name 601 "sub3.example.com". Thus, multiple DNS servers may exist for a single domain. The DNS list exchange unit 62 obtains the DNS list from the DNS list server 70 whenever the DNS list is updated, and updates the DNS list stored in the DNS list storage unit 61.

[0054] Furthermore, if the DNS list exchange unit 62 loses connection with the DNS list server 70, or if the connection failed during the initial connection, it stores an empty DNS list in the DNS list storage unit 61. As a result, the DNS list storage unit 61 stores only the domain name and DNS server address of the local domain, and the program production system S operates independently.

[0055] The DNS list distribution unit 63 distributes the updated DNS list to the controller 10 whenever the DNS list stored in the DNS list storage unit 61 is updated. The DNS list distribution unit 63 accepts a connection from the DNS list receiving unit 11 of the controller 10 and sends the DNS list stored in the DNS list storage unit 61 to the connected DNS list receiving unit 11. The DNS list distribution unit 63 sends the latest DNS list to the DNS list receiving unit 11 whenever the DNS list stored in the DNS list storage unit 61 is updated.

[0056] With the configuration described above, the DNS list acquisition device 60 can notify the controller 10 of the addresses of DNS servers belonging to multiple domains. This allows the controller 10 to obtain the addresses of authorization servers 20 and RDS 30 in different domains that exist individually in multiple program production systems S. Furthermore, the DNS list acquisition device 60 can be operated using a program that causes a computer (not shown in the figure) to function as one of the aforementioned components.

[0057] <DNSリストサーバ> Next, with reference to Figure 7, the configuration of the DNS list server 70 will be described. As shown in Figure 7, the DNS list server 70 comprises a DNS list storage unit 71 and a DNS list distribution unit 72.

[0058] The DNS list storage unit 71 stores the domain names of all domains and the addresses of DNS servers associated with all the domains when multiple program production systems S are connected to a network, as a DNS list. The DNS list storage unit 71 can be made of a general storage medium such as semiconductor memory. The DNS list storage unit 71 stores a DNS list (domain name and DNS server address) for each domain, as provided by the DNS list distribution unit 72. Furthermore, the DNS list storage unit 71 is read by the DNS list distribution unit 72, which reads all DNS lists.

[0059] In other words, as shown in Figure 8, the DNS list storage unit 71 stores a DNS list 700 in which domain names 701 and DNS server addresses 702 are associated. In the example in Figure 8, two DNS server addresses, 702 "203.0.113.1" and "203.0.113.2", are listed as a third domain not shown in Figure 2, corresponding to the domain name 701 "sub3.example.com".

[0060] The DNS list distribution unit 72 accepts connections from DNS list acquisition devices 60, receives DNS lists of the domain to which the DNS list acquisition device 60 belongs from the connected DNS list acquisition device 60, stores them in the DNS list storage unit 71, and distributes all DNS lists stored in the DNS list storage unit 71 to the currently connected DNS list acquisition device 60.

[0061] The DNS list distribution unit 72 accepts network connections from the DNS list acquisition device 60 (DNS list exchange unit 62). The DNS list distribution unit 72 then receives the DNS list from the connected DNS list acquisition device 60 and stores it in the DNS list storage unit 71. The DNS list distribution unit 72 also transmits the DNS list corresponding to all domains stored in the DNS list storage unit 71 to the connected DNS list acquisition device 60. The DNS list distribution unit 72 sends the latest DNS list stored in the DNS list storage unit 71 to all currently connected DNS list acquisition devices 60 whenever the DNS list stored in the DNS list storage unit 71 is updated.

[0062] Furthermore, if the DNS list distribution unit 72 loses connection with the DNS list acquisition device 60, it deletes the DNS list corresponding to the address of the DNS list acquisition device 60 that lost connection from the DNS list storage unit 71. Then, the DNS list distribution unit 72 sends the latest DNS list to all currently connected DNS list acquisition devices 60.

[0063] With the configuration described above, the DNS list server 70 can output the addresses of DNS servers belonging to different domains to the DNS list acquisition device 60. This allows the DNS list server 70 to connect multiple program production systems S belonging to different domains via a network, thereby enabling the construction of a large-scale system. Furthermore, the DNS list server 70 can be operated using a program that causes a computer (not shown in the diagram) to function as one of the aforementioned components.

[0064] ≪Operation of the program production system≫ Next, referring to Figures 9 to 12 (and Figures 3, 5, and 7 as appropriate for the configuration), the operation of multiple program production systems S (linked program production system Sjoin) according to the embodiment of the present invention will be described. Here, as shown in Figure 2, there are two program production systems S A S B The operation will be explained using an example of how it is connected.

[0065] Also, here, as shown in Figure 9, the program production system S A Program production system S B A system that utilizes equipment 40B (a program production system on the equipment user side), program production system S B Program production system S A This system provides equipment 40B (a program production system on the equipment provider side). Figure 9 is a diagram that corresponds to the configuration in Figure 2 and shows the step numbers of the operation. Figures 10 to 12 are sequence diagrams that divide the operation from the connection of the program production system S to the control of equipment 40 into specific operation sections.

[0066] <System Connection> First, referring mainly to Figure 10, we will discuss the two program production systems S A ,S B This section explains the process of connecting the devices.

[0067] In step S1, the DNS list acquisition device 60A connects to the DNS list server 70 via the DNS list exchange unit 62 and sends the local domain name and the DNS server addresses belonging to the local domain, stored in the DNS list storage unit 61, as a DNS list to the DNS list server 70. The DNS list server 70 then receives the DNS list via the DNS list distribution unit 72 and stores it in the DNS list storage unit 71.

[0068] In step S2, the DNS list server 70, via the DNS list distribution unit 72, transmits the DNS list (domain name, DNS server address) corresponding to all domains stored in the DNS list storage unit 71 to all currently connected DNS list acquisition devices 60 (in this case, DNS list acquisition devices 60A). Here, the DNS list acquisition devices 60A receive the DNS list for all domains via the DNS list distribution unit 72 and store it in the DNS list storage unit 61.

[0069] In step S3, the DNS list acquisition device 60A transmits the DNS list stored in the DNS list storage unit 61 to the controller 10A via the DNS list distribution unit 63. At this time, the DNS list distribution unit 63 accepts a connection from the DNS list receiving unit 11 of the controller 10A and transmits the DNS list to the controller 10A with which the connection has been established. The controller 10A then receives the DNS list via the DNS list receiving unit 11, and the domain management unit 120 stores the DNS list for each domain.

[0070] The operation of controller 10B and DNS list acquisition device 60B in steps S1' to S3' is the same as the operation of controller 10A and DNS list acquisition device 60A in steps S1 to S3, so the explanation is omitted. Furthermore, the operation of steps S2″ and S3″ is the same as that of steps S2 and S3, so the explanation is omitted. Through the above operations, the program production system S that will make the connection... A ,S BControllers 10A and 10B will store the addresses of 50 DNS servers for each domain.

[0071] <Device Registration> Next, referring mainly to Figure 11, we will discuss two program production systems S A ,S B The operation for registering device 40 will be described below. Furthermore, it is assumed that the DNS server 50 already stores the address of the authorization server 20 of the program production system S and the endpoints of various APIs (Registration API, Query API, etc.).

[0072] In step S4, DNS server 50A sends the address of authorization server 20A within its own domain and the registration API endpoint of RDS30A to the requesting device 40A.

[0073] In step S5, device 40A receives information from authorization server 20A regarding the program production system S A Obtain authorization (authorization token) to register. Here, device 40A obtains authorization from authorization server 20A to use the RDS30A Registration API in an IS-10 compliant manner.

[0074] In step S6, device 40A registers itself with RDS30A. Here, device 40A, using the Registration API of RDS30A in accordance with IS-04, sends a registration request to RDS30A that includes the authorization and device information obtained in step S5. As a result, RDS30A receives the program production system S A The device 40A connected to it will be registered.

[0075] The operation of steps S4' to S6' is performed by the program production system S A Program production system S corresponding to steps S4 to S6 in the above BSince this is the same operation, the explanation will be omitted. Through the above operations, the program production system S A ,S B The RDS30A and 30B will have device information for 40 devices belonging to their respective domains registered.

[0076] <Equipment Control> Next, referring mainly to Figure 12, we will discuss the program production system S. A Controller 10A of the program production system S A ,S B This section describes the operation of controlling devices 40A and 40B.

[0077] In step S7, the controller 10A, using the DNS-SD processing unit 121, obtains the addresses of the domain-specific authorization servers 20A and 20B, as well as the Query API endpoint (address), from the domain-specific DNS servers 50A and 50B whose addresses were obtained in step S3 (Figure 10).

[0078] In step S8, the controller 10A, via the authorization acquisition unit 122, obtains authorization (authorization token) from the domain-specific authorization servers 20A and 20B, whose addresses were obtained in step S7, to acquire device information for devices 40A and 40B registered in RDS 30A and 30B. Here, the authorization acquisition unit 122 obtains authorization tokens from the authorization servers 20A and 20B, respectively, in an IS-10 compliant manner, for using the Query APIs of RDS30A and 30B.

[0079] In step S9, the controller 10A uses the device information acquisition unit 123 to acquire device information for devices 40A and 40B belonging to their respective domains from RDS 30A and 30B. Here, the device information acquisition unit 123 uses the Query API of RDS30A and 30B obtained in step S7 in a manner compliant with IS-04 to send a query request to RDS30A and 30B that includes the authorization token obtained in step S8, and acquires device information for devices 40A and 40B.

[0080] In step S10, the controller 10A controls the devices 40A and 40B according to the control content specified by the user, via the user interface control unit 13. Here, the user interface control unit 13 outputs to the Connection API the authorization to use the Connection API included in the device information acquired in step S9, and the control content specified by the user. As a result, controller 10A can access program production system S belonging to the same domain. A Equipment 40A within the building and program production system S belonging to a different domain B It can control the internal device 40B.

[0081] As explained above, the program production system S can be configured as a standalone NMOS-compatible system, or multiple program production systems S can be connected to control the equipment 40 of multiple program production systems S.

[0082] ≪A variation of the program production system≫ In this configuration, the program production system S is equipped with an authorization server 20 to enhance API security, but the authorization server 20 can be omitted. In other words, the program production system S is an NMOS-compatible controller 10, as shown in Figure 13. MOD A program production system S, comprising RDS30 and equipment 40, DNS server 50, and DNS list acquisition device 60, is connected via an IP network N. MOD It may be configured as follows.

[0083] In this case, the controller 10 of the present invention MODAs shown in Figure 14, the controller 10 (see Figure 3) can be configured by omitting the authorization acquisition unit 122. Of course, the configuration in Figure 3 can also be used, and the authorization process can be skipped. In this case, the DNS-SD processing unit 121 receives the DNS server addresses for each domain from the domain management unit 120 and obtains the Query API endpoint from each DNS server 50. Then, the device information acquisition unit 123 receives the Query API endpoint for each domain from the domain management unit 120, and uses the Query API for each domain to acquire the device information held by the RDS30. This allows controller 10 MOD This allows control of the equipment 40 of one or more program production systems S without using the authorization server 20.

[0084] Although the program production system S according to an embodiment of the present invention has been described above, the spirit of the present invention is not limited to these descriptions and must be interpreted broadly based on the claims. Furthermore, it goes without saying that various changes and modifications based on these descriptions are also included in the spirit of the present invention. For example, the linked program production system Sjoin is not limited to a configuration in which individual program production systems S within a broadcasting station are linked, but may also be a configuration in which individual program production systems S between a broadcasting station and a mobile broadcasting station are linked, and the network may be a network within a broadcasting station or a broader network that extends beyond the broadcasting station. [Explanation of Symbols]

[0085] Sjoin Linked Program Production System S Program Production System 10 Controllers 11 DNS List Receiving Section 12 NMOS Interface Control Unit 120 Domain Management Department 121 DNS-SD Processing Unit 122 Approval Acquisition Department 123 Device information acquisition section 124 Equipment Control Unit 13 User Interface Control Unit 20 Authorization Servers 30 RDS (Device Information Registration Device) 40 pieces of equipment (equipment for program production) 50 DNS servers 60 DNS List Acquisition Devices 61 DNS List Storage Unit 62 DNS List Exchange Section 63 DNS List Distribution Department 70 DNS List Servers 71 DNS List Storage Unit 72 DNS List Distribution Department N IP Network

Claims

1. The controller in a linked program production system, which connects multiple program production systems for each domain, each comprising an NMOS-compatible controller, an equipment information registration device, and program production equipment, a DNS server, and a DNS list acquisition device that acquires a DNS list for each domain from a DNS list server, and the DNS list server that provides the DNS list, via a network, A DNS list receiving unit receives the DNS list from the DNS list acquisition device, The system obtains the Query API endpoint of the device information registration device for each domain from the DNS servers listed in the DNS list, and obtains device information of the program production equipment for each domain using the Query API, and also controls the program production equipment with an NMOS interface control unit. A user interface control unit that displays the aforementioned equipment information and instructs the NMOS interface control unit to control the program production equipment based on instructions from the user, A controller characterized by having the following features.

2. The aforementioned program production system further includes an authorization server, The controller according to claim 1, wherein the NMOS interface control unit obtains the address of the authorization server for each domain from the DNS server, and uses the authorization from the authorization server to obtain device information of the program production equipment for each domain using the Query API.

3. A program for causing a computer to function as the controller described in claim 1 or claim 2.

4. A DNS list acquisition device in a linked program production system, comprising a plurality of program production systems for each domain, each equipped with an NMOS-compatible controller, equipment information registration device and program production equipment, a DNS server, and a DNS list acquisition device for acquiring a DNS list for each domain from a DNS list server, and the DNS list server that provides the DNS list, all connected via a network, wherein the DNS list acquisition device is a DNS list acquisition device in a linked program production system, A DNS list storage unit that stores the addresses of the DNS servers belonging to its own domain in advance as a DNS list for its own domain, associating them with domain names, A DNS list exchange unit connects to the DNS list server, distributes the DNS list of its own domain to the DNS list server, and obtains the DNS list for each domain available from the DNS list server and stores it in the DNS list storage unit. Each time the DNS list stored in the DNS list storage unit is updated, the DNS list distribution unit distributes the updated DNS list to the controller. A DNS list acquisition device characterized by comprising the following:

5. The DNS list acquisition device according to claim 4, characterized in that the DNS list exchange unit deletes domain names other than its own domain and DNS server addresses from the DNS list storage unit when the connection with the DNS list server is disconnected.

6. A program for causing a computer to function as a DNS list acquisition device according to claim 4 or claim 5.

7. A DNS list server in a linked program production system, which connects multiple program production systems for each domain, each comprising an NMOS-compatible controller, an equipment information registration device, and program production equipment, a DNS server, and a DNS list acquisition device that acquires a DNS list for each domain from a DNS list server, and the DNS list server that provides the DNS list, via a network, A DNS list storage unit stores the addresses of the aforementioned DNS servers as a DNS list, associating them with domain names. A DNS list distribution unit receives a connection from the DNS list acquisition device, receives the DNS list of the domain to which the DNS list acquisition device belongs from the connected DNS list acquisition device, stores it in the DNS list storage unit, and distributes all DNS lists stored in the DNS list storage unit to the currently connected DNS list acquisition device. A DNS list server characterized by having the following features.

8. The DNS list server according to claim 7, characterized in that, when the connection with the DNS list acquisition device is disconnected, the DNS list distribution unit deletes the domain name and DNS server address corresponding to the domain of the DNS list acquisition device from the DNS list storage unit, and distributes the deleted DNS list to other DNS list acquisition devices that are currently connected.

9. A program for causing a computer to function as a DNS list server according to claim 7 or claim 8.

Images