A device redirection gateway side implementation method

Abstract

The present invention belongs to the technical field of device redirection in the video surveillance industry, and specifically relates to a method for implementing device redirection on the gateway side. This method is used to guide the device to register with other gateway services and migrate the device to a normal platform when an abnormality occurs in the gateway node service; the device is flexibly switched and stably connected between different gateways and platforms through registration, redirection, and cancellation of redirection steps, ensuring that the device service is not affected by the abnormality of the gateway service; when an abnormality occurs in the gateway node service, the solution provided by the present invention can guide the device to register with other gateway services, thereby ensuring the online rate of the device even in the case of service abnormality. The present invention enables the device to flexibly switch between different gateways and platforms and maintain a stable connection, ensuring that the device service is not affected by the abnormality of the gateway service. The solution ensures that the device can quickly return to a normal working state under abnormal circumstances, thereby ensuring business continuity.

Description

Technical Field

[0001] The present invention belongs to the technical field of device redirection in the video surveillance industry, and in particular relates to a method for implementing device redirection on a gateway side. Background Art

[0002] With the continuous vigorous development of the visual network social standard business, its application scenarios are constantly enriched and the business scale continues to expand, which puts more stringent requirements on the platform registration mechanism. In this context, it is urgent to build a platform registration model that is not only flexible but also stable to adapt to the increasingly complex business needs and changes in the network environment.

[0003] However, the current technical architecture has exposed serious limitations when facing the situation of abnormal gateway node services. The lack of redirection process is a key problem in the existing technical solutions. When the services of the gateway nodes are partially abnormal, due to the lack of an effective redirection mechanism, the related devices cannot automatically migrate to the normal platform. This directly causes the device to go offline and enter an unavailable state, which in turn causes serious interference to the device business, and business continuity cannot be guaranteed.

[0004] What is more serious is that during the period of gateway service abnormality, the status of all devices registered on the service will be synchronously changed to abnormal, and these devices will always be unavailable until the service returns to normal. This situation greatly affects the normal operation of the equipment, causing a series of adverse consequences such as business interruption, data transmission obstruction, and serious decline in service quality, which has a significant negative impact on user experience and business benefits. Therefore, this field urgently needs an innovative solution to solve the problem that the device cannot be used normally when the gateway service is abnormal, to achieve flexible switching and stable connection of the device between different gateways and platforms, so as to ensure the continuous and stable operation of the device business and improve the reliability and adaptability of the entire system. Summary of the invention

[0005] In view of the limitations of the prior art, the present invention proposes a method for implementing device redirection on the gateway side. When an exception occurs in the gateway service, the device state associated with the service will automatically change to an abnormal state until the service is restored, and the device will remain unavailable. The present invention effectively solves the problem that registered devices cannot be used normally when the device scheduling service is abnormal. When an exception occurs in the gateway node service, the present invention can guide the device to register with other gateway services, thereby ensuring the online rate of the device even in the case of service abnormalities. The present invention enables the device to flexibly switch between different gateways and platforms and maintain a stable connection, ensuring that the device service is not affected by the abnormality of the gateway service. This solution ensures that the device can quickly return to a normal working state under abnormal circumstances, thereby ensuring business continuity.

[0006] To achieve the above-mentioned purpose, the technical solution adopted by the present invention is: a device redirection gateway side implementation method, which is used to guide the device to register with another gateway service and migrate the device to a normal platform when an abnormality occurs in the gateway node service; through the registration, redirection and cancellation of redirection steps, the device can be flexibly switched and stably connected between different gateways and platforms to ensure that the device business is not affected by the abnormality of the gateway service;

[0007] The device redirection gateway side implementation method includes at least the following steps:

[0008] S1. The access management service actively sends redirection information to the original gateway. After receiving the redirection information, the original gateway stores the redirection information in the database; if the device is online, the device logout operation is performed;

[0009] S2. The device initiates a registration request to platform 1. After receiving the registration information, the device access service immediately sends a notification. After receiving the notification, platform 1 queries the middle platform to obtain the device information and stores the device information in the database. The device access service then obtains the data from the database and caches it.

[0010] S3. The device registration request is sent to the device access service again. The device brand is determined, the session key SessionKey for this registration is generated through the SDK, and it is determined whether the device needs to be redirected. If redirection is required, the access service will synchronously send the device capability information and the session key SessionKey to the gateway service of platform 2 through the HTTP protocol, and return the redirection address information to the device. If the registration fails, the address processing in the above process is repeated.

[0011] S4. After receiving the device registration session key SessionKey and device capability information sent by platform 1, the gateway service of platform 2 will convey this information to the device access service in the form of a notification; after receiving this information, the device access service will update and refresh the data in real time;

[0012] S5. The device initiates a registration request to platform 2. The gateway service of platform 2 then queries the middle platform and obtains the device login information. After obtaining the information, it determines whether it is consistent with the device in step S3. If it is consistent, the session key SessionKey of this registration is further verified; if all the information is correct, the device will be successfully launched on platform 2; if there is any information error, the registration fails, and the device will return to platform 1 and repeat the above process.

[0013] Furthermore, the data interaction method between the device access service, gateway service and middle platform during the device registration process is as follows: the device access service sends a notification to the gateway service after receiving the device registration information. The gateway service obtains the device information from the middle platform based on the notification and stores it in the database. The device access service then obtains the data from the database for cache to ensure the integrity and consistency of the data.

[0014] Furthermore, in step S3, the judgment basis for whether the device needs to be redirected includes a comprehensive judgment of the registration mechanism corresponding to the device brand and the device capability information and the session key SessionKey, and the relevant information is sent to the gateway service of platform 2 for judgment through the access service.

[0015] Furthermore, the following steps are included in the device redirection process:

[0016] The access management service actively initiates a device scheduling request, which is sent to the scheduling service;

[0017] The scheduling service assigns a new gateway to the device according to the scheduling strategy;

[0018] The dispatch service sends the data between the device and another gateway to the original gateway through the dispatch device request;

[0019] The original gateway records the scheduling relationship between the device and another gateway, including the device identification and the association information with the other gateway;

[0020] The original gateway returns the scheduling relationship data to the scheduling service, where the scheduling relationship data includes the association record between the device and another gateway;

[0021] The scheduling service transparently transmits the scheduling relationship data to the access management service;

[0022] The access management service stores the scheduling relationship in the database for subsequent query and management;

[0023] At the same time, the original gateway kicks the device offline to ensure that the device's connection to the original gateway is disconnected;

[0024] After the device goes offline, it will resend a registration request to the original gateway to trigger the redirection process;

[0025] The original gateway determines whether the device needs to be redirected based on the data recorded in the scheduling relationship between the device and another gateway;

[0026] If redirection is required, the original gateway will first synchronize the registration information to another gateway to ensure that the other gateway obtains the device's registration information;

[0027] After receiving the information, the other gateway returns a response to the original gateway, which is used to confirm receipt of the registration information;

[0028] After receiving the response, the original gateway sends the redirection information to the device, so that the device obtains the redirection target information;

[0029] After receiving the information, the device initiates registration with another gateway in the redirection information to establish a connection at the new gateway;

[0030] The other gateway returns the registration result to the device, informing it whether the registration is successful;

[0031] The other gateway reports the gateway information to the dispatch service so that the dispatch service can understand the gateway belonging to the device.

[0032] Furthermore, the following steps are included in the process of device redirection cancellation:

[0033] The access management service initiates a request to cancel device scheduling to the original gateway, starting the cancellation redirection process;

[0034] The original gateway modifies the corresponding information between the device and the gateway, and restores the association between the device and the gateway to the original state;

[0035] The original gateway returns the gateway information corresponding to the modified device to the access management service so that the access management service can perform subsequent operations;

[0036] After receiving the data, the access management service sends a request to cancel the device scheduling to another gateway, notifying the other gateway to perform the device offline operation;

[0037] Another gateway takes the device offline;

[0038] After another gateway goes offline, it returns a response to the access management service, informing the access management service that the device is offline;

[0039] The access management service modifies the database, changes the gateway information corresponding to the device to the original gateway, and restores the original record of the gateway information corresponding to the device in the database;

[0040] After the device goes offline, it re-registers with the original gateway to re-establish the connection at the original gateway;

[0041] The original gateway returns the registration result to the device, informing the device whether the registration is successful.

[0042] The present invention adopts the above technical solution, which has at least the following beneficial effects:

[0043] 1. The device redirection gateway side implementation method provided by the present invention is used to guide the device to register with another gateway service and migrate the device to a normal platform when an abnormality occurs in the gateway node service; the device can be flexibly switched and stably connected between different gateways and platforms through registration, redirection and cancellation of redirection steps, ensuring that the device service is not affected by the abnormality of the gateway service and ensuring the normal operation of the device service;

[0044] 2. In the prior art, when an abnormality occurs in a gateway service, the device state associated with the service will automatically change to an abnormal state until the service is restored, and the device will remain unavailable. The solution provided by the present invention effectively solves the problem that registered devices cannot be used normally when the device scheduling service is abnormal. When an abnormality occurs in the gateway node service, the solution provided by the present invention can guide the device to register with other gateway services, thereby ensuring the online rate of the device even in the case of service abnormalities. The present invention enables the device to flexibly switch between different gateways and platforms and maintain a stable connection, ensuring that the device service is not affected by the abnormality of the gateway service. This solution ensures that the device can quickly return to a normal working state under abnormal circumstances, thereby ensuring business continuity. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 It is a flow chart of the method for implementing the device redirection gateway side of the present invention.

[0047] Figure 2 It is a schematic diagram of the platform interaction of the present invention.

[0048] Figure 3 It is a schematic diagram of the device redirection interaction process of the present invention.

[0049] Figure 4 It is a schematic diagram of the redirection interaction process of the present invention. DETAILED DESCRIPTION

[0050] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0051] Embodiment 1

[0052] See also Figure 1 This embodiment provides a device redirection gateway side implementation method. The device redirection gateway side implementation method is used to guide the device to register with another gateway service when an abnormality occurs in the gateway node service, and migrate the device to a normal platform; through the registration, redirection and cancellation of redirection steps, the device can be flexibly switched and stably connected between different gateways and platforms, ensuring that the device business is not affected by the abnormality of the gateway service;

[0053] The device redirection gateway side implementation method includes at least the following steps:

[0054] S1. The access management service actively sends redirection information to the original gateway. After receiving the redirection information, the original gateway stores the redirection information in the database; if the device is online, the device logout operation is performed;

[0055] S2. The device initiates a registration request to platform 1. After receiving the registration information, the device access service immediately sends a notification. After receiving the notification, the gateway service of platform 1 queries and obtains the device information from the middle platform and stores the device information in the database. The device access service then obtains the data from the database and caches it.

[0056] S3. The device registration request is sent to the device access service again. The device brand is determined, the session key SessionKey for this registration is generated through the SDK, and it is determined whether the device needs to be redirected. If redirection is required, the access service will synchronously send the device capability information and the session key SessionKey to the gateway service of platform 2 through the HTTP protocol, and return the redirection address information to the device. If the registration fails, the address processing in the above process is repeated.

[0057] S4. After receiving the device registration session key SessionKey and device capability information sent by platform 1, the gateway service of platform 2 will convey this information to the device access service in the form of a notification; after receiving this information, the device access service will update and refresh the data in real time;

[0058] S5. The device initiates a registration request to platform 2. The gateway service of platform 2 then queries the middle platform and obtains the device login information. After obtaining the information, it determines whether it is consistent with the device in step S3. If it is consistent, the session key SessionKey of this registration is further verified; if all the information is correct, the device will be successfully launched on platform 2; if there is any information error, the registration fails, and the device will return to platform 1 and repeat the above process.

[0059] Embodiment 2

[0060] like Figure 2 The diagram shown is a schematic diagram of platform interaction, which interaction includes at least the following steps:

[0061] 1. The device access service actively sends redirection information to the gateway, and the gateway service stores the information in the database. If the device is online, the device is deregistered.

[0062] 2. Once the device registers with the platform, the device access service obtains the registration information and sends a notification. After receiving the notification, the gateway service obtains the device information (including the redirection address, port, and gateway information) from the middle platform and saves it to the database. The device access service obtains the data from the database and caches it.

[0063] 3. The device registration is sent to the device access service again. If it is Hikvision, the SessionKey session key for this registration is generated through the SDK, and then it is determined whether the device needs to be redirected. If necessary, the access service sends the device capability information and SessionKey (Hikvision) to the gateway service of platform 2 through the http protocol, and then returns the redirection address information to the device. If the registration fails, repeat the above address. If it is not redirected, it remains unchanged.

[0064] SessionKey usually refers to a temporary key used to establish a secure session between two communicating entities in computer network communications. It ensures the security of data exchange, allowing data to be transmitted securely during a specific session to prevent unauthorized access or tampering.

[0065] 4. The platform 2 gateway service receives the device registration SessionKey (Hikvision) and device capability information from platform 1 and sends it to the device access service in the form of a notification. After receiving it, the device access service refreshes the data in real time.

[0066] 5. The device initiates registration with Platform 2. The gateway of Platform 2 obtains the device login information from the middle station. After obtaining the information, if it is Hikvision, the SessionKey of this registration is checked. If all the information is correct, the device goes online on Platform 2; if there is an information error, the registration fails, and returns to Platform 1 to repeat the above process.

[0067] In this implementation example, the data interaction method between the device access service, gateway service and middle station during the device registration process is as follows: the device access service sends a notification to the gateway service after receiving the device registration information, and the gateway service obtains the device information from the middle station based on the notification and stores it in the database. The device access service then obtains the data from the database for cache to ensure the integrity and continuity of the data.

[0068] As a preferred implementation, in step S3 of this embodiment, the basis for judging whether the device needs to be redirected includes the registration mechanism corresponding to the device brand and the comprehensive judgment of the device capability information and the session key SessionKey, and the relevant information is sent to the gateway service of platform 2 through the access service for judgment. For example: in the redirection judgment and data transmission step, for devices of different brands, the judgment criteria corresponding to their registration mechanisms are as follows: Brand A devices are judged based on the specific coding rules of the device serial number and the logical combination of the hardware identifier, brand B devices are judged based on the system version range and specific configuration parameters of the device (such as the presence or absence of a specific network module), and brand C devices are judged based on the pre-set registration code and device type and the current geographical location information of the device (obtained through a variety of positioning technologies), and in the judgment process, if an ambiguous situation is encountered, a supplementary information collection request is sent to the device, and the device responds and makes a final judgment based on comprehensive information from multiple aspects.

[0069] like Figure 3 As shown, as a preferred implementation, this embodiment also includes the steps of device redirection interaction process:

[0070] 0. The access management service actively initiates a device scheduling request, which is sent to the scheduling service;

[0071] 1. The scheduling service assigns a new gateway to the device according to the scheduling strategy;

[0072] 2. The dispatch service sends the data between the device and another gateway to the original gateway through the dispatch device request;

[0073] 3. The original gateway records the scheduling relationship between the device and another gateway, including the device identification and the association information with the other gateway;

[0074] 4. The original gateway returns the scheduling relationship data to the scheduling service, and the scheduling relationship data includes the association record between the device and another gateway;

[0075] 5. The dispatch service transparently transmits the dispatch relationship data to the access management service;

[0076] 6. The access management service stores the scheduling relationship in the database for subsequent query and management;

[0077] 7. At the same time, the original gateway kicks the device offline to ensure that the device's connection to the original gateway is disconnected;

[0078] 8. After the device goes offline, it will resend a registration request to the original gateway to trigger the redirection process;

[0079] 9. The original gateway determines whether the device needs to be redirected based on the data recorded in the scheduling relationship between the device and another gateway;

[0080] 10. If redirection is required, the original gateway will first synchronize the registration information to another gateway to ensure that the other gateway obtains the registration information of the device;

[0081] 11. After receiving the information, the other gateway returns a response to the original gateway, which is used to confirm receipt of the registration information;

[0082] 12. After receiving the response, the original gateway sends the redirection information to the device, so that the device obtains the redirection target information;

[0083] 13. After receiving the information, the device initiates registration with another gateway in the redirection information to establish a connection at the new gateway;

[0084] 14. Another gateway returns the registration result to the device, informing it whether the registration is successful;

[0085] 15. The other gateway reports its gateway information to the dispatch service so that the dispatch service can understand the gateway ownership of the device.

[0086] In order to further elaborate on this step, the following is an expanded description of this step:

[0087] Scheduling request initiation and strategy planning steps: The access management service actively initiates the device scheduling request, and the request is sent to the scheduling service. The timing of initiating the request can be dynamically adjusted according to the device operation status (such as device load, device operation time, etc.) and network environment status (such as network bandwidth utilization, network packet loss rate, etc.). The scheduling service allocates a new gateway to the device according to the scheduling strategy. The scheduling strategy comprehensively considers the gateway load (such as the number of connected devices, gateway resource utilization, etc.), network delay (real-time network delay data), the historical connection performance between the device and the gateway (such as connection stability, average connection time, etc.) and the current business needs of the device (such as data transmission volume, real-time requirements, etc.) and other factors to determine the allocation process. Efficient and fast;

[0088] Data delivery and relationship record maintenance steps: The dispatch service sends the data of the device and another gateway to the original gateway through the dispatch device request. The data includes the device identification (a unique device number), device configuration details (such as network configuration parameters, device function settings, etc.), network connection properties (such as connection protocol, port number, etc.) and device security authentication credentials (such as digital certificates). The original gateway records the dispatch relationship between the device and the other gateway, and uses a standardized relational database structure to record (clearly record fields and data types) to ensure accurate data recording;

[0089] Data feedback and storage management steps: The original gateway returns the scheduling relationship data to the scheduling service, and the scheduling service efficiently transmits the scheduling relationship data to the access management service. The access management service stores the scheduling relationship in a format that is easy to query and manage (such as JSON format) in the database, and regularly backs up the scheduling relationship data (the backup cycle can be set according to the importance of the data) for subsequent query and management;

[0090] Device offline and re-registration triggering stage: At the same time, the original gateway kicks the device offline to ensure that the device's connection at the original gateway is quickly disconnected. After the device goes offline, it will resend a registration request to the original gateway to trigger the redirection process. The timing of resending the registration request is determined according to the device reconnection strategy. The reconnection strategy considers factors such as device type and network environment, and the device reconnection request carries information related to the device offline (such as the reason for the offline, etc.);

[0091] Redirection judgment and information synchronization collaboration steps: The original gateway determines whether the device needs to be redirected based on the data recorded in the scheduling relationship between the device and the other gateway. If redirection is required, the original gateway first synchronizes the registration information to the other gateway. The synchronization process ensures the secure transmission of information (using encrypted transmission). After receiving the information, the other gateway promptly returns a response to the original gateway.

[0092] Registration operation and result feedback steps: After receiving the response, the original gateway sends a redirection message to the device. After receiving the message, the device initiates registration with another gateway in the redirection message. The other gateway returns the registration result to the device to inform the device whether the registration is successful. At the same time, the other gateway reports the gateway information to the scheduling service so that the scheduling service can grasp the gateway affiliation dynamics of the device in real time.

[0093] like Figure 4 As shown, as a preferred implementation, this embodiment also includes the following steps in the process of device canceling redirection interaction:

[0094] 1. The access management service initiates a request to cancel device scheduling to the original gateway and starts the cancellation redirection process;

[0095] 2. The original gateway modifies the corresponding information between the device and the gateway, and restores the association between the device and the gateway to the original state;

[0096] 3. The original gateway returns the gateway response information of the modified device pair to the access management service so that the access management service can perform subsequent operations;

[0097] 4. After receiving the data, the access management service sends a request to cancel the device scheduling to another gateway, notifying the other gateway to take the device offline;

[0098] 5. Another gateway takes the device offline;

[0099] 6. After another gateway goes offline, it returns a response to the access management service, informing the access management service that the device is offline;

[0100] 7. Access the management service to modify the database, change the gateway information corresponding to the device to the original gateway, and restore the original record of the gateway information corresponding to the device in the database;

[0101] 8. After the device goes offline, it re-registers with the original gateway to re-establish the connection at the original gateway;

[0102] 9. The original gateway returns the registration result to the device, informing the device whether the registration is successful.

[0103] In order to further elaborate on this step, the following is an expanded description of this step:

[0104] Cancellation request initiation step: The access management service initiates a request to cancel device scheduling to the original gateway. The timing of initiating the request is determined according to changes in device business requirements or adjustments to network status;

[0105] Information modification and feedback steps: The original gateway modifies the corresponding information between the device and the gateway, restores the association between the device and the gateway to the initial state, and returns the modified gateway information corresponding to the device to the access management service in a timely manner after the modification;

[0106] Cancel instruction issuance and processing steps: After receiving the data, the access management service sends a request to cancel the scheduling device to another gateway. The other gateway processes the device offline and returns a response to the access management service after the processing is completed;

[0107] Database update and device re-registration steps: Access the management service to modify the database, change the gateway information corresponding to the device to the original gateway, and re-register with the original gateway after the device goes offline. The original gateway returns the registration result to the device.

[0108] 2. In the prior art, when an abnormality occurs in a gateway service, the device state associated with the service will automatically change to an abnormal state until the service is restored, and the device will remain unavailable. The solution provided by the present invention effectively solves the problem that registered devices cannot be used normally when the device scheduling service is abnormal. When an abnormality occurs in the gateway node service, the solution provided by the present invention can guide the device to register with other gateway services, thereby ensuring the online rate of the device even in the case of service abnormalities. The present invention enables the device to flexibly switch between different gateways and platforms and maintain a stable connection, ensuring that the device service is not affected by the abnormality of the gateway service. This solution ensures that the device can quickly return to a normal working state under abnormal circumstances, thereby ensuring business continuity.

[0109] Although the embodiments of the present invention have been shown and described above, it will be appreciated that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, substitute and vary the above embodiments within the scope of the present invention.

Claims

1. A device redirection gateway side implementation method, characterized in that: The device redirection gateway side implementation method is used to guide the device to register with another gateway service and migrate the device to a normal platform when an abnormality occurs in the gateway node service; through the registration, redirection and cancellation of redirection steps, the device can be flexibly switched and stably connected between different gateways and platforms to ensure that the device business is not affected by the abnormality of the gateway service; The device redirection gateway side implementation method includes at least the following steps: S1. The access management service actively sends redirection information to the original gateway. After receiving the redirection information, the original gateway stores the redirection information in the database; if the device is online, the device logout operation is performed; S2. The device initiates a registration request to the platform. After receiving the registration information, the device access service immediately sends a notification. After receiving the notification, the gateway service of platform 1 queries the middle platform to obtain the device information and stores the device information in the database; the device access service then obtains the data from the database and caches it; S3. The device registration request is sent to the device access service again. The device brand is determined, the session key SessionKey for this registration is generated through the SDK, and it is determined whether the device needs to perform a redirection operation. If redirection is required, the access service will synchronously send the device capability information and session key SessionKey to the gateway service of platform 2 through the HTTP protocol, and return the redirection address information to the device; if registration fails, the address processing in the above process will be repeated; S4. After receiving the device registration session key SessionKey and device capability information sent by platform 1, the gateway service of platform 2 will convey this information to the device access service in the form of a notification; after receiving this information, the device access service will update and refresh the data in real time; S5. The device initiates a registration request to platform 2. The gateway service of platform 2 then queries the middle platform and obtains the device login information. After obtaining the information, it determines whether it is consistent with the device in step S3. If it is consistent, the session key SessionKey of this registration is further verified; if all the information is correct, the device will be successfully launched on platform 2; if there is any information error, the registration fails, and the device will return to platform 1 and repeat the above process.

2. The method according to claim 1, characterized in that: The data interaction method between the device access service, gateway service and middle platform during the device registration process is as follows: the device access service sends a notification to the gateway service after receiving the device registration information. The gateway service obtains the device information from the middle platform based on the notification and stores it in the database. The device access service then obtains the data from the database for cache to ensure the integrity and consistency of the data.

3. The method according to claim 1, characterized in that: In step S3, the judgment basis for whether the device needs to be redirected includes the registration mechanism corresponding to the device brand and the comprehensive judgment of the device capability information and the session key SessionKey. The relevant information is sent to the gateway service of platform 2 for judgment through the access service.

4. The method according to any one of claims 1 to 3, characterized in that: It also includes the following steps in the device redirection process: The access management service actively initiates a device scheduling request, which is sent to the scheduling service; The scheduling service assigns a new gateway to the device according to the scheduling strategy; The dispatch service sends the data between the device and another gateway to the original gateway through the dispatch device request; The original gateway records the scheduling relationship between the device and another gateway, including the device identification and the association information with the other gateway; The original gateway returns the scheduling relationship data to the scheduling service, where the scheduling relationship data includes the association record between the device and another gateway; The scheduling service transparently transmits the scheduling relationship data to the access management service; The access management service stores the scheduling relationship in the database for subsequent query and management; At the same time, the original gateway kicks the device offline to ensure that the device's connection to the original gateway is disconnected; After the device goes offline, it will resend a registration request to the original gateway to trigger the redirection process; The original gateway determines whether the device needs to be redirected based on the data recorded in the scheduling relationship between the device and another gateway; If redirection is required, the original gateway will first synchronize the registration information to another gateway to ensure that the other gateway obtains the device's registration information; After receiving the information, the other gateway returns a response to the original gateway, which is used to confirm receipt of the registration information; After receiving the response, the original gateway sends the redirection information to the device, so that the device obtains the redirection target information; After receiving the information, the device initiates registration with another gateway in the redirection information to establish a connection at the new gateway; The other gateway returns the registration result to the device, informing it whether the registration is successful; The other gateway reports the gateway information to the dispatch service so that the dispatch service can understand the gateway belonging to the device.

5. The method according to claim 4, characterized in that: It also includes the following steps during the device unredirection process: The access management service initiates a request to cancel device scheduling to the original gateway, starting the cancellation redirection process; The original gateway modifies the corresponding information between the device and the gateway, and restores the association between the device and the gateway to the original state; The original gateway returns the gateway response information corresponding to the modified device to the access management service so that the access management service can perform subsequent operations; After receiving the data, the access management service sends a request to cancel the device scheduling to another gateway, notifying the other gateway to perform the device offline operation; Another gateway takes the device offline; After another gateway goes offline, it returns a response to the access management service, informing the access management service that the device is offline; The access management service modifies the database, changes the gateway information corresponding to the device to the original gateway, and restores the original record of the gateway information corresponding to the device in the database; After the device goes offline, it re-registers with the original gateway to re-establish the connection at the original gateway; The original gateway returns the registration result to the device, informing the device whether the registration is successful.

Images