WO2018233367A1 - 立案方法、装置、终端和计算机可读存储介质 - Google Patents

立案方法、装置、终端和计算机可读存储介质 Download PDF

Info

Publication number
WO2018233367A1
WO2018233367A1 PCT/CN2018/083675 CN2018083675W WO2018233367A1 WO 2018233367 A1 WO2018233367 A1 WO 2018233367A1 CN 2018083675 W CN2018083675 W CN 2018083675W WO 2018233367 A1 WO2018233367 A1 WO 2018233367A1
Authority
WO
WIPO (PCT)
Prior art keywords
case
field
request
verification
filing
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/083675
Other languages
English (en)
French (fr)
Inventor
赵亮
刘金萍
黄建虎
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2018233367A1 publication Critical patent/WO2018233367A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a filing method, apparatus, terminal, and computer readable storage medium.
  • the main purpose of the present application is to provide a method, device, terminal and computer readable storage medium for solving the problem of the existing filing method, low filing efficiency and poor intelligence.
  • the present application provides a filing method, the filing method comprising:
  • the report entry is displayed in the preset interface of the claim system
  • Each verification case is used to review the corresponding cases.
  • the claim settlement plan is generated based on the amount of the compensation corresponding to the case.
  • the present application further provides a filing device, the filing device comprising:
  • a display module configured to display a report entry in a preset interface of the claims system when receiving the case import request
  • the comparison module is configured to extract corresponding data fields in each imported case, and compare the extracted data fields with the pre-stored mapping table to determine a verification rule corresponding to each data field;
  • the audit module is used to review each case by using each verification rule.
  • the claim scheme is generated based on the amount of the claim corresponding to the case.
  • the present application further provides a terminal, where the terminal includes a memory, a processor, and a filing program stored on the memory and operable on the processor, the filing program being The steps of the filing method as described above are implemented when the processor executes.
  • the present application further provides a computer readable storage medium, where the computer readable storage medium stores a filing program, and the filing program is executed by a processor to implement the filing method as described above. step.
  • the technical solution proposed by the present application first displays a report entry in a preset interface of the claims system when receiving the case import request, and then imports a batch case from the report entry, and extracts corresponding data from each imported case. Field, and compare each extracted data field with the pre-stored mapping table to determine the verification rule corresponding to each data field, and finally use each verification rule to review each case, and when the verification is correct, based on the case The corresponding compensation amount is generated to generate a claim plan.
  • this application examines the case through the verification rules of each case, and carries out subsequent filing, realizing the batch filing of the claims plan, without having to manually file each case separately, and improve the claims. The efficiency and intelligence of filing the case saves manpower.
  • FIG. 1 is a schematic structural diagram of a terminal in a hardware operating environment involved in a solution according to an embodiment of the present application
  • FIG. 2 is a schematic flow chart of a first embodiment of a method for filing a case according to the present application
  • FIG. 3 is a schematic flow chart of a second embodiment of a filing method of the present application.
  • the solution of the embodiment of the present application is mainly: when receiving the case import request, first displaying the report entry in the preset interface of the claim system, then importing the batch case from the report entry, and extracting from the imported cases. Corresponding data fields, and comparing the extracted data fields with the pre-stored mapping table to determine the verification rules corresponding to the respective data fields, and finally using the respective verification rules to review the corresponding cases, when the verification is correct A claim settlement plan is generated based on the amount of the claim corresponding to the case. In order to solve the problem of poor intelligence and low efficiency in the existing filing method.
  • FIG. 1 is a schematic structural diagram of a terminal in a hardware operating environment involved in an embodiment of the present application.
  • the device in the embodiment of the present application may be a PC, or may be a mobile terminal device having a display function, such as a smart phone, a tablet computer, an e-book reader, and a portable computer.
  • the device may include a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
  • the communication bus 1002 is used to implement connection communication between these components.
  • the user interface 1003 can include a display, an input unit such as a keyboard, and the optional user interface 1003 can also include a standard wired interface, a wireless interface.
  • the network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a WI-FI interface).
  • the memory 1005 may be a high speed RAM memory or a stable memory (non-volatile) Memory), such as disk storage.
  • the memory 1005 can also optionally be a storage device independent of the aforementioned processor 1001.
  • the device may also include a camera, RF (Radio) Frequency, RF) circuits, sensors, audio circuits, WiFi modules, and more.
  • RF Radio
  • RF Radio Frequency
  • FIG. 1 does not constitute a limitation to the device, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.
  • an operating system, a network communication module, a user interface module, and a filing program may be included in the memory 1005 as a computer readable storage medium.
  • the operating system is a program for managing and controlling terminal and software resources, and supports operation of a network communication module, a user interface module, a filing program, and other programs or software; a network communication module is used to manage and control the network interface 1002; and a user interface module is used.
  • the user interface 1003 is managed and controlled.
  • the network interface 1004 is mainly used to connect to the claims system platform, and performs data communication with the claims system platform;
  • the user interface 1003 is mainly used to connect the client (user end) and perform data communication with the client;
  • the terminal invokes the filing program stored in the memory 1005 by the processor 1001 and executes the steps of the filing method as described below.
  • FIG. 2 is a schematic flow chart of a preferred embodiment of the method for filing a case of the present application.
  • the filing method includes:
  • the filing method is applied to a terminal, and the terminal is a terminal as shown in FIG.
  • the terminal is provided with a claim system, and the claim system is used for reporting and filing.
  • step S10 when the case import request is received, the report entry is displayed in the preset interface of the claim system.
  • the triggering manner of the case import request includes:
  • the terminal displays a preset interface of the claim system, such as a main interface, when the user clicks a preset case import button in the main interface to trigger a case import request.
  • a preset interface of the claim system such as a main interface
  • the terminal receives the report request sent by the third party in the service interface of the claim system, performs risk check on the report request, and triggers the case import request based on the report request when the verification is successful. Specifically, receiving the report request sent by the third party, first identifying the parameter information of the report request, extracting the pre-stored judgment rule based on the parameter information, and verifying the parameter information according to the determination rule, if the parameter is detected The information matches the judgment rule, and the verification is determined to be successful. When the verification is successful, a case flag is added to the report request to trigger the case import request according to the added case flag.
  • the terminal Upon receiving the case import request, the terminal displays the report entry in the preset interface of the claim system, and the report entry can be imported into the batch case at one time.
  • the implementation manner of the step S10 includes:
  • the terminal when the terminal receives the request for importing the case in the preset interface of the claim system, the terminal directly displays the batch report entry in the current interface.
  • the user can import the case based on the batch report entry.
  • the third party can send a case to the report entry through the service interface of the claim system.
  • Step S20 importing a batch case from the report entry.
  • the terminal When the terminal receives the batch case from the report entry, the received batch case is imported into the claim system, and the imported batch case is cached in the cache area.
  • the case of batch import is mainly for the case that the insurance policy has a high frequency of occurrence and a small amount of risk in different policies under the same policy or the same insurance.
  • the terminal imports a batch case from the report entry, it is via CSV (Comma-Separated). Values, character-separated values) are imported.
  • the claim system in this embodiment supports an extensible import template, that is, the report entry is available for the operator to set and import the claim data, and can record and download the original data.
  • Step S30 extracting corresponding data fields in each imported case, and comparing the extracted data fields with the pre-stored mapping table to determine a verification rule corresponding to each data field;
  • the terminal After the terminal imports the batch case from the report entry, the terminal extracts the data field corresponding to each case in each imported case, and then compares the extracted fields with the mapping table prestored by the terminal.
  • the data storage field and the corresponding verification rule are stored in the pre-stored mapping table, where a data field corresponds to a verification rule, a data field corresponds to multiple verification rules, or A plurality of data fields correspond to a verification rule, which is specifically set according to actual conditions.
  • the verification rules corresponding to the respective data fields may be determined according to the mapping table.
  • step S40 each of the corresponding cases is reviewed by using each verification rule.
  • the claim settlement plan is generated based on the amount of the compensation corresponding to the case.
  • each verification rule can be used to review each case, that is, whether each data field in each case satisfies the corresponding verification rule.
  • each case in the comparison process between each data field and the verification rule, if the ratio of the number of data fields satisfying the verification rule to the total data field of the case reaches a preset threshold, the case is considered to be correct, and Determining the amount of the claim, in order to generate a corresponding claim plan according to the amount of the case, specifically: after the case is verified by using each check rule, the amount of the case is compensated according to the amount of compensation previously arranged in the case. Add to the case table to generate the corresponding claims plan.
  • the case in the claim system also has a query function, specifically:
  • the query condition corresponding to the query instruction is determined, and the query condition includes a batch number query, an import start and end time query (limited 7-day range), a batch status query, an organization query, and the like. Moreover, when the case is queried, the query can be performed in a preset order, such as in chronological order.
  • the technical solution proposed by the embodiment when receiving the case import request, first displays the report entry in the preset interface of the claim system, and then imports the batch case from the report entry, and extracts corresponding items from the imported cases. Data field, and compare each extracted data field with a pre-stored mapping table to determine a verification rule corresponding to each data field, and finally use each verification rule to review each case, and when the verification is correct, based on The amount of compensation corresponding to the case generates a claim settlement plan.
  • this application examines the case through the verification rules of each case, and carries out subsequent filing, realizing the batch filing of the claims plan, without having to manually file each case separately, and improve the claims.
  • the efficiency and intelligence of filing the case saves manpower.
  • the method further includes:
  • Step S50 after a case import failure occurs, obtaining a case that the import fails;
  • Step S60 storing the failed import case into the preset storage area, and generating a case list based on the case of the failed import, so as to download the corresponding case based on the case list.
  • the terminal imports the batch case from the report entry, if the case import fails, the terminal stores the failed import case in the preset storage area, and the terminal fails to import the case.
  • Obtaining identification information corresponding to the case where the identification information may be a case name or a case number, to generate a case list according to the obtained identification information, and subsequently, the corresponding case may be downloaded from the preset storage area based on the case list. To prevent the case from failing to import, the case could not be found.
  • the failed import case is stored, and the case that the import failed is found according to the case list for downloading and viewing.
  • the third embodiment of the method of filing is different from the first embodiment of the method of filing.
  • the method further includes:
  • Step A when receiving a call request of a third party in a service interface of the claim system, determining a call request sent by the third party;
  • Step B detecting a request type of the call request, and if the request type is one of preset types, receiving a report request of the third party;
  • Step C Perform a risk check on the report request, and after the verification succeeds, trigger the case import request based on the report request.
  • the terminal before the terminal displays the report entry in the preset interface of the claim system according to the case import request, the terminal first determines the trigger mode of the case import request, and if the trigger mode of the case import request is triggered by a third party, then The third party first calls the service interface of the terminal to establish the communication connection.
  • the third party refers to a partner and can be represented by other devices.
  • the method further includes: before the step A, the method further includes:
  • Step D registering a transaction code for the third party, so that the third party invokes the service interface through the transaction code.
  • the terminal needs to register a transaction code (tradecode) for the third party, and the transaction code is unique, and the third party interacts with the terminal's claim system through the transaction code to call The service interface of the claims system.
  • a transaction code tradecode
  • the existing third parties are different.
  • the service interface is preferably a restful interface. Through the restful interface, different types of third parties can call the service interface without setting different interfaces for different third parties, which improves the high availability of data calls.
  • the service data in the claim system in the present embodiment has a specific form of data in the json format, so that each third party can call and receive data.
  • the terminal When the terminal receives the call request of the third party in the service interface of the claim system, the terminal first determines the call request sent by the third party.
  • the call request sent by the third party is determined, which may be Determining the type of the request corresponding to the call request, specifically, determining the type identifier included in the call request to determine whether the request type of the call request is one of the preset types, and if it is one of the preset types, the third party is considered
  • the call request sent is reasonable, and the preset type is set according to the actual situation, and is not limited herein.
  • the terminal receives the report request of the third party.
  • the report request includes information such as the time of the case, the time of the insurance, the policy number, and the amount of the payment.
  • the terminal After receiving the report request sent by the third party, the terminal performs a risk check on the report request. After the verification succeeds, the case import request is triggered based on the report request, that is, the case flag is added in the report request. The case import request is triggered based on the added case flag.
  • the step of performing risk verification on the report request includes:
  • the terminal first identifies the parameter information carried in the report request, and the parameter information, such as the case time, the time of the insurance, the policy number, etc., after extracting the parameter information, extracts the judgment rule according to the parameter information, and then according to the parameter information.
  • the judgment rule verifies the parameter information.
  • the judgment rule is the existing policy number in the system, and the parameter information is verified according to the judgment rule, which is actually comparing the policy number with each existing policy number in the system. To determine whether the policy number exists, if the policy number exists, it is considered that the parameter information matches the judgment rule, and the verification is determined to be successful. Other parameter information and the verification method of the judgment rule are not described in detail.
  • the case import request may be triggered based on the report request, and the report entry is displayed in the preset interface of the claim system based on the case import request, and the subsequent entry is performed.
  • the operation process, the subsequent operation process has been detailed in the above, and will not be described here.
  • the service interface is first set in the claims system, and the transaction code is set to the third party, and the third party terminal that does not have the claim settlement capability can also be implemented by the third party through the service interface.
  • the fourth embodiment of the filing method is different from the first embodiment of the filing method in that, before the step A, the method further includes:
  • Step E extracting a data field in the preset claim application data, and comparing the extracted data field with the pre-stored field;
  • Step F when the data field matches the pre-stored field, determining that the data field is a basic field
  • Step G when the data field does not match the pre-stored field, determine that the data field is an extended field, and add the field to the system;
  • Step H mapping the basic field and the extended field under a transaction code to map a verification rule corresponding to the basic field and the extended field;
  • step I the basic field and the extended field are associated with the corresponding verification rule for subsequent review of the case.
  • the claim application data refers to the claim data having the public basis, and after obtaining the claim application data, the data field is extracted from the claim application data, such as the application time, the application for the claim partner, the application for the payment amount, etc., and then The extracted data field is compared with the pre-stored field.
  • the data field is considered to be a basic field, and when the data field does not match the pre-stored field, the data field is considered to be an extended field. And add this field to the system.
  • the base field and the extension field are mapped under the transaction code. Since the transaction code can uniquely represent the third party, the base field and the extension field are mapped under the transaction code, optionally Determining the current transaction code, configuring a verification rule for the base field of the transaction code, and configuring another verification rule for the extension field of the transaction code to map the verification corresponding to the base field and the extension field of the transaction code. The rule finally stores the base field and the extended field in association with the corresponding verification rule to obtain a mapping table for subsequent review of the case associated with the transaction code.
  • mapping table in the system before the terminal files the case in the claims system, so that the subsequent review of the case can be carried out through the mapping table, thereby realizing the automatic review of the case and improving the filing of the case. Convenience.
  • the verification rule Upon receiving the verification rule modification instruction, the verification rule is adjusted and/or added or deleted according to the verification rule modification instruction.
  • the filing device includes:
  • a display module configured to display a report entry in a preset interface of the claims system when receiving the case import request
  • the comparison module is configured to extract corresponding data fields in each imported case, and compare the extracted data fields with the pre-stored mapping table to determine a verification rule corresponding to each data field;
  • the audit module is used to review each case by using each verification rule.
  • the claim scheme is generated based on the amount of the claim corresponding to the case.
  • the filing device may be a terminal, and the terminal is a terminal as shown in FIG. 1 .
  • the terminal is provided with a claim system, and the claim system is used for reporting and filing.
  • the triggering manner of the case import request includes:
  • the terminal displays a preset interface of the claim system, such as a main interface, when the user clicks a preset case import button in the main interface to trigger a case import request.
  • a preset interface of the claim system such as a main interface
  • the terminal receives the report request sent by the third party in the service interface of the claim system, performs risk check on the report request, and triggers the case import request based on the report request when the verification is successful. Specifically, receiving the report request sent by the third party, first identifying the parameter information of the report request, extracting the pre-stored judgment rule based on the parameter information, and verifying the parameter information according to the determination rule, if the parameter is detected The information matches the judgment rule, and the verification is determined to be successful. When the verification is successful, a case flag is added to the report request to trigger the case import request according to the added case flag.
  • the terminal Upon receiving the case import request, the terminal displays the report entry in the preset interface of the claim system, and the report entry can be imported into the batch case at one time.
  • the implementation manner of the display module for displaying the report entry in the preset interface of the claim system when receiving the case import request includes:
  • the terminal when the terminal receives the request for importing the case in the preset interface of the claim system, the terminal directly displays the batch report entry in the current interface.
  • the user can import the case based on the batch report entry.
  • the third party can send a case to the report entry through the service interface of the claim system.
  • the terminal When the terminal receives the batch case from the report entry, the received batch case is imported into the claim system, and the imported batch case is cached in the cache area.
  • the case of batch import is mainly for the case that the insurance policy has a high frequency of occurrence and a small amount of risk in different policies under the same policy or the same insurance.
  • the terminal imports a batch case from the report entry, it is via CSV (Comma-Separated). Values, character-separated values) are imported.
  • the claim system in this embodiment supports an extensible import template, that is, the report entry is available for the operator to set and import the claim data, and can record and download the original data.
  • the terminal After the terminal imports the batch case from the report entry, the terminal extracts the data field corresponding to each case in each imported case, and then compares the extracted fields with the mapping table prestored by the terminal.
  • the data storage field and the corresponding verification rule are stored in the pre-stored mapping table, where a data field corresponds to a verification rule, a data field corresponds to multiple verification rules, or A plurality of data fields correspond to a verification rule, which is specifically set according to actual conditions.
  • the verification rules corresponding to the respective data fields may be determined according to the mapping table.
  • each verification rule can be used to review each case, that is, whether each data field in each case satisfies the corresponding verification rule.
  • each case in the comparison process between each data field and the verification rule, if the ratio of the number of data fields satisfying the verification rule to the total data field of the case reaches a preset threshold, the case is considered to be correct, and Determining the amount of the claim, in order to generate a corresponding claim plan according to the amount of the case, specifically: after the case is verified by using each check rule, the amount of the case is compensated according to the amount of compensation previously arranged in the case. Add to the case table to generate the corresponding claims plan.
  • the case in the claim system also has a query function, specifically:
  • the query condition corresponding to the query instruction is determined, and the query condition includes a batch number query, an import start and end time query (limited 7-day range), a batch status query, an organization query, and the like. Moreover, when the case is queried, the query can be performed in a preset order, such as in chronological order.
  • the technical solution proposed by the embodiment when receiving the case import request, first displays the report entry in the preset interface of the claim system, and then imports the batch case from the report entry, and extracts corresponding items from the imported cases. Data field, and compare each extracted data field with a pre-stored mapping table to determine a verification rule corresponding to each data field, and finally use each verification rule to review each case, and when the verification is correct, based on The amount of compensation corresponding to the case generates a claim settlement plan.
  • this application examines the case through the verification rules of each case, and carries out subsequent filing, realizing the batch filing of the claims plan, without having to manually file each case separately, and improve the claims.
  • the efficiency and intelligence of filing the case saves manpower.
  • the obtaining module is configured to obtain a case that the import failed after the case fails to be imported;
  • the first storage module is configured to store the failed import case into the preset storage area, and generate a case list based on the failed import case, so as to download the corresponding case based on the case list.
  • the terminal imports the batch case from the report entry, if the case import fails, the terminal stores the failed import case in the preset storage area, and the terminal fails to import the case.
  • Obtaining identification information corresponding to the case where the identification information may be a case name or a case number, to generate a case list according to the obtained identification information, and subsequently, the corresponding case may be downloaded from the preset storage area based on the case list. To prevent the case from failing to import, the case could not be found.
  • the failed import case is stored, and the case that the import failed is found according to the case list for downloading and viewing.
  • a judging module configured to determine, when the third party call request is received in the service interface of the claim system, the call request sent by the third party;
  • a detecting module configured to detect a request type of the calling request, and if the request type is one of preset types, receiving a report request of the third party;
  • the verification module is configured to perform a risk check on the report request, and after the verification succeeds, trigger the case import request based on the report request.
  • the terminal before the terminal displays the report entry in the preset interface of the claim system according to the case import request, the terminal first determines the trigger mode of the case import request, and if the trigger mode of the case import request is triggered by a third party, then The third party first calls the service interface of the terminal to establish the communication connection.
  • the third party refers to a partner and can be represented by other devices.
  • the device further comprises:
  • a registration module for registering a transaction code for the third party to cause the third party to invoke the service interface via a transaction code.
  • the terminal needs to register a transaction code (tradecode) for the third party, and the transaction code is unique, and the third party interacts with the terminal's claim system through the transaction code to call The service interface of the claims system.
  • a transaction code tradecode
  • the existing third parties are different.
  • the service interface is preferably a restful interface. Through the restful interface, different types of third parties can call the service interface without setting different interfaces for different third parties, which improves the high availability of data calls.
  • the service data in the claim system in the present embodiment has a specific form of data in the json format, so that each third party can call and receive data.
  • the terminal When the terminal receives the call request of the third party in the service interface of the claim system, the terminal first determines the call request sent by the third party.
  • the call request sent by the third party is determined, which may be Determining the type of the request corresponding to the call request, specifically, determining the type identifier included in the call request to determine whether the request type of the call request is one of the preset types, and if it is one of the preset types, the third party is considered
  • the call request sent is reasonable, and the preset type is set according to the actual situation, and is not limited herein.
  • the terminal receives the report request of the third party.
  • the report request includes information such as the time of the case, the time of the insurance, the policy number, and the amount of the payment.
  • the terminal After receiving the report request sent by the third party, the terminal performs a risk check on the report request. After the verification succeeds, the case import request is triggered based on the report request, that is, the case flag is added in the report request. The case import request is triggered based on the added case flag.
  • the verification module is further configured to identify parameter information of the report request, extract a pre-stored determination rule based on the parameter information, and verify the parameter information according to the determination rule; If the parameter information matches the determination rule, it is determined that the verification is successful.
  • the terminal first identifies the parameter information carried in the report request, and the parameter information, such as the case time, the time of the insurance, the policy number, etc., after extracting the parameter information, extracts the judgment rule according to the parameter information, and then according to the parameter information.
  • the judgment rule verifies the parameter information.
  • the judgment rule is the existing policy number in the system, and the parameter information is verified according to the judgment rule, which is actually comparing the policy number with each existing policy number in the system. To determine whether the policy number exists, if the policy number exists, it is considered that the parameter information matches the judgment rule, and the verification is determined to be successful. Other parameter information and the verification method of the judgment rule are not described in detail.
  • the case import request may be triggered based on the report request, and the report entry is displayed in the preset interface of the claim system based on the case import request, and the subsequent entry is performed.
  • the operation process, the subsequent operation process has been detailed in the above, and will not be described here.
  • the service interface is first set in the claims system, and the transaction code is set to the third party, and the third party terminal that does not have the claim settlement capability can also be implemented by the third party through the service interface.
  • the extracting module is configured to extract a data field in the preset claim application data, and compare the extracted data field with the pre-stored field;
  • a determining module configured to determine that the data field is a basic field when the data field matches the pre-stored field
  • the determining module is further configured to: when the data field does not match the pre-stored field, determine that the data field is an extended field, and add the field to the system;
  • mapping module configured to map the basic field and the extended field under a transaction code to map a verification rule corresponding to the basic field and the extended field;
  • the second storage module is configured to store the basic field and the extended field in association with the corresponding verification rule, so as to subsequently review the case.
  • the claim application data refers to the claim data having the public basis, and after obtaining the claim application data, the data field is extracted from the claim application data, such as the application time, the application for the claim partner, the application for the payment amount, etc., and then The extracted data field is compared with the pre-stored field.
  • the data field is considered to be a basic field, and when the data field does not match the pre-stored field, the data field is considered to be an extended field. And add this field to the system.
  • the base field and the extension field are mapped under the transaction code. Since the transaction code can uniquely represent the third party, the base field and the extension field are mapped under the transaction code, optionally Determining the current transaction code, configuring a verification rule for the base field of the transaction code, and configuring another verification rule for the extension field of the transaction code to map the verification corresponding to the base field and the extension field of the transaction code. The rule finally stores the base field and the extended field in association with the corresponding verification rule to obtain a mapping table for subsequent review of the case associated with the transaction code.
  • mapping table in the system before the terminal files the case in the claims system, so that the subsequent review of the case can be carried out through the mapping table, thereby realizing the automatic review of the case and improving the filing of the case. Convenience.
  • a modification module configured to: when the verification rule modification instruction is received, modify the verification rule according to the verification rule modification instruction, and/or add or delete the verification rule.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a filing program, and when the filing program is executed by the processor, the steps of the filing method as described above are implemented.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Technology Law (AREA)
  • Primary Health Care (AREA)
  • Health & Medical Sciences (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)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请公开了一种立案方法，所述方法包括：在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口；从所述报案入口导入批量案件；在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。本申请还公开了一种立案装置、终端和计算机可读存储介质。本申请提高了理赔立案的效率和智能性，节省了人力。

Description

立案方法、装置、终端和计算机可读存储介质
本申请要求于2017年06月22日提交中国专利局、申请号为201710483564.9、发明名称为“立案方法、终端和计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种立案方法、装置、终端和计算机可读存储介质。
背景技术
现有的报案立案服务，在案件量大的情况下，由于案件的赔付、以及各种参数不同，需要人工对案件逐个处理，导致案件的处理周期较长，降低了立案的效率，并且，由人工进行立案，对立案的智能性也较差。
发明内容
本申请的主要目的在于提供一种立案方法、装置、终端和计算机可读存储介质，旨在解决现有的立案方式，立案效率低和智能性差的技术问题。
为实现上述目的，本申请提供一种立案方法，所述立案方法包括：
在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口；
从所述报案入口导入批量案件；
在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；
采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。
此外，为实现上述目的，本申请还提供一种立案装置，所述立案装置包括：
显示模块，用于在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口；
导入模块，用于从所述报案入口导入批量案件；
比对模块，用于在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；
审核模块，用于采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。
此外，为实现上述目的，本申请还提供一种终端，所述终端包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的立案程序，所述立案程序被所述处理器执行时实现如上文所述的立案方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有立案程序，所述立案程序被处理器执行时实现如上文所述的立案方法的步骤。
本申请提出的技术方案，在接收到案件导入请求时，先在理赔系统的预设界面中显示报案入口，然后从所述报案入口导入批量案件，再从导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则，最终采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。本申请在案件量大的情况下，通过各个案件的校验规则，对案件进行审核，并进行后续的立案，实现了理赔方案的批量立案，无须人工对每个案件分别进行立案，提高了理赔立案的效率和智能性，节省了人力。
附图说明
图1是本申请实施例方案涉及的硬件运行环境的终端结构示意图；
图2为本申请立案方法第一实施例的流程示意图；
图3为本申请立案方法第二实施例的流程示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请实施例的解决方案主要是：在接收到案件导入请求时，先在理赔系统的预设界面中显示报案入口，然后从所述报案入口导入批量案件，再从导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则，最终采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。以解决现有的立案方式智能性差，效率低的问题。
如图1所示，图1是本申请实施例方案涉及的硬件运行环境的终端结构示意图。
本申请实施例设备可以是PC，也可以是智能手机、平板电脑、电子书阅读器、便携计算机等具有显示功能的可移动式终端设备。
如图1所示，该设备可以包括：处理器1001，例如CPU，通信总线1002、用户接口1003，网络接口1004，存储器1005。其中，通信总线1002用于实现这些组件之间的连接通信。用户接口1003可以包括显示屏（Display）、输入单元比如键盘（Keyboard），可选用户接口1003还可以包括标准的有线接口、无线接口。网络接口1004可选的可以包括标准的有线接口、无线接口（如WI-FI接口）。存储器1005可以是高速RAM存储器，也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
可选地，设备还可以包括摄像头、RF（Radio Frequency，射频）电路，传感器、音频电路、WiFi模块等等。
本领域技术人员可以理解，图1中示出的设备结构并不构成对设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图1所示，作为一种计算机可读存储介质的存储器1005中可以包括操作系统、网络通信模块、用户接口模块以及立案程序。其中，操作系统是管理和控制终端与软件资源的程序，支持网络通信模块、用户接口模块、立案程序以及其他程序或软件的运行；网络通信模块用于管理和控制网络接口1002；用户接口模块用于管理和控制用户接口1003。
在图1所示的终端中，网络接口1004主要用于连接理赔系统平台，与理赔系统平台进行数据通信；用户接口1003主要用于连接客户端（用户端），与客户端进行数据通信；所述终端通过处理器1001调用存储器1005中存储的立案程序，并执行如下文所述的立案方法的步骤。
基于上述设备硬件结构，提出本申请立案方法实施例。
参照图2，图2为本申请立案方法较佳实施例的流程示意图。
在本实施例中，所述立案方法包括：
在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口；从所述报案入口导入批量案件；在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。
在本实施例中，所述立案方法应用于终端，所述终端如图1所示的终端。所述终端设有理赔系统，所述理赔系统用于报案和立案。
以下是本实施例中实现立案的具体步骤：
步骤S10，在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口。
在本实施例中，所述案件导入请求的触发方式包括：
a、终端显示理赔系统的预设界面，如主界面，当用户在所述主界面中点击预设的案件导入按钮，以触发案件导入请求。
b、终端在理赔系统的服务接口中接收第三方发送的报案请求，对所述报案请求进行风险校验，在校验成功时，基于该报案请求触发案件导入请求。具体地：接收第三方发送的报案请求，先识别所述报案请求的参数信息，基于所述参数信息提取预存的判断规则，根据所述判断规则校验所述参数信息，若检测到所述参数信息与所述判断规则匹配，确定校验成功。在校验成功时，在报案请求中添加案件标志位，以根据添加的案件标志位，触发案件导入请求。
在接收到案件导入请求时，终端在理赔系统的预设界面中显示报案入口，该报案入口可一次性导入批量案件。
本实施例中，所述步骤S10的实施方式包括：
方式一、当终端在理赔系统的第一预设界面接收得到所述案件导入请求时，跳转至第二预设界面中显示批量报案入口。
方式二、终端在理赔系统的预设界面接收得到所述案件导入请求时，直接在当前界面中显示批量报案入口。
当终端在理赔系统的预设界面中显示批量报案入口之后，用户可基于该批量报案入口导入案件。此外，当终端在理赔系统的预设界面中显示批量报案入口之后，第三方可通过所述理赔系统的服务接口向报案入口发送案件。
步骤S20，从所述报案入口导入批量案件。
当终端从所述报案入口接收到批量案件时，将接收到的批量案件导入到理赔系统中，并将导入的批量案件缓存到缓存区中。
需要说明的是，本实施例中，批量导入的案件主要针对同一保单或同一险种下的不同保单中出险频率高，出险金额小的案件。并且，终端从报案入口中导入批量案件时，是通过CSV（Comma-Separated Values，字符分隔值）的方式进行导入。
本实施例中，理赔系统中的案件批量导入存在以下四种情况：1、单一保单支付同一领款人；2、多个保单支付同一领款人；3、单一保单支付多个领款人；4、多个保单支付多个领款人。
为提升理赔处理效率及体验，本实施例中的理赔系统支持可扩展的导入模板，即该报案入口可供操作人员设置、导入理赔数据，并可记录下载原始数据。
步骤S30，在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；
在终端从报案入口中导入批量案件之后，终端在导入的各个案件中抽取出每个案件对应的数据字段，然后将抽取的各个字段与终端预存的映射表进行比对。在本实施例中，所述预存映射表中存储有数据字段以及对应的校验规则，其中，可以是一种数据字段对应一种校验规则、一种数据字段对应多种校验规则、或多种数据字段对应一种校验规则，具体根据实际情况设定。在抽取的各个数据字段与预存的映射表进行比对之后，即可根据该映射表确定各个数据字段对应的校验规则。
步骤S40，采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。
在确定各个数据字段对应的校验规则之后，即可采用各个校验规则对对应的各个案件进行审核，也就是确定各个案件中的各个数据字段是否满足对应的校验规则，本实施例中，对于每一个案件，在各个数据字段与校验规则的比对过程中，若满足校验规则的数据字段的个数占该案件总数据字段的比例达到预设阈值，认为该案件审核无误，并确定该案件的赔付金额，以根据该案件的赔付金额生成对应的理赔方案，具体地：在采用各个校验规则对案件审核无误后，根据该案件事先配置的赔付金额，将该案件的赔付金额添加到案件表中，以生成对应的理赔方案。
此外，本实施例中，所述理赔系统中的案件还具有查询功能，具体地：
在接收到查询指令时，确定所述查询指令对应的查询条件，该查询条件包括批次号查询、导入起止时间查询（限定7天范围）、批次状态查询、机构查询等。并且，查询案件时，可按照预设的顺序进行查询，如按照时间顺序。
本实施例提出的技术方案，在接收到案件导入请求时，先在理赔系统的预设界面中显示报案入口，然后从所述报案入口导入批量案件，再从导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则，最终采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。本申请在案件量大的情况下，通过各个案件的校验规则，对案件进行审核，并进行后续的立案，实现了理赔方案的批量立案，无须人工对每个案件分别进行立案，提高了理赔立案的效率和智能性，节省了人力。
进一步地，基于第一实施例提出本申请立案方法的第二实施例。
立案方法的第二实施例与立案方法的第一实施例的区别在于，参照图3，所述步骤S20之后，所述方法还包括：
步骤S50，在有案件导入失败后，获取导入失败的案件；
步骤S60，将导入失败的案件存储到预设存储区中，并基于导入失败的案件生成案件清单，以便后续基于所述案件清单下载对应的案件。
在本实施例中，在终端从所述报案入口导入批量案件之后，若有案件导入失败，则终端将该导入失败的案件存储到预设存储区中，同时，所述终端在导入失败的案件中获取案件对应的标识信息，所述标识信息可为案件名称或案件标号，以根据获取的标识信息生成案件清单，后续，可基于该案件清单，从所述预设存储区中下载对应的案件，防止案件导入失败时，找不到该案件。
本实施例中，在案件导入失败后，将导入失败的案件存储起来，后续可根据案件清单找到该导入失败的案件进行下载和查看。
进一步地，基于第一实施例提出本申请立案方法的第三实施例。
立案方法的第三实施例与立案方法的第一实施例的区别在于，所述步骤S10之前，所述方法还包括：
步骤A，在理赔系统的服务接口中接收到第三方的调用请求时，对所述第三方发送的调用请求进行判断；
步骤B，检测所述调用请求的请求类型，若所述请求类型是预设类型之一，接收所述第三方的报案请求；
步骤C，对所述报案请求进行风险校验，校验成功后，基于所述报案请求触发所述案件导入请求。
在本实施例中，终端根据案件导入请求在理赔系统的预设界面中显示报案入口之前，先确定该案件导入请求的触发方式，若该案件导入请求的触发方式是由第三方触发的，那么，第三方先调用终端的服务接口，以实现通信连接的建立。本实施例中，所述第三方指合作方，可以用其它设备表示。
其中，所述步骤A之前，所述方法还包括：
步骤D，为所述第三方注册交易代码，以使所述第三方通过交易代码调用所述服务接口。
也就是说，第三方要与终端的理赔系统交互之前，终端需要为第三方注册一个交易代码（tradecode），该交易代码具有唯一性，第三方通过该交易代码与终端的理赔系统交互，以调用理赔系统的服务接口。
本实施例中，需要说明的是，现有的各个第三方各不相同，为了保证不同的第三方都可以使得该理赔系统，所述服务接口优选为restful接口。通过该restful接口，可以让不同类型的第三方都可以调用该服务接口，无须针对不同的第三方设置不同的接口，提高了数据调用的高可用性。
此外，还需要说明的是，本实施中所述理赔系统中的业务数据，具体的表现形式是json格式的数据，以满足各个第三方都可以调用并接收数据。
当终端在理赔系统的服务接口中接收到第三方的调用请求时，先对所述第三方发送的调用请求进行判断，本实施例中，对所述第三方发送的调用请求进行判断，可以是对调用请求对应的请求类型进行判断，具体地，对调用请求中包含的类型标识进行判断，以确定该调用请求的请求类型是否为预设类型之一，若是预设类型之一，认为第三方发送的调用请求合理，所述预设类型根据实际情况设置，此处不做限定。在所述第三方发送的调用请求合理的情况下，终端再接收所述第三方的报案请求，本实施例中，所述报案请求中包括案件时间、出险时间、保单号、赔付金额等信息。终端接收到第三方发送的报案请求之后，再对所述报案请求进行风险校验，在校验成功后，基于所述报案请求触发所述案件导入请求，即在报案请求中添加案件标志位，以根据添加的案件标志位，触发案件导入请求。
本实施例中，所述“对所述报案请求进行风险校验”的步骤包括：
识别所述报案请求的参数信息；
基于所述参数信息提取预存的判断规则；
根据所述判断规则校验所述参数信息；
若检测到所述参数信息与所述判断规则匹配，则确定校验成功。
也就是说，终端先识别该报案请求中携带的参数信息，所述参数信息如上文的案件时间、出险时间、保单号等，在提取出参数信息之后，再根据参数信息提取判断规则，然后根据判断规则校验所述参数信息。为了更好理解本实施例，举例如下：
在参数信息为保单号时，该判断规则就是系统中已有的各个保单号，根据判断规则校验该参数信息，实际上就是将该保单号与系统中已有的各个保单号进行比对，以确定该保单号是否存在，若该保单号存在，认为该参数信息与判断规则匹配，此时确定校验成功。其它参数信息与判断规则的校验方式不在一一赘述。
在对报案请求进行风险校验，并且检验成功后，即可基于所述报案请求触发所述案件导入请求，并基于该案件导入请求在理赔系统的预设界面中显示报案入口，以及执行后续的操作过程，后续的操作过程已经在上文中详述，此处不再赘述。
在本实施例中，先在理赔系统中设置服务接口，并对第三方设置交易代码，由第三方通过该服务接口调用该终端的理赔系统，使得不具备理赔立案能力的第三方终端也可以实现立案，并且将服务接口设置为restful接口，各个第三方都可以调用，无须针对不同的第三方开发不同的接口，节省了成本。
进一步地，基于第一实施例提出本申请立案方法的第四实施例。
立案方法的第四实施例与立案方法的第一实施例的区别在于，所述步骤A之前，所述方法还包括：
步骤E，在预设理赔申请数据中抽取数据字段，将抽取的数据字段与预存字段进行比对；
步骤F，当数据字段与预存字段匹配时，确定所述数据字段为基础字段；
步骤G，当数据字段与预存字段不匹配时，确定所述数据字段为扩展字段，并将该字段添加在系统中；
步骤H，对所述基础字段和所述扩展字段在交易代码下进行映射，以映射出基础字段和扩展字段对应的校验规则；
步骤I，将基础字段和扩展字段与对应的校验规则进行关联存储，以便后续对案件进行审核。
在本实施例中，在理赔系统的服务接口中接收到第三方的调用请求时，并对所述第三方发送的调用请求进行判断之前，先在理赔系统中，获取预设理赔申请数据，该理赔申请数据是指有公共基础的理赔申请数据，在获取到该理赔申请数据之后，从所述理赔申请数据中抽取出数据字段，如申请时间、申请理赔合作方、申请赔付金额等，然后将抽取的数据字段与预存字段进行比对，在检测到数据字段与预存字段匹配时，认为该数据字段为基础字段，而在该数据字段与预存字段不匹配时，认为所述数据字段为扩展字段，并将该字段添加在系统中。接着，对所述基础字段和所述扩展字段在交易代码下进行映射，由于交易代码可唯一表示第三方，因此，对所述基础字段和所述扩展字段在交易代码下进行映射，可选为：确定当前的交易代码，对该交易代码的基础字段配置校验规则，并对该交易代码的扩展字段配置另一个校验规则，以映射出该交易代码下基础字段和扩展字段对应的校验规则，最终将基础字段和扩展字段与对应的校验规则进行关联存储，以得到映射表，以便后续对该交易代码关联的案件进行审核。
在本实施例中，相当于是终端在理赔系统中进行报案立案之前，先在系统中存储映射表，以便后续对案件审核时，通过该映射表进行审核，实现了案件的自动审核，提高了立案的便捷性。
进一步地，基于第一至第四实施例提出本申请立案方法的第五实施例。
立案方法的第五实施例与立案方法的第一至第四实施例的区别在于，所述方法还包括：
在接收到校验规则修改指令时，根据所述校验规则修改指令对校验规则进行调整和/或增删。
在本实施例中，相当于是该校验规则可以根据实际进行修改，以根据修改后校验规则对案件进行审核。
进一步地，提出本申请立案装置实施例。
在本实施例中，所述立案装置包括：
显示模块，用于在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口；
导入模块，用于从所述报案入口导入批量案件；
比对模块，用于在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；
审核模块，用于采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。
在本实施例中，所述立案装置可选为终端，所述终端如图1所示的终端。所述终端设有理赔系统，所述理赔系统用于报案和立案。
在本实施例中，所述案件导入请求的触发方式包括：
a、终端显示理赔系统的预设界面，如主界面，当用户在所述主界面中点击预设的案件导入按钮，以触发案件导入请求。
b、终端在理赔系统的服务接口中接收第三方发送的报案请求，对所述报案请求进行风险校验，在校验成功时，基于该报案请求触发案件导入请求。具体地：接收第三方发送的报案请求，先识别所述报案请求的参数信息，基于所述参数信息提取预存的判断规则，根据所述判断规则校验所述参数信息，若检测到所述参数信息与所述判断规则匹配，确定校验成功。在校验成功时，在报案请求中添加案件标志位，以根据添加的案件标志位，触发案件导入请求。
在接收到案件导入请求时，终端在理赔系统的预设界面中显示报案入口，该报案入口可一次性导入批量案件。
本实施例中，所述显示模块用于在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口的实施方式包括：
方式一、当终端在理赔系统的第一预设界面接收得到所述案件导入请求时，跳转至第二预设界面中显示批量报案入口。
方式二、终端在理赔系统的预设界面接收得到所述案件导入请求时，直接在当前界面中显示批量报案入口。
当终端在理赔系统的预设界面中显示批量报案入口之后，用户可基于该批量报案入口导入案件。此外，当终端在理赔系统的预设界面中显示批量报案入口之后，第三方可通过所述理赔系统的服务接口向报案入口发送案件。
当终端从所述报案入口接收到批量案件时，将接收到的批量案件导入到理赔系统中，并将导入的批量案件缓存到缓存区中。
需要说明的是，本实施例中，批量导入的案件主要针对同一保单或同一险种下的不同保单中出险频率高，出险金额小的案件。并且，终端从报案入口中导入批量案件时，是通过CSV（Comma-Separated Values，字符分隔值）的方式进行导入。
本实施例中，理赔系统中的案件批量导入存在以下四种情况：1、单一保单支付同一领款人；2、多个保单支付同一领款人；3、单一保单支付多个领款人；4、多个保单支付多个领款人。
为提升理赔处理效率及体验，本实施例中的理赔系统支持可扩展的导入模板，即该报案入口可供操作人员设置、导入理赔数据，并可记录下载原始数据。
在终端从报案入口中导入批量案件之后，终端在导入的各个案件中抽取出每个案件对应的数据字段，然后将抽取的各个字段与终端预存的映射表进行比对。在本实施例中，所述预存映射表中存储有数据字段以及对应的校验规则，其中，可以是一种数据字段对应一种校验规则、一种数据字段对应多种校验规则、或多种数据字段对应一种校验规则，具体根据实际情况设定。在抽取的各个数据字段与预存的映射表进行比对之后，即可根据该映射表确定各个数据字段对应的校验规则。
在确定各个数据字段对应的校验规则之后，即可采用各个校验规则对对应的各个案件进行审核，也就是确定各个案件中的各个数据字段是否满足对应的校验规则，本实施例中，对于每一个案件，在各个数据字段与校验规则的比对过程中，若满足校验规则的数据字段的个数占该案件总数据字段的比例达到预设阈值，认为该案件审核无误，并确定该案件的赔付金额，以根据该案件的赔付金额生成对应的理赔方案，具体地：在采用各个校验规则对案件审核无误后，根据该案件事先配置的赔付金额，将该案件的赔付金额添加到案件表中，以生成对应的理赔方案。
此外，本实施例中，所述理赔系统中的案件还具有查询功能，具体地：
在接收到查询指令时，确定所述查询指令对应的查询条件，该查询条件包括批次号查询、导入起止时间查询（限定7天范围）、批次状态查询、机构查询等。并且，查询案件时，可按照预设的顺序进行查询，如按照时间顺序。
本实施例提出的技术方案，在接收到案件导入请求时，先在理赔系统的预设界面中显示报案入口，然后从所述报案入口导入批量案件，再从导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则，最终采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。本申请在案件量大的情况下，通过各个案件的校验规则，对案件进行审核，并进行后续的立案，实现了理赔方案的批量立案，无须人工对每个案件分别进行立案，提高了理赔立案的效率和智能性，节省了人力。
进一步地，基于第一实施例提出本申请立案装置的第二实施例。
立案装置的第二实施例与立案装置的第一实施例的区别在于，所述装置还包括：
获取模块，用于在有案件导入失败后，获取导入失败的案件；
第一存储模块，用于将导入失败的案件存储到预设存储区中，并基于导入失败的案件生成案件清单，以便后续基于所述案件清单下载对应的案件。
在本实施例中，在终端从所述报案入口导入批量案件之后，若有案件导入失败，则终端将该导入失败的案件存储到预设存储区中，同时，所述终端在导入失败的案件中获取案件对应的标识信息，所述标识信息可为案件名称或案件标号，以根据获取的标识信息生成案件清单，后续，可基于该案件清单，从所述预设存储区中下载对应的案件，防止案件导入失败时，找不到该案件。
本实施例中，在案件导入失败后，将导入失败的案件存储起来，后续可根据案件清单找到该导入失败的案件进行下载和查看。
进一步地，基于第一实施例提出本申请立案装置的第三实施例。
立案装置的第三实施例与立案装置的第一实施例的区别在于，所述装置还包括：
判断模块，用于在理赔系统的服务接口中接收到第三方的调用请求时，对所述第三方发送的调用请求进行判断；
检测模块，用于检测所述调用请求的请求类型，若所述请求类型是预设类型之一，接收所述第三方的报案请求；
校验模块，用于对所述报案请求进行风险校验，校验成功后，基于所述报案请求触发所述案件导入请求。
在本实施例中，终端根据案件导入请求在理赔系统的预设界面中显示报案入口之前，先确定该案件导入请求的触发方式，若该案件导入请求的触发方式是由第三方触发的，那么，第三方先调用终端的服务接口，以实现通信连接的建立。本实施例中，所述第三方指合作方，可以用其它设备表示。
其中，所述装置还包括：
注册模块，用于为所述第三方注册交易代码，以使所述第三方通过交易代码调用所述服务接口。
也就是说，第三方要与终端的理赔系统交互之前，终端需要为第三方注册一个交易代码（tradecode），该交易代码具有唯一性，第三方通过该交易代码与终端的理赔系统交互，以调用理赔系统的服务接口。
本实施例中，需要说明的是，现有的各个第三方各不相同，为了保证不同的第三方都可以使得该理赔系统，所述服务接口优选为restful接口。通过该restful接口，可以让不同类型的第三方都可以调用该服务接口，无须针对不同的第三方设置不同的接口，提高了数据调用的高可用性。
此外，还需要说明的是，本实施中所述理赔系统中的业务数据，具体的表现形式是json格式的数据，以满足各个第三方都可以调用并接收数据。
当终端在理赔系统的服务接口中接收到第三方的调用请求时，先对所述第三方发送的调用请求进行判断，本实施例中，对所述第三方发送的调用请求进行判断，可以是对调用请求对应的请求类型进行判断，具体地，对调用请求中包含的类型标识进行判断，以确定该调用请求的请求类型是否为预设类型之一，若是预设类型之一，认为第三方发送的调用请求合理，所述预设类型根据实际情况设置，此处不做限定。在所述第三方发送的调用请求合理的情况下，终端再接收所述第三方的报案请求，本实施例中，所述报案请求中包括案件时间、出险时间、保单号、赔付金额等信息。终端接收到第三方发送的报案请求之后，再对所述报案请求进行风险校验，在校验成功后，基于所述报案请求触发所述案件导入请求，即在报案请求中添加案件标志位，以根据添加的案件标志位，触发案件导入请求。
本实施例中，所述校验模块，还用于识别所述报案请求的参数信息；基于所述参数信息提取预存的判断规则；根据所述判断规则校验所述参数信息；若检测到所述参数信息与所述判断规则匹配，则确定校验成功。
也就是说，终端先识别该报案请求中携带的参数信息，所述参数信息如上文的案件时间、出险时间、保单号等，在提取出参数信息之后，再根据参数信息提取判断规则，然后根据判断规则校验所述参数信息。为了更好理解本实施例，举例如下：
在参数信息为保单号时，该判断规则就是系统中已有的各个保单号，根据判断规则校验该参数信息，实际上就是将该保单号与系统中已有的各个保单号进行比对，以确定该保单号是否存在，若该保单号存在，认为该参数信息与判断规则匹配，此时确定校验成功。其它参数信息与判断规则的校验方式不在一一赘述。
在对报案请求进行风险校验，并且检验成功后，即可基于所述报案请求触发所述案件导入请求，并基于该案件导入请求在理赔系统的预设界面中显示报案入口，以及执行后续的操作过程，后续的操作过程已经在上文中详述，此处不再赘述。
在本实施例中，先在理赔系统中设置服务接口，并对第三方设置交易代码，由第三方通过该服务接口调用该终端的理赔系统，使得不具备理赔立案能力的第三方终端也可以实现立案，并且将服务接口设置为restful接口，各个第三方都可以调用，无须针对不同的第三方开发不同的接口，节省了成本。
进一步地，基于第一实施例提出本申请立案装置的第四实施例。
立案装置的第四实施例与立案装置的第一实施例的区别在于，所述装置还包括：
抽取模块，用于在预设理赔申请数据中抽取数据字段，将抽取的数据字段与预存字段进行比对；
确定模块，用于当数据字段与预存字段匹配时，确定所述数据字段为基础字段；
所述确定模块，还用于当数据字段与预存字段不匹配时，确定所述数据字段为扩展字段，并将该字段添加在系统中；
映射模块，用于对所述基础字段和所述扩展字段在交易代码下进行映射，以映射出基础字段和扩展字段对应的校验规则；
第二存储模块，用于将基础字段和扩展字段与对应的校验规则进行关联存储，以便后续对案件进行审核。
在本实施例中，在理赔系统的服务接口中接收到第三方的调用请求时，并对所述第三方发送的调用请求进行判断之前，先在理赔系统中，获取预设理赔申请数据，该理赔申请数据是指有公共基础的理赔申请数据，在获取到该理赔申请数据之后，从所述理赔申请数据中抽取出数据字段，如申请时间、申请理赔合作方、申请赔付金额等，然后将抽取的数据字段与预存字段进行比对，在检测到数据字段与预存字段匹配时，认为该数据字段为基础字段，而在该数据字段与预存字段不匹配时，认为所述数据字段为扩展字段，并将该字段添加在系统中。接着，对所述基础字段和所述扩展字段在交易代码下进行映射，由于交易代码可唯一表示第三方，因此，对所述基础字段和所述扩展字段在交易代码下进行映射，可选为：确定当前的交易代码，对该交易代码的基础字段配置校验规则，并对该交易代码的扩展字段配置另一个校验规则，以映射出该交易代码下基础字段和扩展字段对应的校验规则，最终将基础字段和扩展字段与对应的校验规则进行关联存储，以得到映射表，以便后续对该交易代码关联的案件进行审核。
在本实施例中，相当于是终端在理赔系统中进行报案立案之前，先在系统中存储映射表，以便后续对案件审核时，通过该映射表进行审核，实现了案件的自动审核，提高了立案的便捷性。
进一步地，基于第一至第四实施例提出本申请立案装置的第五实施例。
立案装置的第五实施例与立案装置的第一至第四实施例的区别在于，所述装置还包括：
修改模块，用于在接收到校验规则修改指令时，根据所述校验规则修改指令对校验规则进行调整和/或增删。
在本实施例中，相当于是该校验规则可以根据实际进行修改，以根据修改后校验规则对案件进行审核。
此外，本申请实施例还提出一种计算机可读存储介质，所述计算机可读存储介质上存储有立案程序，所述立案程序被处理器执行时实现如上文所述的立案方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其它变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其它要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质（如ROM/RAM、磁碟、光盘）中，包括若干指令用以使得一台终端设备（可以是手机，计算机，服务器，空调器，或者网络设备等）执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其它相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种立案方法，其特征在于，所述立案方法包括：
    在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口；
    从所述报案入口导入批量案件；
    在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；
    采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。
  2. 如权利要求1所述的立案方法，其特征在于，所述从所述报案入口导入批量案件的步骤之后，所述方法还包括：
    在有案件导入失败后，获取导入失败的案件；
    将导入失败的案件存储到预设存储区中，并基于导入失败的案件生成案件清单，以便后续基于所述案件清单下载对应的案件。
  3. 如权利要求1所述的立案方法，其特征在于，所述在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口的步骤之前，所述方法还包括：
    在理赔系统的服务接口中接收到第三方的调用请求时，对所述第三方发送的调用请求进行判断；
    检测所述调用请求的请求类型，若所述请求类型是预设类型之一，接收所述第三方的报案请求；
    对所述报案请求进行风险校验，校验成功后，基于所述报案请求触发所述案件导入请求。
  4. 如权利要求3所述的立案方法，其特征在于，所述在理赔系统的服务接口中接收到第三方的调用请求时，对所述第三方发送的调用请求进行判断的步骤之前，所述方法还包括：
    为所述第三方注册交易代码，以使所述第三方通过交易代码调用所述服务接口。
  5. 如权利要求3所述的立案方法，其特征在于，所述对所述报案请求进行风险校验的步骤包括：
    识别所述报案请求的参数信息；
    基于所述参数信息提取预存的判断规则；
    根据所述判断规则校验所述参数信息；
    若检测到所述参数信息与所述判断规则匹配，则确定校验成功。
  6. 如权利要求3所述的立案方法，其特征在于，所述在理赔系统的服务接口中接收到第三方的调用请求时，对所述第三方发送的调用请求进行判断的步骤之前，所述方法还包括：
    在预设理赔申请数据中抽取数据字段，将抽取的数据字段与预存字段进行比对；
    当数据字段与预存字段匹配时，确定所述数据字段为基础字段；
    当数据字段与预存字段不匹配时，确定所述数据字段为扩展字段，并将该字段添加在系统中；
    对所述基础字段和所述扩展字段在交易代码下进行映射，以映射出基础字段和扩展字段对应的校验规则；
    将基础字段和扩展字段与对应的校验规则进行关联存储，以便后续对案件进行审核。
  7. 如权利要求3所述的立案方法，其特征在于，所述服务接口为restful接口。
  8. 如权利要求1所述的立案方法，其特征在于，所述方法还包括：
    在接收到校验规则修改指令时，根据所述校验规则修改指令对校验规则进行调整和/或增删。
  9. 一种立案装置，其特征在于，所述立案装置包括：
    显示模块，用于在接收到案件导入请求时，在理赔系统的预设界面中显示报案入口；
    导入模块，用于从所述报案入口导入批量案件；
    比对模块，用于在导入的各个案件中抽取出对应的数据字段，并将抽取的各个数据字段与预存的映射表进行比对，以确定各个数据字段对应的校验规则；
    审核模块，用于采用各个校验规则对对应的各个案件进行审核，在审核无误时，基于案件对应的赔款金额，生成理赔方案。
  10. 如权利要求9所述的立案装置，其特征在于，所述装置还包括：
    获取模块，用于在有案件导入失败后，获取导入失败的案件；
    第一存储模块，用于将导入失败的案件存储到预设存储区中，并基于导入失败的案件生成案件清单，以便后续基于所述案件清单下载对应的案件。
  11. 如权利要求9所述的立案装置，其特征在于，所述装置还包括：
    判断模块，用于在理赔系统的服务接口中接收到第三方的调用请求时，对所述第三方发送的调用请求进行判断；
    检测模块，用于检测所述调用请求的请求类型，若所述请求类型是预设类型之一，接收所述第三方的报案请求；
    校验模块，用于对所述报案请求进行风险校验，校验成功后，基于所述报案请求触发所述案件导入请求。
  12. 如权利要求11所述的立案装置，其特征在于，所述装置还包括：
    注册模块，用于为所述第三方注册交易代码，以使所述第三方通过交易代码调用所述服务接口。
  13. 如权利要求11所述的立案装置，其特征在于，所述校验模块，还用于识别所述报案请求的参数信息；基于所述参数信息提取预存的判断规则；根据所述判断规则校验所述参数信息；若检测到所述参数信息与所述判断规则匹配，则确定校验成功。
  14. 如权利要求11所述的立案装置，其特征在于，所述装置还包括：
    抽取模块，用于在预设理赔申请数据中抽取数据字段，将抽取的数据字段与预存字段进行比对；
    确定模块，用于当数据字段与预存字段匹配时，确定所述数据字段为基础字段；
    所述确定模块，还用于当数据字段与预存字段不匹配时，确定所述数据字段为扩展字段，并将该字段添加在系统中；
    映射模块，用于对所述基础字段和所述扩展字段在交易代码下进行映射，以映射出基础字段和扩展字段对应的校验规则；
    第二存储模块，用于将基础字段和扩展字段与对应的校验规则进行关联存储，以便后续对案件进行审核。
  15. 如权利要求11所述的立案装置，其特征在于，所述服务接口为restful接口。
  16. 如权利要求11所述的立案装置，其特征在于，所述装置还包括：
    修改模块，用于在接收到校验规则修改指令时，根据所述校验规则修改指令对校验规则进行调整和/或增删。
  17. 一种终端，其特征在于，所述终端包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的立案程序，所述立案程序被所述处理器执行时实现如权利要求1所述的立案方法的步骤。
  18. 一种终端，其特征在于，所述终端包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的立案程序，所述立案程序被所述处理器执行时实现如权利要求2所述的立案方法的步骤。
  19. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有立案程序，所述立案程序被处理器执行时实现如权利要求1所述的立案方法的步骤。
  20. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有立案程序，所述立案程序被处理器执行时实现如权利要求2所述的立案方法的步骤。
PCT/CN2018/083675 2017-06-22 2018-04-19 立案方法、装置、终端和计算机可读存储介质 Ceased WO2018233367A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710483564.9 2017-06-22
CN201710483564.9A CN108335237B (zh) 2017-06-22 2017-06-22 立案方法、终端和计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2018233367A1 true WO2018233367A1 (zh) 2018-12-27

Family

ID=62922085

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083675 Ceased WO2018233367A1 (zh) 2017-06-22 2018-04-19 立案方法、装置、终端和计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN108335237B (zh)
WO (1) WO2018233367A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115185988A (zh) * 2022-06-16 2022-10-14 平安银行股份有限公司 比对方法和比对设备
CN118316670A (zh) * 2024-04-03 2024-07-09 中国工商银行股份有限公司 校验方法、装置、设备、介质和程序产品

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108932612B (zh) * 2018-08-17 2022-07-12 中国建设银行股份有限公司 一种应用于企业年金的数据处理方法、装置及电子设备
CN109934722A (zh) * 2019-01-31 2019-06-25 德联易控科技(北京)有限公司 校验规则的调试方法、装置及电子设备
CN110517007A (zh) * 2019-06-14 2019-11-29 平安科技（深圳）有限公司 仲裁申请立案审核处理方法、装置和计算机设备
CN110377631B (zh) * 2019-06-17 2024-01-09 平安科技（深圳）有限公司 案件信息处理方法、装置、计算机设备和存储介质
CN110335180A (zh) * 2019-07-04 2019-10-15 北京市律典通科技有限公司 案件立案材料智能审查装置
CN110728593A (zh) * 2019-09-04 2020-01-24 杭州安存网络科技有限公司 案件的立案方法和装置、电子设备和存储介质
CN111178822B (zh) * 2019-11-13 2023-08-15 泰康保险集团股份有限公司 理赔链生成方法、装置及存储介质
CN111309672B (zh) * 2020-02-07 2023-11-17 重庆华谷科技有限公司 立案和预立案辅助管理系统及智慧法务辅助服务系统
CN111680693A (zh) * 2020-05-28 2020-09-18 泰康保险集团股份有限公司 理赔业务批量处理方法及装置
CN111640031B (zh) * 2020-05-29 2023-07-14 泰康保险集团股份有限公司 跨系统的理赔数据处理方法、装置及相关设备
CN116029840A (zh) * 2023-02-17 2023-04-28 中国人民财产保险股份有限公司 一种多渠道报案数据集中方法、系统、设备及介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105405053A (zh) * 2015-10-28 2016-03-16 上海商保通健康科技有限公司 人工智能理算系统
CN105956667A (zh) * 2016-04-14 2016-09-21 平安科技（深圳）有限公司 车险定损理赔审核方法及系统
CN106228448A (zh) * 2016-07-29 2016-12-14 深圳市永兴元科技有限公司 基于移动通信网络的车险理赔方法及装置
CN106295151A (zh) * 2016-08-03 2017-01-04 合肥奇也信息科技有限公司 一种医疗保险在线理赔系统
CN106682987A (zh) * 2016-11-21 2017-05-17 中国平安财产保险股份有限公司 一种财产险理赔实现方法及实现系统
CN106875030A (zh) * 2016-12-14 2017-06-20 武汉默联股份有限公司 商业健康保险在线直赔智能推荐系统及方法
CN107705211A (zh) * 2017-11-10 2018-02-16 平安科技（深圳）有限公司 一种保险理赔案件的理算方法和装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002035363A1 (en) * 2000-10-20 2002-05-02 Ge Financial Assurance Holdings, Inc. Interactive insurance premium verification system and method
US7904326B2 (en) * 2001-06-29 2011-03-08 Versata Development Group, Inc. Method and apparatus for performing collective validation of credential information
US7415471B1 (en) * 2001-11-30 2008-08-19 Midland Loan Services, Inc. Methods and systems for automated data collection and analysis for use in association with asset securitization
CN101673268A (zh) * 2008-09-11 2010-03-17 贵州创慧科技开发有限公司 人像组合识别系统
CN201733328U (zh) * 2010-07-09 2011-02-02 中国工商银行股份有限公司 基于银行系统的企业数据维护装置及系统
CN103198200A (zh) * 2012-01-09 2013-07-10 北京汉林信通信息技术有限公司 人案信息采集比对反馈设备及其用途
US20140114691A1 (en) * 2012-10-23 2014-04-24 InnovaPad, LP Methods and Systems for the Integrated Collection of Data for Use in Incident Reports and Insurance Claims and to Related Methods of Performing Emergency Responder Cost Recovery
CN106709696A (zh) * 2016-11-21 2017-05-24 中国平安财产保险股份有限公司 一种自助理赔实现方法及实现系统

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105405053A (zh) * 2015-10-28 2016-03-16 上海商保通健康科技有限公司 人工智能理算系统
CN105956667A (zh) * 2016-04-14 2016-09-21 平安科技（深圳）有限公司 车险定损理赔审核方法及系统
CN106228448A (zh) * 2016-07-29 2016-12-14 深圳市永兴元科技有限公司 基于移动通信网络的车险理赔方法及装置
CN106295151A (zh) * 2016-08-03 2017-01-04 合肥奇也信息科技有限公司 一种医疗保险在线理赔系统
CN106682987A (zh) * 2016-11-21 2017-05-17 中国平安财产保险股份有限公司 一种财产险理赔实现方法及实现系统
CN106875030A (zh) * 2016-12-14 2017-06-20 武汉默联股份有限公司 商业健康保险在线直赔智能推荐系统及方法
CN107705211A (zh) * 2017-11-10 2018-02-16 平安科技（深圳）有限公司 一种保险理赔案件的理算方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115185988A (zh) * 2022-06-16 2022-10-14 平安银行股份有限公司 比对方法和比对设备
CN118316670A (zh) * 2024-04-03 2024-07-09 中国工商银行股份有限公司 校验方法、装置、设备、介质和程序产品

Also Published As

Publication number Publication date
CN108335237B (zh) 2020-10-27
CN108335237A (zh) 2018-07-27

Similar Documents

Publication Publication Date Title
WO2018233367A1 (zh) 立案方法、装置、终端和计算机可读存储介质
WO2019019378A1 (zh) 业务处理方法、装置、适配器及计算机可读存储介质
WO2019019374A1 (zh) 智能语音设备控制家电的方法、装置及系统
WO2018120457A1 (zh) 数据处理方法、装置、设备及计算机可读存储介质
WO2018058919A1 (zh) 标识信息生成方法、装置、设备和计算机可读存储介质
WO2019019493A1 (zh) 数据共享方法、装置及计算机可读存储介质
WO2019024336A1 (zh) 数据查询方法、装置及计算机可读存储介质
WO2018166236A1 (zh) 理赔账单识别方法、装置、设备及计算机可读存储介质
WO2017201899A1 (zh) 连接蓝牙设备的方法及装置
WO2019051890A1 (zh) 终端控制方法、装置及计算机可读存储介质
WO2018082482A1 (zh) 一种网络共享方法、接入网络方法及系统
WO2019051899A1 (zh) 终端控制方法、装置及存储介质
WO2019037395A1 (zh) 密钥管理方法、装置及可读存储介质
WO2019019376A1 (zh) 业务流程管理方法、装置、设备及计算机可读存储介质
WO2018227887A1 (zh) 视频广告投放、生成方法、装置、服务器及可读存储介质
WO2018149191A1 (zh) 保单核保的方法、装置、设备及计算机可读存储介质
WO2018000856A1 (zh) 一种实现SDN Overlay网络报文转发的方法、终端、设备及计算机可读存储介质
WO2018201696A1 (zh) 社保卡保单的保费续缴方法、装置、设备及存储介质
WO2019056462A1 (zh) 名单分配方法、装置、设备以及计算机可读存储介质
WO2019051866A1 (zh) 权益信息管理方法、装置、设备及计算机可读存储介质
WO2019100531A1 (zh) 数字签名生成、验证方法及其设备和存储介质
WO2018176864A1 (zh) 数据库权限管理方法、系统、设备和计算机可读存储介质
WO2019071762A1 (zh) 楼层位置定位方法、系统、服务器和计算机可读存储介质
WO2018018680A1 (zh) 应用提示信息显示方法及装置
WO2019051934A1 (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: 18821041

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

Country of ref document: EP

Kind code of ref document: A1

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 18.03.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18821041

Country of ref document: EP

Kind code of ref document: A1