CN116466982A - SAAS application resource allocation system based on containerization - Google Patents

SAAS application resource allocation system based on containerization Download PDF

Info

Publication number
CN116466982A
CN116466982A CN202310140067.4A CN202310140067A CN116466982A CN 116466982 A CN116466982 A CN 116466982A CN 202310140067 A CN202310140067 A CN 202310140067A CN 116466982 A CN116466982 A CN 116466982A
Authority
CN
China
Prior art keywords
application
saas
saas application
management module
role
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310140067.4A
Other languages
Chinese (zh)
Inventor
李东云
夏婷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zhenghe Gongda Technology Co ltd
Original Assignee
Beijing Zhenghe Gongda Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Zhenghe Gongda Technology Co ltd filed Critical Beijing Zhenghe Gongda Technology Co ltd
Priority to CN202310140067.4A priority Critical patent/CN116466982A/en
Publication of CN116466982A publication Critical patent/CN116466982A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/105—Multiple levels of security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Technology Law (AREA)
  • Multimedia (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Stored Programmes (AREA)

Abstract

The invention belongs to the technical field of SAAS application and containerization, and provides a containerization-based SAAS application resource allocation system, which comprises a SAAS application management module, a role management module, a resource tree module and an APP end application list module; the invention provides a containerized SAAS application resource allocation system, which realizes the compatibility of new and old version user data by endowing new attributes to user data, namely client identity, client labels and user roles, and manages all SAAS applications at an APP end through an SAAS application management module, wherein the management of roles controls the user SAAS application display permission according to client labels and role names to enable different types of user login accounts and SAAS applications configured at the APP end to be different, thereby realizing the reduction of redundant repeated development work, realizing the unification of a unified platform and service objects and improving the system extensible compatibility level of the platform.

Description

SAAS application resource allocation system based on containerization
Technical Field
The invention belongs to the technical field of voiceprint data acquisition, and particularly relates to a SAAS application resource allocation system based on containerization.
Background
The SAAS refers to software as a service, and refers to that an application program is sent to a remote host of a manufacturer or a service provider so as to be provided for a user on the network, and the SAAS is different from the traditional software purchasing mode in that on a cloud service platform, the user does not need to purchase or install the software any more and only needs to order the service on the network; while containerization refers to the integration of software code and all components needed, keeping them isolated in their own container, so that they can be unaffected by the environment or the operating system of the infrastructure.
At present, the traditional village-passing method is divided into a partner version, a distributor version and a store version, because other merchants on the platform have the demands of a purchase-sale-storage system besides self-camping and store houses, the store houses also have the demands of a retail-sale-related system, so that a user needs to install corresponding APP according to own identity, the user needs to re-purchase or install software for many times, and each version APP has a large amount of homogenization functions, so that the traditional village-passing method has the following problems: 1. if multiple identities exist for the user, installing a plurality of APP; 2. the existing APP needs to be developed for a plurality of times if the same function iteration exists; 3. the system scalability compatibility of the platform is poor.
Therefore, there is a need for a resource allocation system that reduces redundant development effort, unifies platforms and unified service objects, and improves system expansion compatibility of the platforms for containerized SAAS applications.
Disclosure of Invention
In order to solve the technical problems, the invention provides a SAAS application resource allocation system based on containerization, which solves the problems that multiple APPs need to be installed in the traditional village-passing multiple identities, the same function iteration needs to be developed for multiple times, and the system of a platform has poor extensible compatibility by giving three new attributes, namely client identity, client label and user role to user data and controlling whether the SAAS application of different types is displayed on an APP end through authority management.
The specific technical scheme of the invention is as follows:
the utility model provides a SAAS application resource allocation system based on containerization, resource allocation system comprises cloud platform and front end, characterized by that includes:
the SAAS application management module is positioned in the cloud platform, the SAAS application management module is internally provided with a plurality of application types, the application types are internally provided with a plurality of applications, the application types internally comprise a plurality of functions, and the SAAS application management module is used for managing all SAAS applications at the APP end;
the role management module is positioned in the cloud platform, a plurality of roles are respectively contained in the role management module, namely a client identity, a client tag and a user role, the client identity is used for distinguishing a buyer identity from a seller identity, the client tag is used for being compatible with old version client attributes, the old version client attributes comprise a store, a town communication partner and a dealer, the user role refers to a user on the platform and comprises a boss, a sales promoter, a delivery driver and a acquirer, the role management module is used for controlling user SAAS application display permission, and the SAAS application management module provides an application list for the role management module;
the resource tree module is positioned in the cloud platform, the resource tree module internally contains public functions, the public functions internally contain application list resources, and the resource tree module is associated with SAAS application management through coding;
the APP terminal application list module is positioned in the front end, the APP terminal application list module is associated with an application card in the front end, the resource tree module provides resources for the APP terminal application list module, and the role management module controls whether the application in the APP terminal application list module is displayed or not.
As a further scheme of the invention, in the SAAS application management module, the selected parent level relationship is successively decreased as follows: application type, SAAS application, intra-application functions, if the application type is either a SAAS application or intra-application function, then the parent function must be selected.
As a further scheme of the invention, in the SAAS application management module, an application code list is provided with a selected code, a function icon and a selected function icon, wherein the APP video type is filled in by default.
As a further aspect of the present invention, in the SAAS application management module, if the selected parent level authority is unavailable to the buyer or the seller, the corresponding child function application authority is unavailable and is not editable, wherein the existing SAAS service of the buyer includes: infrastructure, mall, shopping cart, purchase order, wallet, coupon, live broadcast, distribution revenue, other services show no rights to use at APP end, sell money existing SAAS services include: infrastructure, live, prepaid loans, wallets, vouchers, coupons, business analyses, business coupon details, shelf management, sales policy management, sales order management, sales settlement management, customer management, other services show no rights to use at the APP end.
As a further scheme of the invention, the user data in the role management module is endowed with a plurality of new attributes so as to realize the compatibility of the user data in new and old versions and manage the user's use authority for SAAS application and functions in the SAAS application.
As a further aspect of the present invention, in the character management module, the SAAS application is divided into settable displays and commonly used applications, and functions in the application are settable only for displays.
As a further scheme of the invention, in the role management module, the menu authority checking rule at the APP end is as follows: the display is not checked, the common check is checked, and the default display is checked; and (3) selecting a common, canceling the selecting display, and canceling the selecting by default.
As a further scheme of the invention, in the online information examination of the cloud platform, the client identity is automatically associated, the client label is automatically associated and the user role is automatically associated according to the type of the dealer selected by the user.
As a further scheme of the invention, in the management of dealer personnel of the cloud platform, the newly added roles automatically increase the client identity and the client label corresponding to the dealer, and the user role list is determined according to the client label.
As a further scheme of the invention, in the cloud platform, the store management list, the dealer partner management list and the online information auditing list are added with more attributes, wherein the attributes are respectively a client identity, a client label and a user role.
Compared with the prior art, the invention has the following beneficial effects:
1. the invention provides a SAAS application resource allocation system based on containerization, which realizes the compatibility of new and old versions of user data by endowing the user data with new attributes, and then controls SAAS application display permission through a SAAS application management module, so that different types of user login accounts and SAAS applications configured on an APP end are different, thereby realizing the reduction of redundant repeated development work, realizing unified platform and service object, and improving the system extensible compatibility level of the platform.
Drawings
FIG. 1 is a flow chart of the user and SAAS application relationship of the present invention;
FIG. 2 is a flow chart showing whether the user and SAAS application of the present invention are displayed
Description of the embodiments
Embodiments of the present invention are described in further detail below with reference to the accompanying drawings and examples. The following examples are illustrative of the invention but are not intended to limit the scope of the invention.
In this embodiment, as shown in fig. 1, in a containerized SAAS application resource configuration system, by setting authority management on a cloud platform, a SAAS application management configuration application function and authority are enabled, role management configures various roles of users, gate management configures gate role users, dealer partner management configures a dealer white list, partner role users and online information audit configures a dealer white list, and different types of users are classified into an account, the account is divided into a client identity, a client tag and a user role, so that compatibility of new and old version user data is achieved, then all SAAS applications at an APP end are managed through an SAAS application management module, including controlling user SAAS application display authority according to whether the client identity displays the SAAS application or not, role management is different from each other according to client tag and role name, and because of different types of user login accounts, the configured SAAS applications at the APP end are different, thereby reducing redundant repeated development work, creating a standard product of SAAS well as enabling a required merchant on the platform, and improving the system scalability compatibility level of the platform.
Examples described below with respect to UC:
example 1: a background manager operates the addition, editing, deletion and inquiry of SAAS applications; the specific operation steps are as follows:
s1, clicking a new button of an SAAS application management menu, and entering a new SAAS application page.
S2, filling in function names, function codes, function types, orders, father-level functions, function states and client identity authorities.
S3, clicking a save button, and saving the saved button in an application list.
S4, clicking an editing button of one application of the SAAS application list, and entering an SAAS application editing page.
S5, editing application codes, application names, application codes, application types, ordering, father-level functions, application states and application rights.
S6, clicking a save button, and saving the saved button in an application list.
S7, clicking a delete button of an application in the SAAS application list, and popup a dialog box to prompt' whether to determine to delete the application? ".
S8, selecting yes to delete the application, updating the application list, and selecting no to vanish the dialog box.
S9, the SAAS application front page input box inputs function names.
S10, clicking a query button, and displaying a result after query according to the keywords.
Example 2: the background manager operates the addition, editing, checking, deleting and inquiring of role management; the specific operation steps are as follows:
s1, clicking a role management newly added button to enter a newly added role page.
S2, filling in a role code, a role name, selecting a client note, filling in a role description, checking whether the client note is an boss, and checking menu authority of an APP end.
S3, clicking for storage, and storing in a role list.
S4, clicking an edit button of a role in the role management list, and entering a role edit page.
S5, editing the role codes, the role names, the client labels, the role descriptions and changing the menu authority of the APP terminal.
S6, clicking for storage, and storing in a role list.
S7, clicking a view button of a certain role of the role management list, and entering a role view page.
S8, clicking a return button to return to the role list page.
S9, clicking a delete button of a character in the character management list, and popup a dialog box to prompt' whether to determine to delete the character? ".
S10, selecting 'yes' to delete the role, and updating the role list. Selecting no dialog disappears.
S11, inputting a role name by a role management input box, and selecting a client label.
S12, clicking a query button, and displaying a result after query according to the keywords.
Example 3: dealer boss, dealer delivery driver respectively log in town area application APP and use sales order SAAS application. Displaying different application internal functions according to the authority configuration; the specific operation steps are as follows:
s1, cloud platform SAAS application management is conducted on configured SAAS applications.
S2, the cloud platform role management clicks a new button, and a role new page is opened.
S3, filling in a role name of boss, wherein a client label is a dealer, and the role is described as follows: the dealer client boss role, the APP terminal menu authority is checked, wherein the menu authority comprises a sales order and all the functions in the application in the sales order (all, to be confirmed, to be received, to be paid and completed).
S4, clicking for storage, and storing in a role list.
S5, clicking the new button again, and opening the new page of the character.
S6, filling in a role name of a delivery driver, wherein a client label is the delivery driver, and the role is described as follows: the role of a delivery driver of a dealer selects APP menu authority, wherein the menu authority comprises a sales order and functions in the sales order: all the goods to be received and paid are finished.
S7, clicking for storage, and storing in a role list.
S8, opening the town village communication APP, logging in by using a dealer boss role account, and entering the home page after successful logging in.
S9, clicking tab column application, and entering an application page.
S10, clicking the sales order application, entering a sales order first page, seeing that the order states are all, waiting for confirmation, waiting for receiving goods, waiting for payment, and finishing.
S11, logging out, and logging in a login page.
S12, inputting the account number of the delivery driver of the dealer, clicking to log in, and entering the home page after successful login.
S13, clicking tab column application, and entering an application page.
S14, clicking the sales order application, entering a sales order first page, seeing that the order states are all, waiting for receiving goods, waiting for paying, and finishing.
To sum up, first, a new attribute is given to the user data: the user identity, the client label and the user role are used for realizing the compatibility of new and old version user data, and then the SAAS application management module is used for controlling the SAAS application display permission, so that different types of user login accounts and SAAS applications configured on the APP end are different, the redundant repeated development work is reduced, the unified platform and the service object are unified, and the system extensible compatibility level of the platform is improved.
The embodiments of the present invention have been presented for purposes of illustration and description, but are not intended to be exhaustive or limited to the invention in the form disclosed, and although the invention has been described in detail with reference to the embodiments, it will be apparent to those skilled in the art that modifications may be made to the technical solutions described in the foregoing embodiments, or equivalents may be substituted for some of the technical features thereof.

Claims (10)

1. A containerized SAAS application resource allocation system, the resource allocation system comprising a cloud platform and a front end, comprising:
the SAAS application management module is positioned in the cloud platform, a plurality of application types are formed in the SAAS application management module, the application types are formed by a plurality of applications, the application interior contains a plurality of functions, and the SAAS application management module is used for managing all SAAS applications at the APP end;
the role management module is positioned in the cloud platform, a plurality of roles are contained in the role management module, the role management module is used for controlling the SAAS application display permission of a user, and the SAAS application management module provides an application list for the role management module;
the resource tree module is positioned in the cloud platform, the interior of the resource tree module contains public functions, the interior of the public functions contains application list resources, and the resource tree module is associated with SAAS application management through coding;
the APP terminal application list module is positioned in the front end, the APP terminal application list module is associated with an application card in the front end, the resource tree module provides resources for the APP terminal application list module, and the role management module controls whether the application in the APP terminal application list module is displayed or not.
2. The containerized-based SAAS application resource allocation system of claim 1, wherein: in the SAAS application management module, selecting a parent level hierarchy relationship to be sequentially reduced as follows: application type, SAAS application, intra-application functions.
3. The containerized-based SAAS application resource allocation system of claim 2, wherein: in the SAAS application management module, an application code list is provided with a selected code, a function icon and a selected function icon, wherein the APP video type is filled in by default.
4. The containerized-based SAAS application resource allocation system of claim 3, wherein: in the SAAS application management module, if the selected parent level authority is unavailable to the buyer or the seller, the corresponding sub-function application authority is in an unavailable state and is not editable.
5. The containerized-based SAAS application resource allocation system of claim 1, wherein: and the user data in the role management module is endowed with a plurality of new attributes so as to realize the compatibility of the user data of new and old versions and manage the SAAS application and the use authority of the user on the functions in the SAAS application.
6. The containerized-based SAAS application resource allocation system of claim 5, wherein: within the role management module, SAAS applications are classified into settable displays and common applications, while functions within the applications can only be set for displays.
7. The containerized-based SAAS application resource allocation system of claim 6, wherein: in the role management module, the menu authority checking rule at the APP end is as follows: the display is not checked, the common check is checked, and the default display is checked; and (3) selecting a common, canceling the selecting display, and canceling the selecting by default.
8. The containerized-based SAAS application resource allocation system of claim 1, wherein: and in the online information examination of the cloud platform, automatically associating the client identity, automatically associating the client label and automatically associating the user role according to the type of the dealer selected by the user.
9. The containerized-based SAAS application resource allocation system of claim 8, wherein: and in the management of the dealer personnel of the cloud platform, the newly added role automatically increases the client identity and the client label corresponding to the dealer, and the user role list is determined according to the client label.
10. The containerized-based SAAS application resource allocation system of claim 9, wherein: and in the cloud platform, the store management list, the dealer partner management list and the online information auditing list are added with multiple attributes, wherein the attributes are respectively a client identity, a client label and a user role.
CN202310140067.4A 2023-02-08 2023-02-08 SAAS application resource allocation system based on containerization Pending CN116466982A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310140067.4A CN116466982A (en) 2023-02-08 2023-02-08 SAAS application resource allocation system based on containerization

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310140067.4A CN116466982A (en) 2023-02-08 2023-02-08 SAAS application resource allocation system based on containerization

Publications (1)

Publication Number Publication Date
CN116466982A true CN116466982A (en) 2023-07-21

Family

ID=87184794

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310140067.4A Pending CN116466982A (en) 2023-02-08 2023-02-08 SAAS application resource allocation system based on containerization

Country Status (1)

Country Link
CN (1) CN116466982A (en)

Similar Documents

Publication Publication Date Title
US20030050876A1 (en) Accounting system and method for processing transaction data
US20040193510A1 (en) Modeling of order data
US20070226068A1 (en) Customized extensions of electronic database objects
WO2008081336A2 (en) Technology platform for electronic commerce and a method thereof
US20230032447A1 (en) Systems and methods for selectively preventing origination of transaction requests
JP2003514306A (en) Method and process for pricing calculations using a computer system
MX2013005359A (en) System and method for consolidating account data.
US20230126131A1 (en) System for assisting searches for codes corresponding to items using decision trees
CN111199457A (en) Page generation method and device
CN116466982A (en) SAAS application resource allocation system based on containerization
US11531447B1 (en) System for assisting searches for codes corresponding to items using decision trees
CN115760262A (en) System and method for electronic commerce checkout with delayed loading of checkout options
CN109816558B (en) Transformer technology service platform system based on SAAS
US20210090035A1 (en) System and method for transmitting data over authorized transmission channels
KR20210068655A (en) Open market system with enhanced security by applying blockchain
US11562043B1 (en) System and method for rendering webpage code to dynamically disable an element of template code
US12008628B2 (en) Systems and methods for obscuring content in electronic messages
CN114119091B (en) Operation method and platform for constructing BC fusion ecology of mobile government enterprise business
US20220398646A1 (en) Systems and methods for obscuring content in electronic messages
US11829782B2 (en) System and method for contextual navigation in applications
KR102672386B1 (en) Systems and methods for e-commerce checkout with delay loading of checkout options
KR102476029B1 (en) System for managing business opportunity
KR102612583B1 (en) System and method for representing licenses for export and computer program for the same
US11809904B2 (en) System and method for executing multiple scripts at a single extension point
US20230206247A1 (en) Product catalog mapping and integration across distributed systems and interfaces, dynamic determination and presentation of customized service offers and lifecycle management of services

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination