WO2017032240A1 - 移动终端的数据存储方法和装置 - Google Patents

移动终端的数据存储方法和装置 Download PDF

Info

Publication number
WO2017032240A1
WO2017032240A1 PCT/CN2016/095520 CN2016095520W WO2017032240A1 WO 2017032240 A1 WO2017032240 A1 WO 2017032240A1 CN 2016095520 W CN2016095520 W CN 2016095520W WO 2017032240 A1 WO2017032240 A1 WO 2017032240A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
metadata
cache
key value
database
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/095520
Other languages
English (en)
French (fr)
Chinese (zh)
Inventor
廉洁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to EP16838499.8A priority Critical patent/EP3343395B1/en
Priority to ES16838499T priority patent/ES2812771T3/es
Priority to PL16838499T priority patent/PL3343395T3/pl
Priority to JP2018510513A priority patent/JP6788002B2/ja
Publication of WO2017032240A1 publication Critical patent/WO2017032240A1/zh
Priority to US15/903,995 priority patent/US10776323B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/178—Techniques for file synchronisation in file systems
    • G06F16/1794—Details of file format conversion
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G06F16/116—Details of conversion of file system types or formats
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06F16/2228—Indexing structures
    • G06F16/2272—Management thereof
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/31—Indexing; Data structures therefor; Storage structures
    • G06F16/316—Indexing structures
    • G06F16/325—Hash tables
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/41—Indexing; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/908—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content

Definitions

  • the present application relates to the field of storage technologies, and in particular, to a data storage method and apparatus for a mobile terminal.
  • the present application provides a data storage method and apparatus.
  • a data storage method for a mobile terminal comprising:
  • the first data in the cache that has not been stored in the database, the first metadata of the first data, and the key value of the first data are saved in the database.
  • the determining, according to the correspondence between the key value and the metadata saved in the cache, whether the first data is stored in the database includes:
  • it also includes:
  • the determining whether the second metadata is the same as the first metadata includes:
  • the preset triggering condition includes: reaching a preset time period and the buffered data amount reaches a preset threshold.
  • it also includes:
  • the first data corresponding to the key value is obtained from the database according to the metadata corresponding to the key value saved in the cache;
  • the first data is converted into original data and the read result is returned.
  • a data storage device for a mobile terminal comprising:
  • a first converting unit performing format conversion on the original data to obtain first data in a preset format
  • a metadata creation unit that creates first metadata of the first data
  • the storage judging unit judges whether the first data is stored in the database according to the correspondence between the key value and the metadata stored in the cache;
  • a data cache unit when the first data is not stored in the database, saving the first data, the first metadata of the first data, and the key value of the first data into a cache;
  • the data storage unit saves the first data of the first data, the first metadata of the first data, and the first data in the cache to the database when the preset trigger condition is met.
  • the storage determining unit determines, according to the key value of the first data, whether the second metadata corresponding to the key value is saved in the cache, and if the cache does not save the second corresponding to the key value
  • the metadata determines that the first data is not stored in the database.
  • the storage determining unit when the second metadata corresponding to the key value is saved in the cache, determining whether the second metadata is the same as the first metadata, if the second The metadata is different from the first metadata, and it is determined that the first data is not stored in the database;
  • the data cache unit specifically updates the second metadata corresponding to the key value of the first data stored in the cache to the first metadata, and saves the first data.
  • the storage determining unit specifically determines whether the hash value of the second metadata is the same as the hash value of the first metadata, and if the same, confirms the second metadata and the The first metadata is the same; if not, it is confirmed that the second metadata is different from the first metadata.
  • the preset triggering condition includes: reaching a preset time period and the buffered data amount reaches a preset threshold.
  • the device further includes:
  • the first reading unit searches for a corresponding first data in the cache according to the key value when reading the data
  • a second reading unit when the first data corresponding to the key value is not saved in the cache, acquiring the first data corresponding to the key value from the database according to the metadata corresponding to the key value saved in the cache;
  • the second conversion unit returns the read result after converting the first data into original data.
  • the present application can convert the original data into data in a preset format.
  • Storage in a non-relational database based on Key-Value can eliminate structural differences in data, improve data compatibility, and improve data read and write efficiency.
  • FIG. 1 is a schematic flowchart diagram of a data storage method of a mobile terminal according to an exemplary embodiment of the present application.
  • FIG. 2 is a schematic flow chart of determining whether a first data is stored in a database according to an exemplary embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a mobile terminal according to an exemplary embodiment.
  • FIG. 4 is a schematic structural diagram of a data storage device of a mobile terminal according to an exemplary embodiment of the present application.
  • first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • the word “if” may be interpreted to mean “when” or “when” or “in response to a determination.”
  • FIG. 1 is a schematic flowchart diagram of a data storage method of a mobile terminal according to an exemplary embodiment of the present application.
  • the data storage method may be applied to a mobile terminal, and the terminal may include a smart device such as a smart phone, a tablet computer, or a PDA (Personal Digital Assistant).
  • the data storage method may include the following steps:
  • Step 101 Perform format conversion on the original data to obtain first data in a preset format.
  • the original data is data that needs to be stored in a local database of the mobile terminal, and the original data includes data, such as news, list, information, and the like, which are cached locally by each application.
  • the format of the original data may be a text format, an XML format, or the like.
  • the mobile terminal After receiving the original data that needs to be stored, the mobile terminal performs format conversion on the original data and converts the original data into data in a preset format, and the preset format may be set by an administrator, for example: Binary, decimal, etc.
  • the preset format may be set by an administrator, for example: Binary, decimal, etc.
  • data obtained by format conversion of original data is referred to as first data.
  • Step 102 Create first metadata of the first data.
  • the mobile terminal creates metadata of the first data after converting the original data into the first data.
  • the created metadata of the first data is referred to as a first Metadata.
  • Step 103 Determine, according to the correspondence between the key value and the metadata stored in the cache, whether the first data is stored in the database. If the first data is not stored in the database, step 104 is performed.
  • a non-relational database based on Key-Value storage may be used as an underlying storage medium of the mobile terminal, and the non-relational database includes each original data format converted.
  • the correspondence between each piece of first metadata and its key value in the non-relational database is stored in the cache of the mobile terminal.
  • the first metadata saved in the cache is referred to as being convenient for distinguishing.
  • Second metadata Specifically, the mobile terminal may save the correspondence between each piece of the first metadata and its key value in the non-relational database (hereinafter referred to as the database) to the cache after restarting, for example, memory.
  • the mobile terminal may also, after receiving the original data that needs to be stored in the database, if it is determined that the original data after the format conversion is not stored in the database, that is, the first data in the database is not stored in the database,
  • the first metadata corresponding to the original data and its key value are saved to the cache, and the specific implementation process can be seen in the following description.
  • the mobile terminal may determine, according to the key value of the first data and the correspondence between the key value and the metadata stored in the cache, whether the first data is already stored in the database.
  • the key value of the first data is also the key value of the original data.
  • determining whether the first data is stored in the data may include the following steps:
  • Step 1031 Determine, according to the key value of the first data, whether the second metadata corresponding to the key value is saved in the cache. If the second metadata corresponding to the key value is saved in the cache, step 1032 is executed. If the second metadata corresponding to the key value is not saved in the cache, step 1033 is performed.
  • Step 1032 Determine whether the second metadata is the same as the first metadata. If the second metadata is different from the first metadata, step 1033 is performed, and if the second metadata is the same as the first metadata, step 1034 is performed.
  • the second metadata corresponding to the key value is stored in the cache, the first data corresponding to the key value is stored in the bottom database, but the first data cannot be known. Whether it is the first data of the latest version, so in this step, it can be determined whether the second metadata is the same as the created first metadata.
  • the second metadata may be determined whether the second metadata is identical to the first metadata by comparing the second metadata with each byte of the first metadata.
  • the second metadata includes a hash value corresponding to the first data stored in the database, and in this step, the first data may be calculated according to the first data converted in the foregoing step 101.
  • step 1033 is performed; if the same, the second metadata is determined to be the same as the first metadata, and step 1034 is performed.
  • Step 1033 determining that the first data is not stored in the database.
  • the second metadata corresponding to the key value is not saved in the cache, it may be determined that the first data is not stored in the database.
  • the second metadata is different from the first metadata
  • the first data is converted in the foregoing step 101.
  • the obtained first data is different, so the metadata of the two is different, which may be because the first data stored in the data is not the latest data and needs to be updated, so it is also determined that there is no storage in the database at this time.
  • the first data obtained by the conversion in the foregoing step 101.
  • Step 1034 determining that the first data has been stored in the database.
  • the mobile terminal may delete the original data received in the foregoing step 101, the converted first data, and the first metadata created in the foregoing step 102.
  • Step 104 Save the first data, the first metadata of the first data, and the key value of the first data into a cache.
  • the first data if the first data is not stored in the database, the first data needs to be stored in the database.
  • the first data, the first metadata of the first data, and the key value of the first data may be first saved in a cache.
  • the mobile terminal may first use the first data, the first metadata of the first data, and the The key value of the first data is saved to the cache and marked as not stored.
  • the mobile terminal may set, for the entire data of the first data, the first metadata of the first data, and the key value of the first data, a flag for marking a storage state, for example, a flag bit.
  • a value of 0 indicates no storage, and a flag of 1 indicates storage.
  • the mobile terminal may also set a key value list, and store the key value of the first data that is not stored in the data into the key value list.
  • those skilled in the art may also use other methods to mark whether the data saved in the cache has been It is stored in the database, and this application does not specifically limit this.
  • the second metadata corresponding to the key value of the first data is saved in the cache, but the second metadata is different from the first metadata of the first data.
  • the first data in which the same key value is stored in the database is described, but the first data is not the latest first data and needs to be updated.
  • the mobile terminal may update the second metadata corresponding to the key value of the first data stored in the cache to the first metadata, and save the first data, so that a cache is saved in the cache for a key value. Metadata.
  • the updated data is also marked as not stored.
  • step 105 when the preset trigger condition is met, the first data in the cache that has not been stored in the database, the first metadata of the first data, and the key value of the first data are saved in the database.
  • the mobile terminal may save the first data of the first data, the first metadata of the first data, and the first data that are not stored in the database in the database to the database when the preset trigger condition is met. That is, the data marked as unsaved in the cache is stored in the database.
  • the triggering condition may be set by an administrator.
  • the triggering condition may be that a preset time period is reached, and the triggering condition may also be that the buffered data amount reaches a preset threshold.
  • the present application can convert the original data into a preset format data and store it in a Key-Value based non-relational database, which can eliminate data structural differences, improve data compatibility, and read and write data. s efficiency.
  • the mobile terminal may further store the first data with a higher read frequency into the cache to improve the read efficiency. Therefore, when receiving the data read command, the mobile terminal may first search for a corresponding first data in the cache according to the key value carried in the read command, and when the corresponding first data is saved in the cache, The first data in the cache is converted in the opposite format, converted to the original data and returned to the read result.
  • the metadata corresponding to the key value saved in the cache (second metadata) may be first searched, and then the key is obtained from the database according to the metadata. The first data corresponding to the value is then subjected to the reverse format conversion of the obtained first data, and converted to the original data to return the read result.
  • the mobile terminal deletes the first data saved in the cache when the preset condition is met.
  • the first data saved in the cache may be deleted periodically, or the read frequency of the first data may be less than
  • the first data saved in the cache is deleted when the threshold is used, and the present application does not specifically limit this.
  • the data storage solution provided by the present application may also support encrypted storage.
  • the first data may be encrypted and stored.
  • the mobile terminal decrypts the first data, and then converts the original data into a raw data to return a read result.
  • the present application also provides an embodiment of a data storage device of the mobile terminal.
  • Embodiments of the data storage device of the mobile terminal of the present application can be applied to a mobile terminal.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software.
  • the processor of the mobile terminal in which the mobile terminal is located reads the corresponding computer program instructions in the non-volatile memory into the memory.
  • FIG. 3 is a hardware structure diagram of a mobile terminal where the data storage device of the present application is located, except for the processor, the memory, the network interface, and the non-volatile memory shown in FIG.
  • the mobile terminal where the device is located in the embodiment may also include other hardware according to the actual function of the mobile terminal, and details are not described herein.
  • FIG. 4 is a schematic structural diagram of a data storage device of a mobile terminal according to an exemplary embodiment of the present application.
  • the data storage device 300 of the mobile terminal may include: a first converting unit 301, a metadata creating unit 302, a storage determining unit 303, a data buffering unit 304, a data storage unit 305, and a first reading unit 306.
  • the first converting unit 301 performs format conversion on the original data to obtain first data in a preset format.
  • the metadata creation unit 302 creates first metadata of the first data
  • the storage determining unit 303 determines whether the first data is stored in the database according to the correspondence between the key value and the metadata stored in the cache;
  • the data buffering unit 304 saves the first data, the first metadata of the first data, and the key value of the first data to the cache when the first data is not stored in the database;
  • the data storage unit 305 saves the first data of the first data, the first metadata of the first data, and the first data that are not stored in the database in the database to the database when the preset trigger condition is met.
  • the storage determining unit 303 determines, according to the key value of the first data, whether the second metadata corresponding to the key value is stored in the cache, and if the cache does not save the corresponding key value Binary data, it is determined that the first data is not stored in the database.
  • the storage determining unit 303 determines, when the second metadata corresponding to the key value is stored in the cache, whether the second metadata is the same as the first metadata, if the first The binary data is different from the first metadata, and determining that the first data is not stored in the database;
  • the data cache unit 304 specifically updates the second metadata corresponding to the key value of the first data stored in the cache to the first metadata, and saves the first data.
  • the storage determining unit 303 is configured to determine whether the hash value of the second metadata is the same as the hash value of the first metadata, and if the same, confirm the second metadata and the The first metadata is the same; if not, it is confirmed that the second metadata is different from the first metadata.
  • the preset triggering condition includes: reaching a preset time period and the buffered data amount reaches a preset threshold.
  • the first reading unit 306 searches for a corresponding first data in the cache according to the key value when reading the data;
  • the second reading unit 307 when the first data corresponding to the key value is not saved in the cache, obtain the first corresponding to the key value from the database according to the metadata corresponding to the key value saved in the cache. data;
  • the second converting unit 308 returns the read result after converting the first data into original data.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Software Systems (AREA)
  • Multimedia (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Telephone Function (AREA)
PCT/CN2016/095520 2015-08-24 2016-08-16 移动终端的数据存储方法和装置 Ceased WO2017032240A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP16838499.8A EP3343395B1 (en) 2015-08-24 2016-08-16 Data storage method and apparatus for mobile terminal
ES16838499T ES2812771T3 (es) 2015-08-24 2016-08-16 Método y aparato de almacenamiento de datos para terminal móvil
PL16838499T PL3343395T3 (pl) 2015-08-24 2016-08-16 Sposób i urządzenie do przechowywania danych w terminalu mobilnym
JP2018510513A JP6788002B2 (ja) 2015-08-24 2016-08-16 モバイル端末のためのデータ記憶方法及び装置
US15/903,995 US10776323B2 (en) 2015-08-24 2018-02-23 Data storage for mobile terminals

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510524667.6 2015-08-24
CN201510524667.6A CN106484691B (zh) 2015-08-24 2015-08-24 移动终端的数据存储方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/903,995 Continuation US10776323B2 (en) 2015-08-24 2018-02-23 Data storage for mobile terminals

Publications (1)

Publication Number Publication Date
WO2017032240A1 true WO2017032240A1 (zh) 2017-03-02

Family

ID=58099597

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/095520 Ceased WO2017032240A1 (zh) 2015-08-24 2016-08-16 移动终端的数据存储方法和装置

Country Status (7)

Country Link
US (1) US10776323B2 (enExample)
EP (1) EP3343395B1 (enExample)
JP (1) JP6788002B2 (enExample)
CN (1) CN106484691B (enExample)
ES (1) ES2812771T3 (enExample)
PL (1) PL3343395T3 (enExample)
WO (1) WO2017032240A1 (enExample)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108197324B (zh) * 2018-02-06 2021-07-16 百度在线网络技术（北京）有限公司 用于存储数据的方法和装置
FR3081238A1 (fr) * 2018-05-17 2019-11-22 Amadeus S.A.S. Mise en memoire cache de base de donnees
CN110262329B (zh) * 2019-06-11 2021-12-14 华强方特文化科技集团股份有限公司 载人设备数据采集系统及数据格式化存储方法
US11449430B2 (en) * 2020-04-02 2022-09-20 Samsung Electronics Co., Ltd. Key-value store architecture for key-value devices
CN114185746B (zh) * 2021-12-14 2025-07-15 北京字跳网络技术有限公司 数据存储方法、装置、电子设备及存储介质
CN115203159B (zh) * 2022-07-25 2024-06-04 北京字跳网络技术有限公司 一种数据存储方法、装置、计算机设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102999522A (zh) * 2011-09-15 2013-03-27 阿里巴巴集团控股有限公司 一种数据存储方法和装置
CN103034650A (zh) * 2011-09-29 2013-04-10 北京新媒传信科技有限公司 一种数据处理系统和方法
CN104462127A (zh) * 2013-09-22 2015-03-25 阿里巴巴集团控股有限公司 一种记录数据更新方法及装置
CN104504158A (zh) * 2015-01-19 2015-04-08 浪潮(北京)电子信息产业有限公司 一种快速更新业务的内存缓存的方法和设备

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6529909B1 (en) * 1999-08-31 2003-03-04 Accenture Llp Method for translating an object attribute converter in an information services patterns environment
US7630986B1 (en) * 1999-10-27 2009-12-08 Pinpoint, Incorporated Secure data interchange
US7818365B2 (en) * 2002-05-01 2010-10-19 Sybase, Inc. System, method, and computer program product for online and offline interactive applications on mobile devices
JP4506292B2 (ja) * 2004-06-10 2010-07-21 株式会社日立製作所 キャッシュ制御方法およびデータ処理システム並びにその処理プログラム
US8032707B2 (en) * 2008-09-15 2011-10-04 Microsoft Corporation Managing cache data and metadata
US8635402B2 (en) * 2009-03-31 2014-01-21 Nec Corporation Storage system and storage access method and program
JP4392676B1 (ja) * 2009-06-25 2010-01-06 修平 西山 キー・バリュー・ストアによるデータベース・キャッシュ装置
KR101482518B1 (ko) * 2010-08-25 2015-01-14 네벡스 버츄얼 테크놀로지스 인코포레이티드 캐시 계층화를 위한 방법 및 시스템
JP5524144B2 (ja) * 2011-08-08 2014-06-18 株式会社東芝 ｋｅｙ−ｖａｌｕｅストア方式を有するメモリシステム
CN102298641B (zh) * 2011-09-14 2013-05-01 清华大学 一种基于键值库的文件与结构化数据统一存储方法
US9135350B2 (en) 2012-01-05 2015-09-15 Sri International Computer-generated sentiment-based knowledge base
US9619487B2 (en) * 2012-06-18 2017-04-11 International Business Machines Corporation Method and system for the normalization, filtering and securing of associated metadata information on file objects deposited into an object store
CN103853714B (zh) * 2012-11-28 2017-06-20 中国移动通信集团河南有限公司 一种数据处理方法和装置
WO2014171413A1 (ja) * 2013-04-16 2014-10-23 株式会社日立製作所 処理性能低下を回避するメッセージシステム
US9477731B2 (en) * 2013-10-01 2016-10-25 Cloudera, Inc. Background format optimization for enhanced SQL-like queries in Hadoop
US9405783B2 (en) * 2013-10-02 2016-08-02 Netapp, Inc. Extent hashing technique for distributed storage architecture
US20150249852A1 (en) * 2014-02-28 2015-09-03 United Video Properties, Inc. Systems and methods for crowd-sourced media access control
US9306939B2 (en) * 2014-05-30 2016-04-05 Oracle International Corporation Authorization token cache system and method
TWI550418B (zh) * 2014-12-05 2016-09-21 Real - time processing method and device and application system of huge amount of streaming data
CN104778193B (zh) * 2014-12-23 2018-03-23 北京锐安科技有限公司 数据去重方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102999522A (zh) * 2011-09-15 2013-03-27 阿里巴巴集团控股有限公司 一种数据存储方法和装置
CN103034650A (zh) * 2011-09-29 2013-04-10 北京新媒传信科技有限公司 一种数据处理系统和方法
CN104462127A (zh) * 2013-09-22 2015-03-25 阿里巴巴集团控股有限公司 一种记录数据更新方法及装置
CN104504158A (zh) * 2015-01-19 2015-04-08 浪潮(北京)电子信息产业有限公司 一种快速更新业务的内存缓存的方法和设备

Also Published As

Publication number Publication date
ES2812771T3 (es) 2021-03-18
EP3343395A4 (en) 2018-07-04
EP3343395A1 (en) 2018-07-04
EP3343395B1 (en) 2020-07-22
JP2018526740A (ja) 2018-09-13
CN106484691B (zh) 2019-12-10
US20180181563A1 (en) 2018-06-28
US10776323B2 (en) 2020-09-15
CN106484691A (zh) 2017-03-08
JP6788002B2 (ja) 2020-11-18
PL3343395T3 (pl) 2020-11-16

Similar Documents

Publication Publication Date Title
WO2017032240A1 (zh) 移动终端的数据存储方法和装置
CN108319654B (zh) 计算系统、冷热数据分离方法及装置、计算机可读存储介质
US12393593B2 (en) Priority-driven federated query-based data caching
CN110989937A (zh) 一种数据存储方法、装置、设备及计算机可读存储介质
CN105631035B (zh) 数据存储方法和装置
CN104063409B (zh) 一种数据库的字段增加方法和系统
CN102780603B (zh) 网站流量控制方法及装置
CN104424219B (zh) 一种数据文件的管理方法及装置
CN110851436B (zh) 具有虚拟编索引的分布式搜索框架
CN107092628B (zh) 时间序列数据的处理方法和装置
US20190087130A1 (en) Key-value storage device supporting snapshot function and operating method thereof
CN105094707A (zh) 一种数据存储、读取方法及装置
WO2018095187A1 (zh) 文档在线预览方法及装置
CN104169944A (zh) 自动通知示出共同内容的图像
WO2017166815A1 (zh) 一种用于分布式数据库系统的更新数据的方法及装置
CN108319608A (zh) 访问日志存储查询的方法、装置及系统
CN114706867A (zh) 数据同步方法、装置、电子设备及存储介质
US10824612B2 (en) Key ticketing system with lock-free concurrency and versioning
CN108092667A (zh) 压缩时序数据以及查询时序数据的方法、装置
JP2018526740A5 (enExample)
US20110289289A1 (en) Backup and restore of items using bounded checkpoint and log buffers in memory
CN104281673A (zh) 一种数据库的缓存构建系统及对应的构建方法
CN105915636A (zh) 一种联系人信息的同步方法和装置
CN120596435A (zh) 元数据写入、元数据读取方法和装置
TWI709041B (zh) 移動終端的資料儲存方法和裝置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16838499

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018510513

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016838499

Country of ref document: EP