Saas service processing method and system, and device and storage medium

Abstract

Provided in the embodiments of the present disclosure are a SaaS service processing method and system, and a device and a storage medium. The system comprises: a service provider, a service user and a PaaS platform, which are located in different VPCs, wherein the VPCs where the service user, the service provider and the PaaS platform are respectively located are interconnected, that is, network isolation among the three parties is relieved. The PaaS platform can further use local routing information to realize communication between the service user and the service provider, such that the service user can use any SaaS service which is published on the PaaS platform and provided by any service provider located in any VPC, thereby improving the use convenience of a service user in respect of services in a PaaS platform.

Description

[0001] SaaS Service Processing Method, System, Device, and Storage Medium Cross-Reference This disclosure claims priority to Chinese patent application No. 202311862082.6, filed with the Patent Office of China on December 29, 2023, entitled "SaaS Service Processing Method, System, Device, and Storage Medium," the entire contents of which are incorporated herein by reference. Technical Field This disclosure relates to the field of cloud computing technology, and more particularly to a SaaS service processing method, system, device, and storage medium. Background Cloud computing service models can include Software as a Service (SaaS) and Platform as a Service (PaaS). PaaS is a model that provides a software development platform to users as a service, while SaaS is a service model that provides software applications over the Internet. In practice, different service providers can publish their SaaS services on a PaaS platform, using the PaaS platform as a service marketplace containing multiple SaaS services for service users to choose from. Both service providers and service users can be located in a virtual private cloud (VPC) network. When service providers and service users are in different VPCs, network isolation prevents service users from conveniently using the various SaaS services published on the PaaS platform. Therefore, achieving convenient use of SaaS services has become an urgent issue to be addressed. SUMMARY OF THE INVENTION In view of this, embodiments of the present disclosure provide a SaaS service processing method, system, device, and storage medium to enable service users to conveniently use SaaS services. In a first aspect, embodiments of the present disclosure provide a SaaS service processing system, comprising: a service provider, a service consumer, and a Platform as a Service (PaaS) platform, wherein the VPCs of the service provider, the service consumer, and the PaaS platform are interconnected; the service consumer is configured to send a request to use any Software as a Service (SaaS) service published on the PaaS platform to the PaaS platform, and receive a response corresponding to the request forwarded by the PaaS platform;

[0002] The PaaS platform is configured to forward a usage request to a target service provider providing any SaaS service based on the network address in the routing information. The target service provider is configured to respond to the usage request and send a response corresponding to the usage request to the PaaS platform. In a second aspect, embodiments of the present disclosure provide a SaaS service processing method, applied to a Platform as a Service (PaaS) platform, comprising: receiving a usage request from a service consumer, the usage request corresponding to any Software as a Service (SaaS) service published on the PaaS platform; forwarding the usage request to the target service provider providing any SaaS service based on the network address in the routing information; and sending a response generated by the target service provider to the service consumer. The PaaS platform, the service consumer, and the service provider are interconnected in their virtual private clouds (VPCs). In a third aspect, embodiments of the present disclosure provide a method for processing a SaaS service, applicable to a service consumer, comprising: sending a usage request corresponding to any Software as a Service (SaaS) service published on a Platform as a Service (PaaS) platform to the PaaS platform; and receiving a response generated by the service provider, wherein the response corresponds to the usage request, and the PaaS platform, the service consumer, and the service provider are located in different virtual private clouds (VPCs). In a fourth aspect, embodiments of the present disclosure provide a method for processing a SaaS service, applicable to a service provider, comprising: receiving a usage request from a service consumer for any Software as a Service (SaaS) service published on a Platform as a Service (PaaS) platform; responding to the usage request to obtain a response; and sending the response required by the service consumer, wherein the PaaS platform, the service consumer, and the service provider are located in interconnected virtual private clouds (VPCs). In a fifth aspect, embodiments of the present disclosure provide an electronic device, comprising a processor and a memory, wherein the memory is configured to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method for processing a SaaS service according to the second aspect. The electronic device may also include a communication interface for communicating with other devices or a communication network. In a sixth aspect, embodiments of the present disclosure provide an electronic device comprising a processor, a memory, and a network access module. The electronic device utilizes the network access module to interconnect the electronic device with a virtual private cloud (VPC) hosting a Platform as a Service (PaaS) platform. The memory is configured to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the SaaS service processing method of the third or fourth aspect. The electronic device may further include a communication interface for communicating with other devices or a communication network.In a seventh aspect, embodiments of the present disclosure provide a computer-readable storage medium storing computer instructions. When the computer instructions are executed by one or more processors, the one or more processors execute the SaaS service processing method according to the second, third, or fourth aspect. In an eighth aspect, embodiments of the present disclosure provide a computer program product comprising a computer program. When executed by a processor, the computer program implements the SaaS service processing method according to the second, third, or fourth aspect. Embodiments of the present disclosure provide a SaaS service processing system. In this system, the VPCs of a service provider, a service consumer, and a PaaS platform located in different VPCs are interconnected. When a service consumer needs to use any SaaS service published on the PaaS platform, it can send a request to use any SaaS service to the PaaS platform. The PaaS platform can forward the request to the target service provider providing the SaaS service based on the network address in the local routing information. The target service provider can respond to the request to obtain a response result, which it then sends to the PaaS platform. The PaaS platform ultimately sends the response result to the service consumer, thereby enabling the use of any SaaS service on the PaaS platform. In the above solution, the VPCs of the service user, service provider, and PaaS platform are interconnected, effectively removing the network isolation between the three parties. After network isolation is removed, the PaaS platform can leverage its own routing information to facilitate communication between the service user and service provider. This allows the service user to use any SaaS service published on the PaaS platform and provided by any service provider in any VPC, thereby improving service convenience. Furthermore, since all three parties in the system are in VPCs, this indicates a high level of security. Therefore, using the above system can also improve service security. BRIEF DESCRIPTION OF THE DRAWINGS To more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly describes the figures required in the embodiments or descriptions of the prior art. Obviously, the figures described below represent some embodiments of the present disclosure. Those skilled in the art can derive other figures based on these figures without inventive effort.Figure 1 is a structural diagram of a processing system for a SaaS service provided in an embodiment of the present disclosure; Figure 2 is a schematic diagram of the interface of a homepage provided by a PaaS platform provided in an embodiment of the present disclosure; Figure 3 is a schematic diagram of the interface of a service details page provided by a PaaS platform provided in an embodiment of the present disclosure; Figure 4 is a structural diagram of a processing system for another SaaS service provided in an embodiment of the present disclosure; Figure 5 is a schematic diagram of the structure of a processing system for yet another SaaS service provided in an embodiment of the present disclosure; Figure 6 is a schematic diagram of the structure of a processing system for yet another SaaS service provided in an embodiment of the present disclosure; Figure 7 is a schematic diagram of the configuration interface of a SaaS service provided by a PaaS platform provided in an embodiment of the present disclosure; Figure 8 is a schematic diagram of the management interface of a SaaS service provided by a PaaS platform provided in an embodiment of the present disclosure; Figure 9 is a flow chart of a processing method for a SaaS service provided in an embodiment of the present disclosure; Figure 10 is a flow chart of a processing method for another SaaS service provided in an embodiment of the present disclosure; Figure 11 is a flow chart of a processing method for yet another SaaS service provided in an embodiment of the present disclosure; Figure 12 is a structural diagram of a processing device for a SaaS service provided in an embodiment of the present disclosure; Figure 13 is a structural diagram of an electronic device provided in an embodiment of the present disclosure; Figure 14 is a structural diagram of a processing device for another SaaS service provided in an embodiment of the present disclosure; Figure 15 is a structural diagram of another electronic device provided in an embodiment of the present disclosure; Figure 16 is a schematic diagram of the structure of a processing device for a SaaS service provided in an embodiment of the present disclosure; Figure 17 is a schematic diagram of the structure of another electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION To further clarify the objectives, technical solutions, and advantages of the embodiments of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments represent only a portion of the embodiments of the present disclosure, but not all of them. All other embodiments devised by persons of ordinary skill in the art without inventive effort based on the embodiments of the present disclosure are within the scope of protection of the present disclosure. The terms used in the embodiments of the present disclosure are intended solely to describe specific embodiments and are not intended to limit the present disclosure. As used in the embodiments of the present disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. "A plurality" generally includes at least two, but does not exclude the inclusion of at least one.It should be understood that the term "and / or" as used herein is merely a description of an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. Furthermore, the character " / " in this document generally indicates that the associated objects are in an "or" relationship. Depending on the context, the words "if" and "if" as used herein can be interpreted as "at the time" or "when" or "in response to determining" or "in response to identifying." Similarly, depending on the context, the phrases "if it is determined" or "if (the stated condition or event) is identified" can be interpreted as "when determined" or "in response to determining" or "when identifying (the stated condition or event)" or "in response to identifying (the stated condition or event)." It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. The collection, use, and processing of the relevant data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse. It should also be noted that the terms "include," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion. Thus, a product or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such product or system. Without further restriction, an element defined by the phrase "comprising a..." does not preclude the presence of other identical elements in the product or system comprising said element. Before describing the following embodiments of the present disclosure in detail, the roles involved in this disclosure are explained: the service provider, i.e., the party that develops, publishes, and maintains the SaaS service; and the service user, i.e., the party that uses the SaaS service. Furthermore, the relationship between the service user and the service provider can satisfy a client / server (C / S) architecture.

