WO2012111129A1 - Dispositif de connexion de base de données - Google Patents

Dispositif de connexion de base de données Download PDF

Info

Publication number
WO2012111129A1
WO2012111129A1 PCT/JP2011/053387 JP2011053387W WO2012111129A1 WO 2012111129 A1 WO2012111129 A1 WO 2012111129A1 JP 2011053387 W JP2011053387 W JP 2011053387W WO 2012111129 A1 WO2012111129 A1 WO 2012111129A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
information
file
unit
information device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2011/053387
Other languages
English (en)
Japanese (ja)
Inventor
直史 恵木
寛 芦谷
直道 野末
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Electric Corp
Original Assignee
Mitsubishi Electric Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitsubishi Electric Corp filed Critical Mitsubishi Electric Corp
Priority to PCT/JP2011/053387 priority Critical patent/WO2012111129A1/fr
Publication of WO2012111129A1 publication Critical patent/WO2012111129A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • the present invention relates to a database connection device that connects an information device and a database that manages various data.
  • the registering device has a function of using a database language. Need to be.
  • An object of the present invention is to obtain a database connection device that allows a database to be accessed even if the device does not have a function using a database language.
  • the present invention is connected to a database management unit that executes database management, and an information device that has a function of transmitting a file by specifying a destination in a directory description.
  • a file transfer function unit for receiving a transmission file from the information device, and when the file transfer function unit receives the transmission file from the information device, registration of the database from a directory description of a specified destination The destination management information is acquired, and the database management unit registers the transmission file in the database based on the registration destination information acquired by the file transfer function unit.
  • the database connection device has an effect that the database can be accessed even by a device that does not have a function of using a database language.
  • FIG. 1 is a diagram illustrating a configuration example of a database connection device according to an embodiment of this invention.
  • FIG. 2 is a diagram for explaining an example of the structure of data registered in the database.
  • FIG. 3 is a diagram illustrating an example of an FTP command issued by the information device when a file is transmitted.
  • FIG. 4 is a diagram illustrating an example of an FTP command issued by the information device when a file is transmitted.
  • FIG. 5 is a flowchart for explaining the operation of the database connection apparatus according to the embodiment of the present invention when setting a setting file in an information device.
  • FIG. 6 is a flowchart for explaining the operation of the database connection device according to the embodiment of this invention when an FTP command is received from an information device.
  • FIG. 7 is a diagram illustrating a specific example of the data structure of the table.
  • FIG. 1 is a diagram illustrating a configuration example of a database connection device according to an embodiment of this invention.
  • the database connection device 10 is connected to one or more (here, two) information devices 20, a database 30, and a registration destination storage device 40.
  • the database 30 is a database that manages data related to the FA system, which is constructed using a storage device in a server device (not shown).
  • FIG. 2 is a diagram for explaining an example of the structure of data registered in the database 30.
  • a plurality of tables 31 are registered in the database 30, and each registered table 31 can be specified by a table name.
  • Each table 31 includes a plurality of fields, and each field can be specified by a field name.
  • identification information for specifying a record registered in the own table 31 is registered.
  • Table 1 includes Fields 11 to 15, and Field 11 is registered with an identification number for identifying each record registered in Table 1.
  • an identification number for identifying each record may be referred to as a record name.
  • a file (described later) output from the information device 20 can be registered in the database 30.
  • the file output from the information device 20 is registered in the Field 13 of Table1.
  • “file is registered” means that a file from the information device 20 is stored in a server device that implements the database 30, and information that specifies a storage location of the file in the server device is registered in the database 30. To be done.
  • a file name is registered in the database 30 as information for specifying a storage position.
  • the information device 20 is an element constituting the FA system, and corresponds to a control device such as a vision camera or a programmable controller (PLC) or a display device such as a programmable display.
  • the information device 20 is mounted with a file transfer protocol (FTP) and has both an FTP server function and an FTP client function.
  • FTP file transfer protocol
  • the information device 20 transmits a file to the database connection device 10 as an FTP server.
  • the type of file that can be transmitted to the database connection device 10 is not particularly limited. For example, if the information device 20 is a vision camera, the captured image data can be used as a transmission target file.
  • FIG. 3 is a diagram illustrating an example of an FTP command issued by the information device 20 when a file is transmitted.
  • the file transfer destination directory path is originally described after the file transmission command “STOR”, but here, the transfer destination field may be specified using the path description method. it can. That is, as the transfer destination, a directory name that is originally described for constructing a path, such as “/ registration destination table name / registration destination field name / registration destination record name / transfer file name”, is stored in the database 30. It is described by replacing it with information for specifying the registration destination.
  • the hatched portion in the database 30 of FIG. 2 that is, the table name of the transfer destination is “Table1”, the field name is “Field13”, the record name is “7”, and the transfer target The file name is “Binary.bin”.
  • the file transmission timing, the file name, and the registration destination in the database 30 by the information device 20 are set by, for example, a setting file described later.
  • the information device 20 replaces the unknown information with a predetermined provisional name and transmits the information. For example, when the record name is missing from the registration destination information shown in FIG. 3, as shown in FIG. 4, a predetermined provisional name “ TMP "is output.
  • the information device 20 receives the setting file of the own information device 20 sent from the database connection device 10 as an FTP client, and updates the setting file held by the own information device 20 with the received setting file.
  • the setting file is, for example, a vision camera that has a function of outputting an image captured by the information device 20 or analyzing the captured image to extract and output a shape feature. This corresponds to a setting file for setting various conditions and image data analysis conditions. If the information device 20 is a PLC, a setting file such as a project file is applicable. Further, when the information device 20 is a programmable display device, drawing data (procedure manual) indicating a procedure to be displayed on the screen corresponds to the setting file.
  • the registration destination storage device 40 is referred to from the database connection device 10 when the registration destination information related to the file transmitted by the information device 20 is replaced with a temporary name, and is used instead of the temporary name. It is a device that gives information to the database connection device 10. Note that the method by which the registration destination storage device 40 calculates alternative information is not particularly limited in the present embodiment. Alternatively, serial numbers may be sequentially generated and output each time an inquiry is received.
  • the database connection device 10 registers the file transmitted from the information device 20 in the database 30. Further, the setting data registered in the database 30 is read, and the read setting data is transmitted to the information device 20.
  • the database connection device 10 includes a file transfer function unit 11, a storage unit 12, a database registration unit 13, a database registration destination complementing unit 14, a communication unit 15, and a database reading unit 16. Yes.
  • the storage unit 12 functions as a buffer for data transfer from the information device 20 to the database 30.
  • the storage unit 12 holds the latest setting file set in the information device 20. It is assumed that the setting file is held in the storage unit 12 in a state where it is possible to identify which information device 20 is set. For example, the address of the information device 20 as the FTP server is associated and held.
  • the file transfer function unit 11 is a communication interface for executing file transfer with the information device 20, and has both an FTP server function and an FTP client function. Specifically, the file transfer function unit 11 receives a file transmitted from the information device 20 as an FTP client, and stores the received file in the storage unit 12. Here, the file transfer function unit 11 extracts the registration destination information described in the STOR command from the STOR command, and associates the extracted registration destination information with the file transmitted by the command. 12. Further, the file transfer function unit 11 transmits the setting file stored in the storage unit 12 and targeted for transmission to the information device 20 to the information device 20 as an FTP server.
  • the database registration unit 13 and the database reading unit 16 cooperate to manage the database 30.
  • the user when changing the setting file of the information device 20, the user operates the server device to register a new setting file in the database 30.
  • the database reading unit 16 acquires a new setting file registered in the database 30 using the database language, and stores the acquired new file in the storage unit 12.
  • the setting file stored in the storage unit 12 is transferred to the target information device 20 by the file transfer function unit 11.
  • the database registration unit 13 registers the file in the database 30 based on the registration destination information stored in association with the file received from the information device 20 and stored in the storage unit 12.
  • the database registration unit 13 inquires the database registration destination complementing unit 14 and uses the temporary name. Acquire information of the registration destination with the replaced unknown part being replaced.
  • the database registration unit 13 sets the setting file stored in the storage unit 12 in a field in which the setting file in the record that is the same as or corresponds to the record of the registration destination of the file received from the information device 20 is registered. Register.
  • the communication unit 15 is a communication interface for the database connection device 10 to communicate with the registration destination storage device 40.
  • the database registration destination complementing unit 14 transfers the inquiry to the registration destination storage device 40 via the communication unit 15 and is replaced with a temporary name from the registration destination storage device 40. Information that is replaced with information (that is, information that was unknown) is received via the communication unit 15. The database registration destination complementing unit 14 transfers the received information to the database registration unit 13.
  • FIG. 5 is a flowchart for explaining the operation of the database connection device 10 when setting the setting file in the information device 20.
  • the database reading unit 16 acquires the setting file of the information device 20 from the database 30 (step S1), and stores the acquired setting file in the storage unit 12 (step S2).
  • the transmission destination address of the setting file is registered in advance in the database 30 in association with the setting file, read together with the setting file, and stored in the storage unit 12 in association with the read setting file. You may make it.
  • the file transfer function unit 11 transmits the setting file stored in the storage unit 12 to the setting destination information device 20 (step S3), and the operation of setting the setting file in the information device 20 ends.
  • the user can change the setup of the process executed in the FA system only by registering the setting file in the database 30. Can do.
  • FIG. 6 is a flowchart for explaining the operation of the database connection device 10 when an FTP command is received from the information device 20.
  • the file transfer function unit 11 determines whether or not the received FTP command is a STOR command (step S12). If the received command is not a STOR command (No at Step S12), the file transfer function unit 11 executes an operation according to the received FTP command (Step S13), and ends the operation when receiving the FTP command.
  • the file transfer function unit 11 uses the STOR command to register the table name, field name, record, and file name of the registration target file in the database 30. Is acquired (step S14). Then, the file transfer function unit 11 stores the registration target file and the acquired registration destination information in the storage unit 12 (step S15).
  • the database registration unit 13 reads the registration destination information stored in the storage unit 12 and determines whether or not the read registration destination information includes a part replaced with a provisional name (step). S16). If there is a part replaced with the provisional name in the registration destination information (step S16, Yes), the database registration unit 13 inquires the database registration destination complementing unit 14 to supplement the registration destination information (step). S17). Specifically, the database registration unit 13 notifies the database registration destination complementing unit 14 of registration destination information and makes an inquiry. Upon receiving the inquiry, the database registration destination supplementing unit 14 sends the inquiry via the communication unit 15. To the registration destination storage device 40.
  • the registration destination storage device 40 Upon receipt of the inquiry, the registration destination storage device 40 generates information that replaces the part replaced with the provisional name, and transmits the generated information to the database registration destination complementing unit 14.
  • the part replaced with the provisional name in the registration destination information is replaced with the information received from the registration destination storage device 40.
  • Information of the registration destination in which the portion replaced with the provisional name is replaced with information generated by the registration destination storage device 40 is transmitted to the database registration unit 13.
  • the database registration unit 13 stores the setting file for the transmission source information device 20 in the storage unit 12 is determined (step S18).
  • the database registration unit 13 performs the corresponding registration in the database 30 based on the registration destination information stored in the storage unit 12 or the complemented registration destination information.
  • the setting file and the file from the information device 20 are registered (step S19).
  • the database registration unit 13 stores the registration destination information stored in the storage unit 12 or the complemented registration destination. Based on the information, the file from the information device 20 is registered at the corresponding registration destination in the database 30 (step S20). After the process of step S19 or step S20, the operation when receiving the FTP command is terminated.
  • the database registration unit 13 may register information indicating the storage location of the corresponding setting file in the server device in the database 30 instead of registering the setting file body in the database 30. .
  • the file name is used as the information indicating the storage position, the setting file name is registered.
  • FIG. 7 is a diagram showing a more specific example of the data structure of the table 31 provided in the database 30 created by the above operation.
  • the FA system is a system for manufacturing a product, and a serial number (No.) for individually identifying each manufactured product is assigned.
  • the table 31 includes “product serial number”, “part A lot number”, “image file”, “temperature”, “pressure”, “procedure document identification number (ID)”, and “vision”. It has a field in which “camera setting file” is registered.
  • “Product serial number (No.)” is a serial number assigned to the product and also functions as a record name.
  • Part A lot number is the lot number of part A constituting the product.
  • “Temperature” and “pressure” are manufacturing parameters for each product. Information generated in the manufacturing process, such as “product serial number (No.)”, “part A lot No.”, “temperature”, and “pressure”, can be acquired from a device memory included in the PLC. Since the database connection device 10 or the like already registers a device memory value in the database 30, there is a known method, and therefore, no particular mention is made here.
  • “Procedure ID” is identification information of drawing data as setting data of the programmable display device as the information device 20, and corresponds to a file name associated with the storage position of the drawing data stored in the server device. To do. That is, the drawing data can be registered in the table 31 by registering the “procedure manual ID”.
  • the “vision camera setting file” a setting file of a vision camera as the information device 20 is registered.
  • the table 31 can be configured in this manner, the user can manage not only the manufacturing parameters for each product but also the image file and control device setting data for each product in the database, thereby improving traceability. Can be improved.
  • the communication method between the information device 20 and the database connection device 10 has been described as complying with FTP, but the communication method is configured to comply with HTTP (HyperText Transfer Protocol). May be.
  • HTTP HyperText Transfer Protocol
  • the database 30 and the database connection device 10 may be realized by a single device. Further, the registration destination storage device 40 may be provided in the database connection device 10.
  • the database registration unit 13 as a database management unit for managing the database 30 and the function of transmitting a file by designating a transmission destination by a directory description are provided.
  • a file transfer function unit 11 connected to the information device 20 and receiving a transmission file from the information device 20.
  • the file transfer function unit 11 receives the transmission file from the information device 20, the file transfer function unit 11
  • the database registration unit information is acquired from the directory description, and the database registration unit 13 is configured to register the transmission file in the database 30 based on the registration destination information acquired by the file transfer function unit 11. Even if the information device 20 does not have the function to be used, the database language is used. It is possible to be able to access the database only by simple configuration without implementing the functions. Accordingly, various information devices 20 can be connected.
  • the database 30 holds setting data that defines the operation of the information device 20, the database reading unit 16 as a database management unit acquires setting data held by the database 30, and the file transfer function unit 11 stores the database Since the setting data acquired by the reading unit 16 is transmitted to the target information device 20, the setting file such as the vision camera setting file, the PLC project file, and the work procedure manual displayed on the programmable display is updated. The burden on the user for the work to be performed can be reduced, and as a result, the management cost of the FA system can be reduced.
  • the database reading unit 16 further includes a storage unit 12 that stores the setting data acquired by the database reading unit 16.
  • the file transfer function unit 11 receives transmission data from the information device 20, the database reading unit 16 transmits the transmission data.
  • the setting data related to the information device 20 is stored in the storage unit 12
  • the setting data stored in the storage unit 12 is registered in the database 30 in association with the transmission data. Because it is possible to link manufacturing process information such as serial data generated in the manufacturing process, physical data such as temperature and voltage, and setting files on the FA system side such as vision cameras and PLCs, settings on the FA system side It is possible to track the history including the contents.
  • an information complementing unit database registration destination complementing unit 14, communication unit 15, registration destination
  • database registration destination complementing unit 14, communication unit 15, registration destination that generates information replacing the unknown part and supplements the unknown part. Since the storage device 40) is further provided, even when the information device 20 does not output an accurate registration destination, registration in the database 30 can be performed without outputting an error.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Pour pouvoir accéder à une base de données (30) même lorsqu'un dispositif d'informations (20) ne comporte pas de fonction permettant d'utiliser un langage de bases de données, un dispositif de connexion de base de données (10) comprend : une unité d'enregistrement de base de données (13) qui fait office d'unité de gestion de base de données destinée à gérer la base de données (30) ; et une unité de fonction de transfert de fichier (11) qui est connectée au dispositif d'informations (20) doté d'une fonction permettant d'utiliser une description de répertoire de façon à indiquer une destination de transmission afin de transmettre un fichier, et qui reçoit le fichier transmis par le dispositif d'informations (20). Quand le fichier transmis est reçu en provenance du dispositif d'informations (20), l'unité de fonction de transfert de fichier (11) obtient les informations de destination d'enregistrement de base de données provenant de la description de répertoire de la destination de transmission indiquée. L'unité d'enregistrement de base de données (13) enregistre le fichier transmis dans la base de données (30) sur la base des informations de destination d'enregistrement obtenues par l'unité de fonction de transfert de fichier (11).
PCT/JP2011/053387 2011-02-17 2011-02-17 Dispositif de connexion de base de données Ceased WO2012111129A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2011/053387 WO2012111129A1 (fr) 2011-02-17 2011-02-17 Dispositif de connexion de base de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2011/053387 WO2012111129A1 (fr) 2011-02-17 2011-02-17 Dispositif de connexion de base de données

Publications (1)

Publication Number Publication Date
WO2012111129A1 true WO2012111129A1 (fr) 2012-08-23

Family

ID=46672091

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/053387 Ceased WO2012111129A1 (fr) 2011-02-17 2011-02-17 Dispositif de connexion de base de données

Country Status (1)

Country Link
WO (1) WO2012111129A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10247155A (ja) * 1997-01-31 1998-09-14 Informix Software Inc データベースへのファイルシステムインタフェース
JPH11284682A (ja) * 1998-03-31 1999-10-15 Fuji Photo Film Co Ltd 画像転送システム
JP2003527659A (ja) * 1999-08-05 2003-09-16 オラクル コーポレーション インターネットファイルシステム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10247155A (ja) * 1997-01-31 1998-09-14 Informix Software Inc データベースへのファイルシステムインタフェース
JPH11284682A (ja) * 1998-03-31 1999-10-15 Fuji Photo Film Co Ltd 画像転送システム
JP2003527659A (ja) * 1999-08-05 2003-09-16 オラクル コーポレーション インターネットファイルシステム

