CN115988087B - Service calling method and device based on bus, electronic equipment and storage medium - Google Patents
Service calling method and device based on bus, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115988087B CN115988087B CN202310272449.2A CN202310272449A CN115988087B CN 115988087 B CN115988087 B CN 115988087B CN 202310272449 A CN202310272449 A CN 202310272449A CN 115988087 B CN115988087 B CN 115988087B
- Authority
- CN
- China
- Prior art keywords
- connector
- service
- adapter
- platform
- bus
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Stored Programmes (AREA)
Abstract
本公开提供了一种基于总线的服务调用方法、装置、电子设备和存储介质，涉及人工智能技术领域，尤其涉及云计算、人工智能基础设施技术。具体实现方案为：响应于接收到针对总线上的第一连接器的连接器调用请求，在第一连接器对接的至少一个适配器中，确定出第一适配器；其中，总线上部署有与至少一个标准化服务分别对应的至少一个连接器；通过第一连接器向第一适配器发送服务调用请求；其中，第一适配器部署于第一服务供给平台中，服务调用请求用于通过第一适配器调用第一服务供给平台的平台服务，第一适配器用于实现平台服务与第一连接器所对应的第一标准化服务之间的转换。本公开可以为服务需求侧完成多资源的接入，提升资源利用率。
The present disclosure provides a bus-based service invocation method, device, electronic equipment and storage medium, and relates to the technical field of artificial intelligence, in particular to cloud computing and artificial intelligence infrastructure technology. The specific implementation solution is: in response to receiving a connector call request for the first connector on the bus, determine the first adapter among at least one adapter docked with the first connector; wherein, the bus is deployed with at least one At least one connector corresponding to the standardized service; a service call request is sent to the first adapter through the first connector; wherein, the first adapter is deployed on the first service supply platform, and the service call request is used to call the first adapter through the first adapter. The service provides platform services of the platform, and the first adapter is used to implement conversion between the platform services and the first standardized services corresponding to the first connector. The disclosure can complete multi-resource access for the service demand side and improve resource utilization.
Description
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 smart cities is a complex giant system project. The new technology is endless, and the technologies such as the Internet, the Internet of things, 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) and the like build new market environments, perception data, space-time data, intelligent algorithms and heterogeneous computing power for smart cities to form new production elements.
At present, the construction of a smart city is mainly conducted by a supply side, and the construction is conducted around a production element from the viewpoint of the capability support of the production element.
Disclosure of Invention
The present disclosure provides a service calling method, apparatus, electronic device and storage medium based on a bus.
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 call request to a first adapter through a first connector; the first adapter is deployed in the first service supply platform, the service call request is used for calling 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 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:
in response to receiving a service invocation request from the bus through the first adapter, invoking a platform service; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus, and the first adapter is in butt joint with the first connector on the bus; the service call request is sent when the bus receives a connector call request for the first connector;
and converting 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 a bus-based service invocation apparatus including:
an adaptation module, configured to determine a first adapter in at least one adapter that is docked with the first connector in response to receiving a connector call request for the first connector on the 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 the first service supply platform, the service call request is used for calling 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 first standardized service corresponding to the first connector.
According to another aspect of the present disclosure, there is provided a bus-based service invocation apparatus including:
the third calling module is used for calling the platform service in response to receiving a service calling request from the bus through the first adapter; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus, and the first adapter is in butt joint with the first connector on the bus; the service call request is sent when the bus receives a connector call request for the first connector;
and the service conversion module is used for realizing 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 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 the embodiments of the present disclosure.
According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing the 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 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 deployed in a service supply platform, so that platform service of the service supply platform is called through the adapter by sending a service call request to the adapter, and conversion between the platform service and the standardized service is completed through the adapter. Based on the method, the bus can build a bridge between the cross-platform distributed resources of the supply side and the service demand side, complete multi-resource access 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 the intelligent service can be improved.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a flow diagram of a bus-based service invocation method provided by an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of one exemplary application scenario of a bus-based service invocation method of an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of one example application of a bus-based service invocation method of 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 schematic diagram of a scheduler in one example application of an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of another example application of a bus-based service invocation method, according to an embodiment of the present disclosure;
FIG. 7 is a flow diagram of a bus-based service invocation method provided by another embodiment of the present disclosure;
FIG. 8 is a schematic diagram of another example application of a bus-based service invocation method of an embodiment of the present disclosure;
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 used to implement a bus-based service invocation method of an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made 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" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. The term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, e.g., including at least one of A, B, C, may mean including any one or more elements selected from the group consisting of A, B and C. The terms "first" and "second" herein mean a plurality of similar technical terms and distinguishes them, and does not limit the meaning of the order, or only two, for example, a first feature and a second feature, which means that there are two types/classes of features, the first feature may be one or more, and the second feature may be one or more.
In addition, numerous specific details are set forth in the following detailed description 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 well known to those skilled in the art have not been described in detail in order not to obscure the present disclosure.
Fig. 1 is a flowchart of a bus-based service call 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 a smart bus. In some examples, the bus may provide a converged supported full resource collaborative development and execution environment for smart city scenario applications. The bus may be integrated into a terminal, server cluster, or other processing device, for example.
In an embodiment of the present disclosure, at least one connector corresponding to at least one standardized service, respectively, is deployed on a bus. Each of the at least one connector is mateable with at least one adapter configured in the service provisioning platform for enabling conversion between a platform service and a standardized service of the service provisioning platform. As shown in fig. 1, the method may include:
Step S110, determining a first adapter in at least one adapter in which the first connector is docked in response to receiving a connector call request for the first connector on the bus;
step S120, a service calling request is sent to a first adapter through a first connector; the first adapter is deployed in the first service supply platform, the service call request is used for calling 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 first standardized service corresponding to the first connector.
In the embodiments of the present disclosure, a service provision platform may refer to a platform for providing services related to intelligent algorithms. For example, the service provisioning platform may include an algorithm platform, a computing platform, a data platform, and the like. Alternatively, the bus may abstract the service standard definition of the respective service provision platform to form at least one standardized service, thereby forming at least one connector; wherein each service providing platform comprises an algorithm, a computing power, data, a video, a space-time, a map, a block chain, an IOT (Internet of Things, the internet of things) and other platforms.
Illustratively, the connector may include a standardized service interface on the bus for accessing each service provisioning platform. Optionally, one connector may include multiple APIs (Application Programming Interface, application programming interfaces) for invoking the service provisioning platform to perform various operations. For example, the computing platform workload connector may be used to implement connector actions such as load creation, query, update, delete, instance query, load computing power monitoring query, and the like.
In the above step S110, the connector call 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, a search engine server and the like, and sends a connector call request to a first connector on a bus to acquire related data services. For another example, the service demand platform is an algorithm platform, and sends a connector call request to a first connector on the bus to obtain the relevant computing power service.
In practical application, each connector is maintained by the bus, each service supply platform can refer to various connectors preset on the bus, service access as a lower-level platform is completed through the bus service register, and an adapter in butt joint with the connector is configured so as to complete service capability conversion between platform service and standardized service through the adapter. Optionally, the service capability transformation includes parameter mapping, merging, fusing, and the like. For example, the adapter is configured to convert a service call request issued by a standardized service interface on the connector into a personalized service call request conforming to an interface definition of the service provisioning platform; and converting the returned result output by the service supply platform and conforming to the platform interface definition into a returned result for being sent to the standardized service interface on the connector.
Illustratively, one connector may mate with one or more adapters. The adapters can be deployed in different service supply platforms to realize the access of multiple platforms to the same standardized service.
Alternatively, in the above method steps, the first connector may be any connector deployed on the bus, and accordingly, the first adapter may be any adapter that interfaces with the first connector. In practical application, the bus may provide the connector and the related statement of the standardized service corresponding to the connector for the upper layer service, so that the upper layer service can call the corresponding connector according to the practical service requirement. According to the method steps, when a connector call request to any connector is received, one adapter can be determined from a plurality of adapters which are in butt joint with the connector, then platform service is called through the adapter, and conversion between the platform service and standardized service is completed based on the adapter.
It can be seen that in the method provided in the above embodiment, the bus can build a bridge between the supply side cross-platform distributed resources and the service demand side, complete multi-resource access 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 the intelligent service can be improved.
Fig. 2 is a schematic diagram of an exemplary application scenario of a bus-based service invocation method according to an embodiment of the present disclosure. As shown in fig. 2, bus 200 is disposed between the platforms. The force calculation bin 210 is the lowest service provision platform. The bus may send a service call request to the computing force bin 210 when the data bin 220, algorithm bin 230, application bin 240, etc. initiate a connector call request for the computing force service to the bus, to cause the computing force bin 210 to provide the computing force service based on the corresponding adapter. Alternatively, as shown in FIG. 2, the data store 220 may also serve as a service provisioning platform for providing data services for logical calls by the algorithm store 230 or the application store 240. Algorithm silo 230 may also serve as a service provisioning platform for providing algorithm services to provision application silo 240 for logical calls. The above-described logic call may be implemented through the smart bus 200.
Specifically, as shown in fig. 2, a fusion workbench SDK (Software Development Kit ) is integrated in each platform, and the fusion workbench SDK includes program modules related to the intelligent bus and is used for completing processing procedures such as adapter configuration, service call, service capability conversion and the like. The intelligent bus 200 can adopt a Mongo-like architecture to carry out information transmission with each platform so as to drive each platform to execute relevant services based on the fusion workbench SDK. Optionally, in the service process, if the information with a larger data volume needs to be interacted between the platforms, the intelligent bus 200 may also instruct the platforms to implement information transmission between the platforms through the Hadoop-like architecture in the process of executing the related service. In this application example, a fusion workbench may also be configured for implementing management of the smart bus 200, such as development, joint debugging and testing of the smart bus 200 based on the fusion workbench.
In an exemplary embodiment, in the at least one adapter to which the first connector is mated, determining the first adapter may include: in the case that the connector call request contains adapter indication information, the first adapter is determined in at least one adapter of the first connector docking according to the adapter indication information.
For example, the bus may provide declarations of related services to the upper layers so that the service demand platform may query the connector and corresponding adapter, and in initiating a connector call request, may carry adapter indication information for indicating the adapter that is desired to be invoked.
By adopting the embodiment, each service demand platform can be assigned with an adapter, so that the service with high adaptability is provided further from the service demand side, the service demand is surrounded, various digital elements of cross-organization and cross-hierarchy are efficiently converged and multiplexed, and the construction of smart cities is realized.
In an exemplary embodiment, in the at least one adapter to which the first connector is mated, determining the first adapter may include: in the event that the connector call request does not contain adapter indication information, the first adapter is determined among the at least one adapter to which the first connector is mated according to a pre-configured load distribution policy.
Illustratively, the load distribution policy may include one or more policies of polling, weighting, randomization, and designated affinity.
With the present embodiment, in the case where the service demand platform does not specify an adapter, the first adapter may be automatically determined based on the load distribution policy. Therefore, load balancing can be realized, and service response efficiency is improved.
In an exemplary embodiment, the bus-based service invocation method may further include: storing log information corresponding to the connector call request in a preset database; wherein the log information includes information about the first adapter.
By adopting the implementation mode, the related information of the adapter used in each service calling process can be stored, so that the called adapter information can be queried, and the maintainability of the bus is improved. And the called adapter information can be read in the subsequent service calling process, so that load balancing is better realized.
In an exemplary embodiment, a configuration of the connector is also provided. Illustratively, the bus-based service invocation method may further include: determining at least one standardized service based on a platform type and a service type of each of at least one service provision platform of the access bus; at least one connector is configured based on at least one standardized service.
Illustratively, the platform type may include algorithms, applications, data, etc. that embody information that the platform service is highly cohesive. The service types may include types of specific services under each platform type, such as load-related services, instance-related services, monitoring-related services, etc. 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 under a data platform, structured file related services, etc.
By summarizing the accessed platform types and service types, at least one standardized service that 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 services can be improved, more comprehensive resources can be provided for the service demand side, and therefore the construction of smart cities can be realized.
In an exemplary embodiment, the bus-based service invocation method may further include: providing release information of each connector in at least one connector to each platform; wherein the release information is used to instruct each platform to configure an adapter that interfaces with each connector.
Illustratively, the release information of each connector may include declaration information of a standardized service corresponding to the connector. In this way, each platform can design a conversion manner 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 connected, and platform information to which the adapter belongs, so that the service requirement side can understand standardized services corresponding to each connector and compare each adapter.
By adopting the implementation mode, the service supply platform can complete the accurate configuration of the adapter, thereby accurately completing the access of multiple resources and improving the utilization rate of the resources. Meanwhile, the service demand side can inquire and call the related connector according to the actual demand, and service call efficiency and 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 release information of each connector according to the state of each connector.
By adopting the embodiment, the bus can regularly pull the metadata information of each connector, so that the interface state of a lower multi-platform or multi-application of the bus can be sensitively perceived, and the release information can be timely updated, so that the service requirement can timely perceive the related information, and the service calling efficiency and the success rate are improved.
To facilitate understanding of the above-described embodiments, fig. 3 shows a schematic diagram of an application example of the bus-based service invocation method of the embodiment of the present disclosure. As shown in fig. 3, the method comprises the following steps implemented on the bus operation side:
s301, creating a platform type. Specifically, a platform type may be created from the accessed platform of the corresponding new type.
S302, configuring a platform type.
S303, creating a service type. In particular, creation of service types may be performed according to platform types.
S304, configuring the service type. In particular, the partitioning of standardized services may be performed according to the type of service created.
S305, creating a connector. Specifically, a corresponding connector is created for each standardized service.
S306, editing the connector entry.
S307, editing the connector play parameters.
S308, issuing a connector.
The method further comprises the following steps implemented at the service provider side:
S309, newly-built adapter. Specifically, an adapter corresponding to the connector is newly built according to the release information of the connector.
S310, judging the single multi-API. Specifically, it is determined whether the connector involves one or more APIs.
S311, when the judgment result is a single API, a single API is newly built.
S312, when the judgment result is multiple APIs, creating multiple APIs.
S313, configuring the API attribute of the adapter.
S314, configuration 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 providing platform.
After the service providing platform completes the configuration, the configuration related information is returned to the connector market, so that the adapter related information is added in the release information of the connector.
The method further comprises the following steps implemented at the service demand side:
s315, inquiring the connector. Specifically, the corresponding connector is queried according to the service requirements.
S316, judging the state of the connector. Specifically, whether to call is confirmed according to the connector state.
S317, selecting a connector.
S318, determining whether to designate an adapter.
S319, judging the state of the adapter. Specifically, whether to call is confirmed according to the adapter state.
S320, using a connector. In particular, an adapter or bus may be designated to determine an adapter using a load policy.
Fig. 4 shows a schematic diagram of the relevant components of the 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, for example, a MySql database in fig. 4. The authentication and authorization component 402 is configured to provide a unified authentication function to authenticate and authenticate the service requirement platform when receiving the connector call request. The connector forwarding component 403 is used to forward the connector's request to the adapter. The connector forwarding component 403 needs to invoke the load balancing component 404 so that the load balancing component 404 selects the desired adapter by load policy and returns information about the adapter. Thereafter, the connector forwarding component 403 forwards the request for the connector to the adapter according to the adapter's related information. The parameter mapping component 405 is used to translate the adapter in-parameter and out-parameter configuration into the desired results. The log management component 406 is configured to record the call log and write the call log to a preset database. For example, the adapter information for each connector call is recorded. The timing pulling component 407 is configured to pull metadata information of the connector at a timing, and sense a state of the connector in time.
Optionally, in some embodiments of the present disclosure, the bus-based service invocation method further provides 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 scheduling flow based on the first scheduler, wherein the first scheduling flow is orchestrated based on at least one standardized service; if the first scheduling 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 through the first scheduler.
Illustratively, in the embodiments of the present disclosure, the schedule flow may be a traffic flow that is laid out by a plurality of connectors or a plurality of standardized services, and may be provided as a schedule flow service. The scheduler is a connection for implementing a scheduled stream service, i.e. a cross-platform service connection for implementing different services by the scheduler, may comprise an implementation of one or more scheduled streams. That is, the bus provides a dispatch flow for defining cross-platform services that combine multiple connectors in series according to business intent.
In the above method, the first scheduler is configured to execute the first scheduling flow, and when executing the first scheduling flow to an execution node corresponding to the second standardized service in the first scheduling flow, send a connector call request to a second connector corresponding to the second standardized service. In this way, when a connector call request to the second connector is received, the second adapter is determined in at least one adapter that the second connector is docked to complete the execution node by calling the second adapter. And by analogy, similar processes are realized for each execution node in the first scheduling flow, so that the scheduling flow service can be completed.
According to the method, the bus can provide services outwards in the form of scheduling stream service, 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 is facilitated to obtain efficient service experience.
In an exemplary embodiment, in a case where the first scheduling flow includes an execution node corresponding to the second standardized service, sending, by the first scheduler, a connector call request to a second connector corresponding to the second standardized service, including: determining, by a platform selector in the first scheduler, a second service provision platform among at least one service provision platform for implementing the second standardized service, in the case that the first scheduling flow includes an execution node corresponding to the second standardized service; 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 which is used for indicating the second connector to call a 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 the second standardized service in the current scheduling flow, and then carry the adapter indication information in the connector call request. Thus, when the second connector receives the connector call request, the corresponding second adapter can be determined according to the adapter indication information.
Fig. 5 shows a schematic diagram of a scheduler in one application example of an embodiment of the present disclosure. As shown in FIG. 5, a scheduler includes a number of components, such as a scheduler instantiation component 501, a platform selector 502, an executor 503, a results encapsulation component 504, and the like. The scheduler may provide scheduler service interfaces for image upload, image status query, workload creation, workload deletion, etc. The scheduler instantiation component 501 is operative to instantiate a normalized scheduler flow in accordance with a scheduler call request on a scheduler service interface. The platform selector 502 is configured to select a service providing platform of an execution node, for example, a designated platform, an overall platform, or an optimal platform may be selected. The executor 503 is configured to send a connector call request to a connector, such as a mirror verification connector, a mirror pull connector, a mirror state connector, a workload connector, and the like. The result packaging component 504 is configured to package the result returned by the connector upwards, so as to obtain a processing result returned to the service interface.
By adopting the embodiment, the adapter for realizing the service can be uniformly determined according to the demand of the dispatching flow, thereby being beneficial to ensuring the accurate execution of the whole dispatching flow and improving the service efficiency and the accuracy.
In an exemplary embodiment, the bus-based service invocation method may further include: storing log information corresponding to the dispatcher 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 each scheduling flow calling process can be stored, so that the called information can be queried, and the maintainability of the bus is improved. And the called adapter information can be read in the subsequent service calling process, so that load balancing is better realized.
Fig. 6 shows a schematic diagram of another application example of the bus-based service invocation method according to an embodiment of the present disclosure. As shown in fig. 6, the method includes the following steps implemented on the bus operator side:
s601, creating a scheduler.
S602, configuring a scheduler.
S603, generating a scheduler list.
The method further comprises the following steps implemented at the service demand side:
S604, inquiring the scheduler.
S605, judging the state of the scheduler. Specifically, whether to make a call is confirmed according to the scheduler state.
S606, using a scheduler. Specifically, a scheduler call request is initiated to the bus.
The method also comprises the following steps implemented at the bus operation side:
s607, the query dispatcher executes the record.
S608, judging whether the number of days is larger than a preset number of days, such as 180 days.
S609, confirming that the expected execution record is reserved in the database and checking the execution record of the scheduler when the number of days is not larger than the preset number of days.
Corresponding to the method implemented on the bus side, the embodiment of the disclosure also provides a method implemented by the service providing 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, calling a platform service in response to receiving a service calling request from the bus through the first adapter; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus, and the first adapter is in butt joint with the first connector on the bus; the service call request is sent when the bus receives a connector call 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 release information of a first connector on a bus;
the first adapter is configured based on the published information.
For implementation process and technical details of each step in the above method, reference may be made to corresponding descriptions in the foregoing embodiment and application example, that is, the method of this embodiment may be combined with the foregoing embodiment and application example, which are not described herein in detail.
According to the embodiment, the bus can build a bridge between the cross-platform distributed resources of the supply side and the service demand side, so that the access of multiple resources is completed for 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 the 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 embodiments of the present disclosure.
Fig. 8 shows a schematic diagram of another application example of the bus-based service invocation method of the embodiment of the present disclosure. As shown in fig. 8, multiple platforms in the platform group may access the city smart bus, where the a department provides push work order message service, the B group provides video data stream service, the C company provides accident detection algorithm service, the D organization provides GPU computing service, the E center provides NPU computing service, and the F institution provides work order classification recognition service. The city intelligent bus configures corresponding connectors based on each service, for example, a detection algorithm-GPU connector is configured according to the requirements of the detection algorithm on GPU computing power; the real-time video stream subscriber is configured for the requirements of the detection algorithm for the video data stream. In practical application, the intelligent service can be used for realizing the cross-mode automatic detection of the urban road grid event problem and intelligent distribution of cases. Specifically, under the condition that an accident vehicle is found, a detection algorithm-GPU connector is called, and the GPU power resource of the D mechanism is applied to complete the deployment of algorithm service. And acquiring the required video stream from the B group through an accident detection algorithm of the C company by a real-time video stream subscriber.
According to an embodiment of the present disclosure, the present disclosure further provides a service calling device based on a bus. Fig. 9 shows a schematic block diagram of a bus-based service invocation apparatus 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 that is docked with the first connector; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus;
a first call module 920, configured to send a service call request to the first adapter through the first connector; the first adapter is deployed in the first service supply platform, the service call request is used for calling 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 first standardized service corresponding to the first connector.
Optionally, the adaptation module 910 is configured to:
in the case that the connector call request contains adapter indication information, the first adapter is determined in at least one adapter of the first connector docking according to the adapter indication information.
Optionally, the adaptation module 910 is configured to:
in the event that the connector call request does not contain adapter indication information, the first adapter is determined among the at least one adapter to which the first connector is mated according to a pre-configured load distribution policy.
Alternatively, fig. 10 shows a schematic block diagram of a bus-based service invocation apparatus 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 includes information about the first adapter.
Optionally, as shown in fig. 10, the apparatus may further include:
a service determining module 1020 for determining at least one standardized service based on a platform type and a service type of each of at least one service provision platform of the access bus;
the connector configuration module 1030 is configured to configure at least one connector based on at least one standardized service.
Optionally, as shown in fig. 10, the apparatus may further include:
the publishing module 1040 is configured to provide publishing information of each connector in the at least one connector to each platform; wherein the release information is used to instruct each platform to configure an adapter that interfaces 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 state determining module 1060 for determining the state of each connector according to the metadata information;
the status updating module 1070 is configured to update the release 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 scheduling flow based on a first scheduler in response to receiving a scheduler call request for the first scheduler on the bus; wherein the first scheduling flow is arranged based on at least one standardized service;
the second calling module 1090 is configured to send, when the first scheduling flow includes an execution node corresponding to the second standardized service, a connector calling request to a second connector corresponding to the second standardized service through the first scheduler.
Optionally, as shown in fig. 10, the second calling module 1090 includes:
a platform selection unit 1091, configured to determine, when the first scheduling flow includes an execution node corresponding to the second standardized service, a second service provision platform from at least one service provision platform for implementing the second standardized service, by using a platform selector in the first scheduler;
The connector calling unit 1092 is 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 instruct the second connector to call a second adapter corresponding to the second service providing 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 dispatcher call request in a preset database; wherein the log information includes information about the second connector and the second adapter.
According to an embodiment of the present disclosure, the present disclosure further provides a service calling device based on a bus. Fig. 11 shows a schematic block diagram of a bus-based service invocation apparatus 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; wherein, at least one connector corresponding to at least one standardized service is deployed on the bus, and the first adapter is in butt joint with the first connector on the bus; the service call request is sent when the bus receives a connector call 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 apparatus provided in another embodiment of the disclosure. As shown in fig. 12, the apparatus may further include:
an acquiring module 1210, configured to acquire release information of a first connector on a bus;
the adapter configuration module 1220 is configured to configure the first adapter based on the published information.
For descriptions of specific functions and examples of each module and sub-module of the apparatus in the embodiments of the present disclosure, reference may be made to the related descriptions of corresponding steps in the foregoing method embodiments, which are not repeated herein.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related user personal information all conform to the regulations of related laws and regulations, and the public sequence is not violated.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
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 apparatuses, such as personal digital assistants, cellular telephones, smartphones, wearable devices, and other similar computing apparatuses. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary 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 required for the operation of the device 1300 can also be stored. The computing unit 1301, the ROM 1302, and the RAM 1303 are connected to each other through a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.
Various components in device 1300 are connected to 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, etc.; and a communication unit 1309 such as a network card, a modem, a wireless communication transceiver, or the like. The communication unit 1309 allows the device 1300 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
The computing unit 1301 may be a variety of general and/or special purpose processing components having 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, etc. The computing unit 1301 performs the respective methods and processes described above, such as a bus-based service call method. 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, part or all of the computer program may be loaded and/or installed onto the device 1300 via the ROM 1302 and/or the communication unit 1309. When the computer program is loaded into the RAM 1303 and executed by the 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 to perform the bus-based service invocation method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On 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, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code 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 code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. 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. The 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 portable 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 pointing device (e.g., a mouse or 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 may 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 input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background 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 background, 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 a client and a server. The client and server are typically 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 incorporating a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially, or in a different order, provided that the desired results of the disclosed aspects are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions, improvements, etc. that are within the principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (22)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310272449.2A CN115988087B (en) | 2023-03-17 | 2023-03-17 | Service calling method and device based on bus, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310272449.2A CN115988087B (en) | 2023-03-17 | 2023-03-17 | Service calling method and device based on bus, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115988087A CN115988087A (en) | 2023-04-18 |
| CN115988087B true CN115988087B (en) | 2023-08-01 |
Family
ID=85965243
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310272449.2A Active CN115988087B (en) | 2023-03-17 | 2023-03-17 | Service calling method and device based on bus, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115988087B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10992585B1 (en) * | 2019-05-09 | 2021-04-27 | Amazon Technologies, Inc. | Unified network traffic controllers for multi-service environments |
| WO2022037690A1 (en) * | 2020-08-20 | 2022-02-24 | 第四范式（北京）技术有限公司 | Application construction system, method and platform, and application publication system, method and platform |
| CN114527996A (en) * | 2022-01-30 | 2022-05-24 | 北京百度网讯科技有限公司 | Multi-service deployment method and device, electronic equipment and storage medium |
| CN115550354A (en) * | 2021-06-11 | 2022-12-30 | 腾讯云计算（北京）有限责任公司 | Data processing method and device and computer readable storage medium |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2571230A1 (en) * | 2002-01-15 | 2013-03-20 | Avaya Inc. | Communication application server for converged communication services |
| EP1819415A2 (en) * | 2004-11-08 | 2007-08-22 | Integration Technologies, Llc. | System, method and apparatus for an extensible distributed enterprise integration platform |
| US7996488B1 (en) * | 2006-11-27 | 2011-08-09 | Disney Enterprises, Inc. | Systems and methods for interconnecting media applications and services with automated workflow orchestration |
| KR102050188B1 (en) * | 2019-02-08 | 2019-11-28 | 아콘소프트 주식회사 | Microservice system and method thereof |
| CN113014626B (en) * | 2021-02-09 | 2023-04-18 | 北京互金新融科技有限公司 | Data service management method and device, storage medium and electronic device |
| CN114756340A (en) * | 2022-03-17 | 2022-07-15 | 中国联合网络通信集团有限公司 | Computing power scheduling system, method, device and storage medium |
| CN115086311B (en) * | 2022-04-28 | 2023-10-03 | 上海浦东发展银行股份有限公司 | Management system of enterprise cross-system service based on cloud service bus |
| CN115292071A (en) * | 2022-08-25 | 2022-11-04 | 中电信数智科技有限公司 | Cloud resource management method, device, server and storage medium |
-
2023
- 2023-03-17 CN CN202310272449.2A patent/CN115988087B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10992585B1 (en) * | 2019-05-09 | 2021-04-27 | Amazon Technologies, Inc. | Unified network traffic controllers for multi-service environments |
| WO2022037690A1 (en) * | 2020-08-20 | 2022-02-24 | 第四范式（北京）技术有限公司 | Application construction system, method and platform, and application publication system, method and platform |
| CN115550354A (en) * | 2021-06-11 | 2022-12-30 | 腾讯云计算（北京）有限责任公司 | Data processing method and device and computer readable storage medium |
| CN114527996A (en) * | 2022-01-30 | 2022-05-24 | 北京百度网讯科技有限公司 | Multi-service deployment method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115988087A (en) | 2023-04-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3047376B1 (en) | Type-to-type analysis for cloud computing technical components | |
| US11645111B2 (en) | Managing task flow in edge computing environment | |
| TWI519965B (en) | Flexible assembly system and method for cloud service service for telecommunication application | |
| CN109743192A (en) | A container cluster configuration management method and device | |
| CN102148736B (en) | M2M business platform and the method and system merged with business network of future generation thereof | |
| CN113010428A (en) | Server cluster testing method, device, medium and electronic equipment | |
| CN116932168A (en) | Heterogeneous core scheduling method and device, storage medium and electronic equipment | |
| CN114926163A (en) | Resource cross-chain transfer method and device | |
| CN110471664A (en) | A kind of heterogeneous software platform based on OSGi framework unifies interconnection method | |
| CN115774573B (en) | Application integration method, device, electronic equipment and storage medium | |
| WO2023246127A1 (en) | System and methods for mission execution in network | |
| CN109743202A (en) | Data management method, apparatus, device and readable storage medium | |
| CN114710395B (en) | Method for constructing network service implementation example based on digital twin technology | |
| CN116974748A (en) | Resource scheduling methods, nodes, equipment, media and program products | |
| CN115994022B (en) | Algorithm service calling method and device, electronic equipment and storage medium | |
| CN115988087B (en) | Service calling method and device based on bus, electronic equipment and storage medium | |
| CN113031536A (en) | Flexible manufacturing product processing system based on 5G framework | |
| CN107896242B (en) | Service sharing method and device | |
| CN107305497A (en) | Version upgrading method and device | |
| CN114036250A (en) | High-precision map task processing method and device, electronic equipment and medium | |
| CN116402318B (en) | Multi-stage computing power resource distribution method and device for power distribution network and network architecture | |
| CN109117146A (en) | Automatic deployment method, device, storage medium and the computer equipment of cloud platform duoble computer disaster-tolerance system | |
| CN119045994A (en) | Heterogeneous GPU scheduling system, heterogeneous GPU scheduling method, storage medium, electronic equipment and heterogeneous GPU scheduling product | |
| CN115981632A (en) | System construction method and device, electronic equipment and storage medium | |
| CN116743880A (en) | Service engine interface adapting method, adapting device and adapting system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |