CN115002229A

CN115002229A - Edge cloud network system, scheduling method, device, system and storage medium

Info

Publication number: CN115002229A
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: 2022-09-02

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 the data processing service scheduling system, and the scheduling end can schedule a target data processing service provider providing data processing service for an access request according to the attribute information and the access request of a plurality of data processing service providers aiming at the access request of the data processing service. Furthermore, a driving layer for calling the 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 uniform calling of different data processing service providers is realized. For a user, the interface parameter form and the calling mode of each data processing service provider do not need to be mastered, and the convenience of service calling of different data service providers can be improved.

Description

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

Technical Field

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

Background

With the increasing maturity of artificial intelligence and machine learning techniques, the data processing capabilities of more versatile scenarios have evolved into mature products such as Optical Character Recognition (OCR), Natural Language Processing (NLP), text-to-speech (TTS) services, and so on. The data processing service provider generally provides the out-of-box data processing service capability in the form of an API, and the user calls the relevant data processing service according to the 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 service is oriented to the same scene, the data processing service interface calling modes of different data processing service providers are different, and great inconvenience is brought to the user for calling the data processing service.

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, so as to provide a uniform data processing service scheduling manner, and improve convenience of service invocation by different data service providers.

An embodiment of the present application further provides an edge cloud network system, including: 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 edge nodes are different;

the client is used for providing an access request aiming at 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 calling the 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.

An embodiment of the present application further provides a scheduling system, including: 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 provided by the client and aiming at the data processing service;

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 used for selecting 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 the 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 format.

An embodiment of the present application further provides a computing device, including: 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 above-mentioned data processing service scheduling method.

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

