Interface account management method and device, electronic equipment and storage medium
By automatically collecting and analyzing link data, combined with manual entry, unregistered and long-term inaccessible interfaces can be quickly and accurately identified, solving the problems of high cost and poor flexibility in interface information management, and achieving efficient and accurate interface ledger management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- AGRICULTURAL BANK OF CHINA
- Filing Date
- 2022-12-15
- Publication Date
- 2026-05-15
AI Technical Summary
In existing technologies, there is a lack of unified and effective management methods for interface information management, resulting in high costs, poor flexibility, and low data accuracy in manual tracking and maintenance.
By automatically collecting and analyzing link data, unregistered service provider interfaces and interfaces that have not been accessed for a cumulative number of days reaching the threshold are identified. An interface maintenance process is initiated to improve relevant information. Combined with manual data entry, efficient and accurate management of the interface ledger is achieved.
It enables rapid and accurate management of interface ledgers, reduces the cost of manual data entry, and improves the accuracy and flexibility of data.
Smart Images
Figure CN115981707B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and more specifically, to an interface ledger management method, apparatus, electronic device, and storage medium. Background Technology
[0002] With the current trend of application microservices, application interconnection scenarios are becoming more frequent and application relationships are becoming closer. However, in the face of a constant stream of new interfaces, obsolete and outdated interfaces, and updated and iterated existing interfaces, there is a lack of unified and effective interface information management. If interface information is tracked and maintained manually for a long time, a lot of manpower is required for input and confirmation, which is not only costly, but also has disadvantages such as poor flexibility and low data accuracy.
[0003] Therefore, how to manage the interface ledger efficiently and accurately has become an urgent technical problem to be solved. Summary of the Invention
[0004] This application provides an interface ledger management method, apparatus, electronic device, and storage medium, including the following technical solutions:
[0005] An interface ledger management method, the method comprising:
[0006] Obtain data for each link associated with the target service provider's identifier within the target time range; each link data record shows the call status of one interface of the target service provider by one consumer.
[0007] Extract target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed.
[0008] Based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interfaces of the target service provider, the identifier of the unregistered interfaces of the target service provider and the interfaces whose cumulative access count reaches zero after reaching the threshold number of days are determined.
[0009] An interface maintenance process is initiated for the first account so that the developers of the target service provider using the first account can improve the first type of relevant information for the identifier of the unregistered interface, and improve the second type of relevant information for the interface whose cumulative access count reaches the threshold number of days and is zero.
[0010] In the above method, preferably, the step of initiating the interface maintenance process to the first account of the target service provider includes:
[0011] For the identifier of the unregistered interface, a list of projects that need to be improved is sent to the first account so that the developers of the target service provider can improve the first type of relevant information corresponding to each project in the project list;
[0012] For interfaces that have accumulated zero accesses within the threshold number of days, a confirmation message is sent to the first account so that the developers of the target service provider can confirm whether the interface is operating normally or whether it is an offline interface.
[0013] In the above method, preferably, the step of extracting the target information of each interface of the target service provider from the data of each link includes:
[0014] The link data is clustered according to the interface identifier to determine the interface identifier contained in each link data, and the link data contained in the category corresponding to each interface identifier;
[0015] For any given interface, the number of times the interface is accessed is counted based on the link data contained in the category corresponding to the identifier of the interface.
[0016] The above method, preferably, also includes:
[0017] Extract information about each consumer from the data of each link. The information of each consumer includes at least: consumer identifier and the number of times each interface is accessed.
[0018] Based on the identifiers of each consumer and the number of times each consumer accesses each interface, as well as the identifiers of registered consumers and the historical number of times each consumer accesses each interface, the identifiers of unregistered consumers and consumers whose cumulative access to the target interface is zero after reaching the threshold number of days are determined.
[0019] A maintenance process is initiated for the second account so that the consumer developers using the second account can improve the third type of relevant information for the unregistered consumer's identifier, and improve the fourth type of relevant information for the consumer whose cumulative access to the target interface for the threshold number of days is zero.
[0020] In the preferred embodiment of the above method, extracting information about each consumer from the data of each link includes:
[0021] The data of each link is clustered according to the consumer identifier to determine each consumer identifier contained in each link data, and the link data contained in the category corresponding to each consumer identifier;
[0022] For any consumer, the number of times the consumer accesses each interface is counted based on the link data contained in the category corresponding to the identifier of the consumer.
[0023] The above method, preferably, also includes:
[0024] From the data of each link, filter out the link data at the application interconnection layer;
[0025] When clustering the data of each link according to the interface identifier, the link data of the application interconnection layer is clustered according to the interface identifier;
[0026] When clustering the data of each link according to the consumer identifier, the link data of the application interconnection layer is clustered according to the consumer identifier.
[0027] The above method, preferably, also includes:
[0028] For interfaces that have accumulated zero accesses over a certain number of days, an approval process is initiated with the third-party account of the subscriber of the interface that has accumulated zero accesses over a certain number of days, so that the subscriber can determine whether to agree to take the interface that has accumulated zero accesses over a certain number of days offline.
[0029] For the unregistered consumer, an approval process is initiated with the first account so that the developer using the first account can determine whether to approve the consumer's call to the target service provider's interface.
[0030] An interface ledger management device, the device comprising:
[0031] The acquisition module is used to obtain the data of each link associated with the target service provider's identifier within the target time range; each link data record records the call status of an interface of the target service provider by a consumer.
[0032] The extraction module is used to extract target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed.
[0033] The determination module is used to determine the identifier of the unregistered interface of the target service provider and the interface whose access count has reached zero after reaching a threshold number of days, based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interface of the target service provider.
[0034] The processing module is used to initiate an interface maintenance process to the first account, so that the developers of the target service provider using the first account can improve the first type of relevant information for the identifier of the unregistered interface, and improve the second type of relevant information for the interface whose cumulative access count is zero after reaching the threshold number of days.
[0035] An electronic device, comprising:
[0036] Memory, used to store programs;
[0037] A processor is configured to call and execute the program in the memory, thereby implementing the various steps of the interface ledger management method as described in any of the preceding claims.
[0038] A readable storage medium having a computer program stored thereon, characterized in that, when the computer program is executed by a processor, it implements the various steps of the interface ledger management method as described in any of the preceding claims.
[0039] As can be seen from the above scheme, the interface ledger management method, device, electronic device, and storage medium provided in this application obtain link data associated with the target service provider's identifier within a target time range; each link data records the call status of one interface of the target service provider by one consumer; extracts target information of each interface of the target service provider from each link data, the target information including at least: interface identifier and number of times the interface has been accessed; based on the interface identifier and number of times the interface has been accessed, as well as the identifier and historical number of times the registered interfaces of the target service provider have been accessed, the identifier of the unregistered interfaces of the target service provider and the interfaces whose cumulative access count has reached a threshold of zero days are determined; initiates an interface maintenance process to the first account, so that the developers of the target service provider using the first account can improve the first type of relevant information for the identifier of the unregistered interface and improve the second type of relevant information for the interfaces whose cumulative access count has reached a threshold of zero days. This application, based on the automatic collection and analysis of link data, quickly and accurately identifies the interface identifiers of unregistered service providers and interfaces that have accumulated zero accesses within a certain threshold number of days. This enables developers to quickly and accurately manually improve the interface ledger. In other words, this application combines automatic collection and analysis of link data with manual entry, achieving efficient and accurate management of the interface ledger. Attached Figure Description
[0040] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0041] Figure 1 A flowchart illustrating an implementation of the interface ledger management method provided in this application embodiment;
[0042] Figure 2 A flowchart illustrating an implementation of extracting target information of each interface of the target service provider from at least each link of data, as provided in this application embodiment;
[0043] Figure 3A flowchart illustrating an implementation of extracting information from each consumer from data across various links, as provided in this application embodiment;
[0044] Figure 4 A schematic diagram of the interface ledger management device provided in this application embodiment;
[0045] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0046] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings are used to distinguish similar parts and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that illustrated herein. Detailed Implementation
[0047] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0048] like Figure 1 The flowchart described above, which is an implementation flowchart of the interface ledger management method provided in this application embodiment, may include:
[0049] Step S101: Obtain the link data associated with the target service provider's identifier within the target time range; each link data record shows the call status of an interface of the target service provider by a consumer.
[0050] In an application interconnection scenario, if an application's (hereinafter referred to as the first application) interface (hereinafter referred to as the first interface) is called by another application (hereinafter referred to as the second application), then the first application is the service provider of the first interface, and the second application is the consumer of the first interface.
[0051] In this application, a link data acquisition component can be deployed in at least one of the service provider and the consumer of the first interface to collect link data between the service provider and the caller of the first interface.
[0052] As an example, the link data acquisition component deployed in the first application can add a link data entry when it receives a call request (also known as an access request) sent by the second application through the first interface. This link data entry is identified by a globally unique link identifier (traceid). The link data entry records information such as the identifier of the first application, the name of the first interface, the interface protocol, the identifier of the second application, and the number of times the first interface has been accessed by the second application. After the first application sends a response message to the second application through the first interface, it can also record the response duration of the first interface.
[0053] As an example, the link data acquisition component deployed in the second application can add a link data entry after sending a call request to the first application through the first interface. This link data entry is identified by a unique link identifier and records information such as the identifier of the first application, the name of the first interface, the interface protocol, the identifier of the second application, and the number of times the second application accesses the first interface. After receiving the response message from the second application through the first interface, the second application can also record the response duration of the first interface.
[0054] After collecting link data, the link data acquisition component can upload the collected link data to the database in real time, or it can upload the collected link data to the database at a specified time (e.g., during the idle time of the application where the link data acquisition component is located).
[0055] Optionally, the link data acquisition component can encapsulate the acquired link data into data packets and upload them to the database based on an open-source link acquisition protocol (such as the OpenTracing protocol). When reporting link data, the link data acquisition component carries the reporting time (including the date and specific time, such as 202010092300, which represents 23:00 on October 9, 2020) and the identifier of the application in which the link data acquisition component is located.
[0056] When interface ledger management is required, the device retrieves link data associated with the target service provider's identifier from the database within a target time range. The target time range can be the day before the current date; that is, the interface ledger is maintained and updated daily using the link data from the previous day. The target service provider's identifier can be the identifier of any service provider for which interface ledger management is required.
[0057] Step S102: Extract the target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed.
[0058] This application performs statistical analysis on the extracted link data to determine the identifiers of each interface of the target service provider, as well as the number of times each interface of the target service provider is accessed within the target time range.
[0059] Step S103: Based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interfaces of the target service provider, determine the identifier of the unregistered interfaces of the target service provider, and the interfaces whose cumulative access count reaches zero after reaching the threshold number of days.
[0060] The historical access count of any registered interface refers to the number of times that registered interface has been accessed within each historical target time range. For example, the historical access count of any registered interface refers to the number of times that registered interface has been accessed each day in the past.
[0061] The identifiers of each interface determined in step S102 can be compared with the identifiers of the registered interfaces to determine the identifiers of the interfaces of the target service provider that have not been registered.
[0062] Assuming the threshold number of days is N, for any interface of the target service provider, we can obtain the sum of the number of times that interface was accessed each day within the M days prior to the current date (including the day before the current date), thus obtaining the cumulative number of times that interface was accessed over the M days. M is an integer less than or equal to N. Specifically, when any interface is first put into use, M will be less than N; after any interface has been in use for at least N days, M will equal N.
[0063] Step S104: Initiate an interface maintenance process for the first account so that the developers of the target service provider using the first account can complete the first type of relevant information for the unregistered interface identifier and complete the second type of relevant information for the interface that has been accessed for a cumulative number of days reaching the threshold.
[0064] The first account can be an account that the developer of the target service provider (hereinafter referred to as the target service provider developer) has pre-registered with the interface ledger management device. This account can be a custom account of the target service provider developer or an existing communication account of the target service provider developer, such as the developer's mobile phone number, email address or other account that can uniquely identify the developer, such as an instant messaging software account.
[0065] Optionally, the first type of relevant information may include, but is not limited to, at least some of the following: the meaning of the interface, the interface developers, the average response time of the interface, and the interface design specifications.
[0066] The second category of relevant information may include, but is not limited to, at least some of the following information: whether the interface is running normally, whether the interface is offline, etc. If the interface is offline, the second category of relevant information may also include: offline time, reason for offline, etc.
[0067] When initiating an interface maintenance process to the primary account of the target service provider, a prompt message can be displayed through the interactive interface provided by the interface ledger management device, indicating that a new interface ledger maintenance task has been created. Furthermore, if the primary account is an existing communication account of a developer, in addition to displaying the prompt message on the interactive interface provided by the interface ledger management device, a message can also be sent to the developer's communication account to remind them that the interface ledger management device has an interface ledger maintenance task pending.
[0068] The notification message may include, but is not limited to, identifiers of unregistered interfaces of the target service provider, and identifiers of interfaces that have been accessed zero times in the cumulative number of days that have reached the threshold.
[0069] For unregistered interfaces, developers can add new interfaces in the interface ledger management device to add the identifier of the unregistered interface and the corresponding first-category related information to the interface ledger;
[0070] For interfaces that have accumulated zero accesses over a certain number of days, developers can use the interface ledger management system to determine whether the interface is operating normally and whether it has been taken offline. If the interface is offline, information such as the offline time and reason must be added.
[0071] The interface ledger management method provided in this application quickly and accurately identifies the interface identifiers of unregistered service providers and interfaces that have been accessed for a cumulative number of days reaching a threshold, through automatic collection and analysis of link data. This enables developers to quickly and accurately manually improve the interface ledger. In other words, this application combines automatic collection and analysis of link data with manual entry, achieving efficient and accurate management of the interface ledger.
[0072] In an optional embodiment, one implementation of the above-mentioned initiation of the interface maintenance process to the first account of the target service provider can be:
[0073] For unregistered interfaces, a list of projects that need to be completed is sent to the first account so that the developers of the target service provider can complete the first category of relevant information for each project in the project list.
[0074] By sending the project to be improved to the primary account, the developers of the target service provider using the primary account can directly and clearly know which information needs to be improved, thereby avoiding the omission of information to be improved.
[0075] For interfaces that have accumulated zero accesses within the threshold number of days, a confirmation message is sent to the first account so that the developers of the target service provider can confirm whether the interface is running normally or whether it is an offline interface.
[0076] The confirmation information can have at least three options: Normal Operation, Abnormal Operation, and Offline Interface. Normal operation indicates that the interface is not offline and is functioning normally. Abnormal operation indicates that the interface is not offline but is functioning abnormally. The target service provider's developers can select any option based on the actual situation. If an offline interface is selected, the interface ledger management device can also output a prompt message to remind the target service provider's developers to complete information such as the offline time and reason.
[0077] In an optional embodiment, the flowchart for one method of extracting target information of each interface of the target service provider from each link data is as follows: Figure 2 As shown, it may include:
[0078] Step S201: Cluster the data of each link according to the interface identifier to determine the interface identifiers contained in each link data, and the link data contained in the category corresponding to each interface identifier.
[0079] In this embodiment, the identifier link data with the same interface of the target service provider in each link data are grouped into one category. In this way, each category corresponds to one interface of the target service provider.
[0080] When both the service provider and the consumer report link data, it is only necessary to cluster the link data reported by the same reporting party (service provider or consumer) according to the interface identifier.
[0081] Step S202: For any interface, count the number of times the interface is accessed based on the link data contained in the category corresponding to the identifier of the interface.
[0082] The link data contained in the category corresponding to any interface can be clustered according to the consumer identifier to obtain the subcategories contained in the category corresponding to any interface. Therefore, each subcategory corresponds to a consumer identifier. The maximum number of times that any interface is accessed by the same consumer within the target time range is determined for each link data record in each subcategory. The maximum number of accesses corresponding to each subcategory is obtained. The maximum number of accesses corresponding to each subcategory is summed to obtain the number of times that any interface is accessed within the target time range.
[0083] In an optional embodiment, the interface ledger management method provided in this application may further include:
[0084] Extract information about each consumer from the data of each link. The information of each consumer includes at least: consumer identifier and the number of times each interface was accessed.
[0085] In other words, in addition to extracting the target information of each interface of the target service provider from the data of each link, this application also extracts the information of the consumer of the interface of the target service provider from the data of each link.
[0086] Statistical analysis can be performed on the extracted data from each link to obtain information about each consumer.
[0087] Based on the identifiers of each consumer and the number of times each consumer accesses each interface, as well as the identifiers of registered consumers and the historical number of times each consumer accesses each interface, the identifiers of unregistered consumers and consumers whose cumulative access to the target interface reaches zero after reaching the threshold number of days are identified.
[0088] An unregistered consumer refers to a consumer that has sent a call request to the target service provider's interface but has not registered it in the interface ledger, and therefore has not subscribed to the target service provider's interface.
[0089] The identifiers of each consumer in the consumer information extracted in the previous step can be compared with the identifiers of registered consumers to identify the identifiers of unregistered consumers.
[0090] Assuming the threshold number of days is N, for any consumer, the sum of the number of times that consumer accessed the target interface of the target service provider each day within the M days prior to the current date can be obtained, resulting in the cumulative number of times that consumer accessed the target interface over the M days. Here, M is an integer less than or equal to N. When the target interface is first put into use, M will be less than N; after the target interface has been in use for at least N days, M will equal N.
[0091] A maintenance process is initiated for the second account so that the consumer-side developers using the second account can complete the third category of relevant information for unregistered consumers and the fourth category of relevant information for consumers whose cumulative access to the target interface is zero after reaching the threshold number of days. Specifically, the consumer-side developers are either developers of unregistered consumers or developers of consumers whose cumulative access to the target interface is zero after reaching the threshold number of days. In other words, for unregistered consumers, the consumer-side developers are the developers of the unregistered consumers; for consumers whose cumulative access to the target interface is zero after reaching the threshold number of days, the consumer-side developers are the developers of the consumers whose cumulative access to the target interface is zero after reaching the threshold number of days.
[0092] Since consumers that call the service provider's interface need to meet certain conditions, the consumer's developers need to provide relevant information about the consumer (i.e., the third type of relevant information) so that the service provider's developers can determine whether to allow the consumer to call the service provider's interface.
[0093] The third category of relevant information may include, but is not limited to, at least some of the following: consumption scenario, actual subscribers, peak number of API calls, and average daily number of API calls.
[0094] The fourth category of relevant information may include, but is not limited to, at least some of the following information: whether the target interface consumption is normal (i.e., whether the target interface subscriber is paying normally, etc.), whether the target interface subscription has been canceled, etc.
[0095] In an optional embodiment, the flowchart for one method of extracting information about each consumer from data across each link is shown below. Figure 3 As shown, it may include:
[0096] Step S301: Cluster the data of each link according to the consumer identifier to determine the consumer identifiers contained in each link data, and the link data contained in the category corresponding to each consumer identifier.
[0097] In this embodiment of the application, link data with the same consumer identifier in each link data are divided into one category. Therefore, each category corresponds to one consumer identifier.
[0098] When both the service provider and the consumer report link data, it is only necessary to cluster the link data reported by the same reporting party (service provider or consumer) according to the consumer identifier.
[0099] Step S302: For any consumer, count the number of times the consumer accesses each interface based on the link data contained in the category corresponding to the identifier of the consumer.
[0100] The link data in the category corresponding to any consumer can be clustered according to the interface identifier to obtain the subcategories contained in the category corresponding to any consumer. Therefore, each subcategory corresponds to an interface. The maximum number of times that any consumer accesses the same interface within the target time range is determined by the link data records in each subcategory. The maximum number of accesses corresponding to each subcategory is the number of times that any consumer accesses the interface corresponding to any category within the target time range.
[0101] In an optional embodiment, the interface ledger management method provided in this application may further include:
[0102] Filter out the application interconnection layer link data from the data of each link.
[0103] Depending on actual needs, when collecting link data, the link data collection component may collect link data not only at the application interconnection layer but also at the non-application interconnection layer. Therefore, the link data reported by the link data collection component may include non-application interconnection layer link data. However, the interface ledger management method of this application only requires application interconnection layer link data. Therefore, in order to reduce the amount of data processing in subsequent processes and improve processing efficiency, application interconnection layer link data can be filtered from each link data for subsequent clustering statistics.
[0104] Optionally, link data containing specified keywords can be identified as application interconnect layer link data. In this application, when collecting link data, the link data acquisition component adds specified keywords to application interconnect layer link data, while not adding specified keywords to non-application interconnect layer link data. This allows for the differentiation between application interconnect layer link data and non-application interconnect layer link data using specified keywords.
[0105] When clustering the data of each link according to the interface identifier, the link data of the application interconnection layer are clustered according to the interface identifier.
[0106] When clustering the data of each link according to the consumer identifier, the link data of the application interconnection layer is clustered according to the consumer identifier.
[0107] In an optional embodiment, the interface ledger management method provided in this application may further include:
[0108] For interfaces that have accumulated zero accesses over a certain number of days, an approval process is initiated with the third-party account of the subscriber of the interface that has accumulated zero accesses over a certain number of days, so that the subscriber can determine whether to agree to take the interface offline.
[0109] An interface that has reached the threshold of zero accesses may be an interface that is no longer accessed by consumers, but it may also be an interface that consumers are still subscribing to, but using very infrequently. Therefore, an approval process needs to be initiated with the subscribers of the interface so that they can determine whether they agree to take the interface offline after reaching the threshold of zero accesses. If all subscribers agree to take the interface offline, the developers of the target service provider can take the interface offline. If any subscriber does not agree to take the interface offline, the developers of the target service provider cannot take the interface offline.
[0110] For unregistered consumers, an approval process is initiated with the primary account so that the developers using the primary account can determine whether to approve the consumer's call to the target service provider's interface.
[0111] For unregistered consumers, after the consumer's developers complete the third category of relevant information, an approval process can be initiated with the primary account. The target service provider's developers will then determine whether to approve the consumer's subscription to the target service provider's interface based on the third category of relevant information completed by the consumer's developers. If the target service provider's developers approve the consumer's subscription to the target service provider's interface, the consumer can call the target service provider's interface after the consumer's subscription personnel have subscribed to it; otherwise, the consumer cannot subscribe to or call the target service provider's interface.
[0112] Corresponding to the method embodiments, this application also provides an interface ledger management device. A schematic diagram of the interface ledger management device provided in this application embodiment is shown below. Figure 4 As shown, it may include:
[0113] The acquisition module 401, extraction module 402, determination module 403, and processing module 404 are defined; among them,
[0114] The acquisition module 401 is used to acquire the data of each link associated with the target service provider's identifier within the target time range; each link data record records the call status of an interface of the target service provider by a consumer.
[0115] The extraction module 402 is used to extract target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed.
[0116] The determination module 403 is used to determine the identifier of the unregistered interface of the target service provider and the interface whose access count has reached zero after reaching a threshold number of days, based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interface of the target service provider.
[0117] The processing module 404 is used to initiate an interface maintenance process to the first account, so that the developers using the first account of the target service provider can improve the first type of relevant information for the identifier of the unregistered interface, and improve the second type of relevant information for the interface whose cumulative access count is zero after reaching the threshold number of days.
[0118] The interface provided in this application embodiment, through the automatic collection and analysis of link data in the management device, can quickly and accurately identify the interface identifier of unregistered service providers, as well as the interfaces that have been accessed for a cumulative threshold number of days, thereby enabling developers to quickly and accurately manually improve the interface ledger. In other words, this application combines automatic collection and analysis of link data with manual entry, achieving efficient and accurate management of the interface ledger.
[0119] In an optional embodiment, when the processing module 404 initiates an interface maintenance process to the first account of the target service provider, it is used to:
[0120] For the identifier of the unregistered interface, a list of projects that need to be improved is sent to the first account so that the developers of the target service provider can improve the first type of relevant information corresponding to each project in the project list;
[0121] For interfaces that have accumulated zero accesses within the threshold number of days, a confirmation message is sent to the first account of the target service provider so that the developers can confirm whether the interface is running normally or whether it is an offline interface.
[0122] In an optional embodiment, the extraction module 402 extracts target information of each interface of the target service provider from the data of each link, including:
[0123] The link data is clustered according to the interface identifier to determine the interface identifier contained in each link data, and the link data contained in the category corresponding to each interface identifier;
[0124] For any given interface, the number of times the interface is accessed is counted based on the link data contained in the category corresponding to the identifier of the interface.
[0125] In an optional embodiment, the extraction module 402 is further configured to:
[0126] Extract information about each consumer from the data of each link. The information of each consumer includes at least: consumer identifier and the number of times each interface is accessed.
[0127] The determining module 403 is further configured to: determine the identifier of unregistered consumers and the number of times each consumer accesses each interface based on the identifier of each consumer and the number of times each consumer has accessed each interface in the past, as well as the identifier of registered consumers and the number of times each consumer has accessed each interface in the past.
[0128] The processing module 404 is further configured to: initiate a maintenance process to the second account, so that the consumer developers using the second account can improve the third type of relevant information for the identifier of the unregistered consumer, and improve the fourth type of relevant information for the consumer whose cumulative access to the target interface is zero after reaching the threshold number of days.
[0129] In an optional embodiment, when the extraction module 402 extracts information about each consumer from the data of each link, it is used to:
[0130] The data of each link is clustered according to the consumer identifier to determine each consumer identifier contained in each link data, and the link data contained in the category corresponding to each consumer identifier;
[0131] For any consumer, the number of times the consumer accesses each interface is counted based on the link data contained in the category corresponding to the identifier of the consumer.
[0132] In an optional embodiment, the interface ledger management device further includes:
[0133] The filtering module is used to filter out application interconnection layer link data from the link data.
[0134] When the extraction module 402 clusters the link data according to the interface identifier, it is used to: cluster the link data of the application interconnection layer according to the interface identifier;
[0135] When the extraction module 402 clusters the link data according to the consumer identifier, it is used to: cluster the link data at the application interconnection layer according to the consumer identifier.
[0136] In an optional embodiment, the processing module 404 is further configured to:
[0137] For interfaces that have accumulated zero accesses over a certain number of days, an approval process is initiated with the third-party account of the subscriber of the interface that has accumulated zero accesses over a certain number of days, so that the subscriber can determine whether to agree to take the interface that has accumulated zero accesses over a certain number of days offline.
[0138] For the unregistered consumer, an approval process is initiated with the first account so that the developer using the first account can determine whether to approve the consumer's call to the target service provider's interface.
[0139] Corresponding to the method embodiments, this application also provides an electronic device, a schematic diagram of which is shown below. Figure 5 As shown, it 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.
[0140] In this embodiment, the number of processor 1, communication interface 2, memory 3, and communication bus 4 is at least one, and processor 1, communication interface 2, and memory 3 communicate with each other through communication bus 4.
[0141] Processor 1 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.
[0142] Memory 3 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device.
[0143] The memory 3 stores a program, and the processor 1 can call the program stored in the memory 3. The program is used for:
[0144] Obtain data for each link associated with the target service provider's identifier within the target time range; each link data record shows the call status of one interface of the target service provider by one consumer.
[0145] Extract target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed.
[0146] Based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interfaces of the target service provider, the identifier of the unregistered interfaces of the target service provider and the interfaces whose cumulative access count reaches zero after reaching the threshold number of days are determined.
[0147] An interface maintenance process is initiated for the first account so that the developers of the target service provider using the first account can improve the first type of relevant information for the identifier of the unregistered interface, and improve the second type of relevant information for the interface whose cumulative access count reaches the threshold number of days and is zero.
[0148] Optionally, the refined and extended functions of the program can be found in the description above.
[0149] This application embodiment also provides a storage medium that can store a program suitable for execution by a processor, the program being used for:
[0150] Obtain data for each link associated with the target service provider's identifier within the target time range; each link data record shows the call status of one interface of the target service provider by one consumer.
[0151] Extract target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed.
[0152] Based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interfaces of the target service provider, the identifier of the unregistered interfaces of the target service provider and the interfaces whose cumulative access count reaches zero after reaching the threshold number of days are determined.
[0153] An interface maintenance process is initiated for the first account so that the developers of the target service provider using the first account can improve the first type of relevant information for the identifier of the unregistered interface, and improve the second type of relevant information for the interface whose cumulative access count reaches the threshold number of days and is zero.
[0154] Optionally, the refined and extended functions of the program can be found in the description above.
[0155] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0156] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through interfaces, devices, or units, and may be electrical, mechanical, or other forms.
[0157] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0158] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0159] It should be understood that in the embodiments of this application, the claims, various embodiments, and features can be combined with each other to solve the aforementioned technical problems.
[0160] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0161] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not 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. A method for managing interface ledgers, characterized in that, The method includes: Obtain data for each link associated with the target service provider's identifier within the target time range; each link data record shows the call status of one interface of the target service provider by one consumer. Extract target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed. Based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interfaces of the target service provider, the identifier of the unregistered interfaces of the target service provider and the interfaces whose cumulative access count reaches zero after reaching the threshold number of days are determined. An interface maintenance process is initiated for the first account, so that the developers of the target service provider using the first account can improve the first type of relevant information for the identifier of the unregistered interface, and improve the second type of relevant information for the interface whose cumulative access count is zero after reaching the threshold number of days. The first type of relevant information includes at least some of the following: interface meaning, interface developers, average interface response time, and interface design description; the second type of relevant information includes at least some of the following: whether the interface is running normally, whether the interface is offline, the offline time, and the reason for offline. The process of initiating interface maintenance to the first account includes: For the identifier of the unregistered interface, a list of projects that need to be improved is sent to the first account so that the developers of the target service provider can improve the first type of relevant information corresponding to each project in the project list; For interfaces that have accumulated zero accesses within the threshold number of days, a confirmation message is sent to the first account so that the developers of the target service provider can confirm whether the interface is operating normally or whether it is an offline interface.
2. The method according to claim 1, characterized in that, The step of extracting target information for each interface of the target service provider from the data of each link includes: The link data is clustered according to the interface identifier to determine the interface identifier contained in each link data, and the link data contained in the category corresponding to each interface identifier; For any given interface, the number of times the interface is accessed is counted based on the link data contained in the category corresponding to the identifier of the interface.
3. The method according to claim 1, characterized in that, Also includes: Extract information about each consumer from the data of each link. The information of each consumer includes at least: consumer identifier and the number of times each interface is accessed. Based on the identifiers of each consumer and the number of times each consumer accesses each interface, as well as the identifiers of registered consumers and the historical number of times each consumer accesses each interface, the identifiers of unregistered consumers and consumers whose cumulative access to the target interface is zero after reaching the threshold number of days are determined. A maintenance process is initiated for the second account so that the consumer developers using the second account can improve the third type of relevant information for the unregistered consumer identifier, and improve the fourth type of relevant information for the consumer whose cumulative access to the target interface is zero after reaching the threshold number of days. The third type of relevant information includes at least some of the following information: consumption scenario, actual subscribers, peak number of interface calls, and average daily number of interface calls. The fourth type of relevant information includes at least some of the following information: whether the target interface consumption is normal, and whether the subscription to the target interface has been canceled.
4. The method according to claim 3, characterized in that, The extraction of information about each consumer from the data of each link includes: The data of each link is clustered according to the consumer identifier to determine each consumer identifier contained in each link data, and the link data contained in the category corresponding to each consumer identifier; For any consumer, the number of times the consumer accesses each interface is counted based on the link data contained in the category corresponding to the identifier of the consumer.
5. The method according to claim 2 or 4, characterized in that, Also includes: From the data of each link, filter out the link data at the application interconnection layer; When clustering the data of each link according to the interface identifier, the link data of the application interconnection layer is clustered according to the interface identifier; When clustering the data of each link according to the consumer identifier, the link data of the application interconnection layer is clustered according to the consumer identifier.
6. The method according to claim 3, characterized in that, Also includes: For interfaces that have accumulated zero accesses over a certain number of days, an approval process is initiated with the third-party account of the subscriber of the interface that has accumulated zero accesses over a certain number of days, so that the subscriber can determine whether to agree to take the interface that has accumulated zero accesses over a certain number of days offline. For the unregistered consumer, an approval process is initiated with the first account so that the developer using the first account can determine whether to approve the consumer's call to the target service provider's interface.
7. An interface ledger management device, characterized in that, The device includes: The acquisition module is used to obtain the data of each link associated with the target service provider's identifier within the target time range; each link data record records the call status of an interface of the target service provider by a consumer. The extraction module is used to extract target information of each interface of the target service provider from the data of each link. The target information includes at least: interface identifier and number of times the interface is accessed. The determination module is used to determine the identifier of the unregistered interface of the target service provider and the interface whose access count has reached zero after reaching a threshold number of days, based on the interface identifier and access count of each interface, as well as the identifier and historical access count of the registered interface of the target service provider. The processing module is used to initiate an interface maintenance process to the first account, so that the developers of the target service provider using the first account can improve the first type of relevant information for the identifier of the unregistered interface, and improve the second type of relevant information for the interface whose cumulative access count is zero after reaching the threshold number of days. The first type of relevant information includes at least some of the following: interface meaning, interface developers, average interface response time, and interface design description; the second type of relevant information includes at least some of the following: whether the interface is running normally, whether the interface is offline, the offline time, and the reason for offline. Specifically, the processing module initiates an interface maintenance process to the first account, which is used to: send a list of projects that need to be improved to the first account for the identifier of the unregistered interface, so that the developers of the target service provider can improve the first type of relevant information corresponding to each project in the project list; and send a confirmation message to the first account for the interface that has been accessed for a cumulative number of days reaching the threshold, so that the developers of the target service provider can confirm whether the interface is running normally or whether it is an offline interface.
8. An electronic device, characterized in that, include: Memory, used to store programs; A processor is configured to call and execute the program in the memory, thereby implementing the various steps of the interface ledger management method as described in any one of claims 1-6.
9. A readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements each step of the interface ledger management method as described in any one of claims 1-6.