KR20080011744A - Remote maintenance system based on xml - Google Patents

Abstract

An XML(eXtensible Markup Language)-based remote maintenance system is provided to offer an electronic manual service and a remote maintenance service in a remote place based on an XML document by using a database server designed for storing non- RDBMS(Relational DataBase Management System) type XML data. A database server(100) manages electronic manual information, maintenance target information, and troubleshooting information for target equipment(500) by storing the information to a database(100A) in an XML document form. A remote maintenance server(200) provides the remote maintenance service for the maintenance target equipment by linking with the database server. A web server(300) provides a web service for searching, providing, and editing an XML document through the Internet. A monitor(400) monitors a state of the target equipment controlled by a user computer(600) and transmits the monitored state to the remote maintenance server. The database server includes a maintenance unit managing user information, a security manager managing a security state of whole system, a collection manager managing a collection structure of the database, and a log manager managing operation state information of the database server.

Description

XM-based remote maintenance system {REMOTE MAINTENANCE SYSTEM BASED ON XML}

1 is a configuration diagram of the XM-based remote maintenance system of the present invention,

2 is a diagram illustrating a database 100A having the above-described hierarchy structure.

3 is a block diagram of a database server 100 performing a function as described above,

4 is a view showing an interface screen for managing the database server 100,

5 is a view showing the configuration of the remote maintenance server 200 of FIG.

6 to 8 are diagrams illustrating an example of an interface screen of each of the XML editor, the schema editor, and the XLST editor configured in the electronic manual authoring unit 210. Referring to FIG. ,

9 is a system configuration diagram having a database 100A implemented as an RDBMS and an XMLDBMS to interoperate with a web server according to an embodiment of the present invention.

10 is a view showing a user interface screen of the web server 300 configured as described above,

11 is a view showing an interface screen for a group management function,

12 is a diagram illustrating an interface screen for registering a user among user management functions.

13 is a diagram illustrating an interface screen for an electronic manual management function.

14 and 15 are views showing an interface screen for the electronic manual viewing function,

16 and 17 illustrate interface screens for an electronic manual search function.

18 is a diagram showing an interface screen for registration among electronic manual management functions.

19 is a view showing an interface screen for modification / deletion among electronic manual management functions.

20 is a view showing an interface screen for authorization / authorization recovery among electronic manual management functions.

FIG. 21 is a diagram illustrating an interface screen for content registration in an electronic manual management function.

FIG. 22 is a diagram illustrating an interface screen for moving content among electronic manual management functions.

FIG. 23 is a diagram illustrating an interface screen for deleting contents of an electronic manual management function.

24 is a diagram illustrating an interface screen for arranging contents among electronic manual management functions.

FIG. 25 is a diagram illustrating an interface screen for title type modification of content modification of an electronic manual management function. FIG.

FIG. 26 is a diagram illustrating an interface screen for body type modification of content modification of an electronic manual management function. FIG.

FIG. 27 is a diagram illustrating an interface screen for correcting an image type during content modification of an electronic manual management function. FIG.

FIG. 28 is a diagram illustrating an interface screen for multimedia modification during content modification of an electronic manual management function.

Description of the main symbols in the drawings

100: database server 100A: database (DB)

110: user management unit 120: security management unit

130: collection manager

131: parser unit 132: Xpath engine unit

133: Xupdate engine unit

134: Universal Business Languae (UBL) processor unit

135: index manager

136: schema manager

137: XML object manager

140: log manager

200: remote maintenance server

210: electronic manual authoring unit 220: version control unit

230: file conversion unit 240: monitoring unit

250: remote support

300: web server

400: monitoring device 500: equipment

600: user computer 700: A / S server

The present invention relates to a remote maintenance providing system for a remote device, and more particularly to an X-Mell-based remote maintenance system that can provide electronic manual and diagnosis information on the online.

With the development of electronic commerce, an operating system such as ERP and a remote support system have been established to provide all additional services online.

This ERP or remote support system is applied mainly in B2B, and it establishes the standard of electronic document so that service such as logistics support system, maintenance technical manual, and automobile maintenance manual can be provided online in real time. . Among these, automobile-related services are being introduced by Hyundai, Kia, Samsung, and Ssangyong.

However, in the case of the prior art as described above, the electronic manual has a large number of system-oriented one-way information providing methods irrelevant to the technical expression of the manual in PDF and HTML manners. Mainly as a large and expensive problem. Therefore, ERP as a management innovation tool is also applied very limited mainly to large companies with capital power, and there is a problem that it is difficult to apply a wide range of applications including small and medium companies.

Due to these problems, ERP or remote support systems are currently becoming a trend based on XML documents. The global market for ERP or remote support systems based on XML documents is expected to be $ 700 million in 2004. The introduction of ERP or remote support system based on XML document in Korea was introduced in 1999 by the Ministry of Public Administration and Home Affairs by selecting the XML as an electronic document standard in case of watering. I applied XML to.

As mentioned above, 70% of the total XML demand is concentrated in government and public institutions, but it is expected that the demand for electronic commerce will increase greatly. Specifically, 80% of applications communicating over public networks use XML format, and 75% of new B2B projects are expected to use XML Messaging. Therefore, there is an urgent need for providing a remote maintenance management system based on XML document data management for e-business.

Accordingly, the present invention is to solve the above-described problems of the prior art, a database designed to store the XML data of the non-RDBMS method XML unnecessary OR mapping process when using the XML data (XML) (XML) Equipped with a server, basically Xpath query language, using the DOM and SAX API, XML (XML) data processing using the XDBC API, XML (XML) Its purpose is to provide an XML-based remote maintenance system that provides electronic manual services and remote maintenance services based on XML documents by enabling accurate control during data processing. It is done.

XM-based remote maintenance system of the present invention for achieving the above object, the database of the electronic manual information, maintenance target equipment information, troubleshooting information (troubleshooting) information on the maintenance target equipment database (XML) Database server (DB server) to store and manage in; A remote maintenance server for providing a remote maintenance service for the equipment in association with the database server; A web server providing a web service for searching, providing data, and editing the XML document through the Internet; And a monitoring device mounted on the maintenance target device controlled by the user computer at the user side and monitoring the state of the equipment and transmitting the same to the remote maintenance server.

The database has a physical structure that does not require logical joining of the XML data, and hierarchically stores the XML data document through a tree-based management structure. It is characterized by having a data storage structure of a collection structure for storing divided into the structure of conventional storage locations.

The database server includes a user manager for managing user information; A security management unit for managing a security state of the entire XML-based remote maintenance system; A collection manager for managing a collection structure of the database; And a log manager which manages driving state information of the database server.

The collection manager includes a parser configured to generate a control command of a database by analyzing a query content; The Xpath engine unit performs a query using an Xpath defined by the W3C to query the Document Collections, and returns the queried result as a tree-like result. Wow; An Xupdate engine unit for transforming a single document and a multi document of a database as a function of transforming data after storing the XML document; Order processor, important schema for e-commerce, various schemas provided as a standard for validation, and Ubiel processor architecture as core component (UBL) A Universal Business Languae (UBL) processor unit for providing a Processor Architecture (UBL); An index manager for defining an index on an element and an attribute for improving query performance in the XML document; A schema manager which performs generation modification and validation of a schema of the database; And an XML object manager for managing generation, transformation, and integration of the XML objects represented by the XML document.

 The database server includes a management tool that provides collection, document management, index management, import, and export management functions to manage the database.

A network API including the database server CORBA, XML-RPC (SSL support using JSSE), and SOAP (SSL support using JSSE); XDBC API that allows developers to access the database.

The remote maintenance server includes an electronic manual authoring unit including an XML editor, an XML editor, and an XLST editor; A version control unit which performs version control of the electronic manual; A file conversion unit for converting a commercial heterogeneous extension document into an XML document; A monitoring unit which monitors the equipment; And a remote support for performing fault diagnosis, electronic manual, and remote A / S management for the equipment.

The e-Manual Authoring Section is a form / style (fonts, fonts, margins, headers, etc.) and basic materials necessary for the manufacture and use of manuals (Troubleshooting information, detailed specifications for each device, error codes, drawings, parts, equipment specifications Data such as DB) to be stored.

The XML editor provides a grid and text editing mode, a message window showing errors and information, a source editing function according to the W3C standard, a user-friendly interface such as drag drop, an easy error correction function, and a DB <- > Data conversion function such as XML conversion or HTML <-> XML conversion, Import XML, Export XML function, Validation function for XML document, Repository function using RDBMS, Independent FTP function It provides a project and document management.

The schema editor applies a grid editing method, edits a schema having elements, attributes, entities, and notations recommended by the W3C, validates the schema, and DTDs. It has a function of converting to a document schema and source editing.

The XLST editor has a grid editing method, a multiple document itnerface (MDI) method for interconnected editing of multiple documents, an input window and an output window, a transform function, an RDBMS tree ( TREE) project, wireless management, and independent FTP function to provide an automated function of generating an XSLT style sheet for converting the XML document into a variety of formats.

The version control unit is registered as a formal manual by the approval of all the people involved in the initial manual production and upgrade, maintain the release version until formal approval, support the minimization of manual errors according to collaboration and management, and customers It enables quick response to demands, supports reverting of deletions and updates from edits, saves log records of modifications, additions, deletions, and tracks changes.

The monitoring unit monitors, collects and stores the state information of the equipment in real time through the monitoring device of the user-side equipment, and stores the processed information, and generates and stores failure diagnosis information when a problem occurs.

The remote support unit interlocks with the monitoring unit and transmits related information and solutions to the device in case of a failure inspection of the device and when a problem occurs, and performs a notification function such as a change of screen or an alarm. It performs remote education, A / S support function, history management for fault diagnosis, search function by keyword, and upgrade download function.

