WO2006054401A1 - フィールド機器及びこれを用いたシステム - Google Patents
フィールド機器及びこれを用いたシステム Download PDFInfo
- Publication number
- WO2006054401A1 WO2006054401A1 PCT/JP2005/018355 JP2005018355W WO2006054401A1 WO 2006054401 A1 WO2006054401 A1 WO 2006054401A1 JP 2005018355 W JP2005018355 W JP 2005018355W WO 2006054401 A1 WO2006054401 A1 WO 2006054401A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- additional
- group identifier
- field device
- business
- field
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
Definitions
- the present invention relates to a field device and a system in which a plurality of field devices are connected to each other via a network, and in particular, a function (operation) for a field device can be easily added.
- the present invention relates to a field device capable of operating independently of each other and a system using the same.
- JP-A-10-215492, JP-A-2001-051716, JP-A-2002-318702, and JP-A-2004-054803 disclose a field device and a plurality of field devices. Cited as technical literature related to systems interconnected via a network.
- FIG. 14 shows a configuration example of a conventional system in which a plurality of field devices such as sensors, endorsers, controllers, communication measuring instruments, measuring instruments, recording devices, and servers are connected to each other via a network. It is a block diagram.
- 1 is a high-order server
- 2, 3, 4, and 5 are controllers
- 6 is a sensor group that also includes a plurality of sensor forces.
- a plurality of sensors indicated by “SN01” in FIG. 14 are connected to the controller 2 via a network (not shown), and a plurality of sensors indicated by “SN02” in FIG. 14 are connected to the network (not shown). Connected to controller 3 via
- a plurality of sensors indicated by “SN03” in FIG. 14 are connected to the controller 4 via a network (not shown), and a plurality of sensors indicated by “SN04” in FIG. (Not shown) is connected to the controller 5.
- the controllers 2, 3, 4 and 5 are connected to the upper server 1 via a network (not shown).
- the operation of the sensor group 4 is controlled by the controllers 2, 3, 4 and 5, respectively, and the controllers 2, 3, 4 and 5 are centrally managed by the server 1, and the system as a whole, for example, a production system, etc. Configure To do.
- main business the new functions and problems of the user are solved for the function (hereinafter referred to as "main business") that is currently operated in the field devices such as controllers and servers.
- Function hereinafter referred to as “additional work”
- addition work add programs and parameters to the field devices such as controllers and servers to make the additional work the same as the main work. It will be executed in the execution environment.
- Figure 15 shows the main business (specifically, application program) that runs on field devices and the operating environment such as OS (Operating System) for executing the main business, communication functions, and hardware resources such as IZO. It is explanatory drawing which shows the relationship.
- the main business, execution environment, and software resources are functions unique to field devices, and are hereinafter referred to as “device-specific functions” as necessary.
- HW11 in FIG. 15 is a hardware resource
- OS11 in FIG. 15 is an execution environment
- ⁇ All in FIG. 15 is a main business
- AA11”, “AA12”, and “AA13” in FIG. Is an additional service (specifically, an application program).
- FIG. 16 is a block diagram showing another example of a system in which a plurality of conventional field devices are connected to each other via a network.
- 7 is a high-order server
- 8, 9, 10 and 11 are controllers
- 12 is a group of sensors composed of multiple sensor forces
- 13, 14 and 15 are application servers.
- a plurality of sensors indicated by “SN21” in FIG. 16 are connected to the controller 8 via a network (not shown), and a plurality of sensors indicated by “SN22” in FIG. 16 are connected by a network (not shown). No. ) To the controller 9 via a network (not shown), and a plurality of sensors indicated by “SN22” in FIG. 16 are connected by a network (not shown). No. ) To the controller 9 via a network (not shown), and a plurality of sensors indicated by “SN22” in FIG. 16 are connected by a network (not shown). No. ) To the controller 9 via
- a plurality of sensors indicated by “SN23” in FIG. 16 are connected to the controller 10 via a network (not shown), and a plurality of sensors indicated by “SN24” in FIG. Connected to the controller 11 via a link (not shown).
- the controllers 8, 9, 10 and 11 are connected to the upper server 7 via a network (not shown).
- the application servers 13, 14 and 15 are connected to each field device via a network (not shown).
- sensor group 12 is controlled by controllers 8, 9, 10 and 11, respectively, and controllers 8, 9, 10 and 11
- the server 7 is centrally managed by the server 7 and constitutes a system as a whole, for example, a production system.
- FIG. 17 is an explanatory diagram showing the relationship between the main business operating on the field device and the execution environment or nodeware resource for executing the main business.
- AS31 in FIG. 17 is an application server that provides a service for additional work
- FD31 in FIG. 17 is a field device that operates only the main business that receives the service for additional work.
- HW31 and HW32 are hardware resources of the application server and field device (specifically, communication means such as a network card).
- OS32 is the execution environment of the application server and field device (specifically, OS communication control function, etc.)
- MA11 is the main business of the field device in Fig. 17, and
- AA31 is operating on the application server in Fig. 17 This is an additional service.
- the additional server provided by the application server 13 is added to a plurality of sensors indicated by “SN21” in FIG. 16, and the application server 14 is provided to the server 7 and the controllers 8 and 9.
- An additional service is added, and the duplication indicated by “SN24” in FIG.
- each field device accesses the corresponding application server via the network (not shown) and performs additional services.
- the field device indicated by “FD31” in FIG. 17 is the device specific function (“OS32” and “HW32” in FIG. 17) of the application server indicated by “AS31” in FIG. Operate additional services shown in “AA31” in Fig. 17 using the device-specific functions of field devices ("OS 31" and “HW31” in Fig. 17) and perform communication shown in "CM31” in Fig. 17 To do.
- the application server performs additional work that requires data collection in an extremely short time, such as abnormality analysis processing.
- the CPU Central Processing Unit
- the main business of the field device such as the sensor may be affected. there were.
- An object of the present invention is to easily add a function (business) to a field device and to enable the added function (business) to operate independently of each other and a system using the same. Is to realize.
- the present invention provides a field device connected to a network
- a storage unit a communication unit that communicates via the network, and an arithmetic control that controls the entire field device by executing main work in an execution environment and also controls an operation mechanism that operates in the execution environment.
- the operation mechanism provides a field device that assigns a group identifier, a unique address space, and a unique name space to the activated additional business. This makes it possible for the additional services that are running to operate independently without interfering with each other. In addition, the impact on the main business due to the operation of additional business can be avoided.
- the operating mechanism is:
- the activated additional work is controlled. This makes it possible for the additional services that are running to operate independently without interfering with each other. In addition, the impact on the main business due to the operation of additional business can be avoided.
- the operating mechanism is:
- the operating mechanism is:
- the access destination in the device-specific function is specified, and the logical data to be written is converted into physical data based on the data conversion table. If the main business is accessing the identified access destination, the system waits until the access of the main business is completed, and writes the physical data converted to the identified access destination. For this reason, it is possible to avoid the impact on the main business due to the operation of the additional business.
- the device specific function is a
- the operating mechanism is:
- the group identifier of the other additional job is acquired, and the group identifier of the additional job to be started and the other additional.
- the operation request is transmitted to the other additional business, and the group identifier of the additional business that is started and / or activated is the same as the group identifier of the other additional business. If not, the operation request is not permitted. For this reason, independence between different group identifiers can be ensured.
- the execution environment is a
- the operating mechanism is Prioritize each group identifier. For this reason, priority control in units of virtual systems becomes possible.
- the operating mechanism is
- the operating mechanism is
- the operating mechanism is
- the operating mechanism is
- the group identifier of the additional job is acquired and accessed using an extended path name obtained by adding a group identifier to the path name. For this reason, if the group identifiers are different, the extended path names are completely different, so resources are not duplicated, and the independence between virtual systems (different group identifiers) is further improved.
- the operating mechanism is
- the user's access authority In response to a user operation request, the user's access authority is authenticated and the operation is performed. Determine whether the request is possible. For this reason, it becomes possible to block unauthorized operation requests from users who do not have access authority, and security is improved.
- the present invention provides a field system comprising a plurality of the field devices, wherein the plurality of field devices are connected to a network, and the same group identifier is assigned to the plurality of field devices. For this reason, it becomes possible for activated additional services to operate independently without interfering with each other. In addition, the impact on the main business due to the operation of additional business can be avoided.
- the field system includes:
- a system management server that collectively manages authentication information is provided on the network. This eliminates the need for complicated authentication information management in each field device. When changing authentication information, it is only necessary to change the authentication information of the system management server without changing the authentication information of each field device. .
- the operating mechanism assigns a group identifier when starting the additional work, and assigns a unique address space and a unique name space for each additional work. It is possible to operate independently without interfering with each other.
- the operation mechanism controls the address space to which the additional work is assigned, or does not directly communicate between the active additional works, resulting in the operation of the additional work. This avoids the impact on the main business.
- the main operation is preferentially accessed, resulting in the main operation due to the additional operation. Avoid the effects.
- the operation mechanism determines that the group identifier of the additional job being started and the group identifier of the other additional job are Independence between different group identifiers can be ensured by allowing operation requests only when they are the same.
- the operation mechanism sets priorities for each additional business, the activated additional business can operate independently without interfering with each other.
- the operation mechanism loads a new additional task, it prepares a different name space for each group identifier, and loads and executes the new additional task in the name space. For this reason, the use of a new additional task can be performed independently between group identifiers, so that the independence between virtual systems (different group identifiers) is further improved.
- the operation mechanism When the operation mechanism requests access to a path name with an additional job, it acquires the group identifier of the additional job and accesses it using the extended path name with the group identifier added to the path name. For this reason, if the group identifiers are different, the extended path names are completely different, so resources are not duplicated, and independence between virtual systems (different group identifiers) is further improved.
- the operation mechanism authenticates the access authority of the user in response to an operation request from the user, and determines whether or not the operation request can be made. For this reason, it is possible to block unauthorized operation requests from users who do not have access authority, and security is improved.
- the present invention provides a field system comprising a plurality of the field devices, wherein the plurality of field devices are connected to a network, and the same group identifier is assigned to the plurality of field devices.
- the field system also includes a system management server that collectively manages authentication information on the network. This eliminates the need for complicated authentication information management in each field device. Therefore, it is only necessary to change the authentication information of the system management server without changing the authentication information of each field device.
- FIG. 1 is a configuration block diagram showing an embodiment of a system using field devices according to the present invention.
- FIG. 2 is a configuration block diagram showing a specific example of each field device.
- FIG. 3 is an explanatory diagram showing the relationship between the main business operating on the field device, the execution environment and nodeware resources for executing the main business, the operation mechanism, and the additional business.
- FIG. 4 is a flowchart for explaining the operation of the operation mechanism.
- FIG. 5 is an explanatory diagram showing an example of a group identifier management table.
- FIG. 6 is a flowchart for explaining the operation of the operation mechanism.
- FIG. 7 is a flowchart for explaining the operation of the operation mechanism.
- FIG. 8 is a flowchart for explaining the operation of the operation mechanism.
- FIG. 9 is an explanatory diagram for explaining operations of other additional tasks.
- FIG. 10 is an explanatory diagram for explaining the operation of additional work for different field devices.
- FIG. 11 is an explanatory diagram for explaining a virtual system.
- FIG. 12 is a configuration block diagram showing another embodiment of the system for centrally managing authentication information.
- FIG. 13 is an explanatory diagram showing an example of authentication information managed by the system management server.
- FIG. 14 is a configuration block diagram showing an example of a system in which conventional field devices are connected to each other via a network.
- FIG. 15 is an explanatory diagram showing the relationship between the main business operating on the field device and the execution environment and nodeware resources for executing the main business.
- FIG. 16 is a block diagram showing another example of a system in which a plurality of conventional field devices are connected to each other via a network.
- FIG. 17 is an explanatory diagram showing the relationship between the main business operating on the field device and the execution environment and nodeware resources for executing the main business. Explanation of symbols [0057] 1, 7 servers
- FIG. 1 is a block diagram showing the configuration of an embodiment of a system using field devices according to the present invention.
- 16, 17, 18, 19 and 20 are field devices such as sensors, actuators, controllers, communication measuring instruments, measuring instruments, recording devices, and servers, and 100 is a network.
- Field devices 16, 17, 18, 19 and 20 are connected to each other via a network 100.
- FIG. 2 is a configuration block diagram showing a specific example of each field device.
- 21 is an arithmetic control unit such as a CPU that controls the entire field device
- 22 is an application program such as a main business.
- Storage unit such as hard disk, ROM (Read Only Memory), RAM (Random Access Memory), flash memory, etc. (electrically rewritable ROM), etc.
- 23 is a network card that communicates via a network Etc.
- the communication department. 21, 22, and 23 constitute a field device 50.
- the input / output of the storage unit 22 is connected to the arithmetic control unit 21, and the input / output of the communication unit 23 is also connected to the arithmetic control unit 21.
- the communication unit 23 is connected to a network (not shown).
- FIG. 3 shows the main business (specifically, application program) that runs on the field device, the execution environment such as the OS for executing the main business, the communication function, the hardware resources such as IZO, and the operation mechanism.
- FIGS. 4, 6, 7 and 8 are flowcharts explaining the operation of the operating mechanism
- FIG. 5 is the group identifier management table.
- FIG. 9 is an explanatory diagram for explaining the operation of another additional task
- FIG. 10 is an explanatory diagram for explaining the operation of the additional task for different field devices
- FIG. 11 is an explanatory diagram for explaining the virtual system. .
- “MA41” in FIG. 3 is the main business
- “HW41” in FIG. 3 is the hardware resource
- “OS41” is the execution environment in FIG. 3
- “OF41” in FIG. 3 is the operating mechanism
- "A A41”, “AA42” and “AA43” are additional tasks.
- the operation mechanism indicated by “OF41” in FIG. 3 is implemented in each field device and performs additional work as indicated by “AA41” in FIG. 3, etc.
- “OF41” in FIG. 3 The operating mechanism shown is the task and process as seen from the execution environment (for example, OS) shown in “OS41” in FIG. 3 that configures the device-specific functions of the field device 50 shown in “FD41” in FIG. Treated as an independent unit of execution.
- the operation mechanism indicated by “OF41” in FIG. 3 includes an execution function for executing an additional job, a main job in which the additional job operates on a field device, and an execution environment and hardware for executing the main job.
- Interface functions for using device-specific functions that are resource-rich, additional work management functions that control creation, startup, stop, and deletion of additional work as well as communication between additional work, and group management of additional work Each has a group management function!
- the operating mechanism (“OF41” in FIG. 3) determines whether or not the additional service (the generated additional service or the currently stopped additional service) is activated. If it is determined that an additional job is to be started, the operation mechanism ("OF41" in Fig. 3) starts in "S002" in Fig. 4 and starts in "S003" in Fig. 4 Assign a group identifier for each additional activity.
- the group identifier is an identifier used to manage a plurality of additional tasks based on the group identifier assigned to the additional tasks and to configure a virtual system described later.
- a group identifier list that describes additional tasks (specifically, additional task identifiers) that belong to the group identifier is managed by the operating mechanism ("OF 41" in Fig. 3). Has been.
- the group identifier list not only manages group identifiers corresponding to additional tasks within one field device, but also manages group identifiers corresponding to additional tasks for other related field devices. It doesn't matter.
- the group identifier list may be shared among a plurality of field devices constituting the system.
- the operation mechanism (“OF41” in FIG. 3) displays the group identifier to which the additional business identifier of the additional business started in “S002” in FIG. 4 belongs. Assigned to an additional job that was searched from the group identifier list and started.
- the operation mechanism (“OF41” in FIG. 3) is an address space specific to the activated additional service (for example, a memory space area that can be used by the additional service). ).
- the operation mechanism (“OF41” in FIG. 3) has a unique name space (for example, a variable name or a program name used by the additional task) for the activated additional task. It is a space that defines the name, and because the name space is different, it can be clearly distinguished even if it uses the same variable as other additional work.
- a unique name space for example, a variable name or a program name used by the additional task. It is a space that defines the name, and because the name space is different, it can be clearly distinguished even if it uses the same variable as other additional work.
- the operation mechanism (OF41" in Fig. 3) allocates a group identifier when starting an additional task and assigns a unique address space and name space for each additional task. Businesses can operate independently without interfering with each other.
- the operation mechanism (“OF41" in Fig. 3) does not directly operate the address space to which the additional work is assigned or does not perform communication between the activated additional works. By doing so, it is possible to avoid the impact on the main business due to the behavior of the additional business.
- the operation mechanism (“OF41” in FIG. 3) requests the data read of the device-specific function ("FD41” in FIG. 3) from the activated additional job. If it is determined that there is a read request, the operation mechanism (“OF41” in FIG. 3) in “S1 02” in FIG. Specify the access destination in "FD41").
- the operation mechanism (“OF41" in Fig. 3) is the physical data handled in the device-specific function ("FD41" in Fig. 3) and logical data handled in the supplementary service.
- the operation mechanism (“OF41” in Fig. 3) converts the access destination (logical data name) specified by the additional task into a physical data name based on the data conversion table.
- To identify the access destination (physical data name) in the device-specific function (“FD41" in Figure 3)
- the operation mechanism (“OF41” in FIG. 3) determines whether or not the main business is accessing the specified access destination. If it is determined that it is, it waits until the main business access is completed.
- the operation mechanism (“OF41” in FIG. 3) receives data (physical data) from the access destination (physical data name) in the device-specific function (“FD 41” in FIG. 3).
- the data is read and converted into logical data based on the data conversion table, and the data (logical data) converted in “S105” in FIG. 6 is transmitted to the additional work of the request source.
- the operating mechanism (“OF41” in FIG. 3) sends a request to write data possessed by the device-specific function (“FD41” in FIG. 3) from the additional operation being started. If it is determined that there is a write request, the operation mechanism (“OF41” in FIG. 3) in “S20 2” in FIG. 7 is the device-specific function (FIG. 3). The access destination in “FD41”) is specified, and the data to be written is converted to physical data based on the data conversion table.
- the operation mechanism (“OF41” in FIG. 3) uses the physical data name based on the data conversion table for the access destination (logical data name) specified by the additional task and the data to be written (logical data). And converted into physical data, specify the access destination (physical data name) in the device-specific function ("FD41" in Fig. 3), and generate converted data (physical data) to be written To do.
- the operation mechanism (“OF41” in FIG. 3) determines whether or not the main business is accessing the specified access destination. If it is determined that it is, it waits until the main business access is completed.
- the operation mechanism (OF41" in Fig. 3) gives priority to the main job when the additional job accesses data in the device-specific function ("FD4 1" in Fig. 3). By doing so, it is possible to avoid the impact on the main business due to the operation of the additional business.
- the operating mechanism determines whether or not there has been an operation request for another additional task, such as the additional task being activated.
- the operation request is the setting of operation parameters for other additional tasks, the creation, start, stop, and deletion of other additional tasks, the exchange of data with other additional tasks (with other additional tasks and Communication between the two).
- the operation mechanism (“OF41” in FIG. 3) adds the operation request destination in “S 304” in FIG. Send an operation request to the business.
- an operation request is transmitted to the additional operation request destination (“AA53” in FIG. 9) as indicated by “SQ52” in FIG.
- the operation mechanism (OF41" in Fig. 3) indicates the group identifier of the additional job of the operation request source and the operation request. Independence between different group identifiers can be ensured by permitting an operation request only when the group identifier of the previous additional task is the same identifier.
- the linkage of multiple additional tasks managed by the same group identifier can be handled as an independent virtual system from the linkage of multiple additional tasks managed by other group identifiers. Because there is no interference between virtual systems.
- the operation mechanism is handled as one independent execution unit such as a task or a process in view of the execution environment (for example, OS) that constitutes the device-specific function. It is described that. In other words, the main business and the operating mechanism are independent of each other.
- operation mechanism (“OF41” in FIG. 3) performs priority control for each group identifier of the additional task to be operated, so that the virtual system described above is performed.
- additional work usually belongs to one group identifier (virtual system).
- group identifier virtual system
- additional work that provides a common function it belongs to two or more group identifiers (two or more virtual systems). It doesn't matter.
- the additional task has a plurality of group identifiers, and an operation request can be made with another additional task belonging to each virtual system.
- additional services that provide a common function include a data compression function, a data encoding function, a mail transmission function for alarm notification, or a force / force that causes a data value to exceed a threshold value.
- a monitoring function can be considered.
- a file ("directory A file” with additional work (group identifier: 2)
- the operating mechanism (OF41" in Figure 3) obtains the group identifier of the additional task and passes the path name ( ⁇ A ⁇ A Access the file using the extended path name ( ⁇ 2 ⁇ A ⁇ A. file) with the group identifier added to .file).
- a "device-specific functions, operation mechanisms, and additional business groups (specifically, additional business groups with group identifiers 1, 2, and 3, respectively).
- FD62”, “OF62”, “AA64”, “AA65” and “AA66” in FIG. 10 are the device-specific functions, operation mechanisms and additional business groups of “Field Device B” (specifically, Group identifiers are 1, 2, and 3 additional business groups, respectively).
- the two “field device A” and “field device B” share the group identifier! /, So in “AA61” and “AA64” in FIG. 10 belonging to the group identifier “1”.
- the additional work shown constitutes one virtual system.
- SN71”, “SN72”, and “SN73” in Fig. 11 are the main tasks in each sensor that is a field device, and "CT71” and “CT72” in Fig. 11 are in each controller that is a field device.
- Main service, "SV71” in Fig. 11 is the main service in the server that is a field device.
- ellipses connected by the broken lines (vertical lines) in Fig. 11 are additional tasks added to each field device, and the additional tasks with the same group identifier are the operation requests indicated by the thick solid line. Are associated with each other.
- GP71”, “GP72”, and “GP73” in FIG. 11 are virtual systems that are divided independently from each other by different group identifiers, and are assigned to each virtual system (the same group identifier). The additional work that operates on each field device belongs according to the group identifier list.
- GP71 in Fig. 11 is a virtual system to which additional work necessary for the energy monitoring system in the production system belongs
- GP72 in Fig. 11 is a sensor integrated security system in the production system.
- Virtual system to which required additional tasks belong Figure 11
- Figure 11 Medium
- GP73 is a virtual system to which additional work necessary for the priority monitoring system of specific equipment in the production system belongs.
- the configuration shown in FIG. 11 does not cause interference between virtual systems as described above.
- the virtual work to which the additional work necessary for the energy monitoring system shown in FIG. The user who operates the system is completely independent of the other virtual system (sensor integrated security system or specific device priority monitoring system) without considering any operation, non-operation, and operation status. (Energy monitoring system) can be used.
- the operation mechanism when the additional task force also receives an operation request for another additional task, the operation mechanism (“OF41" in Fig. 3) It is explained that the operation request is permitted only when the group identifier of the additional business of the same and the group identifier of the additional business of the operation request destination are the same identifier.
- the operation mechanism (“OF41” in FIG. 3) may authenticate the access authority of the user and determine whether or not the operation request is possible.
- the operation mechanism of each field device must perform user authentication.
- authentication information such as a user name, password, operation target, and operation authority may be used. It has to be managed individually and becomes complicated.
- FIG. 12 is a configuration block diagram showing another embodiment of a system for centrally managing such authentication information.
- Fig. 12,! 16, 16, 18, 19, 20, and 100 are assigned the same reference numerals as in Fig. 1, and 24 is a system management server that collectively manages authentication information.
- the field devices 16, 17, 18, 19 and 20 are connected to each other via the network 100, and the system management server 24 is also connected to the network 100.
- FIG. 13 is an explanatory diagram showing an example of authentication information managed by the system management server 24.
- the authentication information managed by the system management server 24 includes a user identifier, a user name, and a password, and the operation target group identifier and the operation authority permitted for the user identifier. It is also described.
- the user is in a virtual system configured with an additional task belonging to the group identifier "1". All the operations of creating, starting, stopping, and deleting additional services to be configured are permitted.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Multi Processors (AREA)
- Stored Programmes (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
- Programmable Controllers (AREA)
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/791,187 US8321493B2 (en) | 2004-11-17 | 2005-10-04 | Field device and system employing the same |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004333277A JP4622474B2 (ja) | 2004-11-17 | 2004-11-17 | フィールド機器及びこれを用いたシステム |
JP2004-333277 | 2004-11-17 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006054401A1 true WO2006054401A1 (ja) | 2006-05-26 |
Family
ID=36406947
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/018355 WO2006054401A1 (ja) | 2004-11-17 | 2005-10-04 | フィールド機器及びこれを用いたシステム |
Country Status (4)
Country | Link |
---|---|
US (1) | US8321493B2 (ja) |
JP (1) | JP4622474B2 (ja) |
CN (1) | CN100524230C (ja) |
WO (1) | WO2006054401A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007142268A1 (ja) * | 2006-06-07 | 2007-12-13 | Yokogawa Electric Corporation | アプリケーションプログラム間で連携動作を行うシステム及びフィールド機器 |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009003625A (ja) * | 2007-06-20 | 2009-01-08 | Yokogawa Electric Corp | フィールド機器 |
US9667591B2 (en) * | 2015-05-22 | 2017-05-30 | Conversant, Inc. | System and method for maintaining coherence of assocation across a network address change or reassignment |
DE102016120306A1 (de) * | 2016-10-25 | 2018-04-26 | Endress + Hauser Wetzer Gmbh + Co Kg | Verfahren und System zum Aktivieren zumindest einer Bedien-/Parametrierfunktion eines Feldgerätes der Automatisierungstechnik |
JP6840099B2 (ja) | 2018-02-19 | 2021-03-10 | 日本電信電話株式会社 | サービス提供システム、資源割り当て方法、及び資源割り当てプログラム |
US11169855B2 (en) * | 2019-12-03 | 2021-11-09 | Sap Se | Resource allocation using application-generated notifications |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06231022A (ja) * | 1992-12-31 | 1994-08-19 | American Teleph & Telegr Co <Att> | コンピュータシステムに用いる名前スペースの一部分を別の名前スペースの一部分として利用可能にするための装置及びその方法 |
JP2001051716A (ja) * | 1999-08-12 | 2001-02-23 | Toshiba Corp | 監視制御システム |
JP2003058408A (ja) * | 2001-08-13 | 2003-02-28 | Hitachi Ltd | 情報処理システム |
Family Cites Families (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2594979B2 (ja) * | 1987-10-23 | 1997-03-26 | 株式会社日立製作所 | マルチプロセツサシステム |
JPH05189389A (ja) * | 1992-01-10 | 1993-07-30 | Sony Corp | 階層構造をなす大規模分散計算機システムの接続方法 |
JP3165765B2 (ja) * | 1993-09-20 | 2001-05-14 | 富士通株式会社 | Cad設計支援装置 |
US5487170A (en) * | 1993-12-16 | 1996-01-23 | International Business Machines Corporation | Data processing system having dynamic priority task scheduling capabilities |
US5940612A (en) * | 1995-09-27 | 1999-08-17 | International Business Machines Corporation | System and method for queuing of tasks in a multiprocessing system |
US6424872B1 (en) * | 1996-08-23 | 2002-07-23 | Fieldbus Foundation | Block oriented control system |
US7146230B2 (en) * | 1996-08-23 | 2006-12-05 | Fieldbus Foundation | Integrated fieldbus data server architecture |
US6044305A (en) * | 1996-10-04 | 2000-03-28 | Fisher Controls International, Inc. | Method and apparatus for debugging and tuning a process control network having distributed control functions |
US6047222A (en) * | 1996-10-04 | 2000-04-04 | Fisher Controls International, Inc. | Process control network with redundant field devices and buses |
JP3444159B2 (ja) | 1996-11-29 | 2003-09-08 | 松下電工株式会社 | ビル管理システム |
JPH11119808A (ja) * | 1997-10-17 | 1999-04-30 | Yokogawa Electric Corp | フィールドバスを用いたプラント制御システム |
FI114745B (fi) * | 1998-06-01 | 2004-12-15 | Metso Automation Oy | Kenttälaitteiden hallintajärjestelmä |
FI108678B (fi) * | 1998-06-17 | 2002-02-28 | Neles Controls Oy | Kenttälaitteiden hallintajärjestelmä |
US6788980B1 (en) * | 1999-06-11 | 2004-09-07 | Invensys Systems, Inc. | Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network |
US7342897B1 (en) * | 1999-08-07 | 2008-03-11 | Cisco Technology, Inc. | Network verification tool |
US6687257B1 (en) * | 1999-08-12 | 2004-02-03 | Rockwell Automation Technologies, Inc. | Distributed real-time operating system providing dynamic guaranteed mixed priority scheduling for communications and processing |
US6618745B2 (en) * | 1999-09-10 | 2003-09-09 | Fisher Rosemount Systems, Inc. | Linking device in a process control system that allows the formation of a control loop having function blocks in a controller and in field devices |
US6850973B1 (en) * | 1999-09-29 | 2005-02-01 | Fisher-Rosemount Systems, Inc. | Downloadable code in a distributed process control system |
US6687698B1 (en) * | 1999-10-18 | 2004-02-03 | Fisher Rosemount Systems, Inc. | Accessing and updating a configuration database from distributed physical locations within a process control system |
JP2001125797A (ja) * | 1999-10-25 | 2001-05-11 | Seiko Epson Corp | マルチタスクシステム及びそのプログラムを記録した記録媒体並びに加工装置 |
US7356580B1 (en) * | 2000-03-30 | 2008-04-08 | Lam Research Corporation | Plug and play sensor integration for a process module |
US7143153B1 (en) * | 2000-11-09 | 2006-11-28 | Ciena Corporation | Internal network device dynamic health monitoring |
US7565651B1 (en) * | 2000-05-25 | 2009-07-21 | Oracle International Corporation | Parallel task scheduling system for computers |
US7028299B1 (en) * | 2000-06-30 | 2006-04-11 | Intel Corporation | Task-based multiprocessing system |
IT1319716B1 (it) * | 2000-12-28 | 2003-11-03 | Abb Ricerca Spa | Sistema computerizzato per effettuare operazioni di configurazione ediagnostica remota su un dispositivo di campo |
JP2002244755A (ja) * | 2001-02-16 | 2002-08-30 | Sony Corp | データ処理方法、半導体回路およびプログラム |
US7039917B2 (en) * | 2001-03-20 | 2006-05-02 | Hewlett-Packard Development Company, L.P. | Method and system for executing tools in a service control manager module |
US6574561B2 (en) * | 2001-03-30 | 2003-06-03 | The University Of North Florida | Emergency management system |
US7093244B2 (en) * | 2001-04-18 | 2006-08-15 | Domosys Corporation | Method of remotely upgrading firmware in field-deployed devices |
JP2002318702A (ja) | 2001-04-19 | 2002-10-31 | Mitsubishi Electric Corp | 車載情報システム |
US7302686B2 (en) * | 2001-07-04 | 2007-11-27 | Sony Corporation | Task management system |
US20030014529A1 (en) * | 2001-07-12 | 2003-01-16 | Simpson Shell Sterling | Mediated access to production device options in a distributed environment |
EP1288757A1 (de) * | 2001-08-07 | 2003-03-05 | Siemens Aktiengesellschaft | Verfahren und Prozessleitsystem zum Betrieb einer technischen Anlage |
US20070088518A1 (en) * | 2001-12-27 | 2007-04-19 | Michael Braun | Automated method for generating program modules, to be used for controlling field devices, from a machine-readable parameterized specification of the field devices |
JP2003202929A (ja) * | 2002-01-08 | 2003-07-18 | Ntt Docomo Inc | 配信方法および配信システム |
JP4374832B2 (ja) | 2002-07-24 | 2009-12-02 | 日本電気株式会社 | 監視サーバ装置、ネットワーク監視システム及びそれらに用いる機能変更方法並びにそのプログラム |
JP4015898B2 (ja) * | 2002-07-26 | 2007-11-28 | 松下電器産業株式会社 | プログラム実行装置 |
JP2004078936A (ja) * | 2002-07-31 | 2004-03-11 | Matsushita Electric Ind Co Ltd | 情報処理端末及び情報処理方法 |
JP3974498B2 (ja) * | 2002-10-30 | 2007-09-12 | 株式会社山武 | フィールド機器 |
DE10313389A1 (de) * | 2003-03-25 | 2004-10-07 | Endress + Hauser Process Solutions Ag | Verfahren zur Übertragung von Softwarecode von einer Steuereinheit zu einem Feldgerät der Prozessautomatisierungstechnik |
US7600234B2 (en) * | 2002-12-10 | 2009-10-06 | Fisher-Rosemount Systems, Inc. | Method for launching applications |
JP4140384B2 (ja) * | 2003-01-07 | 2008-08-27 | ソニー株式会社 | 端末装置および方法、記録媒体、並びにプログラム |
JP3891490B2 (ja) * | 2003-01-10 | 2007-03-14 | 株式会社日立製作所 | 無線ネットワークを利用した通信方法 |
US7246194B2 (en) * | 2003-01-30 | 2007-07-17 | Rosemount, Inc. | Interface module for use with a fieldbus device network and with internet and non-internet based process control networks |
JP2004318940A (ja) * | 2003-04-14 | 2004-11-11 | Renesas Technology Corp | 記憶装置 |
US7640543B2 (en) * | 2004-06-30 | 2009-12-29 | Intel Corporation | Memory isolation and virtualization among virtual machines |
US8046770B2 (en) * | 2004-10-25 | 2011-10-25 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for managing productivity |
US7317952B2 (en) * | 2005-04-07 | 2008-01-08 | Honeywell International Inc. | Managing field devices having different device description specifications in a process control system |
US7676604B2 (en) * | 2005-11-22 | 2010-03-09 | Intel Corporation | Task context direct indexing in a protocol engine |
US8032340B2 (en) * | 2007-01-04 | 2011-10-04 | Fisher-Rosemount Systems, Inc. | Method and system for modeling a process variable in a process plant |
-
2004
- 2004-11-17 JP JP2004333277A patent/JP4622474B2/ja not_active Expired - Fee Related
-
2005
- 2005-10-04 CN CNB2005800394498A patent/CN100524230C/zh not_active Expired - Fee Related
- 2005-10-04 WO PCT/JP2005/018355 patent/WO2006054401A1/ja active Application Filing
- 2005-10-04 US US11/791,187 patent/US8321493B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06231022A (ja) * | 1992-12-31 | 1994-08-19 | American Teleph & Telegr Co <Att> | コンピュータシステムに用いる名前スペースの一部分を別の名前スペースの一部分として利用可能にするための装置及びその方法 |
JP2001051716A (ja) * | 1999-08-12 | 2001-02-23 | Toshiba Corp | 監視制御システム |
JP2003058408A (ja) * | 2001-08-13 | 2003-02-28 | Hitachi Ltd | 情報処理システム |
Non-Patent Citations (2)
Title |
---|
BARKAI D.: "Technologies for Sharing and Collaborating on the Net.", PEER-TO-PEER COMPUTING. IEEE., August 2001 (2001-08-01), pages 13 - 28, XP010583969 * |
FERREIRA P ET AL: "Distribution and Peristence in Multiple and Heterogeneous Address Spaces.", ONJECT ORIENTATION IN OPERATING SYSTEMS., December 1993 (1993-12-01), pages 83 - 93, XP010097266 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007142268A1 (ja) * | 2006-06-07 | 2007-12-13 | Yokogawa Electric Corporation | アプリケーションプログラム間で連携動作を行うシステム及びフィールド機器 |
JP2007328480A (ja) * | 2006-06-07 | 2007-12-20 | Yokogawa Electric Corp | アプリケーションプログラム間で連携動作を行うシステム |
Also Published As
Publication number | Publication date |
---|---|
CN101061461A (zh) | 2007-10-24 |
US20070282939A1 (en) | 2007-12-06 |
CN100524230C (zh) | 2009-08-05 |
US8321493B2 (en) | 2012-11-27 |
JP2006146420A (ja) | 2006-06-08 |
JP4622474B2 (ja) | 2011-02-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109067828B (zh) | 基于Kubernetes和OpenStack容器云平台多集群构建方法、介质、设备 | |
JP7085565B2 (ja) | 分離されたネットワークスタックにわたるインテリジェントなスレッド管理 | |
JP5340610B2 (ja) | 複数の構成要素を管理するためのコンピュータ・システム、並びにその方法及びコンピュータ・プログラム | |
US20120203870A1 (en) | Concurrent Web Based Multi-Task Support For Control Management System | |
US20080065850A1 (en) | Data storage system and control method thereof | |
JP2007310901A (ja) | コンピュータシステム | |
US8639775B2 (en) | Computer system and its management method | |
WO2006054401A1 (ja) | フィールド機器及びこれを用いたシステム | |
KR101535792B1 (ko) | 운영체제 구성 장치 및 방법 | |
US20210312271A1 (en) | Edge ai accelerator service | |
Fazio et al. | Managing volunteer resources in the cloud | |
KR102206847B1 (ko) | 하이브리드 보안 시스템 및 통합보안방법 | |
US20230077424A1 (en) | Controlling access to resources during transition to a secure storage system | |
CN101415009A (zh) | 一种通信系统中多用户权限的管理方法和系统 | |
CN110765471A (zh) | 一种基于微控制器的访问权能嵌入式平台及其工作方法 | |
TWI811730B (zh) | 用於限制組合式系統中資料可存取性之方法、系統及電腦可讀取媒體 | |
JP5035129B2 (ja) | アクセス制御プログラム | |
JP6244496B2 (ja) | サーバストレージシステムの管理システム及び管理方法 | |
TWI793420B (zh) | Scada網路hmi系統 | |
WO2007125700A1 (ja) | アクセス制御方法、アクセス制御方法を用いた機器及びシステム | |
JP7282113B2 (ja) | ユーザのリソースへのアクセスを制御するシステム及び方法 | |
WO2018008124A1 (ja) | 計算機、計算機システム及びセキュリティの制御方法 | |
US20230315892A1 (en) | Information processing system and information processing method | |
CN115037800B (zh) | 基于微隔离的生物信息学容器的构建系统及构建方法 | |
US20240028691A1 (en) | Capability-restricted system control |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 11791187 Country of ref document: US Ref document number: 200580039449.8 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 11791187 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 05790246 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: JP |