CN116680681A

CN116680681A - Equipment burning data checking method, ioT platform and user terminal

Info

Publication number: CN116680681A
Application number: CN202310600818.6A
Authority: CN
Inventors: 王鹏飞
Original assignee: Alibaba Cloud Computing Ltd
Current assignee: Alibaba Cloud Computing Ltd
Priority date: 2023-05-22
Filing date: 2023-05-22
Publication date: 2023-09-01

Abstract

The application relates to a device burning data checking method, an internet of things (IoT) platform and a user side, and relates to the technical field of computers, wherein the method comprises the following steps: obtaining login data of each device logging in an IoT platform; when the equipment has abnormal login, determining equipment triggering behavior according to login data, and generating repeated burning judgment results according to the triggering behavior; and determining target login data in the login data according to the repeated burning judgment result, and sending the target login data to the user side so that the user side determines a device burning data checking result according to the target login data. According to the method and the system, analysis is carried out according to login time, platform identity, equipment self-defined identity and IP address, whether repeated burning exists or not is judged, target login data corresponding to equipment with abnormal login are sent to a user side, a user can obtain equipment burning data checking results at will, and potential safety hazards brought to equipment and an IoT platform user after repeated burning of the equipment are reduced.

Description

Equipment burning data checking method, ioT platform and user terminal

Technical Field

The present application relates to the field of computer technologies, and in particular, to a device burning data inspection method, an IoT platform, and a client.

Background

This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. It is not admitted to be prior art by inclusion of this description in this section.

IoT (Internet of Things ) platform is a software system based on cloud computing and big data technology for connecting, managing and controlling internet of things devices and data. The centralized management mode is provided, enterprises and individuals can be helped to easily manage the Internet of things equipment, interconnection and intercommunication among the equipment are realized, and the equipment data is analyzed and processed. Platform identities, typically issued by IoT platforms, are used to determine the legitimacy of devices upon device authentication. Device identity burning refers to writing unique identity information of a device into a non-volatile memory of the device to be read and used at device start-up. The platform identity may be burned into the device by a device identity burning technique. Existing equipment identity burning techniques may cause errors in equipment identity burning due to problems in manual or automatic procedures, for example, burning the same platform identity into two different devices. Device identity burning errors can seriously impact data security when IoT platforms and devices are used.

Disclosure of Invention

The equipment burning data checking method, the IoT platform and the user terminal provided by the embodiment of the application can at least solve the problem of potential safety hazard caused by equipment identity repetition.

According to an aspect of the present application, there is also provided a device burn-in data inspection method, including: obtaining login data of each device logging in an IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; when the equipment has abnormal login, determining equipment triggering behavior according to the login data, and generating repeated burning judgment results according to the triggering behavior; and determining target login data in the login data according to the repeated burning judgment result, and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data.

According to another aspect of the present application, there is also provided a device burn-in data inspection method, including: receiving target login data sent by the IoT platform; the target login data are determined according to repeated burning judgment results, the repeated burning judgment results are generated according to equipment triggering behaviors, and the equipment triggering behaviors are determined according to the login data when equipment is abnormal in login; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; and determining the test result of the equipment burning data according to the target login data.

According to another aspect of the present application, there is also provided an IoT platform comprising: the device comprises a data module, a determining module and a sending module; the data module is used for acquiring login data of all devices logged in the IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; the determining module is used for determining the behavior triggered by the equipment according to the login data when the equipment has login abnormality, and generating a repeated burning judgment result according to the triggered behavior; and the sending module is used for determining target login data in the login data according to the repeated burning judgment result and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data.

According to another aspect of the present application, there is also provided a client, including: a receiving module and a checking module; the receiving module is configured to receive target login data sent by the IoT platform; the target login data are determined according to repeated burning judgment results, the repeated burning judgment results are generated according to equipment triggering behaviors, and the equipment triggering behaviors are determined according to the login data when equipment is abnormal in login; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; and the checking module is used for determining the checking result of the equipment burning data according to the target login data.

According to another aspect of the present application, there is also provided an electronic apparatus including: a processor; and a memory storing a program, wherein the program comprises instructions that when executed by the processor cause the processor to perform a method according to the above.

According to another aspect of the application there is also provided a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method steps according to the above.

According to another aspect of the present application there is also provided a computer program product comprising a computer program which, when executed by a processor, implements the above-mentioned method steps.

The embodiment of the application has the beneficial effects that:

the embodiment of the application acquires login data of each device logged in an IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; when the equipment has abnormal login, determining equipment triggering behavior according to the login data, and generating repeated burning judgment results according to the triggering behavior; and determining target login data in the login data according to the repeated burning judgment result, and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data. According to the embodiment of the application, analysis is carried out according to the login time data, the platform identity data, the equipment self-defined identity data and the IP address data, whether repeated burning exists or not is judged, and a repeated burning judgment result is obtained, so that target login data corresponding to equipment with abnormal login is sent to a user side, a user can obtain an equipment burning data inspection result by himself, and potential safety hazards brought to equipment and an IoT platform user after repeated burning of the equipment are reduced.

The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below to provide a more thorough understanding of the other features, objects, and advantages of the invention.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It is evident that the drawings in the following description are only some embodiments of the invention, from which other embodiments can be obtained for a person skilled in the art without inventive effort.

FIG. 1 is a flowchart of a method for verifying device burn-in data according to an embodiment of the present invention;

FIG. 2 is a flowchart of a method for verifying device burn-in data according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of an embodiment of a method for verifying device burn-in data;

fig. 4 is a schematic structural view of the electronic device of the present embodiment;

FIG. 5 is a schematic diagram of an identity burning process;

FIG. 6 is a diagram of a second identity burning process;

FIG. 7 is an identity binding flow diagram;

fig. 8 is a schematic diagram of an authentication flow.

Detailed Description

Embodiments of the present embodiment will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present embodiments are illustrated in the accompanying drawings, it is to be understood that the present embodiments may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided to provide a more thorough and complete understanding of the present embodiments. It should be understood that the drawings and the embodiments of the present embodiments are presented for purposes of illustration only and are not intended to limit the scope of the embodiments.

Common identity burning technology at the equipment side comprises a flow control equipment identity burning technology and an automatic equipment identity burning technology.

Generally, a small enterprise can adopt a process control equipment identity burning technology, because the equipment quantity is relatively small, the manual mode is relatively controllable, and meanwhile, the input cost of an automatic program can be reduced by manual operation. Referring to fig. 5, which is a schematic diagram of an identity burning flow, the technology may be implemented as follows:

1. manually pulling device identities from an IoT platform;

2. storing the identity of the device in a data file, which may be an excel file or a database;

3. splitting the identities into a plurality of groups in a manual mode, wherein each burner is responsible for one group or a plurality of groups of identities;

4. the burner automatically burns the identity into different devices.

In the above steps, the probability of burning errors is relatively large due to the manual process involved.

Referring to fig. 6, an identity burning flow chart is shown, and an automatic equipment identity burning technology is adopted by a medium/large enterprise, so that the method is suitable for enterprises with large equipment quantity, and can achieve complete automation, safety and controllability.

1. Automatically pulling device identities from IoT platforms by way of platform APIs (Application Program Interface, application program interfaces)

2. Automatic storage of device identity into a data file, typically a database

3. Splitting identities into multiple groups by automatic program, each burner being responsible for one or more groups of identities

4. The burner automatically burns the identity into different devices.

In the above steps, if the automated process is problematic, a large number of burn-in errors may occur.

In principle, the burning accuracy of the equipment end needs to be ensured, but when errors are always caused, whether a robot or a human body is adopted, the errors easily cause great safety accidents for some equipment.

For example, the same identity is burned by different devices, and this situation occurs in the scene of the internet of things, which has a very large potential safety hazard, and brings panic to the user, and also has a very large influence on the reputation of the platform, for example: in the home security camera scene, a user can use a mobile phone APP (Application program) to check the home situation, if the identity is repeatedly burned, a video streaming problem occurs, that is, the user a may see the home situation of the user B, the user B may see the home situation of the user a, and once the situation occurs, the consequences cannot be assumed.

Based on the fact that the equipment production line may cause repeated burning of identities due to flow or program bug, the embodiment of the invention provides an equipment burning data checking method, an IoT platform and a user terminal. The embodiment of the invention combines the platform side identity and the big data analysis to reduce the influence of repeated equipment identity burning, so that the anti-duplication technology is not limited to the improvement of the equipment end, but the platform side is combined with the big data analysis capability to improve the problems, and the scheme can reduce the potential safety hazard brought to the user after repeated equipment burning.

The following description of the terms involved.

Cloud end integration: and (3) combining the equipment end and the platform end.

User discretion: the user decides himself.

Platform identity: are typically issued by IoT platforms to determine the legitimacy of the device at the time of device authentication, the device will burn the platform identity into the firmware.

SN (Serial Number): product serial number of the device.

MAC address (Media Access Control Address): the address for identifying the location of the network device may include network card information.

Device custom identity: typically determined by the device manufacturer, for determining the device's uniqueness, typically using information such as SN, MAC address, etc.

The equipment kicks each other: when the device logs in, the device logged in the previous time can be kicked off.

In the embodiment of the application, a device burning data checking method is provided, and the method can be applied to an IoT platform. Fig. 1 is a flowchart of a method for verifying device burn-in data according to an embodiment of the present application, and method steps involved in fig. 1 are described below.

Step S101, obtaining login data of each device logging in an IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data.

In this step, the IoT platform is a software system based on cloud computing and big data technology for connecting, managing and controlling the internet of things devices and data. The centralized management mode is provided, enterprises and individuals can be helped to easily manage and monitor the Internet of things equipment, interconnection and intercommunication among the equipment are realized, and equipment data are analyzed and processed.

Under the condition that the IoT platform and the cloud end of the device are integrated, login data of each device logging in the IoT platform are obtained, and different devices correspond to different login data. Wherein the login data is data related to device login, and may include: login time data, platform identity data, device custom identity data, and IP address data. The login time data is used to characterize information such as the moment and duration that the device is logged into the IoT platform. The platform identity data can be burnt to the equipment through a burning technology, and the platform distributes different platform identity data for different equipment. In particular implementations, a set of platform identity data may include account number data and password data, for example. The device custom identity data may be determined by the device manufacturer. The IP address data may be assigned to the device by internet service providers, each having its own IP address field. Thus, by querying the IP address field to which the IP address belongs, the internet service provider to which the device belongs can be determined.

It should be noted that cloud end integration means that cloud computing and internet of things technology are combined, and seamless connection and data interaction between the cloud end and the terminal device are achieved. The cloud integrated concept is derived from the development of the internet of things, and combines the powerful computing and storage capacity of cloud computing with the intelligent sensing and data acquisition capacity of the internet of things, so that the interconnection and intercommunication among devices and the real-time processing and analysis of data are realized. In the cloud integrated architecture, the terminal equipment collects and processes data through the sensor and the controller, the data are uploaded to the cloud, the cloud processes and analyzes the data through technologies such as big data analysis and machine learning, and finally the result is fed back to the terminal equipment. Cloud integrated application range comprises the fields of intelligent home, intelligent transportation, intelligent manufacturing and the like.

In the above steps, whenever the device performs an operation of logging in the IoT platform, whether logging in successfully or not, the login data of the device logging in the IoT platform may be obtained, so as to record the login data of each device logging in the IoT platform.

Step S102, when the equipment has abnormal login, determining equipment triggering behavior according to the login data, and generating repeated burning judgment results according to the triggering behavior.

In this step, the device login anomaly may be an anomaly of the device at the time of login, such as login failure, login timeout, login frequency, or the like. Such anomalies may be due to problems with the device itself, network connectivity problems or other external factors. Device login anomalies may cause devices to be out of normal use, such as out of access to a network, out of use of certain functions, etc.

When the equipment is abnormal in login, analyzing the equipment with abnormal login according to the acquired login time data, platform identity data, equipment self-defined identity data, IP address data and other login data, determining equipment triggering behavior, and generating repeated burning judgment results according to the triggering behavior.

The device-triggered behavior may be used to describe the login or use of the device. The login situation of a device can be described by describing the consistency of login data from device to device. For example, one possible trigger-ready behavior may be: in the login data of the first equipment and the second equipment, the identity data of the platform is consistent, but the self-defined identity data of the equipment is inconsistent.

The duplicate burn determination result may be used to determine whether duplicate burns exist between devices logged onto the IoT platform. And according to the equipment triggering behavior, carrying out big data analysis, and judging whether repeated burning exists among the equipment to obtain a repeated burning judgment result. For example, one possible repeated burning determination may be: and repeatedly burning the first device and the second device.

In the above steps, when the equipment has abnormal login, large data analysis is performed based on login data, so that a repeated burning judgment result can be obtained without controlling and adjusting the burning process of the equipment.

Step S103, determining target login data in the login data according to the repeated burning judgment result, and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data.

In the step, the repeated burning judgment result comprises equipment information with abnormal login, login data corresponding to equipment with abnormal login are used as target login data, the target login data are sent to a user side, and the user side determines equipment burning data checking results according to the target login data.

The device burning data checking result can be used for determining the device which is in abnormal login, the device which is in error burning and the device which is in correct burning.

In this step, the user terminal can be used by the device manufacturer, and the device manufacturer determines the device burn data verification result by using the user terminal.

In the above step, after determining the target login data based on the repeated burning judgment result, the target login data is sent to the user side, so that the user can obtain the equipment burning data inspection result by himself, and the data security problem caused by repeated burning is avoided.

The embodiment of the invention acquires login data of each device logged in an IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; when the equipment has abnormal login, determining equipment triggering behavior according to the login data, and generating repeated burning judgment results according to the triggering behavior; and determining target login data in the login data according to the repeated burning judgment result, and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data. According to the embodiment of the invention, analysis is carried out according to the login time data, the platform identity data, the equipment self-defined identity data and the IP address data, whether repeated burning exists or not is judged, and a repeated burning judgment result is obtained, so that target login data corresponding to equipment with abnormal login is sent to a user side, a user can obtain an equipment burning data inspection result by himself, and potential safety hazards brought to equipment and an IoT platform user after repeated burning of the equipment are reduced.

In one possible implementation, the login anomaly includes a device kick from each other; according to the login data, determining the equipment triggering behavior can be performed according to the following steps: if the platform identity data corresponding to the devices mutually kicked by the devices are the same and the device custom identity data are different, determining to trigger a first behavior; determining a first time length according to the login time data, and if the platform identity data corresponding to the devices which are mutually kicked by the devices are the same and the IP address data are different in the first time length, determining to trigger a second behavior.

In this possible implementation manner, the large data is used to analyze the login data of the device to determine whether there is a behavior of identity repetition, and specifically includes determining to trigger the first behavior if the platform identity data corresponding to the devices kicked by each other are the same and the device custom identity data are different. Determining a first time length according to the login time data, and if the platform identity data corresponding to the devices which are mutually kicked by the devices are the same and the IP address data are different in the first time length, determining to trigger a second behavior. By comparing and analyzing the login time data, the platform identity data, the equipment self-defined identity data and the IP address data among the equipment, the behavior triggered by the equipment is judged according to the consistency of the data, so that whether the platform identity data is repeatedly burnt into different equipment is judged.

After determining the device-triggered behavior, in one possible implementation, generating a repeated burning judgment result according to the triggered behavior may be performed according to the following steps:

when the first behavior and/or the second behavior trigger is detected, determining that repeated burning data exists among devices which are mutually kicked; and taking repeated burning data existing among the devices generating the mutual kicking of the devices as repeated burning judgment results.

In this possible implementation manner, in the case of device interaction, if a device triggers a first behavior and/or the second behavior, it is determined that repeated burning data exists between devices where device interaction occurs; and taking repeated burning data existing among the devices generating the mutual kicking of the devices as repeated burning judgment results.

Considering that the geographic location information and the operator information of the device can be approximately determined according to the IP address of the device, in a possible implementation manner, the IP address data are different, and the determination can be performed according to the following steps:

determining geographic position data and/or operator data of the equipment according to the IP address data; if the geographic position data of the equipment is different and/or the operator data of the equipment is different, the IP address data of the equipment is different.

In one possible implementation, before obtaining login data for each device logging into the IoT platform, the following steps may also be performed:

receiving login application data of each device, and judging whether each device logs in the IoT platform for the first time according to the login application data; the login application data comprise platform identity data and equipment self-defining identity data; if yes, setting an identity binding relation between the platform identity data and the equipment self-defined identity data, and authorizing access rights to all the equipment according to the identity binding relation; if not, verifying the identity binding relationship, and enabling the verified device to log in the IoT platform.

In this possible implementation, the device may send login application data to the IoT platform when logging into the IoT platform, the login application data including the platform identity data and the device custom identity data. And the IoT platform receives the login application data of each device, and judges whether each device logs in the IoT platform for the first time according to the login application data.

Referring to the identity binding flow diagram shown in fig. 7, if a device logs in to the IoT platform for the first time, an identity binding relationship between the platform identity data and the device custom identity data is set, and access rights are authorized to the devices according to the identity binding relationship. The platform identity and the device custom identity are bound at the time of device-to-platform activation, which is typically triggered the first time the device logs into the platform.

Referring to the authentication flow diagram shown in fig. 8, if a device is not first logged into the IoT platform, the identity binding relationship is authenticated such that the authenticated device logs into the IoT platform. When the equipment logs in to the platform, whether the equipment logs in for the first time is judged first, and if the equipment does not log in for the first time, the binding relation between the platform identity and the self-defined identity of the equipment is verified. Only if the binding relationship is legal, the device can log in normally.

Consider that a device binds an identity at the time of activation, that is, that identity is considered legitimate at the time of first sign-on. Then if an illegal device impersonates the identity of the normal device and the illegal device completes the first login, the normal device is never logged in instead. For this scenario, in one possible implementation, the login anomaly comprises a login failure; according to the login data, determining the equipment triggering behavior can be performed according to the following steps:

and if the platform identity data corresponding to the equipment with login failure is the same as the platform identity data corresponding to the equipment with login success, determining to trigger a third action.

In this possible embodiment, if one platform identity data is already used by a device that has been successfully logged in, then a device that subsequently re-uses the platform identity data to log in the IoT platform cannot log in successfully, so that login data of a device that has failed to log in and login data of a device that has been successfully logged in are obtained, and big data analysis is performed, if the platform identity data corresponding to the device that has failed to log in is the same as the platform identity data corresponding to the device that has been successfully logged in, it is indicated that repeated burning of the platform identity data may exist between the device that has failed to log in and the device that has been successfully logged in, and thus, it is determined that the third behavior is triggered.

In one possible implementation manner, the generating the repeated burning judgment result according to the triggered behavior may be performed according to the following steps:

when the third behavior trigger is detected, determining that repeated burning data exists between the equipment with login failure and the equipment with login success; and taking repeated burning data existing between the equipment with login failure and the equipment with login success as a repeated burning judgment result.

In this possible implementation manner, repeated writing data exists between the device with login failure and the device with login success, which indicates that the device with login failure may be a device with error writing or a device with correct writing, and the repeated writing data exists between the device with login failure and the device with login success as a repeated writing judgment result, so as to check whether the device with login success is a device with error writing or a device with correct writing, thereby ensuring the data security of the IoT platform and the device.

In one possible embodiment, the following steps may also be performed: receiving a device burning data inspection result; and modifying the identity binding relation according to the equipment burning data checking result.

In this possible implementation manner, after the user side determines the device logging data verification result according to the target login data, the device logging data verification result is sent to the IoT platform, and the IoT platform receives the device logging data verification result, so that the device that wrongly logs the platform identity data and the device that wrongly logs the platform identity data can be known, if the wrongly logged device is bound in the identity binding relationship, the wrongly logged device can be deleted, and the platform identity data and the correctly logged device are bound, so that the correctly logged device can be normally used subsequently, and the security of the IoT platform and the device that logs the IoT platform can be ensured.

Referring to the schematic implementation of the apparatus burn-in data verification method shown in fig. 3, a possible implementation of the method will be described below with a specific example.

First, collecting data related to device login, wherein the data comprises: login time + login IP + platform identity + device custom identity (MAC/SN).

And then, analyzing login data of the equipment through big data to judge whether the identity is repeated, wherein the judging process comprises the following steps:

preconditions are: the same equipment scene shows the condition that equipment kicks each other;

Three behaviors:

1) Behavior 1: the identity of the platform is consistent, and the self-defined identity of the equipment is inconsistent;

2) Behavior 2: within N minutes, the same equipment logs in each time in different cities;

3) Behavior 3, logging in the same equipment in different operators once in N minutes;

if the precondition is met and one or more actions are triggered, the identity of the equipment is considered to be burnt repeatedly or the identity of the equipment is falsified, and the platform informs the user side through a short message or mail.

The user side can see an abnormal device list at a console of the platform, and each piece of abnormal device information comprises:

1. equipment login time;

2. device custom identity (SN/MAC);

3. a city in which the device is logged in;

4. operator information for the device network;

the user side can determine which device is legal according to the abnormal information, and can directly set an effective binding relation in the console or the API gateway.

The invention provides a device burning data checking method, an internet of things (IoT) platform and a user side, and the method solves the problem of device impossibility in a cloud integrated technical scheme through three capabilities of big data analysis, early warning and user discretion, so that potential safety hazards of device identity repetition can be improved.

According to the above description, the IoT platform can analyze according to the login time data, the platform identity data, the device custom identity data and the IP address data, and determine whether the repeated burning exists, so as to obtain a repeated burning determination result, and thus send target login data corresponding to the device with abnormal login to the user side, so that the user can obtain a device burning data inspection result by himself, and potential safety hazards brought to the device and IoT platform user after repeated burning of the device are reduced. The above description is made from the IoT platform perspective and is described below from the user side perspective.

The embodiment of the application provides a device burning data checking method which can be applied to a user side. Fig. 2 is a second flowchart of a method for verifying device burn-in data according to an embodiment of the present application, and the method steps involved in fig. 2 are described below.

Step S201, receiving target login data sent by an IoT platform; the target login data are determined according to repeated burning judgment results, the repeated burning judgment results are generated according to equipment triggering behaviors, and the equipment triggering behaviors are determined according to the login data when equipment is abnormal in login; the login data comprises login time data, platform identity data, equipment self-defining identity data and IP address data.

The target login data can be sent to the user side by the IoT platform in the modes of short message notification, mail notification, APP notification, weChat notification and the like, and the user side receives the target login data sent by the IoT platform.

It should be noted that, under the condition that the IoT platform and the cloud of the device are integrated, the IoT platform obtains login data of each device logged in the IoT platform, and different devices correspond to different login data. Wherein the login data is data related to device login, and may include: login time data, platform identity data, device custom identity data, and IP address data. The login time data is used to characterize information such as the moment and duration that the device is logged into the IoT platform. The platform identity data can be burnt to the equipment through a burning technology, and the platform distributes different platform identity data for different equipment. In particular implementations, a set of platform identity data may include account number data and password data, for example. The device custom identity data may be determined by the device manufacturer. The IP address data may be assigned to the device by internet service providers, each having its own IP address field. Thus, by querying the IP address field to which the IP address belongs, the internet service provider to which the device belongs can be determined.

It should be further noted that cloud end integration means that cloud computing and internet of things technology are combined, and seamless connection and data interaction between the cloud end and the terminal device are achieved. The cloud integrated concept is derived from the development of the internet of things, and combines the powerful computing and storage capacity of cloud computing with the intelligent sensing and data acquisition capacity of the internet of things, so that the interconnection and intercommunication among devices and the real-time processing and analysis of data are realized. In the cloud integrated architecture, the terminal equipment collects and processes data through the sensor and the controller, the data are uploaded to the cloud, the cloud processes and analyzes the data through technologies such as big data analysis and machine learning, and finally the result is fed back to the terminal equipment. Cloud integrated application range comprises the fields of intelligent home, intelligent transportation, intelligent manufacturing and the like.

The device login anomaly may be an anomaly of the device when logging in, such as login failure, login timeout, login frequency, etc. Such anomalies may be due to problems with the device itself, network connectivity problems or other external factors. Device login anomalies may cause devices to be out of normal use, such as out of access to a network, out of use of certain functions, etc.

Step S202, determining the test result of the equipment burning data according to the target login data.

In this step, the user terminal can be used by the device manufacturer, and the device manufacturer determines the device burn data verification result by using the user terminal. The user side can identify the equipment which is correctly burnt and the equipment which is wrongly burnt based on the target login data, and a checking result of the equipment burnt data is obtained.

In the embodiment of the invention, target login data sent by the IoT platform is received; the target login data are determined according to repeated burning judgment results, the repeated burning judgment results are generated according to equipment triggering behaviors, and the equipment triggering behaviors are determined according to the login data when equipment is abnormal in login; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; and determining the test result of the equipment burning data according to the target login data. According to the embodiment of the invention, analysis is carried out according to the login time data, the platform identity data, the equipment self-defined identity data and the IP address data, whether repeated burning exists or not is judged, and a repeated burning judgment result is obtained, so that target login data corresponding to equipment with abnormal login is sent to a user side, a user can obtain an equipment burning data inspection result by himself, and potential safety hazards brought to equipment and an IoT platform user after repeated burning of the equipment are reduced.

In one possible embodiment, the following steps may also be performed: sending a device burning data inspection result to the IoT platform, so that the IoT platform modifies an identity binding relationship according to the device burning data inspection result; the identity binding relationship is used for representing a relationship between the platform identity data and the device custom identity data, and is also used for authorizing access rights to the devices when the devices log on the IoT platform.

In this possible implementation manner, after the user side determines the device logging data verification result according to the target login data, the device logging data verification result is sent to the IoT platform, and the IoT platform receives the device logging data verification result, so that the device that wrongly logs the platform identity data and the device that wrongly logs the platform identity data can be known, if the wrongly logged device is bound in the identity binding relationship, the wrongly logged device can be deleted, and the platform identity data and the correctly logged device are bound, so that the correctly logged device can be normally used subsequently, and the security of the IoT platform and the device that logs the IoT platform can be ensured. The identity binding relationship is used for representing a relationship between the platform identity data and the device custom identity data, and is also used for authorizing access rights to the devices when the devices log on the IoT platform.

Based on the above device burning data checking method provided by the embodiment of the present invention, the embodiment of the present invention further provides an IoT platform, which includes: the device comprises a data module, a determining module and a sending module; the data module is used for acquiring login data of all devices logged in the IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; the determining module is used for determining the behavior triggered by the equipment according to the login data when the equipment has login abnormality, and generating a repeated burning judgment result according to the triggered behavior; and the sending module is used for determining target login data in the login data according to the repeated burning judgment result and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data.

According to the IoT platform provided by the embodiment of the invention, analysis is performed according to the login time data, the platform identity data, the device custom identity data and the IP address data, whether repeated burning exists is judged, and a repeated burning judgment result is obtained, so that target login data corresponding to the device with abnormal login is sent to the user side, the user can obtain a device burning data inspection result by himself, and potential safety hazards brought to the device and IoT platform users after repeated burning of the device are reduced.

In one possible implementation, the login anomaly includes a device kick from each other; the determining module is specifically configured to: if the platform identity data corresponding to the devices mutually kicked by the devices are the same and the device custom identity data are different, determining to trigger a first behavior; determining a first time length according to the login time data, and if the platform identity data corresponding to the devices which are mutually kicked by the devices are the same and the IP address data are different in the first time length, determining to trigger a second behavior.

In a possible implementation manner, the determining module is specifically configured to: when the first behavior and/or the second behavior trigger is detected, determining that repeated burning data exists among devices which are mutually kicked; and taking repeated burning data existing among the devices generating the mutual kicking of the devices as repeated burning judgment results.

In a possible implementation manner, the determining module is specifically configured to: determining geographic position data and/or operator data of the equipment according to the IP address data; if the geographic position data of the equipment is different and/or the operator data of the equipment is different, the IP address data of the equipment is different.

In a possible embodiment, the method further comprises a preprocessing module for: receiving login application data of each device, and judging whether each device logs in the IoT platform for the first time according to the login application data; the login application data comprise platform identity data and equipment self-defining identity data; if yes, setting an identity binding relation between the platform identity data and the equipment self-defined identity data, and authorizing access rights to all the equipment according to the identity binding relation; if not, verifying the identity binding relationship, and enabling the verified device to log in the IoT platform.

In one possible implementation manner, the login anomaly includes login failure, and the determining module is specifically configured to: and if the platform identity data corresponding to the equipment with login failure is the same as the platform identity data corresponding to the equipment with login success, determining to trigger a third action.

In a possible implementation manner, the determining module is specifically configured to: when the third behavior trigger is detected, determining that repeated burning data exists between the equipment with login failure and the equipment with login success; and taking repeated burning data existing between the equipment with login failure and the equipment with login success as a repeated burning judgment result.

In a possible embodiment, the device further comprises an adjustment module for: receiving a device burning data inspection result; and modifying the identity binding relation according to the equipment burning data checking result.

Based on the method for checking the equipment burning data provided by the embodiment of the invention, the embodiment of the invention also provides a user side, which comprises the following steps: a receiving module and a checking module; the receiving module is configured to receive target login data sent by the IoT platform; the target login data are determined according to repeated burning judgment results, the repeated burning judgment results are generated according to equipment triggering behaviors, and the equipment triggering behaviors are determined according to the login data when equipment is abnormal in login; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data; and the checking module is used for determining the checking result of the equipment burning data according to the target login data.

According to the client provided by the embodiment of the invention, the client is used for analyzing according to the login time data, the platform identity data, the equipment self-defined identity data and the IP address data, judging whether repeated burning exists or not, and obtaining the repeated burning judgment result, so that the target login data corresponding to the equipment with abnormal login is sent to the client, the user can obtain the equipment burning data inspection result by himself, and potential safety hazards brought to the equipment and an IoT platform user after repeated burning of the equipment are reduced.

In one possible implementation, the method further includes a result module for: sending a device burning data inspection result to the IoT platform, so that the IoT platform modifies an identity binding relationship according to the device burning data inspection result; the identity binding relationship is used for representing a relationship between the platform identity data and the device custom identity data, and is also used for authorizing access rights to the devices when the devices log on the IoT platform.

The embodiment of the invention also provides electronic equipment, which comprises: at least one processor; and a memory communicatively coupled to the at least one processor. The memory stores a computer program executable by the at least one processor, which when executed by the at least one processor is adapted to cause an electronic device to perform a method of an embodiment of the invention.

The embodiments of the present invention also provide a non-transitory machine-readable medium storing a computer program, wherein the computer program is configured to cause a computer to perform the method of the embodiments of the present invention when executed by a processor of the computer.

The embodiments of the present invention also provide a computer program product comprising a computer program, wherein the computer program, when being executed by a processor of a computer, is for causing the computer to perform the method of the embodiments of the present invention.

With reference to fig. 4, a block diagram of an electronic device that may be a server or a client of an embodiment of the present invention will now be described, which is an example of a hardware device that may be applied to aspects of the present invention. Electronic devices are intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 4, the electronic device includes a computing unit 401 that can perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM) 402 or a computer program loaded from a storage unit 408 into a Random Access Memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the electronic device can also be stored. The computing unit 401, ROM 402, and RAM 403 are connected to each other by a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.

A number of components in the electronic device are connected to the I/O interface 405, including: an input unit 406, an output unit 407, a storage unit 408, and a communication unit 409. The input unit 406 may be any type of device capable of inputting information to an electronic device, and the input unit 406 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device. The output unit 407 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. Storage unit 408 may include, but is not limited to, magnetic disks, optical disks. The communication unit 409 allows the electronic device to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, such as bluetooth devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.

The computing unit 401 may be a variety of general purpose and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 401 include, but are not limited to, a CPU, a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 401 performs the respective methods and processes described above. For example, in some embodiments, method embodiments of the present invention may be implemented as a computer program tangibly embodied on a machine-readable medium, such as storage unit 408. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device via the ROM 402 and/or the communication unit 409. In some embodiments, the computing unit 401 may be configured to perform the above-described methods by any other suitable means (e.g., by means of firmware).

A computer program for implementing the methods of embodiments of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of embodiments of the present invention, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable signal medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

It should be noted that the term "comprising" and its variants as used in the embodiments of the present invention are open-ended, i.e. "including but not limited to". The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. References to "one or more" modifications in the examples of the invention are intended to be illustrative rather than limiting, and it will be understood by those skilled in the art that "one or more" is intended to be interpreted as "one or more" unless the context clearly indicates otherwise.

User information (including but not limited to user equipment information, user personal information and the like) and data (including but not limited to data for analysis, stored data, presented data and the like) according to the embodiment of the invention are information and data authorized by a user or fully authorized by all parties, and the collection, use and processing of related data are required to comply with related laws and regulations and standards of related countries and regions, and are provided with corresponding operation entrances for users to select authorization or rejection.

The steps described in the method embodiments provided in the embodiments of the present invention may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the invention is not limited in this respect.

The term "embodiment" in this specification means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the invention. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive. The various embodiments in this specification are described in a related manner, with identical and similar parts being referred to each other. In particular, for apparatus, devices, system embodiments, the description is relatively simple as it is substantially similar to method embodiments, see for relevant part of the description of method embodiments.

The above examples merely represent a few embodiments of the present invention, which are described in more detail and are not to be construed as limiting the scope of the patent claims. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the invention, which are all within the scope of the invention. Accordingly, the scope of the invention should be assessed as that of the appended claims.

Claims

1. A device burn-in data verification method, comprising:

obtaining login data of each device logging in an IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data;

when the equipment has abnormal login, determining equipment triggering behavior according to the login data, and generating repeated burning judgment results according to the triggering behavior;

and determining target login data in the login data according to the repeated burning judgment result, and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data.

2. The method of claim 1, wherein the login anomaly comprises a device kick from each other; determining the behavior triggered by the equipment according to the login data, wherein the method comprises the following steps:

if the platform identity data corresponding to the devices mutually kicked by the devices are the same and the device custom identity data are different, determining to trigger a first behavior;

determining a first time length according to the login time data, and if the platform identity data corresponding to the devices which are mutually kicked by the devices are the same and the IP address data are different in the first time length, determining to trigger a second behavior.

3. The method of claim 2, wherein generating a repeat burning determination from the triggered behavior comprises:

when the first behavior and/or the second behavior trigger is detected, determining that repeated burning data exists among devices which are mutually kicked;

and taking repeated burning data existing among the devices generating the mutual kicking of the devices as repeated burning judgment results.

4. The method of claim 2, wherein the IP address data is different, comprising:

determining geographic position data and/or operator data of the equipment according to the IP address data;

if the geographic position data of the equipment is different and/or the operator data of the equipment is different, the IP address data of the equipment is different.

5. The method of any of claims 1-4, wherein prior to obtaining login data for each device logging into the IoT platform, further comprising:

receiving login application data of each device, and judging whether each device logs in the IoT platform for the first time according to the login application data; the login application data comprise platform identity data and equipment self-defining identity data;

if yes, setting an identity binding relation between the platform identity data and the equipment self-defined identity data, and authorizing access rights to all the equipment according to the identity binding relation;

If not, verifying the identity binding relationship, and enabling the verified device to log in the IoT platform.

6. The method of claim 5, wherein the login anomaly comprises a login failure; determining the behavior triggered by the equipment according to the login data, wherein the method comprises the following steps:

7. The method of claim 6, wherein generating a repeat burn determination from the triggered behavior comprises:

when the third behavior trigger is detected, determining that repeated burning data exists between the equipment with login failure and the equipment with login success;

and taking repeated burning data existing between the equipment with login failure and the equipment with login success as a repeated burning judgment result.

8. The method of claim 5, further comprising:

receiving a device burning data inspection result;

and modifying the identity binding relation according to the equipment burning data checking result.

9. A device burn-in data verification method, comprising:

Receiving target login data sent by an internet of things (IoT) platform; the target login data are determined according to repeated burning judgment results, the repeated burning judgment results are generated according to equipment triggering behaviors, and the equipment triggering behaviors are determined according to the login data when equipment is abnormal in login; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data;

and determining the test result of the equipment burning data according to the target login data.

10. The method of claim 9, further comprising:

sending a device burning data inspection result to the IoT platform, so that the IoT platform modifies an identity binding relationship according to the device burning data inspection result; the identity binding relationship is used for representing a relationship between the platform identity data and the device custom identity data, and is also used for authorizing access rights to the devices when the devices log on the IoT platform.

11. An IoT platform, comprising: the device comprises a data module, a determining module and a sending module;

the data module is used for acquiring login data of all devices logged in the IoT platform; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data;

The determining module is used for determining the behavior triggered by the equipment according to the login data when the equipment has login abnormality, and generating a repeated burning judgment result according to the triggered behavior;

and the sending module is used for determining target login data in the login data according to the repeated burning judgment result and sending the target login data to a user side so that the user side determines a device burning data checking result according to the target login data.

12. A client, comprising: a receiving module and a checking module;

the receiving module is used for receiving target login data sent by an internet of things (IoT) platform; the target login data are determined according to repeated burning judgment results, the repeated burning judgment results are generated according to equipment triggering behaviors, and the equipment triggering behaviors are determined according to the login data when equipment is abnormal in login; the login data comprise login time data, platform identity data, equipment self-defined identity data and IP address data;

and the checking module is used for determining the checking result of the equipment burning data according to the target login data.

13. An electronic device, comprising: a processor, and a memory storing a program, wherein the program comprises instructions that when executed by the processor cause the processor to perform the method of any of claims 1-10.

14. A non-transitory machine readable medium having stored thereon computer instructions for causing the computer to perform the method according to any one of claims 1-10.

15. A computer program product, wherein the computer program product comprises a computer program which, when executed by a processor, implements the method of any of claims 1-10.