CN115988087A

CN115988087A - Service calling method and device based on bus, electronic equipment and storage medium

Info

Publication number: CN115988087A
Application number: CN202310272449.2A
Authority: CN
Inventors: 苑辰; 娄双双; 孙珂; 刘捷; 吴志全; 王卿鹏; 任俊龙; 宋凯华
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2023-03-17
Filing date: 2023-03-17
Publication date: 2023-04-18
Anticipated expiration: 2043-03-17
Also published as: CN115988087B

Abstract

The disclosure provides a bus-based service calling method and device, electronic equipment and a storage medium, and relates to the technical field of artificial intelligence, in particular to cloud computing and artificial intelligence infrastructure technology. The specific implementation scheme is as follows: in response to receiving a connector call request for a first connector on a bus, determining a first adapter among at least one adapter to which the first connector is docked; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus; sending a service invocation request to the first adapter through the first connector; the first adapter is deployed in the first service supply platform, the service calling request is used for calling the platform service of the first service supply platform through the first adapter, and the first adapter is used for realizing conversion between the platform service and the first standardized service corresponding to the first connector. The method and the device can complete multi-resource access for the service demand side, and improve the resource utilization rate.

Description

Service calling method and device based on bus, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of artificial intelligence technology, and in particular, to cloud computing and artificial intelligence infrastructure technology.

Background

The construction of a smart city is a complex giant system engineering. The new Technology is endlessly developed day by day, and the technologies such as the internet, the internet of things, and the 5G (5 th Generation Mobile Communication Technology, fifth Generation Mobile Communication Technology) construct a new market environment, perception data, space-time data, an intelligent algorithm and heterogeneous computing power for the smart city, so as to form new production elements.

At present, the construction of smart cities is mainly dominated by the supply side, and is carried out around production elements from the perspective of capacity support of the production elements.

Disclosure of Invention

The disclosure provides a bus-based service calling method, a bus-based service calling device, electronic equipment and a storage medium.

According to an aspect of the present disclosure, there is provided a bus-based service invocation method, including:

in response to receiving a connector call request for a first connector on a bus, determining a first adapter among at least one adapter to which the first connector is docked; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus;

sending a service invocation request to the first adapter through the first connector; the first adapter is deployed in the first service supply platform, the service calling request is used for calling the platform service of the first service supply platform through the first adapter, and the first adapter is used for realizing conversion between the platform service and the first standardized service corresponding to the first connector.

According to another aspect of the present disclosure, there is provided a bus-based service invocation method, including:

invoking a platform service in response to receiving a service invocation request from the bus through the first adapter; the first adapter is butted with the first connector on the bus; the service invocation request is sent when the bus receives a connector invocation request for the first connector;

and the conversion between the platform service and the first standardized service corresponding to the first connector is realized through the first adapter.

According to another aspect of the present disclosure, there is provided a bus-based service invocation apparatus, including:

the adapter module is used for responding to a received connector calling request aiming at a first connector on a bus and determining the first adapter in at least one adapter butted with the first connector; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus;

the first calling module is used for sending a service calling request to the first adapter through the first connector; the first adapter is deployed in the first service supply platform, the service calling request is used for calling the platform service of the first service supply platform through the first adapter, and the first adapter is used for realizing conversion between the platform service and the first standardized service corresponding to the first connector.

the third calling module is used for responding to a service calling request received from the bus through the first adapter and calling the platform service; the system comprises a bus, a first adapter and a second adapter, wherein at least one connector corresponding to at least one standardized service respectively is deployed on the bus, and the first adapter is butted with the first connector on the bus; the service invocation request is sent when the bus receives a connector invocation request for the first connector;

and the service conversion module is used for realizing the conversion between the platform service and the first standardized service corresponding to the first connector through the first adapter.

According to another aspect of the present disclosure, there is provided an electronic device including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of any of the embodiments of the present disclosure.

According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform a method according to any one of the embodiments of the present disclosure.

According to another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of the embodiments of the present disclosure.

According to the technical scheme, at least one connector corresponding to at least one standardized service is configured on a bus, the connector is in butt joint with at least one adapter, the adapter is arranged in a service supply platform, so that platform services of the service supply platform are called through the adapter by sending a service calling request to the adapter, and conversion between the platform services and the standardized services is completed through the adapter. Based on the method, the bus can build a bridge between the cross-platform distributed resources on the supply side and the service demand side, so that the access of multiple resources is completed on the service demand side, and the resource utilization rate is improved. And the service adaptation process of each supply platform is deployed in the supply platform, so that the organization is light, and the response efficiency of intelligent service can be improved.

It should be understood that the statements in this section are not intended to identify key or critical features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1 is a schematic flowchart of a bus-based service invocation method according to an embodiment of the present disclosure;

FIG. 2 is a schematic diagram of an exemplary application scenario of a bus-based service invocation method of the disclosed embodiments;

