A migration method of an internet of things cluster user

Abstract

The application discloses a kind of migration methods of Internet of Things cluster user, comprising: determining target user needing migration and the destination cluster to be migrated and greater capacity in source cluster;In source cluster, close target user equipment and the new operation of subscription;Through cross-cluster user migration service, all user information of target user access source cluster is synchronized from source cluster to destination cluster;By the way of user-level domain name switching address, the address of target user's application access Internet of Things is changed from the address of source cluster to the address of destination cluster, and user application changes from interfacing with source cluster to interfacing with destination cluster, only needs to interface with one cluster, without modifying user application;According to the equipment quantity of target user access source cluster, batchwise target user's equipment is accessed to destination cluster, and user is migrated from small-capacity source cluster to large-capacity destination cluster, realizes the expansion of the cluster where user is located, and the application can be widely applied in Internet of Things field.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and in particular to a method for migrating IoT cluster users. Background Technology

[0002] With the rapid development of IoT services, the number of devices connected to IoT platforms is experiencing explosive growth, gradually revealing bottlenecks in the capacity and performance of individual IoT clusters. To ensure service stability, existing technologies typically deploy multiple clusters to increase the device access capacity of the IoT platform, with different users connecting to different clusters. However, considering that the number of user devices connected to the existing cluster may grow rapidly, causing the existing cluster capacity to be unable to meet the usage needs of these users, connecting these new devices to a new cluster would require user applications to simultaneously connect to two IoT clusters. This complicates the user application integration process and necessitates modifications to existing applications, thus limiting cluster scalability to some extent.

[0003] Therefore, this invention provides a migration scheme for IoT cluster users, which can avoid user application modification during user expansion and also avoid user applications connecting to multiple clusters simultaneously. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a migration scheme for IoT cluster users, so as to avoid user application modification during user expansion and also to avoid user applications connecting to multiple clusters at the same time.

[0005] One aspect of this invention provides a method for migrating IoT cluster users, comprising:

[0006] In the source cluster, identify the target user to be migrated and determine the destination cluster to which the target user is to be migrated, wherein the remaining capacity of the destination cluster is greater than the capacity of the user to be migrated.

[0007] Disable new operations and subscription additions for the target user device in the source cluster;

[0008] The user information of the target user is synchronized from the source cluster to the destination cluster through the cross-cluster user migration service. The user information includes all information about the target user's access to the source cluster.

[0009] By switching the address of the user-level domain name, the address of the target user's application access to the Internet of Things platform is changed from the address of the source cluster to the address of the destination cluster;

[0010] Based on the number of devices connected to the source cluster by the target user, the target user's devices are connected to the destination cluster in batches.

[0011] Preferably, if the target user makes an operation request during the migration process, the method further includes:

[0012] If the operation request is a device operation request, the processing method for the device operation request is determined according to the cluster to which the first device requesting the operation is currently connected.

[0013] If the operation request is a non-device operation request, then the non-device operation request is processed in the destination cluster.

[0014] Preferably, if the operation request is a device operation request, then determining the processing method for the device operation request based on the cluster currently connected to the first device requesting the operation includes:

[0015] If the cluster currently accessed by the first device is the target cluster, then the device operation request is processed in the target cluster;

[0016] If the cluster currently accessed by the first device is the source cluster, then the ID of the source cluster and the bizUrl of the access path of the device operation request are added to the header of the device operation request, and the device operation request is forwarded to the cross-cluster routing service of the destination cluster; the cross-cluster routing service of the destination cluster forwards the device operation request to the cross-cluster routing service of the source cluster according to the ID of the destination cluster; the cross-cluster routing service of the source cluster calls the service corresponding to the bizUrl to process the device operation request.

[0017] Preferably, the step of forwarding the device operation request to the source cluster via the cross-cluster routing service of the destination cluster based on the ID of the destination cluster includes:

[0018] The destination cluster ID is obtained from the header of the device operation request through the cross-cluster routing service of the destination cluster;

[0019] The destination access address and destination access credentials corresponding to the ID of the destination cluster are obtained from the pre-stored service information locally through the cross-cluster routing service of the destination cluster.

[0020] The cross-cluster routing service of the destination cluster forwards the device operation request to the destination access address according to the authentication requirements of the destination access credential.

[0021] Preferably, after processing the device operation request according to the bizUrl via the destination cross-cluster routing service, the method further includes:

[0022] The processing result of the device operation request is returned to the destination cross-cluster routing service through the cross-cluster routing service of the source cluster.

[0023] Preferably, the migration process of the target user further includes:

[0024] The uplink messages from the target user's second device are pushed to the target user's application by the cluster currently connected to the second device, according to the target user's subscription rules.

[0025] Preferably, after the target user migration is completed, the process further includes:

[0026] Clean up the user information in the source cluster.

[0027] Another aspect of the present invention provides a migration device for IoT cluster users, comprising:

[0028] The migration target determination unit is used to determine the target user to be migrated in the source cluster and to determine the destination cluster to which the target user is to be migrated, wherein the remaining capacity of the destination cluster is greater than the capacity of the user to be migrated.

[0029] A new operation shutdown unit is added, which is used to shut down the new operation and subscription new operation of the target user device in the source cluster;

[0030] The user information synchronization unit is used to synchronize the user information of the target user from the source cluster to the destination cluster through the cross-cluster user migration service. The user information includes all information about the target user's access to the source cluster.

[0031] The access address change unit is used to change the address of the target user's application access to the Internet of Things platform from the address of the source cluster to the address of the destination cluster by switching the address through a user-level domain name;

[0032] The user equipment migration unit is used to connect the target user's devices to the destination cluster in batches according to the number of devices connected to the source cluster by the target user.

[0033] Another aspect of the present invention provides an electronic device, including a processor and a memory;

[0034] The memory is used to store programs;

[0035] The processor executes the program to implement the above-described method for migrating IoT cluster users.

[0036] Another aspect of this invention provides a computer-readable storage medium storing a program that is executed by a processor to implement the above-described method for migrating users of an IoT cluster.

[0037] This invention also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the aforementioned IoT cluster user migration method.

[0038] This invention provides a method for migrating IoT cluster users. First, the cluster management service can determine the target user to be migrated and the destination cluster for the target user's migration within the source cluster, wherein the remaining capacity of the destination cluster can be greater than the capacity required for the migration of the user. Then, it can disable new device and subscription addition operations for the target user in the source cluster. Next, the cluster management service can synchronize all user information of the target user accessing the source cluster from the source cluster to the destination cluster via a cross-cluster user migration service. Finally, by changing the user-level domain name address, the address of the target user's application accessing the IoT platform is changed from the address of the source cluster to the address of the destination cluster. User applications can switch from interfacing with the source cluster to interfacing with the destination cluster, meaning they only need to interface with one cluster without requiring modifications to the user application, thus simplifying user application development. Finally, based on the number of devices connected to the source cluster by the target user, the target user's devices are connected to the destination cluster in batches. In this way, users can be migrated from a source cluster with a smaller capacity to a single destination cluster with a larger capacity. This not only expands the capacity of the user's current cluster but also avoids the problem of having to interface with multiple clusters simultaneously when expanding the user's capacity. Furthermore, during the cross-cluster migration, the user application is essentially unaware of the execution process of this invention, meaning that this invention can achieve the technical effect of having virtually no impact on user use during the user migration. Attached Figure Description

[0039] 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.

[0040] Figure 1 A flowchart illustrating a method for migrating IoT cluster users provided in an embodiment of the present invention;

[0041] Figure 2A flowchart illustrating a user cross-cluster migration service process for an IoT platform, provided as an embodiment of the present invention;

[0042] Figure 3 A flowchart illustrating the steps for processing an operation request from a user application API, as provided in an embodiment of the present invention;

[0043] Figure 4 A flowchart illustrating how a cross-cluster routing service processes operation requests, as provided in an embodiment of the present invention;

[0044] Figure 5 A flowchart illustrating the steps of user cross-cluster migration provided in an embodiment of the present invention;

[0045] Figure 6 This is a structural block diagram of a migration device for IoT cluster users provided in an embodiment of the present invention. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0047] Reference Figure 1 This invention provides a method for migrating IoT cluster users, specifically including the following steps:

[0048] Step S100: Determine the target user to be migrated in the source cluster, and determine the destination cluster to which the target user is to be migrated, wherein the remaining capacity of the destination cluster is greater than the capacity of the user to be migrated.

[0049] Specifically, the cluster management service can first identify the target users that need to be migrated in the source cluster, and then identify the destination cluster for the target users to be migrated to.

[0050] The process of determining the destination cluster may include: deploying a new cluster on the IoT platform, with the new cluster serving as the destination cluster. In one optional implementation, the capacity of the destination cluster can be greater than the capacity of the migrating users. Then, the ID of the destination cluster can be identified. Subsequently, in the cluster management service, information such as the ID of the destination cluster, the cross-cluster routing service address of the destination cluster, and the access permissions of the cross-cluster routing service are entered.

[0051] Then, initiate the cross-cluster migration operation for the target user: record the target user's migration status in the user migration status tables of the source and destination clusters. The target user migration status table fields can mainly include the target user ID: userId, and whether it is in migration status: isTransfer. The value of isTransfer is 1, which indicates that the target user is in migration status, and other values ​​indicate that the target user is not in migration status.

[0052] Step S110: Disable the new operation and subscription new operation of the target user device in the source cluster.

[0053] Specifically, the cluster management service can disable the addition of new devices and subscriptions for target users in the source cluster. When the device management and subscription management services of the source cluster are processing new operations, they can first determine whether the target user is in a migration state. If isTransfer == 1, the target user can be reminded that the new operation cannot be performed.

[0054] Step S120: Synchronize the user information of the target user from the source cluster to the destination cluster through the cross-cluster user migration service. The user information includes all information about the target user's access to the source cluster.

[0055] Specifically, the cross-cluster user migration service can be used to connect all user information of the target user to the source cluster. For example, the target user's full device, product, application, and subscription information can be synchronized from the source cluster to the database of the destination cluster.

[0056] Step S130: By switching the address of the target user's application access to the IoT platform from the address of the source cluster to the address of the destination cluster, the address of the target user's application is changed.

[0057] Specifically, the address of the target user's application accessing the IoT platform can be changed to the address of the target cluster. This address change process can include: resolving the target user's domain name to the target cluster's capability gateway IP address via DNS service by switching the address using the user-level domain name. After the address change, all subsequent operations of the target user's application only need to interface with the target cluster.

[0058] Step S140: Based on the number of devices of the target user connected to the source cluster, connect the target user's devices to the destination cluster in batches.

[0059] Specifically, the number of devices connected to the source cluster by the target user can be determined first. Based on this number, the devices are divided into multiple batches, and each batch is connected to the destination cluster sequentially. The process of connecting devices to the destination cluster can include: a) Based on the device's capabilities, selecting solutions such as network-side CC value cutover, device-level domain name, or bootstrap to connect the devices to the destination cluster. b) Recording the device migration status in the databases of both the source and destination clusters, mainly including changes in device ID (deviceId), the cluster ID to which the device belongs (belongClusterId), and the cluster ID currently accessed by the device (accessClusterId).

[0060] Reference Figure 2 This invention provides a flowchart illustrating the cross-cluster migration process for users on an IoT platform, in conjunction with the above. Figure 1 The step-by-step instructions provide a clear understanding of the implementation process of this solution.

[0061] Since the migration of target users takes a certain amount of time, and target users may still have operation requests during the migration period, this embodiment of the invention can also add a process for handling operation requests from target users during the migration process, which may specifically include the following:

[0062] Reference Figure 3 This invention provides a flowchart of the steps for processing operation requests from a user application API.

[0063] Specifically, the cluster capability gateway of the source cluster can first receive the operation request from the target user and send the operation request to the corresponding business processing service within the source cluster. The business processing service can then determine whether the operation request is a device operation request. Based on the determination result, the following different situations may occur:

[0064] Scenario 1: If the operation request is a device operation request, the processing method for the device operation request is determined based on the cluster to which the first device requesting the operation is currently connected.

[0065] Specifically, if the operation request is a device operation request such as issuing a command or taking a device snapshot, then we can first determine whether the first device is currently connected to the specified cluster. Based on the cluster that the first device is currently connected to, the operations can be further divided into the following:

[0066] Operation 1: If the cluster currently accessed by the first device is the target cluster, then the device operation request is processed in the target cluster.

[0067] Specifically, if the first device is currently connected to the target cluster, then the device operation requests can be processed directly in the target cluster.

[0068] Reference Figure 4 This invention provides a flowchart for processing operation requests in a cross-cluster routing service.

[0069] Step 2: If the cluster currently accessed by the first device is the source cluster, then add the ID of the source cluster and the bizUrl of the access path of the device operation request to the header of the device operation request, and then forward the device operation request to the cross-cluster routing service of the destination cluster; the cross-cluster routing service of the destination cluster forwards the device operation request to the cross-cluster routing service of the source cluster according to the ID of the destination cluster; the cross-cluster routing service of the source cluster calls the service corresponding to the bizUrl to process the device operation request.

[0070] Specifically, if the first device is currently connected to the source cluster, the source cluster ID (targetClusterId = accessClusterId) and the access path (bizUrl) of the device operation request header of the target user are added. Then, the device operation request is forwarded to the cross-cluster routing service of the destination cluster. The cross-cluster routing service of the source cluster can be used as the source cross-cluster routing service.

[0071] Then, the device operation request is forwarded to the destination cross-cluster routing service of the source cluster based on the destination cluster ID through the cross-cluster routing service of the destination cluster. The above process may include the following steps:

[0072] S1. Obtain the ID of the destination cluster from the header of the device operation request through the cross-cluster routing service of the destination cluster.

[0073] Specifically, when the cross-cluster routing service of the destination cluster starts, it obtains the ID of the source cluster, and retrieves the IDs of all clusters and the corresponding access address information and access permission information of the cross-cluster routing service from the cluster management service, caches them in memory and updates them periodically.

[0074] S2. Obtain the destination access address and destination access credentials corresponding to the ID of the destination cluster from the pre-stored service information through the cross-cluster routing service of the destination cluster.

[0075] Specifically, the targetClusterId is obtained from the received device operation request header, and the targetClusterUrl and access credentials of the cross-cluster routing service of the source cluster are obtained from the local cache.

[0076] S3. The device operation request is forwarded to the destination access address through the cross-cluster routing service of the destination cluster in accordance with the authentication requirements of the destination access credential.

[0077] Specifically, the cross-cluster routing service of the target cluster forwards device operation requests to targetClusterUrl according to authentication requirements, and the access addresses of services within each cluster of the IoT platform remain consistent.

[0078] Finally, after receiving a device operation request, the source cross-cluster routing service of the source cluster obtains the bizUrl from the device operation request header, forwards the device operation request to the service corresponding to the bizUrl, obtains the processing result, and can also return the processing result of the device operation request to the destination cross-cluster routing service through the source cross-cluster routing service.

[0079] Scenario 2: If the operation request is a non-device operation request, then the non-device operation request is processed in the destination cluster.

[0080] Specifically, if the operation request is not a device operation request, it can be processed directly in the destination cluster.

[0081] Furthermore, the migration process for target users may also include:

[0082] The uplink messages from the target user's second device are pushed to the target user's application by the cluster currently connected to the second device, according to the target user's subscription rules.

[0083] In addition, after the target user migration is completed, the process may also include: cleaning up the user information in the source cluster.

[0084] Specifically, after the migration operation of the target user is completed, the cluster management service can set the migration status of the target user in the destination cluster to 0 and clean up user information such as user devices and subscriptions in the source cluster.

[0085] The migration process of cluster users in this invention will be illustrated with specific examples below.

[0086] Reference Figure 5 This invention provides a flowchart of the user cross-cluster migration processing steps.

[0087] 1. Deploy two IoT platform clusters, each with a cross-cluster routing service. Identify the clusters as 001 and 002, where cluster 001 can be used as the source cluster and cluster 002 as the destination cluster. Enter the cluster IDs, cross-cluster routing service addresses, and access permissions for both clusters into the cluster management service.

[0088] 2. Create a user named user1 in cluster 001, and create and connect a certain number of devices for this user. Create a message subscription to push device-reported messages to user1's application.

[0089] 3. Initiate the user cross-cluster migration operation, record the user migration status in the user migration status table of clusters 001 and 002, and mark the user user1's migration status isTransfer as 1.

[0090] 4. Disable new operations such as user1 device and subscription in cluster 001.

[0091] 5. Synchronize all device, product, application, subscription, and other information of user1 from cluster 001 to the database of cluster 002.

[0092] 6. By switching the address using the user-level domain name, the DNS service resolves the domain name of the user accessing the cluster capability gateway to the IP address of the 002 cluster capability gateway.

[0093] 7. Connect user1's device to the target cluster in batches. The device can be connected to the target cluster by CC value cutover, device-level domain name, or bootstrap.

[0094] 8. During the device migration process, the user1 application sends operations such as obtaining device information and issuing commands to the IoT platform capability gateway.

[0095] 9. Uplink messages from the device are still pushed to user applications by each cluster according to the user subscription rules.

[0096] 10. After the migration operation is completed, set the migration status isTransfer of user1 in cluster 002 to 0, and clean up user information such as user1's device and subscription in cluster 001.

[0097] Reference Figure 6 This invention provides a migration device for IoT cluster users, comprising:

[0098] The migration target determination unit is used to determine the target user to be migrated in the source cluster and to determine the destination cluster to which the target user is to be migrated, wherein the remaining capacity of the destination cluster is greater than the capacity of the user to be migrated.

[0099] A new operation shutdown unit is added, which is used to shut down the new operation and subscription new operation of the target user device in the source cluster;

[0100] The user information synchronization unit is used to synchronize the user information of the target user from the source cluster to the destination cluster through the cross-cluster user migration service. The user information includes all information about the target user's access to the source cluster.

[0101] The access address change unit is used to change the address of the target user's application access to the Internet of Things platform from the address of the source cluster to the address of the destination cluster by switching the address through a user-level domain name;

[0102] The user equipment migration unit is used to connect the target user's devices to the destination cluster in batches according to the number of devices connected to the source cluster by the target user.

[0103] This invention also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform... Figure 1 The method shown.

[0104] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order shown in the operation diagrams. For example, depending on the functions / operations involved, two consecutively shown blocks may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. Furthermore, the embodiments presented and described in the flowcharts of this invention are provided by way of example to provide a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is altered and sub-operations described as part of a larger operation are executed independently.

[0105] Furthermore, although the invention has been described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the described functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the invention. Rather, given the properties, functions, and internal relationships of the various functional modules in the apparatus disclosed herein, the actual implementation of the module will be understood within the scope of conventional skill of an engineer. Therefore, those skilled in the art can implement the invention as set forth in the claims using ordinary techniques without excessive experimentation. It is also understood that the specific concepts disclosed are merely illustrative and not intended to limit the scope of the invention, which is determined by the full scope of the appended claims and their equivalents.

[0106] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0107] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0108] More specific examples of computer-readable media (a non-exhaustive list) include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0109] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0110] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0111] Although embodiments of the invention have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.

[0112] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of the present invention.

Claims

1. A method for migrating users in an Internet of Things (IoT) cluster, characterized in that, include: In the source cluster, identify the target user to be migrated and determine the destination cluster to which the target user is to be migrated, wherein the remaining capacity of the destination cluster is greater than the capacity of the user to be migrated. Disable new operations and subscription additions for the target user device in the source cluster; The user information of the target user is synchronized from the source cluster to the destination cluster through the cross-cluster user migration service. The user information includes all information about the target user's access to the source cluster. By switching the address of the user-level domain name, the address of the target user's application access to the Internet of Things platform is changed from the address of the source cluster to the address of the destination cluster; Based on the number of devices connected to the source cluster by the target user, the target user's devices are connected to the destination cluster in batches; If the target user makes a device operation request during the migration process, and if the first device requesting the operation is currently connected to the source cluster, then the ID of the source cluster and the bizUrl of the access path of the device operation request are added to the header of the device operation request. The destination access address and destination access credentials corresponding to the ID of the destination cluster are obtained from the pre-stored service information through the cross-cluster routing service of the destination cluster. The cross-cluster routing service of the destination cluster forwards the device operation request to the destination access address according to the authentication requirements of the destination access credential. The device operation request is processed by calling the service corresponding to the bizUrl through the cross-cluster routing service of the source cluster.

2. The method for migrating IoT cluster users according to claim 1, characterized in that, Also includes: If the target user makes a non-device operation request during the migration process, the non-device operation request will be processed in the destination cluster.

3. The method for migrating IoT cluster users according to claim 2, characterized in that, Also includes: If the cluster currently accessed by the first device is the target cluster, then the device operation request is processed in the target cluster.

4. The method for migrating IoT cluster users according to claim 3, characterized in that, After processing the device operation request according to the bizUrl via the cross-cluster routing service of the source cluster, the process further includes: The processing result of the device operation request is returned to the cross-cluster routing service of the destination cluster through the cross-cluster routing service of the source cluster.

5. The method for migrating IoT cluster users according to claim 1, characterized in that, The migration process for the target users also includes: The uplink messages from the target user's second device are pushed to the target user's application by the cluster currently connected to the second device, according to the target user's subscription rules.

6. The method for migrating IoT cluster users according to claim 1, characterized in that, After the target user migration is completed, the following is also included: Clean up the user information in the source cluster.

7. A migration device for IoT cluster users, characterized in that, The apparatus is used to implement the IoT cluster user migration method as described in claim 1, the apparatus comprising: The migration target determination unit is used to determine the target user to be migrated in the source cluster and to determine the destination cluster to which the target user is to be migrated, wherein the remaining capacity of the destination cluster is greater than the capacity of the user to be migrated. A new operation shutdown unit is added, which is used to shut down the new operation and subscription new operation of the target user device in the source cluster; The user information synchronization unit is used to synchronize the user information of the target user from the source cluster to the destination cluster through the cross-cluster user migration service. The user information includes all information about the target user's access to the source cluster. The access address change unit is used to change the address of the target user's application access to the Internet of Things platform from the address of the source cluster to the address of the destination cluster by switching the address through a user-level domain name; The user equipment migration unit is used to connect the target user's devices to the destination cluster in batches according to the number of devices connected to the source cluster by the target user.

8. An electronic device, characterized in that, Including the processor and memory; The memory is used to store programs; The processor executes the program to implement the migration method for IoT cluster users as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The storage medium stores a program that is executed by a processor to implement the migration method for IoT cluster users as described in any one of claims 1 to 6.

Images