CN111445344A - Insurance business list processing method, electronic equipment and storage medium - Google Patents
Insurance business list processing method, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111445344A CN111445344A CN202010316900.2A CN202010316900A CN111445344A CN 111445344 A CN111445344 A CN 111445344A CN 202010316900 A CN202010316900 A CN 202010316900A CN 111445344 A CN111445344 A CN 111445344A
- Authority
- CN
- China
- Prior art keywords
- file
- rule
- list
- data
- processing method
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 24
- 238000012795 verification Methods 0.000 claims abstract description 38
- 230000008676 import Effects 0.000 claims abstract description 36
- 238000000034 method Methods 0.000 claims abstract description 33
- 238000012545 processing Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 12
- 238000013467 fragmentation Methods 0.000 claims description 9
- 238000006062 fragmentation reaction Methods 0.000 claims description 9
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000000605 extraction Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012946 outsourcing Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005111 flow chemistry technique Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
Abstract
The invention discloses an insurance business list processing method, electronic equipment and a storage medium, wherein the method comprises the steps of S1, obtaining an insured person list file; step S2, format verification is carried out on the list file of the insured life: step S3, judging whether the list file of the insured person exceeds a preset threshold value, if not, entering step S4, and if yes, entering step S5; step S4, generating an import job message, and entering step S6; step S5, carrying out slicing operation on the insured person list file to obtain a plurality of file slices, and then entering the step S4; and step S6, reading the list file of the insured life or the plurality of file pieces by adopting a multithread reading method according to the import operation message to obtain an underwriting operation message. The invention improves the fluency of front-end user experience and business operation.
Description
Technical Field
The invention relates to the technical field of computer data processing, in particular to an insurance business list processing method, electronic equipment and a storage medium.
Background
The large-batch insurance business processing comprises business scenes of group insurance list import, insurance outsourcing data import, claim settlement outsourcing data import and the like, wherein the group insurance application is an important component of the insurance business. The group insurance uses the group as an insurance object, applies insurance on the group name and issues a total insurance contract by an insurer, and the insurer provides insurance for members in the group according to the contract rule. The group insurance insured persons have a large number, and a large amount of insured person data needs to be imported into the insurance company business system at one time when the insurance data is submitted. The existing processing scheme for the large-batch insurance business is processed in a synchronous interface calling mode, and the steps are as follows: the user uploads a list of insured life information. The system reads the data of the insured persons one by one in the information list of the insured persons and checks the data of the insured persons. And inserting the insured life data into the database one by one. And triggering an underwriting process, extracting the information of the insured person associated with the insurance policy from the database, and calling an underwriting interface for many times to verify underwriting rules.
The existing large-batch insurance business processing scheme has the following defects:
when the number of insured persons is large, the imported file (a large amount of insured person data) is too large, which causes the system to consume a large amount of memory when reading the information list file of the insured person, and the system performance is tired, even the system is crashed due to insufficient memory.
Reading and storing data one by one, and repeatedly calling the underwriting interface for many times, thereby bringing greater pressure to the performance of the database IO and the interface.
Prompt information when the data verification and the check guarantee verification are not passed cannot be displayed in a distinguishing way, and a large number of error prompts are returned to a front-end user, so that the problem of poor information readability is caused.
And the synchronous interface calling mode is that the front-end user needs to wait until the flow processing is finished, and when the system resources are insufficient and the processing capacity is reduced, the front-end user needs to wait for a very long time. The fluency of front-end user experience and business operation is influenced.
Disclosure of Invention
The invention aims to provide an insurance business list processing method, electronic equipment and a storage medium, and aims to improve the front-end user experience and the fluency of business operation.
In order to achieve the above purpose, the invention is realized by the following technical scheme:
an insurance business list processing method comprises the following steps:
step S1, acquiring a list file of the insured life;
step S2, format verification is carried out on the list file of the insured life:
step S3, judging whether the list file of the insured person exceeds a preset threshold value, if not, entering step S4, and if yes, entering step S5;
step S4, generating an import job message, and entering step S6;
step S5, carrying out slicing operation on the insured person list file to obtain a plurality of file slices, and entering the step S4;
and step S6, reading the list file of the insured life or the plurality of file pieces by adopting a multithread reading method according to the import operation message to obtain an underwriting operation message.
Preferably, the step S2 includes: acquiring the extension name of the insured person list file, judging whether the extension name is in a.xls format or a.xlsx format, if not, displaying a type error prompt of the insured person list file, and terminating acquiring the insured person list file; if yes, the process proceeds to step S3.
Preferably, the step S5 includes:
creating a file temporary directory, wherein the file temporary directory comprises the file slices;
partially reading the list file of the insured person by using streamreader in a data stream mode, and writing the read data into the file slice correspondingly in sequence; until the data of the insured person list file is written into the file slice; and after the fragmentation operation is finished, deleting the list file of the insured person.
Preferably, the step S5 further includes: and displaying the mark of the slicing operation ending.
Preferably, the import job message includes a policy number and/or a path of the file temporary directory.
Preferably, the step S6 includes:
s6.1, reading the number of the file pieces according to the path of the temporary file directory shown by the import operation message, and starting threads with corresponding number to read the data of each file piece one by one;
s6.2, after each thread reads data, carrying out rule verification on the read data; storing the data which passes the rule verification into an insured person table and a cache file of a database respectively; and writing the data which does not pass the rule verification into an import result list.
Preferably, the step S6 further includes: s6.3, after the processing of all threads is finished, the importing process is finished, and a front-end user can know the data importing situation by checking an importing result list;
and after the import is finished, the system sends the message capable of starting the underwriting operation to the message queue.
Preferably, said step S6.1 further comprises reading said file piece with streamreader.
Preferably, the rule information checked by the rule includes: one or more of non-empty check, identification card number rule and mobile phone number rule.
Preferably, the rule information of the rule verification is pre-configured in the database, and the rule information of the rule verification is imported into the cache file by adopting an automatic triggering or manual triggering mode;
and when the rule is checked, calling the rule information of the rule check from a buffer file.
Preferably, the data stored in the cache file is a zset with the policy number as key value and the insured person number as score.
Preferably, the message content of the underwriting job message includes a policy number and a number of insureds.
In another aspect, the present invention also provides an electronic device comprising a processor and a memory, the memory having stored thereon a computer program which, when executed by the processor, implements the method as described above.
In a further aspect, the invention also provides a readable storage medium having stored therein a computer program which, when executed by a processor, implements the method of any one of claims 1 to 11.
Compared with the prior art, the invention has at least one of the following advantages:
the invention provides a method for processing an insurance business list, which comprises the following steps: step S1, acquiring a list file of the insured life; step S2, format verification is carried out on the list file of the insured life: step S3, judging whether the list file of the insured person exceeds a preset threshold value, if not, entering step S4, and if yes, entering step S5; step S4, generating an import job message, and entering step S6; step S5, carrying out slicing operation on the insured person list file to obtain a plurality of file slices, and then entering the step S4; and step S6, reading the list file of the insured life or the plurality of file pieces by adopting a multithread reading method according to the import operation message to obtain an underwriting operation message. Therefore, the invention effectively solves the problem of importing the data of the insurance service list in large batch by carrying out fragmentation operation on the insurance service in large batch. The asynchronous and efficient data import is met, and the problems of large file uploading and memory overflow during system reading are avoided. The rule information of the rule verification is processed by the cache, the insured person information is stored, and the efficiency of the rule verification and the extraction of the underwriting information is greatly improved. Rule information for realizing rule verification is configured, a program is decoupled from the rule information, the stability of the program is improved, and the code complexity is reduced. The configuration implementation also reduces the development and maintenance cost, and the purpose of improving the front-end user experience and the smoothness of the service operation is achieved. The invention is a technical solution which can be actually grounded and can be butted with the existing system.
Drawings
Fig. 1 is a schematic flowchart of an insurance business listing processing method according to an embodiment of the present invention;
fig. 2 is a schematic flow chart illustrating a first processing stage of a method for processing an insurance business list according to an embodiment of the present invention;
fig. 3 is a schematic flowchart illustrating a second processing stage of the insurance business listing processing method according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a data flow process in an insurance business list processing method according to an embodiment of the present invention;
fig. 5 is a schematic diagram illustrating rule verification definition in an insurance business list processing method according to an embodiment of the present invention;
fig. 6 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The insurance business list processing method, the electronic device and the storage medium according to the present invention will be described in detail with reference to fig. 1 to 6 and the following detailed description. The advantages and features of the present invention will become more apparent from the following description. It is to be noted that the drawings are in a very simplified form and are all used in a non-precise scale for the purpose of facilitating and distinctly aiding in the description of the embodiments of the present invention. To make the objects, features and advantages of the present invention comprehensible, reference is made to the accompanying drawings. It should be understood that the structures, ratios, sizes, and the like shown in the drawings and described in the specification are only used for matching with the disclosure of the specification, so as to be understood and read by those skilled in the art, and are not used to limit the implementation conditions of the present invention, so that the present invention has no technical significance, and any structural modification, ratio relationship change or size adjustment should still fall within the scope of the present invention without affecting the efficacy and the achievable purpose of the present invention.
Referring to fig. 1 to 5, the present embodiment provides a method for processing an insurance business list, including:
step S1, acquiring a list file of the insured life; specifically, the front-end user selects a file to be uploaded through a file import interface. And the system processes the list file of the insured life uploaded by the front-end user through FileUload. It is understood that the FileUpload (upload file program) is used to implement a file upload function under the Java environment.
Step S2, format verification is carried out on the list file of the insured life; the step S2 includes: acquiring the extension name of the insured person list file, judging whether the extension name is in a.xls format or a.xlsx format, if not, displaying a type error prompt of the insured person list file, and terminating acquiring the insured person list file; if yes, the process proceeds to step S3.
In this embodiment, the system restricts the front-end user from recording the insured person information by using the excel table to form an insured person list file; therefore, before uploading the insured person list file, the system first obtains the extension of the insured person list file and judges whether the extension is in the xls format or the xlsx format. If not, the front-end user is prompted to use the wrong file type, and the uploading operation is terminated. If the file format is verified, the system reads the file stream of the uploaded insured person list file, writes the insured person list file into a pre-established file temporary directory, and names the file temporary directory with the insurance policy number. It is to be understood that the system described herein refers to a system that runs a current manifest importer, such as an insurance core system, for example.
Step S3, judging whether the list file of the insured person exceeds a preset threshold value, if not, entering step S4, and if yes, entering step S5;
step S4, generating an import job message, and entering step S6;
step S5, carrying out slicing operation on the insured person list file to obtain a plurality of file slices, and entering the step S4;
the step S5 includes: creating a file temporary directory, wherein the file temporary directory comprises the file slices; partially reading the list file of the insured person by using a streamreader (streaming reading tool) in a data stream mode, and sequentially and correspondingly writing the read data into the file slice; until the data of the insured person list file is written into the file slice; and after the fragmentation operation is finished, deleting the list file of the insured person. The step S5 further includes: and displaying the mark of the slicing operation ending. The import job message includes a policy number and/or a path of the file temporary directory.
Specifically, as shown in fig. 2, in order to prevent the system from reading a large batch of insurance business inventory files, for example: the list file of the group policy insured person has a risk of causing system OOM (risk of memory overflow when the system reads), and a large amount of insurance business list files need to be divided into smaller file pieces for processing. Therefore, after the insurance business list file is uploaded, the system acquires the size of the insurance business list file immediately, and judges whether the size exceeds a preset threshold value (which can be determined manually according to the specific situation of the system, such as 10M). If the insurance business list file exceeds a preset threshold value, classifying the insurance business list file into an oversized file, partially reading the insurance business list file in a data stream mode by using a streamreader, and writing the data of the insurance business list file into a newly-built file slice. When the data of a certain file slice reaches a certain amount, writing the subsequent data into a new file slice until the data of the source file (insurance business list file) is written into the file slice. The source file (insurance business list file) is deleted after fragmentation is finished; if the file size does not exceed the threshold, no processing is done. And after the file fragmentation operation is finished, returning a mark of finishing the processing to the front end, and performing other operations by the front end user at the moment. At the same time, a message (import job message) for starting a data-drop job is pushed to the message queue, the message including a policy number, a folder path (path of each file piece or path of the file temporary directory), and the like.
And step S6, reading the list file of the insured life or the plurality of file pieces by adopting a multithread reading method according to the import operation message to obtain an underwriting operation message.
The step S6 includes:
s6.1, reading the number of the file pieces according to the path of the temporary file directory shown by the import operation message, and starting threads with corresponding number to read the data of each file piece one by one;
step S6.1 further includes reading the file piece using streamreader.
S6.2, after each thread reads data, carrying out rule verification on the read data; storing the data which passes the rule verification into an insured person table and a cache file of a database respectively; and writing the years data which do not pass the rule verification into an import result list.
The step S6 further includes: s6.3, after the processing of all threads is finished, the importing process is finished, and a front-end user can know the data importing situation by checking an importing result list;
and after the import is finished, the system sends the message capable of starting the underwriting operation to the message queue.
The rule checks include, but are not limited to: one or more of non-empty check, identification card number rule and mobile phone number rule.
The rule information of the rule verification is pre-configured in the database, and is imported into the cache file in an automatic triggering or manual triggering mode; and when the rule is checked, calling the rule information of the rule check from the cache file.
The data stored in the cache file is a zset with the policy number as a key value and the insured person number as score. zset is one data type supported by redis caching. Is an ordered collection of non-repeating elements. The key value is used as an identifier for acquiring the set, and score is a basis for ordering each element in the set. The underwriting job message includes a policy number and an insured life number.
Specifically, as shown in fig. 3 to 5, after receiving the import operation message, the data import module of the system reads the number of file pieces according to the path shown in the import operation message, and starts a corresponding number of threads to read the data of each file piece one by one. In order to save memory overhead, streamreader reading is also adopted. After the single thread obtains the data, the data is firstly subjected to entry rule verification, such as non-null verification, identification number rules, mobile phone number rules and the like. And the data which passes the rule verification are simultaneously and respectively stored in an insured list and a buffer file of the database. The data in the cache file is a zset set with the policy number as the key value and the insured person number as score.
And writing the data which is not verified by the entry rule into the import result list. After the processing of all threads is finished, the importing process is finished, and a front-end user can know the data importing situation by checking the importing result list. And after the import is finished, the system sends the message capable of starting the underwriting operation to the message queue. The information content of the underwriting operation comprises a policy number, the number of insured persons and the like.
And entering a rule checking link, wherein all rule information for rule checking is configured in a database, and the rule information is automatically triggered at regular time or manually triggered by a user to be imported into the cache file. The rule information it employs when performing a rule check may be retrieved or recalled from the cache.
Therefore, the embodiment effectively solves the problem of importing the data of the large-batch insurance service list by carrying out the fragmentation operation on the large-batch insurance service. The asynchronous and efficient data import is met, and the problems of large file uploading and memory overflow during system reading are avoided. The rule information of the rule verification is processed by the cache, the insured person information is stored, the efficiency of rule verification and extraction of the check and guarantee information is greatly improved, namely the rule verification is input in a configuration mode, the program and the rule information are decoupled, the stability of the program is improved, and the code complexity is reduced. The configuration implementation also reduces the development and maintenance cost, and the purpose of improving the front-end user experience and the smoothness of the service operation is achieved.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
In still another aspect, based on the same inventive concept, the present invention further provides an electronic device, as shown in fig. 6, where the electronic device includes a processor 301 and a memory 303, and the memory 303 stores a computer program thereon, and when the computer program is executed by the processor 301, the method for processing an insurance service list as described above is implemented.
The electronic device provided by the embodiment can realize the fragmentation operation of the large-batch insurance services, and effectively solves the problem of importing large-batch insurance service list data. The method has the advantages that asynchronous and efficient data import is met, the problems of large file uploading and memory overflow during system reading are solved, rule information of rule verification is processed through the cache, insured person information is stored, and the efficiency of rule verification and extraction of check and guarantee information is greatly improved. Rule information for inputting rule verification is configured, a program is decoupled from the rule information, the stability of the program is improved, and the code complexity is reduced. The configuration implementation also reduces the development and maintenance cost, and the purpose of improving the front-end user experience and the smoothness of the service operation is achieved.
With continued reference to fig. 3, the electronic device further comprises a communication interface 302 and a communication bus 304, wherein the processor 301, the communication interface 302 and the memory 303 are communicated with each other through the communication bus 304. The communication bus 304 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 304 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus. The communication interface 302 is used for communication between the electronic device and other devices.
The Processor 301 in this embodiment may be a Central Processing Unit (CPU), other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, and so on. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, and the processor 301 is the control center of the electronic device and connects the various parts of the whole electronic device by various interfaces and lines.
The memory 303 may be used for storing the computer program, and the processor 301 implements various functions of the electronic device by running or executing the computer program stored in the memory 303 and calling data stored in the memory 303.
The memory 303 may include non-volatile and/or volatile memory, which may include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory, volatile memory which may include Random Access Memory (RAM) or external cache memory, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (S L DRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic (DRDRAM), and memory bus dynamic RAM (RDRAM), to name a few.
In other aspects, based on the same inventive concept, the present invention further provides a readable storage medium, in which a computer program is stored, and the computer program, when executed by a processor, can implement the insurance business listing processing method as described above.
The readable storage medium provided by the embodiment can realize fragmentation operation of a large batch of insurance services, and effectively solves the problem of importing large batch of insurance service list data. The method has the advantages that asynchronous and efficient data import is met, the problems of large file uploading and memory overflow during system reading are solved, rule information of rule verification is processed through the cache, insured person information is stored, and the efficiency of rule verification and extraction of check and guarantee information is greatly improved. Rule information for inputting rule verification is configured, a program is decoupled from the rule information, the stability of the program is improved, and the code complexity is reduced. The configuration implementation also reduces the development and maintenance cost, and the purpose of improving the front-end user experience and the smoothness of the service operation is achieved.
The readable storage medium provided by this embodiment may take any combination of one or more computer-readable media. The readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this context, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
In this embodiment, the computer program code for carrying out operations for embodiments may be written in any combination of one or more programming languages, including AN object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
It should be noted that the apparatuses and methods disclosed in the embodiments herein can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments herein. In this regard, each block in the flowchart or block diagrams may represent a module, a program, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments herein may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
While the present invention has been described in detail with reference to the preferred embodiments, it should be understood that the above description should not be taken as limiting the invention. Various modifications and alterations to this invention will become apparent to those skilled in the art upon reading the foregoing description. Accordingly, the scope of the invention should be determined from the following claims.
Claims (14)
1. An insurance business list processing method, comprising:
step S1, acquiring a list file of the insured life;
step S2, format verification is carried out on the list file of the insured life:
step S3, judging whether the list file of the insured person exceeds a preset threshold value, if not, entering step S4, and if yes, entering step S5;
step S4, generating an import job message, and entering step S6;
step S5, carrying out slicing operation on the insured person list file to obtain a plurality of file slices, and then entering the step S4;
and step S6, reading the list file of the insured life or the plurality of file pieces by adopting a multithread reading method according to the import operation message to obtain an underwriting operation message.
2. The insurance business listing processing method according to claim 1, wherein said step S2 includes: acquiring the extension name of the insured person list file, judging whether the extension name is in a.xls format or a.xlsx format, if not, displaying a type error prompt of the insured person list file, and terminating acquiring the insured person list file; if yes, the process proceeds to step S3.
3. The insurance business listing processing method according to claim 1, wherein said step S5 includes:
creating a file temporary directory, wherein the file temporary directory comprises the file slices;
partially reading the list file of the insured person by using streamreader in a data stream mode, and writing the read data into the file slice correspondingly in sequence; until the data of the insured person list file is written into the file slice; and after the fragmentation operation is finished, deleting the list file of the insured person.
4. The insurance business listing processing method according to any one of claims 1 to 3, wherein said step S5 further includes: and displaying the mark of the slicing operation ending.
5. The insurance business listing processing method according to claim 4, wherein said import job message includes a policy number and/or a path of said file temporary directory.
6. The insurance business listing processing method according to claim 5, wherein said step S6 includes:
s6.1, reading the number of the file pieces according to the path of the temporary file directory shown by the import operation message, and starting threads with corresponding number to read the data of each file piece one by one;
s6.2, after each thread reads data, carrying out rule verification on the read data; storing the data which passes the rule verification into an insured person table and a cache file of a database respectively; and writing the data which does not pass the rule verification into an import result list.
7. The insurance business listing processing method according to claim 6, wherein said step S6 further includes:
s6.3, after the processing of all threads is finished, the importing process is finished, and a front-end user can know the data importing situation by checking the importing result list;
and after the import is finished, the system sends the message capable of starting the underwriting operation to the message queue.
8. The insurance business listing processing method of claim 7,
step S6.1 further includes reading the file piece using streamreader.
9. The insurance business listing processing method of claim 8,
the rule information of the rule verification comprises: one or more of non-empty check, identification card number rule and mobile phone number rule.
10. The insurance business listing processing method according to claim 9, wherein the rule information of the rule verification is pre-configured in the database, and the rule information of the rule verification is imported into the cache file by adopting an automatic triggering or manual triggering mode;
and when the rule is verified, calling the rule information of the verification rule from a buffer file.
11. The insurance business listing processing method of claim 10,
the data stored in the cache file is a zset with the policy number as a key value and the insured person number as score.
12. The insurance business listing processing method of claim 11,
the message content of the underwriting job message comprises a policy number and the number of insured persons.
13. An electronic device comprising a processor and a memory, the memory having stored thereon a computer program which, when executed by the processor, implements the method of any of claims 1 to 12.
14. A readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method of any one of claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010316900.2A CN111445344A (en) | 2020-04-21 | 2020-04-21 | Insurance business list processing method, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010316900.2A CN111445344A (en) | 2020-04-21 | 2020-04-21 | Insurance business list processing method, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111445344A true CN111445344A (en) | 2020-07-24 |
Family
ID=71653419
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010316900.2A Pending CN111445344A (en) | 2020-04-21 | 2020-04-21 | Insurance business list processing method, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111445344A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112950393A (en) * | 2021-02-09 | 2021-06-11 | 深圳木成林科技有限公司 | Insurance business docking method and device, electronic equipment and readable storage medium |
| CN116541419A (en) * | 2023-07-06 | 2023-08-04 | 美云智数科技有限公司 | Data import and export method and device, electronic equipment and readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040186748A1 (en) * | 2003-03-18 | 2004-09-23 | Spx Corporation | Method and apparatus for automating multi-national insurance information requests |
| WO2011077952A1 (en) * | 2009-12-25 | 2011-06-30 | 有限会社 医療福祉開発計画 | Insurance card verification system and insurance card verification method |
| CN108428181A (en) * | 2017-06-12 | 2018-08-21 | 平安科技（深圳）有限公司 | The single device of record, method and computer readable storage medium |
| CN108491475A (en) * | 2018-03-08 | 2018-09-04 | 平安科技（深圳）有限公司 | Data rapid batch introduction method, electronic device and computer readable storage medium |
| CN109427014A (en) * | 2017-12-28 | 2019-03-05 | 中国平安财产保险股份有限公司 | Insurance application generation method, device, equipment and computer readable storage medium |
| CN109598632A (en) * | 2018-12-13 | 2019-04-09 | 泰康保险集团股份有限公司 | Insurance business processing method, device, medium and electronic equipment |
| CN109658259A (en) * | 2018-11-19 | 2019-04-19 | 平安科技（深圳）有限公司 | Peasant household's listings data processing method, device, computer equipment and storage medium |
| CN110909013A (en) * | 2019-10-12 | 2020-03-24 | 中国平安财产保险股份有限公司 | Service list generation method, device, equipment and computer readable storage medium |
-
2020
- 2020-04-21 CN CN202010316900.2A patent/CN111445344A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040186748A1 (en) * | 2003-03-18 | 2004-09-23 | Spx Corporation | Method and apparatus for automating multi-national insurance information requests |
| WO2011077952A1 (en) * | 2009-12-25 | 2011-06-30 | 有限会社 医療福祉開発計画 | Insurance card verification system and insurance card verification method |
| CN108428181A (en) * | 2017-06-12 | 2018-08-21 | 平安科技（深圳）有限公司 | The single device of record, method and computer readable storage medium |
| CN109427014A (en) * | 2017-12-28 | 2019-03-05 | 中国平安财产保险股份有限公司 | Insurance application generation method, device, equipment and computer readable storage medium |
| CN108491475A (en) * | 2018-03-08 | 2018-09-04 | 平安科技（深圳）有限公司 | Data rapid batch introduction method, electronic device and computer readable storage medium |
| CN109658259A (en) * | 2018-11-19 | 2019-04-19 | 平安科技（深圳）有限公司 | Peasant household's listings data processing method, device, computer equipment and storage medium |
| CN109598632A (en) * | 2018-12-13 | 2019-04-09 | 泰康保险集团股份有限公司 | Insurance business processing method, device, medium and electronic equipment |
| CN110909013A (en) * | 2019-10-12 | 2020-03-24 | 中国平安财产保险股份有限公司 | Service list generation method, device, equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 王志成: "信息技术运用于保险公司关联交易管理的必要性、可行性及实施路径", 《上海保险》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112950393A (en) * | 2021-02-09 | 2021-06-11 | 深圳木成林科技有限公司 | Insurance business docking method and device, electronic equipment and readable storage medium |
| CN116541419A (en) * | 2023-07-06 | 2023-08-04 | 美云智数科技有限公司 | Data import and export method and device, electronic equipment and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022095520A1 (en) | Document editing method and device, server, terminal, and storage medium | |
| CN110728455B (en) | Service processing method, service processing device, storage medium and electronic equipment | |
| CN111445344A (en) | Insurance business list processing method, electronic equipment and storage medium | |
| CN110851415A (en) | Log data processing method and device of vehicle-mounted system | |
| CN110705235A (en) | Information input method and device for business handling, storage medium and electronic equipment | |
| CN112784112B (en) | Message verification method and device | |
| CN112445596B (en) | Data importing method, system and storage medium based on multithreading | |
| CN111161085A (en) | Service request processing method and device, electronic equipment and computer readable medium | |
| CN112416972A (en) | Real-time data stream processing method, device, equipment and readable storage medium | |
| CN109284492B (en) | Method and device for generating notification document | |
| CN112052120A (en) | Database deleted data recovery method and device | |
| CN111414339B (en) | File processing method, system, device, equipment and medium | |
| CN110334333B (en) | Information modification method and related device | |
| CN103136234B (en) | Data processing method and data processing device | |
| CN109524009B (en) | Policy entry method and related device based on voice recognition | |
| CN108090128B (en) | Recovery method and device for merged storage space and electronic equipment | |
| CN109493868B (en) | Policy entry method and related device based on voice recognition | |
| CN112615869B (en) | Audio data processing method, device, equipment and storage medium | |
| CN114386407B (en) | Word segmentation method and device for text | |
| CN116303296B (en) | Data storage method, device, electronic equipment and medium | |
| CN115204814A (en) | Order approval method and device, storage medium and computer equipment | |
| CN107886939B (en) | Pause-continue type text voice playing method and device at client | |
| CN114968655A (en) | Data reconstruction method and device and electronic equipment | |
| CN117174259A (en) | Medical image original data acquisition method and system | |
| CN114116978A (en) | Method and device for aligning voice and text, electronic equipment and readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210707 Address after: 200122 4th floor to 6th floor, building 1, No.98 (Software Park), Lane 91, Eshan Road, China (Shanghai) pilot Free Trade Zone, Pudong New Area, Shanghai Applicant after: SHANGHAI NEWTOUCH SOFTWARE Co.,Ltd. Address before: 401122 No.19 datavalley East Road, Xiantao street, Yubei District, Chongqing Applicant before: Chongqing Xinzhi Jinfu Information Technology Co.,Ltd. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200724 |