Information labeling method and apparatus

Abstract

The present disclosure relates to the technical field of data processing, and particularly relates to an information labeling method and device. The information labeling method comprises: in the case that a credit dispute information set is inputted in a first system, acquiring the credit dispute information set through a first network crawler, wherein the credit dispute information set is used to indicate that an information set corresponding to an information subject of any credit dispute information in the credit dispute information set does not meet information requirements; sending a labeling request to a labeling uniform resource locator (URL) of a second system through a second network crawler, wherein the credit dispute information set is carried in the labeling request, and the any credit dispute information is used to label a credit report corresponding to the information subject of the any credit dispute information. The present disclosure can reduce waste of human resources and improve credit dispute input efficiency.

Description

Technical Field

[0001] This disclosure relates to the field of data processing technology, and in particular to an information annotation method and apparatus. Background Technology

[0002] With the development of science and technology, credit reporting agencies can collect credit dispute information from individuals. Credit reporting agency staff can then input this information into various commercial banks. Credit reporting managers can then re-enter the information at the credit reporting center based on the manually entered information from the commercial banks. Therefore, this process requires staff to repeatedly enter the credit dispute information, wasting human resources and reducing the efficiency of credit dispute entry. Summary of the Invention

[0003] This disclosure provides an information annotation method and apparatus to reduce the waste of human resources while improving the efficiency of credit dispute entry. The technical solution of this disclosure is as follows:

[0004] According to a first aspect of the present disclosure, an information annotation method is provided, comprising:

[0005] When the credit dispute information set is entered into the first system, the credit dispute information set is obtained through the first web crawler. The credit dispute information set is used to indicate that the information set corresponding to the information subject of any credit dispute information in the credit dispute information set does not meet the information requirements.

[0006] A second web crawler sends a labeling request to the labeling Uniform Resource Locator (URL) of the second system. The labeling request carries the set of credit dispute information, and any one of the credit dispute information is used to label the credit report corresponding to the information subject of the credit dispute information.

[0007] According to some embodiments, before sending the annotation request to the annotation Uniform Resource Locator URL of the second system via the second web crawler, the method further includes:

[0008] Obtain the input parameter information of the second system;

[0009] The second web crawler sends an access request to the login Uniform Resource Locator URL of the second system, wherein the access request carries the input parameter information;

[0010] Obtain the first response data sent by the second system in response to the access request;

[0011] If the first response data indicates that the input parameter information meets the access permission requirements of the second system, the small text file cookie information in the first response data is obtained and stored.

[0012] According to some embodiments, after obtaining and storing the small text file cookie information in the first response data, the method further includes:

[0013] The second web crawler sends an objection annotation interface token request to the token unified resource locator URL of the second system.

[0014] Obtain the second response data sent by the second system in response to the objection annotation interface token request;

[0015] If the second response data indicates that the objection labeling interface token request has passed, the token data in the second response data is obtained and stored.

[0016] According to some embodiments, after sending the annotation request to the annotation Uniform Resource Locator URL of the second system via the second web crawler, the method further includes:

[0017] The second web crawler sends a label query request to the label query Uniform Resource Locator URL of the second system.

[0018] The second system sends a third response data in response to the annotation query request, wherein the third response data includes a set of elements of the requested page;

[0019] Obtain and store the annotation data set included in the requested page element set, wherein the annotation data set includes at least one annotation number and the annotation status corresponding to any one of the at least one annotation number.

[0020] According to some embodiments, the method further includes:

[0021] Based on the labeled data set and the credit dispute information set, dispute label deletion information is determined, wherein the dispute label deletion information includes a dispute deletion label identifier;

[0022] The second web crawler sends an objection label deletion request to the deletion label Uniform Resource Locator URL of the second system, wherein the objection label deletion request includes the objection deletion label identifier and the token data;

[0023] Obtain the fourth response data sent by the second system in response to the objection label deletion request;

[0024] The result information is queried on the fourth response data. If the fourth response data includes processing completion information, it is determined that the deletion of the objection label has been completed.

[0025] According to some embodiments, after obtaining the fourth response data sent by the second system in response to the objection label deletion request, the method further includes:

[0026] The result information is queried on the fourth response data. If the fourth response data includes information indicating that the processing was not completed, it is determined that the deletion of the objection mark has not been completed, and a prompt message is issued.

[0027] According to some embodiments, sending the annotation request to the annotation Uniform Resource Locator (URL) of the second system via the second web crawler includes:

[0028] The annotation HTTP request is sent via jsoup to the annotation Uniform Resource Locator URL of the second system.

[0029] According to a second aspect of the present disclosure, an information annotation device is provided, comprising:

[0030] The set acquisition unit is used to acquire the credit dispute information set through a first web crawler when the credit dispute information set is entered into the first system. The credit dispute information set is used to indicate that the information set corresponding to the information subject of any credit dispute information in the credit dispute information set does not meet the information requirements.

[0031] The request sending unit is used to send a labeling request to the labeling Uniform Resource Locator URL of the second system through a second web crawler, wherein the labeling request carries the set of credit dispute information, and any credit dispute information is used to label the credit report corresponding to the information subject of the credit dispute information.

[0032] According to a third aspect of the present disclosure, a terminal device is provided, comprising:

[0033] processor;

[0034] Memory used to store the processor's executable instructions;

[0035] The processor is configured to execute the instructions to implement the information annotation method described in any one of the preceding aspects.

[0036] According to a fourth aspect of the present disclosure, a storage medium is provided that, when instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the information annotation method described in any of the preceding aspects.

[0037] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method described in any one of the preceding aspects.

[0038] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0039] In some or related embodiments, after the credit dispute information set is entered into the first system, the credit dispute information set is obtained through a first web crawler. This set is used to indicate that the information set corresponding to the subject of any credit dispute information in the set does not meet the information requirements. A second web crawler sends a labeling request to the labeling Uniform Resource Locator (URL) of the second system. The labeling request carries the credit dispute information set, and each credit dispute information is used to label the credit report corresponding to the subject of that credit dispute information. Therefore, by using a web crawler, the credit dispute information set entered in the first system can be labeled in the second system. This reduces repetitive manual entry and the time spent manually entering the credit dispute information set in the second system, reducing the number of entry steps and thus improving the efficiency of credit dispute entry while reducing human resource waste.

[0040] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0041] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0042] Figure 1 This is a flowchart illustrating an information annotation method according to an exemplary embodiment;

[0043] Figure 2 This is a flowchart illustrating an information annotation method according to an exemplary embodiment;

[0044] Figure 3 This is a flowchart illustrating an information annotation method according to an exemplary embodiment;

[0045] Figure 4 This is a block diagram illustrating an information labeling device according to an exemplary embodiment;

[0046] Figure 5 This is a block diagram illustrating a terminal device according to an exemplary embodiment. Detailed Implementation

[0047] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0048] This disclosure provides an information annotation method and apparatus. In some embodiments, the terms "information annotation method" and "information processing method," "communication method," etc., can be used interchangeably; the terms "information annotation apparatus" and "information processing apparatus," "communication apparatus," etc., can be used interchangeably; and the terms "information processing system," "communication system," etc., can be used interchangeably.

[0049] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0050] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0051] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0052] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

[0053] In the embodiments disclosed herein, "multiple" refers to two or more.

[0054] In some embodiments, the terms “at least one of,” “one or more,” “a plurality of,” and “multiple” may be used interchangeably.

[0055] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (executes A regardless of B); in some embodiments, B (executes B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0056] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, selective execution from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0057] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0058] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0059] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0060] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0061] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

[0062] In some embodiments, "network" can be interpreted as devices included in the network, such as access network devices, core network devices, etc.

[0063] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," etc.

[0064] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0065] In some embodiments, data, information, etc. may be obtained after obtaining the user's consent.

[0066] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0067] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects 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 disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0068] Figure 1 This is a flowchart illustrating an information annotation method according to an exemplary embodiment, such as... Figure 1 As shown, it includes the following steps:

[0069] In step S11, after the credit dispute information set is entered into the first system, the credit dispute information set is obtained through the first web crawler.

[0070] According to some embodiments, the credit dispute information set is used to indicate that the information set corresponding to the information subject of any credit dispute information in the credit dispute information set does not meet the information requirements.

[0071] In some embodiments, the first system may refer to a system for recording credit dispute information. This first system may also include processes such as reviewing and verifying the dispute information. This system is not specifically defined by any particular system. For example, the first system could be any commercial bank, or any system that provides credit dispute information. Therefore, the first system could be Commercial Bank A, or it could be Commercial Bank B, for example.

[0072] According to some embodiments, a credit reporting objection can be, for example, a situation where an information subject confirms that the information collected, stored, or provided by the credit reporting agency contains errors or omissions, and raises an objection with the credit reporting objection agency. Therefore, this credit reporting objection information does not specifically refer to any fixed piece of information. For example, the Q1 credit reporting anomaly information could be that the information corresponding to information subject q1 is incorrect. For example, the Q2 credit reporting anomaly information could be that the information corresponding to information subject q2 is missing.

[0073] Optionally, the entry of credit dispute information set can refer to, for example, entering information into the first system based on credit dispute cases involving a set of information subjects. This credit dispute information set does not specifically refer to a fixed set. For example, when the number of information items corresponding to the credit dispute information set changes, the credit dispute information set can also change accordingly. For example, when any credit dispute information item in the credit dispute information set changes, the credit dispute information set can also change accordingly. The credit dispute information set can, for example, include one credit dispute item, or it can include multiple credit dispute items.

[0074] In one embodiment of this disclosure, the first web crawler may refer to a web crawler that obtains a set of credit dispute information from a first system. The "first" in the first web crawler is only used to distinguish the second web crawler and does not specifically refer to a certain fixed crawler technology.

[0075] According to some embodiments, an information set refers to a collection of at least one piece of information corresponding to an information subject, the information included in the information set being used to indicate the credit information of the information subject. For example, the information set may include the information subject's basic personal information, credit record information, query record information, etc. The basic personal information may include, for example, personal identification information, residential information, occupational information, education information, etc.

[0076] In some embodiments, information requirements can be used, for example, to determine whether the information set corresponding to the information subject is consistent with the actual information of the information subject.

[0077] According to some embodiments, after the credit dispute information set is entered into the first system, the credit dispute information set is obtained through a first web crawler. The entry of the credit dispute information set into the first system can be, for example, done manually.

[0078] In step S12, a labeling request is sent to the labeling Uniform Resource Locator URL of the second system via the second web crawler.

[0079] In one embodiment of this disclosure, the annotation request carries a set of credit reporting objection information, and any credit reporting objection information is used to annotate the credit report corresponding to the information subject of any credit reporting objection information.

[0080] Among them, the annotation of credit dispute information can be, for example, by adding text descriptions to the credit report corresponding to the information subject in the second system, i.e., the target bank or credit reporting center, as needed. These text descriptions are used to indicate that there are disputes regarding the information of the information subject.

[0081] In some embodiments, the second web crawler refers to a crawler technology used to annotate credit dispute information in a second system. The "second" in "second web crawler" is used only to distinguish it from the first web crawler. For example, the second web crawler can also change accordingly when the triggering method changes.

[0082] According to some embodiments, the annotation request is a request to annotate credit dispute information. This annotation request is not specifically a fixed request; for example, when the set of credit dispute information obtained through the first web crawler changes, the annotation request can also change accordingly. For example, when the sending time of the annotation request changes, the annotation request can also change accordingly.

[0083] According to some embodiments, the second system may be used, for example, to instruct a system that needs to add textual descriptions to a report corresponding to an information subject, such as labeled credit abnormality information. The second system may be, for example, a credit reporting center.

[0084] In some embodiments, the URL used to annotate a set of credit dispute information refers to a URL used to annotate the set of credit dispute information.

[0085] According to some embodiments, when the credit dispute information set is entered into the first system, the credit dispute information set is obtained through the first web crawler, and the annotation request is sent to the annotation Uniform Resource Locator URL of the second system through the second web crawler. The annotation request carries the credit dispute information set, and the credit report of the information subject corresponding to the credit dispute information set can be annotated in the second system.

[0086] In some or related embodiments, after the credit dispute information set is entered into the first system, a first web crawler retrieves the credit dispute information set, which is used to indicate that the information set corresponding to the information subject of any credit dispute information in the set does not meet the information requirements. A second web crawler sends a labeling request to the labeling Uniform Resource Locator (URL) of the second system, wherein the labeling request carries the credit dispute information set, and any credit dispute information is used to label the credit report corresponding to the information subject of any credit dispute information. Therefore, by using a web crawler, the credit dispute information set entered into the first system can be labeled in the second system, which can reduce repetitive manual entry, reduce the time spent on manually entering the credit dispute information set in the second system, reduce the number of entry steps, and thus improve the efficiency of credit dispute entry while reducing the waste of human resources.

[0087] Figure 2 This is a flowchart illustrating an information annotation method according to an exemplary embodiment, such as... Figure 2 As shown, it includes the following steps:

[0088] In step S21, after the credit dispute information set is entered into the first system, the credit dispute information set is obtained through the first web crawler.

[0089] The specific process is as described above and will not be repeated here.

[0090] Among them, the credit dispute information set is used to indicate that the information set corresponding to the information subject of any credit dispute information in the credit dispute information set does not meet the information requirements.

[0091] According to some embodiments, the first system may be, for example, system A. The bank corresponding to system A may, for example, add a credit dispute management position, which can input information sets of information subjects. When the information set input is complete, the "Credit Dispute Selected" control can be clicked to obtain the credit dispute information. For example, when the information set of at least one information subject is marked as complete and the submit control is clicked, it can be determined that the input of the credit dispute information set in system A is complete.

[0092] In step S22, the input parameter information of the second system is obtained;

[0093] The specific process is as described above and will not be repeated here.

[0094] According to some embodiments, the triggering condition for labeling the credit dispute information set in the second system may be, for example, receiving an input labeling instruction. This disclosure does not limit this. For example, the labeling of the credit dispute information set in the second system may also be triggered when it is determined that the credit dispute information set has been obtained.

[0095] According to some embodiments, the input parameter information is used to log in to the second system, that is, to obtain the permission to process credit dispute information in the second system. This permission includes, but is not limited to, annotating and deleting credit dispute information.

[0096] The input parameters include, but are not limited to, login name, signature, and password.

[0097] According to some embodiments, when a set of credit dispute information is obtained, the input parameter information of the second system can be obtained.

[0098] In step S23, an access request is sent to the login Uniform Resource Locator URL of the second system via the second web crawler;

[0099] Specifically, an access request is sent to the login Uniform Resource Locator URL of the second system via a second web crawler, and the access request carries input parameter information.

[0100] According to some embodiments, the access request is used to obtain permission to access a second system, specifically permission to process a set of credit dispute information. This permission could also be, for example, full permission to access the second system. The access request is not specific to a particular fixed request; for example, the access request can change accordingly when the input parameter information included in it changes.

[0101] According to some embodiments, the second system may be, for example, the target system. The access request may be, for example, a first HTTP request. Specifically, for example, the first HTTP request may be sent via jsoup, with the request address being the login URL of the target system. The first HTTP request may include, for example, input parameter information.

[0102] In step S24, the first response data sent by the second system in response to the access request is obtained;

[0103] According to some embodiments, the first response data refers to the response data provided in response to an access request. This first response data does not specifically refer to a single, fixed response data. For example, the first response data may change accordingly when the information included in it changes.

[0104] In some embodiments, the first response data sent by the second system in response to the access request can be obtained.

[0105] In step S25, if the first response data indicates that the input parameter information meets the access permission requirements of the second system, the small text file cookie information in the first response data is obtained and stored.

[0106] According to some embodiments, upon receiving the first response data, the first response data can be identified. If the first response data indicates that the input parameter information meets the access permission requirements of the second system, a small text file cookie information from the first response data is acquired and stored.

[0107] According to some embodiments, if the first response data indicates that the input parameter information does not meet the access permission requirements of the second system, a prompt message can be issued to prompt the modification of the input parameter information.

[0108] According to some embodiments, the method further includes:

[0109] The system sends a request for a token to the objection labeling interface to the Token Uniform Resource Locator (URL) of the second system via a second web crawler; it then obtains the second response data sent by the second system in response to the request; if the second response data indicates that the request has been approved, it retrieves and stores the token data from the second response data. Therefore, the token data can be obtained and used for information transmission through the objection labeling interface, improving the accuracy of the credit objection information set labeling.

[0110] In some embodiments, the objection annotation interface token request can be, for example, a second HTTP request. For instance, a second HTTP request can be sent via jsoup to the target system's token Uniform Resource Locator URL.

[0111] According to some embodiments, the second response data refers to the response data fed back in response to the objection annotation interface token request. This second response data does not specifically refer to any single fixed response data. For example, when the information included in the second response data changes, the second response data may also change accordingly.

[0112] Upon receiving the second response data, it can be identified. If the second response data indicates that the objection labeling interface token request passed, the token data in the second response data is acquired and stored. If the second response data indicates that the objection labeling interface token request failed, i.e., the second response data includes error information, the objection labeling interface token request can be re-initiated or a prompt message can be issued.

[0113] In step S26, a labeling request is sent to the labeling Uniform Resource Locator URL of the second system via the second web crawler.

[0114] The annotation request carries a set of credit reporting objection information, and any one of the credit reporting objection information is used to annotate the credit report corresponding to the information subject of any credit reporting objection information.

[0115] The specific process is as described above and will not be repeated here.

[0116] According to some embodiments, after sending the annotation request to the annotation Uniform Resource Locator URL of the second system via the second web crawler, the method further includes:

[0117] Send annotation query requests to the annotation query Uniform Resource Locator URL of the second system via a second web crawler;

[0118] The second system sends a third response data in response to the annotation query request, wherein the third response data includes a set of elements of the requested page;

[0119] The system acquires and stores a set of labeled data, including the element set of the requested page. This set of labeled data includes at least one labeled number and a labeled status corresponding to any one of the labeled numbers. Therefore, the labeled data set can be obtained via web crawler, eliminating the need for manual acquisition and reducing labor costs while improving the efficiency of data acquisition.

[0120] The annotation query request can be, for example, a third HTTP request. For instance, a third HTTP request can be sent via jsoup to the annotation query Uniform Resource Locator (URL) of the second system. The third response data can be, for example, data returned in response to the annotation query request. If the third response data does not include the annotation data set, it can be determined that the annotation data set does not exist. If the third response data does not include the annotation data set, the annotation data set included in the requested page element set can be obtained and stored. This annotation data set includes at least one annotation number and the annotation status corresponding to any one of the at least one annotation number.

[0121] According to some embodiments, the method further includes:

[0122] Based on the set of labeled data and the set of credit dispute information, the objection label deletion information is determined, which includes the objection deletion label identifier;

[0123] The second web crawler sends a request to delete the objection label to the URL of the deletion label in the second system. The request to delete the objection label includes the objection label deletion identifier and token data.

[0124] Obtain the fourth response data sent by the second system in response to the objection label deletion request;

[0125] The results of the fourth response data are queried. If the fourth response data includes processing completion information, the deletion of the objection mark is confirmed. Therefore, web crawlers can be used to determine whether a credit objection has been deleted, which can improve the accuracy of determining the deletion of credit objection information and reduce labor costs by eliminating the need for manual intervention.

[0126] In some embodiments, the objection label removal request may be a fourth HTTP request. For example, a fourth HTTP request can be sent via jsoup, with the request address being the objection label removal URL of the destination system. This fourth HTTP request may include, for example, the objection label removal identifier and token data.

