CN113918660A - API asset management method and device, computer equipment and storage medium - Google Patents
API asset management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN113918660A CN113918660A CN202111111677.9A CN202111111677A CN113918660A CN 113918660 A CN113918660 A CN 113918660A CN 202111111677 A CN202111111677 A CN 202111111677A CN 113918660 A CN113918660 A CN 113918660A
- Authority
- CN
- China
- Prior art keywords
- target
- type
- capability
- api
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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
- G06F16/285—Clustering or classification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/22—Matching criteria, e.g. proximity measures
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Artificial Intelligence (AREA)
- Evolutionary Computation (AREA)
- Evolutionary Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Bioinformatics & Computational Biology (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Life Sciences & Earth Sciences (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application relates to the technical field of API asset management, and particularly discloses an API asset management method, an API asset management device, computer equipment and a storage medium. The method includes obtaining a target API asset; determining a type of service provided by the target API asset; matching a target capability type corresponding to the target API asset from a capability type library according to the service type, wherein a plurality of capability types are stored in the capability type library, and the capability types represent the attributes of the service types provided by the API assets; and marking the target API asset as the target capability type and storing the target API asset in the capability type library. According to the method, the newly added API assets are stored to the capability types corresponding to the attributes through the method, and the management efficiency of the API assets is improved.
Description
Technical Field
The present application relates to the technical field of API asset management, and in particular, to an API asset management method, apparatus, computer device, and storage medium.
Background
An API (Application Programming Interface) is a predefined Interface (e.g., function, HTTP Interface), or a convention for interfacing different components of a software system, which is used to provide an Application and a set of routines that a developer can access based on certain software or hardware, without accessing source code or understanding details of internal working mechanisms.
With the rise of open banks, the API interface is widely applied to the open bank mode, the bank provides the API interface to the outside, and the user calls the API interface to implement the transaction of the service. With the development of technology, the open range of open banks is continuously expanded, API interfaces are continuously increased, API assets are continuously increased along with the expansion of service range, how to efficiently manage API assets becomes an urgent task, and an efficient API asset management method does not exist at present.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an API asset management method, apparatus, computer device and storage medium.
An API asset management method, comprising:
acquiring a target API asset;
determining a type of service provided by the target API asset;
matching a target capability type corresponding to the target API asset from a capability type library according to the service type, wherein a plurality of capability types are stored in the capability type library, and the capability types represent the attributes of the service types provided by the API assets;
and marking the target API asset as the target capability type and storing the target API asset in the capability type library.
In one embodiment, the capability type library includes a basic service capability type and at least one capability type other than the basic service capability type.
In one embodiment, the step of determining the type of service provided by the target API asset comprises:
judging whether the service type provided by the target API asset belongs to basic service or not;
if not, judging whether the service type provided by the target API asset belongs to the technical service.
In one embodiment, the capability type library includes a basic service capability type, a technology capability type and an ecological capability type; the step of matching a target capability type corresponding to the target API asset from a capability type library according to the service type comprises:
when the service type provided by the target API asset belongs to the basic service, determining that the target capability type is the basic service capability type;
when the service type provided by the target API asset belongs to the technical service, determining that the target capability type is a scientific and technological capability type;
and when the service type provided by the target API asset does not belong to the basic service and does not belong to the technical service, determining that the target capability type is the ecological capability type.
In one embodiment, the step of marking the target API asset as the target capability type and storing the target API asset in the capability type library comprises:
determining a functional attribute of the target API asset;
matching a target function category corresponding to the target API asset from the target capability type according to the functional attribute of the target API asset;
and marking the target API assets as the target function categories and storing the target API assets in the target function categories.
In one embodiment, the target capability type has at least one level of target function class, and the level number of the target function class is proportional to the granularity of the target API asset.
An API asset management system comprising:
an acquisition module for acquiring a target API asset;
a determining module, configured to determine a service type provided by the target API asset;
the matching module is used for matching a target capability type corresponding to the API asset from a capability type library according to the service type, wherein a plurality of capability types are stored in the capability type library, and the capability types represent the attributes of the service types provided by the API assets;
and the storage module is used for marking the target API asset as the target capability type and storing the target API asset into the capability type library.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the API asset management method described above when the computer program is executed.
A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, carries out the steps of the API asset management method described above.
A computer program product comprising a computer program which, when executed by a processor, carries out the steps of the API asset management method described above.
According to the API asset management method, the target capability type corresponding to the target API asset is matched from the capability type library according to the service type provided by the target API asset, the target API asset is marked as the target capability type, the target API asset is stored in the target capability type in the capability type library, the unified management of the newly added API asset is realized, a plurality of capability types are stored in the capability type library in advance, and each capability type has the API asset with the same attribute, so that the newly added API asset is searched from the capability type library, matched with the target capability type with the corresponding attribute and stored in the target capability type by the method, the searching, matching and storing rate is improved, and the management efficiency of the API asset is improved.
Drawings
FIG. 1 is a block flow diagram of an API asset management method provided by an embodiment of the present application;
FIG. 2 is a diagram illustrating a structure of a capability type library according to an embodiment of the present application;
FIG. 3 is a block flow diagram of an API asset management system provided by an embodiment of the present application;
fig. 4 is a schematic internal structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
To facilitate an understanding of the present application, the present application will now be described more fully with reference to the accompanying drawings. Preferred embodiments of the present application are given in the accompanying drawings. This application may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
In this application, unless expressly stated or limited otherwise, the terms "mounted," "connected," "secured," and the like are to be construed broadly and can include, for example, fixed connections, removable connections, or integral parts; can be mechanically or electrically connected; they may be directly connected or indirectly connected through intervening media, or they may be connected internally or in any other suitable relationship, unless expressly stated otherwise. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate.
The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
In one embodiment, an API asset management method is provided. The method is used for unified management of the API assets and can be applied to a server side.
Referring to fig. 1, the API asset management method provided in this embodiment includes the following steps:
and step S200, acquiring a target API asset.
As the open scope of open banks continues to expand, the number and variety of API assets continues to increase. Before the newly added API assets are put into use formally, the newly added API assets need to be managed in a unified mode. Wherein, the target API asset refers to the current new API asset.
And S400, determining the service type provided by the target API asset.
After determining the newly added API asset, that is, the target API asset, the service type provided by the target API asset is determined, and the determination of the service type may be determined in combination with the service scenario, for example, if a user performs a service activity of opening an account through an API interface corresponding to the target API asset, the service type provided by the user generally belongs to a service type related to account management.
And step S600, according to the service types, matching target capability types corresponding to the target API assets from a capability type library, wherein multiple capability types are stored in the capability type library, and the capability types represent the attributes of the service types provided by the API assets.
The capability type represents the attribute of the service type provided by the API asset, and the attribute of the service type provided by each API asset is not single any more because the API asset is various and is not limited to the traditional type. For example, the traditional business types generally belong to basic business types of banks, including loan financing, investment financing, foreign exchange business, payment settlement, etc., and at present, besides these basic businesses, the traditional business types may also include high-tech businesses such as artificial intelligence, block chains, etc., and ecological businesses such as real estate, transportation trip, etc. In order to implement efficient management of various types of API assets, in this embodiment, the capability types are divided into multiple types and stored in the capability type library in a classified manner, and each capability type can be obtained by dividing according to the attribute of the service type provided by each API asset, that is, API assets with the same attribute are stored in each capability type.
Thus, when the type of service provided by the target API asset is determined, the appropriate capability type, i.e., the target capability type, can be matched from the capability type library in combination with the attributes of the service type. For example, the service type provided by the target API asset is account management, and the account management belongs to the basic service type of the bank, so the target capability type matched by the target API asset is the basic service capability type of the bank; for another example, the service type provided by the target API asset is artificial intelligence, and the artificial intelligence belongs to a technology capability type, so that the target capability type matched by the target API asset is the technology capability type.
And step S800, marking the target API assets as target capacity types and storing the target API assets in a capacity type library.
When the target capability type is determined, the target API asset can be marked as the target capability type and stored in the capability type base under the target capability type, namely, the management of the newly added API asset is completed based on the capability base type base.
According to the API asset management method, the target capability type corresponding to the target API asset is matched from the capability type library according to the service type provided by the target API asset, the target API asset is marked as the target capability type, and the target API asset is stored in the target capability type in the capability type library, so that the unified management of the newly-added API asset is realized.
In one embodiment, the capability type library includes the basic service capability type and at least one capability type other than the basic service capability type.
That is, the capability type library in this embodiment includes other capability types in addition to the basic business capability types of the bank, so as to adapt to the trend of increasing types of API assets. The capability type library may include a basic service capability type and a scientific and technological capability type, may also include a basic service capability type and an ecological capability type, or includes a basic service capability type, a scientific and technological capability type and an ecological capability type at the same time. It is understood that in addition to scientific capability types and ecological capability types, as the variety of API assets grows, other capability types may be included and are suitable for use in the present solution.
In one embodiment, the step of determining the type of service provided by the target API asset in step S400 includes:
and step S410, judging whether the service type provided by the target API asset belongs to the basic service.
And step S420, if not, judging whether the service type provided by the target API asset belongs to the technical service.
In the process of determining the service type provided by the target API asset, firstly, whether the service type provided by the target API asset belongs to the basic service of the bank is judged, if not, whether the service type provided by the target API asset belongs to the technical service is continuously judged, and if not, the service type provided by the target API asset belongs to the ecological service can be determined. The service type provided by the target API asset can be rapidly determined through the two-stage judgment, the overall management efficiency is improved,
in one embodiment, the capability type library includes a basic business capability type, a scientific capability type and an ecological capability type.
Wherein, the basic business capability type refers to the traditional bank financial product service capability; the technological capability type refers to the technological capability which does not directly relate to banking business logic, is based on digital technology and can improve service efficiency for financial or non-financial services; the ecological capability type refers to the extensive financial and non-financial capability which does not belong to the traditional main business category of the bank. The capacity types are divided into basic business capacity types, scientific and technical capacity types and ecological capacity types, the traditional banking business capacity types and the non-traditional business capacity types are covered, the traditional mode that classification is only carried out according to traditional banking business is broken through, and various types of API assets can be covered.
Step S600, matching a target capability type corresponding to the target API asset from the capability type library according to the service type, includes:
step S610, when the service type provided by the target API asset belongs to the basic service, determining the target capability type as the basic service capability type.
And S620, when the service type provided by the target API asset belongs to the technical service, determining that the target capability type is the technological capability type.
Step S630, when the service type provided by the target API asset does not belong to the basic service and does not belong to the technical service, determining that the target capability type is the ecological capability type.
When it is determined through step S410 that the service type provided by the target API asset belongs to the basic service, the target capability type is determined as the basic service capability type, and the target API asset is marked as the basic service capability type and stored in the basic service capability type. When it is determined through step S420 that the service type provided by the target API asset belongs to the technical service, the target capability type is determined to be the scientific and technological capability type, and the target API asset is marked as the scientific and technological capability type and stored in the scientific and technological capability type. When it is determined through step S420 that the service type provided by the target API asset does not belong to either the basic service or the technical service, it is determined that the service type belongs to the ecological service, the target capability type is determined to be the ecological capability type, and the target API asset is marked as the ecological capability type and stored in the ecological capability type.
In one embodiment, the step S800 of marking the target API asset as the target capability type and storing the target API asset in the capability type library includes:
and step S810, determining the functional attributes of the target API assets.
And step S820, according to the function attribute of the target API asset, matching a target function category corresponding to the target API asset from the target capability type.
And step S830, marking the target API assets as target function categories and storing the target API assets in the target function categories.
In this embodiment, each capability type further includes a plurality of parallel function categories in the capability type library, and the function categories are further divided into API assets according to the function attributes of the API assets. For example, for the "basic service capability type", the original service group of the bank is focused on, and the function categories of loan financing, investment and financing, foreign exchange service, information query, account management, payment settlement and the like can be included; for "technology capability type", looking at the current popular technologies, it may include functional categories such as data and analysis, notification type service, security, payment technology, OCR, artificial intelligence, block chaining, cloud computing, etc.; aiming at the ecological ability type, various fields of ecological clothes and eating and housing are focused on, and the ecological clothes and housing can comprise function categories of equity activities, traveling, transportation, real estate, insurance, food, e-commerce, logistics and the like. Fig. 2 shows a schematic structural diagram of a capability type library in a specific example, where the capability type library includes three layers, namely a first layer (L1), a second layer (L2), and a third layer (L3), the first layer is a root directory, the second layer includes various capability types, which may include a basic service capability type, a scientific capability type, and an ecological capability type, and the third layer includes function categories under various capability types, where the basic service capability type may include function categories such as loan financing, investment financing, and account management, the scientific capability type may include function categories such as data analysis, payment science, and artificial intelligence, and the ecological capability type may include function categories such as travel, business fusion, and transportation.
The functional attributes of the target API asset refer to lower functions that can be implemented by the target API asset, such as purchasing tickets, face recognition, opening an account, and the like. Firstly, determining the functional attribute of the target API asset, and then trying to match a proper functional category under the determined target capability type, for example, matching the target API asset corresponding to the purchased ticket with the "travel" functional category under the ecological capability type, namely, marking the target API asset as the "travel" functional category, and storing the "travel" functional category.
In one embodiment, the target capability type has at least one level of target function class, and the level number of the target function class is proportional to the granularity of the target API asset.
In practical application, the same capability type can comprise multiple levels of target function categories, and the target function categories can be flexibly adjusted according to the granularity of the service types provided by the API assets. For example, the technology capability type- "artificial intelligence" first-level function category- "natural language processing" second-level function category, the ecological capability type- "logistics" first-level function category- "express service" second-level function category, the basic service capability- "account management" first-level function category- "service public account" second-level function category- "make an account reservation to public account" third-level function category.
And after the target capability type is determined, determining each target function type step by step according to the method.
It should be understood that, although the steps in the flowchart are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in the figures may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of execution of the steps or stages is not necessarily sequential, but may be performed alternately or in alternation with other steps or at least some of the other steps or stages.
In one embodiment, an API asset management system is provided.
Referring to fig. 3, the API asset management system provided in the present embodiment includes an obtaining module 200, a determining module 400, a matching module 600, and a storing module 800. Wherein:
the obtaining module 200 is configured to obtain a target API asset;
the determining module 400 is configured to determine a service type provided by the target API asset;
the matching module 600 is configured to match a target capability type corresponding to the API asset from a capability type library according to the service type, where multiple capability types are stored in the capability type library, and the capability types represent attributes of service types provided by the API assets;
the storage module 800 is configured to mark the target API asset as a target capability type and store the target API asset in the capability type library.
In one embodiment, the capability type library includes a basic service capability type and at least one capability type other than the basic service capability type.
In one embodiment, the determining module 400 includes a first determining unit configured to determine whether the service type provided by the target API asset belongs to the basic service, and a second determining unit configured to determine whether the service type provided by the target API asset belongs to the technical service when the first determining unit determines that the service type provided by the target API asset does not belong to the basic service.
In one embodiment, the capability type library comprises a basic service capability type, a scientific and technological capability type and an ecological capability type;
the matching module 600 includes a first determining unit, configured to determine that the target capability type is the basic service capability type when the service type provided by the target API asset belongs to the basic service, determine that the target capability type is the scientific capability type when the service type provided by the target API asset belongs to the technical service, and determine that the target capability type is the ecological capability type when the service type provided by the target API asset does not belong to the basic service and does not belong to the technical service.
In one embodiment, the storage module 800 includes a second determination unit, a matching unit, and a storage unit. The second determining unit is used for determining the functional attribute of the target API asset, the matching unit is used for matching a target function category corresponding to the target API asset from the target capability type according to the functional attribute of the target API asset, and the storage unit is used for marking the target API asset as the target function category and storing the target API asset into the target function category.
In one embodiment, the target capability type has at least one level of target function class, and the level number of the target function class is proportional to the granularity of the target API asset.
For specific limitations of the API asset management system, reference may be made to the above limitations of the API asset management method, which are not described herein again. The various modules in the API asset management system described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 4. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing various data related to the API asset management method. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program when executed by a processor implements an API asset management method.
Those skilled in the art will appreciate that the architecture shown in fig. 4 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
In an embodiment, a computer program product is provided, comprising a computer program which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.
Claims (10)
1. An API asset management method, comprising:
acquiring a target API asset;
determining a type of service provided by the target API asset;
matching a target capability type corresponding to the target API asset from a capability type library according to the service type, wherein a plurality of capability types are stored in the capability type library, and the capability types represent the attributes of the service types provided by the API assets;
and marking the target API asset as the target capability type and storing the target API asset in the capability type library.
2. The API asset management method of claim 1, wherein said capability type library comprises a base service capability type and at least one capability type other than said base service capability type.
3. The API asset management method of claim 1 wherein said step of determining the type of service provided by said target API asset comprises:
judging whether the service type provided by the target API asset belongs to basic service or not;
if not, judging whether the service type provided by the target API asset belongs to the technical service.
4. The API asset management method of claim 3, wherein the capability type library includes a basic business capability type, a technology capability type, and an ecological capability type; the step of matching a target capability type corresponding to the target API asset from a capability type library according to the service type comprises:
when the service type provided by the target API asset belongs to the basic service, determining that the target capability type is the basic service capability type;
when the service type provided by the target API asset belongs to the technical service, determining that the target capability type is a scientific and technological capability type;
and when the service type provided by the target API asset does not belong to the basic service and does not belong to the technical service, determining that the target capability type is the ecological capability type.
5. The API asset management method of claim 1 wherein said step of tagging said target API asset as said target capability type and storing said target API asset in said capability type repository comprises:
determining a functional attribute of the target API asset;
matching a target function category corresponding to the target API asset from the target capability type according to the functional attribute of the target API asset;
and marking the target API assets as the target function categories and storing the target API assets in the target function categories.
6. The API asset management method of claim 5, wherein the target capability types have at least one level of target function categories, the level number of the target function categories being proportional to the granularity of the target API asset.
7. An API asset management system, comprising:
an acquisition module for acquiring a target API asset;
a determining module, configured to determine a service type provided by the target API asset;
the matching module is used for matching a target capability type corresponding to the API asset from a capability type library according to the service type, wherein a plurality of capability types are stored in the capability type library, and the capability types represent the attributes of the service types provided by the API assets;
and the storage module is used for marking the target API asset as the target capability type and storing the target API asset into the capability type library.
8. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program implements the steps of the API asset management method of any of claims 1 to 6.
9. A computer-readable storage medium, having stored thereon a computer program, the computer program, when being executed by a processor, implementing the steps of the API asset management method of any of claims 1 to 6.
10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, carries out the steps of the API asset management method of any of the claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111111677.9A CN113918660A (en) | 2021-09-23 | 2021-09-23 | API asset management method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111111677.9A CN113918660A (en) | 2021-09-23 | 2021-09-23 | API asset management method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113918660A true CN113918660A (en) | 2022-01-11 |
Family
ID=79235670
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111111677.9A Pending CN113918660A (en) | 2021-09-23 | 2021-09-23 | API asset management method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113918660A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114070656A (en) * | 2022-01-18 | 2022-02-18 | 江苏苏宁银行股份有限公司 | Method and device for monitoring abnormity of open API (application program interface) of commercial bank |
| CN116170331A (en) * | 2023-04-23 | 2023-05-26 | 远江盛邦（北京）网络安全科技股份有限公司 | API asset management method, device, electronic equipment and storage medium |
-
2021
- 2021-09-23 CN CN202111111677.9A patent/CN113918660A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114070656A (en) * | 2022-01-18 | 2022-02-18 | 江苏苏宁银行股份有限公司 | Method and device for monitoring abnormity of open API (application program interface) of commercial bank |
| CN114070656B (en) * | 2022-01-18 | 2022-03-25 | 江苏苏宁银行股份有限公司 | Method and device for monitoring abnormity of open API (application program interface) of commercial bank |
| CN116170331A (en) * | 2023-04-23 | 2023-05-26 | 远江盛邦（北京）网络安全科技股份有限公司 | API asset management method, device, electronic equipment and storage medium |
| CN116170331B (en) * | 2023-04-23 | 2023-08-04 | 远江盛邦（北京）网络安全科技股份有限公司 | API asset management method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11810204B2 (en) | Artificial intelligence transaction risk scoring and anomaly detection | |
| CN110032599B (en) | Data structure reading and updating method and device, and electronic equipment | |
| CN110020542B (en) | Data reading and writing method and device and electronic equipment | |
| CN111476667B (en) | Block chain-based original work transaction method and device and electronic equipment | |
| CN109949154B (en) | Customer information classification method, apparatus, computer device and storage medium | |
| CN113711221B (en) | Efficient access to chain recordable | |
| US11593622B1 (en) | Artificial intelligence system employing graph convolutional networks for analyzing multi-entity-type multi-relational data | |
| CN113918660A (en) | API asset management method and device, computer equipment and storage medium | |
| CN110032568B (en) | Data structure reading and updating method and device, and electronic equipment | |
| CN112330181A (en) | Enterprise credit evaluation method and device based on block chain | |
| CN114187112A (en) | Training method of account risk model and determination method of risk user group | |
| CN114693192A (en) | Wind control decision method and device, computer equipment and storage medium | |
| CN113919664A (en) | API asset risk control method and device, computer equipment and storage medium | |
| US12073410B2 (en) | Generating a multi-transaction dispute package | |
| CN116452206A (en) | Method, device, computer equipment and storage medium for determining resource processing strategy | |
| CN111461191A (en) | Method and device for determining image sample set for model training and electronic equipment | |
| CN117993910A (en) | Verification method and related device for abnormal transaction response strategy | |
| CN114444097A (en) | Block chain-based user access method and device, electronic equipment and storage medium | |
| CN113159937A (en) | Method and device for identifying risks and electronic equipment | |
| Mazumder et al. | A Framework for Trustworthy AI in Credit Risk Management: Perspectives and Practices | |
| CN111898004A (en) | Data mining method and device, electronic equipment and readable storage medium thereof | |
| TWM580230U (en) | Financial service application review system | |
| CN112785320B (en) | Credit risk determination method and device, storage medium and electronic equipment | |
| CN118071512A (en) | Penetration risk analysis method, penetration risk analysis device, computer equipment and storage medium | |
| CN116703404A (en) | Abnormal account identification method, device, equipment, storage medium and program product |
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 |