WO2020108107A1 - 一种项目处理方法及装置、一种计算设备及存储介质 - Google Patents

一种项目处理方法及装置、一种计算设备及存储介质 Download PDF

Info

Publication number
WO2020108107A1
WO2020108107A1 PCT/CN2019/110469 CN2019110469W WO2020108107A1 WO 2020108107 A1 WO2020108107 A1 WO 2020108107A1 CN 2019110469 W CN2019110469 W CN 2019110469W WO 2020108107 A1 WO2020108107 A1 WO 2020108107A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
project
case
amount
preset
Prior art date
Application number
PCT/CN2019/110469
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 WO2020108107A1 publication Critical patent/WO2020108107A1/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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • 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

  • This application relates to the technical field of insurance, and in particular to a method and device for processing items, a computing device and a storage medium.
  • the embodiments of the present specification provide an item processing method and device, a computing device, and a storage medium to solve the technical defects in the prior art.
  • an embodiment of the present specification discloses a project processing method, including:
  • an item processing device including:
  • the first receiving module is configured to receive a user's project participation request, where the project participation request carries user identification information;
  • a first acquisition module configured to acquire the first user information and the second user information of the user based on the user identification information
  • the first review module is configured to perform an access review on the user based on the user's first user information and second user information and give an audit result, where the review result includes whether the user is allowed to participate in the project;
  • the first binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user if the result of the review is to allow the user to participate in the project.
  • an embodiment of the present specification discloses a computing device, including a memory, a processor, and computer instructions stored on the memory and executable on the processor.
  • the processor executes the instruction
  • the instruction is processed
  • the steps of the item processing method described above are realized.
  • an embodiment of the present specification discloses a computer-readable storage medium that stores computer instructions that when executed by a processor implement the steps of the item processing method described above.
  • This specification provides a project processing method and device, a computing device, and a storage medium, wherein the method includes receiving a user's request for participating in a project, and the participating project request carries user identification information; based on the user identification information Obtain the first user information and the second user information of the user; perform an access audit on the user based on the first user information and the second user information of the user and give an audit result, where the audit result includes whether to allow the The user participates in the project; when the result of the review is to allow the user to participate in the project, establish a binding relationship between the user identification information and the account corresponding to the user.
  • FIG. 1 is a schematic diagram of a computing device provided by an embodiment of this specification.
  • FIG. 3 is a flowchart of an item processing method provided by an embodiment of this specification
  • FIG. 8 is a schematic structural diagram of an item processing device according to an embodiment of the present specification.
  • first, second, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • the first may also be referred to as the second, and similarly, the second may also be referred to as the first.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination”.
  • Postpayment Users who meet the conditions do not need to pay the guarantee fee when they join, they can enjoy the protection first. When there are insurance claiming users among the members, the premium is evenly distributed to all members according to the actual situation of the compensation case. . Unlike general commercial health insurance, pricing is based on the incidence of disease, allowing users to pay fixed premiums first.
  • Health notification When an insurance company accepts a user's application for insurance, it requires confirmation of the health status of the insured. Once the insurance company underwrites, the health notification will become an integral part of the insurance contract.
  • FIG. 1 is a block diagram showing a structure of a computing device 100 according to an embodiment of this specification.
  • the components of the computing device 100 include but are not limited to the memory 110 and the processor 120.
  • the processor 120 and the memory 110 are connected through a bus 130, and the database 150 is used to store data.
  • the computing device 100 also includes an access device 140 that enables the computing device 100 to communicate via one or more networks 160.
  • networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet.
  • the access device 140 may include one or more of any type of network interface (eg, network interface card (NIC)), wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, global microwave interconnection access ( Wi-MAX) interface, Ethernet interface, Universal Serial Bus (USB) interface, cellular network interface, Bluetooth interface, near field communication (NFC) interface, etc.
  • NIC network interface card
  • FIG. 1 the structural block diagram of the computing device shown in FIG. 1 is for illustrative purposes only, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.
  • the computing device 100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (eg, tablet computer, personal digital assistant, laptop computer, notebook computer, netbook, etc.), mobile phone (eg, smartphone ), a wearable computing device (eg, smart watch, smart glasses, etc.) or other types of mobile devices, or a stationary computing device such as a desktop computer or PC.
  • the computing device 100 may also be a mobile or stationary server.
  • the processor 120 may execute the steps in the method shown in FIG. 2.
  • FIG. 2 shows an item processing method provided in one or more embodiments of this specification, including steps 202 to 208.
  • Step 202 Receive a user's project participation request, where the project participation request carries user identification information.
  • the user identification information includes, but is not limited to, the unique identification number of a user involved in the project during the user's participation in the project, such as the user's name, ID number, parameter The user identification number consisting of the warranty date and the participating serial number.
  • Step 204 Acquire the first user information and the second user information of the user based on the user identification information.
  • the first user information includes but is not limited to the user's health information
  • the second user information includes but is not limited to the user's credit information
  • obtaining the first user information of the user includes:
  • the acquiring second user information of the user includes:
  • the first user information report includes but is not limited to a preset health measurement report
  • the first user information acquisition model includes but is not limited to a preset health model
  • Step 206 Based on the user's first user information and second user information, perform an access audit on the user and give an audit result, where the audit result includes whether the user is allowed to participate in the project.
  • an access audit is performed on the user based on the user's first user information and second user information and the audit result is given, that is, based on the user's health information and credit information judgment Whether the user satisfies the access audit and gives the audit result.
  • Step 208 In the case that the result of the audit is to allow the user to participate in the project, establish a binding relationship between the user identification information and the account corresponding to the user.
  • the audit result is to allow the user to participate in the project, that is, when the user's health information is healthy and the credit information is up to the standard, it is determined that the user satisfies the access audit and the user is allowed to participate in the project.
  • Establishing a binding relationship between the user identification information and the account corresponding to the user is to establish a binding relationship between the user identification information and the bank account corresponding to the user or a system deductible account.
  • the first user information of the users in the user blacklist is acquired according to a preset time interval
  • the user In the case that the first user information of the user satisfies the access review, the user is allowed to participate in the project.
  • a user blacklist is established for users who have not passed the project review, and then the credit information compliance and health information are selected from the user blacklist.
  • the sub-health users then update the health information of these users every certain time period. When the health information of these users is healthy, these users are allowed to participate in the project.
  • the audit result when the audit result is that users are not allowed to participate in the project, after the user blacklist is established, it also includes:
  • the user In the case that the first user information of the user in the user blacklist meets the preset requirements and the specified fee is received from the user, the user is allowed to participate in the project.
  • users whose health information is healthy and whose credit information does not meet the standard are selected from the user blacklist, and then these users are allowed to participate in the project if they agree to pay a specified fee, that is, a deposit or pre-stored fee. For example, if a user's health information is healthy, and the credit information does not meet the standard, then when the user agrees to pre-store the fee, the user can be allowed to participate in the project.
  • the request for participating in the project carries the information of the user’s associated person
  • the method further includes:
  • the related persons include but are not limited to the minor children of the user, etc.
  • the audit result is that the running user participates in the project
  • the user may be allowed to add minor children to participate in the project.
  • the project processing method realizes user participation in the project based on the review mode of the user's first user information and second user information.
  • the use of this free participation in the project greatly improves the user Participate in the project experience, and realize that the user’s affiliates can also participate in the project based on the user’s basic data, ensuring the sustainable development of the project.
  • one or more embodiments of the present specification provide an item processing method, including steps 302 to 316.
  • Step 302 Receive a user's project participation request, where the project participation request carries user identification information.
  • Step 304 Acquire the first user information and the second user information of the user based on the user identification information.
  • Step 306 Based on the first user information and the second user information of the user, perform an access audit on the user and give an audit result, where the audit result includes whether the user is allowed to participate in the project.
  • Step 308 When the result of the review is to allow the user to participate in the project, establish a binding relationship between the user identification information and the account corresponding to the user.
  • Step 310 Receive a request for mutual assistance in the case of applying for mutual assistance.
  • the request for mutual assistance in the application carries the content of the case of mutual assistance to be applied for.
  • the content of the case for mutual assistance to be applied for includes but is not limited to the incident, location and specific detailed process of the incident.
  • Step 312 In the case where it is determined that the pending mutual aid case needs to apply for mutual aid according to the content of the pending mutual aid case, according to the current number of participants in the project and the mutual aid request for the pending mutual aid case The amount determines the apportioned amount of each user currently participating in the project.
  • Step 314 Under the condition that the assessed amount does not exceed the preset assessment threshold, deduct money from the account corresponding to each user who currently participates in the project.
  • the preset allocation threshold may be set according to actual conditions, which is not limited in this application.
  • the preset allocation threshold may be 2 yuan, 5 yuan, or 10 yuan.
  • the allocation amount of each current participating project user is determined according to the current number of users participating in the project and the total amount of mutual assistance application in the case of mutual assistance to be applied 10 yuan.
  • deduction from the account corresponding to each user who currently participates in the project includes:
  • the account corresponding to each user currently participating in the project includes a custom account and a non-custom account.
  • the custom account may be a designated bank account. For example, when a deduction is required from the account corresponding to each user currently participating in the project, the deduction may be made from the user's designated bank account.
  • the non-customized account may be a random account. For example, when a charge is required from the account corresponding to each user of the currently participating project, the user may be deducted from the platform account of the user first. Deductions from other bound bank accounts.
  • Step 316 In the case where the allocation amount exceeds the preset assessment threshold, deduct the same assessment amount as the preset assessment threshold from the account corresponding to each user of the current participating project, and deduct from the second account associated with the project The apportioned amount of the apportioned amount that exceeds the preset apportionment threshold.
  • the second account is an account associated with the project, that is, in the case where the amount of assessment exceeds the preset assessment threshold, the same assessment amount as the preset assessment threshold is deducted from the account corresponding to each currently participating project user After that, the remaining apportioned amount is deducted from the second account associated with the project, that is, the project will bear the remaining apportioned amount.
  • the apportioned amount is 20 yuan, and it is determined that the apportioned amount of 20 yuan exceeds the preset apportioned threshold of 10 yuan, the same apportioned amount of 10 yuan that is the same as the preset apportioned threshold is deducted from the account corresponding to each currently participating project user Then, deduct the apportioned amount of the portion of the apportioned amount of each currently participating project user who exceeds the preset apportionment threshold from the second account number associated with the project, that is, 10 yuan for each currently participating project user.
  • the deduction of the same amount of assessment as the preset assessment threshold from the account corresponding to each currently participating project user includes:
  • a round-trip deduction is made from the account corresponding to each user of the currently participating project to the same amount as the preset threshold, until the deduction is successful or the deduction period ends.
  • the description includes steps 402 to 404.
  • Step 402 In the case where the project balance, channel Y and channel H have been opened, deductions are made from the balance, channel Y or channel H on the first day at 00:00:00-8:00:00; if the payment fails , From the balance, channel Y or channel H will continue to be deducted from 8:00:00-22:00:00 on the first day; if the deduction still fails, from 00:00:00-8:00 on the second day: 00 Continue to deduct from the balance, Y channel or H channel; if the deduction still fails, then debit from the balance, Y channel or H channel at 8:00:00-22:00:00 the next day.
  • the above Y channel and H channel are related internal channels corresponding to the M project platform. That is, if there is an internal channel corresponding to the M project platform, priority is given to deductions through the internal channel.
  • the deduction process can be ended at any time. If the deduction is not successful, the subsequent deduction process needs to be continued.
  • Step 404 Without opening the balance, channel Y and channel H, debit the designated bank account at 8:00:00-22:00:00 on the first day; if the deduction fails, on the second day 8:00:00-22:00:00 continue to debit from the designated bank account.
  • the description includes steps 406 to 408.
  • Step 406 If the first debit channel set by the user is the balance, the Y channel and the H channel, proceed from the balance, the Y channel or the H channel at 00:00:00-8:00:00 on the first day. Deduction; if the deduction fails, the deduction will continue from the balance, Y channel or H channel at 8:00:00-22:00:00 on the first day; if the deduction still fails, it will be deducted at 00:00 the next day :00-8:00:00 Continue debiting from the balance, Y channel or H channel; if the deduction still fails, then from the balance, Y channel or H channel at 8:00:00-22:00:00 the next day Continue to charge.
  • Step 408 If the customized first deduction channel is not the balance, Y channel and H channel, but the bank account number, on the first day from 8:00:00-22:00:00 from the designated bank The account is debited; if the deduction fails, the deduction will be continued from the designated bank account at 8:00:00-22:00:00 the next day.
  • the above-mentioned withholding payment method can be combined with the project associated account, bank account number, etc. to develop the above-mentioned intelligent withholding mechanism, which greatly improves the success rate of deduction.
  • the project processing method adopts a method in which the assessed amount does not exceed the preset allocation threshold, so that in each pending mutual aid case, the allocated amount of each currently participating project user does not exceed the predetermined amount Set a threshold for apportionment, so that each project participant can ensure that his benefits will not be unrestricted if the project is guaranteed.
  • an embodiment provides a detailed description of an item processing method, including steps 502 to 516.
  • Step 502 Receive a user's request for participating in a mutual assistance project, where the request for participating in a mutual assistance project carries user identification information.
  • Step 504 Acquire the user's health information and credit information based on the user identification information.
  • acquiring user health information includes but is not limited to: acquiring user health information determined based on a preset health report; or acquiring user health information based on a preset health model.
  • a health calculation report is set in advance, and after receiving a user's enrollment request, the user's health information is calculated based on the health calculation report filled in by the user, and a health notification is generated.
  • the health notification form is easy to understand by the user, deconstructs the content of the health notification based on the definition of disease, symptom and common medical, so that the user can inform according to his own health.
  • the health information may include but is not limited to the user's health score or may directly determine that the user is healthy, sub-healthy or unhealthy, etc., wherein the health measurement report includes but is not limited to height, weight, family medical history and individual Medical history and other test questions.
  • users with uncertain health problems can also obtain the user's health information based on a preset health model, that is, after receiving a user's enrollment request, the user's health information will be obtained based on an intelligent health problem test. For example, the user's height, weight and personal medical history will be asked first. If there is no personal medical history, the family medical history will be queried. If there is a personal medical history, a detailed test will be conducted on the personal medical history. Through this intelligent robot model, the user's health information will be obtained. , To ensure the accuracy of health information acquisition, and greatly improve the efficiency of health information acquisition. Regardless of the method of obtaining health information, it can provide the process data backtracking and result data recording of health notification, and provide necessary data support and reduce disputes for the determination of the mutual assistance in the case of mutual assistance to be applied for later.
  • a preset health model that is, after receiving a user's enrollment request, the user's health information will be obtained based on an intelligent health problem test. For example, the user's height, weight
  • obtaining user credit information includes, but is not limited to, obtaining user credit information based on a preset credit evaluation model.
  • the user can be profiled through artificial intelligence model analysis by gradually combining the credit points of the mutual assistance platform, the risk control data of the insurance platform, the industry fraud risk control data of the insurance company, and the third-party authorization data, etc., and gradually form the user The credit evaluation model of access review, and then use this credit evaluation model to judge the user's credit information.
  • a user is a mutual assistance platform with a credit score of 650, belongs to the overdue user group, business blacklist users, fact blacklist users are mutual insurance claims user groups, insurance industry blacklist user groups, behavior blacklist users, then pass If the established credit evaluation model is used to obtain the user's credit information, it can be determined that the user's credit information does not meet the criteria for admission review, that is, the obtained user's credit information is not up to the standard, otherwise, the obtained user's credit information For compliance.
  • Step 506 Perform an access audit on the user based on the user's health information and credit information and give an audit result.
  • the audit result includes whether to allow the user to participate in mutual assistance insurance.
  • Step 508 In the case where the result of the audit is to allow the user to participate in mutual assistance participation, establish a binding relationship between the user identification information and the account corresponding to the user.
  • Step 510 Receive a request for mutual assistance in the case of applying for mutual assistance.
  • the request for mutual assistance in the application carries the content of the case of mutual assistance to be applied for.
  • Step 512 In the case where it is determined that the mutual assistance case requires the mutual assistance according to the content of the mutual assistance case to be applied for, according to the current number of participating mutual assistance participants and the application for the mutual assistance case to be applied for The amount of mutual assistance is determined for each current participating mutual insurance participating user.
  • Step 514 Under the condition that the apportioned amount does not exceed the preset apportioned threshold, deduct money from the account corresponding to each user who currently participates in mutual assistance.
  • Step 516 In the case where the allocation amount exceeds the preset allocation threshold, deduct the same allocation amount as the preset allocation threshold from the account corresponding to each current participating mutual assistance insured user, from the first The second account deducts the apportioned amount of the apportioned amount that exceeds the preset apportionment threshold.
  • the project processing method is applied to mutual assistance projects, so that mutual assistance users can enjoy the protection first and then participate in the assessment, and the assessment amount is based on the actual risk and no objection through the disclosure of compensation.
  • the cost allocation is different from the general commercial health insurance. Pricing is based on the incidence of disease, allowing users to pay fixed premiums first, and adopting a method that does not exceed the preset allocation threshold. For each case of mutual assistance to be applied for, each current mutual assistance insured user's apportioned amount does not exceed the preset apportionment threshold, so that each mutual assistance insured person can be assured that his interests will not be unrestricted when he is covered by the insurance loss.
  • the participating item request as an insurance participation request
  • the first user information as health information
  • the second user information as credit information
  • the claim for mutual assistance is a claim request.
  • An example of a project processing method provided in one or more embodiments of this specification is described in detail, including steps 602 to 616.
  • Step 602 Receive a user's enrollment request, where the enrollment request carries user identification information.
  • Step 604 Acquire the user's health information and credit information based on the user identification information.
  • Step 606 Perform an access audit on the user based on the user's health information and credit information and give an audit result, where the audit result includes whether the user is allowed to participate in the insurance.
  • Step 608 In the case that the result of the audit is to allow the user to participate in the insurance, establish a binding relationship between the user identification information and the account corresponding to the user.
  • Step 610 Receive a claim request for the case to be settled, and the claim request carries the content of the case to be settled.
  • claims settlement is a concrete manifestation of an insurance company performing an insurance contract, performing insurance obligations, and assuming insurance liabilities. Specifically, it refers to the handling of claims cases filed by the insured after the insurance accident. After the insured suffers a disaster accident, he or she should apply for a claim to the insurer immediately or through a claims agent, review the submitted documents according to the provisions of the insurance policy, find out whether the cause of the loss is covered by the insurance, estimate the degree of loss, and determine the compensation The amount, the final payment is closed.
  • the content of the case to be settled includes but is not limited to major pathological claims, inpatient claims, etc.
  • Step 612 When it is determined that the case to be settled needs to be settled according to the content of the case to be settled, the allocation amount of each current insured user is determined according to the current number of insured persons and the claim amount of the case to be settled.
  • Step 614 When the assessed amount does not exceed the preset assessment threshold, deduct money from the account corresponding to each current insured user.
  • the preset allocation threshold may be set according to actual conditions, and this is not limited without application.
  • the preset allocation threshold may be 0.1 yuan.
  • the allocation amount of each current insured user is determined to be 0.05 yuan based on the current number of insured persons and the claim amount of the case to be settled.
  • the account corresponding to each current insured user includes a custom account and a non-custom account.
  • the custom account may be a designated bank account. For example, when a deduction is required from the account corresponding to each current insured user, the deduction may be made from the user's designated bank account.
  • the non-customized account may be a random account. For example, when a deduction is required from the account corresponding to each current insured user, the deduction may be made from the user's platform account first. Deductions from other bound bank accounts.
  • the deduction notification may be a system prompt or a short message notification.
  • Step 616 In the case that the amount of assessment exceeds the preset assessment threshold, deduct the same assessment amount as the preset assessment threshold from the account corresponding to each current insured user, and the second account associated with the insurance item Deduct the apportioned amount of the apportioned amount that exceeds the preset apportionment threshold.
  • the apportioned amount is 0.2 yuan, and it is determined that the apportioned amount of 0.2 yuan exceeds the preset apportionment threshold of 0.1 yuan, the same apportionment amount of 0.1 yuan as the preset apportionment threshold is deducted from the account corresponding to each current insured user Then, deduct the apportioned amount of each current insured user that exceeds the preset apportionment threshold from the second account number associated with the insurance item, that is, 0.1 yuan per current insured user.
  • deduction from the account corresponding to each current insured user includes:
  • the deduction of the same amount of assessment as the preset assessment threshold from the account corresponding to each current participating user includes:
  • a round robin deduction will be made from the account corresponding to each current insured user to the same amount of allocation as the preset threshold, until the deduction is successful or the deduction period ends.
  • the project processing method allows the insured users to enjoy protection before participating in the allocation, and the allocation amount is calculated according to the actual risk and no objection through the disclosure of the compensation, according to the actual compensation Case sharing is different from general commercial health insurance. It is priced based on the incidence of disease, allowing users to pay fixed premiums first, and adopting a method of not exceeding the pre-set threshold, so that for each case to be settled The current apportioned user's apportioned amount does not exceed the preset apportioned threshold, so that each insured person can be assured that his benefits will not be unrestricted if he is enrolled.
  • Step 702 Receive an insurance request from a user in the insurance platform A, where the insurance request carries user identification information.
  • Step 704 Obtain the user's health information and credit information based on the user identification information, and determine whether the user satisfies the access enrollment audit and allows the user to participate in the insurance at no cost. If it is met, step 706 is performed. If satisfied, go to step 708.
  • Step 706 Allow the user to participate in the insurance and establish a binding relationship between the user identification information and the account corresponding to the user.
  • Step 708 The user is not allowed to participate in the insurance.
  • Step 710 The user 1 appears, and the insurance platform A receives a claim request from the insured user for the claim case, and the claim request carries the content of the case to be settled.
  • Step 712 The insurance platform A determines whether the case to be settled needs to be settled according to the content of the case to be settled. If yes, step 714 is executed, and if not, step 724 is executed.
  • Step 714 Accept the case for the claim case, and determine the apportioned amount of each current insured user based on the current number of insured persons and the claim amount of the case to be claimed.
  • Step 716 On the 7th and 21st of each month, publicize the content of the claims and the amount of assessment.
  • the public announcement helps to eliminate false cases.
  • Step 718 Under the condition that the assessed amount does not exceed the preset assessment threshold, deduction will be made from the account corresponding to each current insured user on the 14th and 28th of each month.
  • per capita allocation for a single case (amount of compensation + management fee)/day of compensation
  • the preset threshold of assessment is 0.1 yuan, that is, each insured person’s
  • the upper limit of the apportioned amount is 0.1 yuan.
  • Step 720 After all the deductions are successful, the insurance platform A collects the total amount deducted from the account corresponding to each current insured user.
  • Step 722 The insurance platform A pays the compensation amount to the user 1.
  • Step 724 The project review team of the insurance platform A conducts a case review on the claim case, and the project review team determines whether it agrees to apportion the apportioned amount of the claim case. If it agrees, step 726 is performed, and if it does not agree, step 728 is performed.
  • Step 726 Agree to apportion, proceed to step 712.
  • Step 728 Disagree with the apportionment and end the claim settlement case.
  • Step 730 The insured person voluntarily withdraws and does not participate in claims settlement.
  • the project processing method allows the insured users to enjoy protection before participating in the allocation, and the allocation amount is calculated according to the actual risk and no objection through the disclosure of the compensation, according to the actual compensation
  • the cost sharing is different from the general commercial health insurance. It is priced according to the incidence of disease, allowing users to pay fixed premiums first, and adopts the method of the amount of distribution not exceeding the preset distribution threshold; and publicized twice and twice a month Apportion.
  • the confirmed claims will be publicized and accept the objection under the premise of moderately hiding sensitive information, and the security deposits generated by all claims cases without objection, plus the prescribed 10% management fee, It will be shared by all insured users on the apportionment date.
  • the actual amount of apportionment depends on the actual situation announced in each period. However, in a single claim case, the amount allocated to each user will not exceed 1 dime, so that when each insured person is covered by the insurance, he will ensure that his benefits will not be unrestricted.
  • an item processing apparatus provided by one or more embodiments of this specification includes:
  • the first receiving module 802 is configured to receive a user's project participation request, where the project participation request carries user identification information;
  • the first obtaining module 804 is configured to obtain the first user information and the second user information of the user based on the user identification information;
  • the first review module 806 is configured to perform an access review on the user based on the user's first user information and second user information and give an audit result, where the review result includes whether the user is allowed to participate in the project;
  • the first binding module 808 is configured to establish a binding relationship between the user identification information and the account corresponding to the user if the result of the review is to allow the user to participate in the project.
  • the device further includes:
  • the second receiving module is configured to receive a request for mutual assistance in the case of applying for mutual assistance, and the content of the request for mutual assistance in the case of the case of mutual assistance to be applied for;
  • the first determination module is configured to determine the amount of mutual aid to be applied for based on the content of the case of mutual aid to be applied for, according to the number of participants in the current project and the amount of mutual aid to be applied The amount of mutual assistance applied for in the case determines the apportioned amount of each user currently participating in the project;
  • the first deduction module is configured to deduct money from the account corresponding to each currently participating project user when the assessed amount does not exceed a preset assessment threshold;
  • the second deduction module is configured to deduct the same amount of apportionment as the preset apportionment threshold from the account corresponding to each currently participating project user when the apportioned amount exceeds the preset apportionment threshold.
  • the associated second account deducts the apportioned amount of the apportioned amount that exceeds the preset apportionment threshold.
  • the projects include mutual assistance projects, including:
  • the third receiving module is configured to receive a user's request to participate in a project, and the request for participating in the project carries user identification information;
  • a second obtaining module configured to obtain the first user information and the second user information of the user based on the user identification information
  • a second review module configured to perform an access review on the user based on the user's first user information and second user information and give an audit result, where the review result includes whether the user is allowed to participate in the project;
  • the second binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the result of the review is to allow the user to participate in the project.
  • the device further includes:
  • the fourth receiving module is configured to receive a request for mutual assistance in the case of applying for mutual assistance, and the request for mutual assistance in the application carries the content of the case of mutual assistance to be applied for;
  • the second determination module is configured to determine the amount of mutual aid to be applied for based on the content of the case of mutual aid to be applied for according to the content of the case of mutual aid to be applied for, based on the current number of participating projects and the amount of mutual aid
  • the amount of mutual assistance applied for in the case determines the apportioned amount of each user currently participating in the project;
  • the third deduction module is configured to deduct money from the account corresponding to each user who currently participates in the project when the assessed amount does not exceed a preset assessment threshold;
  • the fourth deduction module is configured to deduct the same amount of assessment as the preset assessment threshold from the account corresponding to each currently participating project user when the assessment amount exceeds the preset assessment threshold
  • the associated second account deducts the apportioned amount of the apportioned amount that exceeds the preset apportionment threshold.
  • the item is an insurance item, including:
  • the fifth receiving module is configured to receive a user's request to participate in the project, where the request for participating in the project carries user identification information;
  • a third obtaining module configured to obtain the first user information and the second user information of the user based on the user identification information
  • a third review module configured to perform an access review on the user based on the user's first user information and second user information and give an audit result, the review result including whether the user is allowed to participate in the project;
  • the third binding module is configured to establish a binding relationship between the user identification information and the account corresponding to the user when the result of the review is to allow the user to participate in the project.
  • the device further includes:
  • the sixth receiving module is configured to receive a request for mutual assistance in the case of applying for mutual assistance, and the content of the request for mutual assistance in the case of the case of mutual assistance to be applied for;
  • the third determination module is configured to determine the amount of mutual aid to be applied for according to the content of the case of mutual aid to be applied for according to the content of the case of mutual aid to be applied for, based on the number of current participating projects and the mutual aid
  • the amount of mutual assistance applied for in the case determines the apportioned amount of each user currently participating in the project;
  • the fifth deduction module is configured to deduct money from the account corresponding to each currently participating project user when the assessed amount does not exceed a preset assessment threshold;
  • the sixth deduction module is configured to deduct the same amount of apportionment as the preset apportionment threshold from the account corresponding to each currently participating project user when the apportioned amount exceeds the preset apportionment threshold.
  • the associated second account deducts the apportioned amount of the apportioned amount that exceeds the preset apportionment threshold.
  • the first acquisition module 804, the second acquisition module, or the third acquisition module is further configured to:
  • the first acquisition module 804, the second acquisition module, or the third acquisition module is further configured to include:
  • the device further includes:
  • the establishment module is configured to establish a user blacklist when the audit result is that users are not allowed to participate in the project;
  • a fourth obtaining module configured to obtain the first user information of the user of the user blacklist according to a preset time interval when the second user information of the user in the user blacklist satisfies the access audit;
  • the fourth review module is configured to allow the user to participate in the project if the first user information of the user satisfies the access review.
  • the device further includes:
  • the fee receiving module is configured to allow the user to participate in the project if the first user information of the user in the user blacklist satisfies the preset requirements and the designated fee is received by the user.
  • the project participation request carries the user's related person information
  • the device further includes:
  • the designated related person receiving module is configured to receive the user's designated related person's participation in the project request.
  • the account corresponding to each user currently participating in the project includes a custom account and a non-custom account.
  • the device further includes:
  • the deduction notification sending module is configured to issue a deduction notification for each user who currently participates in the project when it is determined that the to-be-requested mutual aid case requires the mutual assistance according to the content of the to-be-applied mutual aid case.
  • the first deduction module, the third deduction module or the fifth deduction module is further configured to:
  • the second deduction module, the fourth deduction module or the sixth deduction module is further configured to:
  • a round-trip deduction is made from the account corresponding to each user of the currently participating project to the same amount as the preset threshold, until the deduction is successful or the deduction period ends.
  • the project processing device implements user participation in the project through an audit mode based on the user's first user information and second user information. Using this free participation in the project greatly improves the user Participate in the project experience, and realize that the user’s affiliates can also participate in the project based on the user’s basic data, ensuring the sustainable development of the project.
  • An embodiment of the present application further provides a computer-readable storage medium that stores computer instructions, which when executed by the processor implement the steps of the item processing method described above.
  • the computer instructions include computer program code, and the computer program code may be in a source code form, an object code form, an executable file, or some intermediate form.
  • the computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in jurisdictions. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media Does not include electrical carrier signals and telecommunications signals.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Data Mining & Analysis (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Indexing, Searching, Synchronizing, And The Amount Of Synchronization Travel Of Record Carriers (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)

Abstract

一种项目处理方法及装置、一种计算设备(100)及存储介质，其中，所述方法包括接收用户的参与项目请求，所述参与项目请求中携带用户标识信息(202)；基于所述用户标识信息获取用户的第一用户信息以及第二用户信息(204)；基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目(206)；在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系(208)。

Description

一种项目处理方法及装置、一种计算设备及存储介质 技术领域
本申请涉及保险技术领域，特别涉及一种项目处理方法及装置、一种计算设备及存储介质。
背景技术
目前，一般的商业健康保险，根据疾病发生率定价，让用户先行支付固定保费，在进行赔付时也是根据缴纳保费的额数确定赔付金额。而现有的互助产品并不是保险，不承诺刚性兑付，在有互助人申请赔付的情况下，不能很好的保障参与互助人的个人权益。
发明内容
有鉴于此，本说明书实施例提供了一种项目处理方法及装置、一种计算设备及存储介质，以解决现有技术中存在的技术缺陷。
第一方面，本说明书实施例公开了一种项目处理方法，包括：
接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
第二方面，本说明书实施例公开了一种项目处理装置，包括：
第一接收模块，被配置为接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
第一获取模块，被配置为基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
第一审核模块，被配置为基于所述用户的第一用户信息以及第二用户信息对所述 用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
第一绑定模块，被配置为在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
第三方面，本说明书实施例公开了一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，所述处理器执行所述指令时实现该指令被处理器执行时实现如上所述项目处理方法的步骤。
第四方面，本说明书实施例公开了一种计算机可读存储介质，其存储有计算机指令，该指令被处理器执行时实现如上所述项目处理方法的步骤。
本说明书提供了一种项目处理方法及装置、一种计算设备及存储介质，其中，所述方法包括接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
附图说明
图1是本说明书一实施例提供的一种计算设备的示意图；
图2是本说明书一实施例提供的一种项目处理方法的流程图；
图3是本说明书一实施例提供的一种项目处理方法的流程图
图4是本说明书一实施例提供的一种项目处理方法的流程图；
图5是本说明书一实施例提供的一种项目处理方法的流程图；
图6是本说明书一实施例提供的一种项目处理方法的流程图；
图7是本说明书一实施例提供的一种项目处理方法的流程图；
图8是本说明书一实施例提供的一种项目处理装置的结构示意图。
具体实施方式
在下面的描述中阐述了很多具体细节以便于充分理解本申请。但是本申请能够以很多不同于在此描述的其它方式来实施，本领域技术人员可以在不违背本申请内涵的情 况下做类似推广，因此本申请不受下面公开的具体实施的限制。
在本说明书一个或多个实施例中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本说明书一个或多个实施例中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例中可能采用术语第一、第二等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一也可以被称为第二，类似地，第二也可以被称为第一。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
首先，对本说明书中的一个或多个实施例涉及的名词术语进行解释。
后付费：指满足条件的用户在加入的时候不需要支付保障费用，就可以先享受保障，当成员中有出险核赔用户后，根据实际发生赔付案件的情况，才向全体成员进行均摊收取保费。不同于一般的商业健康保险，根据疾病发生率定价，让用户先行支付固定保费。
信用审核：是指对申请加入的用户进行申请条件判断，符合条件用户才可加入，并且与平台信用结合，开发给诚信用户。
健康告知：指保险公司在接受用户投保申请时，要求对被保险人健康状况的确认说明，保险公司一旦承保，健康告知书将成为保险合同的一个组成部分。
在本申请中，提供了一种项目处理方法及装置、一种计算设备及存储介质，在下面的实施例中逐一进行详细说明。
图1是示出了根据本说明书一实施例的计算设备100的结构框图。该计算设备100的部件包括但不限于存储器110和处理器120。处理器120与存储器110通过总线130相连接，数据库150用于保存数据。
计算设备100还包括接入设备140，接入设备140使得计算设备100能够经由一个或多个网络160通信。这些网络的示例包括公用交换电话网(PSTN)、局域网(LAN)、广域网(WAN)、个域网(PAN)或诸如因特网的通信网络的组合。接入设备140可以包括有线或无线的任何类型的网络接口(例如，网络接口卡(NIC))中的一个或多 个，诸如IEEE802.11无线局域网(WLAN)无线接口、全球微波互联接入(Wi-MAX)接口、以太网接口、通用串行总线(USB)接口、蜂窝网络接口、蓝牙接口、近场通信(NFC)接口，等等。
在本说明书的一个实施例中，计算设备100的上述以及图1中未示出的其他部件也可以彼此相连接，例如通过总线。应当理解，图1所示的计算设备结构框图仅仅是出于示例的目的，而不是对本说明书范围的限制。本领域技术人员可以根据需要，增添或替换其他部件。
计算设备100可以是任何类型的静止或移动计算设备，包括移动计算机或移动计算设备(例如，平板计算机、个人数字助理、膝上型计算机、笔记本计算机、上网本等)、移动电话(例如，智能手机)、可佩戴的计算设备(例如，智能手表、智能眼镜等)或其他类型的移动设备，或者诸如台式计算机或PC的静止计算设备。计算设备100还可以是移动式或静止式的服务器。
其中，处理器120可以执行图2所示方法中的步骤。图2示出了本说明书一个或多个实施例提供的一种项目处理方法，包括步骤202至步骤208。
步骤202：接收用户的参与项目请求，所述参与项目请求中携带用户标识信息。
本说明书一个或多个实施例中，所述用户标识信息包括但不限于在用户参与项目的过程中针对某一用户产生的唯一的参与项目的标识号，例如由用户姓名、身份证号、参保日期以及参保流水号组成的用户标识号。
步骤204：基于所述用户标识信息获取用户的第一用户信息以及第二用户信息。
其中，所述第一用户信息包括但不限于用户的健康信息，所述第二用户信息包括但不限于用户的信用信息。
本说明书一个或多个实施例中，获取用户的第一用户信息包括：
获取用户基于预设的第一用户信息报表确定的第一用户信息；或者
基于预设的第一用户信息获取模型获取用户的第一用户信息。
所述获取用户的第二用户信息包括：
基于预设的信用评价模型获取用户的第二用户信息。
其中，所述第一用户信息报表包括但不想限于预设的健康测算报表，所述第一用户信息获取模型包括但不限于预设的健康模型。
步骤206：基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目。
本说明书一个或多个实施例中，基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，即基于所述用户的健康信息以及信用信息判断所述用户是否满足准入审核，并给出审核结果。
步骤208：在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
本说明书一个或多个实施例中，审核结果为允许用户参与项目，即是在所述用户的健康信息为健康以及信用信息为达标的情况下，确定用户满足准入审核，允许用户参与项目。
为所述用户标识信息和用户对应的账号建立绑定关系，即是为所述用户的标识信息和用户对应的银行账号或者系统可扣款账号建立绑定关系。
本说明书一个或多个实施例中，还包括：
在审核结果为不允许用户参与项目的情况下，建立用户黑名单；
在所述用户黑名单中的用户的第二用户信息满足准入审核的情况下，根据预设时间间隔获取所述用户黑名单的用户的第一用户信息；
在所述用户的第一用户信息满足准入审核的情况下，允许所述用户参与项目。
即为了提高用户参与项目的积极性，在审核结果为不允许用户参与项目的情况下，为未通过参与项目审核的用户建立用户黑名单，然后在用户黑名单中挑选出信用信息达标、健康信息为亚健康的用户，然后每隔一定的时间周期对这些用户的健康信息进行一次更新，当这些用户的健康信息为健康的情况下，允许这些用户参与项目。
另一种情况下，在审核结果为不允许用户参与项目的情况下，建立用户黑名单之后，还包括：
在所述用户黑名单中的用户的第一用户信息满足预设要求，并且接收到所述用户缴纳指定费用的情况下，允许用户参与项目。
即在用户黑名单中挑选出健康信息为健康、信用信息不达标的用户，然后在这些用户同意缴纳指定费用即保证金或预存费用的情况下，允许这些用户参与项目。例如某一用户的健康信息为健康，因信用信息造成不达标，那么当在用户同意预存费用的情况 下，则可以允许该用户参与项目。
本说明书一个或多个实施例中，所述参与项目请求中携带有用户的关联人信息，
在审核结果为允许用户参与项目的情况下，所述方法还包括：
接收用户的指定关联人的参与项目请求。
其中，所述关联人包括但不限于用户的未成年子女等，在审核结果为运行用户参与项目的情况下，可以允许用户添加未成年子女也参与该项目。
本说明书一个或多个实施例中，所述项目处理方法通过根据用户的第一用户信息以及第二用户信息的审核模式实现用户参与项目，采用这种免费参与项目的方式极大的提高了用户的参与项目体验，并且根据用户的基本数据实现用户的关联人也可以参与该项目，保障了项目的持续发展性。
参见图3，本说明书一个或多个实施例提供了一种项目处理方法，包括步骤302至步骤316。
步骤302：接收用户的参与项目请求，所述参与项目请求中携带用户标识信息。
步骤304：基于所述用户标识信息获取用户的第一用户信息以及第二用户信息。
步骤306：基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目。
步骤308：在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
本说明书一个或多个实施例中，步骤302至步骤308的具体实现方式可以参见上述实施例，在此不再赘述。
步骤310：接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容。
本说明书一个或多个实施例中，所述待申领互助金案件内容包括但不限于案件发生事件、地点以及案件发生的具体详细过程等。
步骤312：在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额。
步骤314：在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款。
本说明书一个或多个实施例中，所述预设分摊阈值可以根据实际情况进行设置，本申请对此不作限定。例如预设分摊阈值可以为2元、5元或10元等。
例如，在所述分摊金额不超过预设分摊阈值的情况下，根据当前参与项目用户人数和所述待申领互助金案件的申请互助金的总金额确定每个当前参与项目用户的分摊金额为10元。
本说明书一个或多个实施例中，从每个当前参与项目用户对应的账号中进行扣款包括：
在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣款，直至扣款成功或者扣款周期结束。
其中，所述每个当前参与项目用户对应的账号包括自定义账号和非自定义账号。
所述自定义账号可以为指定的银行账号，例如当需要从每个当前参与项目用户对应的账号中进行扣款时，可以从用户的指定银行账号中进行扣款。所述非自定义账号可以为随机账号，例如当需要从每个当前参与项目用户对应的账号中进行扣款时，可以先从用户的平台账号中扣款，若扣款失败则顺序的从用户的其他绑定银行账号中扣款。
步骤316：在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
其中，所述第二账号为与所述项目关联的账号，即在分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额后，剩余的分摊金额从与项目关联的第二账号扣除，即由项目承担剩余的分摊金额。
本说明书一个或多个实施例中，以预设分摊阈值为10元为例，在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额进行详细说明。
若所述分摊金额为20元，确定所述分摊金额20元超过预设分摊阈值10元的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额10元， 然后从与所述项目关联的第二账号扣除分摊金额中每个当前参与项目用户超过预设分摊阈值部分的分摊金额即每个当前参与项目用户的10元。
本说明书一个或多个实施例中，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额包括：
在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣除与预设分摊阈值相同的分摊金额，直至扣款成功或者扣款周期结束。
实际使用中，在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，为每个当前参与项目用户发出扣款通知。
参见图4，本说明书一个或多个实施例中，以所述项目处理方法应用于M项目平台为例，对从每个当前参与项目用户对应的账号中进行扣款详细说明。
每个当前参与项目用户对应的账号中进行扣款分为两种情况，一种是未设置自定义扣款渠道，另一种是已设置自动以扣款渠道。
以未设置自定义扣款渠道为例，进行说明包括步骤402至步骤404。
步骤402：在已开通项目余额、Y渠道以及H渠道的情况下，在第一天00:00:00-8:00:00从余额、Y渠道或者H渠道进行在扣款；若扣款失败，则在第一天8:00:00-22:00:00从余额、Y渠道或者H渠道继续扣款；若还是扣款失败，则在第二天00:00:00-8:00:00从余额、Y渠道或者H渠道继续扣款；若还是扣款失败，则在第二天8:00:00-22:00:00从余额、Y渠道或者H渠道继续扣款。
上述Y渠道和H渠道均为M项目平台对应的相关内部渠道。即若存在与M项目平台对应的内部渠道，优先通过内部渠道扣款。
若扣款成功则可以随时结束扣款流程，若扣款不成功则需要继续执行后续扣款流程。
步骤404：在未开通余额、Y渠道以及H渠道的情况下，在第一天8:00:00-22:00:00从指定银行账号进行扣款；若扣款失败，则在第二天8:00:00-22:00:00从指定银行账号进行继续扣款。
以已设置自定义扣款渠道为例，进行说明包括步骤406至步骤408。
步骤406：若自定义设置的第一扣款渠道为余额、Y渠道以及H渠道的情况下，在第一天00:00:00-8:00:00从余额、Y渠道或者H渠道进行在扣款；若扣款失败，则在第 一天8:00:00-22:00:00从余额、Y渠道或者H渠道继续扣款；若还是扣款失败，则在第二天00:00:00-8:00:00从余额、Y渠道或者H渠道继续扣款；若还是扣款失败，则在第二天8:00:00-22:00:00从余额、Y渠道或者H渠道继续扣款。
步骤408：若自定义设置的第一扣款渠道不是为余额、Y渠道以及H渠道，而是为银行账号的情况下，在第一天8:00:00-22:00:00从指定银行账号进行扣款；若扣款失败，则在第二天8:00:00-22:00:00从指定银行账号进行继续扣款。
本说明书一个或多个实施例中，采用上述代扣缴费方式可以结合项目关联账户、银行账号等，制定出上述智能的代扣发起机制，极大的提高扣款成功率。
本说明书一个或多个实施例中，所述项目处理方法采用分摊金额不超过预设分摊阈值的方法，使得在每个待申领互助金案件中每个当前参与项目用户的分摊金额不超过预设分摊阈值，使得每个参与项目人员获得项目保障的情况下，确保自己的利益不会受到无限制损失。
参见图5，以所述项目为互助项目，所述参与项目请求为参与互助项目请求，所述第一用户信息为健康信息，所述第二用户信息为信用信息为例，对本说明书一个或多个实施例提供的一种项目处理方法进行详细说明，包括步骤502至步骤516。
步骤502：接收用户的参与互助项目请求，所述参与互助项目请求中携带用户标识信息。
步骤504：基于所述用户标识信息获取用户的健康信息以及信用信息。
本说明书一个或多个实施例中，获取用户的健康信息包括但不限于：获取用户基于预设的健康报表确定的健康信息；或者基于预设的健康模型获取用户的健康信息。
例如，预先设置健康测算报表，在接收某个用户的参保请求后，基于该用户填写的健康测算报表测算出用户的健康信息，生成健康告知书。所述健康告知书从易于用户理解出发、以疾病、症状以及常见医学定义，解构健康告知内容，便于用户依据自身健康情况进行告知。所述健康信息可以包括但不限于该用户的健康得分或者是直接可以确定出该用户为健康、亚健康或者不健康等结果，其中，健康测算报表中包括但不限于身高、体重、家族病史以及个人病史等测试问题。
此外，针对健康问题不确定的用户还可以基于预设的健康模型获取用户的健康信息，即接收某个用户的参保请求后，会基于智能的健康问题测试获取用户的健康信息。例如首先会询问用户的身高、体重以及个人病史，若无个人病史则对家族病史进行询问， 若有个人病史则针对个人病史进行详细测试，通过这种智能机器人模式，对用户的健康信息进行获取，保证了健康信息获取的精确性，并且极大的提高了对健康信息获取的高效性。无论是采用哪种健康信息获取的方式，均可以提供健康告知的过程数据回溯、结果数据记录，为后期进行待申领互助金案件的申领互助金确定时提供必要数据支持、减少争议。
本说明书一个或多个实施例中，获取用户的信用信息包括但不限于：基于预设的信用评价模型获取用户的信用信息。
实际使用中，可以通过结合互助平台的信用分、保险平台的风控数据、保险公司的行业骗赔风控数据以及第三方授权数据等，通过人工智能模型分析，对用户进行画像，逐步形成用户准入审核的信用评价模型，然后采用该信用评价模型对用户的信用信息进行判断。
例如某一用户为互助平台信用分650分、属于逾期欠款用户群、业务黑名单用户、事实黑名单用户即互保理赔用户群、保险行业黑名单用户群、行为黑名单用户，那么通过预设的信用评价模型进行用户的信用信息的获取，则可以确定该用户的信用信息不满足准入审核的标准，即获取到的用户的信用信息为不达标，反之，获取到的用户的信用信息为达标。
步骤506：基于所述用户的健康信息以及信用信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与互助参保。
步骤508：在审核结果为允许用户参与互助参保的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
步骤510：接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容。
步骤512：在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与互助参保人数和所述待申领互助金案件的申领互助金额确定每个当前参与互助参保用户的分摊金额。
步骤514：在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与互助参保用户对应的账号中进行扣款。
步骤516：在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与互助参保用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述互助项目关联的第二 账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
需要说明的是，该互助项目处理方法的技术方案与上述的项目处理方法的技术方案属于同一构思，该互助项目处理方法的技术方案未详细描述的细节内容，均可以参见上述项目处理方法的技术方案的描述。
本说明书一个或多个实施例中，所述项目处理方法应用在互助项目中，使得互助参保用户可以先享受保障后参与分摊，且分摊金额按照实际出险并通过核赔公示无异议的情况来计算，根据实际发生申请互助金案例的情况进行费用分摊，不同于一般的商业健康保险，根据疾病发生率定价，让用户先行支付固定保费，并且采用分摊金额不超过预设分摊阈值的方法，使得对于每个待申领互助金案件每个当前互助参保用户的分摊金额不超过预设分摊阈值，使得每个互助参保人员获得参保保障的情况下，确保自己的利益不会受到无限制损失。
参见图6，以所述项目为保险项目，所述参与项目请求为参保请求，所述第一用户信息为健康信息，所述第二用户信息为信用信息，所述待申领互助金案件为待理赔案件，所述申领互助金请求为理赔请求为例，对本说明书一个或多个实施例提供的一种项目处理方法进行详细说明，包括步骤602至步骤616。
步骤602：接收用户的参保请求，所述参保请求中携带用户标识信息。
步骤604：基于所述用户标识信息获取用户的健康信息以及信用信息。
步骤606：基于所述用户的健康信息以及信用信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参保。
步骤608：在审核结果为允许用户参保的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
步骤610：接收对待理赔案件的理赔请求，所述理赔请求中携带所述待理赔案件内容。
本说明书一个或多个实施例中，理赔是保险公司执行保险合同，履行保险义务，承担保险责任的具体体现。具体指保险事故发生后，保险人对被保险人所提出的索赔案件的处理。被保险人遭受灾害事故后，应立即或通过理赔代理人对保险人提出索赔申请，根据保险单的规定审核提交的各项单证，查明损失原因是否属保险范围，估算损失程度，确定赔偿金额，最后给付结案。
实际使用中，所述待理赔案件内容包括但不限于大病理赔、住院理赔等。
步骤612：在根据所述待理赔案件内容确定所述待理赔案件需要理赔的情况下，根据当前参保人数和所述待理赔案件的理赔额确定每个当前参保用户的分摊金额。
步骤614：在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参保用户对应的账号中进行扣款。
本说明书一个或多个实施例中，所述预设分摊阈值可以根据实际情况进行设置，不申请对此不作限定。例如预设分摊阈值可以为0.1元等。
例如，在根据所述待理赔案件内容确定所述待理赔案件需要理赔的情况下，根据当前参保人数和所述待理赔案件的理赔额确定每个当前参保用户的分摊金额为0.05元。
此时所述分摊金额0.05元不超过预设分摊阈值0.1元的情况下，从每个当前参保用户对应的账号中进行扣款0.1元。
本说明书一个或多个实施例中，所述每个当前参保用户对应的账号包括自定义账号和非自定义账号。
所述自定义账号可以为指定的银行账号，例如当需要从每个当前参保用户对应的账号中进行扣款时，可以从用户的指定银行账号中进行扣款。所述非自定义账号可以为随机账号，例如当需要从每个当前参保用户对应的账号中进行扣款时，可以先从用户的平台账号中扣款，若扣款失败则顺序的从用户的其他绑定银行账号中扣款。
实际使用中，在根据所述待理赔案件内容确定所述待理赔案件需要理赔的情况下，可以先为每个当前参保用户发出扣款通知。其中，所述扣款通知可以是系统提示或者是短信通知等。
步骤616：在所述分摊金额超过预设分摊阈值的情况下，从每个当前参保用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述保险项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
本说明书一个或多个实施例中，以预设分摊阈值为0.1元为例，对在所述分摊金额超过预设分摊阈值的情况下，从每个当前参保用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述保险项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额进行详细说明。
若所述分摊金额为0.2元，确定所述分摊金额0.2元超过预设分摊阈值0.1元的情 况下，从每个当前参保用户对应的账号中扣除与预设分摊阈值相同的分摊金额0.1元，然后从与所述保险项目关联的第二账号扣除分摊金额中每个当前参保用户超过预设分摊阈值部分的分摊金额即每个当前参保用户的0.1元。
本说明书一个或多个实施例中，从每个当前参保用户对应的账号中进行扣款包括：
在预设扣款周期内从每个当前参保用户对应的账号中进行轮巡扣款，直至扣款成功或者扣款周期结束；
从每个当前参保用户对应的账号中扣除与预设分摊阈值相同的分摊金额包括：
在预设扣款周期内从每个当前参保用户对应的账号中进行轮巡扣除与预设分摊阈值相同的分摊金额，直至扣款成功或者扣款周期结束。
需要说明的是，该保险项目处理方法的技术方案与上述的项目处理方法的技术方案属于同一构思，该保险项目处理方法的技术方案未详细描述的细节内容，均可以参见上述项目处理方法的技术方案的描述。
本说明书一个或多个实施例中，所述项目处理方法，使得参保用户可以先享受保障后参与分摊，且分摊金额按照实际出险并通过核赔公示无异议的情况来计算，根据实际发生赔付案例的情况进行费用分摊，不同于一般的商业健康保险，根据疾病发生率定价，让用户先行支付固定保费，并且采用分摊金额不超过预设分摊阈值的方法，使得对于每个待理赔案件每个当前参保用户的分摊金额不超过预设分摊阈值，使得每个参保人员获得参保保障的情况下，确保自己的利益不会受到无限制损失。
参见图7，以保险平台A为例，对本说明书一个或多个实施例提供的一种项目处理方法进行说明，包括步骤702至步骤730。
步骤702：接收保险平台A中用户的参保请求，所述参保请求中携带用户标识信息。
步骤704：基于所述用户标识信息获取用户的健康信息以及信用信息，并判断所述用户是否满足准入参保审核，允许用户0费用参保的情况，若满足，则执行步骤706，若不满足，则执行步骤708。
步骤706：允许用户参保，为所述用户标识信息和用户对应的账号建立绑定关系。
步骤708：不允许用户参保。
步骤710：用户1出现，保险平台A接收参保用户中的用户1对待理赔案件的理 赔请求，所述理赔请求中携带所述待理赔案件内容。
步骤712：保险平台A根据所述待理赔案件内容判断所述待理赔案件是否需要理赔，若是，则执行步骤714，若否，则执行步骤724。
步骤714：对该理赔案件进行案件受理，根据当前参保人数和所述待理赔案件的理赔额确定每个当前参保用户的分摊金额。
步骤716：每月的7日、21日对理赔案件内容以及分摊金额进行全民公示。
本说明书一个或多个实施例中，全民公示有助于对虚假案件的剔除。
步骤718：在所述分摊金额不超过预设分摊阈值的情况下，每月14日、28日从每个当前参保用户对应的账号中进行扣款。
本说明书一个或多个实施例中，单一案件人均分摊＝(赔付金额+管理费)/赔付当日，此外，所述预设分摊阈值为0.1元，即在保人数单一案件每个参保人的分摊金额上限为0.1元。
步骤720：全部扣款成功后，保险平台A汇总从每个当前参保用户对应的账号中进行扣款的总金额。
步骤722：保险平台A支付赔付金额给用户1。
步骤724：保险平台A的项目审核组对该理赔案件进行案件审理，由项目审核组判断是否同意分摊该理赔案件的分摊金额，若同意，则执行步骤726，若不同意，则执行步骤728。
步骤726：同意分摊，继续执行步骤712。
步骤728：不同意分摊，结束该理赔案件。
步骤730：参保人员主动退出，不参与理赔。
本说明书一个或多个实施例中，所述项目处理方法，使得参保用户可以先享受保障后参与分摊，且分摊金额按照实际出险并通过核赔公示无异议的情况来计算，根据实际发生赔付案例的情况进行费用分摊，不同于一般的商业健康保险，根据疾病发生率定价，让用户先行支付固定保费，并且采用分摊金额不超过预设分摊阈值的方法；并且每月两次公示、两次分摊。在公示日，其间发生的确诊的理赔案件均会在适度隐藏敏感信息的前提下，给予公示并接受异议申诉，公示无异议的所有理赔案件产生的保障金，加上规定的10％管理费，会在分摊日由所有参保用户均摊，均摊实际金额视每期公示的实 际情况而定。但单一理赔案件中，每个用户被分摊到的金额不会超过1毛钱，使得每个参保人员获得参保保障的情况下，确保自己的利益不会受到无限制损失。
参见图8，本说明书一个或多个实施例提供的一种项目处理装置，包括：
第一接收模块802，被配置为接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
第一获取模块804，被配置为基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
第一审核模块806，被配置为基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
第一绑定模块808，被配置为在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
可选地，所述装置还包括：
第二接收模块，被配置为接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
第一确定模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
第一扣款模块，被配置为在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
第二扣款模块，被配置为在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
可选地，所述项目包括互助项目，包括：
第三接收模块，被配置为接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
第二获取模块，被配置为基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
第二审核模块，被配置为基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
第二绑定模块，被配置为在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
可选地，所述装置还包括：
第四接收模块，被配置为接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
第二确定模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
第三扣款模块，被配置为在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
第四扣款模块，被配置为在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
可选地，所述项目为保险项目，包括：
第五接收模块，被配置为接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
第三获取模块，被配置为基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
第三审核模块，被配置为基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
第三绑定模块，被配置为在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
可选地，所述装置还包括：
第六接收模块，被配置为接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
第三确定模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
第五扣款模块，被配置为在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
第六扣款模块，被配置为在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
可选地，所述第一获取模块804、所述第二获取模块或所述第三获取模块进一步被配置为：
获取用户基于预设的第一用户信息报表确定的第一用户信息；或者
基于预设的第一用户信息获取模型获取用户的第一用户信息。
可选地，所述第一获取模块804、所述第二获取模块或所述第三获取模块进一步被配置为包括：
基于预设的信用评价模型获取用户的第二用户信息。
可选地，所述装置还包括：
建立模块，被配置为在审核结果为不允许用户参与项目的情况下，建立用户黑名单；
第四获取模块，被配置为在所述用户黑名单中的用户的第二用户信息满足准入审核的情况下，根据预设时间间隔获取所述用户黑名单的用户的第一用户信息；
第四审核模块，被配置为在所述用户的第一用户信息满足准入审核的情况下，允许所述用户参与项目。
可选地，所述装置还包括：
费用接收模块，被配置为在所述用户黑名单中的用户的第一用户信息满足预设要求，并且接收到所述用户缴纳指定费用的情况下，允许用户参与项目。
可选地，所述参与项目请求中携带有用户的关联人信息，
在审核结果为允许用户参与项目的情况下，所述装置还包括：
指定关联人接收模块，被配置为接收用户的指定关联人的参与项目请求。
可选地，所述每个当前参与项目用户对应的账号包括自定义账号和非自定义账号。
可选地，所述装置还包括：
扣款通知发送模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，为每个当前参与项目用户发出扣款通知。
可选地，所述第一扣款模块、所述第三扣款模块或所述第五扣款模块进一步被配置为：
在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣款，直至扣款成功或者扣款周期结束；
所述第二扣款模块、所述第四扣款模块或所述第六扣款模块进一步被配置为：
在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣除与预设分摊阈值相同的分摊金额，直至扣款成功或者扣款周期结束。
本说明书一个或多个实施例中，所述项目处理装置通过根据用户的第一用户信息以及第二用户信息的审核模式实现用户参与项目，采用这种免费参与项目的方式极大的提高了用户的参与项目体验，并且根据用户的基本数据实现用户的关联人也可以参与该项目，保障了项目的持续发展性。
需要说明的是，该项目处理装置的技术方案与上述的项目处理方法的技术方案属于同一构思，该项目处理装置的技术方案未详细描述的细节内容，均可以参见上述项目处理方法的技术方案的描述。
本申请一实施例还提供一种计算机可读存储介质，其存储有计算机指令，该指令被处理器执行时实现如前所述项目处理方法的步骤。
上述为本实施例的一种计算机可读存储介质的示意性方案。需要说明的是，该存储介质的技术方案与上述的项目处理方法的技术方案属于同一构思，存储介质的技术方案未详细描述的细节内容，均可以参见上述项目处理方法的技术方案的描述。
所述计算机指令包括计算机程序代码，所述计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括：能够携带所述计算机程序代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM， Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读介质不包括电载波信号和电信信号。
需要说明的是，对于前述的各方法实施例，为了简便描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其它顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定都是本申请所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其它实施例的相关描述。
以上公开的本申请优选实施例只是用于帮助阐述本申请。可选实施例并没有详尽叙述所有的细节，也不限制该发明仅为所述的具体实施方式。显然，根据本说明书的内容，可作很多的修改和变化。本说明书选取并具体描述这些实施例，是为了更好地解释本申请的原理和实际应用，从而使所属技术领域技术人员能很好地理解和利用本申请。本申请仅受权利要求书及其全部范围和等效物的限制。

Claims (30)

  1. 一种项目处理方法，其特征在于，包括：
    接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
    基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
    基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
    在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
    在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
    在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
    在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
  3. 根据权利要求1所述的方法，其特征在于，所述项目包括互助项目，包括：
    接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
    基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
    基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
    在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
  4. 根据权利要求3所述的方法，其特征在于，还包括：
    接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
    在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前 参与项目用户的分摊金额；
    在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
    在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
  5. 根据权利要求1所述的方法，其特征在于，所述项目为保险项目，包括：
    接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
    基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
    基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
    在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
  6. 根据权利要求5所述的方法，其特征在于，还包括：
    接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
    在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
    在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
    在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
  7. 根据权利要求1-6任意一项所述的方法，其特征在于，获取用户的第一用户信息包括：
    获取用户基于预设的第一用户信息报表确定的第一用户信息；或者
    基于预设的第一用户信息获取模型获取用户的第一用户信息。
  8. 根据权利要求1-6任意一项所述的方法，其特征在于，获取用户的第二用户信息包括：
    基于预设的信用评价模型获取用户的第二用户信息。
  9. 根据权利要求1-6任意一项所述的方法，其特征在于，还包括：
    在审核结果为不允许用户参与项目的情况下，建立用户黑名单；
    在所述用户黑名单中的用户的第二用户信息满足准入审核的情况下，根据预设时间间隔获取所述用户黑名单的用户的第一用户信息；
    在所述用户的第一用户信息满足准入审核的情况下，允许所述用户参与项目。
  10. 根据权利要求9所述的方法，其特征在于，在审核结果为不允许用户参与项目的情况下，建立用户黑名单之后，还包括：
    在所述用户黑名单中的用户的第一用户信息满足预设要求，并且接收到所述用户缴纳指定费用的情况下，允许用户参与项目。
  11. 根据权利要求1-6任意一项所述的方法，其特征在于，所述参与项目请求中携带有用户的关联人信息，
    在审核结果为允许用户参与项目的情况下，所述方法还包括：
    接收用户的指定关联人的参与项目请求。
  12. 根据权利要求2或4或6所述的方法，其特征在于，所述每个当前参与项目用户对应的账号包括自定义账号和非自定义账号。
  13. 根据权利要求2或4或6所述的方法，其特征在于，还包括：
    在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，为每个当前参与项目用户发出扣款通知。
  14. 根据权利要求2或4或6所述的方法，其特征在于，从每个当前参与项目用户对应的账号中进行扣款包括：
    在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣款，直至扣款成功或者扣款周期结束；
    从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额包括：
    在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣除与预设分摊阈值相同的分摊金额，直至扣款成功或者扣款周期结束。
  15. 一种项目处理装置，其特征在于，包括：
    第一接收模块，被配置为接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
    第一获取模块，被配置为基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
    第一审核模块，被配置为基于所述用户的第一用户信息以及第二用户信息对所述用 户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
    第一绑定模块，被配置为在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
  16. 根据权利要求15所述的装置，其特征在于，所述装置还包括：
    第二接收模块，被配置为接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
    第一确定模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
    第一扣款模块，被配置为在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
    第二扣款模块，被配置为在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
  17. 根据权利要求15所述的装置，其特征在于，所述项目包括互助项目，包括：
    第三接收模块，被配置为接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
    第二获取模块，被配置为基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
    第二审核模块，被配置为基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
    第二绑定模块，被配置为在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
  18. 根据权利要求17所述的装置，其特征在于，还包括：
    第四接收模块，被配置为接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
    第二确定模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
    第三扣款模块，被配置为在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
    第四扣款模块，被配置为在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
  19. 根据权利要求15所述的装置，其特征在于，所述项目为保险项目，包括：
    第五接收模块，被配置为接收用户的参与项目请求，所述参与项目请求中携带用户标识信息；
    第三获取模块，被配置为基于所述用户标识信息获取用户的第一用户信息以及第二用户信息；
    第三审核模块，被配置为基于所述用户的第一用户信息以及第二用户信息对所述用户进行准入审核并给出审核结果，所述审核结果包括是否允许所述用户参与项目；
    第三绑定模块，被配置为在审核结果为允许用户参与项目的情况下，为所述用户标识信息和用户对应的账号建立绑定关系。
  20. 根据权利要求19所述的装置，其特征在于，还包括：
    第六接收模块，被配置为接收对待申领互助金案件的申领互助金请求，所述申领互助金请求中携带所述待申领互助金案件内容；
    第三确定模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，根据当前参与项目人数和所述待申领互助金案件的申领互助金额确定每个当前参与项目用户的分摊金额；
    第五扣款模块，被配置为在所述分摊金额不超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中进行扣款；
    第六扣款模块，被配置为在所述分摊金额超过预设分摊阈值的情况下，从每个当前参与项目用户对应的账号中扣除与预设分摊阈值相同的分摊金额，从与所述项目关联的第二账号扣除分摊金额中超过预设分摊阈值部分的分摊金额。
  21. 根据权利要求15-20任意一项所述的装置，其特征在于，所述第一获取模块、所述第二获取模块或所述第三获取模块进一步被配置为：
    获取用户基于预设的第一用户信息报表确定的第一用户信息；或者
    基于预设的第一用户信息获取模型获取用户的第一用户信息。
  22. 根据权利要求15-20任意一项所述的装置，其特征在于，所述第一获取模块、所述第二获取模块或所述第三获取模块进一步被配置为包括：
    基于预设的信用评价模型获取用户的第二用户信息。
  23. 根据权利要求15-20任意一项所述的装置，其特征在于，所述装置还包括：
    建立模块，被配置为在审核结果为不允许用户参与项目的情况下，建立用户黑名单；
    第四获取模块，被配置为在所述用户黑名单中的用户的第二用户信息满足准入审核的情况下，根据预设时间间隔获取所述用户黑名单的用户的第一用户信息；
    第四审核模块，被配置为在所述用户的第一用户信息满足准入审核的情况下，允许所述用户参与项目。
  24. 根据权利要求23所述的装置，其特征在于，所述装置还包括：
    费用接收模块，被配置为在所述用户黑名单中的用户的第一用户信息满足预设要求，并且接收到所述用户缴纳指定费用的情况下，允许用户参与项目。
  25. 根据权利要求15-20任意一项所述的装置，其特征在于，所述参与项目请求中携带有用户的关联人信息，
    在审核结果为允许用户参与项目的情况下，所述装置还包括：
    指定关联人接收模块，被配置为接收用户的指定关联人的参与项目请求。
  26. 根据权利要求16或18或20所述的装置，其特征在于，所述每个当前参与项目用户对应的账号包括自定义账号和非自定义账号。
  27. 根据权利要求16或18或20所述的装置，其特征在于，所述装置还包括：
    扣款通知发送模块，被配置为在根据所述待申领互助金案件内容确定所述待申领互助金案件需要申领互助金的情况下，为每个当前参与项目用户发出扣款通知。
  28. 根据权利要求16或18或20所述的装置，其特征在于，所述第一扣款模块、所述第三扣款模块或所述第五扣款模块进一步被配置为：
    在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣款，直至扣款成功或者扣款周期结束；
    所述第二扣款模块、所述第四扣款模块或所述第六扣款模块进一步被配置为：
    在预设扣款周期内从每个当前参与项目用户对应的账号中进行轮巡扣除与预设分摊阈值相同的分摊金额，直至扣款成功或者扣款周期结束。
  29. 一种计算设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令，其特征在于，所述处理器执行所述指令时实现该指令被处理器执行时实现权利要求1-14任意一项所述方法的步骤。
  30. 一种计算机可读存储介质，其存储有计算机指令，其特征在于，该指令被处理器执行时实现权利要求1-14任意一项所述方法的步骤。
PCT/CN2019/110469 2018-11-28 2019-10-10 一种项目处理方法及装置、一种计算设备及存储介质 WO2020108107A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811448955.8A CN110009294B (zh) 2018-11-28 2018-11-28 一种项目处理方法及装置、一种计算设备及存储介质
CN201811448955.8 2018-11-28

Publications (1)

Publication Number Publication Date
WO2020108107A1 true WO2020108107A1 (zh) 2020-06-04

Family

ID=67165049

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/110469 WO2020108107A1 (zh) 2018-11-28 2019-10-10 一种项目处理方法及装置、一种计算设备及存储介质

Country Status (3)

Country Link
CN (2) CN112598402A (zh)
TW (1) TWI785271B (zh)
WO (1) WO2020108107A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112308670A (zh) * 2020-10-30 2021-02-02 上海东方投资监理有限公司 一种云计价方法、系统、装置及存储介质
CN113298481A (zh) * 2020-07-13 2021-08-24 阿里巴巴集团控股有限公司 数据处理方法及装置

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112598402A (zh) * 2018-11-28 2021-04-02 创新先进技术有限公司 一种项目处理方法及装置、一种计算设备及存储介质
CN110033227A (zh) * 2018-11-28 2019-07-19 阿里巴巴集团控股有限公司 数据处理方法、装置、计算设备及存储介质
CN110674617A (zh) * 2019-08-15 2020-01-10 阿里巴巴集团控股有限公司 健康核查过程中的疾病展示方法以及装置
CN110634076B (zh) * 2019-08-15 2023-06-20 创新先进技术有限公司 健康保障项目的用户健康核实方法及装置
CN110517157B (zh) * 2019-08-28 2022-12-06 泰康保险集团股份有限公司 财产相互险管理方法、装置、介质及电子设备
CN110751517B (zh) * 2019-10-17 2022-07-29 蚂蚁胜信(上海)信息技术有限公司 互助项目中的增信方法以及装置
JP6754884B1 (ja) * 2019-12-04 2020-09-16 ＰａｙＰａｙ株式会社 提供装置、提供方法及び提供プログラム
CN115392879A (zh) * 2020-11-23 2022-11-25 支付宝(杭州)信息技术有限公司 项目处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106600416A (zh) * 2016-09-30 2017-04-26 上海互慧保企业管理咨询有限公司 人工智能互助分摊系统
CN107103544A (zh) * 2016-02-23 2017-08-29 平安科技（深圳）有限公司 自助险信息处理方法和装置
US10026129B1 (en) * 2013-12-23 2018-07-17 Massachusetts Mutual Life Insurance Company Analytical methods and tools for determining needs of orphan policyholders
CN110009294A (zh) * 2018-11-28 2019-07-12 阿里巴巴集团控股有限公司 一种项目处理方法及装置、一种计算设备及存储介质

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
NZ525001A (en) * 2000-10-11 2005-06-24 Healthtrio Inc System for communication of health care data
JP2004341913A (ja) * 2003-05-16 2004-12-02 Yasuyuki Sekine 掛金変動型共済管理システム、掛金変動型共済管理プログラム及び掛金変動型共済管理の方法
US20050256747A1 (en) * 2004-04-28 2005-11-17 Hellrigel Robert M System and method for underwriting payment processing risk
TW201009734A (en) * 2008-08-18 2010-03-01 Shacom Com Inc Method and system for mutual investment insurance
US20130253942A1 (en) * 2012-03-22 2013-09-26 Hong Kong Baptist University Methods and Apparatus for Smart Healthcare Decision Analytics and Support
US20140278494A1 (en) * 2013-03-14 2014-09-18 Solarte Health, Inc. Systems and methods for health care account processing
CN107194174A (zh) * 2017-05-19 2017-09-22 白胜西 一种健康状况监测方法、系统和存储介质
CN107909232B (zh) * 2017-08-28 2021-05-04 平安科技（深圳）有限公司 理赔案件分配方法、装置、存储介质和计算机设备
CN107895264B (zh) * 2017-11-13 2021-12-10 招商华软信息有限公司 车辆费用的缴纳方法和装置
CN108022169A (zh) * 2017-11-30 2018-05-11 平安科技（深圳）有限公司 通过网站对接购买保险的方法、装置、设备及介质
CN108289129B (zh) * 2018-02-26 2020-10-23 深圳智乾区块链科技有限公司 区块链生态环境创建方法、系统及计算机可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10026129B1 (en) * 2013-12-23 2018-07-17 Massachusetts Mutual Life Insurance Company Analytical methods and tools for determining needs of orphan policyholders
CN107103544A (zh) * 2016-02-23 2017-08-29 平安科技（深圳）有限公司 自助险信息处理方法和装置
CN106600416A (zh) * 2016-09-30 2017-04-26 上海互慧保企业管理咨询有限公司 人工智能互助分摊系统
CN110009294A (zh) * 2018-11-28 2019-07-12 阿里巴巴集团控股有限公司 一种项目处理方法及装置、一种计算设备及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113298481A (zh) * 2020-07-13 2021-08-24 阿里巴巴集团控股有限公司 数据处理方法及装置
CN112308670A (zh) * 2020-10-30 2021-02-02 上海东方投资监理有限公司 一种云计价方法、系统、装置及存储介质

Also Published As

Publication number Publication date
TW202101331A (zh) 2021-01-01
CN110009294A (zh) 2019-07-12
CN110009294B (zh) 2021-01-26
TWI785271B (zh) 2022-12-01
CN112598403A (zh) 2021-04-02
CN112598402A (zh) 2021-04-02

Similar Documents

Publication Publication Date Title
WO2020108107A1 (zh) 一种项目处理方法及装置、一种计算设备及存储介质
WO2020192272A1 (zh) 基于区块链的转账方法、系统、计算设备及存储介质
CN108713209B (zh) 维修工位的管理方法、系统及数据管理服务器
CN111833179A (zh) 资源分配平台、资源分配方法及装置
US20220391990A1 (en) Blockchain-based systems and methods for self-managed peer group insurance
CN111833180A (zh) 一种资源分配方法以及装置
CN113222750A (zh) 一种跨境支付结算方法、装置、系统、设备及存储介质
CN110246043A (zh) 项目缴费方法、装置、电子设备以及存储介质
US20140288949A1 (en) Telephonic Device Payment Processing
CN112598403B (zh) 一种项目处理方法及装置、一种计算设备及存储介质
CN108446901A (zh) 基于多人付费的咨询通讯系统和方法
CN110942383A (zh) 基于信用组织的风险处理方法以及装置
KR20200006252A (ko) 블록 체인을 이용한 가상화폐 유동성 대여 중계 장치
KR20200006243A (ko) 블록 체인을 이용한 가상화폐 유동성 대여를 위한 프로그램
JP4308580B2 (ja) 与信限度額を超える高額物件のカード決済システム及びその制御方法
CN113344578A (zh) 基于区块链的对象处理方法及装置
KR20200006274A (ko) 블록 체인을 이용한 가상화폐 유동성 담보 처리방법
CN117422531A (zh) Nft处理方法、装置及可读存储介质
KR20200006237A (ko) 블록 체인을 이용한 가상화폐 유동성 대여방법
KR20200006262A (ko) 블록 체인을 이용한 가상화폐 유동성 대여 중계방법
KR20200006304A (ko) 블록 체인을 이용한 가상화폐 유동성 제공방법
KR20200006272A (ko) 블록 체인을 이용한 가상화폐 유동성 담보 처리 장치
KR20200006250A (ko) 기록매체
KR20200006265A (ko) 블록 체인을 이용한 가상화폐 유동성 대여 중계 프로그램
KR20200006330A (ko) 블록 체인을 이용한 가상화폐 유동성 대여방법

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: 19890801

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19890801

Country of ref document: EP

Kind code of ref document: A1