CN107784588A - Insurance user information merging method and device - Google Patents
Insurance user information merging method and device Download PDFInfo
- Publication number
- CN107784588A CN107784588A CN201610817453.2A CN201610817453A CN107784588A CN 107784588 A CN107784588 A CN 107784588A CN 201610817453 A CN201610817453 A CN 201610817453A CN 107784588 A CN107784588 A CN 107784588A
- Authority
- CN
- China
- Prior art keywords
- user
- database
- branch
- mark
- identity data
- 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
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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present invention relates to a kind of Insurance User information merging method, methods described includes：Obtain user profile and merge instruction；One of branch's database is chosen from branch's database of predetermined number, the identity data of one group of user is extracted from selected branch's database；User of the inquiry with common identity data from non-selected branch's database, using the user with common identity data inquired as user to be combined；User profile corresponding to user profile corresponding to the user extracted and user to be combined is merged.The above method can improve the convenience of Insurance User information management.In addition, also corresponding provide a kind of Insurance User information consolidation device.
Description
Technical field
The present invention relates to technical field of information processing, more particularly to a kind of Insurance User information merging method and device.
Background technology
For larger insurance business, multiple data for being used to deposit Insurance User information are generally all provided with
Storehouse, the area different positioned at the whole nation, each database are used for the information for storing the Insurance User of corresponding region.Deposited in each region
In one or more insurance institutions, each insurance institution is used for the Insurance User of server corresponding region scope, and insurance is used
The information at family is stored into the server of corresponding region.
It is increasing however as the mobility of user, it may appear that increasing user is handled insurance by trans-regional
Business.When same Insurance User handles insurance business again in other trans-regional insurance institutions, because the mechanism is corresponding
Database in do not record the information of the Insurance User, thus a use can be increased newly in the database for the Insurance User
Family information.It will so cause an Insurance User that there is different user profile in different databases, Insurance User is believed
The maintenance of breath impacts, and causes managerial confusion.
The content of the invention
Based on this, it is necessary to for above-mentioned technical problem, there is provided one kind can improve Insurance User information management convenience
Insurance User information merging method and device.
A kind of Insurance User information merging method, methods described include：
Obtain user profile and merge instruction；
One of branch's database is chosen from branch's database of predetermined number, from selected branch's database
Extract the identity data of one group of user；
User of the inquiry with common identity data, has identical body by what is inquired from non-selected branch's database
The user of part data is as user to be combined；
User profile corresponding to user profile corresponding to the user extracted and user to be combined is merged.
In one of the embodiments, before the step of acquisition user profile merges instruction, including：
When current time reaches preset time, generate the user profile and merge instruction, the preset time is advance
What is set is used to trigger the time of user profile union operation.
In one of the embodiments, the merging instruction includes merging progress msg, the merging progress packet
Include branch's Database Identification of branch's database and user's mark of the user extracted selected at the end of last merge
Know；
One of branch's database is chosen in branch's database from predetermined number, from selected branch's data
The step of identity data of one group of user is extracted in storehouse, including：
Branch's database corresponding to branch's Database Identification is chosen from branch's database of predetermined number；
Identity of the extraction positioned at the next group of user of user corresponding to user mark from branch's database of selection
Data, subsequently to be merged to the user profile that same subscriber be present in the next group of user.
In one of the embodiments, it is described by corresponding to user profile corresponding to the user extracted and user to be combined
The step of user profile merges, in addition to：
Obtain the creation time of user's mark of the user of the selection and user's mark of user to be combined；
Using the user's mark of creation time the latest as user's mark of the user of the selection and the use to be combined
User's mark at family.
In one of the embodiments, it is described by corresponding to user profile corresponding to the user extracted and user to be combined
The step of user profile merges, in addition to：
The user of user's mark of the user chosen described in central database and user to be combined is identified into user's mark
Know and make to merge mark.
A kind of Insurance User information consolidation device, described device include：
Merge instruction acquisition module, merge instruction for obtaining user profile；
Identity data extraction module, for choosing one of branch's database from branch's database of predetermined number,
The identity data of one group of user is extracted from selected branch's database；
Enquiry module, for user of the inquiry with common identity data from non-selected branch's database, it will inquire about
The user with common identity data gone out is as user to be combined；
Merging module, for user profile corresponding to user profile corresponding to the user extracted and user to be combined to be entered
Row merges.
In one of the embodiments, merge instruction acquisition module to be additionally operable to when current time reaches preset time, it is raw
Into the user profile merge instruct, the preset time be pre-set be used for trigger user profile union operation when
Between.
In one of the embodiments, the merging instruction includes merging progress msg, the merging progress packet
Include branch's Database Identification of branch's database and user's mark of the user extracted selected at the end of last merge
Know；
The identity data extraction module includes：
Branch's database chooses unit, for choosing branch's Database Identification from branch's database of predetermined number
Corresponding branch's database；
Identity data extraction unit, used for being extracted from branch's database of selection positioned at corresponding to user mark
The identity data of the next group of user at family, so as to subsequently to the progress of the user profile of same subscriber in the next group of user be present
Merge.
In one of the embodiments, the merging module be additionally operable to obtain the user of the selection user's mark and
The creation time of user's mark of user to be combined；Use using the user's mark of creation time the latest as the user of the selection
Family identifies and the user of the user to be combined mark.
In one of the embodiments, the merging module is additionally operable to the use for the user that will be chosen described in central database
Family identifies and the user of user to be combined identifies user and identified and makees to merge mark.
Above-mentioned Insurance User information merging method and device, by choosing wherein one from branch's database of predetermined number
Individual branch's database, the identity data of one group of user is extracted from selected branch's database；Again from non-selected branch's number
According to user of the inquiry with common identity data in storehouse, using the user with common identity data inquired as use to be combined
Family；Then user profile corresponding to user profile corresponding to the user extracted and user to be combined is merged.So as to
Keep information of the same user in disparate databases identical, be easy to management and maintenance to Insurance User information.
Brief description of the drawings
Fig. 1 is the applied environment figure of Insurance User information merging method in one embodiment；
Fig. 2 is the flow chart of Insurance User information merging method in one embodiment；
Fig. 3 is that one of branch's database is chosen from branch's database of predetermined number in one embodiment, from institute
The flow chart for the step of identity data of one group of user is extracted in branch's database of selection；
Fig. 4 is the flow chart of Insurance User information merging method in another embodiment；
Fig. 5 is the timing diagram of Insurance User information merging method in one embodiment；
Fig. 6 is the structured flowchart of Insurance User information consolidation device in one embodiment；
Fig. 7 is the structured flowchart of identity data extraction module in one embodiment.
Embodiment
In order to make the purpose , technical scheme and advantage of the present invention be clearer, it is right below in conjunction with drawings and Examples
The present invention is further elaborated.It should be appreciated that specific embodiment described herein is only to explain the present invention, not
For limiting the present invention.
The Insurance User information merging method that the embodiment of the present invention is provided can be applied to application scenarios as shown in Figure 1
In.With reference to shown in figure 1, if branch's database has N number of, respectively branch's database 120A~120N can be located at different areas
Domain, the user data of the user for being stored in business of being handled insurance in the range of corresponding region.In general, each branch's database
Only it is connected with server 110, and between each branch's database and is not attached to.Server 110 is the system service of insurance company
Device, is integrated with central database in it, and central database can be by the network and branch database 120A~120N that pre-set
It is connected, the user for collecting and storing each Insurance User identifies.Server 110 can be associated with respectively by central database
Data in branch's database are managed by individual branch's database.Remembered when needing to merge in each branch's database
During the user profile of the identical user of record, then corresponding branch database can be associated, is chosen successively in each branch's database
User identity data, inquired about as the keyword of inquiry, and according to the identity data in other branch's databases,
The user with common identity data inquired is entered as user to be combined, and by the user extracted and user to be combined
Row merges.
In one embodiment, as shown in Figure 2, there is provided a kind of Insurance User information merging method, this method can be applied
In server as shown in Figure 1, following steps are specifically included：
Step 202, obtain user profile and merge instruction.
In the present embodiment, it is for having identical use by described in multiple branch's databases that user profile, which merges instruction,
The instruction that the user profile at family merges.Merging instruction can be initiated as the terminal to server where keeper, also can be by
System is set automatically, in it is predetermined at the time of initiate.User profile includes the essential information and insurance information of user, basic letter
The information such as the name for including user, sex, identification card number, contact method are ceased, insurance information includes the insurance that user bought
The information such as insurance kind, social security number or taxid, protection amount, insurance period.
Branch's database can be that it distributes corresponding user's mark, the user mark when Insurance User is newly created
For Insurance User corresponding to unique identification.User mark can by the numeral of predetermined number, letter and other spcial characters according to
Certain queueing discipline is formed.Each consolidated storage will can be used after corresponding Insurance User is created corresponding to the Insurance User
Family mark is uploaded to central database, central database can store received user's mark so that can be according to being stored
User is identified to inquire about and be associated with the user profile in other branch's databases, and corresponding user profile is managed.
In one embodiment, before the step of user profile merges instruction is obtained, including：Reach pre- in current time
If during the time, generation user profile merges instruction.
In the present embodiment, user profile merge instruction can be set automatically by system, in it is predetermined at the time of initiate.Service
Device can the real-time detecting system time, when system time reaches preset time, then generate user profile merge instruction.Wherein, in advance
Can be random time if the time is the time for triggering user profile union operation pre-set.Specifically, clothes may be selected
Performed when business device is more idle, such as, it may be configured as 23：00, or 01：00.
Step 204, one of branch's database is chosen from branch's database of predetermined number, from selected branch
The identity data of one group of user is extracted in database.
In the present embodiment, server can be according to the corresponding network interface of merging instruction calls and communications protocol and present count
Branch's database of amount is connected, to carry out the management to the user profile in branch's database for being connected.Wherein present count
Amount can determine according to the quantity of branch's database of required merging treatment.Branch's number corresponding to each branch database local
Identified according to storehouse, for unique identification and determine corresponding branch's database.
After branch's database of connection predetermined number, one of branch's database is chosen, and from selected branch
The identity data of one group of user is extracted in database, the keyword as inquiry.Wherein, the identity data of one group of user includes
The fractional data of at least one user.Identity data is the data for identifying and confirming user identity, can be branch's database
The identification card number of middle stored user, further, in addition to including identification card number, may also include surname, sex, age etc. its
One or more of, using these information as identity data.
The quantity of the identity data extracted can be any amount.When selected identity data is one, then it represents that
Carry out single query.When selected user data is multiple, then it represents that while inquire about in other branch's databases and whether deposit
Identical with any one user of the plurality of user.Specifically, can be set a suitable quantity so that the speed of inquiry with
And reach a poised state between the free value of server and each branch's database.Free value is used to characterize corresponding point of reflection
Portion's database or server are to the situation of Current resource occupancy, i.e. idle degrees.Free value is bigger, then illustrates branch's data
The resources occupation rate in storehouse is smaller, and its execution speed to instruction or task is then faster；Free value is smaller, then illustrates branch's data
The resources occupation rate in storehouse is bigger, and its execution speed to instruction or task is then slower, or even can cause system crash so that instruction
Or tasks carrying failure.
Step 206, user of the inquiry with common identity data, the tool that will be inquired from non-selected branch's database
There is the user of common identity data as user to be combined.
In the present embodiment, server can send the identity data of one group of user to non-selected branch's database, make
Whether the identity data in its interior user of non-selected branch's data base querying is with any one user's in this group of user
Identity data is identical.If so, it with corresponding extracted user is same subscriber then to illustrate that this has the user of common identity data,
As user to be combined, if it is not, then illustrating that same subscriber is not present in non-selected branch's database.
Specifically, server generates query statement according to selected identity data, send to non-selected branch's data
Storehouse, makes whether non-selected branch's data base querying has the user of common identity data in it, and Query Result is fed back into clothes
Business device.Non-selected branch's database is after the query statement of server transmission is received, then according to the query statement according to this
Identity data is inquired about, and is generated Query Result, is sent to server.When inquiring the user in the presence of the identity data, then
When Query Result represents to include same subscriber, user's letter that the user with common identity data is carried in Query Result can be made
Breath；When not inquiring the user in the presence of the identity data, generation Query Result can be made for sky.The non-branch's database of server is anti-
The Query Result of feedback, when Query Result represents the user in the presence of the identity data, acquisition has the user's of common identity data
User profile, using the user with same keyword as user to be combined.
Step 208, user profile corresponding to user profile corresponding to the user extracted and user to be combined is closed
And.
In the present embodiment, server extracted from selected branch's database corresponding to identity data user user
Information, the user profile extracted is sent to corresponding non-selected branch's database so that branch's database believes the user
Breath is incorporated into the user profile of user to be combined.And the user profile of user to be combined is further also sent to point of selection
Portion's database, make selected branch's database that the user profile of user to be combined to be incorporated into the user of the user accordingly extracted
Among information, the merging to same subscriber information is realized.
In the present embodiment, by choosing one of branch's database from branch's database of predetermined number, from selected
The identity data of one group of user is extracted in the branch's database taken；Inquiry has identical body from non-selected branch's database again
The user of part data, using the user with common identity data inquired as user to be combined；Then the use that will be extracted
User profile corresponding to user profile corresponding to family and user to be combined merges.So as to keep same user in different numbers
It is identical according to the information in storehouse, it is easy to management and maintenance to Insurance User information.
In one embodiment, merging instruction includes merging progress msg, merges progress packet and includes last merging
At the end of selected branch's Database Identification of branch's database and user's mark of the user extracted.
In the present embodiment, server can carry out the merging of same subscriber information in preset time period.For example it can be set and be somebody's turn to do
It is daily 0 with preset time period：00~3：00.When server is terminating the execution of preset time period, it is last to can record this
Merging progress when once performing.So that when preparing to initiate to merge instruction next time, corresponding merging progress, root can be read
Generated according to the merging progress and merge instruction.Wherein, branch's database that progress packet includes selected branch's database is merged
The user of mark and the user extracted mark.
As shown in figure 3, one of branch's database is chosen from branch's database of predetermined number, from selected point
The step of identity data of one group of user is extracted in portion's database, including：
Step 302, branch's database corresponding to branch's Database Identification is chosen from branch's database of predetermined number.
In the present embodiment, server can obtain branch's Database Identification in entrained merging progress, by branch's number
According to storehouse identify corresponding to branch's database as choose branch's database.
Step 304, extraction is located at the next group of user of user corresponding to user's mark from branch's database of selection
Identity data.
In the present embodiment, the user profile of the user in branch's database can store in order, and can be to branch's database
In user be numbered, server can once according to the number order of user out of it corresponding user of extraction identity data.
When the identity data for the user not extracted in selected branch's database also be present, extraction therefrom identifies positioned at user
The identity data of the next group of user of corresponding user, as detecting whether the keyword of same subscriber be present, with after an action of the bowels
The continuous user profile to same subscriber be present in the next group of user merges, so as to complete to being deposited in whole branch's database
In the merging of the user profile of same subscriber.
In the present embodiment, include merging progress msg due to merging instruction, so as to according to merging progress msg come true
Surely branch's database selected during union operation and the identity data of corresponding user are continued so that can be achieved to be divided into
Repeatedly complete the merging of the user profile to the same subscriber in all branch's databases.
In one embodiment, by user profile corresponding to user profile corresponding to the user extracted and user to be combined
The step of merging, including：During the establishment of user's mark of the user of acquisition extraction and user's mark of user to be combined
Between；Identified using the user's mark of creation time the latest as user's mark of the user chosen and the user of user to be combined.
In the present embodiment, when server can obtain user's mark of user corresponding to extracted identity data and its create
Between, and the user's mark and its creation time of user to be combined are obtained, and compare the size of the creation time of two user's marks, will
The user's mark of the creation time the latest user mark common as both so that although identical Insurance User is in different pieces of information
There is user profile corresponding to record in storehouse, but be respectively provided with identical user mark, to facilitate management and the dimension to user profile
Shield.For example, if the creation time of user's mark of the user extracted is later than user's mark as user to be combined
Creation time, then the user that user's mark of the user of extraction is revised as to user to be combined identifies, conversely, then by use to be combined
User's mark at family is revised as user's mark of corresponding extracted user.
In one embodiment, by user profile corresponding to user profile corresponding to the user extracted and user to be combined
The step of merging, in addition to：By user's mark of the user chosen in central database and the user of user to be combined
Identify user and identify and make to merge mark.
In the present embodiment, because identical user has record in two or more branch's databases, thus,
There is also corresponding two or more different records in central database for the same subscriber.Thus, by branch's data
After user's mark is modified corresponding to same subscriber in storehouse, can only retain in central database with branch database
Amended user identifies identical user mark, the other users mark for deleting the same subscriber, the user is identified with doing
Merge mark so that would know that the information of the user has record in which branch's database respectively according to merging mark.
In the present embodiment, by also being changed accordingly central database, it can further improve to Insurance User
The convenience of subscriber information management.
In one embodiment, as shown in Figure 4, there is provided another Insurance User information merging method, this method include
Following steps：
Step 402, obtain user profile and merge instruction.
Step 404, one of branch's database is chosen from branch's database of predetermined number.
Step 406, the identity data of one group of user is extracted from selected branch's database.
Step 408, whether inquired about from non-selected branch's database has the user of common identity data.If so, then
Step 410 is performed, otherwise, performs step 412.
For example, the identity data of the user extracted is the jth user in i-th branch's database to jth+k user
Identity data.Jth+a (0 in the identity data and i-th branch's database in the i-th+m branches database in the presence of the n-th user
≤ a≤k) user identity data it is identical when, then it represents that in non-selected branch's database have common identity data user.
Step 410, using the user with common identity data inquired as user to be combined, the user that will be extracted
User profile corresponding to corresponding user profile and user to be combined merges.
Continue that with above-mentioned for example bright, the user profile of the n-th user in the i-th+m branches database can be obtained, will
It is sent in i-th branch's database, makes the jth+a users' that i-th branch's database is incorporated into i-th branch's database
In user profile；Meanwhile the user profile of the jth+a users in i-th branch's database is also obtained, send it to the i-th branch
In database, in the user profile for making the n-th user that i-th branch's database is incorporated into the i-th+m branches database.So as to
The insurance information that user handled there is into comprehensive record in i-th branch's database and the i-th+m branches database, it is real
Now to the merging of the user profile of two same subscribers.
Step 412, the identity data that all users whether had been extracted in selected branch's database is detected.If
It is then to perform step 414, otherwise, performs step 416.
In the present embodiment, after the merging of information of the user with common identity data is completed, or in the absence of being carried
During the user with common identity data taken, then the identity that all users whether had been extracted in branch's database is detected
Data.Specifically, the user in branch's database can be numbered, and extracted successively according to the number order of user out of it
The identity data of corresponding user.If it has M user, then the user in it is used according to the number consecutively that puts in order for the 1st
Family, the 2nd user ... M user.Then when the user extracted in step 406 includes M user, then it represents that branch's data
The identity data of all users had been extracted in storehouse, now, can perform step 414, otherwise, has performed step 416.
Step 414, next branch's database is chosen from branch's database of predetermined number, point as new selection
Portion's database.
In the present embodiment, when in branch's database of predetermined number also exist more than one branch not chosen database
When, then continue to choose next branch's database from branch's database of predetermined number, branch's data as new selection
Storehouse.It is similar, equally can be to branch's database line number in sequence.If N number of branch's database be present, then by predetermined number
Branch's database is according to the number consecutively that puts in order for the 1st branch's database, the 2nd database ... N branches of branch database.
When branch's database selected in step 404 is i-th branch's database, then branch's database selected by step 414 is
I+1 branch database, as new branch's database.
Step 416, the identity data of next group of user is extracted again from selected branch's database.
When the identity data for not extracting all users in the present embodiment, in selected branch's database also be present,
The identity data of next group of user can be extracted again from selected branch's database.Specifically, can be in branch's database
User be divided into K groups according to its number order, every group can have identical or different number of users.Wherein, when for the first time in branch
When being extracted in database, the identity data of the 1st group of user can extract.After the detection and merging to the 1st group of user is completed, then
Continue to extract the identity data of next group of user, that is, extract the identity data of the 2nd group of user.
In the present embodiment, by choosing one of branch's database from branch's database of predetermined number successively, and it is right
The identity data of one group of user is extracted in selected branch's database successively, is then looked into again from non-selected branch's database
Whether ask has the user of common identity data, using the user with common identity data inquired as user to be combined,
User profile corresponding to user profile corresponding to the user extracted and user to be combined is merged, until will complete all
The merging of the user profile of same subscriber in branch's database.It can further improve the management and maintenance to Insurance User information
Convenience.
In one embodiment, above-mentioned non-selected branch's database is numbering positioned at the branch's database currently chosen
Numbering after branch's database.The even currently selected branch's database taken is i-th branch's database, then non-selected point
Portion's database is i+1 branch database to N branches database.Because the user in preceding branch's database has been carried
Inquiry is taken into merging, then when carrying out the same subscriber inquiry to follow-up branch's database, without again from preceding branch
Database is inquired about, and can reduce the occupancy to query resource, improves search efficiency.
In one embodiment, using i-th branch's database as the branch's database chosen, the i-th+j branches database is made
Exemplified by one of them non-selected branch's database, the timing diagram of Insurance User information merging method is as shown in Figure 5.
Step 501, server obtains user profile merging instruction.
Step 502, the identity data of one group of user is extracted from i-th branch's database.
Step 503, the identity data is sent to the i-th+j branches database.
Step 504, the i-th+j branches data base querying whether there is the user with common identity data in it, and generation is looked into
Ask result.
Step 505, Query Result is sent to server.
Step 506, when Query Result represents that identical user is not present, step 502 is continued executing with, from i-th branch's number
According to the identity data that one group of new user is extracted in storehouse, until completing the identity number to all users in i-th branch's database
According to extraction.
Step 507, when Query Result represents to have identical user, then Query Result is sent to i-th branch's data
Storehouse.
In the present embodiment, included in Query Result in the i-th+j branches database, be same subscriber with the user extracted
User profile.
Step 508, the user profile included in received Query Result is merged into accordingly quilt by i-th branch's database
In the user profile of the user of extraction.
Step 509, i-th branch's database sends the user profile for the user being extracted to server.
Step 510, server sends the user profile to the i-th+j branches database.
In the present embodiment, after step 510, step 502 is continued executing with, new one is extracted from i-th branch's database
The identity data of group user, until completing the extraction to the identity data of all users in i-th branch's database.
Step 511, the user profile received is merged into user's letter of corresponding identical user by the i-th+j branches database
Among breath.
In one embodiment, as shown in Figure 6, there is provided a kind of Insurance User information consolidation device, the device include：
Merge instruction acquisition module 602, merge instruction for obtaining user profile.
Identity data extraction module 604, for choosing one of branch's data from branch's database of predetermined number
Storehouse, the identity data of one group of user is extracted from selected branch's database.
Identity data extraction module 606, for being inquired about from non-selected branch's database with common identity data
User, using the user with common identity data inquired as user to be combined.
Merging module 608, for user corresponding to user profile corresponding to the user extracted and user to be combined to be believed
Breath merges.
In one embodiment, merge instruction acquisition module 602 to be additionally operable to when current time reaches preset time, generate
User profile merges instruction, and the preset time is the time for triggering user profile union operation pre-set.
In one embodiment, merging instruction includes merging progress msg, merges progress packet and includes last merging
At the end of selected branch's Database Identification of branch's database and user's mark of the user extracted.
As shown in fig. 7, identity data extraction module 604 includes：
Branch's database chooses unit 702, for choosing branch's Database Identification from branch's database of predetermined number
Corresponding branch's database.
Branch's database chooses unit 704, for being extracted from branch's database of selection positioned at corresponding to user's mark
The identity data of the next group of user of user, so as to subsequently to the progress of the user profile of same subscriber in the next group of user be present
Merge.
In one embodiment, merging module 608 is additionally operable to obtain user's mark of the user chosen and use to be combined
The creation time of user's mark at family；The user's mark of creation time the latest is identified and treated as the user of the user chosen
Merge user's mark of user.
In one embodiment, merging module 608 be additionally operable to the user that will be chosen in central database user identify with
And the user of user to be combined identifies user and identified and makees to merge mark.
Each technical characteristic of embodiment described above can be combined arbitrarily, to make description succinct, not to above-mentioned reality
Apply all possible combination of each technical characteristic in example to be all described, as long as however, the combination of these technical characteristics is not deposited
In contradiction, the scope that this specification is recorded all is considered to be.
Embodiment described above only expresses the several embodiments of the present invention, and its description is more specific and detailed, but simultaneously
Can not therefore it be construed as limiting the scope of the patent.It should be pointed out that come for one of ordinary skill in the art
Say, without departing from the inventive concept of the premise, various modifications and improvements can be made, these belong to the protection of the present invention
Scope.Therefore, the protection domain of patent of the present invention should be determined by the appended claims.
Claims (10)
1. a kind of Insurance User information merging method, it is characterised in that methods described includes：
Obtain user profile and merge instruction；
One of branch's database is chosen from branch's database of predetermined number, is extracted from selected branch's database
The identity data of one group of user；
User of the inquiry with common identity data, has common identity number by what is inquired from non-selected branch's database
According to user as user to be combined；
User profile corresponding to user profile corresponding to the user extracted and user to be combined is merged.
2. according to the method for claim 1, it is characterised in that it is described acquisition user profile merge instruction the step of it
Before, including：
When current time reaches preset time, generate the user profile and merge instruction, the preset time is to pre-set
Be used for trigger time of user profile union operation.
3. according to the method for claim 1, it is characterised in that the merging instruction includes merging progress msg, described
Merging progress packet includes branch's Database Identification of last branch's database selected at the end of merging and extracted
User user mark；
One of branch's database is chosen in branch's database from predetermined number, from selected branch's database
The step of extracting the identity data of one group of user, in addition to：
Branch's database corresponding to branch's Database Identification is chosen from branch's database of predetermined number；
Extraction is located at the identity data of the next group of user of user corresponding to user mark from branch's database of selection,
Subsequently to be merged to the user profile that same subscriber be present in the next group of user.
4. according to the method for claim 1, it is characterised in that described user profile corresponding to the user that extracted and to treat
The step of user profile corresponding to merging user merges, including：
Obtain the creation time of user's mark of the user of the selection and user's mark of user to be combined；
The user that creation time user the latest is identified to the user as the selection identifies and the user to be combined
User identifies.
5. according to the method for claim 4, it is characterised in that described user profile corresponding to the user that extracted and to treat
The step of user profile corresponding to merging user merges, in addition to：
The user of user's mark of the user chosen described in central database and user to be combined is identified user and identified and is made
Merge mark.
6. a kind of Insurance User information consolidation device, it is characterised in that described device includes：
Merge instruction acquisition module, merge instruction for obtaining user profile；
Identity data extraction module, for choosing one of branch's database from branch's database of predetermined number, from institute
The identity data of one group of user is extracted in branch's database of selection；
Enquiry module, for user of the inquiry with common identity data from non-selected branch's database, by what is inquired
User with common identity data is as user to be combined；
Merging module, for user profile corresponding to user profile corresponding to the user extracted and user to be combined to be closed
And.
7. device according to claim 6, it is characterised in that merge instruction acquisition module and be additionally operable to reach in current time
During preset time, generate the user profile and merge instruction, the preset time is to pre-set for triggering user profile
The time of union operation.
8. device according to claim 6, it is characterised in that the merging instruction includes merging progress msg, described
Merging progress packet includes branch's Database Identification of last branch's database selected at the end of merging and extracted
User user mark；
The identity data extraction module includes：
Branch's database chooses unit, corresponding for choosing branch's Database Identification from branch's database of predetermined number
Branch's database；
Identity data extraction unit, for being extracted from branch's database of selection positioned at user corresponding to user mark
The identity data of next group of user, subsequently to be closed to the user profile that same subscriber be present in the next group of user
And.
9. device according to claim 6, it is characterised in that the merging module is additionally operable to obtain the user of the selection
User mark and user to be combined user mark creation time；The user of creation time the latest is identified as described in
User's mark of the user of selection and user's mark of the user to be combined.
10. device according to claim 9, it is characterised in that the merging module is additionally operable to institute in central database
State user's mark of the user of selection and the user of user to be combined identifies user and identified and makees to merge mark.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610817453.2A CN107784588A (en) | 2016-09-12 | 2016-09-12 | Insurance user information merging method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610817453.2A CN107784588A (en) | 2016-09-12 | 2016-09-12 | Insurance user information merging method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107784588A true CN107784588A (en) | 2018-03-09 |
Family
ID=61438157
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610817453.2A Pending CN107784588A (en) | 2016-09-12 | 2016-09-12 | Insurance user information merging method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107784588A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108648092A (en) * | 2018-05-16 | 2018-10-12 | 中国平安人寿保险股份有限公司 | Loss ratio computational methods, device, equipment and computer readable storage medium |
| CN108961078A (en) * | 2018-06-29 | 2018-12-07 | 泰康保险集团股份有限公司 | Insure the method, apparatus storage medium and electronic equipment of family's polymerization |
| CN110825717A (en) * | 2019-10-10 | 2020-02-21 | 厦门市美亚柏科信息股份有限公司 | Data normalization method, device and medium for identity recognition |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1295298A (en) * | 1999-11-05 | 2001-05-16 | 数字网站公司 | Method for merging data base of internet service company |
| CN1407475A (en) * | 2001-08-24 | 2003-04-02 | 前锦网络信息技术(上海)有限公司 | Synchronous updating personnel resume database method based on internet |
| WO2009110837A2 (en) * | 2008-02-11 | 2009-09-11 | Strömberg Distribution Ab | Method for producing documents |
| CN103390003A (en) * | 2012-05-09 | 2013-11-13 | 人人游戏网络科技发展（上海）有限公司 | Method and device for combining user data information among servers |
| CN105207996A (en) * | 2015-08-18 | 2015-12-30 | 小米科技有限责任公司 | Account merging method and apparatus |
-
2016
- 2016-09-12 CN CN201610817453.2A patent/CN107784588A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1295298A (en) * | 1999-11-05 | 2001-05-16 | 数字网站公司 | Method for merging data base of internet service company |
| CN1407475A (en) * | 2001-08-24 | 2003-04-02 | 前锦网络信息技术(上海)有限公司 | Synchronous updating personnel resume database method based on internet |
| WO2009110837A2 (en) * | 2008-02-11 | 2009-09-11 | Strömberg Distribution Ab | Method for producing documents |
| CN103390003A (en) * | 2012-05-09 | 2013-11-13 | 人人游戏网络科技发展（上海）有限公司 | Method and device for combining user data information among servers |
| CN105207996A (en) * | 2015-08-18 | 2015-12-30 | 小米科技有限责任公司 | Account merging method and apparatus |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108648092A (en) * | 2018-05-16 | 2018-10-12 | 中国平安人寿保险股份有限公司 | Loss ratio computational methods, device, equipment and computer readable storage medium |
| CN108961078A (en) * | 2018-06-29 | 2018-12-07 | 泰康保险集团股份有限公司 | Insure the method, apparatus storage medium and electronic equipment of family's polymerization |
| CN110825717A (en) * | 2019-10-10 | 2020-02-21 | 厦门市美亚柏科信息股份有限公司 | Data normalization method, device and medium for identity recognition |
| CN110825717B (en) * | 2019-10-10 | 2022-05-20 | 厦门市美亚柏科信息股份有限公司 | Data normalization method, device and medium for identity recognition |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103368992B (en) | Message push method and device | |
| CN106959963A (en) | A kind of data query method, apparatus and system | |
| CN106528275A (en) | Processing method of data tasks and task scheduler | |
| CN103761279B (en) | Method and system for scheduling network crawlers on basis of keyword search | |
| CN110807085B (en) | Fault information query method and device, storage medium and electronic device | |
| CN106251114B (en) | Method and device for realizing approval in application | |
| CN107861967A (en) | A kind of methods, devices and systems of intelligent Matching good friend | |
| CN104021205B (en) | Method and device for establishing microblog index | |
| CN104392171B (en) | A kind of automatic internal memory evidence analysis method based on data association | |
| CN103593371A (en) | Method and device for recommending search keywords | |
| CN103699544B (en) | The method and system of cross-page selection data | |
| CN110597630B (en) | Method and system for processing content resources in distributed system | |
| CN102148805A (en) | Feature matching method and device | |
| CN110245145A (en) | Structure synchronization method and apparatus of the relevant database to Hadoop database | |
| CN107784588A (en) | Insurance user information merging method and device | |
| CN106713273A (en) | Protocol keyword identification method based on lexicographic tree pruning search | |
| CN106033438A (en) | Public sentiment data storage method and server | |
| CN106709805A (en) | Method and system for acquiring user income data | |
| CN105630995A (en) | Method and system for querying credit | |
| CN101645072A (en) | Changed data extracting method realized by being based on Oracle CDC technique | |
| CN104298570B (en) | Data processing method and device | |
| CN106790130B (en) | Message matching method and device | |
| CN107220251A (en) | Generate the method and device of description information | |
| CN107590233A (en) | A kind of file management method and device | |
| CN107220262A (en) | Information processing method and device |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180309 |
|
| RJ01 | Rejection of invention patent application after publication |