In the embodiment of the application, a scheduling end is additionally arranged in the data processing service scheduling system, and the scheduling end can schedule a target data processing service provider which provides data processing service for an access request according to attribute information and the access request of a plurality of data processing service providers aiming at the access request of the data processing service. Furthermore, a driving layer (namely a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that an 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 uniform calling of different data processing service providers is realized. For a user, the interface parameter form and the calling mode of each data processing service provider do not need to be mastered, and the convenience of service calling of different data service providers can be improved.

On the other hand, according to the attribute information and the access requests of the plurality of data processing service providers, a target data processing service provider providing data processing services for the access requests is scheduled, and dynamic calling of the data processing service providers is realized, so that the data processing service calling does not depend on a single data processing service provider any more. In this way, even if the data processing service provided by a certain data processing service provider is abnormal, the access request can be dispatched to other data processing service providers, so that the robustness of the data processing service is improved, and the influence on the application of the user side is reduced.

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 application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 and fig. 2 are schematic structural diagrams of a scheduling system provided in an embodiment of the present application;

fig. 3 is a schematic process diagram 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 provided in an embodiment of the present application;

fig. 4b is a schematic flowchart 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 described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The data processing service refers to a service that provides various data processing methods. The data includes: character data, image data, video data, audio data, and the like, but are not limited thereto. The data processing service 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 (AI) services and other data processing services, such as data storage services, data query services, and data modification services. AI services refer to data processing services related to the field of artificial intelligence. Such as Optical Character Recognition (OCR), Natural Language Processing (NLP), text-to-speech conversion (TTS), target recognition, etc.

The data processing service provider generally provides the out-of-box data processing service capability in the form of an API, and the user calls the relevant data processing service according to the interface parameters defined by the data processing service provider. For example, a user may initiate an HTTP call to a specified interface of a 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 secret access key (SK).

However, the definitions of interface parameters, call forms, and return values for different data processing service providers are often not completely consistent. Taking the widely used OCR service as an example, some request parameters required by the data processing service provider a are picture URLs, which are represented by an "image" field; meanwhile, configuration parameters such as the minimum height of characters in a picture, the probability of whether to output a character box, the prediction of whether to close the character row direction and the like need to be transmitted in a json form. The return value is a json array, and each part in the json array contains "text content", "text region probability", "region coordinate", and the like. And another data processing service provider also providing OCR services, the interface thereof comprising: picture address URL, represented in the "ImageUrl" field; identifying a language type, which is represented by a 'LanguageType' field; whether PDF identification is turned on is indicated by an "IsPdf" field. And the return values include text line content, confidence, text line coordinates, text line rotation corrected coordinates, language type, and the like. Therefore, even if the data processing service is 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 the data processing service interface of the third-party data processing service provider, which puts strong demands on the use cost and availability of the data processing service interface. If a service interface of a single data processing service provider fails, the application of the user himself has a great influence without a backup interface. Meanwhile, the payment modes, time delays and the like of the interfaces of different data processing service providers are different. If the appropriate data processing service provider is flexibly selected for different areas and different sizes of user requests, a better balance between the use cost, the user experience and the service availability is obtained.

In order to solve the above technical problem, in some embodiments of the present application, a scheduling end is added in a data processing service scheduling system, and the scheduling end may schedule, for an access request of a data processing service, a target data processing service provider providing 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 (namely a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that an 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 uniform calling of different data processing service providers is realized. For a user, the interface parameter form and the calling mode of each data processing service provider do not need to be mastered, and the convenience of service calling of different data service providers can be improved.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

It should be noted that: like reference numerals refer to 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 required in 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 dispatcher 20 and a plurality of data processing service providers 30. Plural means 2 or more.

In this embodiment, the client 10 refers to a computer device used by a user and having functions of computing, accessing internet, communicating and the like required by the user, and may be, for example, a mobile phone, a tablet computer, a personal computer, a wearable device and the like.

The data processing service provider 30 refers to a server that provides data processing services to users. The data processing service provider 30 may deploy data processing services through server-side equipment, and provide a SaaS-based service for a user. 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 with corresponding service capabilities, such as a terminal device (running a service program) such as a computer.

In this embodiment of the application, the data processing service provided by the data processing service provider 30 may be deployed in a server device of a central cloud, or may be deployed in an edge cloud of an edge cloud network. An edge cloud may be a computer room, a Data Center (DC), or an 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: a distributed Data Center (DC), a wireless room or cluster, an edge device such as a communication network of an operator, a core network device, a base station, an edge gateway, a home gateway, a computing device or a storage device, a corresponding network environment, and the like. It is noted that the location, capabilities, and infrastructure involved of the various edge nodes may or may not be the same.

In the embodiment of the present application, there are at least 2 data processing service providers 30 with different definitions of interface parameters and/or scheduling forms of data processing service interfaces provided by the 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 scheduling client 20 is a computing device that can schedule a plurality of data processing service providers 30 in response to an access request from the client 10 for a data processing service provided by the data processing service provider 30. The scheduling end 20 may be 1 or more server-side devices. For the implementation of the server device, reference may be made to the above related contents, which are not described herein again.

In this embodiment, the client 10 and the scheduling end 20 may be connected wirelessly or by wire. Optionally, the client 10 may be communicatively connected to the scheduling end 20 through a mobile network, and accordingly, the network format 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, and the like. Alternatively, the client 10 may also be communicatively connected to the scheduling terminal 20 by bluetooth, WiFi, infrared, etc.

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

In the embodiment of the present application, the dispatcher 20 may provide a data processing service provider dispatching 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 all be logic function modules, and may be deployed in the same physical machine or in different physical machines.

In the embodiment of the present application, referring to fig. 1 to fig. 3, when a user needs to invoke a data processing service for 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 parameter may include: the type of data processing service to be accessed, the data to be processed, and the like. 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 an 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 (URL) of the image.

For the scheduling end 20, an access request for the data processing service sent by the client 10 may be obtained; and performs data processing service scheduling on the access request. Specifically, as shown in fig. 1 and 2, the dispatcher 20 may obtain attribute information of a data processing service provided by a 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, and includes, but is not limited to: value attribute information of the data processing service provided by the data processing service provider 30, performance attribute information, access number quota of the data processing service, access number of the target user providing the access request to the data processing service provided by the data processing service provider 30, and resource package information corresponding to the data processing service, and the like. For the edge cloud network, the attribute information of the data processing service provided by the plurality of data processing service providers 30 may be represented by the attribute information of the data processing service provided by the plurality of edge nodes corresponding to the plurality of data processing service providers 30.

The value attribute information of the data processing service provided by the data processing service provider 30 may be embodied as a charging standard of the data processing service provided by the data processing service provider 30, and the like. The performance attribute information of the data processing service provided by the data processing service provider 30 refers to information reflecting the performance merits of the data processing service provided by the data processing service provider 30, and includes, but is not limited to: the data processing service provided by the data processing service provider 30 corresponds to, but is not limited to, availability of an interface service, access latency, and the like.

The access time quota of the data processing service is used for: the maximum number of times that the user can access the data processing service provided by the data processing service provider 30 within a set period is limited, or the maximum number of times that the user can access the data processing service provided by the data processing service provider 30 in total is limited. For example, the quota of access times for the data processing service may be "1000 times/day", that is, the maximum access times that a user can access the data processing service provided by the data processing service provider 30 within 1 day is 1000 times. For another example, the quota of access times for the data processing service may be "10000 times", that is, the maximum access times that the 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 refers to the 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, a specific implementation of acquiring attribute information of a data processing service provided by a 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 dispatcher 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 that the user subscribes to or rents from. The user may register the configuration information of the data processing service provider 30 in the form of a template set by the dispatcher terminal 20.

The configuration information of the data processing service provider 30 may include: identification (such as name, number or other identifier) of the data processing service provider 30, user name and access key information of the user at the data processing service provider 30, and resource package information and access time quota of the data processing service provider that the user applies, subscribes or rents, etc. Wherein the access key information includes: access Key ID (AK ID), Secret Access Key (SK), and the like.

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

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 the access key information to acquire 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 a user to provide data processing services as attribute information of a plurality of data processing service providers 30. In particular, the monitoring component 203 can monitor the plurality of edge nodes using the user name and the access key information to obtain attribute information of the plurality of edge nodes providing the data processing service.

In the 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 the access request is received 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 for 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 the present embodiment, for the scheduling component 201, a target data processing service provider may be selected from the plurality of data processing service providers 30 according to the access request and the attribute information of the data processing service provided by the plurality of data processing service providers 30.

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

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

In other embodiments, the scheduling component 201 may provide scheduling query information to the client 10 prior to scheduling the data processing service provider for the access request provided by the client 10. The scheduling query information is used for the target user to select whether to approve invoking the data processing service provider registered by the other user. Correspondingly, 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 scheduling component 201 may read, from the database, attribute information of a plurality of data processing service providers registered by the target user who provided the access request and other users, as attribute information of the data processing service provider 30 participating in scheduling of the access request provided for the client 10, in response to the confirmation operation for the scheduling inquiry information. Correspondingly, if the target user does not agree to invoke the data processing service provider registered by the other user, a corresponding negation operation may be triggered. The scheduling component 201 may read, from the database, attribute information of a plurality of data processing service providers registered by a target user providing an access request, as attribute information of the data processing service provider 30 participating in scheduling of the access request provided for the client 10, in response to a negative operation with respect to the scheduling inquiry information.

After obtaining 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 processing service providers 30 according to the access request and the attribute information of the data processing service provided by the plurality of data processing service providers 30 (corresponding to step 9 of fig. 3).

Specifically, the scheduling component 201 may obtain a target data processing type corresponding to the access request from the access request; and acquires target attribute information of the plurality of data processing service providers 30 for a 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 the target attribute information of the plurality of data processing service providers 30 for the target data processing type.

In particular, for any data processing service provider P _i From a data processing service provider P _i In the target attribute information of (2), the data processing service provider P is acquired _i Value attribute information and performance attribute information of (1); further, for the data processing service provider P _i The value attribute information and the performance attribute information are weighted to obtain a data processing service provider P _i The service evaluation parameter of (1).

Optionally, in the data processing service provider P _i Before performing weighting processing on the value attribute information and the performance attribute information, the data processing service provider P may also perform weighting processing on the value attribute information and the performance attribute information _i In the attribute information of (3), acquiring a target user providing an access request for a data processing service provider P _i Is accessed for the target data processing type of (2) _i (ii) a Judging the number of accesses n _i Whether less than the target user accessible data processing service provider P _i Target data ofNumber of times quota q of processing type _i . Further, if the determination result is yes, the data processing service provider P may be notified _i The value attribute information and the performance attribute information are weighted to obtain a data processing service provider P _i The service evaluation parameter of (1).

Correspondingly, if the judgment result is the access times n _i Greater than or equal to the target user accessible data processing service provider P _i Is of the target data processing type q _i Description of a data processing service provider P _i Having no margin available for invocation by the target user, a determination may be made as to which data processing service provider P is to be used _i The service evaluation parameter of (2) is 0.

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

in equation (1), i denotes the ith data processing service provider, and i is 1, 2, …, n. n represents the total number of the plurality of data processing service providers. S _i Indicating the ith data processing service provider P _i The service evaluation parameter of (1). c (i), a (i) and l (i) respectively represent the ith data processing service provider P _i Value attribute information (e.g., single call cost), service availability, and service access latency. Lambda _c 、λ _a And λ _l Respectively represent the ith data processing service provider P _i Such as a single call charge, service availability, and a weight of service access delay.

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 among the plurality of data processing service providers as a 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 may be selected as a target data processing service provider, and the like, from among a plurality of data processing service providers.

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

After determining the target data processing service provider, the driver component 202 may 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 a target data processing service provider from a set correspondence between the data processing service provider and the access format; and converting the access request into a target access format supported by a target data processing service provider to obtain the access request in the target access format. The corresponding relationship between the set data processing service provider and the access format may be set in the driver component 202 or may be set in the database 206.

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

Further, the driver component 202 can schedule a data processing service of a target data processing service provider with an access request in a target access format (corresponding to step 10 of fig. 3). Since the access request in the target access format is in the form of a data processing service interface adapted by the target data processing provider, the driver component 202 may schedule the data processing service 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 calling framework in the form of plug-ins through interface drive adaptation.

For the target data processing service provider, the access request may be processed using 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 identifier of the data to be processed. For example, if the data to be processed is an image and the identifier of the data to be processed is a URL of the image, the data processing service provided by the target data processing service provider may obtain 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 utilize the set data processing logic to process the data to be processed so as to obtain a data processing result.

Further, the target data processing service provider may return the data processing result 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). The set data format is a data transmission format of components between the scheduling terminals 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 in fig. 3).

In the embodiment of the application, a scheduling end is additionally arranged in the data processing service scheduling system, and the scheduling end can schedule a target data processing service provider providing data processing service for an access request according to the attribute information and the access request of a plurality of data processing service providers aiming at the access request of the data processing service. Furthermore, a driving layer (namely a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that an 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 uniform calling of different data processing service providers is realized. For a user, the interface parameter form and the calling mode of each data processing service provider do not need to be mastered, and the convenience of service calling of different data service providers can be improved.

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

Fig. 4a is a schematic structural diagram of an edge cloud network provided in the 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. Plural means 2 or more. For the description of the implementation of the client 41 and the edge node 43, reference may be made to the related contents in the foregoing scheduling system embodiment, and details are not described here. For the description of the scheduling node 42, reference may be made to the related contents of the scheduling end 20 in the foregoing scheduling system embodiment, and details are not described herein again.

In the embodiment of the present application, a plurality of edge nodes 43 are used to provide data processing services; the access formats of the data services provided by the plurality of edge nodes 43 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 by at least 2 edge nodes, for example, the definitions of the interface parameters and/or the scheduling forms of the interfaces are different. Multiple edge nodes 43 may belong to the same data processing service provider or to different data processing service providers.

In the embodiment of the present application, when a user needs to invoke a data processing service for 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 related contents of the foregoing scheduling system embodiment, and details are 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 service 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 obtain attribute information of the plurality of edge nodes 43 providing the data processing service. For the 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 contents of the attribute information of the data processing service provided by the data processing service provider 30, and details are not repeated here.

In the embodiment of the present application, a specific implementation of acquiring attribute information of a data processing service provided by a plurality of edge nodes 43 is not limited. In some embodiments, a user may register configuration information of edge node 43 with scheduling node 42. The edge node 43 with which the user is registered is typically an edge node of a data processing service provider to which the user subscribes or rents. The user may register the configuration information of the edge node 43 in the form of a template set by the scheduling node 42. For the description of the configuration information of the edge node 43, reference may be made to the related contents of the configuration information of the data processing service provider 30, and the description thereof is omitted here.

Accordingly, the scheduling node 42 may obtain configuration information of the edge node 43 provided by the user; and stores configuration information of edge node 43. Alternatively, the configuration information of the edge nodes 43 provided by the user may be stored in a database (. further, the scheduling node 42 may monitor the edge nodes 43 according to the configuration information of the edge nodes 43 registered by the user to obtain the attribute information of the data processing service provided by the edge nodes 43. in the embodiment of the present application, a plurality of edge nodes 43 may be edge nodes of data processing service providers registered by target users providing access requests.

Further, the scheduling node 42 may obtain the user name and the access key information providing the configuration information from the configuration information of the edge node 43; and monitors the plurality of edge nodes 43 using the user name and the access key information to acquire attribute information of the data processing service 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 receiving the access request 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 the 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 service 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 service provided by the plurality of edge nodes 43.

For the scheduling node 42, attribute information of the data processing service provided by the plurality of edge nodes 43 may be read from the database. It is worth noting that in some embodiments, the plurality of edge nodes 43 that participate in scheduling of data processing service providers for access requests provided by the client 41 may be edge nodes of data processing service providers registered for target users that provide the access requests. In other embodiments, the edge nodes of multiple data processing service providers participating 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 registered by a target user providing the access request, and edge nodes of data processing service providers registered by other users.

Accordingly, with 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 for 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 scheduling query information is used for the target user to select whether to approve invoking the edge node of the data processing service provider registered by the other user. Correspondingly, 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 scheduling node 42 may read, from the database, attribute information of edge nodes of a plurality of data processing service providers registered with the target user providing the access request and other users as attribute information of the edge node 43 participating in scheduling of the access request provided for the client 41, in response to the confirmation operation for the scheduling inquiry information. Correspondingly, if the target user does not agree to invoke the data processing service provider registered by the other user, a corresponding negation operation may be triggered. For the scheduling node 42, the attribute information of the edge nodes of the plurality of data processing service providers registered by the target user providing the access request may be read from the database as the attribute information of the edge node 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 obtaining attribute information of the plurality of edge nodes 43 participating in scheduling of the access request provided by 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 the data processing service.

Specifically, the scheduling node 42 may obtain a target data processing type corresponding to the access request from the access request; acquiring target attribute information of the plurality of edge nodes 43 for 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. With regard to a specific embodiment of selecting a destination edge node from the plurality of edge nodes 43 according to the destination attribute information of the plurality of edge nodes 43 for the destination data processing type, reference may be made to the destination attribute information of the plurality of data processing service providers for the destination data processing type, and relevant contents of the destination data processing service provider from the plurality of data processing service providers may be selected, which is not described herein again.

After determining the target edge node, the scheduling node 42 may convert the access request into 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 a target access format supported by the target edge node from the set correspondence between the edge node and the access format; 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 corresponding relationship 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 technical documentation provided by the data processing service provider and set in the scheduling node 42 or a database.

Further, the scheduling node 42 may schedule the data processing services of the destination edge node provider with the access request in the destination 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 edge node, the scheduling node 42 may schedule the data processing service of the target edge node. In the embodiment of the application, the interfaces of different edge nodes of the same scene can be loaded into the calling framework in the form of plug-ins through interface driving adaptation.

For the target edge node, the access request may be processed using 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 identifier of the data to be processed. For example, if the data to be processed is an image and the identifier of the data to be processed is a URL of the image, the data processing service provided by the target edge node may obtain the image according to the URL of the image as the data to be processed, and so on. Further, the data processing service provided by the target edge node can utilize the set data processing logic to process the data to be processed so as to obtain a data processing result.

Further, the target edge node may return the data processing results to dispatch node 42. Since 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 may also perform data format conversion on the data processing result to obtain the set data format. Wherein the set data format is a data transmission format of 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 in 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 for providing data processing service for an access request of the data processing service according to the attribute information and the access request of a plurality of edge nodes. Furthermore, a driving layer for calling a data processing service interface is additionally arranged on the scheduling node, so that an access request of the data processing service can be converted into a target access format supported by a target edge node, the access format of different edge nodes is adapted, and the unified calling of the data processing service provided by different edge nodes is realized. For a user, the interface parameter form and the calling mode of each edge node do not need to be mastered, and the convenience of service calling of different edge nodes can be improved.

On the other hand, according to the attribute information and the access requests of the edge nodes, the target edge node providing the data processing service for the access requests is dispatched, and dynamic calling of the edge nodes is achieved, so that the calling of the data processing service does not depend on a single data processing service provider any more. Therefore, even if the data processing service provided by a certain edge node is abnormal, the access request can be dispatched to other edge nodes, 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 above system embodiments, the embodiments of the present application also provide a data processing service scheduling method, which is exemplarily described below with reference to specific embodiments.

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

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

402. Attribute information of a data processing service provided by a plurality of data processing service providers is acquired.

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

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

405. The access request in the target access format invokes a data processing service of the target data processing service provider.

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

For the scheduling end, in step 401, an access request provided by the client for the data processing service 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 the description of the attribute information of the data processing service provided by the data processing service provider, reference may be made to the relevant contents of the above embodiments, and details are not described herein again.

In the embodiment of the present application, a specific implementation manner of acquiring attribute information of a plurality of data processing service providers for providing 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, the configuration information of the data processing service provider provided by the user can be acquired; and stores configuration information of the data processing service provider. Alternatively, the configuration information of the data processing service provider provided by the user 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 acquire 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 data processing service providers registered 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 a target user registration of the access request and a data processing service provider that other users register.

Further, the user name and the access key information for providing the configuration information can 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 the 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 a plurality of data service providers are deployed at edge nodes. Accordingly, attribute information of a plurality of edge nodes corresponding to a plurality of data processing service providers providing data processing services can be acquired as the attribute information of the plurality of data processing service providers. Specifically, the plurality of edge nodes can be monitored by using the user name and the access key information to acquire attribute information of the plurality of edge nodes for 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 the access request is received or may occur after the access request is received. In some embodiments, the plurality of data processing service providers may be periodically monitored for attribute information at 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 the plurality of data processing service providers based on 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 the data processing service may be read from the database. It is worth noting that in some embodiments, the plurality of data processing service providers participating in the scheduling of the data processing service provider by the access request provided by the client may be registered data processing service providers for the target user providing the access request. In still other embodiments, a plurality of data processing service providers participating in data processing service provider scheduling of access requests provided by clients may include: a data processing service provider registered by a target user providing the access request, and a data processing service provider registered by other users.

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

In other embodiments, the scheduling query information may be provided to the client prior to scheduling the data processing service provider for the access request provided by the client. The scheduling query information is used for the target user to select whether to approve invoking the data processing service provider registered by the other user. Correspondingly, if the target user agrees to invoke the data processing service provider registered by the other user, a corresponding confirmation operation may be triggered. Attribute information of a plurality of data processing service providers registered by a target user providing an access request and other users may 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 confirmation operation for scheduling query information. Correspondingly, if the target user does not agree to invoke the data processing service provider registered by the other user, a corresponding negation operation may be triggered. Accordingly, the attribute information of the plurality of data processing service providers registered by the target user providing the access request may be read from the database as the attribute information of the data processing service provider participating in the scheduling of the access request provided for the client in response to a negative operation with respect to the scheduling inquiry information.

After obtaining the attribute information of the 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 processing service providers based on the access request and the attribute information of the plurality of data processing service providers for 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 the attribute information of the 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 the target attribute information of the plurality of data processing service providers for the target data processing type.

Optionally, the data processing service provider P is paired with _i Before performing weighting processing on the value attribute information and the performance attribute information, the data processing service provider P may also perform weighting processing on the value attribute information and the performance attribute information _i In the attribute information of (2), a target user who provides an access request is acquired for the data processing service provider P _i Is accessed for the target data processing type of (2) _i (ii) a Judging the number of accesses n _i Whether less than the target user accessible data processing service provider P _i Is of the target data processing type q _i . Further, if the determination result is yes, the data processing service provider P may be notified _i The value attribute information and the performance attribute information are weighted to obtain a data processing service provider P _i The service evaluation parameter of (1).

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, 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 in step 404. Specifically, a target access format supported by a target data processing service provider can be acquired from a corresponding relationship between the set data processing service provider and the access format; and converting the access request into a target access format supported by a 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 arranged in the driving component or a 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 a data processing service interface form adapted by 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 calling framework in the form of plug-ins through interface driving adaptation.

For the target data processing service provider, the access request may be processed by the data processing service to obtain a data processing result. For a specific implementation of the target data processing service provider, which can use the data processing service to process the access request, reference may be made to the related contents of the above system embodiments, and details are not described herein again.

Further, the target data processing service provider may return the data processing result to the driver component. 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, so that the data format conversion can be performed on the data processing result to obtain the set data format. The set data format is a data transmission format of components between scheduling terminals. Further, the data processing result with the set data format can be sent to the client side, so that the client side can output the data processing result.

In the embodiment of the present application, for an access request of a data processing service, a target data processing service provider providing the data processing service for the access request may be scheduled according to attribute information of a plurality of data processing service providers and the access request. Furthermore, a driving layer (namely a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that an 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 uniform calling of different data processing service providers is realized. For a user, the interface parameter form and the calling mode of each data processing service provider do not need to be mastered, and the convenience of service calling of different data service providers can be improved.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subject of

steps

401 and 402 may be device a; for another example, the execution subject of step 401 may be device a, and the execution subject of step 402 may be device B; and so on.

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

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

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 50 c; a memory 50a for storing a computer program;

the processor 50b is coupled to the memory 50a and the communication component 50c for executing computer programs for: obtaining access requests for data processing services through the communication component 50 c; acquiring attribute information of a plurality of data processing service providers for providing data processing services; 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 the access request in the target access format; the data processing service of the destination data processing service provider is invoked by the communication component 50c with an access request in the destination access format.

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

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

In other embodiments, the processor 50b, when selecting the target data processing service provider from the plurality of data service providers, is specifically configured to: acquiring 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; and selecting a target data processing service provider from the plurality of data processing service providers according to the target attribute information.

Further, when the processor 50b selects a target data processing service provider from the plurality of data processing service providers according to the target attribute information, the processor is specifically configured to: for any data processing service provider, obtaining 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 a service evaluation parameter 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 carrying out weighting processing on the value attribute information and the performance attribute information aiming at any data processing service provider to obtain a service evaluation parameter aiming at any data processing service provider, acquiring the access times of a target user providing an access request aiming at 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 time quota of the target data processing type of any data processing service provider accessible by the target user; and if so, performing weighting processing on the value attribute information and the performance attribute information of any data processing service provider to obtain a service evaluation parameter of any data processing service provider. Correspondingly, 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 the attribute information of the data processing service provided by the plurality of data processing service providers, is specifically configured to: attribute information of a plurality of data processing service providers registered by a target user who provides an access request is read from a database.

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

Optionally, the processor 50b, when acquiring attribute information of a data processing service provided by a plurality of data processing service providers, is further configured to: providing dispatch query information to the client providing the access request through the communication component 50 c; the scheduling inquiry information is used for the target user to select whether to agree to invoke the data processing service provider registered by other users or not; in response to the confirmation operation of the scheduling inquiry information, attribute information of the plurality of data processing service providers registered by the target user providing the access request and the other users is acquired from the database. Or, in response to a negative operation of scheduling the inquiry information, attribute information of a plurality of data processing service providers registered by the target user who provided 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 set corresponding relation between the data processing service provider and the access format.

In some embodiments, the processor 50b is further configured to: receiving a data processing result corresponding to the access request returned by the target data processing service provider through the communication component 50 c; performing data format conversion on the data processing result to obtain a set data format; and transmitting the data processing result with the set data format to the client providing the access request through the communication component 50c, so that the client outputs the data processing result.

In some optional 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: a display component 50e and an audio component 50 f. Only some of the components are shown schematically in fig. 5, and it is not meant that the computing device must include all of the components shown in fig. 5, nor that the computing device can include only the components shown in fig. 5.

The computing device provided by the embodiment can schedule a target data processing service provider providing a data processing service for an access request according to the attribute information of a plurality of data processing service providers and the access request, aiming at the access request of the data processing service. Furthermore, a driving layer (namely a driving component) called by a data processing service interface is additionally arranged at the dispatching end, so that an 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 uniform calling of different data processing service providers is realized. For a user, the interface parameter form and the calling mode of each data processing service provider do not need to be mastered, and the convenience of service calling of different data service providers can be improved.

In embodiments of the present application, the memory is used to store computer programs and may be configured to store other various data to support operations on the device on which it is located. 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 or combination of volatile or non-volatile memory devices, 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 disks.

In the embodiments of the present application, the processor may be any hardware processing device that can execute the above described method logic. Alternatively, the processor may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or a Micro Controller Unit (MCU); programmable devices such as Field-Programmable Gate arrays (FPGAs), Programmable Array Logic devices (PALs), General Array Logic devices (GAL), Complex Programmable Logic Devices (CPLDs), etc. may also be used; or Advanced Reduced Instruction Set (RISC) processors (ARM), or System On Chips (SOC), etc., but is not limited thereto.

In embodiments of the present 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 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G, 5G or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an 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 the 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 touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

In embodiments of the present application, a power supply component is configured to provide power to various components of the device in which it is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

In embodiments of the present application, the audio component may be configured to output and/or input an audio signal. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal 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 voice recognition mode. The received audio signal may further be 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 devices with language interaction functionality, voice interaction with a user may be enabled through an audio component, and so forth.

It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

As will be appreciated by one skilled in the art, 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 so forth) 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

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

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 implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should 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; the plurality of edge nodes are used for providing data processing services; the access formats of the data services provided by the edge nodes are different;

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

2. A method of scheduling, comprising:

acquiring an access request of a data processing service;

3. The method of claim 2, further comprising:

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

the acquiring attribute information of data processing services provided by a plurality of data service providers comprises:

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

4. The method of claim 3, wherein said monitoring said plurality of data processing service providers for 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 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 destination data processing service provider from the plurality of data processing service providers based on the destination attribute information comprises:

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

weighting the value attribute information and the performance attribute information of any data processing service provider to obtain a service evaluation parameter 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 the performance attribute information for any data processing service provider to obtain the service valuation parameters for any data processing service provider, the method further comprises:

acquiring the access times of a target user providing the access request aiming at the 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 time quota of the target data processing type of any data processing service provider which can be accessed by the target user;

and if so, performing weighting processing on the value attribute information and the performance attribute information of any data processing service provider to obtain a service evaluation parameter of any data processing service provider.

8. The method of claim 2, wherein the data processing services provided by the plurality of data processing service providers are deployed at an edge node of an edge cloud network; the acquiring attribute information of data processing services provided by a plurality of data processing service providers comprises:

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

9. The method of claim 2, wherein obtaining attribute information for a plurality of data processing service providers to provide data processing services comprises:

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

and acquiring attribute information of a plurality of data processing service providers registered by the target user providing the access request and other users from a database in response to the confirmation operation of the scheduling inquiry information.

10. The method of claim 9, further comprising:

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

11. The method of claim 2, further comprising:

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

performing data format conversion on the data processing result to obtain a set data format;

and sending the data processing result with the set data format to a client side providing the access request so as to enable the client side to 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; the scheduling end comprises: the device comprises a scheduling component, a monitoring component and a driving component;

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;

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 having stored thereon computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the method of any one of claims 2-11.