CN114997550A - Business mode based on mixed SaaS and realization system thereof - Google Patents

Abstract

The invention relates to the field of business models, in particular to a business model based on mixed SaaS and an implementation system thereof. The business model participants disclosed by the invention comprise clients, users, advertisers and service providers; a service provider provides and operates various SaaS services such as business, link, advertisement and payment; a first client registers and subscribes a SaaS service to serve own users; an advertiser enters and subscribes to the advertisement SaaS, and issues the advertisement with commission; the second customer subscribes to the link SaaS and publishes the link with commission; the system comprises a first SaaS client and a second SaaS client, wherein the first SaaS client configures an advertisement of an advertiser or a SaaS link of the second client; the user of the first customer consumes the advertiser's advertising service or the second customer's linking service, generates a commission, and shares it between the first customer and the facilitator. The system for realizing the business model can accurately realize all functions required by the business model.

Description

Business mode based on mixed SaaS and realization system thereof

Technical Field

The invention relates to the field of business models, in particular to a business model based on mixed SaaS and an implementation system thereof.

Background

Software as a Service (SaaS) is a completely innovative Software application model that has started to emerge with the development of internet technology and the maturity of application Software. The SaaS service provider uniformly deploys the application software on the server and provides a software service mode for the user through the Internet. According to actual requirements, a customer can order required software services from a SaaS service provider through the Internet, pay the service provider according to the amount and time of the ordered services, and obtain the software services provided by the service provider through the Internet. In the SaaS service mode, a client rents Web-based software to a service provider instead of purchasing the software, and the software is not required to be maintained, so that the client does not need to consume a large amount of manpower and material resources in the aspects of hardware and software maintenance, and the enterprise operating cost is greatly saved.

SaaS application software is generally designed and applied based on a specific field, for example, salegorce is a Customer Relationship Management (CRM) software service provider.

The SaaS application software has three business modes of free, payment and value-added operation:

a free mode: the SaaS service provider can provide software for customers for free; however, advertisements are placed in software to capture revenue; however, software functionality does not support customization nor after-market service support;

and (3) payment mode: subscription fees in a common monthly or annual mode comprise application software license fees, maintenance fees and technical support fees;

value-added mode: free in the case of limited use of basic functions or capacity; but expansion of functionality and capacity upgrades requires payment. Free customer habits are cultivated, and then paid subscription use is guided; in essence, it is also a pay mode.

Since the proposal of SaaS concept, it has been proposed for over 20 years. Salesforce, the originator of SaaS, is currently the highest market value B2B service provider, which has been in the billions of dollars early; however, most of the domestic SaaS manufacturers develop the SaaS unsuccessfully. Enterprises have weak payment willingness, and particularly small and medium-sized micro enterprises only want to use a free SaaS. Whether the cost is free or charged, how to profit and live is always a thought problem for domestic SaaS manufacturers.

Disclosure of Invention

The invention relates to the field of business models, in particular to a business model based on mixed SaaS and an implementation system thereof. The business model participants disclosed by the invention comprise clients, users, advertisers and service providers; a service provider provides and operates various SaaS services such as business, link, advertisement and payment; a first client logs in and subscribes a service SaaS service to serve own user; an advertiser enters and subscribes to the advertisement SaaS, and publishes a marketing advertisement with commission; the second customer subscribes a link SaaS, releases the link with commission and connects to the service SaaS; the system comprises a first SaaS client and a second SaaS client, wherein the first SaaS client configures marketing advertisements of an advertiser or SaaS links of the second client; the user of the first customer, consuming the advertiser's advertisement or the linking service of the second customer, generates a commission, which is shared between the first customer and the facilitator. Specifically, the method comprises the following steps:

the method comprises the following steps that 1, a SaaS service provider provides service SaaS service, main business requirements of customers are met, and users of the SaaS customers are served;

the SaaS service provider provides link SaaS service to meet the requirement of sharing flow among customers; the client can configure SaaS links of other clients to the service SaaS, so that various services are provided for the user, and the income of the client is increased;

3, providing an advertisement SaaS service by a SaaS service provider, and providing a marketing promotion service to an advertiser; customers can be selectively deployed in the service SaaS to earn advertising income;

the SaaS service provider also provides basic SaaS services such as payment and the like as service basic requirements of other SaaS;

5. based on the design of a shared economic model, SaaS customers not only have business income of main business, but also income of links and advertisements, and the possibility of deploying SaaS application is greatly improved.

The brand new business model constructs a mixed SaaS application model combining service SaaS and commission SaaS, can share user flow among customers while meeting the service requirements of SaaS customers, even provides advertisement positions for external third parties, gives the customers the ability of increasing extra income, improves the deployment possibility of the SaaS service, and is a win-win business model. The system for realizing the business model can accurately realize all functions required by the business model.

A hybrid SaaS-based business model, comprising: a facilitator, a customer, a user, and an advertiser;

