Hub identification data processing method and device, storage medium and computer equipment
By using identifier resolution technology to uniformly manage wheel hub production data, the problem of low detection success rate caused by inconsistent data formats has been solved, and efficient data sharing and line division determination have been achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- PURPLE MOUNTAIN LAB
- Filing Date
- 2023-08-15
- Publication Date
- 2026-07-07
Smart Images
Figure CN116991840B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of identification resolution, and more specifically, to a method, apparatus, storage medium, and computer equipment for processing identification data of wheel hubs. Background Technology
[0002] The entire production process of wheel hubs typically involves multiple production stages, and in mixed-line production, wheel hub line segmentation determination is also required. However, in the current technology, the data management method for wheel hubs in the entire production process is not reasonable enough, resulting in inconsistent wheel hub data formats. This can easily lead to problems such as low detection success rate and increased equipment wear during wheel hub line segmentation determination.
[0003] There is currently no effective solution to the above problems. Summary of the Invention
[0004] This invention provides a method, apparatus, storage medium, and computer device for processing wheel hub identification data, in order to at least solve the technical problem of low detection success rate when determining wheel hub markings due to inconsistent wheel hub data formats in related technologies.
[0005] According to one aspect of the present invention, a method for processing wheel hub identification data is provided, comprising: obtaining an initial identification of the wheel hub, a data upload template and production data; determining the data level corresponding to the production data; storing the production data according to the data upload template and the data level; and updating the initial identification based on the storage result of the production data to obtain a target identification.
[0006] Optionally, production data can be stored according to the data upload template and data level, including: initiating an identifier update application based on the production data and data level; receiving the application review result corresponding to the identifier update application; and storing the production data according to the data upload template and data level based on the application review result.
[0007] Optionally, the data level corresponding to the production data can be determined, including: if the production data is only used by the current production stage, the production data is determined as Level 1 data; if the production data is shared by multiple production stages, the production data is determined as Level 2 data; if the production data is shared by other production stages, the production data is determined as Level 3 data.
[0008] Optionally, production data can be stored according to the data upload template and data level, including: when the production data is level 1 or level 2 data, the production data is stored in the local database according to the data upload template; when the production data is level 3 data, the production data is stored in the node used to provide identification services according to the data upload template.
[0009] Optionally, the above method further includes: when the production data is primary or secondary data, the target identifier is carried by an internal identifier carrier embedded inside the wheel hub; when the production data is tertiary data, the target identifier is carried by an external identifier carrier attached to the outer surface of the wheel hub.
[0010] Optionally, the above method also includes: when the above production data is secondary or tertiary data, based on the storage results of the production data, deduplicating the production data of the wheel hub with the same data level in multiple production stages according to data similarity.
[0011] Optionally, after updating the initial identifier based on the storage result of the production data to obtain the target identifier, the method further includes: receiving an identifier cancellation instruction; and deleting the target identifier and the production data based on the identifier cancellation instruction.
[0012] Optionally, when the wheel hub adopts a mixed-line production method, the above method further includes: receiving a line separation determination instruction; based on the line separation determination instruction, using an industrial camera to scan the target mark and parse the target mark to obtain the mark parsing result; based on the mark parsing result, obtaining the wheel hub journal information; and based on the wheel hub journal information, using a robotic arm to separate the wheel hub.
[0013] Optionally, the above method also includes: monitoring the resolution process of the target identifier according to predetermined monitoring items.
[0014] According to another aspect of the present invention, a computer device is also provided, comprising: a memory and a processor, the memory storing a computer program; and a processor for executing the computer program stored in the memory, wherein the computer program, when running, causes the processor to execute the wheel hub identification data processing method described above.
[0015] In this embodiment of the invention, an identifier resolution method is adopted. By uploading and updating the wheel hub identifiers according to a unified template and different levels of importance at different wheel hub production stages, and by deduplicating the data uploaded from each production stage according to the importance of small areas, the data is cleaned. After that, the corresponding information can be obtained by scanning the wheel hub identifier carrier, realizing data sharing. This achieves the goal of efficient and unified management of data generated in the entire wheel hub production process, thereby realizing the technical effects of unified management of data in the entire wheel hub production process, data hierarchical cleaning and high success rate line division determination. This solves the technical problem of low detection success rate in wheel hub line division determination caused by the inconsistent wheel hub data format in related technologies. Attached Figure Description
[0016] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:
[0017] Figure 1 This is a flowchart of a wheel hub identification data processing method provided according to an embodiment of the present invention;
[0018] Figure 2 This is a schematic diagram of an integrated wheel hub production system based on identifier resolution technology according to an optional embodiment of the present invention;
[0019] Figure 3 This is a schematic diagram of a wheel hub production lifecycle data management subsystem provided by an optional embodiment of the present invention;
[0020] Figure 4 This is a flowchart of an integrated system for the entire wheel hub production process based on identifier resolution technology, provided by an optional embodiment of the present invention.
[0021] Figure 5 This is a structural block diagram of a wheel hub identification data processing device provided according to an embodiment of the present invention. Detailed Implementation
[0022] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0023] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0024] As a crucial automotive component, wheel hubs undergo numerous production processes, including die casting, heat treatment, three-stage sorting, and painting. These processes generate a wealth of critical data, such as die casting quality data, die casting reporting data, heat treatment process parameters, and wheel hub quality data. However, this data originates from different workshops, production equipment, and processes, leading to inconsistencies in data formats and redundant information collection. Furthermore, constrained by production workshop capacity and costs, most wheel hub production operates on a mixed-line model, with multiple wheel hub models produced and transported on the same assembly line. To ensure that identical wheel hub blanks are stacked and processed in the same workstation, three-stage sorting is required for line separation. If wheel hub model detection is incorrect, allowing different models of blanks to enter the same production line, it can result in wheel hub scrap, damage to robotic arms, decreased stability of stacking equipment, and even injury to operators.
[0025] In the entire wheel hub production process, precise control of data from stages such as die casting, heat treatment, three-stage sorting, and painting is required to achieve the flow and integration of production data from each stage. This data comes from different workshops, production equipment, and production processes. Traditional wheel hub production process data management methods suffer from problems such as inconsistent data formats, difficulties in information sharing, and redundant information collection.
[0026] Due to limitations in production workshop capacity and production costs, most wheel hubs are produced on mixed lines, with multiple models of wheel hubs being produced and transported on the same production line. In order to ensure that the same model of blank wheel hubs are stacked and processed in the same processing ward, wheel hub line separation judgment is required. Traditional line separation judgment methods have a low success rate, causing problems such as damage to robotic arm equipment and reduced stability of stacking equipment.
[0027] To address the aforementioned problems, this invention provides a method embodiment for processing wheel hub identification data. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.
[0028] Figure 1 This is a flowchart of a wheel hub identification data processing method provided according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:
[0029] Step S102: Obtain the initial identifier of the wheel hub, upload the data template and production data;
[0030] Step S104: Determine the data level corresponding to the production data;
[0031] Step S106: Store production data according to the data upload template and data level;
[0032] Step S108: Based on the storage results of production data, update the initial identifier to obtain the target identifier.
[0033] Through the above steps, using identifier resolution, the data levels of various production data generated throughout the wheel hub production process are determined. Based on the determined data levels, the wheel hub production data can be stored according to a unified data upload template. The initial identifier is updated based on the storage results of the production data to obtain the target identifier. This achieves the purpose of hierarchical storage of wheel hub production data and unified data format. Furthermore, based on the updated target identifier, production data sharing can be easily achieved, thus solving the problem of difficulty in sharing wheel hub production data.
[0034] It should be noted that the above data upload template can be customized by the user, and there is a corresponding relationship between the data upload template and the initial identifier of the wheel hub to ensure that the data format stored corresponding to the same initial identifier is consistent.
[0035] It should be noted that the wheel hub identification data processing process in the above embodiments of the present invention can be implemented based on an identification resolution system. This system assigns an identifier to each object and, with the aid of identification resolution technology, distributes, registers, manages, parses, and routes item identities. This enables cross-regional, cross-industry, and cross-enterprise information querying and sharing, serving as the foundation for breaking down information silos, achieving data interoperability, and mining massive amounts of data. It is also an essential condition for realizing intelligent enterprise management. Therefore, by using identification resolution technology to empower the entire wheel hub production process, assigning a unique identifier to each wheel hub, and using a unified standard to record the entire lifecycle data of wheel hub production, efficient data sharing between upstream and downstream enterprises can be achieved. Automated wheel hub line identification using identification resolution technology can significantly improve the success rate of wheel hub model detection.
[0036] As an optional embodiment, storing production data according to the data upload template and data level includes: initiating an identifier update application based on the production data and data level; receiving the application review result corresponding to the identifier update application; and storing the production data according to the data upload template and data level based on the application review result.
[0037] For production data that needs to be uploaded, this embodiment of the invention will first initiate an identifier update application based on the production data and the data level corresponding to the production data. The user will review the update application. After the review is approved, the application review result corresponding to the above identifier update application will be received. Based on the application review result, the above production data will be stored according to a unified data upload template.
[0038] As an optional embodiment, determining the data level corresponding to the production data includes: determining the production data as Level 1 data when the production data is only used by the current production stage; determining the production data as Level 2 data when the production data is shared by multiple production stages; and determining the production data as Level 3 data when the production data is shared by other production stages.
[0039] In this embodiment of the invention, data can be categorized according to its criticality, privacy level, sharing scope, and data type. For example, data requiring privacy protection can be classified as Level 1 data, which can only be viewed and modified within the current production stage. Data shared within the production stage can be classified as Level 2 data, which is shared only throughout the entire wheel production process and is not publicly visible. Level 2 data can provide data references for each stage of wheel production; for example, Level 2 data uploaded in the current production stage can be used as a reference for the next production stage, and so on. Furthermore, data intended for external sharing can be classified as Level 3 data. This level of data can provide relevant data about the wheel to users outside the production stage, such as wheel production parameters, wheel production quality reports at each stage, and production times at each stage, etc.
[0040] As an optional embodiment, production data is stored according to the data upload template and data level, including: when the production data is level 1 or level 2 data, the production data is stored in the local database according to the data upload template; when the production data is level 3 data, the production data is stored in the node used to provide identification services according to the data upload template.
[0041] Different data levels can be stored in different locations to facilitate data management and retrieval. For example, Level 1 and Level 2 data used in the production process can be stored in a local database and can be retrieved, viewed, or modified at any time during production. Level 3 data, which is shared externally but not used in the production process, can be stored on a node that provides identification services. This ensures that users outside the production process can use the node to parse the target identifier and obtain the Level 3 data without occupying storage space in the local database.
[0042] As an optional embodiment, the above method further includes: when the production data is primary or secondary data, the target identifier is carried by an internal identifier carrier embedded inside the wheel hub; when the production data is tertiary data, the target identifier is carried by an external identifier carrier attached to the outer surface of the wheel hub.
[0043] In this embodiment of the invention, various production data corresponding to the wheel hub can be obtained by parsing the target identifier. Different production data have different scopes of use. For example, production data of level 1 and level 2 are used internally during the wheel hub production process, while production data of level 3 is shared externally outside the wheel hub production process. Therefore, in this embodiment of the invention, the identifier carrier of the production data is also distinguished according to the data level. For example, the target identifier used to carry production data of level 1 and level 2 can be an internal identifier carrier embedded inside the wheel hub, while the target identifier used to carry production data of level 3 can be an external identifier carrier attached to the outside of the wheel hub.
[0044] It should be noted that the aforementioned internal identification carrier is an active identification carrier, which can be embedded inside industrial equipment. It carries industrial internet identification codes and their necessary security certificates, algorithms, and keys, and has network communication capabilities. It can proactively initiate connections to identification resolution service nodes or identification data application platforms without requiring identification reading / writing devices to trigger them. Internal identification carriers include Universal Integrated Circuit Cards (UICCs), chips, modules, and device terminals, etc., which are capable of proactively initiating connections to resolution nodes and application platforms. They are characterized by being embedded within the device, making information difficult to steal, being automatically readable, having strong security capabilities, being able to connect to the network in real time, and having an address within the network.
[0045] It should be noted that the aforementioned external identification carriers are passive identification carriers, including barcode labels, RFIC labels, NFC labels, and other identification carriers that require device reading. These carriers are characterized by the fact that the information is easily stolen when attached to the surface of the device, they require passive reading with the help of a reader, have weak security capabilities and lack certificates, are not connected to the network in real time, and do not have an address in the network.
[0046] As an optional embodiment, the above method further includes: when the production data is secondary or tertiary data, based on the storage results of the production data, deduplicating the production data of the wheel hub with the same data level in multiple production stages according to data similarity.
[0047] Since the wheel hub production process involves multiple stages, the production data uploaded and stored in these stages may contain duplicate data, resulting in data redundancy. Therefore, to avoid data redundancy while improving data cleaning efficiency, this embodiment of the invention, based on the storage results of the production data, performs small-area deduplication on production data of the same data level across different production stages involved in the wheel hub production process, according to data similarity.
[0048] On the one hand, deduplicating production data across different production stages avoids data redundancy between multiple stages. On the other hand, deduplicating production data of the same data level ensures that data cleaning does not affect the storage of production data at different levels. For example, if a piece of production data is simultaneously identified as both level two and level three data, then according to the scheme of this embodiment, deduplication is performed only on level two / level three data at a time. Therefore, after deduplication, this piece of production data will still exist simultaneously in the local database storing level two data and the node storing level three data. This avoids problems such as missing data in the local database or the inability to obtain the data at the node through parsing tags due to deduplication leaving only one copy.
[0049] In addition, the embodiments of the present invention perform deduplication based on the similarity between data. The data similarity can be determined by using a similarity threshold to determine whether the data are similar and whether deduplication is needed. Preferably, similarity optimization technology can be used to perform small-area deduplication on data of the same level in each stage, reducing the number of statistics required each time and the number of deduplications required, thereby improving the efficiency of data cleaning.
[0050] As an optional embodiment, the above method further includes: backing up the data deleted during the deduplication process. To ensure data integrity, this embodiment of the invention performs separate backups of the duplicate deleted data to facilitate data rollback.
[0051] As an optional embodiment, before obtaining the initial identifier of the wheel hub, uploading the data template and production data, the method further includes: receiving an identifier registration instruction; registering an identifier for the wheel hub based on the identifier registration instruction to obtain the initial identifier.
[0052] This invention, based on the received wheel hub identification registration application (i.e., identification registration instruction), registers an identification for the wheel hub and verifies the global uniqueness and format standardization of the identification code in the instruction to ensure that a unique and standardized identification is registered for the wheel hub. After the initial identification passes verification, the identification registration instruction can be transmitted to the backend in the form of a data packet, and the corresponding initial identification is stored in the local database to complete the identification registration of the wheel hub.
[0053] It should be noted that, in this embodiment of the invention, before registering the initial identifier for the wheel hub, an identifier can also be registered for the corresponding enterprise that manufactures the wheel hub to ensure the final resolution effect of the target identifier. For example, before registering the wheel hub identifier, the wheel hub manufacturing enterprise can register an enterprise identifier in the identifier resolution node, wherein the registration specification meets the Handle coding standard. Subsequently, the user can continue to register wheel hub identifiers under this enterprise identifier. The coding specification during wheel hub identifier registration can be customized by the user to facilitate standardized management of the identifiers.
[0054] As an optional embodiment, after updating the initial identifier based on the stored production data to obtain the target identifier, the method further includes: receiving an identifier cancellation instruction; and deleting the target identifier and production data based on the identifier cancellation instruction. If the quality of the wheel hub is substandard and needs to be scrapped or reworked, this embodiment of the invention can synchronously delete the identifier data (i.e., the target identifier and production data) corresponding to the wheel hub from the local database and the identifier resolution node based on the received identifier cancellation instruction, so as to delete invalid data in a timely manner and avoid data chaos.
[0055] As an optional embodiment, when the wheel hub adopts a mixed-line production method, the above method further includes: receiving a line separation determination instruction; based on the line separation determination instruction, using an industrial camera to scan the target mark and parse the target mark to obtain the mark parsing result; based on the mark parsing result, obtaining the wheel hub journal information; and based on the wheel hub journal information, using a robotic arm to separate the wheel hub.
[0056] Wheel hubs are typically produced on mixed production lines, with multiple models flowing along the same line. In such cases, wheel hubs need to be assigned to different production lines based on their model number. In this embodiment of the invention, based on the target identifier of the wheel hub, an industrial camera can directly scan and parse the identifier to obtain the identifier resolution result. The wheel hub journal information is then obtained from the identifier resolution result. This journal information is transmitted to a robotic arm, which can then precisely grasp the wheel hub, improving the accuracy of wheel hub assignment and reducing equipment wear.
[0057] It should be noted that, in this embodiment of the invention, in order to improve the accuracy of wheel hub dividing line determination, the error rate and failure rate of the identifier parsing in the dividing line determination are also recorded, and the recognition accuracy of the industrial camera is corrected in a timely manner based on the recorded results.
[0058] In the above-mentioned line division determination process, the industrial camera scans the target identifier carried by the internal identifier carrier, and the production data obtained in this process is secondary data.
[0059] As an optional embodiment, the above method further includes: monitoring the resolution process of the target identifier according to predetermined monitoring items. This embodiment of the invention also monitors the resolution process of the wheel hub identifier, for example, monitoring the end-to-end latency during the wheel hub identifier resolution process, monitoring the number of resolutions and hits on the local cache during the identifier resolution process, monitoring the status of server hardware and software resources such as CPU and network card during the identifier resolution process, etc. By monitoring each predetermined monitoring item and obtaining monitoring results, this embodiment of the invention can take corresponding predetermined operation and maintenance strategies based on the monitoring results, or promptly notify users to perform operation and maintenance, thereby improving the resolution effect of the target identifier.
[0060] It should be noted that when the target identifier's identifier carrier includes an internal identifier carrier and an external identifier carrier, the parsing of the target identifier and the monitoring of the parsing process of the target identifier in this embodiment of the invention can also be divided into internal identifier parsing and external identifier parsing, or internal identifier parsing monitoring and external identifier parsing monitoring.
[0061] Based on the above embodiments and optional embodiments, the present invention proposes an optional implementation method, which will be described below.
[0062] An optional embodiment of the present invention proposes an integrated system for the entire wheel hub production process based on identifier resolution technology. Figure 2 This is a schematic diagram of an integrated wheel hub production system based on identifier resolution technology according to an optional embodiment of the present invention, such as... Figure 2 As shown, the system includes a wheel hub production lifecycle data management subsystem, a wheel hub production lifecycle data cleaning subsystem, a wheel hub production lifecycle identifier parsing subsystem, and an identifier monitoring subsystem.
[0063] (1) System Architecture
[0064] The entire wheel hub production process includes die casting, marking, heat treatment, three-level sorting, and painting. This invention, in an optional embodiment, designs an integrated system for the entire wheel hub production process based on identifier resolution technology. This system includes a wheel hub production lifecycle data management subsystem, a wheel hub production lifecycle data cleaning subsystem, a wheel hub production lifecycle identifier resolution subsystem, and an identifier monitoring subsystem. Users are divided into internal and external users. Internal users are further divided into super administrators, regular administrators, and system maintenance administrators. External users mainly refer to users who need to query various wheel hub production parameters.
[0065] (2) Wheel hub production lifecycle data management subsystem
[0066] An optional embodiment of this invention designs a data management subsystem for the entire lifecycle of wheel hub production. Figure 3 This is a schematic diagram of a wheel hub production lifecycle data management subsystem provided by an optional embodiment of the present invention, such as... Figure 3 As shown, this subsystem is only for internal super administrators and regular administrators, and includes four parts: user management module, identifier registration module, identifier update module, and identifier deregistration module. Among them:
[0067] 1) User Management Module
[0068] Users must log in to authenticate their identity before using the system. The super administrator is responsible for the registration and management of all wheel hub markings across the entire production line. There is a hierarchical management relationship between the super administrator and regular administrators. Regular administrators, typically users at various stages of wheel hub production, must upload and update wheel hub marking metadata only with the authorization of the super administrator. Any marking update request from a regular administrator must be approved by the super administrator.
[0069] 2) Identifier Registration Module
[0070] Before registering wheel hub identifiers, wheel hub manufacturers need to register their enterprise identifiers in the identifier resolution node, with the registration specifications conforming to the Handle coding standard. Afterwards, the super administrator registers wheel hub identifiers under the enterprise identifiers in this module, categorized into internal and external identifiers, carried by an identifier carrier. The coding specifications are defined by the administrator. The system receives the wheel hub identifier registration application from the super administrator, verifies the global uniqueness and format compliance of the identifier code, and if the verification is successful, transmits the request to the backend via a data packet, storing the wheel hub identifier in the database.
[0071] 3) Identifier Update Module
[0072] Users at each stage of the wheel hub production lifecycle are all ordinary administrators. Ordinary administrators first submit a management request to the super administrator to obtain the right to update the identifier of their respective production stage, and then upload and update the identifier metadata information for that stage. This module provides users with a unified data upload template to ensure consistent data format across all stages of wheel hub production. When uploading data, users can select the data level based on the data's criticality and privacy requirements. An optional implementation of this invention sets the wheel hub data for each stage to three levels.
[0073] Level 1 data: Data requiring privacy protection, which can only be viewed and modified by ordinary administrators in this production process.
[0074] Secondary data: Shared data across production stages. Each production stage uploads secondary data to provide a reference for downstream production stages.
[0075] Level 3 data: Shared data with external users, providing analytical data such as production parameters, wheel hub production quality reports at each stage, and production time at each stage.
[0076] Identifier update requests initiated by regular administrators must be approved by the super administrator. If approved, first-level and second-level data are stored in the local database, while third-level data is stored in the identifier resolution node.
[0077] 4) Identification and Cancellation Module
[0078] If the wheel hub quality is substandard and needs to be scrapped or reworked, the super administrator can submit an application to cancel the identification in this module, and all identification data will be deleted synchronously from the local database and identification resolution node.
[0079] (3) Data cleaning subsystem for the entire life cycle of wheel hub production
[0080] An optional embodiment of this invention designs a data cleaning subsystem for the entire lifecycle of wheel hub production, primarily targeting the deduplication of secondary and tertiary data. To reduce redundant information due to similarity in secondary and tertiary data, and to facilitate the identification, parsing, and display of differentiated information for each production stage to users, this optional embodiment utilizes similarity optimization technology to perform small-area deduplication on data of the same level at each stage, reducing the number of statistics and deduplication steps required each time, thus improving data cleaning efficiency. To ensure the integrity of the original data, duplicate data is backed up separately for easy data rollback.
[0081] (4) Wheel hub production life cycle identification and resolution subsystem
[0082] The optional implementation of this invention designs a wheel hub production lifecycle identification and resolution subsystem, which is divided into three resolution modes: external resolution, internal resolution, and line determination resolution.
[0083] External Resolution: Once an external user acquires the wheel hub, they can scan the external identification carrier to obtain detailed information about each component of the wheel hub. This information is categorized into three levels of data. The final wheel hub identification metadata information is obtained by accessing local cache or external top-level nodes, second-level nodes, enterprise nodes, and recursive nodes. The wheel hub identification metadata information acquisition process utilizes an intelligent routing algorithm to select the optimal resolution path.
[0084] Internal Analysis: Once an internal user acquires a wheel hub, they can scan the internal identification carrier of the wheel hub to obtain upstream production data related to this stage of production, providing a reference for this stage of production. This information is classified as secondary data.
[0085] Separation line judgment analysis: In the three-level sorting process of wheel hubs, many models of wheel hubs are transferred on the same production line. In an optional implementation of the present invention, an industrial camera is designed to analyze the internal markings of the wheel hubs. The industrial camera focuses on the marking carrier inside the wheel hub, scans and obtains the marking metadata information in the secondary data and extracts the wheel hub journal information. The information is transmitted to the robotic arm through a sensor. The robotic arm extends to the corresponding wheel hub diameter and grabs it to the corresponding processing position for further processing.
[0086] (5) Wheel hub marking monitoring subsystem
[0087] An optional embodiment of this invention designs a wheel hub marking monitoring subsystem, which is divided into an external parsing monitoring module, an internal parsing monitoring module, and a line division determination monitoring module. The system operation and maintenance administrator monitors the marking request / response, latency, and other factors during the wheel hub marking parsing process in real time.
[0088] 1) External analysis and monitoring module
[0089] An optional embodiment of this invention designs an external parsing monitoring module to monitor the end-to-end latency of the wheel hub identifier parsing process and record the average value per minute exceeding the request / response latency threshold. In addition, it records the parsing volume and the number of times the local cache is hit during the identifier parsing process. Finally, it monitors the status of server hardware and software resources such as CPU and network card during the identifier parsing process.
[0090] 2) Internal analysis and monitoring module
[0091] An optional embodiment of this invention designs an internal parsing monitoring module to monitor the end-to-end latency of the internal parsing process from the client to the database, and records the average value per minute exceeding the request / response latency threshold. Finally, it monitors the status of server hardware and software resources such as CPU and network card during the parsing process.
[0092] 3) Branch Line Determination and Monitoring Module
[0093] An optional embodiment of this invention designs an identifier resolution monitoring module to monitor the process delay from the wheel hub to the industrial camera and finally into the robotic arm, and records the average value per minute exceeding the delay threshold. In addition, it records the error rate and failure rate of identifier resolution to promptly correct the recognition accuracy of the industrial camera.
[0094] (6) Implementation Plan Introduction
[0095] Figure 4 This is a flowchart of an integrated system for the entire wheel hub production process based on identifier resolution technology, provided by an optional embodiment of the present invention. Figure 4 As shown, the workflow of this system is as follows:
[0096] Step 1: The super administrator completes the wheel hub logo registration in the logo registration module;
[0097] Step 2: Each production stage registers a regular administrator user under the super administrator;
[0098] Step 3: Regular administrators at each production stage upload wheel production information to the identification update module, including primary, secondary, and tertiary data;
[0099] Step 4: The data cleaning module removes duplicates from the secondary and tertiary data of each production stage;
[0100] Step 5: In the third-level sorting stage, the wheel hub journal in the secondary data of the wheel hub is obtained through identifier parsing to realize the wheel hub dividing line determination;
[0101] Step 6: External users obtain the third-level data through identifier resolution, and thus obtain the production information of each stage of the wheel hub production.
[0102] Step 7: Internal users obtain upstream production data related to this stage of production through identifier resolution.
[0103] In summary, the optional embodiments of this invention design an integrated system for the entire wheel hub production process based on identifier resolution technology. This system primarily addresses the challenges of different workshops, production equipment, and production processes throughout the wheel hub production process. Traditional data management methods for the entire wheel hub production process suffer from inconsistent data formats, difficulties in information sharing, and redundant information collection. Furthermore, wheel hub production typically operates on a mixed-line model, and traditional line-based determination methods have low success rates, leading to damage to robotic arms and reduced stability of palletizing equipment. The optional embodiments of this invention design a data cleaning subsystem for the entire wheel hub production lifecycle. Based on similarity optimization technology, it performs small-area deduplication of secondary and tertiary data, reducing the number of statistics and deduplication steps required each time, thus improving data cleaning efficiency. Additionally, the identifier resolution subsystem for the entire wheel hub production lifecycle in the optional embodiments of this invention comprises three functions: external resolution, internal resolution, and line-based determination resolution. This enables accurate wheel hub information queries for both internal and external users, improving the success rate of line-based determination.
[0104] According to an embodiment of the present invention, a wheel hub identification data processing device is also provided. Figure 5 This is a structural block diagram of a wheel hub identification data processing device provided according to an embodiment of the present invention, such as... Figure 5 As shown, the device includes: an acquisition module 51, a determination module 52, a storage module 53, and an update module 54. The device will be described below.
[0105] The acquisition module 51 is used to acquire the initial identifier of the wheel hub, the data upload template, and the production data; the determination module 52 is connected to the acquisition module 51 and is used to determine the data level corresponding to the production data; the storage module 53 is connected to the determination module 52 and is used to store the production data according to the data upload template and the data level; the update module 54 is connected to the storage module 53 and is used to update the initial identifier based on the storage result of the production data to obtain the target identifier.
[0106] According to an embodiment of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to execute the wheel hub identification data processing method described above.
[0107] According to an embodiment of the present invention, a computer device is also provided, comprising: a memory and a processor, wherein the memory stores a computer program; and the processor is configured to execute the computer program stored in the memory, wherein the computer program, when running, causes the processor to execute the wheel hub identification data processing method described above.
[0108] The order of the above embodiments of the present invention is merely for description and does not represent the superiority or inferiority of the embodiments.
[0109] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0110] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units described above can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.
[0111] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0112] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0113] If the integrated units described above are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0114] The above are merely preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.
Claims
1. A method for processing wheel hub identification data, characterized in that, include: Obtain the initial identifier of the wheel hub, upload the data template and production data; The data level corresponding to the production data is determined, wherein the data level is classified according to the criticality, privacy level, sharing scope and data type of the production data; The production data is stored according to the data upload template and the data level. Based on the storage results of the production data, the initial identifier is updated to obtain the target identifier; The step of storing the production data according to the data upload template and the data level includes: when the production data is level 1 or level 2 data, storing the production data in a local database according to the data upload template; when the production data is level 3 data, storing the production data in a node that provides identification services according to the data upload template, and users outside the production process obtain level 3 data by parsing the target identifier based on the node. The first-level data is production data used only in the current production stage; the second-level data is production data shared by multiple production stages; and the third-level data is production data shared by other production stages.
2. The method according to claim 1, characterized in that, The step of storing the production data according to the data upload template and the data level includes: Based on the production data and the data level, initiate an identifier update request; Receive the application review result corresponding to the identifier update application; Based on the application review results, the production data is stored according to the data upload template and the data level.
3. The method according to claim 1, characterized in that, The method further includes: When the production data is primary or secondary data, the target identifier is carried by an internal identifier carrier embedded inside the wheel hub; When the production data is level three data, the target identifier is carried by an external identifier carrier attached to the outside of the wheel hub.
4. The method according to claim 1, characterized in that, The method further includes: In the case that the production data is secondary or tertiary data, based on the storage results of the production data, the production data of the wheel hub with the same data level in multiple production stages are deduplicated according to data similarity.
5. The method according to claim 1, characterized in that, After updating the initial identifier based on the storage result of the production data to obtain the target identifier, the method further includes: Receive the identifier cancellation command; Based on the identification cancellation instruction, delete the target identifier and the production data.
6. The method according to claim 1, characterized in that, When the wheel hub is produced using a mixed-line production method, the method further includes: Receive branch line determination command; Based on the line division determination command, an industrial camera is used to scan the target identifier and parse the target identifier to obtain the identifier parsing result; Based on the identifier parsing result, the hub journal information of the wheel hub is obtained; Based on the wheel hub journal information, a robotic arm is used to divide the wheel hub into sections.
7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Monitor the parsing process of the target identifier according to the predetermined monitoring items.
8. A computer device, characterized in that, include: Memory and processor The memory stores computer programs; The processor is configured to execute a computer program stored in the memory, wherein when the computer program is executed, the processor performs the wheel hub identification data processing method according to any one of claims 1 to 7.