A device code determination method, apparatus and control system

Abstract

The embodiment of the application provides a device code determination method, device and control system, through the generated industrial identification code of the device, the first device code and the second device code and the first corresponding relationship and the second corresponding relationship of the industrial identification code are stored in the receiving end and the sending end respectively, through the definition of the asymmetric coding mark, the internal private code is used for business operation in the platform, that is, the first device code and the second device code, the identification public code is used for communication outside the platform, that is, the industrial identification code, and then the problem of description accuracy and communication timeliness between the receiving end and the sending end can be solved through the identification public code on the basis of protecting the internal private code.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and in particular to a device code determination method, apparatus and control system. Background Technology

[0002] Operating and maintaining equipment and ensuring network security and stability are among the key tasks of the operators to which the equipment belongs. However, due to the large number and variety of brands and types of upstream communication equipment manufacturers (hereinafter referred to as manufacturers), even the same type of equipment may have different configuration parameters from different manufacturers, which brings inconvenience to operators' equipment operation and maintenance. Therefore, in order to reduce the difficulty of equipment operation and maintenance, operators often need to obtain technical support from manufacturers.

[0003] Both manufacturers and operators assign device codes to their equipment, but these codes are considered private and not shared. This means that manufacturers are unaware of the device codes assigned by operators, and vice versa. Consequently, when manufacturers provide technical support to operators, both parties struggle to identify the device being discussed using the device code, leading to inaccurate communication, difficulty in timely problem identification, and other issues. Summary of the Invention

[0004] The purpose of this invention is to provide a device code determination method, apparatus, and control system to solve the problems existing in the prior art. The specific technical solution is as follows:

[0005] According to a first aspect of the present invention, a device code determination method is provided, applied to a receiving end, wherein the receiving end pre-stores a first correspondence between a first device code and an industrial identifier code, wherein each first device code is a private identifier code assigned to a device by a platform to which the receiving end belongs, and the industrial identifier code is a public identifier code assigned to a device by any platform, the method comprising:

[0006] The sender obtains the target industrial identification code sent by the sender. The sender has a second correspondence between the second device code and the industrial identification code stored in advance. The target industrial identification code is the industrial identification code corresponding to the target second device code that the sender determines in response to the input target second device code according to the second correspondence. The second device code is a private identification code assigned to the device by the platform to which the sender belongs.

[0007] Based on the first correspondence, the first device code corresponding to the target industrial identification code is determined as the first target device code.

[0008] As one implementation, the method further includes:

[0009] Obtain the device's first equipment code and industry identification code;

[0010] Establish a first correspondence between the first device code and the industrial identification code.

[0011] As one implementation, the method further includes:

[0012] Obtain the first device code of the device, which carries the device SN code;

[0013] The device SN code is sent to the middleware, so that the middleware determines the industrial identification code corresponding to the device SN code according to the third correspondence between the SN code and the industrial identification code stored in the middleware in advance, and sends the determined industrial identification code to the receiving end; the middleware is a component between the sending end and the receiving end, and both the sending end and the receiving end can access the data stored in the middleware;

[0014] Obtain the industrial identification code sent by the middleware;

[0015] Establish a first correspondence between the first device code and the acquired industrial identification code.

[0016] In one implementation, the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes. The method further includes:

[0017] If the target industrial identification code matches the industrial identification code of the faulty equipment, then the equipment represented by the industrial identification code is determined to be a potentially faulty equipment.

[0018] According to a second aspect of the embodiments of this application, a device code determination method is provided, applied to a sending end, wherein the sending end pre-stores a second correspondence between a second device code and an industrial identification code, each of the second device codes being a private identification code assigned to a device by the platform to which the sending end belongs, and the industrial identification code being a public identification code assigned to a device by any platform, the method comprising:

[0019] Determine the target industrial identification code, which is the industrial identification code corresponding to the target second device code obtained by the sending end in response to the input target second device code according to the second correspondence relationship;

[0020] The target industrial identification code is sent to the receiving end so that the receiving end can determine the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and use it as the first target device code; the receiving end pre-stores the first correspondence relationship between the first device code and the industrial identification code, and each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs.

[0021] As one implementation, the method further includes:

[0022] Obtain the device's second equipment code and industrial identification code;

[0023] Establish a second correspondence between the second device code and the industrial identification code.

[0024] As one implementation, the method further includes:

[0025] Obtain the industrial identification code and equipment serial number (SN) of the equipment; the equipment SN is a unique identifier for the equipment.

[0026] Establish a third correspondence between the industrial identification code and the equipment serial number;

[0027] The third correspondence is saved in the middleware so that the receiving end can establish the first correspondence based on the third correspondence stored in the middleware.

[0028] In one implementation, the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes. The method further includes:

[0029] If the target industrial identification code matches the industrial identification code of the faulty equipment, then the equipment represented by the industrial identification code is determined to be a potentially faulty equipment.

[0030] According to a third aspect of the embodiments of this application, a device code determination system is provided, characterized in that the system includes a transmitting end and a receiving end, wherein:

[0031] The receiving end pre-stores a first correspondence between a first device code and an industrial identifier code, wherein each first device code is a private identifier code assigned to the device by the platform to which the receiving end belongs, and the industrial identifier code is a public identifier code assigned to the device by any platform; the sending end pre-stores a second correspondence between a second device code and an industrial identifier code, wherein the second device code is a private identifier code assigned to the device by the platform to which the sending end belongs.

[0032] The sending end is used to determine the target industrial identification code and send the target industrial identification code to the receiving end. The target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship.

[0033] The receiving end is used to obtain the target industrial identification code sent by the sending end, and determine the first device code corresponding to the target industrial identification code according to the first correspondence relationship, as the first target device code.

[0034] According to a fourth aspect of the embodiments of this application, a device code determination apparatus is provided, characterized in that it is applied to a receiving end, wherein the receiving end pre-stores a first correspondence between a first device code and an industrial identification code, each of the first device codes being a private identification code assigned to a device by the platform to which the receiving end belongs, and the industrial identification code being a public identification code assigned to a device by any platform, the apparatus comprising:

[0035] The first acquisition module is used to acquire the target industrial identification code sent by the sending end. The sending end pre-stores a second correspondence relationship between the second device code and the industrial identification code. The target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship. The second device code is a private identification code assigned to the device by the platform to which the sending end belongs.

[0036] The first determining module is used to determine the first device code corresponding to the target industrial identification code based on the first correspondence relationship, and use it as the first target device code.

[0037] In one embodiment, the device further includes a second acquisition module for acquiring the device's first device code and industrial identification code;

[0038] Establish a first correspondence between the first device code and the industrial identification code.

[0039] In one embodiment, the device further includes a third acquisition module for acquiring a first device code of the device, wherein the first device code carries a device serial number (SN).

[0040] The device SN code is sent to the middleware, so that the middleware determines the industrial identification code corresponding to the device SN code according to the third correspondence between the SN code and the industrial identification code stored in the middleware in advance, and sends the determined industrial identification code to the receiving end; the middleware is a component between the sending end and the receiving end, and both the sending end and the receiving end can access the data stored in the middleware;

[0041] Obtain the industrial identification code sent by the middleware;

[0042] Establish a first correspondence between the first device code and the acquired industrial identification code.

[0043] In one implementation, the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes. The device also includes a first detection module, which is used to determine that the device represented by the industrial identification code is a potentially faulty device if the target industrial identification code matches the industrial identification code of the faulty device.

[0044] According to a fifth aspect of the embodiments of this application, a device code determination apparatus is provided, applied to a transmitting end, wherein the transmitting end pre-stores a second correspondence between a second device code and an industrial identification code, each of the second device codes being a private identification code assigned to a device by the platform to which the transmitting end belongs, and the industrial identification code being a public identification code assigned to a device by any platform, the apparatus comprising:

[0045] The second determining module is used to determine the target industrial identification code, wherein the target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship;

[0046] The sending module is used to send the target industrial identification code to the receiving end, so that the receiving end can determine the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and use it as the first target device code; the receiving end pre-stores the first correspondence relationship between the first device code and the industrial identification code, and each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs.

[0047] In one embodiment, the device further includes a fourth acquisition module for acquiring the device's second device code and industrial identification code;

[0048] Establish a second correspondence between the second device code and the industrial identification code.

[0049] In one embodiment, the device further includes a fifth acquisition module, used to acquire the industrial identification code and the device serial number (SN) of the equipment; the device SN is a unique identifier for the equipment.

[0050] Establish a third correspondence between the industrial identification code and the equipment serial number;

[0051] The third correspondence is saved in the middleware so that the receiving end can establish the first correspondence based on the third correspondence stored in the middleware.

[0052] In one implementation, the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes. The device also includes a second detection module, which is used to determine that the device represented by the industrial identification code is a potentially faulty device if the target industrial identification code matches the industrial identification code of the faulty device.

[0053] According to a fifth aspect of the embodiments of this application, an electronic device is provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0054] Memory, used to store computer programs;

[0055] When a processor executes a program stored in memory, it implements the steps of the method described in either the first or second aspect above.

[0056] According to a sixth aspect of the embodiments of this application, a device code determination device is provided, including a processor and a machine-readable storage medium, the machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being prompted by the machine-executable instructions to perform the steps of the method described in either the first or second aspect above.

[0057] According to a seventh aspect of the embodiments of this application, a computer-readable storage medium is provided, characterized in that the computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the method described in either the first or second aspect above. Attached Figure Description

[0058] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings.

[0059] Figure 1 A flowchart illustrating the device code determination method applied to the receiving end provided in an embodiment of this application;

[0060] Figure 2 A schematic diagram of the process for storing the first correspondence relationship on the platform to which the receiving end belongs, provided in an embodiment of this application;

[0061] Figure 3 A schematic diagram illustrating another process for storing the first correspondence relationship on the platform to which the receiving end belongs, provided in an embodiment of this application;

[0062] Figure 4 A flowchart illustrating the device code determination method applied to the sending end provided in an embodiment of this application;

[0063] Figure 5a A schematic diagram of the device code determination system provided in this application embodiment;

[0064] Figure 5b A schematic diagram illustrating the working principle of the device code determination system provided in this application embodiment;

[0065] Figure 6 This is a schematic diagram of the device code determination device applied to the receiving end provided in an embodiment of this application;

[0066] Figure 7 This is a schematic diagram of the device code determination device applied to the transmitting end provided in an embodiment of this application;

[0067] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0068] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. 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 based on this application are within the scope of protection of the present invention.

[0069] To more clearly illustrate the device code determination method provided in the embodiments of this application, the following will provide an exemplary description of a possible application scenario of the device code determination method provided in this application. It should be understood that the following example is only one possible application scenario of the device code determination method provided in the embodiments of this application. In other possible embodiments, the device code determination method provided in the embodiments of this application can also be applied to other possible application scenarios. The following example does not impose any limitations on this.

[0070] The operator purchases multiple devices with different parameters from the manufacturer, referred to as devices 1-N. It is assumed that the operator configures device codes ABC1, ABC2, ..., ABCN for devices 1-N respectively, and the manufacturer configures device codes DEF1, DEF2, ..., DEFN for devices 1-N respectively.

[0071] For operational and maintenance needs, the operator requires maintenance of device 1 and therefore needs to obtain technical support for device 1 from the manufacturer. However, because the device codes configured by the operator and the manufacturer are considered their respective privacy settings, the operator cannot inform the manufacturer which device codes ABC1-N represent, and similarly, the manufacturer cannot inform the operator which device codes DEF1-N represent. This lack of a unified device identifier during communication between the operator and the manufacturer makes it difficult for the operator to inform the manufacturer which device's technical support they need, meaning the operator cannot obtain technical support for device 1 from the manufacturer.

[0072] Based on this, this application provides a method for determining a device code, such as... Figure 1As shown, the method is applied to a receiving end, which can be an electronic device, such as a mobile phone or computer, and can correspond to the operator described above. Any entity that can implement the functions of the receiving end in this application can be the receiving end of this application, and no limitations are made in this application. The receiving end pre-stores a first correspondence between a first device code and an industrial identification code. Each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs, and the industrial identification code is a public identification code assigned to the device by any platform. The method includes:

[0073] S101. Obtain the target industrial identification code sent by the sending end. The sending end has a second correspondence between the second device code and the industrial identification code stored in advance. The target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence. The second device code is a private identification code assigned to the device by the platform to which the sending end belongs.

[0074] S102. Based on the first correspondence, determine the first equipment code corresponding to the target industrial identification code, and use it as the first target equipment code.

[0075] In this embodiment, the first and second correspondences between the first device code, the second device code, and the industrial identification code are stored at the receiving end and the sending end, respectively. By defining the asymmetric encoding, the industrial identification code of the device is determined through the second correspondence. Based on the first correspondence, the first device code corresponding to the industrial identification code is determined as the target device code. Thus, while protecting the internal private code, the problem of accuracy of description and timeliness of communication between the receiving end and the sending end is solved by identifying the public code.

[0076] Taking the aforementioned exemplary application scenario as an example, the first device codes of devices 1-N within the receiving end are ABC1, ABC2, ..., ABCN, and the second device codes of devices 1-N within the sending end are DEF1, DEF2, ..., DEFN. If the sending end and the receiving end communicate directly, the device codes of devices 1-N are different on different platforms because the device codes of devices 1-N are kept confidential across different platforms. This makes cross-platform communication very difficult due to the different device codes, requiring a high level of technical expertise from the personnel. In this embodiment, before cross-platform communication, an industrial identification code M1, M2, ..., MN is registered for devices 1-N. The receiving end stores the first correspondence between the industrial identification codes M1, M2, ..., MN and the first device codes ABC1, ABC2, ..., ABCN, and the sending end stores the second correspondence between the industrial identification codes M1, M2, ..., MN and the second device codes DEF1, DEF2, ..., DEFN. When the receiving end and the sending end need to communicate based on device 1, technician A at the sending end inputs the second device code DEF1 used by device 1 on the sending end platform. Based on the second correspondence, the industrial identification code corresponding to the second device code DEF is determined to be M1. M1 is identified as the target industrial identification code, and the target industrial identification code M1 is sent to the receiving end. Based on the first correspondence, the receiving end determines the first device code ABC1 within the receiving end platform for the target identification code M1. Therefore, ABC1 can be used to identify the device corresponding to device 1 at the receiving end. Because the receiving end and the sending end communicate through industrial identification codes, with the receiving end using the first device code and the sending end using the second device code, the receiving end and the sending end can quickly locate the same device without compromising confidentiality. This addresses the issues of accurate description and timely communication between the receiving end and the sending end.

[0077] The following will provide a detailed explanation of the aforementioned steps S101-S102:

[0078] In S101, the receiving end obtains the target industrial identification code sent by the sending end by having the sending end directly send the confirmed target industrial identification code to the communication component, and the receiving end obtains the target industrial identification code from the industrial component. The communication component is the platform for communication between the sending end and the receiving end. The sending end can be any electronic device, such as a computer or mobile phone, and can correspond to the manufacturers described above. Any entity that can implement the functions of the sending end in this application can be the sending end of this application, and no limitations are made in this application.

[0079] Taking the aforementioned exemplary application scenario as an example, after the sending end confirms the target industrial identification code M1 of device 1, it sends M1 to the communication component, and the receiving end obtains the target industrial identification code M1 from the communication component. This application does not limit the specific steps for obtaining the target industrial identification code.

[0080] In S102, the private identifier is an identifier used for internal communication within any platform. It is meaningful only within the platform, and other platforms do not know the meaning of the identifier. For example, the first device code of devices 1-N in the receiving end is ABC1, ABC2, ..., ABCN, and the second device code of devices 1-N in the sending end is DEF1, DEF2, ..., DEFN.

[0081] A public identifier is a public code set up by any platform for communication between platforms. It is an identifier that allows communication between different platforms. This public identifier refers to the same item on each platform, and each platform understands the meaning of the identifier. For example, as mentioned above, an industrial identifier M1, M2, ..., MN is registered for devices 1-N. Both the receiving end and the sending end know the devices identified by M1, M2, ..., MN within their respective internal systems.

[0082] Taking the exemplary application scenario as an example, after the receiving end obtains the industrial identification code M1, it finds the first device code ABC1 corresponding to the industrial identification code M1 according to the pre-stored first correspondence relationship. The first device code ABC1 is the first target device code.

[0083] In one possible implementation, before determining the device code, the receiving platform pre-stores the mapping between industrial identification codes and the platform's internal private identification codes. For example... Figure 2 As shown, the specific platform's process of storing the corresponding relationships includes:

[0084] S201. Obtain the first device code and industrial identification code of the device.

[0085] In this step, the receiving end will pre-register a first device code for each device used internally by the receiving end's platform. For example, for devices 1-3, the receiving end will register a first device code for each device within the platform, with the first device code for device 1 being ABC1, the first device code for device 2 being ABC2, and the first device code for device 3 being ABC3.

[0086] The industrial identification code is generated by the sending end and then directly sent to the receiving end. For example, the sending end generates industrial identification codes M1 for device 1, M2 for device 2, and M3 for device 3, and then directly sends the industrial identification codes M1 for device 1, M2 for device 2, and M3 for device 3 to the receiving end.

[0087] S202. Establish a first correspondence between the first device code and the industrial identification code.

[0088] In this step, after receiving the industrial identification code, the receiving end establishes a first correspondence between the first device code and the industrial identification code of each device, and then saves the first correspondence to the communication component. For example, after receiving the industrial identification code M1 of device 1, the industrial identification code M2 ​​of device 2, and the industrial identification code M3 of device 3, it establishes the first correspondence 1: ABC1-M1, the first correspondence 2: ABC2-M2, and the first correspondence 3: ABC3-M3, and then saves the first correspondences 1-3 to the communication component of the receiving end.

[0089] As can be seen, in this embodiment, before determining the device code through subsequent cross-platform communication, the receiving end registers and generates a first device code for each device, which is then used internally by the receiving end platform. This first correspondence is established with the industrial identification codes of each device received from the sending end, and the first correspondence is saved in the communication component on the receiving end side. This allows the receiving end to use the first device code corresponding to the target industrial identification code as the first target device code after receiving the target industrial identification code from the subsequent sending end, based on the first correspondence. This achieves the goal of solving the problems of accuracy and timeliness of communication between the receiving and sending ends by using a public identification code while protecting the internal private code.

[0090] In another possible approach, the receiving end can also determine the industrial identification code based on a third correspondence. This third correspondence is the mapping between the industrial identification code and the device serial number (SN), where each SN is a unique identifier for each device. Specific steps are as follows... Figure 3 As shown:

[0091] S301. Obtain the first device code of the device, which carries the device SN code.

[0092] In this step, when the receiving end generates the first device code for each device, the first device code carries the device SN code of that device, which can uniquely identify the device. For example, for device 1, device 2, and device 3, the receiving end will register a first device code for each device within the platform. The first device code for device 1 is ABC1, which carries the device SN code a1; the first device code for device 2 is ABC2, which carries the device SN code a2; and the first device code for device 3 is ABC3, which carries the device SN code a3.

[0093] S302. Send the device SN code to the middleware, so that the middleware determines the industrial identification code corresponding to the device SN code according to the third correspondence between the SN code and the industrial identification code stored in the middleware in advance, and sends the determined industrial identification code to the receiving end; the middleware is a component between the sending end and the receiving end, and both the sending end and the receiving end can access the data stored in the middleware.

[0094] In this step, after generating the industrial identification code for each device, the sending end stores the third correspondence between the industrial identification code and the device serial number (SN) code in the middleware. This allows the receiving end to determine the industrial identification code corresponding to the device SN code based on the third correspondence from the middleware, and then send it to the receiving end. For example, if the device SN code for device 1 is a1, the device SN code for device 2 is a2, and the device SN code for device 3 is a3, the sending end generates the industrial identification code for device 1 as M1, the industrial identification code for device 2 as M2, and the industrial identification code for device 3 as M3, and establishes the third correspondence between the SN code and the industrial identification code for each device. The third correspondence is: Third Correspondence 1: a1-M1, Third Correspondence 2: a2-M2, Third Correspondence 3: a3-M3, and the third correspondence is saved to the middleware.

[0095] After generating the first device code for each device at the receiving end, the device serial number (SN) carried by the first device code can be sent to the middleware. Then, the middleware determines the industrial identification code corresponding to the device SN code based on the pre-stored third correspondence. For example, if it is determined that device SN code a1 in the first device code ABC1 corresponds to industrial identification code M1, then M1 is the industrial identification code of device 1. If it is determined that device SN code a2 in the first device code ABC2 corresponds to industrial identification code M2, then M2 is the industrial identification code of device 2. If it is determined that device SN code a3 in the first device code ABC3 corresponds to industrial identification code M3, then M3 is the industrial identification code of device 3. The industrial identification codes M1-M3 determined for devices 1-3 are then sent to the receiving end.

[0096] S303. Obtain the industrial identification code sent by the middleware and establish a first correspondence between the first device code and the obtained industrial identification code.

[0097] In this step, after obtaining the industrial identification codes of each device, a first correspondence is established between the first device code and the industrial identification code of each device, and then this first correspondence is saved to the communication component. For example, after obtaining the industrial identification codes M1, M2, and M3 of device 1, a first correspondence 1 is established: ABC1-M1, a first correspondence 2 is established: ABC2-M2, and a first correspondence 3 is established: ABC3-M3. Then, the first correspondences 1-3 are saved to the communication component of the receiving end.

[0098] As can be seen, in this embodiment, before determining the device code through subsequent cross-platform communication, the receiving end registers and generates a first device code for each device, which is used internally by the receiving end platform. This first device code carries a unique device serial number (SN) that identifies the device. Then, based on a third correspondence, the industrial identification code for each device is determined, establishing a first correspondence between the first device code and the determined industrial identification code. This first correspondence is saved in the communication component on the receiving end side. This allows the receiving end to use the first device code corresponding to the target industrial identification code as the first target device code after receiving the target industrial identification code sent by the sending end. The third correspondence is a relationship pre-stored by the sending end in middleware, facilitating the correspondence between the device SN code and the industrial identification code used by various platforms. This approach solves the problems of accuracy and timeliness of communication between the receiving and sending ends by using a public identification code while protecting internal private codes.

[0099] In another feasible implementation, the specific process for generating industrial identification codes is as follows:

[0100] Step a1: Obtain the device's attribute information.

[0101] Equipment attribute information can represent basic attributes of the equipment during its production, such as equipment classification code, equipment object code, equipment safety code, etc. Take equipment A as an example. Assume equipment A has an equipment object code of 6532, is manufactured by Sony, has a equipment classification code of UPF, a production date of February 2, 2022, a production address in Beijing, and a safety code of yy.

[0102] Step a2: Generate industrial identification codes based on attribute information.

[0103] After obtaining the device's attribute information, the attribute information can be sorted according to a preset order to generate the device's industrial identification code. The preset order can be random or based on importance. For example, after obtaining the attribute information of device A, randomly sorting the attribute information yields an identification code: 20220202.UPF6532.Sony.BJ.yy. This identification code 20220202.UPF6532.Sony.BJ.yy is used as the industrial identification code for device A.

[0104] In this embodiment, an industrial identification code for the device is generated based on its attribute information. This allows for communication between platforms. Externally, the interaction is conducted using the industrial identification code (public code), while internally, the platform uses its internal private code. This approach protects the internal private code while addressing the issues of accuracy and timeliness in communication between the receiving and sending ends. Furthermore, since the industrial identification code reflects the device's attribute information, its basic information can be determined, enabling technicians to quickly interpret this information.

[0105] In one feasible approach, the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes. After obtaining the target industrial identification code, the device can be inspected based on the industrial identification code to promptly detect potential quality defects in the device, hereinafter referred to as potentially faulty equipment, and take corresponding measures in a timely manner. Following S101-S102 above, the method further includes:

[0106] S103. If the target industrial identification code matches the industrial identification code of the faulty equipment, then the equipment represented by the industrial identification code is determined to be a potentially faulty equipment.

[0107] In this step, after obtaining the target industrial identification code, the target industrial identification code can be tested based on the attribute information it represents to determine whether the target identification code contains any attribute information related to the industrial identification code of a known defective device. For example, if the target industrial identification code M1 is 20220202.UPF6532.Sony.BJ.yy, and it is known that on February 2, 2022, a batch of 6532 type UPF equipment from Beijing malfunctioned, meaning that part of the industrial identification code of the malfunctioning equipment is 20220202.UPF6532.BJ, and the attribute information of the target industrial identification code M1 includes 20220202.UPF6532.BJ, then it indicates that the equipment corresponding to the target industrial identification code M1 may have a quality defect and is a potentially faulty device.

[0108] When a target industrial identifier code is determined to match the industrial identifier code of a faulty device, the device corresponding to the target industrial identifier code is identified as a potentially faulty device. For example, if device 1 corresponding to the target industrial identifier code M1 is identified as a potentially faulty device, the target industrial identifier code M1 can be highlighted in red to alert users that the device corresponding to the target industrial identifier code M1 may have a quality problem. In addition, other countermeasures can be taken based on the potentially faulty device, which will not be elaborated on in this embodiment.

[0109] In this embodiment of the application, since the industrial identification code can reflect the attribute information of the equipment, the basic information of the equipment can be determined by the industrial identification code. When it is determined that a certain batch of equipment has quality defects, after obtaining the target industrial identification code, the potential faulty equipment can be screened out by detecting the industrial identification code through the attribute information of the same batch, and corresponding countermeasures can be taken to prevent problems before they occur. This allows technicians to maintain the equipment in a timely manner and reduce the cost of maintaining the equipment.

[0110] like Figure 4 As shown, a device code determination method is applied at a sending end. The sending end pre-stores a second correspondence between a second device code and an industrial identification code. Each second device code is a private identification code assigned to the device by the platform to which the sending end belongs, and the industrial identification code is a public identification code assigned to the device by any platform. The method includes:

[0111] S401. Determine the target industrial identification code. The target industrial identification code is the industrial identification code corresponding to the target second device code obtained by the sending end in response to the input target second device code according to the second correspondence relationship. The second device code is the private identification code assigned to the device by the platform to which the sending end belongs.

[0112] S402. Send the target industrial identification code to the receiving end so that the receiving end can determine the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and use it as the first target device code; the receiving end has a first correspondence relationship between the first device code and the industrial identification code in advance, and each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs.

[0113] As can be seen, in this embodiment, the first and second correspondences between the first device code, the second device code, and the industrial identification code are stored at the receiving end and the sending end, respectively. The sending end first determines the corresponding target industrial identification code through the input target second device code, and then sends the target industrial identification code to the receiving end, so that the receiving end can determine the first device code corresponding to the target industrial identification code according to the first correspondence, and use it as the first target device code. Through the definition of asymmetric encoding, the platform uses internal private codes for business operations, namely the first device code and the second device code, and external collaboration uses public identification codes for communication, namely the industrial identification code. Thus, while protecting the internal private codes, the problem of accuracy of description and timeliness of communication between the receiving end and the sending end can be solved by using public identification codes.

[0114] The following will provide a detailed explanation of the aforementioned steps S401-S402:

[0115] In S401, technicians can input the target second device code through the communication component of the sending end, and the sending end can determine the target industrial identification code corresponding to the target second device code through the second correspondence.

[0116] Taking device 1 as an example, if the technicians at the sending end need to understand the usage information of device 1 from the receiving end in order to understand device 1 or accurately provide it with device parameters, they can input the second device code DEF1 of device 1 inside the sending end in the communication component of the sending end. The sending end can determine the industrial identification code corresponding to DEF1 as M1 based on the second correspondence, and then determine M1 as the target industrial identification code.

[0117] In S402, the sending end can directly send the target industrial identification code to the receiving end, or it can send the target industrial identification code to the communication component. This allows the receiving end to obtain the target industrial identification code, and after obtaining it, determine the corresponding target first device code based on the target industrial identification code. Then, it feeds back the information of the device corresponding to the target first device code to the technicians at the sending end. For example, in the above embodiment, the sending end sends the target industrial identification code M1 to the receiving end. The receiving end determines the target first device code as ABC1 based on the target industrial identification code M and the first correspondence pre-stored at the receiving end. The device corresponding to ABC1 is device 1. Subsequently, the technicians at the receiving end can feed back the information of device 1 to the technicians at the sending end, so that the technicians at the sending end can understand the information of device 1 and then perform relevant operations on device 1.

[0118] In one feasible approach, before determining the device code, the platform to which the sending end belongs will pre-store the mapping relationship between the industrial identification code and the platform's internal private identification code. The specific process of the platform storing this mapping relationship includes:

[0119] Step b1: Obtain the device's second device code and industrial identification code.

[0120] Step b2: Establish a second correspondence between the second equipment code and the industrial identification code.

[0121] The specific implementation steps are similar to those in S201 and S202 mentioned above, so they will not be elaborated on here.

[0122] As can be seen, in this embodiment, before determining the device code through subsequent cross-platform communication, the sending end registers and generates a second device code for each device, which is then used internally by the sending end platform. This second device code is then established with the industrial identification codes of each device generated by the sending end, and the second correspondence is saved in the communication component on the sending end side. This allows the sending end to subsequently determine the corresponding target industrial identification code based on the input target second device code. The target industrial identification code is then sent to the receiving end, enabling the receiving end to determine the first device code corresponding to the target industrial identification code based on the first correspondence, which is then used as the first target device code. This approach achieves the goal of solving the problems of accuracy and timeliness of communication between the receiving end and the sending end by using a public identification code while protecting the internal private code.

[0123] In another feasible embodiment, the sending end can also store a third correspondence between the industrial identification code and the device serial number in middleware, so that the receiving end can establish a first correspondence based on the third correspondence stored in the middleware. The specific steps are as follows:

[0124] Step c1: Obtain the industrial identification code and equipment serial number (SN) of the equipment; the equipment SN is a unique identifier for the equipment.

[0125] Step c2: Establish a third correspondence between the industrial identification code and the equipment SN code.

[0126] Step c3: Save the third correspondence to the middleware so that the receiving end can establish the first correspondence based on the third correspondence stored in the middleware.

[0127] The specific steps for the receiving end to establish the first correspondence using the third correspondence are similar to the specific implementation steps of S302 mentioned above, so they will not be elaborated on here.

[0128] As can be seen, in this embodiment, before determining the device code through subsequent cross-platform communication, the sending end registers and generates an industrial identification code for each device, obtains the device serial number (SN) code for each device, establishes a third correspondence between the industrial identification code and the device SN code, and sends this third correspondence to the middleware. This allows the receiving end to determine the industrial identification code for each device based on the third correspondence, establish a first correspondence between the first device code for each device and the determined industrial identification code, and save this first correspondence in the communication component on the receiving end's side. This is so that after receiving the target industrial identification code sent by the subsequent sending end, the receiving end can use the first device code corresponding to the target industrial identification code as the first target device code based on the first correspondence. The third correspondence is a mapping between the device SN code and the industrial identification code that the sending end stores in the middleware beforehand, facilitating use by various platforms. This achieves the goal of solving the problems of accuracy and timeliness of communication between the receiving end and the sending end by using a public identification code while protecting internal private codes.

[0129] In one feasible approach, the industrial identification code is a public identification code assigned to equipment by any platform based on its attributes. After determining the target industrial identification code, the equipment can be inspected based on this code to promptly identify potential quality defects (hereinafter referred to as potentially faulty equipment) and take appropriate measures. The specific steps are as follows:

[0130] If the target industrial identification code matches the industrial identification code of the faulty equipment, then the equipment represented by the industrial identification code is determined to be a potentially faulty equipment.

[0131] The specific implementation steps are similar to those of S103 mentioned above, so they will not be elaborated on here.

[0132] In this embodiment of the application, since the industrial identification code can reflect the attribute information of the equipment, the basic information of the equipment can be determined by the industrial identification code. When it is determined that a certain batch of equipment has quality defects, after obtaining the target industrial identification code, the potential faulty equipment can be screened out by detecting the industrial identification code through the attribute information of the same batch, and corresponding countermeasures can be taken to prevent problems before they occur. This allows technicians to maintain the equipment in a timely manner and reduce the cost of maintaining the equipment.

[0133] like Figure 5aAs shown in the figure, this application provides a device code determination system, which includes a sending end and a receiving end. The receiving end pre-stores a first correspondence between a first device code and an industrial identification code. Each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs, and the industrial identification code is a public identification code assigned to the device by any platform. The sending end pre-stores a second correspondence between a second device code and an industrial identification code. The second device code is a private identification code assigned to the device by the platform to which the sending end belongs.

[0134] The working principle of the device code determination system is as follows: Figure 5b As shown, it includes:

[0135] S501. The sending end determines the target industrial identification code and sends the target industrial identification code to the receiving end. The target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship.

[0136] S502. The receiving end obtains the target industrial identification code sent by the sending end, and determines the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and uses it as the first target device code.

[0137] As can be seen, in this embodiment, the first and second correspondences between the first device code, the second device code, and the industrial identification code are stored at the receiving end and the sending end, respectively. By defining the asymmetric encoding, the industrial identification code of the device is determined through the second correspondence. Based on the first correspondence, the first device code corresponding to the industrial identification code is determined as the target device code. Thus, while protecting the internal private code, the problem of accuracy of description and timeliness of communication between the receiving end and the sending end is solved by identifying the public code.

[0138] Corresponding to the aforementioned device code determination method, this application also provides a device code determination apparatus applied at a receiving end. The receiving end pre-stores a first correspondence between a first device code and an industrial identifier code. Each first device code is a private identifier code assigned to a device by the platform to which the receiving end belongs. The industrial identifier code is a public identifier code assigned to a device by any platform, such as... Figure 6 As shown, it includes:

[0139] The first acquisition module 601 is used to acquire the target industrial identification code sent by the sending end. The sending end pre-stores a second correspondence relationship between the second device code and the industrial identification code. The target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship. The second device code is a private identification code assigned to the device by the platform to which the sending end belongs.

[0140] The first determining module 602 is used to determine the first device code corresponding to the target industrial identification code based on the first correspondence relationship, and use it as the first target device code.

[0141] In one embodiment, the device further includes a second acquisition module 603, used to acquire the device's first device code and industrial identification code;

[0142] Establish a first correspondence between the first device code and the industrial identification code.

[0143] In one embodiment, the device further includes a third acquisition module 604, used to acquire a first device code of the device, wherein the first device code carries a device serial number (SN).