the service provider refers to a business body for providing and operating SaaS;

the client refers to an individual or a business body subscribing to SaaS;

the user refers to an individual served by a customer subscribing to SaaS;

the advertiser refers to an individual or a business needing marketing promotion.

A business model based on hybrid SaaS, wherein, SaaS service provider

1. Providing and operating service SaaS, linking SaaS, advertising SaaS, paying SaaS and the like; assisting clients and advertisers in living and subscribing to SaaS services;

2. the service SaaS refers to a SaaS system that helps a customer develop a main business, such as a property SaaS system for a property company, a retail SaaS system for a roadside shop, and the like;

3. the link SaaS refers to a SaaS system for helping the customers to share flow, provides the capability of the first customer to directly reach the second customer service, and is a value-added SaaS service;

4. the advertisement SaaS refers to a SaaS system for helping SaaS clients and any third party to publish advertisements, and is a value-added SaaS service;

5. the payment SaaS refers to a SaaS system which aggregates a plurality of payment modes, supports other SaaS operation and is a basic SaaS system.

A business model based on mixed SaaS, wherein, a client and a SaaS service provider sign an agreement, check in the SaaS system and subscribe a service SaaS

1. The service SaaS service does not refer to the industry and the field in particular, and can be any SaaS software provided by a SaaS service provider; for example; property companies can subscribe property SaaS, provide functions of repair reporting, entrance guard, parking and the like, and serve community owners; the retail store can subscribe the retail cloud, provide functions of commodity display, navigation, payment and the like, and serve customers of the store;

2. the client can configure links to other clients at the link position of the SaaS service system, such as a service home page;

3. the client can configure advertisements of other clients or third parties on the advertisement position of the SaaS service system, such as a payment result page;

a business model based on mixed SaaS, wherein, a client and a SaaS service provider sign an agreement, check in the SaaS system and subscribe and link the SaaS service

1. Creating a link; the link is a link directly reaching the SaaS system;

2. setting the geographic range, the time range and the commission of the release to release the link;

3. the geographic scope may be based on administrative region, longitude, and latitude;

4. the time range is a limited and unlimited time or date period;

5. the commission can be set as an order calculation formula or a fixed amount for a single order.

A business model based on mixed SaaS, wherein, an advertiser signs an agreement with a SaaS service provider, stays in a SaaS system, and subscribes to an advertisement SaaS service

1. The advertiser may be an in-house SaaS client or may be a third party using any SaaS system

2. Creating an advertisement; the advertisements can be unlinked effect advertisements and linked purchase advertisements;

3. setting the geographic range, the time range and the commission of the distribution to distribute the advertisement;

4. the geographic scope may be based on administrative region, longitude, and latitude;

5. the time range is a limited and unlimited time or date period;

6. the commission can be set as a calculation formula or a fixed amount.

A hybrid SaaS-based business model, wherein system revenue is allocated as;

1. all SaaS subscription fees are collected by a SaaS service provider; subscription mode, based on one or more of the existing modes (free/charged/added value);

the SaaS client receives the income generated by the SaaS service system;

and 3, sharing the link and the income of the advertisement by the SaaS client and the SaaS service provider according to the check-in agreement.

A system for implementing the business model described above, comprising: client, management side, business SaaS, link SaaS, advertisement SaaS, payment SaaS, commission subsystem, service terminal system and database side.

A system for implementing the business model, wherein the client is composed of the following modules,

1. the check-in module provides a protocol for a client to apply and check in the SaaS system;

2. the subscription module is used for subscribing and managing various SaaS services;

3. the link module is used for configuring links based on link bits in the service system;

4. the advertisement module is used for configuring advertisements based on advertisement positions in the service system;

5. the revenue module is used for checking and bringing back revenue shared by the SaaS;

6. the account module is used for displaying and managing information such as login, name, contact information, contract and the like;

and the IO module sends requests of other modules to the service subsystem and receives responses from the service subsystem.

A system for realizing the business model, wherein the management terminal is composed of the following modules,

1. the auditing module is used for auditing the processes of client and advertiser check-in, linkage, advertisement release, commission cash withdrawal and the like;

the SaaS module is used for displaying and detecting the running state of the SaaS and performing calculation resource allocation;

3. the profit module is used for displaying and managing orders, commissions and profits of the whole platform;

4. the order module is used for displaying and managing subscription orders of the whole platform;

5. the wallet module is used for platform fund income, expenditure and statistics;

6. the account module is used for displaying and managing all data of the system such as accounts, links, advertisements and the like;

IO module, sending requests of other modules to the service subsystem and receiving responses from the service subsystem.

A system for realizing the business model is provided, wherein the service SaaS is not specially used, and any SaaS with configurable link slots and advertisement slots can be provided for customers.

A system for implementing the business model, wherein the linked SaaS is composed of the following modules

1. The link module is used for creating and managing a link of a service SaaS of a client;

2. the release module is used for setting parameters such as a position range, a time range, a link commission and the like and releasing a link;

3. a commission module that displays and manages commission orders, account charges, and expenses;

4. the message module provides a message notification interface for other modules to use;

5. the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

A system for realizing the business model is characterized in that the advertisement SaaS consists of the following modules

1. The advertisement module is used for creating and managing various types of advertisements, such as unlinked effect advertisements or linked advertisements;

2. the publishing module is used for setting parameters such as position range, time range, advertisement commission and the like and publishing the advertisement;

3. a commission module for displaying and managing commission orders, account recharge and expenditure;

4. the message module provides a message notification interface for other modules to use;

5. the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

A system for implementing the business model, wherein the payment SaaS is composed of the following modules

1. The payment module provides a uniform payment code or page for the client and the user side and supports multiple payment modes (Paibao, WeChat and Unionpay);

2. the transfer module supports the SaaS service provider to transfer accounts (a payment treasure, a WeChat and a bank card) in various modes to customers and advertisers;

3. the message module provides a synchronous and asynchronous message synchronous mechanism and informs the order payment and transfer results;

4. the data module records payment and transfer details of each order in a database and provides a query function;

and the IO module receives the request of the client and sends the response of other modules.

A system for implementing the business model wherein the commission subsystem is comprised of

1. The address module is used for generating a global unified tracking HTTP address based on the service link of the client and the advertisement of the cloud advertiser;

2. a commission module that generates commissions and assignments based on the link and the advertised order requests, including creating commissions, querying commissions, updating commissions, and commission calculations;

3. the relay module is adapted to a service API of a third-party system;

4. the message module provides a synchronous and asynchronous message synchronous mechanism and receives external notification;

5. the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

A system for realizing the business model, wherein the service terminal system consists of the following modules

1. The auditing module supports various flow requests of all clients, including client check-in, advertisement check-in, link release, advertisement release and cash withdrawal;

2. the order module supports order business requests of all clients, including order creation, order query and order updating;

3. a financial module supporting wallet, commission, payment and cash withdrawal requests of all clients;

4. the account module supports account information requests of all clients, including system user login, data query and update and the like;

5. the message module provides a message notification interface for other modules to use; supporting message notification in all business processes of the system;

6. the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

A system for realizing the business model is provided, wherein the database end is used for storing all data in the system. Drawings

FIG. 1 is a diagram of the relationship between business model bodies of the present invention.

FIG. 2 is a schematic diagram of a system architecture for implementing the present invention.

FIG. 3 is a flow diagram of a first client creating and publishing a link in accordance with an implementation of the present invention.

FIG. 4 is a flow chart of a second client configuration link implemented by the present invention.

FIG. 5 is a flow chart of a user of a second customer consuming a first customer linking service implemented by the present invention.

FIG. 6 is a flow chart of a user of a second customer consuming a third party advertiser service implemented by the present invention.

Figure 7 is a flow diagram of a second customer commission liquidation implemented by the present invention.

Detailed Description

Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

A relationship diagram between the business model participating entities, which includes customers, users, advertisers, and SaaS service providers, is shown in fig. 1.

This business model is illustrated in a story example, in which:

a is a SaaS service provider, and provides and operates a set of mixed SaaS system based on property SaaS, catering SaaS, link SaaS, advertisement SaaS and payment SaaS.

B is a property company of a certain cell, and under the assistance of A, the property company signs a protocol to enter the mixed SaaS system and becomes a client; the property SaaS is subscribed to provide community services such as repair reporting and notification for community users; a also enters into commission sharing agreement with B, and the agreement links commission and shares according to 6 and 4 proportion.

C is an unlocking individual user near a certain cell, and with the assistance of A, the unlocking individual user signs a protocol to enter the mixed SaaS system and becomes a customer; subscribed to link and retail SaaS services. A also signs a link service agreement with B, and agrees on the link commission calculation mode (fixed amount or proportion) and other calculation modes; a also enters into a payment service agreement with B, and the calculation mode (fixed amount or proportion) of payment service fee and other calculation modes are agreed, wherein the fixed value is 0.6%.

D is a restaurant chain store nearby a certain cell, and with the assistance of A, a contract is signed to enter a mixed SaaS system to form a cloud advertiser; and subscribing the advertisement SaaS and providing marketing service for the SaaS system. A also enters into an advertising service agreement with B, agreeing on advertising commission calculation (fixed amount or proportion) and others, here set to 10% of the amount.

E and F are cell users who have requested maintenance using the system of property company B and become users of B.

The unlocking individual C creates and audits the unlocking link, and the commission profit is 1 yuan/pen with fixed amount.

Restaurant chain D created and reviewed an advertisement that passed a 199 family package with a commission revenue of 10% of the order amount.

The property company B configures the service link of the unlocking individual user C to the link bit of the home page- > life service- > unlocking service.

