WO2018014582A1 - Procédé de traitement de données de police d'assurance, dispositif, administrateur et support de stockage - Google Patents

Procédé de traitement de données de police d'assurance, dispositif, administrateur et support de stockage Download PDF

Info

Publication number
WO2018014582A1
WO2018014582A1 PCT/CN2017/078356 CN2017078356W WO2018014582A1 WO 2018014582 A1 WO2018014582 A1 WO 2018014582A1 CN 2017078356 W CN2017078356 W CN 2017078356W WO 2018014582 A1 WO2018014582 A1 WO 2018014582A1
Authority
WO
WIPO (PCT)
Prior art keywords
split
task
target database
log
data
Prior art date
Application number
PCT/CN2017/078356
Other languages
English (en)
Chinese (zh)
Inventor
刘永凡
罗志权
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018014582A1 publication Critical patent/WO2018014582A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • the present application relates to the field of computer technology, and in particular, to a policy data processing method, apparatus, server, and storage medium.
  • a policy data processing method, apparatus, server, and storage medium are provided.
  • a policy data processing method comprising:
  • the query is performed in the corresponding partition according to the dimension information, and the query result is obtained, and the query result is returned to the terminal, so that the terminal performs monthly node processing according to the query result.
  • a policy data processing device comprising:
  • a judging module configured to determine whether the batch processing in the plurality of source databases is completed when the synchronization time is reached
  • a synchronization module configured to: if the batch processing in the multiple source databases is completed, trigger a synchronous operation between the source database and the target database, write policy data in the multiple source databases into the target database, and obtain a policy in the target database. a data summary table corresponding to the data;
  • a splitting module configured to split the data summary table into partitions of multiple dimensions in the target database
  • a receiving module configured to receive a data query instruction sent by the terminal, where the query instruction carries dimension information
  • a query module configured to perform a query in the corresponding partition according to the dimension information, to obtain a query result
  • a sending module configured to return the query result to the terminal, so that the terminal performs monthly node processing according to the query result.
  • a server comprising a memory and a processor, the memory storing computer executable instructions, the computer executable instructions being executed by the processor, such that the processor performs the following steps:
  • the query is performed in the corresponding partition according to the dimension information, and the query result is obtained, and the query result is returned to the terminal, so that the terminal performs monthly node processing according to the query result.
  • One or more non-volatile readable storage media storing computer-executable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:
  • the query is performed in the corresponding partition according to the dimension information, and the query result is obtained, and the query result is returned to the terminal, so that the terminal performs monthly node processing according to the query result.
  • FIG. 1 is an application scenario diagram of a policy data processing method in an embodiment
  • FIG. 2 is a flow chart of a method for processing policy data in an embodiment
  • Figure 3 is a block diagram of a server in one embodiment
  • Figure 4 is a block diagram of a policy data processing apparatus in an embodiment
  • Figure 5 is a block diagram of a policy data processing apparatus in another embodiment.
  • the policy data processing method provided in the embodiment of the present application can be applied to the application scenario shown in FIG. 1 .
  • the terminal 102 and the server 104 are connected through a network.
  • Server 104 runs the job and kettle.
  • the job is configured to synchronize time. When the synchronization time is reached, the job is started and the job is used to determine whether the batch processing in the multiple source databases is completed. If it is completed, the kettle is executed to perform the synchronization operation between the source database and the target database.
  • the policy data in the source database is written into the target database, and the data summary table corresponding to the policy data is obtained in the target database.
  • the server 104 splits the data summary table into partitions of multiple dimensions in the target database.
  • the terminal 102 sends a data query instruction to the server 104, and the server 104 receives the data query instruction, performs a query in the corresponding partition according to the dimension information carried in the query instruction, obtains the query result, and returns the query result to the terminal 102.
  • the terminal 102 performs a monthly knot process based on the result of the query. This makes it possible to provide policy statistics quickly and accurately when performing policy monthly settlement processing.
  • a policy data processing method is provided. It should be understood that although the steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these steps are not necessarily in accordance with The order indicated by the arrows is performed in order. Except as explicitly stated herein, the execution of these steps is not strictly limited, and may be performed in other sequences. Moreover, at least some of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, and the order of execution thereof is not necessarily This may be performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
  • the method is applied to the server as an example, and specifically includes the following steps:
  • Step 202 When the synchronization time is reached, it is determined whether the batch processing in the plurality of source databases is completed; if yes, step 204 is performed; otherwise, the batch processing is completed.
  • the job and the kettle are running on the server, and the kettle is working on the kettle platform.
  • the synchronization time is the time set according to the need for the monthly settlement process of the policy. For example, 20:00 on the 1st of each month.
  • the synchronization time can be either working time or non-working time.
  • the job is configured for synchronization time.
  • the server can be a standalone server or a cluster service.
  • determining whether the batch processing in the plurality of databases is completed comprises: starting a job, using a job to obtain a log corresponding to the batch processing; using a job to check a log corresponding to the batch processing, and determining whether the batch processing is performed according to the content recorded in the log carry out.
  • Batch processing refers to policy-guaranteed settlement and policy monthly snapshot snapshot refreshing. Batch operations are performed in multiple source databases and the logs corresponding to the batch are recorded. The progress of the batch execution is recorded in the log.
  • the job is started, the log corresponding to the batch processing is acquired by the job, and the contents of the log record are checked, and the batch processing is checked according to the content of the log record. If the batch processing is not completed, wait for the preset time. For example, wait for 5 minutes, and use the job to obtain the log corresponding to the batch. The log records the execution status of the batch, and thus uses the job to check according to the contents recorded in the log. Whether the batch is complete. Loop through until the job determines that the batch in multiple source databases is complete.
  • Step 204 trigger a synchronization operation between the source database and the target database, write policy data in the plurality of source databases into the target database, and obtain a data summary table corresponding to the policy data in the target database.
  • Policy data in the source database can be stored in the form of a data table.
  • Data tables in multiple source databases can be in the same format.
  • the data sheet includes the policy number, insured and premiums.
  • Import data tables from multiple source databases into the target database using multiple threads The merchant data is processed by the merchant, and the full-scale insertion synchronization operation is performed in the target database, thereby quickly obtaining the data summary table corresponding to the policy data in the target database.
  • the synchronization operation is performed concurrently by multiple threads, which effectively improves the synchronization efficiency of policy data in multiple source databases.
  • Step 206 Split the data summary table into partitions of multiple dimensions in the target database.
  • the data master Since the amount of data in the data master is usually in the order of millions and tens of millions, the data master is too large. It takes too long to perform data query in the data summary table, which also degrades the performance of the target database, which causes the monthly knot processing to be adversely affected.
  • the data summary table is split into partitions of multiple dimensions in the target database. Partitioning refers to splitting the data master table into policy data in the data master table and storing it in multiple locations.
  • the policy data for the post-partition data master is hashed to multiple locations in the database.
  • the server obtains the dimension field in the target database, and splits the data summary table into multiple partitions according to the dimension field.
  • Dimension fields include time and organization. Among them, the time can be one day, one week or one month.
  • the institution can be the identity of the location of the institution.
  • the server can also configure partition thresholds for the amount of data for the partition. For example, the threshold is 10,000.
  • the server splits the data master into multiple partitions based on the dimension field and the partition threshold. For policy data for a dimension that is less than the threshold, a single partition can be constructed.
  • the server can also divide the partition into multiple sub-partitions. For example, the server divides the partition into sub-partitions based on the type of insurance and premiums. Partitioning can effectively reduce the burden on the target database and improve the performance of the target database.
  • Step 208 Receive a data query instruction sent by the terminal, where the query instruction carries dimension information.
  • Step 210 Perform a query in the corresponding partition according to the dimension information, obtain a query result, and return the query result to the terminal, so that the terminal performs monthly node processing according to the query result.
  • the terminal sends a data query instruction to the server, and the query instruction carries the dimension information.
  • One or more dimension fields, such as time and organization, etc., can be included in the dimension information.
  • the server receives the data query instruction, performs a query in the corresponding partition according to the dimension information, and obtains the query result.
  • the server does not need to query in the data summary table, which can effectively improve the query efficiency.
  • the server returns the query result to the terminal, and the terminal performs the policy monthly settlement process according to the query result.
  • the terminal may send a delete instruction to the server, and the server deletes the corresponding partition according to the delete instruction.
  • the server In the traditional method, if the data in the data summary table is deleted, it needs to be deleted line by line. If the deleted data is more, it takes more time.
  • the server can directly obtain the address of the partition, and delete the entire partition, and the operation is simple and fast.
  • the terminal can also export the partitions required for the policy of the monthly settlement from the target database, and does not need to export the policy data one by one in the multiple source databases, thereby further improving the work efficiency of the policy monthly settlement processing.
  • the terminal can also perform data cleaning and data compression on the exported policy data. Data cleaning refers to reviewing and verifying policy data, deleting duplicate policy data, and invalid policy data.
  • Data compression refers to the consolidation and compression of policy data of the same type of insurance.
  • the synchronization time when the synchronization time is reached, if the batch processing in the plurality of source databases has been completed; the synchronization operation of the source database and the target database is triggered. Thereby, the policy data in the plurality of source databases is written into the target database, and the data summary table corresponding to the policy data is obtained in the target database.
  • the target database Through the synchronization of multiple source databases and the target database, a large amount of policy data is written into the target database, thereby ensuring the accuracy of the policy statistics.
  • Split the data master table into partitions of multiple dimensions in the target database. After receiving the data query instruction sent by the terminal, the query can be quickly performed in the partition according to the dimension information carried in the query instruction, thereby enabling the terminal to perform the policy monthly settlement process according to the query result. Therefore, the policy statistics can be quickly and accurately provided during the policy monthly settlement process.
  • the method further includes: recording a synchronization operation log; after the estimated time period, checking the synchronization operation log by using the job, according to the content recorded in the synchronization operation log. Determine whether the synchronization operation is completed; if yes, generate a prompt message that the synchronization operation is completed, and send the prompt information to the terminal.
  • the server records the synchronization operation log while the kettle performs the synchronization operation of the plurality of source databases and the target database.
  • the execution status of the synchronization operation is recorded in the synchronization operation log.
  • the server uses the job to check the synchronization operation log to determine whether the synchronization operation is completed.
  • the estimated time is the time required to perform the synchronization operation based on the historical data and is an empirical value. For example, the estimated time can be 1 hour.
  • the job After the synchronization operation is triggered, if the job determines that the synchronization operation is not completed, the job waits for the preset time, acquires the synchronization operation log again, checks whether the synchronization operation is completed, and executes the loop until the synchronization operation is completed.
  • the server When the job determines that the synchronization operation is completed, the server generates a prompt message that the synchronization operation is completed, and sends the prompt information to the terminal. Therefore, the synchronous operation is monitored in real time, and it is convenient for the terminal to know the execution status of the synchronous operation in time.
  • the step of splitting the data summary table into the partitions of the plurality of dimensions in the target database comprises: running multiple threads in the target database to perform split task concurrently on the data summary table; and recording the split task splitting Divide the log; when multiple threads exit the target database and then perform the split task again, according to the split log, find the corresponding breakpoint task when multiple threads exit, and multiple threads continue to execute the split concurrently from the breakpoint task. Task until the data master is split into partitions of multiple dimensions.
  • the server runs multiple threads in the target database and concurrently performs the splitting task on the data summary table.
  • the server can generate split tasks based on the dimension fields. Different threads execute split tasks for different dimension fields, and the number of threads is less than the number of split tasks. Multiple threads execute the split task concurrently according to the preset logic, which can effectively improve the splitting efficiency of the data summary table.
  • the server records the split log for the data master table split process, and records the split status of the data master table by splitting the log, thereby monitoring the split process. Once an error occurs during the splitting of the data master, the server can quickly locate the location of the error by calling the split log.
  • multiple threads are run in the target database to perform a split task concurrently on the data summary table, and the corresponding split log is recorded.
  • the breakpoint task corresponding to the multiple threads at the time of exit may be searched according to the execution status of the split task, so that multiple threads continue to perform concurrent operations from the breakpoint task. This eliminates the need to perform full replenishment of the split task, and finds the breakpoint task to continue execution at the breakpoint task, effectively preventing the missed execution and mis-execution of the split task, and effectively improving the policy data. Processing efficiency.
  • the step of executing a split task on the data table concurrently by running multiple threads in the target database includes: obtaining a split task identifier in the target database, grouping the split tasks according to the split task identifier, and obtaining more Task groups; assign corresponding threads to task groups; perform split tasks concurrently on task groups through multiple threads.
  • each split task has a unique split task identifier.
  • the server obtains the split task identifier, and groups the split tasks according to the split task identifier to obtain multiple task groups.
  • the server obtains the split task identifier, and groups the split tasks according to the preset number of task groups according to the sequence of split task identifiers to obtain multiple task groups. For example, there are a total of 100 split tasks in the target database. Each split task has a corresponding split task ID. The default task group is 10. Each of the 10 tasks is grouped according to the order of the split task identification, thereby obtaining 10 task groups.
  • the split task identifier may be a task number
  • the server obtains the split task, and obtains the tasks with the same number and tails according to the task number, and divides the split tasks with the same number and tails into one task group to obtain multiple task groups.
  • the server obtains the split task, and obtains the tasks with the same number and tails according to the task number, and divides the split tasks with the same number and tails into one task group to obtain multiple task groups.
  • Each task has a corresponding task number, such as task 1, task 2, and task 100.
  • the server assigns a corresponding thread to each task group. That is to say, each thread will execute the tasks in the corresponding task group fixedly. For example, there are a total of 10 task groups, 10 tasks in each task group, 5 threads running on the server, and the server assigns thread 1 to task group 1 and task group 3, then thread 1 will execute task group 1 fixedly. 10 tasks in the task until the task in task group 1 is completed. Thread 1 executes task group 3 after executing task group 1. Multiple threads perform concurrent operations based on the corresponding task group to process the policy. Since the thread fixedly executes the task corresponding to a certain task identifier, it is easy to find an abnormality occurring during the execution of the task, and the maintenance cost is low.
  • the step of performing a split task concurrently on the task group by using multiple threads includes: multiple threads randomly acquiring the split task and performing concurrent operations; after the split task is executed, the thread randomly acquires the next split The task performs the corresponding operation.
  • the thread does not perform a split task fixedly, and the split task can be randomly acquired to execute.
  • Multiple threads can simultaneously acquire multiple split tasks and perform operations concurrently, and split the data summary table. After the thread has processed a split task, it can randomly acquire the next split task to execute. Because it does not require a thread to perform a split task, it can effectively reduce the time required to perform split tasks.
  • a server in one embodiment, as shown in FIG. 3, includes a processor coupled via a system bus, an internal memory, a non-volatile storage medium, and a network interface.
  • the non-volatile storage medium of the server stores an operating system, a source database, a target database, and computer executable instructions.
  • the policy data of the organization is stored in the source database, and the data summary table corresponding to the policy data is stored in the target database.
  • Computer executable instructions are used to perform a policy data processing method.
  • the server's processor is used to provide computing and control capabilities that support the operation of the entire server.
  • the server's network interface is used to connect to the terminal and communicate with the terminal.
  • the server can be a separate server or a clustered server.
  • FIG. 3 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
  • a particular server may include more or fewer components than shown, or some components may be combined, or have different component arrangements.
  • a policy data processing apparatus including: a determining module 402, a synchronization module 404, a splitting module 406, a receiving module 408, a querying module 410, and a sending module 412, where:
  • the determining module 402 is configured to determine whether the batch processing in the plurality of source databases is completed when the synchronization time is reached.
  • the synchronization module 404 is configured to: if the batch processing in the multiple source databases is completed, trigger a synchronous operation between the source database and the target database, write policy data in the plurality of source databases into the target database, and obtain policy data in the target database. Corresponding data summary table.
  • the splitting module 406 is configured to split the data summary table into partitions of multiple dimensions in the target database.
  • the receiving module 408 is configured to receive a data query instruction sent by the terminal, where the query instruction carries dimension information.
  • the query module 410 is configured to perform a query in the corresponding partition according to the dimension information to obtain a query result.
  • the sending module 412 is configured to return the query result to the terminal, so that the terminal performs monthly node processing according to the query result.
  • the determining module 402 is further configured to start a job, use a job to obtain a log corresponding to the batch processing, use a job to check a log corresponding to the batch processing, and determine whether the batch processing is completed according to the content recorded in the log.
  • the apparatus further includes: a recording module 414, configured to record a synchronization operation log; and the determining module 402 is further configured to: after the estimated time period, use the job to check the synchronization operation log, according to the synchronization operation. The content recorded in the log is used to determine whether the synchronization operation is completed; if yes, the prompt information for completing the synchronization operation is generated; the sending module 412 is further configured to send the prompt information to the terminal.
  • a recording module 414 configured to record a synchronization operation log
  • the determining module 402 is further configured to: after the estimated time period, use the job to check the synchronization operation log, according to the synchronization operation.
  • the content recorded in the log is used to determine whether the synchronization operation is completed; if yes, the prompt information for completing the synchronization operation is generated; the sending module 412 is further configured to send the prompt information to the terminal.
  • the splitting module 406 is further configured to run multiple threads in the target database to perform a split task concurrently on the data summary table; record a split log of the split task; and when multiple threads exit from the target database When the split task is executed again, according to the split log, multiple breakpoint tasks corresponding to multiple threads are exited, and multiple threads continue to execute the split task concurrently from the breakpoint task until the data summary table is split into multiple dimensions. Partition.
  • the splitting module 406 is further configured to obtain a split task identifier in the target database, group the split tasks according to the split task identifier, and obtain multiple task groups; assign a corresponding thread to the task group; Multiple threads perform split tasks concurrently on the task group.
  • the various modules in the policy data processing apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof.
  • the receiving module 408 is configured to receive a query instruction sent by the terminal through a network interface of the server, and the sending module 412 returns the query result to the terminal through a network interface of the server.
  • the network interface may be an Ethernet card or a wireless network card.
  • the above modules may be embedded in the hardware of the base station or may be stored in the memory of the base station in a software form, so that the processor can call the corresponding operations of the above modules.
  • the processor may be a central processing unit (CPU) or a microprocessor.
  • one or more non-volatile readable storage media having computer-executable instructions that, when executed by one or more processors, cause one or more processors to execute The following steps:
  • the synchronization operation between the source database and the target database is triggered, the policy data in the plurality of source databases is written into the target database, and the data summary table corresponding to the policy data is obtained in the target database;
  • the query is performed in the corresponding partition according to the dimension information, and the query result is obtained, and the query result is returned to the terminal, so that the terminal performs monthly knot processing according to the query result.
  • determining whether the batch processing in the plurality of databases is completed includes: starting a job, acquiring a log corresponding to the batch processing by using a job; and checking a log corresponding to the batch processing by using a job, and determining whether the batch processing is performed according to the content recorded in the log carry out.
  • the one or more processors when the computer executable instructions are executed by one or more processors, the one or more processors further cause the step of: recording a synchronization operation log; after an estimated period of time, checking the synchronization operation log with a job, Determining whether the synchronization operation is completed according to the content recorded in the synchronization operation log; and if so, generating prompt information for completion of the synchronization operation, and transmitting the prompt information to the terminal.
  • splitting the data summary table into multiple dimensions in the target database includes: running multiple threads in the target database to perform split tasks concurrently on the data master table; recording split logs of split tasks And when multiple threads execute the split task after exiting from the target database, find the breakpoint tasks corresponding to the multiple threads at the exit according to the split log, and multiple threads continue to execute the split task concurrently from the breakpoint task. Until the data master is split into partitions of multiple dimensions.
  • running the multiple threads in the target database to perform the splitting task on the data table concurrently includes: obtaining the split task identifier in the target database, grouping the split tasks according to the split task identifier, and obtaining multiple tasks a group; assign a corresponding thread to the task group; and perform a split task concurrently on the task group through multiple threads.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé de traitement de données de police d'assurance, consistant : à déterminer si un traitement par lots dans une pluralité de bases de données sources est terminé lorsqu'un temps de synchronisation est atteint; si c'est le cas, à déclencher une opération de synchronisation de bases de données sources et d'une base de données cible, à écrire des données de police d'assurance de la pluralité de bases de données sources dans la base de données cible et à obtenir une table de données générale correspondant aux données de police d'assurance dans la base de données cible; à diviser la table de données générale en partitions à dimensions multiples dans la base de données cible; à recevoir une instruction de consultation de données envoyée par un terminal, l'instruction de consultation comportant des informations dimensionnelles; et à interroger dans une partition correspondante en fonction des informations dimensionnelles pour obtenir un résultat de requête et à renvoyer le résultat de requête au terminal de telle sorte que le terminal effectue un règlement mensuel en fonction du résultat de requête.
PCT/CN2017/078356 2016-07-22 2017-03-28 Procédé de traitement de données de police d'assurance, dispositif, administrateur et support de stockage WO2018014582A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610585256.2 2016-07-22
CN201610585256.2A CN106980636B (zh) 2016-07-22 2016-07-22 保单数据处理方法和装置

Publications (1)

Publication Number Publication Date
WO2018014582A1 true WO2018014582A1 (fr) 2018-01-25

Family

ID=59340373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/078356 WO2018014582A1 (fr) 2016-07-22 2017-03-28 Procédé de traitement de données de police d'assurance, dispositif, administrateur et support de stockage

Country Status (2)

Country Link
CN (1) CN106980636B (fr)
WO (1) WO2018014582A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109064295A (zh) * 2018-09-05 2018-12-21 中国平安财产保险股份有限公司 投保报价的计算方法、装置、计算机设备和存储介质
CN109213768A (zh) * 2018-09-25 2019-01-15 中国平安人寿保险股份有限公司 电子装置、基于多个临时数据表的数据查询方法及存储介质
CN109583829A (zh) * 2018-10-19 2019-04-05 中国平安人寿保险股份有限公司 基于新产品开发的月结信息处理方法、电子装置及可读存储介质
CN110134512A (zh) * 2019-04-15 2019-08-16 平安科技（深圳）有限公司 集群服务器执行任务的方法、装置、设备及存储介质
CN110308980A (zh) * 2019-06-27 2019-10-08 深圳前海微众银行股份有限公司 数据的批量处理方法、装置、设备及存储介质
CN110489275A (zh) * 2019-07-23 2019-11-22 中国平安财产保险股份有限公司 一种单据信息的处理方法及相关设备
CN110599354A (zh) * 2019-08-15 2019-12-20 中国平安财产保险股份有限公司 线上对账方法、系统、计算机设备和计算机可读存储介质
CN110825953A (zh) * 2019-11-12 2020-02-21 上海德启信息科技有限公司 数据查询方法、装置和设备
CN110895488A (zh) * 2018-09-12 2020-03-20 北京奇虎科技有限公司 任务调度方法及装置
CN111475554A (zh) * 2020-04-30 2020-07-31 上海东普信息科技有限公司 基于快递状态的数据展示方法、装置、设备及存储介质
CN112306949A (zh) * 2019-07-31 2021-02-02 中科寒武纪科技股份有限公司 数据处理方法及装置以及相关产品
CN112581295A (zh) * 2020-12-15 2021-03-30 平安养老保险股份有限公司 基于字段拆分的产品数据处理方法、装置、设备和介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107391758B (zh) * 2017-08-24 2020-08-04 阿里巴巴集团控股有限公司 数据库切换方法、装置及设备
CN107798417B (zh) * 2017-09-25 2019-06-14 平安科技（深圳）有限公司 基于关联交易数据处理的优化方法、装置和计算机设备
CN108509478B (zh) * 2017-11-23 2021-04-27 平安科技（深圳）有限公司 规则引擎文件的拆分调用方法、电子装置及存储介质
CN108629699B (zh) * 2018-05-15 2023-04-18 中国平安人寿保险股份有限公司 数据上传方法、数据上传设备、存储介质及装置
CN110196880B (zh) * 2018-06-08 2023-05-12 腾讯科技（深圳）有限公司 异构数据库数据同步方法和装置、存储介质及电子装置
CN111078510B (zh) * 2018-10-18 2023-05-16 北京国双科技有限公司 一种任务处理进度的记录方法及装置
CN109801174B (zh) * 2018-12-26 2023-11-17 平安科技（深圳）有限公司 理赔数据处理方法、装置、设备及计算机可读存储介质
CN110659328B (zh) * 2019-08-30 2022-04-29 中国人民财产保险股份有限公司 数据查询方法、装置、设备及计算机可读存储介质
CN110928947A (zh) * 2019-10-16 2020-03-27 中国平安财产保险股份有限公司 基于kettle的数据同步方法、装置及相关设备
CN110851533A (zh) * 2019-11-13 2020-02-28 泰康保险集团股份有限公司 跨异构数据库的数据同步方法、装置、介质及电子设备
CN111126935B (zh) * 2019-11-19 2023-07-21 泰康保险集团股份有限公司 保全数据的处理方法、装置、电子设备和存储介质
CN112100219B (zh) * 2020-09-22 2024-01-30 平安养老保险股份有限公司 基于数据库查询处理的报表生成方法、装置、设备和介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104111957A (zh) * 2013-04-22 2014-10-22 阿里巴巴集团控股有限公司 一种分布式事务同步的方法及系统
US20150019488A1 (en) * 2013-07-09 2015-01-15 Oracle International Corporation Automated database migration architecture
CN105138615A (zh) * 2015-08-10 2015-12-09 北京思特奇信息技术股份有限公司 一种构建大数据分布式日志的方法和系统
CN105320676A (zh) * 2014-07-04 2016-02-10 中国移动通信集团黑龙江有限公司 一种客户数据查询服务方法及装置
CN105760485A (zh) * 2016-02-17 2016-07-13 上海携程商务有限公司 财务数据抽取方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104111957A (zh) * 2013-04-22 2014-10-22 阿里巴巴集团控股有限公司 一种分布式事务同步的方法及系统
US20150019488A1 (en) * 2013-07-09 2015-01-15 Oracle International Corporation Automated database migration architecture
CN105320676A (zh) * 2014-07-04 2016-02-10 中国移动通信集团黑龙江有限公司 一种客户数据查询服务方法及装置
CN105138615A (zh) * 2015-08-10 2015-12-09 北京思特奇信息技术股份有限公司 一种构建大数据分布式日志的方法和系统
CN105760485A (zh) * 2016-02-17 2016-07-13 上海携程商务有限公司 财务数据抽取方法及系统

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109064295A (zh) * 2018-09-05 2018-12-21 中国平安财产保险股份有限公司 投保报价的计算方法、装置、计算机设备和存储介质
CN110895488B (zh) * 2018-09-12 2023-10-20 三六零科技集团有限公司 任务调度方法及装置
CN110895488A (zh) * 2018-09-12 2020-03-20 北京奇虎科技有限公司 任务调度方法及装置
CN109213768A (zh) * 2018-09-25 2019-01-15 中国平安人寿保险股份有限公司 电子装置、基于多个临时数据表的数据查询方法及存储介质
CN109583829A (zh) * 2018-10-19 2019-04-05 中国平安人寿保险股份有限公司 基于新产品开发的月结信息处理方法、电子装置及可读存储介质
CN109583829B (zh) * 2018-10-19 2024-03-15 中国平安人寿保险股份有限公司 基于新产品开发的月结信息处理方法、电子装置及可读存储介质
CN110134512A (zh) * 2019-04-15 2019-08-16 平安科技（深圳）有限公司 集群服务器执行任务的方法、装置、设备及存储介质
CN110134512B (zh) * 2019-04-15 2024-02-13 平安科技（深圳）有限公司 集群服务器执行任务的方法、装置、设备及存储介质
CN110308980A (zh) * 2019-06-27 2019-10-08 深圳前海微众银行股份有限公司 数据的批量处理方法、装置、设备及存储介质
CN110489275A (zh) * 2019-07-23 2019-11-22 中国平安财产保险股份有限公司 一种单据信息的处理方法及相关设备
CN110489275B (zh) * 2019-07-23 2023-06-02 中国平安财产保险股份有限公司 一种单据信息的处理方法及相关设备
CN112306949A (zh) * 2019-07-31 2021-02-02 中科寒武纪科技股份有限公司 数据处理方法及装置以及相关产品
CN112306949B (zh) * 2019-07-31 2022-11-01 中科寒武纪科技股份有限公司 数据处理方法及装置以及相关产品
CN110599354B (zh) * 2019-08-15 2023-11-21 中国平安财产保险股份有限公司 线上对账方法、系统、计算机设备和计算机可读存储介质
CN110599354A (zh) * 2019-08-15 2019-12-20 中国平安财产保险股份有限公司 线上对账方法、系统、计算机设备和计算机可读存储介质
CN110825953A (zh) * 2019-11-12 2020-02-21 上海德启信息科技有限公司 数据查询方法、装置和设备
CN110825953B (zh) * 2019-11-12 2024-03-22 上海德启信息科技有限公司 数据查询方法、装置和设备
CN111475554A (zh) * 2020-04-30 2020-07-31 上海东普信息科技有限公司 基于快递状态的数据展示方法、装置、设备及存储介质
CN111475554B (zh) * 2020-04-30 2024-03-01 上海东普信息科技有限公司 基于快递状态的数据展示方法、装置、设备及存储介质
CN112581295A (zh) * 2020-12-15 2021-03-30 平安养老保险股份有限公司 基于字段拆分的产品数据处理方法、装置、设备和介质
CN112581295B (zh) * 2020-12-15 2023-09-26 平安养老保险股份有限公司 基于字段拆分的产品数据处理方法、装置、设备和介质

Also Published As

Publication number Publication date
CN106980636A (zh) 2017-07-25
CN106980636B (zh) 2020-04-03

Similar Documents

Publication Publication Date Title
WO2018014582A1 (fr) Procédé de traitement de données de police d'assurance, dispositif, administrateur et support de stockage
WO2018161478A1 (fr) Support d'informations, serveur, dispositif et procédé de traitement de fragmentation destiné à être utilisé avec des chaînes multi-blocs
WO2018177107A1 (fr) Procédé de migration de données, serveur de migration, et support d'informations
WO2019154394A1 (fr) Système en grappes de bases de données réparties, procédé de synchronisation de données et support de stockage
WO2021003985A1 (fr) Procédé et appareil de stockage d'archivage de données de chaîne de blocs, dispositif informatique et support d'informations
WO2017177769A1 (fr) Procédé et système de déploiement de versions ogg, serveur, et support de stockage
WO2019134226A1 (fr) Procédé de collecte de journaux, dispositif, appareil terminal et support d'informations
CN103729442B (zh) 记录事务日志的方法和数据库引擎
WO2018233037A1 (fr) Procédé de test d'intégration de base de données, dispositif, serveur et support d'informations
WO2018014580A1 (fr) Procédé et appareil de test d'interface de données, serveur et support de stockage
US11726984B2 (en) Data redistribution method and apparatus, and database cluster
WO2020238066A1 (fr) Procédé et appareil de test de pression de logiciel, support d'informations et serveur.
WO2018161479A1 (fr) Système et procédé de traitement de grappe de chaînes de blocs, dispositif informatique et support de stockage
WO2018036167A1 (fr) Procédé, dispositif, serveur et support de stockage d'affectation d'exécuteurs de tâches de test
WO2017162032A1 (fr) Procédé et dispositif d'exécution d'une opération de récupération de données
WO2013117104A1 (fr) Système et procédé de téléchargement de données hors ligne bt, et support de stockage informatique
CN111026767B (zh) 区块链的数据存储方法、装置及硬件设备
CN112182104A (zh) 一种数据同步方法、装置、设备及存储介质
WO2020253314A1 (fr) Procédé, appareil et système de surveillance de transaction pour base de données distribuée et support de stockage
CN113704790A (zh) 一种异常日志信息汇总方法及计算机设备
WO2019047565A1 (fr) Procédé de traitement de tâches, dispositif, dispositif informatique, et support d'informations
WO2021169496A1 (fr) Procédé, appareil et dispositif de lecture de données, et support de stockage
US20170177463A1 (en) Data flow analysis in processor trace logs using compiler-type information method and apparatus
WO2018036168A1 (fr) Procédé et dispositif d'exécution de tâche de traitement de données, serveur d'exécution et support de stockage
WO2017181430A1 (fr) Procédé et dispositif de duplication de base de données dans un système distribué

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

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

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

122 Ep: pct application non-entry in european phase

Ref document number: 17830224

Country of ref document: EP

Kind code of ref document: A1