[0144] The device SN code is sent to the middleware, so that the middleware determines the industrial identification code corresponding to the device SN code according to the third correspondence between the SN code and the industrial identification code stored in the middleware in advance, and sends the determined industrial identification code to the receiving end; the middleware is a component between the sending end and the receiving end, and both the sending end and the receiving end can access the data stored in the middleware;

[0145] Obtain the industrial identification code sent by the middleware;

[0146] Establish a first correspondence between the first device code and the acquired industrial identification code.

[0147] In one implementation, the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes. The device also includes a first detection module 605, which is used to determine that the device represented by the industrial identification code is a potentially faulty device if the target industrial identification code matches the industrial identification code of the faulty device.

[0148] Corresponding to the aforementioned device code determination method, this application also provides a device code determination apparatus applied at a transmitting end. The transmitting end pre-stores a second correspondence between a second device code and an industrial identifier code. Each second device code is a private identifier code assigned to the device by the platform to which the transmitting end belongs. The industrial identifier code is a public identifier code assigned to the device by any platform, such as... Figure 7 The following are included:

[0149] The second determining module 701 is used to determine the target industrial identification code, wherein the target industrial identification code is the industrial identification code corresponding to the target second device code obtained by the sending end in response to the input target second device code according to the second correspondence relationship;

[0150] The sending module 702 is used to send the target industrial identification code to the receiving end, so that the receiving end determines the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and uses it as the first target device code; the receiving end pre-stores the first correspondence relationship between the first device code and the industrial identification code, and each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs.

[0151] In one embodiment, the device further includes a fourth acquisition module 703, used to acquire the device's second device code and industrial identification code;

[0152] Establish a second correspondence between the second device code and the industrial identification code.

[0153] In one embodiment, the device further includes a fifth acquisition module 704, used to acquire the industrial identification code and the device serial number (SN) of the equipment; the device SN is a unique identifier for the equipment.

[0154] Establish a third correspondence between the industrial identification code and the equipment serial number;

[0155] The third correspondence is saved in the middleware so that the receiving end can establish the first correspondence based on the third correspondence stored in the middleware.

[0156] In one implementation, the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes. The device also includes a second detection module 705, which is used to determine that the device represented by the industrial identification code is a potentially faulty device if the target industrial identification code matches the industrial identification code of the faulty device.

[0157] This invention also provides an electronic device that can function as either the aforementioned receiver or the aforementioned transmitter. The structure of the electronic device is as follows: Figure 8 As shown, it includes a processor 801, a communication interface 802, a memory 803, and a communication bus 804. The processor 801, communication interface 802, and memory 803 communicate with each other via the communication bus 804.

[0158] Memory 803 is used to store computer programs;

[0159] When the processor 801 executes the program stored in the memory 803, if the electronic device acts as a receiving end, the following steps are implemented:

[0160] The sender obtains the target industrial identification code sent by the sender. The sender has a second correspondence between the second device code and the industrial identification code stored in advance. The target industrial identification code is the industrial identification code corresponding to the target second device code that the sender determines in response to the input target second device code according to the second correspondence. The second device code is a private identification code assigned to the device by the platform to which the sender belongs.

[0161] Based on the first correspondence, the first device code corresponding to the target industrial identification code is determined as the first target device code.

[0162] If the electronic device is used as the transmitter, the following steps are performed:

[0163] Determine the target industrial identification code, which is the industrial identification code corresponding to the target second device code obtained by the sending end in response to the input target second device code according to the second correspondence relationship;

[0164] The target industrial identification code is sent to the receiving end, so that the receiving end determines the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and uses it as the first target device code; the receiving end pre-stores the first correspondence relationship between the first device code and the industrial identification code, and each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs.

[0165] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0166] The communication interface is used for communication between the aforementioned electronic devices and other devices.

[0167] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0168] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0169] In another embodiment of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and when the computer program is executed by a processor, it implements the steps of any of the above-described device code determination methods.

[0170] In another embodiment of the present invention, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute any of the device code determination methods described above.

[0171] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0172] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0173] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, embodiments of devices, systems, electronic devices, computer-readable storage media, and computer program products are basically similar to the method embodiments, and therefore the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0174] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.

Claims

1. A method for determining a device code, characterized in that, Applied to a receiving end, the receiving end pre-stores a first correspondence between a first device code and an industrial identifier code, each of the first device codes being a private identifier code assigned to the device by the platform to which the receiving end belongs, and the industrial identifier code being a public identifier code assigned to the device by any platform. The method includes: The sender obtains the target industrial identification code sent by the sender. The sender has a second correspondence between the second device code and the industrial identification code stored in advance. The target industrial identification code is the industrial identification code corresponding to the target second device code that the sender determines in response to the input target second device code according to the second correspondence. The second device code is a private identification code assigned to the device by the platform to which the sender belongs. Based on the first correspondence, the first device code corresponding to the target industrial identification code is determined as the first target device code.

2. The method according to claim 1, further comprising: Obtain the device's first equipment code and industry identification code; Establish a first correspondence between the first device code and the industrial identification code.

3. The method according to claim 2, further comprising: Obtain the first device code of the device, which carries the device SN code; The device SN code is sent to the middleware, so that the middleware determines the industrial identification code corresponding to the device SN code according to the third correspondence between the SN code and the industrial identification code stored in the middleware in advance, and sends the determined industrial identification code to the receiving end; the middleware is a component between the sending end and the receiving end, and both the sending end and the receiving end can access the data stored in the middleware; Obtain the industrial identification code sent by the middleware; Establish a first correspondence between the first device code and the acquired industrial identification code.

4. The method according to claim 1, wherein the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes, and the method further includes: If the target industrial identification code matches the industrial identification code of the faulty equipment, then the equipment represented by the industrial identification code is determined to be a potentially faulty equipment.

5. A method for determining a device code, characterized in that, Applied to a transmitting end, the transmitting end pre-stores a second correspondence between a second device code and an industrial identifier code. Each second device code is a private identifier code assigned to the device by the platform to which the transmitting end belongs. The industrial identifier code is a public identifier code assigned to the device by any platform. The method includes: Determine the target industrial identification code, which is the industrial identification code corresponding to the target second device code obtained by the sending end in response to the input target second device code according to the second correspondence relationship; The target industrial identification code is sent to the receiving end, so that the receiving end determines the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and uses it as the first target device code; the receiving end pre-stores the first correspondence relationship between the first device code and the industrial identification code, and each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs.

6. The method according to claim 5, further comprising: Obtain the device's second equipment code and industrial identification code; Establish a second correspondence between the second device code and the industrial identification code.

7. The method according to claim 5, further comprising: Obtain the industrial identification code and equipment serial number of the equipment; The device SN code is a unique identifier for the device; Establish a third correspondence between the industrial identification code and the equipment serial number; The third correspondence is saved in the middleware so that the receiving end can establish the first correspondence based on the third correspondence stored in the middleware.

8. The method according to claim 5, wherein the industrial identification code is a public identification code assigned to the device by any platform based on the device's attributes, and the method further includes: If the target industrial identification code matches the industrial identification code of the faulty equipment, then the equipment represented by the industrial identification code is determined to be a potentially faulty equipment.

9. A device code determination system, characterized in that, The system includes a transmitter and a receiver, wherein: The receiving end pre-stores a first correspondence between a first device code and an industrial identifier code, wherein each first device code is a private identifier code assigned to the device by the platform to which the receiving end belongs, and the industrial identifier code is a public identifier code assigned to the device by any platform; the sending end pre-stores a second correspondence between a second device code and an industrial identifier code, wherein the second device code is a private identifier code assigned to the device by the platform to which the sending end belongs. The sending end is used to determine the target industrial identification code and send the target industrial identification code to the receiving end. The target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship. The receiving end is used to obtain the target industrial identification code sent by the sending end, and determine the first device code corresponding to the target industrial identification code according to the first correspondence relationship, as the first target device code.

10. A device code determination apparatus, characterized in that, Applied to a receiving end, the receiving end pre-stores a first correspondence between a first device code and an industrial identification code, each of the first device codes being a private identification code assigned to the device by the platform to which the receiving end belongs, and the industrial identification code being a public identification code assigned to the device by any platform. The device includes: The first acquisition module is used to acquire the target industrial identification code sent by the sending end. The sending end pre-stores a second correspondence relationship between the second device code and the industrial identification code. The target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship. The second device code is a private identification code assigned to the device by the platform to which the sending end belongs. The first determining module is used to determine the first device code corresponding to the target industrial identification code based on the first correspondence relationship, and use it as the first target device code.

11. The apparatus according to claim 10, characterized in that, The device further includes a second acquisition module for acquiring the device's first equipment code and industrial identification code; Establish a first correspondence between the first device code and the industrial identification code.

12. The apparatus according to claim 11, characterized in that, The device further includes a third acquisition module for acquiring a first device code of the device, wherein the first device code carries a device SN code. The device SN code is sent to the middleware, so that the middleware determines the industrial identification code corresponding to the device SN code according to the third correspondence between the SN code and the industrial identification code stored in the middleware in advance, and sends the determined industrial identification code to the receiving end; the middleware is a component between the sending end and the receiving end, and both the sending end and the receiving end can access the data stored in the middleware; Obtain the industrial identification code sent by the middleware; Establish a first correspondence between the first device code and the acquired industrial identification code.

13. The apparatus according to claim 10, characterized in that, The industrial identification code is a public identification code assigned to a device by any platform based on the device's attributes. The device also includes a first detection module, which is used to determine that the device represented by the industrial identification code is a potentially faulty device if the target industrial identification code matches the industrial identification code of the faulty device.

14. A device code determination apparatus, characterized in that, Applied to a transmitting end, the transmitting end pre-stores a second correspondence between a second device code and an industrial identification code. Each second device code is a private identification code assigned to the device by the platform to which the transmitting end belongs. The industrial identification code is a public identification code assigned to the device by any platform. The device includes: The second determining module is used to determine the target industrial identification code, wherein the target industrial identification code is the industrial identification code corresponding to the target second device code determined by the sending end in response to the input target second device code according to the second correspondence relationship; The sending module is used to send the target industrial identification code to the receiving end, so that the receiving end can determine the first device code corresponding to the target industrial identification code according to the first correspondence relationship, and use it as the first target device code; the receiving end pre-stores the first correspondence relationship between the first device code and the industrial identification code, and each first device code is a private identification code assigned to the device by the platform to which the receiving end belongs.

15. The apparatus according to claim 14, further comprising a fourth acquisition module for acquiring a second device code and an industrial identification code of the device; Establish a second correspondence between the second device code and the industrial identification code.

16. The apparatus according to claim 15, further comprising a fifth acquisition module, configured to acquire the industrial identification code and the device serial number (SN) of the equipment; the device SN is a unique identifier for the equipment; Establish a third correspondence between the industrial identification code and the equipment serial number; The third correspondence is saved in the middleware so that the receiving end can establish the first correspondence based on the third correspondence stored in the middleware.

17. The apparatus according to claim 14, characterized in that, The industrial identification code is a public identification code assigned to a device by any platform based on the device's attributes. The device also includes a second detection module, which is used to determine that the device represented by the industrial identification code is a potentially faulty device if the target industrial identification code matches the industrial identification code of the faulty device.

18. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the method according to any one of claims 1-4 or 5-8.

19. A device code determination device, characterized in that, The method includes a processor and a machine-readable storage medium storing machine-executable instructions that can be executed by the processor, the processor being prompted by the machine-executable instructions to perform the method of any one of claims 1-4 or 5-8.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method described in any one of claims 1-4 or 5-8.

Images