The remote support is characterized in that it is configured to work with a remote A / S center.

The web server provides a web server engine for web services, a web interface for each function of the remote maintenance server, integrated search and content viewing, requirement registration, and update reflecting function.

Hereinafter, the present invention will be described in more detail with reference to the accompanying drawings.

1 is a block diagram of an XM-based remote maintenance system of the present invention.

As shown in FIG. 1, the XM-based remote maintenance system of the present invention includes an electronic manual information of a maintenance target device, a maintenance target device information, a diagnostic (troulbeshooting), and a UBI (UBL) shooting database. A database server (DB server) 100 for storing the DB 100A and then controlling the DB 100A; A remote maintenance server 200 which provides an XML-based electronic manual and information on failure recovery of a device online by interworking with a database server; A web server 300 for providing an Internet access service for a web service through the Internet; The monitoring device 400 mounted on the maintenance target equipment (semiconductor equipment, etc.) 500 controlled by the user computer 600 on the user side to monitor the status of the equipment 500 is connected through the communication network 800. It is composed. And it further comprises an A / S server 700 for providing an online A / S service.

The XM-based remote maintenance system of FIG. 1 configured as described above provides an optimized system and manual contents to an equipment user (user), and automatically transmits diagnosis and remote A / S when a failure occurs by real-time equipment monitoring. Perform support functions.

For the above functions, the database server 100 includes a database 100A that stores electronic manuals, diagnostic data, etc. to be provided to remote locations as XML documents, and stores, changes, deletes, and processes data for the database 100A. Perform the process.

The database 100A will be described in more detail. The database 100A stores XML data in a physical structure so that a logical join is not required for retrieval. In addition, a tree-based management structure divides and stores a large number of documents into hierarchical storage locations.

2 shows a database 100A having the above-described hierarchy structure.

As shown in FIG. 2, the database 100A having a hierarchy structure stores an XML document in a collection. Collections have a hierarchical structure, such as UNIX or WINDOWS FILE SYSTEM. At installation, you have a default database instance (for example, "xmldb", where all collections begin with / xmldb), and the database instance can be newly defined as needed.

In the above-described structure, XML documents are stored in a quarried collection, which serves as a table of the RDBMS. And documents of the same type (DTD, Schema) are stored in a collection.

The structure of the database 100A allows the database server 100 to manage a large number of documents hierarchically through a tree-based management structure, and check-in / out function and work for each user. It can support the separation function of. The database server 100 configured to perform the above functions performs a schema check for each schema (DTD) managed object, and implements a Document Object Model (DOM) and a SAX API in compliance with the W3C standard. Support. In addition, by using the Xpath Query Language, which is basically a W3C standard XML search language, it enables to perform various structure search on single or multiple XML documents stored based on XML. And by processing XML using XDBC API, it is optimized to easily process XML data.

3 is a block diagram of a database server 100 that performs the above functions, and FIG. 4 is a diagram illustrating an interface screen for managing the database server 100.

As shown in FIG. 3, the database server 100 includes a user manager 110 for managing a user together with the above-described database 100A, a security manager 120 for managing a security state such as an access right, and a collection manager. and a log manager 140 that manages driving state information of the collection manager 130 and the database server 100.

In the above-described configuration, the collection manager 130 may include a parser 131, an Xpath engine 132, an Xupdate engine 133, and a UBI (Universal Business Languae). The processor unit 134 includes an index manager 135, a schema manager 136, and an XML object manager 137.

The parser 131 analyzes the query contents and generates a control command of the database.

The Xpath engine unit 132 performs a query using the Xpath defined by the W3C to query Document Collections, and returns the queried result as a tree-shaped result ( return).

The Xupdate engine unit 133 performs a transformation function of data after storing an XML document, and supports transformation of a single document as well as multi document of a database.

The UBI (Universal Business Languae) processor unit 134 is an order processor that is important in e-commerce, and various schemas provided as a standard for validation. It provides a UBI processor architecture (UBL Prpcessor Architecture) as a core component (CC).

The index manager 135 defines an index on elements and attributes as improving query performance in a large amount of XML documents.

The schema manager 136 performs generation modification and validation of a schema.

The XML object manager 137 manages generation, transformation and integration of XML objects.

The database server 100 having the above-described configuration provides a management tool as a tool for managing a database as shown in FIG. 4. The management tool provides an interface for performing the functions of FIG. 3, and provides a collection and document management, an index management function, an import and an export management function.

In addition, although not shown in the drawing, the database server 100 includes a network API and an XDBC API. The network API provides communication APIs such as CORBA, XML-RPC (SSL support using JSSE), SOAP (SSL support using JSSE), and the like, to access the database 100A. And the XDBC API is an API that allows developers to access the database and performs the same function as the JDBC of RDBMS.

As described above, the database server 100 of the present invention provides security through multi-user support, XML document management support using an RDBMS, a data-centric method, a document-centric method, a mixed method (Data and document-centric). Supports all.

In addition, it supports Web Interface and supports XML-RPC and Soap, thereby enabling efficient and stable storage and retrieval of XML documents transmitted from XML-RPC (HTTP) -based clients.

In addition, by supporting multiple access of concurrent users, it provides stable service in multi-access environment such as web environment, and integrates and manages XSD (DTD) and XSL documents related to XML document in the same folder as XML document, Full version control for XSD, DTD, and StyleSheet is supported.

Comparing the database server 100 having the above-described configuration with a conventional RDBMS, the existing RDBMS is a structure for storing XML using the OR Mapping Tool, and the OR Mapping Tool has a null value (column) in the column. Since many tables are used because they store wasted space, they are inefficient in the use of memory space. However, since the database 100A of the present invention does not have such a structure, the use efficiency of memory space is improved. In addition, the conventional RDBMS is stored in a logical structure, the RDBMS uses a logical pointer, but the database server 100 of the present invention is to store the database (100A) in a physical (physical) structure and a physical pointer (physical pointer) Because we use, we can search without logical join and are superior in speed than RDBMS.

That is, the RDBMS having a data-centric structure does not use the Xpath defined by the W3C standard, resulting in the above-described performance difference.

5 is a view showing the configuration of the remote maintenance server 200 in the configuration of FIG.

The remote maintenance server 200 provides an electronic manual service and a web-based monitoring service. Here, the electronic manual service provides electronic manuals online. After generating the standard of the manual, editing, versioning, various DTD (or schema) management, document conversion, dedicated browser, database server Performs services such as interlocking, diagnosis of error codes and transmission of action information.

The web-based monitoring service provides trouble shooting automatic history management, remote education and after-sales service support, remote fault diagnosis and repair, and on-offline integrated support service.

In order to provide the above-described service, the remote maintenance server 200 includes an XML editor, an XML editor, an XML editor, and an XLST editor, as shown in FIG. 5. It includes a manual authoring unit 210, a version control unit 220 for performing version control, a file conversion unit 230 for performing a file conversion function, a monitoring unit 240 and a remote support unit 250.

In the above-described configuration, the electronic manual authoring unit 210 performs a function of creating and editing an XML document desired by a user. The DB <-> XML conversion, HTML <-> XML conversion, import XML, export ( Export) It has XML function, supports Unicode, and can perform project functions, XML document highlighting, interworking with XML repository, and so on. 6 and 8 illustrate an example of an interface screen of each XML editor, a schema editor, and an XLST editor configured in the electronic manual authoring unit 210, respectively. In the drawings, the same reference numerals are used to restrict the corresponding drawings.

As shown in Figure 6, the XML editor (XML editor) provides a grid and text editing mode, a message window showing the error and information, the user-friendly interface, such as source editing function, drag drop according to the W3C standard, Easy error correction function, data conversion function such as DB <-> XML conversion or HTML <-> XML conversion, Import XML, Export XML function, Validation of XML document, RDBMS Provides Repository function and independent FTP function to facilitate project and document management. The XML editor described above may be configured independently of the platform by pure Java.

Next, as shown in Figure 7, the schema editor (schema editor) is to make it easier and easier to create an XML document, applying a grid editing method, elements, attributes (W3C) recommended by the W3C (Attribute) Allows editing of schemas such as), entities, and notations. As shown in FIG. 7, the schema details can be edited in the Properties Window, the schema is validated, the DTD document is converted into the schema, and the source editing function is provided.

Next, the XLST editor automates the generation of an XSLT style sheet for converting XML into various formats as an XSL document can be easily and quickly written. To this end, as illustrated in FIG. 8, the XLST editor includes a grid editing method, a multiple document itnerface (MDI) method, an input window and an output window, and a conversion (multi-document itnerface) method to enable cross-linked editing between various documents. Transform function, project using RDBMS tree window, and wireless management are provided. It also provides standalone FTP functionality.

