WO2018033020A1

WO2018033020A1 - Multi-stage entrance concatenation based network platform framework

Info

Publication number: WO2018033020A1
Application number: PCT/CN2017/096978
Authority: WO
Inventors: 徐子明
Original assignee: 重庆兴韦度科技有限公司
Priority date: 2016-08-16
Filing date: 2017-08-11
Publication date: 2018-02-22
Also published as: CN106326383A; CN106326383B

Abstract

A multi-stage entry concatenation based network platform framework, comprising an entry database, a user database, a service provider database, a service database and a settlement database, wherein the entry database, the user database, the service provider database, the service database and the settlement database respectively comprise an entry processor, a user processor, a service provider processor, a service processor and a settlement processor. The entry database, the user database, the service provider database, the service database and the settlement database are respectively bidirectionally connected to the entry processor, the user processor, the service provider processor, the service processor and the settlement processor. By means of the multi-stage entry concatenation based network platform framework, the data storage is not confusing, which facilitates the transferring of various data and the binding of user data and entry data, and facilitates the transferring of the entry data, and cascading data between entries is clear, which facilitates the transferring of the other cascading entry data.

Description

Network platform framework based on multi-level portal cascading

Technical field

The invention relates to the field of network databases, in particular to a network platform framework based on multi-level portal cascade.

Background technique

At present, consumers are more willing to spend on the network platform, which makes the number of online platforms such as e-commerce and micro-business grow rapidly. Therefore, for a network platform, the quality and price of the items sold on the platform are not affecting one. The most important factor of the network platform. Nowadays, the most important thing for a network platform is its popularity. The higher the popularity of a network platform, the more consumers are willing to spend on this platform. In order to increase the visibility of the network platform, it is necessary to increase the promotion of the network platform. In order to ensure platform promotion, the platform can be promoted by means of multi-level portal promotion. In this way, it is necessary to pay attention to the cascading relationship between the portals. The traditional method generally adopts the entry level of each level of the entry data in the database. In the storage address, after the entry data is retrieved, the data of the upper-level entry is retrieved according to the storage address, and then the data of the upper-level entry is retrieved according to the data of the upper-level entry, and the process is repeated until the retrieval is performed. Level 1 entry data to the cascading relationship where the portal is located. This method of repeated retrieval not only increases the workload of the processor, but also increases the time for data acquisition.

Summary of the invention

To solve the above technical problem, the present invention provides a network platform framework based on a multi-level ingress cascading, where an entry identification data identifies an entry, and the ingress cascading relationship data represents a storage address of all entries of the cascading relationship in which the entry is located, and the entry identification data is The entry data of the associated entry is extracted, and the entry data of all the entries of the cascade relationship of the entry is extracted through the entry data of the entry. Saves processor time Between and workload.

The technical solutions are as follows:

A network platform framework based on multi-level portal cascading, the key lies in: including entry database, user database, service provider database, service database and settlement database, entry database, user database, service provider database, service database and settlement database respectively Including an ingress processor, a user processor, a service provider processor, a service processor, a settlement processor;

The entry database stores entry data a of each level of entry, and the entry data a includes entry identification data a1, entry account data a2, entry cascade data a3, and entry contribution ratio data a4;

User data b of each user is stored in the user database, and the user data b includes a user account b1, a user password b2, and entry identification data a1 at the time of registration;

The service provider database and the service database respectively store the service provider data c and the service data d, and the service provider data c includes a service provider account c1, a service provider password c3, a service provider account data c4, and a service provider contribution ratio data c2, and a service Data d is bound to the service provider data c;

The ingress processor is bidirectionally connected to the ingress database, the user processor, and the settlement processor, respectively, the user processor is bidirectionally connected to the user database and the service processor, respectively, the service provider processor and the The service provider database, the service database, and the settlement processor are bidirectionally connected, and the service processor is bidirectionally connected to the service database, the user processor, and the settlement processor, respectively, and the settlement processor is bidirectionally connected to the settlement database.

The five databases store different data, avoiding mixing different data in one database, causing data confusion and easy database management.

Further, the entry data a stored in the entry database further includes entry invitation code data a5, the entry processor acquires the entry invitation code data a5 and the application data e, and the entry processor retrieves the entry from the entry database The invitation code data a5 is matched with the obtained entry invitation code data a5, and the matching is unsuccessful to display the invitation code error. If the matching is successful, the application data e and the qualified condition data f are paired. If the comparison fails, the application fails to be displayed. If the comparison is successful, the entry data a is generated, and the entry data a is sent to the entry database for storage.

By matching the entry invitation code data a5, the entry cascade data a3 between the entry and the entry can be generated to avoid confusion of the cascade relationship between the entries.

Further, the user processor acquires the entry identification data a1 and the registration data g submitted by the user, and compares the registration data g with the registration condition data h stored in the user processor, and determines whether the registration data g is in compliance with the registration. The condition data h, which does not match the reply registration failure, is generated to the user, the user data b is generated, and the user data b is finally stored in the user database.

The user data b error can be avoided, and the user data b can be bound to the entry data a through the entry identification data a1, so that the later settlement processor can retrieve the entry data a.

Further, the entry identification data a1 includes a storage address of the entry in the entry database, and the entry cascade data a3 includes a storage address of all entries of the cascade in which the entry is located in the entry database, the entry processing Obtaining, by the settlement processor, an instruction j for retrieving the entry data a, the instruction j includes the entry identification data a1, and the entry processor retrieves the entry data a from the entry database according to the entry storage address, The ingress processor matches the entry identification data a1 in the ingress data a that is retrieved with the instruction j, and the matching failure display fails to be retrieved. If the matching succeeds, the ingress processor retrieves the level corresponding to the entry according to the ingress cascade data a3. The associated upper level entry data a _N , the ingress processor sends the retrieved entry data a and the entry data a _{N of the} upper level entry to generate an ingress packet t to the settlement processor.

The entry data a can be found through the entry identification data a1, and the storage address of all the entries of the cascading relationship of the entry can be found through the entry cascading data a3 in the entry data a, thereby facilitating the entry processor to retrieve the cascading of the entry at a time. The entry data a _N of the entry level of the relationship.

Further, the service provider processor obtains the service provider account c1 and the service provider password c3 submitted by the service provider, and retrieves the service provider password c3* matching the service provider account c1 from the service provider database. The submitted service provider password c3 is matched, and the comparison fails to display the account number and the password error. When the comparison is successful, the service provider processor obtains the service information m submitted by the service provider, generates the service data d according to the service information m, and stores the service data d. Go to the service sub-database bound to the service provider data in the service database.

The input service provider data c can be verified to prevent other people from entering the service database for operation, and each service sub-database is bound with the service provider data c, so that the later settlement processor can retrieve the service provider data c.

Further, the service processor acquires the service data d selected by the user, retrieves the service provider data c matching the service data d from the service provider database according to the service data d, and sends the service data d to the service data d. The associated service provider confirms, the service processor determines whether the service provider confirms the order information n, fails to reply to the user order if not received, and retrieves the user data b from the user database if received, according to the user data b And the service data d generates the order data p and sends it to the user for payment, and then determines whether the user receives the payment data k, if not, the payment fails, the order is cancelled; if the order is received, the order is completed, and the payment data k is sent. Give the service provider and settlement processor.

The service provider confirms the order data p, can avoid the error of the service data d on the order, and prevents the final settlement processor from picking up the wrong service provider data c.

Further, the settlement processor acquires the completed payment data k, and generates an instruction q for retrieving the service provider data c from the service provider database and an instruction r for retrieving the entry identification data a1 from the user database according to the completed payment data k. The instruction q and the instruction r are respectively sent to the service provider processor and the user processor;

After the settlement processor acquires the service provider data c and the entry identification data a1, generates an instruction j for extracting the entry data a from the entry database according to the entry identification data a1 and sends the instruction j to the entry processor;

After obtaining the ingress data packet t, the settlement processor extracts from the ingress data packet t the entry contribution ratio data a4 _N according to the entry contribution ratio data a4 and the upper level entry, the entry account data a2, and the upper entry account data a2 _N ;

Extracting data from the service provider service provider proportional contribution data service provider account data c2 and c4, the billing processor in conjunction with an inlet contribution ratio data a4, entry levels of contribution ratio data entry supervisor a4 _N, service providers and the contribution ratio data c2 The payment data k is generated to generate the contribution data s, and the report is sent to the bank, the service provider, and the portal in combination with the contribution data s and the service provider account data c4, the entry account data a2, and the entry account data a2 _{N of the} upper level entry.

The user data only includes the entry identification data a1 without including the entire entry data a, which reduces the data amount of the user data b. The entry identification data a1 can accurately find the entry data a, and the entry data is again retrieved according to the entry data a. The entry level a _N of the upper level of the cascading relationship reduces the workload and working time of the entry processor.

Further, the portal database is divided into a first-level sub-library storing all the first-level entry data, a second-level sub-library storing all the second-level entry data, and an N-level sub-library storing the N-level entry data.

The entry data a is stored in the corresponding sub-library to facilitate encoding of the storage address of the ingress data, reducing the data length of the ingress concatenated data a3, and facilitating retrieval of the ingress data a.

Advantageous Effects: With the network platform framework based on multi-level portal cascading of the invention, data storage is not confusing, and various data are conveniently retrieved, user data is bound to the portal data, and the entry data is easily retrieved, and the cascading data between the portals is facilitated. Clear and easy to retrieve other cascaded entry data.

DRAWINGS

Figure 1 is a block diagram showing the structure of the present invention;

2 is a flow chart of entry data generation in an entry database;

Figure 3 is a flow chart for extracting entry data from an entry database;

Figure 4 is a flow chart of service data generation in a service database;

Figure 5 is a flow chart of user data generation in a user database;

Figure 6 is a workflow diagram of the service processor;

Figure 7 is a flow chart for generating settlement data in the settlement database.

detailed description

The invention will now be further described with reference to the embodiments and the accompanying drawings.

As shown in Figure 1-7, a network platform framework based on multi-level portal cascading includes an entry database, a user database, a service provider database, a service database, and a settlement database, an entry database, a user database, a service provider database, and a service database. And the settlement database includes an entry processor, a user processor, a service provider processor, a service processor, and a settlement processor, respectively.

The ingress processor is bidirectionally connected to the ingress database, the user processor, and the settlement processor, respectively, the user processor is bidirectionally connected to the user database and the service processor, respectively, the service provider processor and the The service provider database, the service database, and the settlement processor are bidirectionally connected, and the service processor is bidirectionally coupled to the service database, the user processor, and the settlement processor, respectively.

The portal database is divided into a first-level sub-library storing all the first-level entry data, a second-level sub-library storing all the second-level entry data, and an N-level sub-library storing the N-level entry data.

The entry database stores entry data a of each level of entry, and the entry data a includes entry identification data a1, entry account data a2, entry concatenation data a3, and entry contribution ratio data a4.

The entry data a stored in the entry database further includes entry invitation code data a5, the entry processor acquires the entry invitation code data a5 and the application data e submitted by the entry applicant, and the entry processor retrieves from the entry database The entry invitation code data a5 is matched with the obtained entry invitation code data a5. If the match is unsuccessful, the entry applicant's invitation code is erroneously matched. If the match is successful, the application data e is compared with the qualified condition data f, and the unsuccessful reply entry application is compared. If the application fails, the entry data a is generated and the entry data a is sent to the entry database for storage. The entry applicant includes the service provider and the user.

The user database b stores user data b of each user, and the user data b includes a user account b1, a user password b2, and entry identification data a1 at the time of registration.

The user processor acquires the entry identification data a1 and the registration data g submitted by the user, and registers The data g is compared with the registration condition data h stored in the user processor, and it is determined whether the registration data g meets the registration condition data h, does not meet the reply registration failure to the user, the generation generates the user data b, and finally stores the user data b. In the user database.

The settlement data of the order for each payment is stored in the settlement database.

The service provider database and the service database respectively store the service provider data c and the service data d, and the service provider data c includes a service provider account c1, a service provider password c3, a service provider account data c4, and a service provider contribution ratio data c2, and a service The data d is bound to the service provider data c.

The service provider processor obtains the service provider account c1 and the service provider password c3 submitted by the service provider, and retrieves the service provider password c3* matching the service provider account c1 from the service provider database and the submitted service provider password c3. Matching, the comparison fails to display the account number and the password error. When the comparison is successful, the service provider processor obtains the service information m submitted by the service provider, generates the service data d according to the service information m, and stores the service data d in the service database. In the service subdatabase bound to the service provider.

The user processor obtains the user account b1 and the user password b2 submitted by the user, and retrieves the user password b2* matching the user account b1 from the user database and matches the obtained user password b2. If the matching succeeds, the login platform selects the service data. d.

The service processor acquires the service data d selected by the user, retrieves the service provider data c matching the service data d from the service provider database according to the service data d, and transmits the service data d to the service provider associated with the service data d Confirming, the service processor determines whether the service provider confirms the order information n, fails to reply to the user's order if not received, and retrieves the user data b from the user database if received, according to the user data b and the service data d The generated order data p is sent to the user for payment, and then it is determined whether the user has received the payment data k. If not received, the payment failure is displayed, the order is cancelled; if received, the order is completed, and the payment data k is generated and sent to the service provider and The settlement processor, the payment data k, includes the service data d and the user account b1.

The settlement processor acquires the completed payment data k, and the completed payment data includes the total contribution data k1. Service data d and user data b. Generating an instruction q for retrieving the service provider data c from the service provider database and an instruction r for retrieving the entry identification data a1 from the user database according to the service data d and the user data b in the completed payment data k, respectively, and respectively respectively, the instruction q and the instruction r are respectively Sent to the service provider processor and user processor.

The service provider processor finds the service provider data c bound to the service sub-database stored by the service data d based on the service data d. The user processor sends the entry identification data a1 included in the user data b matched by the user account b1 from the user database to the settlement processor.

After the settlement processor acquires the service provider data c and the entry identification data a1, an instruction j for extracting the entry data a from the entry database is generated according to the entry identification data a1 and the instruction j is sent to the entry processor.

The entry identification data a1 includes a storage address of the entry in the entry database, the entry cascade data a3 includes a storage address of all entries of the cascade in which the entry is located in the entry database, and the entry processor obtains the An instruction j sent by the settlement processor to retrieve the entry data a, the instruction j containing the entry identification data a1, the entry processor retrieving the entry data a from the entry database according to the entry storage address, the entry processor The entry identification data a1 in the retrieved entry data a is matched with the instruction j, and the matching failure display fails to be retrieved. If the matching succeeds, the ingress processor retrieves the entry data of all the upper-level entries of the entry according to the ingress cascade data a3. a _N , the ingress processor combines the retrieved ingress data a with the ingress entry data a _{N of the} ingress to generate an ingress packet t to be sent to the settlement processor.

After acquiring the ingress packet t, the settlement processor extracts the entry contribution ratio data a4 and the entry contribution ratio data a4 _{N of} its upper level entries from the ingress packet t. The service provider contribution ratio data c2 and the service provider account data c4 are extracted from the service provider data.

The settlement processor generates the contribution data s in combination with the total contribution data k1, the entry contribution ratio data a4 _N , a4 , and the service provider contribution ratio data c2.

The contribution data s includes the service provider contribution data y and the entry contribution degree data z, where y = k1 * c2, and the entry contribution degree data z includes entry contribution degree data z _N , z _N = k1 * a4 _N of the entry of each level.

The report is sent to the bank, the service provider and the portal, and the settlement database storage in combination with the contribution data s and the service provider account data c4, the entry account data a2, and the entry account data a2 _{N of the} upper level entry.

It should be noted that the above description is merely a preferred embodiment of the present invention, and those skilled in the art can make various similarities without departing from the spirit and scope of the present invention. It is intended that such variations fall within the scope of the invention.

Claims

A network platform framework based on multi-level portal cascading, comprising: an entry database, a user database, a service provider database, a service database, and a settlement database, an entry database, a user database, a service provider database, a service database, and a settlement database respectively Including an ingress processor, a user processor, a service provider processor, a service processor, a settlement processor;

The entry database stores entry data a of each level of entry, and the entry data a includes entry identification data a1, entry account data a2, entry cascade data a3, and entry contribution ratio data a4;

User data b of each user is stored in the user database, and the user data b includes a user account b1, a user password b2, and entry identification data a1 at the time of registration;

The settlement database stores settlement data of each order for completing the payment;

The service provider database and the service database respectively store the service provider data c and the service data d, and the service provider data c includes a service provider account c1, a service provider password c3, a service provider account data c4, and a service provider contribution ratio data c2, and a service Data d is bound to the service provider data c;

The ingress processor is bidirectionally connected to the ingress database, the user processor, and the settlement processor, respectively, the user processor is bidirectionally connected to the user database and the service processor, respectively, the service provider processor and the The service provider database, the service database, and the settlement processor are bidirectionally connected, and the service processor is bidirectionally coupled to the service database, the user processor, and the settlement processor, respectively.
The network platform framework of the multi-level portal cascade according to claim 1, wherein the portal data a stored in the portal database further includes entry invitation code data a5, and the portal processor obtains an entry submitted by an applicant. The invitation code data a5 and the application data e, the entry processor retrieves the portal invitation code data a5 from the portal database and matches the acquired portal invitation code data a5, and the matching does not successfully display the invitation code error, and the matching is successful. The data e is compared with the qualification condition data f, The comparison fails to display the application failure. If the comparison is successful, the entry data a is generated, and the entry data a is sent to the entry database for storage.
The network platform framework of the multi-level portal cascade according to claim 1, wherein the user processor acquires the entry identification data a1 and the registration data g submitted by the user, and registers the registration data g with the user processor. The registration condition data h stored in the comparison is compared, it is determined whether the registration data g meets the registration condition data h, the registration failure is not met for the user, the user data b is generated, and the user data b is finally stored in the user database.
The network platform framework of the multi-level portal cascade according to claim 1, wherein the entry identification data a1 includes a storage address of the entry in the entry database, and the entry cascade data a3 includes the entry The storage address of all the entries of the cascade in the entry database;

The entry processor acquires an instruction j sent by the settlement processor to retrieve the entry data a, the instruction j includes the entry identification data a1, and the entry processor retrieves the entry data from the entry database according to the entry storage address a, the ingress processor matches the entry identification data a1 in the retrieved entry data a with the instruction j, and the matching failure display fails to be retrieved. If the matching succeeds, the ingress processor retrieves the data according to the ingress cascade data a3. The ingress cascades the upper level entry data a N , and the ingress processor sends the retrieved ingress data a and the upper level entry data a N to generate an ingress packet t to the settlement processor.
The network platform framework of the multi-level portal cascade according to claim 1, wherein the service provider processor obtains the service provider account c1 and the service provider password c3 submitted by the service provider, and adjusts the database from the service provider database. The service provider password c3* matching the service provider account c1 is matched with the submitted service provider password c3, and the comparison fails to display the account number and the password error. If the comparison is successful, the service provider processor obtains the service information m submitted by the service provider, according to The service information m generates service data d, and stores the service data d in a service sub-database bound to the service provider in the service database.
The network platform framework of the multi-level portal cascade according to claim 1, wherein the service processor obtains the service data d selected by the user, and the service data d is from the service provider database. Retrieving the service provider data c matching the service data d, and transmitting the service data d to the service provider associated with the service data d for confirmation, the service processor determines whether the service provider confirms the order information n, if not received If yes, the user's order fails to be answered. If received, the user data b is retrieved from the user database, and the order data p is generated according to the user data b and the service data d, and is sent to the user for payment, and then it is determined whether the user completes the payment data k. If it is not received, it indicates that the payment has failed, the order is cancelled; if it is received, the order is completed, and the generated payment data k is sent to the service provider and the settlement processor.
The network platform framework of the multi-level portal cascade according to claim 6, wherein the settlement processor acquires the completed payment data k, and generates the service provider data c from the service provider database according to the completed payment data k. An instruction q and an instruction r for extracting the entry identification data a1 from the user database and transmitting the instruction q and the instruction r to the service provider processor and the user processor, respectively;

After the settlement processor acquires the service provider data c and the entry identification data a1, generates an instruction j for extracting the entry data a from the entry database according to the entry identification data a1 and sends the instruction j to the entry processor;

After obtaining the ingress data packet t, the settlement processor extracts from the ingress data packet t the entry contribution ratio data a4 N according to the entry contribution ratio data a4 and the upper level entry, the entry account data a2, and the upper entry account data a2 N ;

Extracting data from the service provider service provider proportional contribution data service provider account data c2 and c4, the billing processor in conjunction with an inlet contribution ratio data a4, entry levels of contribution ratio data entry supervisor a4 N, service providers and the contribution ratio data c2 The payment data k is generated to generate the contribution data s, and the report is sent to the bank, the service provider, and the portal in combination with the contribution data s and the service provider account data c4, the entry account data a2, and the entry account data a2 N of the upper level entry.
The network platform framework of the multi-level portal cascade according to claim 1, wherein the portal database is divided into a first-level sub-library storing all the first-level entry data, and a second-level sub-library storing all the secondary entry data. ,,,, an N-level sub-library that stores N-level entry data.