CN115002229B

CN115002229B - Edge cloud network system, scheduling method, equipment, system and storage medium

Info

Publication number: CN115002229B
Application number: CN202210646468.2A
Authority: CN
Inventors: 付哲; 王广芳; 许文郁; 杜凯
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2022-06-08
Filing date: 2022-06-08
Publication date: 2024-09-13
Anticipated expiration: 2042-06-08
Also published as: CN115002229A

Abstract

The embodiment of the application provides an edge cloud network system, a scheduling method, equipment, a system and a storage medium. In the embodiment of the application, a scheduling end is additionally arranged in a data processing service scheduling system, and the scheduling end can schedule a target data processing service provider for providing data processing service for the access request according to attribute information and the access request of a plurality of data processing service providers. Furthermore, a driving layer called by a data processing service interface is additionally arranged at the dispatching end, so that the access request of the data processing service can be converted into a target access format supported by a target data processing service provider, the formats of different data processing service providers are adapted, and unified call of different data processing service providers is realized. The user does not need to grasp the interface parameter form and the calling mode of each data processing service provider, and the convenience of service calling of different data service providers can be improved.

Description

Edge cloud network system, scheduling method, equipment, system and storage medium

Technical Field

The present application relates to the field of cloud services, and in particular, to an edge cloud network system, a scheduling method, a scheduling device, a scheduling system, and a storage medium.

Background

With the increasing maturity of artificial intelligence and machine learning technologies, the data processing capabilities of more and more general scenarios have evolved into mature products such as Optical Character Recognition (OCR), natural Language Processing (NLP), text-to-speech (TTS) services, and so forth. The data processing service provider typically provides out-of-box data processing service capabilities in the form of APIs, and the user invokes the relevant data processing service in accordance with interface parameters defined by the data processing service provider.

However, the interface parameters, call forms and return values of different data processing service providers are defined differently. Therefore, even if the data processing services are oriented to the same scene, the calling modes of the data processing service interfaces of different data processing service providers are different, and great inconvenience is brought to the user for calling the data processing services.

Disclosure of Invention

Aspects of the present application provide an edge cloud network system, a scheduling method, a device, a system, and a storage medium, which are used to provide a unified data processing service scheduling manner, so as to improve convenience of service call of different data service providers.

The embodiment of the application also provides an edge cloud network system, which comprises: the system comprises a client, a scheduling node and a plurality of edge nodes; the plurality of edge nodes are used for providing data processing services; the access formats of the data services provided by the plurality of edge nodes are different;

the client is used for providing an access request for the data processing service to the scheduling node;

The scheduling node is used for acquiring attribute information of data processing services provided by a plurality of edge clouds; selecting a target edge cloud from the plurality of edge clouds according to the access request and the attribute information; converting the access request into a target access format supported by the target edge cloud to obtain an access request in the target access format; and invoking a data processing service of the target edge cloud by using the access request in the target format.

The embodiment of the application provides a scheduling method, which comprises the following steps:

Acquiring an access request of a data processing service;

Acquiring attribute information of data processing services provided by a plurality of data processing service providers;

Selecting a target data processing service provider from the plurality of data service providers according to the access request and the attribute information;

Converting the access request into a target access format supported by the target data processing service provider to obtain an access request in the target access format;

and calling the data processing service of the target data processing service provider by using the access request in the target access format.

The embodiment of the application also provides a scheduling system, which comprises: the system comprises a client, a scheduling end and a plurality of data processing service providers; the scheduling end comprises: the device comprises a scheduling component, a monitoring component and a driving component;

The scheduling component is used for acquiring an access request for the data processing service provided by the client;

the monitoring component is used for acquiring attribute information of data processing services provided by a plurality of data service providers;

The scheduling component is further configured to select a target data processing service provider from the plurality of data service providers according to the access request and the attribute information;

The driving component is used for converting the access request into a target access format supported by the target data processing service provider so as to obtain an access request in the target access format; and invoking a data processing service of the target data processing service provider with the access request in the target format.

The embodiment of the application also provides a computing device, which comprises: a memory, a processor, and a communication component; wherein the memory is used for storing a computer program;

The processor is coupled to the memory and the communication component for executing the computer program for performing the steps in the data processing service scheduling method described above.

Embodiments of the present application also provide a computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the steps in the data processing service scheduling method described above.

In the embodiment of the application, a scheduling end is additionally arranged in a data processing service scheduling system, and the scheduling end can schedule a target data processing service provider for providing data processing service for the access request according to attribute information and the access request of a plurality of data processing service providers. Furthermore, a driving layer (i.e. a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that the access request of the data processing service can be converted into a target access format supported by a target data processing service provider, the formats of different data processing service providers are adapted, and the unified call of different data processing service providers is realized. The user does not need to grasp the interface parameter form and the calling mode of each data processing service provider, and the convenience of service calling of different data service providers can be improved.

On the other hand, according to the attribute information of the plurality of data processing service providers and the access request, the target data processing service provider providing the data processing service for the access request is scheduled, so that the dynamic call of the data processing service provider is realized, and the data processing service call is not dependent on a single data processing service provider. In this way, even if the data processing service provided by a certain data processing service provider is abnormal, the access request can be scheduled to other data processing service providers, which is helpful for improving the robustness of the data processing service and reducing the influence on the application of the user side.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

Fig. 1 and fig. 2 are schematic structural diagrams of a scheduling system according to an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating a scheduling process of a scheduling system for scheduling data processing services according to an embodiment of the present application;

fig. 4a is a schematic structural diagram of an edge cloud network system according to an embodiment of the present application;

Fig. 4b is a schematic flow chart of a scheduling method according to an embodiment of the present application;

Fig. 5 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The data processing service refers to a service providing various data processing methods. The data includes: character data, image data, video data, audio data, and the like, but is not limited thereto. The data processing services provided by the data processing service provider may be implemented as a software as a service (SaaS) modality product. The data processing service includes: artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) services and other data processing services, such as data storage services, data query services, and data add-drop-change services, among others. AI services refer to data processing services that are involved in the field of artificial intelligence. For example, optical Character Recognition (OCR), natural Language Processing (NLP), text-to-speech (TTS), object recognition, and so forth.

The data processing service provider typically provides out-of-box data processing service capabilities in the form of APIs, and the user invokes the relevant data processing service in accordance with interface parameters defined by the data processing service provider. For example, the user may initiate an HTTP call to a specified interface of the data processing service provider and receive an HTTP return as a data processing result according to interface parameters defined by the data processing service provider, and a pre-applied access key ID (AK) and a secret access key (SK).

However, the interface parameters, call forms, and return values of different data processing service providers are often not exactly defined. Taking the widely used OCR service as an example, some request parameters required by the data processing service provider a are picture URLs, denoted by an "image" field; meanwhile, configuration parameters such as 'minimum height of characters in a picture', 'probability of outputting a character frame', 'whether to close character line direction prediction', and the like are required to be transmitted in json mode. The return value is json array, and each part in the json array contains 'text content', 'text region probability', 'region coordinates', and the like. While another data processing service provider, which also provides OCR services, has an interface comprising: picture address URL, indicated by the "ImageUrl" field; identifying a language type, represented by a "LanguageType" field; whether to turn on PDF recognition is indicated by the "IsPdf" field. And the return values include text line content, confidence, text line coordinates, text line rotation corrected coordinates, language type, and the like. It can be seen that even for data processing services oriented to the same scene, the service interface calling modes of different data processing service providers are different.

On the other hand, more and more applications and services are built based on data processing service interfaces of third party data processing service providers, which puts strong demands on the use costs and availability of the data processing service interfaces. If the service interface of a single data processing service provider fails, the user's own application can have a significant impact without a backup interface. Meanwhile, the payment modes, time delays and the like of interfaces of different data processing service providers are different. If a suitable data processing service provider is flexibly selected for different areas, different sizes of user requests, a better trade-off will be made between cost of use, user experience and service availability.

In order to solve the above technical problems, in some embodiments of the present application, a scheduling end is added to a data processing service scheduling system, where the scheduling end may schedule, for an access request of a data processing service, a target data processing service provider that provides the data processing service for the access request according to attribute information and the access request of a plurality of data processing service providers. Furthermore, a driving layer (i.e. a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that the access request of the data processing service can be converted into a target access format supported by a target data processing service provider, the formats of different data processing service providers are adapted, and the unified call of different data processing service providers is realized. The user does not need to grasp the interface parameter form and the calling mode of each data processing service provider, and the convenience of service calling of different data service providers can be improved.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

It should be noted that: like reference numerals denote like objects in the following figures and embodiments, and thus once an object is defined in one figure or embodiment, further discussion thereof is not necessary in the subsequent figures and embodiments.

Fig. 1 is a schematic structural diagram of a scheduling system according to an embodiment of the present application. As shown in fig. 1, the system mainly includes: a client 10, a scheduler 20 and a plurality of data processing service providers 30. The plural means 2 or more than 2.

In this embodiment, the client 10 is a computer device used by a user and having functions of computing, surfing the internet, and communicating, etc., and may be, for example, a mobile phone, a tablet computer, a personal computer, and a wearable device.

The data processing service provider 30 refers to a service provider that provides data processing services to users. The data processing service provider 30 may deploy data processing services through a server device to provide SaaS-like services to users. The server device may be a single server device, a cloud server array, or a Virtual Machine (VM) running in the cloud server array. In addition, the server device may also refer to other computing devices having corresponding service capabilities, for example, a terminal device (running a service program) such as a computer, and the like.

In the embodiment of the present application, the data processing service provided by the data processing service provider 30 may be deployed in a service end device of a central cloud, or may be deployed in an edge cloud of an edge cloud network. An edge cloud may be a machine room, a data center (DATA CENTER, DC), or an internet data center (INTERNET DATA CENTER, IDC), etc. For an edge cloud network, each edge cloud may include a series of edge infrastructures including, but not limited to: distributed Data Center (DC), wireless room or cluster, operator's communication network, core network devices, base stations, edge gateways, home gateways, computing devices or storage devices, and corresponding network environments, etc. The location, capabilities, and inclusion of infrastructure of the different edge nodes may or may not be the same as described herein.

In the embodiment of the present application, at least 2 definitions of interface parameters and/or scheduling forms of the data processing service interfaces provided by the data processing service providers 30 are different among the plurality of data processing service providers 30. In the embodiment of the present application, in order to implement unified scheduling for multiple data processing service providers 30 scheduled by different interfaces, a scheduling end 20 is added. The scheduler 20 is a computing device that may schedule a plurality of data processing service providers 30 in response to an access request of the client 10 to the data processing service provided by the data processing service providers 30. The scheduler 20 may be 1 or more server devices. For the implementation manner of the server device, reference may be made to the above related content, which is not described herein.

In this embodiment, the client 10 and the dispatcher 20 may be connected wirelessly or by a wire. Alternatively, the client 10 may be communicatively connected to the scheduler 20 through a mobile network, and accordingly, the network system of the mobile network may be any one of 2G (GSM), 2.5G (GPRS), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS), 4G (LTE), 4g+ (lte+), 5G, wiMax, etc. Alternatively, the client 10 may also be communicatively connected to the dispatcher 20 by bluetooth, wiFi, infrared, or the like.

Of course, the scheduling end 20 and the data processing service provider 30 may also be in communication connection, and the communication connection manner may be referred to the communication connection manner between the client 10 and the scheduling end 20, which is not described herein.

In an embodiment of the present application, the scheduler 20 may provide a data processing service provider scheduling service. Specifically, as shown in fig. 1, the scheduling end 20 may include: a scheduling component 201, a driving component 202 and a monitoring component 203. The scheduling component 201, the driving component 202 and the monitoring component 203 may be logic functional modules, which may be deployed on the same physical machine or on different physical machines.

In the embodiment of the present application, referring to fig. 1 to fig. 3, when a user needs to call a data processing service to perform data processing, an access request for the data processing service may be sent to the scheduling end 20 through the client 10 (corresponding to step 7 in fig. 3). The access request may carry access request parameters. Wherein the access request parameters may include: the type of data processing service to be accessed, the data to be processed, etc. Wherein the types of data processing services are different, and the forms of data to be processed are also different. For example, the data to be processed may be character data, image data, video data, audio data, and the like, but is not limited thereto. The data to be processed may be the data itself or the identifier of the data to be processed. For example, the data to be processed is image data. Accordingly, the data to be processed may be the image itself, or may be a uniform resource locator (Uniform Resource Locator, URL) of the image, or the like.

For the scheduling end 20, an access request for a data processing service sent by the client 10 can be obtained; and performs data processing service scheduling on the access request. Specifically, as shown in fig. 1 and 2, the scheduler 20 may acquire attribute information of the data processing services provided by the plurality of data processing service providers 30. The attribute information of the data processing service provided by the data processing service provider 30 refers to information for evaluating the merits of the data processing service provided by the data processing service provider 30, including but not limited to: value attribute information, performance attribute information, access times quota of data processing service, access times of target user providing access request to data processing service provided by data processing service provider 30, and resource package information corresponding to data processing service, etc. of data processing service provided by data processing service provider 30. For the edge cloud network, the plurality of data processing service providers 30 provide attribute information of the data processing service, which may be represented as attribute information of the data processing service provided by a plurality of edge nodes corresponding to the plurality of data processing service providers 30.

Wherein the value attribute information of the data processing service provided by the data processing service provider 30 may be embodied as a charging standard or the like of the data processing service provided by the data processing service provider 30. The performance attribute information of the data processing service provided by the data processing service provider 30 refers to information reflecting performance advantages of the data processing service provided by the data processing service provider 30, including but not limited to: the availability of the data processing service provided by the data processing service provider 30 to the interface service, access latency, etc., but is not limited thereto.

The access times quota of the data processing service is used for: the maximum number of accesses to the data processing service provided by the data processing service provider 30 that the user can access in a set period is limited, or the maximum number of accesses to the data processing service provided by the data processing service provider 30 that the user can access in total is limited. For example, the quota of access times for the data processing service may be "1000 times/day", i.e. the maximum number of access times for the data processing service provided by the data processing service provider 30 within 1 day of the user may be 1000 times. As another example, the quota of access times for the data processing service may be "10000 times", i.e. the maximum number of access times a user can access the data processing service provided by the data processing service provider 30 in total is 10000 times.

The resource package information corresponding to the data processing service is a type of the data processing service provided by the data processing service provider 30. For example, the type of data processing service is used to reflect the functionality of the data processing service. For example, in some embodiments, the type of data processing service is OCR, TTS, or speech recognition, among others.

In the embodiment of the present application, the specific implementation of acquiring attribute information of the data processing service provided by the plurality of data processing service providers 30 is not limited. In some embodiments, as shown in fig. 2 and 3, a user may register configuration information of the data processing service provider 30 with the scheduler 20 (corresponding to steps 1 and 2 of fig. 3). The user-registered data processing service provider 30 is typically a data processing service provider subscribed or rented for the user. The user may register configuration information of the data processing service provider 30 in the form of templates set by the scheduler 20.

The configuration information of the data processing service provider 30 may include, among others: identification of the data processing service provider 30 (e.g., name, number, or other identifier, etc.), user name and access key information of the user at the data processing service provider 30, and resource package information and access times quota of the data processing service provider that the user applies for, subscribes to, or rents, etc. Wherein the access key information includes: an access key identification (ACCESS KEY ID, AK ID), a secret access key (SECRET ACCESS KEY, SK), and the like.

Accordingly, the registrar 204 of the scheduler 20 may obtain configuration information of the data processing service provider 30 provided by the user; and stores configuration information of the data processing service provider 30. Alternatively, in connection with fig. 2 and 3, the registrar 204 may store configuration information of the user-provided data processing service provider 30 in the database 206 (corresponding to step 3 of fig. 3). Further, the monitoring component 203 may monitor the data processing service provider 30 according to configuration information of the data processing service provider 30 registered by the user to obtain attribute information of the data processing service provider 30 (corresponding to steps 4 and 5 of fig. 3). Configuration information for a plurality of data processing service providers 30 may be read from database 206 for monitoring component 203. In an embodiment of the present application, a plurality of data processing service providers 30 may be registered data processing service providers for the target user providing the access request. Of course, the plurality of data processing service providers 30 may also include: a data processing service provider that provides for registration of a target user of an access request and data processing service providers registered by other users.

Further, the monitoring component 203 may obtain, from the configuration information of the data processing service provider 30, a user name and access key information providing the configuration information; and monitors the plurality of data processing providers using the user name and access key information to obtain attribute information of the data processing service provider 30 (corresponding to step 5 of fig. 3). In the embodiment of the present application, the user name and access key information refer to user name and access key information of a user who registers configuration information of the data processing service provider 30.

For an edge cloud network, the monitoring component 203 may obtain attribute information of a plurality of edge nodes provided by users providing data processing services as attribute information of a plurality of data processing service providers 30. Specifically, the monitoring component 203 may monitor the plurality of edge nodes using the user name and access key information to obtain attribute information for the plurality of edge nodes to provide data processing services.

In an embodiment of the present application, the monitoring process performed by the monitoring component 203 on the plurality of data processing providers 30 may occur before or after the access request is received. In some embodiments, the monitoring component 203 may periodically monitor the plurality of data processing service providers 30 to obtain attribute information of the plurality of data processing service providers 30 according to a set monitoring period. Further, as shown in fig. 2 and 3, the monitoring component 203 may store the acquired attribute information of the plurality of data processing service providers 30 in the database 206 (corresponding to step 6 of fig. 3).

Since the attribute information of the data processing service provider 30 may reflect the merits of the data processing service provided by the data processing service provider 30, in this embodiment, for the scheduling component 201, a target data processing service provider may be selected from the plurality of data service providers 30 according to the access request and the attribute information of the plurality of data processing service providers 30 providing the data processing service.

For the scheduling component 201, attribute information for a plurality of data processing service providers 30 providing data processing services may be read from the database 206 (corresponding to step 8 of fig. 3). It is noted that in some embodiments, multiple data processing service providers 30 participating in the scheduling of data processing service providers for an access request provided by a client 10 may be registered for the target user providing the access request. In other embodiments, the plurality of data processing service providers 30 participating in the scheduling of data processing service providers by the access requests provided by the client 10 may comprise: a data processing service provider that provides a target user registration of the access request, and data processing service providers that other users register.

Accordingly, for the scheduling component 201, when scheduling data processing service providers for access requests provided by the client 10, the attribute information of the data processing service provider registered by the target user providing the access request may be read from the database 206 as the attribute information of the data processing service provider 30 participating in the scheduling of the access requests provided by the client 10.

In other embodiments, the scheduling component 201 may provide scheduling query information to the client 10 prior to scheduling a data processing service provider for an access request provided by the client 10. The scheduling query information is used to provide the target user with a choice of whether to agree to invoke the data processing service provider for which other users are registered. Accordingly, if the target user agrees to invoke the data processing service provider registered by the other user, the corresponding confirmation operation may be triggered. The attribute information of a plurality of data processing service providers registered by the target user and other users who provide the access request may be read from the database as attribute information of the data processing service provider 30 participating in the scheduling of the access request provided for the client 10 in response to the confirmation operation for the scheduling query information. Accordingly, if the target user does not agree to invoke the data processing service provider registered by the other user, a corresponding negative operation may be triggered. The attribute information of a plurality of data processing service providers registered by the target user providing the access request may be read from the database as attribute information of the data processing service provider 30 participating in the scheduling of the access request provided for the client 10 in response to a negative operation with respect to the scheduling query information for the scheduling component 201.

After acquiring the attribute information of the plurality of data processing service providers 30 participating in the scheduling of the access request provided for the client 10, the scheduling component 201 may select a target data processing service provider from the plurality of data service providers 30 according to the access request and the attribute information of the plurality of data processing service providers 30 providing the data processing service (corresponding to step 9 of fig. 3).

Specifically, the scheduling component 201 may obtain, from the access request, a target data processing type corresponding to the access request; and acquiring target attribute information of the plurality of data processing service providers 30 for the target data processing type from the attribute information of the plurality of data service providers 30; further, a target data processing service provider may be selected from the plurality of data processing service providers 30 according to target attribute information of the plurality of data processing service providers 30 for a target data processing type.

Specifically, for any one of the data processing service providers P _i, the value attribute information and the performance attribute information of the data processing service provider P _i may be acquired from the target attribute information of the data processing service provider P _i; further, the value attribute information and the performance attribute information for the data processing service provider P _i are weighted to obtain the service evaluation parameters of the data processing service provider P _i.

Optionally, before weighting the value attribute information and the performance attribute information for the data processing service provider P _i, the number n _i of accesses of the target user providing the access request to the target data processing type of the data processing service provider P _i may also be obtained from the attribute information of the data processing service provider P _i; it is determined whether the number of accesses n _i is smaller than the number of times quota q _i of the target data processing type that the target user can access the data processing service provider P _i. Further, if the determination result is yes, the value attribute information and the performance attribute information of the data processing service provider P _i may be weighted, so as to obtain the service evaluation parameter of the data processing service provider P _i.

Accordingly, if the number of accesses n _i is greater than or equal to the number of times quota q _i of the target data processing type of the target user accessible to the data processing service provider P _i, which indicates that the data processing service provider P _i has no margin available for the target user to call, the service evaluation parameter of the data processing service provider P _i may be determined to be 0.

The above calculation process can be expressed as the following formula (1):

In formula (1), i denotes an i-th data processing service provider, i=1, 2, …, n. n represents the total number of data processing service providers. S _i denotes a service evaluation parameter of the i-th data processing service provider P _i. c (i), a (i), and l (i) represent value attribute information (such as a single call charge), service availability, and service access delay, respectively, of the ith data processing service provider P _i. Lambda _c、λ_a and lambda _l represent the weights of the value attribute information (such as single call cost), service availability, and service access delay of the i-th data processing service provider P _i, respectively.

After obtaining the service evaluation parameters of the plurality of data processing service providers, a target data processing service provider may be selected from the plurality of data processing service providers based on the service evaluation parameters of the plurality of data processing service providers. For example, a data processing service provider having the largest service evaluation parameter may be selected from a plurality of data processing service providers as the target data processing service provider. For another example, a data processing service provider whose service evaluation parameter is greater than or equal to a set service evaluation parameter threshold value may be selected from a plurality of data processing service providers as the target data processing service provider, and so on.

According to the data processing service scheduling process, the target data processing service provider with high performance in the access request can be selected according to the attribute information of the data processing service provider, so that dynamic scheduling of the data processing service provider is realized, and the data processing service provider with high performance in the access request can be selected for a user.

After determining the target data processing service provider, the driver component 202 can convert the access request into a target access format supported by the target data processing service provider to obtain an access request in the target access format. Specifically, the driving component 202 may obtain a target access format supported by the target data processing service provider from a correspondence between the set data processing service provider and the access format; and converting the access request into a target access format supported by the target data processing service provider to obtain the access request in the target access format. The correspondence between the set data processing service provider and the access format may be set in the driving component 202 or in the database 206.

The correspondence between the data processing service provider and the access format may be obtained by a developer of the dispatch terminal 20 according to a technical document provided by the data processing service provider, and set in the driving component 202 or the database 206.

Further, the driver component 202 can schedule data processing services of the target data processing service provider with access requests in the target access format (corresponding to step 10 of fig. 3). Because the access request in the target access format is in the form of a data processing service interface that is adapted by the target data processing provider, the driver component 202 can schedule the data processing services of the target data processing service provider. In the embodiment of the application, the interfaces of different data processing service providers in the same scene can be loaded into the call framework in the form of plug-ins through interface driving adaptation.

For the target data processing service provider, the access request can be processed by the data processing service to obtain a data processing result. Specifically, the data processing service provided by the target data processing service provider may obtain the data to be processed according to the access request. In some embodiments, the data processing service provided by the target data processing service provider may parse the pending data from the access request. In other embodiments, the data processing service provided by the target data processing service provider may parse the identification of the data to be processed from the access request; and acquiring the data to be processed according to the identification of the data to be processed. For example, the data to be processed is an image, the identifier of the data to be processed is a URL of the image, and the data processing service provided by the target data processing service provider may acquire the image as the data to be processed according to the URL of the image, and so on. Further, the data processing service provided by the target data processing service provider can process the data to be processed by using the set data processing logic so as to obtain a data processing result.

Further, the target data processing service provider may return the data processing results to the driving component 202 (corresponding to step 11 of fig. 3). Since the data processing result is provided by the target data processing service provider and meets the data format requirement of the target data processing service provider, the driving component 202 may further perform data format conversion on the data processing result to obtain the set data format (corresponding to step 12 in fig. 3). Wherein the set data format is the data transmission format of the components between the scheduling ends 20. Further, the driving component 202 may send the data processing result with the set data format to the client 10, so that the client 10 outputs the data processing result (corresponding to step 13 of fig. 3).

The data processing service scheduling system provided by the embodiment of the application can be realized as central cloud scheduling and also can be realized as edge cloud network scheduling. Correspondingly, the embodiment of the application also provides an edge cloud network system. The following describes an exemplary description of an edge cloud network system provided by the embodiment of the present application.

Fig. 4a is a schematic structural diagram of an edge cloud network according to an embodiment of the present application. As shown in fig. 4a, the edge cloud network includes: a client 41, a scheduling node 42 and a plurality of edge nodes 43. The plural means 2 or more than 2. For a description of the embodiments of the client 41 and the edge node 43, reference may be made to the relevant content in the above embodiment of the scheduling system, which is not described here again. For the description of the scheduling node 42, reference may be made to the content related to the scheduling end 20 in the above-mentioned scheduling system embodiment, which is not described herein.

In an embodiment of the present application, a plurality of edge nodes 43 are used to provide data processing services; the access formats in which the plurality of edge nodes 43 provide data services are different. The different access formats of the data services provided by the plurality of edge nodes 43 means that the access formats of the data processing services provided by the plurality of edge nodes 43 are different, for example, the definition of interface parameters and/or scheduling forms of the interfaces are different. The plurality of edge nodes 43 may belong to the same data processing service provider or may belong to different data processing service providers.

In the embodiment of the present application, when a user needs to call a data processing service to perform data processing, an access request for the data processing service may be sent to the scheduling node 42 through the client 41. For the description of the access request, reference may be made to the relevant content of the above embodiment of the scheduling system, which is not described herein.

In the embodiment of the present application, in order to implement unified scheduling of data processing services provided by a plurality of edge nodes 43 scheduled by different interfaces, an access request for the data processing services sent by a client 41 may be acquired for a scheduling node 42; and performs data processing service scheduling on the access request. Specifically, the scheduling node 42 may acquire attribute information of the plurality of edge nodes 43 providing the data processing service. For description of the attribute information of the data processing service provided by the edge node 43, reference may be made to the above-mentioned related content of the attribute information of the data processing service provided by the data processing service provider 30, which is not described herein.

In the embodiment of the present application, the specific implementation of acquiring attribute information of the plurality of edge nodes 43 providing the data processing service is not limited. In some embodiments, a user may register configuration information of edge node 43 with scheduling node 42. The user registered edge node 43 is typically the edge node of a data processing service provider to which the user subscribes or rents. The user may register configuration information for edge node 43 in the form of templates set by scheduling node 42. For a description of the configuration information of the edge node 43, reference may be made to the relevant content of the configuration information of the data processing service provider 30 described above, and this is not repeated here.

Accordingly, the scheduling node 42 may obtain configuration information of the edge node 43 provided by the user; and stores configuration information of the edge node 43. Optionally, the configuration information of the edge node 43 provided by the user may be stored in a database (. Further, the scheduling node 42 may monitor the edge node 43 according to the configuration information of the edge node 43 registered by the user to obtain attribute information of the edge node 43 providing the data processing service. In an embodiment of the present application, the plurality of edge nodes 43 may be edge nodes of a data processing service provider registered for the target user providing the access request. Of course, the plurality of edge nodes 43 may also include: an edge node of a data processing service provider that provides a target user registration of an access request and other user registered data processing service providers.

Further, the scheduling node 42 may obtain, from the configuration information of the edge node 43, a user name and access key information providing the configuration information; and monitors the plurality of edge nodes 43 using the user name and access key information to obtain attribute information of the data processing services provided by the edge nodes 43. In the embodiment of the present application, the user name and access key information refer to user name and access key information of a user who registers configuration information of a data processing service provider.

In the embodiment of the present application, the process of monitoring the plurality of edge nodes 43 by the scheduling node 42 may occur before or after receiving the access request. In some embodiments, the scheduling node 42 may periodically monitor the plurality of edge nodes 43 according to a set monitoring period to obtain attribute information of the plurality of edge nodes 43. Further, the scheduling node 42 may store the acquired attribute information of the plurality of edge nodes 43 in the database 2.

Since the attribute information of the edge node 43 may reflect the merits of the data processing services provided by the edge node 43, in the present embodiment, for the scheduling node 42, a target edge node may be selected from the plurality of edge nodes 43 according to the access request and the attribute information of the data processing services provided by the plurality of edge nodes 43.

For the scheduling node 42, attribute information for providing data processing services by a plurality of edge nodes 43 may be read from a database. It is noted that in some embodiments, the plurality of edge nodes 43 participating in the scheduling of data processing service providers by the access request provided by the client 41 may be edge nodes of data processing service providers registered for the target user providing the access request. In other embodiments, the edge nodes of multiple data processing service providers that participate in the scheduling of data processing service providers by access requests provided by clients 41 may include: an edge node of a data processing service provider that provides a target user registration of the access request, and an edge node of a data processing service provider that other users register.

Accordingly, for the scheduling node 42, when scheduling the data processing service provider for the access request provided by the client 41, the attribute information of the edge node of the data processing service provider registered by the target user providing the access request may be read from the database as the attribute information of the plurality of edge nodes 43 participating in the scheduling of the access request provided by the client 41.

In other embodiments, scheduling node 42 may provide scheduling query information to client 41 prior to scheduling a data processing service provider for an access request provided by client 41. The dispatch query information is used to provide the target user with a choice of whether to agree to invoke the edge node of the data processing service provider for which the other user is registered. Accordingly, if the target user agrees to invoke the edge node of the data processing service provider registered by the other user, the corresponding confirmation operation may be triggered. The attribute information of the edge nodes of the plurality of data processing service providers registered by the target user and other users who provide the access request may be read from the database as the attribute information of the edge nodes 43 participating in the scheduling of the access request provided for the client 41 for the scheduling node 42 in response to the confirmation operation for the scheduling query information. Accordingly, if the target user does not agree to invoke the data processing service provider registered by the other user, a corresponding negative operation may be triggered. For the scheduling node 42, attribute information of edge nodes of a plurality of data processing service providers registered for a target user providing an access request may be read from the database as attribute information of edge nodes 43 participating in scheduling of the access request provided for the client 41 in response to a negative operation with respect to the scheduling query information.

After acquiring attribute information of a plurality of edge nodes 43 participating in scheduling of an access request provided for the client 41, the scheduling node 42 may select a target edge node from the plurality of edge nodes 43 according to the access request and the attribute information of the plurality of edge nodes 43 providing a data processing service.

Specifically, the scheduling node 42 may obtain, from the access request, a target data processing type corresponding to the access request; acquiring target attribute information of the plurality of edge nodes 43 aiming at the target data processing type from the attribute information of the plurality of edge nodes 43; further, a target edge node may be selected from the plurality of edge nodes 43 according to target attribute information of the plurality of edge nodes 43 for the target data processing type. Regarding the specific embodiment of selecting the target edge node from the plurality of edge nodes 43 according to the target attribute information of the plurality of edge nodes 43 for the target data processing type, reference may be made to the above-mentioned target attribute information of the plurality of data processing service providers for the target data processing type, and the relevant content of the target data processing service provider is selected from the plurality of data processing service providers, which will not be described herein.

After determining the target edge node, the scheduling node 42 may convert the access request to a target access format supported by the target edge node to obtain an access request in the target access format. Specifically, the scheduling node 42 may obtain, from the set correspondence between the edge node and the access format, the target access format supported by the target edge node; and converting the access request into a target access format supported by the target edge node to obtain the access request in the target access format. The correspondence between the set edge node and the access format may be set in the scheduling node 42 or may be set in the database.

The correspondence between the data processing service provider and the access format may be obtained by a developer of the scheduling node 42 from a technical document provided by the data processing service provider and set in the scheduling node 42 or the database.

Further, the scheduling node 42 may schedule data processing services of the target edge node provider with access requests in the target access format. Since the access request in the target access format is in the form of a data processing service interface adapted by the target edge node, the scheduling node 42 may schedule the data processing services of the target edge node. In the embodiment of the application, the interfaces of different edge nodes in the same scene can be loaded into the call frame in the form of plug-ins through interface driving adaptation.

For the target edge node, the access request may be processed by a data processing service to obtain a data processing result. Specifically, the data processing service provided by the target edge node may obtain the data to be processed according to the access request. In some embodiments, the data processing service provided by the target edge node may parse the pending data from the access request. In other embodiments, the data processing service provided by the target edge node may parse the identification of the data to be processed from the access request; and acquiring the data to be processed according to the identification of the data to be processed. For example, the data to be processed is an image, the identifier of the data to be processed is a URL of the image, and the data processing service provided by the target edge node may acquire the image as the data to be processed according to the URL of the image. Further, the data processing service provided by the target edge node can process the data to be processed by using the set data processing logic so as to obtain a data processing result.

Further, the target edge node may return the data processing results to the scheduling node 42. Because the data processing result is provided by the target edge node and meets the data format requirement of the target edge node, the scheduling node 42 can also perform data format conversion on the data processing result to obtain the set data format. Wherein the set data format is the data transmission format of the components between the scheduling nodes 42. Further, the scheduling node 42 may send the data processing result with the set data format to the client 41, so that the client 41 outputs the data processing result (corresponding to step 13 of fig. 3).

In the embodiment of the application, a scheduling node is additionally arranged in the edge cloud network system, and the scheduling node can schedule a target edge node providing data processing service for the access request according to attribute information of a plurality of edge nodes and the access request aiming at the access request of the data processing service. Furthermore, a driving layer called by a data processing service interface is additionally arranged on the dispatching node, so that the access request of the data processing service can be converted into a target access format supported by a target edge node, the access formats of different edge nodes are adapted, and the unified call of the data processing service provided by the different edge nodes is realized. The user does not need to grasp the interface parameter form and the calling mode of each edge node, and the convenience of service calling of different edge nodes can be improved.

On the other hand, according to the attribute information of the edge nodes and the access request, the target edge node providing the data processing service for the access request is scheduled, so that the dynamic call to the edge node is realized, and the data processing service call is not dependent on a single data processing service provider. In this way, even if the data processing service provided by one edge node is abnormal, the access request can be scheduled to other edge nodes, so that the robustness of the data processing service is improved, and the influence on the application of the user side is reduced.

In addition to the system embodiments described above, embodiments of the present application further provide a data processing service scheduling method, and an exemplary description is provided below with reference to specific embodiments.

Fig. 4b is a flowchart of a scheduling method according to an embodiment of the present application. As shown in fig. 4b, the method mainly includes:

401. an access request for a data processing service is obtained.

402. Attribute information of a plurality of data processing service providers providing data processing services is acquired.

403. A target data processing service provider is selected from the plurality of data service providers based on the access request and the attribute information.

404. And converting the access request into a target access format supported by the target data processing service provider to obtain the access request in the target access format.

405. The data processing service of the target data processing service provider is invoked with an access request in the target access format.

In the embodiment of the application, when a user needs to call the data processing service to process data, the user can send an access request for the data processing service to the scheduling end through the client. The access request may carry access request parameters. Wherein the access request parameters may include: the type of data processing service to be accessed, the data to be processed, etc.

For the scheduling end, in step 401, an access request for a data processing service provided by the client may be obtained; and performs data processing service scheduling on the access request. Specifically, in step 402, attribute information of a plurality of data processing service providers providing data processing services may be acquired. For description of the attribute information of the data processing service provided by the data processing service provider, reference may be made to the related content of the above embodiment, and the description thereof will not be repeated.

In the embodiment of the present application, a specific implementation manner of acquiring attribute information of a plurality of data processing service providers to provide data processing services is not limited. In some embodiments, a user may register configuration information of a data processing service provider with a dispatcher. The data processing service provided by the data processing service provider can be deployed in a central cloud or in an edge node of an edge cloud network.

Accordingly, configuration information of a data processing service provider provided by a user can be obtained; and store configuration information for the data processing service provider. Alternatively, the configuration information of the user-provided data processing service provider may be stored in a database.

Further, the data processing service provider may be monitored according to configuration information of the data processing service provider registered by the user to obtain attribute information of the data processing service provider. Configuration information for a plurality of data processing service providers may be read from a database for a monitoring component. In an embodiment of the present application, a plurality of data processing service providers may be registered data processing service providers for a target user providing an access request. Of course, the plurality of data processing service providers may also include: a data processing service provider that provides for registration of a target user of an access request and data processing service providers registered by other users.

Further, the user name and access key information providing the configuration information may be obtained from the configuration information of the data processing service provider; and monitoring the plurality of data processing providers by using the user name and the access key information to acquire attribute information of the data processing service provider. In the embodiment of the present application, the user name and access key information refer to user name and access key information of a user who registers configuration information of a data processing service provider.

For an edge cloud network, data processing services of multiple data service providers are deployed at edge nodes. Accordingly, the attribute information of the data processing service provided by the plurality of edge nodes corresponding to the plurality of data processing service providers can be obtained as the attribute information of the plurality of data processing service providers. Specifically, the user name and access key information may be used to monitor the plurality of edge nodes to obtain attribute information of the plurality of edge nodes providing the data processing service.

In the embodiment of the present application, the process of monitoring the plurality of data processing providers may occur before or after receiving the access request. In some embodiments, the plurality of data processing service providers may be periodically monitored for attribute information of the plurality of data processing service providers according to a set monitoring period. Further, the acquired attribute information of the plurality of data processing service providers may be stored in a database.

Since the attribute information of the data processing service provider may reflect the merits of the data processing service provided by the data processing service provider, in this embodiment, in step 403, a target data processing service provider may be selected from a plurality of data service providers according to the access request and the attribute information of the data processing service provided by the plurality of data processing service providers.

Alternatively, attribute information of a plurality of data processing service providers providing data processing services may be read from the database. It is noted that in some embodiments, multiple data processing service providers participating in the scheduling of data processing service providers for an access request provided by a client may be registered for the target user providing the access request. In other embodiments, a plurality of data processing service providers participating in a client-provided access request for data processing service provider scheduling may include: a data processing service provider that provides a target user registration of the access request, and data processing service providers that other users register.

Accordingly, an alternative embodiment of step 402 is: when the data processing service provider is scheduled for the access request provided by the client, attribute information of the data processing service provider registered by the target user providing the access request may be read from the database as attribute information of the data processing service provider participating in the scheduling of the access request provided by the client.

In other embodiments, the scheduling query information may be provided to the client before scheduling the data processing service provider for the access request provided by the client. The scheduling query information is used to provide the target user with a choice of whether to agree to invoke the data processing service provider for which other users are registered. Accordingly, if the target user agrees to invoke the data processing service provider registered by the other user, the corresponding confirmation operation may be triggered. Attribute information of a plurality of data processing service providers registered by a target user and other users who provide access requests may be read from the database as attribute information of data processing service providers participating in scheduling of access requests provided for clients in response to a confirmation operation for scheduling of the query information. Accordingly, if the target user does not agree to invoke the data processing service provider registered by the other user, a corresponding negative operation may be triggered. Accordingly, attribute information of a plurality of data processing service providers registered by a target user who provides an access request can be read from the database as attribute information of data processing service providers participating in scheduling of an access request provided for a client in response to a negative operation with respect to the scheduling query information.

After obtaining attribute information of a plurality of data processing service providers participating in the scheduling of the access request provided for the client, in step 403, a target data processing service provider may be selected from the plurality of data service providers based on the access request and the attribute information of the plurality of data processing service providers providing the data processing service.

Specifically, the target data processing type corresponding to the access request can be obtained from the access request; acquiring target attribute information of a plurality of data processing service providers aiming at a target data processing type from attribute information of a plurality of data service providers; further, a target data processing service provider may be selected from the plurality of data processing service providers based on target attribute information of the plurality of data processing service providers for the target data processing type.

After obtaining the service evaluation parameters of the plurality of data processing service providers, a target data processing service provider may be selected from the plurality of data processing service providers based on the service evaluation parameters of the plurality of data processing service providers.

After the target data processing service provider is determined, in step 404, the access request may be converted to a target access format supported by the target data processing service provider to obtain an access request in the target access format. Specifically, a target access format supported by a target data processing service provider can be obtained from a corresponding relation between the set data processing service provider and the access format; and converting the access request into a target access format supported by the target data processing service provider to obtain the access request in the target access format. The corresponding relation between the set data processing service provider and the access format can be set in the driving component or in the database.

Further, in step 405, the data processing service of the target data processing service provider may be scheduled with the access request in the target access format. Since the access request in the target access format is in the form of a data processing service interface adapted to the target data processing provider, the data processing service of the target data processing service provider can be scheduled. In the embodiment of the application, the interfaces of different data processing service providers in the same scene can be loaded into the call framework in the form of plug-ins through interface driving adaptation.

For the target data processing service provider, the access request can be processed by the data processing service to obtain a data processing result. For the specific implementation of the target data processing service provider that can utilize the data processing service to process the access request, reference may be made to the relevant content of the above system embodiment, which is not described herein again.

Further, the target data processing service provider may return the data processing results to the drive component. Because the data processing result is provided by the target data processing service provider and meets the data format requirement of the target data processing service provider, the data format conversion can be performed on the data processing result to obtain the set data format. The set data format is the data transmission format of the components between the dispatching terminals. Further, the data processing result with the set data format may be sent to the client for the client to output the data processing result.

In the embodiment of the application, for the access request of the data processing service, the target data processing service provider providing the data processing service for the access request can be scheduled according to the attribute information of a plurality of data processing service providers and the access request. Furthermore, a driving layer (i.e. a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that the access request of the data processing service can be converted into a target access format supported by a target data processing service provider, the formats of different data processing service providers are adapted, and the unified call of different data processing service providers is realized. The user does not need to grasp the interface parameter form and the calling mode of each data processing service provider, and the convenience of service calling of different data service providers can be improved.

It should be noted that, the execution subjects of each step of the method provided in the above embodiment may be the same device, or the method may also be executed by different devices. For example, the execution subject of steps 401 and 402 may be device a; for another example, the execution body of step 401 may be device a, and the execution body of step 402 may be device B; etc.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations, such as 401, 402, etc., are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.

Accordingly, embodiments of the present application also provide a computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the steps in the data processing service scheduling method described above.

Fig. 5 is a schematic structural diagram of a computing device according to an embodiment of the present application. As shown in fig. 5, the computing device includes: a memory 50a, a processor 50b, and a communication component 50c; wherein the memory 50a is used for storing a computer program;

the processor 50b is coupled to the memory 50a and the communication component 50c for executing computer programs for: acquiring an access request for a data processing service through the communication component 50 c; acquiring attribute information of data processing services provided by a plurality of data processing service providers; selecting a target data processing service provider from a plurality of data service providers according to the access request and the attribute information; converting the access request into a target access format supported by a target data processing service provider to obtain an access request in the target access format; the data processing service of the target data processing service provider is invoked by the communication component 50c with an access request in the target access format.

In some embodiments, the processor 50b is further configured to: configuration information for a plurality of data processing service providers provided by a user is obtained via communication component 50 c. Optionally, the processor 50b is specifically configured to, when acquiring attribute information of a plurality of data service providers for providing data processing services: and monitoring a plurality of data processing service providers according to the configuration information to acquire attribute information.

Specifically, the processor 50b is specifically configured to, when monitoring a plurality of data processing service providers based on configuration information of the plurality of data processing service providers: acquiring a user name and access key information for providing configuration information from the configuration information; multiple data processing providers are monitored using the user name and access key information to obtain attribute information.

In other embodiments, the processor 50b is specifically configured to, when selecting a target data processing service provider from a plurality of data service providers: obtaining a target data processing type corresponding to the access request from the access request; acquiring target attribute information of a plurality of data processing service providers aiming at a target data processing type from the attribute information; a target data processing service provider is selected from the plurality of data processing service providers based on the target attribute information.

Further, the processor 50b is specifically configured to, when selecting a target data processing service provider from a plurality of data processing service providers based on the target attribute information: for any data processing service provider, acquiring value attribute information and performance attribute information of any data processing service provider from target attribute information of any data processing service provider; weighting the value attribute information and the performance attribute information of any data processing service provider to obtain service evaluation parameters of any data processing service provider; and selecting a target data processing service provider from the plurality of data processing service providers according to the service evaluation parameters of the plurality of data processing service providers.

Optionally, the processor 50b is further configured to: before weighting the value attribute information and the performance attribute information of any data processing service provider to obtain service evaluation parameters of any data processing service provider, acquiring the access times of a target user providing an access request for a target data processing type of any data processing service provider from the attribute information of any data processing service provider; judging whether the access times are smaller than the times quota of the target data processing type of any data processing service provider accessible by the target user; and if the judgment result is yes, weighting the value attribute information and the performance attribute information of any data processing service provider so as to obtain the service evaluation parameters of any data processing service provider. Accordingly, if the judgment result is negative, determining that the service evaluation parameter of any data processing service provider is 0.

In some embodiments, the processor 50b, when acquiring attribute information of a plurality of data processing service providers providing data processing services, is specifically configured to: attribute information of a plurality of data processing service providers registered by a target user providing an access request is read from a database.

In other embodiments, data processing services of multiple data service providers are deployed at an edge node. Accordingly, the processor 50b, when acquiring attribute information of the data processing services provided by the plurality of data processing service providers, is specifically configured to: and acquiring attribute information of the data processing service provided by a plurality of edge nodes corresponding to the plurality of data processing service providers as the attribute information of the plurality of data processing service providers.

Optionally, the processor 50b, when acquiring attribute information of the data processing services provided by the plurality of data processing service providers, is further configured to: providing scheduling query information to a client providing an access request through the communication component 50 c; the scheduling query information is used for enabling the target user to select whether to agree to call the data processing service provider registered by other users; attribute information of a plurality of data processing service providers registered by a target user and other users who provide access requests is acquired from a database in response to a confirmation operation of scheduling query information. Or in response to a negative operation of scheduling the query information, attribute information of a plurality of data processing service providers registered by the target user providing the access request is read from the database.

Optionally, the processor 50b is further configured to: and acquiring a target access format supported by the target data processing service provider from the corresponding relation between the set data processing service provider and the access format.

In some embodiments, the processor 50b is further configured to: receiving, by the communication component 50c, a data processing result corresponding to the access request returned by the target data processing service provider; converting the data format of the data processing result to obtain a set data format; and transmitting the data processing result having the set data format to the client providing the access request through the communication component 50c for the client to output the data processing result.

In some alternative implementations, as shown in fig. 5, the computing device may further include: power supply assembly 50d, etc. In some embodiments, the computing device may be implemented as a terminal device such as a cell phone, a computer, or the like. Accordingly, the computing device may further include: display component 50e and audio component 50f, etc. Only a portion of the components are schematically shown in fig. 5, which does not mean that the computing device must contain all of the components shown in fig. 5, nor that the computing device can only include the components shown in fig. 5.

The computing device provided in this embodiment may schedule, for an access request of a data processing service, a target data processing service provider that provides the data processing service for the access request according to attribute information of a plurality of data processing service providers and the access request. Furthermore, a driving layer (i.e. a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that the access request of the data processing service can be converted into a target access format supported by a target data processing service provider, the formats of different data processing service providers are adapted, and the unified call of different data processing service providers is realized. The user does not need to grasp the interface parameter form and the calling mode of each data processing service provider, and the convenience of service calling of different data service providers can be improved.

In an embodiment of the present application, the memory is used to store a computer program and may be configured to store various other data to support operations on the device on which it resides. Wherein the processor may execute a computer program stored in the memory to implement the corresponding control logic. The memory may be implemented by any type of volatile or nonvolatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

In an embodiment of the present application, the processor may be any hardware processing device that may execute the above-described method logic. Alternatively, the processor may be a central processing unit (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU) or a micro-control unit (Microcontroller Unit, MCU); programmable devices such as Field-Programmable gate arrays (Field-Programmable GATE ARRAY, FPGA), programmable array Logic devices (Programmable Array Logic, PAL), general-purpose array Logic devices (GENERAL ARRAY Logic, GAL), complex Programmable Logic devices (Complex Programmable Logic Device, CPLD), and the like; or an advanced Reduced Instruction Set (RISC) processor (ADVANCED RISC MACHINES, ARM) or a System On Chip (SOC), etc., but is not limited thereto.

In an embodiment of the application, the communication component is configured to facilitate wired or wireless communication between the device in which it is located and other devices. The device in which the communication component is located may access a wireless network based on a communication standard, such as WiFi,2G or 3G,4G,5G or a combination thereof. In one exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component may also be implemented based on Near Field Communication (NFC) technology, radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, or other technologies.

In an embodiment of the present application, the display assembly may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the display assembly includes a touch panel, the display assembly may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation.

In an embodiment of the application, the power supply assembly is configured to provide power to the various components of the device in which it is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.

In embodiments of the application, the audio component may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive external audio signals when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a speech recognition mode. The received audio signal may be further stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals. For example, for a device with language interaction functionality, voice interaction with a user, etc., may be accomplished through an audio component.

It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

The storage medium of the computer is a readable storage medium, which may also be referred to as a readable medium. Readable storage media, including both permanent and non-permanent, removable and non-removable media, may be implemented in any method or technology for information storage. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims

1. An edge cloud network system, comprising: the system comprises a client, a scheduling node and a plurality of edge nodes; a plurality of edge nodes belong to different data processing service providers, the plurality of data processing service providers provide the same data processing service, the same data processing service provided by the data processing service providers is deployed on the corresponding edge nodes, access formats defined by the plurality of data processing service providers and calling the same data processing service through an API are different, and the access formats are different in interface parameters and/or calling forms;

the client is used for providing an access request for calling the same data processing service for the dispatching node;

The scheduling node is used for acquiring attribute information of the same data processing service provided by a plurality of edge nodes corresponding to a plurality of data processing service providers; selecting a target edge node corresponding to a target data processing service provider from a plurality of edge nodes corresponding to the plurality of data processing service providers according to the access request and the attribute information; converting the access request into an access request which is defined by the target data processing service provider and is in the same data processing service target access format through API call so as to obtain the target access format; and invoking the same data processing service deployed on the target edge node by the target data processing service provider using the access request in the target access format.

2. A scheduling method, applied to a scheduling system, where the scheduling system includes a client, a scheduling node, and a plurality of data processing service providers, where the plurality of data processing service providers provide a same data processing service, and access formats defined by the plurality of data processing service providers for calling the same data processing service through an API are different, where the access formats refer to different interface parameters and/or call forms, and the method is performed by the scheduling node, where the method includes:

Acquiring an access request provided by the client for calling the same data processing service;

acquiring attribute information of the same data processing service provided by a plurality of data processing service providers;

selecting a target data processing service provider from the plurality of data processing service providers according to the access request and the attribute information;

Converting the access request into a target access format defined by the target data processing service provider and calling the same data processing service through an API (application program interface) so as to obtain an access request in the target access format;

And calling the same data processing service of the target data processing service provider by using the access request in the target access format.

3. The method as recited in claim 2, further comprising:

Acquiring configuration information of the plurality of data processing service providers provided by a user;

The acquiring attribute information of a plurality of data processing service providers for providing data processing services includes:

And monitoring the plurality of data processing service providers according to the configuration information to acquire the attribute information.

4. A method according to claim 3, wherein said monitoring said plurality of data processing service providers to obtain said attribute information based on configuration information of said plurality of data processing service providers comprises:

Acquiring a user name and access key information for providing the configuration information from the configuration information;

And monitoring the plurality of data processing providers by using the user name and the access key information to acquire the attribute information.

5. The method of claim 2, wherein selecting a target data processing service provider from the plurality of data processing service providers based on the access request and the attribute information comprises:

acquiring a target data processing type corresponding to the access request from the access request;

Acquiring target attribute information of the plurality of data processing service providers aiming at the target data processing type from the attribute information;

And selecting a target data processing service provider from the plurality of data processing service providers according to the target attribute information.

6. The method of claim 5, wherein selecting a target data processing service provider from the plurality of data processing service providers based on the target attribute information comprises:

for any data processing service provider, acquiring value attribute information and performance attribute information of the any data processing service provider from target attribute information of the any data processing service provider;

Weighting the value attribute information and the performance attribute information of any data processing service provider to obtain service evaluation parameters of any data processing service provider;

And selecting a target data processing service provider from the plurality of data processing service providers according to the service evaluation parameters of the plurality of data processing service providers.

7. The method of claim 6, wherein prior to weighting the value attribute information and performance attribute information for any one data processing service provider to obtain the service valuation parameters for any one data processing service provider, the method further comprises:

Acquiring the access times of a target user providing the access request for the target data processing type of any data processing service provider from the attribute information of the any data processing service provider;

judging whether the access times are smaller than the times quota of the target data processing type of any data processing service provider accessible by the target user;

And if the judgment result is yes, weighting the value attribute information and the performance attribute information of any data processing service provider to obtain the service evaluation parameters of any data processing service provider.

8. The method of claim 2, wherein the same data processing service provided by the plurality of data processing service providers is deployed at an edge node of an edge cloud network; the obtaining attribute information of the same data processing service provided by a plurality of data processing service providers includes:

And acquiring attribute information of the same data processing service provided by a plurality of edge nodes corresponding to the plurality of data processing service providers as the attribute information of the same data processing service provided by the plurality of data processing service providers.

9. The method of claim 2, wherein the obtaining attribute information of the same data processing service provided by a plurality of data processing service providers comprises:

providing scheduling query information to a client providing the access request; the scheduling query information is used for enabling a target user providing the access request to select whether to agree to call a data processing service provider registered by other users;

And responding to the confirmation operation of the scheduling query information, and acquiring attribute information of a plurality of data processing service providers registered by the target user and other users for providing the access request from a database.

10. The method as recited in claim 9, further comprising:

And in response to a negative operation of the scheduling query information, attribute information of a plurality of data processing service providers registered by a target user providing the access request is read from a database.

11. The method as recited in claim 2, further comprising:

receiving a data processing result corresponding to the access request returned by the target data processing service provider;

Converting the data format of the data processing result to obtain a set data format;

And sending the data processing result with the set data format to a client providing the access request so that the client can output the data processing result.

12. A scheduling system, comprising: the system comprises a client, a scheduling end and a plurality of data processing service providers, wherein the plurality of data processing service providers provide the same data processing service, the access formats defined by the plurality of data processing service providers for calling the same data processing service through an API are different, and the access formats are different in interface parameters and/or calling forms; the scheduling end comprises: the device comprises a scheduling component, a monitoring component and a driving component;

the scheduling component is used for acquiring an access request provided by the client for calling the same data processing service by a user;

The monitoring component is used for acquiring attribute information of the same data processing service provided by a plurality of data processing service providers;

the scheduling component is further configured to select a target data processing service provider from the plurality of data processing service providers according to the access request and the attribute information;

the driving component is used for converting the access request into a target access format which is defined by the target data processing service provider and calls the same data processing service through an API so as to obtain an access request in the target access format; and invoking said same data processing service of said target data processing service provider with an access request of said target access format.

13. A computing device, comprising: a memory, a processor, and a communication component; wherein the memory is used for storing a computer program;

The processor is coupled to the memory and the communication component for executing the computer program for performing the steps in the method of any of claims 2-11.

14. A computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the steps in the method of any of claims 2-11.