A method and system for device unitized scheduling access

Abstract

A method and system for device unitized scheduling access are disclosed. In one implementation of the present invention, a terminal device can send a regional unit scheduling address request to a regional unit, which obtains the terminal device's slice information based on the request and assembles a domain name list based on the slice information as a response to the request. The terminal device initiates a service request to a target regional unit based on the received domain name list and obtains a processing result of the service request from a platform service of the target regional unit if the platform service is available. If the platform service is not available, the target regional unit resolves the domain name IP address to a backup regional unit to achieve a seamless handover.

Description

Technical Field

[0001] This invention relates to the field of information technology, and in particular to a unitized scheduling access method and system for equipment. Background Technology

[0002] The Internet of Things (IoT) is a new generation of information technology, an internet that connects everything. With the development of IoT technology, connected terminals have been applied in various industries, such as video surveillance, vehicles, facial recognition, regional alarms, passenger flow statistics, mask recognition, and fire early warning. More and more terminal devices (such as video network terminal devices) are being connected to the terminal interconnection platform.

[0003] Traditional terminal interconnection platforms use a single-center deployment architecture. When devices connect, they rely on the platform center for scheduling. When the platform center fails, the devices cannot come online. User clients also rely on the platform center for command forwarding. Therefore, when the platform center fails, client-side commands from the platform center cannot reach the device, making the user client unusable.

[0004] Therefore, there is a need for methods and systems that can improve upon the deficiencies in existing technologies. Summary of the Invention

[0005] This summary is provided to introduce, in a simplified form, some concepts that will be further described in the following detailed description section. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to help determine the scope of the claimed subject matter.

[0006] To address the aforementioned technical problems in existing technologies, such as the reliance on a single central node for scheduling and signaling distribution during terminal device access, this invention proposes a multi-regional central unit deployment platform without altering the terminal device access interaction. Both the client and device sides support regional scheduling and use the target region's domain name for request access.

[0007] In the event of a failure, operations and maintenance personnel will promptly resolve the domain name and IP address of the faulty area center to the IP address of the backup node unit. Requests from terminal devices, after local domain name resolution, will obtain the new IP address and be able to access the network normally, achieving a seamless switchover. This ultimately achieves domain name separation, independent resource planning, scheduling, and restriction for each entry point, as well as management of signaling storms.

[0008] Specifically, in one embodiment of the present invention, a method for device unitized scheduling access is proposed, the method comprising:

[0009] Receive the regional unit scheduling address request from the terminal device;

[0010] Based on the regional unit scheduling address request, obtain the device fragmentation information corresponding to the terminal device;

[0011] Based on the device fragmentation information and according to the functional modules required by the terminal device, a list of domain names for the device access endpoints is assembled and the list of domain names is returned to the terminal device. The list of domain names includes the IP address of the device access endpoint and the device access endpoint corresponds to the functional module at the target area unit determined based on the device fragmentation information.

[0012] At the target area unit, a service request including the domain name list is received from the terminal device; and

[0013] When the platform service at the target area unit is available, the platform service returns the processing result of the service request to the terminal device.

[0014] When the platform service at the target area unit is unavailable, the service request is forwarded to the backup area unit, and the processing result of the service request by the platform service at the backup area unit is transmitted to the terminal device via the target area unit.

[0015] In one embodiment of the present invention, the regional unit scheduling address request is sent to any regional unit and received by the platform gateway of that regional unit, and obtaining the device fragmentation information corresponding to the terminal device based on the regional unit scheduling address request further includes:

[0016] The device information of the terminal device is parsed from the regional unit scheduling address request;

[0017] Verify the correctness of the device information;

[0018] If the verification passes, a device access information request is sent to the platform service; and

[0019] In response to the device access information request, the device fragmentation information is obtained from the routing service of the area unit.

[0020] In the above embodiments of the present invention, the service request is received by the platform gateway of the target area unit, and after receiving the service request, the method further includes:

[0021] The device information of the terminal device is parsed from the service request;

[0022] Verify the correctness of the device information;

[0023] If the verification passes, obtain the fragmentation information of the terminal device from the routing service; and

[0024] When it is determined from the fragmentation information that the service request is for access within the same fragment of the target region unit, the service request is sent to the platform service of the target region unit for processing.

[0025] In one embodiment of the present invention, the spare area unit is in a hot backup state.

[0026] In one embodiment of the present invention, the platform services of the target area unit and the backup area unit respectively use MySQL to store data and use a group replication plugin to realize data synchronization between area units.

[0027] In one embodiment of the present invention, forwarding the service request to the backup zone unit further includes resolving the domain name list in the service request to a backup domain name list corresponding to the backup zone unit and performing proxy access to the backup zone unit based on the backup domain name list.

[0028] In the above embodiments of the present invention, the list of backup domain names includes the IP addresses of backup device access endpoints corresponding to the functional modules at the backup area unit.

[0029] In another embodiment of the present invention, a system for device unitized scheduling access is disclosed, the system comprising a plurality of distributed regional units, each of the plurality of regional units comprising:

[0030] A platform gateway device configured to receive a regional unit scheduling address request from a terminal device and a service request including a list of domain names as a response to the regional unit scheduling address; and

[0031] The platform service device is configured to:

[0032] Based on the regional unit scheduling address request, obtain the device fragmentation information corresponding to the terminal device;

[0033] Based on the device fragmentation information and according to the functional modules required by the terminal device, a list of domain names for device access endpoints is assembled and returned to the terminal device. This list includes the IP addresses of the device access endpoints, and each device access endpoint corresponds to a functional module at a target regional unit among the plurality of regional units determined based on the device fragmentation information.

[0034] When the platform service at the target area unit is available, the processing result of the service request will be returned to the terminal device.

[0035] When the platform service at the target area unit is unavailable, the platform gateway device is further configured to forward the service request to a backup area unit among the plurality of area units and to pass through the processing result of the service request by the platform service at the backup area unit to the terminal device.

[0036] In one embodiment of the present invention, the regional unit scheduling address request is sent to any one of the plurality of regional units and received by the platform gateway device of that regional unit, wherein the regional unit further includes a routing service device, and the platform gateway device is further configured to:

[0037] The device information of the terminal device is parsed from the regional unit scheduling address request;

[0038] Verify the correctness of the device information; and

[0039] If the verification passes, a device access information request is sent to the platform service device, so that the platform service device can obtain the device fragmentation information from the routing service device in response to the device access information request.

[0040] In the above embodiments of the present invention, after receiving the service request, the platform gateway device is further configured to:

[0041] The device information of the terminal device is parsed from the service request;

[0042] Verify the correctness of the device information;

[0043] If the verification passes, obtain the fragmentation information of the terminal device from the routing service device; and

[0044] When it is determined from the fragmentation information that the service request is for access within the same fragment of the target region unit, the service request is sent to the platform service of the target region unit for processing.

[0045] In one embodiment of the present invention, the platform gateway device is further configured to forward the service request to the backup zone unit by: resolving the domain name list in the service request to a backup domain name list corresponding to the backup zone unit and performing proxy access to the backup zone unit based on the backup domain name list.

[0046] In another embodiment of the present invention, a computer-readable storage medium is disclosed, which stores instructions for device unitized scheduling access, including:

[0047] Instructions used to receive regional unit scheduling address requests from terminal devices;

[0048] Instructions for obtaining device fragmentation information corresponding to the terminal device based on the regional unit scheduling address request;

[0049] An instruction for assembling a list of domain names for device access endpoints based on the device fragmentation information and the functional modules required by the terminal device, and returning the list of domain names to the terminal device, wherein the list of domain names includes the IP address of the device access endpoint and the device access endpoint corresponds to the functional module at the target area unit determined based on the device fragmentation information;

[0050] Instructions for receiving, at the target area unit, a service request including the domain name list from the terminal device; and

[0051] Instructions for returning the processing result of the service request by the platform service to the terminal device when the platform service at the target area unit is available.

[0052] When the platform service at the target area unit is unavailable, the instruction further includes instructions to forward the service request to a backup area unit and to transmit the processing result of the service request by the platform service at the backup area unit to the terminal device via the target area unit.

[0053] In one embodiment of the present invention, the regional unit scheduling address request is sent to any regional unit and received by the platform gateway of that regional unit, and the instruction for obtaining device fragmentation information corresponding to the terminal device based on the regional unit scheduling address request further includes:

[0054] Instructions for parsing device information of the terminal device from the regional unit scheduling address request;

[0055] Instructions used to verify the correctness of the device information;

[0056] An instruction for sending a device access information request to the platform service if the verification passes; and

[0057] Instructions for obtaining device fragmentation information from the routing service of the area unit in response to the device access information request.

[0058] In the above embodiments of the present invention, the service request is received by the platform gateway of the target area unit, and after receiving the service request, the instruction further includes:

[0059] Instructions for parsing device information of the terminal device from the service request;

[0060] Instructions used to verify the correctness of the device information;

[0061] Instructions for obtaining fragmentation information of the terminal device from the routing service if the verification passes; and

[0062] Instructions for sending the service request to the platform service of the target region unit for processing when it is determined from the fragmentation information that the service request is for access within the same fragment of the target region unit.

[0063] In one embodiment of the present invention, the instruction for forwarding the service request to the backup zone unit further includes an instruction for resolving the domain name list in the service request to a backup domain name list corresponding to the backup zone unit and for proxying access to the backup zone unit based on the backup domain name list.

[0064] In the above embodiments of the present invention, the list of backup domain names includes the IP addresses of backup device access endpoints corresponding to the functional modules at the backup area unit.

[0065] Other aspects, features, and embodiments of the invention will become apparent to those skilled in the art after reading the following description of specific exemplary embodiments of the invention in conjunction with the accompanying drawings. Although features of the invention may be discussed below with reference to certain embodiments and drawings, all embodiments of the invention may include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed having certain advantageous features, one or more of such features may also be used according to the various embodiments of the invention discussed herein. Similarly, although exemplary embodiments may be discussed below as embodiments of devices, systems, or methods, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. Attached Figure Description

[0066] To gain a more detailed understanding of the features described above in this disclosure, reference can be made to a more specific description of the above-briefly summarized aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description.

[0067] Figure 1 A schematic diagram of a system architecture for device unitized scheduling access according to an embodiment of the present disclosure is shown.

[0068] Figure 2 A data flow diagram of a system for device unitized scheduling access according to an embodiment of the present disclosure is shown.

[0069] Figure 3 A flowchart of a method for device unitized scheduling access according to an embodiment of the present disclosure is shown. Detailed Implementation

[0070] The various embodiments will now be described in more detail with reference to the accompanying drawings, which form part of this invention and illustrate specific exemplary embodiments. However, the embodiments may be implemented in many different forms and should not be construed as limiting the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of these embodiments to those skilled in the art. The embodiments may be implemented as methods, systems, or devices. Therefore, these embodiments may be implemented in hardware, entirely in software, or in a combination of software and hardware aspects. Therefore, the following detailed description is not intended to be limiting.

[0071] The steps in each flowchart can be performed by hardware (e.g., processor, engine, memory, circuitry), software (e.g., operating system, application, driver, machine / processor executable instructions), or a combination thereof. As will be understood by those skilled in the art, the methods involved in each embodiment may include more or fewer steps than shown.

[0072] To address the shortcomings of existing technologies, this invention discloses a method and system for unitized scheduling access of devices. In one implementation of this invention, a terminal device can send a regional unit scheduling address request to a regional unit. Based on this request, the regional unit obtains the fragmentation information of the terminal device and assembles a domain name list as a response to the request. The terminal device initiates a service request to a target regional unit based on the received domain name list and obtains the processing result of the service request from the platform service of the target regional unit when the platform service is available. If the platform service is unavailable, the target regional unit resolves the domain name IP address to a backup regional unit to achieve seamless handover.

[0073] The following sections will provide a more detailed and comprehensive description of various aspects of this disclosure using block diagrams and method flowcharts.

[0074] Figure 1 A schematic diagram of a system architecture for device unitized scheduling access according to an embodiment of the present disclosure is shown.

[0075] like Figure 1 As shown, in one implementation of the present invention, the system for unitized scheduling access of devices includes multiple regional units (i.e., multiple regional centers) deployed in a distributed manner. Figure 1 The region center is shown in the diagram (in this paper, region cells and region centers are equivalent and can be used interchangeably). For the sake of simplicity, Figure 1 Only two region centers are shown, namely region center 1 and region center 2. In other implementations of the invention, any other suitable number of region units or region centers may be included.

[0076] In one embodiment of the present invention, the regional center adopts a modular architecture, using units as the basic unit of deployment. Multiple units can be deployed across all data centers, with the number varying. These regional units support distributed deployment and expansion, and business capabilities are split across multiple regional unit nodes using data sharding to form mutual backup relationships, thereby improving the platform's resilience and availability. Furthermore, on the client side (such as...) Figure 1 User client 1 and user client 2 (as shown) and device-side (i.e., terminal device, such as...) Figure 1 Cameras 1 and 2 shown (etc.) all support scheduling by region unit.

[0077] like Figure 1 As shown, each terminal device (i.e., Figure 1 The cameras shown all have corresponding area units. For example, camera 1 corresponds to area center 1, and camera 2 corresponds to area center 2. Thus, each terminal device has segmentation information associated with its corresponding area unit.

[0078] In one embodiment of the present invention, such as Figure 1 As shown, each regional center includes a platform gateway, a global routing service, and a platform service.

[0079] In one or more implementations of the present invention, the platform gateway can be used to receive the identification information of the terminal device when the terminal device powers on and requests the service of the regional unit, obtain the corresponding scheduling policy matching it through the routing service, and allocate the device to the regional center of different segments.

[0080] Specifically, in one embodiment of the present invention, the platform gateway may be configured to receive a regional unit scheduling address request from a terminal device (in various embodiments of the present invention, this request from the terminal device may be sent to any regional unit); parse (e.g., via a plug-in) device information of the terminal device from the regional unit scheduling address request; verify the correctness of the device information; and, if the verification passes, send a device access information request to the platform service, so that the platform service, in response to the device access information request, obtains the device fragmentation information of the terminal device from the routing service.

[0081] In one embodiment of the present invention, after receiving a service request from a terminal device, the platform gateway may be further configured to parse (e.g., via a plug-in) device information of the terminal device from the service request; verify the correctness of the device information; if the verification passes, obtain fragment information of the terminal device from the routing service; and when it is determined from the fragment information that the service request is for access within the same fragment of the target area unit (i.e., the target area unit (e.g., area center 1) to which the terminal device (e.g., camera 1) sends the service request is the area unit corresponding to the terminal device) and the platform service of the target area unit is currently available, send the service request to the platform service of the target area unit for processing.

[0082] In another embodiment of the present invention, when the platform service of the target area unit is currently unavailable, the platform gateway may be further configured to forward the service request to a backup area unit (such as area center 2) among the plurality of area units and transparently transmit the processing result of the service request by the platform service at the backup area unit to the terminal device. In another embodiment of the present invention, the platform gateway may be further configured to forward the service request to the backup area unit by: resolving the domain name list in the service request from the terminal device to the backup domain name list corresponding to the backup area unit and performing proxy access to the backup area unit based on the backup domain name list.

[0083] In one or more implementations of this invention, data needs to be directly synchronized with the database and cached data in near real-time, so that the backup node data is in a hot standby state. This allows the backup node of the regional unit to quickly provide services even when the primary node of the regional unit fails, avoiding excessively long failover startup loading wait times that exceed the fault handling time. In an exemplary and non-limiting example of this invention, for the database selection used to store data, TiDB and Cassandra, which support multi-center data synchronization, are suitable as global unit data storage. However, the platform services of the regional center (such as user modules and device modules) do not require multi-region global synchronization, so using MySQL as storage is more efficient, and its MGR (Group Replication) plugin is used to implement the backup node synchronization measures for regional center data. The cached data synchronization method selects a multi-data source write method, supporting different write strategies. The global unit data adopts the simultaneous write success ALWAY strategy, while the backup node data synchronization adopts the local write success LOCAL strategy.

[0084] In one implementation of the present invention, Figure 1The global routing service can be used to provide routing services to terminal devices, and provides global routing services by storing unit fragment routing data (which enables the distribution of service capabilities across multiple regional unit nodes through data fragmentation). Specifically, the routing service is configured to respond to device fragmentation information requests from platform services and platform gateways by providing them with the device fragmentation information of the requesting terminal devices for assembling a domain name list and determining whether to provide access within the same fragment.

[0085] In one implementation of the present invention, Figure 1 The platform services can be tailored to the access terminals (clients, such as user clients 1 and 2) and device terminals (such as terminal devices, for example...) of the product business. Figure 1 Cameras 1 and 2 in the diagram) divide the platform service into user module, device module, scheduling module, cloud storage module, binding module, alarm module, device status module, capability reporting module, etc. (not limited to) Figure 1 These modules are shown. Each module provides various services to the terminal device or user client. For example, the user module stores customer identification data and provides services, the device module stores device identification and provides services, the scheduling module stores device identification and provides services, and so on.

[0086] Before providing the corresponding service, the platform service can first be configured to obtain device fragmentation information corresponding to the terminal device. Specifically, the platform service can obtain the device fragmentation information from the routing service in response to a device access information request from the platform gateway. Then, the platform service can be further configured to assemble a list of domain names of the device access endpoints based on the device fragmentation information and according to the functional modules required by the terminal device (as a response to the device access information request received from the platform gateway), and return the list of domain names to the terminal device. Finally, when the platform service at the target area unit is available, the platform service can return the processing result of the service request to the terminal device.

[0087] In one embodiment of the present invention, the domain name list includes the IP addresses of (multiple) device access endpoints, and each device access endpoint corresponds to a functional module in the target area unit to which the terminal device will issue a service request, determined based on the device fragmentation information. In an exemplary and non-limiting example, the platform service obtains the fragmentation information corresponding to the terminal device from the routing service and, based on the signaling control of the device interaction and the functions to be invoked (such as cloud storage recording, message alarms, etc.), assembles the domain name list of each device access endpoint as a response result and returns it: "return{"cloud":

[0088] "cloud-01.xxx.xxx.com","alarm":"alarm-01.xxx.xxx.com",…}".

[0089] In one embodiment of the present invention, Figure 1 The system architecture shown may also optionally include provincial nodes, which can be used to carry high-bandwidth, high-computational-consumption service modules, such as signaling access, P2P, media forwarding, and maintain long-term connections after login.

[0090] Figure 2 A data flow diagram of a system for device unitized scheduling access according to an embodiment of the present disclosure is shown.

[0091] First, the terminal device requests a regional unit scheduling address from any regional center (i.e., regional unit). The regional center that receives the regional unit scheduling address request (in...) Figure 2 In the example, the platform gateway (which can be any other regional center in other embodiments, specifically regional center 1) parses the device information from the request and verifies it (e.g., by verifying the device information's correctness through a gateway plugin). After successful verification, the platform gateway sends a request to the platform service of that regional center to obtain device access information.

[0092] In response to the device access information request, the platform service obtains the device fragmentation information of the terminal device from the routing service of the regional center, and assembles a list of domain names of the device access endpoints based on the obtained device fragmentation information and the functional modules that the terminal device needs to use (call), and returns the list of domain names to the terminal device, for example, "return{"cloud":"cloud-01.xxx.xxx.com","alarm":"alarm-01.xxx.xxx.com",...}", where "01" can be the identifier of the regional unit to which the terminal device belongs, determined based on the device fragmentation information, and as those skilled in the art will understand, it may also be the identifier of other regional units such as "02" or "03".

[0093] After receiving the domain name list, the terminal device sends the domain names of each module in the list to the corresponding regional center (target regional unit, in...). Figure 2 The platform gateway requests to log in to the services provided by the corresponding endpoints (in which case it is regional center 1, but in other embodiments it may be other regional centers) to log in, for example, to request the cloud storage service of regional center 1 via the request path https: / / cloud-01.xxx.xxx.com / (as an example and not a limitation).

[0094] The platform gateway of the target area unit receives the service request, parses (via the gateway plugin) the device information of the terminal device from the service request, verifies it, and after successful verification, obtains the fragmentation information of the terminal device from the routing service of the target area unit (area center 1) to confirm whether the terminal device corresponds to the target area unit itself (i.e., whether the terminal device is fragmented into the area unit). If confirmed, the platform gateway determines that the service request is an access within the same fragment and forwards the service request to the platform service within the area unit for processing, such as... Figure 2 As shown by reference numeral "1" in the attached figure.

[0095] If the platform service is currently available, the platform processing result is returned to the terminal device as a response to its service request.

[0096] If the current platform service is unavailable, such as when the platform service fails, the platform gateway determines that the access is not within the same shard. Figure 2 As indicated by reference numeral "2" in the attached diagram. At this point, the platform gateway forwards the service request to a backup area unit (such as...). Figure 2 (Region center 2). In one embodiment of the present invention, the backup region unit may be the next region unit after the current target region unit, but in other embodiments of the present invention, any suitable backup region unit selection rule may be used to select the backup region unit.

[0097] In various implementations of the present invention, the platform gateway of the target area unit can forward the service request to the backup area unit by resolving the domain name list in the service request to the backup domain name list corresponding to the backup area unit and proxying access to the backup area unit based on the backup domain name list (such as via the original request path https: / / cloud-02.xxx.xxx.com / ).

[0098] Finally, after the platform service of the backup area unit completes processing, the processing result is transparently transmitted to the terminal device via the platform gateway of the target area unit, such as... Figure 2 The figures are labeled “3” and “4”.

[0099] Although in the above embodiments of the present invention, regional center 1 is used as the target regional unit and regional center 2 is used as the backup regional unit, in other embodiments of the present invention, regional center 2 can also be used as the target regional unit (when the terminal device belongs to regional center 2) and accessed within the same slice (e.g., when platform services are available) Figure 2(As indicated by reference numeral "①" in the attached diagram), and Regional Center 1 can be used as a backup regional unit when platform services at Regional Center 2 are unavailable, and can be accessed from outside the same fragment (e.g., Figure 2 (as indicated by the reference numeral "②" in the attached figure).

[0100] Figure 3 A flowchart of a method 300 for device unitized scheduling access according to an embodiment of the present disclosure is shown.

[0101] like Figure 3 As shown, method 300 begins at step 302, receiving a regional unit scheduling address request from the terminal device. In one embodiment of the invention, the regional unit scheduling address request is sent to any regional unit and received by the platform gateway of that regional unit.

[0102] Next, method 300 continues to step 304, obtaining device fragmentation information corresponding to the terminal device based on the regional unit scheduling address request. In one embodiment of the present invention, this step further includes parsing the device information of the terminal device from the regional unit scheduling address request; verifying the correctness of the device information; sending a device access information request to the platform service if the verification passes; and obtaining the device fragmentation information from the routing service of the regional unit in response to the device access information request.

[0103] Then, method 300 continues to step 306, assembling a list of domain names of the device access endpoints based on the device fragmentation information and according to the functional modules required by the terminal device, and returning the list of domain names to the terminal device, wherein the list of domain names includes the IP address of the device access endpoint and the device access endpoint corresponds to the functional module at the target area unit determined based on the device fragmentation message.

[0104] Next, method 300 continues to step 308, whereby a service request including the domain name list is received from the terminal device at the target area unit. In one embodiment of the present invention, the service request is received by the platform gateway of the target area unit, and after receiving the service request, method 300 further includes: parsing the device information of the terminal device from the service request; verifying the correctness of the device information; if the verification passes, obtaining the fragmentation information of the terminal device from the routing service; and when it is determined from the fragmentation information that the service request is for access within the same fragment of the target area unit, sending the service request to the platform service of the target area unit for processing.

[0105] Finally, method 300 continues to step 310, whereby, when the platform service at the target area unit is available, the processing result of the platform service for the service request is returned to the terminal device; wherein, when the platform service at the target area unit is unavailable, the service request is forwarded to a backup area unit, and the processing result of the platform service at the backup area unit for the service request is transparently transmitted to the terminal device via the target area unit. In one embodiment of the present invention, the backup area unit is in a hot backup state, and the platform services of the target area unit and the backup area unit respectively use MySQL to store data and use a group replication plugin to achieve data synchronization between area units. In one embodiment of the present invention, forwarding the service request to the backup area unit further includes resolving the domain name list in the service request to a backup domain name list corresponding to the backup area unit and performing proxy access to the backup area unit based on the backup domain name list. In the above embodiments of the present invention, the backup domain name list includes the IP address of the backup device access endpoint corresponding to the functional module at the backup area unit.

[0106] In summary, the technical solution of this invention splits business capabilities across multiple regional nodes through data sharding, forming a mutual backup relationship between them. This enhances the platform's resilience and availability, enabling controllable access scheduling for terminal devices and balanced service load. Furthermore, it allows for rapid failover and recovery back to the primary node under high load or failure conditions. Additionally, regional unit scheduling is further subdivided into module scheduling, achieving domain name separation. Resources at each entry point are independently planned, scheduled, and restricted, ensuring that failures or high loads in some services do not affect the use of other functions.

[0107] The embodiments of the present invention have been described above with reference to block diagrams and / or operational descriptions of methods, systems, and computer program products according to embodiments of the present invention. The functions / actions indicated in the blocks may appear in a different order than shown in any flowchart. For example, depending on the functions / actions involved, two blocks shown consecutively may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order.

[0108] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for device unitized scheduling access, applied to a plurality of regional units in distributed deployment, the method comprising: receiving a regional unit scheduling address request from a terminal device, the regional unit scheduling address request being sent to any regional unit of the plurality of regional units and received by a platform gateway of the regional unit; obtaining device slice information corresponding to the terminal device based on the regional unit scheduling address request; assembling a domain name list of device access endpoints based on the device slice information and according to functional modules needed to be used by the terminal device, and returning the domain name list to the terminal device, wherein the domain name list comprises IP addresses of the device access endpoints and the device access endpoints correspond to functional modules at a target regional unit determined based on the device slice information; receiving a service request comprising the domain name list from the terminal device at the target regional unit; and returning a processing result of the platform service to the service request to the terminal device when the platform service at the target regional unit is available, wherein when the platform service at the target regional unit is unavailable, the service request is forwarded to a backup regional unit and a processing result of the platform service at the backup regional unit to the service request is transparently transmitted to the terminal device via the target regional unit. 2.The method of claim 1, wherein obtaining device slice information corresponding to the terminal device based on the regional unit scheduling address request further comprises: parsing device information of the terminal device from the regional unit scheduling address request; checking correctness of the device information; sending a device access information request to the platform service if the checking is passed; and obtaining the device slice information from a routing service of the regional unit in response to the device access information request. 3.The method of claim 2, wherein the service request is received by the platform gateway of the target regional unit, and after receiving the service request, the method further comprises: parsing device information of the terminal device from the service request; checking correctness of the device information; obtaining slice information of the terminal device from the routing service if the checking is passed; and when it is determined according to the slice information that the service request is for access within a same slice of the target regional unit, sending the service request to the platform service of the target regional unit for processing. 4.The method of claim 1, wherein the backup regional unit is in a hot backup state, and the platform services of the target regional unit and the backup regional unit each use MySQL to store data and use a group replication plug-in to realize data synchronization between regional units. 5.The method of claim 1, wherein forwarding the service request to the backup regional unit further comprises resolving the domain name list in the service request to a backup domain name list corresponding to the backup regional unit and proxying access to the backup regional unit based on the backup domain name list. ​ ​ 6.The method of claim 5, wherein the backup domain name list comprises IP addresses of backup device access endpoints corresponding to functional modules at the backup regional unit. 7.A system for device unitized scheduled access, the system comprising a plurality of regional units distributedly deployed, each of the plurality of regional units comprising: a platform gateway device configured to receive, from a terminal device, a regional unit scheduled address request and a service request comprising a domain name list as a response to the regional unit scheduled address, the regional unit scheduled address request being sent to any regional unit of the plurality of regional units and received by the platform gateway device of the regional unit; and a platform service device configured to: obtain device slice information corresponding to the terminal device based on the regional unit scheduled address request; assemble a domain name list of device access endpoints based on the device slice information and according to functional modules needed to be used by the terminal device and return the domain name list to the terminal device, wherein the domain name list comprises IP addresses of the device access endpoints and the device access endpoints correspond to functional modules at a target regional unit of the plurality of regional units determined based on the device slice information; and return a processing result of the service request to the terminal device when a platform service at the target regional unit is available, wherein when the platform service at the target regional unit is unavailable, the platform gateway device is further configured to forward the service request to a backup regional unit of the plurality of regional units and pass through a processing result of the service request by a platform service at the backup regional unit to the terminal device. 8.The system of claim 7, wherein the regional unit further comprises a routing service device, and the platform gateway device is further configured to: resolve device information of the terminal device from the regional unit scheduled address request; check correctness of the device information; and send a device access information request to the platform service device in case that the check passes, so that the platform service device obtains the device slice information from the routing service device in response to the device access information request. 9.The system of claim 8, wherein after receiving the service request, the platform gateway device is further configured to: resolve device information of the terminal device from the service request; check correctness of the device information; obtain slice information of the terminal device from the routing service device in case that the check passes; and send the service request to a platform service of the target regional unit for processing when it is determined according to the slice information that the service request is for an access within a same slice of the target regional unit.

10. The system of claim 7, wherein the platform gateway device is further configured to forward the service request to the backup regional unit by resolving the domain name list in the service request to a backup domain name list corresponding to the backup regional unit and proxying access to the backup regional unit based on the backup domain name list.

Images