Distributed scheduling method, electronic device, and storage medium

Abstract

Embodiments of the present application provide a distributed scheduling method and device. The method is applied to a scheduling server, the scheduling server is in communication connection with terminal devices in a terminal device cluster, each terminal device has task processing authority for at least one service platform, and an embodiment of the method comprises: determining a target service platform involved in a target task, and screening candidate terminal devices having task processing authority for the target service platform from the terminal device cluster; selecting a target terminal device from the candidate terminal devices based on load information of each candidate terminal device; and assigning the target task to the target terminal device. This implementation improves task processing efficiency and simultaneously achieves load balancing of the terminal devices.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a distributed scheduling method and apparatus. Background Technology

[0002] With the development of computer technology, the number and functions of various service platforms are increasing. In some scenarios, unified management of multiple service platforms is necessary. Taking logistics as an example, in rural areas and other rural regions, to solve the problem of scattered parcel collection and delivery, resources such as venues, manpower, and transportation capacity can be centrally allocated to multiple logistics service providers. Based on this, several customer service representatives can be assigned to uniformly manage the logistics service platforms of each logistics service provider.

[0003] In existing technologies, several service platforms that need to be connected can be assigned to each administrator. Each administrator can log in to the corresponding service platform through a terminal device (such as a browser installed on it) to process tasks. This method requires administrators to frequently switch and log in to different service platforms, resulting in low task processing efficiency. At the same time, due to the large differences in the workload of different service platforms, the load on different terminal devices is uneven. Summary of the Invention

[0004] This application provides a distributed scheduling method, apparatus, electronic device, and computer-readable medium to improve task processing efficiency and to load balance terminal devices performing task processing.

[0005] In a first aspect, embodiments of this application provide a distributed scheduling method applied to a scheduling server. The scheduling server is communicatively connected to terminal devices in a terminal device cluster. Each terminal device has a shared task processing client installed and has task processing permissions for at least one service platform. The method includes: determining the target service platform involved in the target task, and filtering candidate terminal devices with task processing permissions for the target service platform from the terminal device cluster; selecting a target terminal device from the candidate terminal devices based on the load information of each candidate terminal device; and sending the target task to the target terminal device to process the target task through the shared task processing client installed on the target terminal device.

[0006] Secondly, this application provides another distributed scheduling method applied to a customer service scheduling server. The customer service scheduling server is communicatively connected to customer service terminals in a customer service terminal cluster. Each customer service terminal has a shared customer service client installed and has task processing permissions for at least one logistics service platform. The method includes: determining the target logistics service platform involved in the target task, and filtering candidate customer service terminals with task processing permissions for the target logistics service platform from the customer service terminal cluster; selecting a target customer service terminal from the candidate customer service terminals based on the load information of each candidate customer service terminal; and assigning the target task to the target customer service terminal so that the target task can be processed through the shared customer service client installed on the target customer service terminal.

[0007] Thirdly, embodiments of this application provide a distributed scheduling device applied to a scheduling server. The scheduling server is communicatively connected to terminal devices in a terminal device cluster. Each terminal device has a shared task processing client installed and has task processing permissions for at least one service platform. The device includes: a determining unit, configured to determine the target service platform involved in the target task and filter candidate terminal devices with task processing permissions for the target service platform from the terminal device cluster; a selecting unit, configured to select a target terminal device from the candidate terminal devices based on the load information of each candidate terminal device; and a sending unit, configured to send the target task to the target terminal device so that the target task can be processed by the shared task processing client installed on the target terminal device.

[0008] Fourthly, this application provides a distributed scheduling device applied to a customer service scheduling server. The customer service scheduling server is communicatively connected to customer service terminals in a customer service terminal cluster. Each customer service terminal has a shared customer service client installed and has task processing permissions for at least one logistics service platform. The device includes: a determining unit, configured to determine the target logistics service platform involved in the target task and filter candidate customer service terminals with task processing permissions for the target logistics service platform from the customer service terminal cluster; a selecting unit, configured to select a target customer service terminal from the candidate customer service terminals based on the load information of each candidate customer service terminal; and a sending unit, configured to allocate the target task to the target customer service terminal so that the target task can be processed by the shared customer service client installed on the target customer service terminal.

[0009] Compared with the prior art, the embodiments of this application have the following advantages:

[0010] In this embodiment, the scheduling server first determines the target service platform involved in the target task, as well as the candidate terminal devices in the terminal device cluster that have task processing permissions for the target service platform. Then, based on the load information of each candidate terminal device, it selects the target terminal device from the candidate terminal devices and assigns the target task to the target terminal device. The target terminal device can process the target task through its installed shared task processing client, eliminating the need for administrators to frequently switch and log in to different service platforms, thus improving task processing efficiency. Simultaneously, since tasks are allocated based on the load information of the terminal devices, distributed scheduling of terminal devices can be achieved, avoiding the problem of uneven task distribution among different terminal devices and realizing load balancing of terminal devices. Attached Figure Description

[0011] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0012] Figure 1A This is an exemplary system architecture diagram to which embodiments of this application can be applied;

[0013] Figure 1B This is a schematic diagram illustrating the establishment of a long connection between the scheduling server and the terminal device in an embodiment of this application;

[0014] Figure 2A This is a schematic diagram of an application scenario of the distributed scheduling method of this application;

[0015] Figure 2B This is a schematic diagram of another application scenario of the distributed scheduling method of this application;

[0016] Figure 2C This is a schematic diagram of obtaining identity data in the distributed scheduling method of this application;

[0017] Figure 3 This is a flowchart of an embodiment of the distributed scheduling method of this application;

[0018] Figure 4 This is a flowchart of yet another embodiment of the distributed scheduling method of this application;

[0019] Figure 5 This is a schematic diagram of the structure of one embodiment of the distributed scheduling device of this application.

[0020] Figure 6 This is a schematic diagram of another embodiment of the distributed scheduling device of this application.

[0021] Figure 7 This is a schematic diagram of the structure of a device provided in an embodiment of this application. Detailed Implementation

[0022] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0023] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0024] The distributed scheduling method of this application can be applied to various task processing scenarios, such as logistics task processing and order processing. In the applicable scenarios, a designated cluster of terminal devices can uniformly process tasks involving multiple service platforms.

[0025] Taking logistics task processing as an example, in rural areas and other regions, to address the issue of dispersed parcel collection and delivery, resources such as facilities, manpower, and transportation capacity can typically be centrally allocated among multiple logistics service providers. Based on this, several customer service representatives can be assigned to manage the logistics service platforms of each provider in a unified manner.

[0026] Taking the order processing scenario as an example, this scenario can involve multiple service platforms such as food delivery service platforms, flash delivery service platforms, and errand service platforms. Several delivery capacity terminals can be allocated to uniformly process orders from various service platforms, and the delivery capacity terminals can be scheduled through a delivery capacity scheduling server to achieve load balancing of delivery capacity.

[0027] Figure 1A An exemplary system architecture 100 to which embodiments of this application may be applied is shown. For example... Figure 1A As shown, the system architecture 100 may include a scheduling server 101, a terminal device cluster 102, and a target server cluster 103 maintaining a service platform. The terminal device cluster 102 may include several terminal devices. The target server cluster 103 may include several target servers. The servers involved in this embodiment can be physical servers or cloud servers, and are not limited here. The terminal devices involved in this embodiment may include, but are not limited to, various electronic devices such as desktop computers, laptops, tablets, and mobile phones. It should be understood that... Figure 1A The number of terminal devices and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices and servers can be used.

[0028] The scheduling server 101 can communicate with the terminal devices in the terminal device cluster 102. Optionally, a persistent connection can be used for communication, and heartbeat signals can be transmitted periodically. The persistent connection can be constructed according to a target protocol, which can be a full-duplex communication protocol based on the Transmission Control Protocol (TCP), such as the WebSocket protocol. The WebSocket protocol is a protocol for full-duplex communication over a single TCP connection, which allows the server to proactively push data to the terminal devices. See also... Figure 1B As shown, a terminal device only needs to complete a handshake with the server once to establish a persistent connection and perform bidirectional data transmission. Therefore, the scheduling server can proactively assign tasks to the terminal device at any time, without requiring the terminal device to send a request in advance. By establishing a long connection, the scheduling server's scheduling efficiency and task assignment efficiency can be improved, thereby increasing the overall task processing efficiency.

[0029] Each target server in the target server cluster 103 can maintain one or more service platforms. The service platform can be maintained by a third-party server or by other internal servers; there are no restrictions here.

[0030] Terminal devices in terminal device cluster 102 may have a shared task processing client installed. The shared task processing client supports interaction with various service platforms and supports the processing of tasks involving each service platform. Each terminal device may have task processing permissions for at least one service platform. Users of each terminal device can process tasks involving the corresponding service platform (i.e., the service platform for which they have task processing permissions) through the shared task processing client. It should be noted that each terminal device may have task processing permissions for all or some service platforms; the task processing permissions of different terminal devices may be the same, different, or partially the same; and the task processing permissions of each terminal device can be changed at any time as needed.

[0031] It should be noted that the distributed scheduling method provided in this application embodiment is generally executed by the scheduling server 101, and correspondingly, the distributed scheduling device is generally set in the scheduling server 101. The scheduling server 101 can maintain a task queue. For a target task to be processed in the task queue, the target service platform involved in the target task can be determined. Then, candidate terminal devices with task processing permissions for the target service platform are screened from the terminal device cluster 102. Based on the load information of each candidate terminal device, a target terminal device is selected from the candidate terminal devices, and the target task is assigned to the target terminal device so that the target terminal device can process the target task through its installed shared task processing client. Thus, there is no need for administrators to frequently switch and log in to different service platforms, improving task processing efficiency. At the same time, since the task is allocated based on the load information of the terminal device, distributed scheduling of the terminal devices can be realized, avoiding the problem of uneven task distribution among different terminal devices and achieving load balancing of the terminal devices.

[0032] The following explanation uses a logistics task processing scenario as an example. (See also...) Figure 2A The diagram illustrates that the customer service dispatch server can communicate with customer service terminals within a customer service terminal cluster. Each customer service terminal can have a shared customer service client installed. This shared client supports interaction with various logistics service platforms and the processing of tasks involving these platforms. The shared client can be maintained by the customer service dispatch server, including sending data and tasks. Each customer service terminal can have task processing permissions for at least one logistics service platform. Users of each customer service terminal can process tasks involving the corresponding logistics service platform (i.e., the logistics service platform with task processing permissions) through the shared client. Logistics service platforms may include, but are not limited to, the work order processing platforms, message processing platforms, arbitration processing platforms, and claims processing platforms of various logistics companies (such as Logistics Company A, Logistics Company B, etc.).

[0033] In this scenario, the customer service dispatch server can maintain a task queue, and the target task can be the task at the head of the queue. The customer service dispatch server can first determine the target logistics service platform involved in the target task to be processed. This target logistics service platform can be determined based on the type of the target task. For example, if the target task is a non-interactive task, such as a work order processing task, message processing task, address modification task, expedited delivery task, returned item after signing, or data analysis task—a task synchronized from a logistics service platform (or a task generated after parsing that task)—then the source logistics service platform of the target task can be used as the target logistics service platform. As another example, if the target task is an interactive task, such as a task synchronizing data from a logistics service platform to the customer service dispatch server, or a task synchronizing processing results stored in the customer service dispatch server to a service platform, then the logistics service platform to be interacted with can be used as the target logistics service platform. Figure 2A In the scenario shown, the target task is the work order processing task of logistics company B, and the target logistics service platform can be the work order processing platform of logistics company B.

[0034] After identifying the target logistics service platform, the customer service dispatch server can filter candidate customer service terminals with task processing permissions for the target logistics service platform from the customer service terminal cluster. Based on the load information of each candidate terminal, the server selects the target customer service terminal. The load information characterizes the task processing pressure of the customer service terminal and can be determined based on one or more factors such as the number of incomplete tasks, the type of incomplete tasks, processor processing power, and customer service personnel level. The load information can be obtained by the customer service dispatch server requesting it from each customer service terminal, or it can be statistically analyzed and updated locally in real time and read directly from the local database; no specific limitation is made here. The customer service dispatch server can choose the candidate customer service terminal with the lowest load as the target candidate customer service terminal.

[0035] Once the target customer service terminal is identified, the customer service dispatch server assigns the target task to it. This allows the target customer service terminal to process the task using its installed shared customer service client. For example, the task might involve processing a work order from Logistics Company B, such as processing the work order for shipment, arbitration, or completion. After processing the task through the shared customer service client, the result is returned to the customer service dispatch server. The server can then store this result and create another task to synchronize it to the target logistics service platform.

[0036] Each task in the task queue can be processed according to the above process. It is understandable that, due to the large number of logistics companies and the numerous logistics service platforms maintained by each company, traditional methods require customer service personnel to frequently switch and log in to different logistics service platforms to acquire data or process tasks, resulting in low task processing efficiency. In this embodiment, customer service personnel can manage and process tasks involving multiple logistics service platforms uniformly through a shared customer service client maintained by the customer service scheduling server, eliminating the need for administrators to frequently switch and log in to different service platforms, thus improving the task processing efficiency of the customer service terminal. Furthermore, since tasks are allocated based on the load information of the terminal devices, distributed scheduling of terminal devices can be achieved, avoiding the problem of uneven task distribution across different terminal devices and realizing load balancing of terminal devices.

[0037] In other logistics task processing scenarios, the target task may be an interaction with a specific logistics service platform. In this case, the logistics service platform to be interacted with can be considered the target logistics service platform. See also... Figure 2B As shown, after identifying the target customer service terminal, the customer service dispatch server can configure an access request to the target logistics service platform based on the target task, thereby sending an access request to the target customer service terminal. This allows the target customer service terminal to forward the access request to the target logistics service platform via a shared customer service client, and subsequently receive the response result from the target logistics service platform. For example, if the target task is a first synchronization task used to synchronize pending tasks from the target logistics service platform to the customer service dispatch server, the access request can be a task synchronization request, and the response result can include the pending tasks from the target logistics service platform. As another example, if the target task is a second synchronization task used to synchronize the processing results of pending tasks to the target logistics service platform, the access request can be a processing result synchronization request, and the response result can include the synchronization result from the target logistics service platform (indicating whether synchronization was successful).

[0038] In this scenario, the target logistics service platform may also pre-store a set of identity data (i.e., cookies). This cookie set may include cookies used by each customer service terminal to access the logistics service platform in advance. See, for example... Figure 2B As shown, cookies in the cookie set can be grouped according to logistics service platforms. Each logistics service platform's corresponding cookie group contains cookies used by customer service representatives with task processing permissions when accessing that logistics service platform. Cookies can be recorded in key-value pairs, such as "Customer Service 1: cookie1", "Customer Service 2: cookie2", etc. This application embodiment does not specifically limit the method of recording cookies.

[0039] Cookies in the cookie set can be obtained by target plugins installed on the client terminal (such as those installed in the browser running on the client terminal) and uploaded by the client terminal to the client dispatch server. See also: Figure 2C As shown, the target plugin can retrieve the cookie stored in the browser when a customer service representative logs into the logistics platform through the browser on the customer service terminal, and then call the logistics service platform's interface to upload the cookie to the logistics service platform. This enables centralized storage and management of cookies.

[0040] It should be noted that the customer service terminals and the customer service dispatch server can maintain heartbeat signal transmission. When any customer service terminal in the customer service terminal cluster logs back into any logistics service platform, the customer service dispatch server can continue to receive updated cookies sent by the customer service terminal that performed the login operation, and update the cookie set based on the updated cookies, such as adding to the cookie set or updating the corresponding original cookies in the cookie set. This enables real-time cookie updates.

[0041] It should also be noted that when the logistics service platform is expanded, the logistics scheduling server can also infer the logistics service platform to which the cookie belongs based on the received cookie, and thus update the cookie set with the new logistics service platform, thereby achieving real-time updates of the cookie set.

[0042] When filtering candidate customer service terminals with task processing permissions to the target logistics service platform from the customer service terminal cluster, the customer service scheduling server can first select candidate cookies for accessing the target logistics service platform from a pre-stored cookie set, and determine the source customer service terminal of each candidate cookie as a candidate customer service terminal with task processing permissions to the target logistics service platform. Thus, candidate customer service terminals with task processing permissions can be accurately identified based on cookies.

[0043] When configuring access requests to the target logistics service platform, the customer service dispatch server can first extract the target cookie used by the first target customer service terminal to access the target logistics service platform from the candidate cookies. Then, based on the target cookie, the target task, and a preset request configuration template, the access request to the target logistics service platform is configured. The request configuration template may include the Uniform Resource Locator (URL), request method information, domain, request header information, request body information, callback interface, etc., for each logistics service platform. The customer service dispatch server can first extract the required content from the request configuration template based on the target task and concatenate it to obtain the initial request. Then, the target cookie is added to the initial request to obtain the access request to the target logistics service platform. For interactive tasks, the access request is configured by the customer service dispatch server and forwarded by the shared customer service client. This reduces the processing logic of the shared customer service client, improves the task processing efficiency of the shared customer service client, and avoids lag in the shared customer service client. In addition, the customer service dispatch server can also parse (such as validation, field matching, reassembly, etc.) the stored data (such as pending tasks obtained from the logistics service platform) to execute the processing logic originally located on the client, thereby further improving the task processing efficiency of the shared customer service client.

[0044] It should be noted that the distributed scheduling method of this application can also be applied to other task processing scenarios involving multiple service platforms, such as order processing, offline data analysis task processing, and information push task processing, which will not be elaborated here.

[0045] Continue to refer to Figure 3 The diagram illustrates a flowchart of an embodiment of the distributed scheduling method of this application. This distributed scheduling method can be applied to a scheduling server (such as...). Figure 1A The scheduling server 101 shown is connected to a cluster of terminal devices (such as...). Figure 1A The terminal devices in the terminal device cluster 102 shown are connected for communication. Each terminal device may have a shared task processing client installed. The shared task processing client supports interaction with various service platforms and supports the processing of tasks involving various service platforms. The shared task processing client may be maintained by a scheduling server, such as sending data and tasks. Each terminal device may have task processing permissions for at least one service platform. Users of each terminal device can process tasks involving the corresponding service platform (i.e., the service platform with task processing permissions) through the shared task processing client. The service platform may be a third-party server (such as...). Figure 1AThe service platform maintained by the target server cluster 103 shown can also be a service platform maintained by other internal servers; this is not limited here.

[0046] In some optional implementations, the scheduling server and the terminal devices in the terminal device cluster can communicate via persistent connections and periodically transmit heartbeat signals. These persistent connections are constructed using a target protocol (such as WebSocket), which supports full-duplex communication over a single Transmission Control Protocol (TCP) connection. Based on these persistent connections, the scheduling server can proactively send tasks to the terminal devices at any time, without requiring the terminal devices to send requests in advance. This improves the scheduling efficiency and task distribution efficiency of the scheduling server, thereby enhancing overall task processing efficiency.

[0047] The process of this distributed scheduling method may include the following steps:

[0048] Step 301: Determine the target service platform involved in the target task.

[0049] In this embodiment, the execution entity of the distributed scheduling method (such as a processor in a scheduling server) can first obtain the target task and then determine the target service platform involved in the target task. The scheduling server may maintain a task queue, and the target task can be the task located at the head of the task queue. The target service platform can be determined based on the type of the target task.

[0050] In some scenarios, the target task can be a non-interactive task. A non-interactive task can be a task synchronized from a service platform, or a task generated after parsing a synchronized task. In this case, the source service platform of the target task can be considered the target service platform. Taking logistics task processing as an example, non-interactive tasks could be work order processing tasks, message processing tasks, address modification tasks, expedited delivery tasks, returned items after signing, or data analysis tasks synchronized from a logistics company's logistics service platform. Taking e-commerce as an example, non-interactive tasks could be message processing tasks, complaint handling tasks, or item verification tasks synchronized from a service platform (such as a food delivery service platform, group buying service platform, self-operated e-commerce service platform, or third-party e-commerce service platform).

[0051] In other scenarios, the target task can be an interactive task, such as a first synchronization task used to synchronize pending tasks in the target service platform to the scheduling server, or a second synchronization task used to synchronize the processing results of the pending tasks to the target service platform. In this case, the service platform to be interacted with can be considered the target service platform.

[0052] Step 302: Select candidate terminal devices with task processing permissions for the target service platform from the terminal device cluster.

[0053] In this embodiment, the execution entity can filter terminal devices with task processing permissions to the target service platform from the terminal device cluster as candidate terminal devices. As an example, the execution entity can pre-record the task processing permission information of each terminal device and determine the candidate terminal devices with task processing permissions to the target service platform based on this information.

[0054] In some optional implementations, the target service platform may pre-store a set of identity data (i.e., cookies). This cookie set may include cookies used by each terminal device to access the respective service platform. Cookies in this set can be obtained by a target plugin installed on the terminal device (e.g., in a browser) and uploaded to the scheduling server by the terminal device. When an administrator logs into the logistics platform through a browser on a terminal device, the target plugin can obtain the cookies recorded in the browser and call the service platform's interface to upload the cookies to the service platform. This allows for centralized storage and management of cookies. When filtering candidate terminal devices with task processing permissions to the target service platform from the terminal device cluster, the scheduling server can first select candidate cookies for accessing the target service platform from the pre-stored cookie set, identifying the source terminal device of each candidate cookie as a candidate terminal device with task processing permissions to the target service platform. Thus, candidate terminal devices with task processing permissions can be accurately determined based on cookies.

[0055] In some optional implementations, when any terminal device in the terminal device cluster re-logins to any service platform, the scheduling server can continue to receive updated cookies sent by the terminal device that performed the login operation, and update the cookie set based on the updated cookies, such as adding them to the cookie set or updating the corresponding original cookies in the cookie set. This enables real-time cookie updates.

[0056] Step 303: Select the target terminal device from the candidate terminal devices based on the load information of each candidate terminal device.

[0057] In this embodiment, load information can characterize the task processing pressure of the terminal device. It can be determined based on one or more factors such as the number of unfinished tasks, the type of unfinished tasks, processor processing power, and the management personnel's level. Load information can be obtained by the aforementioned execution entity by requesting it from each terminal device, or it can be statistically analyzed and updated locally in real time and read directly from the local database; no specific limitations are imposed here. The aforementioned execution entity can select the candidate terminal device with the lowest load as the target candidate terminal device.

[0058] Step 304: Send the target task to the target terminal device so that the target task can be processed through the shared task processing client installed on the target terminal device.

[0059] In this embodiment, different methods can be used to send and process target tasks for different types of target tasks. For example, if the target task is a non-interactive task, its relevant information (such as task content, task source, task number, task type, etc.) can be compiled and sent directly to the target terminal device. The user of the target terminal device can process the target task through a shared task processing client installed on the target terminal device, and return the processing result to the aforementioned execution entity through the shared task processing client.

[0060] As another example, if the target task is an interactive task, an access request to the target service platform can be configured first based on the target task. This access request is then sent to the target terminal device, which forwards the access request to the target service platform via a shared task processing client, and subsequently receives the response from the target service platform. For instance, if the target task is a first synchronization task used to synchronize pending tasks from the target service platform to the scheduling server, the access request could be a task synchronization request, and the response could include the pending tasks from the target service platform. As another example, if the target task is a second synchronization task used to synchronize the processing results of pending tasks to the target service platform, the access request could be a processing result synchronization request, and the response could include the synchronization results from the target service platform (indicating whether synchronization was successful).

[0061] In some optional implementations, when configuring access requests to the target service platform, the scheduling server can first extract the target cookie used by the first target terminal device to access the target service platform from the candidate cookies. Then, based on the target cookie, the target task, and a preset request configuration template, the access request to the target service platform is configured. The request configuration template may include the Uniform Resource Locator (URL) of each service platform, request method information, domain name, request header information, request body information, callback interface, etc. The scheduling server can first extract the required content from the request configuration template based on the target task and concatenate it to obtain the initial request. Then, the target cookie is added to the initial request to obtain the access request to the target service platform. For interactive tasks, the scheduling server configures the access request, which is then forwarded by the shared task processing client. This reduces the processing logic of the shared task processing client, improves the task processing efficiency of the shared task processing client, and avoids client lag. In addition, the scheduling server can also perform parsing (such as validation, field matching, and reassembly) on the stored data (such as tasks to be processed obtained from the service platform) to execute the processing logic originally located on the client, thereby further improving the task processing efficiency of the shared task processing client.

[0062] The method provided in the above embodiments of this application determines the target service platform involved in the target task and the candidate terminal devices in the terminal device cluster that have task processing permissions for the target service platform. Then, based on the load information of each candidate terminal device, a target terminal device is selected from the candidate terminal devices, thereby allocating the target task to the target terminal device. The target terminal device can process the target task through its installed shared task processing client, eliminating the need for administrators to frequently switch and log in to different service platforms, thus improving task processing efficiency. Simultaneously, since tasks are allocated based on the load information of the terminal devices, distributed scheduling of terminal devices can be achieved, avoiding the problem of uneven task distribution among different terminal devices and realizing load balancing of terminal devices.

[0063] Continue to refer to Figure 4The diagram illustrates a flowchart of an embodiment of the distributed scheduling method of this application. This distributed scheduling method can be applied to a customer service scheduling server. The customer service scheduling server can communicate with customer service terminals in a customer service terminal cluster. Each customer service terminal can have a shared customer service client installed. The shared customer service client supports interaction with various logistics service platforms and supports the processing of tasks involving various logistics service platforms. The shared customer service client can be maintained by the customer service scheduling server, such as sending data and tasks. Each customer service terminal can have task processing permissions for at least one logistics service platform. Users of each customer service terminal can process tasks involving the corresponding logistics service platform (i.e., the logistics service platform with task processing permissions) through the shared customer service client. Logistics service platforms can include, but are not limited to, work order processing platforms, message processing platforms, arbitration processing platforms, and claims processing platforms of various logistics companies.

[0064] In some optional implementations, the customer service dispatch server and the customer service terminals in the customer service terminal cluster can communicate via persistent connections and periodically transmit heartbeat signals. These persistent connections are constructed using a target protocol (such as WebSocket), which supports full-duplex communication over a single Transmission Control Protocol (TCP) connection. Based on these persistent connections, the customer service dispatch server can proactively send tasks to the customer service terminals at any time, without requiring the terminals to send requests in advance. This improves the scheduling efficiency and task issuance efficiency of the customer service dispatch server, thereby enhancing overall task processing efficiency.

[0065] The process of this distributed scheduling method may include the following steps:

[0066] Step 401: Identify the target logistics service platform involved in the target task.

[0067] In this embodiment, the execution entity of the distributed scheduling method (such as the processor of the customer service scheduling server) can first obtain the target task, and then determine the target logistics service platform involved in the target task. The customer service scheduling server may maintain a task queue, and the target task can be the task located at the head of the task queue. The target logistics service platform can be determined based on the type of the target task.

[0068] As an example, if the target task is a non-interactive task, such as a work order processing task, message processing task, address modification task, expediting task, return task after signing, or data analysis task, which is a task synchronized from a certain logistics service platform (or a task generated after parsing the task), then the source logistics service platform of the target task can be used as the target logistics service platform.

[0069] As another example, if the target task is an interactive task, such as a first synchronization task used to synchronize the pending tasks in the target logistics service platform to the customer service dispatch server, or a second synchronization task used to synchronize the processing results of the pending tasks to the target logistics service platform, then the logistics service platform to be interacted with can be used as the target logistics service platform.

[0070] Step 402: Select candidate customer service terminals with task processing permissions for the target logistics service platform from the customer service terminal cluster.

[0071] In this embodiment, the aforementioned execution entity can filter customer service terminals with task processing permissions to the target logistics service platform from the customer service terminal cluster as candidate customer service terminals. As an example, the execution entity can pre-record the task processing permission information of each customer service terminal and determine the candidate customer service terminals with task processing permissions to the target logistics service platform based on this information.

[0072] In some optional implementations, the target logistics service platform may pre-store a set of identity data (i.e., cookies). This cookie set may include cookies used by each customer service terminal to access the logistics service platform. Cookies in this set can be obtained by a target plugin installed on the customer service terminal (e.g., in a browser) and uploaded to the customer service dispatch server by the customer service terminal. When a customer logs into the logistics platform through the browser on the customer service terminal, the target plugin can obtain the cookies recorded in the browser and call the logistics service platform's interface to upload the cookies to the logistics service platform. This allows for centralized storage and management of cookies. When filtering candidate customer service terminals with task processing permissions to the target logistics service platform from the customer service terminal cluster, the customer service dispatch server can first select candidate cookies for accessing the target logistics service platform from the pre-stored cookie set, identifying the source customer service terminal of each candidate cookie as a candidate customer service terminal with task processing permissions to the target logistics service platform. Therefore, candidate customer service terminals with task processing permissions can be accurately determined based on cookies.

[0073] In some optional implementations, when any customer service terminal in the customer service terminal cluster re-logins to any logistics service platform, the customer service dispatch server can continue to receive updated cookies sent by the customer service terminal that performed the login operation, and update the cookie set based on the updated cookies, such as adding to the cookie set or updating the corresponding original cookies in the cookie set. This enables real-time cookie updates.

[0074] Step 403: Select the target customer service terminal from the candidate customer service terminals based on the load information of each candidate customer service terminal.

[0075] In this embodiment, load information can characterize the task processing pressure of the customer service terminal. It can be determined based on one or more factors such as the number of unfinished tasks, the type of unfinished tasks, processor processing power, and customer service personnel level. Load information can be obtained by the aforementioned execution entity by requesting it from each customer service terminal, or it can be statistically analyzed and updated locally in real time and read directly from the local database; no specific limitations are imposed here. The aforementioned execution entity can select the candidate customer service terminal with the lowest load as the target candidate customer service terminal.

[0076] Step 404: Send the target task to the target customer service terminal so that the target task can be processed through the shared customer service client installed on the target customer service terminal.

[0077] In this embodiment, different methods can be used to send and process target tasks for different types of target tasks. For example, if the target task is a non-interactive task, such as a work order processing task, message processing task, address modification task, expedited delivery task, returned item after signing, or data analysis task—a task synchronized from a logistics service platform (or a task generated after parsing the task)—then the relevant information of the target task (such as work order, waybill number, task type, etc.) can be organized and directly sent to the target customer service terminal. Users of the target customer service terminal can process the target task through the shared customer service client installed on the target customer service terminal and return the processing result to the aforementioned execution entity through the shared customer service client.

[0078] As another example, if the target task is an interactive task, an access request to the target logistics service platform can be configured first based on the target task. Then, this access request is sent to the target customer service terminal, which forwards the access request to the target logistics service platform via a shared customer service client, and subsequently receives the response from the target logistics service platform through the target customer service terminal. For example, if the target task is a first synchronization task used to synchronize pending tasks from the target logistics service platform to the customer service dispatch server, the access request can be a task synchronization request, and the response result can include the pending tasks from the target logistics service platform. As another example, if the target task is a second synchronization task used to synchronize the processing results of pending tasks to the target logistics service platform, the access request can be a processing result synchronization request, and the response result can include the synchronization result from the target logistics service platform (indicating whether synchronization was successful).

[0079] In some optional implementations, when configuring access requests to the target logistics service platform, the customer service dispatch server can first extract the target cookie used by the first target customer service terminal to access the target logistics service platform from the candidate cookies. Then, based on the target cookie, the target task, and a preset request configuration template, the access request to the target logistics service platform is configured. The request configuration template may include the Uniform Resource Locator (URL), request method information, domain, request header information, request body information, callback interface, etc., for each logistics service platform. The customer service dispatch server can first extract the required content from the request configuration template based on the target task and concatenate it to obtain the initial request. Then, the target cookie is added to the initial request to obtain the access request to the target logistics service platform. For interactive tasks, the access request is configured by the customer service dispatch server and forwarded by the shared customer service client. This reduces the processing logic of the shared customer service client, improves the task processing efficiency of the shared customer service client, and avoids client lag. In addition, the customer service dispatch server can also parse (such as validation, field matching, reassembly, etc.) the stored data (such as pending tasks obtained from the logistics service platform) to execute the processing logic originally located on the client, thereby further improving the task processing efficiency of the shared customer service client.

[0080] The method provided in the above embodiments of this application determines the target logistics service platform involved in the target task and the candidate customer service terminals in the customer service terminal cluster that have task processing permissions for the target logistics service platform. Then, based on the load information of each candidate customer service terminal, a target customer service terminal is selected from the candidate customer service terminals, thereby assigning the target task to the target customer service terminal. The target customer service terminal can process the target task through its installed shared customer service client, eliminating the need for administrators to frequently switch and log in to different logistics service platforms, thus improving task processing efficiency. Simultaneously, since the task is allocated based on the load information of the customer service terminal, distributed scheduling of customer service terminals can be achieved, avoiding the problem of uneven task distribution among different customer service terminals and realizing load balancing of customer service terminals.

[0081] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of this application are not limited to the described order of actions, because according to the embodiments of this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of this application.

[0082] Further reference Figure 5Based on the above embodiments, this application provides an embodiment of a distributed scheduling device, which can be specifically applied to a scheduling server. The scheduling server is communicatively connected to the terminal devices in the terminal device cluster, and each terminal device has a shared task processing client installed and has task processing permissions for at least one service platform.

[0083] like Figure 5 As shown, the distributed scheduling device 500 of this embodiment includes: a determining unit 501, used to determine the target service platform involved in the target task, and to filter candidate terminal devices with task processing permissions for the target service platform from the terminal device cluster; a selecting unit 502, used to select a target terminal device from the candidate terminal devices based on the load information of each candidate terminal device; and a sending unit 503, used to send the target task to the target terminal device so that the target task can be processed by the shared task processing client installed on the target terminal device.

[0084] In some optional implementations of this embodiment, the target task includes an interactive task; the sending unit 503 is further configured to: configure an access request to the target service platform based on the target task; and send the access request to the target terminal device so that the target terminal device forwards the access request to the target service platform through the shared task processing client.

[0085] In some optional implementations of this embodiment, the determining unit 501 is further configured to select candidate identity data for accessing the target service platform from a pre-stored identity dataset, and determine the source terminal device of each candidate identity data as a candidate terminal device with task processing permissions for the target service platform; wherein, the identity dataset includes identity data used by each terminal device to access each service platform in advance, and the identity data in the identity dataset is obtained by the target plugin installed on the terminal device and uploaded by the terminal device to the scheduling server.

[0086] In some optional implementations of this embodiment, the sending unit 503 is further configured to: extract target identity data used by the first target terminal device to access the target service platform in advance from the candidate identity data; and configure an access request to the target service platform based on the target identity data, the target task, and a preset request configuration template.

[0087] In some optional implementations of this embodiment, the above-mentioned apparatus further includes an update unit, which is used to receive updated identity data sent by the terminal device performing the login operation when any terminal device in the above-mentioned terminal device cluster re-logs into any service platform; and to update the above-mentioned identity dataset based on the updated identity data.

[0088] In some optional implementations of this embodiment, the interactive task includes at least one of the following: a first synchronization task for synchronizing the pending task in the target service platform to the scheduling server, and a second synchronization task for synchronizing the processing result of the pending task to the target service platform; the access request includes at least one of the following: a task synchronization request and a processing result synchronization request.

[0089] In some optional implementations of this embodiment, the scheduling server communicates with the terminal devices in the terminal device cluster via a long connection and periodically transmits heartbeat signals; wherein the long connection is constructed in accordance with a target protocol, which is a full-duplex communication protocol based on the transmission control protocol.

[0090] The apparatus provided in the above embodiments of this application determines the target service platform involved in the target task and the candidate terminal devices in the terminal device cluster that have task processing permissions for the target service platform. Then, based on the load information of each candidate terminal device, it selects the target terminal device from the candidate terminal devices and assigns the target task to the target terminal device. Since the target terminal device can process the target task through its installed shared task processing client, administrators do not need to frequently switch and log in to different service platforms, thus improving task processing efficiency. Simultaneously, since tasks are allocated based on the load information of the terminal devices, distributed scheduling of the terminal devices can be achieved, avoiding the problem of uneven task distribution among different terminal devices and realizing load balancing of the terminal devices.

[0091] Further reference Figure 6 Based on the above embodiments, this application provides an embodiment of a distributed scheduling device, which can be specifically applied to a customer service scheduling server. The customer service scheduling server is communicatively connected to customer service terminals in a customer service terminal cluster. Each customer service terminal has a shared customer service client installed and has task processing permissions for at least one logistics service platform.

[0092] like Figure 6As shown, the distributed scheduling device 600 of this embodiment includes: a determining unit 601, used to determine the target logistics service platform involved in the target task, and to filter candidate customer service terminals with task processing permissions for the target logistics service platform from the customer service terminal cluster; a selecting unit 602, used to select a target customer service terminal from the candidate customer service terminals based on the load information of each candidate customer service terminal; and a sending unit 603, used to send the target task to the target customer service terminal so that the target task can be processed through the shared customer service client installed on the target customer service terminal.

[0093] In some optional implementations of this embodiment, the target task includes an interactive task; the sending unit 603 is further configured to: configure an access request to the target logistics service platform based on the target task; and send the access request to the target customer service terminal so that the target customer service terminal forwards the access request to the target logistics service platform through the shared customer service client.

[0094] In some optional implementations of this embodiment, the determining unit 601 is further configured to select candidate identity data for accessing the target logistics service platform from a pre-stored identity dataset, and determine the source customer service terminal of each candidate identity data as a candidate customer service terminal with task processing permissions for the target logistics service platform; wherein, the identity dataset includes the identity data used by each customer service terminal to access each logistics service platform in advance, and the identity data in the identity dataset is obtained by the target plug-in installed on the customer service terminal and uploaded by the customer service terminal to the customer service dispatch server.

[0095] In some optional implementations of this embodiment, the sending unit 603 is further configured to: extract the target identity data used by the first target customer service terminal to access the target logistics service platform in advance from the candidate identity data; and configure the access request to the target logistics service platform based on the target identity data, the target task, and the preset request configuration template.

[0096] In some optional implementations of this embodiment, the above-mentioned apparatus further includes an update unit, which is used to receive updated identity data sent by the customer service terminal that performed the login operation when any customer service terminal in the above-mentioned customer service terminal cluster re-logs into any logistics service platform; and to update the above-mentioned identity dataset based on the updated identity data.

[0097] In some optional implementations of this embodiment, the target task includes at least one of the following: a first synchronization task for synchronizing the pending tasks in the target logistics service platform to the customer service dispatch server, and a second synchronization task for synchronizing the processing results of the pending tasks to the target logistics service platform; the access request includes at least one of the following: a task synchronization request and a processing result synchronization request.

[0098] In some optional implementations of this embodiment, the customer service dispatch server and the customer service terminals in the customer service terminal cluster communicate via a long connection and periodically transmit heartbeat signals; wherein, the long connection is constructed in accordance with a target protocol, which is a full-duplex communication protocol based on the transmission control protocol.

[0099] The apparatus provided in the above embodiments of this application determines the target logistics service platform involved in the target task, and the candidate customer service terminals in the customer service terminal cluster that have task processing permissions for the target logistics service platform. Then, based on the load information of each candidate customer service terminal, it selects the target customer service terminal from the candidate terminals, thereby assigning the target task to the target customer service terminal. Since the target customer service terminal can process the target task through its installed shared customer service client, administrators do not need to frequently switch and log in to different logistics service platforms, improving task processing efficiency. Simultaneously, since the task is allocated based on the load information of the customer service terminal, distributed scheduling of the customer service terminals can be achieved, avoiding the problem of uneven task distribution among different customer service terminals and realizing load balancing of the customer service terminals.

[0100] This application also provides a non-volatile readable storage medium storing one or more modules (programs). When these modules are applied to a device, they enable the device to execute the instructions for the method steps in this application.

[0101] This application provides one or more machine-readable media storing instructions that, when executed by one or more processors, cause an electronic device to perform one or more of the methods described in the above embodiments. In this application, the electronic device includes various types of devices such as terminal devices and servers (clusters).

[0102] The embodiments of this disclosure can be implemented as an apparatus configured as desired using any suitable hardware, firmware, software, or any combination thereof, including electronic devices such as terminal devices, servers (clusters), etc. Figure 7 An exemplary apparatus 700 is schematically shown that can be used to implement the various embodiments described in this application.

[0103] In one embodiment, Figure 7 An exemplary device 700 is shown, which includes one or more processors 702, a control module (chipset) 704 coupled to at least one of the processors 702, a memory 706 coupled to the control module 704, a non-volatile memory (NVM) / storage device 708 coupled to the control module 704, one or more input / output devices 710 coupled to the control module 704, and a network interface 712 coupled to the control module 704.

[0104] Processor 702 may include one or more single-core or multi-core processors, and processor 702 may include any combination of general-purpose processors or special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, device 700 can serve as a terminal device, server (cluster), or other device as described in the embodiments of this application.

[0105] In some embodiments, the apparatus 700 may include one or more computer-readable media (e.g., memory 706 or NVM / storage device 708) having instructions 714 and one or more processors 702 that are combined with the one or more computer-readable media and configured to execute the instructions 714 to implement the module and thus perform the actions described in this disclosure.

[0106] In one embodiment, the control module 704 may include any suitable interface controller to provide any suitable interface to at least one of the processors 702 and / or any suitable device or component communicating with the control module 704.

[0107] The control module 704 may include a memory controller module to provide an interface to the memory 706. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0108] Memory 706 may be used, for example, to load and store data and / or instructions 714 for device 700. In one embodiment, memory 706 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, memory 706 may include double data rate type 4 synchronous dynamic random access memory (DDR4 SDRAM).

[0109] In one embodiment, the control module 704 may include one or more input / output controllers to provide an interface to the NVM / storage device 708 and (one or more) input / output devices 710.

[0110] For example, NVM / storage device 708 may be used to store data and / or instructions 714. NVM / storage device 708 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable (one or more) non-volatile storage devices (e.g., one or more hard disk drives (HDDs), one or more optical disc drives (CDs), and / or one or more digital universal optical disc (DVD) drives).

[0111] NVM / storage device 708 may include storage resources that are physically part of a device on which device 700 is mounted, or that can be accessed by the device without needing to be part of the device. For example, NVM / storage device 708 may be accessed via a network via one or more input / output devices 710.

[0112] One or more input / output devices 710 may provide an interface for device 700 to communicate with any other suitable device. Input / output devices 710 may include communication components, audio components, sensor components, etc. A network interface 712 may provide an interface for device 700 to communicate via one or more networks. Device 700 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and / or protocols, such as accessing wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G, 5G, etc., or combinations thereof.

[0113] In one embodiment, at least one of the processors 702 may be logically packaged with one or more controllers (e.g., memory controller modules) of the control module 704. In one embodiment, at least one of the processors 702 may be logically packaged with one or more controllers of the control module 704 to form a system-in-package (SiP). In one embodiment, at least one of the processors 702 may be integrated with the logic of one or more controllers of the control module 704 on the same die. In one embodiment, at least one of the processors 702 may be integrated with the logic of one or more controllers of the control module 704 on the same die to form a system-on-a-chip (SoC).

[0114] In various embodiments, device 700 may be, but is not limited to, a server, desktop computing device, or mobile computing device (e.g., laptop computing device, handheld computing device, tablet computer, netbook, etc.). In various embodiments, device 700 may have more or fewer components and / or different architectures. For example, in some embodiments, device 700 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0115] The device can use a main control chip as a processor or control module, and sensor data, location information, etc. can be stored in a memory or NVM / storage device. The sensor group can be used as an input / output device, and the communication interface can include a network interface.

[0116] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0117] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0118] It should be noted that all actions involving the acquisition of signals, information, or data in this application are carried out in compliance with the relevant data protection laws and policies of the country where the application is located, and with the authorization granted by the owner of the relevant device.

[0119] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0120] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0121] These computer program instructions may also be loaded onto a computer or other programmable data processing terminal equipment to cause a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable terminal equipment, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0122] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0123] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0124] The distributed scheduling method and apparatus provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and its core ideas. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A distributed scheduling method, characterized in that, The method is applied to a scheduling server, which is communicatively connected to terminal devices in a terminal device cluster. Each terminal device has a shared task processing client installed and has task processing permissions for at least one service platform. Identify the target service platform involved in the target task, and filter candidate terminal devices with task processing permissions for the target service platform from the terminal device cluster; Based on the load information of each candidate terminal device, the target terminal device is selected from the candidate terminal devices; The target task is sent to the target terminal device so that the target task can be processed by the shared task processing client installed on the target terminal device; Wherein; the target task includes interactive tasks; the allocation of the target task to the target terminal device includes: Based on the target task, configure the access request to the target service platform; Send the access request to the target terminal device so that the target terminal device forwards the access request to the target service platform through the shared task processing client; The step of configuring access requests to the target service platform based on the target task includes: From the candidate identity data, extract the target identity data used by the target terminal device to access the target service platform in advance, wherein the candidate identity data is identity data that can be used to access the target service platform; Based on the target identity data, the target task, and the preset request configuration template, configure the access request to the target service platform.

2. The method according to claim 1, characterized in that, The step of filtering candidate terminal devices with task processing permissions for the target service platform from the terminal device cluster includes: From the pre-stored identity dataset, candidate identity data for accessing the target service platform is selected, and the source terminal device of each candidate identity data is determined as a candidate terminal device with task processing permissions to the target service platform; The identity dataset includes identity data used by each terminal device to access each service platform in advance. The identity data in the identity dataset is obtained by the target plugin installed on the terminal device and uploaded to the scheduling server by the terminal device.

3. The method according to claim 2, characterized in that, The method further includes: When any terminal device in the terminal device cluster re-logs into any service platform, it receives updated identity data sent by the terminal device that performed the login operation; The identity dataset is updated based on the updated identity data.

4. The method according to claim 1, characterized in that, The interactive tasks include at least one of the following: a first synchronization task for synchronizing pending tasks in the target service platform to the scheduling server, and a second synchronization task for synchronizing the processing results of the pending tasks to the target service platform; the access requests include at least one of the following: a task synchronization request and a processing result synchronization request.

5. The method according to any one of claims 1-4, characterized in that, The scheduling server communicates with the terminal devices in the terminal device cluster via a long connection and periodically transmits heartbeat signals; wherein the long connection is constructed in accordance with a target protocol, which is a full-duplex communication protocol based on the transmission control protocol.

6. A distributed scheduling method, characterized in that, The method, applied to a customer service dispatch server, is communicatively connected to customer service terminals in a customer service terminal cluster. Each customer service terminal has a shared customer service client installed and has task processing permissions for at least one logistics service platform. Identify the target logistics service platform involved in the target task, and filter out candidate customer service terminals with task processing permissions for the target logistics service platform from the customer service terminal cluster; Based on the load information of each candidate customer service terminal, the target customer service terminal is selected from the candidate customer service terminals. Assign the target task to the target customer service terminal so that the target task can be processed through the shared customer service client installed on the target customer service terminal; The target task includes interactive tasks; the process of assigning the target task to the target customer service terminal includes: Based on the target task, configure an access request to the target logistics service platform; Send the access request to the target customer service terminal so that the target customer service terminal forwards the access request to the target logistics service platform through the shared customer service client; The step of configuring an access request to the target logistics service platform based on the target task includes: From the candidate identity data, extract the target identity data used by the target customer service terminal to access the target logistics service platform in advance, wherein the candidate identity data is identity data that can be used to access the target logistics platform; Based on the target identity data, the target task, and the preset request configuration template, configure the access request to the target logistics service platform.

7. A distributed scheduling device, characterized in that, An apparatus for use with a scheduling server, wherein the scheduling server is communicatively connected to terminal devices in a terminal device cluster, each terminal device having a shared task processing client installed and having task processing permissions for at least one service platform, the apparatus comprising: The determining unit is used to determine the target service platform involved in the target task, and to filter candidate terminal devices with task processing permissions for the target service platform from the terminal device cluster. The selection unit is used to select the target terminal device from the candidate terminal devices based on the load information of each candidate terminal device; The sending unit is configured to send the target task to the target terminal device so that the target task can be processed by the shared task processing client installed on the target terminal device. The target task includes interactive tasks; the sending unit is further configured to: Based on the target task, configure the access request to the target service platform; Send the access request to the target terminal device so that the target terminal device forwards the access request to the target service platform through the shared task processing client; The transmitting unit is further configured to: From the candidate identity data, extract the target identity data used by the target terminal device to access the target service platform in advance, wherein the candidate identity data is identity data that can be used to access the target service platform; Based on the target identity data, the target task, and the preset request configuration template, configure the access request to the target service platform.

8. A distributed scheduling device, characterized in that, An apparatus for use in a customer service dispatch server, wherein the customer service dispatch server is communicatively connected to customer service terminals in a customer service terminal cluster, each customer service terminal is equipped with a shared customer service client and has task processing permissions for at least one logistics service platform, the apparatus comprising: The determining unit is used to determine the target logistics service platform involved in the target task, and to filter candidate customer service terminals with task processing permissions for the target logistics service platform from the customer service terminal cluster. The selection unit is used to select the target customer service terminal from the candidate customer service terminals based on the load information of each candidate customer service terminal. A sending unit is configured to assign the target task to the target customer service terminal so that the target task can be processed through the shared customer service client installed on the target customer service terminal. The target task includes interactive tasks; the sending unit is further configured to: Based on the target task, configure an access request to the target logistics service platform; Send the access request to the target customer service terminal so that the target customer service terminal forwards the access request to the target logistics service platform through the shared customer service client; The transmitting unit is further configured to: From the candidate identity data, extract the target identity data used by the target customer service terminal to access the target logistics service platform in advance, wherein the candidate identity data is identity data that can be used to access the target logistics platform; Based on the target identity data, the target task, and the preset request configuration template, configure the access request to the target logistics service platform.

Images