A method, apparatus, electronic device, and storage medium for binding batch devices.

Abstract

This invention discloses a method, apparatus, electronic device, and storage medium for binding batch devices. The method includes: determining at least one unbound device based on the public IP address of at least one bound device matching a target account; determining candidate devices among the unbound devices based on at least two identification parameters of the unbound devices; wherein the candidate devices are unbound devices that meet the identification parameter filtering conditions; sending verification identifiers to the bound devices and candidate devices to enable multicast communication verification between the candidate devices and the bound devices; if the target candidate device passes the multicast communication verification, then using the target candidate device as a recommended device for binding the target account; wherein the target candidate device is the candidate device among the candidate devices that passes the multicast communication verification. This solution facilitates the rapid binding of batch devices under the same public network but in different virtual local area networks.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, apparatus, electronic device, and storage medium for binding batch devices. Background Technology

[0002] With the increasing demand and application scenarios for video surveillance equipment, in some application scenarios, video surveillance equipment will be deployed in batches, requiring the batch of devices to be bound to the target account.

[0003] Existing device binding methods mainly include two types. The first is to obtain the unique identifier of each video surveillance device and send each unique identifier along with the unique identifier of the target account to the server. The server then binds the target account to each video surveillance device. However, this method requires obtaining the unique identifier of each video surveillance device sequentially, which is slow and costly. The second method involves connecting the client corresponding to the device to be bound and the target account to the same network. The client then broadcasts a query for devices not bound to the target account within that network, sending the unique identifiers of the unbound devices and the target account to the server for binding. However, this method requires both the device to be bound and the client to be connected to the same network. In real-world scenarios, these batches of video surveillance devices are distributed across different VLANs (Virtual Local Area Networks), and broadcast communication does not support cross-VLAN communication. Therefore, this method cannot solve the problem of binding batches of devices on the same public network but in different VLANs. Summary of the Invention

[0004] This invention provides a method, apparatus, electronic device, and storage medium for binding batch devices, so as to achieve rapid binding of batch devices in different VLANs under the same public network.

[0005] In a first aspect, embodiments of the present invention provide a method for binding batch devices, the method comprising:

[0006] Based on the public IP address of at least one bound device that matches the target account, identify at least one unbound device;

[0007] Candidate devices are determined from the unbound devices based on at least two identification parameters of the unbound devices; wherein, the candidate devices are unbound devices that meet the identification parameter filtering conditions;

[0008] Send verification identifiers to both bound devices and candidate devices to enable multicast communication verification between candidate devices and bound devices;

[0009] If the target candidate device is determined to pass the multicast communication verification, then the target candidate device is used as the recommended device for target account binding; wherein, the target candidate device is the candidate device that has passed the multicast communication verification among the candidate devices.

[0010] Secondly, embodiments of the present invention also provide a binding device for batch devices, the device comprising:

[0011] The unbound device determination module is used to determine at least one unbound device based on the public IP address of at least one bound device that matches the target account;

[0012] A candidate device determination module is used to determine candidate devices among unbound devices based on at least two identification parameters of the unbound devices; wherein, the candidate devices are unbound devices that meet the identification parameter filtering conditions;

[0013] The verification identifier sending module is used to send verification identifiers to bound devices and candidate devices, so that candidate devices can perform multicast communication verification with bound devices;

[0014] The target account binding module is used to, if it is determined that the target candidate device passes the multicast communication verification, use the target candidate device as a recommended device, and bind the target account according to the recommended device; wherein, the target candidate device is the candidate device that has passed the multicast communication verification among the candidate devices.

[0015] Thirdly, embodiments of the present invention also provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement a batch device binding method as described in any of the embodiments of the present invention.

[0016] Fourthly, embodiments of the present invention also provide a storage medium for storing computer-executable instructions, which, when executed by a computer processor, are used to perform a batch device binding method as described in any of the embodiments of the present invention.

[0017] The technical solution of this invention determines at least one unbound device based on the public IP address of at least one bound device matching the target account; then, based on at least two identification parameters of the unbound device, a candidate device is determined from the unbound devices; verification identifiers are then sent to both the bound device and the candidate device to enable multicast communication verification between the candidate device and the bound device; if the target candidate device passes the multicast communication verification, it is designated as the recommended device for binding the target account. This solution solves the problems of slow binding speed and high cost of binding batches of devices under different virtual LANs on the same public network, enabling rapid binding of batches of devices, improving binding efficiency, and reducing binding costs.