[0003] The PaaS platform supports service providers in publishing SaaS services and also serves as a platform for service users to use SaaS services. Service providers and service users can be considered users of the PaaS platform. The PaaS platform also manages SaaS services, as well as the service providers and service users who serve as users. For example, it authenticates service providers, restricts illegal service providers and service users from accessing the PaaS platform (i.e., restricts illegal service providers from publishing SaaS services and restricts illegal service users from using SaaS services), deletes their account information, and removes illegal SaaS services from the platform. The above description of roles is based on their functionality. As will be readily understood, the aforementioned functions of the roles are implemented by deploying them on electronic devices. Therefore, the PaaS platform, service providers, and service users mentioned in the following embodiments of this disclosure specifically refer to the electronic devices corresponding to the roles. Before describing the following embodiments of the present disclosure in detail, a brief description of the background of the present disclosure is provided. As described in the background, in practice, service users and service providers can reside in different VPCs. Furthermore, different service providers can also reside in different VPCs. In one scenario, a PaaS platform and service users reside in the same VPC, but the PaaS platform also provides SaaS services from service providers in other VPCs. In this case, network isolation can lead to the problem mentioned in the background: the service user cannot conveniently use any SaaS service published on the PaaS platform. Specifically, the service user uses the PaaS platform to access services provided by service providers in the same VPC, limiting their access to SaaS services. In a more serious scenario, if the PaaS platform and service provider reside in different VPCs, network isolation can prevent the service user from even using the SaaS services provided by the PaaS platform. In the presence of network isolation, to enable service users to use any SaaS service published on a PaaS platform, the systems and methods provided in the following embodiments of this disclosure can be used. The following detailed description of some implementations of this disclosure is provided in conjunction with the accompanying drawings. The following embodiments and their features can be combined unless they conflict with each other. Furthermore, the sequence of steps in the following method embodiments is provided as an example only and is not a strict limitation. Figure 1 is a schematic diagram of the structure of a SaaS service processing system provided in an embodiment of this disclosure.As shown in Figure 1, the system may include a service provider, a service consumer, and a PaaS platform. Initially, the service provider, service consumer, and PaaS platform may be deployed in different VPCs. The different VPCs of the three can include various scenarios: different VPCs, or any two of the three may be in the same VPC while the other is in a different VCP. For example, the service provider and PaaS platform may be in the same VPC while the service consumer is in a different VCP, or the service provider and service consumer may be in the same VPC while the PaaS platform is in another VPC. When the three VPCs are different, the service consumer can interconnect its own VPC with the VPC of the PaaS platform, thereby breaking the network isolation between the service consumer and the PaaS platform and enabling communication between the service consumer and the PaaS platform. Optionally, this network interconnection can be achieved using a network access module deployed internally within the service consumer. Optionally, the network access module can be implemented as a network interface card. The service provider can also interconnect its own VPC with the VPC of the PaaS platform. The specific implementation of this interconnection can be similar to that of the service consumer. In this case, there is no network isolation between the service consumer, service provider, and PaaS platform. When the service provider or service consumer and the PaaS platform are in the same VPC, the aforementioned network interconnection process is unnecessary. In other words, only when the three parties are in different VPCs does the network access module configured internally by the service provider and service consumer play a role in network interconnection. Based on this, the specific operation of the system is described in detail below: In practice, SaaS services published by different service providers on the PaaS platform can be displayed on the PaaS platform homepage in the form of a text directory or a combination of text and images. Optionally, this display can be as shown in Figure 2. The PaaS platform can serve as a service marketplace containing multiple SaaS services. SaaS services published on the PaaS platform may include Vehicle Identification Number (VIN) query, real-name authentication, weather forecast query, and so on. Vehicle Identification Code Query is used to parse the vehicle identification code to obtain vehicle information and provide functions such as the primary service provider, date (e.g., 2023-09.27), free trial, service details, and purchase. Real-name Authentication is used to verify identity information and provides functions such as the secondary service provider and date (e.g., 2023-09.26).Weather forecast queries are used to query data such as temperature, humidity, rain, snow, and wind speed, and provide functions such as third-party service providers and dates (e.g., 2023-09.28). Service users can then select or search for any desired SaaS service on the homepage, thereby generating a request to use that service. This request can be sent to the PaaS platform. Regarding the service user's selection of any SaaS service, one option is for the service user to directly select it on the PaaS platform's homepage or search results page. Alternatively, the service user can perform further operations on the PaaS platform's search results page or the homepage shown in Figure 2 to obtain the service details page shown in Figure 3. Based on the content displayed on the service details page, the service user can determine whether the SaaS service meets their needs. The service user can then directly select the SaaS service on the service details page. As shown in Figure 2, the PaaS platform's homepage displays the service name, service content, release date, service provider, and contact information for each SaaS service. As shown in Figure 3, the service details page displays the SaaS service's service name, usage method, delivery format (such as API or data), and payment rules. The service name is real-name authentication service, and the payment rules are for purchase, renewal, and pricing information. Please visit the PaaS platform sales page for operation and review (a link is provided). Usage methods refer to API information related to the purchased service (a link is provided). Free trial and purchase options are provided below. The information shown in both figures can be considered the service details of the SaaS service, which is clearly visible to service users. Information query services are typically delivered via API, such as the aforementioned VIN query, payment card real-name authentication, and identity real-name authentication. Data warehouse services are typically delivered via data, such as the aforementioned weather forecast query service. The PaaS platform can then respond to the usage request and, based on its routing information, forward the request to the target service provider of the SaaS service. The target service provider may be one of the multiple service providers in Figure 1. The routing information stored in the PaaS platform may include network addresses of different service providers that publish SaaS services in the PaaS platform.Alternatively, different service providers may be located in the same VPC, in different VPCs in the same region, or in different VPCs in different regions. For example, the different service providers providing services to the PaaS platform may include service providers 1 through 4. Service provider 1 may be located in VPC 1 in region 1, service providers 2 and 3 may be located in VPC 2 in region 1, and service provider 4 may be located in VPC 1 in region 1. Therefore, in the above example, service providers 1 and 2 are located in different VPCs in the same region, service providers 1 and 4 are located in different VPCs in different regions, and service providers 2 and 3 are located in the same VPC in the same region. It should be noted that this disclosure does not limit the region or VPC in which service providers are located; any service provider can be located in any VPC in any region. The target service provider can then respond to the usage request forwarded by the PaaS platform to obtain a response. Optionally, the content of the response result is related to the delivery format of the SaaS service. For services delivered as APIs, the response result generated by the target service provider is the API interface information. For services delivered as data, the response result generated by the target service provider is the data required by the service consumer. Since the target service provider has already connected to the VPC where the PaaS platform resides through its own network access module, it can use its own network access module to directly send the response result of the usage request to the PaaS platform. Ultimately, the service consumer can receive the response result forwarded by the PaaS platform, thus enabling the use of any SaaS service. In this embodiment, the VPCs of the service provider, service consumer, and PaaS platform, which are located in different VPCs, are interconnected. When a service consumer needs to use any SaaS service, it can send a request to use this SaaS service to the PaaS platform. The PaaS platform can forward the request to the target service provider providing this SaaS service based on the network address in its local routing information. The target service provider can respond to the request to obtain a response result and send the response result to the PaaS platform. The PaaS platform will eventually send the response result to the service user, thus enabling the use of any SaaS service on the PaaS platform.In the above solution, the VPCs where the service user, service provider, and PaaS platform reside are interconnected, effectively removing the network isolation between the three parties. After removing the network isolation, the PaaS platform can use its own routing information to facilitate communication between the service user and service provider, allowing the service user to use any SaaS service published on the PaaS platform and provided by any service provider in any VPC, thereby improving the convenience of service use. Furthermore, since all three parties in the system are in VPCs, this indicates a high level of security for all three parties. Therefore, using the above system can also improve service security. The technical effects achieved by the systems provided in the above and following embodiments of the present disclosure can also be understood in conjunction with the following: When the PaaS platform, service provider, and service user are located on the public network, the PaaS platform and the SaaS services published on it can be deployed on a cloud server providing Elastic Compute Service (ECS) on the public network. The ECS cloud server's network address on the public network can be exposed to service users, who can then directly access the network address to use the SaaS service. Optionally, to improve network stability and service security, a server load balancing (SLB) device and / or an application programming interface (API) gateway can also be provided on the public network. In this case, instead of exposing the ECS cloud server's network address to the service user, the SLB device or API gateway's network address on the public network can be exposed to the service user. The service user can then indirectly access the ECS cloud server by accessing the SLB device or API gateway, thereby using the SaaS service. In this case, for service users on the public network with a lower security level, these users are more likely to launch attacks on the PaaS platform, thereby affecting the normal use of the SaaS service. On the other hand, the complex and unstable public network environment can lead to high latency when using SaaS services, but this doesn't work for some service users who require low latency. Furthermore, some service users in VPCs with strict data security requirements cannot use SaaS services on PaaS platforms located on the public network.Using the systems provided by various embodiments of the present disclosure, both the service provider and the service consumer are deployed in a VPC. Their respective network access modules can eliminate the network isolation between them and the PaaS platform, allowing service consumers to use SaaS services within the VPC environment. Compared to the public network, VPCs offer greater security and stability, and service consumers within VPCs are also more secure. Therefore, while reducing the likelihood of attacks on the PaaS platform, latency is also reduced. Furthermore, since the SaaS services on the PaaS platform are published within the VPC, service consumers within the VPC can also use the SaaS services normally. Optionally, for the PaaS platform in the systems provided by various embodiments of the present disclosure, the VPC within which the PaaS platform resides can include various structures, such as at least one VPC within the same region, at least one VPC within different regions, or at least one VPC within the same region and at least one VPC within different regions. Optionally, any two VPCs within the PaaS platform can be connected via an interconnection medium, eliminating network isolation between them. Optionally, for any two VPCs in the same region, the interconnection medium can specifically be a private network connection (PrivateLink) between the two VPCs in the same region or a network card with cross-account mounting capabilities. This interconnection medium can be considered a same-region interconnection module that enables interconnection between different VPCs in the same region. Optionally, for any two VPCs in different regions, the interconnection medium between them can be a VPC peering connection or a routing and forwarding device set up between two VPCs in different regions. This routing and forwarding device can serve as a Cloud Enterprise Network (CEN). This interconnection medium can be considered a cross-region interconnection module that enables interconnection between different VPCs in different regions. Optionally, the VPCs in which the service user, service provider, and PaaS platform reside can also be located in different regions, that is, the service provider and service user are located in VPCs in different regions. Assuming that the VPC in which the PaaS platform resides includes multiple VPCs in different regions, from the perspective of network distribution, the SaaS service processing system provided by the present disclosure can also be represented as shown in Figure 4.In Figure 4, the service consumer is in VPC1 in Region A, the service provider is in VPC2 in Region B, and the PaaS platform is in VPC3 and VPC4 in Region A, VPC5 in Region C, and VPC6 in Region B. The service provider can deploy its SaaS services in VPC2. In this case, the service consumer can access VPC3 using its own network access module, and the service provider can access VPC6 using its own network access module. Furthermore, interconnection between adjacent VPCs in VPC3 through VPC6 can also be achieved within the PaaS platform. The combined use of network access modules and interconnection media enables service consumers, service providers, and the PaaS platform, located in different VPCs in different regions, to connect to a single network, eliminating network isolation between them. In this embodiment, the combined use of a network access module and interconnection medium enables interconnection between different VPCs in different regions of the service consumer and service provider and the VPC of the PaaS platform. The process described in the embodiment shown in FIG1 can then be used to enable the service consumer to use any SaaS service published on the PaaS platform. Optionally, the network access module and interconnection medium in the embodiment shown in FIG4 can constitute the network connection system in this embodiment. Furthermore, for details not described in detail in the above embodiments related to the network connection system and the technical effects achievable, please refer to the relevant descriptions of the above embodiments and will not be elaborated here. Based on the system shown in FIG4 , the technical effects achievable in the above and following embodiments of this disclosure can also be understood in conjunction with the following: When the service consumer, service provider, and PaaS platform are deployed in different VPCs, and the service provider and service consumer are in the same region, the service consumer can first subscribe to the SaaS service on the PaaS platform. After receiving the subscription request, the service provider can independently grant the service user access to the SaaS service. Specifically, in response to the service subscription, the service provider adds the service user to the SaaS service's corresponding list, thereby enabling point-to-point communication between the service user and the SaaS service, allowing the service user to use the SaaS service normally. However, in this approach, the service provider needs to grant access to the service user at the same time as publishing the SaaS service, which significantly increases the service provider's processing pressure. Furthermore, the service provider only provides point-to-point communication between the service user and the subscribed SaaS service.As the number of service users and SaaS services increases, the number of subscription requests generated by service users will also increase. Since service providers cannot establish connections between service users and multiple SaaS services in batches, they must frequently perform the aforementioned permission activation operation, further increasing their processing pressure. However, the system provided by various embodiments of the present disclosure, through the network access module, enables interconnection between the VPCs of service users and the PaaS platform, enabling access to any SaaS service on the PaaS platform. This effectively establishes a point-to-point connection between service users and SaaS services on the PaaS platform. Furthermore, the connection process requires no involvement from either service users or service providers, thereby reducing processing pressure on service providers and improving their user experience. Furthermore, in practice, different service providers may be located in different VPCs in different regions. Considering network isolation, to enable service users to access any service on the PaaS platform, service providers must deploy their SaaS services in different regions, increasing deployment costs for service providers. Using the system provided by the embodiments of the present disclosure, service providers can deploy their SaaS services within the VPCs in their respective regions. By leveraging the interconnectivity between different VPCs within the PaaS platform, network isolation between VPCs can be eliminated. This eliminates network isolation between service providers within different VPCs within the PaaS platform. Service consumers can use any service on the PaaS platform, thereby reducing deployment costs for service providers. Corresponding to the system shown in Figure 4 , the PaaS platform's structure will be further described from a functional perspective. Figure 5 is a schematic diagram of the structure of another SaaS service processing system provided by the embodiments of the present disclosure. As shown in Figure 5 , the PaaS platform in this system may specifically include a network connection system. As can be seen from the above embodiments, the PaaS platform uses its stored routing information to forward usage requests and responses. This forwarding function can be implemented by the network connection system within the PaaS platform. To forward usage requests, the network connection system can receive usage requests sent by service consumers. Alternatively, the network connection system may determine the target network address corresponding to any SaaS service from routing information stored on the PaaS platform based on the service network parameters in the usage request. The network connection system may then forward the usage request to the target service provider with the target network address based on a preset routing policy.Optionally, the forwarding function of the aforementioned network connection system can be specifically performed by a routing module in the network connection system. Optionally, based on the embodiment shown in FIG1 , the service details information can further include a service domain name. Service network parameters can specifically include the port number corresponding to the SaaS service, the protocol used, the VPC where the service is located, the network address of the service provider, and the like. Protocols can include User Datagram Protocol (UDP) and Hypertext Transfer Protocol (HTTP). The service network parameters herein and the service details information in the embodiment shown in FIG1 can together constitute the attribute information of the SaaS service, and both can be configured by the service provider when the service is released. As can be seen from the various examples above, the service details information in the attribute information can be textual information describing the details of the SaaS service and can be directly displayed to the service user. The service network parameters in the attribute information can be parameters configured to ensure the normal operation of the service in the network and can be hidden from the service user. Based on the embodiment shown in Figure 1, routing information may include not only the network addresses of different service providers publishing SaaS services on the PaaS platform, but also a mapping relationship between network addresses and service domain names. In determining the target network address based on the service network parameters, the network connection system may optionally use the mapping relationship to resolve the service domain name in the service network parameters and compare the resolved network address with the network address corresponding to a service provider stored in the routing information to see if it matches. If the resolved network address is included in the routing information, the resolved network address is determined as the target network address of the target service provider providing any SaaS service. Regarding forwarding the response result, the network connection system may forward the response result based on the routing information and the network address of the service consumer in the usage request. In this embodiment, the network connection system in the PaaS platform can implement routing and forwarding of usage requests and response results, thereby ensuring that service consumers can conveniently use any SaaS service published on the PaaS platform. Based on the system shown in FIG5 , further, before the service provider responds to a usage request generated by a service user, in order to improve the availability and security of the SaaS service, the network connection system may also verify the usage request to identify whether there are any illegal usage requests that may affect the availability and security of the service.The network connection system can identify the data volume and / or data content of the usage request to determine the legitimacy of the usage request received by the network connection system, namely, whether the usage request constitutes a Distributed Denial of Service (DDoS) attack or other network attack. If the data volume of the usage request exceeds a preset amount, indicating a large number of abnormal requests from the service user, the network connection system can determine that the usage request constitutes a DDoS attack or other network attack and directly intercept the illegal usage request. If the data content in the usage request does not match the content of the SaaS service provided by the service provider, for example, if the data content in the usage request indicates that the user needs to request weather data, but the SaaS service provided by the service provider is a real-name authentication service, indicating a clear inconsistency between the two contents, the network connection system can also directly intercept the illegal usage request. Optionally, the above process can be specifically implemented by a security verification module in the network connection system. In this embodiment, the network connection system is used to intercept illegal requests, preventing the SaaS service from responding to such illegal requests, thereby ensuring the availability and security of the SaaS service. Furthermore, by ensuring service security through the network connection system, the processing pressure on service users can be reduced. Based on the system shown in FIG5 , the network connection system can further verify the legitimacy of any selected SaaS service during the use of the service user to ensure the legitimacy of the SaaS service. It should be noted that the legitimacy of the SaaS service in this embodiment focuses on whether the response corresponds to the service content of the SaaS service. Therefore, the legitimacy of the SaaS service in this embodiment can also be considered as the compliance of the SaaS service. This service legitimacy verification can be specifically implemented by the legitimacy verification module in the network connection system. Regarding legitimacy verification, one optional method is to verify the data content of the response sent by the target service provider to determine whether the SaaS service provided by the target service provider complies with the service details. Alternatively, the network connection system can verify the data content of the response based on the data type of the response. Taking the weather query service mentioned in the embodiment shown in FIG. 1 as an example, when the network connection system identifies that the type of data in the response result is a value, the network connection system can identify that the data content of the response result is weather data.The network connection system can determine whether the SaaS service actually provided by the target service provider matches the service details of the SaaS service, and that the SaaS service provided by the target service provider is legitimate. Optionally, the network connection system can also identify the data content of the response result based on the data range of the response result. Again, using the weather query service mentioned in the embodiment shown in FIG1 as an example, if the network connection system identifies that the data in the response result ranges from 100 to 1000, which clearly exceeds the temperature range, the network connection system can identify that the data content of the response result is not weather data. The network connection system can determine that the SaaS service actually provided by the target service provider does not match the service details of the SaaS service, and that the SaaS service provided by the target service provider is illegal. In this embodiment, the network connection system is used to determine whether the response result is legitimate, thereby further ensuring the legitimacy of the SaaS service. Based on the system shown in FIG5 , further, during the process of a service user using any selected SaaS service, the network connection system can optionally count the data volume of the response result sent by the target service provider and, based on this data volume, further determine the service user's resource consumption. It should be noted that the resources referred to here do not refer to the computing resources and / or network resources required during the use of SaaS services, but rather to the cost resources required by the service user to use the SaaS service. Therefore, the above process actually involves billing the service user based on the data volume during the use of the SaaS service. Optionally, the above billing process can also be implemented by a billing module in the network connection system. In this embodiment, the network connection system can also provide billing functions while ensuring the availability, security, and legality of the SaaS service. Optionally, based on the system shown in Figure 5, Figure 6 is a schematic structural diagram of another SaaS service processing system provided in an embodiment of the present disclosure. As shown in Figure 6, the PaaS platform can further include a service management system. Data communication can exist between the service management system, network connection system, and user management system and each service provider. Figure 6 schematically illustrates the communication between a service provider and different systems. Optionally, the service management system can manage SaaS services provided by different service providers at different stages, and this management can involve both the release and use stages of the SaaS service. Service release can specifically include the service deployment stage and the service launch stage.Optionally, during the service deployment phase, the service provider can trigger a service configuration operation on the configuration interface provided by the PaaS platform to configure the SaaS service's attribute information on that interface. The attribute information configured by the service provider can be stored in the PaaS platform's database for sharing with the service management system, user management system, and network connection platform. As described in the embodiments shown in Figures 1 and 5 , the SaaS service's attribute information specifically includes service details and service network parameters. As shown in the embodiment shown in Figure 1 , the service details may include information visible to the service user, such as the service name, service content, release time, service provider and contact information, SaaS service usage methods, delivery methods, and payment rules. As shown in the embodiment shown in Figure 5 , the service network parameters may include information invisible to the service user, such as the corresponding port number, service domain name, usage protocol, the VPC where the service resides, and the network address of the service provider. Optionally, the configuration interface shown in FIG7 schematically illustrates several configuration options for attribute information. As shown in FIG7 , the configuration interface may include multiple configuration items, such as the service name, service domain name, VPC where the service resides, protocol, and port number. These multiple configuration items may include at least "Select a service," "Enter a service domain name," "Select a VPC," "Select a protocol," and "Enter a port range." The service management system may then further verify the SaaS service based on the attribute information of the SaaS service. In one optional verification method, if the service management system verifies that the service provider name included in the service details in the attribute information is compliant, it can determine that the service provider is a highly secure service provider certified by the PaaS platform. If the service provider is authenticated, the service management platform may deem the SaaS provided by the service provider legitimate, and the service management system may publish the SaaS service provided by the service provider on the PaaS platform. The publishing process can be described in the "Service Launch Phase" below. This verification process can be considered as a pre-release verification of the service's legitimacy. Optionally, the service management system can also verify whether any illegal terms are used in the service details. If no illegal terms are used in the service details, the service management system determines that the SaaS service is legal. Legality here can also be considered the compliance of the SaaS service. In practice, the service management system can select at least one of the multiple verifications described above.Optionally, after the SaaS service configuration is complete, the network connection system can also directly read the SaaS service's attribute information from the database, obtain the service provider's network address from the attribute information, and store the network address as routing information. During the service launch phase, if the service management system can first determine that the SaaS service provided by the service provider is legal and compliant in the manner described above, the service management system can set the attributes of the storage service details field in the database to visible. The service details information will then be displayed on the PaaS platform page, completing the SaaS service launch. As the SaaS service continues to upgrade, the service provider can optionally trigger an edit operation on the management interface provided by the service management system to edit the attribute information of the SaaS service it provides. Similarly, the service provider can also use this service management system to delete the entire SaaS service. The service management system can edit the attribute information of the SaaS service in response to the service provider's edit operation on the SaaS service. Furthermore, during the use of any SaaS service selected by the service user, if the network connection system determines that the SaaS service is illegal, the service management system can automatically delete the SaaS service, effectively taking the SaaS service offline. Optionally, the management interface may be as shown in FIG8 , including the service name, connection status, service protocol and port, and operations. The service provider can perform operations such as "online," "modify," and "delete" on the service. Furthermore, as shown in FIG8 , the service provider can also view the connection status of different SaaS services in this interface, such as "to be launched," "online in progress," and "already online." Service names may include real-name authentication and weather forecast query, service protocols may include Transmission Control Protocol (TCP) and User Datagram Protocol (UDP), and ports may include 23, 3389, 3305, 1521, 9093, 9095, and the like. Optionally, the PaaS platform provided in this embodiment may also include a user management system. Both service providers and service users can serve as users of the PaaS platform. The user management system can store account information for service users and service providers and verify the service provider's service publishing permissions based on the stored account information. Service providers without publishing permissions can be granted the ability to view SaaS services on the PaaS platform.The service provider's account information may include historical service release information or modification information. The service provider's historical release information may reflect the SaaS released by the service provider within a historical period. Similarly, historical modification information may reflect modifications made by the service provider to the released SaaS within a historical period. Optionally, if the user management system identifies illegal SaaS service releases or modifications by the service provider, it may determine that the service provider does not have SaaS release authority. The user management system may also verify whether the service user has permission to use the SaaS service based on the account information. Specifically, the user management system may receive usage requests generated by the service user and, upon determining that the service user has permission, forward the usage requests through the network connection system. The service user's account information may include historical usage behavior. Usage behavior may reflect the time period, frequency, and number of usage requests generated by the service user within a historical period. A high frequency of numerous usage requests within a short period of time may indicate abnormal usage behavior. Optionally, if the user management system identifies that the service user generating the usage request has engaged in abnormal usage behavior within a historical period, it can determine that the service user does not have SaaS usage rights. In this embodiment, utilizing the service management system and user management system within the PaaS platform enables better management of service providers and service users, thereby further improving the security and availability of SaaS services and enhancing the convenience of SaaS services for service users. Furthermore, as shown in the embodiment illustrated in FIG4 , the PaaS platform can be located in different VPCs. Optionally, the user management system and service management system mentioned in this embodiment can be deployed in the same VPC as the PaaS platform, and the account information stored by the user management system and the SaaS service attribute information stored by the service management system deployed in different VPCs can be shared. Based on the above system embodiment, the SaaS service processing process will be described below from a method perspective. FIG9 is a flowchart of a SaaS service processing method provided in an embodiment of the present disclosure. This method provided in an embodiment of the present disclosure can be executed by the PaaS platform in the system illustrated in each of the above embodiments. As shown in FIG9 , the method may include the following steps:

[0004] 5101, receiving a usage request sent by a service user, where the usage request corresponds to any SaaS service published on the PaaS platform.

[0005] 5102, forward the usage request to the target service provider that provides any SaaS service according to the network address in the routing information.

[0006] 5103, sending the response result generated by the target service provider to the service user, wherein the VPCs where the PaaS platform, the service user, and the service provider are located are interconnected.

[0007] The PaaS platform can forward usage requests and responses using its stored routing information. Specifically, the PaaS platform receives a usage request from a service consumer, where the request corresponds to any SaaS service published on the PaaS platform. The PaaS platform then forwards the request to the target service provider of any SaaS service based on the network address in the routing information.

[0008] The specific content of the routing information stored by the PaaS platform can be found in the description of the embodiment shown in FIG1 and will not be repeated here. Regarding forwarding the response result, the PaaS platform can forward the response result based on the routing information and the network address of the service consumer included in the usage request, i.e., send the response result generated by the target service provider to the service consumer. Optionally, the implementation of the interconnection between the PaaS platform, the service consumer, and the VPC in which the service provider resides can be found in the description of the embodiment shown in FIG1 and will not be repeated here. In this embodiment, the process of receiving the usage request, forwarding the usage request, and sending the response result can all be found in the description of the aforementioned embodiments and will not be repeated here. In this embodiment, the PaaS platform can receive a usage request sent by a service consumer and, based on the network address in the local routing information, forward the usage request to the target service provider providing any SaaS service. The target service provider generates a response result corresponding to the usage request and sends the response result to the PaaS platform using its own configured network access module. The PaaS platform ultimately sends the response result to the service consumer, thereby enabling the use of any SaaS service on the PaaS platform. In the above method, the PaaS platform can use its own routing information to enable communication between service users and service providers, allowing service users to use any SaaS service published on the PaaS platform and provided by any service provider in any VPC, thereby improving the convenience of service use. On the other hand, since the three parties in the system are in a VPC, it indicates that the three parties have a high security level. Therefore, using the above system can also improve the security of the service. In addition, the technical effects achieved by this embodiment can also be seen in the embodiments shown in Figures 1 to 8 above. Peer connection between different VPCs in the same region and / or different regions. For related content, please refer to the relevant description in the embodiment shown in Figure 4 above, which will not be repeated here. Optionally, the PaaS platform that executes the method shown in Figure 9 may further include a network connection system, a service management system, and a user management system. In the embodiment shown in Figure 9, the forwarding of usage requests and response results can be implemented by the network connection system. The service management system can manage SaaS services provided by different service providers in the service publishing stage and the usage stage. The user management system can manage service providers and service users. The specific working processes of different systems in the PaaS platform can also be referred to the relevant description in the above embodiments, which will not be repeated here. Figure 10 is a flowchart of another SaaS service processing method provided by an embodiment of the present disclosure. The method provided by the embodiment of the present disclosure can be executed by the service user in the system shown in the above embodiments. As shown in Figure 10, the method may include the following steps:

