Data calling method, device and equipment

Abstract

The embodiments of this specification provide a data calling method, device and equipment that can be used in the field of big data. The method includes receiving a business call request; the business call request includes an XSD document corresponding to the target business; according to the XSD document and the mapping script, determining the element list required for the target business; the mapping script includes a mapping relationship between elements in the BLAZE element menu and elements in the XSD document; based on the data query component corresponding to the elements in the BLAZE element menu, obtaining the data corresponding to each element in the element list; assembling the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string; calling the BLAZE decision engine based on the XML string to obtain a decision result. The embodiments of this specification can effectively solve the problems of frequent BLAZE parameter changes and hard-coded BLAZE data assembly, thereby improving data calling efficiency.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a data calling method, device and equipment. Background Art

[0002] With the rapid development of internet finance and the accelerated transformation of banking marketing models in the era of mass retail, banks are moving towards smart and intelligent operations while developing a wide range of new products and services, such as digital credit cards, financing e-loans, joint auto loans, home improvement installment plans, and cash installment plans. To adapt to the high-quality development of the digital economy, the efficiency of launching new and existing products is becoming increasingly important.

[0003] Currently, many new products and services require integration with the BLAZE process engine of a big data center when they are launched. Before invoking the BLAZE process engine, thousands of elements must be assembled into an XML string. Existing techniques primarily use the XJC command to generate POJO objects from XSD (XML Schema Definition) documents, encapsulate the data in Java Bean objects, and then use dom4j to convert the Java Beans into XML. However, when BLAZE parameters change frequently, this hard-coded approach requires constant modification of the Java Bean class and its corresponding data retrieval logic, which reduces data call efficiency.

[0004] Therefore, the industry is in urgent need of a technical solution that can solve the above technical problems. Summary of the Invention

[0005] The embodiments of this specification provide a data calling method, apparatus, and device, which can effectively solve the problems of frequent BLAZE parameter changes and hard-coded BLAZE data assembly, thereby improving data calling efficiency.

[0006] The data calling method, device and equipment provided in this specification are implemented in the following ways.

[0007] A data calling method comprises: receiving a business calling request; the business calling request includes an XSD document corresponding to a target business; determining a list of elements required for the target business based on the XSD document and a mapping script; the mapping script includes a mapping relationship between elements in a BLAZE element menu and elements in the XSD document; obtaining data corresponding to each element in the element list based on a data query component corresponding to the elements in the BLAZE element menu; assembling the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string; and calling a BLAZE decision engine in a big data center based on the XML string to obtain a decision result.

[0008] A data calling device comprises: a receiving module for receiving a business calling request; the business calling request includes an XSD document corresponding to a target business; a determining module for determining a list of elements required for the target business based on the XSD document and a mapping script; the mapping script includes a mapping relationship between elements in a BLAZE element menu and elements in an XSD document; an acquiring module for acquiring data corresponding to each element in the element list based on a data query component corresponding to the elements in the BLAZE element menu; a generating module for assembling the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string; and an acquiring module for calling a BLAZE decision engine of a big data center based on the XML string to obtain a decision result.

[0009] A data calling device includes at least one processor and a memory storing computer-executable instructions, wherein when the processor executes the instructions, the steps of any method embodiment in the embodiments of this specification are implemented.

[0010] A computer-readable storage medium stores computer instructions, which, when executed, implement the steps of any method embodiment in the embodiments of this specification.

[0011] This specification provides a data calling method, device and equipment. In some embodiments, a business call request can be received, wherein the business call request includes an XSD document corresponding to the target business, and the list of elements required for the target business is determined based on the XSD document and the mapping script, wherein the mapping script includes the mapping relationship between the elements in the BLAZE element menu and the elements in the XSD document. It is also possible to obtain the data corresponding to each element in the element list based on the data query component corresponding to the element in the BLAZE element menu, assemble the element list and the data corresponding to each element in the element list according to the format of the XSD document, and generate an XML string. Furthermore, it is also possible to call the BLAZE decision engine of the big data center based on the XML string to obtain the decision result. By adopting the implementation scheme provided in this specification, it is only necessary to configure the mapping script and expand the data query component to support the rapid launch of various business scenarios and the dynamic expansion of elements, thereby effectively solving the problems of frequent changes in BLAZE parameters and hard-coding of BLAZE data assembly, and improving data calling efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings described herein are used to provide a further understanding of this specification, constitute a part of this specification, and do not constitute a limitation of this specification. In the accompanying drawings:

[0013] Figure 1 This is a flow chart of an embodiment of a data calling method provided in this specification;

[0014] Figure 2 This is a schematic diagram of an embodiment of a data calling method provided in this specification;

[0015] Figure 3 This is a schematic diagram of the module structure of an embodiment of a data calling device provided in this specification;

[0016] Figure 4 This is a hardware structure block diagram of an embodiment of a data call server provided in this specification. DETAILED DESCRIPTION

[0017] To help those skilled in the art better understand the technical solutions in this specification, the following will provide a clear and complete description of the technical solutions in the embodiments of this specification, in conjunction with the accompanying drawings. Obviously, the described embodiments are only some of the embodiments in this specification, not all of them. All other embodiments obtained by those skilled in the art based on one or more embodiments in this specification without creative work should fall within the scope of protection of the embodiments of this specification.

[0018] Business approval in areas such as credit cards, special installments, and personal consumer loans requires docking with the BLAZE process engine of the big data center, and then obtaining BLAZE's decision results. However, before calling the BLAZE process engine of the big data center, a large number of elements need to be assembled into XML strings in accordance with the requirements of the BOM interface document. In order to solve the problems of frequent parameter changes and hard-coded data assembly in the prior art, this application provides a data calling method that can flexibly configure parameters and intelligently assemble according to the approval stage of the business scenario, thereby quickly docking with the big data center and improving data calling efficiency.

[0019] The following describes the implementation plan of this specification using a specific application scenario as an example. Figure 1 The flowchart of an embodiment of a data call method provided in this specification is as follows. Although this specification provides the method operation steps or device structure shown in the following embodiments or figures, the method or device may include more or fewer operation steps or module units based on routine or no creative effort.

[0020] An embodiment provided in this specification can be applied to a client, a server, etc. The client can include a terminal device, such as a smartphone, a tablet computer, etc. The server can include a single computer device, a server cluster consisting of multiple servers, or a server structure of a distributed system, etc.

[0021] It should be noted that the following embodiment description does not limit the technical solutions in other application scenarios that can be expanded based on this specification. Figure 1 As shown, in an embodiment of a data calling method provided in this specification, the method may include the following steps.

[0022] S0: Receive a service call request; the service call request includes an XSD document corresponding to the target service.

[0023] The target business can be any business that requires data, such as credit assessment, home improvement installment loans, next-generation special installment loans, digital credit cards, Rong E-loan, auto joint loans, and cash installment loans. XSD (XML Schema Definition) documents can be used to describe the structure of XML documents, including the XML format and constraints required by the big data center for upload to BLAZE. XML is a markup language used to structure electronic files. BLAZE is a deep learning inference engine that can be used to connect to big data centers.

[0024] In some embodiments, each business may be associated with business information. This business information may include the business category, business subcategory, call phase, and business application number. For example, the business category for the new generation special installment business is "new generation special installment," the corresponding business subcategory may be "new generation special installment calculation," and the call phase is "calculation." The business category for the home improvement installment business is "home improvement installment," the corresponding business subcategory may be "home improvement installment loan," and the call phase is "loan."

[0025] In some embodiments, the major business categories may include at least one of the following: card issuance, credit limit adjustment, new generation special installment, financing e-loan, home improvement installment, E-installment, etc. The minor business categories may include at least one of the following: flexible external data query for card issuance, digital credit card, new generation special installment calculation, new generation special installment credit enhancement, new generation special installment approval, new generation special installment loan, home improvement installment calculation, home improvement installment approval, home improvement installment loan, e-installment loan, etc. The calling stage may include at least one of the following: calculation, credit enhancement, approval, loan, etc. Of course, the above is only an illustrative explanation, and the business information is not limited to the above examples. Technical personnel in the relevant field may make other changes based on the technical essence of this application, but as long as the functions and effects achieved are the same or similar to those of this application, they should be covered within the scope of protection of this application.

[0026] In some embodiments, the big data center can pre-provision a corresponding XSD document for each business. Since each business has corresponding business information, each XSD document corresponds to that business information. An XSD document includes one or more data nodes, each of which includes one or more elements. The XSD document also includes the access URL (Uniform Resource Locator) address for invoking the big data center's BLAZE decision engine.

[0027] In some embodiments, users can send service call requests to the server via smart terminals. These smart terminals can be self-service terminals at bank branches or mobile banking services. For example, in some implementation scenarios, a bank plans to launch a 1+N real-time credit calculation service. Before applying for a credit card, users can calculate their credit limit via a self-service terminal. When calculating their credit limit, they can send a credit calculation service call request to the server. The service call request includes the XSD document corresponding to the credit calculation service.

[0028] S2: Determine a list of elements required for the target business based on the XSD document and the mapping script; the mapping script includes a mapping relationship between elements in the BLAZE element menu and elements in the XSD document.

[0029] In an embodiment of this specification, after receiving a service call request, a list of elements required for the target service can be determined based on the XSD document and mapping script corresponding to the target service included in the service call request. The mapping script may include a mapping relationship between elements in a BLAZE element menu and elements in an XSD document. An element list can be understood as a collection of elements. The list of elements required for the target service can be understood as the fields required to implement the target service.

[0030] In some embodiments, the mapping script can be generated by: obtaining a BOM interface document and an XSD document corresponding to the business provided by the big data center; categorizing the elements in the BOM interface document to obtain a BLAZE element menu; configuring a data query component for each element in the BLAZE element menu; moving the BLAZE element menu and the XSD document to a designated directory, and calling a preset mapping tool to generate a mapping script based on the obtained business category, business subcategory, and call phase. The BOM interface document refers to an Excel-formatted document agreed upon by the application and the big data center for use by multiple parties, such as product managers, developers, and testers.

[0031] In some implementation scenarios, the BLAZE element menu is obtained by classifying the elements in the BOM interface document, grouping the elements with the same data retrieval logic into one category, and then filling in the corresponding data retrieval interface implementation class. In this way, the BLAZE element menu can be represented as an Excel format document including one or more data items. Each data item includes one or more elements. The data item can be understood as a Java Bean object in POJO format, and the member variables of each Java Bean object can correspond to the elements in the data item. The data item can be used as the base class of the return object of the data query component or the generic type of LIST to ensure type consistency.

[0032] In some implementation scenarios, in the BLAZE element menu, the first sheet page can be a menu directory, column A is the data type, column B is the data name, and column C is the data time limit. Each row can represent a data item, and each data item corresponds to each subsequent sheet page. Starting from the second sheet page, each sheet page is a data item, and each data item corresponds to a data node in the XSD document. The sheet name is consistent with the data node name.

[0033] In some implementation scenarios, after obtaining a BLAZE feature menu, you can configure a corresponding data query component for each data item in the BLAZE feature menu. This way, each feature in the same data item corresponds to the same data query component. Each data query component can implement the fetch method of the SourceFetcher interface to retrieve the data corresponding to the feature. Configuring the data query component implementation class in the source data acquisition class cell in the BLAZE feature menu ensures subsequent unified scheduling.

[0034] In some implementation scenarios, the data query component may include at least one of the following: a local query component and an external query component. In some implementation scenarios, the local query component may include at least one of the following: a credit card application information component, a new generation installment information component, a home improvement installment calculation component, a home improvement installment entry component, etc. The external query component may include at least one of the following: a graylist query component, a credit inquiry component, a Bairong credit score query component, a Bairong fraud score query component, a China Credit blacklist query component, a China Higher Education Student Information and Career Center academic qualification query component, or a China Higher Education Student Information and Career Center student status comparison query component.

[0035] In some implementation scenarios, the data query components can be stored in the BLAZE data query component repository.

[0036] In some implementation scenarios, after obtaining the XSD document and BLAZE element menu corresponding to the business, you can move the BLAZE element menu and XSD document to a specified directory, and then call the preset mapping tool to generate a mapping script based on the incoming business category, business subcategory, and calling stage. For example, in some implementation scenarios, the XSD documents and BLAZE element menus corresponding to the business can be placed in the specified directory of the bamdsf project. Then, based on the input business categories (such as dictionary items including: 1-card issuance, 2-credit limit adjustment, 3-new generation special installment, 4-e-loan, 6-home improvement installment, 7-E installment), business subcategories (such as dictionary items including: 11-flexible external data query for card issuance, 12-digital credit card, 31-new generation special installment estimation, 32-new generation special installment credit enhancement, 33-new generation special installment approval, 34-new generation special installment loan, 61-home improvement installment estimation, 62-home improvement installment approval, 63-home improvement installment loan, 71-e installment loan, etc.), calling stage (such as dictionary items including: S1-estimation, S2-credit enhancement, S3-approval, S4-loan, etc.), and other input parameters, the mapping tool class BLAZEParamParserUtils is called to execute the parse method to generate a mapping script. Of course, the above is only an exemplary explanation, and the method of generating the mapping script is not limited to the above example. Technical personnel in the relevant field may make other changes based on the technical essence of this application, but as long as the functions and effects achieved are the same or similar to those of this application, they should be covered within the scope of protection of this application.

[0037] In some implementation scenarios, after generating a mapping script, you can submit it to the BLAZE parameter mapping table for deployment. For example, in some implementation scenarios, you can submit the mapping script to a git repository, publish it to the runtime environment, and then deploy it to the BLAZE parameter mapping table of the Oracle database.

[0038] In an embodiment of the present specification, by classifying the elements in the BOM interface document, a BLAZE element menu is obtained, a data query component is configured for each element in the BLAZE element menu, the BLAZE element menu and the XSD document are moved to a specified directory, and based on the obtained business categories, business subcategories, and calling stages, a preset mapping tool is called to generate a mapping script, which can realize the mapping of each data node in the XSD document to a data item in the BLAZE element menu, and the mapping of each element (also called an attribute) in the XSD document to an element (also called a data field) in the data item, which can facilitate the unified scheduling of subsequent business data, thereby improving data scheduling efficiency.

[0039] In some embodiments, before receiving a service call request, a mapping script can be pre-generated, and a dependent data query component can be configured for each element in the BLAZE element menu. For example, in some implementation scenarios, before receiving a service call request for calculating a credit limit, the server can first read the BLAZE element menu and the XSD document corresponding to the credit limit calculation service. It can then map and match the data names and field names in the BLAZE element menu with the elements in the data nodes in the XSD document. Furthermore, based on business information such as the major business category, minor business category, and call phase, a mapping script can be generated using a tool class to map the elements in the XSD document to the elements in the BLAZE element menu. Finally, the mapping script can be submitted and deployed to the BLAZE parameter mapping table.

[0040] In the embodiments of this specification, by pre-generating a corresponding mapping script for each business and deploying it into the BLAZE parameter mapping table, not only can the reuse of element information be achieved, but also dynamic configuration of elements and intelligent assembly of data can be achieved during data scheduling, thereby improving data scheduling efficiency.

[0041] In some embodiments, determining the list of elements required for the target business based on the XSD document and the mapping script may include: obtaining the corresponding mapping script from the BLAZE parameter mapping table based on the business information corresponding to the XSD document; the business information includes at least business categories, business subcategories, and calling stages; and determining the list of elements required for the target business based on the XSD document and the mapping script.

[0042] In some implementation scenarios, after receiving a business call request, the corresponding mapping script can be obtained from the BLAZE parameter mapping table according to the business major category, business subcategory, and call stage corresponding to the XSD document in the business call request, and then the list of elements required for the target business can be obtained based on the mapping relationship between the elements in the BLAZE element menu in the mapping script and the elements in the XSD document. In some implementation scenarios, the autoBuild method in the BlazeParamAutoBuilder class can be used to pass in parameters such as the business major category, business subcategory, and call stage, and then the mapping script in the BLAZE parameter mapping table can be queried based on the business major category, business subcategory, and call stage to obtain the corresponding mapping script, and then the list of elements required for the target business can be obtained based on the mapping relationship between the elements in the BLAZE element menu in the mapping script and the elements in the XSD document. Among them, the autoBuild method in the BlazeParamAutoBuilder class can be used to receive business parameters.

[0043] S4: Based on the data query component corresponding to the element in the BLAZE element menu, obtain the data corresponding to each element in the element list.

[0044] In the embodiments of this specification, after determining the list of elements required for the target business, the data corresponding to each element in the element list can be obtained based on the data query component corresponding to the element in the BLAZE element menu. Since each data item in the BLAZE element menu is pre-configured with a corresponding data query component, after determining the list of elements required for the target business, the corresponding data can be obtained based on the data query component corresponding to the element.

[0045] In some embodiments, the data query component corresponding to the elements in the BLAZE element menu can group the elements in the element list according to the corresponding data retrieval logic before obtaining the data corresponding to each element in the element list to obtain different element groups. In some implementation scenarios, before obtaining the data corresponding to each element in the element list, the elements in the element list with the same data retrieval logic can be grouped together. Each group can represent an item of data to be queried.

[0046] In the embodiment of this specification, by grouping the elements with the same retrieval logic in the element list into a group and retrieving data according to the data query component corresponding to each group, the data corresponding to the elements with the same retrieval logic can be retrieved at one time, thereby effectively reducing the number of retrieval times and improving the retrieval efficiency.

[0047] In some embodiments, the business information also includes a business application number; the data query component corresponding to the element in the BLAZE element menu is used to obtain the data corresponding to each element in the element list, including: traversing each element group; based on the business application number, using the JAVA reflection mechanism to call the corresponding data query component in the BLAZE element menu to obtain a componentized Response object; the componentized Response object includes each element in the element list and the data corresponding to each element.

[0048] In some implementation scenarios, after grouping the elements in the element list with the same data retrieval logic, you can traverse each element group, pass in the business application number, and call the data query component configured in the mapping script through the JAVA reflection mechanism to automatically obtain the actual value corresponding to the element.

[0049] In some implementation scenarios, the elements in the componentized Response object can be used as keys and the actual values corresponding to the elements can be stored as values.

[0050] In some implementation scenarios, after obtaining a componentized Response object, you can call the BlazeParamAdaptor.append method to map elements to data nodes. The BlazeParamAdaptor.append method can be used to map elements to data nodes.

[0051] S6: Assemble the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string.

[0052] In an embodiment of this specification, after obtaining the data corresponding to each element in the element list, the element list and the data corresponding to each element in the element list can be assembled according to the format of an XSD document to generate an XML string. The XML string can be used as a parameter for connecting to the BLAZE decision engine of the big data center, and the XML string can be used as a data source for the BLAZE decision engine when calling the BLAZE interface of the big data center.

[0053] In some embodiments, after obtaining the data corresponding to each element in the element list, the toXml method can be called to generate an XML string of BLAZE data according to the format of an XSD document from the element list and the data corresponding to each element in the element list. The toXml method is used to generate an XML string of BLAZE data according to the format of an XSD document.

[0054] In some embodiments, when generating an XML string of BLAZE data, a BLAZE data converter may be called to convert the data format. For example, a percentage element may be multiplied by 100 to convert it to a percent format, and an amount may be converted to a three-digit format.

[0055] S8: Calling the BLAZE decision engine of the big data center based on the XML string to obtain a decision result.

[0056] In the embodiments of this specification, after generating an XML string, the BLAZE decision engine in the big data center can be called based on the XML string to obtain a decision result. The decision result may include a decision result flag (0 - approved, 1 - rejected, 2 - transferred to manual processing, 3 - data query), credit method, approval limit, loan limit, credit recommendation limit, guarantee recommendation limit, etc.

[0057] In some embodiments, after generating the XML string, the access URL address for calling the BLAZE decision engine of the big data center can be obtained from the XSD document, and then the BLAZE decision engine of the big data center is called based on the XML string and the access URL address to return the decision result.

[0058] In some embodiments, after obtaining the decision result, the result can be recorded in BAMAP_BLAZE_LOG so that the service interface can be called back later. BAMAP_BLAZE_LOG can be used to record the corresponding log for subsequent query.

[0059] In some embodiments, after obtaining the decision result, the decision result may be pushed to the target terminal so that the user can perform the next operation based on the decision result.

[0060] In the embodiment of this specification, a mapping tool can automatically generate a mapping script between the BLAZE element menu and the XSD document, without the need to manually write the mapping script, which can ensure the subsequent connection to the big data center for data calls and the rapid launch of various business scenarios.

[0061] The embodiments of this specification can support the rapid launch of various business scenarios and the dynamic expansion of elements simply by configuring mapping scripts and extending data query components.

[0062] The embodiments of this manual support flexible configuration of BLAZE parameters and intelligent assembly, rapid connection to big data centers, and accurate decision-making.

[0063] The embodiments of this specification can effectively solve the problems of frequent changes in BLAZE parameters and hard-coded BLAZE data assembly, thereby improving data call efficiency.

[0064] In this specification, the various embodiments of the above method are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. For relevant parts, please refer to the partial description of the method embodiment.

[0065] Of course, the above is only an exemplary description, and the embodiments of this specification are not limited to the above examples. Technical personnel in the relevant field may make other changes based on the technical essence of this application. However, as long as the functions and effects achieved are the same or similar to those of this application, they should be included in the scope of protection of this application.

[0066] like Figure 2 As shown, Figure 2It is a schematic diagram of an embodiment of a data calling method provided in this specification. In this embodiment, the caller initiates a business application to the dispatcher, and the dispatcher reads the mapping script according to the business category, business subcategory, and calling stage, and then polls the scheduling data query component (including query component 1, query component 2, query component 3, and query component 4), further receives the component query data and assembles it into XML format data, and finally calls the big data center BLAZE interface to return the decision result to the caller. Among them, before the caller initiates a business application to the dispatcher, it can first initiate a mapping application to the parser. After receiving the mapping application, the parser can read the BLAZE element menu Excel file and XSD file, and then map and match the data name and field name in the element menu with the elements in the data node in the XSD file, and further generate a mapping script according to business information such as business category, business subcategory, and calling stage to realize the mapping of elements in the XSD document and elements in the BLAZE element menu, and finally submit the mapping script for deployment to the BLAZE parameter mapping table. After generating a mapping script, you can configure dependent data query components for each element in the BLAZE element menu in the mapping script, such as the credit query component, graylist query component, application anti-fraud query component, customer profile query component, and card application score query component. The data query components can be pre-stored in the BLAZE data query component repository.

[0067] From the above description, it can be seen that the embodiment of the present application can receive a business call request, wherein the business call request includes an XSD document corresponding to the target business, and determines the list of elements required for the target business based on the XSD document and the mapping script, wherein the mapping script includes the mapping relationship between the elements in the BLAZE element menu and the elements in the XSD document. It is also possible to obtain the data corresponding to each element in the element list based on the data query component corresponding to the element in the BLAZE element menu, assemble the element list and the data corresponding to each element in the element list according to the format of the XSD document, and generate an XML string. Furthermore, it is also possible to call the BLAZE decision engine of the big data center based on the XML string to obtain the decision result. Since it is only necessary to configure the mapping script and expand the data query component to support the rapid launch of various business scenarios and support the dynamic expansion of elements, the present application can effectively solve the problems of frequent changes in BLAZE parameters and hard-coded BLAZE data assembly, thereby improving data call efficiency.

[0068] Based on the data calling method described above, one or more embodiments of this specification also provide a data calling device. The device may include a system (including a distributed system), software (application), module, component, server, client, etc. using the method described in the embodiment of this specification and combined with the necessary implementation hardware. Based on the same innovative concept, the device in one or more embodiments provided in the embodiment of this specification is as described in the following embodiments. Since the implementation scheme and method for solving the problem of the device are similar, the implementation of the specific device of the embodiment of this specification can refer to the implementation of the aforementioned method, and the repetitions will not be repeated. As used below, the term "unit" or "module" can implement a combination of software and / or hardware for a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0069] Specifically, Figure 3 This is a schematic diagram of the module structure of an embodiment of a data calling device provided in this specification. Figure 3 As shown, a data calling device provided in this specification may include: a receiving module 120 , a determining module 122 , an acquiring module 124 , a generating module 126 , and an obtaining module 128 .

[0070] The receiving module 120 may be configured to receive a service call request, wherein the service call request includes an XSD document corresponding to the target service;

[0071] The determination module 122 may be configured to determine a list of elements required for the target business based on the XSD document and a mapping script; the mapping script may include mapping relationships between elements in the BLAZE element menu and elements in the XSD document;

[0072] The acquisition module 124 may be used to acquire data corresponding to each element in the element list based on a data query component corresponding to an element in the BLAZE element menu;

[0073] The generating module 126 may be configured to assemble the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string;

[0074] The obtaining module 128 may be used to call the BLAZE decision engine of the big data center based on the XML string to obtain a decision result.

[0075] It should be noted that the above-mentioned device may also include other implementation methods according to the description of the method embodiment. The specific implementation methods can refer to the description of the relevant method embodiments and will not be described in detail here.

[0076] This specification also provides an embodiment of a data calling device, including a processor and a memory for storing processor-executable instructions, wherein the instructions, when executed by the processor, implement the following steps: receiving a business call request; the business call request includes an XSD document corresponding to the target business; determining a list of elements required for the target business based on the XSD document and a mapping script; the mapping script includes a mapping relationship between elements in a BLAZE element menu and elements in the XSD document; obtaining data corresponding to each element in the element list based on a data query component corresponding to the elements in the BLAZE element menu; assembling the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string; calling the BLAZE decision engine of a big data center based on the XML string to obtain a decision result.

[0077] It should be noted that the above-mentioned device may also include other implementations according to the description of the method or apparatus embodiment. Specific implementations can refer to the description of the relevant method embodiment and will not be described in detail here.

[0078] The method embodiments provided in this specification can be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Taking running on a server as an example, Figure 4 This is a hardware structure diagram of an embodiment of a data call server provided in this specification. The server can be a data call device or data call equipment in the above embodiment. Figure 4 As shown, the server 10 may include one or more (only one is shown in the figure) processors 100 (the processor 100 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 200 for storing data, and a transmission module 300 for communication functions. It will be understood by those skilled in the art that Figure 4 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 4 More or fewer components shown in the figure may also include other processing hardware, such as a database or multi-level cache, GPU, or other hardware with Figure 4 Different configurations shown.

[0079] The memory 200 can be used to store software programs and modules of application software, such as the program instructions / modules corresponding to the data calling method in the embodiments of this specification. The processor 100 executes various functional applications and data processing by running the software programs and modules stored in the memory 200. The memory 200 may include a high-speed random access memory and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 200 may further include a memory remotely located relative to the processor 100, and these remote memories may be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0080] The transmission module 300 is used to receive or send data via a network. Specific examples of the aforementioned network may include a wireless network provided by a communications provider of a computer terminal. In one embodiment, the transmission module 300 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission module 300 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0081] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0082] The methods or devices described in the above embodiments provided in this specification can implement business logic through computer programs and record them on storage media, and the storage media can be read and executed by computers to achieve the effects of the solutions described in the embodiments of this specification. The storage medium may include a physical device for storing information, which is usually to digitize the information and then store it in a medium using electrical, magnetic or optical methods. The storage medium may include: devices that use electrical energy to store information, such as various types of memories, such as RAM, ROM, etc.; devices that use magnetic energy to store information, such as hard disks, floppy disks, magnetic tapes, magnetic core memories, bubble memories, and USB flash drives; devices that use optical methods to store information, such as CDs or DVDs. Of course, there are other types of readable storage media, such as quantum memories, graphene memories, and so on.

[0083] The above-mentioned data calling method or device embodiments provided in this specification can be implemented by a processor in a computer executing corresponding program instructions, such as using the C++ language of the Windows operating system to implement it on a PC, on a Linux system, or other systems such as Android or iOS system programming languages to implement it on a smart terminal, as well as based on the processing logic of a quantum computer.

[0084] It should be noted that the devices, equipment, and systems described above in the specification may also include other implementation methods based on the description of the relevant method embodiments. The specific implementation methods can refer to the description of the corresponding method embodiments and will not be described in detail here.

[0085] The various embodiments in this application are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, for the hardware + program embodiments, since they are basically similar to the method embodiments, the description is relatively simple. For relevant parts, refer to the partial description of the method embodiments.

[0086] For ease of description, the above devices are described in terms of their functions, divided into various modules. Of course, when implementing one or more of the present inventions, the functions of some modules may be implemented in the same or multiple software and / or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units.

[0087] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices, equipment, and systems according to embodiments of the present invention. It should be understood that it can be implemented by computer program instructions, and these computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing a specified function. These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which is implemented in the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0088] Those skilled in the art will appreciate that one or more embodiments of the present specification may be provided as methods, systems, or computer program products. Thus, one or more embodiments of the present specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware.

[0089] The foregoing is merely an example of one or more embodiments of this specification and is not intended to limit the one or more embodiments of this specification. It will be apparent to those skilled in the art that various modifications and variations may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application shall be included within the scope of the claims.

Claims

1. A data calling method, characterized in that: include: Receive business call requests; The service call request includes the XSD document corresponding to the target service; Determine the list of elements required for the target business based on the XSD document and the mapping script; the mapping script includes the mapping relationship between the elements in the BLAZE element menu and the elements in the XSD document; Based on the data query component corresponding to the element in the BLAZE element menu, obtain the data corresponding to each element in the element list; Assembling the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string; Calling the BLAZE decision engine of the big data center based on the XML string to obtain a decision result; The business information corresponding to the XSD document includes at least the business category, business subcategory, calling stage and business application number; The mapping script is generated in the following way: Obtain the BOM interface document and business-related XSD document provided by the Big Data Center; Classify the elements in the BOM interface document to obtain a BLAZE element menu; Configure a data query component for each element in the BLAZE element menu; Move the BLAZE element menu and the XSD document to a specified directory, and call a preset mapping tool to generate a mapping script based on the obtained business category, business subcategory, and calling stage; The data query component corresponding to the element in the BLAZE element menu is used to obtain the data corresponding to each element in the element list, including: Traversing each element group, where the element group is obtained by grouping elements in the element list that have the same number retrieval logic into one group; Based on the business application number, the corresponding data query component in the BLAZE element menu is called using the JAVA reflection mechanism to obtain a componentized Response object; the componentized Response object includes each element in the element list and the data corresponding to each element.

2. The method according to claim 1, characterized in that Determining a list of elements required for the target business based on the XSD document and mapping script includes: Obtaining a corresponding mapping script from the BLAZE parameter mapping table according to the business information corresponding to the XSD document; the business information at least includes a business category, a business subcategory, and a call stage; Based on the XSD document and the mapping script, a list of elements required for the target business is determined.

3. The method according to claim 2, characterized in that Before obtaining the data corresponding to each element in the element list based on the data query component corresponding to the element in the BLAZE element menu, the method includes: The elements in the element list are grouped according to the data retrieval logic corresponding to the elements to obtain different element groups.

4. The method according to claim 1, wherein The data query component includes at least one of the following: a local query component and an external query component; the local query component includes at least one of the following: a credit card application information component, a new generation installment information component, a home improvement installment calculation component, and a home improvement installment entry component; the external query component includes at least one of the following: a gray list query component, a credit inquiry component, a Bairong credit score query component, a Bairong fraud score query component, a China Credit blacklist query component, a China Higher Education Student Information and Career Center academic qualification query component, and a China Higher Education Student Information and Career Center academic status comparison query component.

5. The method according to claim 1, wherein After generating the mapping script, the following steps are also included: The mapping script is submitted and deployed into the BLAZE parameter mapping table.

6. A data calling device, characterized in that: include: Receiving module, used to receive service call requests; The service call request includes the XSD document corresponding to the target service; A determination module, configured to determine a list of elements required for a target business based on the XSD document and a mapping script; the mapping script includes a mapping relationship between elements in a BLAZE element menu and elements in an XSD document; An acquisition module, configured to acquire data corresponding to each element in the element list based on a data query component corresponding to an element in the BLAZE element menu; A generating module, configured to assemble the element list and the data corresponding to each element in the element list according to the format of the XSD document to generate an XML string; An acquisition module is used to call the BLAZE decision engine of the big data center based on the XML string to obtain a decision result; The business information corresponding to the XSD document includes at least the business category, business subcategory, calling stage and business application number; The mapping script is generated in the following way: Obtain the BOM interface document and business-related XSD document provided by the Big Data Center; Classify the elements in the BOM interface document to obtain a BLAZE element menu; Configure a data query component for each element in the BLAZE element menu; Move the BLAZE element menu and the XSD document to a specified directory, and call a preset mapping tool to generate a mapping script based on the obtained business category, business subcategory, and calling stage; The acquisition module is specifically used to: traverse each element group, where the element group is obtained by grouping elements in the element list with the same data retrieval logic; based on the business application number, use the JAVA reflection mechanism to call the corresponding data query component in the BLAZE element menu to obtain a componentized Response object; the componentized Response object includes each element in the element list and the data corresponding to each element.

7. A data calling device, characterized in that: The method comprises at least one processor and a memory storing computer-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 5 when executing the instructions.

8. A computer-readable storage medium, characterized in that Computer instructions are stored thereon, and when the instructions are executed, the steps of the method according to any one of claims 1 to 5 are implemented.

Images