Program equipment information management device and its program, and controller and its program

Abstract

To provide a program device information management device which can be used with restrictions for each device in program production.SOLUTION: A program device information management device 20 includes: a program information storage part 23 for storing at least an identifier of a device 50 used in a program in association with the identifier of the program to be produced; a registered device information acquisition part 21 for acquiring the device information on the device 50 from a device information registration device 40; a device information storage part 22 for storing the device information in association with the identifier of the device 50; and a program device information distribution part 24 for distributing the device information corresponding to the identifier of the device 50 associated with the identifier of the program to the controller 10 in response to the acquisition request of the device information from the controller 10 including the identifier of the single program.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a program device information management apparatus and its program, as well as a controller and its program.

Background Art

[0002] In a program production system such as a television program, instead of using an SDI (Serial Digital Interface) for connecting devices for transmitting video, audio, and control signals, an IP (Internet Protocol) network is increasingly being used. When using an IP network, device control via the network becomes possible, and thus it is required that one control application can control devices of various vendors using a common control method for vendors.

[0003] Therefore, in recent years, the implementation of NMOS (Networked Media Open Specification) formulated by AMWA (Advanced Media Workflow Association), which is a common control method for vendors using an IP network, has been progressing for each device used in a program production system. In IS-04 of AMWA NMOS (see Non-Patent Document 1), APIs (Application Programming Interfaces) provided by a device information registration apparatus (RDS: Registration and Discovery System) for registering and detecting devices (nodes) in a system are defined. For example, in IS-04, a registration API for registering devices in the system with the RDS and a query API for acquiring information on devices existing in the system are defined.

[0004] Also, in IS-05 of AMWA NMOS (see Non-Patent Document 2), a connection API for performing switching control for controlling connections between devices on a network is defined. 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] Now, referring to Figure 7, we will explain the configuration and control flow of a conventional NMOS-compatible program production system 100. The program production system 100 comprises a controller 10B, an authentication / authorization server 30B, a device information registration device 40, and multiple devices 50, all connected via an IP network (not shown).

[0006] Controller 10B is a control device that performs connection control of equipment 50 within the program production system 100 using a connection API. The Authentication and Authorization Server (Auth)30B is a server that issues authorizations compliant with IS-10. The device information registration device (RDS) 40 is a device that registers and detects devices 50 within the program production system 100, and provides a registration API and a query API. Device (Node)50(501,…,50 N :N is an integer greater than or equal to 1) are program production equipment such as cameras and microphones that accept connection control via a connection API.

[0007] First, device 50 obtains authorization from the authentication / authorization server 30B to use the registration API in a manner compliant with IS-10 (S10). Next, device 50 registers its device information with the device information registration device 40 using the registration API (S11). At this time, the registration request using the registration API includes the authorization obtained in S10. Controller 10B obtains authorization from authentication / authorization server 30B to use the query API in accordance with IS-10 (S12). Controller 10B uses the query API to obtain device information for the devices 50 present in the program production system 100 from the device information registration device 40 (S13). At this time, the information acquisition request using the query API includes the authorization obtained in S12. The query API returns device information for all registered devices 50 as a response.

[0008] The controller 10B then obtains authorization from the authentication / authorization server 30B to use the connection API in accordance with IS-10 (S14). The controller 10B sends a control request to the connection API of the device 50 to control the device 50 (S15). At this time, the control request includes the authorization obtained in S14. This allows the program production system 100 to control various program production equipment (equipment 50) via an IP network. [Prior art documents] [Non-patent literature]

[0009] [Non-Patent Document 1] AMWA IS-04 NMOS Discovery and Registration Specification [Non-Patent Document 2] AMWA IS-05 NMOS Device Connection Management Specification [Non-Patent Document 3] AMWA IS-10 NMOS Authorization Specification [Non-Patent Document 4] RFC 7519 - JSON Web Token (JWT) [Overview of the project] [Problems that the invention aims to solve]

[0010] In conventional NMOS-compatible program production systems, the controller can connect to all devices once it obtains authorization from the authentication / authorization server to use the device (node) connection API. Furthermore, the information obtained from the device information registration device includes information on all devices. Therefore, with conventional NMOS-compatible program production systems, it is possible to control all equipment during program production, which can lead to the problem of accidentally controlling equipment being used for other program productions.

[0011] This invention has been made in view of the above problems, and aims to provide a program equipment information management device and its program, as well as a controller and its program, which can be used with restrictions on each piece of equipment in program production. [Means for solving the problem]

[0012] To solve the aforementioned problems, the program equipment information management device according to the present invention is a program equipment information management device that provides equipment information specifying the operation of equipment used in a program to a controller that controls NMOS-compatible program production equipment, and comprises a program information storage unit, a registered equipment information acquisition unit, an equipment information storage unit, and a program equipment information distribution unit.

[0013] In this configuration, the program equipment information management device stores in advance in the program information storage unit the identifiers of at least the equipment used in the program, associated with the identifier of the program to be produced. The program equipment information management device obtains authorization from the authentication / authorization server, using the method specified in IS-10, to use the interface of the equipment information registration device, which has been pre-registered with equipment information within the program production system, via the registered equipment information acquisition unit, and acquires equipment information such as the type and function of the equipment from the equipment information registration device. This allows the program equipment information management device to obtain equipment information necessary for program production from the equipment information registration device. The program device information management apparatus stores the acquired device information in a device information storage unit in association with an identifier of the device.

[0014] Then, the program device information management apparatus acquires, via a program device information distribution unit, an acquisition request for device information from a controller that includes authorization to use an interface of the program device information management apparatus acquired from an authentication / authorization server and an identifier of a single program. Then, the program device information management apparatus reads, via the program device information distribution unit, device information corresponding to an identifier of a device associated with an identifier of a program in a program information storage unit from the device information storage unit and distributes it to the controller.

[0015] As a result, only the device information used for producing a program specified by an identifier designated by the controller is distributed to the controller by the program device information management apparatus. Note that the program device information management apparatus can be operated by a program for causing a computer to function as each of the above-described units.

[0016] Also, in order to solve the above problems, a controller according to the present invention is a controller that controls an NMOS-compatible device for program production, and includes a program device information acquisition unit, a device control content reception unit, and a device control execution unit.

[0017] In such a configuration, the controller acquires, via the program device information acquisition unit, authorization to use an interface of the program device information management apparatus from an authentication / authorization server, and acquires device information corresponding to an identifier of a program from the program device information management apparatus. As a result, the controller acquires only the device information used for producing a program.

[0018] Then, the controller presents, via the device control content reception unit, the device information acquired by the program device information acquisition unit to the user on a display device such as a monitor, and receives an input of control content for the device from the user using a keyboard, a mouse, or the like. Then, the controller obtains, from the authentication and authorization server, authorization to use the interface of the device acquired by the device control execution unit, and instructs the device to execute the control content.

[0019] As a result, the controller can control only the devices used for program production. Note that the controller can operate a computer using a program for causing the computer to function as each of the above-described units.

Advantages of the Invention

[0020] According to the present invention, in program production, the devices controlled by the controller can be limited to the devices used for program production. As a result, the present invention can prevent performing control on devices that are erroneously used in other program productions.

Brief Description of the Drawings

[0021] [Figure 1] It is an overall configuration diagram showing the configuration of a program production system according to an embodiment of the present invention. [Figure 2] It is a block configuration diagram showing the configuration of a controller according to an embodiment of the present invention. [Figure 3] It is a block configuration diagram showing the configuration of a program device information management apparatus according to an embodiment of the present invention. [Figure 4] It is an explanatory diagram for explaining an example of program information. [Figure 5] It is an explanatory diagram for explaining the control flow of a program production system according to an embodiment of the present invention in comparison with the conventional one. [Figure 6] It is a sequence diagram showing the control flow of a program production system according to an embodiment of the present invention. [Figure 7] It is an explanatory diagram for explaining the configuration and control flow of a conventional program production system. [[ID= forty-two]]

Modes for Carrying Out the Invention

[0022] Embodiments of the present invention will be described below with reference to the drawings. ≪Program Production System Configuration≫ First, with reference to Figure 1, the configuration of the program production system 1 according to an embodiment of the present invention will be described.

[0023] Program production system 1 allows multiple program productions to share equipment within an NMOS-compatible system and control each piece of equipment individually. The program production system 1 comprises a controller 10, a program equipment information management device 20, an authentication / authorization server 30, an equipment information registration device 40, and multiple devices 50, all connected via an IP network 2. Note that, regarding the NMOS API, only those relevant to the present invention are described here; other APIs are omitted from the explanation.

[0024] The controller 10 controls the NMOS-compatible program production equipment 50 in the program production system 1. The controller 10 controls the connection of the equipment 50 within the program production system 1 using a Connection API. Here, the controller 10 obtains authorization from the authentication / authorization server 30 to acquire device information for individual devices 50 and authorization to control the devices 50, and obtains individual device information from the program device information management device 20 to control the devices 50. The controller 10 will be explained in detail later, referring to Figure 2.

[0025] The program equipment information management device 20 provides equipment information of the equipment used in the program to the controller 10 that controls the NMOS-compatible program production equipment 50 in the program production system 1. The program equipment information management device 20 obtains equipment information for registered equipment 50 from the equipment information registration device 40 and responds to the controller 10 with the requested equipment information for equipment 50. The API used to access the program equipment information management device 20 will hereafter be referred to as the Schedule API. The program equipment information management device 20 will be explained in detail later, referring to Figure 3.

[0026] Authentication and authorization server (Auth)30 is a server that issues authorizations compliant with AMWA NMOS IS-10. Here, the authentication and authorization server (Auth) 30, in accordance with IS-10, grants registration authorization to the device 50 and authorization to control the device 50 to the controller 10. In addition to its IS-10 compliance functionality, the authentication and authorization server (Auth) 30 includes an authorization request processing unit (not shown) that accepts authorization requests specifying individual devices 50 to which access tokens are applied. The method of accepting authorization requests by individually specifying devices to which access tokens are applied is a common technique and can be implemented, for example, using the open-source authentication software "Keycloak".

[0027] The Equipment Information Registration Device (RDS) 40 is a device that registers and detects equipment 50 within the program production system 1, which conforms to AMWA NMOS IS-04. The device information registration device 40 has a function to accept registration requests to register device information for device 50 within the device via a Registration API. The device information registration device 40 also has a function to accept query requests to provide device information for registered device 50 via a Query API. Device information refers to various pieces of information that identify the operation of device 50, including an identifier, type (camera, microphone, etc.), and function (number of video / audio input / output ports, etc.).

[0028] Device (Node)50(501,…,50 N(where N is an integer greater than or equal to 1) are various devices such as cameras, microphones, video mixers, and monitors used to produce programs compliant with AMWA NMOS IS-04 / 05. Device 50 obtains authorization from the authentication / authorization server 30 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 the device information registration device 40. Device 50 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. The controller 10 and the program equipment information management device 20 will be described in detail below.

[0029] <Controller> The configuration of the controller 10 will be described with reference to Figure 2. As shown in Figure 2, the controller 10 includes an authorization acquisition unit 11, a program equipment information acquisition unit 12, an equipment control content reception unit 13, and an equipment control execution unit 14.

[0030] The authorization acquisition unit 11 obtains authorization (access tokens) from the authentication / authorization server 30 to access the APIs of each device within the system. Here, the authorization acquisition unit 11 obtains authorization from the authentication / authorization server 30 to use the schedule API of the program equipment information management device 20, in accordance with IS-10. The authorization acquisition unit 11 outputs authorization to the program equipment information acquisition unit 12 for using the acquired schedule API.

[0031] Furthermore, when the authorization acquisition unit 11 receives a request from the device control execution unit 14 for authorization to use the connection API of the device 50 to be controlled, it obtains authorization from the authentication / authorization server 30. In this case, the authorization acquisition unit 11 notifies the authentication / authorization server 30 of the identifier of the device 50 to be controlled and the identifier of the user requesting authorization, and obtains authorization to use the connection API. For example, here we assume that the authentication / authorization server 30 has Keycloak, which is authentication software, installed. In that case, the authorization acquisition unit 11 can obtain authorization by POSTing (HTTP POST) a JSON object with the key "audience" and the value the identifier of the device 50 as claim_token, using the request format defined by UMA (User-Managed-Access), which is an access management protocol standard. The authorization acquisition unit 11 outputs authorization to the device control execution unit 14 for using the acquired connection API.

[0032] The program equipment information acquisition unit 12 requests equipment information, including authorization to use the schedule API and a program identifier, from the schedule API of the program equipment information management device 20, and acquires equipment information corresponding to the program identifier. This device information includes the identifier, type (camera, microphone, etc.), and functions (number of video / audio input / output ports, etc.) of device 50, as well as program-related information (such as the time the device can be used within the program).

[0033] The program equipment information acquisition unit 12 includes the program identifier specified by the user in the authorization for using the schedule API of the program equipment information management device 20, which is input from the authorization acquisition unit 11, and requests and acquires equipment information for the equipment 50 used in the program from the program equipment information management device 20. The program identifier may be a predetermined value entered by the user from an external source, or the user may obtain a list of program identifiers from the program equipment information management device 20 and select one from that list. The program equipment information acquisition unit 12 outputs the acquired equipment information of the equipment 50, along with the identifier of the equipment 50 and the user identifier, to the equipment control content reception unit 13.

[0034] The device control content receiving unit 13 presents the device information of the device 50, which is input from the program device information acquisition unit 12, to the user and accepts input from the user regarding the control content for the device 50. Here, the control content refers to information that defines the control operation of the device 50, 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. The device control content receiving unit 13 displays the device information of the device 50 input from the program device information acquisition unit 12 on a display device such as a monitor (not shown), and accepts the control content via an input device such as a keyboard or mouse (not shown). The device control content receiving unit 13 outputs the input control content, along with the identifier of the device 50 and the user identifier, to the device control execution unit 14.

[0035] The device control execution unit 14 instructs the device 50 to be controlled to execute control based on the control content input from the device control content reception unit 13. The device control execution unit 14 outputs to the authorization acquisition unit 11 a request for authorization to use the connection API of the device 50 to be controlled, which includes the identifier of the device 50 to be controlled and the user identifier, both of which are input from the device control content reception unit 13 along with the control content. The device control execution unit 14 obtains authorization from the authorization acquisition unit 11 and outputs the authorization and control details as a connection request to the connection API of the device 50 to be controlled.

[0036] Furthermore, the device control execution unit 14 may reuse the authorization for the device 50 obtained from the authorization acquisition unit 11 in its internal memory if the device control content reception unit 13 instructs it to control the same device 50 that it has previously controlled. This reduces the communication load on the IP network 2.

[0037] With the configuration described above, the controller 10 can only control the equipment 50 that the user uses for program production, preventing erroneous control of other equipment 50. Furthermore, the controller 10 can be operated using a program that causes a computer (not shown in the diagram) to function as one of the aforementioned components.

[0038] <Program Equipment Information Management Device> Next, with reference to Figure 3, the configuration of the program equipment information management device 20 will be described. As shown in Figure 3, the program equipment information management device 20 includes a registered equipment information acquisition unit 21, an equipment information storage unit 22, a program information storage unit 23, a program equipment information distribution unit 24, and an authorization issuance rule setting unit 25.

[0039] The registered device information acquisition unit 21 obtains authorization from the authentication / authorization server 30 to use the interface of the device information registration device 40, which has previously registered the device information of the NMOS-compatible devices 50 within the program production system 1, and acquires the device information from the device information registration device 40. Here, the Registered Device Information Acquisition Unit 21 requests and obtains authorization from the Authentication and Authorization Server 30 to use the Query API of the Device Information Registration Device 40, using the method defined in IS-10. Then, using the obtained authorization, the Registered Device Information Acquisition Unit 21 retrieves device information for the registered devices 50 from the Query API of the Device Information Registration Device 40. The registered device information acquisition unit 21 stores the device information of the acquired device 50 in the device information storage unit 22.

[0040] The registered device information acquisition unit 21 may either periodically acquire device information in response to the inquiry API of the device information registration device 40, or it may establish a WebSocket connection with the device information registration device 40 and acquire updated device information from the device information registration device 40 in real time. This allows the registered device information acquisition unit 21 to keep the device information of device 50 up to date in the device information storage unit 22.

[0041] The device information storage unit 22 stores the device information of the device 50 registered in the device information registration device 40, which was acquired by the registered device information acquisition unit 21, in association with the identifier of the device 50. The device information storage unit 22 can be made up of a general storage medium such as semiconductor memory.

[0042] The program information storage unit 23 stores information related to the program being produced (program information) in association with the program identifier. Program information includes, for example, the "program identifier (d1)", "production time (d2)", "identifier of the equipment used (d3)", and "identifier of the users involved in production (d4)", as shown in Figure 4.

[0043] The "program identifier (d1)" is identification information that identifies the program being produced. For example, "Program 1," "Program 2," etc. "Production time (d2)" is time information indicating the start and end times of the program being produced. For example, the start time might be 2022 / 01 / 01 10:00:00 and the end time 2022 / 01 / 01 11:00:00. The "Identifier of Equipment Used (d3)" is identification information that identifies the equipment 50 used when producing the program. For example, "CAM1 (camera)", "MIC1 (microphone)", "VMIX1 (video mixer)", etc. The "User Identifier for Production (d4)" is identification information that identifies the users involved in the production of the program. For example, "USER1", "USER2", etc. This program information may be configured using an external configuration file or similar method, or it may be configured using an API provided by the program equipment information distribution unit 24.

[0044] The program equipment information distribution unit 24 distributes the relevant equipment information in response to requests for information on the equipment 50 used in the program being produced. Here, the program equipment information distribution unit 24 distributes equipment information corresponding to the program identifier to the controller 10 when it receives a request from the controller 10 via the schedule API to obtain equipment information that includes a single program identifier in the authorization to use the API. The program equipment information distribution unit 24 reads program information (see Figure 4) corresponding to the requested program identifier from the program information storage unit 23, reads equipment information corresponding to the identifier of the equipment to be used from the equipment information storage unit 22, generates equipment information including the program information, and distributes it to the controller 10.

[0045] The authorization issuance rule setting unit 25 reflects any changes to the program information stored in the program information storage unit 23 in the authorization issuance rules of the authentication / authorization server 30. Specifically, the authorization issuance rule setting unit 25 configures the authentication / authorization server 30 to issue authorization to use the connection API of equipment 50 within the program's production time if the program's production time is changed, or if the equipment 50 or users used outside of production time are changed. As a result, the authentication / authorization server 30 is configured to issue authorization for equipment used in a program to users involved in the program's production at the start time of the program's production time, and to cancel the configuration at the end time. Furthermore, the authorization issuance rule setting unit 25 configures the authentication / authorization server 30 to issue authorizations in response to requests from users involved in program production if the identifier of a user involved in program production changes. This allows the authentication and authorization server 30 to grant authorization only to users involved in the production of the program during the program's production time.

[0046] With the configuration described above, the program equipment information management device 20 only distributes equipment information for the equipment 50 used in program production to the controller 10, thereby preventing the controller 10 from incorrectly controlling other equipment 50. Furthermore, the program equipment information management device 20 can be operated using a program that causes a computer (not shown in the figure) to function as one of the aforementioned components.

[0047] ≪Operation of the program production system≫ Next, with reference to Figures 5 and 6 (and Figures 1 to 3 as appropriate for the configuration), the operation of the program production system 1 according to an embodiment of the present invention will be described.

[0048] In step S1, each device 50 obtains authorization (access token) from the authentication / authorization server 30 to register with the program production system 1. Here, device 50 obtains authorization from the authentication / authorization server 30 to use the registration API of the device information registration device 40 in a manner compliant with IS-10.

[0049] In step S2, the device 50 registers itself with the device information registration device 40. Here, device 50, using a method compliant with IS-04, sends a registration request to the device information registration device 40, including the authorization and device information obtained in step S1, using the registration API of the device information registration device 40. As a result, device 50 connected to the program production system 1 is registered in the device information registration device 40.

[0050] In step S3, the program equipment information management device 20 obtains authorization (access token) from the authentication / authorization server 30 to retrieve equipment information for the registered equipment 50. Here, the program equipment information management device 20 obtains authorization from the authentication / authorization server 30 to use the inquiry API of the equipment information registration device 40, using a method compliant with IS-10, via the registered equipment information acquisition unit 21.

[0051] In step S4, the program equipment information management device 20 obtains equipment information from the equipment information registration device 40. Here, the program equipment information management device 20, using the registered equipment information acquisition unit 21, sends an inquiry request to the equipment information registration device 40, including the authorization obtained in step S3, using the inquiry API of the equipment information registration device 40 in a manner compliant with IS-04, and acquires the equipment information of equipment 50. Furthermore, the registered device information acquisition unit 21 stores the device information of the acquired device 50 in the device information storage unit 22.

[0052] In step S5, if the program information is changed, the program equipment information management device 20 uses the authorization issuance rule setting unit 25 to reflect the changes in the authorization issuance rules of the authentication / authorization server 30. In this process, the authorization issuance rule setting unit 25 notifies the authentication / authorization server 30 of any changes to the program information stored in the program information storage unit 23, and the authentication / authorization server 30 modifies the authorization issuance rule. Note that step S5 only occurs when the user changes the program information.

[0053] In step S6, the controller 10 obtains authorization (access token) from the authentication / authorization server 30 to use the program equipment information management device 20. Here, the controller 10, via the authorization acquisition unit 11, obtains authorization from the authentication / authorization server 30 to use the schedule API of the program equipment information management device 20 in a manner compliant with IS-10.

[0054] In step S7, the controller 10 obtains equipment information for the equipment 50 used in the program to be produced from the program equipment information management device 20. Here, the controller 10, using the program equipment information acquisition unit 12, requests the program equipment information management device 20 to acquire information, including the program identifier specified by the user in the authorization to use the schedule API acquired in step S6, using the schedule API. The program equipment information management device 20 then uses the program equipment information distribution unit 24 to read equipment information corresponding to the program identifier from the program information storage unit 23 and distribute it to the controller 10. Then, the controller 10 acquires device information corresponding to the program identifier using the program device information acquisition unit 12.

[0055] In step S8, the controller 10 obtains authorization (access token) from the authentication / authorization server 30 to use the connection API that controls the registered device 50. Here, the controller 10, through the device control content receiving unit 13, presents the device information acquired in step S7 to the user and receives control content for the device 50 from the user. The controller 10 then obtains authorization from the authentication / authorization server 30 to use the connection API, which includes the identifier of the device 50 and the user identifier, via the authorization acquisition unit 11.

[0056] In step S9, the controller 10 controls the device 50 according to the control content specified by the user. Here, the controller 10, via the device control execution unit 14, authorizes the use of the connection API acquired in step S8 and outputs the control content specified by the user to the connection API. This allows the controller 10 to control only the equipment 50 that the user uses for program production.

[0057] As explained above, the program production system 1 has a program equipment information management device 20 that only distributes equipment information for the equipment 50 used in program production to the controller 10. Therefore, the program production system 1 can prevent the controller 10 from incorrectly controlling other equipment 50 that are not used in the program. Although embodiments of the present invention have been described above, the present invention is not limited to these embodiments. For example, although the program equipment information management device 20 is configured to have separate storage units 22 and 23 inside, it may also store data in a single storage medium divided into areas. Alternatively, the storage units 22 and 23 may be separated as external storage devices. [Explanation of Symbols]

[0058] 1. Program Production System 10 Controllers 11. Approval Acquisition Department 12 Program Equipment Information Acquisition Unit 13. Equipment Control Content Reception Unit 14. Equipment Control Execution Unit 20 Program Equipment Information Management Device 21. Registered Equipment Information Acquisition Unit 22 Device information storage section 23 Program Information Storage Unit 24 Program Equipment Information Distribution Department 25. Authorization Issuance Rule Setting Department 30 Authentication and authorization servers 40. Device Information Registration Device 50 equipment 2 IP Networks

Claims

1. A program equipment information management device that provides equipment information specifying the operation of equipment used in a program to a controller that controls NMOS-compatible program production equipment, A program information storage unit that stores at least the identifiers of the equipment used in the program in association with the identifier of the program being produced, A registered device information acquisition unit obtains authorization from an authentication / authorization server to use the interface of a device information registration device that has the aforementioned device information registered in advance, and acquires the aforementioned device information from the device information registration device. A device information storage unit that stores the device information in association with the identifier of the device, A program equipment information distribution unit delivers equipment information corresponding to the identifier of the equipment associated with the program identifier to the controller in response to a request from the controller to acquire equipment information, which includes authorization using the interface of the program equipment information management device acquired from the authentication / authorization server and a single identifier of the program; A program equipment information management device characterized by being equipped with the following features.

2. The program information storage unit also stores the production time of the program. The program equipment information management device according to claim 1, further comprising an authorization issuance rule setting unit that configures the authentication / authorization server to issue authorization to use the interface of the equipment within the production time of the program if the production time of the program is changed.

3. The aforementioned program information storage unit further stores identifiers of users involved in the production of the program. The program equipment information management device according to claim 2, characterized in that the authorization issuance rule setting unit is configured to issue authorization to the authentication / authorization server in response to requests from users involved in the production of the program when the user's identifier is changed.

4. A program for causing a computer to function as a program equipment information management device according to any one of claims 1 to 3.

5. A controller for controlling NMOS-compatible equipment used for program production, A program equipment information acquisition unit obtains authorization from an authentication / authorization server to use the interface of the program equipment information management device described in any one of claims 1 to 3, and obtains equipment information corresponding to the program identifier from the program equipment information management device, The device control content receiving unit presents the device information acquired by the aforementioned program device information acquisition unit to the user and accepts input of control content for the device from the user, A device control execution unit obtains authorization from an authentication / authorization server to use the interface of the device corresponding to the aforementioned device information, and instructs the device to execute the control content. A controller characterized by having the following features.

6. The controller according to claim 5, characterized in that the device control execution unit reuses the previous authorization when controlling the same device that it has controlled previously.

7. A program for causing a computer to function as the controller described in claim 5.

Images