System capable of flexibly configuring services

Abstract

The invention provides a system capable of flexibly configuring services, which comprises N front-end portals, an integrated support platform, a resource scheduling opening platform and M peripheral service platforms, and is characterized in that M and N are positive integers; wherein the front-end portal calls the integrated support platform through an API (Application Program Interface); the integrated support platform is in butt joint with the resource scheduling opening platform and each peripheral business platform, and is used for receiving the business requirements of the front-end portal after obtaining the business requirements of the front-end portal; and based on the resource scheduling opening platform and each peripheral business platform, configuring a product corresponding to the business demand for the front-end portal. According to the method, personalized service configuration display and service rapid release and change of different front-end portals can be realized, and rapid horizontal extension and rapid deployment and online of lightweight front-end portal contacts are supported. And high-efficiency multiplexing of peripheral platform interfaces can be realized, and the workload of repeated development and butt joint debugging and testing is reduced.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a system capable of flexibly configuring services. Background Art

[0002] With the rapid development of AI technologies and applications represented by large language models such as ChatGTP, GTP, Llama2, and SORA Wensheng video models, and with the vigorous development of various computing power applications, the demand for computing power products and services represented by intelligent computing power is also growing rapidly. Users generally access the corresponding computing power application supplier website portal through the Internet to conveniently obtain computing power services and use computing power applications.

[0003] Currently, portals are mainly deployed in two ways: one is an integrated portal platform that integrates the front-end and back-end, and the other is that the front-end portal and the back-end middle platform are relatively independent. Since the configuration of independent front-end and back-end modules is more flexible and decoupled from each other, the industry currently mainly deploys them through the second method.

[0004] When multiple business operators have similar portal deployment requirements, the existing technology deploys a complete portal system for each operator separately, including front-end portal touchpoints and back-end integrated support platforms. Although this can meet the personalized business needs of each operator, the corresponding software development and hardware resource investment is relatively large.

[0005] Therefore, how to achieve intensive development and deployment of the system becomes a problem that needs to be solved. Summary of the invention

[0006] The technical problem to be solved by the present application is to provide a system capable of flexibly configuring services in order to solve the problems existing in the prior art in view of the above-mentioned deficiencies in the prior art.

[0007] The present application provides a system capable of flexibly configuring services, the system comprising: N front-end portals, an integrated support platform, a resource scheduling and activation platform, and M peripheral service platforms, where M and N are both positive integers;

[0008] The front-end portal calls the integrated support platform through an API interface, and different operator tenants correspond to different front-end portals;

[0009] The integrated support platform is connected to the resource scheduling and activation platform and each of the peripheral business platforms respectively. The integrated support platform is used to configure products corresponding to the business needs of the front-end portal based on the resource scheduling and activation platform and each of the peripheral business platforms after obtaining the business needs of the front-end portal.

[0010] In some embodiments, the integrated support platform is used to implement at least one function of portal configuration, style and language configuration, user management, menu management, product management, order management, and operational data statistics;

[0011] The integrated support platform is provided with a management terminal, and the management terminal is used to implement a configuration management interface for the execution function of the integrated support platform.

[0012] In some embodiments, the integrated support platform implements the portal configuration function, specifically including:

[0013] The management end obtains the portal configuration information and sends it to the integrated support platform, so that the integrated support platform records the portal configuration information into the portal configuration table after receiving the portal configuration information;

[0014] The portal configuration information at least includes a portal ID and a portal name, and the portal ID is used to associate with a tenant ID.

[0015] In some embodiments, the integrated support platform implements style and language configuration functions, specifically including:

[0016] The management end obtains the style configuration information and language configuration information corresponding to each tenant, and sends it to the integrated support platform, so that after receiving the style configuration information and language configuration information, the integrated support platform records the style configuration information to the portal style configuration table and records the language configuration information to the portal language configuration table;

[0017] The style configuration information includes at least a tenant ID and a style ID;

[0018] The language configuration information at least includes a tenant ID and language type information.

[0019] In some embodiments, the integrated support platform implements user management functions, specifically including:

[0020] The management terminal obtains the tenant management information, and sends a tenant management request including the tenant management information and the corresponding tenant ID to the integrated support platform, so that the integrated support platform saves the tenant management information to the user information table;

[0021] The integrated support platform obtains user registration / logout information from the front-end portal and saves the user registration / logout information to the user information table;

[0022] The user information table includes at least a tenant ID and a user ID.

[0023] In some embodiments, the integrated support platform implements menu management functions, specifically including:

[0024] The management end obtains the menu configuration page element and sends it to the integrated support platform, so that the integrated support platform saves the menu configuration page element to the menu configuration table after receiving the menu configuration page element;

[0025] The menu configuration page elements include at least one of a menu name, a menu ID, a menu URL, an applicable portal, and a listing status.

[0026] In some embodiments, the integrated support platform implements product management functions, specifically including:

[0027] The management end obtains the added / deleted product information from the administrator's operation, and sends a added / deleted product request containing the added / deleted product information to the integrated support platform, so that the integrated support platform saves the added / deleted product information to the product information definition table;

[0028] The management end obtains product listing / delisting information from the administrator's operation, and sends a product listing / delisting request containing the product listing / delisting information to the integrated support platform, so that the integrated support platform saves the product listing / delisting information to the product information table;

[0029] The added / deleted product information includes at least one of the product ID, product name, supplier, selling price, and supplier settlement price.

[0030] In some embodiments, at least one of the following is included:

[0031] The product corresponds to one or more front-end portals;

[0032] The listing / delisting status of products is different when they correspond to multiple front-end portals;

[0033] When a product corresponds to multiple front-end portals, the product information and / or price information are different;

[0034] When a product corresponds to multiple front-end portals, the ordering process and / or activation process are different.

[0035] In some embodiments, the integrated support platform implements order management functions, specifically including:

[0036] The integrated support platform returns corresponding product information to the corresponding front-end portal in response to obtaining a product query request from the front-end portal;

[0037] In response to obtaining a product ordering request from a front-end portal, the integrated support platform records the product ordering request into an order table.

[0038] In some embodiments, the integrated support platform implements the operation data statistics function, specifically including:

[0039] The front-end portal obtains the user behavior log data and sends it to the integrated support platform, so that the integrated support platform records the user behavior log data into the operation data statistics table after receiving the user behavior log data;

[0040] The user behavior log data includes at least one of tenant ID, user ID, menu ID, operation type, operation time, terminal ID, and terminal IP.

[0041] In some embodiments, when each of the front-end portals calls the integrated support platform through the same API interface, the tenant ID corresponding to each front-end portal is different.

[0042] The system for flexibly configuring services provided by the present application comprises: N front-end portals, an integrated support platform, a resource scheduling and opening platform, and M peripheral business platforms, where M and N are both positive integers; wherein the front-end portal calls the integrated support platform through an API interface, and different operator tenants correspond to different front-end portals; the integrated support platform is connected to the resource scheduling and opening platform and each peripheral business platform respectively, and the integrated support platform is used to configure products corresponding to the business needs for the front-end portal based on the resource scheduling and opening platform and each peripheral business platform after obtaining the business needs of the front-end portal. The present application can realize the personalized business configuration display, rapid business release and change of different front-end portals, and support the rapid horizontal expansion and rapid deployment of lightweight front-end portal contacts. It realizes the efficient reuse of the business support capabilities of the large and medium-sized platform (i.e., the integrated support platform) and maintains a unified software baseline version, and can also realize the efficient reuse of the peripheral platform interface, reducing the workload of repeated development and docking and debugging. Multiple front-end portals can reuse the same cloud pool resources, and at the same time support a team to uniformly support the operation of multiple front-end portals, realize intensive operation support, and save labor costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0044] Figure 1 This is a traditional portal system architecture diagram in the prior art;

[0045] Figure 2An architecture diagram of a system capable of flexibly configuring services provided in an embodiment of the present application;

[0046] Figure 3 A product ordering flow chart provided for an embodiment of the present application.

[0047] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0048] In order to enable those skilled in the art to better understand the technical solution of the present application, the implementation mode of the present application will be further described in detail below with reference to the accompanying drawings.

[0049] It should be understood that the specific embodiments and drawings described herein are only used to explain the present application, rather than to limit the present application.

[0050] It can be understood that, in the absence of conflict, the various embodiments in the present application and the various features in the embodiments can be combined with each other.

[0051] It can be understood that, for the convenience of description, the drawings of the present application only show the parts related to the present application, while the parts unrelated to the present application are not shown in the drawings.

[0052] It can be understood that each unit and module involved in the embodiments of the present application may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.

[0053] It can be understood that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.

[0054] It is understandable that, in the absence of conflict, the functions and steps marked in the flowcharts and block diagrams of the present application may occur in an order different from that marked in the drawings.

[0055] It is understood that the flowcharts and block diagrams of the present application illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present application. Among them, each box in the flowchart or block diagram may represent a unit, module, program segment, code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or by a combination of hardware and computer instructions.

[0056] It can be understood that the units and modules involved in the embodiments of the present application can be implemented by software or hardware, for example, the units and modules can be located in a processor.

[0057] Figure 1 This is a traditional portal system architecture diagram in the prior art, such as Figure 1 As shown, the existing technology deploys a complete portal system for each operator separately, including front-end portal touchpoints and back-end integrated support platforms. Since each customer's portal system needs to maintain its own software version separately and cannot share a unified baseline version, the number of development and maintenance personnel has increased exponentially, and the development and launch cycle of each new system is long. The number of docking interfaces between the portal and the peripheral platform has increased exponentially. Even if different portals are connected to the same peripheral platform, they need to be independently developed and debugged, and cannot share the same interface.

[0058] In view of the above shortcomings, this application aims to achieve the following objectives:

[0059] 1. Different operators use the same backend support platform to achieve intensive development and deployment of the system;

[0060] 2. Different operators can use different front-end systems to achieve personalized display of the display layer;

[0061] 3. Different operators can use different business processing procedures according to their own circumstances.

[0062] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0063] Figure 2 The architecture diagram of a system capable of flexibly configuring services provided in an embodiment of the present application is as follows: Figure 2 As shown, the present application provides a multi-portal system capable of flexibly configuring services, the system comprising: N front-end portals, an integrated support platform, a resource scheduling and activation platform, and M peripheral service platforms, where M and N are both positive integers;

[0064] The front-end portal calls the integrated support platform through an API interface, and different operator tenants correspond to different front-end portals;

[0065] The integrated support platform is connected to the resource scheduling and activation platform and each of the peripheral business platforms respectively. The integrated support platform is used to configure products corresponding to the business needs of the front-end portal based on the resource scheduling and activation platform and each of the peripheral business platforms after obtaining the business needs of the front-end portal.

[0066] In some embodiments, when each of the front-end portals calls the integrated support platform through the same API interface, the tenant ID corresponding to each front-end portal is different.

[0067] Specifically, in this application, each operator (in this application, the operator of each front-end portal is regarded as a tenant) independently manages and uses a front-end portal, and operates independently. The front-end portal touchpoints can include different forms such as computer WEB, mobile applets, H5, etc. Multiple front-end portals can call and reuse the back-end integrated support platform through API interfaces.

[0068] Optionally, if multiple front-end portals use the same business process, different front-end portals all call the same API interface of the integrated support platform, but carry different tenant IDs in the API interface protocol to distinguish different operators.

[0069] In this application, the integrated support platform is connected to multiple front-end portals in the north, that is, a system architecture combining 1 back-end support platform and N front-end portals is adopted. Products or solutions are flexibly configured and released according to the business operation needs of each front-end portal to support the needs of business display and expansion of different portals.

[0070] In addition, the integrated support platform can connect to multiple peripheral business platforms in the east-west direction to achieve a closed loop of the entire business process, including but not limited to different payment platforms, different order platforms, different third-party partner business platforms, etc., and connect to the resource scheduling and activation platform in the south direction to achieve a closed loop of business processes.

[0071] In some embodiments, the integrated support platform is used to implement at least one function of portal configuration, style and language configuration, user management, menu management, product management, order management, and operational data statistics;

[0072] The integrated support platform is provided with a management terminal, and the management terminal is used to implement a configuration management interface for the execution function of the integrated support platform.

[0073] The following is a detailed explanation of each function:

[0074] In some embodiments, the integrated support platform implements the portal configuration function, specifically including:

[0075] The management end obtains portal configuration information and sends it to the integrated support platform, so that the integrated support platform records the portal configuration information into the portal configuration table after receiving the portal configuration information; wherein the portal configuration information at least includes a portal ID and a portal name, and the portal ID is used to associate with a tenant ID.

[0076] Specifically, the administrator configures the portal information on the management end of the integrated support platform, and the integrated support platform records the configuration information in the portal configuration table after receiving the configuration information.

[0077] For example, the following is a specific example of a portal configuration table:

[0078] Portal ID Portal Name tenant1 Portal 1 tenant2 Portal 2 tenant3 Portal 3

[0079] Table 1

[0080] Taking the data in Table 1 as an example, three operator portals are configured, and the portal names are Portal 1, Portal 2, and Portal 3, and the portal IDs are tenant 1, tenant 2, and tenant 3. The portal ID field is used to associate the tenant IDs of other tables.

[0081] In some embodiments, the integrated support platform implements style and language configuration functions, specifically including:

[0082] The management end obtains the style configuration information and language configuration information corresponding to each tenant, and sends it to the integrated support platform, so that after receiving the style configuration information and language configuration information, the integrated support platform records the style configuration information to the portal style configuration table and records the language configuration information to the portal language configuration table; wherein the style configuration information includes at least the tenant ID and the style ID; wherein the language configuration information includes at least the tenant ID and the language type information.

[0083] Specifically, the integrated support platform supports independent configuration of the front-end portal style of each tenant. The configuration fields include tenant and style. Tenant is a drop-down option, and the value comes from the portal configuration table (i.e. Table 1). Style is also a drop-down option, which is preset by the system. The options include but are not limited to high-tech style, cool style, simple style, default style, etc. The administrator selects the tenant to be configured and the corresponding style on the style configuration page of the system management module. After submission, the browser sends a request to set the tenant style to the integrated support platform. The parameters include tenant ID and style ID. The integrated support platform records the request information in the portal style configuration table.

[0084] For example, the following is a specific example of a portal style configuration table:

[0085] Tenant ID Style ID theme tenant1 style1 Technology tenant2 style2 Cool style tenant3 style3 Simple style tenant4 Style4 Default style

[0086] Table 2

[0087] As shown in Table 2, this implements the configurable management of each tenant's interface style. If not configured, the front-end portal uses the default style.

[0088] In addition, the administrator selects the tenant to be configured and the corresponding language on the tenant language configuration page of the system management module, and the integrated support platform records the configuration request information in the portal language configuration table.

[0089] For example, the following is a specific example of a portal language configuration table:

[0090] Tenant ID Language Type Language type identifier tenant1 Simplified Chinese zh_CN tenant2 Traditional Chinese zh_HK tenant3 English en_US

[0091] Table 3

[0092] As shown in Table 3, for example, the language of portal 1 is simplified Chinese, and the language of portal 3 is English. The process is the same as the style configuration, and will not be repeated.

[0093] This embodiment can provide personalized configuration interfaces such as style configuration and language configuration for different operators.

[0094] In some embodiments, the integrated support platform implements user management functions, specifically including:

[0095] The management terminal obtains the tenant management information, and sends a tenant management request including the tenant management information and the corresponding tenant ID to the integrated support platform, so that the integrated support platform saves the tenant management information to the user information table;

[0096] The integrated support platform obtains user registration / logout information from the front-end portal and saves the user registration / logout information to the user information table;

[0097] The user information table includes at least a tenant ID and a user ID.

[0098] Specifically, the tenant management information is obtained by the management end, and the tenant management information can be configured by the administrator. The management end sends a tenant management request containing the tenant management information and the corresponding tenant ID to the integrated support platform, so that the integrated support platform saves the tenant management information to the user information table, thereby realizing the addition / deletion management of tenants.

[0099] In addition, each tenant can develop its own users. After the user registers in the tenant front-end portal, the front-end portal initiates a user registration request to the integrated support platform. The parameters include the user registration information and the tenant ID of the portal. The integrated support platform saves the user data in the user information table in a unified manner, and the status is "effective".

[0100] For example, the following is a specific example of a user information table:

[0101] Tenant ID User ID username phone number state tenant1 user_id1 user1 number1 Effective tenant1 user_id2 user2 number2 Effective tenant2 user_id3 user3 number3 Effective tenant3 user_id4 user4 number4 Effective

[0102] Table 4

[0103] As shown in Table 4, the information registered by users in each front-end portal is stored in the user information table. The user table uses "tenant ID + user ID" as the unique index, that is, users of different tenants can use the same user name. Users of different tenants are isolated using tenant IDs to ensure that user information between tenants is isolated and cannot be seen by each other.

[0104] In addition, the user's logout process on the front-end portal is similar to the user registration process. The front-end portal submits the user's logout request information (parameters include user ID and portal's tenant ID) to the management end, and then the integrated support platform sets the user status to "logout".

[0105] In some embodiments, the integrated support platform implements menu management functions, specifically including:

[0106] The management end obtains the menu configuration page elements and sends them to the integrated support platform, so that the integrated support platform saves the menu configuration page elements to the menu configuration table after receiving the menu configuration page elements; wherein the menu configuration page elements include at least one of the menu name, menu ID, menu URL, applicable portal, and shelf status.

[0107] Specifically, the integrated support platform allows each tenant to customize their own front-end portal page menu. The administrator configures the menu on the management side. The menu configuration page elements include at least the menu name, menu ID, menu URL, applicable portal, listing status and other fields. The applicable portal is a drop-down multi-option, and the value comes from the portal configuration table (i.e., Table 1). When the administrator configures a menu, he fills in the various page elements of the menu configuration and submits it. The browser sends the menu configuration request to the integrated support platform, which stores the menu configuration.

[0108] For example, the following is a specific example of a menu configuration table:

[0109]

[0110] Table 5

[0111] As shown in Table 5, taking the records in the table as an example, it means that the "Order Management" menu is unique and all tenants use this menu; there are three "Product Management" menus, namely public, tenant 1 and tenant 2.

[0112] When a tenant's front-end portal page loads menu content, the menu information in Table 5 is obtained through the following steps:

[0113] (1) Read all menus whose tenant ID is public or whose tenant ID matches it;

[0114] (2) If the menu ID read in step (1) is repeated, it means that the tenant has customized the menu. In this case, the menu with a public tenant ID is removed and the tenant customized menu is given priority.

[0115] This embodiment enables tenants to load customized menu content through the above method, and uses a unified menu (the tenant ID is public) for uncustomized menus.

[0116] In some embodiments, the integrated support platform implements product management functions, specifically including:

[0117] The management end obtains the added / deleted product information from the administrator's operation, and sends a added / deleted product request containing the added / deleted product information to the integrated support platform, so that the integrated support platform saves the added / deleted product information to the product information definition table; wherein the added / deleted product information includes at least one of the product ID, product name, supplier, selling price, and supplier settlement price.

[0118] The management end obtains product listing / delisting information from the administrator's operation, and sends a product listing / delisting request containing the product listing / delisting information to the integrated support platform, so that the integrated support platform saves the product listing / delisting information to the product information table;

[0119] In this application, the integrated support platform allows administrators to define public products for all tenants, as well as to define customized products for each tenant. The administrator adds a new product in the product management interface of the management end, fills in information such as product ID, product name, supplier, selling price, supplier settlement price, etc., and clicks the submit button. The browser will submit the new product request (the parameters contain the above product information) to the integrated support platform, which will record the product information in the product information definition table with the status of "effective".

[0120] In some embodiments, at least one of the following is included:

[0121] (1) The product corresponds to one or more front-end portals;

[0122] Specifically, product management of multiple operators (front-end portals) is implemented on the same integrated support platform. These products can be shared by multiple operators or customized by one operator.

[0123] (2) The listing / delisting status of a product is different when it corresponds to multiple front-end portals;

[0124] Specifically, products (including the same product and different products) can be added and removed from the shelves by different operators on the same integrated support platform.

[0125] (3) When a product corresponds to multiple front-end portals, the product information and / or price information is different;

[0126] Specifically, the independent definition of product names, product details, sales prices, and settlement prices of products (including the same product and different products) from different operators is achieved on the same integrated support platform.

[0127] (4) The activation process is different when the product corresponds to multiple front-end portals.

[0128] Specifically, different ordering processes and / or activation process definitions of products (including the same product and different products) in different operators are implemented in the same integrated support platform.

[0129] For example, the following is a specific example of a product information definition table:

[0130]

[0131] Table 6

[0132] As shown in Table 6, the table defines the parameter information and status of each product. Products need to be defined before they can be put on the shelves for tenants.

[0133] Optionally, the process of deleting a product is similar to that of adding a new product. The product status in Table 6 is changed to "invalid" and will not be repeated here.

[0134] In addition, for product listing: after the administrator adds a new product on the management side, the product is listed through the product listing interface. The browser queries the integrated support platform for all effective products, and the administrator selects the product to be listed, fills in the product name to be displayed, product price and other information, selects the tenant to be listed and the ordering process (the ordering process definition is omitted here), clicks the submit button, and the browser submits the above product listing information to the integrated support platform, which records the product information in the product information table, and the status is "listed".

[0135] For example, the following is a specific example of a product information table:

[0136]

[0137]

[0138] Table 7

[0139] As shown in Table 7, for a product, the present invention supports multiple product listing modes:

[0140] (1) Add multiple different products (mainly with different product IDs) in the management interface. Different products are listed for different tenants, and the products of different tenants do not affect each other.

[0141] (2) When the same product is listed to multiple tenants in the management interface, the product display name, price and other information of the product in each tenant can be different or the same. If the relevant fields are not filled in, the information of the same fields in the product definition table (Table 6) is used. As shown in Table 7, when product1 is listed to tenant1 and tenant2, the product name and product price are reassigned;

[0142] Optionally, the same product is listed on the management interface to the portals corresponding to all tenants, and the product display names and prices of all tenants are consistent, such as product 3 in Table 7.

[0143] When the front-end portal reads product information, the integrated support platform queries Table 7 for product information listed for the tenant ID and all tenants based on the tenant ID. For products with duplicate IDs, only products listed for the tenant are retained.

[0144] In addition, for product removal: the administrator selects the product ID on the management side, and the integrated platform searches for the tenant where the product is listed in Table 7 combined with Table 1 based on the product ID, and then encapsulates the product ID and tenant ID information and returns it to the management side. The administrator selects the corresponding tenant on the management side and clicks the Remove button, and the browser sends a request to remove the product to the integrated support platform, which sets the corresponding product listing status in Table 7 to "Removed".

[0145] In this application, for business processes: different front-end portals can adopt unified business processes, or they can configure personalized business processes based on different tenant IDs on the integrated support platform according to their respective business characteristics and application scenarios, including but not limited to product ordering, business activation, payment settlement, partner onboarding, customer service and other processes. The administrator can configure the steps included in each workflow in the workflow configuration interface of the management interface, and different workflows can define different business processing nodes.

[0146] For example, the following is a specific example of a product ordering flow chart:

[0147]

[0148] Table 8

[0149] Taking the product ordering process table in Table 8 as an example, the administrator configured the ordering process of two computing power products through workflow1 and workflow3.

[0150] In addition, workflow3 consists of 4 steps: generating order data, synchronizing orders with the billing center for deduction, sending a function activation request to business platform A, and updating the order status to completed. The difference between workflow1 and workflow3 is that workflow1 needs to send function activation requests to both business platform A and business platform B, which usually means that the function of the product using this process requires the collaboration of the two platforms to complete. For example, ordering cloud computing products requires the activation of computing resources and storage resources, and both are managed by the same two platforms. The rest of the ordering process is defined according to business needs, and so on, and will not be repeated here. In this way, by combining Table 7 and Table 8, it is possible to order different products or execute different ordering processes for the same product in different tenants.

[0151] In some embodiments, the integrated support platform implements order management functions, specifically including:

[0152] The integrated support platform returns corresponding product information to the corresponding front-end portal in response to obtaining a product query request from the front-end portal;

[0153] In response to obtaining a product ordering request from a front-end portal, the integrated support platform records the product ordering request into an order table.

[0154] Specifically, the user opens the product center on the front end of portal 1 (i.e. tenant 1), and the browser sends product query requests to the integrated support platform. The integrated support platform queries the product summary information of the tenant ID and all tenants in Table 7 and returns it. The user selects product 1 to browse and order, and the browser sends an order request to the integrated support platform, which archives the order data to the order table.

[0155] For example, here is a specific example for the Orders table:

[0156]

[0157] Table 9

[0158] As shown in Table 9, the data in the table is only an example, indicating that users abc1 and abc2 of tenants tenant1 and tenant2 have respectively subscribed to products product11 and product12, with the amounts being price11 and price12 respectively.

[0159] In some embodiments, the integrated support platform implements the operation data statistics function, specifically including:

[0160] The front-end portal obtains user behavior log data and sends it to the integrated support platform, so that the integrated support platform records the user behavior log data into the operation data statistics table after receiving the user behavior log data; wherein, the user behavior log data includes at least one of tenant ID, user ID, menu ID, operation type, operation time, terminal ID, and terminal IP.

[0161] Specifically, any operation of the user on the front-end portal page will send the user behavior data to the integrated support platform through the pre-set page embedding point. The information sent includes tenant ID, user ID (a randomly generated ID for non-logged-in users), menu ID, operation type, operation time, terminal ID, terminal IP, additional information (non-common fields can be transmitted through this field, such as the order amount when placing an order), etc. The latter records this operation information in the user behavior log table. The integrated support platform collects statistics on the user behavior log data of the previous natural day at 0:00 am every day, and the statistical results are recorded in the operation data statistics table.

[0162] For example, the following is a specific example of an operational data statistics table:

[0163]

[0164] Table 10

[0165] As shown in Table 10, the data in the table respectively represent the PV, UV, number of orders and transaction amount of Portal 1 and Portal 2 on May 1, 2024.

[0166] The administrator can query the operation statistics of a portal for a certain period of time and a certain operator on the operation statistics page of the management end. The browser initiates an operation data query request to the integrated platform, and the input parameters are the start date, end date, and tenant ID. The tenant ID is optional. If no tenant is selected, all tenants are queried. After receiving the query request, the integrated platform classifies and counts each indicator according to the start date, end date, and tenant ID, and returns the results to the management end.

[0167] Optionally, the business tables on the integrated support platform are isolated by tenant ID. In the query statement of each business, by using the tenant ID as an index in the query condition, each tenant can only query the data of the portal he uses (system administrators are not subject to this restriction), preventing horizontal unauthorized access. The same applies to the storage of business acceptance data.

[0168] Compared with the prior art, the improvements of the system in this application mainly include:

[0169] 1. Through the model of N front-ends + 1 integrated support platform, different operators use the same integrated support platform to achieve intensive development, deployment and operation support of the system. Different operators use tenant IDs for data isolation, which includes:

[0170] Implement product management of multiple operators in the same management backend. These products can be shared by multiple operators or customized by one operator.

[0171] In the same management backend, products (including the same product and different products) can be put on and taken off the shelves of different operators;

[0172] In the same management backend, the sales price and settlement price of products (including the same product and different products) can be independently defined by different operators;

[0173] Implement different activation process definitions for products (including the same product and different products) in different operators in the same management backend;

[0174] Implement menu loading for different tenants in the same management backend. These menus can be shared by multiple operators or customized by one operator.

[0175] Realize operational data statistics of different operators in the same management backend.

[0176] 2. Operators can define their own business processing procedures based on their own circumstances;

[0177] 3. Different operators can use different front-end systems to achieve personalized display on the front-end interface;

[0178] 4. The front-end page style and language are stored in the back-end system and distinguished by tenant ID. The operator can switch the page style and language with one click at any time as needed.

[0179] To facilitate further understanding of the present application, the main process is described below by taking the example of a user logging in to portal 1 to place a product order (the rest of the business processes are similar).

[0180] Figure 3 The product ordering flow chart provided in the embodiment of the present application is as follows: Figure 3 As shown, product ordering mainly includes the following steps:

[0181] 1. User a registers an account abc1 on portal 1 (see Table 4 data structure);

[0182] 2. User a logs in to portal 1 through account abc1. Portal 1 queries the menu listing and front-end page style / language configuration from the integrated support platform;

[0183] 3. The integrated support platform loads the tenant ID tenant1 and the public menu according to Table 5. If the menu ID is repeated, it is removed. According to Table 2, the front-end page style of the tenant ID tenant1 is read. If there is no configuration, the default style is used;

[0184] 4. The integrated support platform returns the menu list and front-end style / language configuration to portal 1, and the browser displays the corresponding menu list and page style / language accordingly;

[0185] 5. User a opens the product zone page through account abc1, and portal 1 queries the integrated support platform for the list of products available on this portal;

[0186] 6. The integrated support platform goes to the product listing table (Table 7) to read the tenant ID tenant1 and the products of all tenants, and then returns it to portal 1;

[0187] 7. Portal 1 displays the product information in the product list returned in step 6, and removes duplicate product IDs if they are repeated;

[0188] 8. Account abc1 selects product 1 to order;

[0189] 9. Portal 1 submits the order to the integrated support platform, and the integrated support platform returns a message that the order has been successfully submitted;

[0190] 10. The integrated support platform background process performs order flow processing: In Table 7, query the corresponding workflow as workflow1 according to the tenant ID tenant1, and then process the order flow according to the steps corresponding to workflow1 in Table 8:

[0191] (1) Generate order data and record it in the user order table;

[0192] (2) Call the business platform interface to deduct the user's balance;

[0193] (3) Send a resource or function activation request to resource platform A;

[0194] (4) Send a resource or function activation request to resource platform B;

[0195] (5) Update the order status to completed.

[0196] The present application provides a system that can flexibly configure services, which can realize personalized business configuration display, rapid business release and change of different front-end portals, and support lightweight front-end portal touchpoints for rapid horizontal expansion and rapid deployment and launch. It can realize efficient reuse of the business support capabilities of the large and medium-sized platforms (i.e., integrated support platforms) and maintain a unified software baseline version. It can also realize efficient reuse of peripheral platform interfaces and reduce the workload of repeated development and docking and debugging. Multiple front-end portals can reuse the same cloud pool resources, and at the same time support a team to uniformly support the operation of multiple front-end portals, realize intensive operation support, and save labor costs.

[0197] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present application, but the present application is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and substance of the present application, and these modifications and improvements are also considered to be within the scope of protection of the present application.

Claims

1. A system capable of flexibly configuring services, characterized in that: The system includes: N front-end portals, an integrated support platform, a resource scheduling and activation platform, and M peripheral business platforms, where M and N are both positive integers; The front-end portal calls the integrated support platform through an API interface, and different operator tenants correspond to different front-end portals; The integrated support platform is connected to the resource scheduling and activation platform and each of the peripheral business platforms respectively. The integrated support platform is used to configure products corresponding to the business needs of the front-end portal based on the resource scheduling and activation platform and each of the peripheral business platforms after obtaining the business needs of the front-end portal.

2. The system for flexibly configuring services according to claim 1, characterized in that: The integrated support platform is used to implement at least one function of portal configuration, style and language configuration, user management, menu management, product management, order management, and operation data statistics; The integrated support platform is provided with a management terminal, and the management terminal is used to implement a configuration management interface for the execution function of the integrated support platform.

3. The system for flexibly configuring services according to claim 2, characterized in that: The integrated support platform realizes the portal configuration function, specifically including: The management end obtains the portal configuration information and sends it to the integrated support platform, so that the integrated support platform records the portal configuration information into the portal configuration table after receiving the portal configuration information; The portal configuration information at least includes a portal ID and a portal name, and the portal ID is used to associate with a tenant ID.

4. The system for flexibly configuring services according to claim 2, characterized in that: The integrated support platform implements the style and language configuration functions, specifically including: The management end obtains the style configuration information and language configuration information corresponding to each tenant, and sends it to the integrated support platform, so that after receiving the style configuration information and language configuration information, the integrated support platform records the style configuration information to the portal style configuration table and records the language configuration information to the portal language configuration table; The style configuration information includes at least a tenant ID and a style ID; The language configuration information at least includes a tenant ID and language type information.

5. The system capable of flexibly configuring services according to claim 2, characterized in that: The integrated support platform implements user management functions, specifically including: The management terminal obtains the tenant management information, and sends a tenant management request including the tenant management information and the corresponding tenant ID to the integrated support platform, so that the integrated support platform saves the tenant management information to the user information table; The integrated support platform obtains user registration / logout information from the front-end portal and saves the user registration / logout information to the user information table; The user information table includes at least a tenant ID and a user ID.

6. The system capable of flexibly configuring services according to claim 2, characterized in that: The integrated support platform realizes the menu management function, which specifically includes: The management end obtains the menu configuration page element and sends it to the integrated support platform, so that the integrated support platform saves the menu configuration page element to the menu configuration table after receiving the menu configuration page element; The menu configuration page elements include at least one of a menu name, a menu ID, a menu URL, an applicable portal, and a listing status.

7. The system capable of flexibly configuring services according to claim 2, characterized in that: The integrated support platform realizes product management functions, specifically including: The management end obtains the added / deleted product information from the administrator's operation, and sends a added / deleted product request containing the added / deleted product information to the integrated support platform, so that the integrated support platform saves the added / deleted product information to the product information definition table; The management end obtains product listing / delisting information from the administrator's operation, and sends a product listing / delisting request containing the product listing / delisting information to the integrated support platform, so that the integrated support platform saves the product listing / delisting information to the product information table; The added / deleted product information includes at least one of the product ID, product name, supplier, selling price, and supplier settlement price.

8. The system capable of flexibly configuring services according to claim 7, characterized in that: Include at least one of the following: The product corresponds to one or more front-end portals; The listing / delisting status of products is different when they correspond to multiple front-end portals; When a product corresponds to multiple front-end portals, the product information and / or price information are different; The ordering and / or activation process is different when the product corresponds to multiple front-end portals.

9. The system capable of flexibly configuring services according to claim 2, characterized in that: The integrated support platform realizes the order management function, specifically including: The integrated support platform returns corresponding product information to the corresponding front-end portal in response to obtaining a product query request from the front-end portal; In response to obtaining a product ordering request from a front-end portal, the integrated support platform records the product ordering request into an order table.

10. The system capable of flexibly configuring services according to claim 2, characterized in that: The integrated support platform realizes the operation data statistics function, specifically including: The front-end portal obtains the user behavior log data and sends it to the integrated support platform, so that the integrated support platform records the user behavior log data into the operation data statistics table after receiving the user behavior log data; The user behavior log data includes at least one of tenant ID, user ID, menu ID, operation type, operation time, terminal ID, and terminal IP.

11. The system capable of flexibly configuring services according to any one of claims 1 to 10, characterized in that: When each of the front-end portals calls the integrated support platform through the same API interface, the tenant ID corresponding to each front-end portal is different.

Images