CN115866595A - Device authorization method, device, device and storage medium - Google Patents

Abstract

The present application discloses a device authorization method, device, device, and storage medium. The method includes: after a collision between the master device and the slave device, determine whether the master device and the slave device meet the networking conditions; if the The master device and the slave device meet the networking conditions, the master device obtains the device information of the slave device; the master device distributes domain identification information to the slave device, and uploads the domain identification information to the cloud server , authorizing the slave device, so as to improve the security of device authorization.

Description

Device authorization method, device, device and storage medium

technical field

The present application relates to the technical field of communications, and in particular to a device authorization method, device, device and storage medium.

Background technique

With the continuous development and progress of computer network technology, a variety of new smart devices have entered people's daily life and work, and play an important role in human production activities. The information interconnection of multiple devices requires authentication and authorization of the devices to be connected, so that the collaboration and data sharing between different devices can be completed smoothly. At present, device authentication and authorization are generally carried out through Bluetooth or WiFi (Wireless Fidelity, Wireless Fidelity). During data transmission, due to the use of wireless technology, data transmission is easily intercepted or monitored, especially Bluetooth When authentication is performed between devices, since the encrypted channel has not yet been generated, its security is not guaranteed.

Therefore, how to improve the security of device authorization has become an urgent problem to be solved.

Contents of the invention

Embodiments of the present application provide a device authorization method, device, device, and storage medium, which can improve the security of device authorization.

In the first aspect, the embodiment of the present application provides a device authorization method, the device authorization method includes:

After the master device and the slave device collide, determine whether the master device and the slave device meet the networking conditions;

If the master device and the slave device meet the networking conditions, the master device obtains the device information of the slave device;

The master device distributes domain identification information to the slave device, uploads the domain identification information to a cloud server, and authorizes the slave device.

In the second aspect, the embodiment of the present application also provides a device authorization device, the device authorization device includes a processor and a memory, a computer program is stored in the memory, and when the processor invokes the computer program in the memory Execute the device authorization method described above.

In a third aspect, an embodiment of the present application further provides a device, the device including the device authorization apparatus as described above.

In a fourth aspect, the embodiment of the present application further provides a storage medium, where the storage medium is used to store a computer program, and when the computer program is executed by a processor, the processor implements the above device authorization method.

The embodiment of the present application provides a device authorization method, device, device, and storage medium. After the master device and the slave device touch each other, it is determined whether the master device and the slave device meet the networking conditions. If the master device and the slave device meet the networking conditions Conditions, the master device obtains the device information of the slave device, after that, the master device distributes the domain identification information to the slave device, and uploads the domain identification information to the cloud server to authorize the slave device, because the master device is very close to the slave device The slave device is authorized within a distance, which improves the security of device authorization.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1 is a schematic flowchart of the steps of a device authorization method provided in an embodiment of the present application;

Fig. 2 is a schematic diagram of a device interaction system provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of an interactive process of device authorization provided by an embodiment of the present application;

Fig. 4 is a schematic diagram of another device authorization interaction process provided by the embodiment of the present application;

Fig. 5 is a schematic block diagram of a device authorization apparatus provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, not to limit the present application. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

It should be noted that the descriptions in this application involving "first", "second" and so on are for descriptive purposes only, and should not be understood as indicating or implying their relative importance or implicitly indicating the number of indicated technical features . Thus, the features defined as "first" and "second" may explicitly or implicitly include at least one of these features.

Reference to "one embodiment" or "some embodiments" or the like in the specification of the present application means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in some embodiments," etc. in various places in this specification are not necessarily all References to the same embodiment mean "one or more but not all" unless specifically stated otherwise. The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless specifically stated otherwise.

In addition, the technical solutions of the various embodiments can be combined with each other, but it must be based on the realization of those skilled in the art. When the combination of technical solutions is contradictory or cannot be realized, it should be considered that the combination of technical solutions does not exist , nor within the scope of protection required by the present application.

The flow charts shown in the drawings are just illustrations, and do not necessarily include all contents and operations/steps, nor must they be performed in the order described. For example, some operations/steps can be decomposed, combined or partly combined, so the actual order of execution may be changed according to the actual situation.

With the continuous development and progress of computer network technology, a variety of new smart devices have entered people's daily life and work, and play an important role in human production activities. The information interconnection of multiple devices requires authentication and authorization of the devices to be connected, so that the collaboration and data sharing between different devices can be completed smoothly. At present, device authentication and authorization are generally carried out through Bluetooth or WiFi (Wireless Fidelity, Wireless Fidelity). During data transmission, due to the use of wireless technology, data transmission is easily intercepted or monitored, especially Bluetooth When authentication is performed between devices, since the encrypted channel has not yet been generated, its security is not guaranteed.

In order to solve the above problems, an embodiment of the present application provides a device authorization method, device, device, and storage medium, wherein the method determines whether the master device and the slave device are Satisfy the networking conditions; if the master device and the slave device meet the networking conditions, the master device obtains the device information of the slave device; the master device distributes domain identification information to the slave device, and sends the The domain identification information is uploaded to the cloud server, and the slave device is authorized. Because the slave device is authorized within a very close distance between the master device and the slave device, the security of device authorization is improved.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a device authorization method provided in an embodiment of the present application. The method can be applied to a device, where the device can be a mobile phone, a camera, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality ( Any one of augmented reality (AR)/virtual reality (virtual reality, VR) equipment, notebook computer, personal computer (personal computer, PC), netbook, personal digital assistant (personal digital assistant, PDA), in the embodiment of this application No restrictions are imposed.

As shown in FIG. 1 , the device authorization method provided by the embodiment of the present application includes steps S101 to S103.

S101. After a collision between the master device and the slave device, determine whether the master device and the slave device meet a networking condition.

Exemplarily, both the master device and the slave device are provided with NFC (Near Field Communication, near field communication) modules. Relying on NFC's near-field touch transmission capability, the master device and the slave device touch each other, and each sends its own device type information to the other party. The device type information includes but is not limited to the master device type, slave device type, and slave device. Simultaneously connect to multiple master devices, slave devices are only allowed to connect to one master device at a time, etc. According to the device type information of the slave device, determine whether the master device and the slave device meet the networking conditions.

Exemplarily, determining whether the master device and the slave device meet the networking conditions includes:

The device type of the slave device is only allowed to be connected to one master device at the same time, and the slave device is currently not connected to other master devices; or

The device type of the slave device allows simultaneous connection with multiple master devices.

For example, if the device type of the slave device is only allowed to be connected to one master device at a time, it is checked whether the slave device has currently established a connection with other master devices. If the slave device has already established a connection with other master devices, the master device and the slave device can no longer establish a connection, and the master device and the slave device do not meet the networking conditions. Conversely, if the slave device is not currently connected to other master devices, the master device and the slave device can establish a connection, and the master device and the slave device meet the networking conditions.

For another example, if the device type of the slave device allows simultaneous connection with multiple master devices, the master device and the slave device can establish a connection, and the master device and the slave device meet the networking conditions.

It should be noted that if the device type of the slave device has been determined in advance to allow simultaneous connection with multiple master devices, the operation of determining whether the master device and the slave device meet the networking conditions can be omitted, depending on the specific application scenario , without limitation.

S102. If the master device and the slave device meet a networking condition, the master device obtains device information of the slave device.

If the master device and the slave device meet the networking conditions, that is, the master device and the slave device can establish a connection, at this time, the slave device sends its own device information to the master device, and the master device obtains the device information of the slave device. Wherein, the device information includes but not limited to information such as device version and device ID.

S103. The master device distributes domain identification information to the slave device, uploads the domain identification information to a cloud server, and authorizes the slave device.

After the master device obtains the device information of the slave device, the master device distributes the domain identification information to the slave device, and uploads the domain identification information to the cloud server at the same time, and the cloud server saves the domain identification information. Among them, the domain identification information refers to a collection of a series of IP addresses, and only devices in the same domain can perform authentication networking. The cloud server manages the devices corresponding to each domain identification information in the domain through one or more stored domain identification information. The master device sets permissions for the slave devices. Exemplarily, the permissions of the slave devices include but not limited to common permissions, administrator permissions, and other types. For example, the master device sets the permissions of the slave devices to normal permissions.

For example, as shown in Figure 2, the slave devices include slave device A, slave device B ... slave device N, etc., and the master device touches each slave device P2P (peer-to-peer, peer-to-peer technology), The master device obtains the device information of slave device A, slave device B...slave device N, and then, the master device distributes corresponding domain identification information to slave device A, slave device B...slave device N respectively, and identifies the corresponding domain The information is uploaded to the cloud server, and the master device sets permissions for slave device A, slave device B...slave device N.

In some embodiments, the master device distributes domain identification information to the slave device, uploads the domain identification information to a cloud server, and authorizes the slave device, including:

The master device distributes the domain identification information to the slave device, uploads the domain identification information to the cloud server, and sets the authority of the slave device as normal authority by default.

After the master device obtains the device information of the slave device, the master device distributes domain identification information to the slave device, and at the same time uploads the domain identification information to the cloud server. After receiving the domain identification information, the slave device writes the domain identification information locally, and sets the slave device's authority to normal authority by default.

For example, as shown in Figure 3, the master device touches the slave device, the slave device sends its own device information to the master device, the master device obtains the device information of the slave device, and then the master device distributes domain identification information to the slave device. At the same time, The master device uploads the domain identification information to the cloud server, and the cloud server stores the received domain identification information. After receiving the domain identification information from the device, write the domain identification information, and set the normal authority by default.

In other embodiments, the master device distributes domain identification information to the slave device, uploads the domain identification information to a cloud server, and authorizes the slave device, including:

The master device distributes the domain identification information and general authority information to the slave device, uploads the domain identification information to the cloud server, and sets the authority of the slave device to normal based on the general authority information. permission.

The difference from the above embodiment is that after the master device obtains the device information of the slave device, the master device not only distributes the domain identification information to the slave device, but also distributes the general authority information to the slave device, and at the same time uploads the domain identification information to the cloud server. After receiving the domain identification information and common authority information, the slave device writes the domain identification information, and sets the authority of the slave device as normal authority based on the general authority information. Both set the permissions of the slave device to normal permissions, the difference is that one is set to normal permissions by default, and the other is set to normal permissions based on normal permission information.

In some embodiments, the master device distributes domain identification information to the slave device, and uploads the domain identification information to a cloud server, and after setting permissions on the slave device, includes:

The master device distributes administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information.

Since there are administrator rights in addition to ordinary rights, when the rights of a slave device are to be set as administrator rights, the master device sends administrator rights information to the slave device, and based on the administrator rights information, the rights of the slave device Set to administrator privileges.

In some embodiments, the master device distributes administrator authority information to the slave device, and before setting the authority of the slave device to administrator authority based on the administrator authority information, includes:

The master device determines whether the slave device is an intra-domain device according to the device information of the slave device;

The master device distributes administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information, including:

If the slave device is an intra-domain device, the master device distributes the administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information.

In order to be able to successfully set the administrator authority, when it is necessary to determine the authorized administrator, that is, to be set as a slave device with administrator authority, the master device determines whether the slave device is an intra-domain device based on the device information of the slave device. The slave device is eligible to set administrator privileges.

If the slave device is an intra-domain device, the master device sends administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information. On the contrary, if the slave device is not a device in the domain, then the slave device is not qualified to set administrator rights.

In some embodiments, the master device distributes administrator authority information to the slave device, and after setting the authority of the slave device to administrator authority based on the administrator authority information, includes:

uploading the administrator authority information of the slave device to the cloud server, so that the cloud server stores the administrator authority information of the slave device.

After successfully setting the authority of the slave device to the administrator authority, the master device uploads the administrator authority information of the slave device to the cloud server, and the cloud server stores the administrator authority information of the slave device. The cloud server manages the slave device with the administrator authority through the stored administrator authority information.

Exemplarily, after the administrator authority is set successfully on the slave device, the master device outputs a message that the administrator authority has been delivered successfully. For example, the display screen of the main device displays a message that the administrator authority has been successfully issued. The user can timely receive the success message of issuing the administrator authority, so as to know that the current authority of the slave device is the administrator authority, which further improves the user experience.

For example, as shown in Figure 4, when the master device selects an authorized administrator, the master device first obtains the device information of the slave device, and determines whether the slave device is an intra-domain device according to the device information of the slave device. If the slave device is an intra-domain device, Then the master device issues administrator authority information to the slave device, and sets administrator authority for the slave device based on the administrator authority information. After the administrator authority is successfully set for the slave device, the administrator authority success message is displayed, and the master device uploads the administrator authority information of the slave device to the cloud server, and the cloud server stores the administrator authority information of the slave device.

In this application, the P2P transmission method of NFC is used to carry out the data interaction between the master device and the slave device. Compared with the data transmission through Bluetooth, WiFi, etc., it not only improves the speed of the master device and the slave device to discover each other and transmit data , that is, to achieve faster data transmission and enhance the user experience; at the same time, the master device and the slave device need to be close enough to complete the data transmission during the touch process, which reduces the probability of being intercepted or monitored during the data transmission process. Data interaction will be performed with other devices, therefore, a more secure authorization is realized.

In the above embodiment, after the master device and the slave device touch each other, it is determined whether the master device and the slave device meet the networking conditions. If the master device and the slave device meet the networking conditions, the master device obtains the device information of the slave device. After that, the master device The device distributes domain identification information to the slave device, uploads the domain identification information to the cloud server, and authorizes the slave device. Since the slave device is authorized within a short distance between the master device and the slave device, the security of device authorization is improved. sex.

Please refer to FIG. 5 . FIG. 5 is a schematic block diagram of a device authorization apparatus provided in an embodiment of the present application.

As shown in FIG. 5 , the device authorization apparatus 200 may include a processor 211 and a memory 212, and the processor 211 and the memory 212 are connected through a bus, such as an I2C (Inter-integrated Circuit) bus.

Specifically, the processor 211 may be a micro-controller unit (Micro-controller Unit, MCU), a central processing unit (Central Processing Unit, CPU), or a digital signal processor (Digital Signal Processor, DSP), etc.

Specifically, the memory 212 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) disk, an optical disk, a U disk, or a mobile hard disk. Various computer programs to be executed by the processor 211 are stored in the memory 212 .

Wherein, the processor 211 is used to run a computer program stored in the memory processor 211, and implement the following steps when executing the computer program:

After the master device and the slave device collide, determine whether the master device and the slave device meet the networking conditions;

If the master device and the slave device meet the networking conditions, the master device obtains the device information of the slave device;

The master device distributes domain identification information to the slave device, uploads the domain identification information to a cloud server, and authorizes the slave device.

In some embodiments, the processor 211 is used to implement:

The master device distributes the domain identification information to the slave device, uploads the domain identification information to the cloud server, and sets the authority of the slave device as normal authority by default.

In some embodiments, the processor 211 is used to implement:

The master device distributes the domain identification information and general authority information to the slave device, uploads the domain identification information to the cloud server, and sets the authority of the slave device to normal based on the general authority information. authority.

In some embodiments, the processor 211 realizes that the master device distributes domain identification information to the slave device, uploads the domain identification information to the cloud server, and sets the authority of the slave device. :

The master device distributes administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information.

In some embodiments, before the processor 211 realizes that the master device distributes administrator authority information to the slave device, and sets the authority of the slave device as an administrator authority based on the administrator authority information, it is used to implement :

The master device determines whether the slave device is an intra-domain device according to the device information of the slave device;

The processor 211 is configured to realize:

If the slave device is an intra-domain device, the master device distributes the administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information.

In some embodiments, after the processor 211 realizes that the master device distributes administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information, it is used to implement :

uploading the administrator authority information of the slave device to the cloud server, so that the cloud server stores the administrator authority information of the slave device.

In some embodiments, the master device and the slave device meeting the networking conditions include:

The device type of the slave device is only allowed to be connected to one master device at the same time, and the slave device is currently not connected to other master devices; or

The device type of the slave device allows simultaneous connection with multiple master devices.

An embodiment of the present application also provides a device, the type of which includes but is not limited to mobile phones, cameras, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (augmented reality, AR)/virtual reality (virtual reality, VR) ) device, notebook computer, personal computer (personal computer, PC), netbook, personal digital assistant (personal digital assistant, PDA), etc., there is no limitation in this embodiment of the application.

Wherein, the device includes a device authorization device. Exemplarily, the device authorization device may be the device authorization device 200 described in the foregoing embodiments. The device can execute any of the device authorization methods provided in the embodiments of the present application, and therefore, can achieve the beneficial effects that can be achieved by any of the device authorization methods provided in the embodiments of the present application. For details, see the previous embodiments. Here No longer.

An embodiment of the present application also provides a storage medium, the storage medium stores a computer program, the computer program includes program instructions, and the processor executes the program instructions to implement the device authorization method provided in the above embodiments A step of. For example, the computer program is loaded by the processor and may perform the following steps:

After the master device and the slave device collide, determine whether the master device and the slave device meet the networking conditions;

If the master device and the slave device meet the networking conditions, the master device obtains the device information of the slave device;

The master device distributes domain identification information to the slave device, uploads the domain identification information to a cloud server, and authorizes the slave device.

For the specific implementation of the above operations, reference may be made to the foregoing embodiments, and details are not repeated here.

Wherein, the storage medium may be an internal storage unit of the device authorization device or device in the foregoing embodiments, such as a hard disk or memory of the device authorization device or device. The storage medium can also be an external storage device of the device authorization device or the device, such as a plug-in hard disk equipped on the device authorization device or the device, a smart memory card (Smart MediaCard, SMC), a secure digital (Secure Digital, SD) card , Flash Card (Flash Card) and so on.

Since the computer program stored in the storage medium can execute any of the device authorization methods provided in the embodiments of the present application, therefore, the beneficial effects that can be achieved by any of the device authorization methods provided in the embodiments of the present application can be realized , refer to the previous embodiments for details, and will not be repeated here.

The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structures or equivalent process transformations made by using the description of the application and the accompanying drawings are directly or indirectly used in other related technical fields. , are all included in the patent protection scope of the present application in the same way.

Claims (10)

1. A device authorization method, characterized in that the device authorization method comprises:

after the master device and the slave device collide with each other, determining whether the master device and the slave device meet networking conditions;

if the master device and the slave device meet networking conditions, the master device obtains device information of the slave device;

and the master device dispatches the domain identification information to the slave device, uploads the domain identification information to a cloud server, and authorizes the slave device.

2. The method of claim 1, wherein the master device dispatches domain identification information to the slave device and uploads the domain identification information to a cloud server, and the authorization of the slave device comprises:

and the master equipment dispatches the domain identification information to the slave equipment, uploads the domain identification information to the cloud server, and sets the authority default of the slave equipment as a common authority.

3. The method of claim 2, wherein the master device dispatches domain identification information to the slave device and uploads the domain identification information to a cloud server, and the authorization of the slave device comprises:

and the master device dispatches the domain identification information and the common authority information to the slave device, uploads the domain identification information to the cloud server, and sets the authority of the slave device as the common authority based on the common authority information.

4. The method according to claim 2 or 3, wherein the master device dispatches domain identification information to the slave device and uploads the domain identification information to a cloud server, and after the slave device is subjected to the permission setting, the method comprises:

the master device distributes administrator authority information to the slave device, and sets the authority of the slave device as administrator authority based on the administrator authority information.

5. The method of claim 4, wherein the master device dispatching administrator authority information to the slave device, before setting the authority of the slave device to administrator authority based on the administrator authority information, comprises:

the master device determines whether the slave device is an intra-domain device according to the device information of the slave device;

the method for the master device to dispatch the administrator authority information to the slave device and set the authority of the slave device as the administrator authority based on the administrator authority information comprises the following steps:

if the slave equipment is intra-domain equipment, the master equipment distributes the administrator permission information to the slave equipment, and the permission of the slave equipment is set as administrator permission based on the administrator permission information.

6. The method according to claim 4, wherein the master device sends administrator authority information to the slave device, and after setting the authority of the slave device as administrator authority based on the administrator authority information, the method comprises:

and uploading administrator permission information of the slave equipment to the cloud server so that the cloud server stores the administrator permission information of the slave equipment.

7. The method according to any one of claims 1 to 6, wherein the master device and the slave device satisfying a networking condition comprises:

the device type of the slave device is only allowed to be connected with one master device at the same time, and the slave device is not connected with other master devices currently; or

The slave device is of a device type that allows simultaneous connection with multiple master devices.

8. A device authorization apparatus, characterized in that the device authorization apparatus comprises a processor, a memory, the memory storing a computer program executable by the processor, the computer program, when executed by the processor, implementing the device authorization method according to any of claims 1 to 7.

9. A device, characterized in that the device comprises the device authorization apparatus according to claim 8.

10. A storage medium for computer readable storage, wherein the storage medium stores one or more programs which are executable by one or more processors to implement the steps of the device authorization method of any of claims 1 to 7.

Images