Property company B sets 199 package marketing advertisements for restaurant chain D to be on the home page carousel advertisement position.

In the first business operation example, user E submits an unlock service order with an unlock order price of 150 via the unlock link of the life service page of property company B.

Then, during this transaction, the individual unlocking user C needs to pay the service commission according to the agreement, and the service provider A and the property company B share the link commission income, and the income and expense are calculated as follows

C, income of orders: 150 x (100-0.6)/100 =149.1 members;

c, paying the service fee: 150 × 0.6/100=0.9 membered;

c commission expenditure: 1 yuan;

link revenue a: 1 x 0.6=0.6 membered;

b link revenue: 1 x 0.4=0.4 membered;

service fee income: 150 × 0.6/100=0.9 yuan.

In the second business run example, user F clicked and purchased 199 restaurants of restaurant chain D through the advertising carousel page of the home page of property company B.

Then, during this transaction, chain D needs to pay the advertising commission as agreed upon, and facilitator A and property company B share the link commission revenue, which is calculated as follows

D, order income: 199 yuan;

d advertising commission expenditure: 199 × 10% =19.9 yuan;

and A, advertising revenue income: 19.9 × 0.6=11.94 yuan;

b, advertising revenue income: 19.9 × 0.4=8.05 yuan;

service fee income A: 0-bit.

After two business operations, the service provider A receives 0.9+0.6+11.94=13.44 yuan, and the property company B receives 0.4+8.05=8.45 yuan. As the SaaS client of a, B also shares user traffic with the unlocking individual user C and the catering chain D while subscribing to the service a to serve the user, and generates revenue other than the main business.

A system 200 for implementing the business model is shown in fig. 2.

The system 200 includes a client 210, a management side 220, a business SaaS230, a link SaaS240, an advertisement SaaS250, a payment SaaS260, a commission subsystem 270, a service subsystem 280, and a database 290.

The service SaaS230, the link SaaS240, the advertisement SaaS250, and the payment SaaS260 include two parts, a user side and a service side.

The client 210, the administration end 220, the business SaaS230 user end, the linking SaaS240 user end, the advertising SaaS250 user end, and the payment SaaS260 user end may be implemented as applications of various smart devices, applets (WeChat, Paibao, and Baidu) of various software platforms, or Html web pages running on any of various computing devices, such as a desktop computer, a notebook computer, a smart phone, a tablet computing device, or a computer server system.

The business SaaS230 server, the link SaaS240 server, the advertisement SaaS250 server, the payment SaaS260 server, the commission subsystem and the cloud service terminal system are implemented as a server background process or thread, and run on a physical computer server or a cloud server.

Database 290 is implemented as an open source or commercial version of a software server running on a physical computer server or a cloud server. The database 290 includes a business database 291, a link database 292, an advertisement database 293, a payment database 294, and a SaaS service database 295.

All subsystems of system 200 make service requests and responses over the network. The network may be any of a variety of networks, such as a LAN, WAN, VPN, wireless network, the Internet, a point-to-point network, a cellular telephone network, a 3G/4G/5G network, or any combination thereof.

The client 210 includes a check-in module 211, a subscription module 212, a link module 213, an advertisement module 214, a revenue module 215, an account module 216, and an IO module 217.

The check-in module 211 provides a protocol for a client to apply and check in the SaaS system. Specifically, the receiving client inputs an individual identification code (a business code of a business body or an identity card of an individual), attaches other information and contact information, signs and submits the individual identification code and the identity card to the check-in agreement.

And a subscription module 212 for providing SaaS subscription and managing the SaaS service. Specifically, the SaaS service list is browsed, the detailed function details of the SaaS service are checked, subscription is initiated, and subscription cost is paid.

The link module 213 configures the link based on the link bits in the business system. Specifically, after browsing the configurable link service list and viewing the links and commission details, the available link positions of the business system are selected for configuration.

The advertisement module 214 configures advertisements based on ad slots in the business system. Specifically, a configurable advertisement list is browsed, the display and commission details of the advertisement are viewed, and the available advertisement position of the business system is selected for configuration.

And the revenue module 215 is used for checking and bringing up revenue of SaaS sharing. Specifically, the revenue orders are viewed and counted according to multiple dimensions of time, advertisers, linked customers and the like, and the revenue is brought up.

The account module 216 presents and manages information such as login, name, contact, contract, etc.

The IO module 217 sends requests of other modules to the service subsystem and receives responses from the service subsystem.

The management terminal 220 includes an auditing module 221, a SaaS module 222, a revenue module 223, an order module 224, a wallet module 225, an account module 226, and an IO module 227.

The auditing module 221 audits the flows of client and advertiser check-in, link and advertisement release, commission cash withdrawal and the like; specifically, an audit message from the service terminal system 280 is received, and the flow to be audited is triggered to be reached for auditing; or opening the list to be audited and auditing item by item.

The SaaS module 222 is configured to display and detect a SaaS operating state, and perform resource allocation; specifically, the running state of the SaaS resource, such as the running duty ratio of the CPU, the memory, and the like, and the performance parameters such as the service response time, are checked, and the resource is adjusted.

A revenue module 223 that displays and manages the entire platform order, commission, and revenue; specifically, the system running state is checked according to multiple dimensions such as time, advertisers and clients.

The order module 224 is used for displaying and managing SaaS subscription orders of the whole platform;

a wallet module 225, platform funding, spending, and statistics; in particular, cloud customer subscription revenue, advertiser commission recharge and consumption, customer link commission recharge and consumption, and customer revenue and expenditure are managed.

An account module 226 for displaying and managing all data of the system such as accounts, links, advertisements, etc.;

the IO module 227 sends requests of other modules to the service subsystem and receives responses from the service subsystem.

The commission subsystem 270 includes an address module 271, a commission module 272, a relay module 273, a message module 274, a data module 275, and an IO module 276.

The address module 271 generates a global unified tracking HTTP address based on the business links of the customer and the advertisements of the cloud advertiser. Specifically, for service link and service-oriented SaaS advertisements, a release type, a release Id and a configurator Id are adopted as parameters to identify one commission record; further, for an advertisement directed to the three-party SaaS, a service return service address and a callback service parameter need to be carried.

The commission module 272 generates commissions and allocations based on the link and the advertised order requests, including creating commissions, querying commissions, updating commissions, and commission calculations. Specifically, based on tracking the HTTP address, generating an order record, generating a commission record, and according to the agreement, performing commission sharing calculation to generate a shared commission record.

The relay module 273 configures a service API of the third party system. Specifically, a record of HTTP tracking address access to the third system is sent to the third-party system, and a callback notification of the third-party system is received.

The message module 274, which provides synchronous and asynchronous message synchronization mechanisms, receives commission order change notifications. And receiving a payment notice of the relay module or the payment SaaS.

And a data module 275 for providing a database access interface for use by other modules.

The IO module 276 receives requests from clients and sends responses from other modules.

The service subsystem 280 includes an audit module 281, an order module 282, a financial module 283, an account module 284, a message module 285, a data module 286, an IO module 287.

The auditing module 281: various process class requests are supported for all clients, including client check-in, ad check-in, link publishing, ad publishing, and cash-out.

The order module 282: and supporting order business requests of all clients, including order creation, order query and order updating.

Financial module 283: supporting all clients' wallets, commissions, payments, and cash requests.

The account module 284: and supporting account information requests of all clients, including system user login, data query and update and the like.

Message module 285: providing a message notification interface for other modules to use; and supporting message notification in all business processes of the system.

The data module 286: and providing a database access interface for other modules to use.

The IO module 287: receiving the request of the client and sending the response of other modules.

Fig. 3 is a flow chart illustrating the creation and publication of links by the first client.

Step S3010: the first customer opens the client linked to the SaaS240 and performs a login operation. The login here may be consistency verification based on a login name and a password, or joint login verification based on a third-party software platform such as WeChat and Paibao.

Step S3020: the first client creates or edits a link through a link module; link names, labels, notes, etc. may be set.

Step S3030: and the first client submits a storage request by carrying the filled link data through the link module. And after receiving the link saving request, the link SaaS240 server side saves the link SaaS240 server side into the link database 292 through the data module, and returns the request result to the link SaaS240 client side.

Step S3040: the first client confirms whether the link is immediately published. If not, the process ends, otherwise, the process is continued.

Step S3050: the first client sets a publication target of the link. A customer may have one or more services, SaaS, services in the hybrid SaaS system, and sets one of the services, SaaS, as a linked release target by sending a request acquisition list to the SaaS service terminal system 280. Further, a link sub-path parameter may be set to point to a specific service page of the target service SaaS.

Step S3060: the first client sets the publishing scope of the link. The range dimension may be industry, geography, time, and customer specific, among others. The client carries the customer Id in the data set in the specific dimension, and sends a request to the SaaS service terminal system 280 for acquisition.

Step S3070: the first customer sets the linked commission calculation mode. The commission calculation mode can be various modes of single-stroke fixation, percentage and the like. The commission may also be set to 0 based on the need for 2 customers to share links with each other. The specific commission calculation method is that the client sends a request to the SaaS service terminal system 280 for acquisition.

Step S3080: the first client saves the link publication. And saving the link release by sending a report request to a link SaaS240 server. Further, after receiving the request, the link SaaS240 service side requests the link release of an audit request to the SaaS service subsystem 280.

Step S3090: the link creation and publication process for the first client ends.

The link release can be really retrieved and configured by other customers only after the link release is approved by the SaaS service provider. The flow of link publishing audits follows.

Step S3100: the SaaS service terminal system 280 sends a notification to be checked of the link to the management terminal through the message module 285, and notifies the SaaS service provider to check the link issue.

Step S3110: the SaaS service provider opens the management terminal 220, and checks the detailed content of the link release through the auditing module 221. The auditing module 221 acquires the detailed content of the link release by requesting the link SaaS240 server.

Step S3120: the SaaS service provider submits the audit result through the audit module 221.

Step S3130: the SaaS service subsystem 280 performs different processes according to the audit result. If so, a unified access address is requested from the commission SaaS subsystem 270. Further, in step S3140, the link issuance of this time is placed into the link issuance resource pool.

Step S3150: the SaaS service subsystem 280 sends the audit result notification to the client through the message module 285.

For steps S3100 and S3150, the notifications are shown to be of different types, depending on the client. If the client intelligent terminal is applied as the APP of the mobile phone, the communication channel notification based on the intelligent terminal is realized; if the client is a WeChat or a small program for paying the treasures, realizing service notification of the WeChat or the small program for paying the treasures; if the client is a web page based on the WeChat public number or the Paobao living number, the client is realized as a template message in the public number or the living number; if the client is a browser-based web page, then the prompt notification is implemented as a web page.

Fig. 4 shows a flow chart for configuring a first client link for a second client.

Step S4010: the second client opens the client 210 and performs a login operation. The login here may be consistency verification based on a login name and a password, or joint login verification based on a third-party software platform such as WeChat and Paibao.

Step S4020: and the second client selects the service SaaS of the link to be configured. A customer may have one or more services, SaaS, services in the hybrid SaaS system, and set one of the services, SaaS, as a linked configuration target by sending a request acquisition list to the SaaS service terminal system 280.

Step S4030: the second client looks at the available link configuration bits. The link bits here may be the number and fixed position of the page specified for the service SaaS, or may be a custom addable position.

Step S4040: the second customer selects a certain link configuration bit.

Step S4050: the second client looks for available links. And the data such as the second customer Id and the service SaaS Id are carried, and a list requesting to acquire an available link is sent to the SaaS service subsystem 280.

Step S4060: the second client views the specific links in the link list. And carrying data such as the second customer Id and the link Id, and sending detailed data for requesting to acquire the link to a link SaaS240 server.

Step S4070: the second client submits a configuration link request through the link module. Upon receiving the link configuration request, the SaaS service subsystem 280 generates a link configuration record, and stores the link configuration record in the database 292 through the data module 286.

Step S4080: the SaaS service subsystem 280 sends a link configured notification to the linked SaaS240 client through the message module 285. Notifications are shown as different types, depending on the client. If the client intelligent terminal is applied as the APP of the mobile phone, the communication channel notification based on the intelligent terminal is realized; if the client is a WeChat or Payment-treasure applet, realizing a service notification of the WeChat or Payment-treasure; if the client is a web page based on the WeChat public number or the Paobao living number, the client is realized as a template message in the public number or the living number; if the client is a browser-based web page, then the prompt notification is implemented as a web page.

Step S4090: the configuration link flow ends.

Fig. 5 is a flow chart illustrating the consumption of the first customer link service by the user of the second customer.

Step S5010: and the user of the second customer opens the user side of the SaaS system of the second customer service and clicks the link pointing to the SaaS of the first customer. Further, the user side of the second customer service SaaS system carries the Id of the second customer, the link Id, and the user Id requests the commission subsystem 270 to generate the feature code of the click.

Step S5020: and receiving the feature code, collecting the uniform access address of the link, and jumping the user side system of the second customer SaaS to the user side of the first customer service SaaS.

Step S5030: and the user side of the first client SaaS analyzes the sub-path parameters and directly displays the page corresponding to the link.

Step S5040: the user inputs information and initiates a purchase operation. The input information may be specific amount of money or may be user-defined data such as purchase amount. A first client SaaS user side requests a first client SaaS server side to generate an order number; further, a first client SaaS server side carries an order number to apply for a corresponding payment number to the payment SaaS; further, after obtaining the payment number, the payment SaaS, carrying the order number and the payment number, sends a commission record generation request to the commission subsystem 270.

Step S5050: after receiving the order number and the payment number, the first customer SaaS user side calls a third party payment SDK (WeChat, Payment treasure, Unionpay and the like) and displays a payment page.

Step S5060: the user performs a payment operation.

Step S5070: if the payment is successful, the message module of the payment SaaS260 receives a payment result notification of the third party and sends the result to the service end of the first customer SaaS. Further, the commission subsystem 270 is notified that payment was successful and the commission record status is updated. Further, the commission record updating also comprises splitting between the second customer and the SaaS service provider according to the check-in agreement to generate two sub commission records.

Step S5080: and the first customer SaaS user side jumps to an order display page. Through the order Id, the first customer SaaS user side acquires and displays order detailed data, payment results, service delivery and the like.

Step S5090: the purchase procedure is ended.

Fig. 6 is a flow diagram illustrating a user of a second client consuming a third party advertising service.

Step S6010: and the user of the second client opens the user side of the second client service SaaS system and clicks the advertisement pointing to the third party SaaS. Further, the second customer service SaaS system user side carries the Id of the second customer, the link Id, and the user Id to the commission subsystem 270 to request generation of the feature code of this click.

Step S6020: and receiving the feature codes, collecting the uniform access addresses of the links, and jumping the user side system of the second customer SaaS to the user side of the third party SaaS.

Step S6030: and a user side of the third-party SaaS directly displays the page corresponding to the advertisement.

Step S6040: the third party SaaS system follows the interface definition, carries the feature code to synchronize the order generation data to the commission subsystem 270. After the order data is obtained, the commission subsystem 270 generates a commission record through the relay module 273 after obtaining the order data, and sends an order generation request to the advertisement SaaS server with the order data.

Step S6050: the third party SaaS system follows the interface definition, carrying feature codes to synchronize order payment data to the commission subsystem 270. After obtaining the order payment data, the commission subsystem 270 updates the commission record through the relay module 273; further, updating also includes splitting between the second customer and the SaaS service provider according to the check-in agreement to generate two sub-commission records. And further, sending an order updating request to the advertisement SaaS server by carrying order data.

Fig. 7 is a flow chart showing the second customer profit raising.

Step S7010: the first client opens the client 210 and performs a login operation. The login here may be consistency verification based on a login name and a password, or joint login verification based on a third-party software platform such as WeChat and Paibao.

Step S7020: the first customer views the revenue list through the revenue module 213 for the amount of cash drawable.

Step S7030: the first customer clicks the cash withdrawal and inputs the cash withdrawal amount; revenue module 212 initiates a revenue generation request to service subsystem 280; after the service terminal system 280 receives the cash withdrawal request, the financial module 283 performs data analysis and security verification, generates a cash withdrawal application record through the data module 286, and stores the cash withdrawal application record into the database 295;

step S7040: further, the message module 285 of the service terminal system 280 sends a message to the management terminal 220 to prompt that the current needs to be checked; financial module 283 may also send a message to client 210 via message module 285 to prompt that the cash register creation was successful, waiting for review.

Step S7050: the SaaS service provider opens the management terminal 220. Auditing the cash-out record generated in the step S7030; if the audit is passed, the execution is continued; otherwise, the message module 285 of the service subsystem 280 sends an audit failure notification to the first client.

Step S7060: the financial module 283 of the service terminal system 280, carrying the first customer identification number and the amount of money, sends a transfer request to the payment SaaS260 through the IO module 287.

Step S7070: a transfer module of the payment SaaS260, generating a transfer record according to the first identification number and the amount of money, and storing the transfer record into the database 294 through a data module; further, calling a third party payment platform (WeChat payment, Paibao payment and Unionpay payment) SDK to execute the transfer request; then the message module receives the transfer result of the payment platform, and updates the transfer record state to the database 294 through the data module; finally, the message module sends a payment status message to the service subsystem 280 through the IO module.

Step S7080: the service terminal system 280 receives the payment state message sent by the payment SaaS260, and updates the cash-out record state to the database 295.

Step S7090: service subsystem 280, using message module 285, notifies the first customer of the cash transfer status.

Although the preferred embodiments of the present patent have been described in detail, the present patent is not limited to the above embodiments, and various changes can be made without departing from the spirit of the present patent within the knowledge of those skilled in the art.

Claims (10)

1. A hybrid SaaS-based business model, comprising: service provider, customer, user, and advertiser;

the service provider refers to a business body for developing and operating mixed SaaS;

the client refers to an individual or a business body subscribing to SaaS;

the user refers to an individual subscribed to SaaS by a customer;

the advertiser refers to an individual or a business needing service promotion;

a service provider provides and operates various SaaS services such as business, link, advertisement and payment; a first client logs in and subscribes a service SaaS service to serve own user; an advertiser enters and subscribes to the advertisement SaaS, and publishes a marketing advertisement with commission; the second customer subscribes the link SaaS, releases the link with commission and is connected to the service SaaS of the second customer; the system comprises a first SaaS client and a second SaaS client, wherein the first SaaS client configures marketing advertisements of an advertiser or SaaS links of the second client; the user of the first client consumes the advertisement of the advertiser or the link suit of the second client, generates a commission record and shares the commission record between the first client and the service provider;

the brand new business model constructs a mixed SaaS application model combining service SaaS and commission SaaS, can share user flow among customers while meeting the service requirements of SaaS customers, even provides advertisement positions for external third parties, gives the customers the ability of increasing extra income, improves the deployment possibility of the SaaS service, and is a win-win business model.

2. The business model of claim 1, wherein:

the service SaaS is a system with a link position and an advertisement position and serving for the customer main business;

linking the SaaS into a system for performing user sharing service among mixed SaaS customers;