[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

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

[0020] Figure 1 This is a flowchart of a batch device binding method provided in Embodiment 1 of the present invention;

[0021] Figure 2 This is a flowchart of a batch device binding method provided in Embodiment 2 of the present invention;

[0022] Figure 3 This is a schematic diagram of the structure of a batch equipment binding device provided in Embodiment 3 of the present invention;

[0023] Figure 4 This is a schematic diagram of the structure of a computer device provided in Embodiment 4 of the present invention. Detailed Implementation

[0024] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0026] Example 1

[0027] Figure 1 The flowchart of a batch device binding method provided in Embodiment 1 of the present invention is applicable to batch device binding scenarios under different virtual LANs on the same public network. The method can be executed by a batch device binding device, which can be implemented in hardware and / or software and can be configured in a computer device.

[0028] like Figure 1 As shown, the method includes:

[0029] S110. Based on the public IP address of at least one bound device that matches the target account, determine at least one unbound device.

[0030] For example, in a specific scenario, this solution can be executed by the device management service of a video surveillance platform. Users can access the video surveillance platform by logging in with a pre-registered account. The video surveillance platform can include a device management service and a client. The device management service can manage video surveillance devices, such as binding them. All video surveillance devices can be connected to the same public network. The target account can be the user account currently accessing the video surveillance platform. Each user account can be associated with one or more video surveillance devices. The device management service can store a list of binding statuses for video surveillance devices, recording the binding status of each device with a user account. Based on the public network address of the bound devices associated with the target account, the device management service can filter out unbound devices under that public network from the binding status list.

[0031] In this solution, optionally, at least one unbound device is determined based on the public IP address of at least one bound device matching the target account, including:

[0032] If the number of bound devices matching the target account within the preset time period is greater than or equal to the preset number, then obtain the public IP address of the bound devices;

[0033] Based on the public IP address of the bound device, determine the unbound device that matches the public IP address.

[0034] The device management service triggers a rapid batch device binding mechanism when it detects that the number of bound devices matching the target account within a preset time period reaches or exceeds a preset limit. The preset time period can start from the time the device management service detects continuous device binding by the target account, and the end time can be determined based on a preset duration elapsed from the start time. The preset limit can be one or more. The device management service can obtain the identification parameters of the preset number of bound devices to obtain their public IP addresses.

[0035] If the public IP addresses of the preset number of bound devices are all the same, the device management service can determine the video surveillance devices in the unbound state based on the binding status list, and then filter out the unbound video surveillance devices that match the public IP addresses of the bound devices. The unbound devices that match the public IP addresses can be the same as the public IP addresses of the bound devices.

[0036] If the public IP addresses of the preset number of bound devices are different, for example, if 6 bound devices have public IP address A and 4 bound devices have public IP address B, the device management service can determine the matching unbound devices for each public IP address.

[0037] This solution can filter possible unbound devices under a target account based on the public IP address of the devices already bound to the target account, which helps to narrow down the search range for unbound devices and thus achieve fast and accurate batch device binding.

[0038] S120. Based on at least two identification parameters of the unbound devices, determine the candidate devices among the unbound devices.

[0039] As is easily understood, video surveillance devices can maintain contact with the device management service and report their identification parameters. These parameters may include the device identifier, public IP address, initial keep-alive time, geographical location, device model, media access control address, and PTZ capabilities. The identification parameters of batch-bound video surveillance devices typically have the following properties:

[0040] (1) Same public IP address;

[0041] (2) Similar virtual LAN addresses;

[0042] (3) The initial survival time was similar;

[0043] (4) Geographically close;

[0044] (5) The equipment models are similar;

[0045] (6) Similar media access control addresses;

[0046] (7) All support virtual LAN multicast communication.

[0047] The device management service can determine candidate devices among unbound devices based on the association relationship of the identification parameters of video surveillance devices bound in the same batch, according to the identification parameters of unbound devices and the identification parameters of bound devices in the same batch. The candidate devices can be unbound devices that meet the identification parameter filtering conditions. The device management service can use at least two identification parameters to make a preliminary judgment on whether an unbound device belongs to the same batch as a bound device. For example, the device management service can perform preliminary filtering of unbound devices based on their virtual LAN address and first keep-alive time. The identification parameter filtering conditions are based on selected identification parameter settings. For example, the identification parameter filtering conditions may include a virtual LAN address similarity higher than a preset similarity threshold, and a time interval between the first keep-alive time of the target unbound device and the first keep-alive time of the bound device being lower than a preset time interval threshold. If the virtual LAN address of the target unbound device is more similar to that of the bound device than the preset similarity threshold, and the time interval between the first keep-alive time of the target unbound device and the first keep-alive time of the bound device is lower than the preset time interval threshold, the device management service can determine the target unbound device as a candidate device.

[0048] In one feasible approach, candidate devices are identified from among the unbound devices based on at least two identification parameters of the unbound devices, including:

[0049] Calculate the batch similarity between unbound devices and bound devices based on at least two identifier parameters of unbound devices;

[0050] Candidate devices are identified from the unbound devices based on the batch similarity between unbound devices and bound devices.

[0051] The device management service can calculate batch similarity between unbound and bound devices using at least two of the identification parameters. For example, the device management service uses two identification parameters—Virtual Local Area Network (VLAN) address and first keep-alive time—to determine batch similarity between unbound and bound devices. For instance, there is a bound device 'a' with a VLAN address of 192.168.1.0 and a first keep-alive time of 2022.08.09 12:00:00. An unbound device 'a' has a VLAN address of 192.168.1.2 and a first keep-alive time of 2022.08.09 12:00:10. The device management service can use the ratio of identical address bits to the total address bits as the similarity calculation result for VLAN addresses, and the time difference between the first keep-alive times of bound device 'a' and unbound device 'a' as the similarity calculation result for first keep-alive times. The device management service can use the sum of the similarity calculation results of the virtual LAN addresses and the similarity calculation results of the first keep-alive time as the batch similarity between bound device A and unbound device A. Alternatively, the device management service can calculate the cosine similarity between 192.168.1.0 and 192.168.1.2, and the cosine similarity between 2022.08.0912:00:00 and 2022.08.0912:00:10, and use the sum of the cosine similarity of the virtual LAN addresses and the cosine similarity of the first keep-alive time as the batch similarity between bound device A and unbound device A.

[0052] The device management service can sort the batch similarity of unbound devices associated with the same batch of bound devices, select a preset number of unbound devices with the highest batch similarity, or select unbound devices with batch similarity exceeding a preset similarity threshold as candidate devices.

[0053] The above solution calculates the batch similarity between unbound and bound devices based on the identification parameters, and then filters candidate devices based on the similarity, which can effectively narrow the search range, thereby improving the binding efficiency of device management services and realizing automated batch device binding.

[0054] S130. Send verification identifiers to the bound device and the candidate device to enable the candidate device to perform multicast communication verification with the bound device.

[0055] Since all video surveillance devices bound in batches support virtual LAN multicast communication, the device management service can send verification identifiers to both bound devices and candidate devices to determine whether the candidate devices can communicate with the bound devices via multicast, thereby verifying the candidate devices. Multicast communication can be a one-to-many communication mode between video surveillance devices. The verification identifier can be determined based on time and the device identifier of the bound devices.

[0056] S140. If it is determined that the target candidate device passes the multicast communication verification, then the target candidate device is used as the recommended device, and the target account is bound according to the recommended device.

[0057] After sending verification identifiers to both bound devices and candidate devices, candidate devices can carry these identifiers and trigger multicast communication based on the network information of the bound devices. Bound devices can verify the verification identifiers upon receiving the multicast communication. The bound device replies with a verification pass message to the candidate devices that passed the multicast communication verification, and designates these candidate devices as target candidate devices. Target candidate devices, upon receiving the verification pass message, can report this to the device management service. The device management service can then identify the target candidate device that passed the multicast communication verification as a recommended device and bind it to the target account. Specifically, the device management service can feed back information such as the target candidate device's virtual LAN address and device type to the client, allowing the user to select the target candidate device according to their needs and request the device management service to complete the target account binding.

[0058] The technical solution of this invention determines at least one unbound device based on the public IP address of at least one bound device matching the target account; then, based on at least two identification parameters of the unbound device, a candidate device is determined from the unbound devices; verification identifiers are then sent to both the bound device and the candidate device to enable multicast communication verification between the candidate device and the bound device; if the target candidate device passes the multicast communication verification, it is designated as the recommended device for binding the target account. This solution solves the problems of slow binding speed and high cost of binding batches of devices under different virtual LANs on the same public network, enabling rapid binding of batches of devices, improving binding efficiency, and reducing binding costs.

[0059] Example 2

[0060] Figure 2 This is a flowchart of a batch device binding method provided in Embodiment 2 of the present invention. Based on the above embodiments, the present invention further specifies the batch device binding method.

[0061] like Figure 2 As shown, the method includes:

[0062] S210. If it is determined that the number of bound devices matching the target account within the preset time period is greater than or equal to the preset number, then obtain the public IP address of the bound devices.

[0063] S220. Based on the public network address of the bound device, determine the unbound device that matches the public network address.

[0064] S230. Determine the identification parameters of the bound devices.

[0065] Video surveillance devices can maintain contact with the device management service and report their identification parameters. The device management service can retrieve the identification parameters reported by the bound devices. In this solution, the identification parameters may optionally include at least two of the following: LAN address, first keep-alive time, geographical location, device model, and media access control address. The LAN address can be the address of the video surveillance device in the virtual LAN. The first keep-alive time can be the recorded time when the video surveillance device first maintains contact with the device management service. The geographical location can be the deployment location of the video surveillance device. The device model can be set by the device manufacturer according to national, local, and industry standards, reflecting the performance, quality, and specifications of the video surveillance device. The media access control address can be an identifier that identifies a virtual LAN node.

[0066] S240. Calculate the similarity of each identifier parameter based on the identifier parameters of the unbound device and the identifier parameters of the bound device.

[0067] The device management service can group unbound and bound devices with the same public IP address into groups and calculate the similarity between the identifier parameters of the unbound devices and the corresponding identifier parameters of the bound devices in each group. The device management service can define the calculation method for each identifier parameter similarity. Specifically, LAN address similarity can be determined based on the number of identical bits in the LAN addresses of the unbound and bound devices. For example, if the bound device's LAN address is 192.168.1.0 and the unbound device's LAN address is 192.168.1.2, the device management service can define the value between the separators as one bit. In the example above, the number of identical bits between the bound and unbound LAN addresses is 3, the total number of bits in the LAN addresses is 4, and the LAN address similarity can be 75%.

[0068] The initial keep-alive time similarity can be determined based on the difference between the initial keep-alive times of unbound and bound devices. The device management service can pre-segment the initial keep-alive time difference into segments, such as 1-3 hours and 3-5 hours, and assign a proximity score to each segment, for example, 90% for 1-3 hours and 80% for 3-5 hours. For the same bound device, the initial keep-alive time difference for each unbound device is assigned to its respective segment, and the similarity score for each segment is used as the initial keep-alive time similarity.

[0069] Geographic similarity can be determined based on the geographical distance between unbound and bound devices. Similar to the similarity of initial keep-alive time, the device management service can also pre-segment the geographical distance, set a proximity score for each segment, and for the same bound device, divide the address location distance of each unbound device into its respective segment, and use the proximity score of each segment as the geographical similarity score.

[0070] Device model similarity can be determined based on whether the unbound and bound devices have the same model number. For example, if the unbound and bound devices have the same model number, the device model similarity is 100%; if the unbound and bound devices have different model numbers, the device model similarity is 0.

[0071] Similar to LAN address similarity, media access control (MAC) address similarity can be determined based on the number of identical bits in the MAC addresses of unbound and bound devices. For example, if the MAC address of a bound device is 08:00:20:0A:8C:6D, and the MAC address of an unbound device is 08:00:20:0A:8C:5E, and the device management service defines a hexadecimal number as one digit, then in the above example, the number of identical bits in the MAC addresses of the bound and unbound devices is 10, and the total number of bits in the MAC addresses is 12. Therefore, the MAC address similarity can be approximately 83%.

[0072] S250. The sum of the products of the similarity corresponding to each identifier parameter and the weight of each identifier parameter is used as the batch similarity between unbound devices and bound devices.

[0073] The device management service can configure weights for each identification parameter, and these weights can be the same or different. The service can calculate a weighted sum of the identification parameters, which is the sum of the products of the similarity of each parameter and its weight. This weighted sum is used as the batch similarity between unbound and bound devices. For example, if the LAN address similarity and first keep-alive time similarity are 75% and 90% respectively, and both parameters have a weight of 50%, the weighted sum can be (75% + 90%) × 50% = 82.5%, resulting in a batch similarity of 82.5%. Alternatively, the weights for LAN address and first keep-alive time can be set to 70% and 30% respectively, resulting in a weighted sum of 75% × 70% + 90% × 30% = 79.5%, also resulting in a batch similarity of 79.5%.

[0074] This solution comprehensively considers the impact of multiple identification parameters on the similarity between unbound and bound devices, which is beneficial for accurately locating candidate devices.

[0075] S260. Based on the batch similarity between unbound devices and bound devices, determine candidate devices among the unbound devices.

[0076] S270. Generate a verification identifier based on the time information and the identity identifier of the bound device.

[0077] The device management service can generate a verification identifier based on the current time and the identity identifier of the bound device. The identity identifier of the bound device can be an identifier that indicates the uniqueness of the bound device, such as the device identifier of the bound device, or a management identifier assigned to the bound device by the device management service.

[0078] S280. Send a verification identifier to the bound device, and send the verification identifier and the network information of the bound device to the candidate device, so that the candidate device and the bound device can perform multicast communication verification.

[0079] The device management service can send verification identifiers to bound devices, and send verification identifiers and network information of bound devices to candidate devices. The network information of bound devices may include their IP address, multicast IP address, and other information.

[0080] This scheme verifies the multicast communication of candidate devices by generating verification identifiers, which helps to accurately locate recommended devices and ensure the reliability of batch binding.

[0081] S290. If it is determined that the target candidate device passes the multicast communication verification, then the target candidate device is used as the recommended device, and the target account is bound according to the recommended device.

[0082] Based on the above scheme, the target candidate device is verified through multicast communication, including:

[0083] If it is determined that the multicast communication verification report information sent by the target candidate device has been received, then it is determined that the target candidate device has passed the multicast communication verification.

[0084] The multicast communication verification reporting information is generated by the target candidate device after establishing multicast communication with the target bound device based on the verification identifier and the network information of the target bound device, and after receiving the verification identifier verification pass instruction from the target bound device.

[0085] Understandably, candidate devices can trigger multicast communication based on the network information of the bound devices, carrying a verification identifier. The bound devices can verify the verification identifier upon receiving the multicast communication. For example, the verification identifier could be an interface identifier, and the verification could be implemented using RPF (Reverse Path Forwarding) verification. If the RPF interface matches the arrival interface of the multicast message, the verification passes; otherwise, it fails. If the verification passes, the bound device replies with the verification success information to the target candidate device. Upon receiving the verification success information, the target candidate device can generate multicast communication verification reporting information and report it to the device management service. This multicast communication verification reporting information can include the verification result, verification time, and the address of the verifying device.

[0086] This solution effectively ensures the reliability of the target candidate device verification through multicast communication, thereby achieving fast and accurate device binding.

[0087] The technical solution of this invention determines at least one unbound device based on the public IP address of at least one bound device matching the target account; then, based on at least two identification parameters of the unbound device, a candidate device is determined from the unbound devices; verification identifiers are then sent to both the bound device and the candidate device to enable multicast communication verification between the candidate device and the bound device; if the target candidate device passes the multicast communication verification, it is designated as the recommended device for binding the target account. This solution solves the problems of slow binding speed and high cost of binding batches of devices under different virtual LANs on the same public network, enabling rapid binding of batches of devices, improving binding efficiency, and reducing binding costs.

[0088] Example 3

[0089] Figure 3 This is a schematic diagram of a batch equipment binding device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes:

[0090] The unbound device determination module 310 is used to determine at least one unbound device based on the public IP address of at least one bound device that matches the target account;

[0091] The candidate device determination module 320 is used to determine candidate devices among unbound devices based on at least two identification parameters of the unbound devices; wherein, the candidate devices are unbound devices that meet the identification parameter filtering conditions;

[0092] The verification identifier sending module 330 is used to send verification identifiers to the bound device and the candidate device, so that the candidate device and the bound device can perform multicast communication verification.

[0093] The target account binding module 340 is used to bind the target candidate device as a recommended device if it is determined that the target candidate device passes the multicast communication verification, so as to bind the target account according to the recommended device; wherein, the target candidate device is the candidate device that passes the multicast communication verification among the candidate devices.

[0094] In this solution, the unbound device determination module 310 includes:

[0095] The public IP address acquisition unit is used to acquire the public IP address of the bound device if the number of bound devices matching the target account within a preset time period is greater than or equal to a preset number.

[0096] The unbound device determination unit is used to determine the unbound device that matches the public network address of the bound device.

[0097] In one feasible embodiment, the candidate device determination module 320 includes:

[0098] The similarity calculation unit is used to calculate the batch similarity between unbound devices and bound devices based on at least two identifier parameters of the unbound devices;

[0099] The candidate device determination unit is used to determine candidate devices among unbound devices based on the batch similarity between unbound devices and bound devices.

[0100] Based on the above scheme, the similarity calculation unit includes:

[0101] The identification parameter determination subunit is used to determine the identification parameters of the bound devices;

[0102] The similarity calculation subunit is used to calculate the similarity of each identifier parameter based on each identifier parameter of the unbound device and each identifier parameter of the bound device.

[0103] The similarity determination subunit is used to sum the products of the similarity of each identifier parameter and the weight of each identifier parameter, and use this as the batch similarity between unbound devices and bound devices.

[0104] Optionally, the identification parameters include at least two of the following: local area network address, first keep-alive time, geographical location, device model, and media access control address.

[0105] In a preferred embodiment, the verification identifier sending module 330 includes:

[0106] The verification identifier generation unit is used to generate a verification identifier based on time information and the identity identifier of the bound device;

[0107] The verification identifier sending unit is used to send a verification identifier to the bound device, and to send a verification identifier and the network information of the bound device to the candidate device.

[0108] Based on the above solution, optionally, the target account binding module 340 is specifically used for:

[0109] If it is determined that the multicast communication verification report information sent by the target candidate device has been received, then it is determined that the target candidate device has passed the multicast communication verification.

[0110] The multicast communication verification reporting information is generated by the target candidate device after establishing multicast communication with the target bound device based on the verification identifier and the network information of the target bound device, and after receiving the verification identifier verification pass instruction from the target bound device; wherein, the target bound device is the bound device that sent the multicast communication verification reporting information.

[0111] The batch device binding device provided in the embodiments of the present invention can execute the batch device binding method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0112] Example 4

[0113] Figure 4 This is a schematic diagram of the structure of a computer device provided in Embodiment 4 of the present invention, as shown below. Figure 4 As shown, the computer device includes a processor 40, a memory 41, an input device 42, and an output device 43; the number of processors 40 in the computer device can be one or more. Figure 4 Taking a processor 40 as an example; the processor 40, memory 41, input device 42, and output device 43 in a computer device can be connected via a bus or other means. Figure 4 Taking the example of a connection between China and Israel via a bus.

[0114] The memory 41, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the modules corresponding to the batch device binding method in this embodiment of the invention (e.g., the unbound device determination module 310, the candidate device determination module 320, the verification identifier sending module 330, and the target account binding module 340 in the batch device binding device). The processor 40 executes various functional applications and data processing of the computer device by running the software programs, instructions, and modules stored in the memory 41, thereby implementing the aforementioned batch device binding method. This method includes:

[0115] Based on the public IP address of at least one bound device that matches the target account, identify at least one unbound device;

[0116] Candidate devices are determined from the unbound devices based on at least two identification parameters of the unbound devices; wherein, the candidate devices are unbound devices that meet the identification parameter filtering conditions;

[0117] Send verification identifiers to both bound devices and candidate devices to enable multicast communication verification between candidate devices and bound devices;

[0118] If the target candidate device is determined to pass the multicast communication verification, then the target candidate device is used as the recommended device for target account binding; wherein, the target candidate device is the candidate device that has passed the multicast communication verification among the candidate devices.

[0119] The memory 41 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on terminal usage. Furthermore, the memory 41 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. In some instances, the memory 41 may further include memory remotely located relative to the processor 40, which can be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0120] Input device 42 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the computer device. Output device 43 may include display devices such as a display screen.

[0121] Example 5

[0122] Embodiment 5 of the present invention also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a batch device binding method, the method comprising:

