WO2021218966A1 - 设备检测方法、装置、设备、***、存储介质及程序产品 - Google Patents

设备检测方法、装置、设备、***、存储介质及程序产品 Download PDF

Info

Publication number
WO2021218966A1
WO2021218966A1 PCT/CN2021/090255 CN2021090255W WO2021218966A1 WO 2021218966 A1 WO2021218966 A1 WO 2021218966A1 CN 2021090255 W CN2021090255 W CN 2021090255W WO 2021218966 A1 WO2021218966 A1 WO 2021218966A1
Authority
WO
WIPO (PCT)
Prior art keywords
identity
detected
server
tested
credible
Prior art date
Application number
PCT/CN2021/090255
Other languages
English (en)
French (fr)
Inventor
辛耀东
张纯锋
王正涛
宋军
马百义
楼江辉
宋学武
Original Assignee
青岛海尔滚筒洗衣机有限公司
杭州甘道智能科技有限公司
海尔智家股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 青岛海尔滚筒洗衣机有限公司, 杭州甘道智能科技有限公司, 海尔智家股份有限公司 filed Critical 青岛海尔滚筒洗衣机有限公司
Publication of WO2021218966A1 publication Critical patent/WO2021218966A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/107—Network architectures or network communication protocols for network security for controlling access to devices or network resources wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Definitions

  • This application relates to the technical field of the Internet of Things, and more specifically, to a device detection method, device, device, system, storage medium, and program product.
  • the purpose of this application is to provide a device detection method, device, device, system, storage medium, and program product to solve the problem of tampering with IoT devices and uploading a large amount of fake data.
  • the present application discloses a device detection method, which can be executed by a server.
  • the method includes the following steps: First, the server receives a first device identity sent by a device to be detected, wherein the first device identity passes through a sensor. The obtained device attribute of the device to be detected is determined. Then, the server determines the second device identity of the device to be detected based on the pre-stored device attributes of the device to be detected, and then determines the identity of the device to be detected based on the first device identity and the second device identity. Check whether the device is trustworthy.
  • the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server are used to determine whether the device to be detected is credible.
  • the device attributes collected by the sensor There is a change, which causes the identity of the first device sent by the device to be detected to be different from the identity of the second device determined by the server.
  • the server discovers that the device has been tampered with and accurately determines the illegal node device, thereby stopping subsequent command interactions to ensure The data uploaded by the device is authentic and reliable.
  • the device attributes include the machine code of the device to be detected, the International Mobile Equipment Identity (IMEI) code of the communication unit in the device to be detected, and the subscriber identity module (Subscriber). At least one of the Identity Module (SIM) card number.
  • IMEI International Mobile Equipment Identity
  • SIM Subscriber identity module
  • the determining the second device identity of the device to be detected according to the prestored device attributes of the device to be detected includes: using a preset function and the prestored device attributes, The identity of the second device is determined, wherein the preset function includes at least one of a hash algorithm and a secure hash algorithm (Secure Hash Algorithm, SHA).
  • the receiving the first device identity sent by the device to be detected includes: receiving the encrypted first device identity sent by the device to be detected. Before judging whether the device to be detected is authentic according to the first device identity and the second device identity, the method further includes: decrypting the encrypted first device identity.
  • the method further includes: acquiring the current location of the device to be detected.
  • the judging whether the device to be detected is credible according to the identity of the first device and the identity of the second device includes: according to a pre-stored location of the device to be detected, the current location, and the first device The identity and the identity of the second device determine whether the device to be detected is credible.
  • the method further includes: acquiring information about the environment in which the device to be detected is located.
  • the judging whether the device to be tested is credible according to the identity of the first device and the identity of the second device includes: pre-stored environmental information of the device to be tested and information about the environment in which the device to be tested is located. Information, the identity of the first device, and the identity of the second device to determine whether the device to be tested is credible.
  • the present application discloses a device detection method, which can be executed by a device to be detected.
  • the method includes: firstly, determining the first device of the device to be detected by acquiring the device attributes of the device to be detected by a sensor identity. Then, the first device identity is sent to the server, where the first device identity is used to instruct the server to determine the second device of the device to be detected based on the prestored device attributes of the device to be detected. The identity, based on the identity of the first device and the identity of the second device, determines whether the device to be detected is credible.
  • the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server are used to determine whether the device to be detected is credible.
  • the device attributes collected by the sensor change, so that:
  • the identity of the first device sent by the device to be detected is different from the identity of the second device determined by the server, which in turn makes the server discover that the device has been tampered with and accurately determine the illegal node device, thereby stopping subsequent command interactions to ensure the authenticity of the data uploaded by the device reliable.
  • the device attribute includes the machine code of the device to be tested, and at least one of the IMEI code and the SIM card number of the communication unit in the device to be tested.
  • the determining the first device identity of the device to be detected by the device attribute of the device to be detected obtained by the sensor includes: determining the first device identity through a preset function and the device attribute , Wherein the preset function includes at least one of a hash algorithm and SHA.
  • the sending the first device identity to the server includes: sending the encrypted first device identity to the server.
  • the encrypted first device identity is used to instruct the server to decrypt.
  • this application discloses a device detection device, where the device detection device may be the above-mentioned server itself, or a chip or integrated circuit that realizes the function of the server.
  • the device includes: a receiving module for receiving a first device identity sent by a device to be detected, wherein the first device identity is determined by a device attribute of the device to be detected obtained by a sensor.
  • the first determining module is configured to determine the second device identity of the device to be detected according to the prestored device attributes of the device to be detected.
  • the judging module is used to judge whether the device to be tested is credible according to the identity of the first device and the identity of the second device.
  • this application discloses a device detection device, where the device detection device may be the above-mentioned device to be tested itself, or a chip or integrated circuit that implements the function of the device to be tested.
  • the device includes: a second determining module, which is used to determine the first device identity of the device to be detected by acquiring the device attribute of the device to be detected by the sensor.
  • the sending module is configured to send the first device identity to the server, where the first device identity is used to instruct the server to determine the device attribute of the device to be detected based on the prestored device attributes of the device to be detected
  • the second device identity determines whether the device to be tested is credible according to the first device identity and the second device identity.
  • the present application discloses a device detection system.
  • the system includes a memory, a processor, and computer instructions stored in the memory and running on the processor, and the processor executes the computer When instructing, implement the above-mentioned first aspect or various possible device detection methods of the first aspect.
  • the present application discloses a device detection system.
  • the system includes a memory, a processor, and computer instructions that are stored in the memory and run on the processor, and the processor executes the computer When instructing, implement the above-mentioned second aspect or various possible device detection methods of the second aspect.
  • the present application discloses a computer-readable storage medium having computer instructions stored in the computer-readable storage medium, and when the processor executes the computer instructions, the first aspect or each of the first aspects is implemented.
  • a possible design of equipment testing methods are possible design of equipment testing methods.
  • the present application discloses a computer-readable storage medium having computer instructions stored in the computer-readable storage medium, and when the processor executes the computer instructions, the second aspect or each of the second aspects is implemented.
  • a possible design of equipment testing methods are possible design of equipment testing methods.
  • this application discloses a computer program product, including program code.
  • the program code executes the method provided by any one of the implementations of the first aspect above.
  • this application discloses a computer program product, including program code.
  • the program code executes the method provided by any one of the implementations of the second aspect above.
  • the device detection method, device, device, system, storage medium, and program product provided in this application use the first device identity sent by the device to be tested and the second device identity of the device to be tested determined by the server , Determine whether the device to be detected is credible, wherein the identity of the first device is determined by the device attribute of the device to be detected obtained by a sensor, and the identity of the second device is determined according to the device attribute of the device to be detected pre-stored on the server, and when the device is tampered with , The device attribute collected by the sensor changes, which causes the identity of the first device sent by the device to be detected to be different from the identity of the second device determined by the server, which in turn enables the server to discover that the device has been tampered with in time, accurately determine the illegal node device, and stop Subsequent command interaction ensures that the data uploaded by the device is authentic and reliable.
  • FIG. 1 is a schematic diagram of the architecture of a device detection system provided by an embodiment of the application
  • FIG. 2 is a schematic flowchart of a device detection method provided by an embodiment of the application
  • FIG. 3 is a schematic flowchart of another device detection method provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of yet another device detection method provided by an embodiment of this application.
  • FIG. 5 is a schematic flowchart of another device detection method provided by an embodiment of this application.
  • FIG. 6 is a schematic flowchart of another device detection method provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of another device detection method provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a device detection apparatus provided by an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of another device detection apparatus provided by an embodiment of the application.
  • 10A is a schematic diagram of the basic hardware architecture of a device detection system provided by this application.
  • FIG. 10B is a schematic diagram of the basic hardware architecture of another device detection system provided by this application.
  • the device detection involved in the embodiments of the present application refers to using the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server to determine whether the device to be detected is authentic.
  • the device attribute of the device to be detected obtained by the sensor is determined, and the above-mentioned second device identity is determined according to the device attribute of the device to be detected pre-stored in the server, which solves the problem of the Internet of Things device being tampered with and uploading a large amount of fake data.
  • the device detection method and device provided in the embodiments of the present application can be applied to the detection, management, and control of IoT devices, such as the detection, management, and control of shared washing machines, which are not particularly limited in the embodiments of the present application.
  • FIG. 1 merely describes a possible application scenario of the device detection method provided in the embodiment of the present application by way of example, and the application scenario of the device detection method provided in the embodiment of the present application is not limited to the application scenario shown in FIG. 1.
  • FIG. 1 is a schematic diagram of the device detection system architecture.
  • the foregoing architecture includes a server 11 and multiple washing machines.
  • the multiple washing machines are taken as examples of the first washing machine 12, the second washing machine 13, and the third washing machine 14.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the device detection architecture.
  • the aforementioned architecture may include more or less components than those shown in the figure, or combine certain components, or split certain components, or dispose of different components, depending on the actual application. The scene is determined, and there is no restriction here.
  • the components shown in Figure 1 can be implemented in hardware, software, or a combination of software and hardware.
  • the interaction deduction between the first washing machine 12 and the server 11 is taken as an example.
  • the first washing machine 12 when the service data is uploaded to the server 11, the first device identity is sent first.
  • the identity of the first device is determined by the device attribute of the first washing machine 12 obtained by the sensor.
  • the server 11 receives the first device identity sent by the first washing machine 12, it determines the second device identity according to the pre-stored device attributes of the first washing machine 12, and further, according to the first device identity and the second device identity, It is determined whether the first washing machine 12 is authentic.
  • the server 11 can send corresponding information to the first washing machine 12, and the first washing machine 12 uploads service data to the server 11, and the server 11 deducts fees based on the service data. Ensure that the data uploaded by the device is authentic and reliable.
  • the above-mentioned methods can also be adopted to solve the problem of the Internet of Things devices being tampered with and uploading a large amount of fake data.
  • the device detection method provided in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.
  • the execution subject of this method may be the server 11 in FIG. 1.
  • the work flow of the server 11 mainly includes a receiving phase and a processing phase.
  • the server 11 receives the first device identity sent by the device to be detected, and the first device identity is determined by the device attribute of the device to be detected obtained by the sensor.
  • the server 11 uses the first device identity sent by the device to be tested and the second device identity of the device to be tested determined by the server to determine whether the device to be tested is credible.
  • the device attribute of the device is determined to solve the problem of tampering with IoT devices and uploading a large amount of fake data.
  • FIG. 2 is a schematic flowchart of a device detection method provided by an embodiment of this application.
  • the execution subject of this embodiment may be the server 11 in FIG. 1, and the specific execution subject may be determined according to actual application scenarios.
  • the device detection method provided by the embodiment of the present application includes the following steps:
  • S201 Receive a first device identity sent by a device to be detected, where the first device identity is determined by a device attribute of the device to be detected obtained by a sensor.
  • the device to be tested can be determined according to the actual situation, which is not particularly limited in the embodiment of the present application.
  • the above-mentioned device attributes may include the machine code of the device to be detected, and at least one of the IMEI code and the SIM card number of the communication unit in the detection device.
  • the foregoing device attributes can also be determined according to actual conditions, such as device code, name, etc., which are not particularly limited in the embodiment of the present application.
  • information such as the type and quantity of the above-mentioned sensors can be determined according to the above-mentioned device attributes that need to be acquired.
  • Determining the identity of the first device by the device to be detected based on the device attribute obtained by the sensor may include:
  • the identity of the first device is determined through the preset function and the device attribute.
  • the foregoing preset function includes at least one of a hash algorithm and a SHA.
  • the foregoing preset function can also be set according to actual conditions, which is not particularly limited in the embodiment of the present application.
  • S202 Determine the second device identity of the device to be detected according to the pre-stored device attributes of the device to be detected.
  • the server may pre-store the device attributes of the device to be tested. Specifically, the server may obtain the device attributes of the device to be tested when the device to be tested leaves the factory, and store the device attributes.
  • the server and the device to be tested can be a node of the blockchain respectively.
  • S203 Determine whether the device to be detected is credible according to the above-mentioned first device identity and the second device identity.
  • the server may compare the above-mentioned first device identity and the second device identity, and if the comparison is the same, it is judged that the device to be checked is credible, otherwise, it is judged that the device to be checked is not credible.
  • the device attribute collected by the sensor changes, which causes the identity of the first device sent by the device to be detected to be different from the identity of the second device determined by the server, and it is determined that the device to be detected is not trustworthy.
  • the server judges that the device to be detected is credible, it can continue to exchange information with the device to be detected; otherwise, it stops the information interaction to ensure the accuracy of subsequent processing.
  • the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server are used to determine whether the device to be detected is authentic.
  • the device attribute of the device is determined, and the above-mentioned second device identity is determined according to the device attribute of the device to be detected pre-stored in the server.
  • the device attribute collected by the sensor changes, which causes the identity of the first device sent by the device to be detected to be different from that of the device to be detected.
  • the identity of the second device determined by the server is different, so that the server discovers that the device has been tampered with in time, and accurately determines the illegal node device, thereby stopping subsequent command interaction, and ensuring the authenticity and reliability of the data uploaded by the device.
  • FIG. 3 is a schematic flowchart of another device detection method proposed in an embodiment of the application. As shown in Figure 3, the method includes:
  • S301 Receive a first device identity sent by a device to be detected, where the first device identity is determined by a device attribute of the device to be detected obtained by a sensor.
  • step S301 is implemented in the same manner as the foregoing step S201, and will not be repeated here.
  • S302 Determine the second device identity of the device to be detected through a preset function and prestored device attributes of the device to be detected, where the preset function includes at least one of a hash algorithm and a SHA.
  • the server can quickly and accurately generate the second device identity of the device to be detected through the preset function and the device attributes of the device to be detected pre-stored.
  • the above preset function can be used to derive the device identities of various devices.
  • the pre-stored device attributes of the device to be detected can be used as input parameters to generate the second device identity of the device to be detected.
  • the preset function may also include other The input parameters of this application are not particularly limited in this embodiment.
  • the server and the device to be detected may pre-negotiate the foregoing preset function, so that the server and the device to be detected may respectively use the same preset function to determine the identity of the device based on the device attribute.
  • the foregoing preset function includes at least one of a hash algorithm and a SHA, and may also include other algorithms according to actual needs, which is not particularly limited in the embodiment of the present application.
  • S303 Determine whether the device to be detected is credible according to the above-mentioned first device identity and the second device identity.
  • step S303 is implemented in the same manner as the foregoing step S203, and will not be repeated here.
  • the second device identity of the device to be detected can be quickly and accurately generated through the preset function and the device attributes of the device to be detected pre-stored.
  • the embodiment of the present application uses the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server to determine whether the device to be detected is credible.
  • the device attribute of the detection device is determined, and the above-mentioned second device identity is determined according to the device attribute of the device to be detected pre-stored in the server.
  • the device attribute collected by the sensor changes, resulting in the identity of the first device sent by the device to be detected It is different from the identity of the second device determined by the server, which in turn enables the server to discover that the device has been tampered with and accurately determine the illegal node device, thereby stopping subsequent command interactions and ensuring the authenticity and reliability of the data uploaded by the device.
  • FIG. 4 is a schematic flowchart of yet another device detection method proposed in an embodiment of the application. As shown in Figure 4, the method includes:
  • S401 Receive an encrypted first device identity sent by a device to be detected, where the first device identity is determined by a device attribute of the device to be detected obtained by a sensor.
  • the device to be detected may encrypt the identity of the first device before sending the identity of the first device.
  • the encryption method may adopt a preset encryption algorithm for encryption, and the preset encryption algorithm may include at least one of the message digest algorithm MD5, the data encryption standard DES, and the advanced encryption standard AES.
  • the foregoing preset encryption algorithm can also be determined according to actual conditions, which is not particularly limited in the embodiment of the present application.
  • the device to be detected and the server exchange information in an encrypted manner, thereby avoiding data tampering during transmission and improving the security and accuracy of data transmission.
  • S402 Determine the second device identity of the device to be detected according to the pre-stored device attributes of the device to be detected.
  • step S402 is implemented in the same manner as the foregoing step S202, and will not be repeated here.
  • the server decrypts the encrypted first device identity to obtain the first device identity of the device to be detected.
  • the server and the device to be detected may pre-negotiate the aforementioned preset encryption algorithm, so that after receiving the encrypted first device identity sent by the device to be detected, the server can decrypt the encrypted first device identity to ensure Subsequent processing proceeded normally.
  • S404 According to the decrypted first device identity and the foregoing second device identity, determine whether the device to be detected is credible.
  • step S404 is implemented in the same manner as the foregoing step S203, and will not be repeated here.
  • the information exchange between the device to be detected and the server is performed in an encrypted manner to avoid data tampering during the transmission process.
  • the embodiment of the present application uses the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server to determine whether the device to be detected is credible.
  • the device attribute of the detection device is determined, and the above-mentioned second device identity is determined according to the device attribute of the device to be detected pre-stored in the server.
  • the device attribute collected by the sensor changes, resulting in the identity of the first device sent by the device to be detected It is different from the identity of the second device determined by the server, which in turn enables the server to discover that the device has been tampered with and accurately determine the illegal node device, thereby stopping subsequent command interactions and ensuring the authenticity and reliability of the data uploaded by the device.
  • FIG. 5 is a schematic flowchart of another device detection method proposed in an embodiment of the application. As shown in Figure 5, the method includes:
  • S501 Receive a first device identity sent by a device to be detected, where the first device identity is determined by a device attribute of the device to be detected obtained by a sensor.
  • S502 Determine the second device identity of the device to be detected according to the pre-stored device attributes of the device to be detected.
  • steps S501-S502 are implemented in the same manner as the foregoing steps S201-S202, and will not be repeated here.
  • the server can obtain the current location of the device to be detected by receiving the location information sent by the positioning device set on the device to be detected, or it can obtain the current location of the device to be detected in other ways, which can be determined according to the actual situation.
  • the embodiment does not specifically limit this.
  • S504 Determine whether the device to be detected is credible according to the pre-stored location of the device to be detected, the current location, the identity of the first device, and the identity of the second device.
  • the server may first determine whether the above-mentioned current location exceeds the pre-stored location of the device to be detected.
  • the pre-stored location of the device to be detected can be set according to actual conditions. For example, if the device to be detected is a shared washing machine, the pre-stored The location of the equipment to be detected may be the use area of the shared washing machine. If the server judges that the current position does not exceed the pre-stored position of the device to be detected, it compares whether the identity of the first device and the identity of the second device are the same. letter. If the server determines that the above-mentioned current location exceeds the pre-stored location of the device to be detected, it can directly determine that the device to be detected is not trustworthy.
  • the above-mentioned sequence of determining whether the device to be detected is credible is not particularly limited in the embodiment of this application.
  • the device location can be determined first, and then the device identity can be determined.
  • the device identity can also be determined first, and then the device location can be determined. .
  • the server judges that the device to be checked is credible only when it determines that the current location does not exceed the pre-stored location of the device to be detected and compares the identity of the first device with the identity of the second device. Otherwise, it judges that the device to be detected is not credible.
  • the identity of the device and the location of the device are also considered when determining whether the device to be detected is credible, so as to ensure the accuracy of the determination result and be suitable for the application.
  • the embodiment of the present application uses the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server to determine whether the device to be detected is credible.
  • the device attribute of the detection device is determined, and the above-mentioned second device identity is determined according to the device attribute of the device to be detected pre-stored in the server.
  • the device attribute collected by the sensor changes, resulting in the identity of the first device sent by the device to be detected It is different from the identity of the second device determined by the server, which in turn enables the server to discover that the device has been tampered with in time, and accurately determine the illegal node device, thereby stopping subsequent command interactions and ensuring the authenticity and reliability of the data uploaded by the device.
  • FIG. 6 is a schematic flowchart of another device detection method proposed by an embodiment of the application. As shown in Figure 6, the method includes:
  • S601 Receive a first device identity sent by a device to be detected, where the first device identity is determined by a device attribute of the device to be detected obtained by a sensor.
  • S602 Determine the second device identity of the device to be detected according to the pre-stored device attributes of the device to be detected.
  • steps S601-S602 are implemented in the same manner as the foregoing steps S201-S202, and will not be repeated here.
  • S603 Acquire information about the environment in which the device to be detected is located.
  • the server can obtain the information of the environment in which the equipment to be detected is located by receiving the environmental information sent by the environmental information obtaining device provided in the equipment to be detected, or obtain the information of the environment in which the equipment to be detected is located in other ways, which can be specifically based on The actual situation is determined, and the embodiments of the present application do not specifically limit this.
  • the above-mentioned information about the environment in which the device to be tested is located may include the temperature and humidity of the environment in which the device to be tested is located.
  • S604 Determine whether the device to be tested is credible according to the pre-stored environmental information of the device to be tested, the information of the environment where the device to be tested is located, the identity of the first device and the identity of the second device.
  • the server may first determine whether the above-mentioned information about the environment of the device to be detected exceeds the pre-stored environmental information of the device to be detected, wherein the pre-stored environmental information of the device to be detected can be set according to actual conditions, such as temperature, humidity, etc. . If the server determines that the environment of the device to be detected does not exceed the pre-stored environment information of the device to be detected, it compares whether the identity of the first device and the identity of the second device are the same, and if they are the same, it determines that the device to be detected is credible, Otherwise, the device to be tested is judged to be untrustworthy. If the server determines that the environment of the device to be detected exceeds the pre-stored environmental information of the device to be detected, it can directly determine that the device to be detected is not trustworthy.
  • the above-mentioned sequence of determining whether the device to be detected is authentic is not particularly limited in the embodiment of this application.
  • the device environment information can be determined first, and then the device identity can be determined.
  • the device identity can also be determined first, and then the device Environmental information.
  • the identity of the device and the environmental information of the device are also considered, so as to ensure the accuracy of the judgment result and be suitable for the application.
  • the embodiment of the present application uses the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server to determine whether the device to be detected is credible.
  • the device attribute of the detection device is determined, and the above-mentioned second device identity is determined according to the device attribute of the device to be detected pre-stored in the server.
  • the device attribute collected by the sensor changes, resulting in the identity of the first device sent by the device to be detected It is different from the identity of the second device determined by the server, which in turn enables the server to discover that the device has been tampered with in time, and accurately determine the illegal node device, thereby stopping subsequent command interactions and ensuring the authenticity and reliability of the data uploaded by the device.
  • the execution subject of this method may be the washing machine in FIG. 1, that is, the equipment to be tested.
  • the work flow of the equipment to be tested mainly includes the determination phase and the sending phase.
  • the determination phase the device to be tested acquires the device attributes of the device to be tested through the sensor, and determines the first device identity of the device to be tested.
  • the sending phase the device to be tested sends the identity of the first device to the server.
  • FIG. 7 is a schematic flowchart of another device detection method provided by an embodiment of the application.
  • the execution subject of this embodiment may be the washing machine in FIG. 1, that is, the device to be detected, and the specific execution subject may be determined according to actual application scenarios.
  • the device detection method provided by the embodiment of the present application includes the following steps:
  • S701 Determine the first device identity of the device to be detected by using the device attribute of the device to be detected obtained by the sensor.
  • S702 Send the first device identity to the server, where the first device identity is used to instruct the server to determine the second device of the device to be detected based on the prestored device attributes of the device to be detected The identity, based on the identity of the first device and the identity of the second device, determines whether the device to be detected is credible.
  • the device attribute includes the machine code of the device to be tested, and at least one of the IMEI code and the SIM card number of the communication unit in the device to be tested.
  • the device attribute of the device to be detected obtained by the sensor, and the determination of the first device identity of the device to be detected includes:
  • the identity of the first device is determined through a preset function and the device attribute, where the preset function includes at least one of a hash algorithm and a SHA.
  • the sending the identity of the first device to the server includes:
  • the encrypted first device identity is used to instruct the server to decrypt.
  • the first device identity sent by the device to be detected and the second device identity of the device to be detected determined by the server are used to determine whether the device to be detected is authentic.
  • the device attribute of the device is determined, and the above-mentioned second device identity is determined according to the device attribute of the device to be detected pre-stored in the server.
  • the device attribute collected by the sensor changes, which causes the identity of the first device sent by the device to be detected to be different from that of the device to be detected.
  • the identity of the second device determined by the server is different, so that the server discovers that the device has been tampered with in time, and accurately determines the illegal node device, thereby stopping subsequent command interaction, and ensuring the authenticity and reliability of the data uploaded by the device.
  • FIG. 8 is a schematic structural diagram of the device detection apparatus provided in an embodiment of the application. For ease of description, only the parts related to the embodiments of the present application are shown.
  • FIG. 8 is a schematic structural diagram of a device detection device provided by an embodiment of the application.
  • the device detection device 80 includes a receiving module 801, a first determining module 802, and a determining module 803.
  • the receiving module 801 is configured to receive the first device identity sent by the device to be detected, where the first device identity is determined by the device attribute of the device to be detected obtained by a sensor.
  • the first determining module 802 is configured to determine the second device identity of the device to be detected according to the prestored device attributes of the device to be detected.
  • the judging module 803 is configured to judge whether the device to be detected is credible according to the identity of the first device and the identity of the second device.
  • the device attribute includes the machine code of the device to be tested, and at least one of the IMEI code and the SIM card number of the communication unit in the device to be tested.
  • the first determining module 802 is specifically configured to determine the identity of the second device through a preset function and the pre-stored device attributes, where the preset function includes a hash algorithm And at least one of the secure hash algorithm SHA.
  • the receiving module 801 is specifically configured to receive the encrypted first device identity sent by the device to be detected.
  • the judging module 803 is further configured to decrypt the encrypted first device identity before judging whether the device to be detected is authentic according to the first device identity and the second device identity.
  • the judging module 803 is further configured to obtain the current location of the device to be detected before judging whether the device to be detected is credible. Furthermore, according to the pre-stored location of the device to be detected, the current location, the identity of the first device, and the identity of the second device, it is determined whether the device to be detected is credible.
  • the judging module 803 is further configured to obtain information about the environment in which the device to be detected is located before judging whether the device to be detected is credible. Furthermore, according to the pre-stored environmental information of the device to be tested, information of the environment in which the device to be tested is located, the identity of the first device and the identity of the second device, it is determined whether the device to be tested is credible.
  • the device provided in the embodiment of the present application can be used to implement the technical solutions of the foregoing method embodiments, and its implementation principles and technical effects are similar, and the details of the embodiments of the present application are not repeated here.
  • FIG. 9 is a schematic structural diagram of another device detection device provided by an embodiment of the application.
  • the device detection device 90 includes: a second determining module 901 and a sending module 902.
  • the second determining module 901 is configured to determine the first device identity of the device to be detected through the device attribute of the device to be detected obtained by the sensor.
  • the sending module 902 is configured to send the first device identity to the server, where the first device identity is used to instruct the server to determine the device to be tested based on the device attributes of the device to be tested pre-stored According to the identity of the second device of the first device and the identity of the second device, it is determined whether the device to be detected is credible.
  • the device attribute includes the machine code of the device to be tested, and at least one of the IMEI code and the SIM card number of the communication unit in the device to be tested.
  • the second determining module 901 is specifically configured to determine the identity of the first device through a preset function and the device attribute, where the preset function includes at least one of a hash algorithm and a SHA .
  • the sending module 902 is specifically used to send the encrypted first device identity to the server.
  • the encrypted first device identity is used to instruct the server to decrypt.
  • the device provided in the embodiment of the present application can be used to implement the technical solutions of the foregoing method embodiments, and its implementation principles and technical effects are similar, and the details of the embodiments of the present application are not repeated here.
  • FIGS. 10A and 10B schematically provide a possible basic hardware architecture of the device detection system described in this application.
  • the device detection system 1000 includes at least one processor 1001 and a communication interface 1003. Further optionally, it may also include a memory 1002 and a bus 1004.
  • the device detection system 1000 may be a computer or a server, which is not particularly limited in this application.
  • the number of processors 1001 may be one or more, and FIGS. 10A and 10B only illustrate one of the processors 1001.
  • the processor 1001 may be a central processing unit (CPU), a graphics processing unit (GPU), or a digital signal processor (DSP). If the device detection system 1000 has multiple processors 1001, the types of the multiple processors 1001 may be different or may be the same. Optionally, multiple processors 1001 of the device detection system 1000 may also be integrated into a multi-core processor.
  • the memory 1002 stores computer instructions and data; the memory 1002 can store computer instructions and data required to implement the above device detection method provided by the present application.
  • the memory 1002 stores instructions for implementing the steps of the above device detection method.
  • the memory 1002 may be any one or any combination of the following storage media: non-volatile memory (for example, read only memory (ROM), solid state drive (SSD), hard disk (HDD), optical disk)), volatile memory.
  • the communication interface 1003 may provide information input/output for the at least one processor. It may also include any one or any combination of the following devices: a network interface (for example, an Ethernet interface), a wireless network card, and other devices with a network access function.
  • the communication interface 1003 may also be used for data communication between the device detection system 1000 and other computing devices or terminals.
  • the bus 1004 is represented by a thick line in FIGS. 10A and 10B.
  • the bus 1004 can connect the processor 1001 with the memory 1002 and the communication interface 1003. In this way, through the bus 1004, the processor 1001 can access the memory 1002, and can also use the communication interface 1003 to interact with other computing devices or terminals.
  • the equipment detection system 1000 executes the computer instructions in the memory 1002 to enable the equipment detection system 1000 to implement the above-mentioned equipment detection method provided in this application, or to make the equipment detection system 1000 deploy the above-mentioned equipment detection apparatus.
  • the memory 1002 may include a receiving module 801, a first determining module 802, and a determining module 803.
  • the inclusion here only refers to the functions of the receiving module 801, the first determining module 802, and the judging module 803 that can be implemented respectively when the instructions stored in the memory are executed, and are not limited to the physical structure.
  • the memory 1002 includes a second determining module 901 and a sending module 902.
  • the above-mentioned device detection apparatus can be implemented through software as shown in Figs. 10A and 10B, and can also be implemented as a hardware module or as a circuit unit through hardware.
  • This application provides a computer-readable storage medium, and the computer program product includes computer instructions that instruct a computing device to execute the above-mentioned device detection method provided by this application.
  • the present application provides a chip including at least one processor and a communication interface, and the communication interface provides information input and/or output for the at least one processor. Further, the chip may also include at least one memory, and the memory is used to store computer instructions. The at least one processor is used to call and run the computer instructions to execute the above-mentioned device detection method provided in this application.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Multimedia (AREA)
  • Storage Device Security (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请属于物联网技术领域，具体涉及一种设备检测方法及***。本申请利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。

Description

设备检测方法、装置、设备、***、存储介质及程序产品
本申请要求于2020年4月29日提交中国专利局、申请号为202010353895.2、申请名称为“设备检测方法及***”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及物联网技术领域，更为具体地，涉及一种设备检测方法、装置、设备、***、存储介质及程序产品。
背景技术
随着信息化的发展，各种智能设备广泛应用于人们生活的方方面面。物联网在为用户带来便捷的同时，物联网的安全问题成为物联网产业的尖锐问题。
在物联网应用场景中，常常出现设备被篡改的问题。以共享洗衣机为例，不良商家为了多算服务次数，改造了设备，上传假服务数据，非法牟利。
然后，针对上述问题，现有并没有有效的解决方法，因此，如何管理物联网设备，保证设备上传数据的准确性，成为一个急需解决的问题。
发明内容
本申请的目的在于提供一种设备检测方法、装置、设备、***、存储介质及程序产品，以解决物联网设备被篡改，上传大量假数据的问题。
第一方面，本申请公开一种设备检测方法，该方法可以由服务器执行，该方法包括如下步骤：首先，服务器接收待检测设备发送的第一设备身份，其中，所述第一设备身份通过传感器获取的所述待检测设备的设备属性确定。然后，服务器根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，进而，根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
基于上述技术内容，通过待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
在一个实现方式中，所述设备属性包括所述待检测设备的机器码，以及所述待检测设备中通讯单元的国际移动设备标识(International Mobile Equipment Identity，IMEI)码和用户身份识别模块(Subscriber Identity Module，SIM)***中至少一个。
在一个实现方式中，所述根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，包括：通过预设函数和所述预存的所述设备属性，确定所述第二设备身份，其中，所述预设函数包括哈希算法和安全散列算法(Secure Hash Algorithm，SHA)中至少一个。
在一个实现方式中，所述接收待检测设备发送的第一设备身份，包括：接收所述待检测设备发送的加密的第一设备身份。在所述根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信之前，还包括：对所述加密的第一设备身份进行解密。
在一个实现方式中，在所述判断所述待检测设备是否可信之前，还包括：获取所述待检测设备的当前位置。所述根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信，包括：根据预存的所述待检测设备的位置、所述当前位置、所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
在一个实现方式中，在所述判断所述待检测设备是否可信之前，还包括：获取所述待检测设备所处环境的信息。所述根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信，包括：根据预存的所述待检测设备的环境信息、所述待检测设备所处环境的信息、所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
第二方面，本申请公开了一种设备检测方法，该方法可以由待检测设备执行，该方法包括：首先，通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份。然后，发送所述第一设备身份至服务器，其中，所述第一设备身份用于指示所述服务器根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
通过待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
在一个实现方式中，所述设备属性包括所述待检测设备的机器码，以及所述待检测设备中通讯单元的IMEI码和SIM***中至少一个。
在一个实现方式中，所述通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份，包括：通过预设函数和所述设备属性，确定所述第一设备身份，其中，所述预设函数包括哈希算法和SHA中至少一个。
在一个实现方式中，所述发送所述第一设备身份至服务器，包括：发送的加密的第一设备身份至所述服务器。所述加密的第一设备身份用于指示所述服务器进行解密。
第三方面，本申请公开了一种设备检测装置，这里的设备检测装置可以是上述服务器本身，或者是实现服务器的功能的芯片或者集成电路。该装置包括：接收模块，用于接收待检测设备发送的第一设备身份，其中，所述第一设备身份通过传感器获取的所述待检测设备的设备属性确定。第一确定模块，用于根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份。判断模块，用于根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
第四方面，本申请公开了一种设备检测装置，这里的设备检测装置可以是上述待检测设备本身，或者是实现待检测设备的功能的芯片或者集成电路。该装置包括：第 二确定模块，用于通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份。发送模块，用于发送所述第一设备身份至服务器，其中，所述第一设备身份用于指示所述服务器根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
第五方面，本申请公开了一种设备检测***，所述***包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机指令，所述处理器执行所述计算机指令时实现上述第一方面或者第一方面的各种可能设计的设备检测方法。
第六方面，本申请公开了一种设备检测***，所述***包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机指令，所述处理器执行所述计算机指令时实现上述第二方面或者第二方面的各种可能设计的设备检测方法。
第七方面，本申请公开了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机指令，当处理器执行所述计算机指令时，实现上述第一方面或者第一方面的各种可能设计的设备检测方法。
第八方面，本申请公开了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机指令，当处理器执行所述计算机指令时，实现上述第二方面或者第二方面的各种可能设计的设备检测方法。
第九方面，本申请公开了一种计算机程序产品，包括程序代码，当计算机运行计算机程序产品时，该程序代码执行以上第一方面的任一实现方式提供的方法。
第十方面，本申请公开了一种计算机程序产品，包括程序代码，当计算机运行计算机程序产品时，该程序代码执行以上第二方面的任一实现方式提供的方法。
结合上述技术方案，本申请提供的设备检测方法、装置、设备、***、存储介质及程序产品，该方法利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
附图说明
图1为本申请实施例提供的设备检测***架构示意图；
图2为本申请实施例提供的一种设备检测方法的流程示意图；
图3为本申请实施例提供的另一种设备检测方法的流程示意图；
图4为本申请实施例提供的再一种设备检测方法的流程示意图；
图5为本申请实施例提供的又一种设备检测方法的流程示意图；
图6为本申请实施例提供的又一种设备检测方法的流程示意图；
图7为本申请实施例提供的又一种设备检测方法的流程示意图；
图8为本申请实施例提供的一种设备检测装置的结构示意图；
图9为本申请实施例提供的另一种设备检测装置的结构示意图；
图10A为本申请提供的一种设备检测***的基本硬件架构示意图；
图10B为本申请提供的另一种设备检测***的基本硬件架构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”及“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、***、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例所涉及的设备检测是指利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，解决物联网设备被篡改，上传大量假数据的问题。
本申请实施例提供的设备检测方法及装置可应用在物联网设备的检测、管理、控制等，例如共享洗衣机的检测、管理、控制等，本申请实施例对此不做特别限制。
可选地，本申请实施例提供的设备检测方法及***可以应用于如图1所示的应用场景中。图1只是以示例的方式描述了本申请实施例提供的设备检测方法的一种可能的应用场景，本申请实施例提供的设备检测方法的应用场景不限于图1所示的应用场景。
图1为设备检测***架构示意图。在图1中，以共享洗衣机的检测为例，上述架构包括服务器11和多个洗衣机，这里，该多个洗衣机以第一洗衣机12、第二洗衣机13和第三洗衣机14为例。
可以理解的是，本申请实施例示意的结构并不构成对设备检测架构的具体限定。在本申请另一些可行的实施方式中，上述架构可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置，具体可根据实际应用场景确定，在此不做限制。图1所示的部件可以以硬件，软件，或软件与硬件的组合实现。
在具体实现过程中，本申请实施例中以第一洗衣机12与服务器11交互扣费为例进行说明，当第一洗衣机12被使用后，上传服务数据至服务器11时，先发送第一设备身份至服务器11，其中，该第一设备身份通过传感器获取的第一洗衣机12的设备 属性确定。服务器11在接收到上述第一洗衣机12发送的第一设备身份后，根据预存的第一洗衣机12的设备属性确定第二设备身份，进而，根据上述第一设备身份和所述第二设备身份，判断第一洗衣机12是否可信。如果可信，说明第一洗衣机12未被篡改，服务器11可以发送相应信息至第一洗衣机12，第一洗衣机12再上传服务数据至服务器11，服务器11再基于该服务数据进行扣费，从而，保证设备上传数据的真实可靠。
同理，当第二洗衣机13或第三洗衣机14与服务器11交互扣费时，同样可以采取上述方式，解决物联网设备被篡改，上传大量假数据的问题。
另外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图详细介绍本申请实施例提供的设备检测方法。该方法的执行主体可以为图1中的服务器11。服务器11的工作流程主要包括接收阶段和处理阶段。在接收阶段，服务器11接收待检测设备发送的第一设备身份，第一设备身份通过传感器获取的待检测设备的设备属性确定。在处理阶段，服务器11利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，第二设备身份根据服务器预存的待检测设备的设备属性确定，解决物联网设备被篡改，上传大量假数据的问题。
下面以几个实施例为例对本申请的技术方案进行描述，对于相同或相似的概念或过程可能在某些实施例不再赘述。
图2为本申请实施例提供的一种设备检测方法的流程示意图，本实施例的执行主体可以为图1中的服务器11，具体执行主体可以根据实际应用场景确定。如图2所示，本申请实施例提供的设备检测方法包括如下步骤：
S201：接收待检测设备发送的第一设备身份，其中，该第一设备身份通过传感器获取的待检测设备的设备属性确定。
其中，待检测设备可以根据实际情况确定，本申请实施例对此不做特别限制。
在本申请实施例中，上述设备属性可以包括待检测设备的机器码，以及检测设备中通讯单元的IMEI码和SIM***中至少一个。除此之外，上述设备属性还可以根据实际情况确定，例如设备编码、名称等，本申请实施例对此不做特别限制。
相应的，上述传感器的类型、数量等信息可以根据上述需要获取的设备属性确定。
待检测设备基于传感器获取的设备属性确定第一设备身份可以包括：
通过预设函数和上述设备属性，确定上述第一设备身份。其中，上述预设函数包括哈希算法和SHA中至少一个，除此之外，上述预设函数还可以根据实际情况设置，本申请实施例对此不做特别限制。
S202：根据预存的待检测设备的设备属性，确定待检测设备的第二设备身份。
这里，服务器可以预存待检测设备的设备属性，具体的，服务器可以在待检测设备出厂时，获取待检测设备的设备属性，并存储该设备属性。
其中，服务器和待检测设备可以分别为区块链的一个节点。
S203：根据上述第一设备身份和第二设备身份，判断待检测设备是否可信。
示例性的，服务器可以将上述第一设备身份和第二设备身份进行比较，如果比较相同，则判断待检测设备可信，否则，判断待检测设备不可信。
其中，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，判断待检测设备不可信。
服务器在判断待检测设备可信时，可以继续与待检测设备进行信息交互，否则，停止信息交互，保证后续处理的准确进行。
本申请实施例，利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
另外，本申请实施例在确定待检测设备的第二设备身份时，在基于上述预存的设备属性的基础上，还利用预设函数。图3为本申请实施例提出的另一种设备检测方法的流程示意图。如图3所示，该方法包括：
S301：接收待检测设备发送的第一设备身份，其中，该第一设备身份通过传感器获取的待检测设备的设备属性确定。
其中，步骤S301与上述步骤S201的实现方式相同，此处不再赘述。
S302：通过预设函数和预存的待检测设备的设备属性，确定待检测设备的第二设备身份，其中，上述预设函数包括哈希算法和SHA中至少一个。
这里，服务器通过预设函数和上预存的待检测设备的设备属性，可以快速、准确的生成待检测设备的第二设备身份。其中，上述预设函数可用于派生各种设备的设备身份，如可以将预存的待检测设备的设备属性作为输入参数，生成待检测设备的第二设备身份，另外，预设函数还可能包括其它的输入参数，本申请实施例对此不作特别限制。
示例性的，服务器和待检测设备可以预先协商上述预设函数，从而，服务器和待检测设备可以分别采用相同的预设函数，基于设备属性，确定设备身份。
另外，上述预设函数除包括哈希算法和SHA中至少一个外，还可以根据实际需要包括其它算法，本申请实施例对此不做特别限制。
S303：根据上述第一设备身份和第二设备身份，判断待检测设备是否可信。
其中，步骤S303与上述步骤S203的实现方式相同，此处不再赘述。
本申请实施例，通过预设函数和上预存的待检测设备的设备属性，可以快速、准确的生成待检测设备的第二设备身份。另外，本申请实施例利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的 第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
另外，本申请实施例在接收待检测设备发送的第一设备身份时，是接收的待检测设备发送的加密的第一设备身份。图4为本申请实施例提出的再一种设备检测方法的流程示意图。如图4所示，该方法包括：
S401：接收待检测设备发送的加密的第一设备身份，其中，第一设备身份通过传感器获取的待检测设备的设备属性确定。
这里，待检测设备在发送上述第一设备身份之前，可以对第一设备身份进行加密。其中，加密方式可以采用预设加密算法加密，预设加密算法可以包括信息摘要算法MD5、数据加密标准DES和高级加密标准AES中至少一个。除此之外，还可以根据实际情况确定上述预设加密算法，本申请实施例对此不做特别限制。
在本申请实施例中，待检测设备和服务器之间通过加密的方式进行信息交互，从而，避免在传输过程中数据被篡改，提高数据传输的安全性和准确性。
S402：根据预存的待检测设备的设备属性，确定待检测设备的第二设备身份。
其中，步骤S402与上述步骤S202的实现方式相同，此处不再赘述。
S403：对上述加密的第一设备身份进行解密。
相应的，在服务器接收到待检测设备发送的加密的第一设备身份后，对该加密的第一设备身份进行解密，获得待检测设备的第一设备身份。
示例性的，服务器和待检测设备可以预先协商上述预设加密算法，从而，服务器在接收到待检测设备发送的加密的第一设备身份后，能够对该加密的第一设备身份进行解密，保证后续处理正常进行。
S404：根据解密后的第一设备身份和上述第二设备身份，判断待检测设备是否可信。
其中，步骤S404与上述步骤S203的实现方式相同，此处不再赘述。
本申请实施例，待检测设备和服务器之间通过加密的方式进行信息交互，避免在传输过程中数据被篡改。另外，本申请实施例利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
另外，本申请实施例除根据上述第一设备身份和第二设备身份，判断待检测设备是否可信外，还考虑待检测设备的位置信息。图5为本申请实施例提出的又一种设备检测方法的流程示意图。如图5所示，该方法包括：
S501：接收待检测设备发送的第一设备身份，其中，该第一设备身份通过传感器获取的待检测设备的设备属性确定。
S502：根据预存的待检测设备的设备属性，确定待检测设备的第二设备身份。
其中，步骤S501-S502与上述步骤S201-S202的实现方式相同，此处不再赘述。
S503：获取待检测设备的当前位置。
这里，服务器可以通过接收设置在待检测设备的定位装置发送的位置信息，来获取待检测设备的当前位置，也可以采用其它方式获取待检测设备的当前位置，具体可以根据实际情况确定，本申请实施例对此不做特别限制。
S504：根据预存的待检测设备的位置、上述当前位置、上述第一设备身份和所述第二设备身份，判断待检测设备是否可信。
示例性的，服务器可以首先判断上述当前位置是否超出预存的待检测设备的位置，其中，预存的待检测设备的位置可以根据实际情况设置，例如，如果待检测设备为共享洗衣机，则上述预存的待检测设备的位置可以为共享洗衣机的使用区域。如果服务器判断上述当前位置未超出预存的待检测设备的位置，则比较上述第一设备身份和所述第二设备身份是否相同，如果相同，则判断待检测设备可信，否则判断待检测设备不可信。如果服务器判断上述当前位置超出预存的待检测设备的位置，直接可以判断待检测设备不可信。
这里，对于上述判断待检测设备是否可信的前后顺序，本申请实施例不做特别限制，可以先判断设备位置，再判断设备身份，例如上述描述，也可以先判断设备身份，再判断设备位置。
服务器只有判断上述当前位置未超出预存的待检测设备的位置，且比较上述第一设备身份和所述第二设备身份相同时，才判断待检测设备可信，否则，判断待检测设备不可信。
本申请实施例，在判断待检测设备是否可信时，考虑设备身份，也考虑设备位置，从而保证判断结果的准确性，适合应用。另外，本申请实施例利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
另外，本申请实施例除根据上述第一设备身份和第二设备身份，判断待检测设备是否可信外，还考虑待检测设备的环境信息。图6为本申请实施例提出的又一种设备检测方法的流程示意图。如图6所示，该方法包括：
S601：接收待检测设备发送的第一设备身份，其中，该第一设备身份通过传感器获取的待检测设备的设备属性确定。
S602：根据预存的待检测设备的设备属性，确定待检测设备的第二设备身份。
其中，步骤S601-S602与上述步骤S201-S202的实现方式相同，此处不再赘述。
S603：获取待检测设备所处环境的信息。
这里，服务器可以通过接收设置在待检测设备的环境信息获取装置发送的环境信息，来获取待检测设备所处环境的信息，也可以采用其它方式获取待检测设备所处环境的信息，具体可以根据实际情况确定，本申请实施例对此不做特别限制。
其中，上述待检测设备所处环境的信息可以包括待检测设备所处环境的温度、湿 度等。
S604：根据预存的待检测设备的环境信息、上述待检测设备所处环境的信息、上述第一设备身份和第二设备身份，判断待检测设备是否可信。
示例性的，服务器可以首先判断上述待检测设备所处环境的信息是否超出预存的待检测设备的环境信息，其中，预存的待检测设备的环境信息可以根据实际情况设置，例如，温度、湿度等。如果服务器判断上述待检测设备所处环境，未超出预存的待检测设备的环境信息，则比较上述第一设备身份和所述第二设备身份是否相同，如果相同，则判断待检测设备可信，否则判断待检测设备不可信。如果服务器判断上述待检测设备所处环境超出预存的待检测设备的环境信息，直接可以判断待检测设备不可信。
这里，对于上述判断待检测设备是否可信的前后顺序，本申请实施例不做特别限制，可以先判断设备环境信息，再判断设备身份，例如上述描述，也可以先判断设备身份，再判断设备环境信息。
本申请实施例，在判断待检测设备是否可信时，考虑设备身份，也考虑设备环境信息，从而保证判断结果的准确性，适合应用。另外，本申请实施例利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
下面从另一侧结合附图详细介绍本申请实施例提供的设备检测方法。该方法的执行主体可以为图1中的洗衣机，即待检测设备。待检测设备的工作流程主要包括确定阶段和发送阶段。在确定阶段，待检测设备通过传感器获取的待检测设备的设备属性，确定待检测设备的第一设备身份。在发送阶段，待检测设备发送第一设备身份至服务器。
图7为本申请实施例提供的又一种设备检测方法的流程示意图，本实施例的执行主体可以为图1中的洗衣机，即待检测设备，具体执行主体可以根据实际应用场景确定。如图7所示，本申请实施例提供的设备检测方法包括如下步骤：
S701：通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份。
S702：发送所述第一设备身份至服务器，其中，所述第一设备身份用于指示所述服务器根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
一种可能设计，所述设备属性包括所述待检测设备的机器码，以及所述待检测设备中通讯单元的IMEI码和SIM***中至少一个。
一种可能设计，所述通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份，包括：
通过预设函数和所述设备属性，确定所述第一设备身份，其中，所述预设函数包括哈希算法和SHA中至少一个。
一种可能设计，所述发送所述第一设备身份至服务器，包括：
发送的加密的第一设备身份至所述服务器。所述加密的第一设备身份用于指示所述服务器进行解密。
本申请实施例，利用待检测设备发送的第一设备身份，以及服务器确定的待检测设备的第二设备身份，判断待检测设备是否可信，其中，上述第一设备身份通过传感器获取的待检测设备的设备属性确定，上述第二设备身份根据服务器预存的待检测设备的设备属性确定，当设备被篡改时，传感器采集的设备属性有变化，从而，导致待检测设备发送的第一设备身份与服务器确定的第二设备身份不同，进而，使得服务器及时发现设备被篡改，准确判定非法节点设备，从而，停止后续的命令交互，确保设备上传数据的真实可靠。
对应于上文实施例的设备检测方法，图8为本申请实施例提供的设备检测装置的结构示意图。为了便于说明，仅示出了与本申请实施例相关的部分。图8为本申请实施例提供的一种设备检测装置的结构示意图，该设备检测装置80包括：接收模块801、第一确定模块802以及判断模块803。
其中，接收模块801，用于接收待检测设备发送的第一设备身份，其中，所述第一设备身份通过传感器获取的所述待检测设备的设备属性确定。第一确定模块802，用于根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份。判断模块803，用于根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
一种可能设计，所述设备属性包括所述待检测设备的机器码，以及所述待检测设备中通讯单元的IMEI码和SIM***中至少一个。
一种可能设计，所述第一确定模块802，具体用于：通过预设函数和所述预存的所述设备属性，确定所述第二设备身份，其中，所述预设函数包括哈希算法和安全散列算法SHA中至少一个。
一种可能设计，所述接收模块801，具体用于：接收所述待检测设备发送的加密的第一设备身份。
所述判断模块803在所述根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信之前，还用于：对所述加密的第一设备身份进行解密。
所述判断模块803在所述判断所述待检测设备是否可信之前，还用于：获取所述待检测设备的当前位置。进而，根据预存的所述待检测设备的位置、所述当前位置、所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
所述判断模块803在所述判断所述待检测设备是否可信之前，还用于：获取所述待检测设备所处环境的信息。进而，根据预存的所述待检测设备的环境信息、所述待检测设备所处环境的信息、所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
本申请实施例提供的装置，可用于执行上述方法实施例的技术方案，其实现原理和技术效果类似，本申请实施例此处不再赘述。
图9为本申请实施例提供的另一种设备检测装置的结构示意图，该设备检测装置90包括：第二确定模块901以及发送模块902。
其中，第二确定模块901，用于通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份。发送模块902，用于发送所述第一设备身份至服务器，其中，所述第一设备身份用于指示所述服务器根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
一种可能设计，所述设备属性包括所述待检测设备的机器码，以及所述待检测设备中通讯单元的IMEI码和SIM***中至少一个。
一种可能设计，所述第二确定模块901，具体用于通过预设函数和所述设备属性，确定所述第一设备身份，其中，所述预设函数包括哈希算法和SHA中至少一个。
一种可能设计，所述发送模块902，具体用于发送的加密的第一设备身份至所述服务器。所述加密的第一设备身份用于指示所述服务器进行解密。
本申请实施例提供的装置，可用于执行上述方法实施例的技术方案，其实现原理和技术效果类似，本申请实施例此处不再赘述。
可选地，图10A和10B示意性地提供本申请所述设备检测***的一种可能的基本硬件架构。
参见图10A和10B，设备检测***1000包括至少一个处理器1001以及通信接口1003。进一步可选的，还可以包括存储器1002和总线1004。
其中，设备检测***1000可以是计算机或服务器，本申请对此不作特别限制。设备检测***1000中，处理器1001的数量可以是一个或多个，图10A和10B仅示意了其中一个处理器1001。可选地，处理器1001，可以是中央处理器(central processing unit，CPU)、图形处理器(graphics processing unit，GPU)或者数字信号处理器(digital signal processor，DSP)。如果设备检测***1000具有多个处理器1001，多个处理器1001的类型可以不同，或者可以相同。可选地，设备检测***1000的多个处理器1001还可以集成为多核处理器。
存储器1002存储计算机指令和数据；存储器1002可以存储实现本申请提供的上述设备检测方法所需的计算机指令和数据，例如，存储器1002存储用于实现上述设备检测方法的步骤的指令。存储器1002可以是以下存储介质的任一种或任一种组合：非易失性存储器(例如只读存储器(ROM)、固态硬盘(SSD)、硬盘(HDD)、光盘)，易失性存储器。
通信接口1003可以为所述至少一个处理器提供信息输入/输出。也可以包括以下器件的任一种或任一种组合：网络接口(例如以太网接口)、无线网卡等具有网络接入功能的器件。
可选的，通信接口1003还可以用于设备检测***1000与其它计算设备或者终端进行数据通信。
进一步可选的，图10A和10B用一条粗线表示总线1004。总线1004可以将处理器1001与存储器1002和通信接口1003连接。这样，通过总线1004，处理器1001可以访问存储器1002，还可以利用通信接口1003与其它计算设备或者终端进行数据交互。
在本申请中，设备检测***1000执行存储器1002中的计算机指令，使得设备检 测***1000实现本申请提供的上述设备检测方法，或者使得设备检测***1000部署上述的设备检测装置。
从逻辑功能划分来看，示例性的，如图10A所示，存储器1002中可以包括接收模块801、第一确定模块802以及判断模块803。这里的包括仅仅涉及存储器中所存储的指令被执行时可以分别实现接收模块801、第一确定模块802以及判断模块803的功能，而不限定是物理上的结构。
一种可能设计，如图10B所示，存储器1002中包括第二确定模块901以及发送模块902。
另外，上述的设备检测装置除了可以像上述图10A和10B通过软件实现外，也可以作为硬件模块，或者作为电路单元，通过硬件实现。
本申请提供一种计算机可读存储介质，所述计算机程序产品包括计算机指令，所述计算机指令指示计算设备执行本申请提供的上述设备检测方法。
本申请提供一种芯片，包括至少一个处理器和通信接口，所述通信接口为所述至少一个处理器提供信息输入和/或输出。进一步，所述芯片还可以包含至少一个存储器，所述存储器用于存储计算机指令。所述至少一个处理器用于调用并运行该计算机指令，以执行本申请提供的上述设备检测方法。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。

Claims (18)

  1. 一种设备检测方法，其特征在于，包括：
    接收待检测设备发送的第一设备身份，其中，所述第一设备身份通过传感器获取的所述待检测设备的设备属性确定；
    根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份；
    根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
  2. 根据权利要求1所述的方法，其特征在于，所述设备属性包括所述待检测设备的机器码，以及所述待检测设备中通讯单元的国际移动设备标识IMEI码和用户身份识别模块SIM***中至少一个。
  3. 根据权利要求1或2所述的方法，其特征在于，所述根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，包括：
    通过预设函数和所述预存的所述设备属性，确定所述第二设备身份，其中，所述预设函数包括哈希算法和安全散列算法SHA中至少一个。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述接收待检测设备发送的第一设备身份，包括：
    接收所述待检测设备发送的加密的第一设备身份；
    在所述根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信之前，还包括：
    对所述加密的第一设备身份进行解密。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，在所述判断所述待检测设备是否可信之前，还包括：
    获取所述待检测设备的当前位置；
    所述根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信，包括：
    根据预存的所述待检测设备的位置、所述当前位置、所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
  6. 根据权利要求1-4任一项所述的方法，其特征在于，在所述判断所述待检测设备是否可信之前，还包括：
    获取所述待检测设备所处环境的信息；
    所述根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信，包括：
    根据预存的所述待检测设备的环境信息、所述待检测设备所处环境的信息、所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
  7. 一种设备检测方法，其特征在于，包括：
    通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份；
    发送所述第一设备身份至服务器，其中，所述第一设备身份用于指示所述服务器根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
  8. 根据权利要求7所述的方法，其特征在于，所述设备属性包括所述待检测设备的机器码，以及所述待检测设备中通讯单元的IMEI码和SIM***中至少一个。
  9. 根据权利要求7或8所述的方法，其特征在于，所述通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份，包括：
    通过预设函数和所述设备属性，确定所述第一设备身份，其中，所述预设函数包括哈希算法和SHA中至少一个。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，所述发送所述第一设备身份至服务器，包括：
    发送的加密的第一设备身份至所述服务器，所述加密的第一设备身份用于指示所述服务器进行解密。
  11. 一种设备检测装置，其特征在于，包括：
    接收模块，用于接收待检测设备发送的第一设备身份，其中，所述第一设备身份通过传感器获取的所述待检测设备的设备属性确定；
    第一确定模块，用于根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份；
    判断模块，用于根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
  12. 一种设备检测装置，其特征在于，包括：
    第二确定模块，用于通过传感器获取的待检测设备的设备属性，确定所述待检测设备的第一设备身份；
    发送模块，用于发送所述第一设备身份至服务器，其中，所述第一设备身份用于指示所述服务器根据预存的所述待检测设备的所述设备属性，确定所述待检测设备的第二设备身份，根据所述第一设备身份和所述第二设备身份，判断所述待检测设备是否可信。
  13. 一种设备检测***，其特征在于，所述***包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机指令，所述处理器执行所述计算机指令时实现权利要求1至6任一项所述的设备检测方法。
  14. 一种设备检测***，其特征在于，所述***包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机指令，所述处理器执行所述计算机指令时实现权利要求7至10任一项所述的设备检测方法。
  15. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机指令，当处理器执行所述计算机指令时，实现如权利要求1至6任一项所述的设备检测方法。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机指令，当处理器执行所述计算机指令时，实现如权利要求7至10任一项所述的设备检测方法。
  17. 一种计算机程序产品，其特征在于，包括程序代码，当计算机运行所述计算机程序时，所述程序代码执行如权利要求1至6任一项所述的设备检测方法。
  18. 一种计算机程序产品，其特征在于，包括程序代码，当计算机运行所述计算机程序时，所述程序代码执行如权利要求7至10任一项所述的设备检测方法。
PCT/CN2021/090255 2020-04-29 2021-04-27 设备检测方法、装置、设备、***、存储介质及程序产品 WO2021218966A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010353895.2 2020-04-29
CN202010353895.2A CN113572716B (zh) 2020-04-29 2020-04-29 设备检测方法及***

Publications (1)

Publication Number Publication Date
WO2021218966A1 true WO2021218966A1 (zh) 2021-11-04

Family

ID=78158295

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/090255 WO2021218966A1 (zh) 2020-04-29 2021-04-27 设备检测方法、装置、设备、***、存储介质及程序产品

Country Status (2)

Country Link
CN (1) CN113572716B (zh)
WO (1) WO2021218966A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104506485A (zh) * 2014-11-13 2015-04-08 青岛微智慧信息有限公司 移动互联纳税终端身份认证技术
CN106255102A (zh) * 2016-07-26 2016-12-21 广东欧珀移动通信有限公司 一种终端设备的鉴定方法及相关设备
WO2018127479A1 (en) * 2017-01-05 2018-07-12 Koninklijke Philips N.V. Network device and trusted third party device
CN109492378A (zh) * 2018-11-26 2019-03-19 平安科技（深圳）有限公司 一种基于设备识别码的身份验证方法、服务器及介质

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102790674B (zh) * 2011-05-20 2016-03-16 阿里巴巴集团控股有限公司 身份验证方法、设备和***
CN104767717B (zh) * 2014-01-03 2019-01-29 腾讯科技（深圳）有限公司 身份验证方法及装置
CN104869124B (zh) * 2015-06-05 2018-03-09 飞天诚信科技股份有限公司 一种基于地理位置信息的认证方法
CN105184881A (zh) * 2015-08-28 2015-12-23 宇龙计算机通信科技(深圳)有限公司 一种用户身份识别的方法、装置、服务器以及***
CN109564598B (zh) * 2017-03-13 2022-04-22 华为技术有限公司 一种终端检测方法及终端
CN107404491B (zh) * 2017-08-14 2018-06-22 腾讯科技（深圳）有限公司 终端环境异常检测方法、检测装置及计算机可读存储介质
CN108737381B (zh) * 2018-04-23 2021-11-16 厦门盛华电子科技有限公司 一种物联网***的扩展认证方法
CN110866290A (zh) * 2018-11-21 2020-03-06 哈尔滨安天科技集团股份有限公司 芯片恶意篡改检测方法、装置、电子设备及存储介质
CN110571922B (zh) * 2019-05-14 2022-04-15 恒宝股份有限公司 一种基于共享密钥的物联网设备认证方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104506485A (zh) * 2014-11-13 2015-04-08 青岛微智慧信息有限公司 移动互联纳税终端身份认证技术
CN106255102A (zh) * 2016-07-26 2016-12-21 广东欧珀移动通信有限公司 一种终端设备的鉴定方法及相关设备
WO2018127479A1 (en) * 2017-01-05 2018-07-12 Koninklijke Philips N.V. Network device and trusted third party device
CN109492378A (zh) * 2018-11-26 2019-03-19 平安科技（深圳）有限公司 一种基于设备识别码的身份验证方法、服务器及介质

Also Published As

Publication number Publication date
CN113572716A (zh) 2021-10-29
CN113572716B (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
JP2019013009A (ja) 不正デジタル証明書の自動検出
WO2017129016A1 (zh) 一种资源访问方法、装置及***
US9247432B2 (en) Systems and methods for controlling network access
TWI603206B (zh) Server cluster based data processing method and cluster based data processing system
WO2020220536A1 (zh) 一种数据备份的方法、装置及计算机可读存储介质
CN107800678A (zh) 检测终端异常注册的方法及装置
JP2013532394A (ja) 複数のクライアントを有する電子ネットワークにおける遠隔保守のためのシステム及び方法
JP6093043B2 (ja) 品質設定可能ランダムデータサービス
TW202113642A (zh) 用於產生可供診斷標的網路系統是否受到駭客入侵攻擊的可疑事件時序圖的網路安全漏洞診斷系統
US20240187420A1 (en) Securing browser cookies
US20210400037A1 (en) Authenticated interface element interactions
CN111371889B (zh) 消息处理方法、装置、物联网***和存储介质
CN111614731B (zh) 物联网设备接入区块链方法、***、聚合网关及存储介质
CN104104650A (zh) 数据文件访问方法及终端设备
US9948632B2 (en) Sharing data between sandboxed applications with certificates
TWI817002B (zh) 文檔上傳下載方法、裝置、電腦裝置及介質
WO2021218966A1 (zh) 设备检测方法、装置、设备、***、存储介质及程序产品
US20230244797A1 (en) Data processing method and apparatus, electronic device, and medium
CN111931222B (zh) 应用数据加密方法、装置、终端及存储介质
JP2003092603A (ja) ネットワーク侵入検知システム、装置及びプログラム
CN109543367B (zh) 基于量子加密的软件授权方法、装置及存储介质
KR101737747B1 (ko) 집계된 데이터의 탬퍼 방지 개선
US9842229B2 (en) Automated application analysis for finding leaked personal information
CN112825093A (zh) 安全基线检查方法、主机、服务器、电子设备及存储介质
CN105323287B (zh) 第三方应用程序的登录方法及***

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21797703

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21797703

Country of ref document: EP

Kind code of ref document: A1