WO2018184520A1 - 业务数据处理方法、装置、服务器和存储介质 - Google Patents

业务数据处理方法、装置、服务器和存储介质 Download PDF

Info

Publication number
WO2018184520A1
WO2018184520A1 PCT/CN2018/081705 CN2018081705W WO2018184520A1 WO 2018184520 A1 WO2018184520 A1 WO 2018184520A1 CN 2018081705 W CN2018081705 W CN 2018081705W WO 2018184520 A1 WO2018184520 A1 WO 2018184520A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
type
service
risk
business
Prior art date
Application number
PCT/CN2018/081705
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 WO2018184520A1 publication Critical patent/WO2018184520A1/zh

Links

Images

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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • the application relates to a service data processing method, device, server and storage medium.
  • Insurance means that the insured pays the insurance premium to the insurer according to the contract, and the insurer is liable for the property damage caused by the accident caused by the insurer.
  • the customer can choose to go to the counter to handle the insurance business, or fill in the application materials and return it to the business personnel for entry.
  • the channel of filling in the application materials and then entering the account it is impossible to directly verify the identity of the customer, especially the payment of insurance, etc., and there may be fraudulent acts such as insurance for the unlawful person, which cannot guarantee security.
  • a service data processing method, apparatus, server, and storage medium are provided.
  • a method of processing business data comprising:
  • the business risk level is determined based on the account risk level and the cumulative returned business value.
  • a service data processing device includes:
  • An extraction module configured to obtain return service data, and extract account information from the returned service data
  • a historical data obtaining module configured to acquire historical record data according to the account information
  • An account type determining module configured to determine an account type according to the historical record data
  • a dividing module configured to divide an account risk level according to the account type
  • a calculation module configured to calculate, according to the historical record data, a cumulative return service value of the account within a first preset time
  • the business risk determining module is configured to determine a business risk level according to the account risk level and the accumulated return service value.
  • a server comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to perform the following Step: acquiring return service data, and extracting account information from the returned service data; acquiring history record data according to the account information; determining an account type according to the history record data; and dividing an account risk level according to the account type; The historical record data calculates an accumulated return service value of the account within a first preset time; and determines a business risk level according to the account risk level and the accumulated returned service value.
  • One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of: obtaining the returned service data, and Extracting account information from the returned service data; acquiring history record data according to the account information; determining an account type according to the history record data; dividing an account risk level according to the account type; calculating an account according to the historical record data A cumulative return service value within a predetermined time period; and determining a business risk level based on the account risk level and the cumulative returned service value.
  • FIG. 1 is a block diagram of a server in accordance with one or more embodiments.
  • FIG. 2 is a flow diagram of business data processing in accordance with one or more embodiments.
  • FIG. 3 is a flow diagram of determining an account type based on historical data in accordance with one or more embodiments.
  • FIG. 4 is a flow chart showing the determination of an account type based on historical data in another embodiment.
  • FIG. 5 is a flow diagram of determining a business risk level based on an account risk level and a cumulative returned service value, in accordance with one or more embodiments.
  • FIG. 6 is a block diagram of a traffic data processing apparatus in accordance with one or more embodiments.
  • FIG. 7 is a block diagram of an account type determination module in accordance with one or more embodiments.
  • FIG. 8 is a block diagram of a partitioning module in accordance with one or more embodiments.
  • FIG. 9 is a block diagram of a business risk determination module in accordance with one or more embodiments.
  • FIG. 10 is an application environment diagram of a service data processing method according to one or more embodiments.
  • the service data processing method provided by the present application can be applied to an application environment as shown in FIG.
  • the terminal 1002 communicates with the server 1004 via a network.
  • the server 1004 obtains the returned service data, and extracts account information from the returned service data; acquires historical record data according to the account information; determines an account type according to the historical record data; and divides an account risk level according to the account type;
  • the historical record data calculates an accumulated return service value of the account within a first preset time; the server 1004 determines a business risk level according to the account risk level and the accumulated returned service value.
  • the terminal 1002 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablets, and portable wearable devices, and the server 1004 can be implemented by a stand-alone server or a server cluster composed of a plurality of servers.
  • FIG. 1 is a block diagram of a server in one embodiment.
  • the server includes a processor, memory, and network interface connected by a system bus.
  • the memory of the server includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium may be a non-transitory computer readable storage medium.
  • the non-volatile storage medium of the server stores an operating system, a database, and computer readable instructions, and the database stores the returned service data, the account information, the history data, and the like, and the computer readable instructions are used to implement the embodiment of the present application.
  • a business data processing method that is provided for the server.
  • the server's processor is used to provide computing and control capabilities that support the operation of the entire server.
  • the internal memory of the server provides a cached operating environment for operating systems and computer readable instructions in a non-volatile storage medium.
  • the network interface of the server is used to communicate with an external terminal through a network connection, such as a return service operation request sent by the receiving terminal.
  • the server can be implemented with a stand-alone server or a server cluster consisting of multiple servers. It will be understood by those skilled in the art that the structure shown in FIG. 1 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. Specifically, the server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.
  • a service data processing method is provided.
  • the method is applied to the server shown in FIG. 10 or FIG. 1 as an example, and includes the following steps:
  • step S210 the returned service data is acquired, and the account information is extracted from the returned service data.
  • the non-parent channel refers to the channel that cannot directly verify the true identity of the customer, and may include filling in the paper application materials and then inputting by the business personnel, directly in the Fill in the electronic application materials and submit them to the server, or apply by phone.
  • the terminal may send a return service operation request to the server, and send the returned service data to the server for processing.
  • the server receives the return service operation request sent by the terminal, and obtains the return service data according to the return service operation request, and the returned service data may include the account information processed, the returned service type, the returned amount, and the like, wherein the account information may include an account ID (idenfication, Identity), account name, etc.
  • Step S220 acquiring history data according to the account information.
  • the server may extract the account information from the returned service data, and may query the account ID in the account information as a key (key) in the database to obtain a matching value (value), thereby obtaining history data matching the account ID.
  • Step S230 determining an account type based on the history data.
  • the account type may include a secure account, a brand new account, and a general account, wherein the secure account refers to an account that has been verified to have a particularly high level of customer identity security, and the new account refers to an account that has not handled the business.
  • the ordinary account refers to an account that has already handled the business but has not verified the identity of the customer.
  • the account type can be set according to the security level of the account. In this embodiment, the security level of the account is Security Account > Normal Account > Brand New Account.
  • the server obtains the history data matching the account ID, and can determine the account type of the returned service according to the historical record data.
  • Step S240 the account risk level is divided according to the account type.
  • the server may divide the account risk level of the returned business according to the preset relationship between the account type and the account risk level, and may divide the account risk level according to actual needs, and set an account corresponding to each account risk level.
  • the account risk level can be set to include a low risk account, a medium risk account, and a high risk account, the low risk account corresponds to a security account, the medium risk account corresponds to a normal account, and the high risk account corresponds to a new account, but is not limited thereto.
  • Step S250 Calculate the accumulated return service value of the account in the first preset time according to the historical record data.
  • the server may obtain the returned service data that the account has processed in the first preset time according to the service type and the processing time and the like, for example, obtain the returned service data that the account has processed within 90 days.
  • the server may extract the returned service value from the returned service data processed in the first preset time, and perform an accumulated calculation to obtain a cumulative returned service value.
  • Step S260 determining a business risk level according to the account risk level and the accumulated returned service value.
  • the server may determine the business risk level according to the account risk level and the accumulated return service value of the account within the first preset time, may preset the business risk level and the corresponding judgment condition, and convert the business risk level and the corresponding judgment condition into
  • the matching fields and configuration values are stored in the configuration table.
  • the business risk level is a low-risk business. If the corresponding judgment condition includes a low-risk account and the accumulated return service value is less than 1000 RMB, it can be converted into a field and a configuration value in the configuration table as shown in Table 1.
  • Sum_money represents the cumulative return business value
  • Grade_account risk represents the account risk level
  • Grade_business risk represents the business risk level
  • the tag corresponding to the service risk level can be added to the returned service data, so that when the service data is returned to the next process flow node, the service personnel can perform corresponding processing according to the service risk level, for example, If the secondary return service is a high-risk business, it is necessary to authenticate the customer through video or cabinet, etc., but it is not limited to this, and it can effectively control the business risk.
  • the foregoing service data processing method extracts account information from the returned service data, acquires historical record data according to the account information, determines an account type according to the account information and the historical record data, and divides the account risk level according to the account type, and calculates the account at the first preset.
  • the business risk level can be determined according to the account risk level and the accumulated returned business value, and the risk of the business can be evaluated, thereby effectively controlling the business risk, and ensuring the business security when the identity of the customer cannot be directly verified. Sex.
  • step S230 determines an account type based on the history data, including the following steps:
  • step S302 when the history data includes a record for processing the business through the counter channel or the remote machine channel, the account type is determined to be a security account.
  • the server may determine, according to the processing channel field of the historical data, whether the history data is included in the historical data recorded through the counter channel or through the remote machine channel, wherein the remote machine channel refers to the client logging in to the remote host through the remote host and the cabinet.
  • the business personnel of the company connect and conduct business through video calls and the like.
  • the history data contains records for processing through the cabinet channel or the remote channel, the customer associated with the account has been authenticated and the account type is determined to be a secure account.
  • Step S304 when the account type is not a secure account, and the history data is empty, it is determined that the account type is a brand new account.
  • the server may further determine whether the history data is empty. If yes, it indicates that the account has not been processed before, and the account type may be determined to be a new account.
  • Step S306 when the account type is not a secure account or a brand new account, it is determined that the account type is a normal account.
  • the server determines that the account type is a normal account, and the ordinary account may be further divided.
  • the common account may include a first general account, a second normal account, and a third normal account, and different types of ordinary accounts correspond to different accounts.
  • Features can be set according to actual needs, further refine the account type to make business risk assessment more accurate.
  • step S306 after determining that the account type is a normal account, the following steps are also included:
  • Step S402 obtaining a payment service record according to the history data.
  • Step S404 determining whether the time for continuously processing the payment service is greater than the second preset time according to the payment service record, and determining the account type when the time for continuously processing the payment service is greater than the second preset time, and the type of the service to be paid is a preset type. For the first ordinary account.
  • the server may select, from the history data, the record data of the service type as the payment service, and determine whether the time for continuously paying the service is greater than the second preset time according to the processing time in each payment service record, understandably, the second preset The time can be set according to actual needs. For example, the time for continuing to pay the business is more than 2 years or 3 years.
  • the server may further determine whether the type of the service to be paid is a preset type, and the preset type may be set in advance according to actual needs, such as the first premium, the renewal premium, Self-pay repayment, etc., where the first premium refers to the premium paid by the customer in the first year after the insurance, and the renewal premium refers to the insurance premium paid in installments after the first premium.
  • the insurance premium paid by the insurance company during the grace period is not paid by the customer in accordance with the period specified in the insurance contract.
  • the server may determine that the account type is the first normal account.
  • Step S406 obtaining the first registration time from the history data.
  • the first registration time is the first time the account is processed.
  • the server can select the earliest processing time from the historical data as the first registration time of the account.
  • step S408 when the account information carries the error data identifier, or the time interval between the first registration time and the current return service is less than the third preset time, the account type is determined to be the third normal account.
  • the server may detect whether the account information carries the error data identifier, wherein the error data identifier is used to mark the account information and there is error information and no correction is made, or the server determines the first registration time of the account. Whether the time interval from the current return service is less than the third preset time, for example, less than 1 year or less than 14 months. When the account information carries the error data identifier, or the time interval between the first registration time and the current return service is less than the third preset time, the server may determine that the account type is the third normal account.
  • Step S410 when the account type is neither the first normal account nor the third normal account, it is determined that the account type is the second normal account.
  • the first ordinary account, the second ordinary account, and the third ordinary account are used to indicate different levels of account risk, the first ordinary account has the lowest risk, and the third ordinary account has the highest risk.
  • step S240 divides the account risk level according to the account type, and may include: when the account type is a secure account or a first normal account, the account is divided into a low risk account; when the account type is a second normal account, The account is divided into medium risk accounts; when the account type is a new account or a third ordinary account, the account is divided into high risk accounts. It can be understood that the correspondence between the account type and the account risk level can be set according to actual needs, and is not limited thereto.
  • the account type may be determined according to the historical record data, and the account risk level may be divided according to the account type, so that the business risk assessment may be performed according to the account risk level, thereby improving the accuracy of the business risk assessment, thereby effectively controlling the business risk.
  • Business security is guaranteed when the identity of the customer cannot be verified directly.
  • step S260 the business risk level is determined according to the account risk level and the accumulated returned service value, including the following steps:
  • Step S502 when the accumulated return service value is less than the first threshold or the account is a low risk account, it is determined that the business risk level is a low risk service.
  • the server may determine a business risk level that matches the account risk level and the cumulative returned service value according to a preset configuration table. In this embodiment, when the accumulated return service value is less than the first threshold or the account is a low risk account, the server may determine that the service risk level is a low risk service, where the first threshold may be set according to actual needs, for example, 1000. Renminbi.
  • Step S504 When the accumulated return service value is greater than or equal to the first threshold and less than or equal to the second threshold, and the account is a medium risk account, determine that the business risk level is a medium risk service.
  • the server can determine the business risk level as the medium risk level.
  • Step S506 when the business risk level corresponding to the account risk level and the accumulated return service value is not a low risk level service or a medium risk level service, the business risk level is determined to be a high risk business.
  • the determining condition of the business risk level may include other judgment conditions in addition to the accumulated return service value and the account risk level of the first preset time of the account, for example, determining whether to make a call within the first preset time.
  • the change wherein the telephone change refers to the change of the account information or the policy information by the customer by telephone.
  • the risk of returning the service may be increased, and may be adjusted according to actual needs. Configuration table.
  • the business risk level is not limited to the above-mentioned low-risk business, medium-risk business and high-risk business, and can also be expressed in other ways, such as A, B, C, D, E risk level services, etc., for different Business can be changed by adjusting the configuration table to change the business risk level and corresponding judgment conditions.
  • the business risk level may be determined according to the accumulated return service value and the account risk level of the account within the first preset time, and the risk of the business may be evaluated, thereby effectively controlling the business risk, and the customer may not be directly verified. When it comes to identity, it guarantees business security.
  • a service data processing apparatus including an extraction module 610, a historical data acquisition module 620, an account type determination module 630, a division module 640, a calculation module 650, and a business risk determination module. 660.
  • the extracting module 610 is configured to obtain the returned service data, and extract the account information from the returned service data.
  • the historical data obtaining module 620 is configured to acquire historical record data according to the account information.
  • the account type determining module 630 is configured to determine an account type according to the history data.
  • the dividing module 640 is configured to divide the account risk level according to the account type.
  • the calculating module 650 is configured to calculate, according to the historical record data, the accumulated return service value of the account within the first preset time.
  • the business risk determination module 660 is configured to determine a business risk level according to the account risk level and the accumulated return service value.
  • the service data processing device extracts account information from the returned service data, acquires historical record data according to the account information, determines an account type according to the account information and the historical record data, and divides the account risk level according to the account type, and calculates the account at the first preset. After the accumulated return value of the business in the time, the business risk level can be determined according to the account risk level and the accumulated returned business value, and the risk of the business can be evaluated, thereby effectively controlling the business risk, and ensuring the business security when the identity of the customer cannot be directly verified. Sex.
  • the account type includes a security account, a general account, and a brand new account
  • the general account includes a first general account, a second general account, and a third general account.
  • the account type determination module 630 includes a secure account unit 631, a brand new account unit 633, a normal account unit 635, a record acquisition unit 637, and a time acquisition unit 639.
  • the security account unit 631 is configured to determine that the account type is a security account when the history data includes a record for processing the service through the cabinet channel or the remote machine channel.
  • the new account unit 633 is configured to determine that the account type is a brand new account when the account type is not a secure account and the history data is empty.
  • the ordinary account unit 635 is configured to determine that the account type is a normal account when the account type is not a secure account or a brand new account.
  • the record obtaining unit 637 is configured to obtain a payment service record according to the history data.
  • the common account unit 635 is further configured to determine, according to the payment service record, whether the time for continuously processing the payment service is greater than the second preset time, and the time for continuously processing the payment service is greater than the second preset time, and the service type paid is a preset type. , then determine the account type as the first normal account.
  • the time acquisition unit 639 is configured to acquire the first registration time from the history data.
  • the common account unit 635 is further configured to determine that the account type is the third normal account when the account information carries the error data identifier, or the time interval between the first registration time and the current return service is less than the third preset time.
  • the normal account unit 635 is further configured to determine that the account type is the second normal account when the account type is neither the first normal account nor the third normal account.
  • the account type can be determined according to the historical record data, and the account type is refined to make the business risk assessment more accurate.
  • the dividing module 640 includes a first dividing unit 642, a second dividing unit 644, and a third dividing unit 646.
  • the first dividing unit 642 is configured to divide the account into a low risk account when the account type is a security account or a first general account.
  • the second dividing unit 644 is configured to divide the account into a medium risk account when the account type is the second general account.
  • the third dividing unit 646 is configured to divide the account into a high-risk account when the account type is a brand new account or a third general account.
  • the account type may be determined according to the historical record data, and the account risk level may be divided according to the account type, so that the business risk assessment may be performed according to the account risk level, thereby improving the accuracy of the business risk assessment, thereby effectively controlling the business risk.
  • Business security is guaranteed when the identity of the customer cannot be verified directly.
  • the business risk determination module 660 includes a first determining unit 662, a second determining unit 664, and a third determining unit 666.
  • the first determining unit 662 is configured to determine that the service risk level is a low risk service when the accumulated return service value is less than the first threshold or the account is a low risk account.
  • the second determining unit 664 is configured to determine that the service risk level is a medium risk service when the accumulated return service value is greater than or equal to the first threshold and less than or equal to the second threshold, and the account is a medium risk account.
  • the third determining unit 666 is configured to determine that the business risk level is a high-risk service when the business risk level corresponding to the account risk level and the accumulated return service value is not a low-risk service or a medium-risk service.
  • the business risk level may be determined according to the accumulated return service value and the account risk level of the account within the first preset time, and the risk of the business may be evaluated, thereby effectively controlling the business risk, and the customer may not be directly verified. When it comes to identity, it guarantees business security.
  • Each of the above-described business data processing devices may be implemented in whole or in part by software, hardware, and combinations thereof.
  • the above modules may be embedded in the hardware in the processor or in the memory in the server, or may be stored in the memory in the server, so that the processor calls the corresponding operations of the above modules.
  • a computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executed by one or more processors such that one or more processors implement any of the present application
  • the steps of the business data processing method provided in the embodiment are not limited to:
  • One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to be implemented in any one embodiment of the present application The steps of the business data processing method provided. .
  • Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory can include random access memory (RAM) or external cache memory.
  • RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • Synchlink DRAM SLDRAM
  • Memory Bus Radbus
  • RDRAM Direct RAM
  • DRAM Direct Memory Bus Dynamic RAM
  • RDRAM Memory Bus Dynamic RAM

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种业务数据处理方法，包括：获取退回业务数据，并从所述退回业务数据中提取账户信息；根据所述账户信息获取历史记录数据；根据所述历史记录数据确定账户类型；根据所述账户类型划分账户风险等级；根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；根据所述账户风险等级及累计退回业务数值确定业务风险等级。