The electronic manual operation unit 210 configured as described above is required to form and style (fonts, fonts, margins, headers, etc.) and drafts and manuals necessary for making and using the manual (Troubleshooting information, detailed specifications for each device, By storing the data such as error codes, drawings, parts, equipment specifications, etc. as a DB, the manual can be produced quickly and used as a general data search material such as basic data search.

That is, the electronic manual authoring unit provides templates, styles and templates for simple manual production, provides an editing environment and management function for easy production / maintenance, and provides manual editing for objects registered through the standard system. It performs the two steps of operation process of registration that selects only necessary objects and editing manual by using registered objects and templates.

The version control unit 220 to perform the version management is to be registered as a formal manual by the approval of all the work involved during the initial manual production and upgrade, and maintain the release version until formal approval, manual according to the collaboration and management Support the minimization of errors, enable rapid response to customer needs, support reverting from edits to deletes and updates, save log records of modifications, additions, deletions, and track changes To perform.

The file converting unit 230 that performs the file converting function converts a commercial document such as DOC, HWP, etc. into an XML when described with an extension.

The monitoring unit 240 monitors and stores in real time through the monitoring device 400 of the equipment 500 installed on the user side. That is, the state information of the equipment 500 is collected, processed and stored, and if a problem occurs, the fault diagnosis information is generated and stored.

The remote support unit 250 is to be linked with the monitoring unit 240. In the event that an unusual matter occurs in the equipment 500, a failure inspection and failure of the equipment 500 and related information and solutions are transmitted to the equipment 500, and a notification function such as a screen change or an alarm is performed. That is, the manual and fault diagnosis information are displayed in the form of a pop-up window on the operation screen of the equipment 500. In addition, it performs remote education, after-sales support, and history management for fault diagnosis. Then, the keyword search function and the upgrade download function are performed.

A / S support of the above-described functions of the remote support unit 250 may be performed in parallel with the on-line and offline, that is, the remote support unit 250 is the first step in the case of supporting the A / S as described above with the equipment Send the solution for the error code and equipment failure through the interworking of the DB to the monitor of the equipment 500, and if the failure of the equipment is not resolved in the first step, the Internet with the A / S server 700 in the second step Performs remote A / S business support function through call center, and when offline service is needed, Internet call center equipped with A / S server 700 visits user directly from A / S center closest to user's area in 3 steps Take action.

In addition to the above functions, the remote maintenance server 200 also provides additional services such as providing regular newsletters, customer-specific online technical writing courses, manual training and consulting.

Next, in the configuration of FIG. 1, the web server 300 provides a web server engine and a user interface for a web service, and a web interface for each function of the remote maintenance server 200 of FIGS. 5 to 8. It provides screens, provides integrated search and contents viewing, reflects when requirements are registered and updated, and provides an electronic manual creation, management, and search interface.

FIG. 9 is a system configuration diagram of a web server 300 according to an exemplary embodiment as described above, and a database 100A implemented as an RDBMS and an XMLDBMS to work with the web server 300.

As shown in FIG. 9, the web server 300 adopts a Java-based Tomcat module 310 as a middleware, and uses all data except XML and all modules except Java UI (JAVA Beans) 320. It can be configured to have maximum extensibility and portability by configuring), and to facilitate interworking and expansion with other systems. And by using a Java-based virtual machine, it is configured to establish a stable server base and to handle a large amount of processing reliably. The JavaBeans 320 passes the user interface and parameters, receives the corresponding result, and causes the UI to process the same.

At this time, the database 100A configured in the database server 100 stores the information data for the manual in the RDB, and stores the information in the RDBMS 100AR for recording the information in a history format. The actual data for the manual is XML It is stored in XML-dedicated database (XMLDBMS (ISIS)) (100AX) and configured to search and modify the XML document.

10 is a view showing a user interface screen of the web server 300 configured as described above, "group management" button for the group management function, "user management" button for the user management function, for registration of the user User registration button, e-manual viewing function, e-manual search function, e-manual registration / deletion / modification / authorization / authorization count, content registration-move-delete-reordering (sorting)-contents management including modification Provides an interface screen for outputting a user list having a "view manual" and a "manual management" button for an electronic manual management function of the user, and having a registered group list and a user registration / modification button of a specific function.

11 is a diagram illustrating an interface screen for the group management function.

The group management of FIG. 11 can be performed only by the system administrator, and only when the user logs in as the system administrator, the "user management" button as shown in the upper right of FIG. 10 is shown. Can be. When the system administrator clicks the "user management" button on the screen of Figure 10, the group list is shown on the left, the user list corresponding to the group appears. In this case, when the "Group management" button is clicked on the upper left, a group management new window as shown in FIG. 11 is displayed, and a group registration, modification and deletion can be performed using the group management new window of FIG.

 As shown in FIG. 11, the group management new window is provided with a registered group list and a "group registration" button for group registration, a "M (Modify)" button for editing, and a "d (delete)" button for deleting. A group list is provided. In FIG. 11, the group list is NTECHSOFT and Doculator.

Group registration is performed by clicking the "Register Group" button on the upper right side of the Group Management New Window of FIG. 11, and clicking the "Register Group" button outputs a screen for registering by entering a group name to register a group. It becomes possible.

The group modification is performed by clicking the "M" button to the right of the group name. The same screen as when registering a group is displayed, and the group name is corrected by inputting the modified group name.

Deleting a group is performed by clicking the "d" button on the right side of the group name, so that the group can be deleted.

The user management function may be performed through the interface screen of FIG. 10.

The interface screen for user registration is output by the user registration button of FIG. 10.

12 is a diagram illustrating an interface screen for user registration among user management functions.

The user management of FIG. 12 may also be performed only by the system administrator, and only when the user logs in as the system administrator, the user registration button as shown in the upper right of FIG. 10 is visible, and user management may be performed using the user. Can be. When the system administrator clicks the "user registration" button on the screen of FIG. 10, a user registration screen as shown in FIG. 12 is output. If the user inputs and registers registration target user information on the screen of FIG. 12, the user registration is completed.

At this time, the user class of the user information may be divided into "system administrator", "manual administrator", "general user".

Among these, the system administrator can perform group management, user management, and manual manager change of a specific manual. In addition, the manual administrator can perform manual creation, manual authority management (Read, Write, Delete), and change the manual administrator function of the manual under his manual management. Finally, general users are the permissions (Read, Write, Delete) granted from the manual administrator. When a user is registered as a general user for the first time, the user can only log in, and there are no manuals that can be viewed or created. It is set to be able to view / write / delete manual only when authorized by.

The interface screen for the user modification function of the user management function is output by the “M” button as a modification button provided on the right side of the user list among the interface screens of FIG. 10. At this time, the output screen is changed to the same screen as the user registration and the item to be modified is modified, and the user modification function is performed by clicking the registration button.

The user delete function among the user management functions is a delete button provided on the right side of the user list in the interface screen of FIG. 10 and is executed by the "d" button. To delete a user, click the "d" button in the rightmost field of the user list, and the delete confirmation dialog box is displayed. If the delete confirmation is selected, the user is deleted. When a user is deleted, recovery can be configured to be available only to the DBA (Database administrator) of the RDB.

13 is a diagram illustrating an interface screen for an electronic manual management function.

The interface screen for managing the electronic manual of FIG. 13 is output by the “view manual” button of FIG. 10, and the read (R), write (W), and delete (D) rights are checked by checking the authority of the currently logged in user. The list of included manuals is printed.

14 and 15 illustrate an interface screen for an electronic manual viewing function.

The interface screen for the electronic manual viewing function of FIG. 14 is output when the manual list to be viewed in FIG. 13 is clicked. In the interface screen for viewing the electronic manual of FIG. 14, information on a manual is shown on the right screen, and the contents of the manual are shown in a tree structure on the left screen. The tree structure on the left is configured for each content, and when the corresponding content is clicked, the content of the corresponding content is output on the right screen as shown in FIG. In FIG. 15, when a content is selected and clicked in the left content tree, all lower contents of the corresponding content are output on the right side.

16 and 17 illustrate interface screens for an electronic manual search function.

The electronic filter search function of FIGS. 16 and 17 is performed using the search box of the left screen of FIG. 14 or FIG. 15. There are two methods of searching an electronic manual, an index search method for viewing keywords and a search keyword input method.

In this case, the index search method may be an index when clicking “View Index” at the top of the contents tree on the left screen.

The keyword input search is then performed by entering a search keyword at the top of the table of contents tree and clicking the "Search" button. In this case, the AND search may be set based on the space. In other words, if "A B" is inputted, the contents containing A and B are searched. 17 shows a search result screen.

18 is a diagram illustrating an interface screen for registration among electronic manual management functions.

The interface screen for registration of the electronic manual management function of FIG. 18 is output when the "New Manual Registration" button is clicked on the interface screen of FIG. (*) Is a required item. Enter the item and click the "Register" button to register a new manual.

19 is a diagram illustrating an interface screen for modification / deletion among electronic manual management functions.

19 shows an interface screen for modification / deletion among electronic manual management functions by clicking a manual title of the manual list of FIG.

The modification of the electronic manual is configured to correct the information of the electronic manual. Enter the information on the electronic manual and press the "Modify" button to modify the information on the electronic manual. And the deletion of the electronic manual is performed by clicking the "Delete Manual" button. In this case, the electronic manual deleted once may be set to be recoverable only by the DBA (Database administrator) of the RDB.

At this time, in the interface screen of FIG. 19, the "Manual Delete" button in the upper right is only for the manual administrator of the manual or a general user who has received the Delete authority, and the "Permission Management" button is for only the manual administrator of the manual and the "Administrator" of the administrator item. The "Select" button is displayed only for system administrators or manual administrators of the manual.

Content modification of the electronic manual may be performed by a content modification operation to be described below.

20 is a diagram illustrating an interface screen for authorization / authorization recovery among electronic manual management functions.

Authorization / revocation of the electronic manual management function of Figure 20 can only be the manual administrator of the electronic manual. The interface screen of FIG. 20 for authorization / authorization of the electronic manual is output when the user clicks the "Permission Management" button on the upper right of the manual modification screen, and as shown in FIG. Only users in the same group are displayed. That is, all the operations such as viewing, creating, and deleting the electronic manual are performed only in the group.

In the above-described permission relationship, the read, write, and delete rights are included in each other. Granting delete permission automatically gives you read and write permissions. Granting write permission automatically grants read permission. Check to grant the right, and uncheck to reclaim the right. If you press the Apply button after the authorization / recovery operation, the authority is applied from that point on.

21 to 29 illustrate interface screens for performing content management.

In an embodiment of the present invention, the actual document work on the electronic manual is performed by performing content management. Content management is divided into registration-modification-delete-move and so on. The content management is generated from "manual management" at the upper right of the screen, and configured to be output through the interface screen of FIG. 19 which is output after selecting an output electronic manual list, but is not limited thereto.

The interface screens for content management of FIGS. 21 to 29 are output when the " modification of contents " linked in the table of contents in the upper left of the interface screen of FIG. 19 is clicked. Click the Edit Contents button, and the content management screen will be displayed in a new window. The content management screen is configured to enable registration, deletion, and movement except for modification of content, but is not limited thereto.

21 is a diagram illustrating an interface screen for content registration in an electronic manual management function.

FIG. 21 is a screen output by clicking " modification of contents " of FIG. 19. Referring to FIG. 21, the content registration process will be described below.

Select the parent content of the content you want to add in the menu tree and press the "Add" button at the top. If it is the top level content, do not select the top level content and press the "Add Top Level" button. Then enter the minimum information of the content on the right side and press the "Register" button. Press the "Register" button to register the content. The content work of the actual content is made through the following content modification. In this case, content that has not been modified and only registered content is not yet distributed, and in this case, it does not appear in the "Manual View".

FIG. 22 is a diagram illustrating an interface screen for moving content among electronic manual management functions.

FIG. 22 is a screen output when clicking "Move" on the screen displayed by clicking "Edit Table of Contents" of FIG. 19. In the interface screen of FIG. 22, the content to be moved in the table of contents tree on the left is selected. Press the "Move" button to move the content. If you need to move to the top level, press the "Move to top" button. If there is a sub-content of the moving content, the sub-contents all move accordingly.

FIG. 23 is a diagram illustrating an interface screen for deleting contents of an electronic manual management function.

To delete the content, select the corresponding content in the contents tree of the content management window by clicking the "Edit Table of Contents" of FIG. 19 and press the "Delete" button at the top to output the interface screen of FIG. If you click OK on the output screen for confirmation of deletion, the corresponding content is deleted. In this case, if there is a lower content of the corresponding content, the lower content is also deleted.

24 is a diagram illustrating an interface screen for changing an order of contents in an electronic manual management function.

The interface screen of FIG. 24 for reordering (sorting) the contents is output by clicking the "Reorder" button among the screens that are displayed by clicking "Modify Table of Contents" in FIG. While movement of the content means movement up and down, reordering (ordering) means changing the order at the same level.

In order to change the order, as shown in FIG. 24, the upper content of the contents to be changed is selected and the "order change" button is pressed. If you want to change the order of the lower level contents of the top level, press the "Top level sorting" button. The order is changed by selecting and moving content on the left screen. If you press the save button after that, the changed order is applied.

25 to 28 are diagrams illustrating an interface screen for content modification in an electronic manual management function.

Content modification of FIGS. 25 to 28 is performed by the "refresh" button in the table of contents of FIG. In FIG. 19, when the "refresh" button is clicked, the modified table of contents tree is displayed, and when the content to be modified is selected in the table of contents tree, the screen is output in a type suitable for the corresponding content on the left screen.

Types of content modification include "title type", "body type", "image type", "multimedia type", and the like. FIG. 25 is a view showing an interface screen for title type modification during content modification of an electronic manual management function. FIG. 26 is a diagram illustrating an interface screen for body type modification during content modification of an electronic manual management function, and FIG. 27 is a diagram showing an interface screen for image type modification during content modification of an electronic manual management function. FIG. Is a diagram illustrating an interface screen for multimedia modification during content modification of an electronic manual management function.

In addition to the above-described modification type of the contents of FIGS. 25 to 28, "warning type", "error code", "troubleshooting", and parts list may be added.

The present invention described above is a Business to Business (B2B) Application, a Government to Business (G2B) Application, eCommerce, eCatalog System, Contents Management System (CMS) Application, WML (Wireless Markup Language) Wireless It can be applied to the Internet, Electronic Data Interchange (EDI), electronic libraries, database integration, enterprise application integration (EAI), companies and governments building XML systems, and any institution that extends from an existing system to an XML system.

By implementing the above-described XML-based data processing of the present invention, it is possible to build an online remote maintenance system at a low cost, thereby expanding the remote maintenance service online through small and medium-sized businesses to further revitalize the e-commerce industry. It provides an effect.

Claims (16)

A database server (DB server) for storing and managing electronic manual information, maintenance target device information, and troubleshooting information about the maintenance target device in a database as an XML document; A remote maintenance server for providing a remote maintenance service for the equipment in association with the database server; A web server providing a web service for searching, providing data, and editing the XML document through the Internet; XM-based remote maintenance characterized in that it comprises a; monitoring device is mounted on the maintenance target equipment controlled by the user computer on the user side to monitor the status of the equipment to transmit to the remote maintenance server; system. The method of claim 1, wherein the database, By using the XML data as a physical structure that does not require a logical join, a tree-based management structure of the XML data document of the hierarchical storage locations XM-based remote maintenance system, characterized in that having a data storage structure of the collection structure to store the structure divided. The method of claim 1, wherein the database server A user manager for managing user information; A security management unit for managing a security state of the entire XML-based remote maintenance system; A collection manager for managing a collection structure of the database; X-ML-based remote maintenance system, characterized in that it comprises a; log manager for managing the driving state information of the database server. The method of claim 3, wherein the collection management unit, A parser for analyzing a query and generating a control command of a database; The Xpath engine unit performs a query using an Xpath defined by the W3C to query the Document Collections, and returns the queried result as a tree-like result. Wow; An Xupdate engine unit for transforming a single document and a multi document of a database as a function of transforming data after storing the XML document; Order processor, important schema for e-commerce, various schemas provided as a standard for validation, and Ubiel processor architecture as core component (UBL) A Universal Business Languae (UBL) processor unit for providing a Prpcessor Architecture; An index manager for defining an index on an element and an attribute for improving query performance in the XML document; A schema manager which performs generation modification and validation of a schema of the database; XM-based remote maintenance, characterized in that it comprises a; XML object manager (XML Object Manager) for managing the generation, transformation, and integration of the XML objects represented in the XML document (XML); system. The method of claim 3 or 4, wherein the database server, XML comprises a management tool that provides collection and document management, index management, import and export management functions to manage the database. Based remote maintenance system. The method of claim 5, wherein the database server, Network APIs including CORBA, XML-RPC (SSL support using JSSE), SOAP (SSL support using JSSE); XDB-based remote maintenance system, characterized in that it comprises; XDBC API to enable developers to access the database. According to claim 1, The remote maintenance server, An electronic manual authoring unit including an XML editor, an XML editor, and an XLST editor; A version control unit which performs version control of the electronic manual; A file conversion unit for converting a commercial heterogeneous extension document into an XML document; A monitoring unit which monitors the equipment; XM-based remote maintenance system, characterized in that it comprises a; a remote support for performing fault diagnosis, electronic manual, remote A / S management for the equipment. The method of claim 7, wherein the electronic manual operation unit, Basic materials necessary for the production and use of the format / style (font, font, margin, header, etc.) of the XML document (Troubleshooting information, detailed specifications for each device, error codes, drawings, parts, equipment specifications) XML-based remote maintenance system, characterized in that to store the data such as DB). The method of claim 7, wherein the XML Editor (XML editor), Provides grid and text editing modes, message windows showing errors and information, and user-friendly interfaces such as source editing, drag drop, easy error correction, DB <-> XML conversion, or HTML <-> XML. Provides data conversion function such as conversion, import XML, export XML function, validation of XML document, repository function using RDBMS, and independent FTP function for project and document management. XM-based remote maintenance system, characterized in that performing. The method of claim 7, wherein the schema editor (schema editor), Grid editing is applied and editing of schemas with elements, attributes, entities, and notations recommended by the W3C, validation of schemas, conversion to schema of DTD documents, source editing XM-based remote maintenance system, characterized in that it has a function. The method of claim 7, wherein the XLST editor (XLST editor), Grid editing method, MDI (Multiple Document Itnerface) method for editing cross-linking between documents, input window and output window, transform function, project using RDBMS tree window, XML-based remote maintenance system, characterized in that it provides an automated function of generating an XSLT style sheet for converting the XML document to a variety of formats with a wireless management and independent FTP function. The method of claim 7, wherein the version control unit, When the initial manual is produced and upgraded, it is registered as a full manual by the approval of all the people involved in the work, it is maintained as a release version until formal approval, supports minimization of manual errors due to collaboration and management, and prompt response to customer requirements. Responsive, support reverting of deletions and updates from edits, saves log records of modifications, additions, deletions, etc., and provides the ability to track changes. Maintenance system. The apparatus of claim 7, wherein the monitoring unit monitors and collects the state information of the equipment in real time through a monitoring device of the user equipment, processes and stores the collected state information, and generates and stores fault diagnosis information when a problem occurs. XM-based remote maintenance system, characterized in that. The method of claim 7, wherein the remote support unit, In the event of any abnormality in the equipment in connection with the monitoring unit, it transmits related information and solutions to the equipment during the failure inspection and failure of the equipment, and performs notification functions such as screen changes or alarms, and remote education and A / S support function, history management for fault diagnosis, XM-based remote maintenance system, characterized in that performs the search function and the download download function by keyword. 15. The XM-based remote maintenance system of claim 14, wherein the remote support unit is configured to interwork with a remote A / S center. The web server of claim 1, wherein the web server provides a web server engine for a web service, a web interface for each function of the remote maintenance server, integrated search and content viewing, requirement registration, and update reflecting function. XM-based remote maintenance system, characterized in that.

Images