CN109299035A - A kind of CHR file management method, system and computer readable storage medium - Google Patents
A kind of CHR file management method, system and computer readable storage medium Download PDFInfo
- Publication number
- CN109299035A CN109299035A CN201810725180.8A CN201810725180A CN109299035A CN 109299035 A CN109299035 A CN 109299035A CN 201810725180 A CN201810725180 A CN 201810725180A CN 109299035 A CN109299035 A CN 109299035A
- Authority
- CN
- China
- Prior art keywords
- file
- chr
- ueid
- snapshot
- enb
- 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.)
- Granted
Links
Abstract
The invention discloses a kind of CHR file management methods: storage management: response CHR file imports request, receives CHR file；By received CHR file import whether time point of the CHR file in UEID memory database and in importing process in real-time detection UEID memory database exceeds preset time period, if so, the CHR file before being located at the CHR document time point is deleted；The received CHR file of institute is imported into UEID document data bank, and is written in MDFS；Update the corresponding UEID disk snapshot file of UEID memory database；Searching and managing: whether response CHR file query requests judge the CHR file in inquiry request in UEID memory database；If so, inquiring corresponding CHR file in UEID memory database and returning to query result；If it is not, then inquiring corresponding CHR file in MDFS and returning to query result.The present invention requires low, low to the requirement of IT technical capability and construction fast hardware environment, can manage the data volume of TB grade 10,000,000,000 records or more.
Description
Technical field
The present invention relates to big data analysis field more particularly to a kind of CHR file management methods, system and computer-readable
Storage medium.
Background technique
Currently, for awareness network quality, providing some foundations after wireless network is built up for the network optimization, being simultaneously
Positioning certain online operation problems, need to record the details of each calling, pass through analysis CHR (Call History
Record, call history) can note abnormalities calls the probability sent, reason etc., such as, it is possible to find wireless signal covering
The number of cell of difference, the number of certain block veneer for causing most of call failure etc..
The data volume of CHR data is huge and extremely complex, and it is very big to analyze offer to CHR to the optimum management of CHR data
Convenience.But although common big data processing platform such as Hadoop/Teladata etc. can also handle CHR data, usually
Such system investments are big, technical threshold is high, the construction period is long, investment return effect is undesirable, especially for medium-sized and small enterprises,
Due to the limitation of itself IT technical capability and economic capability, it is difficult to solve the big data demand of oneself using these platforms.
Summary of the invention
For overcome the deficiencies in the prior art, one of the objects of the present invention is to provide a kind of management method of CHR file,
It requires low, low to the requirement of IT technical capability and construction fast hardware environment, can manage the number of TB grade 10,000,000,000 records or more
According to amount.
The second object of the present invention is to provide a kind of CHR file management system, to hardware environment require it is low, to IT skill
Art Capability Requirement is low and construction is fast, can manage the data volume of TB grade 10,000,000,000 records or more.
The third object of the present invention is to provide a kind of computer readable storage medium, the journey stored in the storage medium
The management to CHR file can be realized when sort run, require low, low to the requirement of IT technical capability and construction fast hardware environment, energy
Enough manage the data volume of TB grade 10,000,000,000 records or more.
An object of the present invention adopts the following technical scheme that realization:
A kind of CHR file management method, comprising the following steps:
Storage management:
It responds CHR (call history) file and imports request, receive CHR file；
The received CHR file of institute is imported in UEID (host ID) memory database and is examined in real time in importing process
Whether the time point for the CHR file surveyed in the UEID memory database exceeds preset time period, if so, will be located at the CHR
CHR file before document time point is deleted；
The received CHR file of institute is imported into UEID document data bank, and is written in MDFS (distributed file system)；
Update the corresponding UEID disk snapshot file of the UEID memory database；
Searching and managing:
CHR file query requests are responded, judge the CHR file in inquiry request whether in UEID memory database；
If so, inquiring corresponding CHR file in the UEID memory database and returning to query result；
If it is not, then inquiring corresponding CHR file in the MDFS and returning to query result.
It is further, described to import institute's received CHR file in UEID memory database specifically:
The received CHR file of institute is grouped according to ENB (evolved base station) and is stored in the corresponding ENB object of each ENB
In；
The CHR file in each ENB object is grouped according to UEID respectively and to be stored in each UEID UEID pairs corresponding
As in.
Further, there are two the UEID disk snapshot file tools, one of UEID disk snapshot is only updated every time
File.
Further, the method for the corresponding UEID disk snapshot file of the UEID memory database is updated are as follows:
A snapshot is created in systems, and thread is written；
After a CHR file process, data import thread and write snapshot signal to snapshot write-in thread transmission；
Snapshot write-in thread receives write snapshot signal after, wait 5 seconds；
If the snapshot write-in thread receives new snapshot signal of writing again in 5 seconds, then waiting shape is reentered
State；
If the snapshot write-in thread does not receive new snapshot signal of writing in 5 seconds, then enters and write snapshot state；
If the snapshot write-in thread receives new snapshot signal of writing during writing snapshot state, judgement is current
Whether the ENB quantity of processing is less than the 80% of sum；
If so, abandoning recent snapshot, wait state is reentered；
If it is not, then continuing to write to recent snapshot.
Further, the time of the CHR file in importing process in UEID memory database described in real-time detection
Whether point exceeds preset time period, if so, the CHR file before being located at the CHR document time point is deleted specifically:
Whether the time point of the CHR file in importing process in UEID memory database described in real-time detection is located at distance
Before 24 hours of current time, if so, the CHR file before being located at the CHR document time point is deleted.
Further, the UEID document data bank is MONGODB database, the CHR text in the MONGODB database
The storage mode of part are as follows: the CHR file of every day of each ENB is stored in a data file.
Further, the snapshot document in the UEID disk snapshot file is grouped according to ENB, the data quilt of each ENB
It is stored in corresponding ENB snapshot document, each ENB snapshot document is stored in correspondence according to the ID of the ENB of the ENB snapshot document
Subdirectory under.
Further, the loading method of the UEID disk snapshot file is on-demand loading mode.
The second object of the present invention adopts the following technical scheme that realization:
A kind of CHR file management system, comprising: memory service end, file service end, UEID memory database, UEID text
Part database, snapshot document storage unit, memory service end query interface and MDFS；
The memory service end is used to import CHR file in the UEID memory database, and the file service end is used
It is imported in the UEID document data bank in by CHR file, the snapshot document storage unit is for storing the UEID memory
The snapshot document of database, the snapshot document storage unit are connect with the UEID memory database, the memory service end
Query interface is connect with the UEID memory database, and the MDFS is connect with the UEID document data bank, and client can lead to
Memory service end query interface is crossed to obtain the CHR file in the UEID memory database and obtain by the MDFS
CHR file in the UEID document data bank.
The third object of the present invention adopts the following technical scheme that realization:
A kind of computer readable storage medium, the computer-readable recording medium storage have executable computer program,
Such as above-mentioned CHR file management method is realized when the computer program is run.
Compared with prior art, the beneficial effects of the present invention are:
The CHR file management method to hardware environment require it is low, to IT technical capability require it is low and can with Fast Construction,
The data volume of TB grade 10,000,000,000 records or more can be managed；CHR file is respectively stored in UEID memory database and UEID
In document data bank, UEID memory database is only saved the data apart from current time in 24 hours, once it detects
CHR file in UEID memory database is more than then automatic to remove for 24 hours apart from current time；When client wants to obtain away from
When from CHR file within current time 24 hours, direct inquiry UEID memory database, and when client wants will obtain
CHR file before 24 hours, then directly loaded from UEID document data bank.
Detailed description of the invention
Fig. 1 is the storage management flow chart in a kind of CHR file management method provided by the invention；
Fig. 2 is the searching and managing flow chart in a kind of CHR file management method provided by the invention；
Fig. 3 is a kind of structural framing figure of CHR file management system provided by the invention, for ease of understanding work of system
Process shows client in figure.
Specific embodiment
In the following, being described further in conjunction with attached drawing and specific embodiment to the present invention, it should be noted that not
Under the premise of conflicting, new implementation can be formed between various embodiments described below or between each technical characteristic in any combination
Example.
It please refers to Fig.1 to Fig.3, a kind of CHR file management method, comprising the following steps:
Storage management:
S11, response CHR (call history) file import request, receive CHR file；
S12, the received CHR file of institute is imported in UEID (host ID) memory database and real in importing process
When detection UEID memory database in time point of CHR file whether exceed preset time period, if so, the CHR will be located at
CHR file before document time point is deleted；In the present embodiment, preset time period is in 24 hours of current time；
S13, the received CHR file of institute is imported into UEID document data bank, and be written in MDFS (distributed file system)；
S14, the corresponding UEID disk snapshot file of UEID memory database is updated；
Searching and managing:
Whether S21, response CHR file query requests, judge the CHR file in inquiry request in UEID memory database
In；
S22, if so, inquiring corresponding CHR file in UEID memory database and returning to query result；
S23, if it is not, then inquiring corresponding CHR file in MDFS and returning to query result.
The CHR file management method to hardware environment require it is low, to IT technical capability require it is low and can with Fast Construction,
The data volume of TB grade 10,000,000,000 records or more can be managed；CHR file is respectively stored in UEID memory database and UEID
In document data bank, UEID memory database is only saved the data apart from current time in 24 hours, once it detects
CHR file in UEID memory database is more than then automatic to remove for 24 hours apart from current time；When client wants to obtain away from
When from CHR file within current time 24 hours, direct inquiry UEID memory database, and when client wants will obtain
CHR file before 24 hours, then directly loaded from UEID document data bank.
In the present embodiment, the service processes resident as one using MME-UEID query service end, will be apart from current
CHR caching in 24 hours time is stored in UEID memory database in memory, pass through the offer pair of WCF query interface
The query service of these CHR data.UEID disk snapshot file provides UEID memory database in complete mirror image sometime,
When server resets, UEID memory database can quickly recover to the newest shape for saving and updating from UEID disk snapshot file
State.
As a preferred embodiment, the received CHR file of institute is imported in UEID memory database specifically:
The received CHR file of institute is grouped according to ENB (evolved base station) and is stored in the corresponding ENB object of each ENB
In；
The CHR file in each ENB object is grouped according to UEID respectively and to be stored in each UEID UEID pairs corresponding
It is as shown in the table as in:
According to the distribution character analysis to CHR, the frequency of UEID duplicate allocation is higher in CHR, it may be assumed that under each ENB
For each difference UEID, averagely have 15 effects daily redistributes record.In this case, all records are pressed
UEID grouping is a kind of optimal institutional framework, and using this structure, the record set that needs to resequence in updating operation can be compared with
It is small, and when being inquired, it can be directly targeted to UEID, then can directly be navigated to accordingly by binary chop
Record.
In the present embodiment, CHR data are all to carry out subregion by ENB first, after data are carried out subregion according to ENB,
The data ensemble average of each ENB subregion only accounts for several a ten thousandths entirely recorded, greatly improves the performance of update and inquiry；
In update and inquiry operation, it usually needs update CHR or need matched MR/ ticket, data itself are organized according to ENB
Together, thus by under the same ENB N number of update or inquiry request be packaged as the update or inquiry request of a batch,
Only need the positioning of an ENB subregion, so that it may complete thousands of updates and inquiry request, further promotion updates and inquiry
Performance；In addition, after update or inquiry request are packaged progress batch processing by ENB, the lock between update and inquiry operation
Fixed operation, can promote the locking of ENB rank, this is the moderate lock granularity of a scale, than the lock for recording rank, need into
Capable lock number of operations is less, and lock operation will lack several orders of magnitude to the occupancy of memory, and the lock relative to library rank, then provides
Higher concurrency, read-write operation can concurrently carry out on different ENB.
Due to the daily data volume of each ENB be it is uncertain, the size of each ENB record array also can not be prior
It determines, can only be dynamically distributed and be adjusted according to real data.According to data statistics, each ENB daily data volume is average
5000, therefore, in the present embodiment, the record array of each ENB is radix with 512, when array size is not enough to save 24
When the data of hour, 512 elements of capacity extension of array.
As a preferred embodiment, only updating one of them every time there are two UEID disk snapshot file tools
UEID disk snapshot file.The process for writing snapshot is a prolonged operation, and in this process, service processes may malfunction
Or be terminated, to leave an incomplete snapshot on disk, it is clear that cannot allow such a incomplete snapshot shadow
Ring server resets hereafter.Therefore, during writing snapshot, a complete snapshot should be also maintain on disk, if
Snapshot failure is specifically write, then starting will use previous complete snapshot next time.So actually being maintained always in system
Two snapshots, wherein at least one be complete snapshot.
We distinguish the two snapshots with two different directory names: X, Y are here by SNAPSHOT-X, SNAPSORT-Y
Two numbers indicate that the version of snapshot, two numbers are continuous such as (1,2).Assume first that the two catalogues are constantly present
(for the first time operation a snapshot can be first created with historical data, then replicate portion become two snapshots), it is assumed that be
Small that of label is always written when snapshot is written in SNAPSHOT-1, SNAPSORT-2, i.e. in SNAPSHOT-1,
After being written successfully, its directory name is revised as SNAPSHOT-3.It is an atomic operation since catalogue renames, once
Catalogue is renamed as SNAPSHOT-3, then indicating that write operation is completely completed.Service starting when, always only from
Data are read in that big snapshot of label, therefore, if SNAPSHOT-1 write-in failure, snapshot (SNAPSHOT-1,
SNAPSORT-2 SNAPSORT-2 is still complete snapshot in), otherwise two snapshots should be (SNAPSHOT-2,
SNAPSORT-3), wherein SNAPSORT-3 is newest complete snapshot.
The frequency of snapshot write-in, which is that a needs are balanced, to be considered the problems of, on the one hand, after server resets, even if from snapshot
It can be restored to state when creation snapshot, but subsequent data file to be imported to processing again once from the moment, because
This, it is clear that snapshot update must be more frequent, and the file left after snapshot is fewer, and the data processing and state after server resets are just
More reliable, but then, each updating decision is also according to the IO expense for requiring 10GB, influence of this expense for server
It can not despise.
The update of internal storage data is as unit of CHR original record file, therefore, it is not necessary in a CHR file
Updating decision is gone to shine during processing, it, theoretically should be immediately after the record of a CHR file is all updated to memory
A snapshot is created, in this way after the service of restarting, does not need to reprocess this CHR file and the file before it.But
CHR file is also likely to be Batch Arrival, several CHR files disposably may be reached in minutes, if each text
Part handled after all create snapshot, it is clear that as soon as and it is inappropriate --- a snapshot is just created, may at once failure
?.
The above several points are comprehensively considered, as a preferred embodiment, plan is written using a balanced snapshot in system
Slightly, specific as follows:
A snapshot is created in systems, thread is written, and maintain the snapshot that thread is written always, be at waiting shape
State waits snapshot signal to be written；
After a CHR file process, data import thread and write snapshot signal to snapshot write-in thread transmission；
Snapshot write-in thread receives write snapshot signal after, wait 5 seconds；
If snapshot write-in thread receives new snapshot signal of writing again in 5 seconds, then previous signal is abandoned, again
Into wait state；
If snapshot write-in thread does not receive new snapshot signal of writing, then enters and write snapshot state in 5 seconds, start by
A processing ENB, writes snapshot；
If snapshot write-in thread received during writing snapshot state it is new write snapshot signal, judge current processed
ENB quantity whether be less than sum 80%；
If so, abandoning recent snapshot, wait state is reentered, the processing of this batch file is waited to complete；
If it is not, then continuing to write to recent snapshot.
In addition, at no point in the update process, data import thread when updating some ENB data, thread is written to snapshot first
Its state is inquired, if snapshot write-in thread is writing snapshot state: if write-in shape is exited in snapshot write-in thread statement
State then updates the ENB data, after the ENB snapshot is otherwise written, then updates the ENB data.Such case is generally present in batch
It, can for the snapshot write-in processed ENB of thread in renewal process and when snapshot write-in a part of ENB of thread have processed
Directly update.
As a preferred embodiment, the CHR file in importing process in real-time detection UEID memory database
Time point whether exceed preset time period, if so, the CHR file before being located at the CHR document time point is deleted specific
Are as follows:
It is current whether the time point of the CHR file in importing process in real-time detection UEID memory database is located at distance
Before 24 hours of time, if so, the CHR file before being located at the CHR document time point is deleted.
In the present embodiment, UEID memory database will at least preserve 24 hour records.Such as some UEID has now
So two records T0=23:50, T1=02:30.Inquiry if deleting this record of T0, before 02:30
It will all match less than as a result, this is clearly inappropriate.It can be seen that " at least 24 hour records " from this example actually to answer
This refers to " to the time T fallen within 24 hours, guaranteeing to inquire definitive result ".From this example it can also be seen that such as
Fruit T1 is before 24 hours, then T0 can be removed, will be unable to guarantee inquiry after otherwise rejecting T0.So carrying out more
When new operation, it is necessary first to be ranked up next time point (out-of-service time T1) that record is recorded according to every.Often
When an additional record, the smallest T1 in existing record is detected, if T1 before 24 hours, can reject this note
Record does not need to carry out dilatation to array；If T1, within 24 hours, array off-capacity accommodates updated data, then right
Array carries out dilatation.
Due to during being updated operation, needing constantly to detect and reject the smallest T1, therefore we use
One small top pile structure is ranked up T1.About 5% data volume is only related to due to updating operation every time and uses small top heap knot
Structure can effectively improve the performance of update.
Further, since needing to be ranked up record by T1 in updating operation, and the sortord during inquiry
It is entirely different, and only have one in the entire system and update concurrently, therefore be not necessarily to carry out original place update, it is updating every time
In the process, all it is that former data are copied to more new district first to handle, is copied on ENB again after the completion of updating.In this way whole
In a renewal process, write operation just only is carried out to ENB in the ENB stage that copies back into later, also subtracts the time of write operation
Minimum has been arrived less, also reduces the Read-Write Locks collision probability on ENB.
As a preferred embodiment, UEID document data bank is MONGODB database, in MONGODB database
CHR file storage mode are as follows: the CHR file of every day of each ENB is stored in a data file.In order to right
Data before a couple of days are inquired, it is necessary to these data are stored in the file of persistence, when client needs to inquire data
When, it directly inquires data from load of file to the memory headroom of oneself.In view of inquiring client terminal may divide
On any one server, these data files should be able to be accessed cloth from a server, these files are stored in
It is proper in MONGODB database.Since inquiry operation is usually as unit of ENB, and in the case where filling mining,
A small number of several ENB may usually be only related to.Therefore, external data file is proper as unit of ENB days, i.e., will
One ENB, mono- day data organization is in a data file.Every month ten thousand data files of about 30,000 * 30=100.It is average
Each file about 5000 records, every record save (MME-UID, T, IMSI, MDN) 4 32 bytes of field, i.e., each text
Part is averaged 160KB, even if data volume 11-fold increase, daily file only 2MB.
As a preferred embodiment, the snapshot document in UEID disk snapshot file is grouped according to ENB, each
The data of ENB are saved in corresponding ENB snapshot document, and each ENB snapshot document is according to the ENB's of the ENB snapshot document
ID is stored under corresponding subdirectory.Since the ENB quantity for including in system is up to tens of thousands of, we cannot be by all ENB snapshots
File is placed under a catalogue, otherwise due under catalogue file will largely effect on IO performance too much.Therefore, ENB snapshot document quilt
It is dispersed under 100 subdirectories of 00-99, determines that the snapshot document of an ENB answers corresponding specific item according to the ID%100 of ENB
Record.
As a preferred embodiment, the loading method of UEID disk snapshot file is on-demand loading mode.In order to
It can start offer service immediately after server resets, it is clear that entire snapshot cannot be waited to be loaded into memory, therefore,
The load of snapshot must just load data, and every time only by the way of on-demand loading, i.e., when needing to use data
Very small part data are loaded, during the load of entire snapshot is distributed to a large amount of on-demand loading in this way, although adding every time
Load needs to wait a bit of time (< 1s), but client withouts waiting for several minutes as long as.
Referring to Fig. 3, the present invention also provides a kind of CHR file management systems, comprising: memory service end, file service
End, UEID memory database, UEID document data bank, snapshot document storage unit, memory service end query interface and MDFS；
Memory service end is used to import CHR file in UEID memory database, and file service end is for leading CHR file
Enter in UEID document data bank, snapshot document storage unit is used to store the snapshot document of UEID memory database, snapshot document
Storage unit is connect with UEID memory database, and memory service end query interface is connect with UEID memory database, MDFS with
The connection of UEID document data bank, client can obtain the CHR text in UEID memory database by memory service end query interface
Part and pass through MDFS obtain UEID document data bank in CHR file.
Storage is accounted for up to 10-20GB due to UEID disk snapshot file, for improve the write-in of snapshot and from snapshot it is quick
The performance of recovery, snapshot document storage unit use SSD (solid state hard disk).
In addition, the present invention also provides a kind of computer readable storage medium, the computer-readable recording medium storage
There is executable computer program, such as above-mentioned CHR file management method is realized when the computer program is run.
The above embodiment is only the preferred embodiment of the present invention, and the scope of protection of the present invention is not limited thereto,
The variation and replacement for any unsubstantiality that those skilled in the art is done on the basis of the present invention belong to institute of the present invention
Claimed range.
Claims (10)
1. a kind of CHR file management method, which comprises the following steps:
Storage management:
It responds CHR file and imports request, receive CHR file；
The received CHR file of institute is imported in UEID memory database and the UEID memory described in real-time detection in importing process
Whether the time point of the CHR file in database exceeds preset time period, if so, will be located at before the CHR document time point
CHR file delete；
The received CHR file of institute is imported into UEID document data bank, and is written in MDFS；
Update the corresponding UEID disk snapshot file of the UEID memory database；
Searching and managing:
CHR file query requests are responded, judge the CHR file in inquiry request whether in the UEID memory database；
If so, inquiring corresponding CHR file in the UEID memory database and returning to query result；
If it is not, then inquiring corresponding CHR file in the MDFS and returning to query result.
2. CHR file management method as described in claim 1, which is characterized in that described to import the received CHR file of institute
In UEID memory database specifically:
The received CHR file of institute is grouped according to ENB and is stored in the corresponding ENB object of each ENB；
The CHR file in each ENB object is grouped according to UEID respectively and is stored in the corresponding UEID object of each UEID.
3. CHR file management method as described in claim 1, which is characterized in that the UEID disk snapshot file has two
It is a, one of UEID disk snapshot file is only updated every time.
4. CHR file management method as described in claim 1, which is characterized in that it is corresponding to update the UEID memory database
UEID disk snapshot file method are as follows:
A snapshot is created in systems, and thread is written；
After a CHR file process, data import thread and write snapshot signal to snapshot write-in thread transmission；
Snapshot write-in thread receives write snapshot signal after, wait 5 seconds；
If the snapshot write-in thread receives new snapshot signal of writing again in 5 seconds, then wait state is reentered；
If the snapshot write-in thread does not receive new snapshot signal of writing in 5 seconds, then enters and write snapshot state；
If snapshot write-in thread received during writing snapshot state it is new write snapshot signal, judge current processed
ENB quantity whether be less than sum 80%；
If so, abandoning recent snapshot, wait state is reentered；
If it is not, then continuing to write to recent snapshot.
5. CHR file management method as described in claim 1, which is characterized in that the institute of the real-time detection in importing process
Whether the time point for stating the CHR file in UEID memory database exceeds preset time period, if so, will be located at the CHR file
CHR file before time point is deleted specifically:
It is current whether the time point of the CHR file in importing process in UEID memory database described in real-time detection is located at distance
Before 24 hours of time, if so, the CHR file before being located at the CHR document time point is deleted.
6. CHR file management method as described in claim 1, which is characterized in that the UEID document data bank is MONGODB
Database, the storage mode of the CHR file in the MONGODB database are as follows: the CHR file of every day of each ENB stores
In a data file.
7. CHR file management method as described in claim 1, which is characterized in that fast in the UEID disk snapshot file
It is grouped according to file according to ENB, the data of each ENB are saved in corresponding ENB snapshot document, each ENB snapshot document root
It is stored under corresponding subdirectory according to the ID of the ENB of the ENB snapshot document.
8. CHR file management method as claimed in claim 7, which is characterized in that the load of the UEID disk snapshot file
Mode is on-demand loading mode.
9. a kind of CHR file management system characterized by comprising memory service end, file service end, UEID internal storage data
Library, UEID document data bank, snapshot document storage unit, memory service end query interface and MDFS；
The memory service end is used to import CHR file in the UEID memory database, and the file service end is used for will
CHR file imports in the UEID document data bank, and the snapshot document storage unit is for storing the UEID internal storage data
The snapshot document in library, the snapshot document storage unit are connect with the UEID memory database, the memory service end inquiry
Interface is connect with the UEID memory database, and the MDFS is connect with the UEID document data bank, and client can pass through institute
Memory service end query interface is stated to obtain the CHR file in the UEID memory database and pass through described in MDFS acquisition
CHR file in UEID document data bank.
10. a kind of computer readable storage medium, which is characterized in that the computer-readable recording medium storage has executable meter
Calculation machine program, the computer program realize CHR file management method as claimed in any one of claims 1 to 8 when running.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810725180.8A CN109299035B (en) | 2018-07-04 | 2018-07-04 | CHR file management method, system and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810725180.8A CN109299035B (en) | 2018-07-04 | 2018-07-04 | CHR file management method, system and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109299035A true CN109299035A (en) | 2019-02-01 |
| CN109299035B CN109299035B (en) | 2021-10-15 |
Family
ID=65167840
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810725180.8A Active CN109299035B (en) | 2018-07-04 | 2018-07-04 | CHR file management method, system and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109299035B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110297673A (en) * | 2019-06-20 | 2019-10-01 | 福建天泉教育科技有限公司 | The method of internal storage data Optimized loading, storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101196852A (en) * | 2008-01-03 | 2008-06-11 | 杭州华三通信技术有限公司 | Distributed caching method and system, caching equipment and non-caching equipment |
| CN101231642A (en) * | 2007-08-27 | 2008-07-30 | 中国测绘科学研究院 | Space-time database administration method and system |
| CN102073739A (en) * | 2011-01-25 | 2011-05-25 | 中国科学院计算技术研究所 | Method for reading and writing data in distributed file system with snapshot function |
| JP2011151620A (en) * | 2010-01-21 | 2011-08-04 | Sumitomo Mitsui Banking Corp | Inter-base telephone call taking-over system and method for the same |
| CN103020236A (en) * | 2012-12-15 | 2013-04-03 | 安科智慧城市技术（中国）有限公司 | Method, system and distributed database system for retrieving recorded video |
| US20140074854A1 (en) * | 2010-06-08 | 2014-03-13 | Google Inc. | Scalable rendering of large spatial databases |
| CN104317926A (en) * | 2014-10-31 | 2015-01-28 | 北京思特奇信息技术股份有限公司 | Persistent data storage method, persistent data query method, persistent data storage device and persistent data query system |
| CN105718484A (en) * | 2014-12-04 | 2016-06-29 | 中兴通讯股份有限公司 | File writing method, file reading method, file deletion method, file query method and client |
| CN106339860A (en) * | 2016-09-05 | 2017-01-18 | 南京简睿捷软件开发有限公司 | Enterprise internal call response management system and management method |
| CN106934001A (en) * | 2017-03-03 | 2017-07-07 | 广州天源迪科信息技术有限公司 | Distributed quick inventory inquiry system and method |
| CN107071005A (en) * | 2017-03-24 | 2017-08-18 | 厦门中控生物识别信息技术有限公司 | A kind of method of data synchronization and system |
| US20170302791A1 (en) * | 2007-03-30 | 2017-10-19 | Mattersight Corporation | System and methods for routing a telephonic communication |
| CN107911565A (en) * | 2017-11-02 | 2018-04-13 | 平安科技（深圳）有限公司 | Calling-control method, terminal, equipment and computer-readable recording medium |
-
2018
- 2018-07-04 CN CN201810725180.8A patent/CN109299035B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170302791A1 (en) * | 2007-03-30 | 2017-10-19 | Mattersight Corporation | System and methods for routing a telephonic communication |
| CN101231642A (en) * | 2007-08-27 | 2008-07-30 | 中国测绘科学研究院 | Space-time database administration method and system |
| CN101196852A (en) * | 2008-01-03 | 2008-06-11 | 杭州华三通信技术有限公司 | Distributed caching method and system, caching equipment and non-caching equipment |
| JP2011151620A (en) * | 2010-01-21 | 2011-08-04 | Sumitomo Mitsui Banking Corp | Inter-base telephone call taking-over system and method for the same |
| US20140074854A1 (en) * | 2010-06-08 | 2014-03-13 | Google Inc. | Scalable rendering of large spatial databases |
| CN102073739A (en) * | 2011-01-25 | 2011-05-25 | 中国科学院计算技术研究所 | Method for reading and writing data in distributed file system with snapshot function |
| CN103020236A (en) * | 2012-12-15 | 2013-04-03 | 安科智慧城市技术（中国）有限公司 | Method, system and distributed database system for retrieving recorded video |
| CN104317926A (en) * | 2014-10-31 | 2015-01-28 | 北京思特奇信息技术股份有限公司 | Persistent data storage method, persistent data query method, persistent data storage device and persistent data query system |
| CN105718484A (en) * | 2014-12-04 | 2016-06-29 | 中兴通讯股份有限公司 | File writing method, file reading method, file deletion method, file query method and client |
| CN106339860A (en) * | 2016-09-05 | 2017-01-18 | 南京简睿捷软件开发有限公司 | Enterprise internal call response management system and management method |
| CN106934001A (en) * | 2017-03-03 | 2017-07-07 | 广州天源迪科信息技术有限公司 | Distributed quick inventory inquiry system and method |
| CN107071005A (en) * | 2017-03-24 | 2017-08-18 | 厦门中控生物识别信息技术有限公司 | A kind of method of data synchronization and system |
| CN107911565A (en) * | 2017-11-02 | 2018-04-13 | 平安科技（深圳）有限公司 | Calling-control method, terminal, equipment and computer-readable recording medium |
Non-Patent Citations (2)
| Title |
|---|
| LEI XU 等: "VSFS: A Searchable Distributed File System", 《IEEE》 * |
| 陈栋波: "基于HBase的海量小文件管理系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110297673A (en) * | 2019-06-20 | 2019-10-01 | 福建天泉教育科技有限公司 | The method of internal storage data Optimized loading, storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109299035B (en) | 2021-10-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101956236B1 (en) | Data replication technique in database management system | |
| Lampson et al. | A new presumed commit optimization for two phase commit | |
| US11520772B2 (en) | Tracking change data in a database | |
| US9542424B2 (en) | Lifecycle-based horizontal partitioning | |
| CN102629247B (en) | Method, device and system for data processing | |
| US6772177B2 (en) | System and method for parallelizing file archival and retrieval | |
| US9672241B2 (en) | Representing an outlier value in a non-nullable column as null in metadata | |
| US20070185912A1 (en) | Off-loading I/O and computationally intensive operations to secondary systems | |
| US20070088912A1 (en) | Method and system for log structured relational database objects | |
| US20140101167A1 (en) | Creation of Inverted Index System, and Data Processing Method and Apparatus | |
| CN104239377A (en) | Platform-crossing data retrieval method and device | |
| US10671641B1 (en) | Method and computer program product for efficiently loading and synchronizing column-oriented databases | |
| US20140181059A1 (en) | Batching content management operations to facilitate efficient database interactions | |
| US20170329836A1 (en) | Database transfer of changes | |
| WO2010077549A2 (en) | Data integrity in a database environment through background synchronization | |
| CN110309233A (en) | Method, apparatus, server and the storage medium of data storage | |
| US20210271660A1 (en) | Method For Implementing Change Data Capture In Database Management System | |
| CN107273449B (en) | Breakpoint processing method and system based on memory database | |
| CN106649530B (en) | Cloud detail query management system and method | |
| CN111538699A (en) | Data archiving method and device | |
| US11150964B1 (en) | Sequential processing of changes in a distributed system | |
| CN109299035A (en) | A kind of CHR file management method, system and computer readable storage medium | |
| US7275065B2 (en) | Method and system for supporting per-user-per-row read/unread tracking for relational databases | |
| US20070118574A1 (en) | Reorganizing data with update activity | |
| US20210318834A1 (en) | Distributed Storage Orphan Scan |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |