CN111488382A - Data calling method and system and electronic equipment - Google Patents
Data calling method and system and electronic equipment Download PDFInfo
- Publication number
- CN111488382A CN111488382A CN202010300021.0A CN202010300021A CN111488382A CN 111488382 A CN111488382 A CN 111488382A CN 202010300021 A CN202010300021 A CN 202010300021A CN 111488382 A CN111488382 A CN 111488382A
- Authority
- CN
- China
- Prior art keywords
- data
- queue
- service data
- new
- query
- 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
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000009286 beneficial effect Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 3
- 230000004888 barrier function Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G06Q50/60—
Abstract
The invention relates to a data calling method, a system and electronic equipment, which are characterized in that preset rules in a database are configured, data are obtained from the database in advance, a plurality of service data and corresponding queue IDs are generated, the service data are stored in a data cache pool, the queue IDs are stored in a cache queue, when a service data request is made, the data do not need to be obtained from the database, the query queue ID corresponding to the service data request is matched with the queue ID in the cache queue, and when the matching is successful, the corresponding service data are directly called from the data cache pool and returned to a calling party.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a data calling method, system and electronic device.
Background
With the development of the telecommunication industry, the business data is more diversified and massive, the data is inevitably stored and called by using the related technology of a big data ecosphere, the technical specifications and calling modes of the storage components used for storing the business data, namely the data models of the databases, are different, and in the using process of the project, a set of corresponding packaging methods needs to be respectively realized or quoted for different databases, and related data is called by different methods, so that more requirements on the aspects of resources, strategies and the like are inevitably required, and therefore, the problems of complex data calling process and low efficiency exist.
Disclosure of Invention
The invention provides a data calling method, a data calling system and electronic equipment, aiming at the defects of the prior art.
The technical scheme of the data calling method is as follows:
acquiring data from at least one database according to preset rules in a configuration library, generating at least one piece of service data and a queue ID corresponding to each piece of service data according to the acquired data, storing each piece of service data in a data cache pool, and storing each queue ID in a cache queue;
receiving at least one service data request sent by a calling party, and generating a query queue ID according to the service data request;
and matching the query queue ID with the queue ID in the cache queue, if the query queue ID is successfully matched with the queue ID in the cache queue, calling corresponding service data from the data cache pool according to the successfully matched queue ID, and returning the service data to the caller.
The beneficial effects of the data calling method of the invention are as follows:
the method comprises the steps of acquiring data from a database in advance by configuring preset rules in a library, generating a plurality of service data and corresponding queue IDs, storing the service data into a data cache pool, and storing the queue IDs into a cache queue.
On the basis of the above scheme, the data calling method of the present invention can be further improved as follows.
Further, still include: if the matching is unsuccessful:
obtaining a query condition according to the service data request and the preset rule;
and acquiring corresponding new data from the corresponding database according to the query condition, generating corresponding new service data according to the new data, and returning the corresponding new service data to the calling party.
The beneficial effect of adopting the further scheme is that: and matching the query queue ID with the queue ID in the cache queue, if the matching is unsuccessful, acquiring corresponding new data from a corresponding database according to the query condition, generating new service data and returning the new service data to the calling party so as to ensure that the calling party can acquire the service data corresponding to the service data request.
Further, the obtaining of corresponding new service data according to the new data and returning to the caller includes:
storing the new service data to the data cache pool, and generating a corresponding new queue ID;
and calling the new service data from the updated data cache pool according to the new queue ID, and returning the new service data to a calling party.
The beneficial effect of adopting the further scheme is that: the new service data is stored in the data cache pool, then the new queue ID is called from the data cache pool, and the programming code of 'calling the corresponding service data from the data cache pool according to the successfully matched queue ID and returning to the calling party' can be repeatedly used, so that the workload is reduced.
Further, still include: and storing the new queue ID into the buffer queue.
The beneficial effect of adopting the further scheme is that: when the calling party repeatedly initiates the same service data request, the corresponding service data can be directly called from the data cache pool, and the efficiency is high.
The technical scheme of the data calling system is as follows:
the system comprises an acquisition cache module, a receiving module and an inquiry return module;
the acquisition caching module is used for acquiring data from at least one database according to preset rules in the configuration library, generating at least one piece of service data and a queue ID corresponding to each piece of service data according to the acquired data, storing each piece of service data in a data caching pool, and storing each queue ID in a caching queue;
the receiving module is used for receiving at least one service data request sent by a calling party and generating a query queue ID according to the service data request;
and the query returning module is used for matching the query queue ID with the queue ID in the cache queue, if the matching is successful, calling corresponding service data from the data cache pool according to the successfully matched queue ID, and returning the service data to the calling party.
The beneficial effects of the data calling system of the invention are as follows:
the method comprises the steps of acquiring data from a database in advance by configuring preset rules in a library, generating a plurality of service data and corresponding queue IDs, storing the service data into a data cache pool, and storing the queue IDs into a cache queue.
On the basis of the above scheme, the data calling system of the present invention can be further improved as follows.
Further, the query return module is further configured to, if the matching is unsuccessful, then
Obtaining a query condition according to the service data request and a preset rule;
and acquiring corresponding new data from the corresponding database according to the query condition, generating corresponding new service data according to the new data, and returning the corresponding new service data to the calling party.
The beneficial effect of adopting the further scheme is that: and matching the query queue ID with the queue ID in the cache queue, if the matching is unsuccessful, acquiring corresponding new data from a corresponding database according to the query condition, generating new service data and returning the new service data to the calling party so as to ensure that the calling party can acquire the service data corresponding to the service data request.
Further, the query return module is specifically configured to:
storing the new service data to the data cache pool, and generating a corresponding new queue ID;
and calling the new service data from the updated data cache pool according to the new queue ID, and returning the new service data to a calling party.
The beneficial effect of adopting the further scheme is that: the new service data is stored in the data cache pool, then the new queue ID is called from the data cache pool, and the programming code of 'calling the corresponding service data from the data cache pool according to the successfully matched queue ID and returning to the calling party' can be repeatedly used, so that the workload is reduced.
Further, the cache obtaining module is further configured to store the new queue ID into the cache queue.
The beneficial effect of adopting the further scheme is that: when the calling party repeatedly initiates the same service data request, the corresponding service data can be directly called from the data cache pool, and the efficiency is high.
The technical scheme of the electronic equipment is as follows:
the method comprises a memory, a processor and a program stored on the memory and running on the processor, wherein the processor realizes the steps of any one of the data calling methods when executing the program.
The electronic equipment has the following beneficial effects:
the method comprises the steps of acquiring data from a database in advance by configuring preset rules in a library, generating a plurality of service data and corresponding queue IDs, storing the service data into a data cache pool, and storing the queue IDs into a cache queue.
Drawings
Fig. 1 is a schematic flowchart of a data calling method according to an embodiment of the present invention;
FIG. 2 is a logic diagram of a data call method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a data call system according to an embodiment of the present invention.
Detailed Description
As shown in fig. 1, a data calling method according to an embodiment of the present invention includes the following steps:
s1, acquiring data from at least one database according to preset rules in the configuration library, generating at least one piece of service data and a queue ID corresponding to each piece of service data according to the acquired data, storing each piece of service data in a data cache pool, and storing each queue ID in a cache queue;
s2, receiving at least one service data request sent by a calling party, and generating a query queue ID according to the service data request;
and S3, matching the query queue ID with the queue ID in the cache queue, if the matching is successful, calling corresponding service data from the data cache pool according to the successfully matched queue ID, and returning the service data to the caller.
The method comprises the steps of acquiring data from a database in advance by configuring preset rules in a library, generating a plurality of service data and corresponding queue IDs, storing the service data into a data cache pool, and storing the queue IDs into a cache queue.
Taking data of the telecommunication industry as an example, as shown in fig. 2, specifically:
s10, acquiring data from different databases according to preset rules in the configuration library:
suppose that the data of China Mobile, China Union or China telecom in different provinces are stored in different databases, the databases comprise Hbase database, Hive database, Hdfs database, ES (elastic search) database, MySQ L database and the like;
the preset rules in the configuration library can be service identification-time period and database-data relationship, wherein the database-data relationship can be understood as that one kind of data can be obtained from the Hbase database, another kind of data can be obtained from the Hive database, for example, the service identification of the service queried by the cell phone number bill can be set as A, the time period is set from 1 month and 1 day of 2020 to 1 month and 7 days of 2020, or from 1 month and 1 day of 2020 to 1 month and 31 days of 2020, and the like, and for the Hbase database, the Hive database, the Hdfs database, the ES (elastic search) database and the MySQ L database, corresponding data can be obtained through an Hbase API, a hiveAPI, an ES API and MySQ L Dao, respectively, wherein the service identification and the time period can be set according to actual conditions;
s11, generating at least one service data and a queue ID corresponding to each service data according to the obtained data, specifically:
1) it is assumed that only the service identifier a and the time period for the mobile phone number bill query are configured in the configuration library: at this time, the bill data of each mobile phone number or part of mobile phone numbers in 1 month 1 day in 2020 to 1 month 31 day in 2020 is obtained from each database, and at this time, the bill data of each mobile phone number can understand each service data, or the service data has a fixed format, and the bill data is converted into the service data with the fixed format. The fixed format can be set according to actual conditions.
2) It is assumed that only the service identifier a and the time period for the mobile phone number bill query are configured in the configuration library: from 1/2020 to 31/2020, the billing data of each mobile phone number or part of the mobile phone numbers from 1/2020 to 31/2020/1/31 is obtained from each database, but for the convenience of user query or due to some conventional query requirements, the generated service data is: in short, by acquiring data from each database at one time, service data under different conditions such as different time periods can be generated, the frequency of acquiring data from each database is reduced, and the efficiency is improved.
Taking the mobile phone numbers 153 ×××××××× and 180 ×××××××× as examples, the billing data, i.e., service data of the mobile phone number 153 ×××××××× from 1/2020 to 1/31/2020 is generated into a queue ID of a _20200101_20200131_153 ×××××××× according to the format of the service identifier _ start time _ end time _ mobile phone number, and the billing data, i.e., service data of the mobile phone number 180 ×××××××× from 1/2020 to 1/31/2020 is generated into a queue ID of a _20200101_20200131_180 ×××××××× according to the format of the service identifier _ start time _ end time _ mobile phone number, where the format of the service identifier _ start time _ end time _ mobile phone number can be adjusted according to actual situations, and details are not described herein.
Wherein, the execution frequency of S10 and S11 can be set, specifically: s10 and S11 may be set to be executed once every 12 hours or 24 hours, and delete the data acquired last time, the service data in the data buffer pool, and the queue ID in the buffer queue, and store the updated service data and the updated queue ID.
S12, query process:
when a user of the mobile phone number 153 ××××××××, namely a calling party, initiates a service data request, the service data request necessarily includes information such as bill inquiry, keywords, namely the mobile phone number and time period, and the information is extracted, and a query queue ID A-20200101-20200131-153 ×××××××× is generated according to the same format, namely service identification-start time-end time-mobile phone number;
and matching the query queue ID A _20200101_20200131_153 ×××××××× with the queue ID in the cache queue, wherein the cache queue contains the queue ID of A _20200101_20200131_153 ××××××××, the matching is successful, and the corresponding service data is called from the data cache pool according to the successfully matched queue ID A _20200101_20200131_153 ×××××××× and returned to the 153 ×××××××× user with the mobile phone number, namely the calling party.
Moreover, the above processes can be integrated in a data unified delivery platform, a cache queue, a data cache pool and a configuration library are all arranged in the data unified delivery platform, and Hbase API, Hive API, ES API and MySQ L Dao are arranged on a data interface layer of the data unified delivery platform, and when data needs to be acquired from another database Solr, a corresponding interface is added on the data interface layer, which has expansibility, and a data interaction API is arranged in the data unified delivery platform, specifically:
the unified data delivery platform receives the service data requests from the first calling party and the Nth calling party … … through the data interaction API, analyzes the bill query and the keywords, namely the mobile phone number, the time period and other information in the service processing request, then splices the information into a query queue ID, matches the query queue ID with the queue ID in the cache queue in a one-by-one matching mode or a Boolean mode, acquires corresponding service data from the data cache pool if the matching is successful, returns to the corresponding first calling party and the corresponding Nth calling party through the data interaction API … …, can package the service data in json or in other modes, and then returns the service data so as to ensure that the service data cannot lose details.
Because the current universal contact trend in the telecommunication industry is that the same service is issued in a multi-contact channel, the first caller and the second caller … …, the nth caller can be understood as the first contact and the second contact … …, when a real user initiates services such as mobile phone number payment inquiry and the like, a service data request is initiated to the data unified delivery platform through the first contact, the second contact … … or the nth contact, wherein N is a positive integer.
Moreover, the data unified delivery platform is suitable for all terminal products with different PC versions, pads and mobile terminals.
Preferably, in the above technical solution, the method further comprises: if the matching is unsuccessful:
s30, obtaining a query condition according to the service data request and the preset rule;
and S31, acquiring corresponding new data from the corresponding database according to the query condition, generating corresponding new service data according to the new data, and returning the new service data to the calling party.
For example, if the query queue ID a _20200101_20200131_153 ×××××××× does not match a consistent queue ID in the cache queue, the matching is not successful, at this time, a user of a mobile phone number 153 ×××××××× initiates a service data request of billing data from 1/2020 to 1/2020/31, assuming that a preset rule is to obtain the billing data from the Hbase database, the query condition is that the mobile phone number 153 ××××××××, the service identifier a, 1/2020 to 1/2020, and 31/Hbase database are used, and the corresponding billing data, i.e., corresponding new data, is found from the Hbase database according to the preset condition, and new service data corresponding to the service data is generated according to the billing data, where the service data can be understood as converting the billing data into service data in a fixed format, and then the new service data is returned.
Preferably, in the above technical solution, in S31, obtaining corresponding new service data according to the new data and returning the new service data to the caller includes:
s310, storing the new service data to the data cache pool, and generating a corresponding new queue ID;
s311, the new service data is called from the updated data cache pool according to the new queue ID, and the new service data is returned to the calling party.
The new service data is stored in the data cache pool, then the new queue ID is called from the data cache pool, and the programming code of 'calling the corresponding service data from the data cache pool according to the successfully matched queue ID and returning to the calling party' can be repeatedly used, so that the workload is reduced.
The new queue ID refers to the queue ID in the above, and the new service data is called from the updated data cache pool, and the content of calling the corresponding service data from the data cache pool in the above is also referred to, which is not described herein again.
Preferably, in the above technical solution, the method further comprises:
s312, storing the new queue ID into the buffer queue. When the calling party repeatedly initiates the same service data request, the corresponding service data can be directly called from the data cache pool, and the efficiency is high.
The invention relates to a data calling method, which is characterized in that preset rules in a database are configured, data are obtained from the database in advance, a plurality of service data and corresponding queue IDs are generated, the service data are stored in a data cache pool, the queue IDs are stored in a cache queue, when a service data request is carried out, the data do not need to be obtained from the database, the query queue ID corresponding to the service data request is matched with the queue ID in the cache queue, when the matching is successful, the corresponding service data are directly called from the data cache pool and returned to a calling party, namely, in the calling process, the service data do not need to be concerned about the difference of databases, database APIs (application program interfaces) and calling methods, only the service data need to be concerned about, technical barriers brought by different databases and corresponding matched components for realizing data calling are reduced or even eliminated, and the technical barriers brought by storing the service data into the data cache pool and storing the queue IDs into the cache queue are realized by a mechanism The automatic learning and automatic adaptation capability changes the phase of each caller into the following contacts to realize the preloading effect of service data, and solves the problems that part of large data assemblies have poor IO efficiency and cannot adapt to the performance of an interface service layer, such as: hive database, the general simple query statement of which needs minute level to respond.
As shown in fig. 3, a data calling system 200 according to an embodiment of the present invention includes an obtaining cache module 210, a receiving module 220, and a query returning module 230;
the obtaining cache module 210 is configured to obtain data from at least one database according to a preset rule in the configuration library, generate at least one piece of service data and a queue ID corresponding to each piece of service data according to the obtained data, store each piece of service data in the data cache pool, and store each queue ID in the cache queue;
the receiving module 220 is configured to receive at least one service data request sent by a caller, and generate a query queue ID according to the service data request;
the query returning module 230 is configured to match the query queue ID with the queue ID in the cache queue, and if the matching is successful, call corresponding service data from the data cache pool according to the successfully matched queue ID, and return the service data to the caller.
The method comprises the steps of acquiring data from a database in advance by configuring preset rules in a library, generating a plurality of service data and corresponding queue IDs, storing the service data into a data cache pool, and storing the queue IDs into a cache queue.
Preferably, in the above technical solution, the query returning module 230 is further configured to, if the matching is unsuccessful, then,
obtaining a query condition according to the service data request and the preset rule;
and acquiring corresponding new data from the corresponding database according to the query condition, generating corresponding new service data according to the new data, and returning the corresponding new service data to the calling party.
And matching the query queue ID with the queue ID in the cache queue, if the matching is unsuccessful, acquiring corresponding new data from a corresponding database according to the query condition, generating new service data and returning the new service data to the calling party so as to ensure that the calling party can acquire the service data corresponding to the service data request.
Preferably, in the above technical solution, the query returning module 230 is specifically configured to:
storing the new service data to the data cache pool, and generating a corresponding new queue ID;
and calling the new service data from the updated data cache pool according to the new queue ID, and returning the new service data to a calling party.
The new service data is stored in the data cache pool, then the new queue ID is called from the data cache pool, and the programming code of 'calling the corresponding service data from the data cache pool according to the successfully matched queue ID and returning to the calling party' can be repeatedly used, so that the workload is reduced.
Preferably, in the above technical solution, the obtaining cache module 210 is further configured to store the new queue ID into the cache queue.
When the calling party repeatedly initiates the same service data request, the corresponding service data can be directly called from the data cache pool, and the efficiency is high.
The above steps for implementing the corresponding functions of each parameter and each unit module in the data call system 200 of the present invention may refer to each parameter and step in the above embodiments of a data call method, which are not described herein again.
An electronic device according to an embodiment of the present invention includes a memory, a processor, and a program stored in the memory and running on the processor, where the processor implements the steps of the data call method according to any one of the embodiments when executing the program.
The method comprises the steps of acquiring data from a database in advance by configuring preset rules in a library, generating a plurality of service data and corresponding queue IDs, storing the service data into a data cache pool, and storing the queue IDs into a cache queue.
The electronic device may be a computer, a mobile phone, or the like, and correspondingly, the program is computer software or a mobile phone APP, and the parameters and the steps in the electronic device of the present invention may refer to the parameters and the steps in the above embodiment of the data call method, which is not described herein again.
In the present invention, the terms "first", "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (9)
1. A data calling method, comprising:
acquiring data from at least one database according to preset rules in a configuration library, generating at least one piece of service data and a queue ID corresponding to each piece of service data according to the acquired data, storing each piece of service data in a data cache pool, and storing each queue ID in a cache queue;
receiving at least one service data request sent by a calling party, and generating a query queue ID according to the service data request;
and matching the query queue ID with the queue ID in the cache queue, if the query queue ID is successfully matched with the queue ID in the cache queue, calling corresponding service data from the data cache pool according to the successfully matched queue ID, and returning the service data to the caller.
2. The data calling method according to claim 1, further comprising:
if the matching is unsuccessful, obtaining a query condition according to the service data request and the preset rule;
and acquiring corresponding new data from the corresponding database according to the query condition, generating corresponding new service data according to the new data, and returning the corresponding new service data to the calling party.
3. The data calling method according to claim 2, wherein the obtaining of the corresponding new service data according to the new data and returning to the caller comprises:
storing the new service data to the data cache pool, and generating a corresponding new queue ID;
and calling the new service data from the updated data cache pool according to the new queue ID, and returning the new service data to a calling party.
4. The data calling method according to claim 3, further comprising: and storing the new queue ID into the buffer queue.
5. A data calling system is characterized by comprising an acquisition cache module, a receiving module and a query returning module;
the acquisition caching module is used for acquiring data from at least one database according to preset rules in the configuration library, generating at least one piece of service data and a queue ID corresponding to each piece of service data according to the acquired data, storing each piece of service data in a data caching pool, and storing each queue ID in a caching queue;
the receiving module is used for receiving at least one service data request sent by a calling party and generating a query queue ID according to the service data request;
and the query returning module is used for matching the query queue ID with the queue ID in the cache queue, if the matching is successful, calling corresponding service data from the data cache pool according to the successfully matched queue ID, and returning the service data to the calling party.
6. The data call system as claimed in claim 5, wherein the query return module is further configured to return the query to the query module if the matching is unsuccessful
Obtaining a query condition according to the service data request and the preset rule;
and acquiring corresponding new data from the corresponding database according to the query condition, generating corresponding new service data according to the new data, and returning the corresponding new service data to the calling party.
7. The data call system according to claim 6, wherein the query return module is specifically configured to:
storing the new service data to the data cache pool, and generating a corresponding new queue ID;
and calling the new service data from the updated data cache pool according to the new queue ID, and returning the new service data to a calling party.
8. The data call system as claimed in claim 7, wherein said get cache module is further configured to store said new queue ID in said cache queue.
9. An electronic device comprising a memory, a processor and a program stored on the memory and running on the processor, wherein the steps of a data call method as claimed in any one of claims 1 to 4 are implemented when the program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010300021.0A CN111488382A (en) | 2020-04-16 | 2020-04-16 | Data calling method and system and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010300021.0A CN111488382A (en) | 2020-04-16 | 2020-04-16 | Data calling method and system and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111488382A true CN111488382A (en) | 2020-08-04 |
Family
ID=71812907
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010300021.0A Pending CN111488382A (en) | 2020-04-16 | 2020-04-16 | Data calling method and system and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111488382A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948434A (en) * | 2021-02-25 | 2021-06-11 | 平安壹钱包电子商务有限公司 | Business event-based business processing method and device, computer equipment and storage medium |
| CN113806651A (en) * | 2021-09-18 | 2021-12-17 | 深圳市酷开网络科技股份有限公司 | Data caching method, device, server and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0643853A1 (en) * | 1992-06-03 | 1995-03-22 | PITTS, William M. | System for accessing distributed data cache channel at each network node to pass requests and data |
| EP1133105A2 (en) * | 2000-03-06 | 2001-09-12 | Sony Corporation | Buffer allocation method for 1394 serial bus |
| EP1489524A1 (en) * | 2003-06-18 | 2004-12-22 | Hitachi, Ltd. | Storage area network with a cache server |
| CN103390061A (en) * | 2013-07-31 | 2013-11-13 | 浙江大学 | Multi-level cache-based sea spatio-temporal data accessing method taking user as center |
| CN103390041A (en) * | 2013-07-18 | 2013-11-13 | 杭州东信北邮信息技术有限公司 | Method and system for providing data service based on middleware |
| CN103729471A (en) * | 2014-01-21 | 2014-04-16 | 华为软件技术有限公司 | Method and device for database query |
| CN108874946A (en) * | 2018-06-05 | 2018-11-23 | 政采云有限公司 | A kind of ID management method and device |
| CN109902103A (en) * | 2019-01-17 | 2019-06-18 | 平安城市建设科技(深圳)有限公司 | Service data management method, device, equipment and computer readable storage medium |
| CN110633296A (en) * | 2018-05-31 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Data query method, device, medium and electronic equipment |
-
2020
- 2020-04-16 CN CN202010300021.0A patent/CN111488382A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0643853A1 (en) * | 1992-06-03 | 1995-03-22 | PITTS, William M. | System for accessing distributed data cache channel at each network node to pass requests and data |
| EP1133105A2 (en) * | 2000-03-06 | 2001-09-12 | Sony Corporation | Buffer allocation method for 1394 serial bus |
| EP1489524A1 (en) * | 2003-06-18 | 2004-12-22 | Hitachi, Ltd. | Storage area network with a cache server |
| CN103390041A (en) * | 2013-07-18 | 2013-11-13 | 杭州东信北邮信息技术有限公司 | Method and system for providing data service based on middleware |
| CN103390061A (en) * | 2013-07-31 | 2013-11-13 | 浙江大学 | Multi-level cache-based sea spatio-temporal data accessing method taking user as center |
| CN103729471A (en) * | 2014-01-21 | 2014-04-16 | 华为软件技术有限公司 | Method and device for database query |
| CN110633296A (en) * | 2018-05-31 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Data query method, device, medium and electronic equipment |
| CN108874946A (en) * | 2018-06-05 | 2018-11-23 | 政采云有限公司 | A kind of ID management method and device |
| CN109902103A (en) * | 2019-01-17 | 2019-06-18 | 平安城市建设科技(深圳)有限公司 | Service data management method, device, equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 崔朝霞: ""基于Savant中间件的物联网底层数据缓冲区管理策略的研究"", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948434A (en) * | 2021-02-25 | 2021-06-11 | 平安壹钱包电子商务有限公司 | Business event-based business processing method and device, computer equipment and storage medium |
| CN112948434B (en) * | 2021-02-25 | 2024-04-09 | 平安壹钱包电子商务有限公司 | Business event-based business processing method, device, computer equipment and storage medium |
| CN113806651A (en) * | 2021-09-18 | 2021-12-17 | 深圳市酷开网络科技股份有限公司 | Data caching method, device, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11310066B2 (en) | Method and apparatus for pushing information | |
| CN107872523B (en) | Network data loading method and device, storage medium and mobile terminal | |
| US20050021767A1 (en) | Keeping persistency while switching between modalities | |
| CN111488382A (en) | Data calling method and system and electronic equipment | |
| CN110377369B (en) | Method, device and computer storage medium for running small program | |
| CN108415998B (en) | Application dependency relationship updating method, terminal, device and storage medium | |
| CN114465998A (en) | Multi-device file transmission method and device, terminal device and readable storage medium | |
| CN113127564B (en) | Parameter synchronization method and device | |
| CN114741335A (en) | Cache management method, device, medium and equipment | |
| CN110389976B (en) | Multi-interface data scheduling method and device | |
| CN113282590A (en) | Interface joint debugging method and device based on 5G message | |
| CN112598529B (en) | Data processing method and device, computer readable storage medium and electronic equipment | |
| CN108959294B (en) | Method and device for accessing search engine | |
| CN113194339A (en) | Live list generation method and device, electronic equipment and readable storage medium | |
| CN111046113B (en) | Data retrieval device and method for different types of data warehouses | |
| CN108769232A (en) | Application resource method for pushing, device, equipment and storage medium | |
| CN113065054A (en) | Request processing method and device, electronic equipment and storage medium | |
| CN113760948A (en) | Data query method and device | |
| CN113037851A (en) | Method for achieving cloud mobile phone system overdivision based on storage | |
| CN113051271B (en) | Cold and hot data separation method, device and equipment thereof | |
| CN116028696A (en) | Resource information acquisition method and device, electronic equipment and storage medium | |
| CN111198853A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN112486409B (en) | Method, system, terminal and storage medium for automatically recycling cluster cloud hard disk | |
| US10402391B2 (en) | Processing method, device and system for data of distributed storage system | |
| CN113779122A (en) | Method and apparatus for exporting data |
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 |