WO2019153483A1 - 手续费确定方法、装置、终端设备及介质 - Google Patents

手续费确定方法、装置、终端设备及介质 Download PDF

Info

Publication number
WO2019153483A1
WO2019153483A1 PCT/CN2018/082613 CN2018082613W WO2019153483A1 WO 2019153483 A1 WO2019153483 A1 WO 2019153483A1 CN 2018082613 W CN2018082613 W CN 2018082613W WO 2019153483 A1 WO2019153483 A1 WO 2019153483A1
Authority
WO
WIPO (PCT)
Prior art keywords
fee
business
stored
proportion
service
Prior art date
Application number
PCT/CN2018/082613
Other languages
English (en)
French (fr)
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 WO2019153483A1 publication Critical patent/WO2019153483A1/zh

Links

Classifications

    • 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/04—Billing or invoicing
    • 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/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2282—Tablespace storage structures; Management thereof
    • 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/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • 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/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting

Definitions

  • the present application belongs to the field of information processing technology, and in particular, to a method, device, terminal device and medium for determining a fee.
  • the calculation of the existing fee depends on the database, that is, the calculation fee for obtaining relevant data from the database is required.
  • the insurance handling fee it is necessary to obtain all the premium data of the previous trading day from the three system databases of contract, claim and preservation, including online and offline insurance and online and offline surrender data, and then according to the system.
  • the proportion of the fee set calculate the handling fee, and then write the corresponding fee data to the financial system for the financial system settlement fee.
  • the embodiment of the present application provides a method, a device, a terminal device, and a medium for determining a fee, so as to solve the problem that the calculation of the existing fee depends on the database, so that the calculation period of the fee is long, and the calculation efficiency of the fee is decreased.
  • a first aspect of the embodiments of the present application provides a method for determining a fee, including:
  • each form contains the salesperson, business source, business type, business order number and business expenses;
  • the commission for each group of forms after grouping is calculated in parallel according to the business order number, service fee, and commission ratio of the form stored in the HIVE.
  • a second aspect of the embodiments of the present application provides a fee determining apparatus, including:
  • the form obtaining unit is configured to obtain all the forms in the target system preset time period, and each form includes a salesperson, a service source, a service type, a business order number, and a service fee;
  • the fee proportion inquiry unit is configured to query the proportion of the fee corresponding to each form from the pre-stored fee scale table according to the salesperson, the service source and the service type of each form obtained;
  • a data storage unit configured to store the business order number and the business fee of each form obtained, and the proportion of the handling fee corresponding to each form that is queried, into the HIVE;
  • a form grouping unit configured to determine the size of each form obtained, and group all the obtained forms according to the determined size of each form
  • the fee calculation unit is configured to calculate the commission of each group of forms after the grouping according to the business order number, the service fee, and the commission fee ratio of the form stored in the HIVE.
  • a third aspect of the embodiments of the present application provides a fee determination terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor The following steps are implemented when the computer readable instructions are executed:
  • each form contains the salesperson, business source, business type, business order number and business expenses;
  • the commission for each group of forms after grouping is calculated in parallel according to the business order number, service fee, and commission ratio of the form stored in the HIVE.
  • a fourth aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions that, when executed by at least one processor, implement the following steps:
  • each form contains the salesperson, business source, business type, business order number and business expenses;
  • the commission for each group of forms after grouping is calculated in parallel according to the business order number, service fee, and commission ratio of the form stored in the HIVE.
  • the relevant data of the calculation fee is stored in the HIVE, and the prior art is solved.
  • the database runs slower and the database performance is reduced.
  • the parallel fee is used to calculate the commission, reduce the calculation time of the fee, improve the calculation efficiency of the fee, and meet the existing business needs.
  • FIG. 1 is a schematic flow chart of a method for determining a fee according to an embodiment of the present application
  • FIG. 2 is a schematic flow chart of a method for determining a fee according to another embodiment of the present application.
  • FIG. 3 is a schematic flow chart of a method for determining a fee according to still another embodiment of the present application.
  • FIG. 4 is a schematic flow chart of a method for determining a fee according to another embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for determining a fee according to another embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a fee determination procedure provided by an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a fee determination terminal device according to an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a method for determining a fee according to an embodiment of the present application.
  • an angle trigger of a terminal is used as an example.
  • the terminal may be a smart phone or a tablet. Wait for mobile terminals.
  • the processing of the terminal may include the following steps:
  • S101 Acquire all forms in the preset time period of the target system, where each form includes a salesperson, a service source, a service type, a business order number, and a service fee.
  • the target system may be a system that specifies a calculation fee, such as a contract system, a claims system, a security system, etc.
  • the preset time period may also be pre-specified, such as the previous transaction day, the previous hour, and the like.
  • the target system and the preset time period can be specified according to actual needs.
  • the system modification instruction and the time segment modification instruction can also be received, the specified target system is modified according to the system modification instruction, and the specified preset is modified according to the time period modification instruction. Time period until the requirements are met.
  • a form is a data sheet that contains a variety of collected data, such as a policy. After obtaining all the forms in the preset time period of the target system, it is possible to first detect whether all the obtained forms contain preset keywords, and if all the forms include preset keywords, the following steps may be performed, if some The form does not contain a preset keyword, deletes the form that does not contain the preset keyword, and performs the next steps as the new acquired form.
  • the preset keyword is set according to the actual situation, so that the obtained form is detected by setting the preset keyword, and the passed form can be executed to perform the subsequent steps to ensure that the form in the subsequent step conforms to the actual situation.
  • S102 Query the proportion of the fee corresponding to each form from the pre-stored fee scale table according to the obtained salesperson, service source, and service type of each form.
  • the pre-stored fee scale table may be generated by acquiring a plurality of forms of salespersons, service sources, and service types, and determining each one based on the retrieved form salesperson, service source, and service type based on the RETE algorithm. The proportion of the fee for the form, and the scale of the fee is generated.
  • the query failure information may be generated, and in order to facilitate the user to understand the situation, the specific fee proportions of the forms may not be displayed. Then, the fee generation ratio generating process can be given, and the fee fee proportion generating interface is entered, and the user is prompted to provide the corresponding data generating fee proportion according to the above-mentioned fee proportional generation process.
  • HIVE is a data warehouse tool based on Hadoop, which can map structured data files into a database table and provide structured query language query function, which can convert structured statements into MapReduce tasks.
  • the business order number and the business fee of each form to be obtained, and the proportion of the handling fee corresponding to each form that is queried, may be included in the HIVE: first, according to the business order number and the business expense of each form obtained. And the proportion of the fee corresponding to each form that is queried, establish the correspondence between the business order number, the business fee and the commission fee ratio of each form, and store the corresponding relationship of each form in the form of HIVE, which is to calculate the handling fee.
  • the related data is stored in HIVE, which solves the problem of database performance consumption caused by the database computing fee in the prior art, and improves the calculation speed of the fee.
  • S104 Determine the size of each form acquired, and group all the obtained forms according to the determined size of each form.
  • the determined form size may be recorded, and the obtained forms are sorted according to the size of the form, so as to facilitate subsequent grouping of the forms.
  • the above grouping all the obtained forms according to the determined size of each form may include: firstly, according to each form containing the salesperson, the service source, the service type, the business order number, or the business expense, the first time is obtained for all the forms obtained. Grouping, and then determining the size of each form obtained, and obtaining the size of each group after the first grouping according to the determined size of each form, according to the upper limit of the preset group size and the size of each group after the first grouping. Perform the second grouping.
  • S105 Calculate the processing fee of each group form after grouping according to the service order number, the service fee, and the commission fee ratio of the form stored in the HIVE.
  • the commission fee is calculated by the ratio of the service fee and the fee, that is, the commission fee corresponding to each service ticket number is multiplied by the service fee corresponding to the service ticket number, and the commission corresponding to the service ticket number is calculated.
  • the processing fee for each group of forms after grouping is calculated in parallel, the calculation speed of the fee is increased, and the calculation cycle of the fee is shortened.
  • the method for determining the fee in the embodiment of the present application is to calculate the commission of the fee by storing all the forms in the preset time period of the target system and the commission fee for each form in the query.
  • the data exists in HIVE, which solves the problem that the database running speed is slowed down and the database performance is reduced based on the database computing fee.
  • the processing fee is calculated in parallel, the calculation time of the fee is reduced, and the calculation efficiency of the fee is improved. Meet existing business needs.
  • FIG. 2 is a schematic flowchart of determining a fee according to another embodiment of the present application.
  • the difference between this embodiment and the above embodiment is S203 ⁇ S207, where S201 ⁇ S202 are the same as S101 ⁇ S102 in the previous embodiment, and S208 ⁇ S209 are the same as S104 ⁇ S105 in the previous embodiment.
  • S101 ⁇ S102 and S104 ⁇ S105 in the example are not described here.
  • the fee determination in this embodiment may further include:
  • S203 Determine, according to the obtained mediation and pre-stored mediation fee scale table in each form, the proportion of the intermediary fee corresponding to each form, wherein each form obtained includes an intermediary.
  • the proportion of the fee corresponding to the intermediary of each form is further obtained, and the form fee calculation requirement in various application scenarios is satisfied. .
  • S205 If it is detected that there are multiple mediations in the target form, determining, according to the correspondence between the pre-stored mediation and the fee split ratio, determining a fee split ratio corresponding to each mediation in the target form, the target
  • the form is any form in each form that gets.
  • the target form is any one of the obtained forms. If there are multiple mediations in the form in the acquired form, each form having multiple mediations needs to be described in step S205 above.
  • the target form determines the split ratio for each agent in each form. If it is detected that there are multiple mediations in the target form, for example, there are mediation 0, mediation 1, and mediation 2, according to the correspondence between the pre-stored mediation and the fee split ratio, the formalities corresponding to each mediation in the target form are determined.
  • the ratio of the fee splitting for example, according to the correspondence between the pre-stored intermediary and the split ratio of the fee, it is determined that the split ratio corresponding to the intermediary 0 is 1/3, and the split ratio corresponding to the intermediary 1 is 1/6, and the split ratio corresponding to the intermediary 2 is The ratio is 1/2. According to the correspondence between the above-mentioned intermediary and the split ratio, the ratio of the intermediary fee is further split.
  • S206 Split the proportion of the intermediary fee corresponding to the target form according to the fee split ratio corresponding to each agent in the target form, and determine the intermediary fee corresponding to each agent in the target form. proportion.
  • S207 Deposit the business order number and the business fee of each form obtained, and the proportion of the handling fee corresponding to each form that is queried, and the ratio of the intermediary handling fee corresponding to each intermediary in the target form to the HIVE.
  • FIG. 3 is a schematic flowchart of a method for determining a fee according to another embodiment of the present application.
  • the determining the size of each form acquired, and grouping all the acquired forms according to the determined size of each form may include S304.
  • S301 ⁇ S303 and S101 ⁇ in the previous embodiment S103 is the same, S305 is the same as S105 in the previous embodiment.
  • S304 may include S3041 ⁇ S3042:
  • S3041 Determine the size of each form obtained, obtain the sum of the sizes of all the obtained forms according to the determined size of each form, and check whether the sum of the sizes of all the obtained forms exceeds the upper limit of the preset group size.
  • the preset packet size upper limit may be set according to actual conditions, for example, the preset packet size upper limit is 100. All the forms obtained are Form 1, Form 2, Form 3 and Form 4. The size of Form 1 is 50, the size of Form 2 is 60, the size of Form 3 is 40, and the size of Form 4 is 50. The sum of the sizes of all the obtained forms is 200, exceeds the preset packet size upper limit of 100, and groups all the obtained forms according to the preset packet size upper limit, so that the size of each group after the grouping does not exceed the preset group size upper limit, that is, the form 1 and the form 4 are divided. For a group, Form 2 and Form 3 are grouped together. After the grouping is completed, the handling fee of each group of forms after grouping is calculated in parallel, and the calculation of the handling fee is completed quickly, thereby improving the calculation efficiency.
  • FIG. 4 is a schematic flowchart of determining a fee according to another embodiment of the present application.
  • the difference between the foregoing embodiment and the embodiment is S403 ⁇ S405, where S401 ⁇ S402 are the same as S101 ⁇ S102 in the previous embodiment.
  • S401 ⁇ S402 are the same as S101 ⁇ S102 in the previous embodiment.
  • the fee determination in this embodiment may further include:
  • S404 Determine the size of each form acquired, and group all the obtained forms according to the determined size of each form.
  • S405 Extract the key value pairs from the HIVE, and pass each key value pair as a parameter to the map function to calculate the processing fee of each group form after the grouping.
  • the key value pair is extracted from HIVE (the business order number is key, the fee ratio and the business fee are used as values), and each key value pair is passed as a parameter to the map function, and the map function calculates the group form of each group in parallel.
  • the handling fee is calculated by the ratio of the operating expenses and the handling fee, that is, the commission fee corresponding to each business order number is multiplied by the business expense corresponding to the business order number, and the handling fee corresponding to the business order number is calculated.
  • the calculated commission can also be cached, and the cached fee is periodically written into HIVE.
  • the manner in which the cached fee is periodically written into the HIVE is as follows: the service order number of each form is used as the key, and the corresponding handling fee for each form is a value, which is periodically written into the HIVE. After the above-mentioned cached fee is periodically written into HIVE, the data can also be imported from the HIVE into the relational database for subsequent financial settlement.
  • the map function is used to calculate the commission in parallel and reduce the handling fee. Calculate the time and increase the calculation efficiency of the fee.
  • FIG. 5 is a schematic flowchart of a method for determining a fee according to another embodiment of the present application.
  • the difference between the embodiment corresponding to FIG. 1 is that: according to the salesperson, the service source, and the service type in each form obtained, the proportion of the fee corresponding to each form in the pre-stored fee scale table may include S502.
  • S501 is the same as S101 in the previous embodiment, S503 ⁇ S505 and S103 ⁇ in the previous embodiment.
  • S502 may include S5021 ⁇ S5023:
  • S5021 Determine a proportion of the salesman fee corresponding to each form according to the obtained salesperson and the pre-stored salesman fee scale table in each form, wherein the pre-stored fee scale table includes pre-stored salesman procedures Fee scale table, business source fee scale table and business type fee scale.
  • S5022 Determine the proportion of the service source fee corresponding to each form according to the obtained service source in each form and the pre-stored service source fee scale table.
  • S5023 Determine the proportion of the service type corresponding to each form according to the type of business in each form and the pre-stored service type fee scale table.
  • the proportion of the fee corresponding to each of the above forms includes the ratio of the salesman's fee, the proportion of the service source fee, and the proportion of the service type fee. According to the pre-stored fee scale, the salesperson and the source of the service in each form are determined. The proportion of the handling fee corresponding to the type of business ensures that the subsequent processing is carried out normally, and the actual handling fee calculation requirements are met, which is suitable for practical application.
  • FIG. 6 is a schematic diagram showing the operating environment of the fee determination program provided by the embodiment of the present application. For the convenience of explanation, only the parts related to the present embodiment are shown.
  • the fee determination program 600 is installed and operated in the terminal device 60.
  • the terminal device 60 can be a mobile terminal, a palmtop computer, a server, or the like.
  • the terminal device 60 can include, but is not limited to, a memory 601, a processor 602, and a display 603.
  • Figure 6 shows only terminal device 60 having components 601-603, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
  • the memory 601 may be an internal storage unit of the terminal device 60, such as a hard disk or memory of the terminal device 60, in some embodiments.
  • the memory 601 may also be an external storage device of the terminal device 60 in other embodiments, such as a plug-in hard disk equipped on the terminal device 60, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, flash card, etc.
  • SMC smart memory card
  • SD Secure Digital
  • flash card etc.
  • the memory 601 may also include both an internal storage unit of the terminal device 60 and an external storage device.
  • the memory 601 is configured to store application software and various types of data installed in the terminal device 60, such as program codes of the fee determination program 600, and the like.
  • the memory 601 can also be used to temporarily store data that has been output or is about to be output.
  • the processor 602 can be a central processor (Central) in some embodiments A processing unit (CPU), a microprocessor or other data processing chip for running program code or processing data stored in the memory 601, for example, executing the fee determination program 600 and the like.
  • Central central processor
  • CPU central processing unit
  • microprocessor microprocessor or other data processing chip for running program code or processing data stored in the memory 601, for example, executing the fee determination program 600 and the like.
  • the display 603 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an Organic Light-Emitting Diode (OLED) touch device or the like in some embodiments.
  • the display 603 is used to display information processed in the terminal device 60 and a user interface for displaying visualizations, such as an application menu interface, an application icon interface, and the like.
  • the components 601-603 of the terminal device 60 communicate with one another via a system bus.
  • FIG. 7 is a functional block diagram of the fee determination program 600 provided by the embodiment of the present application.
  • the fee determination program 600 may be divided into one or more modules, the one or more modules being stored in the memory 601 and being processed by one or more processors (this An embodiment is performed by the processor 602) to complete the application.
  • the fee determination program 600 may be divided into a form acquisition unit 701, a fee ratio inquiry unit 702, a data storage unit 703, a form grouping unit 704, and a fee calculation unit 705.
  • a unit referred to in the present application refers to a series of computer readable instruction instruction segments capable of performing a specific function, and is more suitable than the program to describe the execution process of the fee determination program 600 in the terminal device 60.
  • the following description will specifically describe the functions of the modules 701-705.
  • the form obtaining unit 701 is configured to acquire all forms in the target system preset time period, and each form includes a salesperson, a service source, a service type, a service order number, and a service fee.
  • the fee ratio inquiry unit 702 is configured to query the proportion of the fee corresponding to each form from the pre-stored fee scale table according to the obtained salesperson, service source, and service type of each form.
  • the data storage unit 703 is configured to store the business order number and the business fee of each form obtained, and the commission fee ratio corresponding to each form that is queried, into the HIVE.
  • the form grouping unit 704 is configured to determine the size of each form acquired, and group all the acquired forms according to the determined size of each form.
  • the fee calculation unit 705 is configured to calculate the commission of each group of forms after the grouping according to the business order number, the service fee, and the commission fee ratio of the form stored in the HIVE.
  • each form obtained also contains an intermediary.
  • the commission determination program 600 can also be divided into a first intermediary commission ratio determination unit 706, an intermediary detection unit 707, a commission split ratio determination unit 708, and a second intermediary commission ratio determination unit 709.
  • the first intermediary fee ratio determining unit 706 is configured to determine the proportion of the intermediary fee corresponding to each form according to the obtained intermediary in each form and the pre-stored intermediary fee ratio table.
  • the mediation detecting unit 707 is configured to detect whether there are multiple mediations in each form.
  • the fee split ratio determining unit 708 is configured to: if it is detected that there are multiple mediations in the target form, determine, according to the correspondence between the pre-stored mediation and the fee split ratio, the corresponding media in the target form The fee split ratio, which is any form in each form obtained.
  • the second intermediary fee ratio determining unit 709 is configured to split the ratio of the intermediary fee corresponding to the target form according to the fee split ratio corresponding to each agent in the target form, and determine the target form.
  • the ratio of agency fees corresponding to each intermediary in the medium is further configured to: obtain the service order number and the service fee of each form, and the commission fee ratio corresponding to each form that is queried, and the intermediary procedure corresponding to each agent in the target form.
  • the fee ratio is stored in HIVE.
  • the form grouping unit 704 can also be divided into a form size review unit 7041 and a form processing unit 7042.
  • the form size review unit 7041 is configured to determine the size of each form obtained, obtain the sum of the sizes of all the obtained forms according to the determined size of each form, and check whether the sum of the sizes of all the obtained forms exceeds the preset group size.
  • Upper limit The form processing unit 7042 is configured to: if the sum of the sizes of all the obtained forms exceeds the upper limit of the preset group size, group all the obtained forms according to the upper limit of the preset group size, so that each group form after the grouping The size does not exceed the upper limit of the preset packet size.
  • the data storage unit 703 is further configured to use the acquired business unit number of each form as a key, and obtain the business expense and the fee ratio of each form obtained by the value, and obtain the business form of each form.
  • the number and the business fee, as well as the commission fee ratio corresponding to each form queried, are stored in the HIVE in the form of a key-value pair.
  • the fee calculation unit 705 is further configured to extract a key value pair from the HIVE, and pass each key value pair as a parameter to the map function to calculate the processing fee of each group form after the grouping.
  • the pre-stored fee scale includes a pre-stored commission fee scale, a service source fee scale, and a service type fee scale.
  • the commission ratio inquiry unit 702 can be divided into a salesman fee ratio determination unit 7021, a service source fee ratio determination unit 7022, and a service type fee ratio determination unit 7023.
  • the salesperson fee ratio determining unit 7021 is configured to determine a commission fee ratio corresponding to each form according to the obtained salesperson in each form and the pre-stored commission fee ratio table.
  • the service source fee proportion determining unit 7022 is configured to determine a service source fee ratio corresponding to each form according to the obtained service source in each form and the pre-stored service source fee scale table.
  • the service type fee ratio determining unit 7023 is configured to determine a service type fee ratio corresponding to each form according to the type of service in each form acquired and the pre-stored service type fee scale table.
  • each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed.
  • the module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.
  • Each functional unit and module in the embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit, and the integrated unit may be hardware.
  • Formal implementation can also be implemented in the form of software functional units.
  • the specific names of the respective functional units and modules are only for the purpose of facilitating mutual differentiation, and are not intended to limit the scope of protection of the present application.
  • For the specific working process of the unit and the module in the foregoing system reference may be made to the corresponding process in the foregoing method embodiment, and details are not described herein again.
  • the disclosed device/terminal device and method may be implemented in other manners.
  • the device/terminal device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units.
  • components may be combined or integrated into another system, or some features may be omitted or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated modules/units if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium.
  • the computer readable instructions when executed by a processor, may implement the steps of the various method embodiments described above.
  • the computer readable instructions comprise computer readable instruction code, which may be in the form of source code, an object code form, an executable file or some intermediate form or the like.
  • the computer readable medium may include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), electrical carrier signals, telecommunications signals, and software distribution media. It should be noted that the content contained in the computer readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable media Does not include electrical carrier signals and telecommunication signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Databases & Information Systems (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Technology Law (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Computational Linguistics (AREA)
  • Software Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请适用于信息处理技术领域，提供了一种手续费确定方法、装置、终端设备及介质。该手续费确定方法包括：获取目标系统预设时间段内的所有表单；根据获取的每个表单的业务员、业务来源和业务种类，查询每个表单对应的手续费比例；将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；根据HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单手续费，可以解决现有技术基于数据库计算手续费出现的数据库运行速度变慢，数据库性能降低的问题，同时减少手续费计算时间，提高手续费计算效率。

Description

手续费确定方法、装置、终端设备及介质
本申请申明享有2018年2月7日递交的申请号为201810121707.6、名称为“手续费确定方法及终端设备”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请属于信息处理技术领域，尤其涉及手续费确定方法、装置、终端设备及介质。
 背景技术
现有手续费计算依赖于数据库，即需要从数据库获取相关数据计算手续费。以投保手续费为例，需要从契约，理赔和保全三个系统数据库，获取前一交易日的所有保费数据，包括线上、线下投保和线上、线下退保的数据，然后根据系统中设定好的手续费比例，算出手续费，再将相应的手续费数据写到财务系统，供财务系统结算费用。
但是由于需要从数据库获取的数据较多，而且数据库中数据不断更新，导致计算手续费需要从数据库获取的数据越来越多，数据库运行速度变慢，数据库性能降低，使得手续费计算周期变长，手续费计算效率下降，无法满足现有业务需要。
 技术问题
有鉴于此，本申请实施例提供了手续费确定方法、装置、终端设备及介质，以解决现有手续费计算依赖于数据库，使得手续费计算周期变长，手续费计算效率下降的问题。
 技术解决方案
本申请实施例的第一方面提供了一种手续费确定方法，包括：
获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
本申请实施例的第二方面提供了一种手续费确定装置，包括：
表单获取单元，用于获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
手续费比例查询单元，用于根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
数据存储单元，用于将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
表单分组单元，用于确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
手续费计算单元，用于根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
本申请实施例的第三方面，提供了一种手续费确定终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
本申请实施例的第四方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，所述计算机可读指令被至少一个处理器执行时实现如下步骤：
获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
 有益效果
本申请实施例，通过将获取的目标系统预设时间段内的所有表单和查询到的每个表单的手续费比例存入HIVE，即将计算手续费的相关数据存在HIVE中，解决了现有技术基于数据库计算手续费出现的数据库运行速度变慢，数据库性能降低的问题，同时采用并行的方式计算手续费，减少手续费计算时间，提高手续费计算效率，满足现有业务需要。
 附图说明
图 1是本申请实施例提供的一种手续费确定方法的示意流程图；
图2是本申请另一实施例提供的一种手续费确定方法的示意流程图；
图3是本申请再一实施例提供的一种手续费确定方法的示意流程图；
图4是本申请又一实施例提供的一种手续费确定方法的示意流程图；
图5是本申请又一实施例提供的一种手续费确定方法的示意流程图；
图6是本申请实施例提供的一种手续费确定程序的示意性框图；
图7是本申请实施例提供的一种手续费确定终端设备的示意性框图。
 本发明的实施方式
为了说明本申请所述的技术方案，下面通过具体实施例来进行说明。
参见图1，图1是本申请实施例提供的一种手续费确定方法的示意流程图，在该实施例中，以终端的角度触发为例进行说明，这里，终端可以为智能手机、平板电脑等移动终端。如图1所示，在该实施例中，终端的处理过程可以包括以下步骤：
S101：获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用。
这里，目标系统可以为预先指定需要计算手续费的系统，例如契约系统，理赔系统、保全系统等，同样预设时间段也可以是预先指定的，例如前一交易日、前一小时等。目标系统和预设时间段可以根据实际需要指定，在指定完成后，还可以接收系统修改指令和时间段修改指令，根据系统修改指令修改指定的目标系统，根据时间段修改指令修改指定的预设时间段，直到符合要求。
表单为包含多种采集数据的数据单，例如保单。在上述获取目标系统预设时间段内的所有表单之后，可以首先检测获取的所有表单中是否都包含预设关键字，如果所有表单中都包含预设关键字则可以执行后续步骤，如果某些表单中没有包含预设关键字，删除没有包含预设关键字的表单，将剩余的表单作为新的获取的所有表单执行后续步骤。具体地，预设关键字根据实际情况设置，这样通过设置预设关键字对获取的表单进行检测，检测通过的表单才能执行后续步骤，保证后续步骤中的表单符合实际情况。
S102：根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例。
具体地，预存的手续费比例表可以通过以下方式生成：获取多个表单的业务员、业务来源和业务种类，基于RETE算法，根据获取的表单的业务员、业务来源和业务种类，确定每个表单的手续费比例，生成手续费比例表。
上述如果没有从预存的手续费比例表中查询到某些表单对应的手续费比例，则可以生成查询失败信息，同时为了方便用户了解情况，也可以显示具体哪些表单的手续费比例没有查询到，然后可以给出手续费比例生成流程，进入手续费比例生成界面，在该界面提示用户按照上述手续费比例生成流程提供相应数据生成手续费比例。
S103：将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中。
这里，HIVE是基于Hadoop的一个数据仓库工具，可以将结构化的数据文件映射为一张数据库表，并提供结构化查询语言查询功能，可以将结构化语句转换为MapReduce任务进行运行。上述将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中可以包括：首先根据获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，建立每个表单的业务单号、业务费用和手续费比例的对应关系，将建立的每个表单的对应关系存入HIVE，即将计算手续费的相关数据存入HIVE，解决了现有技术基于数据库计算手续费出现的消耗数据库性能问题，提高手续费计算速度。
S104：确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组。
这里，在确定获取的每个表单的大小后，可以对确定的表单大小进行记录，按照表单大小对获取的表单进行排序，方便后续进行表单分组。上述根据确定的每个表单的大小对获取的所有表单进行分组可以包括：先按照每个表单中包含业务员、业务来源、业务种类、业务单号或业务费用对获取的所有表单进行第一次分组，然后确定获取的每个表单的大小，根据确定的每个表单的大小获得第一次分组后每组表单的大小，按照预设分组大小上限和第一次分组后每组表单的大小，进行第二次分组。
S105：根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
具体地，通过业务费用和手续费比例算出手续费，即将每个业务单号对应的手续费比例乘以该业务单号对应的业务费用，计算得到该业务单号对应的手续费。这里，并行计算分组后每组表单的手续费，提高手续费计算速度，缩短手续费计算周期。
从以上描述可知，本申请实施例的手续费确定方法，通过将获取的目标系统预设时间段内的所有表单和查询到的每个表单的手续费比例存入HIVE，即将计算手续费的相关数据存在HIVE中，解决了现有技术基于数据库计算手续费出现的数据库运行速度变慢，数据库性能降低的问题，同时采用并行的方式计算手续费，减少手续费计算时间，提高手续费计算效率，满足现有业务需要。
请参阅图2，图2为本申请另一实施例提供的一种手续费确定的示意流程图。本实施例与上述实施例的区别在于S203~S207，其中S201~S202与上一实施例中的S101~S102相同，S208~S209与上一实施例中的S104~S105相同，具体请参阅上述实施例中S101~S102和S104~S105的相关描述，此处不赘述。本实施例中的手续费确定还可以包括：
S203：根据获取的每个表单中的中介和预存的中介手续费比例表，确定每个表单对应的中介手续费比例，其中，获取的每个表单中还包含中介。这里，除上述获取每个表单的业务员、业务来源和业务种类对应的手续费比例外，还进一步获取每个表单的中介对应的手续费比例，满足多种应用场景中的表单手续费计算需求。
S204：检测每个表单中的中介是否有多个。
S205：若检测到目标表单中的中介有多个，则根据预存的中介与手续费拆分比例的对应关系，确定所述目标表单中的每个中介对应的手续费拆分比例，所述目标表单为获取的每个表单中的任意一个表单。
具体地，目标表单为获取的每个表单中的任意一个表单，如果获取的表单中有多个表单中的中介有多个，则具有多个中介的每个表单都需作为上述步骤S205所述的目标表单，确定每个表单中的每个中介对应的手续费拆分比例。若检测到目标表单中的中介有多个，例如有中介0、中介1、中介2，根据预存的中介与手续费拆分比例的对应关系，确定所述目标表单中的每个中介对应的手续费拆分比例，例如根据预存的中介与手续费拆分比例的对应关系，确定中介0对应的拆分比例是1/3，中介1对应的拆分比例是1/6，中介2对应的拆分比例是1/2。根据上述中介与拆分比例的对应关系，将中介手续费比例进一步拆分。
S206：根据所述目标表单中的每个中介对应的手续费拆分比例，对所述目标表单对应的中介手续费比例进行拆分，确定所述目标表单中的每个中介对应的中介手续费比例。
这里，如果一个表单中有多个中介，则首先确定该表单中每个中介对应的手续费拆分比例，然后根据每个中介对应的手续费拆分比例确定该表单中每个中介对应的中介手续费比例，方便后续计算中介手续费，在单个表单包含多个中介时，快速、准确地计算出不同中介对应的手续费，适合实际应用。
S207：将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例和所述目标表单中的每个中介对应的中介手续费比例，存入HIVE中。
请参阅图3，图3是本申请再一实施例提供的一种手续费确定方法的示意流程图。与图1对应的实施例的区别在于：所述确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组可以包括S304。其中S301~ S303与上一实施例中的S101~ S103相同，S305与上一实施例中的S105相同，具体请参阅上述实施例中S101~ S103、S105的相关描述，此处不赘述。具体地，S304可以包括S3041~ S3042：
S3041：确定获取的每个表单的大小，根据确定的每个表单的大小获得获取的所有表单的大小总和，审核获取的所有表单的大小总和是否超过预设分组大小上限。
S3042：若审核获取的所有表单的大小总和超过所述预设分组大小上限，则根据所述预设分组大小上限对获取的所有表单进行分组，使分组后的每一组表单的大小均不超过所述预设分组大小上限。
具体地，预设分组大小上限可以根据实际情况设置，例如预设分组大小上限为100。获取的所有表单为表单1、表单2、表单3和表单4，表单1大小为50，表单2大小为60，表单3大小为40，表单4大小为50，则获取的所有表单的大小总和为200，超过预设分组大小上限100，根据预设分组大小上限对获取的所有表单进行分组，使分组后的每一组表单的大小均不超过预设分组大小上限，即将表单1和表单4分为一组，表单2和表单3分为一组。分组完成后，并行计算分组后每组表单的手续费，快速完成手续费计算，提高计算效率。
请参阅图4，图4为本申请又一实施例提供的一种手续费确定的示意流程图。本实施例上述实施例的区别在于S403~S405，其中S401~S402与上一实施例中的S101~S102相同，具体请参阅上述实施例中S101~S102的相关描述，此处不赘述。本实施例中的手续费确定还可以包括：
S403：以获取的每个表单的业务单号为key，以获取的每个表单的业务费用和手续费比例为值，将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，以键值对的形式存入HIVE中。这里，以上述每个表单的业务单号为key，获取的每个表单对应的手续费比例和上述每个表单的业务费为值，存入到HIVE中，即将计算手续费的相关数据存储在HIVE，解决了现有技术基于数据库计算手续费出现的手续费计算周期长问题。
S404：确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组。
S405：从所述HIVE中抽取键值对，将每一个键值对作为参数传递给map函数并行计算分组后每组表单的手续费。具体地，从HIVE中抽取键值对（业务单号为key, 手续费比例和业务费用作为值），每一个键值对都作为参数传递给map函数，map函数并行计算分组后每组表单的手续费，通过业务费用和手续费比例算出手续费，即每个业务单号对应的手续费比例乘以该业务单号对应的业务费用，计算该业务单号对应的手续费。
在并行计算分组后每组表单的手续费后，还可以缓存计算得到的手续费，并将缓存的手续费定期写入HIVE中。
上述将缓存的手续费定期写入HIVE的方式包括：以上述每个表单的业务单号为key，计算的每个表单对应的手续费为值，定期写入HIVE中。在上述将缓存的手续费定期写入HIVE后，还可以从HIVE中把数据导入到关系型数据库中，用于后续财务结算。
这里，通过将计算手续费的相关数据存在HIVE中，解决了现有技术基于数据库计算手续费出现的数据库运行速度变慢，数据库性能降低的问题，同时采用map函数并行计算手续费，减少手续费计算时间，提高手续费计算效率。
请参阅图5，图5是本申请再一实施例提供的一种手续费确定方法的示意流程图。与图1对应的实施例的区别在于：所述根据获取的每个表单中的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例可以包括S502。其中S501与上一实施例中的S101相同，S503~ S505与上一实施例中的S103~ S105相同，具体请参阅上述实施例中S101、S103~ S105的相关描述，此处不赘述。具体地，S502可以包括S5021~ S5023：
S5021：根据获取的每个表单中的业务员和预存的业务员手续费比例表，确定每个表单对应的业务员手续费比例，其中，所述预存的手续费比例表包括预存的业务员手续费比例表、业务来源手续费比例表和业务种类手续费比例表。
S5022：根据获取的每个表单中的业务来源和预存的业务来源手续费比例表，确定每个表单对应的业务来源手续费比例。
S5023：根据获取的每个表单中的业务种类和预存的业务种类手续费比例表，确定每个表单对应的业务种类手续费比例。
这里，上述每个表单对应的手续费比例包括业务员手续费比例、业务来源手续费比例和业务种类手续费比例等，根据预存的手续费比例表，确定每个表单中的业务员、业务来源和业务种类对应的手续费比例，保证后续处理正常进行，满足实际手续费计算要求，适合实际应用。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
对应于上文实施例所述的手续费确定方法，图6 示出了本申请实施例提供的手续费确定程序的运行环境示意图。为了便于说明，仅示出了与本实施例相关的部分。
在本实施例中，所述的手续费确定程序600安装并运行于终端设备60中。该终端设备60可以是移动终端、掌上电脑、服务器等。该终端设备60可包括，但不仅限于，存储器601、处理器602及显示器603。图6仅示出了具有组件601-603的终端设备60，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
所述存储器601在一些实施例中可以是所述终端设备60的内部存储单元，例如该终端设备60的硬盘或内存。所述存储器601在另一些实施例中也可以是所述终端设备60的外部存储设备，例如所述终端设备60上配备的插接式硬盘，智能存储卡（Smart Media Card，SMC），安全数字（Secure Digital，SD）卡，闪存卡（Flash Card）等。进一步地，所述存储器601还可以既包括所述终端设备60的内部存储单元也包括外部存储设备。所述存储器601用于存储安装于所述终端设备60的应用软件及各类数据，例如所述手续费确定程序600的程序代码等。所述存储器601还可以用于暂时地存储已经输出或者将要输出的数据。
所述处理器602在一些实施例中可以是一中央处理器（Central Processing Unit，CPU），微处理器或其他数据处理芯片，用于运行所述存储器601中存储的程序代码或处理数据，例如执行所述手续费确定程序600等。
所述显示器603在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及有机发光二极管（Organic Light-Emitting Diode，OLED）触摸器等。所述显示器603用于显示在所述终端设备60中处理的信息以及用于显示可视化的用户界面，例如应用菜单界面、应用图标界面等。所述终端设备60的部件601-603通过系统总线相互通信。
请参阅图7，是本申请实施例提供的手续费确定程序600的功能模块图。在本实施例中，所述的手续费确定程序600可以被分割成一个或多个模块，所述一个或者多个模块被存储于所述存储器601中，并由一个或多个处理器（本实施例为所述处理器602）所执行，以完成本申请。例如，在图7中，所述的手续费确定程序600可以被分割成表单获取单元701、手续费比例查询单元702、数据存储单元703、表单分组单元704及手续费计算单元705。本申请所称的单元是指能够完成特定功能的一系列计算机可读指令指令段，比程序更适合于描述所述手续费确定程序600在所述终端设备60中的执行过程。以下描述将具体介绍所述模块701-705的功能。
其中，表单获取单元701，用于获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用。手续费比例查询单元702，用于根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例。数据存储单元703，用于将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中。表单分组单元704，用于确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组。手续费计算单元705，用于根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
可选的，获取的每个表单中还包含中介。所述的手续费确定程序600还可以被分割成第一中介手续费比例确定单元706、中介检测单元707、手续费拆分比例确定单元708和第二中介手续费比例确定单元709。
其中，第一中介手续费比例确定单元706，用于根据获取的每个表单中的中介和预存的中介手续费比例表，确定每个表单对应的中介手续费比例。中介检测单元707，用于检测每个表单中的中介是否有多个。手续费拆分比例确定单元708，用于若检测到目标表单中的中介有多个，则根据预存的中介与手续费拆分比例的对应关系，确定所述目标表单中的每个中介对应的手续费拆分比例，所述目标表单为获取的每个表单中的任意一个表单。第二中介手续费比例确定单元709，用于根据所述目标表单中的每个中介对应的手续费拆分比例，对所述目标表单对应的中介手续费比例进行拆分，确定所述目标表单中的每个中介对应的中介手续费比例。所述数据存储单元703，还用于将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例和所述目标表单中的每个中介对应的中介手续费比例，存入HIVE中。
可选的，所述的表单分组单元704还可以被分割成表单大小审核单元7041和表单处理单元7042。
其中，表单大小审核单元7041，用于确定获取的每个表单的大小，根据确定的每个表单的大小获得获取的所有表单的大小总和，审核获取的所有表单的大小总和是否超过预设分组大小上限。表单处理单元7042，用于若审核获取的所有表单的大小总和超过所述预设分组大小上限，则根据所述预设分组大小上限对获取的所有表单进行分组，使分组后的每一组表单的大小均不超过所述预设分组大小上限。
可选的，数据存储单元703，还用于以获取的每个表单的业务单号为key，以获取的每个表单的业务费用和手续费比例为值，将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，以键值对的形式存入所述HIVE中。手续费计算单元705，还用于从所述HIVE中抽取键值对，将每一个键值对作为参数传递给map函数并行计算分组后每组表单的手续费。
可选的，所述预存的手续费比例表包括预存的业务员手续费比例表、业务来源手续费比例表和业务种类手续费比例表。所述手续费比例查询单元702可以被分割为业务员手续费比例确定单元7021、业务来源手续费比例确定单元7022和业务种类手续费比例确定单元7023。
其中，业务员手续费比例确定单元7021，用于根据获取的每个表单中的业务员和预存的业务员手续费比例表，确定每个表单对应的业务员手续费比例。业务来源手续费比例确定单元7022，用于根据获取的每个表单中的业务来源和预存的业务来源手续费比例表，确定每个表单对应的业务来源手续费比例。业务种类手续费比例确定单元7023，用于根据获取的每个表单中的业务种类和预存的业务种类手续费比例表，确定每个表单对应的业务种类手续费比例。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。实施例中的各功能单元、模块可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中，上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。另外，各功能单元、模块的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。上述系统中单元、模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的实施例中，应该理解到，所揭露的装置/终端设备和方法，可以通过其它的方式实现。例如，以上所描述的装置/终端设备实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通讯连接可以是通过一些接口，装置或单元的间接耦合或通讯连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的模块/单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，也可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一计算机可读存储介质中，该计算机可读指令在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机可读指令包括计算机可读指令代码，所述计算机可读指令代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器（Read-Only Memory，ROM）、随机存取存储器（Random Access Memory，RAM）、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读介质不包括电载波信号和电信信号。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种手续费确定方法，其特征在于，包括：
    获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
    根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
    将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
    确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
    根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
  2. 如权利要求1所述的手续费确定方法，其特征在于，获取的每个表单中还包含中介；
    所述方法还包括：根据获取的每个表单中的中介和预存的中介手续费比例表，确定每个表单对应的中介手续费比例；
    检测每个表单中的中介是否有多个；
    若检测到目标表单中的中介有多个，则根据预存的中介与手续费拆分比例的对应关系，确定所述目标表单中的每个中介对应的手续费拆分比例，所述目标表单为获取的每个表单中的任意一个表单；
    根据所述目标表单中的每个中介对应的手续费拆分比例，对所述目标表单对应的中介手续费比例进行拆分，确定所述目标表单中的每个中介对应的中介手续费比例。
  3. 如权利要求1所述的手续费确定方法，其特征在于，所述确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组包括：
    确定获取的每个表单的大小，根据确定的每个表单的大小获得获取的所有表单的大小总和，审核获取的所有表单的大小总和是否超过预设分组大小上限；
    若审核获取的所有表单的大小总和超过所述预设分组大小上限，则根据所述预设分组大小上限对获取的所有表单进行分组，使分组后的每一组表单的大小均不超过所述预设分组大小上限。
  4. 如权利要求1所述的手续费确定方法，其特征在于，所述将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中包括：
    以获取的每个表单的业务单号为键，以获取的每个表单的业务费用和手续费比例为值，将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，以键值对的形式存入所述HIVE中；
    所述根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费包括：
    从所述HIVE中抽取键值对，将每一个键值对作为参数传递给map函数并行计算分组后每组表单的手续费。
  5. 如权利要求1所述的手续费确定方法，其特征在于，所述预存的手续费比例表包括预存的业务员手续费比例表、业务来源手续费比例表和业务种类手续费比例表；
    所述根据获取的每个表单中的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例包括：
    根据获取的每个表单中的业务员和预存的业务员手续费比例表，确定每个表单对应的业务员手续费比例；
    根据获取的每个表单中的业务来源和预存的业务来源手续费比例表，确定每个表单对应的业务来源手续费比例；
    根据获取的每个表单中的业务种类和预存的业务种类手续费比例表，确定每个表单对应的业务种类手续费比例。
  6. 一种手续费确定装置，其特征在于，包括：
    表单获取单元，用于获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
    手续费比例查询单元，用于根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
    数据存储单元，用于将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
    表单分组单元，用于确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
    手续费计算单元，用于根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费
  7. 根据权利要求6所述的手续费确定装置，其特征在于，获取的每个表单中还包含中介；
    所述装置还包括：第一中介手续费比例确定单元，用于根据获取的每个表单中的中介和预存的中介手续费比例表，确定每个表单对应的中介手续费比例；
    中介检测单元，用于检测每个表单中的中介是否有多个；
    手续费拆分比例确定单元，用于若检测到目标表单中的中介有多个，则根据预存的中介与手续费拆分比例的对应关系，确定所述目标表单中的每个中介对应的手续费拆分比例，所述目标表单为获取的每个表单中的任意一个表单；
    第二中介手续费比例确定单元，用于根据所述目标表单中的每个中介对应的手续费拆分比例，对所述目标表单对应的中介手续费比例进行拆分，确定所述目标表单中的每个中介对应的中介手续费比例；
    数据存储单元，还用于将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例和所述目标表单中的每个中介对应的中介手续费比例，存入HIVE中。
  8. 根据权利要求6所述的手续费确定装置，其特征在于，所述表单分组单元还包括：
    表单大小审核单元，用于确定获取的每个表单的大小，根据确定的每个表单的大小获得获取的所有表单的大小总和，审核获取的所有表单的大小总和是否超过预设分组大小上限；
    表单处理单元，用于若审核获取的所有表单的大小总和超过所述预设分组大小上限，则根据所述预设分组大小上限对获取的所有表单进行分组，使分组后的每一组表单的大小均不超过所述预设分组大小上限。
  9. 根据权利要求6所述的手续费确定装置，其特征在于，所述数据存储单元，还用于以获取的每个表单的业务单号为键，以获取的每个表单的业务费用和手续费比例为值，将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，以键值对的形式存入所述HIVE中；
    所述手续费计算单元，还用于从所述HIVE中抽取键值对，将每一个键值对作为参数传递给map函数并行计算分组后每组表单的手续费。
  10. 根据权利要求6所述的手续费确定装置，其特征在于，所述预存的手续费比例表包括预存的业务员手续费比例表、业务来源手续费比例表和业务种类手续费比例表；
    所述手续费比例查询单元还包括：
    业务员手续费比例确定单元，用于根据获取的每个表单中的业务员和预存的业务员手续费比例表，确定每个表单对应的业务员手续费比例；
    业务来源手续费比例确定单元，用于根据获取的每个表单中的业务来源和预存的业务来源手续费比例表，确定每个表单对应的业务来源手续费比例；
    业务种类手续费比例确定单元，用于根据获取的每个表单中的业务种类和预存的业务种类手续费比例表，确定每个表单对应的业务种类手续费比例。
  11. 一种手续费确定终端设备，其特征在于，包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
    获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
    根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
    将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
    确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
    根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
  12. 根据权利要求11所述的手续费确定终端设备，其特征在于，获取的每个表单中还包含中介；所述处理器执行所述计算机可读指令时还实现如下步骤：
    根据获取的每个表单中的中介和预存的中介手续费比例表，确定每个表单对应的中介手续费比例；
    检测每个表单中的中介是否有多个；
    若检测到目标表单中的中介有多个，则根据预存的中介与手续费拆分比例的对应关系，确定所述目标表单中的每个中介对应的手续费拆分比例，所述目标表单为获取的每个表单中的任意一个表单；
    根据所述目标表单中的每个中介对应的手续费拆分比例，对所述目标表单对应的中介手续费比例进行拆分，确定所述目标表单中的每个中介对应的中介手续费比例。
  13. 根据权利要求11所述的手续费确定终端设备，其特征在于，所述确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组包括：
    确定获取的每个表单的大小，根据确定的每个表单的大小获得获取的所有表单的大小总和，审核获取的所有表单的大小总和是否超过预设分组大小上限；
    若审核获取的所有表单的大小总和超过所述预设分组大小上限，则根据所述预设分组大小上限对获取的所有表单进行分组，使分组后的每一组表单的大小均不超过所述预设分组大小上限。
  14. 根据权利要求11所述的手续费确定终端设备，其特征在于，所述将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中包括：
    以获取的每个表单的业务单号为键，以获取的每个表单的业务费用和手续费比例为值，将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，以键值对的形式存入所述HIVE中；
    所述根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费包括：
    从所述HIVE中抽取键值对，将每一个键值对作为参数传递给map函数并行计算分组后每组表单的手续费。
  15. 根据权利要求11所述的手续费确定终端设备，其特征在于，所述预存的手续费比例表包括预存的业务员手续费比例表、业务来源手续费比例表和业务种类手续费比例表；
    所述根据获取的每个表单中的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例包括：
    根据获取的每个表单中的业务员和预存的业务员手续费比例表，确定每个表单对应的业务员手续费比例；
    根据获取的每个表单中的业务来源和预存的业务来源手续费比例表，确定每个表单对应的业务来源手续费比例；
    根据获取的每个表单中的业务种类和预存的业务种类手续费比例表，确定每个表单对应的业务种类手续费比例。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其特征在于，所述计算机可读指令被至少一个处理器执行时实现如下步骤：
    获取目标系统预设时间段内的所有表单，每个表单中包含业务员、业务来源、业务种类、业务单号和业务费用；
    根据获取的每个表单的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例；
    将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中；
    确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组；
    根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费。
  17. 根据权利要求16所述的计算机可读存储介质，其特征在于，获取的每个表单中还包含中介；所述计算机可读指令被至少一个处理器执行时还实现如下步骤：
    根据获取的每个表单中的中介和预存的中介手续费比例表，确定每个表单对应的中介手续费比例；
    检测每个表单中的中介是否有多个；
    若检测到目标表单中的中介有多个，则根据预存的中介与手续费拆分比例的对应关系，确定所述目标表单中的每个中介对应的手续费拆分比例，所述目标表单为获取的每个表单中的任意一个表单；
    根据所述目标表单中的每个中介对应的手续费拆分比例，对所述目标表单对应的中介手续费比例进行拆分，确定所述目标表单中的每个中介对应的中介手续费比例。
  18. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述确定获取的每个表单的大小，根据确定的每个表单的大小对获取的所有表单进行分组包括：
    确定获取的每个表单的大小，根据确定的每个表单的大小获得获取的所有表单的大小总和，审核获取的所有表单的大小总和是否超过预设分组大小上限；
    若审核获取的所有表单的大小总和超过所述预设分组大小上限，则根据所述预设分组大小上限对获取的所有表单进行分组，使分组后的每一组表单的大小均不超过所述预设分组大小上限。
  19. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，存入HIVE中包括：
    以获取的每个表单的业务单号为键，以获取的每个表单的业务费用和手续费比例为值，将获取的每个表单的业务单号和业务费用，以及查询到的每个表单对应的手续费比例，以键值对的形式存入所述HIVE中；
    所述根据所述HIVE中存储的表单的业务单号、业务费用和手续费比例，并行计算分组后每组表单的手续费包括：
    从所述HIVE中抽取键值对，将每一个键值对作为参数传递给map函数并行计算分组后每组表单的手续费。
  20. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述预存的手续费比例表包括预存的业务员手续费比例表、业务来源手续费比例表和业务种类手续费比例表；
    所述根据获取的每个表单中的业务员、业务来源和业务种类，从预存的手续费比例表中查询每个表单对应的手续费比例包括：
    根据获取的每个表单中的业务员和预存的业务员手续费比例表，确定每个表单对应的业务员手续费比例；
    根据获取的每个表单中的业务来源和预存的业务来源手续费比例表，确定每个表单对应的业务来源手续费比例；
    根据获取的每个表单中的业务种类和预存的业务种类手续费比例表，确定每个表单对应的业务种类手续费比例。
PCT/CN2018/082613 2018-02-07 2018-04-11 手续费确定方法、装置、终端设备及介质 WO2019153483A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810121707.6 2018-02-07
CN201810121707.6A CN108446989B (zh) 2018-02-07 2018-02-07 手续费确定方法及终端设备

Publications (1)

Publication Number Publication Date
WO2019153483A1 true WO2019153483A1 (zh) 2019-08-15

Family

ID=63191671

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082613 WO2019153483A1 (zh) 2018-02-07 2018-04-11 手续费确定方法、装置、终端设备及介质

Country Status (2)

Country Link
CN (1) CN108446989B (zh)
WO (1) WO2019153483A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109377336A (zh) * 2018-09-28 2019-02-22 平安科技（深圳）有限公司 手续费结算的数据处理方法、装置、设备及存储介质
CN110020944A (zh) * 2018-10-25 2019-07-16 阿里巴巴集团控股有限公司 对象计算方法、装置、电子设备及计算机可读存储介质
CN109598495A (zh) * 2018-10-26 2019-04-09 阿里巴巴集团控股有限公司 数据处理方法、装置、服务器及计算机可读存储介质
CN109727060B (zh) * 2018-11-29 2024-04-02 平安科技（深圳）有限公司 日展费用处理方法、装置、设备及可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050060247A1 (en) * 2003-09-12 2005-03-17 Tien Yuan Hui Forwarder stocktaking management system and method
CN104318466A (zh) * 2014-10-20 2015-01-28 深圳市深信信息技术有限公司 一种交易系统及交易结算方法
CN105719088A (zh) * 2016-01-25 2016-06-29 深圳市华阳信通科技发展有限公司 一种智能分润结算方法及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160071028A1 (en) * 2014-09-10 2016-03-10 Amadeus S.A.S. Updating travel data in a server database of a centralized mid-back office system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050060247A1 (en) * 2003-09-12 2005-03-17 Tien Yuan Hui Forwarder stocktaking management system and method
CN104318466A (zh) * 2014-10-20 2015-01-28 深圳市深信信息技术有限公司 一种交易系统及交易结算方法
CN105719088A (zh) * 2016-01-25 2016-06-29 深圳市华阳信通科技发展有限公司 一种智能分润结算方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WANG, ZHENGYE: "Hadoop (Performance Optimization of a Massive Data Query and Analysis System on Hadoop", CHINESE MASTER S THESES FULL-TEXT DATABASE, INFORMATION SCIENCE & TECHNOLOGY, 15 August 2015 (2015-08-15) *

Also Published As

Publication number Publication date
CN108446989A (zh) 2018-08-24
CN108446989B (zh) 2021-04-30

Similar Documents

Publication Publication Date Title
US8924426B2 (en) Joining tables in a mapreduce procedure
WO2019153483A1 (zh) 手续费确定方法、装置、终端设备及介质
CN108536761A (zh) 报表数据查询方法及服务器
US11675779B2 (en) Enhanced high performance real-time relational database system and methods for using same
US20210287298A1 (en) Actuarial processing method and device
AU2014364942B2 (en) Long string pattern matching of aggregated account data
CN109299164A (zh) 一种数据查询方法、计算机可读存储介质及终端设备
US11288094B2 (en) Systems and methods for caching task execution
WO2021051546A1 (zh) 一种链路异常识别方法、服务器及计算机可读存储介质
US9600559B2 (en) Data processing for database aggregation operation
CN111046237A (zh) 用户行为数据处理方法、装置、电子设备及可读介质
CN113946690A (zh) 潜在客户挖掘方法、装置、电子设备及存储介质
CN111611241A (zh) 一种字典数据操作方法、装置、可读存储介质及终端设备
CN113590632B (zh) 数据库索引创建方法、装置、设备及介质
CN111612616A (zh) 区块链账户评估方法、装置、终端设备及计算机可读介质
CN113902574A (zh) 协议数据处理方法、装置、计算机设备及存储介质
CN109542657A (zh) 系统异常的处理方法及服务器
CN103809915B (zh) 一种磁盘文件的读写方法和装置
CN110705816B (zh) 基于大数据的任务分配方法和装置
US9092472B1 (en) Data merge based on logical segregation
CN112667619B (zh) 辅助检查数据的方法、装置、终端设备及存储介质
CN116628042A (zh) 数据处理方法、装置、设备及介质
CN115114297A (zh) 数据轻量存储及查找方法、装置、电子设备及存储介质
CN111723129A (zh) 报表生成方法、报表生成装置和电子设备
CN113127574A (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: 18905748

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 03.11.2020.)

122 Ep: pct application non-entry in european phase

Ref document number: 18905748

Country of ref document: EP

Kind code of ref document: A1