Description

业务数据处理方法、装置、服务器和存储介质
相关申请的交叉引用
本申请要求于2017年04月07日提交中国专利局，申请号为2017102249192，申请名称为“业务数据处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及一种业务数据处理方法、装置、服务器和存储介质。
背景技术
保险，是指投保人根据合同约定，向保险人支付保险费，保险人对于合同约定的可能发生的事故因其发生所造成的财产损失承担赔偿保险金责任。通常地，客户办理保险业务可选择到柜台亲自办理，或是填写申请材料再交回业务人员进行录入。对于填写申请材料再进行录入等渠道，由于无法直接对客户本人的身份进行验证，特别是支付保险金等业务，可能存在不法人员冒领保险金等骗保行为，无法保障安全性。
发明内容
根据本申请公开的各种实施例，提供一种业务数据处理方法、装置、服务器和存储介质。
一种业务数据处理方法，包括：
获取退回业务数据，并从所述退回业务数据中提取账户信息；
根据所述账户信息获取历史记录数据；
根据所述历史记录数据确定账户类型；
根据所述账户类型划分账户风险等级；
根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及
根据所述账户风险等级及累计退回业务数值确定业务风险等级。
一种业务数据处理装置，包括：
提取模块，用于获取退回业务数据，并从所述退回业务数据中提取账户信息；
历史数据获取模块，用于根据所述账户信息获取历史记录数据；
账户类型确定模块，用于根据所述历史记录数据确定账户类型；
划分模块，用于根据所述账户类型划分账户风险等级；
计算模块，用于根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及
业务风险确定模块，用于根据所述账户风险等级及累计退回业务数值确定业务风险等级。
一种服务器，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行以下步骤：获取退回业务数据，并从所述退回业务数据中提取账户信息；根据所述账户信息获取历史记录数据；根据所述历史记录数据确定账户类型；根据所述账户类型划分账户风险等级；根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及根据所述账户风险等级及累计退回业务数值确定业务风险等级。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：获取退回业务数据，并从所述退回业务数据中提取账户信息；根据所述账户信息获取历史记录数据；根据所述历史记录数据确定账户类型；根据所述账户类型划分账户风险等级；根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及根据所述账户风险等级及累计退回业务数值确定业务风险等级。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中服务器的框图。
图2为根据一个或多个实施例中业务数据处理的流程示意图。
图3为根据一个或多个实施例中根据历史记录数据确定账户类型的流程示意图。
图4为另一个实施例中根据历史记录数据确定账户类型的流程示意图。
图5为根据一个或多个实施例中根据账户风险等级及累计退回业务数值确定业务风险等级的流程示意图。
图6为根据一个或多个实施例中业务数据处理装置的框图。
图7为根据一个或多个实施例中账户类型确定模块的框图。
图8为根据一个或多个实施例中划分模块的框图。
图9为根据一个或多个实施例中业务风险确定模块框图。
图10为根据一个或多个实施例中业务数据处理方法的应用环境图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本 申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
本申请提供的业务数据处理方法，可以应用于如图10所示的应用环境中。终端1002与服务器1004通过网络进行通信。服务器1004获取退回业务数据，并从所述退回业务数据中提取账户信息；根据所述账户信息获取历史记录数据；根据所述历史记录数据确定账户类型；根据所述账户类型划分账户风险等级；根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；服务器1004根据所述账户风险等级及累计退回业务数值确定业务风险等级。终端1002可以但不限于是各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备，服务器1004可以用独立的服务器或者是多个服务器组成的服务器集群来实现。
图1为一个实施例中服务器的框图。如图1所示，该服务器包括通过系统总线连接的处理器、存储器和网络接口。该服务器的存储器包括非易失性存储介质和内存储器。在其中一个实施例中，非易失性存储介质可以是非易失性计算机可读存储介质。该服务器的非易失性存储介质存储有操作系统、数据库和计算机可读指令，数据库中存储有退回业务数据、账户信息及历史记录数据等，该计算机可读指令用于实现本申请实施例中提供的适用于服务器的一种业务数据处理方法。该服务器的处理器用于提供计算和控制能力，支撑整个服务器的运行。该服务器的内存储器为非易失性存储介质中的操作系统和计算机可读指令提供高速缓存的运行环境。该服务器的网络接口用于据以与外部的终端通过网络连接通信，比如接收终端发送的退回业务操作请求等。服务器可以用独立的服务器或者是多个服务器组成的服务器集群来实现。本领域技术人员可以理解，图1中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的服务器的限定，具体地服务器可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
如图2所示，在其中一个实施例中，提供了一种业务数据处理方法，现以该方法应用于图10或图1所示的服务器为例进行举例说明，包括以下步骤：
步骤S210，获取退回业务数据，并从退回业务数据中提取账户信息。
退回业务，指的是退费业务，由银行或保险公司等向客户退还一定的金额，例如保险公司向客户支付保险金，或是返回保险费用等。在本实施例中，客户可通过非亲办渠道办理退回业务，非亲办渠道指的是无法直接验证客户本人真实身份的渠道，可包括填写纸质申请资料再由业务人员进行录入、直接在相关网站填写电子申请材料并提交到服务器，或通过电话进行申请等。
当客户通过非亲办渠道办理退回业务时，终端采集了客户的退回业务数据后，可向服务器发送退回业务操作请求，并将退回业务数据发送至服务器进行处理。服务器接收终端发送的退回业务操作请求，可根据退回业务操作请求获取退回业务数据，退回业务数据可包括办理的账号信息、退回业务种类、退回金额等，其中，账号信息可包括账号ID (idenfication，身份标识)、账号名称等。
步骤S220，根据账户信息获取历史记录数据。
服务器可从退回业务数据中提取账户信息，可将账户信息中的账号ID作为数据库中的key(键)进行查询，得到匹配的value(值)，从而获取与账号ID匹配的历史记录数据。历史记录数据记录有与账号ID关联的业务办理信息，包括办理时间、办理地点、业务种类、办理渠道、业务明细等。例如，将账号ID59845321作为key，在数据库中查找对应的value，可包括TIME＝2016-07-25，ADD＝Shenzhen，SERVICE_TYPE＝pay，CHANNEL＝counter，MONEY＝1000RMB(人民币)，表示该账号ID在2016年7月25日时，在深圳办理缴纳业务，办理渠道为柜面办理，缴纳金额为1000人民币。
步骤S230，根据历史记录数据确定账户类型。
在其中一个实施例中，账户类型可包括安全账户、全新账户及普通账户，其中，安全账户指的是已经验证过客户身份安全级别特别高的账户，全新账户指的是没有办理过业务的账户，普通账户指的是已办理过业务但未验证过客户身份的账户，可按照账户的安全程度设定账户类型，在本实施例中，账户的安全程度为安全账户＞普通账户＞全新账户。服务器获取与账号ID匹配的历史记录数据，可根据历史记录数据确定本次办理退回业务的账户类型。
步骤S240，根据账户类型划分账户风险等级。
服务器可根据预先设定的账户类型与账户风险等级的对应关系，划分本次办理退回业务的账户风险等级，可根据实际需求对账户风险等级进行划分，并设定每个账户风险等级对应的账户类型。例如，可设定账户风险等级包括低风险账户、中风险账户及高风险账户，低风险账户对应安全账户，中风险账户对应普通账户，高风险账户对应全新账户等，但不限于此。
步骤S250，根据历史记录数据计算账户在第一预设时间内的累计退回业务数值。
服务器可根据业务种类及办理时间等字段，从历史记录数据中获取账户在第一预设时间内办理过的退回业务数据，例如，获取账户在90天内办理过的退回业务数据。服务器可从第一预设时间内办理过的退回业务数据中提取退回业务数值，并进行累加计算，得到累计退回业务数值。
步骤S260，根据账户风险等级及累计退回业务数值确定业务风险等级。
服务器可根据账户风险等级及账户在第一预设时间内的累计退回业务数值，确定业务风险等级，可预先设定业务风险等级及对应的判断条件，并将业务风险等级及对应的判断条件转化为匹配的字段及配置值存储在配置表中。例如，业务风险等级为低风险业务，对应的判断条件包括低风险账户及累计退回业务数值小于1000人民币，则可转化为如表1所示的配置表中的字段及配置值。
表1
Sum_money Grade_account risk Grade_business risk
＜1000RMB LOW LOW
其中，Sum_money表示累计退回业务数值，Grade_account risk表示账户风险等级，Grade_business risk表示业务风险等级。
服务器确定了业务风险等级后，可在本次的退回业务数据添加与业务风险等级对应的标记，方便退回业务数据进入下一处理流程节点时，业务人员可根据业务风险等级进行相应处理，例如本次退回业务为高风险业务，则需通过视频或柜面等方式对客户进行身份验证等，但不限于此，能够有效对业务风险进行管控。
上述业务数据处理方法，从退回业务数据中提取账户信息，根据账户信息获取历史记录数据，根据账户信息及历史记录数据确定账户类型，并根据账户类型划分账户风险等级，计算账户在第一预设时间内的累计退回业务数值后，可根据账户风险等级及累计退回业务数值确定业务风险等级，能够对业务的风险进行评估，从而有效管控业务风险，在无法直接验证客户本人身份时，保障业务安全性。
如图3所示，在其中一个实施例中，步骤S230根据历史记录数据确定账户类型，包括以下步骤：
步骤S302，当历史记录数据中包含通过柜面渠道或远程机渠道办理业务的记录，则确定账户类型为安全账户。
服务器可根据历史记录数据的办理渠道字段判断历史记录数据中是否包含通过柜面渠道或通过远程机渠道办理的历史记录，其中，远程机渠道指的是客户登录远程的主机，通过远程主机与柜面的业务人员进行连接，并通过视频通话等方式办理业务。当历史记录数据中包含通过柜面渠道或远程机渠道办理业务的记录，则说明已对与账户关联的客户进行身份验证，可确定账户类型为安全账户。
步骤S304，当账户类型不是安全账户，且历史记录数据为空，则确定账户类型为全新账户。
当账户类型不是安全账户，服务器可进一步判断历史记录数据是否为空，若是，则说明账户之前没有办理过相关业务，可确定账户类型为全新账户。
步骤S306，当账户类型不是安全账户也不是全新账户，则确定账户类型为普通账户。
在其中一个实施例中，服务器确定账户类型为普通账户，可进一步对普通账户进行划分，普通账户可包括第一普通账户、第二普通账户及第三普通账户，不同类型的普通账户对应不同的特征，可根据实际需求进行设定，进一步对账户类型进行细化，使业务风险评估更为精准。
如图4所示，在其中一个实施例中，在步骤S306当账户类型不是安全账户也不是全新账户，则确定账户类型为普通账户之后，还包括以下步骤：
步骤S402，根据历史记录数据获取缴纳业务记录。
步骤S404，根据缴纳业务记录判断持续办理缴纳业务的时间是否大于第二预设时间，当持续办理缴纳业务的时间大于第二预设时间，且缴纳的业务类型为预设类型，则确定账 户类型为第一普通账户。
服务器可从历史记录数据中选取业务种类为缴纳业务的记录数据，并根据各缴纳业务记录中的办理时间判断持续办理缴纳业务的时间是否大于第二预设时间，可以理解地，第二预设时间可根据实际需求进行设定，例如，持续办理缴纳业务的时间大于2年或3年等。当持续办理缴纳业务的时间大于第二预设时间，则服务器可进一步判断缴纳的业务类型是否为预设类型，预设类型可根据实际需求提前进行设定，例如首期保费、续期保费、自垫还款等，其中，首期保费指的是客户参加保险后第一年所缴纳的保险费，续期保费指的是首期保险费后分期缴纳的保险费，自垫还款指的是客户没有按照保险合同规定的时期缴纳续期保费，由保险公司在宽限期内垫负的保险费。当持续办理缴纳业务的时间大于第二预设时间，且缴纳的业务类型为预设类型，则服务器可确定账户类型为第一普通账户。
步骤S406，从历史记录数据获取首次登记时间。
首次登记时间即为账户首次办理业务时间，服务器可从历史记录数据中选取最早的办理时间作为账户的首次登记时间。
步骤S408，当账户信息携带错误资料标识，或首次登记时间与本次退回业务的时间间隔小于第三预设时间，则确定账户类型为第三普通账户。
当账户类型不是第一普通账户，服务器可检测账户信息中是否携带错误资料标识，其中，错误资料标识用于标记账户信息中存在有误信息且未进行更正，或是服务器判断账户的首次登记时间与本次退回业务的时间间隔是否小于第三预设时间，例如，小于1年或小于14个月等。当账户信息携带错误资料标识，或首次登记时间与本次退回业务的时间间隔小于第三预设时间，则服务器可确定账户类型为第三普通账户。
步骤S410，当账户类型既不是第一普通账户也不是第三普通账户，则确定账户类型为第二普通账户。
第一普通账户、第二普通账户及第三普通账户用于表示不同程度的账户风险，第一普通账户的风险最低，而第三普通账户的风险最高。
在其中一个实施例中，步骤S240根据账户类型划分账户风险等级，可包括：当账户类型为安全账户或第一普通账户，则将账户划分为低风险账户；当账户类型为第二普通账户，则将账户划分为中风险账户；当账户类型为全新账户或第三普通账户，则将账户划分为高风险账户。可以理解地，账户类型与账户风险等级的对应关系可根据实际需求进行设定，并不限于此。
在本实施例中，可根据历史记录数据确定账户类型，并根据账户类型划分账户风险等级，从而可根据账户风险等级进行业务风险评估，可提高业务风险评估准确性，从而有效管控业务风险，在无法直接验证客户本人身份时，保障业务安全性。
如图5所示，在其中一个实施例中，步骤S260，根据账户风险等级及累计退回业务数值确定业务风险等级，包括以下步骤：
步骤S502，当累计退回业务数值小于第一阈值或账户为低风险账户，则确定业务风 险等级为低风险业务。
服务器可根据预设的配置表，确定与账户风险等级及累计退回业务数值匹配的业务风险等级。在本实施例中，当累计退回业务数值小于第一阈值或账户为低风险账户，则服务器可确定业务风险等级为低风险业务，其中，第一阈值可根据实际需求进行设定，例如，1000人民币。
步骤S504，当累计退回业务数值大于或等于第一阈值且小于或等于第二阈值，且账户为中风险账户，则确定业务风险等级为中风险业务。
若账户在第一预设时间内的累计退回业务数值大于或等于第一阈值，同时小于或等于第二阈值，例如，累计退回业务数值≥1000人民币，且≤8000人民币，且账户为中风险账户，则服务器可确定业务风险等级为中风险等级。
步骤S506，当账户风险等级及累计退回业务数值对应的业务风险等级不是低风险等级业务也不是中风险等级业务，则确定业务风险等级为高风险业务。
可以理解地，确定业务风险等级的判断条件除了包括账户第一预设时间的累计退回业务数值及账户风险等级外，还可包含其它的判断条件，例如判断在第一预设时间内是否进行电话变更，其中，电话变更指的是客户通过电话对账户信息或保单信息等进行变更，当在第一预设时间内进行过电话变更，可能会增加本次退回业务的风险，可根据实际需求调整配置表。此外，业务风险等级并不仅限于上述的低风险业务、中风险业务及高风险业务，也可以用其它的方式进行表示，例如A、B、C、D、E风险等级业务等，针对于不同的业务，可通过调整配置表即可变更业务风险等级及对应的判断条件，操作更为简便。
在本实施例中，可根据账户在第一预设时间内的累计退回业务数值及账户风险等级确定业务风险等级，能够对业务的风险进行评估，从而有效管控业务风险，在无法直接验证客户本人身份时，保障业务安全性。
应该理解的是，虽然图2-5的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2-5中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
如图6所示，在其中一个实施例中，提供一种业务数据处理装置，包括提取模块610、历史数据获取模块620、账户类型确定模块630、划分模块640、计算模块650及业务风险确定模块660。
提取模块610，用于获取退回业务数据，并从退回业务数据中提取账户信息。
历史数据获取模块620，用于根据账户信息获取历史记录数据。
账户类型确定模块630，用于根据历史记录数据确定账户类型。
划分模块640，用于根据账户类型划分账户风险等级。
计算模块650，用于根据历史记录数据计算账户在第一预设时间内的累计退回业务数值。
业务风险确定模块660，用于根据账户风险等级及累计退回业务数值确定业务风险等级。
上述业务数据处理装置，从退回业务数据中提取账户信息，根据账户信息获取历史记录数据，根据账户信息及历史记录数据确定账户类型，并根据账户类型划分账户风险等级，计算账户在第一预设时间内的累计退回业务数值后，可根据账户风险等级及累计退回业务数值确定业务风险等级，能够对业务的风险进行评估，从而有效管控业务风险，在无法直接验证客户本人身份时，保障业务安全性。
在其中一个实施例中，账户类型包括安全账户、普通账户及全新账户，普通账户包括第一普通账户、第二普通账户及第三普通账户。如图7所示，账户类型确定模块630包括安全账户单元631、全新账户单元633、普通账户单元635、记录获取单元637及时间获取单元639。
安全账户单元631，用于当历史记录数据中包含通过柜面渠道或远程机渠道办理业务的记录，则确定账户类型为安全账户。
全新账户单元633，用于当账户类型不是安全账户，且历史记录数据为空，则确定账户类型为全新账户。
普通账户单元635，用于当账户类型不是安全账户也不是全新账户，则确定所述账户类型为普通账户。
记录获取单元637，用于根据历史记录数据获取缴纳业务记录。
普通账户单元635，还用于根据缴纳业务记录判断持续办理缴纳业务的时间是否大于第二预设时间，当持续办理缴纳业务的时间大于第二预设时间，且缴纳的业务类型为预设类型，则确定账户类型为第一普通账户。
时间获取单元639，用于从历史记录数据获取首次登记时间。
普通账户单元635，还用于当账户信息携带错误资料标识，或首次登记时间与本次退回业务的时间间隔小于第三预设时间，则确定账户类型为第三普通账户。
普通账户单元635，还用于当账户类型既不是第一普通账户也不是第三普通账户，则确定账户类型为第二普通账户。
在本实施例中，可根据历史记录数据确定账户类型，并对账户类型进行细化，使业务风险评估更为精准。
如图8所示，在其中一个实施例中，划分模块640包括第一划分单元642、第二划分单元644及第三划分单元646。
第一划分单元642，用于当账户类型为安全账户或第一普通账户，则将账户划分为低风险账户。
第二划分单元644，用于当账户类型为第二普通账户，则将账户划分为中风险账户。
第三划分单元646，用于当账户类型为全新账户或第三普通账户，则将账户划分为高风险账户。
在本实施例中，可根据历史记录数据确定账户类型，并根据账户类型划分账户风险等级，从而可根据账户风险等级进行业务风险评估，可提高业务风险评估准确性，从而有效管控业务风险，在无法直接验证客户本人身份时，保障业务安全性。
如图9所示，在其中一个实施例中，业务风险确定模块660包括第一确定单元662、第二确定单元664及第三确定单元666。
第一确定单元662，用于当累计退回业务数值小于第一阈值或账户为低风险账户，则确定业务风险等级为低风险业务。
第二确定单元664，用于当累计退回业务数值大于或等于第一阈值且小于或等于第二阈值，且账户为中风险账户，则确定业务风险等级为中风险业务。
第三确定单元666，用于当账户风险等级及累计退回业务数值对应的业务风险等级不是低风险业务也不是中风险业务，则确定业务风险等级为高风险业务。
在本实施例中，可根据账户在第一预设时间内的累计退回业务数值及账户风险等级确定业务风险等级，能够对业务的风险进行评估，从而有效管控业务风险，在无法直接验证客户本人身份时，保障业务安全性。
关于业务数据处理装置的具体限定可以参见上文中对于业务数据处理方法的限定，在此不再赘述。上述业务数据处理装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于服务器中的处理器中，也可以以软件形式存储于服务器中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
一种计算机设备，包括存储器和一个或多个处理器，存储器中储存有计算机可读指令，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器实现本申请任意一个实施例中提供的业务数据处理方法的步骤。
一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器实现本申请任意一个实施例中提供的业务数据处理方法的步骤。。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM (DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种业务数据处理方法，包括：
    获取退回业务数据，并从所述退回业务数据中提取账户信息；
    根据所述账户信息获取历史记录数据；
    根据所述历史记录数据确定账户类型；
    根据所述账户类型划分账户风险等级；
    根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及
    根据所述账户风险等级及累计退回业务数值确定业务风险等级。
  2. 根据权利要求1所述的方法，其特征在于，所述账户类型包括安全账户、普通账户及全新账户；所述根据所述历史记录数据确定账户类型，包括：
    当所述历史记录数据中包含通过柜面渠道或远程机渠道办理业务的记录，则确定账户类型为安全账户；
    当所述账户类型不是安全账户，且所述历史记录数据为空，则确定所述账户类型为全新账户；及
    当所述账户类型不是安全账户也不是全新账户，则确定所述账户类型为普通账户。
  3. 根据权利要求2所述的方法，其特征在于，所述普通账户包括第一普通账户、第二普通账户及第三普通账户；
    在所述当所述账户类型不是安全账户也不是全新账户，则所述账户类型为普通账户的步骤之后，还包括：
    根据所述历史记录数据获取缴纳业务记录；
    根据所述缴纳业务记录判断持续办理缴纳业务的时间是否大于第二预设时间，当所述持续办理缴纳业务的时间大于所述第二预设时间，且缴纳的业务类型为预设类型，则确定所述账户类型为第一普通账户；
    从所述历史记录数据获取首次登记时间；
    当所述账户信息携带错误资料标识，或所述首次登记时间与本次退回业务的时间间隔小于第三预设时间，则确定所述账户类型为第三普通账户；及
    当所述账户类型既不是第一普通账户也不是第三普通账户，则确定所述账户类型为第二普通账户。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述账户类型划分账户风险等级，包括：
    当所述账户类型为安全账户或第一普通账户，则将账户划分为低风险账户；
    当所述账户类型为第二普通账户，则将所述账户划分为中风险账户；及
    当所述账户类型为全新账户或第三普通账户，则将所述账户划分为高风险账户。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述根据所述账户风险等级及累计退回业务数值确定业务风险等级，包括：
    当所述累计退回业务数值小于第一阈值或账户为低风险账户，则确定业务风险等级为低风险业务；
    当所述累计退回业务数值大于或等于所述第一阈值且小于或等于第二阈值，且所述账户为中风险账户，则确定所述业务风险等级为中风险业务；及
    当所述账户风险等级及累计退回业务数值对应的业务风险等级不是低风险业务也不是中风险业务，则确定所述业务风险等级为高风险业务。
  6. 一种业务数据处理装置，包括：
    提取模块，用于获取退回业务数据，并从所述退回业务数据中提取账户信息；
    历史数据获取模块，用于根据所述账户信息获取历史记录数据；
    账户类型确定模块，用于根据所述历史记录数据确定账户类型；
    划分模块，用于根据所述账户类型划分账户风险等级；
    计算模块，用于根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及
    业务风险确定模块，用于根据所述账户风险等级及累计退回业务数值确定业务风险等级。
  7. 根据权利要求6所述的装置，其特征在于，所述账户类型包括安全账户、普通账户及全新账户；
    所述账户类型确定模块，包括：
    安全账户单元，用于当所述历史记录数据中包含通过柜面渠道或远程机渠道办理业务的记录，则确定账户类型为安全账户；
    全新账户单元，用于当所述账户类型不是安全账户，且所述历史记录数据为空，则确定所述账户类型为全新账户；及
    普通账户单元，用于当所述账户类型不是安全账户也不是全新账户，则确定所述账户类型为普通账户。
  8. 根据权利要求7所述的装置，其特征在于，所述普通账户包括第一普通账户、第二普通账户及第三普通账户；
    所述账户类型确定模块，还包括：
    记录获取单元，用于根据所述历史记录数据获取缴纳业务记录；
    所述普通账户单元，还用于根据所述缴纳业务记录判断持续办理缴纳业务的时间是否大于第二预设时间，当所述持续办理缴纳业务的时间大于所述第二预设时间，且缴纳的业务类型为预设类型，则确定所述账户类型为第一普通账户；
    时间获取单元，用于从所述历史记录数据获取首次登记时间；
    所述普通账户单元，还用于当所述账户信息携带错误资料标识，或所述首次登记时间与本次退回业务的时间间隔小于第三预设时间，则确定所述账户类型为第三普通账户；及
    所述普通账户单元，还用于当所述账户类型既不是第一普通账户也不是第三普通账 户，则确定所述账户类型为第二普通账户。
  9. 根据权利要求8所述的装置，其特征在于，所述划分模块，包括：
    第一划分单元，用于当所述账户类型为安全账户或第一普通账户，则将账户划分为低风险账户；
    第二划分单元，用于当所述账户类型为第二普通账户，则将所述账户划分为中风险账户；及
    第三划分单元，用于当所述账户类型为全新账户或第三普通账户，则将所述账户划分为高风险账户。
  10. 根据权利要求6至9任一所述的装置，其特征在于，所述业务风险确定模块，包括：
    第一确定单元，用于当所述累计退回业务数值小于第一阈值或账户为低风险账户，则确定业务风险等级为低风险业务；
    第二确定单元，用于当所述累计退回业务数值大于或等于所述第一阈值且小于或等于第二阈值，且所述账户为中风险账户，则确定所述业务风险等级为中风险业务；及
    第三确定单元，用于当所述账户风险等级及累计退回业务数值对应的业务风险等级不是低风险业务也不是中风险业务，则确定所述业务风险等级为高风险业务。
  11. 一种服务器，包括存储器和一个或多个处理器，存储器中储存有计算机可读指令，计算机可读指令被处理器执行时，使得一个或多个处理器执行以下步骤：
    获取退回业务数据，并从所述退回业务数据中提取账户信息；
    根据所述账户信息获取历史记录数据；
    根据所述历史记录数据确定账户类型；
    根据所述账户类型划分账户风险等级；
    根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及
    根据所述账户风险等级及累计退回业务数值确定业务风险等级。
  12. 根据权利要求11所述的服务器，其特征在于，所述账户类型包括安全账户、普通账户及全新账户；所述处理器执行所述计算机可读指令时还执行以下步骤：
    当所述历史记录数据中包含通过柜面渠道或远程机渠道办理业务的记录，则确定账户类型为安全账户；
    当所述账户类型不是安全账户，且所述历史记录数据为空，则确定所述账户类型为全新账户；及
    当所述账户类型不是安全账户也不是全新账户，则确定所述账户类型为普通账户。
  13. 根据权利要求12所述的服务器，其特征在于，所述普通账户包括第一普通账户、第二普通账户及第三普通账户；所述处理器执行所述计算机可读指令时还执行以下步骤：
    根据所述历史记录数据获取缴纳业务记录；
    根据所述缴纳业务记录判断持续办理缴纳业务的时间是否大于第二预设时间，当所述 持续办理缴纳业务的时间大于所述第二预设时间，且缴纳的业务类型为预设类型，则确定所述账户类型为第一普通账户；
    从所述历史记录数据获取首次登记时间；
    当所述账户信息携带错误资料标识，或所述首次登记时间与本次退回业务的时间间隔小于第三预设时间，则确定所述账户类型为第三普通账户；及
    当所述账户类型既不是第一普通账户也不是第三普通账户，则确定所述账户类型为第二普通账户。
  14. 根据权利要求13所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：
    当所述账户类型为安全账户或第一普通账户，则将账户划分为低风险账户；
    当所述账户类型为第二普通账户，则将所述账户划分为中风险账户；及
    当所述账户类型为全新账户或第三普通账户，则将所述账户划分为高风险账户。
  15. 根据权利要求11至14所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：
    当所述累计退回业务数值小于第一阈值或账户为低风险账户，则确定业务风险等级为低风险业务；
    当所述累计退回业务数值大于或等于所述第一阈值且小于或等于第二阈值，且所述账户为中风险账户，则确定所述业务风险等级为中风险业务；及
    当所述账户风险等级及累计退回业务数值对应的业务风险等级不是低风险业务也不是中风险业务，则确定所述业务风险等级为高风险业务。
  16. 一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
    获取退回业务数据，并从所述退回业务数据中提取账户信息；
    根据所述账户信息获取历史记录数据；
    根据所述历史记录数据确定账户类型；
    根据所述账户类型划分账户风险等级；
    根据所述历史记录数据计算账户在第一预设时间内的累计退回业务数值；及
    根据所述账户风险等级及累计退回业务数值确定业务风险等级。
  17. 根据权利要求16所述的存储介质，其特征在于，所述账户类型包括安全账户、普通账户及全新账户；所述计算机可读指令被所述处理器执行时还执行以下步骤：
    所述根据所述历史记录数据确定账户类型，包括：
    当所述历史记录数据中包含通过柜面渠道或远程机渠道办理业务的记录，则确定账户类型为安全账户；
    当所述账户类型不是安全账户，且所述历史记录数据为空，则确定所述账户类型为全新账户；及
    当所述账户类型不是安全账户也不是全新账户，则确定所述账户类型为普通账户。
  18. 根据权利要求17所述的存储介质，其特征在于，所述普通账户包括第一普通账户、第二普通账户及第三普通账户；所述计算机可读指令被所述处理器执行时还执行以下步骤：
    在所述当所述账户类型不是安全账户也不是全新账户，则所述账户类型为普通账户的步骤之后，还包括：
    根据所述历史记录数据获取缴纳业务记录；
    根据所述缴纳业务记录判断持续办理缴纳业务的时间是否大于第二预设时间，当所述持续办理缴纳业务的时间大于所述第二预设时间，且缴纳的业务类型为预设类型，则确定所述账户类型为第一普通账户；
    从所述历史记录数据获取首次登记时间；
    当所述账户信息携带错误资料标识，或所述首次登记时间与本次退回业务的时间间隔小于第三预设时间，则确定所述账户类型为第三普通账户；及
    当所述账户类型既不是第一普通账户也不是第三普通账户，则确定所述账户类型为第二普通账户。
  19. 根据权利要求18所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：
    当所述账户类型为安全账户或第一普通账户，则将账户划分为低风险账户；
    当所述账户类型为第二普通账户，则将所述账户划分为中风险账户；及
    当所述账户类型为全新账户或第三普通账户，则将所述账户划分为高风险账户。
  20. 根据权利要求16至19所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：
    当所述累计退回业务数值小于第一阈值或账户为低风险账户，则确定业务风险等级为低风险业务；
    当所述累计退回业务数值大于或等于所述第一阈值且小于或等于第二阈值，且所述账户为中风险账户，则确定所述业务风险等级为中风险业务；及
    当所述账户风险等级及累计退回业务数值对应的业务风险等级不是低风险业务也不是中风险业务，则确定所述业务风险等级为高风险业务。
PCT/CN2018/081705 2017-04-07 2018-04-03 业务数据处理方法、装置、服务器和存储介质 WO2018184520A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710224919.2 2017-04-07
CN201710224919.2A CN108257022A (zh) 2017-04-07 2017-04-07 业务数据处理方法及装置

Publications (1)

Publication Number Publication Date
WO2018184520A1 true WO2018184520A1 (zh) 2018-10-11

Family

ID=62721932

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081705 WO2018184520A1 (zh) 2017-04-07 2018-04-03 业务数据处理方法、装置、服务器和存储介质

Country Status (2)

Country Link
CN (1) CN108257022A (zh)
WO (1) WO2018184520A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108985070B (zh) * 2018-07-11 2020-07-03 阿里巴巴集团控股有限公司 风险控制方法、风险控制装置、电子设备和存储介质
CN109492885B (zh) * 2018-10-25 2024-02-09 平安医疗健康管理股份有限公司 医保风险项目分析方法装置、终端及可读介质
CN110264210B (zh) * 2019-05-06 2023-08-08 创新先进技术有限公司 账号正确性的检测方法和装置
CN111754235B (zh) * 2020-06-03 2023-05-09 支付宝(杭州)信息技术有限公司 一种资源回退方法、装置及设备
CN117011074A (zh) * 2023-07-25 2023-11-07 明亚保险经纪股份有限公司 风险预警方法及平台

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160171618A1 (en) * 2014-12-16 2016-06-16 Hartford Fire Insurance Company Calibrated underwriting system
CN106022657A (zh) * 2016-06-24 2016-10-12 深圳前海征信中心股份有限公司 信用风险的监控方法及装置
CN106503562A (zh) * 2015-09-06 2017-03-15 阿里巴巴集团控股有限公司 一种风险识别方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160171618A1 (en) * 2014-12-16 2016-06-16 Hartford Fire Insurance Company Calibrated underwriting system
CN106503562A (zh) * 2015-09-06 2017-03-15 阿里巴巴集团控股有限公司 一种风险识别方法及装置
CN106022657A (zh) * 2016-06-24 2016-10-12 深圳前海征信中心股份有限公司 信用风险的监控方法及装置

Also Published As

Publication number Publication date
CN108257022A (zh) 2018-07-06

Similar Documents

Publication Publication Date Title
WO2018184520A1 (zh) 业务数据处理方法、装置、服务器和存储介质
CN110232565B (zh) 资源清算方法、装置、计算机设备和存储介质
CN108615119B (zh) 一种异常用户的识别方法及设备
CN108304554B (zh) 文件拆分方法、装置、计算机设备和存储介质
WO2019041912A1 (zh) 理赔案件分配方法、装置、计算机设备和存储介质
WO2019100682A1 (zh) 风险评估方法、装置、计算机设备及可读存储介质
CN111769941B (zh) 一种业务处理方法、装置和综合业务服务系统
US20210326886A1 (en) Blockchain-based resource transaction methods, apparatuses, and systems
WO2020056973A1 (zh) 跨平台产品推荐方法、装置、服务器和存储介质
CN110633963A (zh) 电子票据处理方法、装置、计算机可读存储介质和设备
CN109033139B (zh) 客户信息查询方法、装置、计算机设备和存储介质
WO2019041931A1 (zh) 工作流数据的时限提醒方法、处理方法及其装置、设备
WO2019019777A1 (zh) 保单退费处理方法、装置、计算机设备和存储介质
CN112533209A (zh) 黑产识别方法及黑产识别装置
WO2019127889A1 (zh) 数据核对方法、装置、计算机设备及可读存储介质
CN109492856B (zh) 业务请求处理方法、装置、计算机设备以及存储介质
CN109598519B (zh) 车辆审核方法、装置、计算机设备和存储介质
US20220150278A1 (en) Synthetic identity signal network
WO2019200754A1 (zh) 数据传输风险评估方法、装置、计算机设备和存储介质
WO2020233310A1 (zh) 实时处理数据的异步补偿方法、装置、设备及存储介质
CN111126966A (zh) 票据审核方法、装置、计算机设备和计算机可读存储介质
CN107516213B (zh) 风险识别方法及装置
CN113051257B (zh) 一种业务数据清洗方法及装置
US20230088867A1 (en) System and Method for Secure Linking of Anonymized Data
CN110532516B (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: 18780561

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 1205A DATED 20.01.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18780561

Country of ref document: EP

Kind code of ref document: A1