A method and system for authorizing equipment in a production process

Abstract

The present invention discloses a method and system for authorizing equipment in a production process, and relates to the technical field of equipment production authorization. The method comprises: uniformly managing a unique identifier on a server side, and generating a configuration file for obtaining a unique identifier; when the equipment needs authorization, inserting a storage medium with a configuration file, and then calling the interface of the server side through the network to obtain the unique identifier; when the server side is called by the interface, generating a unique identifier according to the configuration file; when the equipment obtains the unique identifier, writing it to a designated system directory, and saving the file writing time; each time the service side is accessed, the equipment sends the unique identifier and the file writing time to the service side, and obtains authorization after verification. The method and system for authorizing equipment in a production process provided by the present invention separate the authorization license from the binding with the MAC address and fully correspond to the number of authorized equipment, thereby ensuring the interests of the authorized party while reducing the production cost of the factory.

Description

Technical Field

[0001] The present invention relates to the technical field of equipment production authorization, and in particular to an authorization method and system for equipment in a production process. Background Art

[0002] With the development of technology, the division of labor in society is becoming more and more refined. For example, some companies are good at providing service content, while some companies are good at producing and manufacturing products. Therefore, the cooperative OEM production model is becoming increasingly popular. In the existing factory production process, an authorization process will be added so that the equipment produced is authorized by the partner.

[0003] Currently, the licensor usually grants authorization based on the MAC address of the device. The MAC address is an address used to confirm the location of the network device. In principle, the MAC address is globally unique and corresponds one-to-one with the hardware device. However, in the actual production of hardware devices, a MAC address may be burned into multiple hardware devices, or it may be manually modified so that a MAC address corresponds to more than one hardware, thereby damaging the interests of the licensor. At the same time, the MAC address needs to be written into the equipment produced by the factory line, and the MAC address needs to be purchased through a formal organization, so it will incur additional production costs for the manufacturer. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a method and system for authorizing equipment in a production process, by uniformly managing the unique identifier on the server side and inserting a storage medium with a configuration file provided by the server side on the device side to obtain the unique identifier, so that the authorization license is no longer bound to the MAC address, thereby ensuring the interests of the authorized party while reducing the production costs of the factory.

[0005] In a first aspect, the present invention provides a method for authorizing equipment in a production process, comprising:

[0006] Unique identifiers are managed uniformly on the server side, and configuration files for obtaining unique identifiers are generated;

[0007] When the device needs authorization, insert the storage medium with the configuration file, and then call the server interface through the network to obtain the unique identifier;

[0008] When the server is called by the interface, a unique identifier is generated according to the configuration file;

[0009] When the device obtains the unique identifier, it writes it into the specified system directory and saves the file write time. Each time the device accesses the server, it sends the unique identifier and file write time to the server and obtains authorization after verification.

[0010] Furthermore, the method further comprises:

[0011] When the device needs to re-flash the firmware, perform the unique identification recovery operation;

[0012] The server marks the unique identifier as allocatable according to the unique identifier recovery operation;

[0013] After the device has reflashed its firmware, the storage medium with the configuration file is inserted again, and then the server interface is called through the network to obtain the unique identifier.

[0014] Furthermore, the configuration file is generated according to a configuration file generation operation, and includes the number of allocable unique identifiers.

[0015] Furthermore, after a device obtains the unique identifier, the storage medium with the configuration file can continue to be used for another device to obtain the unique identifier.

[0016] Furthermore, the method also includes: encrypting the unique identifier and the file writing time.

[0017] In a second aspect, the present invention provides an authorization system for equipment in a production process, including a server and equipment:

[0018] The server is used to generate and manage a unique identifier, and to generate a configuration file for obtaining the unique identifier; when the server is called by an interface, a unique identifier is generated according to the configuration file; when the device sends the unique identifier and the file writing time to the server, authorization is performed after verification;

[0019] The device is used to insert a storage medium with a configuration file when authorization is required, and then call the server's interface through the network to obtain a unique identifier; when the device obtains the unique identifier, it writes it into a designated system directory and saves the file write time; each time the server is accessed, the device sends the unique identifier and file write time to the server.

[0020] Furthermore, when the device needs to re-flash the firmware, a unique identifier recovery operation is performed; the server marks the unique identifier as allocable based on the unique identifier recovery operation; after the device re-flashes the firmware, the storage medium with the configuration file is inserted again, and then the server interface is called through the network to obtain the unique identifier.

[0021] Furthermore, the configuration file includes the number of allocatable unique identifiers.

[0022] Furthermore, after a device obtains the unique identifier, the storage medium with the configuration file can continue to be used for another device to obtain the unique identifier.

[0023] Furthermore, the device is also used to perform encryption operations on the unique identifier and the file writing time.

[0024] The technical solution provided in the embodiments of the present invention has at least the following technical effects:

[0025] By managing the unique identifier on the server side and issuing it according to the configuration file in the storage medium, the authorization license is no longer bound to the MAC address, and there is no need to write the MAC address when the factory produces equipment. By verifying the unique identifier and file write time at each authorization, tampering by other devices is prevented, so that the number of unique identifiers issued is completely consistent with the number of authorized devices, thus ensuring the interests of the authorized party. In addition, when the equipment is produced, only the storage medium needs to be inserted to wait for authorization, which reduces the cost of identifier writing and maintenance for the equipment manufacturer and improves the authorization efficiency.

[0026] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0028] Figure 1 is a flow chart of the method in Embodiment 1 of the present invention;

[0029] Figure 2 It is a schematic diagram of the structure of the system in the second embodiment of the present invention. DETAILED DESCRIPTION

[0030] The embodiment of the present invention provides a method and system for authorizing equipment in a production process, manages the unique identifier in a unified manner on the server side, and inserts a storage medium with a configuration file provided by the server side into the device side to obtain the unique identifier, so that the authorization license is no longer bound to the MAC address, thereby ensuring the interests of the authorized party while reducing the production cost of the factory.

[0031] The technical solution in the embodiment of the present invention has the following general idea:

[0032] 1. The unique identifier is centrally managed by the server, which generates a configuration file for obtaining the unique identifier.

[0033] 2. Develop a client APP and install it on the device. The APP is responsible for writing a unique identifier to the device as a license.

[0034] The APP performs the following operations:

[0035] (1) When the production equipment in the factory line is authorized, a storage medium with a configuration file (such as an SD card) is inserted. The storage medium contains the configuration file provided by the server. After the APP detects the configuration file, it connects to the network (such as WiFi) and obtains a unique identifier by calling the server's interface. The unique identifier is written into the device's system directory, and then the identifier is used as a license to access the server for authorization.

[0036] (2) When the APP writes a unique identifier to the device, it also saves the file writing time and performs verification during authorization to prevent tampering.

[0037] (3) The APP provides a logo recycling entrance. When you need to re-flash the firmware, just click Recycle. After the recycling is successful, re-flash the firmware and execute the authorization process.

[0038] Embodiment 1 Embodiment 1 provides a method for authorizing a device in a production process, such as Figure 1 As shown, including;

[0039] Unique identifiers are managed uniformly on the server side, and configuration files for obtaining unique identifiers are generated;

[0040] When the device needs authorization, insert the storage medium with the configuration file, and then call the server interface through the network to obtain the unique identifier;

[0041] When the server is called by the interface, a unique identifier is generated according to the configuration file;

[0042] When the device obtains the unique identifier, it writes it into the designated system directory and saves the file writing time (the unique identifier and file writing time can be encrypted using existing technology to ensure their security);

[0043] Each time the device accesses the server, it sends the unique identifier and file write time to the server, and is authorized after verification.

[0044] In a possible implementation, in order to solve the problem in the prior art that if the firmware of the device is reflashed, the same MAC address needs to be manually re-authorized again, which is not easy to maintain, the method further includes:

[0045] When the device needs to re-flash the firmware, perform the unique identification recovery operation;

[0046] The server marks the unique identifier as allocatable according to the unique identifier recovery operation;

[0047] After the device has reflashed its firmware, the storage medium with the configuration file is inserted again, and then the server interface is called through the network to obtain the unique identifier.

[0048] The server can assign the recycled unique identifier to the next terminal that requires authorization, and the unique identifier does not need to be bound to the terminal. When the device that has re-flashed its firmware inserts the storage medium with the configuration file again to obtain the unique identifier, it may be assigned the previously recycled unique identifier or another unique identifier. The interests of the authorized party can be guaranteed by ensuring that the number of unique identifiers issued is completely consistent with the number of authorized devices. At the same time, since the identifier is recycled and redistributed, there is no need for manual re-authorization, which makes maintenance very convenient.

[0049] In a possible implementation, the configuration file is generated according to a configuration file generation operation, including the number of unique identifiers that can be allocated. When the device calls the interface of the server to obtain the unique identifier, the server determines whether to issue the unique identifier based on the number of unique identifiers that can be allocated in the configuration file and the number of unique identifiers that have been obtained by the configuration file.

[0050] In a possible implementation, after a device obtains a unique identifier, the storage medium with the configuration file can continue to be used by another device to obtain a unique identifier. The storage medium of the configuration file can be an external SD-card. When a device needs to obtain a unique identifier, the SD-card is inserted and then waits for server authorization. After the unique identifier is written to the specified system directory and the file writing time is saved, the SD-card can be removed and inserted into the next device to obtain the unique identifier.

[0051] Based on the same inventive concept, the present application also provides a system corresponding to the method in Example 1, see Example 2 for details.

[0052] Embodiment 2 In this embodiment, a system for authorizing equipment in a production process is provided. Figure 2 As shown, including a server and a device;

[0053] The server is used to generate and manage a unique identifier, and to generate a configuration file for obtaining the unique identifier; when the server is called by an interface, a unique identifier is generated according to the configuration file; when the device sends the unique identifier and the file writing time to the server, authorization is performed after verification;

[0054] The device is used to insert a storage medium with a configuration file when authorization is required, and then call the server's interface through the network to obtain a unique identifier; when the device obtains the unique identifier, it writes it into a designated system directory and saves the file write time; each time the server is accessed, the device sends the unique identifier and file write time to the server.

[0055] In one possible implementation, when the device needs to re-flash the firmware, a unique identifier recovery operation is performed; the server marks the unique identifier as allocable based on the unique identifier recovery operation; after the device re-flashes the firmware, the storage medium with the configuration file is inserted again, and then the server interface is called through the network to obtain the unique identifier.

[0056] In a possible implementation, the configuration file includes the number of allocatable unique identifiers.

[0057] In a possible implementation, after a device obtains the unique identifier, the storage medium with the configuration file can continue to be used by another device to obtain the unique identifier.

[0058] In a possible implementation, the device is further used to perform encryption operations on the unique identifier and the file writing time.

[0059] Since the system introduced in the second embodiment of the present invention is a system used to implement the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the system based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All systems used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0060] The present invention manages the unique identifier through the server, and issues the unique identifier according to the configuration file in the storage medium, so that the authorization license is no longer bound to the MAC address, and there is no need to write the MAC address when the factory produces the equipment; by verifying the unique identifier and the file write time at each authorization, tampering by other devices is prevented, so that the number of unique identifiers issued is completely consistent with the number of authorized devices, thereby ensuring the interests of the authorizer; in addition, when the equipment is produced, it only needs to insert the storage medium to wait for authorization, which reduces the cost of identifier writing and maintenance and improves the authorization efficiency.

[0061] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0062] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0063] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0064] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0065] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A method for authorizing equipment in a production process, It is characterized in that include: Unique identifiers are managed uniformly on the server side, and configuration files for obtaining unique identifiers are generated; When the device needs authorization, insert the storage medium with the configuration file, and then call the server interface through the network to obtain the unique identifier; When the server is called by the interface, a unique identifier is generated according to the configuration file; When the device obtains the unique identifier, it writes it into the specified system directory and saves the file writing time; Each time the device accesses the server, it sends the unique identifier and file write time to the server, and is authorized after verification. When the device needs to re-flash the firmware, perform the unique identification recovery operation; The server marks the unique identifier as allocatable according to the unique identifier recovery operation; After the device has reflashed its firmware, insert the storage medium with the configuration file again, and then call the server's interface through the network to obtain the unique identifier; The configuration file is generated according to a configuration file generation operation, and includes a number of allocable unique identifiers; After a device obtains a unique identifier, the storage medium with the configuration file can continue to be used for another device to obtain a unique identifier; Encrypt the unique identifier and file write time.

2. An authorization system for equipment in the production process, It is characterized in that Including server and equipment: The server is used to uniformly manage the unique identifier and generate a configuration file for obtaining the unique identifier; when the server is called by the interface, the unique identifier is generated according to the configuration file; when the device sends the unique identifier and the file writing time to the server, authorization is performed after verification; The device is used to insert a storage medium with a configuration file when authorization is required, and then call the interface of the server through the network to obtain a unique identifier; when the device obtains the unique identifier, it writes it into a designated system directory and saves the file writing time; each time the server is accessed, the device sends the unique identifier and the file writing time to the server; When the device needs to re-flash the firmware, the unique identifier recovery operation is performed; the server marks the unique identifier as assignable according to the unique identifier recovery operation; after the device re-flashes the firmware, the storage medium with the configuration file is inserted again, and then the server interface is called through the network to obtain the unique identifier; The configuration file includes the number of unique identifiers that can be allocated; After a device obtains a unique identifier, the storage medium with the configuration file can continue to be used for another device to obtain a unique identifier; The device is also used to perform encryption operations on the unique identifier and the file writing time.

Images