FIG. 3 is a schematic diagram of an application example of a bus-based service invocation method according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of the relevant components of a connector in an application example;

FIG. 5 is a diagram of a scheduler in an example application of the disclosed embodiments;

FIG. 6 is a schematic diagram of another application example of a bus-based service invocation method according to an embodiment of the present disclosure;

FIG. 7 is a flowchart illustrating a bus-based service invocation method according to another embodiment of the present disclosure;

FIG. 8 is a schematic diagram of another application example of the bus-based service invocation method according to the disclosed embodiment;

FIG. 9 is a schematic block diagram of a bus-based service invocation apparatus provided by an embodiment of the present disclosure;

FIG. 10 is a schematic block diagram of a bus-based service invocation apparatus provided by another embodiment of the present disclosure;

FIG. 11 is a schematic block diagram of a bus-based service invocation apparatus provided by another embodiment of the present disclosure;

FIG. 12 is a schematic block diagram of a bus-based service invocation apparatus provided by another embodiment of the present disclosure;

FIG. 13 is a block diagram of an electronic device for implementing a bus-based service invocation method of an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, it will be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. The term "at least one" herein means any combination of any one or more of a plurality, for example, including at least one of a, B, C, and may mean including any one or more elements selected from the group consisting of a, B, and C. The terms "first" and "second" used herein refer to and distinguish one from another in the similar art, without necessarily implying a sequence or order, or implying only two, such as first and second, to indicate that there are two types/two, first and second, and first and second may also be one or more.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the subject matter of the present disclosure.

Fig. 1 shows a flowchart of a bus-based service invocation method according to an embodiment of the present disclosure. The bus may refer to a service module for providing unified adaptation and docking of different platforms, and may also be referred to as an intelligent bus. In some examples, the bus may provide a fully resource collaborative development and execution environment for smart city scene applications with converged support. Illustratively, the bus may be integrated within a terminal, server cluster, or other processing device.

In the disclosed embodiment, at least one connector corresponding to at least one standardized service, respectively, is disposed on the bus. Each of the at least one connector is mateable with at least one adapter configured in the service provisioning platform for effecting a conversion between the platform service of the service provisioning platform and the standardized service. As shown in fig. 1, the method may include:

step S110, in response to receiving a connector calling request aiming at a first connector on a bus, determining a first adapter in at least one adapter in butt joint with the first connector;

step S120, sending a service calling request to the first adapter through the first connector; the first adapter is deployed in the first service supply platform, the service calling request is used for calling the platform service of the first service supply platform through the first adapter, and the first adapter is used for realizing conversion between the platform service and the first standardized service corresponding to the first connector.

In the embodiment of the present disclosure, the service provision platform may refer to a platform for providing a service related to an intelligent algorithm. For example, the service provisioning platform may include an algorithm platform, a computing power platform, a data platform, and the like. Optionally, the bus may abstract the service standard definition of each service provisioning platform, forming at least one standardized service, thereby forming at least one connector; each service supply platform includes an algorithm, a calculation power, data, video, space-time, a map, a block chain, an IOT (Internet of Things), and the like.

Illustratively, the connector may include a standardized service interface on the bus for accessing each service provisioning platform. Alternatively, one connector may include a plurality of APIs (Application Programming interfaces) for calling the service provisioning platform to implement various operations. For example, computing platform workload connectors may be used to implement connector actions such as load creation, querying, updating, deletion, instance querying, load computing monitoring querying, and the like.

In the step S110, the connector invocation request may be sent by the service requirement platform to the first connector on the bus. Alternatively, the service requirement platform may be an application platform, an algorithm platform, a data platform, or the like. For example, the service requirement platform is an application platform such as an electronic map server and a search engine server, and sends a connector call request to a first connector on the bus to obtain a relevant data service. For another example, the service requirement platform is an algorithm platform, and sends a connector call request to a first connector on the bus to obtain the relevant computing service.

In practical application, the bus maintains each connector, each service supply platform can complete service access serving as a subordinate platform through the bus service register by referring to various connectors preset on the bus, and an adapter in butt joint with the connector is configured, so that service capability conversion between platform service and standardized service is completed through the adapter. Optionally, the service capability conversion includes parameter mapping, merging, fusing, and the like. For example, the adapter is used for converting a service calling request issued by a standardized service interface on the connector into a personalized service calling request conforming to the interface definition of the service supply platform; and the return result which is output by the service supply platform and conforms to the platform interface definition is converted into a return result which is sent to the standardized service interface on the connector.

Illustratively, one connector may interface with one or more adapters. The adapters can be deployed in different service supply platforms to realize access of multiple platforms to the same standardized service.

Optionally, in the above method steps, the first connector may be any one of connectors disposed on the bus, and accordingly, the first adapter may be any one of adapters that interface with the first connector. In practical applications, the bus may provide the upper layer service with the connector and the related declaration of the standardized service corresponding to the connector, so that the upper layer service can call the corresponding connector according to the actual service requirement. According to the method steps, when a connector calling request for any connector is received, one adapter can be determined from a plurality of adapters butted by the connector, then the platform service is called through the adapter, and simultaneously conversion between the platform service and the standardized service is completed based on the adapter.

It can be seen that, in the method provided by the above embodiment, the bus can build a bridge between the cross-platform distributed resources on the supply side and the service demand side, so as to complete access of multiple resources for the service demand side, and improve the resource utilization rate. And the service adaptation process of each supply platform is deployed in the supply platform, so that the organization is light, and the response efficiency of intelligent service can be improved.

FIG. 2 is a schematic diagram of an exemplary application scenario of a bus-based service invocation method in accordance with an embodiment of the present disclosure. As shown in FIG. 2, a bus 200 is disposed between the platforms. The computation bin 210 is the lowest service provisioning platform. The bus may send a service invocation request to computing bin 210 when data bin 220, algorithm bin 230, application bin 240, etc. initiate a connector invocation request for computing services to the bus, to cause computing bin 210 to provide computing services based on the corresponding adapter. Optionally, as shown in fig. 2, the data bin 220 may also serve as a service provisioning platform for providing data services for logic calls by the algorithm bin 230 or the application bin 240. Algorithm silo 230 may also serve as a service provisioning platform for providing algorithm services for logical calls to application silo 240. The logic call may be implemented via the smart bus 200.

Specifically, as shown in fig. 2, a converged workbench SDK (Software Development Kit) is integrated in each platform, and the converged workbench SDK includes program modules related to the intelligent bus and is used for completing processing procedures such as adapter configuration, service invocation, service capability conversion and the like. The intelligent bus 200 can adopt a similar Mongo architecture to transmit information with each platform, so as to drive each platform to execute related services based on the fusion workbench SDK. Optionally, in the service process, if information with a large data amount needs to be interacted between the platforms, the intelligent bus 200 may further instruct the platforms to implement information transmission between the platforms through a Hadoop-like architecture in the process of executing the relevant service. In this application example, a fusion workbench may be further configured to implement management and control of the smart bus 200, for example, development, joint debugging and testing of the smart bus 200 are implemented based on the fusion workbench.

In an exemplary embodiment, determining a first adapter in at least one adapter with which the first connector is mated may include: and under the condition that the connector calling request contains adapter indication information, determining the first adapter in at least one adapter which is butted with the first connector according to the adapter indication information.

For example, the bus may provide a declaration of the relevant service to the upper layer, so that the service requirement platform may query the connector and the corresponding adapter, and may carry adapter indication information in initiating the connector invocation request to indicate the adapter desired to be invoked.

By adopting the embodiment, each service demand platform can designate the adapter, so that the service with high adaptability is further provided from the service demand side, the service demands are favorably surrounded, the high-efficiency convergence and multiplexing of various cross-organization and cross-level digital elements are favorably realized, and the construction of a smart city is favorably realized.

In an exemplary embodiment, determining the first adapter in the at least one adapter with which the first connector is mated may include: and under the condition that the connector calling request does not contain adapter indication information, determining a first adapter in at least one adapter which is butted by the first connector according to a pre-configured load distribution strategy.

Illustratively, the load distribution policy may include one or more of polling, weighting, random, and assigned affinity.

By adopting the embodiment, the first adapter can be automatically determined based on the load distribution strategy under the condition that the service demand platform does not specify the adapter. Therefore, load balancing can be realized, and the service response efficiency can be improved.

In an exemplary embodiment, the bus-based service calling method may further include: storing the log information corresponding to the connector calling request in a preset database; wherein the log information comprises information related to the first adapter.

By adopting the embodiment, the relevant information of the adapter used in each service calling process can be stored, so that the called adapter information can be inquired, and the maintainability of the bus is improved. And the called adapter information can be read in the subsequent service calling process, so that the load balance is better realized.

In an exemplary embodiment, a connector configuration is also provided. Illustratively, the bus-based service calling method may further include: determining at least one standardized service based on the platform type and the service type of each of at least one service supply platform accessing the bus; at least one connector is configured based on the at least one standardized service.

Illustratively, the platform type may include information embodying a high cohesion of the platform service, such as algorithms, computing power, applications, data, and the like. The service types may include types of specific services under each platform type, such as load-related services, instance-related services, monitoring-related services, and the like under the computing platform; task algorithm related services, task plan related services, algorithm database related services and the like under the algorithm platform; video streaming related services, structured file related services, etc. under the data platform.

By summarizing each platform type and each service type accessed, at least one standardized service which is different from each other can be abstracted, so that a corresponding connector is configured for each standardized service. According to the embodiment, the coverage of standardized service can be improved, more comprehensive resources can be provided for the service demand side, and therefore the smart city construction can be realized.

In an exemplary embodiment, the bus-based service invocation method may further include: providing each platform with release information for each of the at least one connector; and the release information is used for indicating each platform to configure the adapter which is butted with each connector.

For example, the publishing information of each connector may include declaration information of the standardized service corresponding to the connector. In this way, each platform can design a conversion mode between the standardized service and the platform service according to the declaration information, thereby configuring the adapter.

Optionally, the release information of each connector may further include one or more information such as metadata information of the connector, an adapter to which the connector is docked, and platform information to which the adapter belongs, so that the service demand side can understand the standardized service corresponding to each connector and compare the standardized service with each adapter.

By adopting the embodiment, the service supply platform can complete the accurate configuration of the adapter, thereby accurately completing the access of multiple resources and improving the resource utilization rate. Meanwhile, the service demand side can inquire and call the related connector according to the actual demand, and the service calling efficiency and the success rate are improved.

In an exemplary embodiment, the bus-based service invocation method may further include: periodically reading metadata information of each connector in a preset database; determining the state of each connector according to the metadata information; and updating the distribution information of each connector according to the state of each connector.

By adopting the embodiment, the bus can pull the metadata information of each connector at regular time, so that the interface states of multiple platforms or multiple applications at the subordinate level of the bus can be sensed sensitively, the release information can be updated timely, the service requirement can be sensed timely, and the service calling efficiency and the success rate can be improved.

To facilitate understanding of the foregoing embodiments, fig. 3 is a schematic diagram illustrating an application example of the bus-based service invocation method according to the embodiment of the present disclosure. As shown in fig. 3, the method comprises the following steps implemented on the bus operator side:

s301, creating a platform type. Specifically, the platform type may be created according to the accessed platform corresponding to the new type.

S302, configuring the platform type.

S303, creating a service type. Specifically, the creation of the service type may be performed according to the platform type.

S304, configuring the service type. In particular, the division of standardized services may be made according to the type of service created.

S305, creating a connector. Specifically, a corresponding connector is created for each standardized service.

And S306, entering the parameters by editing the connector.

And S307, outputting the parameters by the editing connector.

S308, issuing a connector.

The method further comprises the following steps implemented at the service provisioning side:

s309, building an adapter. Specifically, the adapter corresponding to the connector is newly created according to the release information of the connector.

And S310, judging whether the API is single or multiple. Specifically, it is determined whether the connector involves one or more APIs.

And S311, under the condition that the judgment result is the single API, newly building the single API.

And S312, establishing the multi-API under the condition that the judgment result is the multi-API.

And S313, configuring the adapter API attribute.

And S314, configuring adapter API mapping. Specifically, the API mapping of the adapter is configured according to the API to which the connector relates and the API of the service provisioning platform.

After the service supply platform completes the configuration, the configuration related information is returned to the connector market, so that the adapter related information is added to the issued information of the connector.

The method further comprises the following steps implemented at the service requirement side:

and S315, inquiring the connector. Specifically, the corresponding connector is queried according to the service requirements.

And S316, judging the state of the connector. Specifically, whether to invoke is confirmed according to the connector status.

And S317, selecting a connector.

S318, determining whether the adapter is designated.

And S319, judging the adapter state. Specifically, whether to invoke is confirmed according to the adapter status.

And S320, using a connector. In particular, the adapter or bus may be specified to determine the adapter using a load policy.

Fig. 4 shows a schematic diagram of relevant components of a connector in an application example. As shown in fig. 4, the related components include a metadata management component 401, an authentication component 402, a connector forwarding component 403, a load balancing component 404, a parameter mapping component 405, a log management component 406, and a timing pull component. The metadata management component 401 is configured to implement configuration management of the connector and the adapter, and write metadata information of the connector into a preset database, which is exemplified by a MySql database in fig. 4. The authentication component 402 is configured to provide a unified authentication function to authenticate the service requirements platform when receiving the connector invocation request. Connector forwarding component 403 is used to forward the request for the connector to the adapter. The connector forwarding component 403 needs to invoke the load balancing component 404 to cause the load balancing component 404 to select the desired adapter through the load policy and return information about the adapter. Thereafter, the connector forwarding component 403 forwards the request of the connector to the adapter according to the relevant information of the adapter. Parameter mapping component 405 is used to convert the adapter join, leave join configuration to a desired result. The log management component 406 is used for recording the call log and writing the call log into a preset database. For example, the adapter information is recorded for each connector call. The timing pull component 407 is used to pull the metadata information of the connector at a timing and sense the state of the connector at a timing.

Optionally, in some embodiments of the present disclosure, the bus-based service invocation method further provides a dispatch flow-based service invocation. Illustratively, the method may further comprise: in response to receiving a scheduler call request for a first scheduler on the bus, executing a first scheduled flow based on the first scheduler, wherein the first scheduled flow is scheduled based on at least one standardized service; when the first scheduler flow includes an execution node corresponding to the second standardized service, a connector call request is transmitted to a second connector corresponding to the second standardized service by the first scheduler.

For example, in the embodiment of the present disclosure, the dispatch flow may be a traffic flow organized by a plurality of connectors or a plurality of standardized services, and may be served as a dispatch flow service. The scheduler is a connection for implementing a scheduled flow service, i.e. a cross-platform service connection for implementing different services, and may contain one or more implementation programs for scheduled flows. That is, the bus provides a dispatch flow for defining a cross-platform service that combines multiple connectors in series according to business intent.

In the method, the first scheduler is configured to execute the first scheduled flow, and when the first scheduled flow is executed to an execution node corresponding to the second standardized service in the first scheduled flow, the first scheduler sends a connector call request to the second connector corresponding to the second standardized service. In this way, when a connector call request for the second connector is received, the second adapter is determined in at least one adapter to which the second connector is mated, so that the execution node is completed by calling the second adapter. By analogy, similar processes are implemented for each execution node in the first dispatch flow, so that dispatch flow service can be completed.

According to the method, the bus can provide services outwards in the form of scheduling stream services, namely cross-platform service resource providing of single service can be provided, and full-mode resource providing of multiple services can be provided. Based on the method, the calling mode of the service demand side can be simplified, and the service demand side can obtain efficient service experience.

In an exemplary embodiment, in a case where the first scheduler flow includes an execution node corresponding to the second standardized service, sending, by the first scheduler, a connector invocation request to a second connector corresponding to the second standardized service includes: when the first scheduling flow comprises an execution node corresponding to the second standardized service, determining a second service supply platform from at least one service supply platform for realizing the second standardized service through a platform selector in the first scheduler; and sending a connector calling request to the second connector through an actuator in the first scheduler, wherein the connector calling request comprises adapter indication information, and the adapter indication information is used for indicating the second connector to call the second adapter corresponding to the second service supply platform.

In this embodiment, the first scheduler includes a platform selector, and the first scheduler may determine a second adapter for executing a second standardized service in the current scheduling flow, and then carry the adapter indication information in the connector invocation request. In this way, when the second connector receives the connector call request, the corresponding second adapter may be determined according to the adapter indication information.

Fig. 5 shows a schematic diagram of a scheduler in an application example of the embodiment of the present disclosure. As shown in fig. 5, a plurality of components are included in the scheduler, such as a scheduler instantiation component 501, a platform selector 502, an executor 503, a result encapsulation component 504, and the like. The scheduler may provide scheduler service interfaces for mirror upload, mirror state query, workload creation, workload deletion, and the like. The scheduler instantiation component 501 is used to instantiate a standardized scheduling flow according to a scheduler call request on the scheduler service interface. The platform selector 502 is used to select a service provisioning platform of the execution node, for example, a specific platform, a full platform, or an optimal platform may be selected. The executor 503 is used to send a connector invocation request to a connector, such as a mirror verification connector, a mirror pull connector, a mirror state connector, a workload connector, etc. The results encapsulation component 504 is used to encapsulate the results returned by the connector upwards, resulting in processing results returned to the service interface.

By adopting the embodiment, the adapters for realizing the service can be uniformly determined according to the requirements of the dispatching flow, so that the accurate execution of the whole dispatching flow is ensured, and the service efficiency and the accuracy are improved.

In an exemplary embodiment, the bus-based service calling method may further include: storing the log information corresponding to the scheduler calling request in a preset database; wherein the log information includes information about the second connector and the second adapter.

By adopting the embodiment, the related information of the connector and the adapter used in the calling process of each scheduling flow can be stored, so that the called information can be inquired, and the maintainability of the bus is improved. And the called adapter information can be read in the subsequent service calling process, so that the load balance is better realized.

FIG. 6 is a schematic diagram illustrating another example application of a bus-based service invocation method according to an embodiment of the present disclosure. As shown in fig. 6, the method comprises the following steps implemented on the bus operator side:

s601, creating a scheduler.

S602, a scheduler is configured.

And S603, generating a scheduler list.

s604, inquiring a dispatcher.

S605, judging the state of the scheduler. Specifically, whether to make a call is confirmed according to the scheduler status.

S606, using a scheduler. Specifically, a scheduler call request is initiated to the bus.

The method further comprises the following steps implemented at the bus operator side:

s607, inquiring the scheduler to execute the record.

And S608, judging whether the number of days is larger than a preset number of days, such as 180 days.

And S609, under the condition that the number of days is not more than the preset number of days, confirming that the expected execution record is reserved in the database, and checking the execution record of the scheduler.

Corresponding to the method implemented on the bus side, the embodiment of the present disclosure further provides a method implemented by the service provisioning platform. Fig. 7 illustrates a bus-based service invocation method provided by another embodiment of the present disclosure. As shown in fig. 7, the method includes:

s710, responding to a service calling request received from a bus through a first adapter, and calling platform service; the first adapter is butted with the first connector on the bus; the service invocation request is sent when the bus receives a connector invocation request for the first connector;

s720, conversion between the platform service and the first standardized service corresponding to the first connector is achieved through the first adapter.

Optionally, the method may further include:

acquiring issuing information of a first connector on a bus;

based on the release information, the first adapter is configured.

The implementation process and technical details of each step in the above method may refer to the corresponding descriptions in the foregoing implementation embodiments and application examples, that is, the method of this embodiment may be combined with the foregoing implementation embodiments and application examples, and are not described in detail herein.

According to the embodiment, the bus can build a bridge between the cross-platform distributed resources on the supply side and the service demand side, so that the access of multiple resources is completed on the service demand side, and the resource utilization rate is improved. And the service adaptation process of each supply platform is deployed in the supply platform, so that the organization is light, and the response efficiency of intelligent service can be improved.

Another example of an application in a specific business scenario is provided below to more clearly understand the method of the disclosed embodiments.

Fig. 8 is a schematic diagram illustrating another application example of the bus-based service invocation method according to the embodiment of the present disclosure. As shown in FIG. 8, multiple platforms in the platform group can access the city intelligent bus, wherein the A department provides the push work order message service, the B group provides the video data stream service, the C company provides the accident detection algorithm service, the D organization provides the GPU computing power service, the E center provides the NPU computing power service, and the F institution provides the work order classification identification service. The urban intelligent bus configures corresponding connectors based on each service, for example, a detection algorithm-GPU connector is configured according to the calculation force requirement of the detection algorithm on the GPU; and configuring a real-time video stream subscriber according to the requirement of a detection algorithm on the video data stream. In practical application, the intelligent service can be used for automatically detecting urban road grid events across modalities and intelligently distributing cases. Specifically, under the condition that an accident vehicle is found, a detection algorithm-GPU connector is called, and GPU computing power resources of a D mechanism are applied to complete the deployment of algorithm services. And acquiring the required video stream from the group B through an accident detection algorithm of a real-time video stream subscriber for company C.

According to the embodiment of the disclosure, the disclosure further provides a service calling device based on the bus. Fig. 9 shows a schematic block diagram of a bus-based service invocation device provided by an embodiment of the present disclosure. As shown in fig. 9, the apparatus includes:

an adaptation module 910, configured to determine, in response to receiving a connector call request for a first connector on a bus, a first adapter among at least one adapter to which the first connector is mated; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus;

a first invoking module 920, configured to send a service invoking request to the first adapter through the first connector; the first adapter is deployed in the first service supply platform, the service calling request is used for calling the platform service of the first service supply platform through the first adapter, and the first adapter is used for realizing conversion between the platform service and the first standardized service corresponding to the first connector.

Optionally, the adaptation module 910 is configured to:

and under the condition that the connector calling request contains adapter indication information, determining the first adapter in at least one adapter which is butted with the first connector according to the adapter indication information.

Optionally, the adaptation module 910 is configured to:

and under the condition that the connector calling request does not contain adapter indication information, determining a first adapter in at least one adapter butted by the first connector according to a pre-configured load distribution strategy.

Optionally, fig. 10 shows a schematic block diagram of a bus-based service invocation device provided by another embodiment of the present disclosure. As shown in fig. 10, the apparatus may further include:

a first log module 1010, configured to store log information corresponding to the connector call request in a preset database; wherein the log information comprises information related to the first adapter.

Optionally, as shown in fig. 10, the apparatus may further include:

a service determination module 1020, configured to determine at least one standardized service based on a platform type and a service type of each of at least one service provisioning platform accessing the bus;

a connector configuration module 1030 for configuring at least one connector based on the at least one standardized service.

Optionally, as shown in fig. 10, the apparatus may further include:

a publishing module 1040, configured to provide publishing information of each connector in the at least one connector to each platform; and the release information is used for indicating each platform to configure the adapter which is butted with each connector.

Optionally, as shown in fig. 10, the apparatus may further include:

a reading module 1050, configured to periodically read metadata information of each connector in a preset database;

a status determination module 1060, configured to determine the status of each connector according to the metadata information;

the status updating module 1070 is configured to update the distribution information of each connector according to the status of each connector.

Optionally, as shown in fig. 10, the apparatus may further include:

a scheduling module 1080 for executing a first scheduled flow based on a first scheduler in response to receiving a scheduler call request for the first scheduler on the bus; wherein the first dispatch flow is arranged based on at least one standardized service;

a second invoking module 1090, configured to send, by the first scheduler, a connector invocation request to a second connector corresponding to the second standardized service when the first scheduled flow includes an execution node corresponding to the second standardized service.

Optionally, as shown in fig. 10, the second invoking module 1090 includes:

a platform selecting unit 1091, configured to determine, by a platform selector in the first scheduler, a second service provision platform among the at least one service provision platform for implementing the second standardized service, when the first scheduler flow includes an execution node corresponding to the second standardized service;

a connector invoking unit 1092, configured to send a connector invoking request to the second connector through the executor in the first scheduler, where the connector invoking request includes adapter indication information, and the adapter indication information is used to indicate the second connector to invoke the second adapter corresponding to the second service provision platform.

Optionally, as shown in fig. 10, the apparatus may further include:

the second log module 1000 is configured to store log information corresponding to the scheduler call request in a preset database; wherein the log information includes information about the second connector and the second adapter.

According to the embodiment of the disclosure, the disclosure further provides a service calling device based on the bus. Fig. 11 shows a schematic block diagram of a bus-based service invocation device provided by an embodiment of the present disclosure. As shown in fig. 11, the apparatus includes:

a third calling module 1110, configured to call a platform service in response to receiving a service call request from the bus through the first adapter; the first adapter is butted with the first connector on the bus; the service invocation request is sent when the bus receives a connector invocation request for the first connector;

the service conversion module 1120 is configured to implement conversion between the platform service and a first standardized service corresponding to the first connector through the first adapter.

Optionally, fig. 12 shows a schematic block diagram of a bus-based service invocation device provided by another embodiment of the present disclosure. As shown in fig. 12, the apparatus may further include:

an obtaining module 1210, configured to obtain issue information of a first connector on a bus;

an adapter configuration module 1220 for configuring the first adapter based on the publishing information.

For a description of specific functions and examples of each module and sub-module of the apparatus in the embodiment of the present disclosure, reference may be made to the description of corresponding steps in the foregoing method embodiments, and details are not repeated here.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

Fig. 13 illustrates a schematic block diagram of an example electronic device 1300 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 13, the apparatus 1300 includes a computing unit 1301 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 1302 or a computer program loaded from a storage unit 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for the operation of the device 1300 can also be stored. The calculation unit 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.

A number of components in the device 1300 connect to the I/O interface 1305, including: an input unit 1306 such as a keyboard, a mouse, or the like; an output unit 1307 such as various types of displays, speakers, and the like; storage unit 1308, such as a magnetic disk, optical disk, or the like; and a communication unit 1309 such as a network card, modem, wireless communication transceiver, etc. A communication unit 1309 allows the device 1300 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

Computing unit 1301 may be a variety of general and/or special purpose processing components with processing and computing capabilities. Some examples of computing unit 1301 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. Computing unit 1301 performs the various methods and processes described above, such as bus-based service invocation methods. For example, in some embodiments, the bus-based service invocation method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 1308. In some embodiments, some or all of the computer program may be loaded onto and/or installed onto device 1300 via ROM 1302 and/or communications unit 1309. When the computer program is loaded into RAM 1303 and executed by computing unit 1301, one or more steps of the bus-based service invocation method described above may be performed. Alternatively, in other embodiments, computing unit 1301 may be configured in any other suitable manner (e.g., by way of firmware) to perform a bus-based service invocation method.

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel or sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A bus-based service invocation method, comprising:

in response to receiving a connector call request for a first connector on a bus, determining a first adapter among at least one adapter with which the first connector is docked; wherein at least one connector corresponding to at least one standardized service is deployed on the bus;

sending a service invocation request to the first adapter through the first connector; the first adapter is deployed in a first service provisioning platform, the service invocation request is used for invoking a platform service of the first service provisioning platform through the first adapter, and the first adapter is used for realizing conversion between the platform service and a first standardized service corresponding to the first connector.

2. The method of claim 1, wherein said determining a first adapter among the at least one adapter with which the first connector is mated comprises:

and under the condition that the connector calling request contains adapter indication information, determining the first adapter in at least one adapter in the first connector butt joint according to the adapter indication information.

3. The method of claim 1 or 2, wherein said determining a first adapter among the at least one adapter with which the first connector is docked comprises:

and under the condition that the connector calling request does not contain adapter indication information, determining the first adapter in at least one adapter which is butted by the first connector according to a pre-configured load distribution strategy.

4. The method of claim 1 or 2, further comprising:

storing the log information corresponding to the connector calling request in a preset database; wherein the log information comprises information related to the first adapter.

5. The method of claim 1 or 2, further comprising:

determining at least one standardized service based on the platform type and the service type of each of at least one service supply platform accessing the bus;

configuring the at least one connector based on the at least one standardized service.

6. The method of claim 5, further comprising:

providing the published information for each of the at least one connector to the platforms; wherein the release information is used for indicating each platform to configure the adapter which is in butt joint with each connector.

7. The method of claim 6, further comprising:

periodically reading metadata information of each connector in a preset database;

determining the state of each connector according to the metadata information;

and updating the release information of each connector according to the state of each connector.

8. The method of claim 1 or 2, further comprising:

in response to receiving a scheduler call request for a first scheduler on a bus, executing a first scheduled flow based on the first scheduler; wherein the first scheduled flow is arranged based on at least one standardized service;

when the first dispatch flow includes an execution node corresponding to a second standardized service, a connector invocation request is sent by the first dispatcher to a second connector corresponding to the second standardized service.

9. The method of claim 8, wherein said sending, by the first scheduler, a connector invocation request to a second connector corresponding to a second standardized service if the first scheduled flow contains an execution node corresponding to the second standardized service comprises:

when the first scheduling flow comprises an execution node corresponding to a second standardized service, determining a second service supply platform from at least one service supply platform for realizing the second standardized service through a platform selector in the first scheduler;

and sending a connector calling request to the second connector through an executor in the first scheduler, wherein the connector calling request comprises adapter indication information, and the adapter indication information is used for indicating the second connector to call a second adapter corresponding to the second service provision platform.

10. The method of claim 9, further comprising:

storing the log information corresponding to the scheduler calling request in a preset database; wherein the log information includes information about the second connector and the second adapter.

11. A bus-based service invocation method, comprising:

invoking a platform service in response to receiving a service invocation request from the bus through the first adapter; the first adapter is connected with the first connector on the bus in an abutting mode; the service invocation request is sent when the bus receives a connector invocation request for the first connector;

and converting the platform service and the first standardized service corresponding to the first connector through the first adapter.

12. The method of claim 11, further comprising:

acquiring issuing information of the first connector on the bus;

configuring the first adapter based on the release information.

13. A bus-based service invocation apparatus, comprising:

the system comprises an adaptation module, a first processing module and a second processing module, wherein the adaptation module is used for determining a first adapter in at least one adapter in butt joint with a first connector in response to receiving a connector calling request aiming at the first connector on a bus; wherein at least one connector corresponding to at least one standardized service is deployed on the bus;

the first calling module is used for sending a service calling request to the first adapter through the first connector; the first adapter is deployed in a first service provisioning platform, the service invocation request is used for invoking a platform service of the first service provisioning platform through the first adapter, and the first adapter is used for realizing conversion between the platform service and a first standardized service corresponding to the first connector.

14. The apparatus of claim 13, wherein the adaptation module is to:

15. The apparatus of claim 13 or 14, wherein the adaptation module is to:

16. The apparatus of claim 13 or 14, further comprising:

the first log module is used for storing log information corresponding to the connector calling request into a preset database; wherein the log information comprises information related to the first adapter.

17. The apparatus of claim 13 or 14, further comprising:

the service determining module is used for determining at least one standardized service based on the platform type and the service type of each platform in at least one service supply platform accessed to the bus;

a connector configuration module to configure the at least one connector based on the at least one standardized service.

18. The apparatus of claim 17, further comprising:

the release module is used for providing release information of each connector in the at least one connector for each platform; wherein the release information is used for indicating each platform to configure the adapter which is in butt joint with each connector.

19. The apparatus of claim 18, further comprising:

the reading module is used for periodically reading the metadata information of each connector in a preset database;

the state determining module is used for determining the state of each connector according to the metadata information;

and the state updating module is used for updating the release information of each connector according to the state of each connector.

20. The apparatus of claim 13 or 14, further comprising:

a scheduling module to execute a first scheduled flow based on a first scheduler on a bus in response to receiving a scheduler call request for the first scheduler; wherein the first scheduled flow is arranged based on at least one standardized service;

a second invoking module for sending, by the first scheduler, a connector invocation request to a second connector corresponding to a second standardized service if the first scheduled flow includes an execution node corresponding to the second standardized service.

21. The apparatus of claim 20, wherein the second calling module comprises:

a platform selection unit, configured to determine, by a platform selector in the first scheduler, a second service provision platform among at least one service provision platform for implementing a second standardized service when the first scheduler stream includes an execution node corresponding to the second standardized service;

and a connector calling unit, configured to send a connector calling request to the second connector through an executor in the first scheduler, where the connector calling request includes adapter indication information, and the adapter indication information is used to indicate the second connector to call a second adapter corresponding to the second service provision platform.

22. The apparatus of claim 21, further comprising:

the second log module is used for storing the log information corresponding to the scheduler calling request in a preset database; wherein the log information includes information about the second connector and the second adapter.

23. A bus-based service invocation apparatus, comprising:

the third calling module is used for responding to a service calling request received from the bus through the first adapter and calling the platform service; the first adapter is connected with the first connector on the bus in an abutting mode; the service invocation request is sent when the bus receives a connector invocation request for the first connector;

24. The apparatus of claim 23, further comprising:

the acquisition module is used for acquiring the release information of the first connector on the bus;

and the adapter configuration module is used for configuring the first adapter based on the release information.

25. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-12.

26. A non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1-12.

27. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-12.