CN115981707A

CN115981707A - Interface account management method and device, electronic equipment and storage medium

Info

Publication number: CN115981707A
Application number: CN202211619818.2A
Authority: CN
Inventors: 徐玲
Original assignee: Agricultural Bank of China
Current assignee: Agricultural Bank of China
Priority date: 2022-12-15
Filing date: 2022-12-15
Publication date: 2023-04-18

Abstract

The embodiment of the application discloses an interface ledger management method, an interface ledger management device, electronic equipment and a storage medium, and the interface ledger management method and the interface ledger management device are used for acquiring each link data associated with a target server identification within a target time range; extracting target information of each interface of a target service party from each link data, wherein the target information at least comprises: interface identification and interface access times; determining the identification of the unregistered interface of the target service party and the interfaces with the access times of zero when the accumulated number of days reaches a threshold value based on the interface identification and the interface access times of each interface and the identification and the historical access times of the registered interfaces of the target service party; initiating an interface maintenance process to the first account so that a target service party developer using the first account perfects the first type of related information for the identification of the unregistered interface and perfects the second type of related information for the interface with zero number of accesses for the number of accumulated days reaching the threshold value. The application realizes the high-efficiency and accurate management of the interface ledger.

Description

Interface standing book management method and device, electronic equipment and storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to an interface ledger management method and apparatus, an electronic device, and a storage medium.

Background

Along with the current technical trend of micro-servitization, application interconnection scenes are more and more frequent, application relations are more and more compact, however, in the face of the infinite new interfaces, the abandoned offline interfaces and the update iterative stock interfaces, unified and effective interface information management is lacked, if long-term tracking and maintenance of interface information are carried out in a manual mode, a large amount of manpower is required to be invested for inputting and confirming, and the defects of high cost, poor flexibility, low data accuracy and the like exist.

Therefore, how to efficiently and accurately manage the interface ledger becomes a technical problem to be solved urgently.

Disclosure of Invention

The application provides an interface standing book management method and device, an electronic device and a storage medium, and the method comprises the following technical scheme:

an interface ledger management method, the method comprising:

acquiring each link data associated with the target server identification within a target time range; each link data record has the calling condition of one interface of the target service party by one consumer;

extracting target information of each interface of the target service party from each link data, wherein the target information at least comprises: interface identification and interface access times;

determining the identification of the unregistered interface of the target service party and the interfaces with the access times of zero accumulated to reach the threshold number of days based on the interface identification and the interface access times of each interface and the identification and the historical access times of the registered interfaces of the target service party;

initiating an interface maintenance process to a first account so that a developer of the target service party using the first account perfects a first type of related information for the identification of the unregistered interface and perfects a second type of related information for the interface with the number of times of access zero when the number of accumulated days reaches a threshold value.

Preferably, the initiating an interface maintenance procedure to the first account of the target service provider includes:

sending a project list needing to be completed to the first account according to the identifier of the unregistered interface so that a developer of the target service party can complete first-class related information corresponding to each project in the project list;

and sending information to be confirmed to the first account aiming at the interface with zero access times when the accumulated number of days reaches the threshold value so as to ensure that developers of the target service party confirm whether the interface normally operates or is an off-line interface.

Preferably, the extracting target information of each interface of the target service party from each link data includes:

clustering the link data according to the interface identification to determine the interface identification contained in the link data and the link data contained in the category corresponding to each interface identification;

and for any interface, counting the accessed times of the interface according to the link data contained in the category corresponding to the identifier of the interface.

The above method, preferably, further comprises:

extracting information of each consumer from each link data, wherein the information of each consumer at least comprises: consumer identification and number of times each interface is accessed;

determining the identifier of the unregistered consumer and the number of times of accessing the target interface by accumulating the number of days reaching a threshold value to be zero based on the identifier of each consumer and the number of times of accessing each interface by each consumer, the identifier of the registered consumer and the number of times of accessing each interface by each consumer historically;

and initiating a maintenance process to a second account so that a consumer developer using the second account perfects third type of related information for the identification of the unregistered consumer and perfects fourth type of related information for the consumer who accesses the target interface for zero times when the accumulated number of days reaches a threshold value.

Preferably, the method for extracting information of each consumer from each link data includes:

clustering the link data according to the consumer identification to determine the consumer identification contained in the link data and the link data contained in the category corresponding to each consumer identification;

and for any consumer, counting the times of accessing each interface by the consumer according to the link data contained in the category corresponding to the identifier of the consumer.

The above method, preferably, further comprises:

screening out link data of an application interconnection layer from the link data;

when the link data are clustered according to the interface identification, clustering the link data of the application interconnection layer according to the interface identification;

and clustering the link data of the application interconnection layer according to the consumer identification when clustering the link data according to the consumer identification.

The above method, preferably, further comprises:

initiating an approval process to a third account of a subscriber of the interface with zero access times when the number of accumulated days reaches a threshold value, so that the subscriber can determine whether to agree to the offline of the interface with zero access times when the number of accumulated days reaches the threshold value;

initiating an approval process to the first account for the unregistered consumer so that a developer using the first account determines whether the consumer agrees to invoke the interface of the target service party.

An interface ledger management apparatus, the apparatus comprising:

the acquisition module is used for acquiring each link data associated with the target server identification in a target time range; each link data record has the calling condition of one interface of the target service party by one consumer;

an extracting module, configured to extract target information of each interface of the target server from each link data, where the target information at least includes: interface identification and interface access times;

the determining module is used for determining the identifier of the unregistered interface of the target service party and the interface with zero access times accumulated for reaching the threshold number of days based on the interface identifier and the interface access times of each interface and the identifier and the historical access times of the registered interface of the target service party;

and the processing module is used for initiating an interface maintenance process to a first account so as to improve the first type of related information aiming at the identifier of the unregistered interface by using the developer of the target service party of the first account, and improve the second type of related information aiming at the interface with zero accessed times when the accumulated number of days reaches a threshold value.

An electronic device, comprising:

a memory for storing a program;

and the processor is used for calling and executing the program in the memory, and the steps of the interface ledger management method are realized by executing the program.

A readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the steps of the interface ledger management method of any preceding claim.

According to the scheme, the interface ledger management method and device, the electronic equipment and the storage medium obtain each link data associated with the target service party identifier within the target time range; each link data record has the calling condition of one interface of the target service party by one consumer; extracting target information of each interface of a target service party from each link data, wherein the target information at least comprises: interface identification and interface access times; determining the identifier of the unregistered interface of the target service party and the interfaces with the access times of zero accumulated days reaching a threshold value based on the interface identifier and the interface access times of each interface and the identifier and the historical access times of the registered interfaces of the target service party; initiating an interface maintenance process to the first account so that a developer of a target service party using the first account perfects the first type of related information for the identification of the unregistered interface and perfects the second type of related information for the interface with zero number of accesses accumulated until a threshold number of days. According to the method and the system, based on automatic acquisition and analysis of link data, the interface identification of an unregistered server is rapidly and accurately determined, and the number of access times to the interface is zero when the number of days reaches a threshold value in an accumulated mode, so that developers can rapidly and accurately complete the interface account manually, namely, the link data are automatically acquired and analyzed and manually input to be combined, and the interface account is efficiently and accurately managed.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.

Fig. 1 is a flowchart of an implementation of an interface ledger management method according to an embodiment of the present application;

fig. 2 is a flowchart of an implementation of extracting target information of each interface of a target server from at least each link data according to an embodiment of the present application;

FIG. 3 is a flow chart of one implementation of extracting information of each consumer from each link data according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of an interface ledger management apparatus according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in other sequences than described or illustrated herein.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without inventive step, are within the scope of the present disclosure.

As shown in fig. 1, an implementation flowchart of the interface ledger management method provided in the embodiment of the present application may include:

step S101: acquiring each link data associated with the target server identification within a target time range; each link data record is the calling condition of one interface of the target service party by one consumer.

In an application interconnection scenario, if an interface (denoted as a first interface) of one application (denoted as a first application) is called by another application (denoted as a second application), the first application is a service side of the first interface, and the second application is a consumer side of the first interface.

In the application, a link data acquisition component may be deployed in at least one of the service side and the consumer side of the first interface, and link data between the service side and the caller side of the first interface is acquired through the link data acquisition component.

As an example, a link data collection component deployed in a first application may add a piece of link data when receiving, through a first interface, a call request (also referred to as an access request) sent by a second application, where the link data is identified by a globally unique link identifier (traceid), and the link data records information such as an identifier of the first application, a name of the first interface, an interface protocol, an identifier of the second application, and the number of times that the first interface is accessed by the second application; after the first application feeds back the response message to the second application through the first interface, the response duration of the first interface may also be recorded.

As an example, a link data acquisition component deployed in a second application may add a piece of link data after sending a call request to a first application through a first interface, where the link data is identified by a unique link identifier, and the link data records information such as an identifier of the first application, a name of the first interface, an interface protocol, an identifier of the second application, and the number of times the second application accesses the first interface; and after the second application receives the response message fed back by the second application through the first interface, the response duration of the first interface can be recorded.

The link data collection component may upload the collected link data to the database in real time after collecting the link data, or may upload the collected link data to the database at a specified time (for example, at an idle time of an application where the link data collection component is located).

Optionally, the link data acquisition component may encapsulate the acquired link data into a data packet based on an open source link acquisition protocol (such as an opentraining protocol) and upload the data packet to the database. When the link data acquisition component reports link data, a data packet carries reporting time (including date and specific time point, for example, 202010092300, which indicates that 23/9/10/2020).

When the interface standing book management device needs to perform interface standing book management, the interface standing book management device acquires each link data which is associated with the target service party identifier in a target time range from the database. The target time range may be the day before the current date, that is, the interface ledger is maintained and updated with the link data of the day before each day. The target server identification may be an identification of any server that needs interface ledger management.

Step S102: extracting target information of each interface of a target service party from each link data, wherein the target information at least comprises: interface identification and the number of times the interface is accessed.

The extracted data of each link is subjected to statistical analysis, so that the identification of each interface of the target server and the information such as the number of times that each interface of the target server is accessed in the target time range are determined.

Step S103: and determining the identification of the unregistered interface of the target service party and the interfaces with the access times of zero accumulated reaching the threshold number of days based on the interface identification and the interface access times of each interface and the identification and the historical access times of the registered interfaces of the target service party.

The historical number of times that any registered interface was accessed refers to the number of times that any registered interface was accessed within each historical target time frame. For example, the number of times of historical accesses of any registered interface refers to the number of times of accesses of the any registered interface in the past each day, and the like.

Each interface identifier determined in step S102 may be compared with an interface identifier of a registered interface, and an identifier of an interface for which the target service party is not registered may be determined.

Assuming that the threshold number of days is N, for any interface of the target service party, the sum of the number of times of accessing the any interface per day in M days before the current time belongs to the date (including the day before the current time belongs to the date) can be obtained, so as to obtain the cumulative number of times of accessing the any interface for M days. M is an integer less than or equal to N. Wherein M is less than N when any one of the interfaces is just put into use, and M is equal to N at least N days after any one of the interfaces is put into use.

Step S104: initiating an interface maintenance process to the first account so that a developer of a target service party using the first account perfects the first type of related information for the identification of the unregistered interface and perfects the second type of related information for the interface with zero number of accesses accumulated until a threshold number of days.

The first account may be an account that a developer of the target service provider (which may be referred to as a target service provider developer) has registered with the interface account management apparatus in advance, where the account may be customized by the target service provider developer, or may be an existing communication account of the target service provider, for example, a mobile phone number of the developer, a mailbox, or another account that can uniquely identify the developer, such as an account of instant messaging software.

Optionally, the first type of related information may include, but is not limited to, at least part of the following information: interface meaning, interface developer, interface average response time, interface design description and the like.

The second type of related information may include, but is not limited to, at least part of the following information: whether the interface normally runs, whether the interface is off-line or not and the like, if the interface is off-line, the second type of related information further comprises: time of line-off, reason of line-off, etc.

When initiating an interface maintenance process to the first account of the target service party, prompt information can be displayed through an interactive interface provided by the interface standing book management device, and the prompt information indicates that a new interface standing book maintenance task exists. Further, when the first account is an existing communication account of the developer, in addition to displaying prompt information on an interactive interface provided by the interface ledger management device, a message can be sent to the communication account of the developer to remind the developer that the interface ledger management device has an interface ledger maintenance task to be processed.

The hints information may include, but is not limited to, an identification of unregistered interfaces of the target service and an identification of interfaces that are accessed zero times for a cumulative threshold number of days.

For the unregistered interface, a developer can perform related operation of adding an interface in the interface ledger management device so as to add an identifier of the unregistered interface and first-type related information corresponding to the unregistered interface in the interface ledger;

for an interface with the number of accesses being zero when the number of days reaches the threshold value accumulatively, a developer can determine whether the interface with the number of accesses being zero when the number of days reaches the threshold value accumulatively is in normal operation or not and whether the interface is off-line or not in the interface ledger management device. If the interface is an offline interface, information such as offline time and offline reason is also supplemented.

According to the interface ledger management method, the interface identification of the unregistered service party is quickly and accurately determined through automatic acquisition and analysis of link data, and the interfaces with the number of times of access being zero are accumulated to reach the threshold number of days, so that developers can quickly and accurately complete the interface ledger manually, namely, the interface ledger management method combines automatic acquisition and analysis of the link data with manual entry, and efficient and accurate management of the interface ledger is achieved.

In an optional embodiment, one implementation manner of initiating the interface maintenance procedure to the first account of the target service party may be:

and aiming at the identifier of the unregistered interface, sending a project list needing to be completed to the first account so that a developer of the target service party completes first-class related information corresponding to each project in the project list.

By sending the item to be completed to the first account, the developer of the target service party using the first account can directly and clearly know which information is to be completed, so that the omission of the information to be completed is avoided.

And sending information to be confirmed to the first account aiming at the interface with zero access times when the number of accumulated days reaches the threshold value so as to ensure that a developer of the target service party confirms whether the interface normally operates or is an off-line interface.

There may be at least three options in the information to be validated: normal operation, abnormal operation and offline interface. And the normal operation representation interface is an offline interface and operates normally. The abnormal operation characterization interface is an offline interface and is operated abnormally. The developer of the target service party can select any option according to actual conditions. If the offline interface is selected, the interface standing book management device can also output prompt information to prompt developers of the target service party to improve information such as offline time and offline reasons.

In an alternative embodiment, an implementation flowchart of the extracting target information of each interface of the target service party from each link data is shown in fig. 2, and may include:

step S201: and clustering the link data according to the interface identification to determine the interface identification contained in the link data and the link data contained in the category corresponding to each interface identification.

In the embodiment of the application, the identification link data with the same interface of the target server in each link data is classified into one type. Thus, each category corresponds to an interface of the target service party.

Under the condition that both the server and the consumer report the link data, the link data reported by the same reporting party (the server or the consumer) only needs to be clustered according to the interface identification.

Step S202: and for any interface, counting the accessed times of the interface according to the link data contained in the category corresponding to the identifier of the interface.

The link data included in the category corresponding to any interface can be clustered according to the consumer identifier to obtain each sub-category included in the category corresponding to any interface, so that each sub-category corresponds to one consumer identifier; determining the maximum value of the number of times that any interface of each link data record in each subcategory is accessed by the same consumer within the target time range, obtaining the maximum access times corresponding to each subcategory, and summing the maximum access times corresponding to each subcategory to obtain the number of times that any interface is accessed within the target time range.

In an optional embodiment, the interface ledger management method provided by the present application may further include:

extracting information of each consumer from each link data, wherein the information of each consumer at least comprises: the number of times the consumer identifies and accesses each interface.

That is, the present application extracts, from each link data, not only target information of each interface of the target service provider, but also information of a consumer of the interface of the target service provider.

The extracted data of each link can be statistically analyzed, so that the information of each consumer can be determined.

And determining the identifier of the unregistered consumer based on the identifier of each consumer and the number of times each consumer accesses each interface, and the identifier of the registered consumer and the number of times each consumer accesses each interface historically, and accumulating the number of times the consumer accesses the target interface for zero after reaching a threshold number of days.

An unregistered consumer is a consumer who has sent a call request to the interface of the target server but has not registered in the interface ledger, i.e., has not subscribed to the interface of the target server.

Each consumer identifier in the consumer information extracted in the previous step may be compared with the consumer identifier of the registered consumer to determine the identifier of the unregistered consumer.

Assuming that the threshold number of days is N, for any consumer, the sum of the number of times that the consumer accesses the target interface of the target server every day in M days before the current time date can be obtained, and the number of times that the consumer accesses the target interface in M days is obtained. Wherein M is an integer less than or equal to N. M will be less than N in the case of the target interface just being put into use, and M equals N at least N days after the target interface has been put into use.

And initiating a maintenance process to the second account so that the consumer developer using the second account perfects the third type of related information for the identification of the unregistered consumer and perfects the fourth type of related information for the consumer with zero times of accessing the target interface for the number of accumulated days reaching the threshold value. The consumer developer is a developer of unregistered consumers, or a developer of consumers who access the target interface for zero times when the number of accumulated days reaches the threshold value. That is, for an unregistered consumer, the consumer developer is a developer of the unregistered consumer; and the consumer developer is the developer of the consumer who accesses the target interface for zero times by accumulating the number of days reaching the threshold value.

Since the consumer calling the interface of the service provider needs to meet a certain condition, the developer of the consumer is required to provide the related information (i.e., the third type of related information) of the consumer, so that the developer of the service provider determines whether to allow the consumer to call the interface of the service provider.

The third type of related information may include, but is not limited to, at least part of the following information: consumption scenes, actual subscribers, peak calling times of the interface, daily average calling times of the interface and the like.

The fourth type of related information may include, but is not limited to, at least some of the following: whether the target interface consumption is normal (i.e., the target interface subscriber is normally charged, etc.), whether to cancel the subscription to the target interface, etc.

In an alternative embodiment, an implementation flowchart of the above-mentioned extracting information of each consumer from each link data is shown in fig. 3, and may include:

step S301: and clustering the link data according to the consumer identifications to determine the consumer identifications contained in the link data and the link data contained in the category corresponding to each consumer identification.

In the embodiment of the application, the link data with the same consumer identifier in each link data is classified into one category, and therefore each category corresponds to one consumer identifier.

Under the condition that both the server and the consumer report the link data, the link data reported by the same reporting party (the server or the consumer) only needs to be clustered according to the consumer identification.

Step S302: and for any consumer, counting the times of accessing each interface by the any consumer according to the link data contained in the category corresponding to the identifier of the any consumer.

The link data in the category corresponding to any consumer can be clustered according to the interface identifier to obtain each sub-category contained in the category corresponding to any consumer, so that each sub-category corresponds to one interface; and determining the maximum value of the times of accessing the same interface by any consumer within the target time range of each link data record in each subcategory to obtain the maximum access times corresponding to each subcategory, wherein the maximum access times corresponding to any subcategory are the times of accessing the interface corresponding to any category within the target time range by any consumer.

In an optional embodiment, the interface ledger management method provided in the embodiment of the present application may further include:

and screening out the link data of the application interconnection layer from the link data.

According to actual needs, when the link data acquisition component acquires link data, link data of a non-application interconnection layer may be acquired in addition to link data of an application interconnection layer, and therefore link data reported by the link data acquisition component may include link data of the non-application interconnection layer. The interface ledger management method only needs to apply the link data of the interconnection layer, so that the link data of the application interconnection layer can be screened from each link data for subsequent cluster statistics in order to reduce the data processing amount of subsequent processes and improve the processing efficiency.

Alternatively, the link data containing the specified keyword may be determined as the link data of the application interconnection layer. In the application, when the link data acquisition component acquires link data, the specified keywords are added aiming at the link data of the application interconnection layer, but the specified keywords are not added to the link data of the non-application interconnection layer, so that the link data of the application interconnection layer and the link data of the non-application interconnection layer can be distinguished through the specified keywords.

And clustering the link data of the application interconnection layer according to the interface identifier when clustering the link data according to the interface identifier.

and initiating an examination and approval process to a third account of the subscriber of the interface with the zero access times accumulated for reaching the threshold number of days so as to facilitate the subscriber to determine whether to agree to take the interface with the zero access times accumulated for reaching the threshold number of days down.

The interface with the number of accesses of zero accumulated to reach the threshold number of days may be an interface which is not accessed by the consumer any more, but may also be an interface which is still subscribed by the consumer, but the use frequency is extremely low, so an approval process needs to be initiated to the subscriber who subscribes the interface so that the subscriber determines whether to agree with the interface with the number of accesses of zero accumulated to reach the threshold number of days to be offline, if all the subscribers agree with the interface to be offline, the developer of the target service party can take the interface offline, and if the subscribers disagree with the interface to be offline, the developer of the target service party cannot take the interface offline.

And initiating an approval process to the first account number aiming at the unregistered consumers so that the developers using the first account number can determine whether the consumers are allowed to call the interface of the target service party.

For unregistered consumers, an approval process can be initiated to the first account after the developer of the consumer completes the third type of related information, and whether the developer of the target service party agrees to subscribe the interface of the target service party is judged by the developer of the target service party according to the third type of related information completed by the developer of the consumer. If the developer of the target service party agrees that the consumer subscribes to the interface of the target service party, the consumer can call the interface of the target service party after the subscriber of the consumer subscribes to the interface of the target service party, otherwise, the consumer cannot subscribe or call the interface of the target service party.

Corresponding to the method embodiment, the present application further provides an interface ledger management apparatus, and a schematic structural diagram of the interface ledger management apparatus provided in the embodiment of the present application is shown in fig. 4, and may include:

an obtaining module 401, an extracting module 402, a determining module 403 and a processing module 404; wherein,

the obtaining module 401 is configured to obtain link data associated with a target server identifier within a target time range; each link data record has the calling condition of one interface of the target service party by one consumer;

the extracting module 402 is configured to extract target information of each interface of the target service party from the each link data, where the target information at least includes: interface identification and interface access times;

the determining module 403 is configured to determine, based on the interface identifier and the number of times that the interface is accessed of each interface, and the identifier and the historical number of times that the registered interface of the target service party is accessed, the identifier of the unregistered interface of the target service party, and the number of times that the interface is accessed is zero when the number of days reaches a threshold value in an accumulated manner;

the processing module 404 is configured to initiate an interface maintenance procedure to the first account, so that a developer using the first account of the target service provider perfects the first type of relevant information for the identifier of the unregistered interface, and perfects the second type of relevant information for the interface with zero number of times of access when the number of days reaches the threshold value in the accumulation.

The interface provided by the embodiment of the application is in a management device, the interface identification of an unregistered service party is rapidly and accurately determined through automatic acquisition and analysis of link data, and the number of access times reaches zero when the number of days reaches a threshold value in an accumulated mode, so that developers can rapidly and accurately complete the interface account manually, namely, the interface account is combined with automatic acquisition and analysis of the link data and manual entry, and efficient and accurate management of the interface account is realized.

In an optional embodiment, when the processing module 404 initiates an interface maintenance procedure to the first account of the target service provider, it is configured to:

and sending information to be confirmed to the first account of the target service party aiming at the interface with the number of times of access being zero when the number of days reaches the threshold value in the accumulating manner so as to ensure that the developer confirms whether the interface normally runs or is an off-line interface.

In an optional embodiment, the extracting module 402 extracts target information of each interface of the target service party from the link data, including:

In an optional embodiment, the extracting module 402 is further configured to:

the determining module 403 is further configured to: determining the identifier of the unregistered consumer and the number of times of accessing the target interface by accumulating the number of days reaching a threshold value to be zero based on the identifier of each consumer and the number of times of accessing each interface by each consumer, the identifier of the registered consumer and the number of times of accessing each interface by each consumer historically;

the processing module 404 is further configured to: and initiating a maintenance process to a second account so that a consumer developer using the second account perfects third type of related information for the identification of the unregistered consumer and perfects fourth type of related information for the consumer who accesses the target interface for zero times when the accumulated number of days reaches a threshold value.

In an optional embodiment, when the extracting module 402 extracts information of each consumer from the link data, the extracting module is configured to:

clustering the link data according to the consumer identifications to determine the consumer identifications contained in the link data and the link data contained in the category corresponding to each consumer identification;

In an optional embodiment, the interface ledger management apparatus further includes:

the screening module is used for screening out the link data of the application interconnection layer from the link data;

when the extracting module 402 clusters the link data according to the interface identifier, the extracting module is configured to: clustering the link data of the application interconnection layer according to the interface identification;

when the extracting module 402 clusters the link data according to the consumer identifier, it is configured to: and clustering the link data of the application interconnection layer according to the consumer identification.

In an optional embodiment, the processing module 404 is further configured to:

Corresponding to the embodiment of the method, the present application further provides an electronic device, a schematic structural diagram of which is shown in fig. 5, and the electronic device may include: at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4.

In the embodiment of the present application, the number of the processor 1, the communication interface 2, the memory 3, and the communication bus 4 is at least one, and the processor 1, the communication interface 2, and the memory 3 complete mutual communication through the communication bus 4.

The processor 1 may be a central processing unit CPU, or an application specific integrated circuit ASIC (application specific integrated circuit), or one or more integrated circuits configured to implement the embodiments of the present application, etc.

The memory 3 may include a high-speed RAM memory, and may further include a non-volatile memory (non-volatile memory) or the like, for example, at least one disk memory.

Wherein the memory 3 stores a program, and the processor 1 may call the program stored in the memory 3, the program being configured to:

determining the identifier of the unregistered interface of the target service party and the interfaces with the access times of zero accumulated days reaching a threshold value based on the interface identifier and the interface access times of each interface and the identifier and the historical access times of the registered interfaces of the target service party;

Alternatively, the detailed function and the extended function of the program may be as described above.

Embodiments of the present application further provide a storage medium, where a program suitable for execution by a processor may be stored, where the program is configured to:

initiating an interface maintenance process to a first account so that a developer of the target service party using the first account perfects first-type related information aiming at the identification of the unregistered interface and perfects second-type related information aiming at the interface with zero accessed times when the accumulated number of days reaches a threshold value.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

It should be understood that the technical problems can be solved by combining and combining the features of the embodiments from the claims.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An interface ledger management method, characterized in that the method comprises:

2. The method of claim 1, wherein initiating the interface maintenance procedure to the first account comprises:

and sending information to be confirmed to the first account aiming at the interface with zero access times when the number of days reaches the threshold value in the accumulating mode so that a developer of the target service party can confirm whether the interface normally runs or is an off-line interface.

3. The method of claim 1, wherein the extracting the target information of each interface of the target server from each link data comprises:

4. The method of claim 1, further comprising:

5. The method according to claim 4, wherein said extracting information of each consumer from each link data comprises:

6. The method of claim 3 or 5, further comprising:

clustering the link data of the application interconnection layer according to the interface identifier when clustering the link data according to the interface identifier;

7. The method of claim 4, further comprising:

initiating an approval process to a third account of a subscriber of the interface with zero accessed times when the number of accumulated days reaches the threshold number of days so that the subscriber can determine whether to agree to offline the interface with zero accessed times when the number of accumulated days reaches the threshold number of days;

8. An interface ledger management apparatus, characterized in that the apparatus comprises:

9. An electronic device, comprising:

a memory for storing a program;

a processor for calling and executing the program in the memory, and implementing the steps of the interface ledger management method according to any one of claims 1 to 7 by executing the program.

10. A readable storage medium on which a computer program is stored which, when being executed by a processor, carries out the steps of the interface ledger management method of any one of claims 1-7.