IoT device data migration system, method, apparatus and storage medium

By establishing a virtual private channel between the gateway platform and the server cluster of the IoT platform and using user identifiers for data routing, the high cost problem in IoT device data migration is solved, and efficient device data migration is achieved.

CN114385314BActive Publication Date: 2026-04-21E SURFING IOT CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
E SURFING IOT CO LTD
Filing Date
2021-12-30
Publication Date
2026-04-21

AI Technical Summary

Technical Problem

In existing technologies, data migration for IoT devices requires reconfiguration of IP addresses, resulting in high manpower and time costs and making it difficult to efficiently distribute load among server clusters.

Method used

By establishing a virtual private channel between the gateway platform and each server cluster of the IoT platform, and using pre-defined user identifiers to determine the data transmission path, data migration can be achieved without directly changing the configuration of IoT devices.

Benefits of technology

It reduces the cost of data migration for IoT devices, decreases dependence on device configuration, and improves data migration efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114385314B_ABST
    Figure CN114385314B_ABST
Patent Text Reader

Abstract

This invention discloses a data migration system, method, apparatus, and storage medium for Internet of Things (IoT) devices, relating to the field of IoT communication technology. The IoT device data migration system includes a gateway platform and an IoT platform, wherein the IoT platform includes multiple server clusters; the gateway platform communicates with each of the server clusters of the IoT platform via a Virtual Private Channel (VPN); the gateway platform receives data from IoT devices, determines the user identifier of the IoT device based on the data, determines a VPN for transmitting the data based on the user identifier, and sends the data through the VPN, wherein the user identifier is pre-installed in the gateway platform. The IoT device data migration system of this application can reduce the data migration cost of IoT devices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) communication technology, and in particular to an IoT device data migration system, method, apparatus, and storage medium. Background Technology

[0002] In the field of mobile cellular IoT communication, IoT platforms provide unified management of IoT devices and data collection functions. IoT devices connect to the IoT platform's server cluster via the mobile communication network and then through the backbone network. Typically, the IoT platform needs to configure the public IP addresses of the server cluster for the IoT devices, and the IoT devices send data to the server cluster connected to the IoT platform based on these configured IP addresses.

[0003] Currently, with the increasing number of IoT devices, the business processing pressure on IoT platforms is gradually increasing, necessitating the addition of IP addresses to expand server clusters for load balancing. However, IoT devices are widely distributed and numerous, so migrating their data to new server clusters by reconfiguring their destination IP addresses on-site or remotely modifying them would incur significant manpower and time costs. Summary of the Invention

[0004] This invention aims to at least solve one of the technical problems existing in the prior art. To this end, this invention proposes a data migration system, method, apparatus, and storage medium for Internet of Things (IoT) devices, which can reduce the data migration cost of IoT devices.

[0005] On one hand, embodiments of the present invention provide an IoT device data migration system, including a gateway platform and an IoT platform, wherein the IoT platform includes multiple server clusters;

[0006] The gateway platform communicates with each of the server clusters of the IoT platform through a virtual private channel.

[0007] The gateway platform is used to receive data from IoT devices, determine the user identifier of the IoT devices based on the data, determine a virtual private channel for transmitting the data based on the user identifier, and send the data through the virtual private channel, wherein the user identifier is preset in the gateway platform.

[0008] According to some embodiments of the present invention, the gateway platform includes a device access authentication module, which is used for:

[0009] Obtain the device identifier of the IoT device;

[0010] A user identifier and a first IP address are generated for the IoT device based on the device identifier;

[0011] Send the first IP address to the IoT device;

[0012] The device identifier and the user identifier are bound to form a first relationship mapping table.

[0013] According to some embodiments of the present invention, the gateway platform further includes a data packet forwarding module, the data packet forwarding module being used for:

[0014] The device identifier of the IoT device is obtained by parsing the data;

[0015] The user identifier is obtained by querying the first relationship mapping table based on the device identifier;

[0016] The virtual private channel for transmitting the data is determined by querying the second relational mapping table based on the user identifier.

[0017] The data is sent through the virtual private channel.

[0018] According to some embodiments of the present invention, the server cluster is used for:

[0019] Receive the data from the virtual private channel;

[0020] Parse the second IP address in the data;

[0021] The destination server is determined based on the second IP address.

[0022] According to some embodiments of the present invention, the gateway platform further includes a configuration module, the configuration module being used for:

[0023] Get configuration commands;

[0024] In response to the configuration instruction, the user identifier and server cluster number are obtained by parsing the configuration instruction;

[0025] The virtual private channel is determined based on the server cluster code;

[0026] A second relationship mapping table is formed by binding the virtual private channel with the user identifier in the configuration instruction.

[0027] On the other hand, embodiments of the present invention also provide a method for migrating data of IoT devices, which is applied to the gateway platform of the IoT device data migration system as described above;

[0028] The IoT device data migration method includes the following steps:

[0029] Receive data from IoT devices;

[0030] The user identifier of the IoT device is determined based on the data;

[0031] A virtual private channel for transmitting the data is determined based on the user identifier;

[0032] The data is sent through the virtual private channel.

[0033] According to some embodiments of the present invention, the IoT device data migration method further includes the following steps:

[0034] Obtain the device identifier of the IoT device;

[0035] A user identifier and a first IP address are generated for the IoT device based on the device identifier;

[0036] Send the first IP address to the IoT device;

[0037] The device identifier and the user identifier are bound to form a first relationship mapping table.

[0038] According to some embodiments of the present invention, determining the user identifier of the Internet of Things device based on the data includes the following steps:

[0039] The device identifier of the IoT device is obtained by parsing the data;

[0040] The user identifier is obtained by querying the first relationship mapping table based on the device identifier, wherein the user identifier is preset in the gateway platform;

[0041] Determining the virtual private channel for transmitting the data based on the user identifier includes the following steps:

[0042] The virtual private channel used to transmit the data is determined by querying the second relational mapping table based on the user identifier.

[0043] On the other hand, embodiments of the present invention also provide an IoT device data migration apparatus, comprising:

[0044] At least one processor;

[0045] At least one memory for storing at least one program;

[0046] When the at least one program is executed by the at least one processor, the at least one processor implements the IoT device data migration method as described above.

[0047] On the other hand, embodiments of the present invention also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the IoT device data migration method as described above.

[0048] The technical solution described above has at least one of the following advantages or beneficial effects: When an IoT device transmits data to the server cluster of an IoT platform, the gateway platform first receives the data from the IoT device and determines the user identifier of the IoT device pre-installed in the gateway platform based on the data. A virtual private channel (VPN) for data transmission is then determined based on the user identifier. Since each VPN corresponds to a server cluster, the data of the IoT device can be migrated to the corresponding server cluster after the VPN is determined. By establishing a VPN between the gateway platform and each server cluster of the IoT platform, instead of addressing and forwarding based on the IP address in the data, the gateway platform determines the VPN based on the user identifier of the IoT device, thereby enabling data to be sent to the server cluster corresponding to the VPN. Therefore, only the user identifier pre-installed in the gateway platform needs to be changed to achieve data migration for the IoT device, without needing to change the configuration of the IoT device, thus saving data migration costs. Attached Figure Description

[0049] Figure 1 This is a schematic diagram of an IoT device data migration system provided in an embodiment of the present invention;

[0050] Figure 2 This is a schematic diagram of an IoT device data migration system provided in another embodiment of the present invention;

[0051] Figure 3 This is a flowchart of the IoT device data migration method provided in an embodiment of the present invention;

[0052] Figure 4 This is a schematic diagram of the application framework of the IoT device data migration method provided in the embodiments of the present invention;

[0053] Figure 5 This is a schematic diagram of an IoT device data migration apparatus provided in an embodiment of the present invention. Detailed Implementation

[0054] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar originals or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0055] In the description of this invention, it should be understood that the orientation descriptions, such as up, down, left, right, etc., are based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limiting this invention.

[0056] In the description of this invention, the use of terms such as "first," "second," etc., is for the purpose of distinguishing technical features only and should not be construed as indicating or implying relative importance, or implicitly indicating the number of technical features indicated, or implicitly indicating the order of the technical features indicated.