Similar Documents

Publication Publication Date Title
US10009410B2 (en) Description files and web service protocols for tasking capability on internet of things
US8010555B2 (en) System and method for managing images over a network
JP5788934B2 (ja) クラウドコンピューティングベースのデータ共有システム及び方法
US9754002B2 (en) Method and system for providing a synchronization service
US10754869B2 (en) Managing data format of data received from devices in an internet of things network
US9692794B2 (en) Aggregation of sensor appliances using device registers and wiring brokers
JP7028117B2 (ja) 情報処理システム、情報処理装置、情報処理方法及びプログラム
WO2013063950A1 (fr) Procédé et système de vérification en rapport avec un dispositif de communication multimode
CN103248695A (zh) 文件下载方法、系统及cdn中的服务器节点
CN110187907A (zh) 飞行器的固件升级方法、装置、系统和存储介质
JP4591875B2 (ja) 中継サーバ及び中継通信システム
CN102394909B (zh) 远程会诊业务处理方法和系统
KR20170028218A (ko) 동적 모드버스 프로토콜 매핑을 지원하는 통신 장치
KR20150116344A (ko) 사물 인터넷 브로커링 방법 및 장치
JP2009277111A (ja) 情報処理装置
WO2016074412A1 (fr) Procédé d'administration de compatibilité basé sur un protocole de configuration de réseau, support de stockage et dispositif
CN110661850A (zh) 一种边缘计算方法、系统、计算机设备和存储介质
JPWO2020136787A1 (ja) データ処理装置、データ処理システム、データ処理方法及びプログラム
CN114390044A (zh) 一种文件上传方法、系统、设备及存储介质
CN102571935A (zh) 一种数据传输的方法、客户端、服务器和系统
WO2024198818A1 (fr) Procédé et système de configuration de dispositif, et dispositif et support d'enregistrement
CN106202296B (zh) 网页的局部更新方法及系统
JP2006235831A (ja) 状態管理装置および方法およびプログラム
US20190042812A1 (en) Location based situation awareness system and method thereof
KR101698184B1 (ko) 홈 네트워크 가상화 장치 및 그 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11858962

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11858962

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP