CN110704545A - Data calling method and device for data source provider - Google Patents
Data calling method and device for data source provider Download PDFInfo
- Publication number
- CN110704545A CN110704545A CN201910868163.4A CN201910868163A CN110704545A CN 110704545 A CN110704545 A CN 110704545A CN 201910868163 A CN201910868163 A CN 201910868163A CN 110704545 A CN110704545 A CN 110704545A
- Authority
- CN
- China
- Prior art keywords
- data source
- calling
- data
- provider
- source provider
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- 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
Abstract
The application discloses a data calling method and device for a data source supplier. The method comprises the following steps: marking a calling state label for a data source supplier according to a first preset rule; setting the calling priority of the data source supplier according to a second preset rule, wherein the calling priority refers to the calling sequence of the data source supplier; receiving a data calling request of a user; and determining the calling result of the data source supplier according to the calling state label and the calling priority, and returning the calling result to the user. The method and the device solve the technical problem that stable data calling service cannot be provided for the user due to the fact that effective management is not conducted on a data source provider in a data calling method in the related technology. By the method and the device, the purpose of effectively managing the data source supplier is achieved, and therefore the technical effect of providing stable data calling service for the user is achieved.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a data calling method and apparatus for a data source provider.
Background
Although the internet financial industry in China is rapidly developed at present, credit investigation systems are still unsound, personal credit investigation data are scattered in consumption main bodies such as a central bank credit investigation center, large non-bank financial institutions and operators and electronic commerce, and any single data source cannot accurately evaluate users. In order to better serve users and control risks, a consuming body needs to cooperate with an external data source to meet the requirement of judging user risks from multiple dimensions and multiple perspectives.
The mature data types in the related art are relatively concentrated and have certain homogeneity and replaceability. There may be multiple vendors supporting the same type of data. The inventor finds that the data calling method in the related art has at least the following problems: the data source suppliers are not configured and managed effectively, and when a supplier of a certain data source cannot provide services, other suppliers cannot be replaced in time to meet the data calling requirements of users, so that the normal operation of services is ensured.
Aiming at the problem that a data calling method in the related art cannot provide stable data calling service for a user due to the lack of effective management on a data source provider, an effective solution is not provided at present.
Disclosure of Invention
The present application mainly aims to provide a data calling method and apparatus for a data source provider, so as to solve the problem that a data calling method in the related art cannot provide a stable data calling service for a user due to lack of effective management on the data source provider.
To achieve the above object, according to one aspect of the present application, there is provided a data calling method for a data source provider.
The data calling method for the data source supplier comprises the following steps: marking a calling state label for a data source supplier according to a first preset rule, wherein the calling state label is a label used for representing whether the data source supplier can be called or not; setting the calling priority of the data source supplier according to a second preset rule, wherein the calling priority refers to the calling sequence of the data source supplier; receiving a data calling request of a user; and determining the calling result of the data source supplier according to the calling state label and the calling priority, and returning the calling result to the user.
Further, the marking and calling the status label for the data source supplier according to the first preset rule includes: determining whether the data source provider can be invoked; if the data source provider can be called, marking a callable status tag for the data source provider; if the data source provider is not invokable, the data source provider is marked with a non-invokable status tag.
Further, the marking and calling the status label for the data source supplier according to the first preset rule includes: monitoring the calling condition of the data source supplier in a preset time period; if the data source supplier cannot be called or the calling times of the data source supplier exceed a preset threshold, marking a non-calling state label for the data source supplier; and determining whether to release the non-invokable status label of the data source supplier according to the manual rechecking result.
Further, after the marking and calling the status label for the data source supplier according to the first preset rule, the method includes: establishing a corresponding relation between the data source supplier and the user according to a third preset rule; storing the corresponding relation into a relational database; and calling the data source supplier corresponding to the user in the relational database according to the data calling request of the user.
Further, after receiving the data call request of the user, the method further includes: determining a data source supplier matched with the data calling request according to the data calling request of the user; identifying a call status tag of the data source provider; determining the calling priority of the data source supplier according to the identification result; and returning the calling result of the data source supplier to the user according to the calling priority.
Further, the determining the calling result of the data source provider according to the calling state tag and the calling priority and returning the calling result to the user includes: monitoring the calling result of the data source supplier; and judging whether the calling priority of the data source supplier needs to be adjusted or not according to the monitoring result.
To achieve the above object, according to another aspect of the present application, there is provided a data call apparatus for a data source provider.
The data calling device for the data source supplier comprises: the system comprises a marking module, a data source supplier and a data source module, wherein the marking module is used for marking a calling state label for the data source supplier according to a first preset rule, and the calling state label is a label used for representing whether the data source supplier can be called or not; the setting module is used for setting the calling priority of the data source supplier according to a second preset rule, wherein the calling priority refers to the sequence of calling the data source supplier; the receiving module is used for receiving a data calling request of a user; and the first determining module is used for determining the calling result of the data source supplier according to the calling state label and the calling priority and returning the calling result to the user.
Further, the marking module includes: a judging unit, configured to judge whether the data source provider can be called; a first marking unit for marking the data source provider with an invokable status tag if the data source provider can be invoked; a second marking unit, configured to mark a non-invokable status tag for the data source provider if the data source provider is not invokable.
Further, the marking module includes: the monitoring unit is used for monitoring the calling condition of the data source supplier in a preset time period; a third marking unit, configured to mark an invokable status tag for the data source provider if the data source provider is not invokable or the number of invocations of the data source provider exceeds a preset threshold; and the releasing unit is used for determining whether to release the invokable state label of the data source supplier according to the result of the manual review.
Further, still include: the establishing module is used for establishing a corresponding relation between the data source supplier and the user according to a third preset rule; the storage module is used for storing the corresponding relation into a relational database; and the calling module is used for calling the data source supplier corresponding to the user in the relational database according to the data calling request of the user.
In the embodiment of the application, a calling state label is marked for a data source provider according to a first preset rule, wherein the calling state label is a label used for representing whether the data source provider can be called or not; setting the calling priority of the data source supplier according to a second preset rule, wherein the calling priority refers to the calling sequence of the data source supplier and receives a data calling request of a user; and determining a calling result of the data source provider according to the calling state label and the calling priority, and returning the calling result to the user, so that the aim of effectively managing the data source provider is fulfilled, the technical effect of providing stable data calling service for the user is realized, and the technical problem that the stable data calling service cannot be provided for the user due to the lack of effective management on the data source provider in the data calling method in the related technology is solved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, serve to provide a further understanding of the application and to enable other features, objects, and advantages of the application to be more apparent. The drawings and their description illustrate the embodiments of the invention and do not limit it. In the drawings:
FIG. 1 is a schematic flow chart diagram of a data call method for a data source provider according to a first embodiment of the present application;
FIG. 2 is a schematic flow chart diagram of a data call method for a data source provider according to a second embodiment of the present application;
FIG. 3 is a flowchart illustration of a data invocation method for a data source provider according to a third embodiment of the present application;
FIG. 4 is a schematic flow chart diagram of a data call method for a data source provider according to a fourth embodiment of the present application;
FIG. 5 is a schematic flow chart diagram of a data call method for a data source provider according to a fifth embodiment of the present application;
FIG. 6 is a flowchart illustrating a data call method for a data source provider according to a sixth embodiment of the present application;
fig. 7 is a schematic diagram of a component structure of a data calling device for a data source provider according to a first embodiment of the present application;
fig. 8 is a schematic diagram of a component structure of a data calling device for a data source provider according to a second embodiment of the present application; and
fig. 9 is a schematic diagram of a component structure of a data call device for a data source provider according to a third embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be used. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
According to an embodiment of the present invention, there is provided a data calling method for a data source provider, as shown in fig. 1, the method includes steps S101 to S104 as follows:
step S101, according to a first preset rule, a calling state label is marked for a data source supplier, wherein the calling state label is a label used for representing whether the data source supplier can be called or not.
In specific implementation, a data source provider in the embodiment of the present application refers to a main body providing services such as data source calling, in order to ensure stability of a user calling a data source, at least two online providers need to provide calling services for each type of data, and once a main channel cannot provide services due to an accident, a standby channel can be switched online immediately, thereby ensuring normal operation of company services.
The provider of the data source typically has an unavailability for some time during the day-to-day service, which typically occurs in two ways. The first case is that the supplier system upgrade actively informs the user that the service will be upgraded in a certain period of time, at which time the service will not be available; the second situation is that the service of the provider is not available due to the abnormality of the system of the provider or the network, and the occurrence time of the situation is generally unpredictable. Therefore, for the above two cases, in order to make the service of the data source stable and reliable, the data source provider needs to be first marked with the call status tag according to a certain preset rule, that is, used for marking whether the data source provider can provide the data call service.
Step S102, setting the calling priority of the data source supplier according to a second preset rule, wherein the calling priority refers to the sequence of the data source supplier being called.
In specific implementation, when multiple suppliers exist in the same data source, the system is required to select the most suitable supplier to prioritize service, and for how to prioritize the suppliers, the calling priority of the data source supplier can be set in the following three ways to meet complex business logic. The first mode is a priority mode, which can manually sort and identify the priority for the suppliers of the same data source, and when the selection mode of the data source is the priority mode, the supplier with higher priority is preferentially selected to serve. The second way is a routing way, that is, the information of the data source supplier and the information of some query requests, such as user information, request time, etc. can be used as input items to enter the route, and the supplier a is selected under a certain condition and the supplier B is selected under another condition by configuring routing rules. For example, vendor a is selected when the user locates the address in shanghai city, and vendor B is selected when the user locates the address in other cities. The application scene of the application can be greatly expanded through a routing mode. The third mode may be a rule mode, that is, a rule file is written to select a provider, and compared with the second routing mode, the third mode is more flexible and variable, and the adaptive scenario is more complex.
Step S103, receiving a data calling request of a user.
In a specific implementation, the data call of the data source provider is triggered by a data call request initiated by a user, and the data call request initiated by the user further may include a data type of the call, information of the data source provider to be called, and the like.
And step S104, determining the calling result of the data source supplier according to the calling state label and the calling priority, and returning the calling result to the user.
During specific implementation, a data source provider matched with a call request of a user is searched in a preset database by identifying the data call request initiated by the user, then whether the data call service of the data source provider is available or not is judged according to the call state label of the data source provider, and if the unavailable label is marked on the provider, the provider can be automatically switched to the available provider to serve as a data source service party. If the number of the available data source providers is multiple, the calling priority of the available data source providers is further judged, the data source providers with high calling priority are called preferentially, and finally the final calling result of the data source provider is determined by integrating the calling state label and the judging result of the calling priority and is sent to the client.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 2, the marking and calling a status label for a data source provider according to a first preset rule includes steps S201 to S203 as follows:
step S201, determining whether the data source provider can be called.
In particular, the provider of the data source will typically have an unavailable status for a certain period of time during the daily service, which typically occurs in two ways. The first case is that the supplier system upgrade actively informs the user that the service will be upgraded in a certain period of time, at which time the service will not be available; the second situation is that the service of the provider is not available due to the abnormality of the system of the provider or the network, and the occurrence time of the situation is generally unpredictable. Therefore, before data call is performed, it is first necessary to determine whether the data source provider has the above-mentioned non-callable condition within a certain time period, so as to determine which data source providers are callable and which are non-callable within the time period.
Step S202, if the data source supplier can be called, the data source supplier is marked with a calling state label.
In specific implementation, if the calling state of the data source provider in a certain time period is found to be normal through the judgment, that is, the data source provider can be called, the data source provider is marked with a label that can be called.
Step S203, if the data source provider cannot be called, marking a non-callable status tag for the data source provider.
In specific implementation, if it is found through the above determination that the calling state of the data source provider is abnormal within a certain time period, such as the above listed condition that the data source provider cannot be called, the data source provider is marked with a label that the data source provider cannot be called.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 3, the marking and calling the status label for the data source provider according to the first preset rule includes steps S301 to S303 as follows:
step S301, monitoring the calling condition of the data source provider within a preset time period.
In a specific implementation, the calling condition of each data source provider needs to be monitored within a certain time period, where the calling condition may include whether each data source provider can be called within the time period, the number of times of being called, and the like.
Step S302, if the data source provider cannot be called or the number of times of calling of the data source provider exceeds a preset threshold, marking a non-callable status tag for the data source provider.
In specific implementation, when the calling condition of the data source provider has the abnormal condition that the data source provider cannot be called as listed above, or the calling frequency exceeds a warning value, namely the calling is excessively called, and the like, the unavailable state label is automatically marked for the data source provider.
Step S303, determining whether to release the invokable status label of the data source supplier according to the result of the manual review.
In specific implementation, the unavailable status tag of the data source provider can be set to be released after manual review, that is, whether the calling status of the data source provider is normal or not is determined through manual check, and if the calling status of the data source provider is normal, the unavailable status tag of the data source provider is released.
In addition to the automatic marking mode of the data source supplier, a manual marking mode can be adopted, namely, labels which cannot be used are marked on the supplier manually, and the labels which cannot be used of the supplier can be deleted manually after the supplier service can be used.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 4, after the step of marking and calling the status label for the data source provider according to the first preset rule, the following steps S401 to S403 are included:
step S401, establishing a corresponding relationship between the data source provider and the user according to a third preset rule.
In specific implementation, the corresponding relationship between each data source provider and the user requesting to invoke data may be established according to a certain rule, for example, the information of each data source provider, the information of the user sending the query request or the invocation request, the request time, and the like are simply used as the input entry incoming route, the provider a is selected under a certain condition by configuring the routing rule, and the provider B is selected under another condition. The corresponding relationship between the data source provider and the geographical position of the user who initiates the request can be established, for example, when the user location address is in Shanghai city, the data source provider A corresponding to the user location address is selected, and when the user location address is in other cities, the data source provider B corresponding to the user location address is selected. The application scene of the application can be greatly expanded by configuring the routing rule.
Step S402, storing the corresponding relation into a relational database.
During specific implementation, the established corresponding relation between the data source supplier and the user is stored in a relational database, so that the data source supplier matched with the user request can be conveniently and quickly called in the following process.
Step S403, according to the data call request of the user, calling the data source provider corresponding to the user in the relational database.
In specific implementation, after receiving a call request of a user, a data source provider corresponding to the call request is called in a database based on request information of the user, specifically, before the call, the call state of the data source provider also needs to be judged, and when a plurality of data source providers can be called, the priority condition of each data source provider, and the data source provider with a high priority level, is called preferentially.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 4, after receiving a data call request of a user, the following steps S501 to S504 are further included:
step S501, determining a data source supplier matched with the data calling request according to the data calling request of the user.
In specific implementation, the data source information requested to be called by the user needs to be determined, and the data source information is queried in a preset data source provider database according to the data source information to obtain one or more data source providers matched with the data calling request of the user.
Step S502, identifying the calling state label of the data source supplier.
In specific implementation, when one or more data source providers all have data source information requested by a user, it is first required to determine whether the one or more data source providers are in a callable service state, that is, whether the data source provider can be called is determined by identifying a call state tag marked before.
Step S503, determining the calling priority of the data source supplier according to the identification result.
In specific implementation, if it is recognized that all the call status tags of the multiple data source providers are call status tags, it indicates that all the multiple data source providers can provide data source call services for the user, and further determines the call priorities of the data source providers, and the data source provider with the higher call priority level is called preferentially. If the calling status labels of some data source suppliers are identified as non-callable status labels, the judgment of calling priority level is not carried out.
And step S504, returning the calling result of the data source supplier to the user according to the calling priority.
In specific implementation, which data source provider or data source providers are preferentially called is determined according to the preset judgment rule of calling priority, such as the priority mode, the configuration routing mode and the writing rule file mode, and the finally determined data source provider to be called is sent to the user.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 6, after determining the invocation result of the data source provider according to the invocation status tag and the invocation priority, and returning the invocation result to the user, the following steps S601 to S602 are included:
step S601, monitoring a calling result of the data source provider.
In the specific implementation, the call priorities of all data source providers are not constant, and the call priorities of the data source providers may be changed along with the adjustment of the service capability of the data source providers due to the change of the services and the adjustment of the service capability of the data source providers, so that the call condition of each data source provider needs to be monitored regularly or irregularly.
Step S602, determining whether the call priority of the data source provider needs to be adjusted according to the monitoring result.
In specific implementation, if a call request of a user is rejected by a certain data source provider for multiple times, or the number of times of call failures of the certain data source provider within a certain time period reaches a preset threshold, it indicates that the data source provider has poor capability of providing data source call service within the time period, and automatically adjusts the call priority of the data source provider, specifically, the call priority of the data source provider is reduced, the degraded data source provider can restore the previous call priority or improve the call priority in a manual review mode, and the data call process is more efficient and stable by integrating the results of the manual review and the automatic adjustment of the priority.
From the above description, it can be seen that the present invention achieves the following technical effects: marking a calling state label for a data source supplier according to a first preset rule; setting the calling priority of the data source supplier according to a second preset rule; the calling result of the data source provider is determined according to the calling state label and the calling priority, and the calling result is returned to the user, so that the purpose of effectively managing the data source provider is achieved, the data source provider is efficiently and automatically screened, a stable data calling service is provided for the user, the payment cost of a company is effectively reduced, the method and the system have higher safety and flexible service expansibility, and system stability, and better experience is brought to the user.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than presented herein.
According to an embodiment of the present invention, there is also provided an apparatus for implementing the data call method for a data source provider, as shown in fig. 7, the apparatus includes: the device comprises a marking module 1, a setting module 2, a receiving module 3 and a first determining module 4.
The marking module 1 in the embodiment of the application is configured to mark a calling status label for a data source provider according to a first preset rule, where the calling status label is a label used for characterizing whether the data source provider can be called.
In specific implementation, a provider of a data source usually has an unavailable state for a certain time in a daily service process, and therefore, in order to make the service of the data source stable and reliable, a calling state tag needs to be marked for the provider of the data source according to a certain preset rule through a marking module, that is, the marking module is used for marking whether the provider of the data source can provide the data calling service.
The setting module 2 in this embodiment is configured to set a call priority of the data source provider according to a second preset rule, where the call priority refers to an order in which the data source provider is called.
In specific implementation, when multiple suppliers exist in the same data source, the system is required to select the most suitable supplier to prioritize service, and for how to prioritize the suppliers, the setting module can set the calling priority of the data source supplier according to the following three ways to meet complex business logic. The first mode is a priority mode, the second mode is a configuration routing mode, and the third mode can be a writing rule file mode.
The receiving module 3 in the embodiment of the application is configured to receive a data call request of a user.
In specific implementation, the data call of the data source provider is triggered by a data call request initiated by a user, the data call request initiated by the user further may include a data type of the call, information of the data source provider to be called, and the like, and the data call request of the user is received by the receiving module to obtain the information.
The first determining module 4 of the embodiment of the application determines the calling result of the data source provider according to the calling state tag and the calling priority, and returns the calling result to the user.
During specific implementation, a data source provider matched with a call request of a user is searched in a preset database by identifying the data call request initiated by the user, then whether the data call service of the data source provider is available or not is judged according to the call state label of the data source provider, and if the unavailable label is marked on the provider, the provider can be automatically switched to the available provider to serve as a data source service party. If the number of the available data source providers is multiple, the calling priority of the available data source providers is further judged, the data source providers with high calling priority are called preferentially, and finally the final calling result of the data source provider is determined by the comprehensive calling state label and the judgment result of the calling priority through the first determination module and is sent to the client.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 8, the marking module 1 includes: a judging unit 11, a first marking unit 12 and a second marking unit 13.
The determining unit 11 in this embodiment of the application is configured to determine whether the data source provider can be called.
In a specific implementation, a data source provider usually has an unavailable state for a certain time in a daily service process, and therefore, before data call is performed, it is first required to determine whether the data source provider has the above-mentioned unavailable condition or not by using a determination unit within a certain time period, so as to determine which data source providers are available and which are unavailable within the time period.
The first marking unit 12 of the embodiment of the present application is configured to mark an invokable status label for the data source provider if the data source provider can be invoked.
In specific implementation, if the calling state of the data source provider within a certain time period is found to be normal through the above judgment, that is, the data source provider can be called, the first marking unit is used to mark a label that can be called for the data source provider.
The second marking unit 13 in this embodiment of the application is configured to mark the data source provider with a non-invokable status tag if the data source provider is not invokable.
In specific implementation, if it is found through the above determination that the calling state of the data source provider in a certain time period is abnormal, i.e. cannot be called, as in the above two cases, the data source provider is tagged with an invokable label through the second tagging unit.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 8, the marking module 1 includes: a monitoring unit 14, a third marking unit 15 and a releasing unit 16.
The monitoring unit 14 according to the embodiment of the present application is configured to monitor a calling condition of the data source provider within a preset time period.
In a specific implementation, the calling condition of each data source provider needs to be monitored by the monitoring unit within a certain time period, where the calling condition may include whether each data source provider can be called within the time period, the number of times of being called, and the like.
The third marking unit 15 in this embodiment is configured to mark the status label of non-invokable data source provider if the data source provider is not invokable or the number of invocations of the data source provider exceeds a preset threshold.
In specific implementation, when the calling condition of the data source provider has the abnormal condition that the data source provider cannot be called as listed above, or the calling frequency exceeds a warning value, that is, the data source provider is excessively called, and the like, the unavailable status tag is automatically marked for the data source provider through the third marking unit.
The releasing unit 16 in the embodiment of the present application is configured to determine whether to release the invokable status tag of the data source provider according to a result of the manual review.
In specific implementation, the unavailable status tag of the data source provider can be set to be released after manual review, that is, whether the calling status of the data source provider is normal or not is determined through manual check, and if the calling status of the data source provider is normal, the unavailable status tag of the data source provider is released through the releasing unit.
As a preferred implementation of the embodiment of the present application, as shown in fig. 9, the apparatus further includes: the device comprises a building module 5, a storage module 6 and a calling module 7.
The establishing module 5 in the embodiment of the present application is configured to establish a corresponding relationship between the data source provider and the user according to a third preset rule.
In specific implementation, the establishing module may establish a corresponding relationship between each data source provider and a user requesting to invoke data according to a certain rule, for example, simply use information of each data source provider, information of a user sending an inquiry request or an invocation request, request time, and the like as input items to enter a route, select provider a under a certain condition by configuring a routing rule, and select provider B under another condition. The corresponding relationship between the data source provider and the geographical position of the user who initiates the request can be established, for example, when the user location address is in Shanghai city, the data source provider A corresponding to the user location address is selected, and when the user location address is in other cities, the data source provider B corresponding to the user location address is selected. The application scene of the application can be greatly expanded by configuring the routing rule.
The storage module 6 of the embodiment of the application is configured to store the corresponding relationship in a relationship database.
During specific implementation, the established corresponding relation between the data source supplier and the user is stored in a relational database through a storage module, so that the data source supplier matched with the user request can be conveniently and quickly called in the following process.
The invoking module 7 in the embodiment of the application is configured to invoke, according to the data invoking request of the user, the data source provider corresponding to the user in the relational database.
In specific implementation, after receiving a call request of a user, a data source provider corresponding to the call request is called in a database through a call module based on the request information of the user, specifically, before the call, the call state of the data source provider also needs to be judged, and when a plurality of data source providers can be called, the priority condition of each data source provider, the data source provider with a high priority level, is called preferentially.
As a preferred implementation of the embodiment of the present application, the apparatus further includes: the device comprises a matching module, an identification module, a second determination module and a return module.
And the matching module is used for determining a data source supplier matched with the data calling request according to the data calling request of the user.
In specific implementation, the data source information requested to be called by the user needs to be determined through the matching module, and the data source information is queried in a preset data source provider database according to the data source information, so that one or more data source providers matched with the data calling request of the user are obtained.
And the identification module is used for identifying the calling state label of the data source supplier.
In specific implementation, when one or more data source providers all have data source information requested by a user, first, it is necessary to determine, by an identification module, whether the one or more data source providers are in a callable service state, that is, determine, by identifying a call state tag marked before, whether the data source provider can be called.
And the second determining module is used for determining the calling priority of the data source supplier according to the identification result.
In specific implementation, if it is recognized that all the call status tags of the multiple data source providers are call status tags, indicating that all the multiple data source providers can provide data source call services for the user, the call priorities of the data source providers are further determined by the second determination module, and the data source provider with the higher call priority level is called preferentially. If the calling status labels of some data source suppliers are identified as non-callable status labels, the judgment of calling priority level is not carried out.
And the return module is used for returning the calling result of the data source supplier to the user according to the calling priority.
In specific implementation, which data source provider or data source providers are preferentially called is determined according to the preset judgment rule of calling priority, such as the priority mode, the configuration routing mode and the writing rule file mode, and the finally determined and called data source provider is sent to the user through the return module.
As a preferred implementation of the embodiment of the present application, the apparatus further includes: the device comprises a monitoring module and an adjusting module.
And the monitoring module is used for monitoring the calling result of the data source supplier.
In a specific implementation, the call priorities of all data source providers may not be the same, and the call priorities of the data source providers may be changed along with the adjustment of the service capability of the data source providers due to the change of the service, and the like, so that the call condition of each data source provider needs to be monitored regularly or irregularly by the monitoring module.
And the adjusting module is used for judging whether the calling priority of the data source supplier needs to be adjusted or not according to the monitoring result.
In specific implementation, if a call request of a user is rejected by a certain data source provider for multiple times, or the number of times of call failures of the certain data source provider within a certain time period reaches a preset threshold, it indicates that the data source provider has poor capability of providing data source call service within the time period, the call priority of the data source provider is automatically adjusted through an adjustment module, specifically, the call priority of the data source provider is reduced, the degraded data source provider can restore the previous call priority or improve the call priority in a manual review mode, and the data call process is more efficient and stable by integrating results of the manual review and the automatic adjustment of the priority.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (10)
1. A data invocation method for a data source provider, comprising:
marking a calling state label for a data source supplier according to a first preset rule, wherein the calling state label is a label used for representing whether the data source supplier can be called or not;
setting the calling priority of the data source supplier according to a second preset rule, wherein the calling priority refers to the calling sequence of the data source supplier;
receiving a data calling request of a user;
and determining the calling result of the data source supplier according to the calling state label and the calling priority, and returning the calling result to the user.
2. The data call method for the data source provider according to claim 1, wherein the marking the call state tag for the data source provider according to the first preset rule comprises:
determining whether the data source provider can be invoked;
if the data source provider can be called, marking a callable status tag for the data source provider;
if the data source provider is not invokable, the data source provider is marked with a non-invokable status tag.
3. The data call method for the data source provider according to claim 1, wherein the marking the call state tag for the data source provider according to the first preset rule comprises:
monitoring the calling condition of the data source supplier in a preset time period;
if the data source supplier cannot be called or the calling times of the data source supplier exceed a preset threshold, marking a non-calling state label for the data source supplier;
and determining whether to release the non-invokable status label of the data source supplier according to the manual rechecking result.
4. The data calling method for the data source provider according to claim 1, wherein the marking the calling status tag for the data source provider according to the first preset rule comprises:
establishing a corresponding relation between the data source supplier and the user according to a third preset rule;
storing the corresponding relation into a relational database;
and calling the data source supplier corresponding to the user in the relational database according to the data calling request of the user.
5. The data call method for the data source provider according to claim 1, further comprising, after receiving the data call request from the user:
determining a data source supplier matched with the data calling request according to the data calling request of the user;
identifying a call status tag of the data source provider;
determining the calling priority of the data source supplier according to the identification result;
and returning the calling result of the data source supplier to the user according to the calling priority.
6. The data calling method for the data source provider according to claim 1, wherein the determining the calling result of the data source provider according to the calling status tag and the calling priority and returning the calling result to the user comprises:
monitoring the calling result of the data source supplier;
and judging whether the calling priority of the data source supplier needs to be adjusted or not according to the monitoring result.
7. A data invocation mechanism for a data source provider, comprising:
the system comprises a marking module, a data source supplier and a data source module, wherein the marking module is used for marking a calling state label for the data source supplier according to a first preset rule, and the calling state label is a label used for representing whether the data source supplier can be called or not;
the setting module is used for setting the calling priority of the data source supplier according to a second preset rule, wherein the calling priority refers to the sequence of calling the data source supplier;
the receiving module is used for receiving a data calling request of a user;
and the first determining module is used for determining the calling result of the data source supplier according to the calling state label and the calling priority and returning the calling result to the user.
8. The data invocation device for a data source provider according to claim 7, wherein said tagging module comprises:
a judging unit, configured to judge whether the data source provider can be called;
a first marking unit for marking the data source provider with an invokable status tag if the data source provider can be invoked;
a second marking unit, configured to mark a non-invokable status tag for the data source provider if the data source provider is not invokable.
9. The data invocation device for a data source provider according to claim 7, wherein said tagging module comprises:
the monitoring unit is used for monitoring the calling condition of the data source supplier in a preset time period;
a third marking unit, configured to mark an invokable status tag for the data source provider if the data source provider is not invokable or the number of invocations of the data source provider exceeds a preset threshold;
and the releasing unit is used for determining whether to release the invokable state label of the data source supplier according to the result of the manual review.
10. The data invocation device for data source providers according to claim 7, further comprising:
the establishing module is used for establishing a corresponding relation between the data source supplier and the user according to a third preset rule;
the storage module is used for storing the corresponding relation into a relational database;
and the calling module is used for calling the data source supplier corresponding to the user in the relational database according to the data calling request of the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910868163.4A CN110704545B (en) | 2019-09-12 | 2019-09-12 | Data calling method and device for data source provider |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910868163.4A CN110704545B (en) | 2019-09-12 | 2019-09-12 | Data calling method and device for data source provider |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110704545A true CN110704545A (en) | 2020-01-17 |
| CN110704545B CN110704545B (en) | 2022-06-07 |
Family
ID=69196072
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910868163.4A Active CN110704545B (en) | 2019-09-12 | 2019-09-12 | Data calling method and device for data source provider |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110704545B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6069882A (en) * | 1997-07-30 | 2000-05-30 | Bellsouth Intellectual Property Corporation | System and method for providing data services using idle cell resources |
| US20140108474A1 (en) * | 2012-10-16 | 2014-04-17 | Rackspace Us, Inc. | System and Method for Exposing Cloud Stored Data to a Content Delivery Network |
| CN105159669A (en) * | 2015-08-13 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Method and system for orderly processing multiple Ajax data sources |
| CN105190532A (en) * | 2013-03-13 | 2015-12-23 | 高通股份有限公司 | Hierarchical orchestration of data providers for the retrieval of point of interest metadata |
| CN106557307A (en) * | 2015-09-29 | 2017-04-05 | 腾讯科技（深圳）有限公司 | The processing method and processing system of business datum |
| CN106649638A (en) * | 2016-12-08 | 2017-05-10 | 贵州数据宝网络科技有限公司 | Big data acquisition method |
| CN107729460A (en) * | 2017-09-30 | 2018-02-23 | 上海数据交易中心有限公司 | Data query method and device, storage medium, terminal |
| CN107748792A (en) * | 2017-11-01 | 2018-03-02 | 上海数据交易中心有限公司 | Data retrieval method and device, terminal |
| CN109995833A (en) * | 2017-12-29 | 2019-07-09 | 顺丰科技有限公司 | Voice service providing method, server, client, system, equipment and medium |
-
2019
- 2019-09-12 CN CN201910868163.4A patent/CN110704545B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6069882A (en) * | 1997-07-30 | 2000-05-30 | Bellsouth Intellectual Property Corporation | System and method for providing data services using idle cell resources |
| US20140108474A1 (en) * | 2012-10-16 | 2014-04-17 | Rackspace Us, Inc. | System and Method for Exposing Cloud Stored Data to a Content Delivery Network |
| CN105190532A (en) * | 2013-03-13 | 2015-12-23 | 高通股份有限公司 | Hierarchical orchestration of data providers for the retrieval of point of interest metadata |
| CN105159669A (en) * | 2015-08-13 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Method and system for orderly processing multiple Ajax data sources |
| CN106557307A (en) * | 2015-09-29 | 2017-04-05 | 腾讯科技（深圳）有限公司 | The processing method and processing system of business datum |
| CN106649638A (en) * | 2016-12-08 | 2017-05-10 | 贵州数据宝网络科技有限公司 | Big data acquisition method |
| CN107729460A (en) * | 2017-09-30 | 2018-02-23 | 上海数据交易中心有限公司 | Data query method and device, storage medium, terminal |
| CN107748792A (en) * | 2017-11-01 | 2018-03-02 | 上海数据交易中心有限公司 | Data retrieval method and device, terminal |
| CN109995833A (en) * | 2017-12-29 | 2019-07-09 | 顺丰科技有限公司 | Voice service providing method, server, client, system, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110704545B (en) | 2022-06-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11586673B2 (en) | Data writing and reading method and apparatus, and cloud storage system | |
| CN111580977B (en) | Resource adjustment method and related equipment | |
| US20020052952A1 (en) | Service execution method and apparatus | |
| CN107451853B (en) | Method, device and system for real-time red packet distribution and storage medium | |
| CN112766907A (en) | Service data processing method and device and server | |
| JP6217644B2 (en) | Rule distribution server, event processing system, method and program | |
| US7974865B2 (en) | Systems and methods of managing assignments | |
| US20170289354A1 (en) | System and Method for Allocation And Management Of Shared Virtual Numbers | |
| CN112860342A (en) | Method, device, equipment, system and storage medium for microservice configuration | |
| CN103270520A (en) | Importance class based data management | |
| CN115757611A (en) | Big data cluster switching method and device, electronic equipment and storage medium | |
| US8726235B2 (en) | Telecom business-oriented taxonomy for reusable services | |
| CN110704545B (en) | Data calling method and device for data source provider | |
| CN116319810A (en) | Flow control method, device, equipment, medium and product of distributed system | |
| CN116192752A (en) | Service flow control method, device, electronic equipment and storage medium | |
| CN105956811A (en) | Unmanned supermarket inventory management system | |
| CN114006907A (en) | Service degradation method and device for distributed server, electronic equipment and medium | |
| CN110033145B (en) | Financial sharing job order separating method and device, equipment and storage medium | |
| CN114428913A (en) | Data management method, device, equipment and storage medium | |
| CN112685157A (en) | Task processing method and device, computer equipment and storage medium | |
| CN107909460B (en) | Position synchronization method, device, data center and storage medium | |
| US20150006347A1 (en) | Asset inventory system | |
| KR20200134589A (en) | Accomodation inventory integrated management server, mobile device and methods therefor | |
| US11687269B2 (en) | Determining data copy resources | |
| CN109034768A (en) | Finance allot method, apparatus, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |