CN111209325A - Service system interface identification method, device and storage medium - Google Patents
Service system interface identification method, device and storage medium Download PDFInfo
- Publication number
- CN111209325A CN111209325A CN201911425810.0A CN201911425810A CN111209325A CN 111209325 A CN111209325 A CN 111209325A CN 201911425810 A CN201911425810 A CN 201911425810A CN 111209325 A CN111209325 A CN 111209325A
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- type
- service system
- association
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000004044 response Effects 0.000 claims abstract description 126
- 230000005540 biological transmission Effects 0.000 claims description 11
- 230000000694 effects Effects 0.000 abstract description 5
- 238000007726 management method Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000014759 maintenance of location Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a service system interface identification method, which comprises the following steps: determining the association degree data among request response data generated by a service system; determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold; and dividing the service interface of the target data into the same data interface so as to transmit data from the data interface when the target data is requested. The invention also discloses a service system interface recognition device and a computer readable storage medium. By dividing the service interfaces with the relevance higher than the relevance threshold into the same data interface, the efficiency and the effect of interface identification and interface management of the service system are improved.
Description
Technical Field
The present invention relates to the field of network management technologies, and in particular, to a service system interface identification method, a service system interface identification apparatus, and a computer-readable storage medium.
Background
No matter the service system is deployed in an intranet or an extranet, a manager needs to configure different service interfaces to know which users access which service interfaces and which interfaces relate to which important or sensitive data. In a specific use environment, a plurality of service systems are possible in the network, and some service systems have hundreds of interfaces, so that it is obviously impractical for a manager to manually configure each interface, and the method has the disadvantages of large workload, time and labor consumption and easy error; when the number of interfaces is large, a large amount of identification time is consumed for the service system to identify the interfaces of the received data requests, and the identification process is easy to generate false identification.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a service system interface identification method, a service system interface identification device and a computer readable storage medium, and aims to solve the problem that in the prior art, the service system interface identification efficiency is low and management is not facilitated.
In order to achieve the above object, the present invention provides a service system interface identification method, which comprises the following steps:
determining the association degree data among request response data generated by a service system;
determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold;
and dividing the service interface of the target data into the same data interface so as to transmit data from the data interface when the target data is requested.
Optionally, the step of determining the association degree data between the request response data generated by the service system includes:
acquiring data types of request response data generated by a service system, and determining a relevancy extractor corresponding to each data type;
and determining the association degree data among the request response data of each data type by using the association degree extractor corresponding to each data type.
Optionally, the step of obtaining data types of request response data generated by the service system, and determining an association extractor corresponding to each data type, includes:
if the data type is a first data type, determining that an association extractor corresponding to the first data type is a first association extractor;
if the data type is a second data type, determining that an association extractor corresponding to the second data type is a second association extractor;
if the data type is a third data type, determining that an association extractor corresponding to the third data type is a third association extractor; the first data type is an html data type, the second data type is a json data type, and the json data type comprises: and the third data type is other data types except the first data type and the second data type.
Optionally, the step of determining the association degree data between the request response data of each data type by using the association degree extractor corresponding to each data type includes:
if the data type is the first data type, a first relevance extractor is used for obtaining a weighted average value of the style relevance, the structure relevance and the display content relevance of the request response data of the first data type, and the weighted average value is determined as relevance data of target data of the first data type;
if the data type is a second data type, taking the key name and the structure type of the request response key after the value is removed and the key is left as matching conditions, calculating the matching times of the matching conditions by using a second relevancy extractor, and determining relevancy data of target data of the second data type according to the matching times;
and if the data type is a third data type, extracting fingerprint information of the target data of the third data type by using a third association extractor, and determining association data of the target data of the third data type according to the fingerprint information.
Optionally, the step of determining target data according to the association degree data, where an association degree between request response data in the target data is above an association degree threshold includes:
determining the association degree between the request response data of each data type according to the association degree data;
judging whether the association degree between the request response data of each data type exceeds a corresponding association degree threshold value or not;
and if so, determining the associated data with the association degree exceeding the corresponding association degree threshold value and the associated data type corresponding to the associated data, and determining the associated data as the target data corresponding to the associated data type.
Optionally, after the step of dividing the service interface of the target data into the same data interface to perform data transmission from the data interface when the target data requests, the method further includes:
classifying the divided data interfaces according to the classification parameters of the target data, and dividing the divided data interfaces into different types of data interfaces so as to transmit data from the data interfaces of the corresponding types when the target data is requested; the classification parameters include: request type, return type, request mode, access information, website path depth, request association degree and response association degree.
Optionally, the step of classifying the classified data interfaces into different categories of data interfaces to perform data transmission from the data interfaces of the corresponding categories when a target data request is received includes:
acquiring feature information of the classified target data corresponding to each type of data interface, and taking the feature information as interface information corresponding to each type of data interface;
and defining each type of data interface according to the interface information so as to transmit data from the data interface of the corresponding type according to the definition of each type of data interface when a target data request is made.
Optionally, after the step of dividing the service interface of the target data into the same data interface to perform data transmission from the data interface when the target data requests, the method further includes:
constructing a parent-child relationship among all service system interfaces according to a data head source address field of target data and a hyperlink in a target data response body;
and generating an interface relation tree of the business system based on the parent-child relation, and identifying the hierarchical relation of the business system interface based on the interface relation tree.
In addition, in order to achieve the above object, the present invention further provides a service system interface recognition apparatus, where the service system interface recognition apparatus includes a memory, a processor, and a service system interface recognition program stored on the processor and operable on the processor, and the processor implements the steps of the service system interface recognition method when executing the service system interface recognition program.
In addition, to achieve the above object, the present invention further provides a computer readable storage medium, having a service system interface identification program stored thereon, which when executed by a processor implements the steps of the service system interface identification method as described above.
In the embodiment of the invention, the association degree data among the request response data generated by the service system is determined, the target data is determined according to the association degree data, and the service interfaces of the target data are divided into the same data interface, so that when an uploading or downloading request corresponding to the target data is received, data transmission is carried out from the same interface corresponding to the target data, the service interfaces with the association degree exceeding the association degree threshold are classified into the same service interface, the number of the interfaces is reduced, the time for identifying the interfaces and the time for managing the interfaces can be reduced, the interface identification and the interface management are more facilitated, and the efficiency and the effect of the interface identification and the management are improved.
Drawings
Fig. 1 is a schematic structural diagram of a service system interface identification apparatus of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a service system interface identification method according to the present invention;
FIG. 3 is an application scenario diagram of a specific application embodiment of the service system interface identification method of the present invention;
FIG. 4 is a schematic flow chart illustrating a detailed process of determining relevancy data between request response data generated by a service system according to a preferred embodiment of the interface identification method of a service system of the present invention;
FIG. 5 is a schematic diagram illustrating a detailed flow of determining target data according to the relevancy data in a preferred embodiment of the service system interface identification method of the present invention;
fig. 6 is a flowchart illustrating a service system interface identification method according to a second embodiment of the present invention;
fig. 7 is a flowchart illustrating a service system interface identification method according to a third embodiment of the present invention.
FIG. 8 is a flowchart illustrating a tree diagram for establishing a relationship between interfaces of a service system according to an embodiment of the method for identifying interfaces of a service system of the present invention;
the implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Determining the association degree data among request response data generated by a service system; determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold; and dividing the service interface of the target data into the same data interface so as to transmit data from the data interface when the target data is requested.
The current business system interface identification method has the problems of high interface identification difficulty, low efficiency, being not beneficial to a manager to manage the business system according to interface information and the like when the interfaces of the business system are excessive. Therefore, the invention provides a service system interface identification method, a service system interface identification device and a computer readable storage medium, by determining the association degree data among the request response data of different data types generated by a service system, determining the target data corresponding to the request response data of each data type according to the association degree data, and classifying the service interface corresponding to the target data with the association degree higher than the association degree threshold value into the same data interface, so as to perform data transmission from the data interface when the target data is requested, which is beneficial to identifying the data interfaces corresponding to the data requests of different types according to the classified data interfaces, and is convenient for a manager to perform analysis and management of the service system through the classified interfaces, thereby improving the efficiency of interface identification and management.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a service system interface identification apparatus in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the service system interface identifying device may include: a communication bus 1002, a processor 1001, such as a CPU, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the business system interface identifying means configuration shown in fig. 1 does not constitute a limitation of business system interface identifying means and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a business system interface identification program.
In the service system interface identification apparatus shown in fig. 1, the network interface 1004 is mainly used for connecting to a background server and performing data communication with the background server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and processor 1001 may be configured to invoke a business system interface identification program stored in memory 1005 and perform the following operations:
determining the association degree data among request response data generated by a service system;
determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold;
and dividing the service interface of the target data into the same data interface so as to transmit data from the data interface when the target data is requested.
Alternatively, the processor 1001 may call the business system interface identification program stored in the memory 1005, and further perform the following operations:
acquiring data types of request response data generated by a service system, and determining a relevancy extractor corresponding to each data type;
and determining the association degree data among the request response data of each data type by using the association degree extractor corresponding to each data type.
Alternatively, the processor 1001 may call the business system interface identification program stored in the memory 1005, and further perform the following operations:
if the data type is a first data type, determining that an association extractor corresponding to the first data type is a first association extractor;
if the data type is a second data type, determining that an association extractor corresponding to the second data type is a second association extractor;
if the data type is a third data type, determining that an association extractor corresponding to the third data type is a third association extractor; the first data type is an html data type, the second data type is a json data type, and the json data type comprises: and the third data type is other data types except the first data type and the second data type.
Alternatively, the processor 1001 calls the service system interface identification program stored in the memory 1005 and performs the following operations:
if the data type is the first data type, a first relevance extractor is used for obtaining a weighted average value of the style relevance, the structure relevance and the display content relevance of the request response data of the first data type, and the weighted average value is determined as relevance data of target data of the first data type;
if the data type is a second data type, taking the key name and the structure type of the request response key after the value is removed and the key is left as matching conditions, calculating the matching times of the matching conditions by using a second relevancy extractor, and determining relevancy data of target data of the second data type according to the matching times;
and if the data type is a third data type, extracting fingerprint information of the target data of the third data type by using a third association extractor, and determining association data of the target data of the third data type according to the fingerprint information.
Alternatively, the processor 1001 may call the business system interface identification program stored in the memory 1005, and further perform the following operations:
determining the association degree between the request response data of each data type according to the association degree data;
judging whether the association degree between the request response data of each data type exceeds a corresponding association degree threshold value or not;
and if so, determining the associated data with the association degree exceeding the corresponding association degree threshold value and the associated data type corresponding to the associated data, and determining the associated data as the target data corresponding to the associated data type.
Optionally, after the step of dividing the service interface of the target data into the same data interface, so as to perform data transmission from the data interface when the target data is requested, the processor 1001 may call the service system interface identification program stored in the memory 1005, and further perform the following operations:
classifying the divided data interfaces according to the classification parameters of the target data, and dividing the divided data interfaces into different types of data interfaces so as to transmit data from the data interfaces of the corresponding types when the target data is requested; the classification parameters include: request type, return type, request mode, access information, website path depth, request association degree and response association degree.
Alternatively, the processor 1001 may call the business system interface identification program stored in the memory 1005, and further perform the following operations:
acquiring feature information of the classified target data corresponding to each type of data interface, and taking the feature information as interface information corresponding to each type of data interface;
and defining each type of data interface according to the interface information so as to transmit data from the data interface of the corresponding type according to the definition of each type of data interface when a target data request is made.
Optionally, after the step of dividing the service interface of the target data into the same data interface, so as to perform data transmission from the data interface when the target data is requested, the processor 1001 may call the service system interface identification program stored in the memory 1005, and further perform the following operations:
constructing a parent-child relationship among all service system interfaces according to a data head source address field of target data and a hyperlink in a target data response body;
and generating an interface relation tree of the business system based on the parent-child relation, and identifying the hierarchical relation of the business system interface based on the interface relation tree.
Referring to fig. 2, fig. 2 is a flowchart of a first embodiment of a service system interface identification method of the present invention, in this embodiment, the service system interface identification method includes the following steps:
step S10: determining the association degree data among request response data generated by a service system;
the service system is a system which helps the basic system to process service logic and ensures that the basic system is not coupled with the service as much as possible. Common service systems include a url (Uniform Resource Locator), a request parameter, and a restful interface-based service system. The restful interface is an interface of a restful style, and the restful can be understood as a specification, constraint and principle of an architecture, and an interface conforming to the specification, constraint and principle of the architecture is an interface of the restful style; the interface is a reference type for defining the agreement, and can include an interface inside the program (for example, an interface needs to be thrown out for calling inside the system for exchange between login and posting) and an interface outside the system (for example, between a shopping website and a third party payment, the third party does not provide a database for a shopper, but provides an interface for calling the shopping website). Generally, a service system based on a restful interface requests a page only once or several times, other data are loaded through the restful interface, and request parameters and return results of different pages are different, formats of the request data generally include json (JS Object Notation), xml (EXtensible markup language), xxx-url-form (http post request default data format), and the return data generally include json and xml formats.
Referring to fig. 3, in a specific application scenario, the service system establishes a communication connection with the gateway, and the gateway establishes a communication connection with the user terminal. When a user accesses a service system, the request and response data of the service system connected with the gateway are obtained through the gateway, the obtained request and response data are analyzed through a data analysis tool, and the analyzed data are returned to a user side connected with the gateway. According to the analyzed data, a user can conveniently acquire the operation condition of the user service interface, the downloaded and uploaded data information and the like, and a manager can conveniently manage and find risks in time. Therefore, before determining the association data among the request response data generated by the service system, the request and response data of all users accessing the service system, i.e. the request response data generated by the service system, are audited from the gateway establishing communication connection with the service system. The request response data generated by the service system has different data types, and may be in a json format or an xml format, and the like, so that after the gateway audits all the request response data generated by the service system, the data types of the request response data generated by the service system are obtained first, the association degree extractor corresponding to each data type is determined, and the association degree extractor corresponding to each data type is used for determining the association degree data of the request response data of each data type; the relevancy extractor is used as a relevancy extraction tool and is mainly used for extracting relevancy data of request response data generated by a business system, relevancy extractors corresponding to different data types are different, and the relevancy data of the request response data of each data type is determined by using the relevancy extractor corresponding to each data type, so that the reliability of the relevancy data can be improved. Therefore, to determine the association degree extractor corresponding to each data type, the data type of the request response data generated by the business system is determined first, and the request response data generated by the business system is classified.
As shown in fig. 4, fig. 4 is a schematic diagram illustrating a detailed flow of determining the relevancy data between request response data generated by the business system in a preferred embodiment. As can be seen from the figure, the present embodiment provides a better classification manner, in which request response data generated by a service system is divided into three data types, and then three association degree extractors corresponding to the three data types are determined. That is, when request response data generated by a service system is of a first data type, determining that an association extractor corresponding to the first data type is a first association extractor, when the data type is of a second data type, determining that an association extractor corresponding to the second data type is a second association extractor, and when the data type is of a third data type, determining that an association extractor corresponding to the third data type is a third association extractor. The first data type is an html data type, namely when request response data are data in an html format, the data type corresponding to the html format is determined to be the first data type; the second data type is a json data type, and the json data type comprises: the data types corresponding to the xml format, the xxx-url-encoded-form format and the json format, that is, when the request response data is a data type corresponding to any one of the xml format, the xxx-url-encoded-form format and the json format, the current request response data can be considered as the second data type; the third data type is other data types except the first data type and the second data type, namely the data types corresponding to other formats except html format, xml format, xxx-url-encoded-form format and json format are determined as the third data type.
After determining the relevance extractor corresponding to each data type, when the request response data is of a first data type (html data type), using the first relevance extractor to obtain a weighted average value of the style relevance, the structure relevance and the display content relevance of the request response data of the first data type, and determining the weighted average value as the relevance data of the target data of the first data type, wherein the style relevance is to extract the contents of style-related fields in each data packet in sequence, and comparing the style-type relevance of two pages through the related fields; the structural association degree is to extract the name of each data packet and compare the association degree through the hierarchical relationship among the data packets; the display content relevance is to compare relevance according to text content, and a weighted average value is taken for the three relevance obtained by comparing relevance, and the weight of the weighted average value can be determined according to factors such as relevance, and because the text content has a situation of low relevance, a preferred weight value taking mode in this embodiment is to sequentially take the weights of the style relevance, the structure relevance and the display content relevance as 0.4, 0.4 and 0.2. When the request response data is of a second data type (json data type), the key name and the structure type of the request response key after value removal and key retention are used as matching conditions, a second relevance extractor is used for calculating the matching times of the matching conditions, and the relevance data of the target data of the second data type is determined according to the matching times, wherein before the value removal and key retention, if the data format of the request corresponding data is an xml format and an xxx-url-form format, the data of the xml format and the xxx-url-form format need to be converted into the json format, if the data is of the json format, the value removal and key retention (key value retention is cleared), so that the next step is convenient for carrying out relevance matching by taking the key name and the structure type as the matching conditions, and when the key name or the structure type of two json data are matched, the data are marked as matching once, and calculating the association degree by calculating the matching times of the matched matching conditions, wherein the calculation formula is the quotient of the matching times and the total matching times (the matching times plus the non-matching times). And when the request response data is of the third data type, extracting fingerprint information of the target data of the third data type by using a third association extractor, and determining association data of the target data of the third data type according to the fingerprint information.
Step S20: determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold;
determining the association degree between the request response data according to the association degree data between the request response data generated by the service system, judging whether the association degree exceeds an association degree threshold, if so, determining the request response data with the association degree exceeding the association degree threshold as target data, and the target data meets the condition that the association degree is above the association degree threshold.
Since the association degree data corresponding to different types of request-response data can be obtained when the data types of the request-response data are not consistent, this embodiment provides a better implementation manner, and referring to fig. 5, after determining the association degree data among the request-response data generated by the service system, the step of determining the target data according to the association degree data may include: determining the association degree of the request response data of each data type according to the association degree data; judging whether the association degree of the request response data of each data type exceeds a corresponding association degree threshold value or not; if the correlation degree exceeds the corresponding correlation degree threshold value, determining the correlation data with the correlation degree exceeding the corresponding correlation degree threshold value and the correlation data type corresponding to the correlation data, and determining the correlation data as the target data corresponding to the correlation data type; and if not, judging that the associated data with the association degree smaller than the corresponding association degree threshold value is not the target data. And determining target data corresponding to different data types from the request response data of different data types according to the association data, and firstly determining the association of the request response data of each data type according to the association data.
Specifically, when the data type of the request response data is the first data type, the association degree data may include style association degree data, structure association degree data, display content association degree data, a weight of each association degree, an association degree obtained by weight calculation, and the like; when the data type of the request response data is the second data type, the association degree data may include the number of times of key name matching, the number of times of structure type matching, the number of times of key name and structure type matching at the same time, the association degree calculated according to the number of times of matching, and the like; when the data type of the request response data is the third data type, the association degree data may include the number of times of fingerprint information matching, the association degree calculated according to the number of times of fingerprint matching, and the like. Determining the association degree between the request response data of each data type according to the association degree data, judging whether the association degree between the request response data of each data type exceeds a corresponding association degree threshold, if so, determining the association data of which the association degree exceeds the corresponding association degree threshold and the associated data type corresponding to the association data, determining the association data as target data corresponding to the associated data type, and if not, determining that the request response data of which the association degree does not exceed the corresponding association degree threshold are not associated. The corresponding relevancy threshold refers to a relevancy threshold corresponding to each data type, that is, each data type has a corresponding relevancy threshold.
If the data type is the first data type, comparing the association degree between the request response data of the first data type with an association degree threshold corresponding to the first data type, judging whether the association degree between the request response data of the first data type exceeds the association degree threshold corresponding to the first data type, if so, determining the request response data of which the association degree exceeds the association degree threshold corresponding to the first data type as the first association data, determining the first data type corresponding to the first association data as the first association data type, and determining the first association data as the target data corresponding to the first association data type; if the data type is the second data type, comparing the association degree between the request response data of the second data type with an association degree threshold corresponding to the second data type, judging whether the association degree between the request response data of the second data type exceeds the association degree threshold corresponding to the second data type, if so, determining the request response data of which the association degree exceeds the association degree threshold corresponding to the second data type as second associated data, determining the second data type corresponding to the second associated data as the second associated data type, and determining the second associated data as target data corresponding to the second associated data type; and if the data type is the third data type, comparing the association degree between the request response data of the third data type with an association degree threshold corresponding to the third data type, judging whether the association degree between the request response data of the third data type exceeds the association degree threshold corresponding to the third data type, if so, determining the request response data of which the association degree exceeds the association degree threshold corresponding to the third data type as third associated data, determining the third data type corresponding to the third associated data as the third associated data type, and determining the third associated data as target data corresponding to the third associated data type. Therefore, the target data corresponding to different data types can be determined according to the association degree data among the request response data generated by the service system.
Step S30: dividing the service interface of the target data into the same data interface so as to transmit data from the data interface when the target data is requested;
according to the association degree data of the request response data of the service system, after the request response data of which the association degree exceeds the association degree threshold is determined as target data, the service interfaces of the target data are divided into the same data interface. In the process of determining the association between the request response data of each data type, the first request response data of the corresponding data type is used as reference data, and the subsequent request response data of the corresponding data type is compared with the first data to obtain the association, so that when the number of the request response data of the corresponding data type is N (N is a natural number), N-1 association degrees are obtained, and the association degrees exceeding the corresponding association degree threshold in the N-1 association degrees may be zero, one or more, the corresponding target data may also be zero, one or more, and after the service interface of the target data is divided into the same data interface, the obtained divided data interface may also be zero, one or more correspondingly. No matter whether the divided data interface is one or more, the number of the interfaces is reduced after the business interface of the target data is divided into the same data interface, so that when the business system receives a target data request, the interface corresponding to the target data can be found more quickly, and data transmission is carried out from the data interface. It is worth mentioning that when the divided data interfaces are zero, that is, there is no target data with the association degree higher than the corresponding association degree threshold in the request response data generated by the service system, at this time, the request response data with the association degree smaller than or equal to the corresponding association degree threshold is used as the unassociated data, and the service interface of the unassociated data is directly reserved as the data interface corresponding to the unassociated data.
In this embodiment, by determining the association data among the request response data generated by the service system, the request response data with the association higher than the association threshold is determined as the target data according to the association data, and the service interface of the target data is divided into the same data interface, so that when a request corresponding to the target data is received, the data is input or output from the divided data interface, and the service interfaces are merged according to the association data, so that the access condition, the uploading and downloading condition, and the like of accessing the service system by the target data are identified according to the merged data interface, and a system administrator is facilitated to perform centralized management on the data interfaces, which is beneficial to improving the efficiency of interface identification and interface management.
Referring to fig. 6, fig. 6 is a flowchart of a second embodiment of a service system interface identification method of the present invention, in this embodiment, the service system interface identification method includes the following steps:
step S11: determining the association degree data among request response data generated by a service system;
step S12: determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold;
step S13: dividing the service interface of the target data into the same data interface;
step S14: classifying the divided data interfaces according to the classification parameters of the target data, and dividing the divided data interfaces into different types of data interfaces so as to transmit data from the data interfaces of the corresponding types when the target data is requested.
In this embodiment, after determining association data between request response data generated by a service system, and determining target data according to the association data, and dividing service interfaces of the target data into the same data interface, because there may be a plurality of divided data interfaces, if the divided data interfaces are more, the divided data interfaces are not classified and labeled, and thus, a long identification time and an error in the identification process are likely to occur in the interface identification process, and a manager of the service system is not used to manage a plurality of interfaces.
Therefore, the present embodiment provides a better classification method, classifying the divided data interfaces according to the classification parameters of the target data, and classifying the divided data interfaces into different types of data interfaces, where the classification parameters include a request type, a return type, a request mode, access information, a website path depth, a request association degree, and a response association degree, where the request type refers to a data type of request data generated by a service system, and includes json/xml/url _ areas/url encoded-form, and the like; the return type refers to the data type of response data generated by the service system, and comprises json/xml/html and the like; the request mode comprises resource acquisition GET, new resource POST and the like; the access information corresponds to a host field in the http header, and the domain name/IP address and port number information of the http server appointed to be accessed by the client can be obtained through the host field; the website path depth is url depth and represents the number of levels of a webpage; the request association degree refers to the association degree of request data generated by a service system, and comprises the association degree of the request data of different data types; the response relevance refers to the relevance of response data generated by the business system, and comprises the relevance of response data of different data types. The above-mentioned parameters as the classification parameters are only a preferred embodiment of this embodiment. The classification parameter may be a combination of the above-mentioned parameter and other parameters as a classification parameter, or one or more of the above-mentioned parameters are selected as a classification parameter, or a combination of some of the above-mentioned parameters and other parameters is selected as a classification parameter, or of course, other parameters that do not include the above-mentioned parameters may be used as a classification parameter, and the like. The corresponding parameters may be specifically selected as the classification parameters according to the type of the service system, the application environment of the service system, the number of data interfaces, and the like, and the specific parameters included in the classification parameters are not limited herein.
After the divided data interfaces are divided into data interfaces of different categories according to the classification parameters of the target data, acquiring feature information of the target data corresponding to each classified data interface, wherein the feature information is common information of the target data corresponding to each data interface, the common information is used as the feature information of the target data corresponding to each data interface, and the feature information is used as interface information corresponding to each data interface to define each data interface (or to paste a corresponding label on each data interface).
In the embodiment, by determining the association degree data among the request response data generated by the service system, the request response data with the association degree higher than the association degree threshold is determined as the target data according to the association degree data, after the target data is determined, dividing the service interface of the target data into the same data interface, classifying the divided data interfaces according to the classification parameters of the target data, dividing the divided data interfaces into different types of data interfaces, so as to transmit data from the data interface of the corresponding category when the target data is requested, thereby facilitating the business system to identify the data interface corresponding to the target data request according to the classified data interface, and the user can conveniently manage the interface and the service system according to the classified data interface, thereby further improving the efficiency and the efficiency of identifying the service system interface and further improving the efficiency and the effect of managing the service system interface.
Referring to fig. 7, fig. 7 is a flowchart of a third embodiment of a service system interface identification method of the present invention, in this embodiment, the service system interface identification method includes the following steps:
step S21: determining the association degree data among request response data generated by a service system;
step S22: determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold;
step S23: dividing the service interface of the target data into the same data interface;
step S24: constructing a parent-child relationship among all service system interfaces according to a data head source address field of target data and a hyperlink in a target data response body;
step S25: and generating an interface relation tree of the business system based on the parent-child relation, and identifying the hierarchical relation of the business system interface based on the interface relation tree.
In this embodiment, after determining association degree data among request response data generated by a service system, determining the request response data with the association degree higher than a desired humidity threshold as target data according to the association degree data, dividing a service interface of the target data into the same data interface, constructing a parent-child relationship among the service system interfaces according to a data header source address field of the target data and a hyperlink in a target data response body, generating an interface relationship tree of the service system based on the parent-child relationship, and identifying a hierarchical relationship of the service system interfaces based on the interface relationship tree.
Specifically, referring to fig. 8, based on the service interface identified in the previous step, it is determined whether there are landmark fields such as "home", "dashboard (dashboard)", and "workbench", if there is the landmark field in the title, the current service interface is marked as home/title, if there is no landmark field in the title, it is determined whether the last path in the url contains landmark fields such as "home", "dashboard (dashboard)", and "workbench", if there is the landmark field in the last path in the url, the current service interface is marked as home/url, if there is the landmark field in the last path in the url, the same service interface is aggregated, and the most likely service interface is selected as the home page according to the priority order of home/title, home/url, and shortest url. Meanwhile, extracting a father service interface according to a data head source address (referrer) field of the request data, judging whether the returned data is in an html format, if the returned data is in the html format, analyzing an href label (designating a url of a hyperlink target), extracting a son service interface, if the returned data is not in the html format, aggregating the same service interface, and establishing a relationship graph of each interface according to the father-son relationship corresponding to the father service interface and the son service interface. And then, after the homepage is selected and the relationship graph of each interface is established, the last root node is obtained again according to the priority sequence of the root node with the priority of the home/title and the shortest url, a simplified relationship graph is searched through breadth first, an interface relationship tree of the service system is generated, and the hierarchical relationship of the interfaces of the service system can be identified based on the interface relationship tree.
In this embodiment, association data among request response data generated by a service system is determined, target data is determined according to the association data, service interfaces of the target data are divided into the same data interface after the target data is determined, parent-child relationships among the interfaces of each service system are constructed according to a data header source address field of the target data and hyperlinks in a target data response body after the interfaces are combined, an interface relationship tree of the service system is generated based on the parent-child relationships, not only can interface identification be realized according to the interface relationship tree, but also hierarchical relationships among different interfaces can be identified, interface identification can be realized more rapidly according to the hierarchical relationships, errors are not easy to occur in the identification process, the efficiency and effect of interface identification are improved, and the time for interface management of a user can be shortened according to the hierarchical relationships, the management process is more convenient, so that the efficiency and the effect of interface management are improved.
In addition, an embodiment of the present invention further provides a service system interface identification device, where the service system interface identification device includes a memory, a processor, and a service system interface identification program that is stored on the processor and can be run on the processor, and the processor implements the steps of the service system interface identification method when executing the service system interface identification program.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a service system interface identification program is stored on the computer-readable storage medium, and when executed by a processor, the service system interface identification program implements the steps of the service system interface identification method described above.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a television, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A service system interface identification method is characterized by comprising the following steps:
determining the association degree data among request response data generated by a service system;
determining target data according to the association degree data, wherein the association degree between request response data in the target data is above an association degree threshold;
and dividing the service interface of the target data into the same data interface so as to transmit data from the data interface when the target data is requested.
2. The service system interface identification method of claim 1 wherein said step of determining relevancy data between request response data generated by the service system comprises:
acquiring data types of request response data generated by a service system, and determining a relevancy extractor corresponding to each data type;
and determining the association degree data among the request response data of each data type by using the association degree extractor corresponding to each data type.
3. The service system interface identification method according to claim 2, wherein the step of obtaining data types of request response data generated by the service system and determining the association extractor corresponding to each data type comprises:
if the data type is a first data type, determining that an association extractor corresponding to the first data type is a first association extractor;
if the data type is a second data type, determining that an association extractor corresponding to the second data type is a second association extractor;
if the data type is a third data type, determining that an association extractor corresponding to the third data type is a third association extractor; the first data type is an html data type, the second data type is a json data type, and the json data type comprises: and the third data type is other data types except the first data type and the second data type.
4. The business system interface identification method of claim 3 wherein the step of determining the association data between the request response data for each data type using the association extractor corresponding to each data type comprises:
if the data type is the first data type, a first relevance extractor is used for obtaining a weighted average value of the style relevance, the structure relevance and the display content relevance of the request response data of the first data type, and the weighted average value is determined as relevance data of target data of the first data type;
if the data type is a second data type, taking the key name and the structure type of the request response key after the value is removed and the key is left as matching conditions, calculating the matching times of the matching conditions by using a second relevancy extractor, and determining relevancy data of target data of the second data type according to the matching times;
and if the data type is a third data type, extracting fingerprint information of the target data of the third data type by using a third association extractor, and determining association data of the target data of the third data type according to the fingerprint information.
5. The service system interface identification method according to any one of claims 1 to 4, wherein said determining target data based on said relevancy data, said step of determining relevancy between request response data in said target data above a relevancy threshold comprises:
determining the association degree between the request response data of each data type according to the association degree data;
judging whether the association degree between the request response data of each data type exceeds a corresponding association degree threshold value or not;
and if so, determining the associated data with the association degree exceeding the corresponding association degree threshold value and the associated data type corresponding to the associated data, and determining the associated data as the target data corresponding to the associated data type.
6. The service system interface identification method according to claim 1, wherein said step of dividing the service interface of the target data into the same data interface for data transmission from the data interface when the target data is requested further comprises:
classifying the divided data interfaces according to the classification parameters of the target data, and dividing the divided data interfaces into different types of data interfaces so as to transmit data from the data interfaces of the corresponding types when the target data is requested; the classification parameters include: request type, return type, request mode, access information, website path depth, request association degree and response association degree.
7. The service system interface identification method according to claim 6, wherein said step of classifying said divided data interfaces into different classes of data interfaces for data transmission from the corresponding class of data interface upon a target data request comprises:
acquiring feature information of the classified target data corresponding to each type of data interface, and taking the feature information as interface information corresponding to each type of data interface;
and defining each type of data interface according to the interface information so as to transmit data from the data interface of the corresponding type according to the definition of each type of data interface when a target data request is made.
8. The service system interface identification method according to claim 1, wherein said step of dividing the service interface of the target data into the same data interface for data transmission from the data interface when the target data is requested further comprises:
constructing a parent-child relationship among all service system interfaces according to a data head source address field of target data and a hyperlink in a target data response body;
and generating an interface relation tree of the business system based on the parent-child relation, and identifying the hierarchical relation of the business system interface based on the interface relation tree.
9. A service system interface identification device, comprising a memory, a processor and a service system interface identification program stored in the memory and executable on the processor, wherein the processor implements the steps of the service system interface identification method according to any one of claims 1 to 8 when executing the service system interface identification program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a service system interface identification program, which when executed by a processor implements the steps of the service system interface identification method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911425810.0A CN111209325B (en) | 2019-12-31 | 2019-12-31 | Service system interface identification method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911425810.0A CN111209325B (en) | 2019-12-31 | 2019-12-31 | Service system interface identification method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111209325A true CN111209325A (en) | 2020-05-29 |
| CN111209325B CN111209325B (en) | 2024-02-23 |
Family
ID=70788611
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911425810.0A Active CN111209325B (en) | 2019-12-31 | 2019-12-31 | Service system interface identification method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111209325B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112992137A (en) * | 2021-01-29 | 2021-06-18 | 青岛海尔科技有限公司 | Voice interaction method and device, storage medium and electronic device |
| CN114885359A (en) * | 2022-06-09 | 2022-08-09 | 中国联合网络通信集团有限公司 | Time delay performance evaluation method, access network device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080215673A1 (en) * | 2007-03-01 | 2008-09-04 | International Business Machines Corporation | Data Processing Method For Generating Service Interface Descriptions |
| CN103970899A (en) * | 2014-05-27 | 2014-08-06 | 重庆大学 | Service-oriented metadata relevance extraction management method and management system |
| US20180113586A1 (en) * | 2016-10-25 | 2018-04-26 | International Business Machines Corporation | Context aware user interface |
| CN110515676A (en) * | 2019-07-11 | 2019-11-29 | 平安普惠企业管理有限公司 | Interface integration method, device, equipment and storage medium |
-
2019
- 2019-12-31 CN CN201911425810.0A patent/CN111209325B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080215673A1 (en) * | 2007-03-01 | 2008-09-04 | International Business Machines Corporation | Data Processing Method For Generating Service Interface Descriptions |
| CN103970899A (en) * | 2014-05-27 | 2014-08-06 | 重庆大学 | Service-oriented metadata relevance extraction management method and management system |
| US20180113586A1 (en) * | 2016-10-25 | 2018-04-26 | International Business Machines Corporation | Context aware user interface |
| CN110515676A (en) * | 2019-07-11 | 2019-11-29 | 平安普惠企业管理有限公司 | Interface integration method, device, equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112992137A (en) * | 2021-01-29 | 2021-06-18 | 青岛海尔科技有限公司 | Voice interaction method and device, storage medium and electronic device |
| CN114885359A (en) * | 2022-06-09 | 2022-08-09 | 中国联合网络通信集团有限公司 | Time delay performance evaluation method, access network device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111209325B (en) | 2024-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11150874B2 (en) | API specification generation | |
| US9954886B2 (en) | Method and apparatus for detecting website security | |
| CN108805694B (en) | Credit consultation service method, apparatus, device and computer readable storage medium | |
| CN109376291B (en) | Website fingerprint information scanning method and device based on web crawler | |
| AU2014400621B2 (en) | System and method for providing contextual analytics data | |
| US10452730B2 (en) | Methods for analyzing web sites using web services and devices thereof | |
| WO2017124692A1 (en) | Method and apparatus for searching for conversion relationship between form pages and target pages | |
| CN110798445B (en) | Public gateway interface testing method and device, computer equipment and storage medium | |
| EP2857987A1 (en) | Acquiring method, device and system of user behavior | |
| CN111209325B (en) | Service system interface identification method, device and storage medium | |
| KR20190058141A (en) | Method for generating data extracted from document and apparatus thereof | |
| CN111177481B (en) | User identifier mapping method and device | |
| CN107786529B (en) | Website detection method, device and system | |
| CN103793495A (en) | Application message search method and system and application message acquisition method and system | |
| CN109862074B (en) | Data acquisition method and device, readable medium and electronic equipment | |
| CN105893584A (en) | Method, client and system for displaying website label of favorites | |
| CN116776030A (en) | Gray release method, device, computer equipment and storage medium | |
| CN115801455B (en) | Method and device for detecting counterfeit website based on website fingerprint | |
| CN112035744A (en) | Page recommendation method, device, equipment and storage medium | |
| CN111314326A (en) | Method, device, equipment and medium for confirming HTTP vulnerability scanning host | |
| CN113806647A (en) | Method for identifying development framework and related equipment | |
| CN105677827B (en) | A kind of acquisition methods and device of list | |
| US20140337069A1 (en) | Deriving business transactions from web logs | |
| CN114356991A (en) | Data query method, data aggregation method, device, equipment and medium | |
| CN114490246A (en) | Monitoring method, monitoring device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |