Service processing methods and systems

By receiving object generation requests and generating instantiated objects based on service scheduling policies, the problem that SDK providers in the prior art cannot quickly and flexibly package suppliers, and realize the reduction of operating costs and the rapid generation of SDK products that meet the needs.

CN114461358BActive Publication Date: 2024-11-15ALIBABA (CHINA) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111583509.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-22
Publication Date
2024-11-15
Estimated Expiration
2041-12-22

AI Technical Summary

Technical Problem

In the prior art, SDK providers cannot quickly and flexibly package supplier capabilities when facing massive application scenarios and the needs of different Internet institutions, resulting in high operating and maintenance costs of SDK products and the inability to quickly generate SDK products that meet specific needs.

Method used

By receiving object generation requests, determining the service provider based on object attribute information, and obtaining object generation services based on service scheduling strategies, generating instantiated objects and sending them to task processing modules, realizing the rapid generation of SDK products according to needs.

Benefits of technology

It reduces the operating costs of instantiated objects, avoids complex access and high maintenance costs under traditional customized packaging methods, and realizes the rapid generation of SDK products that meet the needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114461358B_ABST
    Figure CN114461358B_ABST
Patent Text Reader

Abstract

The embodiments of this specification provide a service processing method and system, the method comprising: receiving an object generation request sent by a task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of an instantiated object; determining a service provider based on the object attribute information, and determining a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service; obtaining the object generation service based on the service scheduling strategy; generating the instantiated object based on the object generation service, and sending the instantiated object to the task processing module. This method realizes flexible and rapid determination of an object generation service according to demand based on a service scheduling strategy, and rapidly generates an instantiated object through the object generation service, thereby avoiding the problem of increased operating and maintenance costs caused by the use of customized packaging.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present specification relate to the field of computer technology, and in particular to a service processing method. Background Art

[0002] With the continuous development of computer technology, Internet organizations need to obtain the required SDK (software development kit) products from SDK providers according to their own needs in order to save development costs during the process of computer software development, so that the goal of efficient development of computer software can be achieved through the SDK products.

[0003] In the prior art, SDK providers need to access the supplier capabilities provided by suppliers, and package the supplier capabilities according to the needs of different Internet organizations through customized packaging, thereby providing packages that meet specific needs for different Internet organizations.

[0004] However, this customized packaging method is to package the supplier capabilities one by one. In the face of many factors such as massive application scenarios, different demands of different organizations, and the stability of SDK products, the supplier capabilities cannot be packaged flexibly and quickly, resulting in a significant increase in the operation and maintenance costs of SDK products. In addition, it is further impossible to quickly generate SDK products required by Internet organizations in the future. Summary of the invention

[0005] In view of this, the present specification provides a service processing method. One or more embodiments of the present specification also relate to a service processing system, a service processing device, a computing device, a computer-readable storage medium, and a computer program to solve the technical defects existing in the prior art.

[0006] According to a first aspect of an embodiment of this specification, a service processing method is provided, including:

[0007] Receive an object generation request sent by a task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of an instantiated object;

[0008] Determine a service provider based on the object attribute information, and determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining object generation services;

[0009] Acquire the object generation service based on the service scheduling strategy;

[0010] The instantiated object is generated based on the object generation service, and the instantiated object is sent to the task processing module.

[0011] According to a second aspect of the embodiments of this specification, a service processing system is provided, including a task processing module and an object generation module, wherein:

[0012] The task processing module is configured to receive a target task, generate an object generation request based on object attribute information carried in the target task, and send the object generation request to the object generation module;

[0013] The object generation module is configured to receive an object generation request sent by the task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of the instantiated object, determine a service provider based on the object attribute information, and determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service, obtain the object generation service based on the service scheduling strategy, generate the instantiated object based on the object generation service, and send the instantiated object to the task processing module;

[0014] The task processing module is further configured to process the target task based on the received instantiated object.

[0015] According to a third aspect of an embodiment of this specification, a service processing device is provided, including:

[0016] A receiving module is configured to receive an object generation request sent by a task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of an instantiated object;

[0017] a determination module configured to determine a service provider based on the object attribute information, and to determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service;

[0018] An acquisition module, configured to acquire the object generation service based on the service scheduling strategy;

[0019] The generation module is configured to generate the instantiated object based on the object generation service and send the instantiated object to the task processing module.

[0020] According to a fourth aspect of an embodiment of this specification, a computing device is provided, including:

[0021] Memory and processor;

[0022] The memory is used to store computer executable instructions, and the processor is used to execute the computer executable instructions. When the computer executable instructions are executed by the processor, the steps of the service processing method are implemented.

[0023] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the service processing method are implemented.

[0024] According to a sixth aspect of the embodiments of this specification, a computer program is provided, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the service processing method.

[0025] The service processing method provided in this specification includes receiving an object generation request sent by a task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of an instantiated object; determining a service provider based on the object attribute information, and determining a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service; obtaining the object generation service based on the service scheduling strategy; generating the instantiated object based on the object generation service, and sending the instantiated object to the task processing module.

[0026] Specifically, the method determines the service provider based on the object attribute information carried in the object generation request, and based on the service scheduling strategy determined by the service provider, realizes flexible and rapid determination according to demand of the object generation service required to generate the instantiated object, thereby quickly generating the instantiated object through the object generation service, thereby avoiding the problem of increased operation and maintenance costs caused by the use of customized packaging; and, by sending the instantiated object to the task processing module, it is convenient for the task processing module to quickly generate the SDK product based on the instantiated object. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a structural diagram of a service processing system provided by an embodiment of this specification;

[0028] Figure 2 This is a structural diagram of a service processing system applied to an SDK product scenario provided by an embodiment of this specification;

[0029] Figure 3 is a flow chart of a service processing method provided by an embodiment of this specification;

[0030] Figure 4 It is a flowchart of determining a target service provider in a service processing method provided in an embodiment of this specification;

[0031] Figure 5A process flow chart of a service processing method provided by an embodiment of the present specification is shown;

[0032] Figure 6 It is a structural diagram of a service processing device provided by an embodiment of this specification;

[0033] Figure 7 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0034] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0035] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0036] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0037] First, the terms involved in one or more embodiments of this specification are explained.

[0038] SDK: Software Development Kit, which is generally a collection of development tools used by software engineers to build application software for specific software packages, software frameworks, hardware platforms, operating systems, etc.

[0039] Hot plugging: When developers use SDK capabilities, the SDK provider does not need to recompile and package. Instead, they can allow customers to select different vendor libraries for integration based on different needs.

[0040] Class: It is the basis for object-oriented programming (OOP) to achieve information encapsulation. A class is a user-defined reference data type, also known as a class type. Each class contains a data description and a set of functions that operate data or pass messages. An instance of a class is called an object.

[0041] Object: An object is a concrete instance of a class.

[0042] Factory class: refers to a class in Java (an object-oriented programming language) that must be created through its getInstance method.

[0043] getInstance: is a function that can be used in Java to create an instance of a class using the singleton pattern.

[0044] With the continuous development of computer technology, organizations need to obtain the required SDK (software development kit) products from SDK providers according to their own needs in order to save development costs during the process of computer software development, so that they can achieve the goal of efficient development of computer software through the SDK products.

[0045] When SDK providers (SDK manufacturers) access supplier capabilities and generate SDK products based on these supplier capabilities, they often face the access of multiple supplier capabilities, and the stability and success rate of these supplier capabilities vary; at the same time, SDK demanders may also have demands for alternative access or designated supplier access due to issues such as supplier package size, service factors, and bidding. Faced with a large number of customer scenarios, different demands from different customers, and many other factors such as product stability, this manual provides a method that uses a customized packaging solution for scenarios with multiple suppliers or designated suppliers, packaging SDK capabilities (supplier capabilities) with supplier libraries or customized dependency implementations, and providing SDK demanders with packages that meet specific needs.

[0046] However, if the SDK provider packages the capabilities of suppliers one by one for different scenarios, the operation and maintenance costs of the SDK provider will increase significantly, greatly reducing the R&D efficiency and the ROI (return on investment) of the SDK provider. At the same time, it will cause trouble for customers to access. When the SDK provider or SDK demander changes suppliers, the SDK product must be replaced. And if there is a conflict between the SDK product and other supplier libraries integrated by the customer itself, the conflict cannot be solved well.

[0047] Based on this, in this specification, a service processing method is provided. This specification also involves a service processing system, a service processing apparatus, a computing device, a computer-readable storage medium and a computer program, which are described in detail one by one in the following embodiments.

[0048] Figure 1 FIG. 1 shows a schematic diagram of a service processing system according to an embodiment of the present specification. The service processing system includes a task processing module 102 and an object generation module 104.

[0049] The task processing module is configured to receive a target task, generate an object generation request based on object attribute information carried in the target task, and send the object generation request to the object generation module;

[0050] The object generation module is configured to receive an object generation request sent by the task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of the instantiated object, determine a service provider based on the object attribute information, and determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service, obtain the object generation service based on the service scheduling strategy, generate the instantiated object based on the object generation service, and send the instantiated object to the task processing module;

[0051] The task processing module is further configured to process the target task based on the received instantiated object.

[0052] In actual applications, the service processing system can quickly support access to different customer demands under the ToB product. The ToB product can be set according to the actual application scenario, and this manual does not make specific restrictions on this; for example, the ToB product can be an SDK product; and when the service processing system is applied to the SDK product scenario, it has strong versatility in the SDK product, can achieve flexible access to the capabilities of multiple suppliers, and there is no need to customize different SDK products for different scenarios. For ease of understanding, the following description is based on the scenario of the service processing system being applied to the SDK product.

[0053] Among them, the service processing system can be understood as a system that can generate instantiated objects and process target tasks based on the instantiated objects. In practical applications, the service processing system can be applied to the scenario of SDK products. In the scenario of SDK products, the service processing system can generate objects for processing pending requests sent by the SDK demander based on the object generation module 104, and implement the SDK product that processes pending requests based on the instantiated objects through the task processing module 102. In other words, the service processing system can support the implementation of SDK products. Correspondingly, the instantiated object can be understood as an object that processes the target task, for example, an object obtained by instantiating a class. The SDK demander can be understood as an organization that develops computer software, such as an Internet organization. In practical applications, the SDK demander obtains the required SDK product from the SDK provider in order to improve development efficiency and reduce development costs, thereby realizing some functions of the computer software based on the SDK product.

[0054] The target task can be understood as a request from the SDK demander to instruct the SDK product to perform a specific operation, that is, a pending request. In actual applications, the target task will be different for different SDK products. For example, if the SDK product is a payment SDK, the target task may be a request to instruct the payment SDK to perform a transfer operation. If the SDK product is a data analysis SDK, the target task may be a request to instruct the data analysis SDK product to perform a data analysis operation.

[0055] The task processing module 102 can be understood as a module that can process the target task. In the scenario where the service processing system provided in this specification is applied to SDK products, the task processing module 102 can be the service function logic of the SDK, and it is also the capability provided by the SDK manufacturer to the outside world, that is, the capability provided by the SDK manufacturer to the SDK demander; when the SDK product is different, the capability is also different. For example, the capability can be a transfer capability, a data analysis capability, or a data search capability.

[0056] The service provider can be understood as a provider of various computer software capabilities, for example, a supplier that can provide various computer software capabilities to SDK manufacturers, such as data analysis agencies, Internet financial institutions, communication agencies, etc. Correspondingly, the object generation service can be understood as the computer software capabilities provided by the supplier to the SDK manufacturer; due to the differences in the suppliers, the capabilities provided by the supplier are also different. For example, if the supplier is a data analysis agency, the computer software capabilities provided by the supplier may be data analysis capabilities; if the supplier is an Internet financial institution, the computer software capabilities provided by the supplier may be transfer capabilities; in actual applications, the computer software capabilities provided by the supplier are also called atomic capabilities, and the computer software capabilities are implemented based on the classes created by the supplier.

[0057] The object generation module 104 can be understood as a module in the service processing system that generates instantiated objects based on the object generation service. When the object generation service is a computer software capability provided by the supplier, and the computer software capability is implemented by a class, the object generation module 104 can be a module that instantiates the class that implements the computer software capability to obtain an object. Based on this, the object obtained by instantiating the class can implement the computer software capability provided by the supplier, so that the request of the SDK demander can be processed based on the computer software capability.

[0058] In actual applications, there are multiple suppliers connected to the SDK provider, and the capabilities provided by the suppliers may be the same or different; therefore, when the object generation module 104 obtains the atomic capabilities provided by the supplier and generates an object based on the atomic capabilities, how to determine which supplier's atomic capabilities need to be obtained can be determined through the service scheduling strategy. In other words, the service scheduling strategy can be understood as a strategy for determining a specific supplier from multiple suppliers connected to the SDK provider, so as to facilitate the subsequent generation of instantiated objects based on the atomic capabilities of the specific supplier. Alternatively, the service scheduling strategy can be understood as a strategy for determining a specific supplier from multiple suppliers connected to the SDK provider, and obtaining the atomic capabilities of the specific supplier, so as to facilitate the subsequent generation of instantiated objects based on the atomic capabilities of the specific supplier. It should be noted that the way in which the service scheduling strategy determines a specific supplier from multiple suppliers can be set according to the actual application scenario, and this specification does not make specific restrictions on this.

[0059] At the same time, the object generation module 104 can also make an abstract design for the supplier capabilities used by the task processing module 102, and abstract one or more supplier capabilities of the same type into an interface. Therefore, the object generation module 104 will not have a specific implementation, but only provide an interface. For example, the supplier A provides a "SMS acquisition capability A", and the supplier B provides a "SMS acquisition capability B". The "SMS acquisition capability A" and "SMS acquisition capability B" are the same type of capabilities. Based on this, the object generation module 104 can abstract the "SMS acquisition capability A" and "SMS acquisition capability B" into a SMS acquisition interface. In actual applications, before accessing the supplier capabilities, the object generation module 104 needs to make an abstract design for the capabilities provided by the supplier, abstract the core interface, and obtain an abstract interface; for the upper-level task processing module 102, it does not need to care about which supplier's capabilities are accessed, and only needs to process the target task based on the object sent by the object generation module 104. After accessing the supplier capabilities, each supplier creates an independent module when accessing, and relies on the abstract interface of the object generation module 104, creates an access implementation class in the module, and the implementation class needs to implement the abstract interface to provide the access capability. And the implementation class needs to register itself with the factory class of the object generation module 104.

[0060] The object attribute information can be set according to the actual application scenario, and this specification does not make any specific limitations on this. For example, the object attribute information can be the identifier of the supplier specified by the SDK demander for generating the instantiated object, the network type of the SDK demander, the specified parameters of the SDK demander, or the service type of the instantiated object required by the SDK demander. The service type can be the type of computer software capability that the instantiated object can implement. For example, the service type can be data analysis, data search, one-click login, etc. In actual applications, many SDK demanders can directly specify the generation of instantiated objects through the capabilities of a specific supplier by sending a request to the SDK product, so as to implement specific operations through the instantiated object. For example, SDK demander A sends a "one-click login" processing request to the SDK product, and carries the identifier of communication supplier A and the identifier of data acquisition supplier B in the processing request. After receiving the processing request, the SDK product can obtain the communication capability provided by communication supplier A and the data acquisition capability provided by data acquisition supplier B based on the identifier of communication supplier A and the identifier of data acquisition supplier B carried in the processing request; and generate an instantiated object that can implement the "one-click login" function based on the communication capability and data acquisition capability. Alternatively, SDK demander B sends a processing request for "data analysis" to the SDK product, wherein the processing request only carries the service type of the instantiated object required by SDK demander B, which may be data analysis; based on this, after receiving the processing request, the SDK product can determine the supplier who can generate the instantiated object that realizes the data analysis capability based on the service type carried in the processing request, which may be supplier C and supplier D; obtain the capabilities provided by supplier C and the capabilities provided by supplier D, and generate an instantiated object that can realize the "data analysis" function based on the capabilities of both. Based on this, the object generation request can be understood as a task that instructs the object generation module 104 to generate an instantiated object.

[0061] Specifically, the task processing module 102 in the service processing system can receive a target task carrying object attribute information, and then the task processing module 102 generates an object generation request based on the object attribute information that can instruct the object generation module 104 to generate an instantiated object, and sends the object generation request to the object generation module 104.

[0062] The object generation module 104 in the service processing system can receive the object generation request sent by the task processing module 102, and determine the service provider based on the object attribute information carried in the object generation request, wherein the object attribute information is one or more attributes corresponding to the instantiated object. After determining the service provider, a service scheduling strategy can be determined based on the service provider, and the service scheduling strategy is a strategy for obtaining the object generation service. After that, the object generation module 104 can obtain the object generation service based on the scheduling strategy, and generate an instantiated object that can process the target task based on the object generation service, and send the instantiated object to the task processing module 102.

[0063] The task processing module 102 can receive the instantiated object sent by the object generation module 104 and process the target task based on the instantiated object.

[0064] The following takes the application of the service processing system in the SDK product scenario as an example to further explain the service processing system. Among them, the target task can be a processing request sent by the SDK demander; the service provider is a supplier that provides capabilities to the SDK manufacturer; the object generation service is the capability provided by the supplier, which is implemented through a class, and the instantiated object is an object obtained by instantiating the class.

[0065] Based on this, the task processing module 102 of the service processing system can receive a processing request sent by the SDK demander, which can be a request for "data analysis", and generate an object generation request instructing the object generation module 104 to generate an object based on the supplier identifier carried in the processing request, and send the object generation request to the object generation module 104, where the supplier identifier is 3.

[0066] After receiving the object generation request, the object generation module 104 determines the three suppliers (supplier A, supplier B, supplier C) corresponding to the supplier identifier based on the three supplier identifiers carried in the object generation request, wherein the capabilities of the three suppliers are all different; then determines the service scheduling strategy based on the three suppliers. When the capabilities of the three suppliers are all different, the service scheduling strategy can be to directly determine the three suppliers as suppliers for generating objects, and obtain the atomic capabilities provided by the three suppliers. That is, obtain the class provided by the three suppliers that can implement the atomic capabilities. After obtaining the class, the object generation module 104 instantiates the class to obtain an object that can process the processing request sent by the SDK demander, and sends the generated object to the task processing module 102.

[0067] In actual applications, if the capabilities of the three suppliers are the same, for example, supplier A and supplier B have the same capabilities, in this case, a supplier with lower latency can be selected from supplier A and supplier B with the same capabilities through the service scheduling strategy, and the supplier with lower latency can be supplier A; and obtain the atomic capabilities provided by supplier A and supplier C. Alternatively, the service scheduling strategy can obtain the atomic capabilities of supplier A and supplier B in turn.

[0068] For example, if the capabilities of supplier A, supplier B, and supplier C are the same, a supplier with reduced latency can be selected from suppliers A, supplier B, and supplier C with the same capabilities through the service scheduling strategy, and the latency reduction can be supplier A; and the atomic capability provided by supplier A is obtained. Alternatively, the service scheduling strategy can obtain the atomic capabilities of supplier A, supplier B, and supplier C in turn.

[0069] The task processing module 102 can receive an object sent by the object generation module 104 that can process the processing request, and processes the processing request based on the object, thereby realizing the "data analysis" capability required by the SDK demander.

[0070] The service processing system provided in an embodiment of the present specification sends an object generation request generated based on the object attribute information carried in the target task to the object generation module 104 through the task processing module 102, and determines the service provider according to the object attribute information in the object generation request through the object generation module 104, and flexibly determines the object generation service based on the service scheduling strategy determined by the service provider, so as to quickly generate instantiated objects through the object generation service, thereby reducing the operating cost of the instantiated objects, and by sending the instantiated objects to the task processing module 102, the task processing module 102 quickly provides SDK products to SDK demanders based on the instantiated objects, thereby avoiding the problem of low efficiency in providing SDK products.

[0071] In addition, since the SDK product obtained through customized packaging makes it more complicated for the SDK demander to access the SDK product, when the supplier fails or changes, the SDK demander needs to access the SDK product regenerated by the SDK provider again, resulting in a waste of time and labor costs. Therefore, the service processing system obtains the instantiation object by instantiating the class, quickly provides the SDK demander with the required SDK product, avoiding the problem of a more complicated access method, and can quickly and flexibly regenerate the instantiation object when the supplier fails or changes, thereby avoiding a large waste of time and labor costs.

[0072] Furthermore, the service processing system provided in this specification also includes:

[0073] The service storage module is configured to receive the object generation service provided by the service provider.

[0074] Among them, the service storage module can be understood as a module that stores the capabilities provided by the supplier. In actual applications, the service storage module is only the access implementation of the capabilities of each supplier. The access implementation of each supplier needs to implement an abstract interface with the object generation module 104, so as to provide corresponding capabilities for the object generation module 104, so that the subsequent object generation module 104 can quickly obtain the capabilities provided by the supplier, and in this process, the supplier needs to register itself with the object generation module 104.

[0075] In actual applications, each supplier in the service storage module creates an independent module when accessing, and relies on the abstract interface of the object generation module 104 to create an access implementation class in the module; and the implementation class needs to implement the abstract interface of the object generation module 104 to provide access capabilities. And the implementation class needs to register itself with the factory class of the abstract layer.

[0076] Based on this, the object generation module 104 in the service processing system is further configured to obtain the object generation service from the service storage module based on the service scheduling strategy.

[0077] Specifically, the service storage module included in the service processing method can receive the object generation service provided by the service provider and store the object generation service; correspondingly, when the object generation module 104 needs to generate an instantiated object, it can obtain the required object generation service from the service storage module based on the service scheduling strategy, thereby facilitating the subsequent rapid generation of instantiated objects based on the object generation service.

[0078] In actual applications, in order to ensure the security of the transfer operation performed by the instantiated object, the SDK demander and the service provider will agree on a key in advance. The key consists of two parts, which are saved separately by the SDK demander and the service provider. In this way, the security of the transfer operation is guaranteed by the key during the transfer operation. However, in the service processing system provided in the present specification, the object generation service provided by the service provider can be generated into an instantiated object by the object generation module 104, and the instantiated object is sent to the task processing module 102, so that the task processing module 102 can process the target task sent by the SDK demander based on the capabilities provided by the service provider; and in this process, there is no interaction between the service provider and the object generation service, or the interaction between the service provider and the object generation service is relatively complex. Therefore, when the task processing module 102 needs to obtain the key stored by the service provider, it will be impossible to obtain it, or it will be difficult to obtain it. Based on this, the service processing system provided in the present specification includes a data storage module, which is used to store the key stored by the service provider, and a connection is established between the data storage module and the task processing module 102, so that when the task processing module 102 needs to obtain the key stored by the service provider, it can obtain it in a timely and fast manner, avoiding the problem of being unable to obtain the key or obtaining the key with difficulty. The specific implementation method is as follows.

[0079] The service processing system provided in this manual also includes:

[0080] The data storage module is configured to store the first key of the service provider.

[0081] The data storage module may be understood as a module for storing the first key of the storage service provider.

[0082] In actual applications, the service processing system saves the first key of the service provider through the data storage module, so that the subsequent task processing module 102 can quickly obtain the first key.

[0083] Based on this, in the service processing system provided in this specification, the task processing module 102 is further configured as follows:

[0084] Determine the object generation service corresponding to the instantiated object, and obtain a provider identifier of the service provider corresponding to the object generation service;

[0085] Acquire the first key corresponding to the provider identifier from the data storage module, and determine the second key carried in the target task;

[0086] In a case where the first key matches the second key, the target task is processed based on the instantiated object.

[0087] Among them, the first key can be understood as the key saved by the service provider, and correspondingly, the second key can be understood as the key saved by the SDK demander.

[0088] Using the above example, the supplier identifier may be a supplier ID. Based on this, when the supplier is connected to the SDK manufacturer, it is necessary to send the first key stored by itself to the data storage module, which is connected to the task processing module 102.

[0089] When the task processing module 102 determines that the supplier's first key is required for initialization, it determines the class corresponding to the object, that is, determines the class that obtains the object through instantiation; then determines which supplier provides the class and obtains the supplier ID of the supplier; and obtains the first key corresponding to the supplier ID from the data storage module; after determining the first key, the first key is matched with the second key carried in the "transfer" processing request sent by the SDK demander, and if the matching result is consistent, the transfer operation is performed based on the object. This ensures the security of the transfer operation and avoids losses to the SDK demander and the supplier.

[0090] The following combination Figure 2 , taking the application of the service processing system provided in this specification in the scenario of the transfer SDK product as an example, the service processing system is further explained. Figure 2 A structural diagram of a service processing system applied to an SDK product scenario provided by an embodiment of the present specification is shown, wherein the system architecture of the service processing system includes four modules, namely, an SDK service layer, a supplier capability abstraction layer, a supplier capability access implementation layer and an SDK storage layer. The SDK service layer can be understood as the task processing module in the above embodiment; the supplier capability abstraction layer can be understood as the object generation module in the above embodiment; the supplier capability access implementation layer can be understood as the service storage module in the above embodiment; and the SDK storage layer can be understood as the data storage module in the above embodiment.

[0091] Among them, the SDK service layer can be the service function logic of the SDK product, and it is also the capability provided by the SDK manufacturer to the developer APP (computer software of the SDK demander). In specific implementation, when the developer APP needs to call the "data analysis" capability of the SDK product, it can send a "data analysis" processing request to the SDK service layer, and the processing request can also be understood as a call request. The SDK service layer can instruct the supplier capability abstraction layer to generate a task to implement an object of the "data analysis" capability based on the "data analysis" processing request sent by the developer APP and based on the parameters carried in the request (which can be the supplier identifier, network type or user-specified parameters).

[0092] Moreover, after receiving the object capable of realizing the "data analysis" capability returned by the supplier capability abstraction layer based on the task, the "data analysis" capability required by the developer's APP can be realized based on the object.

[0093] In another case, when the developer APP needs to call some higher-security capabilities to perform specific operations, such as the "transfer" capability, in order to ensure the security of the transfer operation, the developer APP can agree on a key with the supplier, and the key is saved by the developer APP and the supplier respectively. In order for the SDK service layer to quickly obtain the saved key, the supplier can store the key in the SDK storage layer. If the supplier SDK (capabilities provided by the supplier) requires parameters such as keys for initialization, the SDK service layer can obtain the corresponding key parameters from the server according to the corresponding supplier identifier for initialization, thereby ensuring the security of the operation.

[0094] Among them, the supplier capability abstraction layer can exist as an independent module. The supplier capability abstraction layer can abstract the supplier capabilities used by the SDK service layer to generate an abstract interface. In addition, the supplier capability abstraction layer also has an important capability of loading supplier instances, that is, instantiating the class provided by the supplier through a factory class to obtain an object.

[0095] In actual applications, the supplier capability abstraction layer selects the corresponding supplier ID based on the network type, user-specified parameters or supplier ID parameters carried in the task sent by the SDK service layer, and after obtaining the supplier ID through the factory class, matches it from its own registration list through the scheduling strategy, which can be understood as the service scheduling strategy in the above embodiment. When a suitable supplier instance is matched, the supplier instance is dynamically loaded and instantiated by utilizing the reflection loading of the factory class, thereby obtaining an object that can realize the capabilities required by the developer's APP, and returning the object to the SDK service layer for use.

[0096] In addition, before accessing supplier capabilities, the supplier capability abstraction layer needs to make an abstract design of the supplier capabilities and abstract the core interface. For the upper-level SDK service layer, it does not need to care which supplier is connected underneath. It only needs to implement the capabilities required by the developer's APP based on the objects sent by the supplier capability abstraction layer.

[0097] Among them, the supplier capability access implementation layer is only the access implementation of each supplier's capabilities. Each supplier's implementation needs to implement the abstract layer interface, provide corresponding capabilities, and register itself with the abstract layer.

[0098] In actual applications, each supplier creates an independent module when accessing, and relies on the interface of the above supplier capability abstract layer. In this module, an access implementation class is created, and the implementation class needs to implement the abstract interface to provide access capabilities for the supplier. Among them, the implementation class needs to register itself with the factory class of the abstract layer. Subsequently, the factory class matches the appropriate supplier instance from the implementation class registered in the registration list.

[0099] In addition, by creating independent modules when suppliers are connected, if new suppliers want to be connected in the future, new supplier modules can be directly added. Neither the SDK service layer nor the supplier capability abstraction layer needs to be adjusted. If the SDK demander wants to dynamically select different suppliers, they only need to connect to the different supplier modules.

[0100] The service processing system provided in the embodiments of this specification changes the traditional method of directly packaging or directly relying on supplier capabilities with SDK. Through the modular separation architecture design and the dynamic loading of the factory class of the supplier capability abstract layer, the obtained supplier instance is instantiated, and the generated object after instantiation is returned to the SDK service layer for use, thereby achieving complete decoupling of the SDK service layer and supplier capabilities. In this way, the dynamic hot plugging of supplier capabilities can be realized, and the SDK demander can also freely choose the supplier it needs.

[0101] In addition, different rule matching strategies (dynamic loading strategies) are adopted when using supplier instances, and the reflection loading of the factory class is used to dynamically load the supplier instance, so that when selecting different supplier instances, the factory can adopt different loading strategies to meet different scenario requirements and achieve the best effect. At the same time, through different scheduling strategies (dynamic loading strategies) of the factory class, faults can be automatically isolated and the calling scheme can be optimized to further meet different scenario requirements.

[0102] Figure 3 A flow chart of a service processing method provided according to an embodiment of the present specification is shown, which specifically includes the following steps.

[0103] Step 302: Receive an object generation request sent by a task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of an instantiated object.

[0104] The service processing method provided in this specification can be applied to the object generation module in the service processing system. Based on this, the object generation request sent by the receiving task processing module can be understood as the object generation module being able to receive the object generation request sent by the task processing module.

[0105] In actual applications, the step of receiving the object generation request sent by the task processing module can refer to the step in the above service processing system where the object generation module receives the object generation request sent by the task processing module, and this specification will not go into details here.

[0106] Step 304: Determine a service provider based on the object attribute information, and determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for acquiring object generation services.

[0107] Specifically, the object generation module can determine the service provider corresponding to the object data information based on the object attribute information carried in the object generation request, and determine the service scheduling strategy based on the service provider.

[0108] Further, determining a service scheduling strategy based on the service provider includes:

[0109] Determining an object generation service provided by the service provider, and determining a service type of the object generation service;

[0110] In a case where the service types of the object generation services are the same, a service scheduling strategy is determined based on the service types.

[0111] In which, when the object generation service is a supplier capability, the service type can be understood as the type of the supplier capability, for example, data analysis type, data search type, etc.

[0112] Continuing with the above example, after determining three suppliers (supplier A, supplier B, and supplier C), the object generation module can determine the supplier capabilities (atomic capabilities) provided by the three suppliers and determine the types of the supplier capabilities. The capability type of supplier A can be data analysis, the capability type of supplier B can be data deduplication, and the capability type of supplier C can be data deduplication. When the types are the same, that is, the capability types of supplier B and supplier C are the same, a service scheduling strategy can be determined, and the data analysis capability of supplier A can be obtained through the service scheduling strategy, and it can be determined to obtain data deduplication capability from supplier B or supplier C.

[0113] In addition, when the capabilities of the three suppliers are different, a service scheduling strategy is determined based on the three suppliers. Subsequently, when the capabilities of the three suppliers are different, the service scheduling strategy can be used to obtain the capabilities provided by the three suppliers respectively.

[0114] In the service processing method provided in this specification, the object generation service provided by the service provider is determined, and the service type of the object generation service is determined; when the service types of the object generation services are the same, a service scheduling strategy is determined based on the service type, so as to facilitate the subsequent acquisition of the object generation service through the service scheduling strategy.

[0115] In the service processing method provided in this specification, in order to meet the requirements of different scenarios and optimize the service scheduling effect, different loading strategies can be supported. Moreover, after determining the service scheduling strategy based on the service type, the service scheduling strategy can also be determined based on the scheduling strategy identifier. The specific implementation method is as follows.

[0116] The determining of the service scheduling strategy based on the service provider includes:

[0117] Determine a scheduling policy identifier corresponding to the service provider, and determine a service scheduling policy based on the scheduling policy identifier.

[0118] Among them, the scheduling policy identifier can be understood as an identifier that uniquely identifies a service scheduling policy. In actual applications, the object generation module can pre-configure the corresponding scheduling policy identifier for each service provider during the process of generating instantiated objects, so that when the service scheduling policy is determined by the service scheduler, the service scheduling policy can be directly determined based on the scheduling policy identifier corresponding to each service scheduler, thereby facilitating the subsequent acquisition of object generation services based on the service scheduling policy.

[0119] Step 306: Obtain object generation service based on the service scheduling strategy.

[0120] In actual application, the object generation module can obtain the object generation service based on the service scheduling strategy, and its specific implementation method includes steps 1 and 2:

[0121] Step 1: Determine the target service provider based on the service scheduling strategy.

[0122] The target service provider is determined from the service providers. The target service provider can be understood as a service provider corresponding to an object generation service that can generate an instantiated object.

[0123] In one case, the service scheduling strategy may be to determine suppliers with the same capabilities when there are suppliers with the same capability types, and select a supplier with the highest service quality as the target supplier based on the service quality parameters of the suppliers. The specific implementation method is as follows.

[0124] The determining the target service provider based on the service scheduling strategy includes:

[0125] A service quality parameter of the service provider is determined based on the service scheduling policy, and a target service provider is determined based on the service quality parameter.

[0126] The service quality parameter may be understood as a parameter characterizing the service quality of the service provider. For example, the service quality parameter may be understood as a parameter such as delay, failure probability, and request time consumption.

[0127] Continuing with the above example, the service quality parameter can be understood as the request time. Based on this, when the capability types of suppliers are the same, the suppliers with the same capability are determined based on the service scheduling strategy, and based on the request time of the supplier, the supplier with the smallest request time is selected from the suppliers with the same capability type as the target supplier. The target supplier can be the supplier corresponding to the class that can generate an implementation object by instantiation, and the object is the object of the capability required by the SDK demander.

[0128] In the embodiments of this specification, the service quality parameters of the service provider are determined based on the service scheduling strategy, and the target service provision is determined based on the service quality parameters, so that different loading strategies (scheduling strategies) can be flexibly adopted when selecting different supplier instances to meet different scenario requirements and achieve the best effect. In addition, it is convenient to generate an object that realizes the capabilities required by the SDK demander based on the capabilities (supplier instance) provided by the target supplier.

[0129] Furthermore, in the process of selecting a supplier with the shortest request time from suppliers with the same capability type, the method of determining the supplier with the shortest request time is as follows.

[0130] The determining of the target service provider based on the service quality parameter comprises:

[0131] sorting the service providers in descending order based on the service quality parameter;

[0132] The first service provider after sorting is determined as the target service provider.

[0133] Using the above example, we obtain the request time of each supplier among multiple suppliers with the same capability type, and sort the multiple suppliers in descending order based on the request time. The first supplier after sorting is the supplier with the smallest request time, and the first supplier after sorting is determined as the target supplier. This facilitates the subsequent generation of objects that realize the capabilities required by the SDK demander based on the capabilities provided by the target supplier.

[0134] In another case, the service scheduling strategy may be to determine suppliers with the same capability when the capability types of suppliers are the same, and select one supplier from the suppliers in turn as the target supplier. The specific implementation method is as follows.

[0135] The service processing method provided in this specification includes at least two service providers;

[0136] Accordingly, determining the target service provider based on the service scheduling strategy includes:

[0137] determining each of the service providers;

[0138] Each of the service providers is taken as a target service provider in turn based on the service scheduling strategy.

[0139] Continuing with the above example, each service provider can be supplier A, supplier B and supplier C. When the capabilities of supplier A, supplier B and supplier C are the same, the service scheduling strategy can select one of the three suppliers as the target supplier in turn. Specifically, the service scheduling strategy selects supplier A as the target supplier when it needs to select one of the three suppliers as the target supplier for the first time; selects supplier B as the target supplier for the second time; selects supplier C as the target supplier for the third time; and selects supplier A as the target supplier again for the fourth time. The above operations are performed in sequence, thereby realizing selecting one of the three suppliers as the target supplier in turn.

[0140] In the embodiment of this specification, each service provider among the service providers is determined; each service provider is sequentially selected as the target service provider based on the service scheduling strategy, so that different loading strategies (scheduling strategies) can be flexibly adopted when selecting different supplier instances to meet different scenario requirements and achieve the best effect. In addition, it is convenient to generate an object that realizes the capabilities required by the SDK demander based on the capabilities (supplier instance) provided by the target supplier.

[0141] In the embodiments of the present specification, after the target service provider is determined, if the target service provider fails and cannot provide the object generation service, the service scheduling strategy can also re-determine a target service provider from other service providers of the same service type, thereby ensuring the stability of generating instantiated objects; the specific implementation method is as follows.

[0142] After determining the target service provider based on the service scheduling strategy, the method further includes:

[0143] Acquiring the operating status data of the target service provider;

[0144] In the case where it is determined that the operating status data is abnormal operating status data, determining the target service provider as an abnormal service provider;

[0145] Determining the service type of the abnormal service provider, and determining service providers with the same service type among the service providers as candidate service providers;

[0146] A target service provider is determined from the candidate service providers based on the service scheduling policy.

[0147] Among them, the operating status data can be understood as data that identifies the operating status of the service provider, and the operating status data can be normal operating status data and abnormal operating status data, wherein the normal operating status data can indicate that the service provider is operating normally; the abnormal operating status data can indicate that the operation of the service provider is abnormal, and the abnormality includes but is not limited to failure, request timeout, connection interruption, etc.

[0148] Using the above example, see Figure 4 , Figure 4 is a flow chart of determining a target service provider in a service processing method provided in one embodiment of this specification; see Figure 4, the abstract layer in the SDK product, when the supplier instance generated by the supplier with capability type A is requested based on the factory class, suppliers A1 and A2 can be two different suppliers that provide the same capability A. In this case, if the SDK demander is connected to A1 and A2, the scheduling strategy is selected based on suppliers A1 and A2, and A1 is selected first based on the scheduling strategy, and it is judged whether A1 complies with the scheduling strategy, that is, it is judged whether there is no failure when using A1. If it is, the supplier instance based on A1 is returned; if it is not, it means that there is a failure when using A1, then the factory class will mark the Class that implements the capability provided by A1 and switch to the A2 instance. In this way, automatic scheduling of faults can be achieved. At the same time, it is also necessary to judge whether A2 complies with the scheduling strategy, that is, it is judged whether there is no failure when using A2. If it is, the supplier instance based on A2 is returned; if it is not, it means that there is a failure when using A2, then the factory class will mark the Class that implements the capability provided by A2 and return empty.

[0149] Based on this, more scheduling strategies can be extended to the factory class, such as alternating scheduling of A1 and A2, or counting the request time of A1 and A2 to select the instance with better performance (because the same supplier may have slightly different performance for different user groups or regions).

[0150] Step 2: Obtain the object generation service provided by the target service provider based on the service call interface.

[0151] The service call interface is determined by processing the object generation service of the same service type. When the service processing method is applied to the object generation module in the service processing system, the service call interface can be understood as an abstract interface of the object generation module, which is an interface obtained by the object generation module through abstract design of the capabilities provided by the supplier. Based on this, after determining the target service provider, the capabilities provided by the target service provider can be obtained based on the abstract interface.

[0152] Continuing with the above example, after determining the target provider, the object generation module determines the provider instance that matches the identifier of the target provider from its own registration list based on the factory class, and dynamically loads the provider instance using reflective loading of the factory class.

[0153] Step 308: Generate an instantiated object based on the object generation service, and send the instantiated object to the task processing module

[0154] Specifically, after obtaining the object generation service, the object generation module can instantiate the object generation service to obtain an instantiated object, and send the instantiated object to the task processing module.

[0155] Furthermore, the object generation module can be implemented through a factory class during the process of instantiating the object generation service. The specific implementation is as follows.

[0156] The generating an instantiated object based on the object generating service comprises:

[0157] The object generation service is instantiated based on the object generation unit to obtain an instantiated object.

[0158] Among them, the object generation unit can be understood as a factory class.

[0159] Continuing with the above example, the object generation service can be understood as a supplier instance, that is, a class that implements supplier capabilities; based on this, after obtaining the supplier instance, the object generation module instantiates the supplier instance and returns the object obtained after instantiating the supplier instance to the SDK service layer for use.

[0160] The service processing method provided in this specification determines the service provider based on the object attribute information carried in the object generation request, and flexibly determines the object generation service based on the service scheduling strategy determined by the service provider, so as to quickly generate instantiated objects through the object generation service, thereby reducing the operating costs of the instantiated objects, and by sending the instantiated objects to the task processing module, it is convenient for the subsequent task processing module to quickly provide SDK products based on the instantiated objects, thereby avoiding the problem of low efficiency in SDK product provision.

[0161] The above is a schematic scheme of a service processing method of this embodiment. It should be noted that the technical scheme of the service processing method and the technical scheme of the above service processing system belong to the same concept. For details not described in detail in the technical scheme of the service processing method, please refer to the description of the technical scheme of the above service processing system. Correspondingly, for details not described in detail in the technical scheme of the service processing system, please refer to the description of the technical scheme of the service processing method.

[0162] The following combination Figure 5 , taking the application of the service processing method provided in this specification in the scenario of SDK products as an example, the service processing method is further explained. Figure 5 A processing flow chart of a service processing method provided by an embodiment of the present specification is shown. The service processing method is applied to the supplier capability abstraction layer of the service processing system and specifically includes the following steps.

[0163] Step 502: The supplier capability abstraction layer receives the object generation request sent by the SDK service layer.

[0164] Step 504: The provider capability abstraction layer determines a scheduling strategy.

[0165] Step 506: The supplier capability abstraction layer obtains the supplier instance from the supplier capability access layer through the scheduling strategy based on the factory class.

[0166] Step 508: The supplier capability abstraction layer instantiates the supplier instance based on the factory class, and sends the instantiated object to the SDK service layer.

[0167] In the specific implementation process, the supplier capability abstraction layer determines the corresponding supplier ID based on the network type, user-specified parameters or supplier ID parameters carried in the task sent by the SDK service layer; and matches from its own registration list through the factory class through the scheduling strategy, which can be understood as the service scheduling strategy in the above embodiment. When a suitable supplier instance is matched, the supplier instance is dynamically loaded and instantiated by utilizing the reflection loading of the factory class, thereby obtaining an object that can realize the capabilities required by the developer's APP, and the object is returned to the SDK service layer for use.

[0168] The service processing system provided in the embodiments of this specification changes the traditional method of directly packaging or directly relying on supplier capabilities with SDK. Through the modular separation architecture design and the dynamic loading of the factory class of the supplier capability abstract layer, the obtained supplier instance is instantiated, and the generated object after instantiation is returned to the SDK service layer for use, thereby achieving complete decoupling of the SDK service layer and supplier capabilities. In this way, the dynamic hot plugging of supplier capabilities can be realized, and the SDK demander can also freely choose the supplier it needs.

[0169] In addition, different rule matching strategies (dynamic loading strategies) are adopted when using supplier instances, and the reflection loading of the factory class is used to dynamically load the supplier instance, so that when selecting different supplier instances, the factory can adopt different loading strategies to meet different scenario requirements and achieve the best effect. At the same time, through different scheduling strategies (dynamic loading strategies) of the factory class, faults can be automatically isolated and the calling scheme can be optimized to further meet different scenario requirements.

[0170] Corresponding to the above method embodiment, this specification also provides a service processing device embodiment. Figure 6 FIG. 1 is a schematic diagram showing the structure of a service processing device provided by an embodiment of the present specification. Figure 6 As shown, the device comprises:

[0171] The receiving module 602 is configured to receive an object generation request sent by the task processing module, wherein the object generation request carries object attribute information, and the object attribute information is one or more attributes of the instantiated object;

[0172] The determination module 604 is configured to determine a service provider based on the object attribute information, and determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service;

[0173] An acquisition module 606 is configured to acquire the object generation service based on the service scheduling strategy;

[0174] The generation module 608 is configured to generate the instantiated object based on the object generation service and send the instantiated object to the task processing module.

[0175] Optionally, the determining module 604 is further configured to:

[0176] Determining an object generation service provided by the service provider, and determining a service type of the object generation service;

[0177] In a case where the service types of the object generation services are the same, a service scheduling strategy is determined based on the service types.

[0178] Optionally, the determining module 604 is further configured to:

[0179] Determine a scheduling policy identifier corresponding to the service provider, and determine a service scheduling policy based on the scheduling policy identifier.

[0180] Optionally, the acquisition module 606 is further configured to:

[0181] Determining a target service provider based on the service scheduling strategy, wherein the target service provider is determined from the service providers;

[0182] The object generation service provided by the target service provider is acquired based on a service calling interface, wherein the service calling interface is determined by processing the object generation services with the same service type.

[0183] Optionally, the acquisition module 606 is further configured to:

[0184] A service quality parameter of the service provider is determined based on the service scheduling policy, and a target service provider is determined based on the service quality parameter.

[0185] Optionally, the acquisition module 606 is further configured to:

[0186] sorting the service providers in descending order based on the service quality parameter;

[0187] The first service provider after sorting is determined as the target service provider.

[0188] Optionally, there are at least two service providers;

[0189] Accordingly, the acquisition module 606 is further configured to:

[0190] determining each of the service providers;

[0191] Each of the service providers is taken as a target service provider in turn based on the service scheduling strategy.

[0192] Optionally, the acquisition module 606 is further configured to:

[0193] Acquiring the operating status data of the target service provider;

[0194] In the case where it is determined that the operating status data is abnormal operating status data, determining the target service provider as an abnormal service provider;

[0195] Determining the service type of the abnormal service provider, and determining service providers with the same service type among the service providers as candidate service providers;

[0196] A target service provider is determined from the candidate service providers based on the service scheduling policy.

[0197] Optionally, the generating module 608 is further configured to:

[0198] The object generation service is instantiated based on the object generation unit to obtain an instantiated object.

[0199] The present specification provides a service processing device, which determines the service provider based on the object attribute information carried in the object generation request, and flexibly determines the object generation service based on the service scheduling strategy determined by the service provider, so as to quickly generate instantiated objects through the object generation service, thereby reducing the operating cost of the instantiated objects, and by sending the instantiated objects to the task processing module, it is convenient for the subsequent task processing module to quickly provide SDK products based on the instantiated objects, thereby avoiding the problem of low efficiency in SDK product provision.

[0200] The above is a schematic scheme of a service processing device of this embodiment. It should be noted that the technical scheme of the service processing device and the technical scheme of the above service processing method belong to the same concept, and the details not described in detail in the technical scheme of the service processing device can be referred to the description of the technical scheme of the above service processing method.

[0201] Figure 7 The block diagram of a computing device 700 according to an embodiment of the present specification is shown. The components of the computing device 700 include but are not limited to a memory 710 and a processor 720. The processor 720 is connected to the memory 710 via a bus 730, and the database 750 is used to store data.

[0202] The computing device 700 also includes an access device 740 that enables the computing device 700 to communicate via one or more networks 760. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 740 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0203] In one embodiment of the present specification, the above components of the computing device 700 and Figure 7 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 7 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0204] The computing device 700 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. The computing device 700 may also be a mobile or stationary server.

[0205] The processor 720 is used to execute the following computer executable instructions, which, when executed by the processor 720, implement the steps of the above-mentioned service processing method.

[0206] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the above service processing method belong to the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the above service processing method.

[0207] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which can implement the steps of the above-mentioned service processing method when executed by a processor.

[0208] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the above service processing method belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the above service processing method.

[0209] An embodiment of the present specification further provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned service processing method.

[0210] The above is an illustrative solution of a computer program of this embodiment. It should be noted that the technical solution of the computer program and the technical solution of the above service processing method belong to the same concept, and the details not described in detail in the technical solution of the computer program can be referred to the description of the technical solution of the above service processing method.

[0211] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0212] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0213] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0214] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0215] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. A service processing method, comprising: Receive an object generation request sent by a task processing module, wherein the object generation request carries object attribute information, the object attribute information is one or more attributes of an instantiated object, and the object attribute information at least includes an identifier of a service provider specified by an SDK demander for generating the instantiated object; Determine a service provider based on the object attribute information, and determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining object generation services; Acquire the object generation service based on the service scheduling strategy; The instantiated object is generated based on the object generation service, and the instantiated object is sent to the task processing module, wherein the instantiated object is used to provide SDK products for the SDK demander.

2. The service processing method according to claim 1, wherein determining a service scheduling strategy based on the service provider comprises: Determining an object generation service provided by the service provider, and determining a service type of the object generation service; In a case where the service types of the object generation services are the same, a service scheduling strategy is determined based on the service types.

3. The service processing method according to claim 1, wherein determining a service scheduling strategy based on the service provider comprises: Determine a scheduling policy identifier corresponding to the service provider, and determine a service scheduling policy based on the scheduling policy identifier.

4. According to any one of claims 1 to 3, the acquiring of the object generation service based on the service scheduling strategy comprises: Determining a target service provider based on the service scheduling strategy, wherein the target service provider is determined from the service providers; The object generation service provided by the target service provider is acquired based on a service call interface, wherein the service call interface is determined by processing object generation services with the same service type.

5. The service processing method according to claim 4, wherein determining the target service provider based on the service scheduling strategy comprises: A service quality parameter of the service provider is determined based on the service scheduling policy, and a target service provider is determined based on the service quality parameter.

6. The service processing method according to claim 5, wherein determining the target service provider based on the service quality parameter comprises: sorting the service providers in descending order based on the service quality parameter; The first service provider after sorting is determined as the target service provider.

7. The service processing method according to claim 4, wherein the number of service providers is at least two; Accordingly, determining the target service provider based on the service scheduling strategy includes: determining each of the service providers; Each of the service providers is taken as a target service provider in turn based on the service scheduling strategy.

8. The service processing method according to claim 4, after determining the target service provider based on the service scheduling strategy, further comprising: Acquiring the operating status data of the target service provider; In the case where it is determined that the operating status data is abnormal operating status data, determining the target service provider as an abnormal service provider; Determining the service type of the abnormal service provider, and determining service providers with the same service type among the service providers as candidate service providers; A target service provider is determined from the candidate service providers based on the service scheduling policy.

9. A service processing system, comprising a task processing module and an object generation module, wherein: The task processing module is configured to receive a target task, generate an object generation request based on object attribute information carried in the target task, and send the object generation request to the object generation module, wherein the object attribute information at least includes an identifier of a service provider specified by the SDK demander for generating an instantiated object; The object generation module is configured to receive an object generation request sent by the task processing module, wherein the object generation request carries object attribute information, the object attribute information is one or more attributes of the instantiated object, a service provider is determined based on the object attribute information, and a service scheduling strategy is determined based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service, the object generation service is obtained based on the service scheduling strategy, the instantiated object is generated based on the object generation service, and the instantiated object is sent to the task processing module, wherein the instantiated object is used to provide SDK products for the SDK demander; The task processing module is further configured to process the target task based on the received instantiated object.

10. The service processing system according to claim 9, further comprising: The service storage module is configured to receive the object generation service provided by the service provider.

11. According to the service processing system of claim 10, the object generation module is further configured to obtain the object generation service from the service storage module based on the service scheduling strategy.

12. A service processing device, comprising: A receiving module is configured to receive an object generation request sent by a task processing module, wherein the object generation request carries object attribute information, the object attribute information is one or more attributes of an instantiated object, and the object attribute information at least includes an identifier of a service provider specified by an SDK demander for generating the instantiated object; a determination module configured to determine a service provider based on the object attribute information, and to determine a service scheduling strategy based on the service provider, wherein the service scheduling strategy is a strategy for obtaining an object generation service; An acquisition module, configured to acquire the object generation service based on the service scheduling strategy; The generation module is configured to generate the instantiated object based on the object generation service and send the instantiated object to the task processing module, wherein the instantiated object is used to provide SDK products for the SDK demander.

13. A computing device comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the service processing method described in any one of claims 1 to 8 are implemented.

14. A computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the service processing method according to any one of claims 1 to 8.