[0009] 5201, sending a usage request corresponding to any SaaS service published on the PaaS platform to the PaaS platform.

[0010] At step 5202, a response result generated by the service provider is received. The response result corresponds to the usage request, and the VPCs of the PaaS platform, the service consumer, and the service provider are interconnected. Initially, the PaaS platform, the service consumer, and the service provider may be deployed in different VPCs. In this case, the VPCs of the PaaS platform, the service consumer, and the service provider can be interconnected, thereby breaking through the network isolation between the service consumer and the PaaS platform and enabling communication between the service consumer and the PaaS platform. Alternatively, the specific implementation of the interconnection can be found in the description of the embodiment shown in FIG. 1 and will not be repeated here. After VPC interconnection is achieved, the service consumer can send a usage request corresponding to any SaaS service published on the PaaS platform to the PaaS platform, and can also receive a response result generated by the service provider and forwarded by the PaaS platform to the usage request. In this embodiment, the process of sending the usage request and receiving the response result can be found in the description of the above embodiments and will not be repeated here. In addition, for details not described in this embodiment and the technical effects that can be achieved, please refer to the relevant descriptions of the embodiments shown in Figures 1 to 8 above, and will not be repeated here. Figure 11 is a flowchart of another SaaS service processing method provided by an embodiment of the present disclosure. The method provided by the embodiment of the present disclosure can be executed by the service provider in the system shown in each of the above embodiments. As shown in Figure 11, the method may include the following steps:

[0011] 5301, receiving a request from a service user to use any SaaS service published on the PaaS platform.

[0012] 5302 , respond to the usage request to obtain a response result.

[0013] 5303: Send the response result required by the service consumer. The VPCs of the PaaS platform, service consumer, and service provider are interconnected. Similar to the embodiment shown in Figure 10, initially, the PaaS platform, service consumer, and service provider may be deployed in different VPCs. In this case, the VPCs of the three parties can also be interconnected to break through the network isolation between the service provider and the PaaS platform and enable communication between the service provider and the PaaS platform. The service provider receives a request from the service consumer for any SaaS service published on the PaaS platform, forwarded by the PaaS platform. The service provider then responds to the request and generates a corresponding response result. The service provider can also send the response result required by the service consumer to the PaaS platform, which then forwards the response result to the service consumer. In this embodiment, the process of receiving the request, responding to the request, and sending the response result can all be found in the relevant descriptions of the above embodiments and will not be repeated here. In addition, any details not described in this embodiment and the technical effects that can be achieved can be found in the relevant descriptions of the embodiments shown in Figures 1 to 8 above, and will not be repeated here. The above embodiments have already described in detail the SaaS service processing process from the perspective of systems and methods. To facilitate understanding, the specific implementation process of the above SaaS service processing system and method will be described below using a specific scenario. Continuing with the SaaS service processing system architecture provided in the above embodiments, the VPCs where the service user and the service provider providing the SaaS service reside can be interconnected with the VPC where the PaaS platform resides. Based on this, the service user can see the PaaS platform homepage shown in Figure 2, which displays four published SaaS services: Vehicle Identification Code Query Service, Payment Card Real-Name Authentication Service, Identity Real-Name Authentication Service, and Weather Forecast Query Service. In one scenario, the service user can directly initiate a request to use the identity real-name authentication service on the PaaS platform homepage, for example, by clicking the "Try" or "Buy" button under the Identity Real-Name Authentication section on the homepage. Alternatively, a service consumer can first view the PaaS platform homepage and then click on the real-name authentication service to display the service details page shown in Figure 3. From this page, the service consumer can initiate a request to use the real-name authentication service, for example by clicking the "Try" or "Buy" button. The service consumer can then send this request to the PaaS platform using its own network access module.The real-name authentication service is delivered as an API interface. The PaaS platform then uses a mapping relationship to resolve the domain name of the real-name authentication service in the request, compares the resolved network address, and finds the target network address of the target service provider providing the real-name authentication service from the network address stored in the routing information. The PaaS platform then forwards the request to the target service provider with the target network address. The target service provider responds to the request forwarded by the PaaS platform to obtain the API interface information required to implement the authentication service. The target service provider can further use its own network access module to send the API interface information as a response to the request to the PaaS platform. Finally, the service consumer can also use its own network access module to receive the API interface information required to implement the authentication service forwarded by the PaaS platform and use the authentication service by calling the interface. The above schematically illustrates a scenario for using the real-name authentication service. For actual usage scenarios of any SaaS service, please refer to the relevant descriptions of the above embodiments and will not be repeated here. In addition, for details not described in detail in this embodiment and the technical effects that can be achieved, please refer to the relevant descriptions in the above embodiments and will not be repeated here. The following describes in detail the processing devices of the SaaS service of one or more embodiments of the present disclosure. Those skilled in the art will understand that these processing devices can be configured using commercially available hardware components through the steps taught in this solution. Figure 12 is a schematic structural diagram of a processing device for a SaaS service provided in an embodiment of the present disclosure. As shown in Figure 12, the device includes: a first receiving component 11, which is used to receive a usage request sent by a service user, where the usage request corresponds to any SaaS service published on the PaaS platform. A forwarding component 12, which is used to forward the usage request to a target service provider for providing any SaaS service based on the service provider address in the routing information. A first sending component 13, which is used to send the response result generated by the target service provider to the service user, wherein the VPCs in which the PaaS platform, the service user, and the service provider are located are interconnected.The service provider and service consumer are located in VPCs in different regions; the service provider utilizes an internally configured network access module to interconnect the VPC of the service provider with the VPC of the PaaS platform; the service consumer utilizes an internally configured network access module to interconnect the VPC of the service consumer with the VPC of the PaaS platform; the PaaS platform is located in at least one VPC in the same region or in at least one VPC in a different region; the PaaS platform is configured with an interconnection medium; the interconnection medium is used to establish a communication connection between any two VPCs in the same region or between any two VPCs in different regions. The routing information includes the network addresses of different service providers that publish SaaS services on the PaaS platform, and the different service providers are located in the same VPC, different VPCs in the same region, or VPCs in different regions. Optionally, the apparatus further includes: an acquisition component 14 for acquiring attribute information of the SaaS service provided by the service provider in response to a service configuration operation triggered by the service provider; and a determination component 15 for determining the legitimacy of the SaaS service based on the attribute information. The display component 16 is configured to display the service details in the attribute information if the SaaS service is legal. The determination component 17 is configured to determine the network address in the attribute information as routing information if the SaaS service is legal. The apparatus shown in FIG12 can execute the method of the embodiment shown in FIG9 . For portions not described in detail in this embodiment, reference can be made to the relevant description of the embodiment shown in FIG9 . The execution process and technical effects of this technical solution are described in the embodiment shown in FIG9 and will not be repeated here. In one possible design, the SaaS service processing method provided in the above embodiments can be applied in an electronic device. As shown in FIG13 , the electronic device may include: a first processor 21 and a first memory 22. The first memory 22 is configured to store a program that supports the electronic device in executing the SaaS service processing method provided in the embodiment shown in FIG9 . The first processor 21 is configured to execute the program stored in the first memory 22.The program includes one or more computer instructions, wherein when executed by the first processor 21, the one or more computer instructions can implement the following steps: receiving a usage request sent by a service user, the usage request corresponding to any SaaS service published on the PaaS platform; forwarding the usage request to a target service provider providing any SaaS service based on the service provider address in the routing information; and sending a response generated by the target service provider to the service user. The PaaS platform, the service user, and the VPC in which the service provider resides are interconnected. Optionally, the first processor 21 is further configured to execute all or part of the steps in the embodiment shown in FIG. 9 . The electronic device may also include a first communication interface 23 for communicating with other devices or a communication network. Furthermore, embodiments of the present disclosure provide a computer storage medium for storing computer software instructions used by the electronic device, including a program for executing the processing method for the SaaS service shown in FIG. 9 . Figure 14 is a schematic diagram of the structure of another SaaS service processing device provided by an embodiment of the present disclosure. As shown in Figure 14, the device includes: a second sending component 31 for sending a usage request corresponding to any SaaS service published on a PaaS platform to the PaaS platform. A second receiving component 32 for receiving a response generated by the service provider, wherein the response corresponds to the usage request and the VPC interconnection between the PaaS platform, the service user, and the service provider. The device shown in Figure 14 can execute the method shown in the embodiment of Figure 10. For portions not described in detail in this embodiment, please refer to the relevant description of the embodiment shown in Figure 10. The execution process and technical effects of this technical solution are described in the embodiment shown in Figure 10 and will not be repeated here. In one possible design, the SaaS service processing method provided by the above embodiments can be applied in another electronic device. As shown in Figure 15, the electronic device may include: a second processor 41 and a second memory 42. The second memory 42 is used to store a program that supports the electronic device in executing the SaaS service processing method provided by the embodiment shown in Figure 10. The second processor 41 is configured to execute the program stored in the second memory 42.The program includes one or more computer instructions, wherein when executed by the second processor 41, the one or more computer instructions can implement the following steps: sending a usage request corresponding to any SaaS service published on the PaaS platform to the PaaS platform; and receiving a response result generated by the service provider, wherein the response result corresponds to the usage request, the interconnection between the PaaS platform, the service user, and the VPC in which the service provider resides. Optionally, the second processor 41 is further configured to perform all or part of the steps in the embodiment shown in FIG10 . The electronic device may also include a second communication interface 43 for communicating with other devices or a communication network. Furthermore, an embodiment of the present disclosure provides a computer storage medium for storing computer software instructions used by the electronic device, including a program for executing the SaaS service processing method shown in FIG10 . FIG16 is a schematic diagram of the structure of another SaaS service processing device provided in an embodiment of the present disclosure. As shown in FIG16 , the device includes: a third receiving component 51 for receiving a usage request from a service user for any SaaS service published on the PaaS platform; and a response component 52 for responding to the usage request to obtain a response result. The third sending component 53 is used to send the response result required by the service user, wherein the VPCs where the PaaS platform, the service user, and the service provider are located are interconnected. The device shown in Figure 16 can execute the method of the embodiment shown in Figure 11. For the parts not described in detail in this embodiment, please refer to the relevant description of the embodiment shown in Figure 11. The execution process and technical effects of this technical solution are described in the embodiment shown in Figure 11 and will not be repeated here. In one possible design, the processing method of the SaaS service provided by the above embodiments can be applied to another electronic device. As shown in Figure 17, the electronic device may include: a third processor 61 and a third memory 62. The third memory 62 is used to store a program that supports the electronic device to execute the processing method of the SaaS service provided in the embodiment shown in Figure 11. The third processor 61 is configured to execute the program stored in the third memory 62. The program includes one or more computer instructions, wherein the one or more computer instructions, when executed by the third processor 61, can implement the following steps: receiving a request from a service user to use any SaaS service published on the PaaS platform; responding to the request to obtain a response result; and sending the response result required by the service user, wherein the VPCs where the PaaS platform, the service user, and the service provider are located are interconnected.Optionally, the third processor 61 is further configured to execute all or part of the steps in the embodiment shown in FIG. 11 . The electronic device may further include a third communication interface 63 for communicating with other devices or a communication network. Furthermore, the embodiments of the present disclosure provide a computer storage medium for storing computer software instructions used by the electronic device, including a program for executing the processing method for the SaaS service shown in FIG. 11 Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present disclosure and are not intended to limit them. Although the present disclosure has been described in detail with reference to the above embodiments, those skilled in the art will understand that the technical solutions described in the above embodiments may be modified or some of the technical features may be replaced with equivalents. Such modifications or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure. Industrial Applicability: The embodiments of the present disclosure provide solutions for service providers, service users, and PaaS platforms in different VPCs, interconnecting the VPCs of the service users, service providers, and PaaS platforms, thereby eliminating network isolation between the three parties. The PaaS platform can further utilize local routing information to enable communication between service users and service providers, so that service users can use any SaaS service published on the PaaS platform and provided by any service provider in any VPC, thereby solving the technical problem of low convenience for service users to use services in the PaaS platform.

Claims

Claims 1. A processing system for SaaS services, characterized in that Including: A service provider, a service user, and a Platform as a Service (PaaS) platform. Among them, the virtual private clouds (VPCs) where the service provider, the service user, and the PaaS platform are located are interconnected. The service user is used to send a usage request for any Software as a Service (SaaS) service published on the PaaS platform to the PaaS platform and receive the response result corresponding to the usage request forwarded by the PaaS platform. The PaaS platform is used to forward the usage request to the target service provider that provides the any SaaS service according to the network address in the routing information. The target service provider is used to respond to the usage request and send the response result corresponding to the usage request to the PaaS platform.

2. The system according to claim 1, characterized in that The service provider and the service user are in VPCs in different regions. The service provider uses an internally configured network access module to interconnect the VPC where the service provider is located with the VPC where the PaaS platform is located. The service user uses an internally configured network access module to interconnect the VPC where the service user is located with the VPC where the PaaS platform is located. The PaaS platform is in at least one VPC in the same region or in at least one VPC in different regions. The PaaS platform is configured with an interconnection medium. The interconnection medium is used to establish a communication connection between any two VPCs in the same region or establish a communication connection between any two VPCs in different regions.

3. The system according to claim 1, wherein The routing information includes the network addresses of different service providers that publish SaaS services in the PaaS platform. The different service providers are in the same VPC, or in different VPCs in the same region, or in VPCs in different regions.

4. The system according to claim 1, wherein The PaaS platform includes: a network connection system, which is used to determine the target network address corresponding to the any SaaS service according to the service network parameters in the usage request; and forward the usage request to the target service provider with the target network address.

5. The system according to claim 1, characterized in that The PaaS platform includes: a service management system, which is configured to obtain the attribute information of the SaaS service provided by the service provider in response to a service configuration operation triggered by the service provider on the service management system, where the attribute information includes service detail information and / or service network parameters; and display the service detail information in the attribute information when it is determined that the SaaS service is legal according to the attribute information; a network connection system, which is configured to obtain the network address included in the attribute information from the service management system when the SaaS service is legal; and determine the network address in the attribute information as the routing information.

6. The system according to claim 1, wherein The PaaS platform includes: a network connection system, which is configured to determine the legality of the usage request according to the data volume and / or data content of the usage request.

7. The system according to claim 1, characterized in that The PaaS platform includes: a network connection system, which is used to determine the data volume of the response result sent by the target service provider; and determine the consumption of the cost resources of the service user according to the data volume.

8. The system according to claim 1, characterized in that, The PaaS platform includes: a network connection system and a service management system; the network connection system is configured to determine the legality of any SaaS service according to the data content of the response result; the service management system is configured to delete any SaaS service when any SaaS service is illegal.

