WO2018033020A1 - Structure de plate-forme de réseau basée sur une concaténation d'entrée multi-étage - Google Patents

Structure de plate-forme de réseau basée sur une concaténation d'entrée multi-étage Download PDF

Info

Publication number
WO2018033020A1
WO2018033020A1 PCT/CN2017/096978 CN2017096978W WO2018033020A1 WO 2018033020 A1 WO2018033020 A1 WO 2018033020A1 CN 2017096978 W CN2017096978 W CN 2017096978W WO 2018033020 A1 WO2018033020 A1 WO 2018033020A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
entry
database
processor
service provider
Prior art date
Application number
PCT/CN2017/096978
Other languages
English (en)
Chinese (zh)
Inventor
徐子明
Original Assignee
重庆兴韦度科技有限公司
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 重庆兴韦度科技有限公司 filed Critical 重庆兴韦度科技有限公司
Publication of WO2018033020A1 publication Critical patent/WO2018033020A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders

Definitions

  • the invention relates to the field of network databases, in particular to a network platform framework based on multi-level portal cascade.
  • 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.
  • 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.
  • 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.
  • 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.
  • the entry cascade data a3 between the entry and the entry can be generated to avoid confusion of the cascade relationship between the entries.
  • 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.
  • 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
  • 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 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.
  • 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.
  • 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
  • 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.
  • the service provider and settlement 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
  • 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.
  • 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;
  • the settlement 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;
  • the settlement 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 ;
  • 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.
  • 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.
  • Figure 1 is a block diagram showing the structure of the present invention
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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
  • 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.
  • 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 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne une structure de plate-forme de réseau basé sur une concaténation d'entrée multi-étage, comprenant une base de données d'entrées, une base de données d'utilisateurs, une base de données de fournisseurs de services, une base de données de services et une base de données de règlements, la base de données d'entrées, la base de données d'utilisateurs, la base de données de fournisseurs de services, la base de données de services et la base de données de règlements comprenant respectivement un processeur d'entrée, un processeur d'utilisateur, un processeur de fournisseur de services, un processeur de service et un processeur de règlement. La base de données d'entrées, la base de données d'utilisateurs, la base de données de fournisseurs de services, la base de données de services et la base de données de règlement sont respectivement reliées de manière bidirectionnelle au processeur d'entrée, au processeur d'utilisateur, au processeur de fournisseur de service, au processeur de service et au processeur de règlement. Au moyen de la structure de plate-forme de réseau basée sur une concaténation d'entrée multi-étage, la mémoire de données n'est pas embrouillée, ce qui facilite le transfert de diverses données et la liaison de données d'utilisateur et de données d'entrée et facilite le transfert des données d'entrée et des données en cascade entre des entrées sont claires, ce qui facilite le transfert des autres données d'entrée en cascade.
PCT/CN2017/096978 2016-08-16 2017-08-11 Structure de plate-forme de réseau basée sur une concaténation d'entrée multi-étage WO2018033020A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610674751.0A CN106326383B (zh) 2016-08-16 2016-08-16 基于多级入口级联的网络平台框架
CN201610674751.0 2016-08-16

Publications (1)

Publication Number Publication Date
WO2018033020A1 true WO2018033020A1 (fr) 2018-02-22

Family

ID=57740754

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/096978 WO2018033020A1 (fr) 2016-08-16 2017-08-11 Structure de plate-forme de réseau basée sur une concaténation d'entrée multi-étage

Country Status (2)

Country Link
CN (1) CN106326383B (fr)
WO (1) WO2018033020A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106326383B (zh) * 2016-08-16 2019-05-24 重庆翼耀科技咨询有限公司 基于多级入口级联的网络平台框架
CN110445812B (zh) * 2019-07-29 2022-03-11 湖南工业大学 一种基于个人信息数据库的通讯方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1407473A (zh) * 2001-08-13 2003-04-02 通用电气公司 启动服务入口的自动控制模块
CN103810619A (zh) * 2014-02-13 2014-05-21 陈炳福 基于电子平台的返利方法及其系统
CN105719171A (zh) * 2016-01-19 2016-06-29 南京图牛商城有限公司 一种用于电子商务的关联管理系统及方法
CN106326383A (zh) * 2016-08-16 2017-01-11 重庆兴韦度科技有限公司 基于多级入口级联的网络平台框架

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8046557B2 (en) * 2005-12-05 2011-10-25 Intelitrac Inc. Apparatus and method for on-demand in-memory database management platform
CN101673388A (zh) * 2009-09-27 2010-03-17 蓝劲松 利用区域数据库保存网上交易信息的方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1407473A (zh) * 2001-08-13 2003-04-02 通用电气公司 启动服务入口的自动控制模块
CN103810619A (zh) * 2014-02-13 2014-05-21 陈炳福 基于电子平台的返利方法及其系统
CN105719171A (zh) * 2016-01-19 2016-06-29 南京图牛商城有限公司 一种用于电子商务的关联管理系统及方法
CN106326383A (zh) * 2016-08-16 2017-01-11 重庆兴韦度科技有限公司 基于多级入口级联的网络平台框架

Also Published As

Publication number Publication date
CN106326383B (zh) 2019-05-24
CN106326383A (zh) 2017-01-11

Similar Documents

Publication Publication Date Title
US9904916B2 (en) Incremental login and authentication to user portal without username/password
US9785989B2 (en) Determining a characteristic group
US8751419B2 (en) Shipping system and method with taxonomic tariff harmonization
US10176512B2 (en) Processing electronic data across network devices
US10546336B2 (en) Search device, search method, program, and storage medium
JP2019117653A (ja) トランザクションデータをモバイルデバイスに提供するシステムおよび方法
US9311644B2 (en) Item listing categorization system
US20210312557A1 (en) Automatically Generating Personal Articles Insurance Data Based Upon Digital Images
WO2018033020A1 (fr) Structure de plate-forme de réseau basée sur une concaténation d'entrée multi-étage
US20140337190A1 (en) Purchase Order Matching
Perron et al. Testing for flexible nonlinear trends with an integrated or stationary noise component
CN109472567B (zh) 数字货币处理方法、装置、计算机设备及存储介质
US9626356B2 (en) System support for evaluation consistency
CN112990868A (zh) 车辆保险自动赔付方法、系统、设备及存储介质
US20150081728A1 (en) Automatic format conversion
WO2018033021A1 (fr) Plateforme de réseau basée sur une concaténation d'entrée multi-étage et son procédé d'interaction de données
CN106156149B (zh) 一种数据转移方法及装置
US10795934B2 (en) Automatically optimizing business process platforms
US20150206158A1 (en) System and method for spend analysis of the service category
CN112686732B (zh) 异常地址数据识别方法、装置、设备、介质
US10007398B2 (en) Integrated supplier information tool
US20130300562A1 (en) Generating delivery notification
WO2018103485A1 (fr) Cadre de plateforme de réseau basé sur une topologie arborescente et procédé d'échange de données associé
CN110309235B (zh) 一种数据处理方法、装置、设备及介质
CN111488343A (zh) 基于业务数据区块链的电商数据上链方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17840994

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17840994

Country of ref document: EP

Kind code of ref document: A1