WO2018201887A1 - Procédé de réponse de données, appareil, dispositif terminal et support - Google Patents

Procédé de réponse de données, appareil, dispositif terminal et support Download PDF

Info

Publication number
WO2018201887A1
WO2018201887A1 PCT/CN2018/083297 CN2018083297W WO2018201887A1 WO 2018201887 A1 WO2018201887 A1 WO 2018201887A1 CN 2018083297 W CN2018083297 W CN 2018083297W WO 2018201887 A1 WO2018201887 A1 WO 2018201887A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
feature information
data management
management operation
request
Prior art date
Application number
PCT/CN2018/083297
Other languages
English (en)
Chinese (zh)
Inventor
曾芳
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018201887A1 publication Critical patent/WO2018201887A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G06F16/288—Entity relationship models
    • 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/242—Query formulation
    • G06F16/2425—Iterative querying; Query formulation based on the results of a preceding query
    • 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/25—Integrating or interfacing systems involving database management systems
    • G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual databases

Definitions

  • the present application belongs to the field of database technologies, and in particular, to a data response method, device, terminal device and medium.
  • a database for managing the information resources of the enterprise has been established within the existing major enterprises.
  • information resources of different service categories are usually stored in different databases.
  • This storage method also realizes the classification management of data to a certain extent.
  • the storage method also has the problem that the data is difficult to be uniformly processed.
  • the effective data that the user actually needs is usually not only an information resource of a certain category, and thus needs to jointly call information resources in multiple databases to achieve the data management purpose of the user.
  • the data management operation needs to be performed multiple times in the library, and the operation is cumbersome. Therefore, the data management efficiency is relatively low.
  • the embodiment of the present application provides a data response method and a data response device to solve the problem that the data management efficiency in the prior art is relatively low and the unified processing of data is difficult to implement.
  • a first aspect of the embodiments of the present application provides a data response method, including:
  • a second aspect of an embodiment of the present application provides a data response apparatus including means for performing the data response method of the first aspect described above.
  • a third aspect of the embodiments of the present application provides a terminal device, including a memory and a processor, where the computer stores computer readable instructions executable on the processor, the processor executing the computer The steps of the data response method as described in the first aspect are implemented when the instructions are read.
  • a fourth aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions, the computer readable instructions being executed by a processor to implement the first aspect as described in the first aspect The steps of the data response method.
  • the second database when the data management operation request for the feature information is received, the second database is used as a bridge to directly process the associated data corresponding to the feature information in the plurality of first databases in the background.
  • the unified processing of data is realized, and the user does not need to perform data management operations of multiple sub-databases, thereby improving data management efficiency.
  • FIG. 1 is a system architecture diagram applicable to a data response method provided by an embodiment of the present application
  • FIG. 2 is a flowchart of an implementation of a data response method provided by an embodiment of the present application
  • FIG. 3 is a specific implementation flowchart of a data response method S202 provided by an embodiment of the present application.
  • FIG. 5 is a specific implementation flowchart of a data response method S206 provided by an embodiment of the present application.
  • FIG. 6 is a flowchart of a specific implementation of a data response method S206 according to another embodiment of the present application.
  • FIG. 7 is a structural block diagram of a data response apparatus according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • FIG. 1 is a system architecture diagram of a data response method provided by an embodiment of the present application. For convenience of description, only parts related to the embodiment are shown.
  • the system consists of a second database 11, a client 12 and a plurality of independent first databases 13.
  • Each of the first databases 13 is used to store basic data of different service categories.
  • the second database 11 is configured to read the correlation data in the first database 13 according to the mutual relationship between the basic data of different service categories, and determine the feature information of the associated data, so as to match the feature information and the feature information.
  • the mapping relationship between the associated data is stored.
  • the second database 11 is further configured to provide the client 12 with the feature information-based data management operation response service to determine the data management operation request in the first database 13 according to the mapping relationship between the stored feature information and the associated data.
  • the data management operation on the associated data is implemented and the response result is returned, so that the client 12 can browse or manage the data actually stored in the first database 13 according to the response result.
  • the client 12 can be an application client or a web client, and runs on a terminal device that provides network access functions, including a personal computer, a tablet, or a mobile phone.
  • Each client 12 can serve as a request client of a data management operation, submit a data management operation request to the second database 11, and display a plurality of data records or display users required by the user according to the response result returned by the data management operation. Whether the management operation of the data is completed.
  • the back-end database is the first database
  • the intermediate database is the second database
  • FIG. 2 is a flowchart showing an implementation process of a data response method provided by an embodiment of the present application, which is described in detail as follows:
  • S201 Acquire associated data distributed in a plurality of first databases, where the associated data is data that needs to be processed jointly during a data operation.
  • the intermediate database establishes a dblink connection with multiple databases independently in the background.
  • the intermediate database can access the data stored in the backend database just like a local database.
  • Each database in the background stores multiple data tables, each of which contains multiple fields and contains attribute values corresponding to each record in each field.
  • the same two fields may exist in different databases or different data tables. If a field abc in one data table A is the primary key field abc in another data table B, and another field efg included in the data table A also exists in the data table B, the two data tables are related to each other. Data sheet.
  • the interrelated data table B there are N attribute values under the primary key field, and each attribute value corresponds to one record, and for each record corresponding to each attribute value, it corresponds to the attribute value in the data table A.
  • One record is associated data. In the process of a data management operation, since the associated data is distributed in multiple data tables or multiple databases, and the associated data is consistent, it is necessary to perform the same data management operation in each data table to achieve The purpose of joint processing.
  • the user when the user needs to modify the attribute value of the field efg corresponding to a certain attribute value in the primary key field abc in the data table B, the user also needs to use the data in the data table A under the field abc.
  • the attribute value of the field efg corresponding to the attribute value is subjected to the same modification operation to ensure data consistency and integrity.
  • the intermediate database When the intermediate database receives the read instruction based on the multiple associated data tables input by the data administrator, the intermediate database reads the multiple associated data tables, and uses the union The all method connects multiple associated data tables to identify multiple sets of associated data between the associated data tables.
  • S202 Acquire first feature information of the associated data.
  • the feature information is information capable of describing a constraint condition between each group of associated data.
  • the foregoing S202 specifically includes: S301: respectively acquiring attribute values of each data in the associated data.
  • S302 Create an attribute group.
  • S303 If the attribute values of the at least two data are the same, the attribute value is stored in the attribute group.
  • each set of associated data For each set of associated data, it can be known from the above S201 that there are substantially multiple records in the data table having mutually constrained relationships, and the records have two or more identical attribute values, and one of the attribute values is a primary key. value. Thus, these same attribute values in the associated data can be read and the fields corresponding to each attribute value can be determined. Also, create an attribute group for each set of associated data. If each of the attribute values in each set of associated data has the same attribute value of at least two data, the attribute value is stored in the attribute group.
  • the action field is used to mark the type of data management operations that the attribute group is allowed to perform, including deleting, querying, modifying, and disabling all types.
  • the action field can be set by the database administrator in accordance with the data management authority.
  • the feature information of each group of associated data acquired by the intermediate database is referred to as first feature information
  • the operation field included in the first feature information is referred to as a first operation field.
  • S203 Establish a mapping relationship between the first feature information and the associated data, and store the first feature information and the mapping relationship to a pre-established second database.
  • the specific generated first feature information can be used to represent the constraint condition between each group of associated data, and therefore, the first feature information has a mapping relationship with a group of associated data.
  • the intermediate database stores a mapping relationship between each of the first feature information and its corresponding set of associated data.
  • the feature information field is the primary key
  • each of the first feature information is used as each primary key value in the mapping relationship data table, and each of the first feature information corresponds to one.
  • the data table name and database name of each record in the group association data are the attribute values of the remaining fields in the mapping relationship data table.
  • S204 Obtain a data management operation request that is sent by the client to the second database and carries the second feature information.
  • the user selects a field name in any number of field option drop-down boxes displayed by the client, and generates a real-time attribute value matching the selected multiple field names.
  • the Options drop-down box select the multiple attribute values that you want to perform data management operations on.
  • the data management operation drop-down box displayed by the client select the type of data management operation that you need to perform on the above multiple attribute values.
  • the client If the data management operation type selected by the user is a query, after the client receives the confirmation instruction issued by the user, the client generates second feature information, and encapsulates the second feature information in the data management operation request to Data management operation requests are sent to the intermediate database.
  • the second feature information includes the option values respectively corresponding to the respective drop-down boxes.
  • the client If the data management operation type selected by the user is modified, the client generates an input box corresponding to each attribute value selected by the user, so that the user types the parameter value modified by the attribute value in the input box.
  • the client After the client receives the confirmation command issued by the user, the client generates second feature information, and encapsulates the second feature information in the data modification operation request to send the data modification operation request to the intermediate database.
  • the second feature information includes an option value corresponding to each of the above-mentioned drop-down boxes and a parameter value in the input box.
  • S205 Determine, in the plurality of sets of the first feature information stored in the second database, first feature information that is the same as the second feature information, and determine, according to the mapping relationship, that the data management operation request is matched. Linked data.
  • the intermediate database searches for the first feature information that is the same as the second feature information, and reads the corresponding data table stored in the record according to the record in which the first feature information is located. Name and database name.
  • the intermediate database determines that the associated data corresponding to the first feature information is each record stored in each data table of the background database, wherein each database in which the record is located is a back-end database corresponding to the read database name, and each The data table in which a record is located is the data table corresponding to the read data table name in the background database.
  • each determined record is associated data that matches the data management operation request.
  • the second feature information includes an attribute group and a second operation field.
  • the above S205 specifically includes:
  • S401 Determine, in the plurality of sets of the first feature information stored in the second database, the first feature information that is the same as the attribute group in the second feature information.
  • the attribute group includes the option values respectively selected by the user in each of the drop-down boxes of the client except the data management operation drop-down box.
  • Each option value selected by the user in each drop-down box except the data management operation drop-down box is an element in the attribute group of the second feature information.
  • the intermediate database searches for the first feature information that is the same as the attribute group in the second feature information, that is, in the mapping relationship data table, finds the first element that includes each element of the attribute group. Feature information.
  • S402 Determine whether the second operation field is the same as the first operation field in the determined first feature information.
  • the first operation field in the first feature information that is found is read to determine a data management operation type corresponding to the first feature information.
  • the first operation field is compared with the second operation field of the second feature information to determine whether the data management operation types corresponding to the two operation fields are the same.
  • step S403 is performed.
  • the S403 is specifically: returning the rejection response prompt information.
  • the intermediate database directly returns a rejection response prompt message to inform the user that it is an illegal operation, or informs the user that its operation is not within the scope of authorization.
  • step S404 is performed.
  • the S404 is specifically configured to: determine association data that matches the data management operation request according to the mapping relationship between the first feature information and the associated data.
  • the data management operation matching the data management operation type corresponding to the attribute group in the background database is allowed to be performed, and the second feature information and attributes are determined.
  • the first feature information of the same group is the same.
  • the intermediate database determines that the associated data corresponding to the first feature information is each record stored in each data table of the background database, wherein each database in which the record is located is a back-end database corresponding to the read database name, and each The data table in which a record is located is the data table corresponding to the read data table name in the background database.
  • the user only needs to directly select the attribute group element data of the associated operation and the data management operation type in the drop-down box displayed by the client, that is, the data management operation carrying the second feature information may be sent to the intermediate database.
  • the request does not need to input the SQL statement that can be recognized by the database, which improves the user's data acquisition efficiency.
  • the intermediate database can directly determine whether to allow the operation of the associated data related to the second feature information, without separately going to each database in the background. Request confirmation is performed, thereby further improving the efficiency of data processing.
  • S206 Perform a data management operation on the determined associated data according to the data management operation request to respond to the data management operation request.
  • the intermediate database serves as a request client of the background database, and respectively issues a request to each background database to request the determined data to be associated with the data management operation type. Matching data management operations.
  • the intermediate database After the background database returns the response result to the intermediate database, the intermediate database generates the client response data to extract the valid message data in the response result returned by the background database, encapsulates it into the client response data, and returns the client to the intermediate database.
  • the interaction between the client and the back-end database can be implemented in a form similar to an intermediate bridge.
  • the intermediate database when receiving the data management operation request for the feature information, is used as a bridge to directly process the associated data corresponding to the feature information in the plurality of databases in the background, thereby implementing the data. Unified processing, the user does not need to perform multiple data management operations of the sub-library, thereby improving data management efficiency.
  • the above S206 includes:
  • the intermediate database After the intermediate database obtains the associated data that matches the data query operation request, the background database and the data table stored by the associated data are obtained.
  • the intermediate database calls a preset query statement template, and fills a plurality of attribute values included in the second feature information and a database name and a data table name stored in each associated data into the query statement template, respectively, to generate a plurality of query statements. .
  • the intermediate database transmits the respective query statements to the corresponding database in the background based on the database name in the query statement.
  • each database in the background When each database in the background receives the query sent by the intermediate database, it processes and responds to the query. According to the plurality of attribute values and the data table name carried by the query statement, the database in the background reads a record corresponding to the plurality of attribute values from the data table corresponding to the data table name, and stores the record as The associated data in the background database is returned to the intermediate database.
  • the intermediate database After the intermediate database receives the associated data returned by each back-end database, the intermediate database summarizes the associated data to return all the associated data together as a response result of the data management operation request sent by the client.
  • the client after receiving the associated data returned by the background database one by one, the client can uniformly display all the associated data corresponding to the attribute group required by the user according to the response result returned by the intermediate database. For the user, it is not necessary to perform the data query operation of the multiple sub-databases, and it is not necessary to separately query the associated data corresponding to the attribute group in each background database, thereby realizing the unified processing of the data and improving the query efficiency of the data.
  • the above S206 includes:
  • the operation field in the second feature information carried by the data management operation request is a modification
  • the modified parameter value is input in the input box, and the modified parameter based on the attribute value in the second feature information is the parameter input by the user. value.
  • the intermediate database reads the modified parameters based on the attribute value from the data modification request.
  • the modified parameter is processed by using a preset conversion algorithm to respectively generate a parameter modification instruction corresponding to the associated data in the plurality of the first databases.
  • the intermediate database After the intermediate database obtains the associated data that matches the data modification operation request, the background database and the data table stored by the associated data are obtained.
  • the intermediate database calls the preset modification statement template, and fills the plurality of attribute values included in the second feature information, the modification parameters corresponding to each attribute value, and the database name and the data table name stored in each associated data to the query respectively.
  • the statement template multiple parameter modification instructions are generated.
  • S603 Send the parameter modification instruction to each of the plurality of first databases, so that the plurality of the first databases respectively modify the stored associated data.
  • the intermediate database transmits the parameter modification instructions to the corresponding database in the background based on the database name in the parameter modification instruction.
  • the parameter modification instruction is processed and responded.
  • the database in the background reads a record corresponding to the plurality of attribute values from the data table corresponding to the data table name, and the record is in the record
  • the attribute value is changed to the modified parameter in the parameter modification instruction, and at the same time, the modification completion prompt information is returned and returned to the intermediate database.
  • the intermediate database After the intermediate database receives the modification completion prompt information returned by each back-end database, the intermediate database returns a response result based on the modification completion prompt information to the client.
  • the intermediate database can automatically generate parameter modification instructions related to the associated data distributed in multiple back-end databases, thereby automatically requesting to uniformly modify all the records including the attribute group in each database in the background. Ensure data consistency and integrity. For the user, there is no need to perform multiple data modification operations of the sub-database, and it is not necessary to sequentially modify multiple records of the same attribute value in each background database, thereby realizing unified processing of data and improving data modification efficiency. .
  • FIG. 7 is a structural block diagram of the data response apparatus provided by the embodiment of the present application. For the convenience of explanation, only the parts related to the present embodiment are shown.
  • the data response device 71 includes:
  • the associated data obtaining unit 711 is configured to acquire associated data distributed in a plurality of first databases, where the associated data is data that needs to be processed in common during a data operation.
  • the feature information obtaining unit 712 is configured to acquire first feature information of the associated data.
  • the mapping relationship establishing unit 713 is configured to establish a mapping relationship between the first feature information and the associated data, and store the first feature information and the mapping relationship to a pre-established second database.
  • the request obtaining unit 714 is configured to acquire a data management operation request that is sent by the client to the second database and that carries the second feature information.
  • the association data matching unit 715 is configured to determine, in the plurality of sets of the first feature information stored in the second database, the first feature information that is the same as the second feature information, and determine the location and the location according to the mapping relationship. The associated data of the data management operation request matching.
  • the request response unit 716 is configured to perform a data management operation on the determined associated data according to the data management operation request to respond to the data management operation request.
  • the feature information acquiring unit 712 includes: an obtaining subunit, configured to respectively acquire attribute values of each data in the associated data.
  • a storage subunit configured to store the attribute value in the attribute group if the attribute values of the at least two data are the same.
  • Adding a subunit configured to add a first operation field to the attribute group, and output the attribute group including the first operation field as the first feature information.
  • the first operation field is used to indicate the type of the data management operation corresponding to the attribute group.
  • the second feature information includes the attribute group and a second operation field
  • the associated data matching unit 715 includes:
  • Determining a subunit configured to determine, in the plurality of sets of the first feature information stored in the second database, the same first feature information as the attribute group in the second feature information.
  • a determining subunit configured to determine whether the second operation field is the same as the first operation field in the determined first feature information.
  • a matching subunit configured to determine the data according to the mapping relationship between the first feature information and the associated data, if the second operation field is the same as the first operation field in the determined first feature information Manage the associated data that the operation request matches.
  • the request response unit 716 includes:
  • the downloading subunit is configured to download the determined related data when the data management operation request is a data query request.
  • the method is used to return the associated data as a response result of the data query request.
  • the request response unit 716 includes:
  • the obtaining subunit is configured to acquire, when the data management operation request is a data modification request, a modification parameter based on the attribute group in the data modification request.
  • the modifying subunit is configured to separately send the parameter modification instruction to the plurality of the first databases, so that the plurality of the first databases respectively modify the stored associated data.
  • FIG. 8 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 8 of this embodiment includes a processor 80 and a memory 81 in which computer readable instructions 82, such as data response programs, executable on the processor 80 are stored.
  • the processor 80 executes the computer readable instructions 82 to implement the steps in the various data response method embodiments described above, such as steps 201 through 206 shown in FIG.
  • the processor 80 when executing the computer readable instructions 82, implements the functions of the various modules/units in the various apparatus embodiments described above, such as the functions of the units 711 through 716 shown in FIG.
  • the computer readable instructions 82 may be partitioned into one or more modules/units that are stored in the memory 81 and executed by the processor 80, To complete this application.
  • the one or more modules/units may be a series of computer readable instruction segments capable of performing a particular function, the instruction segments being used to describe the execution of the computer readable instructions 82 in the terminal device 8.
  • the terminal device 8 may be a computing device such as a desktop computer, a notebook, a palmtop computer, or a cloud server.
  • the terminal device may include, but is not limited to, the processor 80 and the memory 81. It will be understood by those skilled in the art that FIG. 8 is merely an example of the terminal device 8, and does not constitute a limitation on the terminal device 8, and may include more or less components than those illustrated, or combine some components, or different components.
  • the terminal device may further include an input/output device, a network access device, a bus, and the like.
  • the so-called processor 80 can be a central processing unit (Central Processing Unit, CPU), can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 81 may be an internal storage unit of the terminal device 8, such as a hard disk or a memory of the terminal device 8.
  • the memory 81 may also be an external storage device of the terminal device 8, such as a plug-in hard disk provided on the terminal device 8, a smart memory card (SMC), and a secure digital (SD). Card, flash card, etc. Further, the memory 81 may also include both an internal storage unit of the terminal device 8 and an external storage device.
  • the memory 81 is configured to store the computer readable instructions and other programs and data required by the terminal device.
  • the memory 81 can also be used to temporarily store data that has been output or is about to be output.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Computational Linguistics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention s'applique au domaine de la technologie des bases de données et concerne un procédé de réponse de données, un appareil, un dispositif terminal et un support. Le procédé consiste à : obtenir des données associées réparties sur une pluralité de premières bases de données ; obtenir des premières informations de caractéristiques des données associées ; établir une relation de mappage entre les premières informations de caractéristiques et les données associées, et stocker les premières informations de caractéristiques et la relation de mappage dans une deuxième base de données ; obtenir une demande d'opération de gestion de données contenant des deuxièmes informations de caractéristiques et envoyée par un client à la deuxième base de données ; déterminer parmi de multiples ensembles des premières informations de caractéristiques stockées par la deuxième base de données, les premières informations de caractéristiques identiques aux deuxièmes informations de caractéristiques, et déterminer, en fonction de la relation de mappage, les données associées correspondant à la demande d'opération de gestion de données ; et selon la demande d'opération de gestion de données, effectuer une opération de gestion de données sur les données associées déterminées de façon à répondre à la demande d'opération de gestion de données. La présente invention réalise un traitement de données unifié, de sorte qu'un client n'ait pas besoin d'effectuer une opération de gestion de données en mettant en œuvre de multiples actions de fragmentation, ce qui améliore l'efficacité de gestion de données.
PCT/CN2018/083297 2017-05-05 2018-04-17 Procédé de réponse de données, appareil, dispositif terminal et support WO2018201887A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710313344.1A CN107798038B (zh) 2017-05-05 2017-05-05 数据响应方法及数据响应设备
CN201710313344.1 2017-05-05

Publications (1)

Publication Number Publication Date
WO2018201887A1 true WO2018201887A1 (fr) 2018-11-08

Family

ID=61531047

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083297 WO2018201887A1 (fr) 2017-05-05 2018-04-17 Procédé de réponse de données, appareil, dispositif terminal et support

Country Status (2)

Country Link
CN (1) CN107798038B (fr)
WO (1) WO2018201887A1 (fr)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107798038B (zh) * 2017-05-05 2020-02-14 平安科技（深圳）有限公司 数据响应方法及数据响应设备
CN108600333B (zh) * 2018-04-03 2021-03-12 广东阿里影业云智软件有限公司 一种基于代理服务器的数据传输方法、设备以及系统
CN108920109A (zh) * 2018-07-19 2018-11-30 郑州云海信息技术有限公司 一种存储平台统一管理方法、装置、设备及系统
CN109241068B (zh) * 2018-08-22 2023-04-07 中国平安人寿保险股份有限公司 前后台数据比对的方法、装置及终端设备
CN109033457A (zh) * 2018-08-29 2018-12-18 广州中赢财富信息科技有限公司 多源数据库关联的审计方法及系统
CN110928896A (zh) * 2018-09-19 2020-03-27 北京国双科技有限公司 一种数据查询方法及装置
CN109213821B (zh) * 2018-09-25 2022-03-15 中国银行股份有限公司 数据处理方法及系统
CN110109924A (zh) * 2019-04-23 2019-08-09 重庆紫光华山智安科技有限公司 检索方法及装置
CN110324403A (zh) * 2019-05-23 2019-10-11 平安科技（深圳）有限公司 动态分库路由方法、装置、服务器及存储介质
CN110442632A (zh) * 2019-08-09 2019-11-12 泰康保险集团股份有限公司 数据处理方法和装置
CN112287644B (zh) * 2020-09-30 2024-01-30 成都新潮传媒集团有限公司 一种数据提交方法、装置、计算机设备和可读存储介质
CN113590883A (zh) * 2021-08-10 2021-11-02 上海杉互健康科技有限公司 医疗信息与数据库映射的方法、系统、设备及存储介质
CN114489510A (zh) * 2022-01-28 2022-05-13 维沃移动通信有限公司 数据读取方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103365929A (zh) * 2012-04-10 2013-10-23 阿里巴巴集团控股有限公司 一种数据库连接的管理方法及系统
CN105847320A (zh) * 2016-03-02 2016-08-10 乐视致新电子科技（天津）有限公司 一种资源获取方法和装置
CN107798038A (zh) * 2017-05-05 2018-03-13 平安科技（深圳）有限公司 数据响应方法及数据响应设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100535856C (zh) * 2006-10-16 2009-09-02 中兴通讯股份有限公司 一种构造中间库的方法
US8229945B2 (en) * 2008-03-20 2012-07-24 Schooner Information Technology, Inc. Scalable database management software on a cluster of nodes using a shared-distributed flash memory
CN102438042B (zh) * 2011-11-04 2014-04-02 中国工商银行股份有限公司 一种多点接入设备的动态参数同步方法及系统
CN102724295B (zh) * 2012-05-24 2016-05-18 中国电子科技集团公司第十五研究所 数据同步方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103365929A (zh) * 2012-04-10 2013-10-23 阿里巴巴集团控股有限公司 一种数据库连接的管理方法及系统
CN105847320A (zh) * 2016-03-02 2016-08-10 乐视致新电子科技（天津）有限公司 一种资源获取方法和装置
CN107798038A (zh) * 2017-05-05 2018-03-13 平安科技（深圳）有限公司 数据响应方法及数据响应设备

Also Published As

Publication number Publication date
CN107798038A (zh) 2018-03-13
CN107798038B (zh) 2020-02-14

Similar Documents

Publication Publication Date Title
WO2018201887A1 (fr) Procédé de réponse de données, appareil, dispositif terminal et support
JP7222036B2 (ja) モデルトレーニングシステムおよび方法および記憶媒体
US10868865B2 (en) System and apparatus to manage data using a peer-to-peer network and the blockchain
US20210385087A1 (en) Zero-knowledge identity verification in a distributed computing system
WO2020001105A1 (fr) Procédé et appareil de vérification de données basées sur une chaîne de blocs, et dispositif électronique
WO2019200756A1 (fr) Procédé et appareil d'examen et d'approbation de données, dispositif informatique et support d'informations
WO2021012553A1 (fr) Procédé de traitement de données et dispositif associé
US9483386B2 (en) Information interaction test device and method based on automatic generation of associated test cases
WO2020168692A1 (fr) Procédé de partage de données de masse, plateforme de partage ouverte et dispositif électronique
WO2018040722A1 (fr) Procédé et dispositif d'interrogation de données de tables
US20110302277A1 (en) Methods and apparatus for web-based migration of data in a multi-tenant database system
US11106659B2 (en) Blockchain-based recording and querying operations
US20230024345A1 (en) Data processing method and apparatus, device, and readable storage medium
WO2021208762A1 (fr) Enregistrement et interrogation de données
CN113094334B (zh) 基于分布式存储的数字服务方法、装置、设备及储存介质
WO2020001162A1 (fr) Procédé, appareil et dispositif de gestion de conteneur
WO2019127773A1 (fr) Procédé et appareil de traitement de ventes de produit d'assurance, support de stockage, et terminal
WO2023216532A1 (fr) Procédé de gestion d'actifs numériques et dispositif associé
TWI812366B (zh) 一種資料共用方法、裝置、設備及存儲介質
CN111782652B (zh) 数据调用方法、装置、计算机设备和存储介质
CN116894732A (zh) 数字资产管理方法、装置、系统及可读存储介质
CN107181801B (zh) 一种电子附件存储方法及终端
WO2018188607A1 (fr) Procédé et dispositif de traitement de flux
WO2020082580A1 (fr) Procédé et appareil de synchronisation d'informations, et support d'enregistrement et serveur
WO2023279770A1 (fr) Procédé, appareil et système de stockage de données, support de stockage et produit de programme

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

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

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

122 Ep: pct application non-entry in european phase

Ref document number: 18794907

Country of ref document: EP

Kind code of ref document: A1