[0057] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0058] HSS (Home Subscriber Server) is a crucial component of the control layer in IMS (IP Multimedia Subsystem). HSS supports the main user database for IMS network entities that handle calls / sessions. It contains user profiles, performs user authentication and authorization, and provides information about user physical locations. It is similar to GSM HomeLocationRegister. The entities that communicate with HSS are the application server and the call session control function server.

[0059] The MME (Mobility Management Entity) is a key control node in the 3GPP LTE access network. It is responsible for the location of UEs (User Equipment) in idle mode, paging processes, including relaying; simply put, the MME is responsible for signaling processing. It is involved in the bearer activation / deactivation process and selects an SGW (Serving Gateway) for a UE when it initializes and connects. It authenticates a user by interacting with the HSS and assigns a temporary ID to the user.

[0060] The Serving Gateway (SGW) is a crucial network element in the core mobile communication network. In traditional networks, the Serving GPRS Support Node (SGSN) is responsible for both signaling plane functions such as mobility management and user access control, as well as user data forwarding. Based on the principle of separating control and bearer functions, the functions of the SGSN are split in the core mobile communication network: signaling plane functions are handled by the MME (Mobile Equipment Manager) network element, while user plane functions such as user data forwarding are taken over by the SGW network element.

[0061] A PGW (PDN Gateway) is a boundary gateway for the mobile communication core network, providing functions such as user session management and bearer control, data forwarding, IP address allocation, and access for non-3GPP users. It serves as the anchor point for the PDN (Public Data Network) in both 3GPP and non-3GPP access networks. 3GPP access refers to radio access technologies from the 3GPP standards family, while non-3GPP access refers to radio access technologies outside the 3GPP standards family.

[0062] CE (Customer Edge) is the user-end router to which the service provider connects. The CE router provides service access to users by connecting to one or more PE routers.

[0063] VPN (Virtual Private Network) is a remote access technology that uses data encapsulation and encryption to establish a private network over a public network, thus creating a virtual private tunnel on the public network. A VPN gateway enables remote access by encrypting data packets and translating their destination addresses. VPNs can be implemented through various methods, including servers, hardware, and software.

[0064] Each server cluster on the IoT platform provides a public IP address to the outside world, while using internal IP addresses within the server cluster. The traditional method for IoT devices to send data to the IoT platform is as follows: the IoT device is configured with the destination server's IP address; the IoT device encapsulates data packets based on the destination IP address and sends the packets to the gateway platform for forwarding; the gateway platform forwards the data to the corresponding server cluster based on IP address addressing; and the server cluster then forwards the data to the destination server within the server cluster based on the destination IP address in the data. Because data forwarding uses IP address addressing at the gateway platform, the internal IP addresses within different server clusters cannot be the same, otherwise routing conflicts will occur. To migrate data from an IoT device to another server cluster, the destination IP address configured in the IoT device must be changed.

[0065] Based on this, embodiments of the present invention provide an IoT device data migration system, referring to... Figure 1 The IoT device data migration system includes a gateway platform and an IoT platform, where the IoT platform comprises multiple server clusters. A virtual private channel (VPN) is established between the gateway platform and each server cluster of the IoT platform for communication.

[0066] The gateway platform is used to receive data from IoT devices, determine the user identifier of the IoT devices based on the data, determine the virtual private channel for data transmission based on the user identifier, and send data through the virtual private channel. The user identifier is pre-set in the gateway platform.

[0067] Specifically, with Figure 1 Taking the IoT device data migration system shown as an example, the system includes a gateway platform and an IoT platform. The IoT platform includes server cluster 1 and server cluster 2. Based on VPN technology, a virtual private channel (VPN1) is established between the gateway platform and server cluster 1, and a similar VPN2 is established between the gateway platform and server cluster 2. IoT devices 1, 2, 3, and 4 are connected to the gateway platform. When the gateway platform receives data from any IoT device, it determines the user identifier pre-installed in the gateway platform for that IoT device based on the received data, and then determines the VPN2 used to transmit the data. For example, the VPN2 corresponds to user identifier "1" and the VPN3 corresponds to user identifier "2". Devices 1 and 2 have user identifiers of "1" in the gateway platform, while devices 3 and 4 have user identifiers of "2". Therefore, data from devices 1 and 2 is transmitted to server cluster 1 via VPN1, and data from devices 3 and 4 is transmitted to server cluster 2 via VPN2. Because different Virtual Private Channels (VPNs) are established between the gateway platform and different server clusters, these VPNs can create network barriers and avoid routing conflicts. Therefore, the destination IP address of data transmitted in different VPNs can be the same. For example, device 1 and device 3 may be configured with the same destination IP address, but because device 1 and device 3 have different user identifiers pre-configured in the gateway platform, they can be addressed in different server clusters through different VPNs. If it is necessary to migrate data from device 1 to server cluster 2, simply changing the user identifier of device 1 in the gateway platform to "2" will allow the data from device 1 to be transmitted to server cluster 2 via VPN 2, without needing to change the destination IP address configured in device 1.