[0123] Based on the public IP address of at least one bound device that matches the target account, identify at least one unbound device;

[0124] Candidate devices are determined from the unbound devices based on at least two identification parameters; wherein, the candidate devices are unbound devices that meet the identification parameter filtering conditions.

[0125] Send verification identifiers to both bound devices and candidate devices to enable multicast communication verification between candidate devices and bound devices;

[0126] If the target candidate device is determined to pass the multicast communication verification, then the target candidate device is used as the recommended device for target account binding; wherein, the target candidate device is the candidate device that has passed the multicast communication verification among the candidate devices.

[0127] Of course, the computer-executable instructions provided in the embodiments of the present invention are not limited to the method operations described above, but can also perform related operations in the batch device binding method provided in any embodiment of the present invention.

[0128] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0129] It is worth noting that in the above-mentioned embodiment of the batch device binding device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0130] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A method for binding batch devices, characterized in that, include: Based on the public IP address of at least one bound device that matches the target account, identify at least one unbound device; Candidate devices are determined from the unbound devices based on at least two identification parameters of the unbound devices; wherein, the candidate devices are unbound devices that meet the identification parameter filtering conditions; Send verification identifiers to both bound devices and candidate devices to enable multicast communication verification between candidate devices and bound devices; If the target candidate device is determined to pass the multicast communication verification, then the target candidate device is used as the recommended device for target account binding; wherein, the target candidate device is the candidate device that has passed the multicast communication verification among the candidate devices.

2. The method according to claim 1, characterized in that, Based on the public IP address of at least one bound device matching the target account, identify at least one unbound device, including: If the number of bound devices matching the target account within the preset time period is greater than or equal to the preset number, then obtain the public IP address of the bound devices; Based on the public IP address of the bound device, determine the unbound device that matches the public IP address.

3. The method according to claim 1, characterized in that, Candidate devices are identified from the unbound devices based on at least two identification parameters, including: Calculate the batch similarity between unbound devices and bound devices based on at least two identifier parameters of unbound devices; Candidate devices are identified from the unbound devices based on the batch similarity between unbound devices and bound devices; The step of calculating the batch similarity between unbound devices and bound devices based on at least two identifier parameters of unbound devices includes: Determine the identification parameters of the bound devices; Calculate the similarity of each identifier parameter based on the identifier parameters of the unbound device and the identifier parameters of the bound device. The sum of the products of the similarity of each identifier parameter and the weight of each identifier parameter is used as the batch similarity between unbound devices and bound devices.

4. The method according to claim 3, characterized in that, The identification parameters include at least two of the following: local area network address, first keep-alive time, geographical location, device model, and media access control address.

5. The method according to claim 1, characterized in that, Send verification identifiers to bound devices and candidate devices, including: Generate a verification identifier based on the time information and the identity of the bound device; Send a verification identifier to the bound device, and send the verification identifier and the network information of the bound device to the candidate device.

6. The method according to claim 5, characterized in that, The determination of target candidate devices is verified through multicast communication, including: If it is determined that the multicast communication verification report information sent by the target candidate device has been received, then it is determined that the target candidate device has passed the multicast communication verification. The multicast communication verification reporting information is generated by the target candidate device after establishing multicast communication with the target bound device based on the verification identifier and the network information of the target bound device, and after receiving the verification identifier verification pass instruction from the target bound device; wherein, the target bound device is the bound device that sent the multicast communication verification reporting information.

7. A binding device for batch equipment, characterized in that, include: The unbound device determination module is used to determine at least one unbound device based on the public IP address of at least one bound device that matches the target account; A candidate device determination module is used to determine candidate devices among unbound devices based on at least two identification parameters of the unbound devices; wherein, the candidate devices are unbound devices that meet the identification parameter filtering conditions; The verification identifier sending module is used to send verification identifiers to bound devices and candidate devices, so that candidate devices can perform multicast communication verification with bound devices; The target account binding module is used to, if it is determined that the target candidate device passes the multicast communication verification, use the target candidate device as a recommended device, and bind the target account according to the recommended device; wherein, the target candidate device is the candidate device that has passed the multicast communication verification among the candidate devices.

8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the batch device binding method as described in any one of claims 1-6.

9. A storage medium for storing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the batch device binding method as described in any one of claims 1-6.

Images