CN110908955B

CN110908955B - Management system of IO device description file

Info

Publication number: CN110908955B
Application number: CN201911120692.2A
Authority: CN
Inventors: 吴国进; 顾洁洁; 周松
Original assignee: Hefei Ansheng Intelligent Electronics Co ltd
Current assignee: Hefei Ansheng Intelligent Electronics Co ltd
Priority date: 2019-11-15
Filing date: 2019-11-15
Publication date: 2023-02-03
Anticipated expiration: 2039-11-15
Also published as: CN110908955A

Abstract

The invention discloses a management system of an IO device description file, which comprises: the registration login module is used for realizing registration and login of professional users and common users; the file generation module is used for providing a creation interface of the IO equipment description file through the browser after the professional user successfully logs in, and generating the IO equipment description file according to editing information input by the professional user through the creation interface; and the issuing module is used for issuing the IO equipment description file to the IO equipment description file resource library by a professional user with issuing authority after the IO equipment description file is generated. The management system uses the B/S framework based on the Internet, a user can access and use the B/S framework through a browser, software does not need to be installed, the management system can be practical for free, the generated IO equipment description file can be published, and the inquiry and the downloading of the user are facilitated.

Description

Management system of IO device description file

Technical Field

The invention relates to the technical field of internet, in particular to a management system of an IO device description file.

Background

The IO Device Description (IO Device Description) file is a Description file of an IO-Link Device (such as a sensor and an actuator), and is created by an IO-Link Device manufacturer and used for describing the IO-Link Device to realize a corresponding function. The IODD file includes a main file (e.g., xml format), a plurality of language files, and a picture file. Each IO-Link device needs an IODD file, which can be understood as the instruction book of the device.

Because of the complexity and the specialty of the IODD file, the prior IODD file generator is of a single machine version and can be used only by paying. The IODD file generator can only be used by one user, data can not be shared, a temporary storage function is not provided, the user needs to edit all the data at one time, one IODD file usually has thousands of lines, the user needs to spend a long time, and the use is inconvenient; meanwhile, data is stored in a personal computer of a user, and the risk of loss due to damage of the personal computer exists.

Disclosure of Invention

The present invention is directed to solving, at least to some extent, one of the technical problems in the related art. Therefore, an object of the present invention is to provide a management system for IO device description files, so as to facilitate users to manage IO device description files.

In order to achieve the above object, the present invention provides a management system for IO device description files, where users of the management system include professional users and ordinary users, and the management system includes: the system comprises a registration login module, a server and a display module, wherein the registration login module is used for providing a registration interface and a login interface for a user through a browser, storing registration information input by the user through the registration interface to the server, and sending the login information input by the user through the login interface to the server so that the server judges whether the user successfully logs in, wherein the registration information comprises a user type, and the user type comprises the professional user and the ordinary user; the file generation module is used for providing an interface containing a file creation option for a user through a browser when the user logs in successfully and is a professional user, switching the interface containing the file creation option into a creation interface of an IO device description file according to the creation request after the user inputs a creation request through the file creation option, receiving editing information input by the user through the creation interface, and generating the IO device description file according to the editing information, wherein the creation interface displays a creation type option and editing items corresponding to the creation type, and the creation type comprises new creation, new copy creation and import; and the release module is used for judging whether the user has a release authority after the IO device description file is generated, and providing a release interface for the user through a browser if the user has the release authority so that the user can release the IO device description file to an IO device description file repository through the release interface.

According to the management system of the IO device description file, a B/S (Browser/Server) framework is used based on the Internet, a user can access and use the IO device description file through a Browser without installing software, the IO device description file can be used freely, the generated IO device description file can be issued, and the IO device description file is convenient for the user to inquire and download.

In addition, the management system of the IO device description file according to the embodiment of the present invention may further have the following additional technical features;

according to an embodiment of the present invention, the users of the management system further include general users, and the management system further includes: and the query downloading module is used for providing a query downloading interface of the IO device description file for the user through a browser when the user logs in successfully and the user is a common user or the user is a common user so that the user can query and/or download the required IO device description file, wherein the query downloading interface displays the IO device description file queried by the user from the IO device description file resource library and downloading options corresponding to the IO device description files, and when the user is the common user, the query downloading interface also displays collection options corresponding to the IO device description files.

According to an embodiment of the present invention, the query downloading module is further configured to: and when a query instruction input by the user through the query downloading interface is received, or IO equipment access is detected, displaying the queried IO equipment description file to the user through the query downloading interface, wherein the query instruction comprises one or more of a keyword, a manufacturer name, a product name and an equipment ID.

According to an embodiment of the present invention, when the user type is a professional user, the corresponding registration information further includes a user name, a password, a mailbox, a verification code, a vendor name, a business license, and an application letter.

According to an embodiment of the invention, the management system further comprises: and the statistical analysis module is used for counting one or more of the download quantity of each IO device description file, the download quantity of all IO device description files released by each manufacturer, the quantity of all released IO device description files, the quantity of all IO devices and the quantity of manufacturers of all released IO device description files in the IO device description file resource library.

According to an embodiment of the invention, the statistical analysis module is further configured to: and providing the counted download amount of each IO device description file to a user corresponding to a manufacturer who issues the IO device description file, and providing the download amount of all the IO device description files issued by each manufacturer to the user corresponding to the manufacturer.

According to an embodiment of the invention, the management system further comprises: and the storage module is used for storing the IO device description file in the editing stage and the generated IO device description file to a server, and regularly performing full backup and incremental backup by using the server.

According to an embodiment of the present invention, the editing item includes basic information, a device function, a user interface, a communication link, and a text set, so that the professional user sequentially performs editing steps of the basic information, the device function, the user interface, the communication link, and the text set, wherein the file generating module is further configured to: and verifying the format, the length and the range of the data input by the user, displaying first error prompt information on the creation interface when the verification is failed, logically checking the data input in each editing step after each editing step is completed, and displaying second error prompt information on the creation interface when the checking is abnormal.

According to an embodiment of the present invention, the file generation module is further configured to: after an IO device description file is generated, a preset checking tool is called from the server to check the IO device description file, third error prompt information is displayed on the creation interface when an error occurs in the checking, and the IO device description file is set to be in a pre-release state when no error occurs in the checking, so that the user can check the IO device description file in the pre-release state.

According to an embodiment of the present invention, the professional users include professional management users and professional sub-users, and the registration login module is further configured to: and when the user logs in successfully and is a professional management user, providing a professional sub-user creation interface for the user so as to facilitate the user to create a professional sub-user, wherein the professional sub-user creation interface displays permission setting information so as to facilitate the user to set the permission of the professional sub-user to be created.

Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.

Drawings

Fig. 1 is a block diagram showing a configuration of an IO device description file management system according to a first embodiment of the present invention;

FIG. 2 is a flowchart of the operation of an IO device description management system according to an example of the present invention;

FIG. 3 is a block diagram of an IO device description management system according to an exemplary embodiment of the present invention;

FIG. 4 is a block diagram illustrating a management system for IO device description files according to a second embodiment of the present invention;

fig. 5 is a block diagram showing a configuration of an IO device description file management system according to a third embodiment of the present invention;

fig. 6 is a block diagram of a management system of an IO device description file according to a fourth embodiment of the present invention.

Detailed Description

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative and intended to explain the present invention and should not be construed as limiting the present invention.

The following describes a management system of an IO device description file according to an embodiment of the present invention with reference to the drawings.

Fig. 1 is a block diagram of a management system of an IO device description file according to a first embodiment of the present invention.

In the embodiment of the present invention, the users of the management system include professional users and general users, and optionally, the users of the management system may also include general users.

As shown in fig. 1, the management system includes: a registration login module 110, a file generation module 120, and a publication module 130.

In this embodiment, the registration login module 110 is configured to provide a registration interface and a login interface for a user through a browser, store registration information input by the user through the registration interface to a server, and send login information input by the user through the login interface to the server, so that the server determines whether the user has successfully logged in, where the registration information includes a user type, and the user type includes a professional user and a general user.

Wherein, professional users, namely equipment manufacturers register, and can be used for creating and releasing IODD files; the ordinary user, namely the user using the IODD file, can provide the functions of collecting, inquiring and downloading the IODD file; the ordinary users, i.e. users who do not need to register an account number, can directly inquire and download the IODD file. When the user type is a professional user, the registration information may further include a user name, a password, a mailbox, a verification code, a manufacturer name, a business license, an application letter, and the like.

As an example, the professional users include a professional management user and professional sub-users, and the registration login module 110 is further configured to provide a professional sub-user creation interface to the user when the user login is successful and the user is a professional management user, so that the user creates the professional sub-users, wherein the professional sub-user creation interface displays permission setting information so that the user sets permissions of the professional sub-users to be created.

Specifically, both the professional management user and the professional sub-user may have the authority to create the IODD file by default, and the professional management user may have the authority to issue the IODD file by default and may set whether the professional sub-user has the authority to issue the IODD file. After the professional management user successfully logs in, the user can input a professional sub-user creation instruction through a management interface of the professional management user, and at this time, the registration login module 110 can provide a professional sub-user creation interface for the professional management user. The user can input the user name (such as a mobile phone number, a mailbox and the like) and the password of the professional sub-user through the interface, and set whether the professional sub-user is granted the authority to issue the IODD file.

It should be noted that, the sharing of the factory-owned IODD file can be realized among professional users of the same manufacturer. Moreover, each professional user can only edit the IODD file created by the user, and cannot modify the IODD files of other professional users.

In a specific example, as shown in fig. 2, the registration step of the professional management user is: the user name, the password, the mailbox, the verification code, the selected manufacturer, the uploading of the business license and the uploading of the application official letter are filled in the registration interface, the information is submitted to the platform after being filled in, the registration login module 110 sends the information to a platform manager to remind the manufacturer of registering, the platform manager timely verifies the registration information, and the account is opened for the manufacturer after the verification is correct. The account is an administrator account (professional management user) of a manufacturer, the manufacturer can create a sub-account (professional sub-user) through the account, the sub-account has an IODD file creation authority as a default, and the issuing authority needs to be set independently through the administrator account. Only one administrator account can be registered by one manufacturer, a plurality of sub-accounts can be created, and the number is not limited. When the account number binds to the mailbox or the mobile phone number, the registration login module 110 sends the verification code to the mailbox or the mobile phone, and the binding can be successful only if the verification code is correct. The selected manufacturer information during registration comes from the registered members of the IO-Link association, and the system periodically and automatically synchronizes the member information from the IO-Link website.

Further, after the professional user is checked, the system can be logged in through a user name (or a mailbox) and a password, and the file generation module 120 is triggered to start. If the account number is not approved or is not the manufacturer account number, the file generation module 120 cannot be entered to create the IODD file.

Certainly, when a common user registers, only the user name, the password, the mailbox and the verification code need to be filled in the registration interface, and then the system can be logged in through the user name (or the mailbox) and the password when logging in; the general user does not need to register and can directly access the management system, for example, the login option of the general user can be set on a login interface, and the access can be realized.

In this embodiment, the file generating module 120 is configured to, when the user logs in successfully and the user is a professional user, provide an interface including a file creation option to the user through a browser, after the user inputs a creation request through the file creation option, switch the interface including the file creation option into a creation interface of an IO device description file according to the creation request, receive edit information input by the user through the creation interface, and generate the IO device description file according to the edit information, where the creation interface displays an edit item corresponding to a creation type option and a creation type, and the creation type includes a new addition, a new copy addition, and an import.

Wherein, newly adding, namely creating an empty IODD file, and is suitable for the IODD file of a new product. Newly-added copy, namely, an IODD file is created by taking the issued IODD file as a template, all information in the original file is copied, the method is suitable for upgrading the IODD file of a product or a product with similar functions, and the method can be completed only by modifying part of the file content. The import is to import an IODD file into the system for editing, which may be an xml file of a main IODD or a complete zip file, and is suitable for IODD files that were not generated by the system before.

As an example, the editing item includes basic information, device functions, a user interface, a communication connection, and a text collection, so that a professional user sequentially performs editing steps of the basic information, the device functions, the user interface, the communication connection, and the text collection.

In this example, the file generation module 120 is further configured to verify the format, length, and range of the data input by the user, and when the verification fails, display a first error prompt message on the creation interface, and after each editing step is completed, perform a logical check on the data input in the editing step, and when an abnormality occurs in the check, display a second error prompt message on the creation interface.

Specifically, editing an IODD file is mainly divided into: basic information, equipment functions, a user interface, communication connection and a text set are 5 editing steps, and since the former step is the premise of the latter step, the editing is carried out according to the step sequence. Each editing step may further comprise a plurality of sub-steps, for example, the device function editing step may comprise: editing data set, standard variable, variable set, process data, error type set and event set. The form can check the data format, length and range during editing, and prompt a user through the first error prompt information during error checking so as to facilitate the user to modify. When the one-step editing is completed and the next step is performed, the file generation module 120 also performs a logical check to ensure the accuracy of the data edited in the previous step. Optionally, the background may also perform data check to ensure correctness and integrity of the data, and if there is an error, a detailed error log may be prompted to prompt the user to modify the error log.

As an example, the file generating module 120 is further configured to, after the IO device description file is generated, call a preset checking tool from the server to check the IO device description file, and when an error occurs in the check, display a third error prompt message on the creation interface, and when it is detected that no error occurs, set the IO device description file in a pre-release state, so that the user checks the IO device description file in the pre-release state.

Specifically, after all the information is edited, an IODD file can be generated, and the name and release date of the IODD file are filled in to generate the IODD file. The file generating module 120 may call a Checker tool stored in the server and provided by the IO-Link association to check, store a checked log, and if there is an error in the check, the user may check the log, search for the cause of the error by referring to the generated IODD file, and modify the log. After modification, the IODD file needs to be regenerated and the Checker tool needs to be called again to check until all errors are modified. After there is no error, the IODD file may be set to a pre-release state, for example, the generated IODD file is displayed in a "generated" option box and may be arranged by file type (e.g., main file, language file, picture file) for user inspection.

For example, after the IODD file is generated, a checker tool may be automatically called to detect the IODD file, or a "check" button may be displayed on the creation interface, and a user may call the checker tool through the button to detect the IODD file. The checker tool is placed on the server, the call may be a check request sent by the client to the server, and the server executes the check operation after receiving the request.

In this embodiment, the publishing module 130 is configured to determine whether the user has a publishing right after the IO device description file is generated, and if the user has the publishing right, provide a publishing interface to the user through a browser, so that the user can publish the IO device description file to the IO device description file repository through the publishing interface.

Specifically, as shown in fig. 2 and 3, the IODD file enters a pre-release state after being generated, and after a professional user with a release authority logs in the management system, the IODD file in the pre-release state can be checked, and after the file information is confirmed to be correct, the IODD file can be released to the IODD resource library. It should be noted that the publishing operation is not reversible, so that the user is required to verify the publication without error. The published IODD file can be queried and downloaded by ordinary users or general users. Meanwhile, the professional user can also inquire the IODD file which is just released in the IODD file which is released. Alternatively, for professional sub-users without publishing rights, the publishing module 130 may provide an interface containing a rights request option through which a user may input a rights request, which may be sent to a corresponding professional management user, who may grant publishing rights to professional sub-users without publishing rights through the request.

Therefore, the management system of the IO device description file uses a B/S (Browser/Server) framework based on the Internet, a user can access and use the system through a Browser, and the user does not need to install software; the system supports multiple users, provides an administrator account, can create sub-accounts through the administrator account, is unlimited in number, supports data sharing, and can be used freely; the generated IO device description file can be issued, and the required user can conveniently inquire and download. Meanwhile, the creation and the release of the IO device description file are integrated in a management system, so that the use of a user is facilitated.

In a second embodiment of the present invention, as shown in fig. 4, the management system further includes an inquiry downloading module 140, where the inquiry downloading module 140 is configured to provide an inquiry downloading interface of the IO device description file to the user through a browser when the user logs in successfully and the user is a normal user, or when the user is a normal user, so that the user can inquire and/or download the required IO device description file, where the inquiry downloading interface displays the IO device description file inquired by the user from the IO device description file repository and downloading options corresponding to the IO device description files, and the inquiry downloading interface also displays collection options corresponding to the IO device description files when the user is a normal user.

Further, the query downloading module 140 is further configured to display the queried IO device description file to the user through the query downloading interface when a query instruction input by the user through the query downloading interface is received or when the IO device access is detected, where the query instruction includes one or more of a keyword, a manufacturer name, a product name, and a device ID.

Specifically, referring to fig. 2, an IODD file issued by a professional user with an issue right enters an IODD repository, all files in the IODD repository are public, and a general user or a general user can query and download the files. The user can register an account number and download the IODD file after logging in, or directly download the IODD file without registering the account number. The user who registers the account number can add the commonly used IODD file to the favorite, and the favorite is convenient to continue to use next time.

Referring to fig. 3, the manner of querying and downloading the IODD file may include: 1) In a webpage access mode, the query and download module 140 provides an IODD file retrieval function, and a common user or a general user can query the IODD file through keywords, a manufacturer name, a product name, an equipment ID and the like, and can query file details and download the IODD file; 2) An API (Application Programming Interface) Interface mode, which is suitable for IO-Link equipment or software manufacturers, is integrated in the equipment or software of the IO-Link equipment or software manufacturers, and calls the API Interface through platform distribution keys to search and download the IODD file. When the user uses the equipment or software, the user does not need to manually import the IODD file, only a networking program is needed to automatically call the API interface to download the corresponding IODD file from the IODD resource library, the user can use the equipment more conveniently, for example, a computer is connected to the Internet and is connected with the equipment, the corresponding IODD file can be determined according to two parameters of the vendorId and the deviceId in the equipment by reading the two parameters, the IODD file can be found from the IODD file resource library and can be directly downloaded, and the process is automatically operated by the program and does not need user operation.

Therefore, the creation, the release and the inquiry downloading of the description file of the IO device are integrated in a management system, so that the use of a user is more convenient, and the user can know the description file of the latest version of the IO device in time so as to update and perfect the function of the IO device.

In a third embodiment of the present invention, as shown in fig. 5, the management system further includes a statistical analysis module 150, where the statistical analysis module 150 is configured to count one or more of a download amount of each IO device description file, a download amount of all IO device description files issued by each manufacturer, a number of all issued IO device description files, a number of all IO devices, and a number of manufacturers of all issued IO device description files in the IO device description file repository.

Specifically, referring to fig. 2, the statistical analysis module 150 may collect data of the retrieval browsing situation, the downloading situation, and the like of the IODD file, and may perform statistics according to indexes such as a user area, a device type, and a file downloading amount. When a user retrieves and downloads IODD files, the system records related logs and counts the downloading amount of a certain IODD file, the downloading amount of all IODD files of a manufacturer, the downloading amount of all IODD files, the number of manufacturers of all published IODD files, the number of all published IODD files and the number of all devices, wherein the downloading amount of a certain IODD file and the downloading amount of all IODD files of a manufacturer are used for the manufacturer to check the manufacturer and cannot check other manufacturers.

Further, the statistical analysis module 150 is further configured to provide the statistical download amount of each IO device description file to a user corresponding to a manufacturer that issues the IO device description file, and provide the download amounts of all IO device description files issued by each manufacturer to the user corresponding to the manufacturer.

In a fourth embodiment of the present invention, as shown in fig. 5, the management system further includes a storage module 160. The storage module 160 is configured to store the IO device description file in the editing stage and the generated IO device description file to a server, and periodically perform full backup and incremental backup by using the server.

Specifically, the IODD file created by the professional user may be temporarily stored, the storage module 160 may record the current editing position, and the storage module may directly enter the current editing position for continuous editing when logging in next time, which is convenient to use. The data is stored on the server 170, and a complete backup strategy is provided to ensure data security, so that data loss caused by weak personal security awareness is avoided.

Optionally, the storage module 160 may further perform mirroring on the saved IO device description file by using a server, and when receiving the restoration request, restore the saved data to the restoration time in the restoration request.

As an example, the management system for the IO device description file may further include a language switching module, which may switch languages of the interfaces, such as chinese to english, german, korean, and the like, so as to meet usage requirements of more national users.

To sum up, the management system of the IO device description file in the embodiment of the present invention adopts a B/S architecture, a user does not need to install software, the system can be accessed through a browser, the program version is updated at a server, and the user does not need any operation; the system supports multiple users, provides an administrator account, can create sub-accounts through the administrator account, is unlimited in number, and supports data sharing; can be used for free; temporary data storage is supported, the system is quitted, and the next time the data is continuously edited; the form provides a real-time data checking function, and errors are prompted in time, so that the problem that the errors are prompted after all data are edited, and the time is wasted due to the fact that the errors cannot be saved is avoided; the system interface supports Chinese and English switching, and meets the use requirements of domestic and foreign users; the system data is stored in the cloud server, a complete backup strategy is provided, and data safety is guaranteed; the IODD generator and the resource library are integrated, and the IODD generator can be released to the resource library after being edited, so that the use is smoother.

In addition, the management system of the IO device description file according to the embodiment of the present invention, in which the file generation and management modes are used, may also be applied to the GSD file generation and management of Profinet and Profibus protocols, and the EDS file of EtherNet/IP and DeviceNet, and the ESI file of EtherCAT.

In the description of the specification, reference to the description of "one embodiment," "some embodiments," "an example," "a specific example," or "some examples" or the like means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.

In the present invention, unless otherwise expressly stated or limited, the first feature "on" or "under" the second feature may be directly contacting the first and second features or indirectly contacting the first and second features through an intermediate. Also, a first feature "on," "above," and "over" a second feature may be directly on or obliquely above the second feature, or simply mean that the first feature is at a higher level than the second feature. A first feature being "under," "below," and "beneath" a second feature may be directly under or obliquely under the first feature, or may simply mean that the first feature is at a lesser elevation than the second feature.

Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.

Claims

1. A management system for IO device description files, wherein users of the management system include professional users and ordinary users, and the management system comprises:

the system comprises a registration login module, a server and a display module, wherein the registration login module is used for providing a registration interface and a login interface for a user through a browser, storing registration information input by the user through the registration interface to the server, and sending the login information input by the user through the login interface to the server so that the server judges whether the user successfully logs in, wherein the registration information comprises a user type, and the user type comprises the professional user and the ordinary user;

the file generation module is used for providing an interface containing a file creation option for a user through a browser when the user logs in successfully and is a professional user, switching the interface containing the file creation option into a creation interface of an IO device description file according to the creation request after the user inputs a creation request through the file creation option, receiving editing information input by the user through the creation interface, and generating the IO device description file according to the editing information, wherein the creation interface displays a creation type option and editing items corresponding to the creation type, and the creation type comprises new creation, new copy creation and import;

the publishing module is used for judging whether the user has a publishing authority after the IO device description file is generated, and if the user has the publishing authority, providing a publishing interface for the user through a browser so that the user can publish the IO device description file to an IO device description file resource library through the publishing interface; wherein

The editing item comprises basic information, an equipment function, a user interface, a communication connection and a text set, so that the professional user can edit the basic information, the equipment function, the user interface, the communication connection and the text set in sequence, wherein the file generating module is further used for: the method comprises the steps of verifying the format, the length and the range of data input by a user, displaying first error prompt information on a creation interface when the verification is failed, logically checking the data input in the editing step after each editing step is completed, displaying second error prompt information on the creation interface when the checking is abnormal, calling a preset checking tool from a server to check an IO device description file after the IO device description file is generated, displaying third error prompt information on the creation interface when an error occurs in the checking, and setting the IO device description file to be in a pre-release state when the error does not occur in the checking so that the user can check the IO device description file in the pre-release state.

2. The management system of IO device description file according to claim 1, wherein the users of the management system further include general users, the management system further includes:

and the query downloading module is used for providing a query downloading interface of the IO device description file for the user through a browser when the user logs in successfully and the user is a common user or the user is a common user so that the user can query and/or download the required IO device description file, wherein the query downloading interface displays the IO device description file queried by the user from the IO device description file resource library and downloading options corresponding to the IO device description files, and when the user is the common user, the query downloading interface also displays collection options corresponding to the IO device description files.

3. The IO device description file management system of claim 2, wherein the query download module is further configured to:

and when a query instruction input by the user through the query downloading interface is received, or IO equipment access is detected, displaying the queried IO equipment description file to the user through the query downloading interface, wherein the query instruction comprises one or more of a keyword, a manufacturer name, a product name and an equipment ID.

4. The system for managing an IO device description file of claim 1, wherein when the user type is a professional user, the corresponding registration information further includes a user name, a password, a mailbox, a verification code, a vendor name, a license and an application letter.

5. The management system of IO device description files of claim 4, wherein the management system further comprises:

and the statistical analysis module is used for counting one or more of the download quantity of each IO device description file, the download quantity of all IO device description files released by each manufacturer, the quantity of all released IO device description files, the quantity of all IO devices and the quantity of manufacturers of all released IO device description files in the IO device description file resource library.

6. The management system of IO device description files of claim 5, wherein the statistical analysis module is further configured to:

and providing the counted download amount of each IO device description file to a user corresponding to a manufacturer issuing the IO device description file, and providing the download amount of all IO device description files issued by each manufacturer to the user corresponding to the manufacturer.

7. The management system of IO device description files of claim 1, wherein the management system further comprises:

and the storage module is used for storing the IO device description file in the editing stage and the generated IO device description file to a server and periodically performing full backup and incremental backup by using the server.

8. The system for managing IO device description files of claim 1, wherein the professional users include professional management users and professional sub-users, and the login module is further configured to:

and when the user successfully logs in and is a professional management user, providing a professional sub-user creation interface for the user so that the user can create professional sub-users, wherein the professional sub-user creation interface displays authority setting information so that the user can set the authority of the professional sub-users to be created.