[0127] According to some embodiments, after obtaining the fourth response data sent by the second system in response to the objection label deletion request, the method further includes:

[0128] The results information of the fourth response data is queried. If the fourth response data includes information on incomplete processing, it is determined that the deletion of the objection mark has not been completed, and a prompt message is issued.

[0129] According to some embodiments, sending a labeling request to the labeling Uniform Resource Locator (URL) of the second system via a second web crawler includes:

[0130] The annotation HTTP request is sent via jsoup to the annotation Uniform Resource Locator URL of the second system.

[0131] Figure 3 This is a flowchart illustrating an information annotation method according to an exemplary embodiment. For example, it may include: a credit dispute entry personnel entering information into a first system based on the objection information of the information subject. A first web crawler can be used to obtain and store the set of credit dispute information in the first system. Upon receiving an annotation instruction, a second web crawler can be used to annotate the set of credit dispute information in a second system.

[0132] In some or related embodiments, the following steps are taken: Input parameter information of the second system is obtained; an access request is sent to the login Uniform Resource Locator (URL) of the second system via a second web crawler; first response data is obtained from the second system in response to the access request; and if the first response data indicates that the input parameter information meets the access permission requirements of the second system, a small text file cookie information is obtained and stored from the first response data. Therefore, access permissions to the second system can be obtained through a web crawler, and these permissions can be used to annotate the credit dispute information set in the second system. This reduces repetitive manual data entry and the time spent manually entering the credit dispute information set in the second system, thus reducing the number of steps involved in entering the credit dispute information set. Consequently, the efficiency of credit dispute entry can be improved while reducing the waste of human resources.

[0133] Figure 4 This is a block diagram illustrating an information labeling device according to an exemplary embodiment. (Refer to...) Figure 4 The information labeling device 400 includes:

[0134] The set acquisition unit 401 is used to acquire the credit objection information set through the first web crawler when the credit objection information set is entered in the first system. The credit objection information set is used to indicate that the information set corresponding to the information subject of any credit objection information in the credit objection information set does not meet the information requirements.

[0135] The request sending unit 402 is used to send a labeling request to the labeling Uniform Resource Locator URL of the second system through the second web crawler. The labeling request carries a set of credit dispute information, and any credit dispute information is used to label the credit report corresponding to the information subject of any credit dispute information.

[0136] According to some embodiments, the request sending unit 402 is further configured to, before sending the annotation request to the annotation Uniform Resource Locator URL of the second system via the second web crawler:

[0137] Obtain the input parameter information of the second system;

[0138] The second web crawler sends an access request to the login Uniform Resource Locator URL of the second system, wherein the access request carries input parameter information;

[0139] Obtain the first response data sent by the second system in response to the access request;

[0140] If the input parameter information in the first response data indicates that the access permission requirements of the second system are met, the small text file cookie information in the first response data is obtained and stored.

[0141] According to some embodiments, the request sending unit 402 is further configured to, after acquiring and storing the small text file cookie information in the first response data:

[0142] Send a request for the objection annotation interface token to the token Uniform Resource Locator URL of the second system via the second web crawler;

[0143] The second system requests and sends a second response data in response to the objection annotation interface token request.

[0144] If the second response data indicates that the objection annotation interface token request has passed, the token data in the second response data is retrieved and stored.

[0145] According to some embodiments, the request sending unit 402 is further configured to, after sending the annotation request to the annotation Uniform Resource Locator URL of the second system via the second web crawler:

[0146] Send annotation query requests to the annotation query Uniform Resource Locator URL of the second system via a second web crawler;

[0147] The second system sends a third response data in response to the annotation query request, wherein the third response data includes a set of elements of the requested page;

[0148] Obtain and store the annotation data set included in the requested page element set, wherein the annotation data set includes at least one annotation number and the annotation status corresponding to any one of the at least one annotation number.

[0149] According to some embodiments, the request sending unit 402 is further configured to:

[0150] Based on the set of labeled data and the set of credit dispute information, the objection label deletion information is determined, which includes the objection deletion label identifier;

[0151] The second web crawler sends a request to delete the objection label to the URL of the deletion label in the second system. The request to delete the objection label includes the objection label deletion identifier and token data.

[0152] Obtain the fourth response data sent by the second system in response to the objection label deletion request;

[0153] Query the results information of the fourth response data. If the fourth response data includes processing completion information, confirm that the deletion of the objection label has been completed.

[0154] According to some embodiments, the request sending unit 402 is further configured to, after obtaining the fourth response data sent by the second system in response to the objection label deletion request:

[0155] The system queries the results information of the fourth response data. If the fourth response data includes information indicating that the processing was not completed, it determines that the deletion of the objection mark was not completed and issues a prompt message.

[0156] According to some embodiments, when the request sending unit 402 sends an annotation request to the annotation Uniform Resource Locator URL of the second system via the second web crawler, it is specifically used for:

[0157] The annotation HTTP request is sent via jsoup to the annotation Uniform Resource Locator URL of the second system.

[0158] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0159] In some or related embodiments, the set acquisition unit is used to acquire the credit objection information set through a first web crawler after the credit objection information set has been entered into the first system. The credit objection information set is used to indicate that the information set corresponding to the information subject of any credit objection information in the set does not meet the information requirements. The request sending unit is used to send a labeling request to the labeling Uniform Resource Locator (URL) of the second system through a second web crawler. The labeling request carries the credit objection information set, and any credit objection information is used to label the credit report corresponding to the information subject of any credit objection information. Therefore, by using a web crawler, the credit objection information set entered in the first system can be labeled in the second system. This reduces repetitive manual entry and the time spent manually entering the credit objection information set in the second system, and reduces the number of entry steps. Consequently, it improves the efficiency of credit objection entry while reducing human resource waste.

[0160] Figure 5This is a block diagram of a terminal device UE500 provided in one embodiment of this disclosure. For example, UE500 may be a mobile phone, computer, digital broadcasting terminal device, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.

[0161] Reference Figure 5 UE500 may include at least one of the following components: processing component 502, memory 504, power supply component 506, multimedia component 508, audio component 510, input / output (I / O) interface 512, sensor component 514, and communication component 516.

[0162] Processing component 502 typically controls the overall operation of UE 500, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 502 may include at least one processor 520 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 502 may include at least one module to facilitate interaction between processing component 502 and other components. For example, processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502.

[0163] Memory 504 is configured to store various types of data to support operation on UE 500. Examples of this data include instructions for any application or method operating on UE 500, contact data, phonebook data, messages, pictures, videos, etc. Memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0164] Power supply component 506 provides power to various components of UE500. Power supply component 506 may include a power management system, at least one power supply, and other components associated with generating, managing, and distributing power to UE500.

[0165] The multimedia component 508 includes a screen that provides an output interface between the UE 500 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes at least one touch sensor to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or swipe action but also detect the wake-up time and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 508 includes a front-facing camera and / or a rear-facing camera. When the UE 500 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0166] Audio component 510 is configured to output and / or input audio signals. For example, audio component 510 includes a microphone (MIC) configured to receive external audio signals when UE 500 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 504 or transmitted via communication component 516. In some embodiments, audio component 510 also includes a speaker for outputting audio signals.

[0167] I / O interface 512 provides an interface between processing component 502 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0168] Sensor assembly 514 includes at least one sensor for providing state assessment of various aspects of UE 500. For example, sensor assembly 514 can detect the on / off state of UE 500, the relative positioning of components such as the display and keypad of UE 500, changes in position of UE 500 or one of its components, the presence or absence of user contact with UE 500, orientation or acceleration / deceleration of UE 500, and temperature changes of UE 500. Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 514 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0169] Communication component 516 is configured to facilitate wired or wireless communication between UE 500 and other devices. UE 500 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 516 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0170] In an exemplary embodiment, UE500 may be implemented by at least one application-specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field-programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic component to perform the above method.

[0171] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0172] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0173] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0174] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0175] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), the Internet, and blockchain networks.

[0176] Computer systems can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. A server can be a cloud server, also known as a cloud computing server or cloud host, a hosting product within the cloud computing service system that addresses the shortcomings of traditional physical hosts and VPS (Virtual Private Server) services, such as high management difficulty and weak business scalability. Servers can also be servers for distributed systems or servers incorporating blockchain technology.

[0177] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0178] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. An information annotation method, characterized in that, include: When the credit dispute information set is entered into the first system, the credit dispute information set is obtained through the first web crawler. The credit dispute information set is used to indicate that the information set corresponding to the information subject of any credit dispute information in the credit dispute information set does not meet the information requirements. A second web crawler sends a labeling request to the labeling Uniform Resource Locator (URL) of the second system. The labeling request carries the set of credit dispute information, and any one of the credit dispute information is used to label the credit report corresponding to the information subject of the credit dispute information.

2. The method according to claim 1, characterized in that, Before sending the annotation request to the annotation Uniform Resource Locator (URL) of the second system via the second web crawler, the method further includes: Obtain the input parameter information of the second system; The second web crawler sends an access request to the login Uniform Resource Locator URL of the second system, wherein the access request carries the input parameter information; Obtain the first response data sent by the second system in response to the access request; If the first response data indicates that the input parameter information meets the access permission requirements of the second system, the small text file cookie information in the first response data is obtained and stored.

3. The method according to claim 2, characterized in that, After obtaining and storing the small text file cookie information in the first response data, the method further includes: The second web crawler sends an objection annotation interface token request to the token unified resource locator URL of the second system. Obtain the second response data sent by the second system in response to the objection annotation interface token request; If the second response data indicates that the objection labeling interface token request has passed, the token data in the second response data is obtained and stored.

4. The method according to claim 3, characterized in that, After sending the annotation request to the annotation Uniform Resource Locator (URL) of the second system via the second web crawler, the method further includes: The second web crawler sends a label query request to the label query Uniform Resource Locator URL of the second system. The second system sends a third response data in response to the annotation query request, wherein the third response data includes a set of elements of the requested page; Obtain and store the annotation data set included in the requested page element set, wherein the annotation data set includes at least one annotation number and the annotation status corresponding to any one of the at least one annotation number.

5. The method according to claim 4, characterized in that, The method further includes: Based on the labeled data set and the credit dispute information set, dispute label deletion information is determined, wherein the dispute label deletion information includes a dispute deletion label identifier; The second web crawler sends an objection label deletion request to the deletion label Uniform Resource Locator URL of the second system, wherein the objection label deletion request includes the objection deletion label identifier and the token data; Obtain the fourth response data sent by the second system in response to the objection label deletion request; The result information is queried on the fourth response data. If the fourth response data includes processing completion information, it is determined that the deletion of the objection label has been completed.

6. The method according to claim 5, characterized in that, After obtaining the fourth response data sent by the second system in response to the objection label deletion request, the method further includes: The result information is queried on the fourth response data. If the fourth response data includes information indicating that the processing was not completed, it is determined that the deletion of the objection mark has not been completed, and a prompt message is issued.

7. The method according to claim 1, characterized in that, The step of sending annotation requests to the annotation Uniform Resource Locator (URL) of the second system via the second web crawler includes: The annotation HTTP request is sent via jsoup to the annotation Uniform Resource Locator URL of the second system.

8. An information labeling device, characterized in that, include: The set acquisition unit is used to acquire the credit dispute information set through a first web crawler when the credit dispute information set is entered into the first system. The credit dispute information set is used to indicate that the information set corresponding to the information subject of any credit dispute information in the credit dispute information set does not meet the information requirements. The request sending unit is used to send a labeling request to the labeling Uniform Resource Locator URL of the second system through a second web crawler, wherein the labeling request carries the set of credit dispute information, and any credit dispute information is used to label the credit report corresponding to the information subject of the credit dispute information.

9. A terminal device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the information annotation method as described in any one of claims 1 to 7.

10. A storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the information annotation method as described in any one of claims 1 to 7.

Images