Method, device and equipment for platform access to service center
Through the method and device of the platform access service center, the problem of inclusion of multiple PaaS platforms when sharing basic services is solved, the unified management and tenant isolation of multi-platform access is realized, and the efficiency and consistency of resource management are improved.
Patent Information
- Application Number
- CN202110909884.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-09
- Publication Date
- 2025-08-26
- Estimated Expiration
- 2041-08-09
AI Technical Summary
In the prior art, PaaS platforms of each manufacturer are difficult to meet different needs at the same time. Multiple PaaS service users need to take care of them separately when sharing basic services, resulting in service management problems.
Provide a method and device for accessing a service center on the platform. By receiving access requests from multiple platforms, obtaining the underlying service resource information of the service center, and allocating resources to each platform, realizing unified access and management of multi-platform access, multi-tenant isolation and service management.
It realizes unified access and management of multi-platform access service centers, solves the development differences between service components and platform access differences, and realizes the isolation of tenants and effective resource management.
Smart Images

Figure CN115914218B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of big data information processing technology, and in particular to a method, device and equipment for platform access to a service center. Background Art
[0002] In recent years, Platform-as-a-Service (PaaS) has accelerated the development of the internet industry as a service delivery model. As each vendor has the resources, they will develop their own PaaS platforms to provide services.
[0003] The existing solution requires each manufacturer to develop and implement Hadoop (distributed system infrastructure) separately. Even if service center A's own PaaS management platform is introduced as an intermediate layer, it is difficult to meet the different needs of each manufacturer at the same time.
[0004] For some PaaS service centers, if multiple PaaS service users want to share basic services, they need to manage the shared services on their respective PaaS platforms, which leads to service management issues. Summary of the Invention
[0005] In view of the above problems, embodiments of the present invention are proposed to provide a method, apparatus, and device for platform access service center that overcome the above problems or at least partially solve the above problems.
[0006] According to one aspect of an embodiment of the present invention, a method for platform access service center is provided, which is applied to a platform access device, and the method includes:
[0007] Receive access requests from at least two platform access service centers;
[0008] Obtain resource information of the underlying basic service of the service center according to the access request;
[0009] The resources allocated to each of the at least two platforms are returned to the platform.
[0010] According to another aspect of an embodiment of the present invention, a method for a platform to access a service center is provided. The method is applied to the platform and includes:
[0011] Sending an access request to the platform access service center to the platform access device;
[0012] Receive resource information of the underlying basic service allocated to the platform by the service center according to the access request, which is returned by the platform access device.
[0013] An embodiment of the present invention further provides a platform access device, comprising:
[0014] A receiving module, configured to receive access requests from at least two platform access service centers;
[0015] An acquisition module, configured to acquire resource information of the underlying basic service of the service center according to the access request;
[0016] The sending module is configured to return the resources allocated to each of the at least two platforms.
[0017] An embodiment of the present invention further provides a platform, comprising:
[0018] A sending module, configured to send an access request to the platform access service center to the platform access device;
[0019] The receiving module is configured to receive resource information of the underlying basic service allocated to the platform by the service center according to the access request and returned by the platform access device.
[0020] According to another aspect of an embodiment of the present invention, there is provided a computing device, comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other via the communication bus;
[0021] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute operations corresponding to the method for platform access to the service center as described above.
[0022] According to another aspect of an embodiment of the present invention, a computer storage medium is provided, wherein the storage medium stores at least one executable instruction, and the executable instruction enables a processor to execute operations corresponding to the method for platform access to a service center as described above.
[0023] According to the solution provided by the above embodiment of the present invention, access requests from at least two platforms to the service center are received; resource information of the underlying basic services of the service center is obtained according to the access requests; and resources allocated to the platform are returned to each of the at least two platforms; the problems of multi-platform access, multi-tenant isolation and service management inconsistency are solved, thereby achieving unified access and management of multi-platform access to the service center.
[0024] The above description is only an overview of the technical solutions of the embodiments of the present invention. In order to more clearly understand the technical means of the embodiments of the present invention, they can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiments of the present invention more obvious and easy to understand, the specific implementation methods of the embodiments of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the embodiments of the present invention. The same reference numerals are used throughout the accompanying drawings to denote the same components. In the accompanying drawings:
[0026] Figure 1 A flow chart of a method for platform access to a service center provided by an embodiment of the present invention is shown;
[0027] Figure 2 A flow chart showing a method for platform access to a service center provided by another embodiment of the present invention is shown;
[0028] Figure 3 A system architecture diagram showing multi-PaaS platform access service center and service management provided by another embodiment of the present invention is shown;
[0029] Figure 4 A schematic diagram of a specific module diagram of a platform access device provided by an embodiment of the present invention is shown;
[0030] Figure 5 A schematic structural diagram of a platform access device provided by an embodiment of the present invention is shown;
[0031] Figure 6 A schematic structural diagram of a computing device provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0032] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.
[0033] Figure 1 The flowchart of the method for platform access service center provided by the embodiment of the present invention is shown. Figure 1 As shown, the method is applied to a platform access device, and the method includes the following steps:
[0034] Step 11: Receive access requests from at least two platform access service centers;
[0035] Step 12: Obtain resource information of the underlying basic service of the service center according to the access request;
[0036] Step 13: Return the resources allocated to each of the at least two platforms.
[0037] The method described in this embodiment is applied to a platform access device. After receiving access requests from multiple platforms, the platform access device interacts with the service center through a unified interface. After receiving access requests from multiple platforms to the service center, the multi-platform access device obtains resource information of the underlying basic services of the service center according to the access requests, manages the underlying basic service components in the service center, and isolates tenants, thereby shielding development differences between service components and differences in platform access.
[0038] In an optional embodiment of the present invention, step 13 may include: returning resources allocated to the cluster of the platform to each of the at least two platforms.
[0039] Optionally, returning the resources allocated to each of the at least two platforms further includes: returning a service package to each of the at least two platforms.
[0040] In this embodiment, the platform can be a PaaS (Platform-as-a-Service), and a resource list of the underlying basic services of the service center can be obtained through the platform access device. The platform access device returns the total amount of resources and the activated amount of all clusters allocated to the PaaS platform. The PaaS platform can effectively control the resource allocation through the platform access device. The platform access device can also return service subscription packages, multiple service individual or combined packages, such as HDFS (distributed file system) individual packages, HIVE (data warehouse tool) individual packages, YARN (resource manager) individual packages, HDFS and HIVE combined packages, HDFS and YARN combined packages, etc. For example, when multiple manufacturer platforms access service center A through the platform access device, different manufacturers will have different cluster resource displays. After service center A allocates cluster resources to manufacturer B and manufacturer C respectively, the manufacturers access the system, and the system will uniquely identify manufacturers B and C. After manufacturer B accesses the system, it will only query the cluster resources allocated to manufacturer B by service center A through the platform access device. After manufacturer C accesses the system, it will only query the cluster resources allocated to manufacturer C by service center A through the service directory module, thereby effectively isolating tenant resources at the manufacturer level.
[0041] In an optional embodiment of the present invention, based on the above 11 to 13, at least one of the following may be further included:
[0042] Step 14: Receive a service subscription request from each of the at least two platforms, and send the service subscription request to the service center, which creates an underlying service for the platform. After the platform access device receives and feeds back the service subscription request, it can allocate the service resource size in a planned manner based on the resource information of the underlying basic service of the service center, and after passing the resource size and the fixed structure of the service directory into the service creation module, multiple underlying services can be created by subscribing once, and a creation switch for each underlying service is built in.
[0043] Step 15: Receive a service update request from each of the at least two platforms, and send the service update request to the service center, which will update the underlying service for the platform. After the platform access device receives and feeds back the service update request, it can adjust the service resource size in a planned manner based on the resource information of the underlying basic service of the service center. Multiple underlying services can be updated at one time, and an update switch for each underlying service is built in.
[0044] Step 16: Receive the identifier of the first service instance sent by each of the at least two platforms, send the identifier of the first service instance to the service center, and the service center deletes the service resource list corresponding to the identifier of the first service instance and releases the corresponding cluster resources.
[0045] Step 17: Receive a resource query request for the second service instance sent by each of the at least two platforms, send the resource query request for the second service instance to the service center, and the service center returns the resources corresponding to the second service instance to the platform according to the resource query request; and query the specific resource name and size of the second service instance.
[0046] Step 18: Receive a binding request for the third service instance sent by each of the at least two platforms, send the binding request for the third service instance to the service center, and the service center obtains the access credentials of the third service instance according to the binding request and binds with the third service instance.
[0047] Step 19: Receive an unbinding request for the fourth service instance from each of the at least two platforms, and send the unbinding request to the service center. The service center obtains the access credentials for the fourth service instance based on the unbinding request and unbinds the fourth service instance. This step unbinds the tenant from the service instance at the platform level. If the access credentials are needed again later, the service instance can be re-binded through the service binding module.
[0048] Step 20, according to the asynchronous operation request sent by each of the at least two platforms, the asynchronous operation request is sent to the service center, and the service center performs a status query of the asynchronous call interface according to the asynchronous operation request, obtains the query result, and returns the query result to the platform. When the PaaS platform accesses a system that accesses multiple PaaS platforms and manages services, it can be an asynchronous operation or a synchronous operation. When the interface is called asynchronously, it is necessary to query the status of the asynchronous interface through this step. The platform access device can query the status of asynchronous operations such as creation, update and deletion of service instances. When the polling query status is SUCCEED, it means that the operation is successful; when the query status is IN_PROGRESS, it means that the operation is in progress; when the query status is FAILED, it means that the operation has failed. The status of the asynchronous query operation can be used to determine whether the operation of the service resource is normal.
[0049] In this embodiment, the numbering of the above steps is not intended to limit the order of the steps. Without affecting the purpose of the present invention, the order of the above steps can be changed, or some steps can be performed simultaneously. The platform access device receives various requests sent by multiple PaaS platforms and, based on the above method, can uniformly connect to the service center to achieve the management of the underlying basic service resources, effectively decoupling the PaaS platform and the service center.
[0050] Figure 2 A flow chart of a method for platform accessing a service center according to another embodiment of the present invention is shown. Figure 2 As shown, the method includes the following steps:
[0051] Step 21: Sending an access request from the platform access service center to the platform access device;
[0052] Step 22: Receive resource information of the underlying basic service allocated to the platform by the service center according to the access request, which is returned by the platform access device.
[0053] The method described in this embodiment is applied to the platform side. The platform sends an access request for the platform to the service center to access the platform to interact with the service center through a unified interface. The resource information of the underlying basic services of the service center is obtained according to the access request. Then, the platform receives the resources allocated to the platform according to the access request from the service center through the platform access device, and then performs operations such as subscription, update, and cancellation on the basic services on the resource pool.
[0054] In an optional embodiment of the present invention, based on the above 21 to 22, at least one of the following may be further included:
[0055] Step 23: Send a service subscription request to the platform access device. After the service subscription request is sent to the service center through the platform access device, the service center creates an underlying service for the platform.
[0056] Step 24: Send a service update request to the platform access device. After the service update request is sent to the service center through the platform access device, the service center updates the underlying service for the platform.
[0057] Step 25: Send the identifier of the first service instance to the platform access device. After the identifier of the first service instance is sent to the service center via the platform access device, the service center deletes the service resource list corresponding to the identifier of the first service instance.
[0058] Step 26: Send a resource query request for the second service instance to the platform access device. After the resource query request for the second service instance is sent to the service center through the platform access device, the service center returns the resources corresponding to the second service instance to the platform according to the resource query request.
[0059] Step 27: Send a binding request for the third service instance to the platform access device. After the binding request for the third service instance is sent to the service center through the platform access device, the service center obtains the access credential of the third service instance and binds it to the third service instance.
[0060] Step 28: Sending an unbinding request for the fourth service instance to the platform access device. After the unbinding request for the fourth service instance is sent to the service center via the platform access device, the service center obtains the access credential of the fourth service instance and unbinds the fourth service instance.
[0061] Step 29: Send an asynchronous operation request to the platform access device. After the asynchronous operation request is sent to the service center via the platform access device, the service center queries the status of the asynchronous call interface, obtains the query result, and returns the query result to the platform. If the polling query status is SUCCEED, it indicates that the operation is successful; if the query status is IN_PROGRESS, it indicates that the operation is in progress; if the query status is FAILED, it indicates that the operation has failed. The asynchronous query operation status is used to determine whether the service resource is operating normally.
[0062] In this embodiment, the numbering of the above steps does not limit the order of the steps. Without affecting the purpose of the present invention, the order of the above steps can be changed, or some steps can be performed simultaneously. Multiple PaaS platforms achieve access to the service center and management of the underlying basic services through the ordering service, updating service, deleting service, querying service, binding service, unbinding service, and asynchronous query service steps of the above method.
[0063] The following describes the specific implementation process of the above method in combination with the specific system architecture:
[0064] like Figure 3 and Figure 4 As shown, the above method and the combined system can access various heterogeneous big data basic services and perform unified multi-tenant management and allocation of services. The various basic services of the big data ecosystem can be divided into physical deployment basic services, virtual deployment basic services and container deployment basic services according to their different deployment methods. Any basic service can be uniformly connected to the PaaS platform in this way. The present invention can be effectively applied to the access of multiple PaaS platforms to the PaaS service center, fully utilizing the advantages of open API capabilities, eliminating the strong coupling between PaaS platforms, and uniformly managing basic services.
[0065] PaaS platforms from multiple manufacturers are uniformly developed according to the interfaces provided by the system, and then connected to the system to manage the basic services of the service center and perform operations such as ordering, updating, and unsubscribing on the basic services on the resource pool.
[0066] Methods for accessing multiple PaaS platforms and managing services include: Figure 3 As shown, Manufacturer B and Manufacturer C have their own PaaS platforms. There is no need to customize, develop, and manage each service of Service Center A individually. Their respective PaaS platforms uniformly access the platform access and component management system of this proposal to manage the underlying basic service components in Service Center A, thereby isolating tenants and shielding the development differences between service components and differences in platform access.
[0067] The main steps involved in the vendor PaaS platform access and service management method are as follows:
[0068] Step 1: The manufacturer's PaaS platform accesses service center A through the service management system of the platform access device to obtain the service catalog information under the corresponding cluster, thereby providing resource quantity basis for subsequent operations such as ordering.
[0069] Step 2: After the manufacturer's PaaS platform is connected to the service center A through the service management system of the platform access device, basic services can be ordered according to the service catalog information.
[0070] In step 3, after the manufacturer's PaaS platform is connected to the service center A through the service management system of the platform access device, the size of the ordered basic service resources can be updated according to the service catalog information.
[0071] In step 4, after the manufacturer's PaaS platform is connected to the service center A through the service management system of the platform access device, it can delete the subscribed basic services and release the corresponding cluster resources according to the service catalog information.
[0072] In step 5, after the manufacturer's PaaS platform is connected to the service center A through the service management system of the platform access device, it can query the service instance details and obtain the details of resource subscription.
[0073] In step 6, after the manufacturer's PaaS platform is connected to the service center A through the service management system of the platform access device, it can bind the service instance and obtain information such as service resource access method and credentials.
[0074] In step 7, after the manufacturer's PaaS platform is connected to the service center A through the service management system of the platform access device, it can unbind the service instance, thereby hiding information such as service resource access methods and credentials.
[0075] Step 8. After the manufacturer's PaaS platform is connected to service center A through the service management system of the platform access device, the status of asynchronous ordering, updating, and deletion operations can be queried. When the polling query status is SUCCEED, it means that the operation is successful; when the query status is IN_PROGRESS, it means that the operation is in progress; when the query status is FAILED, it means that the operation has failed. The status of the asynchronous query operation can be used to determine whether the operation of the service resource is normal.
[0076] It should be noted that there is no necessary order restriction for steps 1 to 8, and one or more steps can be implemented individually or in combination.
[0077] Optionally, the specific module diagram of the platform access device 50 is as follows: Figure 4 As shown, it specifically includes: service catalog module, service creation module, service update module, service binding module, service unbinding module, service deletion module, service query module, and service asynchronous query module.
[0078] The service catalog module can implement steps 11 to 13 above. It can serve as a health check mechanism for the vendor PaaS platform on the service center. More importantly, the vendor PaaS platform can use this module to obtain a resource list of service center A's underlying infrastructure services. The module returns the total resource allocation and activated resource count for all clusters allocated to the vendor PaaS platform, allowing the PaaS platform to effectively control resource allocation. The module can also return service subscription packages, including individual or combined service packages, such as HDFS, HIVE, YARN, HDFS and HIVE, and HDFS and YARN. Different vendors will have different cluster resource displays. When service center A allocates cluster resources to vendors B and C, the system uniquely identifies vendors B and C. Once vendor B connects to the system, the service catalog module will only display the cluster resources allocated to vendor B by service center A. Once vendor C connects to the system, the service catalog module will only display the cluster resources allocated to vendor C by service center A, effectively isolating tenant resources at the vendor level.
[0079] The service creation module can implement step 14 above. It serves as the entry point for the manufacturer's PaaS platform to connect with service center A to order underlying service instances. The PaaS platform can obtain a list of service resources from the service catalog module and systematically allocate service resource sizes. After passing the resource size and the fixed service catalog structure parameters to the service creation module, a single order can create multiple underlying services, with built-in creation switches for each underlying service.
[0080] The service update module implements step 15 above. It serves as the entry point for the vendor's PaaS platform to connect with service center A to update the resource size of underlying service instances. Service instance updates are based on existing service instances. The PaaS platform can systematically adjust service resource sizes based on the service resource list obtained from the service catalog module. A single update can update multiple underlying services, and includes built-in update switches for each underlying service.
[0081] The service deletion module can implement step 16 above. It serves as the entry point for the manufacturer's PaaS platform to connect to service center A to delete the underlying service instance. After the PaaS platform passes the instance ID to the module, the system uses the instance ID to obtain the service resource list in the record and then deletes the service.
[0082] The service query module can implement the above step 17. The service query module serves as the entry for the manufacturer's PaaS platform to connect to the service center A to query the resource details of the underlying service instance. The PaaS platform can query the specific resource name and size of the service instance based on this module.
[0083] The service binding module can implement the above step 18. The service binding module serves as the entry point for the manufacturer's PaaS platform to connect to the service center A and bind the underlying service instance. The PaaS platform can bind to the service instance based on the module and obtain information such as the access credentials of the service instance.
[0084] The service unbinding module implements step 19 above. It serves as the gateway for the vendor's PaaS platform to connect with Service Center A and unbind the underlying service instance. The PaaS platform uses this module to unbind the service instance, thereby unbinding the tenant from the service instance at the platform level. If access credentials are needed again later, the service instance can be rebinded using the service binding module.
[0085] The service asynchronous query module can implement step 20 above. It serves as the entry point for the manufacturer's PaaS platform to connect to service center A to asynchronously query the status of various operations. When a PaaS platform accesses multiple PaaS platforms and manages services, operations can be either asynchronous or synchronous. When an interface is called asynchronously, the status of the asynchronous interface needs to be queried through the service asynchronous query module. The PaaS platform can use this module to query the status of asynchronous operations such as the creation, update, and deletion of service instances.
[0086] The PaaS platforms of multiple manufacturers can be uniformly connected to the service center through the platform access device and the above-mentioned method, which can effectively reduce the differences in multi-platform docking. Through the various modules of the system, the service catalog can be viewed, services can be ordered, services can be updated, services can be deleted, services can be queried, services can be bound, services can be unbound, and asynchronous query service steps can be used to achieve access to the service center and management of underlying basic services, effectively decoupling the PaaS platform and the service center. This method is also applicable to the access of containerized services.
[0087] Figure 5 FIG. 5 is a schematic structural diagram of a platform access device 50 provided in an embodiment of the present invention. The device 50 includes:
[0088] A receiving module 51 is configured to receive access requests from at least two platform access service centers;
[0089] An acquisition module 52 is configured to acquire resource information of the underlying basic service of the service center according to the access request;
[0090] The sending module 53 is configured to return the resources allocated to each of the at least two platforms.
[0091] Optionally, returning the resources allocated to each of the at least two platforms to the platform includes:
[0092] Resources allocated for the cluster of platforms are returned to each of the at least two platforms.
[0093] Optionally, when returning the resources allocated to each of the at least two platforms to the platform, the method further includes:
[0094] A service subscription package is returned to each of the at least two platforms.
[0095] Optionally, the receiving module 51 is further configured to implement at least one of the following:
[0096] receiving a service subscription request from each of the at least two platforms, sending the service subscription request to the service center, and having the service center create an underlying service for the platform;
[0097] receiving a service update request from each of the at least two platforms, and sending the service update request to the service center, so that the service center updates the underlying service for the platform;
[0098] receiving an identifier of a first service instance sent by each of the at least two platforms, sending the identifier of the first service instance to the service center, and having the service center delete a service resource list corresponding to the identifier of the first service instance;
[0099] receiving a resource query request for a second service instance sent by each of the at least two platforms, sending the resource query request for the second service instance to the service center, and having the service center return resources corresponding to the second service instance to the platform according to the resource query request;
[0100] receiving a binding request for a third service instance sent by each of the at least two platforms, sending the binding request for the third service instance to the service center, whereby the service center obtains an access credential for the third service instance according to the binding request and binds the access credential to the third service instance;
[0101] receiving an unbinding request for a fourth service instance sent by each of the at least two platforms, sending the unbinding request for the fourth service instance to the service center, whereby the service center obtains an access credential for the fourth service instance according to the unbinding request and unbinds the access credential from the fourth service instance;
[0102] According to the asynchronous operation request sent by each of the at least two platforms, the asynchronous operation request is sent to the service center, and the service center performs a status query of the asynchronous call interface according to the asynchronous operation request, obtains the query result, and returns the query result to the platform.
[0103] In this embodiment, the device is a device corresponding to the method on the platform access device side. All implementation methods in the above embodiments are applicable to the embodiments of the device and can achieve the same technical effects.
[0104] An optional embodiment of the present invention further provides a platform, comprising:
[0105] A sending module, configured to send an access request to the platform access service center to the platform access device;
[0106] The receiving module is configured to receive resource information of the underlying basic service allocated to the platform by the service center according to the access request and returned by the platform access device.
[0107] Optionally, the sending module is further configured to implement at least one of the following:
[0108] Sending a service subscription request to the platform access device, after the service subscription request is sent to the service center through the platform access device, the service center creates an underlying service for the platform;
[0109] Sending a service update request to the platform access device, after which the service update request is sent to the service center through the platform access device, and the service center updates the underlying service for the platform;
[0110] Sending an identifier of the first service instance to the platform access device, after the identifier of the first service instance is sent to the service center through the platform access device, the service center deletes the service resource list corresponding to the identifier of the first service instance;
[0111] Sending a resource query request for the second service instance to the platform access device, after the resource query request for the second service instance is sent to the service center through the platform access device, the service center returns the resources corresponding to the second service instance to the platform according to the resource query request;
[0112] Sending a binding request for a third service instance to the platform access device. After the binding request for the third service instance is sent to the service center through the platform access device, the service center obtains the access credential of the third service instance and binds the third service instance;
[0113] sending an unbinding request for the fourth service instance to the platform access device, whereby the unbinding request for the fourth service instance is sent to the service center through the platform access device, and the service center obtains the access credential of the fourth service instance and unbinds the fourth service instance;
[0114] An asynchronous operation request is sent to the platform access device. After the asynchronous operation request is sent to the service center through the platform access device, the service center performs a status query on the asynchronous call interface, obtains the query result, and returns the query result to the platform.
[0115] In this embodiment, the device is a device corresponding to the method on the platform side mentioned above. All implementation methods in the above embodiments are applicable to the embodiments of the device and can achieve the same technical effects.
[0116] An embodiment of the present invention provides a non-volatile computer storage medium, wherein the computer storage medium stores at least one executable instruction, and the computer executable instruction can execute the method of platform accessing a service center in any of the above method embodiments.
[0117] Figure 6 The schematic diagram of the structure of the computing device provided by the embodiment of the present invention is shown. The specific embodiment of the present invention does not limit the specific implementation of the computing device.
[0118] like Figure 6 As shown, the computing device may include: a processor, a communication interface, a memory, and a communication bus.
[0119] The processor, communication interface, and memory communicate with each other via a communication bus. The communication interface is used to communicate with other devices, such as clients or other server network elements. The processor is used to execute programs, specifically, the steps described in the aforementioned method embodiment for enabling a computing device to access a service center through a platform.
[0120] Specifically, the program may include program codes including computer operation instructions.
[0121] The processor may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the computing device may be processors of the same type, such as one or more CPUs, or processors of different types, such as one or more CPUs and one or more ASICs.
[0122] Memory is used to store programs. The memory may include high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk storage.
[0123] The program can be specifically configured to cause the processor to execute the platform access service center method in any of the aforementioned method embodiments. The specific implementation of each step in the program can be found in the corresponding descriptions of the corresponding steps and units in the aforementioned method embodiments for platform access service center, and will not be repeated here. Those skilled in the art will clearly understand that, for ease and brevity of description, the specific operating processes of the devices and modules described above can refer to the corresponding process descriptions in the aforementioned method embodiments, and will not be repeated here.
[0124] The algorithm or display provided herein is not inherently related to any particular computer, virtual system or other device. Various general-purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious that the structure required for constructing such systems. In addition, the embodiment of the present invention is not directed to any specific programming language. It should be understood that various programming languages can be utilized to implement the content of the embodiment of the present invention described herein, and the above description of specific languages is for the purpose of disclosing the best mode of implementation of the embodiment of the present invention.
[0125] In the description provided herein, numerous specific details are described. However, it is understood that embodiments of the present invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of this description.
[0126] Similarly, it should be understood that in order to streamline the embodiments of the invention and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed approach should not be interpreted as reflecting an intention that the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as reflected in the claims below, inventive aspects lie in less than all of the features of the individual embodiments disclosed above. Accordingly, the claims that follow the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of the invention.
[0127] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition may be divided into multiple submodules or subunits or subcomponents. All features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed herein may be combined in any combination, except that at least some of such features and / or processes or units are mutually exclusive. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.
[0128] Furthermore, those skilled in the art will appreciate that although some embodiments herein include certain features included in other embodiments but not other features, combinations of features from different embodiments are intended to be within the scope of the present invention and to form different embodiments. For example, in the claims below, any of the claimed embodiments may be used in any combination.
[0129] The various component embodiments of the present invention can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of the present invention. The embodiments of the present invention can also be implemented as a device or apparatus program (e.g., a computer program and a computer program product) for executing part or all of the methods described herein. Such a program implementing an embodiment of the present invention can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.
[0130] It should be noted that the above embodiments illustrate rather than limit the embodiments of the invention, and that a person skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between brackets should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The embodiments of the invention may be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments should not be understood as limiting the order of execution unless otherwise specified.
Claims
1. A method for platform access to a service center, characterized in that: Applied to a platform access device, the method includes: Receive access requests from at least two platform access service centers; Obtain resource information of the underlying basic service of the service center according to the access request, and manage the underlying basic service components of the service center; Returning the resources allocated to each of the at least two platforms to the platform; The method also includes: receiving a resource query request for a second service instance sent by each of the at least two platforms, sending the resource query request for the second service instance to the service center, and the service center returning the resources corresponding to the second service instance to the platform according to the resource query request.
2. The method for platform access service center according to claim 1, characterized in that: Returning the resources allocated to each of the at least two platforms to the platform includes: Resources allocated for the cluster of platforms are returned to each of the at least two platforms.
3. The method for platform access service center according to claim 1, characterized in that: When returning the resources allocated to each of the at least two platforms, the method further includes: A service package is returned to each of the at least two platforms.
4. The method for platform access service center according to claim 1, characterized in that: Also include at least one of the following: receiving a service subscription request from each of the at least two platforms, sending the service subscription request to the service center, and having the service center create an underlying service for the platform; receiving a service update request from each of the at least two platforms, and sending the service update request to the service center, so that the service center updates the underlying service for the platform; receiving an identifier of a first service instance sent by each of the at least two platforms, sending the identifier of the first service instance to the service center, and having the service center delete a service resource list corresponding to the identifier of the first service instance; receiving a binding request for a third service instance sent by each of the at least two platforms, sending the binding request for the third service instance to the service center, whereby the service center obtains an access credential for the third service instance according to the binding request and binds the access credential to the third service instance; receiving an unbinding request for a fourth service instance sent by each of the at least two platforms, sending the unbinding request for the fourth service instance to the service center, whereby the service center obtains an access credential for the fourth service instance according to the unbinding request and unbinds the access credential from the fourth service instance; According to the asynchronous operation request sent by each of the at least two platforms, the asynchronous operation request is sent to the service center, and the service center performs a status query of the asynchronous call interface according to the asynchronous operation request, obtains the query result, and returns the query result to the platform.
5. A method for platform access to a service center, characterized in that: Applied to the platform, the method includes: Sending an access request to the platform access service center to the platform access device; receiving resource information of the underlying basic service allocated by the service center to the platform according to the access request, which is returned by the platform access device, wherein the platform access device manages the underlying basic service components of the service center; A resource query request for the second service instance is sent to the platform access device. After the resource query request for the second service instance is sent to the service center through the platform access device, the service center returns the resources corresponding to the second service instance to the platform according to the resource query request.
6. The method for platform access service center according to claim 5, characterized in that: Also include at least one of the following: Sending a service subscription request to the platform access device, after the service subscription request is sent to the service center through the platform access device, the service center creates an underlying service for the platform; Sending a service update request to the platform access device, after which the service update request is sent to the service center through the platform access device, and the service center updates the underlying service for the platform; Sending an identifier of the first service instance to the platform access device, after the identifier of the first service instance is sent to the service center through the platform access device, the service center deletes the service resource list corresponding to the identifier of the first service instance; Sending a binding request for a third service instance to the platform access device. After the binding request for the third service instance is sent to the service center through the platform access device, the service center obtains the access credential of the third service instance and binds the third service instance; Sending an unbinding request for the fourth service instance to the platform access device, whereby the unbinding request for the fourth service instance is sent to the service center through the platform access device, and the service center obtains the access credential of the fourth service instance and unbinds the fourth service instance; An asynchronous operation request is sent to the platform access device. After the asynchronous operation request is sent to the service center through the platform access device, the service center performs a status query on the asynchronous call interface, obtains the query result, and returns the query result to the platform.
7. A platform access device, characterized in that: The device comprises: A receiving module, configured to receive access requests from at least two platform access service centers; An acquisition module, configured to acquire resource information of the underlying basic service of the service center according to the access request, so as to manage the underlying basic service components of the service center; a sending module, configured to return the resources allocated to each of the at least two platforms; The receiving module is also used to: receive a resource query request for the second service instance sent by each of the at least two platforms, send the resource query request for the second service instance to the service center, and the service center returns the resources corresponding to the second service instance to the platform according to the resource query request.
8. A platform, characterized in that: include: A sending module, configured to send an access request to the platform access service center to the platform access device; a receiving module, configured to receive resource information of the underlying basic service allocated by the service center to the platform according to the access request, returned by the platform access device, wherein the platform access device manages the underlying basic service components of the service center; The sending module is also used to: send a resource query request for the second service instance to the platform access device. After the resource query request of the second service instance is sent to the service center through the platform access device, the service center returns the resources corresponding to the second service instance to the platform according to the resource query request.
9. A computing device comprising: A processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform an operation corresponding to the method for platform access service center according to any one of claims 1 to 4 or an operation corresponding to the method for platform access service center according to any one of claims 5-6.
10. A computer storage medium, wherein the storage medium stores at least one executable instruction, wherein the executable instruction causes a processor to perform an operation corresponding to the method for accessing a platform service center as described in any one of claims 1 to 4 or an operation corresponding to the method for accessing a platform service center as described in any one of claims 5 to 6.
Citation Information
Patent Citations
Resource access method, device and system under server-free architecture and storage medium
CN112019475A
Resource allocation method for multi-tenant distributed storage request service
CN112165508A