Machine tool remote management platform and machine tool remote management system
By utilizing the receiving, storage, permission management, and collaborative review modules of the machine tool remote management platform, the problems of collaboration difficulties and insufficient permission control in existing machine tool machining code file remote management systems have been solved, achieving precise management of user operation permissions and improving collaboration efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-31
- Publication Date
- 2026-05-05
AI Technical Summary
Existing remote management systems for machine tool processing code files lack effective collaboration mechanisms and access control, which makes it easy for multiple engineers to overwrite each other's work results and makes it impossible to accurately control the operating permissions of different users.
A remote machine tool management platform is provided, including a receiving module, a data storage module, a permission management module, and an execution module, which is used to manage various operation permissions of users on machining code files and supports collaborative review and version management.
It enables effective management of different user operation permissions, improves collaboration efficiency and the accuracy of permission control, and ensures the security and integrity of processed code files.
Smart Images
Figure CN121979119A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of intelligent manufacturing technology, and in particular to a machine tool remote management platform and a machine tool remote management system. Background Technology
[0002] Currently, the remote transmission of machining programs for machine tools in the industry is usually based on DNC (Distributed Numerical Control) systems using servers such as industrial control computers. In a DNC system, machining code files, such as machining programs, can be sent from the server to the corresponding machine tool.
[0003] However, the existing DNC system still has the following problems: (1) Difficulty in collaboration: When multiple engineers need to collaborate to complete the programming of a complex workpiece, there is a lack of effective collaboration mechanism - changes cannot be automatically merged, and it is easy to overwrite the work results of others; (2) Lack of access control: It is impossible to accurately control the permissions of different users to view, edit or download the machining code file.
[0004] Therefore, the remote management of machining code files for machine tools still needs further improvement. Summary of the Invention
[0005] This application aims to at least address one of the technical problems existing in the prior art. Embodiments of this application provide a machine tool remote management platform and a machine tool remote management system, capable of effectively managing the permissions of different users for various operations on machining code files.
[0006] The relevant technical solutions of the embodiments of this application include the following: A first aspect of this application provides a remote machine tool management platform. The remote machine tool management platform is used for communication connection with a machine tool, and the remote machine tool management platform includes: The receiving module is used to receive machining code files from the machine tool, wherein the machining code files have permission information representing user operation permissions; A data storage module, connected to the receiving module, is used to store machining code files from the machine tool; The permission management module, connected to the receiving module and the data storage module, is used to respond to the type of user request and verify the user's operation permissions for the processed code file corresponding to the request type; and The execution module, connected to the permission management module, is used to respond to the user's request when the permission management module verifies that the user has the corresponding operation permissions.
[0007] The machine tool remote management platform in this application embodiment has at least the following technical effects: the permission management module in the machine tool remote management platform can respond to the type of user request and verify the user's operation permission for the machining code file corresponding to the type of request, thereby effectively managing the permissions of different users for various operations on the machining code file.
[0008] Optionally, the permission information includes viewing permissions, editing permissions, download permissions, and review permissions; The execution module is used to respond to the user's viewing request and open the processing code file when the user has viewing, editing, downloading or reviewing permissions; The execution module is also used to respond to the user's review request, open the processing code file and receive the user's review comments when the user has review permissions; The execution module is also used to respond to the user's editing or downloading requests and send the machining code file to the machine tool when the user has editing and downloading permissions.
[0009] Optionally, the machine tool remote management platform also includes a collaborative review module, which allows users with review permissions within the same collaborative review group to annotate, return, or approve machining code files. Different users within the same collaborative review group are located at different nodes in the review process for the same machining code file and have editing, reviewing, or publishing permissions respectively.
[0010] Optionally, the collaborative review module includes: The collaborative workflow notification unit is used to respond to a user's review operation on a processed code file at a certain node of the same review workflow. It notifies users at adjacent nodes of the workflow number, the latest review operation type, the latest review operation time, and the username of the user performing the latest review operation. The review operation types include edit, comment, return, approve, and publish. The review history display unit is used to display the review operation type, review operation username, and review operation time of each node in the order of the review process. It is also used to display the annotation content of nodes with annotation operations.
[0011] Optionally, the collaborative review module includes: The file comparison unit is used to compare the processed code files before and after editing at the nodes with editing operations in the review process, line by line. The difference display unit is used to mark and display the differences between the processed code files before and after editing.
[0012] Optionally, the file comparison unit is also used to compare the processed code files before and after editing in a column-based display manner; The difference display unit is also used to identify machining parameter variables in the machining code file and highlight their changes, wherein the machining parameter variables include feed rate or spindle speed.
[0013] Optionally, it also includes a sending module connected to the execution module for sending machining code files to the machine tool; the data storage module is also used to store the submission time, submitter information, associated machine tool number, and reason for modification of the machining code files.
[0014] Optionally, the machine tool remote management platform further includes a version management module. The version management module is used to assign file numbers to the machining code files stored in the data storage module according to the submission time and the reason for modification. The file number includes a file number and a version number, wherein the version number includes sequence information representing the order of the submission time and attribute information representing whether the modification belongs to the test and verification category.
[0015] Optionally, the version management module includes: The main version genealogy construction unit is used to filter and aggregate all non-test / verification class processing code files belonging to the same file number, and construct a tree-structured version genealogy with the processing code file with the latest submission time as the root node. The tree-structured version genealogy displays all non-test / verification class processing code files with the same file number in chronological order from most recent to oldest. The bypass version genealogy construction unit is used to filter and aggregate all processing code files of the test and verification classes belonging to the same file number, and construct a tree-structured version genealogy with the processing code file with the latest submission time as the root node. The tree-structured version genealogy displays all processing code files of the test and verification classes with the same file number in chronological order from most recent to oldest.
[0016] A second aspect of this application provides a remote machine tool management system. The remote machine tool management system includes a machine tool, a machine tool management client, and a remote machine tool management platform according to any technical solution of the first aspect of this application. The machine tool is equipped with a controller and a gateway connected to the controller. The remote machine tool management platform is communicatively connected to the machine tool management client, and the remote machine tool management platform is also communicatively connected to the controller through the gateway.
[0017] The machine tool remote management system in this application embodiment also has at least the technical effects of the machine tool remote management platform in the foregoing embodiments, which will not be repeated here.
[0018] Additional aspects and advantages of this application will be set forth in part in the description which follows. Some will become apparent from the description, or may be learned by practice of this application. Attached Figure Description
[0019] Figure 1 This is a schematic diagram of the components of a machine tool remote management platform in some embodiments of this application; Figure 2 This is a schematic diagram of the constituent modules of a machine tool remote management platform in some embodiments of this application; Figure 3 This is a schematic diagram of the collaborative review module in an embodiment of this application; Figure 4 This is a schematic diagram of the version management module in the embodiments of this application. Detailed Implementation
[0020] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar components or components having the same or similar functions throughout.
[0021] The embodiments described in this application with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application. The technical solutions of the various embodiments of this application can be combined with each other, but should be based on what those skilled in the art can implement.
[0022] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar components or components having the same or similar functions throughout.
[0023] The embodiments described in this application with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application. The technical solutions of the various embodiments of this application can be combined with each other, but should be based on what those skilled in the art can implement.
[0024] In the description of this application, the term "multiple" means at least two. Unless otherwise specified, "connection" means at least a communication connection or coupling between program modules, wherein "communication connection" means the transmission and exchange of information through a medium, and communication connections include wired connections and wireless connections.
[0025] In this application, terms such as “first” or “second” are used only for distinguishing purposes and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated.
[0026] A first aspect of this application provides a machine tool remote management platform 100. The machine tool remote management platform 100 can be a service platform built on cloud computing, i.e., a cloud platform. The machine tool remote management platform 100 provides a series of cloud computing services and applications that can be invoked.
[0027] like Figure 1 As shown, the machine tool remote management platform 100 is used to communicate with the machine tool, and the machine tool remote management platform 100 includes a receiving module 110, a data storage module 120, an access control module 130, and an execution module 140.
[0028] The receiving module 110 receives machining code files from the machine tool, which contain permission information representing user operation permissions. The receiving module 110 can receive machining code files sent by the machine tool itself, as well as those sent by the machine tool management client. The machine tool remote management platform 100 communicates with both the machine tool and the machine tool management client. The machine tool may be configured with a gateway and a controller; the machine tool remote management platform 100 communicates with the machine tool's controller through the gateway.
[0029] Processing code files use their file numbers or configuration metadata (such as access control lists) to characterize user access permissions. Access Control Lists (ACLs) can be embedded internally into processing code files or managed externally by the server's database. An ACL contains multiple control entries, each of which is either a username entry or a group entry. Each username entry contains the username and permissions that can be granted to that user, while each group entry contains the name of the user group and permissions that can be granted to its members.
[0030] The data storage module 120 is connected to the receiving module 110 and is used to store the machining code files of the machine tool. Both machining code files sent by the machine tool management client and those sent by the machine tool itself can be stored in the data storage module 120 of the machine tool remote management platform 100.
[0031] The permission management module 130 is connected to the receiving module 110 and the data storage module 120 respectively, and is used to respond to the type of user request and verify whether the user has the operation permission corresponding to the type of request for the processed code file.
[0032] The execution module 140 is connected to the permission management module 130 and is used to respond to user requests when the permission management module 130 verifies that the user has the corresponding operation permissions. For example, a user may not have editing permissions for a certain code file, but their operation triggers an editing request. After verification, the permission management module 130 determines that the user does not have the operation permissions corresponding to the request type. Therefore, the execution module 140, based on the verification result of the permission management module 130, determines not to respond to the user's editing request.
[0033] The permission management module 130 in the machine tool remote management platform 100 of this application embodiment can respond to the type of user request and verify the user's operation permission for the machining code file corresponding to the type of request, thereby effectively managing the permissions of different users for various operations on the machining code file.
[0034] Optionally, in some embodiments of this application, the permission information includes viewing permission, editing permission, download permission, and review permission. The execution module 140 is configured to respond to a user's viewing request and open the machining code file when the user has viewing permission, editing permission, download permission, or review permission; the execution module 140 is also configured to respond to a user's review request, open the machining code file, and receive the user's review comments when the user has review permission; the execution module 140 is also configured to respond to a user's editing request or download request and send the machining code file to the machine tool when the user has both editing and download permission.
[0035] Optionally, in some embodiments of this application, such as Figure 2 As shown, the machine tool remote management platform 100 also includes a collaborative review module 150. The collaborative review module 150 is used to allow users with review permissions within the same collaborative review group to annotate, return, or approve machining code files. Different users within the same collaborative review group are located at different nodes in the review process for the same machining code file and have editing, reviewing, or publishing permissions respectively.
[0036] Optionally, in some embodiments of this application, such as Figure 3As shown, the collaborative review module 150 includes a collaborative process notification unit 151 and a review history display unit 152. The collaborative process notification unit 151 responds to a user's review operation on a processed code file at a certain node of the same review process, notifying users at adjacent nodes of the review process number, the latest review operation type, the latest review operation time, and the latest review operation username. The review operation types include edit, comment, return, approve, and publish. The review history display unit 152 displays the review operation type, review operation username, and review operation time of each node according to the node order of the review process, and also displays the comment content of nodes with comment operations.
[0037] Optionally, in some embodiments of this application, such as Figure 3 As shown, the collaborative review module 150 includes a file comparison unit 153 and a difference display unit 154. The file comparison unit 153 is used to compare the processed code files before and after editing at nodes with editing operations in the review process, sentence by sentence. The difference display unit 154 is used to mark and display the differences between the processed code files before and after editing.
[0038] Optionally, in some embodiments of this application, the file comparison unit 153 is further configured to compare the machining code files before and after editing in a column-based display manner. The difference display unit 154 is further configured to identify machining parameter variables in the machining code files and highlight their changes, wherein the machining parameter variables include feed rate or spindle speed. For most machine tools, feed rate and spindle speed are important parameters for machining workpieces. Therefore, identifying and highlighting the machining parameter variables in the machining code files helps users quickly clarify the changes before and after editing the machining code files.
[0039] Optionally, in some embodiments of this application, such as Figure 2 As shown, the machine tool remote management platform 100 also includes a sending module 160, which is connected to the execution module 140. The sending module 160 is used to send machining code files to the machine tool. The data storage module 120 is also used to store the submission time, submitter information, associated machine tool number, and modification reason of the machining code file. The information stored in the data storage module 120 allows users to easily trace the reasons for the creation and modification of the machining code file.
[0040] Optionally, in some embodiments of this application, such as Figure 2As shown, the machine tool remote management platform 100 also includes a version management module 170. The version management module 170 assigns file numbers to the machining code files stored in the data storage module based on the submission time and the reason for modification. The file number includes a file ID and a version sequence number. The version sequence number includes sequence information representing the order of submission times and attribute information representing whether the modification belongs to the test / verification category. If the machining code file belongs to the test / verification category, many users can have download, edit, or review permissions; however, if the machining code file does not belong to the test / verification category, typically only some users are granted viewing, download, and publishing permissions, while editing permissions are not granted.
[0041] Optionally, in some embodiments of this application, the version management module 170 includes a main version lineage construction unit and a bypass version lineage construction unit. The main version lineage construction unit is used to filter and aggregate all non-test / verification class processing code files belonging to the same file number, and construct a tree-structured version lineage with the processing code file with the latest submission time as the root node. The tree-structured version lineage displays all non-test / verification class processing code files with the same file number in chronological order from most recent to oldest. The bypass version lineage construction unit is used to filter and aggregate all test / verification class processing code files belonging to the same file number, and construct a tree-structured version lineage with the processing code file with the latest submission time as the root node. The tree-structured version lineage displays all test / verification class processing code files with the same file number in chronological order from most recent to oldest.
[0042] Using the most recently submitted code file as the root node, and working backward from the root node, the complete review history can be clearly seen, making it easier for users to understand the evolution of the code file.
[0043] A second aspect of this application provides a remote machine tool management system. The remote machine tool management system includes a machine tool, a machine tool management client, and a remote machine tool management platform 100 according to any technical solution of the first aspect of this application. The machine tool is equipped with a controller and a gateway connected to the controller. The remote machine tool management platform 100 is communicatively connected to the machine tool management client, and the remote machine tool management platform 100 is also communicatively connected to the controller through the gateway.
[0044] The machine tool management client can be a web browser client, desktop application client, or mobile application client. The machine tool management client is installed on the client device and can communicate with the machine tool. The client device can be any wired or wireless terminal device such as a mobile phone, tablet, PDA (personal digital assistant), or in-vehicle computer. Wireless smart terminal devices can be handheld devices with wireless connectivity or other processing devices connected to a wireless modem.
[0045] With the help of the machine tool remote management platform 100, the machine tool management client can communicate with the machine tool. More specifically, with the help of the machine tool remote management platform 100 and the gateway, the machine tool management client can communicate with the machine tool's controller, enabling different users to collaboratively review machining code files on the same online platform, and effectively manage the permissions of different users for various operations on the machining code files.
[0046] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. Any combination of technical features that does not contradict each other should be considered within the scope of this application.
[0047] Those skilled in the art will understand that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.
Claims
1. A machine tool remote management platform, used for communication connection with machine tools, characterized in that, include: The receiving module is used to receive machining code files from the machine tool, wherein the machining code files have permission information representing user operation permissions; A data storage module, connected to the receiving module, is used to store machining code files from the machine tool; The permission management module, connected to the receiving module and the data storage module, is used to respond to the type of user request and verify the user's operation permissions for the processed code file corresponding to the type of request. as well as The execution module, connected to the permission management module, is used to respond to the user's request when the permission management module verifies that the user has the corresponding operation permissions.
2. The machine tool remote management platform according to claim 1, characterized in that, The permission information includes viewing permissions, editing permissions, download permissions, and review permissions; The execution module is used to respond to the user's viewing request and open the processing code file when the user has viewing, editing, downloading or reviewing permissions; The execution module is also used to respond to the user's review request, open the processing code file and receive the user's review comments when the user has review permissions; The execution module is also used to respond to the user's editing or downloading requests and send the machining code file to the machine tool when the user has editing and downloading permissions.
3. The machine tool remote management platform according to claim 1, characterized in that, The machine tool remote management platform also includes a collaborative review module, which allows users with review permissions within the same collaborative review group to annotate, return, or approve machining code files. Different users within the same collaborative review group are located at different nodes in the review process for the same machining code file and have editing, reviewing, or publishing permissions respectively.
4. The machine tool remote management platform according to claim 3, characterized in that, The collaborative review module includes: The collaborative workflow notification unit is used to respond to a user's review operation on a processed code file at a certain node of the same review workflow. It notifies users at adjacent nodes of the workflow number, the latest review operation type, the latest review operation time, and the username of the user performing the latest review operation. The review operation types include edit, comment, return, approve, and publish. The review history display unit is used to display the review operation type, review operation username, and review operation time of each node in the order of the review process. It is also used to display the annotation content of nodes with annotation operations.
5. The machine tool remote management platform according to claim 3, characterized in that, The collaborative review module includes: The file comparison unit is used to compare the processed code files before and after editing at the nodes with editing operations in the review process, line by line. The difference display unit is used to mark and display the differences between the processed code files before and after editing.
6. The machine tool remote management platform according to claim 5, characterized in that, The file comparison unit is also used to compare the processed code files before and after editing in a column-based display manner; The difference display unit is also used to identify machining parameter variables in the machining code file and highlight their changes, wherein the machining parameter variables include feed rate or spindle speed.
7. The machine tool remote management platform according to any one of claims 1 to 6, characterized in that, It also includes a sending module, connected to the execution module, for sending machining code files to the machine tool; the data storage module is also used to store the submission time, submitter information, associated machine tool number, and reason for modification of the machining code file.
8. The machine tool remote management platform according to claim 7, characterized in that, The machine tool remote management platform also includes a version management module. The version management module is used to assign file numbers to the machining code files stored in the data storage module according to the submission time and the reason for modification. The file number includes a file number and a version number, wherein the version number includes sequence information representing the order of submission time and attribute information representing whether the modification belongs to the test and verification category.
9. The machine tool remote management platform according to claim 8, characterized in that, The version management module includes: The main version genealogy construction unit is used to filter and aggregate all non-test / verification class processing code files belonging to the same file number, and construct a tree-structured version genealogy with the processing code file with the latest submission time as the root node. The tree-structured version genealogy displays all non-test / verification class processing code files with the same file number in chronological order from most recent to oldest. The bypass version genealogy construction unit is used to filter and aggregate all processing code files of the test and verification classes belonging to the same file number, and construct a tree-structured version genealogy with the processing code file with the latest submission time as the root node. The tree-structured version genealogy displays all processing code files of the test and verification classes with the same file number in chronological order from most recent to oldest.
10. A machine tool remote management system, comprising a machine tool, characterized in that, It also includes a machine tool management client and a machine tool remote management platform according to any one of claims 1 to 9, wherein the machine tool is configured with a controller and a gateway connected to the controller, the machine tool remote management platform is communicatively connected to the machine tool management client, and the machine tool remote management platform is also communicatively connected to the controller through the gateway.