the system comprises a system for providing advertisement service for a mixed SaaS client or any external third party by using an advertisement SaaS;

and paying other SaaS such as SaaS to provide basic service for the mixed SaaS system.

3. A system for realizing the business mode comprises a client, a management end, a business SaaS, a link SaaS, an advertisement SaaS, a payment SaaS, a commission subsystem, a service terminal system and a database end.

4. The system of claim 3, wherein:

the client is realized as application programs of various intelligent devices, small programs (WeChat, Paobao and Baidu) of various software platforms or Html web pages and consists of the following modules:

the check-in module provides a protocol for a client to apply and check in the SaaS system;

the subscription module is used for subscribing and managing various SaaS services;

the link module is used for configuring links based on link bits in the service system;

the advertisement module is used for configuring advertisements based on advertisement positions in the service system;

the revenue module is used for checking and bringing back revenue shared by the SaaS;

the account module is used for displaying and managing information such as login, name, contact information, contract and the like;

the IO module sends requests of other modules to the service subsystem and receives responses from the service subsystem.

5. The system of claim 3, wherein:

the management terminal is realized as application programs of various intelligent devices, small programs (WeChat, Paibao and Baidu) of various software platforms or an Html webpage and comprises the following modules:

the auditing module is used for auditing the processes of client and advertiser check-in, linkage, advertisement release, commission cash withdrawal and the like;

the SaaS module is used for displaying and detecting the running state of the SaaS and performing calculation resource allocation;

the profit module is used for displaying and managing orders, commissions and profits of the whole platform;

the order module is used for displaying and managing subscription orders of the whole platform;

the wallet module is used for platform fund income, expenditure and statistics;

the account module is used for displaying and managing all data of the system such as accounts, links, advertisements and the like;

and the IO module sends the request of other modules to the service terminal system and receives the response from the service terminal system.

6. The system of claim 3, wherein:

the link SaaS comprises a user side and a service side; the user side is realized as application programs of various intelligent devices, small programs (WeChat, Paibao and Baidu) of various software platforms or an Html webpage; the server is realized as a server background process or a thread; the system consists of the following modules:

the link module is used for creating and managing a link of a service SaaS of a client;

the release module is used for setting parameters such as a position range, a time range, a link commission and the like and releasing a link;

a commission module that displays and manages commission orders, account charges, and expenses;

the message module provides a message notification interface for other modules to use;

the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

7. The system of claim 3, wherein:

the advertisement SaaS comprises a user side and a server side; the user side is realized as application programs of various intelligent devices, small programs (WeChat, Paibao and Baidu) of various software platforms or an Html webpage; the server is realized as a server background process or a thread; the system consists of the following modules:

the advertisement module is used for creating and managing various types of advertisements, such as unlinked effect advertisements or linked advertisements;

the publishing module is used for setting parameters such as position range, time range, advertisement commission and the like and publishing the advertisement;

a commission module that displays and manages commission orders, account charges, and expenses;

the message module provides a message notification interface for other modules to use;

the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

8. The system of claim 3, wherein:

the payment SaaS comprises a user side and a service side; the user side is realized as application programs of various intelligent devices, small programs (WeChat, Paibao and Baidu) of various software platforms or an Html webpage; the server is realized as a server background process or a thread; the system consists of the following modules:

the payment module provides a uniform payment code or page for the client and the user side and supports multiple payment modes (Paibao, WeChat and Unionpay);

the account transfer module supports the SaaS service provider to transfer accounts (payment treasures, WeChat and bank cards) in various modes to the customers and the advertisers;

the message module provides a synchronous and asynchronous message synchronous mechanism and informs the order payment and transfer result;

the data module records payment and transfer details of each order in a database and provides a query function;

and the IO module receives the request of the client and sends the response of other modules.

9. The system of claim 3, wherein:

the commission subsystem is implemented as a server background process or thread and consists of the following modules:

the address module is used for generating a global unified tracking HTTP address based on the service link of the client and the advertisement of the cloud advertiser;

a commission module that generates commissions and allocations based on the link and the advertised order requests, including creating commissions, querying commissions, updating commissions, and commission calculations;

the relay module is adapted to a service API of a third-party system;

the message module provides a synchronous and asynchronous message synchronous mechanism and receives external notification;

the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

10. The system of claim 3, wherein:

the service terminal system is realized as a server background process or a thread and comprises the following modules:

the auditing module supports various flow requests of all clients, including client check-in, advertisement check-in, link release, advertisement release and cash-out;

the order module supports order business requests of all clients, including order creation, order query and order updating;

a financial module supporting wallet, commission, payment and cash withdrawal requests of all clients;

the account module supports account information requests of all clients, including system user login, data query and update and the like;

the message module provides a message notification interface for other modules to use; supporting message notification in all service flows of the system;

the data module provides a database access interface for other modules to use;

and the IO module receives the request of the client and sends the response of other modules.

Images