[0068] According to some specific embodiments of the present invention, referring to Figure 2The gateway platform includes a device access authentication module, which is used for:

[0069] Obtain the device identifier of the IoT device;

[0070] Generate a user identifier and a first IP address for the IoT device based on the device identifier;

[0071] Send the first IP address to the IoT device;

[0072] The binding device identifier and user identifier form the first relationship mapping table.

[0073] Specifically, the IoT device initiates a network access authentication module to access the network. The module uses the IoT device's MAC address as the device identifier and assigns a CC (Charging Characteristic) value as the user identifier to the MAC address. Then, it binds the MAC address and the CC value to form a first relationship mapping table. Furthermore, after the IoT device initiates the authentication request, the module assigns a first IP address as the source IP address and sends the assigned first IP address to the IoT device. The IoT device's network access request is then successful.

[0074] According to some embodiments of the present invention, with reference to Figure 2 The gateway platform also includes a data packet forwarding module, which is used for:

[0075] Parse the data to obtain the device identifier of the IoT device;

[0076] The user identifier is obtained by querying the first relational mapping table based on the device identifier;

[0077] The virtual private channel used for data transmission is determined by querying the second relational mapping table based on the user identifier;

[0078] Data is sent via a virtual private channel.

[0079] Specifically, the IoT device sends data to the server cluster in the IoT platform through the gateway, using the first IP address as the source IP address. The data packet forwarding module in the gateway platform parses the data from the IoT device to obtain the MAC address of the IoT device. Based on the MAC address, it queries the first relational mapping table in the device access authentication module to obtain the corresponding CC value. Then, based on the CC value, it queries the second relational mapping table to determine the corresponding virtual private channel, and finally sends the data to the corresponding server cluster through the virtual private channel.

[0080] According to some specific embodiments of the present invention, the server cluster is used for:

[0081] Receive data from the virtual private channel;

[0082] The second IP address is parsed from the data;

[0083] The destination server is determined based on the second IP address.

[0084] Specifically, the server cluster is equipped with firewall devices. These firewall devices decrypt and identify data packets, accepting only data from the corresponding virtual private channel (VPN) and isolating data from other VPNs. The server cluster then parses the second IP address in the data, which is the destination IP address. Based on this second IP address, the data is determined and forwarded to the destination server or the next-level destination server cluster.

[0085] According to some specific embodiments of the present invention, the gateway platform further includes a configuration module, which is used for:

[0086] Get configuration commands;

[0087] In response to configuration commands, parse the user identifier and server cluster number contained in the configuration commands;

[0088] The virtual private channel is determined based on the server cluster code;

[0089] A second relationship mapping table is formed by binding the virtual private channel and the user identifier in the configuration command.

[0090] Specifically, the configuration module obtains configuration instructions input by the user, which include a user identifier and a server cluster number. In response to the configuration instructions, the module parses them to obtain the user identifier and server cluster number, then determines the corresponding Virtual Private Channel (VPN) based on the server cluster number. A second relationship mapping table is formed by binding the VPN with the user identifier in the configuration instructions, enabling batch migration of IoT device data. In this embodiment, the configuration instructions can change the correspondence between user identifiers and VPNs in the gateway platform. For example, changing the VPN corresponding to user identifier "2" to VPN1 can enable batch migration of data from all IoT devices with user identifier "2" to server cluster 1.

[0091] In other embodiments, the configuration instructions input by the user may also include a user identifier and a device identifier. In the configuration module, in response to the configuration instructions, the user identifier and device identifier are parsed, and the user identifier and device identifier in the configuration instructions are bound to form a second relationship mapping table, enabling data migration for a specific IoT device. In this embodiment, the configuration instructions can change the correspondence between user identifiers and device identifiers in the gateway platform. For example, changing the user identifier corresponding to device identifier "MAC1" from "1" to "2" can migrate the data of the IoT device with device identifier "MAC1" from server cluster 1 to server cluster 2.

[0092] This invention provides a method for migrating data from Internet of Things (IoT) devices, applied to the gateway platform of the network device data migration system described in the above embodiments. (Refer to...) Figure 3 The IoT device data migration method of this invention includes, but is not limited to, steps S110, S120, S130 and S140.

[0093] Step S110: Receive data from IoT devices;

[0094] Step S120: Determine the user identifier of the IoT device based on the data, wherein the user identifier is pre-set in the gateway platform;

[0095] Step S130: Determine the virtual private channel used for data transmission based on the user identifier;

[0096] Step S140: Send the data through a virtual private channel.

[0097] In this embodiment, the gateway platform receives data from IoT devices and determines the user identifier of the IoT device pre-installed in the gateway platform based on the data. Based on the user identifier, a virtual private channel (VPN) is determined for data transmission. Since each VPN corresponds to a server cluster, the data of the IoT device can be migrated to the corresponding server cluster after the VPN is determined. By establishing VPNs between the gateway platform and each server cluster of the IoT platform, instead of forwarding data based on the IP address in the data, the gateway platform determines the VPN based on the user identifier of the IoT device, thus enabling data to be sent to the server cluster corresponding to the VPN. Therefore, only the user identifier pre-installed in the gateway platform needs to be changed to achieve data migration for the IoT device, without needing to change the configuration of the IoT device, saving data migration costs.

[0098] According to some specific embodiments of the present invention, the IoT device data migration method of the present invention further includes, but is not limited to, the following steps:

[0099] Obtain the device identifier of the IoT device;

[0100] Generate a user identifier and a first IP address for the IoT device based on the device identifier;

[0101] Send the first IP address to the IoT device;

[0102] The binding device identifier and user identifier form the first relationship mapping table.

[0103] In this embodiment, network access attachment can be implemented for IoT devices. Network access attachment includes assigning a first IP address to the IoT device, which is the source IP address in the data packets uploaded by the IoT device. Network access attachment also includes pre-setting a user identifier for the IoT device.

[0104] According to some specific embodiments of the present invention, step S120 includes, but is not limited to, the following steps:

[0105] Parse the data to obtain the device identifier of the IoT device;

[0106] The user identifier is obtained by querying the first relational mapping table based on the device identifier;

[0107] Step S130 includes, but is not limited to, the following steps:

[0108] The virtual private channel used for data transmission is determined by querying the second relational mapping table based on the user identifier.

[0109] In this embodiment, based on the device identifier in the data of the IoT device, the virtual private channel used to transmit the data is determined by querying the first relation mapping table and the second relation mapping table, so as to send the data to the corresponding server cluster through the corresponding virtual private channel.

[0110] The following reference Figure 4 Taking the gateway platform as the 4G core network and the user identifier as the CC value as an example, this paper illustrates the IoT device data migration method of this embodiment.

[0111] The 4G core network includes MME, HSS, SGW, PGW, and CE network elements. When a user's IoT device initiates a network access request to the MME, the MME forwards the request to the HSS. The HSS obtains a CC value from the receiving end and returns it to the MME. The MME then sends the IoT device's device identifier and CC value to the SGW for storage. When the IoT device uploads data to the IoT platform's server cluster, the SGW maps the IoT device's data to obtain the user identifier, and the PGW determines the Virtual Private Channel (VPN) based on the user identifier. The CE uses Network Address Translation (NAT) technology to send the data into the corresponding VPN, thus delivering it to the relevant server cluster. The server cluster's firewall receives the data from the corresponding VPN.

[0112] Reference Figure 5 , Figure 5This is a schematic diagram of an IoT device data migration apparatus according to an embodiment of the present invention. The IoT device data migration apparatus of this embodiment includes one or more control processors and a memory. Figure 5 The example consists of a control processor and a memory.

[0113] The control processor and memory can be connected via a bus or other means. Figure 5 Taking the example of a connection between China and Israel via a bus.

[0114] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to a control processor, and these remote memories can be connected to an Internet of Things (IoT) device data migration device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks (LANs), mobile communication networks, and combinations thereof.

[0115] Those skilled in the art will understand that Figure 5 The device structure shown does not constitute a limitation on the data migration device for IoT devices, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0116] The non-transitory software program and instructions required to implement the IoT device data migration method applied to the IoT device data migration device in the above embodiments are stored in the memory. When executed by the controlled processor, the IoT device data migration method applied to the IoT device data migration device in the above embodiments is executed.

[0117] Furthermore, one embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions that are executed by one or more control processors, causing the one or more control processors to perform the IoT device data migration method in the above method embodiment.

[0118] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0119] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the present invention is not limited to the above embodiments. Within the scope of knowledge possessed by those skilled in the art, various changes can be made without departing from the spirit of the present invention.

Claims

1. A data migration system for Internet of Things (IoT) devices, characterized in that, It includes a gateway platform and an Internet of Things (IoT) platform, wherein the IoT platform includes multiple server clusters; The gateway platform communicates with each of the server clusters of the IoT platform through a virtual private channel; the virtual private channel is implemented using VPN technology. The gateway platform is used to receive data from IoT devices, parse the data to obtain the device identifier of the IoT device, query a first relational mapping table based on the device identifier to obtain a user identifier, query a second relational mapping table based on the user identifier to determine a virtual private channel for transmitting the data, and send the data through the virtual private channel; the user identifier is represented by a billing attribute value. The first relationship mapping table is used to represent the mapping relationship between device identifiers and user identifiers, and the second relationship mapping table is used to represent the mapping relationship between user identifiers and virtual private channels. By modifying the mapping relationship in the second relationship mapping table, IoT device data can be migrated in batches. The gateway platform includes a device access authentication module, which is used for: Obtain the device identifier of the IoT device; A user identifier and a first IP address are generated for the IoT device based on the device identifier; Send the first IP address to the IoT device; A first relationship mapping table is formed by binding the device identifier and the user identifier; The server cluster is used for: Receive the data from the virtual private channel; Parse the second IP address in the data; The destination server is determined based on the second IP address.

2. The IoT device data migration system according to claim 1, characterized in that, The gateway platform also includes a configuration module, which is used for: Get configuration commands; In response to the configuration command, the configuration command is parsed to obtain the user identifier and server cluster number; The virtual private channel is determined based on the server cluster number; A second relationship mapping table is formed by binding the virtual private channel with the user identifier in the configuration instruction.

3. A method for data migration of Internet of Things (IoT) devices, characterized in that, Applied to the gateway platform of the IoT device data migration system as described in claim 1; The IoT device data migration method includes the following steps: Receive data from IoT devices; The device identifier of the IoT device is obtained by parsing the data; The user identifier is obtained by querying the first relationship mapping table based on the device identifier; The virtual private channel for transmitting the data is determined by querying the second relational mapping table based on the user identifier. The data is sent through the virtual private channel; The first relationship mapping table is used to represent the mapping relationship between device identifiers and user identifiers, and the second relationship mapping table is used to represent the mapping relationship between user identifiers and virtual private channels. By modifying the mapping relationship in the second relationship mapping table, IoT device data can be migrated in batches. The IoT device data migration method further includes the following steps: Obtain the device identifier of the IoT device; A user identifier and a first IP address are generated for the IoT device based on the device identifier; Send the first IP address to the IoT device; The device identifier and the user identifier are bound to form a first relationship mapping table.

4. A data migration device for Internet of Things (IoT) devices, characterized in that, include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the IoT device data migration method as described in claim 3.

5. A computer-readable storage medium storing a processor-executable program, characterized in that, When the processor executes the program, it is used to implement the IoT device data migration method as described in claim 3.

Citation Information

Patent Citations

  • Data migration method, device and equipment and readable storage medium

    CN113220660A

  • Data transfer in a system of connected things

    US20170237815A1