9. The system according to claim 1, wherein The PaaS platform includes: a service management system, which is configured to display the SaaS services published on the PaaS platform; and edit the attribute information of the SaaS service in response to an edit operation of the service provider.

10. The system according to claim 1, wherein The PaaS platform includes: a user management system, which is configured to store the account information of the service provider; and verify the service publishing permission of the service provider according to the account information of the service provider.

11. A processing method for SaaS services, characterized in that Applied to a platform as a service (PaaS) platform, it includes: receiving a usage request sent by a service user, where the usage request corresponds to any software as a service (SaaS) service published on the PaaS platform; forwarding the usage request to the target service provider that provides the any SaaS service according to the network address in the routing information; and sending the response result generated by the target service provider in response to the usage request to the service user, where the PaaS platform, the service user, and the service provider are interconnected through a private virtual cloud (VPC).

12. The method according to claim 11, characterized in that The service provider and the service user are in VPCs in different regions; the service provider uses an internally configured network access module to interconnect the VPC where the service provider is located with the VPC where the PaaS platform is located; the service user uses an internally configured network access module to interconnect the VPC where the service user is located with the VPC where the PaaS platform is located; the PaaS platform is in at least one VPC in the same region or in at least one VPC in different regions; the PaaS platform is configured with an interconnection medium; the interconnection medium is used to establish a communication connection between any two VPCs in the same region or to establish a communication connection between any two VPCs in different regions.

13. The method according to claim 11, characterized in that, The routing information includes the network addresses of different service providers that publish SaaS services in the PaaS platform, and the different service providers are in the same VPC, or in different VPCs in the same region, or in VPCs in different regions.

14. The method according to claim 11, characterized in that The method further includes: in response to a service configuration operation triggered by the service provider, obtaining the attribute information of the SaaS service provided by the service provider; when it is determined that the SaaS service is legal according to the attribute information, displaying the service detail information in the attribute information, and determining the network address in the attribute information as the routing information.

15. A processing method for SaaS services, characterized in that Applied to a service user, it includes: sending a usage request corresponding to any software as a service (SaaS) service published on a platform as a service (PaaS) platform to the PaaS platform; receiving a response result generated by the service provider, where the response result corresponds to the usage request, and the PaaS platform, the service user, and the virtual private cloud (VPC) where the service provider is located are interconnected.

16. A processing method for SaaS services, characterized in that, Applied to a service provider, it includes: receiving a usage request from a service user for any software as a service (SaaS) service published on a platform as a service (PaaS) platform; responding to the usage request to obtain a response result; sending the response result required by the service user, where the PaaS platform, the service user, and the virtual private cloud (VPC) where the service provider is located are interconnected.

17. An electronic device, characterized in that, It includes: A memory and a processor; wherein, executable code is stored on the memory, and when the executable code is executed by the processor, the processor executes the processing method of the SaaS service according to any one of claims 11 to 14.

18. An electronic device, characterized in that, It includes: A memory, a processor, and a network access module; wherein, the electronic device uses the network access module to interconnect the electronic device and a virtual private cloud (VPC) where a platform as a service (PaaS) platform is located, and executable code is stored on the memory, and when the executable code is executed by the processor, the processor is caused to execute the processing method of the SaaS service as described in claim 15 or 16.

19. A computer-readable storage medium storing computer instructions, characterized in that, When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the processing method of the SaaS service as described in any one of claims 11 to 16.

20. A computer program product, characterized in that, It includes a computer program which, when executed by a processor, implements the processing method of the SaaS service as described in any one of claims 11 to 16.

Images